primordic/IssueDupesLite huggingface dataset:
Repository: ethereum-mining/ethminer

Issue #154: Duplicate repositories are confusing users
Created: 2017-07-14T11:52:41Z
We have currently two repositories:

Genoil's cpp-ethereum "ethminer": https://github.com/Genoil/cpp-ethereum
This new repository here: https://github.com/ethereum-mining/ethminer

The code is not the same. One repo contains commits that are 17 days old, the other contains code that is 7 days old.
As you can see there are new pull requests in both repositories so the users don't know where to submit them.
Please clarify which repository will contain the newest code and which is obsolete. Please also change the README of the obsolete repository to let the user know what repository should be used.
Please also check all pull requests of all repositories to be sure that all user-improvements are included inside the newest version.
@chfast Can you explain what is happening here? What is the best and newest repo?

Duplicate issue #157: What's the difference between this fork and Genoil's?
Created: 2017-07-15T06:38:21Z

Closing comment (2017-07-18T13:24:10Z): Duplicate of #154.
Repository: ethereum-mining/ethminer

Issue #346: Benchmarking RX 570 produces OpenCL Error: clSetKernelArg -49
Created: 2017-10-08T14:06:25Z
My machine:
Ubuntu 16.04.3 LTS 4.10.0-35-generic #39~16.04.1-Ubuntu SMP x86_64
AMDAPPSDK version 3.0 installed
Same results with amdgpu-pro drivers 17.30.465504 installed or not installed.
I have ethminer version 0.12.0rc3 running successfully with command line:
ExecStart=/usr/local/bin/ethminer --farm-recheck 200 -G -RH -SP 1 -S us1.ethermine.org:4444 -FS us2.ethermine.org:4444 -O <ether_address>.<rig_name>:x --cl-local-work 256 --cl-global-work 16384 --api-port 3344 --work-timeout 40 --verbosity 9

The -SP 1 was unexpected since it is not recommended for ethermine.
Output of benchmark test:
$ ethminer -G -M -v 9
  ℹ  09:53:29|ethminer  Found suitable OpenCL device [ Ellesmere ] with 6205165568  bytes of GPU memory
Benchmarking on platform: CL
Preparing DAG for block #0
 cl  09:53:29|cl-0      No work. Pause for 3 s.
Warming up...
 cl  09:53:32|cl-0      New work: header #50c856ae… target 0000000000000002000000000000000000000000000000000000000000000000
 cl  09:53:32|cl-0      New seed #00000000…
 cl  09:53:32|cl-0      Platform: AMD Accelerated Parallel Processing
 cl  09:53:32|cl-0      Device:   Ellesmere  / OpenCL 1.2 AMD-APP (2442.7)
 cl  09:53:33|cl-0      Build info: 
 cl  09:53:33|cl-0      Creating light cache buffer, size 16776896
 cl  09:53:33|cl-0      Creating DAG buffer, size 1073739904
 cl  09:53:33|cl-0      Loading kernels
 cl  09:53:33|cl-0      Writing light cache buffer
 cl  09:53:33|cl-0      Creating buffer for header.
 cl  09:53:33|cl-0      Creating mining buffer
 cl  09:53:33|cl-0      Generating DAG
 cl  09:53:34|cl-0      DAG 0 %
...
 cl  09:53:42|cl-0      DAG 93 %
 cl  09:53:42|cl-0      Switch time 13610 ms / 10611438 us
Trial 1... 3987779
Trial 2... 4197452
Trial 3... 4406663
Trial 4... 4407104
Trial 5... 4511583
  ✘  09:53:59|cl-0      OpenCL Error: clSetKernelArg -49

Duplicate issue #727: New error in 14.0.dev1 after a few hours
Created: 2018-02-11T05:00:20Z
I get this now after a few hours of mining, this one after around 2:40...

✘  02:41:53|getwork   Failed getting work!
ℹ  02:41:53|getwork   Disconnected from http://127.0.0.1:8545
ℹ  02:41:53|getwork   Shutting down miners...
✘  02:41:53|cl-0      OpenCL Error: clSetKernelArg: CL_INVALID_ARG_INDEX (-49)
m  02:41:58|ethminer  not-connected
cl  02:42:00|cl-1      Build info:
cl  02:42:00|cl-1      Creating light cache buffer, size 25165376
cl  02:42:00|cl-1      Creating DAG buffer, size 1610610304
cl  02:42:00|cl-1      Loading kernels
cl  02:42:00|cl-1      Writing light cache buffer
[end of log]

Closing comment (2018-02-11T05:10:25Z): Duplicate of #346, closing and raising there.
Repository: ethereum-mining/ethminer

Issue #888: ethminer stops reporting hashrate to the pool after couple hours
Created: 2018-03-13T17:41:14Z
Running ethminer version 0.14.0.dev3+git.de05cc3
Build: linux/release/gnu
the -RH option is specified and the hashrate reporting works for a while but then just stops working. Please see the image below from ethermine

Duplicate issue #912: dev4 is loosing report hashrate after few hours
Created: 2018-03-21T07:47:53Z
I'm on Ubuntu and even miner is running great and continues mining, after few hours ethminer stops reporting hashrate to pool. My other rigs running the same version are reporting hashrate forever without loosing it. It just happens only on one rig

Closing comment (2018-03-21T16:13:52Z): duplicate #888
fixing attempts #897
Repository: ethereum-mining/ethminer

Issue #366: std::out_of_range exception
Created: 2017-11-04T18:24:13Z
I have several miners with 6 cards each and am getting an exceptions on at least one of them every 24 hours.  It's always the same.  The log output from ethminer is attached.
ESC[32m  m  ESC[35m03:36:35ESC[0mESC[30m|ESC[34methminerESC[0m  Speed ESC[1;36m 92.82ESC[0m Mh/s    gpu/0 ESC[36m15.07ESC[0m  gpu/1 ESC[36m14.88ESC[0m  gpu/2 ESC[36m19.17ESC[0m  gpu/3 ESC[36m14.69ESC
[0m  gpu/4 ESC[36m14.50ESC[0m  gpu/5 ESC[36m14.50ESC[0m  [A7383+70:R0+0:F0] Time: 108:13ESC[0m
ESC[32m  m  ESC[35m03:36:35ESC[0mESC[30m|ESC[34methminerESC[0m  Speed ESC[1;36m 92.82ESC[0m Mh/s    gpu/0 ESC[36m15.07ESC[0m  gpu/1 ESC[36m14.88ESC[0m  gpu/2 ESC[36m19.17ESC[0m  gpu/3 ESC[36m14.69ESC
[0m  gpu/4 ESC[36m14.50ESC[0m  gpu/5 ESC[36m14.50ESC[0m  [A7383+70:R0+0:F0] Time: 108:13ESC[0m
ESC[32m  m  ESC[35m03:36:35ESC[0mESC[30m|ESC[34methminerESC[0m  Speed ESC[1;36m 92.82ESC[0m Mh/s    gpu/0 ESC[36m15.07ESC[0m  gpu/1 ESC[36m14.88ESC[0m  gpu/2 ESC[36m19.17ESC[0m  gpu/3 ESC[36m14.69ESC
[0m  gpu/4 ESC[36m14.50ESC[0m  gpu/5 ESC[36m14.50ESC[0m  [A7383+70:R0+0:F0] Time: 108:13ESC[0m
ESC[32m  m  ESC[35m03:36:35ESC[0mESC[30m|ESC[34methminerESC[0m  Speed ESC[1;36m 92.82ESC[0m Mh/s    gpu/0 ESC[36m15.07ESC[0m  gpu/1 ESC[36m14.88ESC[0m  gpu/2 ESC[36m19.17ESC[0m  gpu/3 ESC[36m14.69ESC
[0m  gpu/4 ESC[36m14.50ESC[0m  gpu/5 ESC[36m14.50ESC[0m  [A7383+70:R0+0:F0] Time: 108:13ESC[0m
ESC[94m  ℹ  ESC[35m03:36:35ESC[0mESC[30m|ESC[34mstratum ESC[0m  Received new job #1bb0266eESC[0m
ESC[94m  ℹ  ESC[35m03:36:36ESC[0mESC[30m|ESC[34mCUDA0   ESC[0m  set work; seed: #cfa3e37c, target: ESC[0m #00000000dbe6ESC[0m
ESC[94m  ℹ  ESC[35m03:36:36ESC[0mESC[30m|ESC[34mCUDA1   ESC[0m  set work; seed: #cfa3e37c, target: ESC[0m #00000000dbe6ESC[0m
ESC[94m  ℹ  ESC[35m03:36:36ESC[0mESC[30m|ESC[34mCUDA2   ESC[0m  set work; seed: #cfa3e37c, target: ESC[0m #00000000dbe6ESC[0m
ESC[94m  ℹ  ESC[35m03:36:36ESC[0mESC[30m|ESC[34mCUDA3   ESC[0m  set work; seed: #cfa3e37c, target: ESC[0m #00000000dbe6ESC[0m
ESC[94m  ℹ  ESC[35m03:36:36ESC[0mESC[30m|ESC[34mCUDA4   ESC[0m  set work; seed: #cfa3e37c, target: ESC[0m #00000000dbe6ESC[0m
ESC[94m  ℹ  ESC[35m03:36:36ESC[0mESC[30m|ESC[34mCUDA5   ESC[0m  set work; seed: #cfa3e37c, target: ESC[0m #00000000dbe6ESC[0m
terminate called after throwing an instance of 'std::out_of_range'
  what():  vector::_M_range_check: __n (which is 6) >= this->size() (which is 6)

Duplicate issue #1123: Error: vector::_M_range_check
Created: 2018-05-18T16:38:20Z
Recently, I've been getting this error every few days on my 6x1060 system my with a conservative overclock/undervolt (core +50, memory +300, max power 60w). I'm using Ethminer 0.13.0 stable release on Antegros Linux.

Closing comment (2018-05-21T14:04:53Z): Duplicate of #366.
Repository: evidence-dev/evidence

Issue #382: Value component treats dates differently to other components
Created: 2022-08-15T16:26:10Z
Bug Description
Value component returns different dates to other components
Expected Behavior
Value component returns the same date as other components
Error Messages and Screenshots

Steps To Reproduce
https://stackblitz.com/edit/evidence-k2rxhd?file=pages%2Findex.md
Database:

 SQLite (but I think to would affect all)

Duplicate issue #356: Dates without timezones display incorrectly during formatting
Created: 2022-07-21T16:23:25Z
In timezones outside UTC, passing a date without a timezone will assume UTC, which can lead to unexpected outcomes.
Steps to reproduce
```usage_data
select '2022-06-06' as usage_mmm
```

<Value data={usage_data} column=usage_mmm/>

should display Jun, Instead displays May.
Why
If the date doesn’t have a timezone associated with it, JS date assumes UTC timezone in the backend.
So 2022-06-01 would be 2022-06-01 0:00 UTC
At the time of presenting, JS will look at the timezone on the browser and apply it.
If you are in EST, 2022-06-01 0:00 UTC becomes 2022-05-31 19:00 EST
The month extracted from that would hence be May.

Closing comment (2022-09-21T20:20:58Z): Closing this because the solution will be the same as #382
Repository: evidence-dev/evidence

Issue #2179: [Bug]: Dropdown containing `null` will not load
Created: 2024-07-02T16:24:41Z
Describe the bug
If the query feeding a dropdown component contains a null value, the input will not be set, even if a default value is supplied.
Steps to Reproduce
Reproducible example below. If null is included in the selection query, the DataTable will not load. If you change that to "def", it will load.
```sql selection
select 'abc' as option
union all
select null as option
union all
select 'ghi' as option
```

<Dropdown data={selection} name=withnulls value=option defaultValue=ghi/>

```sql filtered
select * from (
select 'abc' as option, 100 as sales
union all
select 'def' as option, 200 as sales
union all
select 'ghi' as option, 300 as sales
)
where option = '${inputs.withnulls.value}'
```

<DataTable data={filtered}/>

Logs
No response
System Info
No response
Severity
annoyance
Additional Information, or Workarounds
Workaround by filtering nulls out of the query feeding the dropdown

Duplicate issue #2215: [Bug]: DropDown component breaks when one of the value is `null`
Created: 2024-07-14T13:54:09Z
Describe the bug
The Dropdown component cannot select value of one of the option contains a value null.
Steps to Reproduce
SELECT *  FROM (VALUES (null),('Hello world'),('Hello world')) t1  (repo)

Logs
@evidence-dev_core-components.js?v=07564e1d:206600 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'toString')
    at @evidence-dev_core-components.js?v=07564e1d:206600:57
    at Array.sort (<anonymous>)
    at hygiene (@evidence-dev_core-components.js?v=07564e1d:206585:25)
    at @evidence-dev_core-components.js?v=07564e1d:206706:14
    at Object.update (chunk-TSNIGPV6.js?v=07564e1d:38:9)
    at select (@evidence-dev_core-components.js?v=07564e1d:206692:13)
    at @evidence-dev_core-components.js?v=07564e1d:206753:9


### System Info

_No response_

### Severity

serious, but I can work around it

### Additional Information, or Workarounds

Filter out null values in query but it might not be workable in all scenarios

Closing comment (2024-07-15T15:52:39Z): Closing as duplicate of #2179, thanks for flagging
Repository: evidence-dev/evidence

Issue #121: Vite SSR Errors
Created: 2021-09-03T15:11:47Z
Several users are seeing errors from Vite related to SSR. These issues are detailed here: sveltejs/kit#2086. One example is vitejs/vite#3953.
There should be a workaround until those are fixed by using older package versions, which work for running an Evidence project. Specific versions to be added to docs.

Duplicate issue #109: New pages return 404 on page refresh and direct navigation, but load when navigated from another page
Created: 2021-08-29T14:56:22Z
After adding a new page to the src/pages directory, page won't load on direct navigation or on page refresh. Page loads when clicked through from another page.

Closing comment (2021-09-04T15:56:48Z): Underlying issue here is related to #121. Can be fixed by restarting dev server.
Repository: evidence-dev/evidence

Issue #603: Deploy Evidence to non-root path / folder
Created: 2023-01-27T17:52:25Z
Evidence Maintainer Edit
Non-root paths are not supported, but we are keeping this issue up to date as we frequently get asked about this.
You may want to consider the following alternative options:

deploying to a subdomain: subdomain.yourwebsite.com
embedding Evidence inside your app: using an iframe or similar on your desired subfolder

It is possible we will support non-root paths in the future, but it is not on the near term roadmap. Below are some workarounds though they are likely to be fragile.
Feature Description
I would like to override sveltekit's base URI and others settings like outDir when I run evidence build. The documentation of sveltekit  suggests to use svelte.config.js,
Goal of Feature
I would like to deploy a static evidence's build on Github Pages or something equivalent. Github Pages requires the urls to be relative or following the URI of the repository, so I need to set the sveltekig --base parameter. But it is not suffisant because the URIs in the Evidence.dev html (ex /favicon.ico) are all hard coded to point to the root "/".
Current Solution
The current source code in cli.js does not allow to override svelte.config.js, it overrides the svelte.config.js everytime we run evidence build
So my current solution is using unix's find to track all urls
mv -R ./build ./public
find ./public/* -type f -not -path '*.ico' -exec sed -i '' "s,=\"/,=\"/my_github_uri/,g" {} +

Duplicate issue #1527: Support deploying to a subpath 
Created: 2024-01-26T11:10:16Z
Steps To Reproduce
I started deploying Evidence on my project site, doing some manual copying to put the Evidence build output into a subpath (/reports).
When loading the deployed Evidence reports (/reports), I'm getting 404s as Evidence looks for all those files in domain.com/_app/immutable/ instead of domain.com/reports/_app/immutable/.
Extra Context

Steps I'm running to deploy
Deployed site with errors

Environment

Node version (node -v): v18.19.0
npm version (npm -v): 10.2.3
OS: Ubuntu 22.04
Browser: Brave
Database: DuckDB

Closing comment (2024-02-21T12:20:19Z): @srenatus
I'm going to close this issue as it's a duplicate of #603 and it's confusing to have both open right now!
#603 has a linked PR which explains why this is hard / suboptimal to support
Repository: evidence-dev/evidence

Issue #2193: [Feature]: Support selecting multiple dimensions in dimension grid
Created: 2024-07-08T12:58:38Z
Description
Support selecting multiple of the same dimension in dimension grid
What problem would this solve?
I want to select three provinces as a group and include them in a filter selection
How should it work?
UI:
Either shift click enables selecting multiple dimensions or just clicking a second one is supported.
API:
boolean multiple prop defaulted to false, same as drop down
input store:
multiple province dimensions selected: (province = 'ontario' or province = 'quebec') and language = 'en'

Duplicate issue #2138: Feature Request: Add multiselect capabilities to `DimensionGrid`
Created: 2024-06-20T14:53:17Z

Closing comment (2024-07-15T13:22:55Z): Dupe #2193
Repository: evidence-dev/evidence

Issue #1476: ECharts component has regressions
Created: 2024-01-09T15:50:42Z
See #1431

Support reactivity in Echarts component
Allow users to use query names, rather than data: [...queryname]
Test cases: https://docs.evidence.dev/components/custom-echarts

Duplicate issue #1494: Regression: query data is not accessible using `{my_query}`
Created: 2024-01-15T21:28:46Z
Steps To Reproduce
```sql my_query
select * from orders limit 10
```

{JSON.stringify(my_query)}

Expected Behavior
data array, eg
[{"id":1,"order_datetime":"2020-06-08T16:13:42.000Z","order_month":"2020-06-01T00:00:00.000Z","first_name":"Tracey","last_name":"Coppard","email":"tcoppard0@ameblo.jp","address":"2 Mosinee Trail","state":"Minnesota","zipcode":55417,"item":"Model Racehorse","category":"Sinister Toys","sales":12.35,"channel":"Google Paid","channel_group":"Paid Search","channel_month":"Google Paid2020-06-01"},{"id":2,"order_datetime":"2019-12-11T07:01:08.000Z","order_month":"2019-12-01T00:00:00.000Z","first_name":"Noland","last_name":"Kupka","email":"nkupka1@samsung.com","address":"840 Cordelia Crossing","state":"Texas","zipcode":77223,"item":"Microscope","category":"Odd Equipment","sales":129.6,"channel":"Tiktok Ads","channel_group":"Social","channel_month":"Tiktok Ads2019-12-01"}]

Actual Behaviour
{"opts":{"noResolve":false},"__isQueryStore":true,"hash":"18bem6o","id":"orders"}

Workarounds
use {[...my_query]} to access the data

Closing comment (2024-02-05T22:28:27Z): same as #1476
Repository: evidence-dev/evidence

Issue #121: Vite SSR Errors
Created: 2021-09-03T15:11:47Z
Several users are seeing errors from Vite related to SSR. These issues are detailed here: sveltejs/kit#2086. One example is vitejs/vite#3953.
There should be a workaround until those are fixed by using older package versions, which work for running an Evidence project. Specific versions to be added to docs.

Duplicate issue #15: Windows support
Created: 2021-08-03T18:28:14Z

Closing comment (2021-09-15T13:12:15Z): Related to #121
Repository: evidence-dev/evidence

Issue #412: Support Dual (Secondary / Multiple) Y-Axes
Created: 2022-09-15T15:45:32Z
Feature Description
Dual Axis support, for <Chart> components: <BarChart>, <LineChart>, <AreaChart>

Goal of Feature
What would this feature help you accomplish?
Increase the density of information you can display. Often combines a bar chart with a line chart, for example.
Current Solution
Two charts with separate axes
Alternative Ideas
Support Side by side - two charts in one row, would also allow for higher information density

Duplicate issue #404: Multiple y axis support
Created: 2022-09-08T20:13:40Z
Be able to have two y-axes with different scales for different series.
For example:

Closing comment (2022-09-21T20:21:55Z): Closing as duplicate of #412
Repository: evidence-dev/evidence

Issue #1018: BigValue Format Tag Error on data update
Created: 2023-07-10T14:48:12Z
The most basic way to reproduce:
<script>
  import { BigValue } from '@evidence-dev/core-components';

  let testData = [{ test: 1 }];
  setTimeout(() => {
    testData = [{ test: 2 }];
  }, 1000);
</script>

<BigValue data={testData} value="test" />


on the second render (after the 1000ms timeout), I get an exception:
Uncaught (in promise) potentialFormatTag.toLowerCase is not a function

Duplicate issue #1019: BigValue is breaking for data modified after page load
Created: 2023-07-10T15:12:37Z
Steps To Reproduce
<script>
  import { BigValue } from '@evidence-dev/core-components';

  let testData = [{ test: 1 }];
  setTimeout(() => {
    testData = [{ test: 2 }];
  }, 1000);
</script>

<BigValue data={testData} value="test" />
Expected Behavior
Bigvalue renders 1 and then after 1s, shows a 2
Actual Behaviour
Uncaught (in promise) potentialFormatTag.toLowerCase is not a function

Closing comment (2023-07-10T15:38:39Z): dupe (#1018)
Repository: evidence-dev/evidence

Issue #1479: Unset input values are always in a loading state
Created: 2024-01-10T19:51:36Z
Current behavior is an input value that is unset freezes the QueryStore to prevent errors; this is an intentional behavior.
The problem comes from inputs like ButtonGroup that may not have a default value, or where no selection (and no value) is a valid choice.
We should adjust the behavior to enter the "forever loading" state when the input value is undefined, and we should pass along null. null is an intentional empty where undefined is unintentional.
Components that do not need a default or initial value are responsible for setting their input key to null, Evidence should not handle this.

Duplicate issue #1480: Input nulls cause queries to not execute
Created: 2024-01-10T20:04:48Z
Steps To Reproduce
Navigate to https://mdsinabox.com/nba/teams/
view the query filtered_summary_by_team
Inspect the SQL

Expected Behavior
The user has not selected a button yet, so the input result is null, and returns the expected query results for if '${inputs.my_input}' was null
Actual Behaviour

The query does not return data and so remains in a loading state
Workarounds
Create an {#if} block before the results are available, returning different data. See the source code

Closing comment (2024-01-10T21:09:53Z): Duplicate of #1479
Repository: expo/router

Issue #320: Multiple re-renders on _layouts and pages.
Created: 2023-02-25T01:57:53Z
Summary
Main Issue
I noticed that my screen is triggering the initial useEffect twice. I was suspecting that some upper level component was unmounting and mounting again, but turns out that the _layout.tsx file is rendering more than once.
Details
My currently structure is the following:
app/
    _layout.tsx (<Slot />)
    (auth)
    (app)
        index.tsx (with a redirect to home/index)
        _layout.tsx (<Slot />)
        (tabs)
            _layout.tsx (<Tabs />)
            home/
                _layout.tsx (<Stack />)
                index.tsx            
         lives/
            [liveId].tsx
            _layout.tsx (<Stack />)

Logs
When I reload my app and the router put me at the logged index, these were the renders that happened:

Why app/(app)/_layout.tsx rendered 3 times and app/(app)/home/ndex.tsx rendered twice?
I understand that the first render of the layout is related to the (app)/index that does the redirect. Another is related to the screen I was redirected to. But what about the third time? I also noticed that it is not being remounted because does not trigger the unmount of the useEffect.
Minimal reproducible example
My app/(app)/_layout.tsx for reference:
import { Slot } from "expo-router";
import { useEffect } from "react";

export default function AppLayout() {
  console.log('rendering AppLayout');

  useEffect(() => {
    return () => {
      console.log('AppLayout unmount');
    };
  }, []);
  return (
    <Slot />
  );
};

Duplicate issue #523: Web useSearchParams bug. useSearchParams populated with first old values when moving from dynamic route to dynamic route
Created: 2023-04-28T08:37:03Z
Which package manager are you using? (Yarn is recommended)
pnpm (known issues due to Metro)
Summary
Hey.
Using expo-router with web presents bug: useSearchParams populated with first old values when moving from dynamic route to dynamic route.
Example app structure:
app/
  index.tsx
  test1/
    [id].tsx
  test2/
   [id].tsx

Explanation scenario:

Moving from '/' to '/test1/1'


React.useEffect(() => { console.log(id) }, [id]), renders twice: first with "undefined", second with "1"


Moving from '/test1/1' to '/test2/2'


React.useEffect(() => { console.log(id) }, [id]), renders twice: first with "1", second with "2"

This creates a problem for example when passed searchParam is used to fetch data according to the passed dynamic id. Now it will fetch two times,
Tried to search if this is expected or not and how to fix this but didn't find or understand there were prior issues/explanations covering this are in this package.
Thank you for this package and to whole Expo team! expo + expo-router has really been a blessing and joy in development.
Minimal reproducible example
https://github.com/fuelkoy/useSearchParamsBug

Closing comment (2023-04-29T16:53:32Z): Might be similar to #320
Repository: expo/router

Issue #131: [WEB] Attempting to load assets on nested route fails
Created: 2022-11-14T18:22:47Z
Summary
Loading assets from a 'base' route (e.g. /somepath) works correctly, loading them from /assets/[path to assets].
When attempting to load assets such as fonts from a nested path (e.g. /nested/123), the page attempts to load them from /nested/assets/[path to assets] which is incorrect and leads to the page not rendering correctly. This only happens if you visit the page URL directly, or refresh the browser while on that page.
This happens with locally-sourced assets (e.g. those hosted inside the assets folder) but also with node_modules (e.g. the expo-google-fonts packages exhibit the same behaviour).
This test was done on the web platform - I haven't explicitly tested on mobile/native as there is no way to refresh the page to trigger the bug.
For clarification, I'm unsure if this is a router-specific issue or a bundler issue. Please move to the appropriate repo if this is not the correct one.
Minimal reproducible example
https://github.com/ChronSyn/expo-router_bug-report-assetpath

Duplicate issue #216: When viewed on the web, @expo/vector-icons is not displayed in the nested router.
Created: 2023-01-22T02:19:10Z
Summary
When I try to open the Nested URL directly on the web(http://localhost:19000/memo/1),
I get the following error and the icon does not appear.
It seems to be going to the nested URL to look for the Icon file, any solution?

Minimal reproducible example
You can reproduce the following by webbuilding the following and opening the URL(localhost/nest/1 ).
https://github.com/t0m0120/expo-router-check-nested-icon

Closing comment (2023-01-22T20:58:44Z): Possibly related to #131
Repository: expo/router

Issue #768: Navigation not working with nested navigator in v2
Created: 2023-07-11T16:33:25Z
Which package manager are you using? (Yarn is recommended)
yarn
Summary
I'm not getting navigation to work whenever there's a nested navigator in my segment-group. This worked with Router 1.x + Expo 48, but did break after upgrading to Router 2 + Expo 49. Whenever I try to navigate to a page (using the Link-component from Expo Router) I get the following error:
The action 'NAVIGATE' with payload {"name":"app"} was not handled by any navigator.

Do you have a screen named 'app'?

Minimal reproducible example
https://github.com/dasovm/expo-router-issue-768

Init a new repo using the SDK 49 tabs template:
npx create-expo-app@latest --template tabs@49

Use the following type of structure in the app-directory:
- _layout.tsx
- index.tsx
- (app)
  - _layout.tsx
  - app.tsx

In (app)/_layout.tsx just use a basic layout:
import { Stack } from "expo-router";
export default Stack;
In index.tsx use the following code:
export default function IndexPage() {
  return (
    <View>
      <Link href="/(app)/app">App</Link>
    </View>
  );
}
The navigation won't work and will throw the error mentioned above. If you then remove the Stack-layout from (app)/_layout.tsx (remove the file), it will then work again.

Duplicate issue #832: Layout in nested Slot causes <Link /> to not route in v2.
Created: 2023-08-09T17:35:24Z
Which package manager are you using? (Yarn is recommended)
yarn
Summary
When converting a normal modal.tsx file to a modal folder with a _layout and index file, <Link href="/modal" /> no longer works.
Minimal reproducible example
https://github.com/austin43/expo-router-layout-routing

Closing comment (2023-08-09T19:59:34Z): Possibly related to #768.  When I pull initialRouteName out, the routing works again as expected.
Repository: expo/router

Issue #29: expo-router/entry cannot be found when local project name is "expo-router"
Created: 2022-09-29T15:30:05Z
Hello!
Love this so much! Just tried following the docs exactly and got this when running "expo start"
error: Error: While resolving module `expo-router/entry`, the Haste package `expo-router` was found. However the module `entry` could not be found within the package. Indeed, none of these files exist:

any ideas?

Duplicate issue #67: Unable to resolve module expo-router/entry
Created: 2022-10-07T22:58:29Z
Getting the following error while bundling for iOS simulator. Using pnpm.
Unable to resolve module expo-router/entry from <root>/apps/expo/index.js: expo-router/entry could not be found within the project or in these directories:
  node_modules
  ../../node_modules
  node_modules
  ../../node_modules
> 1 | import "expo-router/entry"
    |         ^
  2 |

package.json:
"dependencies": {
    "app": "workspace:*",
    "expo": "46.0.15",
    "expo-router": "^0.0.25",
    "expo-splash-screen": "~0.16.1",
    "expo-status-bar": "~1.4.0",
    "react": "18.0.0",
    "react-dom": "18.0.0",
    "react-native": "0.69.6",
    "react-native-gesture-handler": "~2.5.0",
    "react-native-reanimated": "~2.9.1",
    "react-native-safe-area-context": "4.3.1",
    "react-native-screens": "~3.15.0",
    "react-native-web": "~0.18.7"
  },
  "devDependencies": {
    "@babel/core": "^7.18.6",
    "@babel/runtime": "^7.18.6",
    "@types/react": "~18.0.0",
    "@types/react-native": "~0.69.1",
    "typescript": "^4.6.3"
  }

babel.config.js, metro.config.js and index.js:

Closing comment (2022-10-21T06:52:22Z): @META-DREAMER Did you figure out what was wrong? I have the same issue with pnpm, and it's not a duplicate of #29.
Repository: expo/router

Issue #157: Expo AuthSession (proxy) sends Android users to 404 route after authenticating
Created: 2022-12-12T16:33:21Z
Summary
When Expo Router is used in conjunction with Expo Auth Session, Android users are sent to the "Unmatched route" ([...unmatched]) screen after successfully authenticating.
Expected Behavior
Redirection to authentication callback URL schemes triggered by Expo AuthSession should not impact the router.
Other Notes
This issue doesn't impact iOS platform.
Minimal reproducible example
A repository with a minimal reproduction of the bug can be found here:
https://github.com/nderscore/expo-router-auth-demo
To reproduce the issue, follow the instructions in the README, launch the app in an Android emulator, then click on one of the "LOG IN" pressables on any screen, and then complete the authentication flow.

Duplicate issue #764: Google login with Google.useAuthRequest does not work on android as the login route is remounted after coming back from google login webpage
Created: 2023-07-10T15:59:10Z
Which package manager are you using? (Yarn is recommended)
npm version 8.5.5
Summary
When using Google.useAuthRequest API with projectNameForProxy set, after clicking login and then clicking "Yes" on this auth.expo.io page,

the google login page opens.
But after login when it is redirected to the app, nothing happens.
Upon debugging I saw that the response from the return value of useAuthRequest is null. The request object looks fine and has all the proper parameters including the redirectUri.
On iOS expo go app and web it is working perfectly fine.
It was also working fine with Expo SDK 48 and without expo-router.
Minimal reproducible example
import React from "react";
import { Pressable } from "react-native";
import * as Google from "expo-auth-session/providers/google";
import config from "../config";

export default function Login() {
  const [request, response, promptAsync] = Google.useAuthRequest(
    {
      expoClientId: config.EXPO_CLIENT_ID,
      iosClientId: config.GOOGLE_AUTH_IOS_CLIENT_ID,
      androidClientId: config.GOOGLE_AUTH_ANDROID_CLIENT_ID,
      webClientId: config.GOOGLE_AUTH_WEB_CLIENT_ID,
      responseType: ResponseType.Code,
      shouldAutoExchangeCode: false,
      extraParams: {
        access_type: "offline",
      },
    },
    { projectNameForProxy: config.PROJECT_NAME }
  );

  useEffect(() => {
    console.log({ request, response });
  }, [request, response]);

  return (
    <Pressable
      onPress={async () => {
        await promptAsync({ projectNameForProxy: config.PROJECT_NAME });
      }}
      isDisabled={!request}
    >
      Login with Google
    </Pressable>
  );
}
The console log always has proper value of request. But response is always null.

Closing comment (2023-07-17T20:28:08Z): duplicate #157
Repository: expressjs/session

Issue #425: Request: Option for refreshing the session ID
Created: 2017-02-09T14:38:14Z
Sometimes, there is the need to refresh the session ID without loosing the session data.
Examples:

Refreshing session ID after authentication (to protect against session fixation attacks)
https://www.owasp.org/index.php/Session_fixation
jaredhanson/passport#192
Manually refreshing session ID before it expires (e.g. if the user wants to keep working after the maximum session lifetime, but we do not want the same session ID to be used)

Duplicate issue #463: Change session ID
Created: 2017-05-18T20:51:31Z
I cannot currently find a way to change the SID for a certain session. I want to generate a new SID every time a user logs in, to mitigate the risk of someone being able to log into their account if they get their session. But it seems that the SID is completely static, and that is a bit of a security risk.
Is there a way to change it? If not there really should be.

Closing comment (2017-05-18T21:04:34Z): It is not a current feature. Duplicate of #425 I believe.
Repository: expressjs/session

Issue #161: Sessions In API's
Created: 2015-05-24T01:35:37Z
Note: So I am sorry if this is a duplicate of something else, but most of the issues I found relating to this are not all that helpful.
Using the RedisStore, but this is not redis specific, I was planning on sharing my sessions between a bunch of API microservices and a web app.  Obviously I don't want to use cookies for these api's, I want to use the auth header.  But the same session will also be accessed from my web app, which will use cookies.
To solve this I would like to generate a single token to act as both my cookie value and my auth header.  When my web app makes a request to an api it would just load the cookie value into the auth header.
At my work we have a session module that does this and it works great, but it is not open source.  I was hoping to get your opinion on having this module support that.  Do you like the idea?  Do you know of another module that already does this?  Is there a way to get this module to do that already that I am just stupidly missing?  I would be happy to get this working in a PR or make a proof of concept first, just let me know.

Duplicate issue #543: Cookieless Session
Created: 2018-01-23T04:31:23Z
How can we implement cookie-less session in express js? Express-session provides a way to maintain session using cookies but what if we try to use express-session without cookies? Is there any way to achieve that?

Closing comment (2022-02-13T14:53:31Z): This is the same as #161 right?
Repository: expressjs/session

Issue #10: .maxAge for the session store
Created: 2014-02-16T01:33:52Z
senchalabs/connect#371

Duplicate issue #18: Session cookie expires immediately in WebView when cookie.maxAge is set
Created: 2014-04-02T15:42:21Z
Using following configuration for express.session middleware
{
    secret : crypto.randomBytes(16).toString('hex'),
    cookie: {
      maxAge: 86400
    },  
}
Causes WebView from Android before 4.4  and iPhone 4s block the session cookie immediately after they are set.
Removing cookie.maxAge from configuration fix the issue.
Can we add a notice somewhere in the documentation?

Closing comment (2014-05-08T00:27:36Z): Maybe related to #10 ?
Repository: expressjs/session

Issue #425: Request: Option for refreshing the session ID
Created: 2017-02-09T14:38:14Z
Sometimes, there is the need to refresh the session ID without loosing the session data.
Examples:

Refreshing session ID after authentication (to protect against session fixation attacks)
https://www.owasp.org/index.php/Session_fixation
jaredhanson/passport#192
Manually refreshing session ID before it expires (e.g. if the user wants to keep working after the maximum session lifetime, but we do not want the same session ID to be used)

Duplicate issue #560: Feature request: Renew session id
Created: 2018-03-08T04:09:05Z
My goal is to change session id but make every other remain unchanged.
I think session.regenerate() will be useful. But it will destroy and re-create the session instance.
req.session.regenerate(function(err) {
    // will have a new session here
})

Can we have something like that?
req.session.regenerate(preserveData = false, function(err) {
    // will have a new session here
    // if preserveData set to true, preserve session data
})

Closing comment (2018-03-08T04:25:19Z): Definately something that has been on the docket, I believe. Duplicate of #425 I think. If you don't think this is a duplicate of that issue, I may be misunderstanding the feature request, I apologise!
Repository: expressjs/session

Issue #837: Secure Flag cannot be set for unproxied localhost
Created: 2021-07-30T13:09:09Z
Browsers consider localhost to be a secure origin (i.e. see https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies).
express-session does not. This means for my local configuration, I need to disable the Secure flag, which has other repercussions:

I cannot set the Cookie Name to __Host-sid and need to make a special-case development exception
I cannot use CORS Requests to localhost with Cookies, since non-secure Cookies aren't sent, even with SameSite=none

I understand that this is the result of express-session trying to be smart and trying to prevent sending cookies over insecure connections.
The code causing this is in index.js:
if (req.session.cookie.secure && !issecure(req, trustProxy)) {

I don't think that issecure can reliably detect if the connection attempt is secure or not for the localhost case.
I see two possible solutions:

Allow disabling the issecure check and unconditionally set the cookie (this is what I actually want, because otherwise it just silently fails)
Potentially  inspect the origin-header for localhost as a heuristic, this (should?) remain unchanged through proxies too

Duplicate issue #909: secure=true cookies don't work for localhost
Created: 2022-08-06T20:27:42Z
express-session seems to withhold sending secure cookies over HTTP, but this causes wrong behavior for localhost. MDN says secure cookies are allowed on localhost. I think the cookie should be always sent, and the browser should decide what to do with it.
const express = require('express');
const session = require('express-session');
const app = express();
app.use(session({
    secret: 'qwerqwerqwer',
    resave: true,
    saveUninitialized: true,
    cookie: {
        secure: true,
    },
}));
app.get('/hello', (req, res) => {
    res.cookie('test', 'asdf', {secure: true});
    res.send('');
});
const PORT = 7000;
app.listen(PORT, () => {
    console.log(`backend listening on port ${PORT}`);
});

res.cookie works because I see a test cookie but there is no connect.sid cookie. There is only a Set-Cookie header for test and not for connect.sid

Closing comment (2022-08-06T20:30:45Z): Hello, yes, the specs for cookies have changed since 1.0 of this module was released. When created, the specs said that secure cookies were not to be sent over insecure connections from the server, which is how this module was implemented. The newer specs remove this and browsers have additionally made it such that localhost, even http non-secure protocol, is considered secure (which it didn't use to be). There is an issue regarding this and we are tracking to change the module's behavior in 2.0.
Duplicate of #837
Repository: expressjs/session

Issue #837: Secure Flag cannot be set for unproxied localhost
Created: 2021-07-30T13:09:09Z
Browsers consider localhost to be a secure origin (i.e. see https://developer.mozilla.org/en-US/docs/Web/HTTP/Cookies#restrict_access_to_cookies).
express-session does not. This means for my local configuration, I need to disable the Secure flag, which has other repercussions:

I cannot set the Cookie Name to __Host-sid and need to make a special-case development exception
I cannot use CORS Requests to localhost with Cookies, since non-secure Cookies aren't sent, even with SameSite=none

I understand that this is the result of express-session trying to be smart and trying to prevent sending cookies over insecure connections.
The code causing this is in index.js:
if (req.session.cookie.secure && !issecure(req, trustProxy)) {

I don't think that issecure can reliably detect if the connection attempt is secure or not for the localhost case.
I see two possible solutions:

Allow disabling the issecure check and unconditionally set the cookie (this is what I actually want, because otherwise it just silently fails)
Potentially  inspect the origin-header for localhost as a heuristic, this (should?) remain unchanged through proxies too

Duplicate issue #857: Enable secure cookies over localhost
Created: 2021-12-22T12:19:02Z
I think it is reasonable to enable secure cookies on localhost, since browsers accepts them.
This simplifies development and avoid developers confusion, since now cookies are suppressed silently.
What I propose is updating isSecure:

  
    
      session/index.js
    
    
         Line 623
      in
      0048bca
    
  
  
    

        
          
           function issecure(req, trustProxy) { 
        
    
  


And add something like this:
if (req.connection.remoteAddress === '127.0.0.1' ||
    req.connection.remoteAddress === '::ffff:127.0.0.1'
) {
    return true;
}
I am opening a PR in a moment
Also see #837

Closing comment (2021-12-24T08:21:50Z): Hello, and thanks for opening this issue. It seems to be a duplicate of #837 though. I can re-open if there is elaboration on how it is not a duplicate, though.
Repository: expressjs/session

Issue #799: Session object not modifiable in typescript (while using @types/express-session)
Created: 2020-12-09T17:04:20Z
I've been using express-session in various express applications, but never with typescript.
Disclaimer: This might be a bug with @types/express-session, but I figure this is the right community to ask either way, so here's what's happening.
The session object is essentially just not modifiable, ie I can't seem to add properties to it, and, perhaps because of a recent update, all methods of fixing this I've found either don't work or just break the whole thing.
In this example use case:
router.get("/example", (req, res) => {
	console.log(req.session); // Works
	req.session.username = "mine" // Fails
	req.session.destroy(data => console.log(data)); // Works
	res.send('something')
});
I get the following error:
Property 'username' does not exist on type 'Session & Partial<SessionData>'
Not sure if this is in any way useful, but these are my session options
const sessionConfig: session.SessionOptions = {
	name: "uid",
	secret,
	store: new RedisStore({
		client: redisClient,
		disableTTL: true,
		disableTouch: true,
	}),
	cookie: {
		maxAge: 1000000000000999,
		httpOnly: true,
		sameSite: "lax",
		secure: __prod__,
	},
	saveUninitialized: false,
	resave: false,
};
I have attempted to create a separate type combining express.Request and the session options, but I can't really get that to work either, and I'm assuming there's a bit more elegant way of dealing with this.
Thank your for your time.

Duplicate issue #807: Extending session object
Created: 2021-01-20T07:36:43Z
Hi there, I know this is not an actual issue, but a help wanted.
I'm struggling with typescript and express session and I have been playing around and trying to fiugure out this one for quite a bit.
I'm trying to extend my session object, for that, I'm trying to do a merge of typings as per in the documentation:
I have a types/session.d.ts with the following interface to be merged:
declare module 'express-session' {
  interface SessionData {
    userId: string;
  }
}

But this is not working, as an example, in other-folder/some.ts
req.session.userId = user.id;
// Property 'userId' does not exist on type 'Session & Partial<SessionData>'.

However, if I import Session from express-session, it does work:
import { Session } from 'express-session'

declare module 'express-session' {
  interface SessionData {
    userId: string;
  }
}

I'm not very proficient with TypeScript and I'm unsure about importing a module in a type defintion, event TypeScript complains about this (warning):
'Session' is declared but its value is never read.
I'm wondering, is this the right way of tackling the problem?
What can I do different?
Kind regards!
PS: my tsconfig should be fine as I have available through my code other type definitions and they are working with no issues at all.

Closing comment (2021-01-20T07:40:01Z): I think this is a duplicate of #799 . If not, let me know and I can re-open this one.
Repository: expressjs/session

Issue #4: better solution for disconnected store
Created: 2014-02-16T01:30:13Z
migrated from senchalabs/connect#973

Duplicate issue #762: avoid req.session being undefined even if !storeReady
Created: 2020-06-26T05:24:44Z
Our project currently uses express-session and cookie-session with its corresponding @DefinitelyTyped definitions. Recent updates to the latter have revealed that req.session as set by the two middlewares can take on slightly different types, as follows:


cookie-session would set the property to be either:

an object on deserialization or creation, or;
null when set by a controller to destroy the session.



express-session would set the property to be either:

an object on deserialization or creation;
null when set by a controller to destroy the session, or;
undefined, when the session store is not available.



It is the lattermost state that results in express-session type definitions that are incompatible with cookie-session.
We hence propose that when the session store is unavailable, req.session is set to null, for the following reasons:

Consistency with the shape of the property set by cookie-session;
Largely backward compatible with code that checks for req.session truthiness to see if a session has been set;
Retention of semantics regarding session destruction, where req.sessionID is non-null while req.session is null, since if the store is not available req.sessionID will not be populated anyway.

I am open to other approaches we can take to somehow bring cookie-session and express-session in-line, though I will note that discussions amongst TypeScript users have suggested that they generally expect req.session to be non-optional (ie, never undefined)

Closing comment (2020-06-26T05:32:37Z): Largely backward compatible with code that checks for req.session truthiness to see if a session has been set;

Unfortunately it is not actually backwards compatible, so it cannot be changed in the 1.x series. Yes, it works for those who check truthiness, but as it has always been undefined for all of the project's existence, and many linters telling users to use ===, it is highly likely users are using === undefined checks. (Simple github search for likely public occurrences: https://github.com/search?l=JavaScript&q=%22req.session+%3D%3D%3D+undefined%22&type=Code)

I am open to other approaches we can take to somehow bring cookie-session and express-session in-line,

I'm not sure this project's issue tracker is the proper forum for such a discussion. Middlewares not by no means required to be compatible with each other like this, especially since they noth use the same property a single express app is unlikely to actually be able to use both at the same time.

Though I will note that discussions amongst TypeScript users have suggested that they generally expect req.session to be non-optional (ie, never undefined)

This is not a typescript project, and we work to adhere to javascript principals and design patterns.
Ultimately I think overall this is really a duplicate of #4 as it has to do with the behavior when the store is not ready.
Repository: fabiolb/fabio

Issue #169: TCP+SNI support on the same port as HTTPS 
Created: 2016-09-28T13:05:45Z
I have a use case where I need to route on port 443 two type of services:

services that are already using https. fabio would just need to use SNI to forward the TCP connection to them
services which are plain HTTP, fabio need to wrap a SSL connection around that

I understand that fabio can do both, but not on the same port. Would it be possible to do that? Basically, it would need to :

read SNI information
check if the underlying service talks https, if so, proxy the TCP stream
if the underlying service only talks unencrypted http, wrap the http in SSL using a certificate from the store

Duplicate issue #213: Mixing of HTTPS proxying and SNI+TCP on a single port
Created: 2017-01-12T17:41:11Z
In my setup the majority of HTTPS handling is done at the edge of the cluster by Fabio with internal services running only HTTP. However, BitBucket is being a complete pain and, thinking the request is on HTTP, generating 302 redirects to HTTPS because it doesn't realise the proxy is handling this.
It would be very useful to be able to mix SNI+TCP and HTTPS proxying on the same port (443) based on the incoming request hostname. If the incoming request matches a hostname for SNI+TCP then SNI+TCP will be used, otherwise HTTPS proxying down to HTTP would be used.

Closing comment (2017-12-14T13:06:14Z): Duplicate of #169
The tcp+sni is an awesome feature which is one of the reasons we are looking to use fabio for client load balancing, and would definitely like the flexibilty to choose tcp+sni or https termination.