Do we consider migrating to sveltekit

As we start to think about supporting a backend, should we consider looking in detail at something like sveltekit as a framework we could use?
Particularly interested @dabreegster your thoughts, did you look at this initially?

I've read through the SvelteKit docs and don't understand what it would buy us. But I also haven't done web dev in over a decade, so maybe I'm just stuck on the frontend / backend / database architecture.
https://kit.svelte.dev/docs/introduction#sveltekit-vs-svelte talks about intercepting links and making multiple URLs/pages be implemented without navigating away. Right now, we've only got 3 pages (homepage to choose an area, an internal-focused browse scheme page, and the main editor). I don't understand the purpose of swapping out part of the page, instead of using all the browser-native handling of multiple pages. (aka, I don't think we really care about being a "Single Page App")
Offline support and prerendering part of the page server-side also don't sound relevant. If we wanted ATIP to work offline, we're pretty close to that -- would need #45 to remove the dependency on remote map tiles. Our pages are quite simple DOM-wise; prerendering anything on a server has no purpose I can see.
To me it kind of sounds like SvelteKit mixes the frontend/backend code in a kind of confusing way. Do we even want to write the backend in TS?
Alternatives
I propose spinning this question around and starting from what we want the authenticated version of ATIP to do. I started some user stories for different groups of users in #229. From that we can figure out how to evolve the Svelte app. Very roughly, I would picture some stuff like:

a new page for login / account management, mostly using fetch with a backend
something to plumb around logged-in state, like cookies / sessions; I'm kind of assuming the GDS auth layer provides this, but I haven't dug into it yet
Some new pages and regular Svelte UI components to show a scheme's timeline, manage feedback, upload files, etc. Most of these would call an API.

New page for login sounds good, that can be navigated to from link/button on open version presumably. Slightly off topic but the UI will change depending on logged-in status, right? I was thinking of a placeholder button in the open version that does nothing or says "Authenticated version in progress" or something. Alex and I discussed this yesterday and I now realise that the changes for the authenticated version will take a lot of work and that we should start on that soon.
I don't have an opinion about the choice of software, just want the codebase to be easy to develop and deploy in other places so the generalisability of the solution should be a factor also, would it be easy to spin-up an authenticated version in Scotland, for example?

Alex and I discussed this yesterday and I now realise that the changes for the authenticated version will take a lot of work and that we should start on that soon.

Could we sketch out what the important parts are to get working in the short-term? In the backend PR doc, I proposed stuff like feedback and a timeline view that could take longer to build. If the real MVP is just auth, a way to upload new versions of files for LAs, and a way to browse all schemes, this is probably something we could prototype much faster.

Could we sketch out what the important parts are to get working in the short-term?

@Sparrow0hawk on the case, please send us stuff for review, maybe the demand doc covers some of it? Would be good to get your comments on that Dustin if you've not looked over yet.

There are open questions around what the priorities are for authentication, however. My view, given that dashboard by @becfleming-ate covers much of the key scheme level info, is that it should be for local government staff first and foremost with key features including:

[ ] Auto upload of schemes
[ ] Ability to view schemes in your authority, we'll need to have per-authority authentication
[ ] Edit capabilities and everything that entails including history etc, fine as dataset volumes and velocities will be low and easily handles by a Postgres DB for the kind of n. users we're talking about in authenticated version. I don't see that as MVP though.
[ ] New contextual layers available in dropdown menus, e.g. from OS's NGD API

The dashboard stuff that is more internal facing already covered by Bec's work largely but longer term will be amazing to have ATE level overview of all schemes for "ATE authentication" which could just be a group with access to schemes from all authorities.

Thoughts @Sparrow0hawk ?

This has slightly meandered away from the topic of this issue (sveltekit) and onto more specific ATE priorities so going to migrate to internal issue

I think we have a slightly bigger question than should we use sveltekit:
How do we want to organise our front end code. Svelte kit is one answer but it might come some at costs in terms of being restrictive to how we host on github currently.
I personally think we need a task to assess and then present some options for how we want to refactor the existing front end code, if at all.
My 2 cents are that we need some more separation between logic and view. Something like MVC or MVVM altough to be honest I don't remember the exact implication of those two paradigms. Beyond that I don't know if we want a pre-existing opinionated framework, our own guidelines, or what. I think SvelteKit could be a good answer but we need someone to go away and come back with some proposals imo.
Some of these questions will inevitably play into our backend infrastructure question. I think they're separate questions but we gotta be mindful of our backend options when deciding about this.

On a point discussed in person but not in this thread.
Adopting svelte kit would not preclude us hosting on github pages: https://kit.svelte.dev/docs/adapter-static. This means we can use it with the current dev deployment method without issue. If we decide it's a nice sane way of helping us organise our code it's an option.

I've a little look into this today. I haven't found much in the way of strong recommendations or discussions of best practices for Svelte but I think I've found an uncontroversial starting point:
https://kim-jangwook.medium.com/best-practices-for-organizing-and-structuring-svelte-applications-5f85a3d5a6f5#:~:text=When building a Svelte application%2C it's important to use consistent,more easily readable and maintainable.
I think it would be worth reorganising our App in this way:

Reorganise our Svelte code into into components, pages, and store, and then see what remains outside these groups and think where we'd logically wanna put it.
Each Svelte component or page exists in its own directory where it has at least, maybe at most, two files: component-name.svelte and componentName.ts. Additionally I would like it if we tried to have as little actual logic in component-name.svelte files, maybe a hardline rule that all that can be called in those are named functions imported from componentName.ts?

I think this might be a nice starting point for separating our code, and would leave us pretty close to Svelte Kit view of the world so we could more easily adopt it later if we decided we wanted to.
I do see an issue of timing, though. This is going to be a hefty refactor so doing this whilst any other work is going on might be quite tricky.

Just gonna ping @dabreegster @Sparrow0hawk @markhobson in case you don't get notified by default, any thoughts on the above?

I agree it'll be a lot of work, so probably best to wait until we have a clear direction. I think trying out SvelteKit as a standalone spike would be an interesting knowledge gathering exercise if you were interested.

For all of these questions, https://discord.com/invite/svelte could be a great place to ask. I've asked some questions there before and gotten great answers -- sometimes even example code! And for the questions we're asking, I reckon there's some existing threads.

Reorganise our Svelte code into into components, pages, and store

I've struggled to find best practices or good examples of how to structure stuff. Today, we're not terribly far from this -- components/ is called lib/, and there's an attempt at further organization in there. We have pages/ as well, but it's unclear to me what the conventions are for defining separate components that only belong to one page. A subdirectory per page could work.

Additionally I would like it if we tried to have as little actual logic in component-name.svelte files, maybe a hardline rule that all that can be called in those are named functions imported from componentName.ts?

Hmm, where is this recommended? I don't think I've seen example projects structured this way. The Medium article makes some odd recommendations about having a separate .js and .css file per page. I think it goes against https://svelte.dev/tutorial/styling, right? Scoping CSS to one component means much simpler selectors, often not even needing to come up with class names. I guess we'd still have this with a separate .css per page, but I don't understand the benefit.

This is going to be a hefty refactor so doing this whilst any other work is going on might be quite tricky.

I think we could do it pretty quickly. Let's agree here (or before writing lots of code) what the structure/renaming should look like, then just do it. I've got a few bigger PRs in progress, but I don't mind handling merge conflicts.

What would it look like if we try and spin around the question a bit? Rather than figure out if SvelteKit does something useful for us, let's think about likely things we want to do soon, and spend a bit of time investigating how we might do that.
Integrate with gov.uk styling
https://frontend.design-system.service.gov.uk/
I think (not sure) GDS requirements will ask us to use these design standards. I helped/watched Will add this to https://github.com/ADD-William-WaltersDavis/dft_hackathon a few months ago, and I think it required configuring one of those CSS preprocessors. We could experimentally cutover current ATIP to this design system to figure out any integration challenges. There's existing code we can refer to of that integration with Svelte, and Will to ask for help if we get stuck.
Integrate with One Login
I haven't started looking into https://www.sign-in.service.gov.uk/ yet. We could see what it'll take to integrate with a static Svelte app (or discover that it needs some backend that isn't gov-run, and prototype that).

@dabreegster

I think we could do it pretty quickly. Let's agree here (or before writing lots of code) what the structure/renaming should look like, then just do it. I've got a few bigger PRs in progress, but I don't mind handling merge conflicts.

I agree, I mostly wanted to flag that we would want to be mindful of other ongoing work ideally

Additionally I would like it if we tried to have as little actual logic in component-name.svelte files, maybe a hardline rule that all that can be called in those are named functions imported from componentName.ts?

Hmm, where is this recommended? I don't think I've seen example projects structured this way. The Medium article makes some odd recommendations about having a separate .js and .css file per page. I think it goes against https://svelte.dev/tutorial/styling, right? Scoping CSS to one component means much simpler selectors, often not even needing to come up with class names. I guess we'd still have this with a separate .css per page, but I don't understand the benefit.

It's not explicitly recommended but as a principle from most frameworks of writing a GUI that I've worked with, and when thinking about things being modular: it has generally been recommended and good to separate the code that describes the visuals from the logic operating on the data. It's implied by that medium article by the naming conventions but I haven't found somewhere recommending specifically this. Maybe I'm missing some reason it makes sense in SvelteLand to have the more entangled but it doesn't feel like good practice. Feels like a code smell to me.

Old issue that turned into a few conversations. We're using Express today as our backend, and sticking with Svelte for the frontend


Configurable root volume size on vSphere

Fixes #788
Needs testing on vSphere
cc @chrislovecnm

Docs here: https://github.com/rakutentech/terraform-provider-vsphere


Cypress error Unexpected token '{' after upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>

Describe the bug
I tried to upgrade<EMAIL_ADDRESS>to<EMAIL_ADDRESS>but Cypress could not longer run tests because of the error Unexpected token '{' (see logs section for more detailed stack trace).
Reproduction
sorry none at this time
Steps to reproduce
I will write more detailed steps to reproduce if this upgrade becomes more important.
I suspect the following would work:

Create a react app using TypeScript
yarn add<EMAIL_ADDRESS>(note, I'm stuck on this old Cypress version)
Create a simple Cypress test
Try to run the Cypress test against the react app
Observe error in the Cypress console

System Info
"cypress": "8.5.0",
"vite-tsconfig-paths": "^4.2.0",

Used Package Manager
yarn
Logs
Vite Logs
See google doc, it was too long to paste into the message body.
Cypress Console Log
Error seen in Cypress console:
SyntaxError: Unexpected token '{'

More detail by printing the Cypress log to the console log:
cypress_runner.js:190988 SyntaxError: The following error originated from your application code, not from Cypress.

  > Unexpected token '{'

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
SyntaxError: The following error originated from your application code, not from Cypress.

  > Unexpected token '{'

When Cypress detects uncaught errors originating from your application it will automatically fail the current test.

This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
From previous event:
    at Object.run (http://localhost:3000/__cypress/runner/cypress_runner.js:182821:23)
    at Object.run (http://localhost:3000/__cypress/runner/cypress_runner.js:168727:17)
    at $Cy.cy.<computed> [as wait] (http://localhost:3000/__cypress/runner/cypress_runner.js:169897:19)
    at __stackReplacementMarker (http://localhost:3000/__cypress/runner/cypress_runner.js:169205:13)
    at Context.runnable.fn (http://localhost:3000/__cypress/runner/cypress_runner.js:170121:23)
    at callFn (http://localhost:3000/__cypress/runner/cypress_runner.js:122959:21)
    at Test.../driver/node_modules/mocha/lib/runnable.js.Runnable.run (http://localhost:3000/__cypress/runner/cypress_runner.js:122946:7)
    at http://localhost:3000/__cypress/runner/cypress_runner.js:176663:30
From previous event:
    at Object.onRunnableRun (http://localhost:3000/__cypress/runner/cypress_runner.js:176648:19)
    at $Cypress.action (http://localhost:3000/__cypress/runner/cypress_runner.js:166202:28)
    at Test.Runnable.run (http://localhost:3000/__cypress/runner/cypress_runner.js:174382:13)
    at Runner.../driver/node_modules/mocha/lib/runner.js.Runner.runTest (http://localhost:3000/__cypress/runner/cypress_runner.js:123618:10)
    at http://localhost:3000/__cypress/runner/cypress_runner.js:123744:12
    at next (http://localhost:3000/__cypress/runner/cypress_runner.js:123527:14)
    at http://localhost:3000/__cypress/runner/cypress_runner.js:123537:7
    at next (http://localhost:3000/__cypress/runner/cypress_runner.js:123439:14)
    at http://localhost:3000/__cypress/runner/cypress_runner.js:123505:5
    at timeslice (http://localhost:3000/__cypress/runner/cypress_runner.js:117431:27)

Validations

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

I'm having this same issue in Safari 16.3 using StimulusJS and vite-rails.
This typescript:
export default class extends Controller {
  static targets = ['menu']
}

Is being turned into this:
export default class extends Controller {
  static {
    this.targets = ["menu"];
  }
}

And Safari says SyntaxError: Unexpected token '{' about the static {.

I recently upgraded from 4.3.0 to 4.4.4. After doing a few downgrades, 4.3.9 works fine, but 4.4.0 produces this error.

We're getting this error as well, only in Safari 15 and earlier (in our Astro + Vue app). @mosofsky would you mind updating the title of this issue, since it's not just about Cypress? It affects production applications.

@ffxsam are you also using Typescript?

@natematykiewicz Yessir.

https://github.com/evanw/esbuild/blob/main/CHANGELOG.md#0180
I think this is the real problem:
"TypeScript's target no longer affects esbuild's target"
https://github.com/evanw/esbuild/issues/2628
But I can't figure out the right way to set the esbuild target via Vite.

Under Vite 4.3.9 this Typescript:
export default class extends Controller {
  static targets = ['menu']
}

becomes this:
export default class dropdown_menu_controller_default extends Controller {
}
dropdown_menu_controller_default.targets = ["menu"];

I'm having this same issue in Safari 16.3 using StimulusJS and vite-rails.
This typescript:
export default class extends Controller {
  static targets = ['menu']
}

Is being turned into this:
export default class extends Controller {
  static {
    this.targets = ["menu"];
  }
}

And Safari says SyntaxError: Unexpected token '{' about the static {.

Under Vite 4.3.9 this Typescript becomes this:
export default class dropdown_menu_controller_default extends Controller {
}
dropdown_menu_controller_default.targets = ["menu"];

I can't tell what's going on in my situation. Our stack is Astro + Vue, and the Astro Vue integration depends on Vite 4.4.x. When I load up our app in Safari 15 or earlier, I get this:

What's your build target in tsconfig.json? Ours was es2015, and I'm assuming we're no longer getting es2015 with the esbuild 0.18 upgrade.

Can someone help provide a repro for this? I made a stackblitz, but I can't quite repro the difference between Vite 4.3.9 and 4.4.0. Couple questions:

Is tsconfig.json compilerOptions.target set?
Is esbuild.target Vite config set?
Is the static property code coming from your source code or a dependency?

I think I have a fix, but I'm not sure what regression it's fixing. Also related https://github.com/vitejs/vite/issues/13756

"TypeScript's target no longer affects esbuild's target"

As noted in https://github.com/vitejs/vite/pull/13525:

This is not a breaking change for us. We always set esbuild's target so target in tsconfig was never used.

Which I can also confirm, that I'm not sure if we have a regression here.

So far I've been unable to put together a reproduction from scratch. So I think I'm gonna work the other way around: take my project, make a branch, and start cutting chunks away until the problem goes away. Then I'll have a better idea of how to create a reproduction—hopefully.

Yes

tsconfig.json
{
  "compilerOptions": {
    "target": "es2015",
    "lib": [
      "dom",
      "dom.iterable",
      "es2015"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "esModuleInterop": true,
    "noEmit": true,
    "module": "esnext",
    "sourceMap": true,
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "downlevelIteration": true,
    "allowSyntheticDefaultImports": true,
    "noUnusedLocals": true,
    "types": [
      "vite/client"
    ]
  },
  "include": [
    "app/javascript/**/*.ts",
    "vite.config.ts"
  ],
  "exclude": [
    "node_modules"
  ]
}

No
vite.config.ts

import { defineConfig } from 'vite'
import RubyPlugin from 'vite-plugin-ruby'

export default defineConfig({
  plugins: [RubyPlugin()],
})

My source code

Re-opening since there seems to be a regression somewhere, but I'm still unsure how it happens.
@natematykiewicz Thanks for the response. IIUC the "target": "es2015" setting shouldn't be respected in other versions of Vite too. If you use Vite 4.3.9 and set "target": "esnext" instead, would you get the same error too? If it does, that's really confusing to me 😅

Changing the compiler options target on 4.3.9 is definitely changing my output JS.
Given this typescript:
import { Controller } from '@hotwired/stimulus'
import { useClickOutside } from 'stimulus-use'
// eslint-disable-next-line @typescript-eslint/ban-ts-comment
// @ts-ignore
import { enter, leave } from 'el-transition'

export default class extends Controller {
  static targets = ['menu']

  declare menuTarget: HTMLElement

  connect() {
    useClickOutside(this, { element: this.menuTarget })
  }

  show() {
    this.menuTarget.classList.remove('hidden')
    enter(this.menuTarget)
  }

  hide() {
    Promise.all([leave(this.menuTarget)]).then(() => {
      this.menuTarget.classList.add('hidden')
    })
  }

  toggle() {
    if (this.menuTarget.classList.contains('hidden')) {
      this.show()
    } else {
      this.hide()
    }
  }

  clickOutside() {
    this.hide()
  }
}

es2015
import { Controller } from "/vite-dev/@fs/.../node_modules/.vite/deps/@hotwired_stimulus.js?v=11d7a1aa";
import { useClickOutside } from "/vite-dev/@fs/.../node_modules/.vite/deps/stimulus-use.js?v=11d7a1aa";
import { enter, leave } from "/vite-dev/@fs/.../node_modules/.vite/deps/el-transition.js?v=11d7a1aa";
export default class dropdown_menu_controller_default extends Controller {
    connect()
    {
        useClickOutside(this, {
            element: this.menuTarget
        });
    }
    show()
    {
        this.menuTarget.classList.remove("hidden");
        enter(this.menuTarget);
    }
    hide()
    {
        Promise.all([leave(this.menuTarget)]).then(() => {
            this.menuTarget.classList.add("hidden");
        });
    }
    toggle()
    {
        if (this.menuTarget.classList.contains("hidden")) {
            this.show();
        } else {
            this.hide();
        }
    }
    clickOutside()
    {
        this.hide();
    }
}
dropdown_menu_controller_default.targets = ["menu"];

esnext
import { Controller } from "/vite-dev/@fs/.../node_modules/.vite/deps/@hotwired_stimulus.js?v=11d7a1aa";
import { useClickOutside } from "/vite-dev/@fs/.../node_modules/.vite/deps/stimulus-use.js?v=11d7a1aa";
import { enter, leave } from "/vite-dev/@fs/.../node_modules/.vite/deps/el-transition.js?v=11d7a1aa";
export default class extends Controller {
  static targets = ["menu"];
  connect() {
    useClickOutside(this, { element: this.menuTarget });
  }
  show() {
    this.menuTarget.classList.remove("hidden");
    enter(this.menuTarget);
  }
  hide() {
    Promise.all([leave(this.menuTarget)]).then(() => {
      this.menuTarget.classList.add("hidden");
    });
  }
  toggle() {
    if (this.menuTarget.classList.contains("hidden")) {
      this.show();
    } else {
      this.hide();
    }
  }
  clickOutside() {
    this.hide();
  }
}

Omitting the compilerOptions:
import { Controller } from "/vite-dev/@fs/.../node_modules/.vite/deps/@hotwired_stimulus.js?v=11d7a1aa";
import { useClickOutside } from "/vite-dev/@fs/.../node_modules/.vite/deps/stimulus-use.js?v=11d7a1aa";
import { enter, leave } from "/vite-dev/@fs/.../node_modules/.vite/deps/el-transition.js?v=11d7a1aa";
export default class dropdown_menu_controller_default extends Controller {
    connect()
    {
        useClickOutside(this, {
            element: this.menuTarget
        });
    }
    show()
    {
        this.menuTarget.classList.remove("hidden");
        enter(this.menuTarget);
    }
    hide()
    {
        Promise.all([leave(this.menuTarget)]).then(() => {
            this.menuTarget.classList.add("hidden");
        });
    }
    toggle()
    {
        if (this.menuTarget.classList.contains("hidden")) {
            this.show();
        } else {
            this.hide();
        }
    }
    clickOutside()
    {
        this.hide();
    }
}
dropdown_menu_controller_default.targets = ["menu"];

It's worth noting, every time I change my tsconfig.json while my server is running, I see this log line:
3:48:41 PM [vite] changed tsconfig file detected: /my_path/tsconfig.json - Clearing cache and forcing full-reload to ensure TypeScript is compiled with updated config values.

On Vite 4.4.7, with "es2015" the file is:
import { Controller } from "/vite-dev/@fs/.../node_modules/.vite/deps/@hotwired_stimulus.js?v=c8bdaac7";
import { useClickOutside } from "/vite-dev/@fs/.../node_modules/.vite/deps/stimulus-use.js?v=24b8e4a2";
import { enter, leave } from "/vite-dev/@fs/.../node_modules/.vite/deps/el-transition.js?v=b7575016";
export default class extends Controller {
  static {
    this.targets = ["menu"];
  }
  connect() {
    useClickOutside(this, { element: this.menuTarget });
  }
  show() {
    this.menuTarget.classList.remove("hidden");
    enter(this.menuTarget);
  }
  hide() {
    Promise.all([leave(this.menuTarget)]).then(() => {
      this.menuTarget.classList.add("hidden");
    });
  }
  toggle() {
    if (this.menuTarget.classList.contains("hidden")) {
      this.show();
    } else {
      this.hide();
    }
  }
  clickOutside() {
    this.hide();
  }
}

This errors. Safari does not seem to understand this part:
static {
}

I tried "esnext" and the file is:
import { Controller } from "/vite-dev/@fs/.../node_modules/.vite/deps/@hotwired_stimulus.js?v=a996cf86";
import { useClickOutside } from "/vite-dev/@fs/.../node_modules/.vite/deps/stimulus-use.js?v=a996cf86";
import { enter, leave } from "/vite-dev/@fs/.../node_modules/.vite/deps/el-transition.js?v=a996cf86";
export default class extends Controller {
  static targets = ["menu"];
  connect() {
    useClickOutside(this, { element: this.menuTarget });
  }
  show() {
    this.menuTarget.classList.remove("hidden");
    enter(this.menuTarget);
  }
  hide() {
    Promise.all([leave(this.menuTarget)]).then(() => {
      this.menuTarget.classList.add("hidden");
    });
  }
  toggle() {
    if (this.menuTarget.classList.contains("hidden")) {
      this.show();
    } else {
      this.hide();
    }
  }
  clickOutside() {
    this.hide();
  }
}

I tried a bunch of different values for compilerOptions target, and es2021 errors (same output as es2015), but es2022 works fine (same output as esnext).
This is so strange.
I'm sure it's obvious, but by updating Vite from 4.3 to 4.4, it also updated esbuild from 0.17 to 0.18.

I've found the bug at opened https://github.com/vitejs/vite/pull/13992 to fix it. It was useDefineForClassFields that's causing the transpilation that I didn't see in the repro, which had that turned on to true. Setting it to false revealed it.
But it is still true that the target isn't what's Vite is transpiling to, the target just so happen to toggle the default value of useDefineForClassFields in Vite 4.3.9 that causes the issue.

@ffxsam I've touched on that at https://github.com/vitejs/vite/issues/13756#issuecomment-1651103462. Maybe in future versions tsconfig target will affect TS, because I think that's a better default too. But for build.target, it's a build-only setting so it shouldn't affect dev. Most of the build.* options implicitly has this rule so we can't change that.

Yeah it'd be better to resort to the Vite configuration whenever possible, I'm not sure how it's picking up that es2015 config today though.

I was able to upgrade from 4.3.9 to 4.4.8 without any problems. So it looks like you fixed whatever was happening. But I agree, I feel like I'm not configuring something right. I'm not setting any targets in my Vite config, but when I had tried, they didn't seem to help my problem.

I just tried build.target: "es2015" in the Vite config (for my Astro site), and it did not go well. 😅
Transforming async generator functions to the configured target environment ("es2015" + 2 overrides) is not supported yet
1297|  function isPromise(value) {
1298|    return !!value && typeof value === "object" && typeof value.then === "function";
1299|  }
   |    ^
1300|  async function* streamAsyncIterator(stream) {
   |  ^
1301|    const reader = stream.getReader();

These errors look like they're coming from third-party libraries, so I have no control over this.


Update cac upload description

Changed directions - PR should be created after uploading to prod/staging/experimental so that that step can also be verified as part of the PR.

The how-to docs are now in the wiki. You may want to put this here: https://github.com/transcom/mymove/wiki/use-mtls-with-cac


Test monobundle as part of the nuget tests

sorry for the delay, i have build a repro project with a test that currently just checks for the existence of Contents/MonoBundle/package/lib/cli/cli.js within the macOS .app file. Currently i assume that everything that should live in the package directory is in the first level directly in  Contents/MonoBundle.
Here is the project which consists of a Xamarin.Forms project a Xamarin.Mac project and an mstest project.
https://github.com/nor0x/playwright-xmac-test
this is a very similar project structure to the main application that i'm building which is closed source for now
Originally posted by @nor0x in https://github.com/microsoft/playwright-sharp/issues/1093#issuecomment-786567662

follow-up to this issue - currently i'm experimenting with the version 0.192.0 which creates a folder named @(PlaywrightDriverFiles->;'bin in my macOS project directory, which contains an .app folder with Contents and MonoBundle which is empty though

workaround for every who has issues with the .playwright directory inside the MonoBundle in the .app folder. I have added this custom target to my macOS project file which copies everything from the bin/{configuration}/.playwright/osx folder into Contents/MonoBundle/
<Target Name="CopyPlaywrightMacOS" AfterTargets="CopyFilesToOutputDirectory">
    <ItemGroup>
        <OutFiles Include="$(TargetDir)\.playwright\osx\**\*.*" />
    </ItemGroup>
    <Copy SourceFiles="@(OutFiles)" DestinationFolder="$(TargetDir)\Deon.app\Contents\MonoBundle\.playwright\osx\%(RecursiveDir)" />
</Target>

Don't you wan to take a look at it https://github.com/microsoft/playwright-sharp/blob/main/src/PlaywrightSharp/build/netstandard2.0/PlaywrightSharp.targets#L23 ?
I remember doing that and testing it... :/

i did take a look at it and it seems that the path in DestinationFiles here is wrong:
https://github.com/kblok/playwright-sharp/blob/2caf57a7d005596abb7857fb7085b08a66aa002b/src/PlaywrightSharp/build/netstandard2.0/PlaywrightSharp.targets#L30
any specific reason why we have PlaywrightDriverFiles-> in DestinationFiles="... i think this gets interpreted wrong on macOS

@nor0x I think we have an extra semi-colon there...

@kblok you are right - at first i thought it's part of the copy command 👀


Update ThreePrinciples.md

Change Mutations with Actions. I had a discussion with another React developer and it seemed to be some confusing and it turned that it was caused by a misunderstanding of the concept of functional programming, pure functions and the use of the word mutation. I hope that this helps.

@urbanvikingr These are mutations, not actions -- the mutations to the state. You don't write actions as functions -- they are plain objects.

@sompylasar Mutation mean that you change the existing state, but Redux is creating a new state with the changes. I think that the word mutation gives some confusing. The text underneath clearly states that the Redux state tree is immutable.

I changed Actions to Transformation. I hope that this helps.

That makes more sense. Let's see what @gaearon thinks.

Maybe just "changes are described by pure functions"?

I updated to Changes are made with pure functions, because it would be more readable, but I like Changes are done by pure functions too. I would just like to avoid using the word mutation. I hope that this helps.

Action creators aren't necessarily pure

@acdlite The section is about Reducers :)

Haha yes it is, was skimming through my notifications and got my wires crossed. Carry on :D

Close to what @gaearon suggested, and reads nicely, so I think this can be merged. Thanks @urbanvikingr!

Thank you :)


⚠ Samsung has degraded performance

In 3255a0c, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 1958 ms

Resolved: Samsung performance has improved in 90278be.


I use emcc compile a simple cpp to wasm. but can't works in life

emcc
When I run life with the wasm , it crashed because some global env are missing(such as __memory_base, __table_base, etc..).

I use other ways to compile cpp, I works in some caese.
but when I use std::cout << "", It fails with panic: runtime error: slice bounds out of range


Options for parcel plugin

I'm wondering if the @svgr/parcel-plugin-svgr can accept options. The configuration file options don't seem to have any effect when using the parcel plugin.

parcel is zero-conf so usually the plugins follow that, so unless they read the package.json (on the plugin and pass it down to svgr) it won't have any effect (sw-precache for example, does https://github.com/cyyyu/parcel-plugin-sw-precache/blob/master/index.js#L41)

Parcel plugin should work with .svgrrc. Please submit another issue describing the bug if it is not working as expected.

Just wanted to note here the issue I was experiencing was with parcel's caching, not svgr. Changes to the .svgrrc didn't SEEM to be taking effect. Parcel's --no-cache option fixed this.
Indeed the svgr parcel plugin works with.svgrrc as expected.


Update localnet.md

Checklist

[ ] all tests passes
[ ] documentation is changed or added
[ ] (option)

Affected core subsystem(s)

Description of change

I just updated docs in main branch, thanks.


ENOENT: no such file or directory tmp/../vendor/.bin/indent-string

I have an issue with multiple apps using ember-cli-sass and the latest versions of all of node, npm, libsass and this library (via updated ember-cli-sass). I tried everything I could come up with in order to fix it, but it keeps failing with the follow stack trace, whenever I try to build and/or watch one of these apps:
~/src/remotestorage/apps/dashtab $ ember build
Future versions of Ember CLI will not support v5.0.0. Please update to Node 0.12 or io.js.
version: 1.13.8
Build failed.
ENOENT: no such file or directory, stat '/home/basti/src/remotestorage/apps/dashtab/tmp/sass_compiler-input_base_path-VTbfcUKS.tmp/0/vendor/.bin/indent-string'
Error: ENOENT: no such file or directory, stat '/home/basti/src/remotestorage/apps/dashtab/tmp/sass_compiler-input_base_path-VTbfcUKS.tmp/0/vendor/.bin/indent-string'
    at Error (native)
    at Object.fs.statSync (fs.js:892:18)
    at SassCompiler.keyForFile (/home/basti/src/remotestorage/apps/dashtab/node_modules/broccoli-sass-source-maps/node_modules/broccoli-caching-writer/index.js:91:55)
    at Array.map (native)
    at SassCompiler.CachingWriter._conditionalBuild (/home/basti/src/remotestorage/apps/dashtab/node_modules/broccoli-sass-source-maps/node_modules/broccoli-caching-writer/index.js:107:61)
    at /home/basti/src/remotestorage/apps/dashtab/node_modules/broccoli-sass-source-maps/node_modules/broccoli-plugin/read_compat.js:61:34
    at lib$rsvp$$internal$$tryCatch (/home/basti/src/remotestorage/apps/dashtab/node_modules/rsvp/dist/rsvp.js:493:16)
    at lib$rsvp$$internal$$invokeCallback (/home/basti/src/remotestorage/apps/dashtab/node_modules/rsvp/dist/rsvp.js:505:17)
    at lib$rsvp$$internal$$publish (/home/basti/src/remotestorage/apps/dashtab/node_modules/rsvp/dist/rsvp.js:476:11)
    at lib$rsvp$asap$$flush (/home/basti/src/remotestorage/apps/dashtab/node_modules/rsvp/dist/rsvp.js:1198:9)

[deleted]
indent-string in that dir exists, but seems to be a wrong symlink:
tmp/sass_compiler-input_base_path-oemkgqKh.tmp/0/vendor/.bin/indent-string -> ../indent-string/cli.js

Update: the whole library seems to be present in the linked directory, but it only contains an index.js and no cli.js.
Update 2: This happened in July: https://github.com/sindresorhus/indent-string/commit/4322f1ad7e236f5bdab83d5d5b97d2c89cfd0827

I think maybe @stefanpenner may know something about this problem?

Forgot to add: looks like multiple nested deps too loosely defined and the last one not using SemVer correctly. I have no idea how to fix my stuff, though.

Closing due to inactivity, feel free to reopen.


[Issue-106] Bug related to Send fund feature

Related issue(s)

#106

Is your feature request related to a problem(s)? Please describe.

Fix not change value when select max and change fee option

Describe the solution you'd like

Fix not change value when select max and change fee option

Describe alternatives you've considered

No

Additional context

No

🚀 Deployed on https://pr-117--papaya-melba-f5c160.netlify.app


[Enhancement] blacklist/disable hair

I saw that we have blacklist props, but don't include hair in it. So if i want to blacklist hair, is there any solution for that ?

Implemented in #179


clicking select kernel without Jupyter extension installed opens an empty quick pick that loads forever

I ran into this after opening a workspace in a dev container that didn't have the Jupyter extension and trying to run a notebook. There was no suggestion for how to get anything to show up in that list.

Fixed via https://github.com/microsoft/vscode/pull/169586

repro:
create a temporary empty profile
open a notebook
click 'select kernel'

@amunger can you share what you saw, did you see "Select Kernel" in the quick pick title? Does it work if you close and reopen the select kernel quick pick?

it stays like that forever

It happens when you have

Jupyter installed
Play around with Jupyter notebooks a bit, especially using the kernel picker
Switch to a new profile
Now open a notebook, open kernel picker 🐛

When we switch profiles, we would restart EH. The kernel detection tasks registered through previous EH were not disposed.


Url is wrong encoded

https://discord.com/api/v10/oauth2/authorize?scope=identify%2Cguilds%2Cguilds.members.read&prompt?.....
as you can see it does identify%2Cguilds... it should be identify%20guilds

here are some debugging things

I'm on node v20.7.0

The fault is in remix-auth-oauth2 in getAuthorizationUrl

params.set("scope", Array.isArray(this.scope) ? this.scope.join(" ") : this.scope);
that would fix it (in remix-auth-oauth2)
this.scope has to be a STRING not an array.

https://github.com/JonnyBnator/remix-auth-discord/pull/6

Resolved with PR #6


Evaluation script!

Hello!
Could you please provide the evaluation script?
Regards,
Yokesh

Hi @yokee06 ! Thanks for asking.
We have just uploaded our evaluation code, evaluation_metrics.py, where we use the Evaluation codes for MS COCO caption generation for evaluation.
Kindly install pycocoevalcap and the pycocotools dependency, then you could run the evaluation code following the instrutions here: https://github.com/YuxiXie/SG-Deep-Question-Generation/blob/master/README.md#evaluating

Thank you!


Added "Create Folder (Tree)" task

Created "Create Folder (Tree)" task, that can create a full folder tree in XLD, without having to create multiple tasks for it. It will traverse through the ID provided and create the folder structure in the Type (Applications/Environments/Infrastructure/Configuration) provided

I had considered doing that, but the "Create CI" Task does not do this either, so I opted against it.
In the pipeline that I have, I now use a "Does CI Exist" task in front of the "Create Folder" task (which is now just a script), which then outputs a True/False variable, which is the precondition for this task.
I do the same for a "Create Application" task (which is also a "Create CI" task).
Additionally: I specifically chose to do a "PUT" in the HTTP-request, to ensure that if you want to create, for instance, a "folder1/folder2" and a "folder1/folder3" the command will not break on the existence of the "folder1" folder (which is what a POST would do for you).

I'd suggest Create CI Task should be amended to check first then :)
Create CI is doing a POST not a PUT -which as you point out should throw an error. So we should be error handling earlier and not letting the REST API return it's ugly failure.
In this case, if you have Applications/folder1/folder2/folder3/folder4/ - you could end up making multiple calls for something that already exists. An extra does_ci_exist call adds a single call, but could save 5 calls.
Doing the previous task yourself using the Does CI Task Exist is good - but you're forcing other users to think of that optimisation by themselves. Plus, if we have to make 20 folders at once, that's 20 extra Does CI Exist tasks.
If we build it in, we can assure the user that if this task passes, the Folder definitively exists - either because we've checked it or because we made it.

I'm going to start in the middle of your comment, because yes, you could save 5 calls, but you could also add additional calls.
Suppose I want to create "Applications/folder1/folder2/folder3/folder4".
I do a "Does CI Exist" on the full path first, and find that the full path does not exist. I would then go ahead and do my "Create Folder (Tree)" task. Within this task, I would then have to check for each separate folder whether or not the CI exists. So, that would add, in this example, 3 "Does CI Exist" calls, and then also the additional calls to create the folders.
Using the PUT basically an update in this case, which creates it if it doesn't exist, and "updates" it if it already exists.
For the 20 folders at once, those checks would still be there, because of my point above.

Ah, I see what you mean.
I didn't mean to suggest doing a check_ci_exist every time - I just meant a single check. at the start around line 14 of createFolder.py.
If the folder as given by the user exists, just pass. If it doesn't, then roll on through the folder tree as per. That way, no more than 1 extra call when it doesn't exist and only one call when it does.

I discussed with Joris on this, and we decided to go ahead with the combination of check_ci_exists and create_directory methods, so as to make sure there is consistency in the plugin.
The amount of calls it makes shouldn't be something bad, as XLD should be able to handle it without problem.
So, I've adjusted the plugin to use the check_ci_exists and the create_directory methods.
It should be okay now :-)

D'oh! Should have looked at the commits first :)
Nice one - I've got a use for this bad boy coming up on my radar.


fix: categories.tsv was downloading interactions

close #474
Unsure how to test this locally?

We might consider having the top row (with the latest data) always be a consistent link out/title i.e. "latest". This would make this data easier to consistently access programmatically


VM: importing dart:core with a prefix hides dynamic

import 'dart:core' as core;
main(){
  // Should still be available because it is not a member of dart:core.
  Expect.isTrue(dynamic is Type);

  Expect.throws(() => mycore.dynamic is Type,
                (e) => e is NoSuchMethodError,
                'dynamic is not a member of dart:core');
}

@mhausner @rmacnak-google This appears to still happen, but is it still incorrect? Is this issue stale?

I believe this issue is still valid.
tests/language/dynamic_prefix_core_test.dart isn't marked as failing for kernel though, so it will probably end up fixed by the new front end.

This is still valid, but will be obsolete with the new front-end. I don't see a reason to fix this for the current front-end.
As @rmacnak-google observes, this works in the new Front-end, so closing the issue.

This is closed, but in case anyone ever takes a look here: Please note that dynamic is exported by 'dart:core', and tests/language{,_2}/import_core_prefix_test.dart need to be updated as described in #32060.


CFE-878: Add userLabels in Infrastructure to driver args list

PR has the changes for https://github.com/openshift/enhancements/pull/1217 proposed to support GCP labels in OCP, which requires gcp-pd-csi-driver-operator to add gcp userLabels available in the status sub resource of infrastructure CR, to the gcp resources created by the driver.

/hold https://github.com/openshift/enhancements/pull/1217

/test test
/test verify

/remove-hold

/cc @tsmetana

/retest

/test e2e-gcp

/label px-approved

/lgtm

/label qe-approved

/label docs-approved

/label docs-approved


Remove beta from ObservableHQ link

shouldn't it be https://observablehq.com/collection/@d3/d3-force instead?

Sure, I've updated the link.


Regression model design

Problem: We need to predict Death, ANYCHD, CVD, and HYPERTEN
Solution: Design regression model: linear or logistic

10 period training for the next commit

Ready to review.
Next issues :
- Compare each loss function.
- Refacto each file.
- Add documentation (function/class and README).
Next step ideas:
- Anova to visualize the dependence of each feature.
- Multinomial logistic regression to predict multi-classes
- Binning data : for exemple SYSBP could probably be grouped by values corresponding to normal, pre-hypertensive and hypertensive.


Add order service type and extend metadata logic

This redesigns how we deal with metadata.

metadata models can be defined in specific django apps
a metadata registry keeps track of all the metadata
you need to register a metadata using a metadata module with

>>> from datahub.metadata.registry import registry
>>> registry.register(
        id=<metadata-id>,
        model=<model>,
        queryset=<queryset>,
        serializer=<serializer>
    )

that automatically generates the right view and tests

This also adds a new OMIS ServiceType metadata which uses the new registry logic.

Codecov Report

Merging #379 into develop will increase coverage by 0.06%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop     #379      +/-   ##
===========================================
+ Coverage    95.55%   95.62%   +0.06%
===========================================
  Files           67       70       +3
  Lines         2633     2674      +41
  Branches       234      234
===========================================
+ Hits          2516     2557      +41
  Misses          85       85
  Partials        32       32

Impacted Files
Coverage Δ

datahub/core/management/commands/loadmetadata.py
100% <ø> (ø)
:arrow_up:

datahub/omis/order/serializers.py
100% <100%> (ø)
:arrow_up:

datahub/metadata/views.py
100% <100%> (ø)
:arrow_up:

datahub/omis/order/metadata.py
100% <100%> (ø)

datahub/metadata/metadata.py
100% <100%> (ø)

datahub/metadata/registry.py
100% <100%> (ø)

Continue to review full report at Codecov.

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

@reupen thanks for the comments, very helpful. Have another look when you can.


SetConsoleCtrlHandler not working with console

First, I would like to thank you for this awesome library! Keep up the great work. I have a little problem, nothing dramatic, but it would be nice if somebody could help me.
SetConsoleCtrlHandler works perfectly with the pure Python console (without being compiled with Nuitka) and with the compiled Nuitka version without console. I use it mainly to kill other processes with https://github.com/ElyDotDev/windows-kill the SetConsoleCtrlHandler helps me to not crash my own process. When I compile Nuitka with Tkinter and Console, SetConsoleCtrlHandler doesn't have any effect.
Is there any way to fix that? Here is an example:
# Ctrl+C handler

from ctypes import WINFUNCTYPE, windll
from ctypes.wintypes import BOOL, DWORD
import sys

ctrl_config = sys.modules[__name__]
ctrl_config.function = lambda *args, **kwargs: None

kernel32 = windll.LoadLibrary("kernel32")
PHANDLER_ROUTINE = WINFUNCTYPE(BOOL, DWORD)
SetConsoleCtrlHandler = kernel32.SetConsoleCtrlHandler
SetConsoleCtrlHandler.argtypes = (PHANDLER_ROUTINE, BOOL)
SetConsoleCtrlHandler.restype = BOOL

(
    CTRL_C_EVENT,
    CTRL_BREAK_EVENT,
    CTRL_CLOSE_EVENT,
    CTRL_LOGOFF_EVENT,
    CTRL_SHUTDOWN_EVENT,
) = 0, 1, 2, 3, 4
continue_proc = True

def disable_con_proc():
    print("kill: {}".format(continue_proc))

@PHANDLER_ROUTINE
def console_handler(ctrl_type):
    r"""
    Console Control Handler for Windows

    This module provides functionality for handling console control events in Windows,
    namely CTRL_C_EVENT, CTRL_BREAK_EVENT, CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT, CTRL_SHUTDOWN_EVENT

        Args:
            ctrl_type (int): The type of control event.

        Returns:
            bool: True if the event is handled; False otherwise.

        Example:
            To use this module, import it and set your desired function as the console handler:

            >>> from consolectrlhandler import ctrl_config

            Define your custom function to handle console control events:

            >>> def ctrl_handler(ctrl_type):
            ...     print(f"Received control event: {ctrl_type}")

            Assign your custom function as the console handler:

            >>> ctrl_config.function = ctrl_handler

            Then run your main program loop.

            # Complete code
            from consolectrlchandler import ctrl_config
            import time

            def ctrlhandler(ctrl_type):
                print(f"ctrl handler {ctrl_type}")

            ctrl_config.function = ctrlhandler
            while True:
                print("test")
                time.sleep(1)
    """
    if ctrl_type in (
        CTRL_C_EVENT,
        CTRL_BREAK_EVENT,
        CTRL_CLOSE_EVENT,
        CTRL_LOGOFF_EVENT,
        CTRL_SHUTDOWN_EVENT,
    ):
        ctrl_config.function(ctrl_type=ctrl_type)
        return True
    return False

if not SetConsoleCtrlHandler(console_handler, True):
    raise RuntimeError("SetConsoleCtrlHandler failed.")

# to import

            from consolectrlchandler import ctrl_config
            import time

            def ctrlhandler(ctrl_type):
                print(f"ctrl handler {ctrl_type}")

            ctrl_config.function = ctrlhandler
            while True:
                print("test")
                time.sleep(1)

    test
    test
    ctrl handler 0
    test
    ctrl handler 0
    ctrl handler 0
    ctrl handler 0
    ctrl handler 0
    test
    ctrl handler 0
    test
    test```

You didn't provide the information from the issue template, nor the options used to compile.

I am sorry, I should have read it better.
python -m nuitka --version
2.1.5
Commercial: None
Python: 3.11.8 | packaged by Anaconda, Inc. | (main, Feb 26 2024, 21:34:05) [MSC v.1916 64 bit (AMD64)]
Flavor: Anaconda Python
Executable: C:\ProgramData\anaconda3\envs\proxifierapp\python.exe
OS: Windows
Arch: x86_64
WindowsRelease: 10
Version C compiler: C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.38.33130\bin\Hostx64\x64\cl.exe (cl 14.3).
How did you install Nuitka and Python?
I installed anaconda and the pip from anaconda. Then I used Anaconda's pip to install Nuitka. I never had any problems using it that way
command line
start "" "C:\ProgramData\anaconda3\envs\proxifierapp\python.exe" -m nuitka C:/ProgramData/anaconda3/envs/proxifierapp/multiinstancemanagerstacks.pyw --standalone --assume-yes-for-downloads --output-dir=c:/ctrlctest --onefile --windows-icon-from-ico=C:/Users/hansc/AppData/Local/Temp/tmpxtljzj_n.ico --windows-uac-admin --file-version=<IP_ADDRESS> --onefile-tempdir-spec=%CACHE_DIR%/multiinstancemanagerstacks/<IP_ADDRESS> --enable-plugin=tk-inter --jobs=1 --plugin-enable=multiprocessing --show-progress --show-modules

Nuitka converts these into KeyboardInterrupt by the onefile bootstrap I believe. That may interfere with your code, which is not handling that exception properly maybe. Otherwise, you probably can receive those events in the Python code no problem.

Yes, onefile bootstrap will convert them to CTRL_C_EVENT and send that to the Python process. Python then converts that to KeyboardInterrupt normally. Not responding gets it killed. If it don't want that to happen, set the timeout to a large value, that is --onefile-child-grace-time.
I am not entirely sure what you want to achieve though.

Thank you very much for your help! I will try that tomorrow! It's just about killing Bluestacks Instances. I build something like an Multiple-Instance-Manager. When I use "taskkill" to kill the instances, they break quite often and can't be started anymore, because the data is corrupt. When there is no console, everything is working fine, but I like the console when I do testing.

I am assuming, the grace time is not sufficient for your program, but it's a user error like that. In a way, this hard kill happening needs to be better described somewhere, but I don't track this a bug right now.

Thank you so much for your help! Like you, I also don't think that it is not a bug. Today I won't be able to check it, but during the week, I will compile it again, and give it a little more grace time. Have a good Sunday!


Gravity Model file missing/typo?

I'm getting this error during loading:
000006.141: Module Mars.dll .............. [Build 231227, API 231227]
000006.146: GRAVITY MODEL ERROR: COEFFICIENT FILE GravityModels\jgmro_120f_sha.tab NOT FOUND
The file included in the package is "jgmro_120d_sha.tab", which also doesn't match with the contents of the file "Notes on Gravity Models.txt".
Using the latest auto-build x86 package. (I didn't any thing else yet due to lack of time)

That's really odd. Especially since I know for an absolute fact that I had 120f, and tested it, and at least a few others have as well. There are graphs on the forum of data collected from mars. Yet the commit history doesn't show where anything has ever changed since my initial commits 2 years ago.
Either way, its a very easy fix, I just need to download the correct model from here https://ode.rsl.wustl.edu/mars/DataSetExplorer.aspx?target=mars&instrumenthost=MRO&instrumentid=RSS&datasetid=MRO-M-RSS-5-SDP-V1.0&volumeid=MRORS_1XXX&pathtovol=data/shadr/ and commit it.
I suppose it's possible that I had a local copy of 120f that was living in my out/Install/... folder, that made it so it worked?


Is it possible to disable globbing?

I'm trying to copy files from s3 to a local system. The files were downloaded from a variety of sources and kept their original filenames, some of which seem to have included ** or other wildcard patterns. Is there a way to disable globbing or escape the filenames? I am using filenames directly as supplied by an s3fs ls call.

The top level user methods like cat expect to expand paths. However, there are other methods like cat_file that work one file at a time and don't expand.
Currently, only recursive= is passed on by the bulk functions to .expand_path. There has been talk of disabling or being able to configure this process more, but these is no such option right now.

Thanks, get_file is exactly what I needed.
Maybe it would be good to mention this in the documentation? Something like adding "does not expand paths" to the get_file documentation, and something like "You can use get_file to get a single file" in the get documentation. Now that you've explained it it's a clear convention, but being new to the library I never would have realized it.

Updating docstring to make things clearer is always a good idea. Would you like to contribute an update? The change would be in fsspec.spec.AbstractFileSystem , which is S3FileSystem's superclass.


bugfix: use applyMode for apply cli

Describe what this PR does / why we need it
Does this pull request fix one issue?

Describe how you did it
Describe how to verify it
Special notes for reviews

Codecov Report
Base: 17.51% // Head: 17.51% // No change to project coverage :thumbsup:

Coverage data is based on head (792f647) compared to base (6d331c3).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1973   +/-   ##
=======================================
  Coverage   17.51%   17.51%
=======================================
  Files         103      103
  Lines        9184     9184
=======================================
  Hits         1609     1609
  Misses       7362     7362
  Partials      213      213

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

LGTM


HTTPFileController allows for serving files

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a66a5d7). Click here to learn what that means.
The diff coverage is 96.42%.

@@            Coverage Diff            @@
##             master     #255   +/-   ##
=========================================
  Coverage          ?   86.39%
=========================================
  Files             ?       88
  Lines             ?     5585
  Branches          ?        0
=========================================
  Hits              ?     4825
  Misses            ?      760
  Partials          ?        0

Impacted Files
Coverage Δ

lib/src/http/response.dart
91.66% <ø> (ø)

lib/src/http/request.dart
97.5% <100%> (ø)

lib/src/http/http_codec_repository.dart
92.45% <100%> (ø)

lib/src/application/application_server.dart
97.14% <100%> (ø)

lib/src/http/file_controller.dart
95.45% <95.45%> (ø)

Continue to review full report at Codecov.

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


Customizable paths

Trying to use jib for producing a flyyway migrations image. In this case flyway expects files in different paths.
Here's an example of how I produce the current docker image:
	val dockerfile by creating(Dockerfile::class) {
		dependsOn(shadowJar)

		from(From("flyway/flyway"))

		environmentVariable(mapOf(
			"FLYWAY_URL" to "jdbc:postgresql://hostname/database",
			"FLYWAY_USER" to "user",
			"FLYWAY_PASSWORD" to "password",
			"FLYWAY_SCHEMAS" to "public",
			"FLYWAY_TABLE" to "schema_version",
			"FLYWAY_LOCATIONS" to "classpath:db/migration"
		))

		copyFile(shadowJar.get().outputs.files.first().relativeTo(project.buildDir).path, "/flyway/jars")
	}

I would like to get rid of the shadowjar, but as you can see flyway looks up jars in /flyway/jars, and provides its own entrypoint for everything.
So what I would like is if it would be possible to customize /app/libs, /app/classes and /app/resources paths to somewhere under /flyway. I haven't managed to find such configuration in the gradle plugin, correct me if I'm wrong.

That doesn't allow me to move files, only to decide their layers - or if some files should be omitted - if I understand correctly. Or you mean reading the source of the filter extension and develop my own? Sure that's a fallback to explore.

It looks like you want to set the app root of the container? https://github.com/GoogleContainerTools/jib/blob/891c6c4584b873d1e1bf25e343c533a467e01d98/jib-gradle-plugin/README.md#extended-usage. The default root directory, as you have noticed, is app/ in Jib but jib.container.appRoot lets you customize where the contents of the app are placed. Alternatively,  you also have the option to customize the entrypoint of the image generated by Jib.

Unfortunately not enough. Jib uses /approot/{classes, libs, resources}, while flyway uses /flyway/{jars, sql} etc... but you're right, I guess the entrypoint could intercept the flyway entrypoint and setup some symlinks inbetween, and I guess the same could be done to handle AWS Lambda where classes should end up in /var/task.

@dsvensson I'm having this exact issue with AWS Lambda with /app/classes -> /var/task and /app/libs -> /var/task/lib. Do you have anything you can point me to on how to set this up? thanks

@jdimeo I think they are talking about running a bash script where you can do anything, including running, for example, the ln UNIX-command to create symlinks at container runtime. Check out this Stack Overflow answer: https://stackoverflow.com/a/69259214/1701388

Thanks @chanseokoh - it would be amazing if Jib allowed more path customizations because we get so close with the appRoot config option. Currently trying this out per the linked post but it's still not setting up the links correctly:
#!/bin/sh
ln -s /app/classes/ /var/task
ln -s /app/libs/ /var/task/lib
/lambda-entrypoint.sh com.Class::handleRequest

it would be amazing if Jib allowed more path customizations because we get so close with the appRoot config option.

@jdimeo I hear you. However, Jib is a highly opinionated tool with a certain intention, and although it provides some degree of customization knobs. Providing too many knobs would increase the API surface too much and may compromise the philosophy of the direction of Jib. As a compromise, for such narrow use cases, Jib provides the Jib Extensions interface, although it means you'll have to write your own extension.

Totally understood- Jib is super powerful as it is. But I think I'm stuck in this case.
Lambda insists that classes go right into /var/task. But I can't symlink /var/task to point to something else, because it needs to be a folder with a lib symlink inside of it.  I must be missing something here?
I'll look into the extensions, maybe that is the best way to support AWS Lambda? Which I'm guessing would be really popular? More context on the Usage tab here: https://gallery.ecr.aws/lambda/java

I got really close with this:
#!/bin/sh
rm -rf /var/task
ln -s /app/classes/ /var/task
ln -s /app/libs/ /app/classes/lib
/lambda-entrypoint.sh com.Class::handleRequest

What this is doing is removing the original /var/task folder which allows me to replace it with the /var/task link to /app/classes. Inside /app/classes I link a lib folder back out to /app/libs. My ls commands look good when I inspect the image locally:

But- Lambda is still upset because the file system is read only:

So close yet so far...

Ah, so you cannot make any changes at runtime to your immutable image layers (at least on /var/task) on Lambda, which makes sense. Then unfortunately, I think the only available option is the Jib Extension.

Thank you so much for your helpful replies and thank you so much for Jib! it's a dream come true with Maven builds. That being said, I do think there is a valid use case for customizing the "layout" that Jib uses to build the app. We already have two use cases: Flyway and AWS Lambda and there will be many more. I don't think this is really a niche use case IMO, but I understand that you have to consider a lot when maintaining this.

Just so you know, I am no longer a maintainer of Jib. From what I can see, the chance that they may implement this kind of path customization is very unlikely, unfortunately. If so, I think the Jib Extension is the only option.

OK I got it to work! Here it is. Will be tagging a 1.0.0 release soon and you can use Jitpack to integrate into Maven builds. Note that it's actually a general purpose "find and replace" to adjust entry paths, it just comes with a default config for the AWS Lambda convention: https://github.com/jdimeo/jib-extension-aws-lambda


Disable Artifacts if project is using .NET SDK's built-in artifacts functionality

If a user has opted into the .NET SDK's artifacts functionality by setting the MSBuild property UseArtifactsOutput, then disable Microsoft.Build.Artifacts since you would only want to be using one or the other.
Also enables the pipeline to run tests against .NET 7.0

Related PR in .NET SDK to disable itself if Microsoft.Build.Artifacts is in use: https://github.com/dotnet/sdk/pull/33470

/azp run


Add libblas host dependency

per https://github.com/conda-forge/r-forecast-feedstock/pull/16#issuecomment-606875193

Checklist

[ ] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

@conda-forge-admin, please rerender


Add ICANN reserved names

Reserved names
Details: https://www.icann.org/resources/pages/reserved-2013-07-08-en
XML file they link to: https://www.icann.org/sites/default/files/packages/reserved-names/ReservedNames.xml
Looks like it has sections for:

International Olympic Committee
Red Cross
IGOs

…and ~770 total reserved names.
Two-char ASCII

https://www.icann.org/resources/two-character-labels
looks like they're all initially reserved, but gTLDs can eventually release them if they want.

Country and Territory names

https://www.icann.org/resources/country-territory-names
but like two-char ASCII, registries can release them if they want.

Hm, these aren’t zones, but they are reserved labels. I’m not sure if zones are the best place to record this data?
Maybe metadata as a list of reserved labels?


Make keyboard shortcuts discoverable

There is currently no way of discovering the keyboard shortcuts.
It would be good to have a simple help modal which lists all keyboard shortcuts. It should itself be available via the ? shortcut.

:+1: Good examples:

Github
Gmail
Trello

Current shortcuts (originally posted in discussion over on #2033):
esc closes any open modal
c opens the create modal
g a navigates to the Apps page
g d navigates to the Deployments page
g v shows the current UI version number
⇧+, shows the about modal

@philipnrmn very cool idea – though hiding the keyboard shortcut legend behind another keyboard shortcut probably won't help noobs. How about adding an info section to our About modal?


timeout

Describe Your Problem:
been working great now getting timeout errors may be related to having been connected to vpn earlier. on iMac safari is not the best of letting go.
Logs:
[5/5/2022, 6:04:48 PM] [Garage Door] [API] An error occurred getting oauth token; timeout of 5000ms exceeded
[5/5/2022, 6:04:48 PM] [Garage Door] [API] An error occurred getting devices from account; timeout of 5000ms exceeded
[5/5/2022, 6:04:48 PM] [Garage Door] Failed to load doors from account; skipping discovery
Show the Homebridge logs here, remove any sensitive information.

Plugin Config:
Show your Homebridge config.json here, remove any sensitive information.

{
"name": "Garage Door",
"username": "xxx",
"password": "xxx,
"batteryLowLevel": 15,
"userInfoCacheTtl": 3600,
"doorStatusStationaryCacheTtl": 15,
"doorStatusTransitioningCacheTtl": 5,
"doorStatusPollInterval": 15000,
"logApiResponses": false,
"platform": "GenieAladdinConnect"
}
Screenshots:

Environment:

Plugin Version:
Homebridge Version: homebridge-config-ui-x v4.43.2
homebridge-genie-aladdin-connect v2.1.4
Node.js Version:
NPM Version:
Operating System:

I just started getting the same thing. They either have an outage or change the URL. Looking..

Their app is not loading for me so I assume its a system wide issue with the genie API. I will continue periodically checking in to see if the app starts working again and will report back.

Hmm the app is still not working however my control4 integration is still working.

I can confirm that my Aladdin Connect app is all levels of buggy, but I am still able to open and close using Siri and HomeBridge.
Seems to be a server wide issue.

It looks like they have resolved the issue and the plugin is working again. Can you confirm @arlieeh and @jnubz?

@derek-miller It started working again just after Midnight EST. Had nothing to do with your code. ;)

Could not respond sooner! Mine is still not working. I am able to use Connect again. No error message on restart of HomeKit or when selecting open or close. I also tried switching Home to a different hub did not make a difference.

@arlieeh do you mind opening a new ticket and providing the requested info? I ask because this seems like a different issue. Its also helpful if you could run homebridge in debug mode so we get more detailed logs.


Handle absence of parameter files gracefully or provide sensible defaults

Currently, cats works fine if run from the git checkout as it finds config.yml and fixed_parameters.yml. When run out of tree, for example by using a pipx install, cats fails as it does not find parameter files.
Steps to reproduce:
$ cd <directory where cats is cloned>
$ pipx install .
$ cd <any other directory>
$ cats -d 5 --loc OX1 --jobinfo=cpus=2,gpus=0,memory=8,partition=CPU_partition
WARNING:root:config file not found
Traceback (most recent call last):
  File "/Users/abhidg/.local/bin/cats", line 8, in <module>
    sys.exit(main())
             ^^^^^^
  File "/Users/abhidg/.local/pipx/venvs/climate-aware-task-scheduler/lib/python3.12/site-packages/cats/__init__.py", line 285, in main
    args.jobinfo, expected_partition_names=config["partitions"].keys()
                                           ~~~~~~^^^^^^^^^^^^^^
KeyError: 'partitions'

Expected output:
cats should show a user-friendly error in this case and suggest a config file.
Other points:
If the fixed_parameters.yaml file is fixed and non-configurable by the user, then it makes sense to inline it in the carbonFootprint module. Data files can be installed through pyproject.toml, but this may not be needed for this use case.

fixed_parameters.yaml is not used anymore


Enhancement to heat maps to show the second stage when proofs are found

Would it be possible to have a second version of heat maps that would show time spent processing found proofs?  With the Chia 1.2.0+ looks like there is a big deterioration in times needed for the second stage (when proofs are found).  Having heatmaps that would show those times would be really nice.

That is a good idea now that pooling is out and the partial proofs can be stale if sent too late. The current heatmap doesn't really give good info on the proofs found lookup times when looking at it. I will look into something like this once I finish up with my current project.


[BUG] Pop up message not visible clearly.

Description
In the pop up message, the text is not clearly visible with grey color.
Screenshots

Any additional information?
No response
What browser are you seeing the problem on?
Chrome
Checklist

[X] I have checked the existing issues.
[X] I have read the Code Of Conduct
[X] The changes don't break the code
[X] Please attach the screenshots and video of the development work once it is done

Assign me this issue


Resource leak in InputStreamDownload.java

There is a bug in this code:
@Override
	public void write(HttpServletResponse response) throws IOException {
		writeDetails(response);

		OutputStream out = response.getOutputStream();
		ByteStreams.copy(stream, out);
	}

the input stream is never disposed.
I have submitted a PR:
https://github.com/caelum/vraptor4/pull/1069

thanks @siddjain. I just left a comment in your PR


How to make proChat UI in English language instead of Chinese?

Currently the language is Chinese by default as shown in the image. But I want English Language by default

nice question, we are doing the globalization things，links：https://github.com/ant-design/pro-chat/issues/56

nice question, we are doing the globalization things，links：#56

I have seen that but I couldn't make it work.. Can you please help the users of Prochat UI where to make the changes? which file or any documentation available?

nice question, we are doing the globalization things，links：#56

Hi Any help on this? Can you answer where to make changes for Globalization? We need English and not only Chinese.

nice question, we are doing the globalization things，links：#56

I have seen that but I couldn't make it work.. Can you please help the users of Prochat UI where to make the changes? which file or any documentation available?

we still doing this work, u can find the feature in pull request page, maybe it will be ready in next small version

nice question, we are doing the globalization things，links：#56

I have seen that but I couldn't make it work.. Can you please help the users of Prochat UI where to make the changes? which file or any documentation available?

we still doing this work, u can find the feature in pull request page, maybe it will be ready in next small version
@AIAnytime wating this pr ready haha
https://github.com/ant-design/pro-chat/pull/106

Thanks for the reply. Any other alternative to Pro Chat? I loved the components but can't wait many days to get the solution up and running.

Is Globalization PR is merged?

Is Globalization PR is merged?

not ready hahaha plz wait a time  QAQ

Just want to add that we can set the locale prop in the ProChat component to en-US and it works.


DeviceNetwork needs documenting

@Zumorica @juliangiebel
Updated with Julian had.

Code needs some commenting.
Event unsubscriptions (for the UI stuff it never gets unsubscribed but a lot of stuff seems to do this which is bad).
NetworkConnection should probably be a component given it's attached to an entity
Some dependencies are manually resolved when they could just use the attribute.
There's 2 recursive methods under DeviceNetworkConnection that don't seem like they'd ever finish?
Disposal mailing units seem to be hardcoded to wired connections (should also be a component).
DisposalMailingUnit was a copy-paste from DisposalUnit when it shouldn't be.
public fields
Internal seems to be used instead of private in a few spots.

The hackmd page i linked in the pr is here https://hackmd.io/@dUUm5XdUR2Gd9I7x4_Weyg/BJAzlGQ8D
It's a bit outdated by now

Finished up to date documentation here: https://docs.spacestation14.io/en/content/device-network
Mailing units got yeeted and i will reimplement them.
Device network rewrite to ECS: #4205


Native API: Allow custom JSON serializers

Hi,
As far as I can tell, both new and old native API expect the documents to come in Map<String, Object> and be serialized with Jackson. However, this approach may be unsuitable for folks using other JSON libraries, that are not reflection-based (disclaimer: I’m one of them).
I think it should be straightforward to add something like putDocument(String _id, String _rev, Map<String, Object> _attachments, String json) to support this usecase. json here of course includes _id, _rev and _attachments as well. It would be even better (although less efficient) to have putDocument(String json), which would parse the json internally.
Similarly, there could be versions of getDocument and queries, that return raw JSON.

@stanch I had the same problem with you and implemented a fix. I'm also using Scala. You should check it out:
https://github.com/a-reisberg/typebase-lite


for some hexo renders of markdown, the css of image is not compatible with tag plugins mode, it should be set the image link style to markdown mode.

for some hexo renders of markdown, the css of image is not compatible with tag plugins mode, it should be set the image link style to markdown mode.

with the tag plugins mode, the image is out of page, and can't zoom-in.

html code after render:

with markdown mode, it's fine.

html code after render:

Thanks for your contribution.
But when you want to use original markdown mode for images, removing this plugin is a better way. In another word, the plugin exists just for replacing markdown image with hexo image which having a correct src.


[FEATURE REQUEST] Display package released date (if applicable) and installed date.

Can we display package released date (if application) on the Discover tab and Package released and installed date on Installed tab please? Also if this is possible, then I am sure sort on the dates on respective tabs please.

Can we display package released date (if application) on the Discover tab and Package released and installed date on Installed tab please? Also if this is possible, then I am sure sort on the dates on respective tabs please.

Most package managers don't provide this information (unless you manually query each package info, which is not an option), so only 1 out of 10 packages would have the date, and the other 9 would show Not Available.

Thanks @marticliment for your prompt reply. How about installation date? That should be ok as wingetUI installs it. Won't it be helpful on the "Installed packages" tab to sort by installed date?

The issue here is the same, this information is not easily provided by Package Managers


Unable to install using Pip

I am unable to install using pip install .It gives  Running setup.py bdist_wheel for MulticoreTSNE ... error, CMake error at CMakeLists.txt:1 Failed to run MSBuild command.Then build failed error. I am using cmake version 3.11.0-rc4, Microsoft .Net Framework v4.0.30319.
I am getting this error:
$ pip install .
Processing c:\users\deep chatterjee\multicore-tsne
Requirement already satisfied: numpy in e:\anaconda3\lib\site-packages (from Mul                                                                                ticoreTSNE==0.1) (1.14.5)
Requirement already satisfied: cffi in e:\anaconda3\lib\site-packages (from Mult                                                                                icoreTSNE==0.1) (1.10.0)
Requirement already satisfied: pycparser in e:\anaconda3\lib\site-packages (from                                                                                cffi->MulticoreTSNE==0.1) (2.18)
Building wheels for collected packages: MulticoreTSNE
Running setup.py bdist_wheel for MulticoreTSNE: started
Running setup.py bdist_wheel for MulticoreTSNE: finished with status 'error'
Complete output from command E:\Anaconda3\python.exe -u -c "import setuptools,                                                                                tokenize;file='C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-                                                                                req-build-fc9af9iu\setup.py';f=getattr(tokenize, 'open', open)(file);code=f                                                                                .read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))" b                                                                                dist_wheel -d C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-wheel-c0r7vy                                                                                ex --python-tag cp36:
running bdist_wheel
running build
running build_py
creating build
creating build\lib.win-amd64-3.6
creating build\lib.win-amd64-3.6\MulticoreTSNE
copying MulticoreTSNE_init_.py -> build\lib.win-amd64-3.6\MulticoreTSNE
creating build\lib.win-amd64-3.6\MulticoreTSNE\tests
copying MulticoreTSNE\tests\test_base.py -> build\lib.win-amd64-3.6\MulticoreT                                                                                SNE\tests
copying MulticoreTSNE\tests_init_.py -> build\lib.win-amd64-3.6\MulticoreTS                                                                                NE\tests
running egg_info
creating MulticoreTSNE.egg-info
writing MulticoreTSNE.egg-info\PKG-INFO
writing dependency_links to MulticoreTSNE.egg-info\dependency_links.txt
writing requirements to MulticoreTSNE.egg-info\requires.txt
writing top-level names to MulticoreTSNE.egg-info\top_level.txt
writing manifest file 'MulticoreTSNE.egg-info\SOURCES.txt'
reading manifest file 'MulticoreTSNE.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'MulticoreTSNE.egg-info\SOURCES.txt'
running build_ext
cmake version 3.11.0-rc4
CMake suite maintained and supported by Kitware (kitware.com/cmake).
-- Building for: Visual Studio 10 2010
CMake Error at CMakeLists.txt:1 (PROJECT):
Failed to run MSBuild command:
  C:/Windows/Microsoft.NET/Framework/v4.0.30319/MSBuild.exe

to get the value of VCTargetsPath:

  Microsoft (R) Build Engine version 4.6.1055.0
  [Microsoft .NET Framework, version 4.0.30319.42000]
  Copyright (C) Microsoft Corporation. All rights reserved.

  Build started 02-08-2018 17:04:52.
  Project "C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-f                                                                                c9af9iu\build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCTargetsPath.vcx                                                                                proj" on node 1 (default targets).
  C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-fc9af9iu\b                                                                                uild\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCTargetsPath.vcxproj(14,2                                                                                ): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was not                                                                                found. Confirm that the path in the <Import> declaration is correct, and that th                                                                                e file exists on disk.
  Done Building Project "C:\Users\Public\Documents\Wondershare\CreatorTemp\p                                                                                ip-req-build-fc9af9iu\build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCT                                                                                argetsPath.vcxproj" (default targets) -- FAILED.

  Build FAILED.

  "C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-fc9af9iu\                                                                                build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCTargetsPath.vcxproj" (d                                                                                efault target) (1) ->
    C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-fc9af9iu                                                                                \build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCTargetsPath.vcxproj(14                                                                                ,2): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was no                                                                                t found. Confirm that the path in the <Import> declaration is correct, and that                                                                                the file exists on disk.

      0 Warning(s)
      1 Error(s)

  Time Elapsed 00:00:00.06

Exit code: 1

-- Configuring incomplete, errors occurred!
See also "C:/Users/Public/Documents/Wondershare/CreatorTemp/pip-req-build-fc9a                                                                                f9iu/build/temp.win-amd64-3.6/Release/CMakeFiles/CMakeOutput.log".
ERROR: Cannot generate Makefile. See above errors.

Failed building wheel for MulticoreTSNE
Running setup.py clean for MulticoreTSNE
Failed to build MulticoreTSNE
Installing collected packages: MulticoreTSNE
Running setup.py install for MulticoreTSNE: started
Running setup.py install for MulticoreTSNE: finished with status 'error'
Complete output from command E:\Anaconda3\python.exe -u -c "import setuptool                                                                                s, tokenize;file='C:\Users\Public\Documents\Wondershare\CreatorTemp\pi                                                                                p-req-build-fc9af9iu\setup.py';f=getattr(tokenize, 'open', open)(file);code                                                                                =f.read().replace('\r\n', '\n');f.close();exec(compile(code, file, 'exec'))"                                                                                install --record C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-record-r                                                                                ni883bh\install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_py
creating build
creating build\lib.win-amd64-3.6
creating build\lib.win-amd64-3.6\MulticoreTSNE
copying MulticoreTSNE_init_.py -> build\lib.win-amd64-3.6\MulticoreTSNE
creating build\lib.win-amd64-3.6\MulticoreTSNE\tests
copying MulticoreTSNE\tests\test_base.py -> build\lib.win-amd64-3.6\Multicor                                                                                eTSNE\tests
copying MulticoreTSNE\tests_init_.py -> build\lib.win-amd64-3.6\Multicore                                                                                TSNE\tests
running egg_info
writing MulticoreTSNE.egg-info\PKG-INFO
writing dependency_links to MulticoreTSNE.egg-info\dependency_links.txt
writing requirements to MulticoreTSNE.egg-info\requires.txt
writing top-level names to MulticoreTSNE.egg-info\top_level.txt
reading manifest file 'MulticoreTSNE.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'MulticoreTSNE.egg-info\SOURCES.txt'
running build_ext
cmake version 3.11.0-rc4
CMake suite maintained and supported by Kitware (kitware.com/cmake).
-- Building for: Visual Studio 10 2010
CMake Error at CMakeLists.txt:1 (PROJECT):
  Failed to run MSBuild command:

    C:/Windows/Microsoft.NET/Framework/v4.0.30319/MSBuild.exe

  to get the value of VCTargetsPath:

    Microsoft (R) Build Engine version 4.6.1055.0
    [Microsoft .NET Framework, version 4.0.30319.42000]
    Copyright (C) Microsoft Corporation. All rights reserved.

    Build started 02-08-2018 17:04:57.
    Project "C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build                                                                                -fc9af9iu\build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCTargetsPath.v                                                                                cxproj" on node 1 (default targets).
    C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-fc9af9iu                                                                                \build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCTargetsPath.vcxproj(14                                                                                ,2): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was no                                                                                t found. Confirm that the path in the <Import> declaration is correct, and that                                                                                the file exists on disk.
    Done Building Project "C:\Users\Public\Documents\Wondershare\CreatorTemp                                                                                \pip-req-build-fc9af9iu\build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\V                                                                                CTargetsPath.vcxproj" (default targets) -- FAILED.

    Build FAILED.

    "C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-fc9af9i                                                                                u\build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCTargetsPath.vcxproj"                                                                                (default target) (1) ->
      C:\Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-fc9af9                                                                                iu\build\temp.win-amd64-3.6\Release\CMakeFiles\3.11.0-rc4\VCTargetsPath.vcxproj(                                                                                14,2): error MSB4019: The imported project "C:\Microsoft.Cpp.Default.props" was                                                                                not found. Confirm that the path in the <Import> declaration is correct, and tha                                                                                t the file exists on disk.

        0 Warning(s)
        1 Error(s)

    Time Elapsed 00:00:00.04

  Exit code: 1

-- Configuring incomplete, errors occurred!
See also "C:/Users/Public/Documents/Wondershare/CreatorTemp/pip-req-build-fc                                                                                9af9iu/build/temp.win-amd64-3.6/Release/CMakeFiles/CMakeOutput.log".

ERROR: Cannot generate Makefile. See above errors.

----------------------------------------

Command "E:\Anaconda3\python.exe -u -c "import setuptools, tokenize;file='C:                                                                                \Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-fc9af9iu\se                                                                                tup.py';f=getattr(tokenize, 'open', open)(file);code=f.read().replace('\r\n'                                                                                , '\n');f.close();exec(compile(code, file, 'exec'))" install --record C:\Use                                                                                rs\Public\Documents\Wondershare\CreatorTemp\pip-record-rni883bh\install-record.t                                                                                xt --single-version-externally-managed --compile" failed with error code 1 in C:                                                                                \Users\Public\Documents\Wondershare\CreatorTemp\pip-req-build-fc9af9iu\
Thanks in advance

I have the same problem and unable to install

me too. i tried eveything and nothing seemed to work :(

Same here, Windows, py 3.7.4

I have successfully installed it today on my Windows 8.1 machine. Steps worked for me:

Uninstall and re-install cmake link:https://cmake.org/download/
Install Chocolatey link: https://chocolatey.org/courses/installation/installing?method=installing-chocolatey?quiz=true
Install Visual c++ build tools link: https://chocolatey.org/packages/visualcpp-build-tools.
Run pip install MulticoreTSNE at my Anaconda environment.

@ccheung39 @koalap-2018 @AmichayAfriat Hope these steps help you too. Happy Learning.

I had the same error and followed the steps above, but I seem to get the same error again.
I am using: python 3.7.0, Windows.

I have successfully installed it today on my Windows 8.1 machine. Steps worked for me:

Uninstall and re-install cmake link:https://cmake.org/download/
Install Chocolatey link: https://chocolatey.org/courses/installation/installing?method=installing-chocolatey?quiz=true
Install Visual c++ build tools link: https://chocolatey.org/packages/visualcpp-build-tools.
Run pip install MulticoreTSNE at my Anaconda environment.

@ccheung39 @koalap-2018 @AmichayAfriat Hope these steps help you too. Happy Learning.

I had the same error and followed the steps above, but I seem to get the same error again.
I am using: python 3.7.0, Windows.


chore: [FX-4013] Integrate focus state and autoFocus

FX-4013
Description
We need to integrate to the new RTE:

focus state
auto focus

How to test

check temploy

Development checks

[ ] Make sure that additions and changes on design follow Toptal's BASE design, and it's been already discussed with designers at #-base-core
[x] Annotate all props in component with documentation
[ ] Ensure that deployed demo has expected results and good examples
[x] Self reviewed
[x] Covered with tests

All development checks should be done and set checked to pass the
GitHub Bot: TODOLess action

PR commands

List of available commands:

@toptal-bot run package:alpha-release - Release alpha version
@toptal-anvil ping reviewers - Ping FX team for review

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit: to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

@toptal-anvil ping reviewers


Accessibility | Sign In & Sign Up | Enter on last field of the form does not fire event

Where?

Signup
Signin

What?
If user has entered all fields and is on the last field, pressing Enter/Return should execute the button click handler.

If you allow I'll look into this bug as well @aadeshkulkarni

Sure, assigned to you

#75 closes this


Activ edge

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@c06b2ee). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   33.72%
=========================================
  Files             ?       58
  Lines             ?     3039
  Branches          ?      469
=========================================
  Hits              ?     1025
  Misses            ?     1850
  Partials          ?      164

Continue to review full report at Codecov.

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


Added new tokens

Changes to be committed:
modified:   .vscode/launch.json
modified:   PirateLexer/Globals.cs
modified:   PirateLexer/Lexer.cs
modified:   PirateLexer/Models/TokenType.cs
modified:   PirateLexer/TokenRepository.cs
modified:   PirateParser/Parser.cs
modified:   Shell/CommandRepository.cs
new file:   Shell/main.pirate
deleted:    Shell/test.pirate
new file:   packingcommands.txt

Summary:

Added list defined between []
Added for loop for looping through a range
Added foreach loop for looping through a collection

New foreacha nd in keywords

Added += . and $ operators
Added SYNTAX.ms for current syntax


GLSL shader not compiling

I am running a mac 10.14.6 build with an integrated graphics and run into the following errors upon clicking New Game.
Known pipe types:
  CocoaGraphicsPipe
(all display modules loaded.)
:display:gsg:glgsg(error): An error occurred while compiling GLSL vertex shader Assets/Shared/shaders/pbr_shader_v.vert:
ERROR: Assets/Shared/shaders/pbr_shader_v.vert:4: '' :  version '130' is not supported
ERROR: Assets/Shared/shaders/pbr_shader_v.vert:31: 'transform_index' : syntax error: syntax error
:display:gsg:glgsg(error): An error occurred while compiling GLSL fragment shader Assets/Shared/shaders/pbr_shader_f.frag:
ERROR: Assets/Shared/shaders/pbr_shader_f.frag:5: '' :  version '130' is not supported
:display:gsg:glgsg(error): An error occurred while compiling GLSL vertex shader Assets/Shared/shaders/pbr_shader_v_invert.vert:
ERROR: Assets/Shared/shaders/pbr_shader_v_invert.vert:4: '' :  version '130' is not supported
ERROR: Assets/Shared/shaders/pbr_shader_v_invert.vert:31: 'transform_index' : syntax error: syntax error
:display:gsg:glgsg(error): An error occurred while compiling GLSL fragment shader Assets/Shared/shaders/pbr_shader_f_invert.frag:
ERROR: Assets/Shared/shaders/pbr_shader_f_invert.frag:5: '' :  version '130' is not supported

Which leads to the following.

I'm unsure if this is (1) a mac thing or (2) an integrated graphics thing. Is the goal to provide support for either or both of these?

It looks like your hardware or software does not support OpenGL version 130. Our team is not currently testing on Mac. The demo has been tested on i5 integrated graphics and Ubuntu with success.


New version: Modeliosoft.Modelio version 5.4.1

Pull request has been created with WinGet Automation :rocket:
Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:


Implement addon resource

https://developer.atlassian.com/bitbucket/api/2/reference/resource/addon

moving this to #31


feature (folder_item): add open item in new tab on click mouse

Added functionality for opening an element by clicking the middle mouse button

@nicolay-i Thank you for your contribution!
I am working on adding keyboard navigation now and have changed the same code almost the same way. Also, I recently added opening in new tab by the middle mouse button. Please check if you have the latest version of the extension.


Extraction goes into infinite loop with some cab files

When trying to extract cab files from Texas Instruments Avigo Manager, extraction goes into infinite loop.
unshield -D3 x data5.cab results in this:
http://pastie.org/pastes/10830939/text?key=9gocgtm2mhruuhy0ngiq
Same thing for all the cab files in the zip.
Here is a direct link to the file in question: https://www.ti.com/organizers/avigo/docs/avigomanager11b22.zip

Thanks for the bug report. That's really interesting! I'll see if I can find anything obvious.
As always, PR is welcome! :-)

That was some really old InstallShield files you had there... Fixed in git now, thanks again! And you need to use the -O command line option to enable "old (de)compression".

Yes, seems to be working after a pull and a rebuild. Thank you so much for such a fast response and fix!


Update Tile for Foundry VTT v10.286

To Change
Tile
Kind of Change
Update
Additional Info
No response

I'd like to work on this one.


[WIP] 2019 Roadmap

This proposes an outline of our 2019 roadmap. Please leave comments and propose new items.

A few things I can think of that should probably be on the roadmap - sidecar containers for Tasks, the ability to have a Task run on something other than a container (i.e., running on a Windows or Mac box somewhere), and the ability for a Task to pause until some condition it can poll for is met (to enable things like manual approval steps to be built on top of Build Pipeline).


Bit shifting

If anyone needs this, tell me, otherwise I won't add it, because I can't think of a use case atm