primordic/IssueDupesLite huggingface dataset:
Repository: vega/vega-lite

Issue #3270: header/footer/titleBand for Composition Layout
Created: 2018-01-16T23:47:40Z
Good examples to add:

 Ridgeline plot #3036

Duplicate issue #3437: faceting row/column, is there a way to specify the space between(negative or positive)?
Created: 2018-03-02T13:44:24Z
Looking to do some custom views/effects, I was reading through:
https://vega.github.io/vega-lite/docs/facet.html#facet-field-definition
And I am not seeing a means to specify the gap between the facts - weather there is a way to make them overlap by some amount or to spread them out more.
Is there a method to do this - did I look in the wrong place?
I was just playing around with the parameters to see what I can tweak.  I noticed these plots (joy plots):
https://bokeh.pydata.org/en/latest/docs/gallery/joyplot.html
Just tinkering around to see if I can reproduce that by hiding the axes and grids and making them overlap a bit.

Closing comment (2018-03-02T17:56:01Z): Duplicate of #3270
Repository: vega/vega-lite

Issue #5896: Selection doesn't work for stacked bar chart with corner radius
Created: 2020-02-12T19:32:30Z
Breaking spec:
{
  "$schema": "https://vega.github.io/schema/vega-lite/v4.json",
  "data": {"url": "data/seattle-weather.csv"},
  "mark": {"type": "bar", "cornerRadiusEnd": 2},
  "selection": {"highlight": {"type": "single", "on": "mousemove"}},
  "encoding": {
    "x": {"timeUnit": "month", "field": "date", "type": "ordinal"},
    "y": {"aggregate": "count", "field": "*", "type": "quantitative"},
    "fill": {"field": "weather", "type": "nominal"},
    "opacity": {
      "condition": {"selection": "highlight", "value": 1},
      "value": 0.2
    }
  }
}
Without the "cornerRadiusEnd": 2, selection works fine.

Duplicate issue #5956: Tooltips not showing for rounded bars
Created: 2020-02-21T21:36:13Z
Tooltips fail to display on rounded bars. Here is an example (vega editor):
{
  "data": {"url": "data/seattle-weather.csv"},
  "concat": [
    {
      "mark": {
        "type": "bar",
        "cornerRadiusTopLeft": 3,
        "cornerRadiusTopRight": 3
      },
      "encoding": {
        "x": {"type": "ordinal", "field": "date", "timeUnit": "month"},
        "y": {"type": "quantitative", "aggregate": "count"},
        "color": {"type": "nominal", "field": "weather"},
        "tooltip": {"type": "nominal", "field": "weather"}
      }
    },
    {
      "mark": "bar",
      "encoding": {
        "x": {"type": "ordinal", "field": "date", "timeUnit": "month"},
        "y": {"type": "quantitative", "aggregate": "count"},
        "color": {"type": "nominal", "field": "weather"},
        "tooltip": {"type": "nominal", "field": "weather"}
      }
    }
  ]
}

In the left panel, tooltips fail to display. In the right panel, tooltips display as expected. The only difference is the specification of cornerRadiusTopLeft and cornerRadiusTopRight.

Closing comment (2020-03-07T23:13:42Z): If you use the SVG renderer it works. It won't work in the canvas renderer. The issue could be in Vega's canvas handler.
Related to #5896
Repository: vega/vega-lite

Issue #3154: Cannot hover marks under a brush
Created: 2017-10-20T15:52:28Z
For example, given a new example I add for #3146, I cannot trigger a brushed point to be blue even though the condition for hover comes first.
{
  "$schema": "https://vega.github.io/schema/vega-lite/v2.json",
  "description": "Drag out a rectangular brush to highlight points.",
  "data": {"url": "data/cars.json"},
  "selection": {
    "brush": {
      "type": "interval"
    }, 
    "hoverbrush": {
      "type": "multi", "on": "mouseover",
      "nearest": true,
      "empty": "none"
    }
  },
  "mark": "point",
  "encoding": {
    "x": {"field": "Horsepower", "type": "quantitative"},
    "y": {"field": "Miles_per_Gallon", "type": "quantitative"},
    "color": {
      "condition": [ 
        {"selection": "hoverbrush", "value": "blue"},
        {"selection": "brush", "value": "skyblue"}
      ],
      "value": "grey"
    }
  }
} 

A more important issue would be that even with just one condition and brush (e.g., the brush.vl.json), we cannot hover a data point to see tooltip.

Duplicate issue #5728: Mouseover color-encoding does not work/casues errors inside interval selection
Created: 2020-01-08T10:23:30Z
Hi
I have a Histogram (binned quantitative) with interval selection and a hover selection (mouseover; spec below) to highlight the hovered bar.
When I set an interval and then hover over a bin inside, the hover color is not applied and there is an error every time my mouse enters the interval.
To me, it looks like the mouseover is not passed through the interval to the bins "behind" it
Spec:
https://vega.github.io/editor/#/url/vega-lite/N4KABGBEAkDODGALApgWwIaQFxUQFzwAdYsB6UgN2QHN0A6agSz0QFcAjOxge1IRQyUa6ALQAbZskoAWOgCtY3AHaQANOCgATdHkw5gkVgCcx2LTvSlU3Co2Sx5ilQF91ESBiMBrM5HbojNQ1IZCV4bk1GJWozUAh3AA9YjXiodiizPCNWZDdUqAAzOzFNXwBJAFkAEQAhAH0AJR0omLzUyDwAT0JkXwBHVnQlPGZmqkgUsFdJyE7k-Kh0amojYTxenEhw1mGghY7ujagBoZHdEfHJ6fbwsW5A-Un3CnQxHN8AYgBWAE5f372+S2ykiI2UZgA2k94nEFvEOvY8PM4e0hqUcFCUQtgFBYMgxMh4GCVJs8QSichSlNoQsALo0+LXLGQF5vI6QD4AMU5AGEAMzSAAMExRTOxDPcZMJxN8iBsyECbThLNe7023wATDzBTyeSK4c5ofTUoaIEzIFKiTwSWBYZL8dLKcj2l0er4ousjKzAe00IQur4lMpekr3J4fPpIEUxKZ1dz+UK1IVGDGAPKEdDwZhzHCCug-VS4rLcLzsrm8gXC02MpWQOVUB626EHN2kloEn3wv0BzZBpQh5vgzbWVh4+WK5vwAkBXwjsesJFXDSGw1AA

Closing comment (2020-05-23T16:41:37Z): Yes this is a current limitation (and a duplicate of #3154).
Repository: vega/vega-lite

Issue #1830: APIs to interact with Selection
Created: 2017-01-16T00:53:35Z

Duplicate issue #4751: Experimental selection APIs
Created: 2019-03-22T17:44:37Z
vl.selection(view, "name")
vl.add/removeSelectionListener or vl.selection.add/removeListener

I guess add/removeSelectionListener is better (a bit more modern style--flattened)?

Closing comment (2020-05-15T23:32:11Z): Closing as this is a duplicate of #1830
Repository: vega/vega-lite

Issue #170: Zero Baseline error for bars and areas
Created: 2015-02-01T22:46:01Z

Duplicate issue #168: Stacked Bar has wrong offset
Created: 2015-02-01T21:57:35Z
This might be due to the last few lines in stacking().

Closing comment (2015-02-01T23:24:22Z): duplicate of #170
Repository: vega/vega-lite

Issue #8531: support for expression in scheme parameter object
Created: 2022-11-02T10:30:05Z
Given the following bar chart with quantize color scale Open the Chart in the Vega Editor:

I would like to bind the defined parameter (no_classes) to the scheme parameter count (link to doc).
As such:
"scale": {
  "type": "quantize",
  "scheme": {"name": "purples", "count": {"expr":"no_classes"}}
}
But this gives me an error:
Unsupported object: {"expr":"no_classes"}
That is unfortunate and therefor on the wish-list

Duplicate issue #9120: Add Expression Ref Support for Bin Transform
Created: 2023-10-02T20:31:43Z
Currently, properties of the bin transform currently take specific property types like Numbers; however, using those primitive types instead of vega expressions restricts the ability to use parameters to customize your transform.
In an ideal world, you could add a slider for bin size and slide to see your data in various levels of aggregation.
See thread here for more information.
Related to this demo of changing levels of aggregation:

Closing comment (2023-10-03T04:49:34Z): Similar to #8531 and probably the same fix.
Repository: vega/vega-lite

Issue #2026: Gridline can be weird for faceted plot without either x or y
Created: 2017-03-08T20:28:29Z
{
  "data": {
    "values": [
      {
        "q1": 1,
        "q2": 2,
        "t": "2017-03-08T20:26:07.092Z",
        "n1": "a",
        "n2": 1,
        "_id": 2
      },
      {
        "q1": 100,
        "q2": 23,
        "t": "2017-03-08T20:26:07.092Z",
        "n1": "c",
        "n2": 1,
        "_id": 3
      }
    ]
  },
  "mark": "point",
  "encoding": {
    "x": {"field": "q1","type": "quantitative"},
    "row": {"field": "n1","type": "nominal"}
  },
  "config": {
    "overlay": {"line": true},
    "scale": {"useUnaggregatedDomain": true}
  }
}

Duplicate issue #2078: Correct Facet's grid sizing
Created: 2017-04-04T17:24:11Z
See examples in #2070 (comment)

Closing comment (2017-04-05T04:26:15Z): Duplicate of #2026
Repository: vercel/ai

Issue #4082: Multimodal Live API by Google (Gemini)
Created: 2024-12-13T00:54:53Z
Feature Description
Google has announced its multi-modal realtime api: https://ai.google.dev/gemini-api/docs/models/gemini-v2
Is that possible to add it into the AI SDK?
Use Cases
No response
Additional context
No response

Duplicate issue #4441: Gemini 2.0 Multimodal Live API
Created: 2025-01-19T03:08:24Z
Feature Description
https://ai.google.dev/api/multimodal-live?_gl=1*onf55t*_up*MQ..&gclid=Cj0KCQiAv628BhC2ARIsAIJIiK_6K7PGS7IPAagPgui-e-xEhKtXZ31vMt-HM9meJBDRegeN4skZEXgaAt6JEALw_wcB
Gemini Multimodal Live API would be a nice feature to add to AI SDK
Use Cases
Multimodal Live API includes the following key capabilities:
Multimodality: The model can see, hear, and speak.
Low-latency real-time interaction: Provides fast responses.
Session memory: The model retains memory of all interactions within a single session, recalling previously heard or seen information.
Support for function calling, code execution, and Search as a tool: Enables integration with external services and data sources.
Automated voice activity detection (VAD): The model can accurately recognize when the user begins and stops speaking. This allows for natural, conversational interactions and empowers users to interrupt the model at any time.
Additional context
No response

Closing comment (2025-01-22T11:59:41Z): Duplicates #4082
Repository: vercel/ai

Issue #2289: experimental_useObject onFinish
Created: 2024-07-16T08:34:16Z
Can we add an onFinish method to experimental_useObject similar to useCompletion?

Duplicate issue #2492: onFinish callback for experimental_useObject
Created: 2024-07-31T07:45:02Z
Feature Description
Is is possible to add an onFinish callback for experimental_useObject so that we can add custom logic at client side when the stream finishes? There is the onError callback on client side, onFinish callback on server side for streamObject, but I can't find onFinish on client side.
Use Case
Perform custom actions when the stream completes, e.g., url redirecting, client logs, etc
Additional context
No response

Closing comment (2024-07-31T16:16:54Z): Duplicates #2289
Repository: vercel/ai

Issue #239: `streamToResponse` does not stream
Created: 2023-06-28T02:23:38Z
"Can we use the AI SDK to implement a pure Node backend service? I have looked at the documentation for https://sdk.vercel.ai/docs/api-reference/stream-to-response and deployed it on Vercel. The frontend is implemented using a separate frontend and backend approach, but I have not been able to achieve the typewriter effect with stream flow. How can we achieve this effect?"
能否使用 ai sdk 实现一个纯node后端服务 ， 目前看了文档https://sdk.vercel.ai/docs/api-reference/stream-to-response 这个方案 将其部署在vercel上， 前端使用前后端分离的方案实现的， 没能实现打字机效果stream流式返回，如何才能实现这种效果呢

Duplicate issue #283: Streaming does not work once deployed
Created: 2023-07-06T02:21:55Z
I'm having an issue where streaming works perfectly fine when running locally, but after deploying it only returns the results all at once.
This is using streamToResponse in a normal serverless function (not an edge function).

Closing comment (2023-07-06T06:04:29Z): Closing as a dupe of #239.
Repository: vercel/ai

Issue #4082: Multimodal Live API by Google (Gemini)
Created: 2024-12-13T00:54:53Z
Feature Description
Google has announced its multi-modal realtime api: https://ai.google.dev/gemini-api/docs/models/gemini-v2
Is that possible to add it into the AI SDK?
Use Cases
No response
Additional context
No response

Duplicate issue #3176: Add support for OpenAI `realtime` voice models.
Created: 2024-10-02T04:52:28Z
Feature Description
Add support for the new OpenAI realtime modes.
Use Case
Building Voice to Voice realtime apps.
Additional context
https://openai.com/index/introducing-the-realtime-api/

Closing comment (2025-03-12T17:13:52Z): Right now this issue is related to #4082 .
Both OpenAI and Google's APIs use WebSocket for real-time streaming. OpenAI's API streams text, while Google's supports multiple data types like images and text. They have similar connection approaches but differ in payload formats and authentication. A unified abstraction layer with provider-specific adapters in the Vercel AI SDK could support both APIs seamlessly.
Repository: vercel/ai

Issue #1316: 3.0.20 create a breaking change for `StreamingTextResponse`
Created: 2024-04-10T03:31:40Z
Description
the correct response with ai@3.0.19:

the error response with ai@3.0.20:

it cause an issue with it: lobehub/lobe-chat#1945
Code example
import { OpenAIStream, StreamingTextResponse } from 'ai';
import OpenAI, { ClientOptions } from 'openai';

const response = await this.client.chat.completions.create(postPayload);

return new StreamingTextResponse(OpenAIStream(response));
Additional context
I check the update code, I think it's a breaking change for StreamingTextResponse :

please consider to revert it. Or I have to stay with 3.0.19.
a6b2500#diff-ee443c120877f90b068a98d03b338a35958a3953db7e0159035ae060b5b9052b

Duplicate issue #1344: Nuxt: Updating AI SDK from 3.0.19 to later causes error in useChat
Created: 2024-04-14T11:26:32Z
Description
Nuxt app works fine with ai@3.0.19 . However, updating to latest AI SDK causes the following browser error (shown via the onError callback in useChat):
Error
Failed to parse stream string. Invalid code
Reverting to ai@3.0.19 is the last version that works before the above error begins to show starting at version 3.0.20.
Code example
const {
	messages,
	input,
	handleSubmit,
	setMessages,
	reload,
	isLoading,
	stop,
	append
} = useChat({
	api: config.public.chatUrl,
	headers: { "Content-Type": "application/json" },
	body: agent,
	onError: (error) => {
		isLoading.value = false
		console.log("onError from useChat: ", error)
		errorMessage.value = error
	}
})

Additional context


Operating System: Windows_NT
Node Version:     v18.18.0
Nuxt Version:     3.11.2
CLI Version:      3.11.1
Nitro Version:    2.9.6
Package Manager:  npm@9.8.1
Builder:          -
User Config:      routeRules, devtools, nitro, modules, eslint, runtimeConfig, vuefire, image
Runtime Modules:  @nuxt/ui@2.15.2, @nuxt/image@1.5.0, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, nuxt-vuefire@1.0.2, @vueuse/nuxt@10.9.0, @nuxt/eslint@0.3.6, @nuxt/content@2.12.1, @nuxt/fonts@0.6.1
Build Modules:    -

Closing comment (2024-04-14T11:43:25Z): Duplicate of #1316
See #1316 (comment) for upgrade instructions.
Repository: vercel/ai

Issue #1316: 3.0.20 create a breaking change for `StreamingTextResponse`
Created: 2024-04-10T03:31:40Z
Description
the correct response with ai@3.0.19:

the error response with ai@3.0.20:

it cause an issue with it: lobehub/lobe-chat#1945
Code example
import { OpenAIStream, StreamingTextResponse } from 'ai';
import OpenAI, { ClientOptions } from 'openai';

const response = await this.client.chat.completions.create(postPayload);

return new StreamingTextResponse(OpenAIStream(response));
Additional context
I check the update code, I think it's a breaking change for StreamingTextResponse :

please consider to revert it. Or I have to stay with 3.0.19.
a6b2500#diff-ee443c120877f90b068a98d03b338a35958a3953db7e0159035ae060b5b9052b

Duplicate issue #1370: Got '0:" !"\n' out of very strange characters from the stream since the last update, and the document is not updated.
Created: 2024-04-17T06:36:47Z
Description
Since the last update, the AI SDK now fully supports custom file reading.

Code example
I use ReadStream to read stream from OpenAI :
export const readStream = async (
  stream: ReadableStream,
  onChunkValue: (chunk: string) => void
) => {
  const reader = stream.getReader();
  const decoder = new TextDecoder();
  let done = false;

  let result = '';

  while (!done) {
    // eslint-disable-next-line no-await-in-loop
    const { value, done: doneReading } = await reader.read();
    done = doneReading;
    const chunkValue = decoder.decode(value);

    result += chunkValue;

    onChunkValue(result);
  }
};
And follow the documentation for the app router :
import OpenAI from 'openai';
import { OpenAIStream, StreamingTextResponse } from 'ai';
 
// Optional, but recommended: run on the edge runtime.
// See https://vercel.com/docs/concepts/functions/edge-functions
export const runtime = 'edge';
 
const openai = new OpenAI({
  apiKey: process.env.OPENAI_API_KEY!,
});
 
export async function POST(req: Request) {
  // Extract the `messages` from the body of the request
  const { messages } = await req.json();
 
  // Request the OpenAI API for the response based on the prompt
  const response = await openai.chat.completions.create({
    model: 'gpt-3.5-turbo',
    stream: true,
    messages: messages,
  });
 
  // Convert the response into a friendly text-stream
  const stream = OpenAIStream(response);
 
  // Respond with the stream
  return new StreamingTextResponse(stream);
}
Additional context
In this file from the Next.js example, I see that the documentation seems to not be updated: https://github.com/vercel/ai/blob/main/examples/next-openai/app/api/chat/route.ts

Closing comment (2024-04-17T06:41:30Z): Duplicate of #1316
See #1316 (comment) for solutions
Repository: vercel/ai

Issue #167: Allow submitting form without adding a message in useChat hook
Created: 2023-06-20T00:14:11Z
Currently we do nothing if no text is input in the form - https://github.com/vercel-labs/ai/blob/fd69e9a5628d1cd21a7c4a36584b4c577e0cc0a6/packages/core/react/use-chat.ts#L253
But, submitting a new API request without adding a new user message is a good way to get the LLM to continue its previous response, for example if the user hit stop, or the previous response reached the token limit. This is how the OpenAI playground works.

Duplicate issue #323: Append completion instead of wiping it when triggering a new complete()
Created: 2023-07-12T22:31:21Z
Is there a way to append completion when using useCompletion() rather than reset it when submitting via complete(). initialCompletion could work for this but there is no way to reference the initial content.

Closing comment (2023-07-13T02:12:18Z): Going to close this as a dupe of #167. PRs welcome!
Repository: vercel/ai

Issue #1896: Programmatic access to the model capabilities and provider listings
Created: 2024-06-10T00:54:17Z
Feature Description
Please allow the ability to:


query the model capabilities, such as the maximum token limit, image input support etc.


list all the providers and their supported models, along with their default configuration values etc.


through programmatic means.
Use Case
To build UIs that allow switching the models dynamically from the client side, we would need to query the model capabilities and the model listings.
For example, consider the below screenshot from the Playground:

Additional context
Could not find any API to programmatically list the models or access their capabilities in the documentation. Adding such API helps in dynamically switching the models from the client side.

Duplicate issue #4769: Add model list per provider
Created: 2025-02-07T16:11:10Z
Feature Description
When generating the docs it would be really usefull to see all of the model names we can use as parameters, for example the current model shown in Gemini AI is 1.5-pro while 2.0 Flash is already out and usable via gemini api
https://sdk.vercel.ai/providers/ai-sdk-providers/google-generative-ai
If there was a table list with all available models, that would be amazing.
Use Cases
When looking at what available models each provider has.
Additional context
This would be good for your SEO

Closing comment (2025-02-15T21:39:34Z): Duplicate of #1896

It's not a duplicate, the other issue is really helpful too. But I'm talking about the documentation website.

Oh I see, my bad.
Repository: vergecurrency/verge

Issue #118: Random auto-create address | Can't delete address | Renaming label issues
Created: 2017-12-21T11:51:04Z
1)I just did my first transfer from Binance to QT wallet to an address (labelled "XY" for example), and the wallet created automatically another address without label.
2)If i rename the "XY" label, the automatically created address i wrote in point 1 get automatically renamed with the same name... (usually after 2 renames).
3)I can't see a way to remove/delete an address.

Duplicate issue #235: "Edit name" on secondary address also applies to primary address (in receiving address tab)
Created: 2018-01-01T20:55:13Z
Under the receiving addresses tab, when performing name edit on a secondary address (right click + edit name) it also applies to the primary address as well.
Win 10 pro ver 1703 build 15063.786
VERGE-qt 4.0 v2.1.0.0-unk-beta

Closing comment (2018-01-01T22:08:45Z): Also reported in #118
Repository: vergecurrency/verge

Issue #708: Connected nodes from pool wallet daemon. v 4.01 - 4.02
Created: 2018-04-12T18:27:42Z
Hi!
wallet version branch: 80de5df
pool software: yiimp
Is it normal wallet connections to nodes running version 4.01 ?
Should the wallet connect only to wallets with the latest version 4.02 ?
Thanks!

Duplicate issue #707: New Wallet not mining
Created: 2018-04-12T18:25:55Z
hello, i have set up a small mining pool for verge with about 500Gh on blake2s, i could not get a block on 48 hrs running non stop, looking at my blake2s.log file i found this errors:
18:15:33: XVG 2054281 - diff 13544747.158115184 job 522 to 145/145/145 clients, hash 545540.144/1530901212.545 in 1.3 ms
18:15:55: XVG 2054281 - diff 13544747.158115184 job 523 to 145/145/145 clients, hash 535762.673/1530901212.545 in 1.4 ms
18:16:15: Verge 2054282 not reporting
18:16:16: XVG 2054283 - diff 13544747.158115184 job 524 to 145/145/145 clients, hash 528200.539/1572276920.992 in 1.3 ms
18:16:36: Verge 2054283 not reporting
18:16:37: XVG 2054284 - diff 13544747.158115184 job 525 to 146/146/146 clients, hash 533105.231/1572276920.992 in 1.4 ms
18:16:57: Verge 2054285 not reporting
18:16:58: XVG 2054286 - diff 10123889.088431366 job 526 to 146/146/146 clients, hash 534306.585/1175183041.707 in 1.5 ms
18:17:18: Verge 2054286 not reporting
18:17:19: XVG 2054287 - diff 10123889.088431366 job 527 to 146/146/146 clients, hash 539064.468/1175183041.707 in 1.3 ms
18:18:01: Verge 2054289 not reporting
18:18:02: XVG 2054290 - diff 10123889.088431366 job 528 to 148/148/148 clients, hash 569413.579/1207827015.087 in 1.4 ms
18:18:22: Verge 2054290 not reporting
18:18:23: XVG 2054291 - diff 10123889.088431366 job 529 to 148/148/148 clients, hash 573013.264/1207827015.087 in 1.4 ms
18:18:43: Verge 2054291 not reporting
18:18:44: XVG 2054292 - diff 10123889.088431366 job 52a to 147/147/147 clients, hash 568189.734/1207827015.087 in 1.4 ms
18:19:04: Verge 2054292 not reporting
18:19:05: XVG 2054293 - diff 10123889.088431366 job 52b to 147/147/147 clients, hash 564438.892/1242336358.376 in 1.4 ms
18:19:26: XVG 2054293 - diff 10123889.088431366 job 52c to 147/147/147 clients, hash 583800.714/1242336358.376 in 1.4 ms
Any ideas why is not working, a different coin for the same pool is working great... got a lot of those "Verge 2054XXX not reporting"
this is my config file, i am running Ubuntu 16 on a VPS
rpcuser=yiimprpc
rpcpassword=XXXXXXXXXXXXX
rpcport=5610
rpcthreads=8
rpcallowip=127.0.0.1
onlynet=ipv4
maxconnections=12
daemon=1
algo=blake
gen=0
alertnotify=echo %s | mail -s "Verge alert!" info@clouddatatech.net
blocknotify=/var/stratum/blocknotify pool2mine.com:5766 561 %s

Closing comment (2018-04-13T16:05:46Z): duplicate of #708 i think... will consolidate both of you on that issue
@pool2mine feel free to re-open if you feel your issue is different .. and make sure you did what justin suggested about the gen=0 and 4.0clearnet
Repository: vergecurrency/verge

Issue #443: MacOS Cosmetic issues thread - latest release 4.0.2
Created: 2018-01-11T04:04:01Z
I saw some issues with UI, I think they're not difficult to fix and make our product as perfect as possible.
Screenshots


My Environment

Verge Release: VERGE-Qt-4.0.1.dmg
Mac pro MF840.
OS:

 I'm using Mac High Serria 10.13.2

Duplicate issue #423: Cosmetic Dropdown Issue MacOs
Created: 2018-01-09T06:27:51Z
Old issue was closed, problem persists in the latest commit.

Transaction fee also could be improved.

Closing comment (2018-03-26T02:53:43Z): duplicate of #443  ,, will close this one ... keep an eye updates for #443
Repository: vergecurrency/verge

Issue #717: [BUG] Compiling fails for Windows
Created: 2018-04-14T21:27:39Z
Prerequisites

lastest master branch
windows 10

User Story:

"I'm submitting a ... "

 bug report



Compiling log
...
checking whether we are using the GNU Objective C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for i686-w64-mingw32.static-ar... no
checking for ar... /usr/bin/ar
checking for i686-w64-mingw32.static-ranlib... no
checking for ranlib... /usr/bin/ranlib
checking for i686-w64-mingw32.static-strip... no
checking for strip... /usr/bin/strip
checking for i686-w64-mingw32.static-gcov... no
checking for gcov... /usr/bin/gcov
checking for lcov... no
checking for java... /usr/bin/java
checking for genhtml... no
checking for git... /usr/bin/git
checking for ccache... /usr/bin/ccache
checking for xgettext... /usr/bin/xgettext
checking for hexdump... /usr/bin/hexdump
checking for i686-w64-mingw32.static-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for main in -lmingwthrd... no
configure: error: lib missing
make: *** No rule to make target `check'.  Stop.
cat: src/test-suite.log: No such file or directory
done
I think somethings are completely broken in the requirements scripts, but I don't know how to fix them.
But I would love to get them running, because I have to test all sorts of things on windows on well.
Like the loadingBlockIndex thingy -> referring to #710
Either someone explains it to me, or gives me a quick hint to get into it.

Duplicate issue #767: Build for Windows
Created: 2018-06-14T10:10:13Z
Issue Template
Context

Prerequisites

 Are you running the latest version?

User Story:

"I'm submitting a ... "

 bug report
 feature request
 support request
 translation request




Expected Behavior

Current Behavior

Screenshots

Possible Solution

Steps to Reproduce (for bugs)


Steps :







Your Environment


Verge Release:
CPU:
GPU:
RAM:
OS:

 I'm using Mac
 I'm using Linux
 I'm using Mac



Any extra information that might be useful in the debugging process.

Hello guys. I have one question. I trying build Verge from source for  windows using  easywinbuilder and Dockerfile, but first & second method fail with multiple errors. Question: It's actually now or I must using another way for build Qt Wallet for Windows?
I see travis logs for windows, build log have multiple errors too, but travis have green status.

Closing comment (2018-06-14T20:35:48Z): Yeah I gave this a shot as well and gave up a month or so ago.  We'll probably need to write a clear step-by-step guide after the new codebase.
Will flag this as a duplicate of #717  , keep all "Windows Compiling" issues under there.
Repository: vergecurrency/verge

Issue #192: Manually loading Blockchain on OSX causes App to hang on launch
Created: 2018-01-01T09:24:46Z
Hi all,
When trying to load the Blockchain manually i am seeing a aHang on launch of the latest vvraith build on 10.13.2
REPRO:

QuitQT-Verge
2* Download blockchain from -- https://verge-blockchain.com/blockchain/Wallet_v3.0_Verge-Blockchain_2017-December-30.zip
3* Follow install guide to a copy into App support -- https://drive.google.com/file/d/1KxIfooNfgRIghWXvndeyQFkz6bD9yOVr/view
4* Launch QT Verge

I took a sample and captured Syslog
Sample of VERGE-Qt.txt
Verge_syslog.txt
Verge_syslog.txt

Duplicate issue #291: mac wallet hangup
Created: 2018-01-03T02:47:30Z
mac 10.13.1
loading window appears, "loading block index...", wheel of death, window disappears, nothing happens. app shows active in dock, need to kill

Closing comment (2018-01-03T02:54:43Z): It takes 5-10 minutest to load currently
this is a dupe of #192
Repository: vergecurrency/verge

Issue #381: Display issues and QR Code not working - Mac - v2.1.0.0-75fa380-beta
Created: 2018-01-05T01:47:56Z
Above are display issues I found in the block explorer tab
Another display issue I found was adjusting column width in the wallet tab and address book tab does not work.
And last Show QR Code when right clicking on wallet address does not work

Duplicate issue #387: Drop Downs
Created: 2018-01-05T18:27:39Z
Hi Team,
v4.0.1.0-13d8f32-beta just built fine, I'm very happy with the consistency and reliability.
One question: Is there a plan to fix those dropdown boxes in the preferences window?
Thanks!

Closing comment (2018-01-05T21:35:34Z): Duplicates #381
Already reported in #381, feel free to close your issue if there's nothing else to report.
And keep it related to development topics, thank you.
Regard Kyon.
Repository: vergecurrency/verge

Issue #192: Manually loading Blockchain on OSX causes App to hang on launch
Created: 2018-01-01T09:24:46Z
Hi all,
When trying to load the Blockchain manually i am seeing a aHang on launch of the latest vvraith build on 10.13.2
REPRO:

QuitQT-Verge
2* Download blockchain from -- https://verge-blockchain.com/blockchain/Wallet_v3.0_Verge-Blockchain_2017-December-30.zip
3* Follow install guide to a copy into App support -- https://drive.google.com/file/d/1KxIfooNfgRIghWXvndeyQFkz6bD9yOVr/view
4* Launch QT Verge

I took a sample and captured Syslog
Sample of VERGE-Qt.txt
Verge_syslog.txt
Verge_syslog.txt

Duplicate issue #248: After copying blockchain, Verge is hanging, OSX High Sierra
Created: 2018-01-02T02:42:19Z
I installed verge wallet to my os x high sierra, I was able to open application without any problem. I downloaded latest blockchain from https://verge-blockchain.com and then I followed macos instructions to copy new blockchain to my verge app.
When i click app icon, it starts with splash screen and then it comes to Loading Block Index, it hangs.
When I click verge icon in my lauchpad, it says application is not responding. I waited it like 20 min.
I attached process detail view. What should I do?

Closing comment (2018-01-02T05:11:09Z): Ya it takes a while and you don't get a lot of feedback. Going to go through some of these and start to create issues we can prioritize in the coming weeks.
Duplicate of #192
Repository: verus-lang/verus

Issue #835: lifetime-generate might put unit type in if-condition
Created: 2023-09-29T16:55:32Z
pub const B: u64 = 7;

fn test(a: usize) {
    proof {
        if a <= B {
        } else {
        }
    }
}

This fails with
error: mismatched types
  --> testif.rs:19:12
   |
19 |         if a <= B {
   |            ^^^^^^

Specifically because lifetime_generate produces:
if op::<_, ()>((x23_a, f22_B(), )) 

It looks like a pretty easy fix, but I'm not sure what some of the intent behind some of the op-handling code is, so I don't want to make it worse with an ill-thought-out band-aid fix.

Duplicate issue #911: Mismatched type "in Verus pass: ownership checking of tracked code"
Created: 2023-11-20T15:18:11Z
I don't quite understand what's happening here but it looks like a bug.
use vstd::prelude::*;

verus!{

fn main() { }

fn foo() {
    let ofs: usize = 0usize;
    proof {
        // no type error:
        if ofs == 0usize {
        }
        // yes type error:
        if ofs > 0usize {
        }
    }
}
}
ξ verus-release /st/verus/test.rs
error: mismatched types
  --> /st/verus/test.rs:14:12
   |
14 |         if ofs > 0usize {
   |            ^^^^^^^^^^^^

error: aborting due to previous error

note: This error was found in Verus pass: ownership checking of tracked code

error: aborting due to 2 previous errors

Closing comment (2023-11-20T17:54:27Z): I think this is the same as #835.
Repository: verus-lang/verus

Issue #740: Verus ignoring Z3 warning about if in patterns
Created: 2023-08-09T00:25:37Z
Today @jaylorch, @Chris-Hawblitzel, and I discovered an issue where Verus continues with verification despite a 'if' cannot be used in patterns. warning from Z3. This playground link demonstrates the warning. I didn't have time to replicate it in a small example, but when we encountered this issue in my project, it was causing a (small) function that we knew should not verify to time out even on high rlimits. Chris hypothesized that Z3 had an issue with the triggers Verus chose for the forall and chose other triggers that caused a loop. I can post the code or try to replicate that behavior in the small example if that would be helpful.
Additionally, Z3 seems to be giving the wrong line number in the warning. When I run Verus on the playground code on my own computer, the warning is WARNING: (1878,5): 'if' cannot be used in patterns. but in the SMT file produced with --log-all (in this zip file: .verus-log.zip), line 1878 seems completely unrelated to the warning.

Duplicate issue #1583: WARNING: (2693,6): 'if' cannot be used in patterns.
Created: 2025-04-09T01:08:27Z
The following Verus program generates a mysterious warning about if statements in patterns:
% cat warning.rs
use vstd::prelude::*;

verus! {
    spec fn f(i: u64, j: int) -> bool { true }

    fn main() {
        for i in 0..1u64
            invariant
                forall |j: int| #[trigger] f(i, j)
        {
        }
    }
}
% verus warning.rs
WARNING: (2693,6): 'if' cannot be used in patterns.
WARNING: (2763,15): 'if' cannot be used in patterns.
WARNING: (2826,1): 'if' cannot be used in patterns.
WARNING: (2924,1): 'if' cannot be used in patterns.
verification results:: 2 verified, 0 errors

Closing comment (2025-04-10T16:59:02Z): correction: not a duplicate of #740
Repository: verus-lang/verus

Issue #705: Variable shadowing is reported unsupported when associated type is used
Created: 2023-07-24T23:39:31Z
I wrote a proof function which is roughly like:
pub proof fn lemma_x<K: ResourceView, R: Reconciler<K>>(
    spec: TempPred<State<K, R>>, cr: K, state: R::T, next_state: R::T
)
    requires
        ..., // some preconditions
    ensures
        ..., // some postconditions
{
    let filter = |s: R::T| { s == next_state };
    temp_pred_equality(
        lift_state(at_reconcile_state::<K, R>(cr.object_ref(), next_state)),
        lift_state(at_expected_reconcile_states::<K, R>(cr.object_ref(), filter))
    );
    lemma_y::<K, R>(spec, cr, state, filter);
}

Here the trait Reconciler takes a generic K and the trait also has an associated type T which is the type of the two parameters state, next_state.
And the verifier complains the following:
error: variable shadowing not yet supported
   --> kubernetes_cluster/proof/controller_runtime_liveness.rs:323:28
    |
323 |     let filter = |s: R::T| { s == next_state };
    |                            ^^^^^^^^^^^^^^^^^^^

I am a bit confused because I can't see variable shadowing here.
Plus, we previously made T also a generic to Reconciler and at that time the verification went through. The verification fails after we change it into an associated type.
We need some help on this. Please let me know if you need more information.

Duplicate issue #758: Panic or strange error message when using `Seq<Tracked<S>>`
Created: 2023-08-16T22:47:35Z
The following code causes a verifier panic: thread 'rustc' panicked at 'internal error: ill-typed AIR code: name vstd!seq.Seq<main!S.>. is already in scope', rust_verify\src\verifier.rs:334:17:
    pub struct S
    {
    }

    pub proof fn bug(ps: Seq<&Tracked<S>>)
        ensures
            ps.map(|_i: int, p: &Tracked<S>| p@).len() >= 0
    {
    }

The following similar code yields the strange message error: variable shadowing not yet supported:
    pub struct S { }

    pub proof fn bug(ps: Seq<&Tracked<S>>)
        ensures
            ps.map(|_i: int, p: &Tracked<S>| p).len() >= 0
    {
    }

Even if the reference to the tracked object is never referred to in the closure, we still get the strange message error: variable shadowing not yet supported:
    pub struct S
    {
    }

    pub proof fn bug(ps: Seq<&Tracked<S>>)
        ensures
            ps.map(|i: int, _p| i).len() >= 0
    {
    }

Closing comment (2023-08-28T14:40:03Z): Probably related to #705
For collections of tracked objects, vstd best supports the use of Map<K, V> where V is some tracked type. Also, it's generally recommended to keep the Tracked< ... > on the outside, where it can be easily peeled off.
Repository: verus-lang/verus

Issue #1582: Verus panics in `lifetime-generate` when the `rsa` crate is imported
Created: 2025-04-09T00:36:04Z
Reproducing crate attached, or can manually reproduce. After cargo verus new --lib <LIB_NAME>, in lib.rs, add the following line:
use rsa;

and then in Cargo.toml add the following line to the [dependencies]:
rsa = "0.7.2"

Or any other version of rsa seems to cause the issue too.
Then just run cargo verus verify (or manually invoke verus passing appropriate compiled dependencies). This results in the following panic:
[rust_verify/src/lifetime_generate.rs:560:13] ty = dyn [Binder { value: Trait(rsa::signature::digest::DynDigest), bound_vars: [] }] + 'static
thread 'rustc' panicked at rust_verify/src/lifetime_generate.rs:561:13:
unexpected type
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I'm not sure why just importing a crate without even using it anywhere should cause Verus to crash---I don't think I told Verus to attempt to verify or examine rsa.

Duplicate issue #1597: Crash when project depends on dyn_clone
Created: 2025-04-16T20:19:19Z
Running cargo verus verify (using commit ec90cbaf857ab4f55f8a64f6b411554d51e73dab) on a project that depends on dyn_clone results in an internal Verus error, even when definitions from dyn_clone are not referenced in verified code:
$ cargo verus verify
   Compiling verus_sample v0.1.0
[rust_verify/src/lifetime_generate.rs:561:13] ty = dyn [Binder { value: Trait(dyn_clone::DynClone), bound_vars: [] }, Binder { value: AutoTrait(DefId(2:3407 ~ core[fafc]::marker::Sync)), bound_vars: [] }, Binder { value: AutoTrait(DefId(2:27213 ~ core[fafc]::marker::Send)), bound_vars: [] }] + 'clone/#0
thread 'rustc' panicked at rust_verify/src/lifetime_generate.rs:562:13:
unexpected type
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: could not compile `verus_sample` (bin "verus_sample")

This is src/main.rs:
use vstd::prelude::*;
#[allow(unused)]
use dyn_clone::DynClone;

verus! {
fn main() {
}
}

Here's the corresponding Cargo.toml:
[package]
name = "verus_sample"
version = "0.1.0"
edition = "2021"

[dependencies]
vstd = { path = "../verus/source/vstd" }
builtin = { path = "../verus/source/builtin" }
builtin_macros = { path = "../verus/source/builtin_macros" }
dyn-clone = "1.0.19"

[package.metadata.verus]
verify = true

As a workaround, it seems to work to add TyKind::Dynamic(..) => Box::new(TypX::Never), in lifetime_generate::erase_ty but I'm pretty sure that that's not the right fix and only works because dyn_clone is not actually used for any verified code.

Closing comment (2025-04-16T20:54:02Z): This seems related to #1582
Repository: verus-lang/verus

Issue #839: error: `use` import is not supported in `trait`s or `impl`s
Created: 2023-10-04T11:50:29Z
Due to erasure. Discovered by @jonhnet and @tenzinhl.
@tenzinhl minimal reproducing example from https://verus-lang.zulipchat.com/#narrow/stream/399078-help/topic/error.3A.20.60use.60.20import.20is.20not.20supported.20in.20.60trait.60s.20or.20.60impl.60s/near/394718451
        use state_machines_macros::state_machine;

        state_machine!{ MachineWithProof {
        fields {
            pub x: int,
        }

        // If the `pub` access specifier is added then the error message goes away
        proof fn truey()
            ensures true
        {
            assume(false);
        }
        } }

Duplicate issue #823: reveal_with_fuel doesn't work inside state_machine! macro
Created: 2023-09-20T20:29:07Z
[2023-09-20-13-28-11.zip](https://github.com/verus-lang/verus/files/12677314/2023-09-20-13-28-11.zip)
error: unexpected token
   --> src/allocation_layer/AllocationJournal_v.rs:468:101
    |
468 | ...n_Journal::State::build_lsn_au_index_au_walk, 10 );
    |                                                ^

Closing comment (2023-10-05T01:30:02Z): I fixed the comma token problem. However, it doesn't entirely resolve the issue; we now get the strange:
error: `use` import is not supported in `trait`s or `impl`s

Which I'm guessing is related to #839
Repository: verus-lang/verus

Issue #1437: Stable release or "latest" tag?
Created: 2025-02-06T21:36:34Z
Hello!
I need to automate the installation of verus on a linux machine, and the fact your are using a rolling release makes pinning a particular tag/commit not possible (as the older releases are deleted). Would it be possible to keep the latest release under a consistent tag, such that I can reliably pull it from a script?
Specifically, instead of wget https://github.com/verus-lang/verus/releases/download/release%2Frolling%2F0.2025.02.06.cec767d/verus-0.2025.02.06.cec767d-x86-linux.zip one could do https://github.com/verus-lang/verus/releases/download/latest/verus-latest-x86-linux.zip
The goal is to automatically install the latest version of verus.

Duplicate issue #1493: Support Stable Release?
Created: 2025-03-05T17:15:20Z
Currently, Verus binaries are released on a rolling basis, with only the latest version available. However, we often develop against a fixed version of Verus to avoid disruptions caused by updates breaking our pipelines. Would it be possible to introduce versioned stable release tags or provide access to past rolling release binaries?

Closing comment (2025-03-27T21:43:06Z): Duplicate of #1437.
Repository: verus-lang/verus

Issue #657: Functions with `#[verifier(external_body)]` should not be transformed by the syntax macro
Created: 2023-06-29T19:42:15Z
This currently causes issues with using e.g. assert! in bodies of trusted #[verifier(external_body)] functions inside the verus macro.
Discovered by @jialin-li and @hayley-leblanc.

Duplicate issue #1151: Verus checking code in some `external_body` functions
Created: 2024-05-31T17:51:56Z
Hi folks, I'm writing some code involving MaybeUninit in external_body functions and have found that Verus is incorrectly checking the bodies of some of these functions. The specific case I encountered involves obtaining a mutable reference to a MaybeUninit object; attempting to verify an external_body function that does this results in a verification error about &mut not being supported.
An example of such a function that does not verify:
#[verifier::external_body]
fn test_maybe_uninit() {
    let mut maybe_uninit: MaybeUninit<u64> = MaybeUninit::uninit();
    let mut bytes: &mut [MaybeUninit<u8>] = maybe_uninit.as_bytes_mut();
    let new_bytes: [u8; 8] = [0, 0, 0, 0, 0, 0, 0, 0];
    MaybeUninit::write_slice(bytes, &new_bytes);
}

Attempting to verify this function results in error: The verifier does not yet support the following Rust feature: &mut types, except in special cases.
This does not happen with all external_body functions involving mutable references; for example, this function verifies as expected:
#[verifier::external_body]
fn test_vec() {
    let mut vec = vec![1, 2, 3];
    let mut bytes: &mut [u8] = vec.as_mut_slice();
    let new_bytes: [u8; 3] = [0, 0, 0];
    bytes.copy_from_slice(&new_bytes);
}

Both functions are implemented at https://play.verus-lang.org/?version=stable&mode=basic&edition=2021&gist=a677a25cc24042da30e69c076811d4c1
I also noticed that removing #[verifier::external_body] from test_maybe_uninit() results in a different error: error: The verifier does not yet support the following Rust feature: &mut dereference in this position (note: &mut dereference is implicit here)

Closing comment (2024-05-31T18:43:32Z): This may be related to #657 .
Repository: verus-lang/verus

Issue #392: invalid AIR for let-assignment with function-returning-unit
Created: 2023-02-23T20:49:58Z
fn returns_nothing(a: u8, b: u8)
    requires a == b,
    ensures a == b,
{
}

fn test() {
    let x = returns_nothing(0, 0);
}

Gives invalid AIR in expected 2 arguments, found 3 arguments' in expression '(ens%returns_nothing. 0 0 x~8@)'

Duplicate issue #497: Ill-typed AIR for unit variable when trait execution
Created: 2023-04-10T18:43:46Z
Consider:
use vstd::prelude::*;

verus! {

    trait Foo {
        exec fn foo(&self);
    }

    struct X;

    impl Foo for X {
        exec fn foo(&self) {
            // do nothing
        }
    }

    exec fn bar() {
        let z: X = X;
        let x: () = z.foo();
    }

}

fn main() {}
Produces:
$ rust-verify.sh --release a.rs
note: verifying root module

thread 'rustc' panicked at 'internal error: generated ill-typed AIR code: error 'in call to %Poly%tuple%0., argument #1 has type "tuple%0." when it should have type "Poly"' in expression '(%Poly%tuple%0. (tuple%0./tuple%0))'', rust_verify/src/verifier.rs:375:21
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
@Chris-Hawblitzel this is the minimized reproducer for the bug we mentioned a short while ago (not particularly high priority btw, since the fix is to just not have the trivial let binding)

Closing comment (2023-04-10T18:46:07Z): I think this is a duplicate of #392. The trait isn't actually necessary for the bug.
Repository: vikejs/vike

Issue #1400: Unwarranted client router import warning when using server routing
Created: 2024-01-02T09:29:18Z
Description
During development I get the error "[vike][Warning] You shouldn't import { something } from 'vike/client/router'", even if I'm not using anything related to client routing.
Both assert client and server routing are called even when only using server routing, and the call to the former results in the warning in the latter. The client side routing assertion seems to be coming from this file: 
  
    
      vike/vike/shared/route/utils.ts
    
    
         Line 9
      in
      5562903
    
  
  
    

        
          
           assertClientRouting() 
        
    
  


Versions:
"vite": "4.3.9",
"vike": "0.4.153",

Duplicate issue #1401: Unwarranted client router import warning when using server routing
Created: 2024-01-02T09:29:22Z
Description
During development I get the error "[vike][Warning] You shouldn't import { something } from 'vike/client/router'", even if I'm not using anything related to client routing.
Both assert client and server routing are called even when only using server routing, and the call to the former results in the warning in the latter. The client side routing assertion seems to be coming from this file: 
  
    
      vike/vike/shared/route/utils.ts
    
    
         Line 9
      in
      5562903
    
  
  
    

        
          
           assertClientRouting() 
        
    
  


Versions:
"vite": "4.3.9",
"vike": "0.4.153",

Closing comment (2024-01-02T09:30:18Z): Unintended duplicate of #1400
Repository: vikejs/vike

Issue #1341: `vike.config.js`
Created: 2023-12-09T15:30:31Z
Description
Some settings are inherently global (e.g. all pre-rendering settings). It would be nice for the user to define these in a vike.config.js instead of vite.config.js.
We may need this for #562, thus labeling as https://github.com/vikejs/vike/labels/server%20%F0%9F%8C%90.
We'll also need this for #341.

Duplicate issue #1408: `vike.config.js`
Created: 2024-01-03T20:54:50Z
Description
For settings and hooks that are global.

Closing comment (2024-03-06T11:20:03Z): Duplicate of #1341.