[BUG] Leftover persona "Dev"?

Description
Is it intended to have both "Dev" and "Developer" personas? "Dev" is hidden by default, which is perhaps why it hasn't been noticed? "Dev"'s system prompt is included in "Developer", and I think most developers would want an advanced assistant, rather than a basic one. The Cursor community has been sharing more advanced system prompts.
Device and browser
All
Screenshots and more

"Developer" imposes a cutoff date of Aug 2023. Is that intended? Why not leave that up to the model(s)?

Willingness to Contribute

[ ] 🙋♂ Yes, I would like to contribute a fix.

Thanks - this shall be also taken care off once we fully redo the Personas system #35 .


Update shoppingcart_products.yaml

Add fields to blueprint to add Collection header

That's an important and necessary change. Especially for the non-technical people!

header.category is also missing.  I will do another edit

Thanks Mike. Still miss more blueprint configuration in pages, in the plans

I will submit what I see.  I have been doing another cart
Sent from my BlackBerry - the most secure mobile device - via the Bell Network
From<EMAIL_ADDRESS>Sent: April 7, 2017 1:52 PM
To<EMAIL_ADDRESS>Reply-to<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>Subject: Re: [flaviocopes/grav-plugin-shoppingcart] Update shoppingcart_products.yaml (#58)
Thanks Mike. Still miss more blueprint configuration in pages, in the plans
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/flaviocopes/grav-plugin-shoppingcart/pull/58#issuecomment-292606621, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AFkZf84w82uLPE6RTb3szSad6DHDgozRks5rtnf1gaJpZM4M0YMF.


RHOARDOC-1597: Creating a new app using Launcher

@tradej I have received approval on this procedure from Thomas Q over email on 2019-06-27


Support for new laravel-mongodb version

Allowing version jenseggers/laravel-mongodb = 3.5.* to patch critical problem [jenssegers/laravel-mongodb/pull/1712]
It will be a breaking change as it is specific to laravel = "5.8" and will not work for any laravel = "<5.8"
Hence recommended to release new version with this change applied specifically for laravel = "5.8".

Any update on this?
@StevePorter92 @willtj  @danjohnson95

Looks good to me, thanks. This change will support extra versions of jenssegers/mongodb but it won't require anyone to update so I don't think this alone needs to be considered a breaking change.

@willtj current passport version is 7.2.1 maybe add that version too? I have tested and looks good.


SPFx project upgrade missing react types

Hi,
when upgrading some solutions from SPFx 1.7.0 and 1.7.1 to 1.8.0 I noticed that the upgrade report is missing the steps to upgrade @types/react and @types/react-dom.
The solutions to be upgraded where still on React 15, so I got the steps to upgrade to React 16 in the report:

FN001008 react | Required
FN001009 react-dom | Required

Expected behavior:
If the React version is still v15 and the upgrade recommends upgrading to React 16 the types should also be included in the upgrade report:

FN001005 @types/react | Required
FN001006 @types/react-dom | Required

Thank you for reporting this issue @cwdata. I'll investigate it and get back to you as soon as I know more.

So this behavior is by design. The way project upgrades are implemented in the CLI is that they are based on the difference between one version of the project and another. For example, with regards to react, the only change that has been changed between v1.7.1 and v1.8.0 is the version of react and react-dom. @types/react and @types/react-dom are still on the same version. If you had a project using SPFx v1.7.1 based on react v15, which is different than the version of react you get when you'd create a new project, you'd only get notified of update of react and not @types/react. The project comparison is based on the assumption, that all elements of the projects match all properties of a newly created project on the same SPFx version. If you've upgraded your project manually in the past and haven't changed some properties then it could be that the recommended upgrade steps won't be complete.

Ok I see - thanks for the clarification.


SWT Price FX Cycle

From @bkawk on July 24, 2017 23:56
Everywhere a price is displayed, the user should be able to click the price to cycle through different currencies.

The default is set to SWT
The first click cycles to ETH the second click cycles to USD the third is EUR then back to SWT
When the user selects a different currency all prices in the app are changed to that currency not just the selected one
Multiple Fx API providers needs to be found
This will form its own component that will be applied to others via the slot
This will pull data from a new data-fx component that will try multiple providers
Update the spec on the Wiki
Insert new component into display-hashtag-deals

Copied from original issue: swarmcity/sc-boardwalk-production#122

From @kingflurkel on July 25, 2017 0:31
The value input also changes to the ref currency. Only on the final make deal screen, the SWT value is shown.

I'm not really on board with this. I don't think it's good to have every price be a clickaction, with a sort of carrousel-thingy. Can we please discuss this more/better and for now, label this as "future-feature-suggestion"?


On Demand list should filter for fortnightly shows

When listing on demand episodes, the app shows all available for the on demand key. However, the on demand key is shared for fortnightly shows. This means that off-weeks are also listed. This can be confusing for listeners.
We should be able to use the date of the on demand episode to calculate whether that episode was in week A or B, then filter based on the Show's place in the schedule, and only show this show's episodes.

Done!


Forced unwrap null value solved (iOS)

Connection with issue(s)
No issue created
Testing and Review Notes
v6.0.0-beta.23 an error is thrown here:
let cookie = HTTPCookie(properties: properties)!
A force unwrap is done on a value that can be null. The PR wraps a null check around it.

@maxmitz could you post a code example to replicate this issue? It should always work. If it doesn’t work, than there is something wrong before creating the cookie.

@maxmitz could you post a code example to replicate this issue? It should always work. If it doesn’t work, than there is something wrong before creating the cookie.

Even if it will always work if it will never pass the swift lint, the force unwrap should never be used, this is why swift has guard statement and if let statement.

@all-contributors please add @maxmitz for code


If this was meant to just be temporary for debugging, we should probably remove it as not to add unnecessary complexity to our class.

If this was meant to just be temporary for debugging, we should probably remove it as not to add unnecessary complexity to our class.
Originally posted by @Brennan1994 in https://github.com/HydrologicEngineeringCenter/fda-model/pull/288#discussion_r907798611

I hear you. I think @Brennan1994 referred to the property I added to help me debug - which probably shouldn't live on in the code.


I experienced some performance issued and started to measure latency, reproducing something similar to my setup in this demonstrator project https://github.com/MOOM-Planet/graphql-mesh-perf-example.
As you can see there, GraphQL mesh is caching almost all backend responses, the test query triggers one call to the backend server. This backend endpoint is , around 1ms.
Using additional types and additional resolvers, GraphQL Mesh adds 1300 fields to each backend response, all these fields are populated from cache.
I measured GraphQL Mesh latency around 308ms with the same workload applied to the backend.
In my application context, with more data and deployed on real servers, latency is a problem.
Is there any tweaks I can apply to squeeze some performance improvements, or is it unrealistic to expect faster results for this use-case ?
I attached the cpu profile of an other run.
CPU-20210204T174104.cpuprofile.gz
Thanks, Thomas

@trecloux Thank you for reporting the issue!
Does the latency decrease if you remove images from the selection set?

Thanks for the quick reply ;-)
When I remove images from the selection set, 75% percentile latency is around 90ms.
It also removes 1000 of the 1300 computed fields.

Closing this issue for now. Please let us know if you have new results with the latest versions.


Using the Auth Middleware

Hello, congratulations on your work. Do you have any suggestions for a more up-to-date package for using GraphQL with AdonisJS 6? Alternatively, could you help me understand how to use the auth middleware with your package?

Hell Leandro, thanks for your support.

Do you have any suggestions for a more up-to-date package for using GraphQL with AdonisJS 6?

You can check out https://friendsofadonis.com/docs  they also have implementation for GraphQL with AdonisJS 6

Could you help me understand how to use the auth middleware with your package?

Can you share you use case so I can understand how I can help you?


Creating a TypeScript app with --typescript option does not work

Is this a bug report?
Yes

Did you try recovering your dependencies?

N/A
Which terms did you search for in User Guide?

TypeScript
Environment

Environment Info:
System:
OS: macOS Sierra 10.12.6
CPU: x64 Intel(R) Core(TM) i7-4850HQ CPU @ 2.30GHz
Binaries:
Node: 11.2.0 - /usr/local/bin/node
Yarn: 1.12.3 - /usr/local/bin/yarn
npm: 6.4.1 - /usr/local/bin/npm
Browsers:
Chrome: 70.0.3538.102
Firefox: 60.0.2
Safari: 12.0.1
npmPackages:
react: ^16.6.3 => 16.6.3
react-dom: ^16.6.3 => 16.6.3
react-scripts: 2.1.1 => 2.1.1
npmGlobalPackages:
create-react-app: Not Found
Steps to Reproduce

(Write your steps here:)

npx create-react-app my-app --typescript

Expected Behavior

A TypeScript app is created with .tsx files
Actual Behavior

An ES6 app is created with .js files
Reproducible Demo

N/A

Your local/system create-react-app "binary" is must be quite old (v1.x). Try to update it to the latest version npm install --global create-react-app.

Hi! Please run npx create-react-app --version, make sure it's at least 2.1.
If not, run npm i -g create-react-app like @miraage mentioned.
After doing this, it will work as expected.

Thanks @miraage & @brunolemos. Turns out that I did not have create-react-app installed in global. Somehow I thought that it was not required when using npx. As soon as I installed it, I was able to create a typescript app.
Thanks for your help.

@nareshbhatia it's not required, but sometimes it ends up using an existing version on your machine instead of the newest one

Ah, I see. Thanks for clarifying, @brunolemos.


Mafia: Add information about roles and themes.

Will run the tests I promised to run later.

Passes my tests, will make the modifications requested soon so this and other mafia PRs can progress.


BinarySearch in Rust

@laci84 You must changed the README.md for the Rust implementation.  But first update your README.md then change it. Otherwise you get merge conflicts.


Update logback-classic, logback-core to 1.4.7

About this PR
📦 Updates

ch.qos.logback:logback-classic
ch.qos.logback:logback-core

from 1.4.6 to 1.4.7
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "ch.qos.logback" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "ch.qos.logback" }
}]

labels: test-library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #103.


enable config a ready cluster

reduce unnecessary test
add support and test for config a ready cluster for config Equinix k8s cluster.

merge as it is, for Equinix testing.


Add events for mouse/touch move

It would be good if there is an event for mouse/touch move.
Possible usecase: print/display current yaw/pitch/hfov values when it changed

There's nothing stopping you from adding mousemove and touchmove event listeners to the <div> you initialize Pannellum with, using the normal mechanism (addEventListener). Thus, adding these events to Pannellum is redundant.
As for your possible use case, this PR doesn't handle other input methods such as keyboard inputs. This more general type of event to handle view changes is discussed in #310, but I have some reservations about it related to rate limiting.
Thanks for the attempt, but I'm closing this PR as it only provides redundant functionality and doesn't address the nuances of a more general view change event.


How to add a command to the CommandRegistry from a plugin?

I'm trying to build the autocomplete functionality in iTerm into hyperterm. It's not clear to me how to get access to the command registry to register my own commands so that others will be able to bind my autocomplete action to whatever they'd like.
I ended up usinng decorateTerms to get a ref to the terms object, which ought to have registerCommands available as a property (https://github.com/zeit/hyper/blob/canary/lib/components/terms.js#L19). When I inspect the constructor of the terms object being passed to ref, I get an instance of the exposeDecorators constructor, which doesn't have the commandregistry accessible.
I'm going to have to hardcode my trigger for now until I get some guidance on how to add commands to hyperterm through a plugin.
Any suggestions?

@tastycode We wrote a non yet published documentation about writing plugins.: https://github.com/zeit/hyper/blob/plugin-doc/PLUGINS.md#keymaps
Please give us your feedback about it. Is it clear? Is there some points to develop?
Thank you in advance. 🙏

It wasn't immediately apparent what this.terms was being invoked in the context of. I'm assuming that's from something like
exports.decorateTerms = ( Terms, { React } ) => {
   return class extends React.Component {
     componentDidMount() {
         // i have access to this.terms here from the ref call in the passed HOC
      }

      render() {
         return <Terms ref={terms => this.terms = terms } {...this.props}/>
      }
   }
}

Thanks for the notes about the keybindings, that'll definitely be helpful. Though, I remember trying the above and not seeing a registerCommands available on the terms. It seemed i was getting an "exposeDecorator" terms instead.
In other news, I noticed this tidbit later in the page
Hyper v2 uses xterm.js instead of hterm. It means that PTY ouput renders now in a canvas not with a hackable DOM structure. For example, plugins can't use TermCSS anymore in order to modify text or links style. It is now required to use only available configuration params that will be passed down to xterm.js.

I had a ton of trouble finding any sort of a cannonical state anywhere that would tell me exactly what's on the screen. It seemed that hterm was dispatching SESSION_PTY_DATA and SESSION_ADD_DATA events through redux and those ended up getting passed to write or onData calls on the hterm instance. E.g. If I typed test. I would get a redux action for t e s then t. Nowhere in the session, or ui state tree could I find what I had just typed.
Since I'm working on autocomplete, I need to be able to index all the text on the screen. So I resorted to this gruesome hack.
exports.reduceSessions = (state, action) => {
  if (action.type === 'SESSION_PTY_DATA') {
    const hypercompleteStatePrev = state.hypercompleteState || {
      lines: []
    }
    const prevLines = hypercompleteStatePrev.lines
    const frameDocument = document.querySelector('iframe').contentWindow.document
    const currentLines = [...frameDocument.querySelectorAll('x-row')].map( row => row.innerText )
    const nextLines = R.takeLast(LINE_LIMIT)(R.uniq([prevLines, ...currentLines]))

    return state.set('hypercompleteState', {
      lines: nextLines
    })
  }
  return state
}

Will there be a better way to get access to all the text on the current term in 2.0?

@tastycode  For input recording, you can have a look at hyper-history or my refactored implementation.
But I don't know how to execute a command after you have made some autocomplete.


WithInitialKubernetesContainers missing enrichment

Current situation
Using WithInitialKubernetesContainers gets all the containers from the api server but doesn't enrich them with runtime metadata.
Impact
Forces using WithContainerRuntimeEnrichment in order to list the initial containers.
Ideal future situation
Adding enrichment.
Implementation options
[ Optional: please provide one or more options for implementing the feature requested ]
Additional information
[ Please Add any information that does not fit into any of the above sections here ]

Hi @amitschendel, that's the expected behaviour. Enriching containers with runtime metadata implies additional calls to the runtime for each container, thus it's not done by default but only if requested.

This requires the user to implement the logic of figuring the container runtime and then doing the enrichment. I would expect ig to have this logic built in.

You can initialize WithMultipleContainerRuntimesEnrichment(rc) with all the runtimes:
    rc := []*containerutilsTypes.RuntimeConfig{
	    {Name: "docker"},
	    {Name: "containerd"},
	    {Name: "crio"},
    }

And IG will find the proper runtime for each container and enrich it with the runtime metadata.


Upgrading using windows installer can take a very long time

Encountered this when installing 0.15 on top of 0.13.2. If an old installation is detected, it will attempt to migrate data files from old location in the source directory to the .kalite directory -- but this takes a really long time. I suspect it's due to the huge number of assessment item files. I have two ideas:

Give some feedback during the process, by showing the cmd.exe window handling this process instead of suppressing it. This creates the possibility that a user might prematurely terminate that process, though, which could result in unrecoverable data loss.
It's probably unnecessary to copy assessment item files, so the process could be tweaked to be more selective.

Setting 0.16.0 milestone -- this is annoying but IMO not a release blocker since core functionality works.

Suspicion confirmed -- assessment items (among other files) are first copied to a temp location, then later to a user's .kalite directory. This can be improved.


TypeError on GET request after updating to 2.4.0

Hi, I'm getting a type error for all requests after updating to 2.4.0.
I'm using format=modules and TypeScript. I'm firing the request with postman and it works fine if I downgrade to 2.3.0.
I'll add the error and my basic setup below.
[mf:err] GET /api/pricing/v2: TypeError: Failed to parse URL from [object Object]
    at new Request (/Users/dan/work/pricing-v2/node_modules/undici/lib/fetch/request.js:83:23)
    at new Request (/Users/dan/work/pricing-v2/node_modules/miniflare/node_modules/@miniflare/core/src/standards/http.ts:407:13)
    at EventTarget.dispatchFetch (/Users/dan/work/pricing-v2/node_modules/miniflare/node_modules/@miniflare/core/src/index.ts:1014:51)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Server.<anonymous> (/Users/dan/work/pricing-v2/node_modules/@miniflare/http-server/src/index.ts:168:20)
[mf:err] Cause: TypeError: Invalid URL
    at new NodeError (node:internal/errors:371:5)
    at onParseError (node:internal/url:552:9)
    at new URL (node:internal/url:628:5)
    at new Request (/Users/dan/work/pricing-v2/node_modules/undici/lib/fetch/request.js:81:21)
    at new Request (/Users/dan/work/pricing-v2/node_modules/miniflare/node_modules/@miniflare/core/src/standards/http.ts:407:13)
    at EventTarget.dispatchFetch (/Users/dan/work/pricing-v2/node_modules/miniflare/node_modules/@miniflare/core/src/index.ts:1014:51)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at Server.<anonymous> (/Users/dan/work/pricing-v2/node_modules/@miniflare/http-server/src/index.ts:168:20)
GET /api/pricing/v2 500 Internal Server Error (134.37ms)

My setup for modules format built by following the documentation:
Index.ts
import { handleRequest } from "./handleRequest";

const worker: ExportedHandler<Bindings> = { fetch: handleRequest };
export default worker;

handleRequest.ts
import { router } from "./router";
declare global {
  var env: Bindings;
  var host: string | null
}

export async function handleRequest(request: Request, env: Bindings) {
  globalThis.env = env;
  globalThis.host = request.headers.get("host")
  return await router.handle(request, env);
}

Let me know if you need more info to investigate this.
Thanks

No OP, but I'm using yarn 3 and had the same issue. I'm not using yarn in PNP mode, but I did have two different versions of miniflare installed (you can list them with yarn why miniflare). The solution was to yell Yarn to force only a single version of this module by adding this to package.json -
  "resolutions": {
    "miniflare": "^2.4.0"
  },

The root issue is having multiple versions of miniflare. For example, the latest released version of wrangler2 pins the dependency<EMAIL_ADDRESS>(https://github.com/cloudflare/wrangler2/blob/754f6c677d93ca9321c3264964ae6c144ef88393/packages/wrangler/package.json#L40) , but I also use jest-environment-miniflare which pins it at miniflare@2.4.0(https://github.com/cloudflare/miniflare/blob/6c26e320611f5209ba928cb5fba0013b8d4f2a20/packages/jest-environment-miniflare/package.json#L48) . Both require an exact version, so yarn installs both versions, but for miniflare there must be only one version to work.


Fail Test Case 5_2

All my other test case has passed but I am still failing this test case. Anyone can help point out what is wrong?

You might want to check whether you lazily evaluate the entire expression or do some sort of half-evaluation when doing .op() with an Expr<T>. The former is the correct way to do it.


Add Remix gitignore

Pull Request
Thank you for contributing to @toptal/gitignore and https://www.gitignore.io.
New or update
Select the appropriate check box for this pull request. This helps when merging to ensure there are no conflicts with other templates or misunderstandings of how thee template list works.
New

[x] Template - New .gitignore template
[ ] Composition - Template made from smaller templates
[ ] Inheritance - Template similar to an existing template
[ ] Patch - Template extending functionality of existing template

Update

[ ] Template - Update existing .gitignore template

Details
Create .gitignore template for Remix.run
This file is based on the templates from remix^1. I Just added all of them to one file and removed all dupes.

Good point, I didn't thought of that.
Instead of removing them completely, I would suggest to either:

uncomment it and leave a notice like Uncomment the following line if you use Arc (and the same for the others).

or

create a separate file that builds on top the base Remix gitignore (e.g. Remix-Arc.gitignore, etc)

What do you think about that?

Updated. I hope I did everything right.


Error: errorMissingInputUtxos

Describe the bug
When I attempt to create a valid transactions containing valid input UTXO's, I get an error after signing the transactions saying that I'm missing input UTXOs
To Reproduce
Here is my code:

I call the functions using

Expected behavior
A transaction should be signed
Screenshots

Additional context
Add any other context about the problem here.

Keep in mind that the UTXOs do exist. In fact, when I print input, I get this which is correct. As you can see, there is a perfect input UTXO in there

I don't see obvious reason for the error.  One possible reason can be filtering out dust transactions.  Though with the low byteFee=2 value that is unlikely.
There are many edge case tests in these files:

https://github.com/trustwallet/wallet-core/blob/master/tests/Bitcoin/TransactionPlanTests.cpp
https://github.com/trustwallet/wallet-core/blob/master/tests/Bitcoin/TWBitcoinSigningTests.cpp
Look for cases with Error_missing_input_utxos, maybe that gives you an idea.

I found the issue. For some reason - when I use a legacy address it doesn’t work
When I use a segwit address, it does
Srikanth

From: Adam R @.>
Sent: Monday, June 28, 2021 10:40:54 AM
To: trustwallet/wallet-core @.>
Cc: Srikanth Srinivas @.>; Author @.>
Subject: Re: [trustwallet/wallet-core] Error: errorMissingInputUtxos (#1478)
EXTERNAL EMAIL:
I don't see obvious reason for the error. One possible reason can be filtering out dust transactions. Though with the low byteFee=2 value that is unlikely.
There are many edge case tests in these files:

https://github.com/trustwallet/wallet-core/blob/master/tests/Bitcoin/TransactionPlanTests.cpp
https://github.com/trustwallet/wallet-core/blob/master/tests/Bitcoin/TWBitcoinSigningTests.cpp
Look for cases with Error_missing_input_utxos, maybe that gives you an idea.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/trustwallet/wallet-core/issues/1478#issuecomment-869743200, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGB2H5TGUCVT3I7HURPXBMTTVCCXNANCNFSM47M2VBLA.

what's your wallet core version? could you please try latest? we have a fix for legacy address: https://github.com/trustwallet/wallet-core/pull/1433

Most recent version. I am using testnet addresses like: mjvSp3PweYBqmqpAZxpYZUR3L3sANeyzTz

We don’t support testnet addresses

That's weird because when I use testnet witness addresses, it works.


'Unexpected token, expected ","' while parsing typescript 4.5.x+ preserveValueImports setting

The latest Svelte, SvelteKit and VSCode language-tools will auto-import Typescript types and values in a mixed single line statement:
import { getTest, type Test } from "$lib/test";

This will cause an error during Houdini preprocessing and runtime generation - Encountered error parsing path/to/some/Component.svelte: Unexpected token, expected ",".
Avoiding the error requires enabling the preserveValueImports option for Typescript - https://www.typescriptlang.org/tsconfig#preserveValueImports - which is enabled in the latest auto-generated SvelteKit tsconfig.
However, Houdini package.json has a dependency resolution that pins the version to 3.9.5. It needs to at 4.5.0+ in order for the preseveValueImports option to be recognized. https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-5.html#disabling-import-elision
I can submit a PR that updates the example to the latest SvelteKit and changes the typescript version resolution. The tests are passing. But I wonder why it was pinned to 3.9.5 in the first place?
Thanks for this awesome project! Happy to see all the continued development that is happening here.
Example project to produce. The kit folder has no errors, then I copied that folder to kit-with-houdini and used npx houdini init and then hit the error. https://github.com/rmarscher/sveltekit-houdini-typescript

I'm testing a potential solution on a fork over here - https://github.com/rmarscher/houdini/tree/typescript-4

I updated the typescript resolution to 4.6.3 in my fork. I also had to fork ts-ast-serializer to relax it's peerDependency of typescript.
I still receive the error in my repro repo when using the build cmd.js though. I though the typescript upgrade would have fixed it unless there is another configuration that needs to be set when houdini parses typescript outside of the local tsconfig.json.


Query: q=config

Check for

media endpoint (must be full URL)
syndication targets
proper response if no settings

Done in 02a9ee656f3fc7e7f9334bec2b0d14bec51d3a24


Inconsistent query execution plan

Running 3.2.9, single-server on Ubuntu 16.04.
Following the recommendation given in #3984, I've created an extra index in our pre-production database to confirm that it would speed up one of our slow queries. As the result was positive, I've created the very same index in our production database, but after a while I noticed that those queries were still slow. So I've compared the execution plans for the very same query between pre-production and production, and it appears that the new index is not used in production.
Pre-production:
Query string:
 WITH users
 FOR s IN shares FILTER 'hasPublished/5566497733' IN s.publications[*].id
 LET user = DOCUMENT(users, s.targetKey)
 LET follows = FIRST(FOR f IN follows FILTER f._from == ('users/' + s.targetKey) && f._to ==
 'users/$keakr' LIMIT 1 RETURN f)
 RETURN { share: s, follows: follows, user: user }

Execution plan:
 Id   NodeType          Est.   Comment
  1   SingletonNode        1   * ROOT
 16   IndexNode          455     - FOR s IN shares   /* hash index scan */
  5   CalculationNode    455       - LET user = DOCUMENT(users   /* all collection documents */, s.`targetKey`)   /* simple expression */   /* collections used: s : shares */
 12   SubqueryNode       455       - LET #5 = ...   /* subquery */
  6   SingletonNode        1         * ROOT
 17   IndexNode            1           - FOR f IN follows   /* hash index scan */
 10   LimitNode            1             - LIMIT 0, 1
 11   ReturnNode           1             - RETURN f
 14   CalculationNode    455       - LET #12 = { "share" : s, "follows" : FIRST(#5), "user" : user }   /* simple expression */   /* collections used: s : shares */
 15   ReturnNode         455       - RETURN #12

Indexes used:
 By   Type   Collection   Unique   Sparse   Selectivity   Fields                     Ranges
 16   hash   shares       false    false         0.22 %   [ `publications[*].id` ]   ("hasPublished/5566497733" in s.`publications`[*].`id`)
 17   hash   follows      true     false       100.00 %   [ `_from`, `_to` ]         ((f.`_from` == ("users/" + s.`targetKey`)) && (f.`_to` == "users/$keakr"))

Optimization rules applied:
 Id   RuleName
  1   remove-unnecessary-calculations
  2   use-indexes
  3   remove-filter-covered-by-index
  4   remove-unnecessary-calculations-2

Production:
Query string:
 WITH users
 FOR s IN shares FILTER 'hasPublished/5566497733' IN s.publications[*].id
 LET user = DOCUMENT(users, s.targetKey)
 LET follows = FIRST(FOR f IN follows FILTER f._from == ('users/' + s.targetKey) && f._to ==
 'users/$keakr' LIMIT 1 RETURN f)
 RETURN { share: s, follows: follows, user: user }

Execution plan:
 Id   NodeType          Est.   Comment
  1   SingletonNode        1   * ROOT
 16   IndexNode            6     - FOR s IN shares   /* hash index scan */
  5   CalculationNode      6       - LET user = DOCUMENT(users   /* all collection documents */, s.`targetKey`)   /* simple expression */   /* collections used: s : shares */
 12   SubqueryNode         6       - LET #5 = ...   /* subquery */
  6   SingletonNode        1         * ROOT
 17   IndexNode            1           - FOR f IN follows   /* edge index scan */
 18   CalculationNode      1             - LET #10 = (f.`_from` == ("users/" + s.`targetKey`))   /* simple expression */   /* collections used: f : follows, s : shares */
  9   FilterNode           1             - FILTER #10
 10   LimitNode            1             - LIMIT 0, 1
 11   ReturnNode           1             - RETURN f
 14   CalculationNode      6       - LET #12 = { "share" : s, "follows" : FIRST(#5), "user" : user }   /* simple expression */   /* collections used: s : shares */
 15   ReturnNode           6       - RETURN #12

Indexes used:
 By   Type   Collection   Unique   Sparse   Selectivity   Fields                     Ranges
 16   hash   shares       false    false        16.33 %   [ `publications[*].id` ]   ("hasPublished/5566497733" in s.`publications`[*].`id`)
 17   edge   follows      false    false        57.58 %   [ `_to` ]                  (f.`_to` == "users/$keakr")

Optimization rules applied:
 Id   RuleName
  1   remove-unnecessary-calculations
  2   use-indexes
  3   remove-filter-covered-by-index
  4   remove-unnecessary-calculations-2

And here are the indexes as reported by arangosh.
Pre-production:
<IP_ADDRESS>:8529@preprod> db.follows.getIndexes()
[
  {
    "fields" : [
      "_key"
    ],
    "id" : "follows/0",
    "selectivityEstimate" : 1,
    "sparse" : false,
    "type" : "primary",
    "unique" : true
  },
  {
    "fields" : [
      "_from",
      "_to"
    ],
    "id" : "follows/2",
    "selectivityEstimate" : 0.10864767128986907,
    "sparse" : false,
    "type" : "edge",
    "unique" : false
  },
  {
    "deduplicate" : false,
    "fields" : [
      "_from",
      "_to"
    ],
    "id" : "follows/593046825872",
    "selectivityEstimate" : 1,
    "sparse" : false,
    "type" : "hash",
    "unique" : true
  }
]

Production:
<IP_ADDRESS>:8529@keakr> db.follows.getIndexes()
[
  {
    "fields" : [
      "_key"
    ],
    "id" : "follows/0",
    "selectivityEstimate" : 1,
    "sparse" : false,
    "type" : "primary",
    "unique" : true
  },
  {
    "fields" : [
      "_from",
      "_to"
    ],
    "id" : "follows/2",
    "selectivityEstimate" : 0.30785300014004596,
    "sparse" : false,
    "type" : "edge",
    "unique" : false
  },
  {
    "deduplicate" : false,
    "fields" : [
      "_from",
      "_to"
    ],
    "id" : "follows/5577262147",
    "selectivityEstimate" : 1,
    "sparse" : false,
    "type" : "hash",
    "unique" : true
  }
]

Seems like the better selectivityEstimate leads to the production db using the wrong index.
Are you actually using follows in traversals? Maybe you could just create it as a normal document collection

But the hash index has a much better selectivity (1) than then edge index (0.3) so it should pick this one in my opinion. Yes we're using the follows edge collection for traversals.

Hi,
Thanks again for opening this ticket. Version 3.2.10 has been released yesterday
I am now closing this ticket. Please feel free to comment if the problem persists
Many thanks,


GO:0031002 definition too strict?

The definition mentions presence in Dicty, but it sounds general and definitely has more general child terms.  Change definition?

Agreed. Broadened definition and added PMIDs as def dbxrefs.


Avoid StackOverflowException when Kafka.poll() 'timeout' param is 0

implement fetchBatch() as a loop when kafka.poll is not large enough interval for data to reach kafkaClient from kafkaServer

I am merging this, thanks again for this @mariobriggs
I can take care of the follow-up but do let me know if you disagree.


ionic2 -  sometimes simulates two clicks?

Short description of the problem:
When using multiple ion-toggles, which are conditionally shown using ngIf, the next item in a list in sometimes clicked when one if the ion-toggles is hidden. This is better explained with the plunker given below.
Note: This only happens SOME of the time. It's quite random. I'll switch the toggles a couple of times and it will work fine, but then after a bit it'll start clicking things where the hidden toggle used to be
What behavior are you expecting?
I expect clicking something to not generate two clicks, or at least click-block should block the second click.
Other information: (e.g. stacktraces, related issues, suggestions how to fix, stackoverflow links, forum links, etc)
Environment: Chrome w/ ionic serve
Could it have something to do with click-block not being activated? Even so, I don't think there should be any reason to have two clicks fire.
Which Ionic Version? 2.x beta.7
Plunker that shows an example of your issue
Note: This plunker is set up the exact same way as my own personal code, but I could not get it to reproduce the bug for whatever reason
https://plnkr.co/edit/FNUxp4LFDvYAL2YwijUq?p=preview
Run ionic info from terminal/cmd prompt: (paste output below)
Cordova CLI: 6.0.0
Gulp version:  CLI version 3.9.1
Gulp local:   Local version 3.9.1
Ionic Framework Version: 2.0.0-beta.7
Ionic CLI Version: 2.0.0-beta.25
Ionic App Lib Version: 2.0.0-beta.15
ios-deploy version: 1.8.4
ios-sim version: 5.0.6
OS: Mac OS X El Capitan
Node Version: v4.4.4
Xcode version: Xcode 7.3 Build version 7D175

Hello, thanks for opening an issue with us! Would you mind trying this on your device with a fresh starter project and seeing if you get the same issue? I have been using toggles over the past couple of days and have not seen anything like this. Thanks for using Ionic!

Sure thing. I'll try that out and get back to you

Thanks!

Hello! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!

Hi @jgw96 ! I am still seeing this issue. What happens is: if a toggle is clicked, and then UI elements are displayed above that toggle (such as an ion-select) which push the toggle down, then another click will happen where the toggle used to be. The result: the select's alert will open.
Here is a demo repo: https://github.com/zakton5/ionic2-toggle-click-bug


Make a Release

Our last Zipline release was 1.3 and released on Jul 17, 2018. That is quite a long time ago but we are definitely planning on releasing a new version of the project. There are a few issues that we're actively working on and are planning to address before we do so.

@ssanderson

A couple issues that we'd probably like to address before releasing:

[ ] https://github.com/quantopian/zipline/issues/2627
[ ] https://github.com/quantopian/zipline/issues/2616
[ ] We're in the process of trying to migrate a bunch of our packaging infrastructure to conda forge. See notes in https://github.com/quantopian/zipline/issues/2637.

Are there other important issues that should block releasing a new version?

@ssanderson
Would it as well include a possibility to use fundamental data?
There are some ideas already on this GitHub.

@carstenf I'm not sure what it would look like for Zipline to support fundamental data in a first class way.
On Quantopian we support two fundamental data providers, Morningstar and FactSet, but their data structure (and even what they count as "fundamental" data) is quite different. It's not clear to me how we could allow Zipline to support general fundamental data in a way that wouldn't be tied relatively tightly to a specific (and likely non-free) vendor's data.

@ssanderson
I agree, it would not a plug-and-solution, but the same is true with your regular ingest process. If one wants to use a different data provider, one needs to change the code slightly.
If found two solution were you could start, and just maybe, add a example how to use Quandl data. The examples uses this as well.
(Morningstar and FactSet might be a bit expensive for starting...)
I could use these, but maybe after one of your updates, things will not work.
It would be better using something which is supported by zipline.
Thanks
Carsten
Examples:
http://alphacompiler.com/blog/6/
https://github.com/calmitchell617/Springbok

Does anyone have example or know how to make a Pipeline locally on Zipline?

@ssanderson perhaps not fundamental data specifically, but if you could add a utility or documentation on incorporating general data into a DataSet to be used by factors and pipelines that would be incredibly helpful.
Currently it's pretty easy to add custom pricing data for running backtests by adding somthing like this in extensions:
register(
    'new_bundle',
    csvdir_equities(
        ['daily'],
        '/path',
    ),
    calendar_name=name
    start_session=start_session,
    end_session=end_session
)

then running: zipline ingest
I'm not entirely sure what the APIs would look like but would it be possible to mirror this type behavior for loading arbitrary csv data to be used as datasets in factors and pipelines. perhaps something like this could also go in the extensions file:
class FundamentalData(DataSet):
    price_to_earnings = Column(float64_dtype)
    price_to_book = Column(float64_dtype)
    ...

register_dataset(
    FundamentalData,
    csvdir_equities(
        ['daily'],
        '/path/',
    ),
    # maybe just explicitly map the names of the columns in the csv to the Column names
    # defined in the DataSet in case they differ
    columns={
        'price_to_earnings': 'price_to_earnings',
        'price_to_book': 'price_to_book',
        ...
    }
)

You might then need to run a similar ingest type command or zipline could just read the extension and then load the data dynamically from the csv file at backtest runtime.
is something like this possible? or does functionality like this already exist?
@cemal95 have you looked here: https://github.com/quantopian/zipline/blob/master/zipline/examples/momentum_pipeline.py

#2434
the hard coded NYSE in data bundle. if there could be a fix, or a new document to address this would be great

While I would appreciate the fundamental data enhancement, genuinely would be good to get a new stable release out of whatever features are currently done, ASAP, with the focus being on bugs and supporting newer versions of pandas/etc. I have used zipline in-house for 18 months or so, but are exploring other options now as the number of workarounds and issues we are having is growing, and while supposedly supported by Quantopian, the lack of releases in almost 2 years doesn't fill us with confidence any more.
(We ingest our own price data from an external (paid for) provider - writing the custom data bundle in general works fine, apart from performance issues. We have a separate database of PiT fundamentals and just look that up when needed for the given backtest day. Don't use any of the factor stuff yet, mainly as can't load in custom data for creating them).

It's difficult to tell whether there will be much more development going on.  I sure hope so.
There are still many new people trying Zipline and running into significant roadblocks due to the 1.3.0 release having issues that have been resolved in the latest code.  You can see the new issues coming in.
However, the majority of employees were furloughed in late April and others in May (including Scott Sanderson who appears to be leading the commits):
https://permadeath.com/Moving-on-from-Quantopian/
https://www.partiallyapplied.com/blog/moving-on/
It's a pity because there were a bunch of commits and really good work done in April.
It would be nice to get an opinion from any current or ex-Quantopians of:

"where things are realistically currently at" with regards to a release of Zipline.  Please tell us how it is (and if you want to do it anonymously or via a third party that's fine too).
Likelihood of Quantopian issuing a new release in the next few months

Of course, open source has a way of working through such difficulties through forks and/or project ownership transfer,, but the folks at Quantopian have done so much good work to date it'd be great to hear from them.

However, the majority of employees were furloughed in late April and others in May (including Scott Sanderson who appears to be leading the commits):

I did not realise that had happened, obviously hope people who have been impacted are OK, and hope to get an update from Quantopian people when they can on the impact on zipline.

fundamental support +1

Hi all,
As mentioned above, Quantopian is a much smaller team now, though we hope to continue making (slower) progress.
Our first goal is to cut a zipline 1.4.0 release that includes the benchmark/treasury curve downloading improvements, python 3.6 CI/packages, and all the international tooling - basically everything from the past 2 years (changelog and highlights in progress).
Our next goal is for a subsequent release that improves the packaging/installation situation, including moving to conda-forge and supporting newer pythons.
I believe the benchmark downloading and packaging issues are the two biggest, based on the discussions here in GitHub, and improving our packaging/CI will also speed up our ability to fix/test/confirm issues and pull in PRs.

Released https://github.com/quantopian/zipline/releases/tag/1.4.0


ddl: Fix exchange partition impl

What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tiflash/issues/8378
Problem Summary:

TableIDMap::emplaceTableID/TableIDMap::emplacePartitionTableID should check whether the old value is the same as new value before logging a warning message. Or there could be too many meanless warning logging.
When executing exchange partition, "renaming old non-partition table belonging new database" fail should not affect "renaming the exchanged partition table belonging new database"
The nesting if ... else ... in applySetTiFlashReplica is too deep and hard to read
Executing exchange partition in table id mapping is not atomic, this may make other functions get something wrong
https://github.com/pingcap/tiflash/blob/1addc37a549f23310bbe36f5bc75853bd6508ffd/dbms/src/TiDB/Schema/SchemaBuilder.cpp#L128-L131

What is changed and how it works?

Add some test case to master branch from https://github.com/pingcap/tiflash/issues/8372
Make exchange partition to be an atomic function TableIDMap::exchangeTablePartition
TableIDMap::emplaceTableID/TableIDMap::emplacePartitionTableID check whether the old value is the same as new value before logging a warning message
Use do ... while ... break to make "renaming old non-partition table belonging new database" fail not affect "renaming the exchanged partition table belonging new database"
Adding return to simplify applySetTiFlashReplica

Check List
Tests

[ ] Unit test
[x] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/hold

[2023-11-20T03:00:29.762Z] fullstack-test2/ddl/alter_exchange_partition.test: Running
[2023-11-20T03:00:37.839Z]   File: fullstack-test2/ddl/alter_exchange_partition.test
[2023-11-20T03:00:37.840Z]   Error line: 49
[2023-11-20T03:00:37.840Z]   Error: set session tidb_isolation_read_engines='tiflash'; select * from test.e order by id;
[2023-11-20T03:00:37.840Z]   Result:
[2023-11-20T03:00:37.840Z]     ERROR 1105 (HY000) at line 1: other error for mpp stream: Code: 0, e.displayText() = DB::TiFlashException: The schema does not match the query, details: the column in the query is not found in current columns, keyspace=4294967295 table_id=593 column_id=4, e.what() = DB::TiFlashException,
[2023-11-20T03:00:37.840Z]   Expected:
[2023-11-20T03:00:37.840Z]     +-----+-------+-------+------+
[2023-11-20T03:00:37.840Z]     | id  | fname | lname | c1   |
[2023-11-20T03:00:37.840Z]     +-----+-------+-------+------+
[2023-11-20T03:00:37.840Z]     |   2 | a     | b     | NULL |
[2023-11-20T03:00:37.840Z]     | 108 | a     | b     | NULL |
[2023-11-20T03:00:37.840Z]     +-----+-------+-------+------+

/run-all-tests

/unhold

/build

/hold

/run-all-tests

/run-all-tests

replace by https://github.com/pingcap/tiflash/pull/8421 and https://github.com/pingcap/tiflash/pull/8422


Remove dpp and delta optimize write configs since now supported

Remove setting these confs to false since we now support them.

build


Masked Patch Prediction "Suggested in #63" Work in Progress

Implementation of masked patch prediction for self-supervised learning.

@zankner Hi Zack! Thanks for the PR! Left you some comments - I think the PR may require some back and forth still, but I'd like to see it added. One question I have is, this leaves the generation of the random masks up to the user?

@zankner Hi Zack! Thanks for the PR! Left you some comments - I think the PR may require some back and forth. One question I have is, this leaves the generation of the random masks up to the user?

@zankner Is your code aimed at the implementation where the masked tokens predict the mean pixel value?

@zankner Hi Zack! Thanks for the PR! Left you some comments - I think the PR may require some back and forth. One question I have is, this leaves the generation of the random masks up to the user?

As of right now it would but the PR still isn't finished yet. Just wanted to get the outline out to get your feedback on the direction.

@zankner Is your code aimed at the implementation where the masked tokens predict the mean pixel value?

Yeah exactly.

@zankner very cool! I'll show you two of my self-supervised repos i was planning on repurposing for ViT

masked language modeling - https://github.com/lucidrains/mlm-pytorch
electra - https://github.com/lucidrains/electra-pytorch

i think the wrapper technique would work well with ViT, and the masked token would belong as a parameter under that wrapper
anyways, i'll let you think about it some more, let me know if you ever want me to step in and finish it
btw, i'm borned and raised around Boston too :) I'm from Andover :)

@zankner very cool! I'll show you two of my self-supervised repos i was planning on repurposing for ViT

masked language modeling - https://github.com/lucidrains/mlm-pytorch
electra - https://github.com/lucidrains/electra-pytorch

i think the wrapper technique would work well with ViT, and the masked token would belong as a parameter under that wrapper
anyways, i'll let you think about it some more, let me know if you ever want me to step in and finish it
btw, i'm born and raised around Boston too :) I'm from Andover :)

@lucidrains Awesome! I'll give those repos a check. Yeah, the task is basically the same as masked language modeling so I'm sure whatever is there will be perfect.
That's awesome that your from Boston.  Still had to modify the forward call in vit module as the image has to be reshaped first in the forward pass of the wrapper. Reason being that the tokens are no longer just ids for embedding layer, but are instead patches of the image which affects the way that the mask token gets added to the input.
btw - do you have a preferred style guide for me to use with the code?

looking better, but I left some comments!
this could also benefit from a section in the readme eventually!

Yeah that makes a lot of sense about the readme

@lucidrains just pushed a change that fixes loss and leaves vit forward unchanged. Sorry to bother you with this question again, but is there any style guide you prefer like yapf or pep8?

@zankner looking better! i think remaining is really discretizing the RGB values to 512, and various cleanup and readme :)
hmm, I like my style the best :D perk of owning your own repos in a non-corporate environment ;)

@zankner just use whatever style you like (but leave the rest of the repository code unchanged)

@zankner looking better! i think remaining is really discretizing the RGB values to 512, and various cleanup and readme :)
hmm, I like my style the best :D perk of owning your own repos in a non-corporate environment ;)

@lucidrains I might be wrong but I think the discretizing RGB values is finished. I take the mean RGB over the entire patch, and then discretize each channel to 3 bits. So in the end there are 8 possible values per channel, meaning 512 possible total colors.

@lucidrains Hey, just wanted to check if there is anything you still need me to change?

@zankner Hi Zach! Sorry for the delay in response, had been busy
Could you point me in the paper where they show they are doing the binary cross entropy over the 8 bits of each token? I still think what they are doing is discretizing to 512 values for each token, and doing a direct cross entropy on that, but I could be wrong

@lucidrains by token are you referring to the whole patch of the image ?

@zankner yup, each token, representing a patch

@lucidrains I was mostly looking at section B.1.2 in the appendix. When they said "predicting only the mean,
3bit color (i.e., 1 prediction of 512 colors)" I took this to mean that for each pixel in the patch, you would discretize each channel to 3-bits. Across 3 channels this would lead to 512 possible colors per pixel. Then you would take the mean of the image patch, and that would serve as the target. The transformer would then try to predict this mean of the discretized values.
Still not completely convinced of this so I would be interested to hear your interpretation.

I think you can use something like https://stackoverflow.com/questions/55918468/convert-integer-to-pytorch-tensor-of-binary-bits to convert from binary to decimal, then treat that as a hard label to predict (512 values)

@lucidrains Oh ok yeah that makes a lot of sense. With respect to the mean, I should take the mean before I convert to binary right?

@zankner yup!

@lucidrains added the converting bin to decimal. If it looks good I can add a section to the read me

@zankner this looks good now! if you write up a section in the readme, happy to merge this in 💯 💯

@lucidrains Thanks a lot for all your help on this! If there is any other project you are working on that you would want my help with please let me know, would love to work on it!


issue with httpclient 2.7.1

signature of #create_socket has changed in httpclient between <IP_ADDRESS>
httpclient/session.rb:    def create_socket(site)
and 2.7.1
httpclient/session.rb:    def create_socket(host, port)
httplog is not compatible with the most up to date signature.

Thanks for reporting this - fixed, will release new version shortly.

v0.3.2 is available from rubygems.org.

great, works like a charm, thanks


Add "-open"

As there is the default folder "folder.svg" and "folder-open.svg" why not add others as well? Just a question

Purely because it is twice the amount of work anytime a new folder icon is added and it requires functionality to be updated to support both. I'll leave this issue open to track the interest.


Drop annotations support?

I just skimmed through the codebase of ZF2 and couldn't find scenarios where the "base" annotation parser of zend-code is used in it, except for zend-di. We could probably get rid of the entire Zend\Code\Annotation namespace.
While I realize that coming from me it sounds like I'm suggesting for people to just use doctrine/annotations, this part of the codebase really lies unused, and is a relatively complex layer that just proxies through to doctrine/annotations, in fact.
I propose deprecating it (probably 4.0) and dropping support for it in the subsequent major version. This allows us to also get rid of the zendframework/zend-eventmanager dependency inside zend-code.

@Ocramius why waiting a major version to deprecate it ? A deprecation can happen in a minor version (deprecating is not a BC break when done properly. The BC break would be the removal)

@stof 3.0 is gonna happen real soon ( zendframework/zend-code#29 ), and this sort of decision isn't something I can take on my own anyway.

@Ocramius I think we use Zend\Code\Annotation in zend-form as well; can you check?
In terms of deprecation, we could add the deprecation to the 3.0 release of zend-code, as far as I'm concerned.
Also, one question, what did you mean by this?

This allows us to also get rid of the zendframework/zend-eventmanager dependency inside ZF2.

That has never been proposed…

@weierophinney zendframework/zend-eventmanager is required only due to how the annotation manager works: removing annotation support means that no event manager is needed either

@Ocramius I think we use Zend\Code\Annotation in zend-form as well; can you check?

Yes, but by default it just uses doctrine annotations

The clarification is s/ZF2/zend-code/ in your original statement. :)
Regarding zend-form, we should make a note to drop support for Zend\Code\Annotation for the next major release of that component, which will make your suggestion possible.

@Ocramius @weierophinney what do you think about my previous question about making optional dependency with possible removing in the next major?

@lisachenko making the dependency optional is already a BC break, so I'd just go with a new major

making the dependency optional is already a BC break, so I'd just go with a new major

@Ocramius it's perfectly ok for me :+1:
Also PHP strict types are welcome for new major ) So, my huge vote to make this library de facto standard for code generation

Yeah, the library is way sub-standard compared to most other components, but can be improved with some spit & polish

@lisachenko I won't be able to continue on that for now, sorry.

Are there other maintainers? Maybe I will be able to spend some time on this library...

@lisachenko @zendframework/community-review-team is maintaining this. zend-code is relatively low maintenance, but we really do need to move forward with spring cleanups, so if you want to take over on that patch I can gladly help/review while commuting every day :-)

Unfortunately, @zendframework/community-review-team is private, so haven't idea how to ask members about possible changes. But your review and PR merging should be enough )
Let me check if I can help. I will propose list of todo and changes for 4.0 and link them with PR's

@lisachenko even just a patch removing annotations is sufficient for now - the other one can be rebased.

@Ocramius — We use the annotation support in the zend-server package, and thus each of its dependents (zend-json-server, zend-soap, zend-xmlrpc). Each of these needs some significant refactors at this time, though — but annotation support will still be required for any exposed methods with variant signatures. If there's a third-party package that provides that functionality, we can move to that; any suggestions would be quite welcome!
@lisachenko Team pages cannot be viewed publicly, even if the team is public. You can always mention the team in order to ping all members for review, however.

@weierophinney Maybe, switch for the next version to the doctrine/annotations library? It's already listed in require-dev section, thus installed during development process.

@lisachenko D'oh! We use that with forms already, so of course I should know that one! Yeah, that would work fine, and we can use that in the other packages as well.

@weierophinney ok, so, doctrine/annotations should be ok. But not sure, should it be included as direct dependency, because main responsibility of this library is to generate code and provide API for that.
In my opinion, parsing of annotations should be outside of this library's scope, so no getters for annotations are required.

@Ocramius — We use the annotation support in the zend-server package, and thus each of its dependents (zend-json-server, zend-soap, zend-xmlrpc). Each of these needs some significant refactors at this time, though — but annotation support will still be required for any exposed methods with variant signatures. If there's a third-party package that provides that functionality, we can move to that; any suggestions would be quite welcome!

@weierophinney this would be in a major version anyway, so the affected packages would need to bump the dependency anyway.
I think I told this in 2013 or so btw: let's not come up with further different annotation syntaxes. Getting rid of this alternate parser/syntax is a good thing (TM)

Handled in #153


Remove geometric operations: geojoin, @groupby, @combine and @transform

These operations have been moved to the GeoTables.jl package in the following PR: https://github.com/JuliaEarth/GeoTables.jl/pull/69

Codecov Report

Merging #173 (1c1b553) into master (8cca215) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #173      +/-   ##
==========================================
+ Coverage   96.16%   96.19%   +0.03%
==========================================
  Files          41       36       -5
  Lines         886      631     -255
==========================================
- Hits          852      607     -245
+ Misses         34       24      -10

Files
Coverage Δ

src/GeoStatsBase.jl
100.00% <ø> (ø)

src/geoops/utils.jl
100.00% <ø> (ø)


Add RecvBufferAllocator API for allocating Buffer instances

Motivation:
In order for transports to be able to read into new-api Buffers, we need the RecvBufferAllocator to be able to allocate such buffers.
Modification:
Add an allocate overload to RecvBufferAllocator.Handle that take a BufferAllocator and return a Buffer.
Update all implementing classes to support this new API, in addition to the existing ByteBuf API.
Result:
Our RecvBufferAllocator implementations can now allocate Buffers, in addition to ByteBufs.

Thanks a lot !


configtool: Add option to override Azure endpoint (PROJQUAY-891)

Allows overriding the Azure storage endpoint, as an example accountname.blob.core.usgovcloudapi.net.

lgtm


Incorrect configuration to enable DEBUG logs

Description:
The following configuration provided in the documentation [1] to enable DEBUG logs for the "APILogMessageHandler" component is incorrect.

The provided configurations are in accordance with the log4j logging format and that should be corrected to be in accordance with the log4j2 logging format.
Affected Product Version:
APIM-3.1.0
[1] https://apim.docs.wso2.com/en/latest/develop/extending-api-manager/extending-gateway/writing-custom-handlers/#using-apilogmessagehandler

@fazlan-nazeem , would you be able to provide input in this regard please.

Fixed in https://github.com/wso2/docs-apim/issues/1826. Duplicate issue.


CP-1002 update license text and karma-jspm dependency

Issue

outdated OSS license text
outdated karma-jspm dependency

Changes
Source:

docs only change

Tests:

no changes

Areas of Regression

karma-jspm test runs

Testing

CI is happy
test karma-jspm run on a consumer app

Code Review
@maxwellpeterson-wf
@evanweible-wf
@dustinlessard-wf
@jayudey-wf

+1

+1

+1

@jayudey-wf ready for merge

QA Resource Approval: +10

[ ] Testing instruction
[ ] Dev +1's
[ ] Dev/QA +10 with detail of what was tested
installed into a consumer app and verified that tests were able to be run as expected
[ ] Unit test created/updated
[ ] All unit tests pass

Merging into master.

rosie


Add vehicles

Connection with issue(s)
No open issue to add Vehicles. I needed it for a personal project and figured it was worth sharing.
Testing and Review Notes
Running unit tests should cover all cases

dartfmt run, newline added to the end of pubspec.yml

@kalebhermes Sorry, merged another PR before yours. Could you merge/rebase master into your branch? :pray:

@drager It's done!

@drager bump

Bump again ;)

Haha @kalebhermes! :smile: Sorry for being slow. Let's merge it! :tada:

🎉 🚢


Impossible to pass "false" as training input value

When I try to set crop_based_on_salience to false, I try:
replicate train stability-ai/sdxl<EMAIL_ADDRESS>resolution=128 crop_based_on_salience=false caption_prefix="pixelart sprites in the style of TOK, " --destination=andreasjansson/sdxl-pixelart-sprites
Training created: https://replicate.com/p/7tyxhvtboyeblkprtiulb6aeqm

The training doesn't actually include the crop_based_on_salience argument

@andreasjansson I spent a while chasing this down only to realize that the issue was in how training inputs are rendered on the website. If you do curl https://api.replicate.com/v1/predictions/7tyxhvtboyeblkprtiulb6aeqm | jq, you should see crop_based_on_salience set to false in the inputs for the training.

See also https://github.com/replicate/replicate-python/issues/140


elasticsearch 1.7.2

delete by query is now deprecated, recommendation is to use search-scan and bulk request, done.

spandex #397 SUCCESS
This pull request looks good

This build looks good.

:shipit:


fix(school-name): refactor the format school name so it doesnt live i…

…n generic listbox
Description
the formatSchoolName was being called in generic listbox component
so i have moved it further up to be called only by the schoolPicker
Issue(s)
Fixes #
How to test

Go to https://deploy-preview-2019--oak-web-application.netlify.thenational.academy
Click on _______
You should see _______

Screenshots
How it used to look (delete if n/a):
{screenshots}
How it should now look:
{screenshots}
Checklist

[ ] Added or updated tests where appropriate
[ ] Manually tested across browsers / devices
[ ] Considered impact on accessibility
[ ] Design sign-off
[ ] Approved by product owner
[ ] Does this PR update a package with a breaking change

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


Being able to build a 3.2.34 kernel using docker

cc @aimxhaisse

Need to move lots of things outside the main folder to allow non-destructive git clean -fxd

It works, but it's a little bit slow for now, since I'm copying the .git file instead of working on checked out repository (it allows me to run this on case-insensitive file systems)


create_server fails if server already exists

Should handle rc=1 which means a redundant operation. See the server command doc

start_server has a similar problem.

fixed by commit 6e9bcf50b0


Startup link working directory fix

Fixes the created startup link, to include a working directory, to read the saved "DuckDNS.cfg"

Sorry, I think I miss a step.


startDate and endDate not recognized in example code.

I have installed the package according to the ReadMe instructions, but when I create a new swift file containing the sample code, the default values for startDate and endDate throw errors.

Am I missing something in the instructions? It seems like according to the docs that just executing this should default the start and end dates to todays value. Is there something that needs to be done here that isn't explicitly shown in ReadMe?

These are date objects and you can declare these variables in your view based your needs like:
private let startDate = Date().addingTimeInterval(TimeInterval(60 * 60 * 24 * (-30 * 36)))
private let endDate = Date().addingTimeInterval(TimeInterval(60 * 60 * 24 * (30 * 36)))

Adjust TimeInterval based on your specific needs. This should be fixed in documentation though. I will open a PR to do just that.

Thanks @sethi-ishmeet for helping out.


form.commit({validate:false}) still validates individual fields

When I call form.commit({validate: false}) I am receiving errors in response.
var MyModel = Backbone.Model.extend({
  schema: {
    headline: { type: "Text", validators: [ "required" ] },
    slug: { type: "Text", validators: [ "required" ] }
  }
});
var model_instance = new MyModel();
var form = new BackboneForm({
  model: model_instance,
  fields: [ "slug", "headline" ]
}).render();

$('body').append(form.el);
var result = form.commit({ validate: false });
console.log("number of errors: ", _.keys(result).length);

It looks like individual fields are being validated with in form.validate() BEFORE checking if skipModelValidate is set.
I'm going to file a PR shortly to check skipModelValidate before the individual fields are validated.
This wasn't intentional, right? I'm not missing something important?

From the README:

There are 2 levels of validation: schema validators and the regular built-in Backbone model validation. Backbone Forms will run both when form.validate() is called. Calling form.commit() will run schema level validation by default, and can also run model validation if { validate: true } is passed.

In other words, I believe the validate flag is specifically designed to mirror / pass through to Backbone's set (whose option is described on http://backbonejs.org/#Model-validate). So yes, I think it was intentional this way and it would definitely a backwards incompatible change for validate: false to suddenly also ignore schema-level validation.
If this behavior is really needed, perhaps introducing another option (e.g. schemaValidate) would be better, though I'd question why you bother with form/schema validation if you want to disable it.

@philfreo Thanks for breaking it down for me. I thought there was an intent that I wasn't picking up on.
My usecase is this:
I want to show users a rendered preview of their form values as they input data. Like a WYSIWG. (e.g. insert a headline in a form input, have it show up in a "preview pane" inside an <h1> tag).
I have a slug field that I definitely want to validate on form submission, but I don't care about whether or not it's valid before then. The slug doesn't show up in the preview pane.
 I don't want one invalid field to break my entire preview pane.
On form submit, I will definitely validate and prevent submission if there are invalid fields.

One idea is to move slug validation to the Backbone model then? Or have a selective backbone-forms validator that only gets triggered when a certain criteria (final submission) is true.

I think I see what you're getting at. It's an anti-pattern to commit dirty data to the model, and in a sense defeats the purpose of having validation schemas in the first place.
However, I'm not a big fan of moving validation to the Backbone model's validate, as I lose out on backbone-form's schema pattern, which I really prefer, and ultimately on final submission, I want to use.
Also, moving to a custom validator would be alright, but in practice, I'll probably end up writing custom validators for all my fields and then would have to lay some more code on to determine the state of a commit (final submission vs. preview render). So I'd either have to abstract Backbone-Form's validators or rewrite them.
I'm going to submit a PR to see if there are thoughts on adding an option to form.commit().

How about having a different form + schema (in which you define which
fields you want to validate. e.g.: all except slug) for the preview pane?
Preview pane and normal form are backed by the same model.
On Wed, Feb 8, 2017 at 1:46 AM, Charley Bodkin<EMAIL_ADDRESS>wrote:

I think I see what you're getting at. It's an anti-pattern to commit dirty
data to the model, and in a sense defeats the purpose of having validation
schemas in the first place.
However, I'm not a big fan of moving validation to the Backbone model's
validate, as I lose out on backbone-form's schema pattern, which I really
prefer, and ultimately on final submission, I want to use.
Also, moving to a custom validator would be alright, but in practice, I'll
probably end up writing custom validators for all my fields and then would
have to lay some more code on to determine the state of a commit (final
submission vs. preview render). So I'd either have to abstract
Backbone-Form's validators or rewrite them.
I'm going to submit a PR to see if there are thoughts on adding an option
to form.commit().
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/powmedia/backbone-forms/issues/540#issuecomment-278193400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYAK2TAs-bvImthj1q39_Is1Xei1zl3ks5raRBkgaJpZM4L6I4s
.

Don't write unvalidated data to the model. That's indeed an anti-pattern.
You never know which other view attached to the model expects a valid state
and would totally crash. Don't break that interface/contract.
On Wed, Feb 8, 2017 at 10:21 AM, Geert-Jan Brits (Clearskyabove) <
<EMAIL_ADDRESS>wrote:

How about having a different form + schema (in which you define which
fields you want to validate. e.g.: all except slug) for the preview pane?
Preview pane and normal form are backed by the same model.
On Wed, Feb 8, 2017 at 1:46 AM, Charley Bodkin<EMAIL_ADDRESS>wrote:

I think I see what you're getting at. It's an anti-pattern to commit
dirty data to the model, and in a sense defeats the purpose of having
validation schemas in the first place.
However, I'm not a big fan of moving validation to the Backbone model's
validate, as I lose out on backbone-form's schema pattern, which I really
prefer, and ultimately on final submission, I want to use.
Also, moving to a custom validator would be alright, but in practice,
I'll probably end up writing custom validators for all my fields and then
would have to lay some more code on to determine the state of a commit
(final submission vs. preview render). So I'd either have to abstract
Backbone-Form's validators or rewrite them.
I'm going to submit a PR to see if there are thoughts on adding an option
to form.commit().
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/powmedia/backbone-forms/issues/540#issuecomment-278193400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAYAK2TAs-bvImthj1q39_Is1Xei1zl3ks5raRBkgaJpZM4L6I4s
.


Nested

Version
2.5.2
Reproduction link
https://jsfiddle.net/ybb37jr4/
Steps to reproduce
Create a template where a certain condition directive must only emit text, and therefore the developer must use <template v-else> rather than  or similar. That nested template tag will only work with {{ text }} but not with v-text="text".
For example:

No message...

<template v-else v-text="message"/>

What is expected?
Both nested <template v-else v-text="text"/> and <template v-else>{{ text }}</template> emit text from the variable.
What is actually happening?
Nested <template v-else v-text="text"/> does not emit anything.

Interestingly, <template v-else v-text="text"/> actually works in SSR, but immediately crashes once the client-side Vue inits, with:
[Vue warn]: The client-side rendered virtual DOM tree is not matching server-rendered content.

v-text should be used on real nodes as it sets the inner text of an element. So it cannot be used with a template
We can however, add a warning for this

This is expected: <template> itself doesn't produce any visible content.

@yyx990803 But in my example it is combined with a structural directive (v-else).
@posva But it does work in SSR:
const Vue = require('vue')
const app = new Vue({
  template: '

No foo
<template v-else v-text="foo"/>
',
  data: { foo: 'Hello' },
})

const renderer = require('vue-server-renderer').createRenderer()

renderer.renderToString(app, (err, html) => {
  if (err) throw err
  console.log(html)
})

this emits:

Hello

exactly as expected.

The same code does not work in the browser, however (see the jsfiddle). Isn't this inconsistency a problem?

Let's put it this way: v-text is the equivalent of setting textContent property of a node. This is why it doesn't work on a <template> node. The fact that it works in SSR it coincidental and we will probably fix it to maintain consistency with client-side behavior, so you should not rely on it.


Dev stopping after period of time

Home Assistant release (hass --version): Latest dev at time of posting (#8251039ca48aa576b6c59a9801e1bca154ec69b4)
Python release (python3 --version): 3.5.2
Component/platform: Core
Description of problem: Application stops after a period of time (around 40 minutes), nothing in the logs, even running in debug. Please advise on how I can capture more information on the crash, is there a way to dump a Python app on exit?

Maybe related to #3453 ?

@balloob potentially, would dmesg show that?


(Cheap) Count ranged tombstones

Explaining the metrics for future observers:
In Cassandra 2.x, range tombstones are treated differently than cells, where as in C* 3.x, range tombstones are treated as cells. This is important detail, as the iterators used when counting/viewing cells, do not contain range tombstones, as they're not cells. Thus, we've to wrap the iterator which reads from disk, but then we're only getting tombstones from disk -- leaving any tombstones in a memtable ignored.
So we end up with three different metrics:
(1) RangeTombstonesReadHistogram: Total number of range tombstones read from disk
(2) DroppableRangeTombstonesReadHistogram: Total number of droppable range tombstones read from disk
(3) RangeTombstonesHistogram: Total number of range tombstones, both memory and disk.
Which gives us the following: RangeTombstonesHistogram >= RangeTombstonesReadHistogram >=  DroppableRangeTombstonesReadHistogram
We cannot figure out the number of droppable tombstones for both memory/disk as we'd need to do an O(N) scan (N being number of range tombstones) to determine which are droppable -- there's also no convenient place to put this in the code where we are already performing the scan.


Database Change means that Archive has not been archiving anything

A while ago we changed the database structure on Kingfisher
https://github.com/open-contracting/kingfisher-process/commit/0c6d0531cc5307b1d165bc8dc411f6274fea766f#diff-84d496d7ab3f310d1b590d371592dc0c
This has broken Archive, and it hasn't tried to archive anything since then.
We do
select source_id, to_char(data_version, 'YYYYMMDD_HH24MISS') from collection where store_end_at is not null and transform_type is null

Need to change to
transform_type = ''

As well as doing this change, whoever does this should take the opportunity to make sure the store_end_at check is still correct to.

Fixed yesterday: https://github.com/open-contracting/kingfisher-archive/commit/5d23fcd807d1ce200c1fb680368bcac9179318d7


clarify cli

add clarification.

@johnkemnetz : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@GitHubber17 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


IGAPP-136: Internal linking - pathname parser

This pull request belongs to an issue on our bugtracker.
You can find it there by looking for an issue with the key which is mentioned in the title of this pull request.
It starts with the keyword IGAPP.
First part of a refactored, consistent and generic internal linking. This moves all route types to the api-client so they can be used at a later point in web as well. It also adds an InternalRouteParser which parses internal urls and returns information for the corresponding route.

We could move this parser to the api-client. I think it would make sense there because path names are actually part of an API.
Maybe we can also make use of it in the web.

We could move this parser to the api-client. I think it would make sense there because path names are actually part of an API.
Maybe we can also make use of it in the web.

Is this only for linking form native to web or should / can it also be used for navigation (issues) in native?

Is this only for linking form native to web or should / can it also be used for navigation (issues) in native?

@SteffiStuffel currently this is meant to parse web urls/pathnames (e.g. https://integreat.app/augsburg/de/events/2134) and return all relevant information to be able to open the corresponding page in the native app. However, of course it can be used for other things if it helps there. Not sure if I understand the question though :)

Is this only for linking form native to web or should / can it also be used for navigation (issues) in native?

@SteffiStuffel currently this is meant to parse web urls/pathnames (e.g. https://integreat.app/augsburg/de/events/2134) and return all relevant information to be able to open the corresponding page in the native app. However, of course it can be used for other things if it helps there. Not sure if I understand the question though :)

oke i see. I asked because I'm struggling a bit with the navigation stuff especially the routes in the store and was wondering if this PR is related to my troubles ;)

@SteffiStuffel not sure, but probably notthen. What are you struggling with?

@SteffiStuffel not sure, but probably not, then. What are you struggling with?

May lets have a call about this or talk about it on coworking-wednesday?

We could move this parser to the api-client. I think it would make sense there because path names are actually part of an API.
Maybe we can also make use of it in the web.

will do in #135 . Somehow git makes strange things here.


Guide/Docs: Documentation on Injecting attributes & TailwindCSS v4 (+ Shadcn/ui)

Since these three topics are fairly related to each other (or atleast in the way I've been using them), I've added the following three topics to the docs/guides and the link to my repo where I've been using these implementations in docs/community.
The topics are as follows:

TailwindCSS v4 - Installation + configuration
TailwindCSS v4 (reference to guide 1 of this list) + Shadcn/ui
Stream interception middleware to inject attributes into the stream content (example inject lang + classname into the html root element)

In any changes are required, feel free to give me notice! You're time is appreciated 👍

@sandren I've just removed the TailwindCSS v4 + Shadcn/ui guides and updated the community link to point to a stripped down version of the demo I had linked previously.
If any other changes are required, let me know! 😃 👍


Terminal Cursor Ghosting When Window Zoom Set To -1

Issue Type: Bug

Set "window.zoomLevel": -1
Click into terminal window (Tested using powershell terminals both integrated and included)
Remove cursor from window
Place cursor in window and press enter to new line.
Observe square cursor ghosting outline

Expected Result: No ghosted cursor outline when moving to new line in terminal

VS Code version: Code 1.49.1 (58bb7b2331731bf72587010e943852e13e6fd3cf, 2020-09-16T23:27:51.792Z)
OS version: Windows_NT x64 10.0.18363
Extensions (5)

Extension
Author (truncated)
Version

bracket-pair-colorizer-2
Coe
0.2.0

prettier-vscode
esb
5.6.0

powershell-preview
ms-
2020.9.0

material-icon-theme
PKi
4.3.0

vscodeintellicode
Vis
1.2.10

(1 theme extensions excluded)

Same issue here.

Yup @AxonneQ that's exactly what my terminal looks like after a while. Really annoying and distracting.

Can you share your settings.json file? A workaround is to set terminal.integrated.rendererType to dom

{
"workbench.iconTheme": "material-icon-theme",
"[powershell]": {
"editor.renderWhitespace":"selection",
"editor.renderControlCharacters": false,
"files.trimTrailingWhitespace": true,
"files.encoding": "utf8bom",
"files.autoGuessEncoding": true,
"editor.tabCompletion": "on"
},
"bracket-pair-colorizer-2.activeScopeCSS": [
"borderStyle : solid",
"borderWidth : 2px",
"borderColor : {color}",
"opacity: 0.8"
],
"bracket-pair-colorizer-2.showBracketsInGutter": true,
"editor.suggestSelection": "first",
"vsintellicode.modify.editor.suggestSelection": "automaticallyOverrodeDefaultValue",
"terminal.integrated.shell.windows": "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe",
"files.autoSave": "afterDelay",
"powershell.codeFormatting.autoCorrectAliases": true,
"powershell.integratedConsole.suppressStartupBanner": true,
"terminal.integrated.automationShell.linux": "",
"powershell.powerShellDefaultVersion": "Windows PowerShell (x64)",
"powershell.codeFormatting.useCorrectCasing": true,
"terminal.integrated.cursorBlinking": false,
"workbench.colorCustomizations": {
"terminalCursor.foreground": "#FFFFFF",
"terminalCursor.background": "#1e1e1e"
},
"workbench.view.alwaysShowHeaderActions": true,
"window.zoomLevel": -1
}

Looks like the issue is with the window.zoomLevel: -1 when the value is 0 or higher, ghosting disappears. Kind of sucks since on 1440p, the UI is a bit too big for me. that's why I zoomed it out.

Can you try close vscode and launch using code --disable-featuers="LayoutNG" to see if the issue still happens?

Can you try close vscode and launch using code --disable-featuers="LayoutNG" to see if the issue still happens?

Removed the workaround and tried starting using what you suggested. Issue is still happening. Here is the output of the command prompt:
C:\Users\jt114881\AppData\Local\Programs\Microsoft VS Code> code --disable-featuers="LayoutNG"
Warning: 'disable-featuers' is not in the list of known options, but still passed to Electron/Chromium.
[main 2020-09-23T23:38:52.827Z] update#setState idle
(node:109112) Electron: Loading non-context-aware native module in renderer: '\?\C:\Users\jt114881\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar.unpacked\vscode-sqlite3\build\Release\sqlite.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:109112) Electron: Loading non-context-aware native module in renderer: '\?\C:\Users\jt114881\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar.unpacked\node-pty\build\Release\conpty.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:109112) Electron: Loading non-context-aware native module in renderer: '\?\C:\Users\jt114881\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar.unpacked\windows-process-tree\build\Release\windows_process_tree.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:109112) Electron: Loading non-context-aware native module in renderer: '\?\C:\Users\jt114881\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar.unpacked\spdlog\build\Release\spdlog.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
(node:113736) Electron: Loading non-context-aware native module in renderer: '\?\C:\Users\jt114881\AppData\Local\Programs\Microsoft VS Code\resources\app\node_modules.asar.unpacked\spdlog\build\Release\spdlog.node'. This is deprecated, see https://github.com/electron/electron/issues/18397.
[main 2020-09-23T23:39:22.827Z] update#setState checking for updates
[main 2020-09-23T23:39:23.205Z] update#setState idle

Having the same issue here, VSCode 1.49.1, windows 10

Can confirm with Manjaro and the Snap version.
Versión: 1.50.0-insider
Confirmación: e6a742d2407c4a94c6540b49aa5f801468dbd1c8
Fecha: 2020-09-22T18:12:43.551Z
Electron: 9.3.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
Sistema Operativo: Linux x64 5.4.64-1-MANJARO snap

Window zoom level, --disable-features flag have no effect. DOM renderer is a workaround, although I end up with a sort-of-shaved-off cursor.

@Tyriar this is still marked as 'needs more info', do you require any more information from me?

I was able to repro with stable but I cannot repro the issue with our insiders https://code.visualstudio.com/insiders/, can others confirm ?

@deepak1556 confirmed issue still happening on latest insiders build as well.
Set it up with the same extensions and settings file, minus the workaround.

I followed your steps and reused same settings but wasn't able to repro the issue with insiders. Attaching the screen recording from both stable and insiders.
cursor_ghosting.zip

I followed your steps and reused same settings but wasn't able to repro the issue with insiders. Attaching the screen recording from both stable and insiders.
cursor_ghosting.zip

See my repro attached.
Confirmation.zip

@deepak1556  unfortunately, it's still ghosting even on insiders build

thanks for confirming, couple of things I want to check

Can you launch with code --disable-features=LayoutNG , I know that it was requested in https://github.com/microsoft/vscode/issues/106981#issuecomment-697971958 but the flag has a typo in that comment.

Can you launch with code --disable-gpu

Can you check with our exploration builds https://az764295.vo.msecnd.net/exploration/a9522785ef3c54961079e12afab9d3915ea68e08/VSCodeUserSetup-x64-1.51.0-exploration.exe that comes with newer chromium runtime.

let me know which of these work and don't.

thanks for confirming, couple of things I want to check

Can you launch with code --disable-features=LayoutNG , I know that it was requested in #106981 (comment) but the flag has a typo in that comment.
Can you launch with code --disable-gpu
Can you check with our exploration builds https://az764295.vo.msecnd.net/exploration/a9522785ef3c54961079e12afab9d3915ea68e08/VSCodeUserSetup-x64-1.51.0-exploration.exe that comes with newer chromium runtime.

let me know which of these work and don't.

I have tried code --disable-gpu and it seems that the ghosting has stopped but when you use --disable-features=LayoutNG its still there.

@Tyriar considering this is a gpu specific issue, next step would be create a minimal repro and file report in chromium, can you help with that ?

Same issue. "terminal.integrated.rendererType": "dom" and code --disable-gpu are both confirmed workarounds.
I just want to add that adjusting the size of the terminal makes the effect go away, for me at least, but it comes back after some time.
It also seem that the ghosting only shows when :

"window.zoomLevel" is less than 0
clicking out of terminal and then getting back in it

here's a gif of how i repro

Can anyone confirm whether "terminal.integrated.rendererType": "experimentalWebgl" also works around the issue?

works for me

@colinpmillar great to hear! So this is restricted to the canvas renderer that while it is the default, I want to get rid of in favor of webgl with a fallback of dom based on some automatic detection https://github.com/microsoft/vscode/issues/106202. This is after we close the gap in functionality, which I think is only context loss and underline support at this point https://github.com/xtermjs/xterm.js/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Faddon%2Fwebgl

"terminal.integrated.rendererType": "experimentalWebgl" doesn't work for me, unfortunately.
I also noticed that this "cube" shows up on experimentalWebgl , canvas and auto

But when i set it on dom this shows up

These two pictures shows the cursor when i clic away from the terminal

I also see the "two-lines" cursor when using the "terminal.integrated.rendererType": "dom"  setting!

I also see the "two-lines" cursor that @Ofsen mentions when using the "terminal.integrated.rendererType": "dom" setting!

This sounds like a separate bug as this issue is specifically about canvas changes in Chromium. I don't think that's been reported yet so feel free to create it.

experimentalWebgl produces the exact same artifacts for me.
But, upon switching the renderer, the terminal gets fully redrawn, which termporarily fixes it. The artifacts reappear soon enough though.

I had a similar problem, pressing backspace left residue cursors and setting "terminal.integrated.rendererType": "dom" solved the problem...

I had a similar problem, pressing backspace left residue cursors and setting "terminal.integrated.rendererType": "dom" solved the problem...

Can confirm this issue too in 1.52.1.

After reading this thread I've tried:

setting "terminal.integrated.rendererType": "experimentalWebgl": doesn't help, same issue
starting with --disable-features="LayoutNG": doesn't help
setting "terminal.integrated.rendererType": "dom": makes VS Code unbearably slow. Not sure if this works around/fixes the render issue, but it makes everything so slow that it's unworkable

settings:

"terminal.integrated.shell.windows" is set to PowerShell.exe
"terminal.integrated.fontSize": 12

Same problem here.. Just wanted to share one thing that I've noticed about this: if you resize the terminal panel the artifacts are gone. Maybe it helps to figure out the inner problem and/or solution.

A workaround for me with the "double lined" block was to change the Cursor Style from block to line, and increase the Cursor Width to 8, which is approximately the same size as the "block" style.

Has there been any other alternative workarounds for this? For me, when changing the render type, it causes my terminal to be extremely slow, so watching logs and what not just take much longer.

VSCode updated this morning, and now the issue seems to have returned for me... I too work on a zoomed environment of -1 and can confirm that anything less than zoom level 0 causes this.

I'm not a fan of underline or block size looking cursor. Setting the cursor width to 2 worked for me and I hope it works for you if you are a fan of line cursor style...
  "terminal.integrated.cursorStyle": "line",
  "terminal.integrated.cursorWidth": 2

https://user-images.githubusercontent.com/5789670/119606908-0ea47800-bdfc-11eb-9c52-5bd52f7cdac2.mp4

xterm.js issue: https://github.com/xtermjs/xterm.js/issues/3391

While this does appear to be a regression due to a Chromium update, looks like the fix can be done on our end without much compromise.

This was driving me crazy, can't believe I came to this issue to find out it will probably be fixed in Insiders on monday, guess I'm a lucky boy :)

I wasn't able to repro in stable so couldn't verify. If anyone hits this on their machine, please appease the bot above https://github.com/microsoft/vscode/issues/106981#issuecomment-889223678

For me this issue is gone on stable 1.58.2 too, great!

I'm still experiencing this on stable 1.58.2 in MacOS 11.5.1 (M1 version) :(

@Juanpam please try Insiders https://github.com/microsoft/vscode/issues/106981#issuecomment-889223678

@connor4312 May I install this one side by side with the stable release? Also, I noticed the terminal.integrated.rendererType config option is no longer available :(

@connor4312 Can confirm the bug is gone on Insiders (at least for me) version:
Version: 1.59.0-insider (Universal)
Commit: 8f58c1f457bd2ddf6cf81120c450c783b6e8c01b
Date: 2021-08-04T08:44:13.089Z
Electron: 13.1.7
Chrome: 91.0.4472.124
Node.js: 14.16.0
V8: 9.1.269.36-electron.0
OS: Darwin arm64 20.6.0

Thanks!


Replace type with a nested type

 @Test
    fun replaceWithNestedType(jp: JavaParser) = assertChanged(
        jp,
        recipe = ChangeType("java.io.File", "java.util.Map.Entry"),
        before = """
            import java.io.File;

            class Test {
                File p;
            }
        """,
        after = """
            import java.util.Map;

            class Test {
                Map.Entry p;
            }
        """
    )

Currently the following produced:
import java.util.Map.Entry;

class Test {
    Map.Entry p;
}

Looks like ChangeType#visitCompilationUnit(...) code adding the import should account for nested types... seems like we'd go for Map.Entry in the code and java.util.Map (top level type as the import. (I was going the other direction but think the one you picked is a better one)

Perhaps this test should actually go in the other direction - the nested type in the import (the targetType of the ChangeType) rather than the top level:
    @Test
    fun replaceWithNestedType(jp: JavaParser) = assertChanged(
        jp,
        recipe = ChangeType("java.io.File", "java.util.Map.Entry"),
        before = """
            import java.io.File;

            class Test {
                File p;
            }
        """,
        after = """
            import java.util.Map.Entry;

            class Test {
                Entry p;
            }
        """
    )

Seemed to me it should easier to adjust ChangeType to this expected result rather than the one in the description at the top

I think we'll stick to the first form @BoykoAlex if that's OK, because that's what the IDE does by default.


prevent torus from erroring when used for login

Purpose
Initial support for the SDK only worked if you logged in through Metamask. Torus logins fail, and if you had already logged in with Torus the app would not even load.
Solution
This PR adds the ability to choose the correct provider based on which login method had been selected.
Change summary

A detailed list of bulleted
changes that go into detail about
the specifics of the changes
to the codebase

Steps to Verify

Open the example client.
Sign up for Torus
Log in through Torus (you should get no error)
Attempt to make a Post (you should get a Torus popup to sign the batch announcement).

I tried to verify and got

superseded by #37


Pre Turkey Update

Team Pawnsy
Overview

Our project will be a social media website and forum where users can discuss chess topics and interact with Artificial Intelligence to learn and play chess.
Our project is based on the flocker project and will utilize numerous elements such as the posting and post database, user authentication and database, and external APIs pertaining to chess. For the posts specifically, we will require an upload system that will be based on the pfp storage system, and we will likely need to create a new API endpoint for the storage system.
Our initial discussion for Sprint 4: https://github.com/code259/sprint4_frontend/issues/1#issue-2677335072

Repositories

https://github.com/code259/sprint4_backend
https://github.com/code259/sprint4_frontend

Pages

Landing Page: Since page will be a social media website, we will have landing page to inform new visitors of the purpose of the website and to redirect to various pages.
Home Page: After login and authentication the user will go to a home page with a list of posts by all users, of chess related topics such as certain board positions, tactics, questions, etc. User will be able to view the post and interact with the posts by having commenting capabilities, which will likely be shown in a modal.
Chat Page: Will have a chess board where users can interact with an Gemini or other LLM to talk and learn about chess.
Game Page (TBD): May create a page where user can use a real chess board to play against a bot, plan on using some sort of API.

Tasks & Roles
Note: Groups not finalized until Add/Drop deadline.

Scrum Master: Nikhil Maturi
Assistant Scrum Master: Aarush Gowda
Developer 1: Vasanth Rajasekaran

Landing Page Design and Development, Javascript for Animations (GSAP)

Developer 2: Aarush Gowda

Landing Page Design and Development, UML, and Javascript for Modal Design

Developer 3: Nikhil Maturi

API Calls and Upload API

Developer 4: TBD

Next Steps (For Checkpoint 1)
List of future ideas: https://github.com/code259/sprint4_frontend/issues/2#issue-2677357558

[x] Create Kanban Board to track iterations and features.
[ ] Utilize PEP 8 Guideline for Code (https://peps.python.org/pep-0008/#introduction)
[ ] Use UML or planning methods to show plan for integration of new ideas and features from Flocker.
[x] Create visually appealing Homepage - create brief design using figma
[ ] Remove redundancy in other pages and create good UX.
[ ] Remove features from Flocker not required for our project.
[ ] Implement API requests to LLM (AI Model), sending image data.

I am not really understanding general purpose from the description.  I have found that if I don't understand most of your team members will not get what they are supposed ot work on.
Perhaps you should setup chess tournaments and have people report back on play.   Perhaps you could have individual play chess against Gemini at different levels (if capability is there).   You could have people comment on matches and talk about "strategy" you mentioned.
.88 a lot is missing from my perspective for a weeks plan.