added
stringdate
2025-04-01 04:05:38
2025-04-01 07:14:06
created
timestamp[us]date
2001-10-09 16:19:16
2025-01-01 03:51:31
id
stringlengths
4
10
metadata
dict
source
stringclasses
2 values
text
stringlengths
0
1.61M
2025-04-01T04:35:50.548531
2016-05-01T05:18:55
152111679
{ "authors": [ "LordFlashmeow", "dgies" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11814", "repo": "valerian/ksp-planetshine", "url": "https://github.com/valerian/ksp-planetshine/issues/27" }
gharchive/issue
Update PlanetShine.version to support KSP 1.1.1 PlanetShine is throwing up a warning box on KSP 1.1.1. You may want to make it accept any patch level in 1.1. I've made a pull request that will update it to 1.3. Let's see if it gets merged
2025-04-01T04:35:50.569601
2016-09-14T17:15:12
176966436
{ "authors": [ "markpritchett", "valorkin" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11816", "repo": "valor-software/ng2-bootstrap", "url": "https://github.com/valor-software/ng2-bootstrap/issues/971" }
gharchive/issue
Suggestion: consider bringing in popover component from an existing repository There are a few repositories that have a popover component for angular 2. The one I've briefly played around with is ng2-popover. Would it be worth contacting the author of this component (or the authors of any other popover components) to discuss using their implementation in this project? Just thinking that as this project is gaining a fair amount of momentum, it might make sense to re-use some of the existing work done elsewhere to fill the gaps of missing components. done on 80% I am in the middle of rewriting positioning service to allow auto positioning of elements which did not feet in view port... Implement ed
2025-04-01T04:35:50.577479
2021-09-15T22:13:12
997563234
{ "authors": [ "noisypigeon" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11817", "repo": "valora-inc/wallet", "url": "https://github.com/valora-inc/wallet/pull/1120" }
gharchive/pull-request
Adopt Google Secrets Manager for key id and issuer id Description Adopt Google Secrets Manager for key id and issuer id. This PR depends on https://github.com/valora-inc/release-automation/pull/14. Other changes No. Tested https://github.com/valora-inc/release-automation/runs/3615862714?check_suite_focus=true How others should test N/A. Related issues N/A. Backwards compatibility N/A. The test was a success! @silasbw if you could please review.
2025-04-01T04:35:50.581713
2021-11-01T20:34:14
1041598102
{ "authors": [ "ValoraQA", "gnardini" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11818", "repo": "valora-inc/wallet", "url": "https://github.com/valora-inc/wallet/pull/1346" }
gharchive/pull-request
Make token picker on bottom sheet scrollable Description The token picker is now scrollable. https://user-images.githubusercontent.com/6062888/139738067-b5aad11c-5723-4c3f-bc9a-20a73784bcf6.mov Other changes Fixed a warning due to a missing key attribute. Tested I made a few copies of the tokens I had to test with a large token list. How others should test Get a lot of different tokens and check that they can all be seen from the token picker Related issues Part of #1126 Backwards compatibility N/A Hey @MuckT, We have verified this issue using Latest iOS Alfajores Nightly V1.23.0, Android Alfa jores nightly V1.23.0 and added the result in below sheet. Sheet Link: https://docs.google.com/spreadsheets/d/1LcYXmQcuLTBIHZrzUjoYaUvnzisq2ReRvxVwmn-xGEA/edit#gid=1458277593 Devices: iPhone 13 mini (15.1.1), One plus 7t (11.0) CC: @gnardini Thanks..!!
2025-04-01T04:35:50.587499
2022-07-15T14:45:39
1306124807
{ "authors": [ "dvilelaf" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11819", "repo": "valory-xyz/open-autonomy", "url": "https://github.com/valory-xyz/open-autonomy/pull/1081" }
gharchive/pull-request
[WIP] Docs/publishing Proposed changes Add a package publishing section to the documentation. TODO [ ] Confirm that the steps are correct [ ] Review language [ ] Confirm with Jose that the images are self-explanatory Fixes n/a Types of changes What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.) Put an x in the box that applies [x] Non-breaking fix (non-breaking change which fixes an issue) [ ] Breaking fix (breaking change which fixes an issue) [ ] Non-breaking feature (non-breaking change which adds functionality) [ ] Breaking feature (breaking change which adds functionality) [ ] Refactor (non-breaking change which changes implementation) [ ] Messy (mixture of the above - requires explanation!) Checklist Put an x in the boxes that apply. [x] I have read the CONTRIBUTING doc [x] I am making a pull request against the main branch (left side). Also you should start your branch off our main. [x] Lint and unit tests pass locally with my changes [ ] I have added tests that prove my fix is effective or that my feature works [ ] I have locally run services that could be impacted and they do not present failures derived from my changes There is some problem with the hashing versioning
2025-04-01T04:35:50.615481
2021-11-26T06:36:46
1064147391
{ "authors": [ "atapatel", "fulopattila122" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11820", "repo": "vanilophp/adjustments", "url": "https://github.com/vanilophp/adjustments/issues/1" }
gharchive/issue
Custom Adjustments. Hello, Is it possible to add custom adjustments like. If a user buys 1 iPhone, we give them AirPods free. Yes, it was designed to achieve such functionality. See the Adjusters section here: https://vanilo.io/docs/master/adjustments Please note that this module is still WIP. To be released in December/January 2022.
2025-04-01T04:35:50.617715
2024-09-14T10:59:46
2526252568
{ "authors": [ "Tao-VanJS", "eevleevs" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11821", "repo": "vanjs-org/van", "url": "https://github.com/vanjs-org/van/issues/366" }
gharchive/issue
VanUI Toggle does not respond to first click when on is true See https://codesandbox.io/p/devbox/musing-merkle-h6hcgx?file=%2Fsrc%2Fmain.ts Thanks @eevleevs for reporting the bug. It was fixed in VanUI 0.10.1. See: https://codesandbox.io/p/sandbox/github/vanjs-org/van/tree/main/components/examples/toggle?file=%2Fsrc%2Fmain.ts%3A1%2C1. @all-contributors add @eevleevs for bug Thanks for the quick fix!
2025-04-01T04:35:50.649190
2017-05-30T23:09:13
232408110
{ "authors": [ "gengliangwang", "vanzin" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11822", "repo": "vanzin/spark", "url": "https://github.com/vanzin/spark/pull/39" }
gharchive/pull-request
SHS-NG M7: Limit disk usage of the history server. This change adds a new configuration option and support code that limits how much disk space the SHS will use. The default value is pretty generous so that applications will, hopefully, only rarely need to be replayed. This works by keeping track of how much data each application is using; because it's not possible to know, before replaying, how much space will be needed, it's possible that usage will exceed the configured limit temporarily. The code uses the concept of a "lease" to try to limit how much the SHS will exceed the limit. Active UIs are also tracked, so they're never deleted. This works in tandem with the existing option of how many active UIs are loaded; because unused UIs will be unloaded, their disk stores will also become candidates for deletion. If the data is not deleted, though, re-loading the UI is pretty quick. Hi Vanzin, I just come up with a idea. Instead of using two configurations EVENT_TO_STORE_SIZE_RATIO and MAX_LOCAL_DISK_USAGE to control the disk usage, how about allowing user to limit the max number of applications written to disk store? It may be simpler and more user friendly. limit the max number of applications written to disk store The size of the disk store can vary wildly from application to application, so that's not very user-friendly if the goal is to control how much disk space to use.
2025-04-01T04:35:50.651163
2019-10-20T20:49:21
509650631
{ "authors": [ "eli-schwartz", "vapier" ], "license": "unlicense", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11823", "repo": "vapier/ncompress", "url": "https://github.com/vapier/ncompress/pull/24" }
gharchive/pull-request
make: add PREFIX conformance, add option to only install main program Inspired by similar logic from the master branch. This makes the install routine useful for linux packaging without a lot of post-install cleanup. Fixes #23 Split out the strip/mandir changes into separate commits. thx bud As a matter of curiosity, do you have plans to cut a new release with this and the exit code fixes in the near future? i've tagged v<IP_ADDRESS> now
2025-04-01T04:35:50.658260
2018-02-11T04:45:26
296160423
{ "authors": [ "0xTim", "Joannis", "mcdappdev", "twof" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11824", "repo": "vapor/mysql-driver", "url": "https://github.com/vapor/mysql-driver/pull/64" }
gharchive/pull-request
Adds URL init for MySQLDatabase Allows you to do something like let db = MySQLDatabase(databaseURL: databaseURL) Which is necessary if you're going to be connecting to a MySQL DB from Heroku Does ‘URI’ still exist in Vapor 3? If so I would suggest using that instead of manually splicing the string. That was such a useful class Updated. I have it returning nil if something doesn't work right now, but it should probably throw instead. I'm not sure what error to throw though. It should still exist, I use it here https://github.com/brokenhandsio/SteamPress/blob/vapor3/Sources/SteamPress/Controllers/BlogController.swift#L145 Ahhh I see it's in HTTP. I think casting String to a URL works fine for now. It's a nice addition :) I'm wondering if this is all there is to support, or if there are more features that we're not using. @Joannis There are tooooons of properties you can pass in via the URL that are unimplemented as far as I can tell. I don't know how much use most of them get though https://dev.mysql.com/doc/connector-j/8.0/en/connector-j-reference-configuration-properties.html @Joannis It looks like there are more properties available, but they'd need to be defined in the driver? http://razorsql.com/docs/help_mysql.html ADDITIONAL JDBC CONNECTION PROPERTIES Additional connection properties can be appended to the JDBC URL. The format to add connection properties is the following: jdbc:mysql://<host>:<port>/<database_name>?property1=value1&property2=value2 Here are examples of connection properties for the MySQL Connector/J driver. Consult your driver documentation for more examples of connection properties. connectTimeout (Timeout for socket connect (in milliseconds), with 0 being no timeout. Only works on JDK-1.4 or newer. Defaults to 0.) socketTimeout (Timeout on network socket operations (0, the default means no timeout).) autoReconnect (Should the driver try to re-establish stale and/or dead connections.) Examples: jdbc:mysql://neptune.acme.com:3306/test jdbc:mysql://<IP_ADDRESS>:3306/test jdbc:mysql://localhost:3306/mysql?connectTimeout=0&socketTimeout=0&autoReconnect=true I don't think so in this case, since JDBC != raw MySQL I think. @gwynne any problems with this PR, still? Otherwise we could retract your rejection
2025-04-01T04:35:50.659600
2018-03-15T06:56:24
305435343
{ "authors": [ "rafiki270", "tanner0101" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11825", "repo": "vapor/service", "url": "https://github.com/vapor/service/pull/17" }
gharchive/pull-request
Adding get with default value When configuring my environment, doing a default value fallback is the most common repeating code in my app ... thought this could help other people keep their apps clean of loads of guards and ?? @rafiki270 I think ?? is the correct solution here. No reason to expand Vapor's API when there are already tools in Swift to handle this. Thanks for the PR!
2025-04-01T04:35:50.664777
2018-11-14T19:45:24
380857670
{ "authors": [ "penny-coin", "tanner0101" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11826", "repo": "vapor/service", "url": "https://github.com/vapor/service/pull/29" }
gharchive/pull-request
ServiceKit 2.0 Removes ServiceCache Singletons can still be registered using Services.instance(...). The service cache is unnecessary if services are injected at initialization time. Removes service Config Only one service can be registered against a given protocol now. If multiple services are registered to the same protocol, the last registered service will be used. The goal behind this change is to make services easier to reason about and reduce possible runtime error cases. Adds Services.extend() Non-singleton services can now be extended using Services.extend s.extend(Commands.self) { commands, c in try commands.add(c.make(MigrateCommand.self), named: "migrate") } This gives service providers more power to configure applications. Renames module to ServiceKit. Removes Service protocol. This protocol is no longer required since the Services registration methods now have unique names. Removing this empty protocol requirement should make it easier to get started using services. Removes ServiceType protocol. Services no longer support registering services against an Any.Type interface. While this change greatly improves type safety and internal consistency, it is no longer possible to use ServiceType since it relied on an array of [Any.Type] interfaces. It's possible to update the protocol to only register Self.self as a supported interface, but I'm not sure how useful that would be. Removes all dependencies besides SwiftNIO. NIO is still required since Container must hold a reference to EventLoop. This is a fundamental part of how ServiceKit works, since many services (like HTTPClient, Databases, etc) require an event loop to initialize. Hey @tanner0101, you just merged a pull request, have a coin! You now have 1030 coins.
2025-04-01T04:35:50.676971
2023-10-14T23:59:38
1943610375
{ "authors": [ "zypus" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11827", "repo": "varabyte/kobweb", "url": "https://github.com/varabyte/kobweb/pull/351" }
gharchive/pull-request
Preliminary implementation of dispose callback generation for server api This pull request accompanies this discussion #350 It adds a @DisposeApi annotation next to the @InitApi annotation and adds the encessary code generation to add a dispose function to the ApiJarFile. This dispose function is currently called when the cache of the ApiJarFileImpl gets invalidated. This currently is only relevant for the DEV mode. As the ApiJarFileImpl is quite deeply hidden and I already exposed it from the cache, I did not implement that the dispose function is also called when the actual server shutdown, but it should for consistency be also called on shutdown. Hence this part would still be a TODO. Did branch from main which was incorrect, gonna fix that and open a new pull request.
2025-04-01T04:35:50.699154
2023-11-19T07:15:02
2000730583
{ "authors": [ "chouchouji", "gaoting" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11828", "repo": "varletjs/varlet", "url": "https://github.com/varletjs/varlet/pull/1309" }
gharchive/pull-request
feat(date-time-picker):Components Checklist List of tasks you have already done and plan to do. [x] Fix linting errors [x] Tests have been added / updated (or snapshots) Issues The issues you want to close, formatted as close #1261 Don't forget to add type and complete components map, refer to this pr floating panel Add prev and next events may be necessary. Please confirm it for haoziqaq.
2025-04-01T04:35:50.708100
2022-11-14T07:30:46
1447537525
{ "authors": [ "BeADre", "a145789", "codecov-commenter" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11829", "repo": "varletjs/varlet", "url": "https://github.com/varletjs/varlet/pull/750" }
gharchive/pull-request
Feat/var link Checklist [x] Fix linting errors [ ] Tests have been added / updated (or snapshots) Change information 支持 link 组件,还需要英文文档和测试用例 Codecov Report Merging #750 (5d9cd92) into feat/link (86f5dc0) will decrease coverage by 0.71%. The diff coverage is 0.00%. @@ Coverage Diff @@ ## feat/link #750 +/- ## ============================================= - Coverage 95.37% 94.66% -0.72% ============================================= Files 218 221 +3 Lines 5364 5417 +53 Branches 986 996 +10 ============================================= + Hits 5116 5128 +12 - Misses 248 289 +41 Impacted Files Coverage Δ packages/varlet-ui/src/link/Link.vue 0.00% <0.00%> (ø) packages/varlet-ui/src/link/index.ts 0.00% <0.00%> (ø) packages/varlet-ui/src/link/props.ts 0.00% <0.00%> (ø) packages/varlet-ui/src/tabs-items/TabsItems.vue 97.91% <0.00%> (+0.69%) :arrow_up: Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. 我先合了 后续看能不能把customAttrs优化一下 然后文档测试啥的新开pr吧
2025-04-01T04:35:50.743059
2019-06-08T22:51:22
453843277
{ "authors": [ "coveralls", "vaskoz" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11830", "repo": "vaskoz/dailycodingproblem-go", "url": "https://github.com/vaskoz/dailycodingproblem-go/pull/595" }
gharchive/pull-request
Day290 Resolves #594. Pull Request Test Coverage Report for Build 1107 0 of 0 changed or added relevant lines in 0 files are covered. No unchanged relevant lines lost coverage. Overall coverage remained the same at 100.0% Totals Change from base Build 1111: 0.0% Covered Lines: 5 Relevant Lines: 5 💛 - Coveralls
2025-04-01T04:35:50.768039
2021-07-17T13:25:38
946824021
{ "authors": [ "vasudevgupta7" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11831", "repo": "vasudevgupta7/gsoc-wav2vec2", "url": "https://github.com/vasudevgupta7/gsoc-wav2vec2/pull/5" }
gharchive/pull-request
export TF saved-models This PR add code for exporting TF saved-model to TF-Hub. Added one notebook also to show how extra head can be appended over the pre-trained model and how the resulting model can be trained. I will add some detailed- text in the notebook if basic structure looks fine to you. I can merge it if everything looks alright to you @sayakpaul @MorganR @sayakpaul thanks for the review! I will work on your suggestion by today.
2025-04-01T04:35:50.786862
2024-09-27T16:02:25
2553274394
{ "authors": [ "LibretroAdmin", "vawser" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11832", "repo": "vawser/Smithbox", "url": "https://github.com/vawser/Smithbox/issues/123" }
gharchive/issue
Dark Souls 1 Remastered project crashes at startup Shows these error dialog boxes when opening a new or existing project - Used to work fine before. Looks to be linked to the WIP ESD Editor. I'll disable the feature flag since it shouldn't have been enabled for a release.
2025-04-01T04:35:50.787914
2022-09-13T23:42:39
1372127756
{ "authors": [ "vbekasov" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11833", "repo": "vbekasov/cpp", "url": "https://github.com/vbekasov/cpp/issues/1" }
gharchive/issue
Template struct in template class template struct in template class c++ OOP I am going to implement template struct for my binary tree. solved
2025-04-01T04:35:50.830455
2024-03-25T08:47:53
2205205867
{ "authors": [ "geahaad" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11834", "repo": "vcsphere/upptime", "url": "https://github.com/vcsphere/upptime/issues/348" }
gharchive/issue
⚠️ Spryr has degraded performance In 33fa3a6, Spryr (https://spryr.com) experienced degraded performance: HTTP code: 200 Response time: 3460 ms Resolved: Spryr performance has improved in a3d6c7c after 7 minutes.
2025-04-01T04:35:50.835094
2022-10-23T17:16:47
1419862945
{ "authors": [ "keerthanak-tw", "vczb" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11835", "repo": "vczb/sagu-ui", "url": "https://github.com/vczb/sagu-ui/issues/55" }
gharchive/issue
BUG - Deprecation Warning Deprecation Warning on console to reproduce: Run the command $ yarn lint (node:73477) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./2020/" in the "exports" field module resolution of the package at /home/vini/src/sagu-ui/node_modules/es-abstract/package.json. Update this package.json to use a subpath pattern like "./2020/*". (Use `node --trace-deprecation ...` to show where the warning was created) (node:73477) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./helpers/" in the "exports" field module resolution of the package at /home/vini/src/sagu-ui/node_modules/es-abstract/package.json. Update this package.json to use a subpath pattern like "./helpers/*". I also tried for node v14 and v12 in which it doesn't seem to appear.. If you are still getting the error, what you can try is removing line highlighted in red and mapping ./* to ./* like highlighted in green (in package.json) Not raising a PR as I am not able to reproduce the error Thanks for noticing that. I will check ASAP I cannot see this ./ mapping in package.json.. So try adding the mentioned line in file.. Then you need to add exports and add it.. Reference: https://github.com/postcss/postcss/commit/92155c73e105a36af5196a75bcc34ada377a711f Seems to be fixed... I can't reproduce, feel free to reopen in case of it back
2025-04-01T04:35:50.921196
2016-01-15T17:14:05
126915243
{ "authors": [ "aqiank", "tanema" ], "license": "bsd-3-clause", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11836", "repo": "veandco/go-sdl2", "url": "https://github.com/veandco/go-sdl2/issues/176" }
gharchive/issue
ShowMessageBox doesn't properly display buttons Hey I was quite happy to see the new message box implementation so I started to play around with it and noticed that it doesn't quite work yet. I just ran the example and I got this for the buttons: If you press the unlabeled one it will crash the example and give a button id of 200. Also the escape button does not work on it (the return key does though). I tried looking at the code to see if it was a simple fixable problem but could not come up with anything. It must have something to do with changing the data into cptrs but I cannot tell. go version: go version go1.5.1 darwin/amd64 git SHA: ead8e10e4e972e55f44d99f6e57c82963040f848 (most current) cheers, Hi @tanema, I've fixed it in a recent commit. Please try again. It works perfectly @aqiank, it looks like my suspicions were correct as well. Thanks for the fix!
2025-04-01T04:35:50.961323
2017-08-28T08:28:08
253260963
{ "authors": [ "ylecollen" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11837", "repo": "vector-im/riot-android", "url": "https://github.com/vector-im/riot-android/issues/1521" }
gharchive/issue
app crash while accessing room files reported by @garblur83:matrix.org https://github.com/matrix-org/riot-android-rageshakes/issues/790 i don't reproduce this issue
2025-04-01T04:35:50.962665
2019-08-19T09:24:17
482200385
{ "authors": [ "jryans" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11838", "repo": "vector-im/riot-android", "url": "https://github.com/vector-im/riot-android/issues/3268" }
gharchive/issue
Placeholder issue for privacy migration path We're expecting some additional (currently undefined) work for the migration path to support older HSes etc. as we migrate towards the ideal state. Cloned from https://github.com/vector-im/riot-web/issues/10593. We've agreed as a group that this undefined mystery issue isn't helping us much. We can add real issues for migration as they arise.
2025-04-01T04:35:50.964747
2019-09-25T19:19:08
498474276
{ "authors": [ "GammaPi" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11839", "repo": "vector-im/riot-android", "url": "https://github.com/vector-im/riot-android/pull/3325" }
gharchive/pull-request
Try to fix issue 2453 Will this fix #2453 ? I didn't have build environment at hand for testing and not quite familiar with this repository. So I just made those small changes based on my observation: I found "refreshForegroundNotification" seems to be a function called when synchronising from homeserver. And since mForegroundNotificationState != INCOMING_CALL or CALL_IN_PROGRESS, I just call hideCallNotifications() to remove the notification. Sorry for not digging deeper into the source code. This bug is really very annoying, please help me to verify whether this fix works. Thanks a lot. @bmarty After looking through code. I found this fix doesn't work. But I will provide some details I found in issue 2453
2025-04-01T04:35:50.982204
2016-09-15T16:35:51
177225867
{ "authors": [ "ara4n", "giomfo" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11840", "repo": "vector-im/vector-ios", "url": "https://github.com/vector-im/vector-ios/issues/634" }
gharchive/issue
Chat screen: Update emote layout like in web-client The emote layout on web is currently in flux. Right now on /develop the behaviour matches iOS.
2025-04-01T04:35:51.049359
2018-03-12T07:56:09
304270787
{ "authors": [ "dtcristo", "veelenga" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11841", "repo": "veelenga/awesome-crystal", "url": "https://github.com/veelenga/awesome-crystal/pull/266" }
gharchive/pull-request
Add cray Adds cray to "Game Development". Bindings for raylib, an easy-to-use game development library. Tried your examples locally. Works and looks nice 👍 Thanks! I think raylib is a great library for playing around with game development and even simple 3D. And with Crystal bindings it's even more fun. Now all we need is a more OO abstraction around this to make the game code more Crystal like.
2025-04-01T04:35:51.056616
2022-09-22T18:02:48
1382824429
{ "authors": [ "dgulinobw", "pcgeek86", "veeso" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11842", "repo": "veeso/termscp", "url": "https://github.com/veeso/termscp/issues/124" }
gharchive/issue
[BUG] - 0.9.0 doesn't run on Ubuntu 22.04 Description running termscp, errors with: "termscp: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory" Steps to reproduce run termscp Expected behaviour termscp should start Environment OS: Ubuntu 22.10 Architecture x86_64 Rust version: N/A termscp 0.9.0 (installed via curl --proto '=https' --tlsv1.2 -sSLf "https://git.io/JBhDb" | sh) Protocol used: N/A Remote server version and name: N/A Log  curl --proto '=https' --tlsv1.2 -sSLf "https: //git.io/JBhDb" | sh Termscp configuration > Platform: linux > Arch: x86_64 ? Install termscp 0.9.0? [y/N] y > Detected dpkg on your system > Installing termscp via Debian package > Downloaded debian package to /tmp/tmp.p34Qy4gYTZ.deb ! Root permissions are required to install termscp… [sudo] password for dgulino: > Installing termscp as root, please wait… (Reading database ... 296583 files and directories currently installed.) Preparing to unpack /tmp/tmp.p34Qy4gYTZ.deb ... Unpacking termscp (0.9.0) over (0.9.0) ... Setting up termscp (0.9.0) ... ✓ Congratulations! Termscp has successfully been installed on your system! > If you're a new user, you might be interested in reading the user manual <https://veeso.github.io/termscp/#user-manual> > While if you've just updated your termscp version, you can find the changelog at this link <https://veeso.github.io/termscp/#changelog> > Remember that if you encounter any issue, you can report them on Github <https://github.com/veeso/termscp/issues/new> > Feel free to open an issue also if you have an idea which could improve the project > If you want to support the project, please, consider a little donation <https://ko-fi.com/veeso> > I hope you'll enjoy using termscp :D termscp termscp: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory Additional information uname -a Linux 5520 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy Have you already tried with apt install libssl this shouldn't be an issue anymore starting from 0.10 since libssl will be statically linked. Ubuntu 22 uses the libssl3 package which includes: /usr/lib/x86_64-linux-gnu/libssl.so.3 /usr/lib/x86_64-linux-gnu/libssl.so I installed a non-standard libssl 1.0 and was able to get termscp to work with: LD_LIBRARY_PATH=/usr/local/ssl/lib/ termscp Oh no... looks like I'll have to link statically for GNU/Linux systems for 0.10... I have the same problem, trying to install termscp into a Linux container, using Docker, with the Ubuntu 22.04 base image. Start a new container: docker run --pull=always -it --rm ubuntu Then run: apt update apt install libdbus-1-dev libssl-dev --yes curl --proto '=https' --tlsv1.2 -sSLf "https://git.io/JBhDb" | sh 0.10 will definitely will be shipped with static libssl it should have been fixed
2025-04-01T04:35:51.059827
2021-08-02T19:17:01
958436178
{ "authors": [ "tramhao", "veeso" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11843", "repo": "veeso/tui-realm-treeview", "url": "https://github.com/veeso/tui-realm-treeview/issues/4" }
gharchive/issue
[BUG] - upgrade to tuirealm 0.5 Description When I upgrade to tui-realm 0.5, treeview cannot compile. Steps to reproduce Upgrade to tuirealm 0.5, this component will not work. Expected behaviour It should work as before, but now it complains two version of tui-realm is used. Environment OS: Arch linux Architecturex x86_64x Rust version: 1.53.0 tui-realm-treeview version 0.2 Additional information Thanks. Add any other context about the problem here. Yep, I totally forgot to update this crate 😅 . 0.2.1 fixes the issue
2025-04-01T04:35:51.086507
2023-06-30T13:59:41
1782604185
{ "authors": [ "JonRay15", "ciaran-", "daunatv" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11844", "repo": "vegaprotocol/vega.xyz", "url": "https://github.com/vegaprotocol/vega.xyz/issues/721" }
gharchive/issue
LP dashboard and website homepage tiles are showing terminated markets Issue Mainnet dashboard is displaying the markets that were terminated this morning. All three are showing as "Continuous" for some reason. In Console they appear with a status of "Settled" .. we should be detecting this same status and if settled should be removing them from the view completely, I see no reason to show them here. Once this LP dashboard change is done we can revisit whether additional change is needed on the homepage to make it stop showing them too. Proposal Add a filter to the query on the markets API to exclude any records where state is one of: STATE_REJECTED, STATE_CANCELLED, STATE_CLOSED, STATE_SETTLED For reference, this means we are including the following: STATE_UNSPECIFIED, STATE_PROPOSED, STATE_PENDING, STATE_ACTIVE, STATE_SUSPENDED, STATE_TRADING_TERMINATED. I have opted to only exclude the most "final" states of "not a market anymore" so we're erring on the side of including where there's doubt. The only one that is contentious I think is trading terminated. We could exclude this too since a terminated market does not need liquidity, but generally speaking markets only stay in that state for a few hours, and I would normally expect a market maker to not pull their liquidity until they have settled the market, so I think its best to include. @JonRay15 PR incoming for this. Do we want to include state as a column in the table as well, or are we happy filtering by it silently ? I think that adding state is just going to confuse people... cos you can have all the below, which can exist I believe in various combinations that I dont dare to attempt to list out! Ultimately for the LP Dashboard we care about: Market in opening auction - this has a trading mode, would be in state pending or proposed, cant remember, but neither adds much useful info Market in continuous trading - this is a trading mode, state would be active, which is obvious Market in auction - this is a trading mode, irritatingly I dont know if we know the diff between liquidity auction vs price monitoring auction but I seem to recall we do ... in either case state here is suspended, which again doesnt really add much Market terminated - I included this above and I guess it would show TRADING_MODE_NO_TRADING ... here the state does add some useful info but its the only case. I am actually now thinking for simplicity lets not show terminated ones cos TRADING_MODE_NO_TRADING will raise questions for the few hours it is the case So TLDR No dont add state Can you exclude state = STATE_TRADING_TERMINATED on second thought Should exclude state = STATE_SETTLED as well. Think the main issue right now is that the markets are shown as continuous and that they are taking up 2 out of 4 spots on the main page. This was subsequently amended to also exclude STATE_PROPOSED
2025-04-01T04:35:51.190462
2021-12-04T00:16:37
1071066160
{ "authors": [ "Arlodotexe", "veler" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11845", "repo": "veler/DevToys", "url": "https://github.com/veler/DevToys/issues/100" }
gharchive/issue
Pin specific tools to start Is your feature request related to a problem? Please describe. Having to open the app, then select the tool is a bit cumbersome. Describe the solution you'd like Pinning a tool to Start and launching right into it. Describe alternatives you've considered n/a Additional context n/a Thank you for the suggestion :) That would be a nice addition to the following work item: #75 Thank you for the suggestion :) That would be a nice addition to the following work item: #75 I agree, these two features would completement each other nicely. Might be a good idea to investigate doing the full-page view mentioned in #88 first, though. Thanks again @Arlodotexe ! It will be available in the next update :)
2025-04-01T04:35:51.192236
2014-09-23T18:44:12
43667387
{ "authors": [ "rupurt", "travisjeffery" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11846", "repo": "velesin/jasmine-jquery", "url": "https://github.com/velesin/jasmine-jquery/pull/216" }
gharchive/pull-request
Only show inner text on failure of toContainText matcher This is for 1.7.x. I can also submit another one for master if you would like. The old output included the entire DOM structure which made it hard to parse Hey i'm good to merge this, do you mind updating your branch so there's a clean merge? Thanks! @travisjeffery it looks like this may already be done on master. We're still on the 1.7.x branch as we haven't upgraded to Jasmine 2 yet.
2025-04-01T04:35:51.193254
2020-05-27T08:20:03
625483558
{ "authors": [ "emilbryggare", "velikanov" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11847", "repo": "velikanov/opensource-candies", "url": "https://github.com/velikanov/opensource-candies/pull/78" }
gharchive/pull-request
Added convas.io Convas is a feedback page for companies and projects. We have a free plan for open source projects. Thank you! 👍
2025-04-01T04:35:51.195834
2023-05-12T11:33:32
1707462081
{ "authors": [ "Gobliins", "dr-dimitru" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11848", "repo": "veliovgroup/Meteor-Files", "url": "https://github.com/veliovgroup/Meteor-Files/issues/872" }
gharchive/issue
Question: Can you store directly in GridFS? Hey, currently my flow is like this: When someone uploads a file it's first saved as a file on the filesystem and later after upload, the file is moved into GridFS. Similar to https://github.com/veliovgroup/Meteor-Files/wiki/GridFS-Integration My (approximately) Code: // GridFS Bucket create createBucket = (bucketName) => { const options = bucketName ? { bucketName } : void 0; return new MongoInternals.NpmModule.GridFSBucket( MongoInternals.defaultRemoteCollectionDriver().mongo.db, options, ); }; export const Files = new FilesCollection({ .... // move uploaded File from FS to GridFS onAfterUpload(fileObj) { const readStream = fs.createReadStream(filepath); // FS Read const writeStream = this.gridFsBucket.openUploadStream(filepath); // GridFS Write readStream.pipe(writeStream) ... // unlink from FS }, ... So when adding Files via the Files.load() or Files.insert() methods, is it possible to skip the Filesystem and upload / load / add files, directly into GridFs? Regards @Gobliins I understand your frustration but there's no way to skip local file system as intermediate point @dr-dimitru No worries, just wanted to know :)
2025-04-01T04:35:51.198517
2021-11-09T17:57:50
1048907175
{ "authors": [ "velovix" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11849", "repo": "velovix/debutizer", "url": "https://github.com/velovix/debutizer/issues/42" }
gharchive/issue
Ensure that the imported GPG key is the one used in signing Right now we make the assumption that, when using DEBUTIZER_GPG_SIGNING_KEY, the key will be imported as the first and only key in the keyring. If that isn't true, it may not be properly chosen as the signing key. We should check the ID of the imported key and explicitly tell GPG to use that. I "fixed" this by making the upload_target.gpg_key_id field required when using package signing. This may seem like a workaround but makes sense to me, as it ensures that environments that aren't importing a key through DEBUTIZER_GPG_SIGNING_KEY will use the correct key as well.
2025-04-01T04:35:51.280526
2017-05-17T13:20:09
229349786
{ "authors": [ "aleph7", "nhatlee" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11850", "repo": "venturemedia/mxml", "url": "https://github.com/venturemedia/mxml/issues/3" }
gharchive/issue
2/2 Test #2: lxml_tester ......................***Not Run 0.00 sec I faced with the error when run make test. And below is the log(MacBook Pro (Retina, Mid 2012), MacOS: 10.12.4 (16E195)): mxml git:(master) make test Running tests... Test project /Users/apple/Documents/MyProject/mxml Start 1: mxml_tester Could not find executable /Users/apple/Documents/MyProject/mxml/build/mxml_tester Looked in the following places: /Users/apple/Documents/MyProject/mxml/build/mxml_tester /Users/apple/Documents/MyProject/mxml/build/mxml_tester /Users/apple/Documents/MyProject/mxml/build/Release/mxml_tester /Users/apple/Documents/MyProject/mxml/build/Release/mxml_tester /Users/apple/Documents/MyProject/mxml/build/Debug/mxml_tester /Users/apple/Documents/MyProject/mxml/build/Debug/mxml_tester /Users/apple/Documents/MyProject/mxml/build/MinSizeRel/mxml_tester /Users/apple/Documents/MyProject/mxml/build/MinSizeRel/mxml_tester /Users/apple/Documents/MyProject/mxml/build/RelWithDebInfo/mxml_tester /Users/apple/Documents/MyProject/mxml/build/RelWithDebInfo/mxml_tester /Users/apple/Documents/MyProject/mxml/build/Deployment/mxml_tester /Users/apple/Documents/MyProject/mxml/build/Deployment/mxml_tester /Users/apple/Documents/MyProject/mxml/build/Development/mxml_tester /Users/apple/Documents/MyProject/mxml/build/Development/mxml_tester Users/apple/Documents/MyProject/mxml/build/mxml_tester Users/apple/Documents/MyProject/mxml/build/mxml_tester Users/apple/Documents/MyProject/mxml/build/Release/mxml_tester Users/apple/Documents/MyProject/mxml/build/Release/mxml_tester Users/apple/Documents/MyProject/mxml/build/Debug/mxml_tester Users/apple/Documents/MyProject/mxml/build/Debug/mxml_tester Users/apple/Documents/MyProject/mxml/build/MinSizeRel/mxml_tester Users/apple/Documents/MyProject/mxml/build/MinSizeRel/mxml_tester Users/apple/Documents/MyProject/mxml/build/RelWithDebInfo/mxml_tester Users/apple/Documents/MyProject/mxml/build/RelWithDebInfo/mxml_tester Users/apple/Documents/MyProject/mxml/build/Deployment/mxml_tester Users/apple/Documents/MyProject/mxml/build/Deployment/mxml_tester Users/apple/Documents/MyProject/mxml/build/Development/mxml_tester Users/apple/Documents/MyProject/mxml/build/Development/mxml_tester Unable to find executable: /Users/apple/Documents/MyProject/mxml/build/mxml_tester 1/2 Test #1: mxml_tester ......................***Not Run 0.00 sec Start 2: lxml_tester Could not find executable /Users/apple/Documents/MyProject/mxml/build/lxml_tester Looked in the following places: /Users/apple/Documents/MyProject/mxml/build/lxml_tester /Users/apple/Documents/MyProject/mxml/build/lxml_tester /Users/apple/Documents/MyProject/mxml/build/Release/lxml_tester /Users/apple/Documents/MyProject/mxml/build/Release/lxml_tester /Users/apple/Documents/MyProject/mxml/build/Debug/lxml_tester /Users/apple/Documents/MyProject/mxml/build/Debug/lxml_tester /Users/apple/Documents/MyProject/mxml/build/MinSizeRel/lxml_tester /Users/apple/Documents/MyProject/mxml/build/MinSizeRel/lxml_tester /Users/apple/Documents/MyProject/mxml/build/RelWithDebInfo/lxml_tester /Users/apple/Documents/MyProject/mxml/build/RelWithDebInfo/lxml_tester /Users/apple/Documents/MyProject/mxml/build/Deployment/lxml_tester /Users/apple/Documents/MyProject/mxml/build/Deployment/lxml_tester /Users/apple/Documents/MyProject/mxml/build/Development/lxml_tester /Users/apple/Documents/MyProject/mxml/build/Development/lxml_tester Users/apple/Documents/MyProject/mxml/build/lxml_tester Users/apple/Documents/MyProject/mxml/build/lxml_tester Users/apple/Documents/MyProject/mxml/build/Release/lxml_tester Users/apple/Documents/MyProject/mxml/build/Release/lxml_tester Users/apple/Documents/MyProject/mxml/build/Debug/lxml_tester Users/apple/Documents/MyProject/mxml/build/Debug/lxml_tester Users/apple/Documents/MyProject/mxml/build/MinSizeRel/lxml_tester Users/apple/Documents/MyProject/mxml/build/MinSizeRel/lxml_tester Users/apple/Documents/MyProject/mxml/build/RelWithDebInfo/lxml_tester Users/apple/Documents/MyProject/mxml/build/RelWithDebInfo/lxml_tester Users/apple/Documents/MyProject/mxml/build/Deployment/lxml_tester Users/apple/Documents/MyProject/mxml/build/Deployment/lxml_tester Users/apple/Documents/MyProject/mxml/build/Development/lxml_tester Users/apple/Documents/MyProject/mxml/build/Development/lxml_tester Unable to find executable: /Users/apple/Documents/MyProject/mxml/build/lxml_tester 2/2 Test #2: lxml_tester ......................***Not Run 0.00 sec 0% tests passed, 2 tests failed out of 2 Total Test time (real) = 0.00 sec The following tests FAILED: 1 - mxml_tester (Not Run) 2 - lxml_tester (Not Run) Errors while running CTest make: *** [test] Error 8 Looking forwards to hearing from you. Did you run git submodule update --init Yes, I did. Ok, I missed a step in the instructions. You need to run make then make test Thanks for your support, added make is worked.
2025-04-01T04:35:52.324931
2023-02-07T08:06:15
1573865153
{ "authors": [ "chris-olszewski", "sneko" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11851", "repo": "vercel/turbo", "url": "https://github.com/vercel/turbo/issues/3669" }
gharchive/issue
[turborepo] Unable to find resolved version for * when pruning What version of Turborepo are you using? 1.6.4 (but tested with 1.7.2) What package manager are you using / does the bug impact? pnpm What operating system are you using? Mac Describe the Bug Hi, When pruning I got this error: Run turbo prune --scope=docs ERROR could not construct graph: 4 errors occurred: * Unable to find resolved version for<EMAIL_ADDRESS>in apps/docs Turbo error: could not construct graph: 4 errors occurred: * Unable to find resolved version for<EMAIL_ADDRESS>in packages/ui * Unable to find resolved version for react-dom@[18](https://github.com/inclusion-numerique/mediature/actions/runs/4111581811/jobs/7095492150#step:8:19).2 in packages/eslint-config-custom * Unable to find resolved version for<EMAIL_ADDRESS>in apps/main * Unable to find resolved version for<EMAIL_ADDRESS>in apps/docs * Unable to find resolved version for<EMAIL_ADDRESS>in packages/ui * Unable to find resolved version for<EMAIL_ADDRESS>in packages/eslint-config-custom * Unable to find resolved version for<EMAIL_ADDRESS>in apps/main I have to admit it was a bit weird because I didn't not change anything in my global package.json (pnpm) and it breaks, then after retrying previous commit it was no longer working :/ ... I tried to remove caches because I found it was hard to explain but impossible to make things working again. After giving multiple attempts, it was not due to the turbo version. But it's probably something between pnpm and turbo. In my main package.json I do have a section .pnpm.overrides (https://github.com/inclusion-numerique/mediature/blob/04e9585a14626873be04aced9469fcb0a7bfad28/package.json#L33-L73) to make sure I have shared dependencies between all my monorepo packages (to avoid building my packages with multiple React versions...). In a sense, they seem not conflicting because it worked at any time (except at a moment with the turbo pruning), but to fix this I had to align specifically each package to use the exact same version range. Since the monorepo has multiple package.json it's hard to explain describe by text, but here you can find the fix I had to do: https://github.com/inclusion-numerique/mediature/commit/b6071bd29d94787dc7cc0ef310878b8cbcf66b68 (if you browse the package.json files you can see it's to align version ranges) Didn't see this error on the repo so I posted for record, but if you think it's just on my end, you can close. Expected Behavior So it works To Reproduce https://github.com/inclusion-numerique/mediature/tree/04e9585a14626873be04aced9469fcb0a7bfad28 Reproduction Repo No response Hi @sneko, thanks for the report. #3656 should fix this, I'll try to get a patch out ASAP. Sorry for the disruption. Please upgrade to 1.7.4 and reopen if the issue persists.
2025-04-01T04:35:52.335894
2024-04-23T07:33:13
2258167646
{ "authors": [ "anthonyshew", "mayank1513" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11852", "repo": "vercel/turbo", "url": "https://github.com/vercel/turbo/pull/8021" }
gharchive/pull-request
Rsc lib example Added an example for creating libraries that unleash the full potential of React18 - especially the server components. This example contain: Build setup that builds my-lib - can support server and client components Turbo repo generators that generate component file, component test file, and index file exporting the component and also updates index.ts files in the path. Plugin also removes test files and data-testid attributes from the final build Testing Instructions Create a repo using this example Test whether build is working and all tests are passing Introducing Example: Leveraging Turborepo for React 18 Libraries This pull request introduces a comprehensive example that demonstrates the utilization of Turborepo to craft React 18 libraries, aimed at unleashing the full potential of server components. Here's what's included in this showcase: Build Setup: The example encompasses a robust build setup tailored for React 18 libraries. This setup is designed to support both server and client components seamlessly. Turborepo Implementation: Leveraging Turborepo, the example showcases an efficient approach to managing and organizing multiple packages within a single repository. This enables smoother collaboration and streamlined development workflows. Enhanced Development Workflow: With Turborepo, developers can enjoy improved efficiency and maintainability by automating various tasks such as generating component files, test files, and index files. Additionally, a plugin has been integrated to optimize the build process further by removing redundant test files and data-testid attributes. Testing Instructions: To validate the efficacy of these changes, please follow these steps: Repository Creation: Set up a repository using the provided example. Build and Test: Ensure that the build process functions correctly and that all tests pass seamlessly. Your feedback on these enhancements is invaluable. Thank you for reviewing! Thanks for the pull request! The basic example already has an RSC library in it for folks to take a look at. Additionally, I spy some problems with what's proposed here: We don't want to encourage barrel files since they can quickly make for large compilation times. Today, the odds are high that you should use a bundler for a TypeScript library, opting for tsc instead. In general, there's a little too much configuration going on for a "starter". For example, the plugin to remove test IDs. We want the examples in the repo to be as absolutely minimal as possible. I definitely appreciate your willingness to contribute! However, we'll close this one as we're not looking to have more examples in the repo, in general. Thanks for the quick response. This example was targeted for library creators who wish to craft and publish their libraries with full power of React 18. There is just one plugin used. Removing test files etc. are just byproduct. The main focus is creating a build which adds “use client” directive to selected components only. I don't see any example in this directory that demonstrates how to build RSC compatible libraries Barrel files can be removed if you wish to accept and move ahead with the basic/bare minimum build set up for building RSC compatible libraries. Should I update the example and reopen this PR or create a new one? Looking forward to your positive response. Also, there is no example showing how to use CSS/CSS modules inside the library. No use creating UI component as a shared library component but keeping the multiple copies of style sheets in each app I have a solution for this as well. And if you and your team agree to add such an example, I shall create that one as well. Your reply is highly appreciated. A popular openion: In practice, the benefits of using barrel files in terms of code organization and maintainability often outweigh any minor increase in compilation time. Additionally, modern build tools and compilers are generally optimized to handle large codebases efficiently, so the impact on compilation time should be manageable.
2025-04-01T04:35:52.340823
2017-03-22T02:19:40
215933671
{ "authors": [ "emcniece", "juanpicado" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11853", "repo": "verdaccio/verdaccio", "url": "https://github.com/verdaccio/verdaccio/issues/139" }
gharchive/issue
Use tokens for auth? I need to build an app in a CI pipeline, so the application must be built without human intervention. Is it possible to get and pass a token as a header, or as part of the URL? What is the method for CI builds without having a human perform npm login first? Have you read this thread ? perhaps is useful. I haven't tried this solution but it's a worthile to try. https://github.com/npm/npm/issues/8356#issuecomment-174320077 Thank you. I have implemented the .npmrc file population approach and it is working well.
2025-04-01T04:35:52.341920
2017-11-21T20:15:46
275845648
{ "authors": [ "justinvforvendetta", "markimjas" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11854", "repo": "vergecurrency/VERGE", "url": "https://github.com/vergecurrency/VERGE/issues/99" }
gharchive/issue
I did leave it open but not syncing Wallet has been open for days and is not syncing. I closed it opened it and still not syncing. maybe its your firewall? what os? theres not enough information here for us to help.
2025-04-01T04:35:52.409344
2020-08-11T11:27:05
676799596
{ "authors": [ "nitan2001", "vetriedi" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11855", "repo": "vernemq/vernemq", "url": "https://github.com/vernemq/vernemq/issues/1604" }
gharchive/issue
Vernemq Permission denied error Environment VerneMQ Version: OS:ubuntu 16.04 Erlang/OTP version (if building from source):Erlang/OTP 22 [erts-10.6.4] VerneMQ configuration (vernemq.conf) or the changes from the default Cluster size/standalone:standalone make rel cmd successfully created the release ===> Including Erts from /usr/lib/erlang ===> release successfully created! root@ubuntu-listener:/option/_build/default/rel/vernemq# bin/vernemq start bin/vernemq: 172: bin/vernemq: /option/_build/default/rel/vernemq/bin/../erts-10.6.4: Permission denied vmq_cluster_node_sup vernemq failed to start within 15 seconds, see the output of 'vernemq console' for more information. If you want to wait longer, set the environment variable WAIT_FOR_ERLANG to the number of seconds to wait. Hello vetriedi, Have you resolved this issue? Could you share it? Thank you.
2025-04-01T04:35:52.443585
2018-10-18T13:31:15
371531938
{ "authors": [ "ppatierno", "vietj", "wwhai" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11857", "repo": "vert-x3/issues", "url": "https://github.com/vert-x3/issues/issues/412" }
gharchive/issue
How to get vertx mqttClient info? I want to design a mqtt server with vertx MqttServer,Now I have complated a demo,This demo contains some simple function for remote mqtt client to connect. I have a question, how to get client info which have already connected? I can not found a API to get this info, please help me. this is core code: ` MqttServer mqttServer = MqttServer.create(vertx); List clientList =mqttServer.getClientList(); ` such this API it seems like a missing feature, WDYT @ppatierno ? On 18 Oct 2018, at 21:31, wangwenhai<EMAIL_ADDRESS>wrote: I want to design a mqtt server with vertx MqttServer,Now I have complated a demo,This demo contains some simple function for remote mqtt client to connect. I have a question, how to get client info which have already connected? I can not found a API to get this info, please help me. this is core code: ` MqttServer mqttServer = MqttServer.create(vertx); List clientList =mqttServer.getClientList(); ` such this API — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/vert-x3/issues/issues/412, or mute the thread https://github.com/notifications/unsubscribe-auth/AANxiteWOLZ9EiYiSaImf0NbCl7XEA8Uks5umIKkgaJpZM4Xtcai. Yeah it seems a new feature. @wwhai what kind of information would you like to see for a client? All the ones provided by the MqttEndpoint interface? Yeah it seems a new feature. @wwhai what kind of information would you like to see for a client? All the ones provided by the MqttEndpoint interface? Such as the number of the online mitt client or more detail, such of client's current state, etc; All of those are provided in Activemq,In Activemq we can sub a special topic to get current clients. I hope vertx-mqtt also provide the same interface,It can help us to monitor the client number in realtime. Yeah it seems a new feature. @wwhai what kind of information would you like to see for a client? All the ones provided by the MqttEndpoint interface? I hope next version MqttEndpoint interface or MqttServer can provider a method such this: List list=server/endpoint.getAllClient(); for(list)...... Though this interface we can get detail info what are realtime needs. I could think about providing the list of clients even because connection/endpoint(s) objects are already taken in memory but in any case, consider that ActiveMQ is a broker. The MQTT server is not a broker so it's out of its scope providing too much. FYI I have just opened this one https://github.com/vert-x3/vertx-mqtt/issues/107 thanks @ppatierno let's close this issue in favor of the new one
2025-04-01T04:35:52.458364
2022-11-21T03:11:09
1457225260
{ "authors": [ "DanDroryNano", "Todd-j-sutherland" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11858", "repo": "verteva/photon", "url": "https://github.com/verteva/photon/pull/245" }
gharchive/pull-request
D/plat 223 input phone Description ticket: https://verteva.atlassian.net/browse/PLAT-223 cx-branding: https://github.com/verteva/cx-branding/pull/22 Type of change [x] New feature (non-breaking change which adds functionality) PR checklist [x] I have run the test suite locally and fixed any issues that were caught [x] I have written unit tests for new functionality one piece of feedback is I can scroll past the available countries one piece of feedback is I can scroll past the available countries This has been the case in the original component as well... So I don't know if I should change this or not? I decided against it
2025-04-01T04:35:52.465454
2022-11-30T03:59:36
1469011250
{ "authors": [ "EternalllZM", "vertyco" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11859", "repo": "vertyco/vrt-cogs", "url": "https://github.com/vertyco/vrt-cogs/issues/41" }
gharchive/issue
[Feature Request] [Tickets] Multiple panels on single message It would be very useful if we could utilize a single message to host multiple different ticket panels/buttons that behave different. This would allow members to select what type of ticket they are opening so it can be directed to the correct category/team for remediation immediately. Thank you for considering. The cog will act as it does now, except now when adding a panel, you can specify a message that already has a button on it and that button will be added to it.
2025-04-01T04:35:52.466428
2023-11-28T05:18:58
2013665694
{ "authors": [ "lvyanquan" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11860", "repo": "ververica/flink-cdc-connectors", "url": "https://github.com/ververica/flink-cdc-connectors/pull/2767" }
gharchive/pull-request
[cdc-runtime] maintain a set of TableId in DataSinkWriterOperator maintain a set of TableId in DataSinkWriterOperator to make sure that a CreateTableEvent is sent before all DataChangeEvents with the same TableId. @PatrickRen @leonardBang PTAL.
2025-04-01T04:35:52.482727
2020-12-26T07:40:36
774837294
{ "authors": [ "FoggyFinder", "codecov-io" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11861", "repo": "verybadcat/CSharpMath", "url": "https://github.com/verybadcat/CSharpMath/pull/187" }
gharchive/pull-request
Fix ci build [x] Build / [ ] Test / Codecov Report Merging #187 (9386557) into master (2431d7d) will decrease coverage by 0.02%. The diff coverage is n/a. @@ Coverage Diff @@ ## master #187 +/- ## ========================================== - Coverage 87.34% 87.31% -0.03% ========================================== Files 156 156 Lines 11329 11329 ========================================== - Hits 9895 9892 -3 - Misses 1434 1437 +3 Impacted Files Coverage Δ CSharpMath/Atom/MathList.cs 86.20% <0.00%> (-2.30%) :arrow_down: CSharpMath.Editor/MathKeyboard.cs 88.81% <0.00%> (-0.22%) :arrow_down: Continue to review full report at Codecov. Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 40b8ddf...9386557. Read the comment docs. Codecov Report Merging #187 (9386557) into master (2431d7d) will decrease coverage by 0.02%. The diff coverage is n/a. @@ Coverage Diff @@ ## master #187 +/- ## ========================================== - Coverage 87.34% 87.31% -0.03% ========================================== Files 156 156 Lines 11329 11329 ========================================== - Hits 9895 9892 -3 - Misses 1434 1437 +3 Impacted Files Coverage Δ CSharpMath/Atom/MathList.cs 86.20% <0.00%> (-2.30%) :arrow_down: CSharpMath.Editor/MathKeyboard.cs 88.81% <0.00%> (-0.22%) :arrow_down: Continue to review full report at Codecov. Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 40b8ddf...9386557. Read the comment docs.
2025-04-01T04:35:52.503013
2024-10-12T18:44:41
2583326084
{ "authors": [ "angelozerr", "theodorklauritzen" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11862", "repo": "vespa-engine/vespa", "url": "https://github.com/vespa-engine/vespa/issues/32583" }
gharchive/issue
What about using LSP4IJ ? I notice that you have implemented your own LSP. Please note that we have released https://github.com/redhat-developer/lsp4ij which is a free IntelliJ LSP support plugin. You can see plugins which are based on LSP4IJ at https://github.com/redhat-developer/lsp4ij?tab=readme-ov-file#who-is-using-lsp4ij I suggest that you read https://idetools.dev/blog/lsp4ij-announcement/ article to have an overview of LSP4IJ. If you want to evaluate it, check out the following documentation: LSP4IJ's LSP Support Developer's Guide LSP Console And if you want to quickly evaluate LSP4IJ without developing a plugin but just by filling a parameter in your ls startup command, please check https://github.com/redhat-developer/lsp4ij/blob/main/docs/UserDefinedLanguageServer.md All lsp features like completion, sem1ntic tokens, rename etc that you have implemented are supported by lsp4ij Hope you could be interested with LSP4IJ Thank you for the great feedback, @angelozerr! I’ve updated our IntelliJ plugin to use LSP4IJ, which seems to be working better than the built-in features in the Ultimate edition. I noticed in the guide that we’re instructed to exclude LSP4J as a dependency. Do you know if this is necessary when our LSP4J instance is in a separate JAR, run by a separate process? Thank you for the great feedback, @angelozerr! I’ve updated our IntelliJ plugin to use LSP4IJ, which seems to be working better than the built-in features in the Ultimate edition. Wow that's great! I noticed in the guide that we’re instructed to exclude LSP4J as a dependency. Do you know if this is necessary when our LSP4J instance is in a separate JAR, run by a separate process? I think it is better to do that because if your LSPJ version is not the same that LSPJ version from LSP4IJ you will have some problem. Could you please: add your plugin in https://github.com/redhat-developer/lsp4ij?tab=readme-ov-file#who-is-using-lsp4ij if you think that LSP4IJ isgood, add a review at https://plugins.jetbrains.com/plugin/23257-lsp4ij/edit/reviews to help us to promote LSP4IJ, thanks! Perfect! I've crated a PR in LSP4IJ to add our plugin there and I'll write a review.
2025-04-01T04:35:52.505486
2019-09-19T17:17:39
495927196
{ "authors": [ "baldersheim", "bratseth" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11863", "repo": "vespa-engine/vespa", "url": "https://github.com/vespa-engine/vespa/pull/10739" }
gharchive/pull-request
Bratseth/vip logic take 2 @baldersheim don't merge, this is just to inform you that I'm on it @baldersheim please review This test is way too slow, but I think I'm out of time for today. Also, I think we can gc the code in prelude.cluster now. From the PR build it looks like this test is also unstable. I think we need to write it to work in a single thread. It is limited by the ping rate, I guess the simplest is to increase that. I will run it some times and see before I merge. I made the test drive the pings itself. Hopefully that should make it stable.
2025-04-01T04:35:52.508070
2021-01-07T13:54:41
781330278
{ "authors": [ "arnej27959" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11864", "repo": "vespa-engine/vespa", "url": "https://github.com/vespa-engine/vespa/pull/15950" }
gharchive/pull-request
Arnej/add distance threshold I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner. @geirst please review @geirst PTAL i think it's enough to just test some simple cases. @geirst PTAL i think it's enough to just test some simple cases. Note: this breaks the query serialization protocol. Note: this breaks the query serialization protocol. @geirst now added the hack with flag in allow_approximate @geirst now added the hack with flag in allow_approximate
2025-04-01T04:35:52.509101
2017-11-14T12:42:19
273778856
{ "authors": [ "baldersheim", "havardpe" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11865", "repo": "vespa-engine/vespa", "url": "https://github.com/vespa-engine/vespa/pull/4116" }
gharchive/pull-request
Always hold the lock when accessing the handler map. Simplify, and avoid naked new. @geirst or @havardpe PR Small one with no semantic changes. 👍
2025-04-01T04:35:52.511243
2016-02-29T07:01:47
137169724
{ "authors": [ "AurelWu", "vexe" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11866", "repo": "vexe/VFW", "url": "https://github.com/vexe/VFW/issues/81" }
gharchive/issue
Is there support for NetworkBehaviour? the readme says to replace monobehaviour with betterbehaviour, nothing is mentioned at all when it comes to multiplayers / networkbehaviour, so I assume there is no current support for that? This has been asked multiple times, see VFW thread post #439. Due to the way (inflexibility) the Unity editor system works, you have to duplicate code to get it to work. Ideally you'd want to mark your class with [VFW] or something without having to inherit from BaseBehaviour etc. But that will require a revamping of the entire Editor class to work this way.
2025-04-01T04:35:52.520290
2022-09-09T09:53:57
1367581790
{ "authors": [ "asset-web", "wooorm" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11867", "repo": "vfile/vfile-reporter-json", "url": "https://github.com/vfile/vfile-reporter-json/pull/8" }
gharchive/pull-request
#7: Extend messagesToJson to support reporting well known fields, suc… …h as actual, expected, url and note; Update tests to reflect extra fields Initial checklist [x] I read the support docs [x] I read the contributing guide [x] I agree to follow the code of conduct [x] I searched issues and couldn’t find anything (or linked relevant results below) [x] If applicable, I’ve added docs and tests Description of changes Implement #7 Extended messagesToJson to support reporting well known fields, such as actual, expected, url and note Updated tests to reflect extra fields Updated documentation to include new fields Friendly ping! Had some time to solve this myself today. Went ahead and credited you, released in 3.2.0! Thanks Tessa :)
2025-04-01T04:35:52.645219
2024-02-06T15:04:20
2121007159
{ "authors": [ "dorien-er", "rcannood" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11868", "repo": "viash-hub/biobase", "url": "https://github.com/viash-hub/biobase/pull/18" }
gharchive/pull-request
Busco list datasets Description add component to list available busco datasets (that can be used in the busco component) Issue ticket number Closes #xxxx Checklist before requesting a review [x] I have performed a self-review of my code [x] Conforms to the Contributing guidelines [x] Proposed changes are described in the CHANGELOG.md [x] I have tested my code with viash ns test --parallel -q <name or namespace> Check the correct box. Does this PR contain: [ ] Breaking changes [x] New functionality [ ] Major changes [ ] Minor changes [ ] Documentation [ ] Bug fixes this is a supporting component that's referenced in busco/busco, is it useful to add the help text here again, since they're already present in busco/busco? this is a supporting component that's referred to in busco/busco, is it useful to add the help text here again, since they're already present in busco/busco? One possibility is to add it to one entry but structure it a little bit, e.g. Add busco: busco run (#...) busco list (#...) busco download (#...) this is a supporting component that's referred to in busco/busco, is it useful to add the help text here again, since they're already present in busco/busco? One possibility is to add it to one entry but structure it a little bit, e.g. Add busco: busco run (#...) busco list (#...) busco download (#...) WDYT? Sounds good... But what about the help.txt file - doesn't seem useful to have that seem file in all 3 subcomponents, shall I just leave it under the main component only?
2025-04-01T04:35:52.659360
2017-07-14T05:28:33
242900977
{ "authors": [ "take-five", "vic" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11869", "repo": "vic/params", "url": "https://github.com/vic/params/pull/21" }
gharchive/pull-request
Fix Dialyzer warnings for Elixir 1.4/OTP 20 After running Dialyzer on OTP 20, following warnings have been emitted: :0: Unknown type 'Elixir.Map':t/0 :0: Unknown type 'Elixir.Struct':t/0 lib/params.ex:198: Function defaults/2 will never be called This commit fixes those warnings and also removes unused auto-generated defaults/2 function. Thank you <3 ! Could you please release a patch version with this small fix? Done, published 2.0.3, thank you again :)
2025-04-01T04:35:52.667376
2018-05-06T11:43:58
320585495
{ "authors": [ "NataliaBondarenko", "victordomingos" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11870", "repo": "victordomingos/Count-files", "url": "https://github.com/victordomingos/Count-files/pull/3" }
gharchive/pull-request
proposed changes in the project structure, unit tests proposed changes in the project structure, unit tests, dataset for tests, gitignore Hello! Please, check out changes in the project structure. Tests are usually stored in a separate folder. Accordingly, you need to import the parser and the main function into test files. Therefore, I propose to make changes to be able to automate the search for bugs on fork https://github.com/NataliaBondarenko/Count-files Hi! You have done a lot of work. Thanks again for contributing. I have a question. Now that the application is composed of more that one file shouldn’t it be made into a package, with all the code separated from tests, README file...? That would probably make easier the installation. I must confess I never submitted anything to Pypi, so I have no experience with setup.py files and the rest of the process, but feels to me like we should further separate executable files from documentation and tests. What do you think? https://github.com/pypa/sampleproject/blob/master/setup.py line 128. Do not worry :) Thank you for your cooperation. I am also interested in this project.
2025-04-01T04:35:52.839677
2017-05-26T06:19:52
231536075
{ "authors": [ "gongchao", "greypants" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11871", "repo": "vigetlabs/blendid", "url": "https://github.com/vigetlabs/blendid/issues/445" }
gharchive/issue
you can join gulp-useref ?? In the new version? I'm not familiar with gulp-useref... so no? What are you wanting to do?
2025-04-01T04:35:52.851854
2024-01-24T22:38:01
2099230894
{ "authors": [ "spartanhaden", "vikhyat" ], "license": "Apache-2.0", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11872", "repo": "vikhyat/moondream", "url": "https://github.com/vikhyat/moondream/issues/15" }
gharchive/issue
Better support for GPU and Flash Attention during inference The inference code provided in this repository forces moondream to run on CPU. We should allow the user to leverage GPUs and Flash Attention for faster inference if they want to. Added CUDA support in #22
2025-04-01T04:35:52.865556
2016-04-07T05:12:29
146511412
{ "authors": [ "betaveros", "chrisbra" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11873", "repo": "vim-airline/vim-airline-themes", "url": "https://github.com/vim-airline/vim-airline-themes/pull/32" }
gharchive/pull-request
Tweak jellybeans for more readability, information OK, a much smaller set of tweaks I wanted to see: darken green background of INSERT (to match original) restore orange modified highlight unify 2nd sections, deduplicate 3rd sections make sides of inactive bar brighter for better readability I know this is largely a matter of taste, but hopefully these are reasonably uncontroversial. I think points 1 and 4 increase readability, point 2 adds information, point 3 is partly bookkeeping and partly changing the rather counterintuitive way the center sections brighten and the 2nd sections darken simultaneously when switching from Normal to anything else. can you post a screenshot please? is this OK? So this is the new patched version? Can you also post a screenshot of the current non-patched version? thanks looks good.
2025-04-01T04:35:52.906791
2017-10-04T12:28:18
262768613
{ "authors": [ "Blaze349", "lcd047" ], "license": "WTFPL", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11874", "repo": "vim-syntastic/syntastic", "url": "https://github.com/vim-syntastic/syntastic/issues/2084" }
gharchive/issue
Syntastic weird behaviour First syntastic shows me an incorrect error. I then had to delete the file. Once I deleted the file and recreated it exactly the same way (very few lines of code) the error disappeared. Is there a way for me to clear the errors without deleting the files? I can't really parse what you're saying, but perhaps this could help: :h :SyntasticReset. I stand corrected. Syntastic is still showing this error You do understand that syntastic doesn't know anything about C++ and just runs third-party linters, right? Hmm, so these linters don't scan through header files? It's up to you to configure them how to run to avoid useless error messages. It's all described in the manual. I'm confused because I didn't have to do any of this before and I don't usually do this. I'm equally confused: do you expect me to guess what you did in the past, what you're doing now, and why the two differ? :smile: Sorry but I do have another thing to futher muddle this issue. No error here. Why does Syntastic report an error there but not here? Syntastic doesn't, one of the linters does. It may not even be the same linter. Enable debugging to find out what's going on (see :h syntastic-config-makeprg and :h syntastic-debug). Then it will become clear what each linter does, and you'll be able to reproduce the same results by running said linters in a terminal. Then I'll be able to tell you to ask the developers of those linters why they produce the results you're seeing. :smile: syntastic: 3.335576: g:syntastic_version = '3.8.0-84 (Vim 800, Darwin)' syntastic: 3.335699: &shell = '/bin/bash', &shellcmdflag = '-c', &shellpipe = '2>&1| tee', &shellquote = '', &shellredir = '>%s 2>&1', &shelltemp = 1, &shellxquote = '', &autoc hdir = 0, &shellxescape = '' syntastic: 3.336104: UpdateErrors (auto): default checkers syntastic: 3.336414: CacheErrors: default checkers syntastic: 3.337095: g:syntastic_aggregate_errors = 0 syntastic: 3.337298: getcwd() = '/Users/Me/Programming/Pokemon-Clone' syntastic: 3.337678: CacheErrors: no checkers available for cpp syntastic: 3.337771: aggregated: {'_sorted': 0, '_name': '', '_owner': 1, '_columns': 1, '_rawLoclist': []} syntastic: 3.337678: CacheErrors: no checkers available for cpp Which means syntastic didn't even get to run. You have some other plugin (perhaps YCM?) that produces the errors you're accusing. Hmm. I looked at another thread and it followed :SyntasticInfo and this was my output Syntastic version: 3.8.0-84 (Vim 800, Darwin) Info for filetype: cpp Global mode: active Filetype cpp is active The current file will be checked automatically Available checker: gcc Currently enabled checkers: - Checkers for filetype cpp possibly disabled by YouCompleteMe Checkers for filetype cpp possibly disabled by YouCompleteMe Well then, this was quick. Yep, to fix this I disabled the diagnostic UI for YouCompleteMe. Everything is now functional, I think. I believe even that is covered in the manual: :h syntastic-ycm.
2025-04-01T04:35:52.910481
2022-06-18T18:41:17
1275856889
{ "authors": [ "bfrg", "heavenshell" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11875", "repo": "vim/vim", "url": "https://github.com/vim/vim/issues/10591" }
gharchive/issue
Vim9: unexpected error when invoking '% delete _' Steps to reproduce Run this shell command: vim -Nu NONE -S <(cat <<'EOF' vim9script silent % delete _ EOF ) E1050 is raised: E1050: Colon required before a range: % delete _ If not vim9script, it's works fine. also, deletebufline() works fine. vim -Nu NONE -S <(cat <<'EOF' vim9script silent deletebufline('%', 1, '$') EOF ) Expected behaviour No error is raised. Version of Vim 8.2.5125 Environment Operating system: Ubuntu 20.04 Terminal: Terminal.app(ssh from macOS) value of $TERM: xterm-256color shell: bash Logs and stack traces Error detected while processing command line..script /dev/fd/11: line 2: E1050: Colon required before a range: % delete _ You need to add a colon like the error message indicates: silent :%delete _
2025-04-01T04:35:52.920596
2016-09-26T13:16:41
179225659
{ "authors": [ "iCyMind", "k-takata", "nuko8", "oblitum" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11876", "repo": "vim/vim", "url": "https://github.com/vim/vim/issues/1118" }
gharchive/issue
Highlight VertSplit do not function correctly version: vim8.0 (+termguicolors) vimrc: set termguicolors :highlight Normal guibg=red works well. :highlight VertSplit guibg=NONE do not affect the vertsplitbar background color. :highlight VertSplit guibg=NONE cterm=NONE works well @iCyMind With exactly the same settings as used in your report above, run vim and do :highlight VertSplit. Then you'll know what colors and graphical attributes are set for VertSplit. If you don't find guibg=<color> there but only gui=reverse or something else other than color specifications, then you'll understand that :highlight VertSplit guibg=NONE won't/shouldn't make sense; after all, there's been no color to be overwritten by the :highlight command from the beginning. If guibg is set to a valid value , the command should work as expected. Sorry, I have not expressed clearly above. I meet this issue vim with iTerm2 3.0(truecolor support). As :h termguicolors says, the vim should use guibg/guifg attributes in the terminal. When :hi VertSplit guibg=NONE, it do make VertSplitBar's bg transparent in GUIvim/MacVim/neovim. But nothing happen in vim unless :hi VertSplit cterm=NONE. I don't know it's a bug or not, maybe I misunderstand the "termguicolors" option. But in my opinion, the neovim's behavior is more reasonable. When :hi VertSplit guibg=NONE, it do make VertSplitBar's bg transparent in GUIvim/MacVim Note that what "transparent" exactly means is that the background is painted in the same background color around the object to be painted. Eventually, the background of the object appears as if it were made transparent. Knowing that, you'll see why vim and gvim behave differently. /neovim. I know of it, but haven't used it yet. I have nothing to say about that. But in my opinion, the neovim's behavior is more reasonable. I don't think so. Neovim has no GUI; therefore, the existence of guibg is nonsense and illogical, and the use of it is an abuse. I wonder how you could call that "more reasonable." I don't know it's a bug or not, maybe I misunderstand the "termguicolors" option. I think this issue invalid for vim because of its inaccurate description of the problem and irrational comparison with what one cannot compare with. Maybe related (or duplicate?): #981 In a sense, one can say that they are related each other... But there's a subtle difference between them. As to the background color to be used, one comes from vim's internal (this issue) and another from the terminal (#981). To avoid giving further mess, I intentionally refrained from quoting #981. :) thanks for reply. But in my opinion, the neovim's behavior is more reasonable. I don't think so. Neovim has no GUI; therefore, the existence of guibg is nonsense and illogical, and the use of it is an abuse. I wonder how you could call that "more reasonable." You may stop at that since you said yourself to have never tried NeoVim. guibg is perfectly logical for NeoVim since it was first created not to exist through its first frontend, the terminal, but to be embedded by any GUI frontend. You may think of NeoVim as a core that can bring Vim mode to other editors. Hence guibg should still make perfect sense. Second, it was Vim that started with the idea of bringing GUI colors to the terminal by means of termguicolors. So if that's nonsense, it started with Vim. The Vim implementation of that is not uniform as already explained, NeoVim's implementation makes more sense indeed. I don't know it's a bug or not, maybe I misunderstand the "termguicolors" option. I think this issue invalid for vim because of its inaccurate description of the problem and irrational comparison with what one cannot compare with.
2025-04-01T04:35:52.924306
2023-05-29T21:34:45
1731255002
{ "authors": [ "chrisbra", "lbrayner" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11877", "repo": "vim/vim", "url": "https://github.com/vim/vim/issues/12464" }
gharchive/issue
+command, -c command is executed after VimEnter Steps to reproduce for n in {1..1001}; do { < /dev/urandom tr -dc A-Za-z0-9 | head -c30; echo; } ; done > /var/tmp/thousand_one_lines.txt vim --clean -u /var/tmp/WinEnter.vim -c "vsplit" /var/tmp/thousand_one_lines.txt /var/tmp/WinEnter.vim is: set nocompatible set number set relativenumber function! s:Number() set number set relativenumber " setting nonumber if length of line count is greater than 3 if len(line("$"))>3 set nonumber endif endfun augroup Number autocmd! autocmd VimEnter * autocmd Number \ BufRead,BufEnter,BufWritePost * call s:Number() autocmd VimEnter * call s:Number() " Triggered at window creation on startup, disabled after autocmd WinEnter * call s:Number() autocmd VimEnter * autocmd! Number WinEnter augroup END if v:vim_did_enter doautocmd Number VimEnter endif Expected behaviour Both windows have 'number' set to false, i.e, the WinEnter autocmd was triggered. Version of Vim 8.2.2434 Environment Ubuntu 20.04 st st-256color zsh Logs and stack traces No response I only see that relativenumber is set and not number with 9.0.1569. Can you please try with an uptodate vim?
2025-04-01T04:35:52.927234
2024-06-03T01:31:28
2329988751
{ "authors": [ "chrisbra", "lkintact", "ubaldot" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11878", "repo": "vim/vim", "url": "https://github.com/vim/vim/issues/14901" }
gharchive/issue
Just a typo in the docs Steps to reproduce In $VIMRUNTIME/pack/dist/opt/matchit/doc/matchit.txt, line 177, hat been loaded should be changed to has been loaded. Expected behaviour . Version of Vim 9.1.443 Environment . Logs and stack traces No response I plan to send a PR for improving the docs of :h typename() soon. I could fix this as well if you all agree. this issue belongs to https://github.com/chrisbra/matchit/
2025-04-01T04:35:52.935255
2019-01-16T08:28:38
399697019
{ "authors": [ "mattn", "ychin" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11879", "repo": "vim/vim", "url": "https://github.com/vim/vim/issues/3808" }
gharchive/issue
gVim on Windows starts with a tiny window when using "set guioptions+=k" Bug When running gVim on Windows, if you have set guioptions +=k in vimrc, the window will be really tiny (see screenshot). The user has to manually resize it for it to be in a usable size. This issue doesn't show up if the 'k' guioptions wasn't set. Screenshot Cause This bug was introduced by #3616. See my comment (https://github.com/vim/vim/pull/3616#issuecomment-449952161) for more details. We can't just fix this by reverting that PR (which changed initialization to call gui_set_shellsize with FALSE) since it would break the original issue it's trying to fix (#3615), but we should probably find a way to initialize it properly so it still works with set guioptions+=k in vimrc. Can this solve this? diff --git a/src/gui.c b/src/gui.c index d993bc6b0..3d2e632bf 100644 --- a/src/gui.c +++ b/src/gui.c @@ -682,7 +682,11 @@ gui_init(void) // Set the shell size, adjusted for the screen size. For GTK this only // works after the shell has been opened, thus it is further down. // For MS-Windows pass FALSE for "mustset" to make --windowid work. - gui_set_shellsize(FALSE, TRUE, RESIZE_BOTH); + // But if go+=k specified, resize forcibly. + if (vim_strchr(p_go, GO_KEEPWINSIZE) == NULL) + gui_set_shellsize(FALSE, TRUE, RESIZE_BOTH); + else + gui_set_shellsize(TRUE, TRUE, RESIZE_BOTH); #endif #if defined(FEAT_GUI_MOTIF) && defined(FEAT_MENU) /* Need to set the size of the menubar after all the menus have been I don't make sure that it is needed to checking whether --windowid or --socketid is specified. I think this patch wouldn't completely fix the issue. If a user's vimrc has set go+=k and launches gVim using --windowid he would still see the issue that #3616 is trying to fix (that the window size doesn't look maximized). Looking more into it, the issue is that when you pass --windowid in, these lines in gui_mch_init(void) will maximize the window (win_socket_id would be non-null in this case): if (s_hwnd != NULL && win_socket_id != 0) { SetParent(s_hwnd, (HWND)win_socket_id); ShowWindow(s_hwnd, SW_SHOWMAXIMIZED); } As I mentioned in https://github.com/vim/vim/pull/703#issuecomment-199448937, if the window is maximized, we should be calling gui_set_shellsize(FALSE,…) to initialize with the system's provided dimensions. Otherwise, we should pass call gui_set_shellsize(TRUE,…) to initialize with Vim's default lines/columns dimensions regardless of whether GO_KEEPWINSIZE is. The original patch (#703) just assumed gVim never starts maximized. For reference this is the code in gui_set_shellsize(int mustset, …) that shows the behavior: /* If not setting to a user specified size and maximized, calculate the * number of characters that fit in the maximized window. */ if (!mustset && (vim_strchr(p_go, GO_KEEPWINSIZE) != NULL || gui_mch_maximized())) { gui_mch_newfont(); return; } I think this following patch should fix the issue in Windows. I need to see if there are other lurking issues with the GTK implementation as well (even though this issue isn't related to the GTK GUI). This also fixes a bug in gui_init_font(…), where if you call set guifont=… when maximized, it will bump you out of the maximized state. diff --git a/src/gui.c b/src/gui.c index 39968954a..dc99919ae 100644 --- a/src/gui.c +++ b/src/gui.c @@ -681,8 +681,13 @@ gui_init(void) #ifndef FEAT_GUI_GTK // Set the shell size, adjusted for the screen size. For GTK this only // works after the shell has been opened, thus it is further down. - // For MS-Windows pass FALSE for "mustset" to make --windowid work. - gui_set_shellsize(FALSE, TRUE, RESIZE_BOTH); + // If the window is already maximized (e.g. when --windowid is passed in), + // we want to use the system-provided dimensions by passing FALSE to + // mustset. Otherwise, we want to initialize with the default rows/columns. + if (gui_mch_maximized()) + gui_set_shellsize(FALSE, TRUE, RESIZE_BOTH); + else + gui_set_shellsize(TRUE, TRUE, RESIZE_BOTH); #endif #if defined(FEAT_GUI_MOTIF) && defined(FEAT_MENU) /* Need to set the size of the menubar after all the menus have been @@ -721,7 +726,10 @@ gui_init(void) # endif /* Now make sure the shell fits on the screen. */ - gui_set_shellsize(TRUE, TRUE, RESIZE_BOTH); + if (gui_mch_maximized()) + gui_set_shellsize(FALSE, TRUE, RESIZE_BOTH); + else + gui_set_shellsize(TRUE, TRUE, RESIZE_BOTH); #endif /* When 'lines' was set while starting up the topframe may have to be * resized. */ @@ -906,7 +914,7 @@ gui_init_font(char_u *font_list, int fontset UNUSED) # endif gui_mch_set_font(gui.norm_font); #endif - gui_set_shellsize(TRUE, TRUE, RESIZE_BOTH); + gui_set_shellsize(FALSE, TRUE, RESIZE_BOTH); } return ret; After scrubbing through the code seems like the only real place that sets mustset to TRUE outside of this is when you call :win or :set lines/:set columns. This means if you are in maximized mode calling :win 100 100 will put you back to windowed mode. I'm not sure if that's the desired behavior or not (seems like :win should just be ignored in maximized mode).
2025-04-01T04:35:52.940184
2020-10-19T18:10:20
724864257
{ "authors": [ "lacygoill" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11880", "repo": "vim/vim", "url": "https://github.com/vim/vim/issues/7172" }
gharchive/issue
Vim9: E1069 not raised when white space missing after comma in dictionary in :def function Describe the bug In Vim9 script, E1069 is not raised when white space is missing after a comma in a dictionary in a :def function. To Reproduce Run this shell command: vim -Nu NONE -S <(cat <<'EOF' vim9script def Func() var d = #{k1: 1,k2: 2} enddef Func() EOF ) No error is raised. Expected behavior E1069 is raised: E1069: White space required after ',' Because a comma is missing between the two items in the dictionary: var d = #{k1: 1,k2: 2} ^ ✘ Environment Vim version: 8.2 Included patches: 1-1865 OS: Ubuntu 16.04.7 LTS Terminal: xterm(360) Additional context An error is correctly raised at the script level: vim9script var d = #{k1: 1,k2: 2} E1069: White space required after ',' Duplicate of https://github.com/vim/vim/issues/6672. Sorry for the noise.
2025-04-01T04:35:52.947238
2020-11-15T18:05:53
743310743
{ "authors": [ "brammool", "lkintact" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11881", "repo": "vim/vim", "url": "https://github.com/vim/vim/issues/7302" }
gharchive/issue
A couple of corrections to the docs As the count parameter for the :z and :z# commands is optional, the {count}s at :help :z and :help :z# should perhaps be replaced with [count]s. Also, perhaps for better understanding the scrs ('scroll' values?) in the table at :help :z should be replaced with cnts (counts). Vim version: 8.2.1980. As the count parameter for the :z and :z# commands is optional, the {count}s at :help :z and :help :z# should perhaps be replaced with [count]s. Also, perhaps for better understanding the scrs ('scrolls'?) in the table at :help :z should be replaced with cnts (counts). Does this seem right: {range}z[+-^.=][count] Display several lines of text surrounding the line specified with {range}, or around the current line if there is no {range}. If there is a [count], that's how many lines you'll see; if there is no [count] and only one window then twice the value of the 'scroll' option is used, otherwise the current window height minus 3 is used. This is the value of "scr" in the table below. If there is a [count] the 'window' option is set to its value. -- hundred-and-one symptoms of being an internet addict: 250. /// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net \ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \ \\ an exciting new programming language -- http://www.Zimbu.org /// \\ help me help AIDS victims -- http://ICCF-Holland.org /// Does this seem right: I think it does. It just occurred to me that {range} should be changed to [range], since it's, too, optional. Yes, the range here is also optiona. The docs are corrected now, so closing.
2025-04-01T04:35:52.948572
2022-10-11T05:41:23
1404034912
{ "authors": [ "brammool", "tillmanmatthew" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11882", "repo": "vim/vim", "url": "https://github.com/vim/vim/pull/11343" }
gharchive/pull-request
Typo in os_haiku.txt Simply add ncurses and not ncurses6 to build 9.x from scratch on haiku beta 3. Using ncurses6 will cause configure to fail. Also, the multi-line command examples didn't end properly in my mind but it's out of scope for this fix. I'll include it, thanks.
2025-04-01T04:35:52.949676
2024-06-24T07:32:00
2369465537
{ "authors": [ "chrisbra", "ubaldot" ], "license": "Vim", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11883", "repo": "vim/vim", "url": "https://github.com/vim/vim/pull/15091" }
gharchive/pull-request
Added Deprecation Warnings As discussed, here is a proposal for introducing Deprecation Warnings. Let's see if it could be a viable solution for handling old stuff without creating too much unhappy users. I took the freedom to set a deadline 1 Jan 2025, but we can discuss on possible time-windows of course. thanks!
2025-04-01T04:35:53.024781
2017-05-22T11:33:04
230366777
{ "authors": [ "TheDancerCodes", "suraj-afrogleap" ], "license": "apache-2.0", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11884", "repo": "vincentbrison/vb-android-app-quality", "url": "https://github.com/vincentbrison/vb-android-app-quality/issues/22" }
gharchive/issue
Checkstyle classpath {null} When updating the gradle wrapper to 3.5, checkstyle fails. @suraj-afrogleap Any luck finding a solution for this? @TheDancerCodes Ended up using checkstyle version 5.9. @suraj-afrogleap It worked! Thanks a lot.
2025-04-01T04:35:53.055390
2021-04-22T20:28:44
865439450
{ "authors": [ "dpetrovaliev", "vinkla" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11885", "repo": "vinkla/laravel-hashids", "url": "https://github.com/vinkla/laravel-hashids/issues/147" }
gharchive/issue
Wrong return type of Facade methods Hi, I'm using 8.1.0 version of your package and just spotted that the return types of these methods are wrong: https://github.com/vinkla/laravel-hashids/blob/8.1.0/src/Facades/Hashids.php I've seen that this is fixed in 9.X versions. Are you planing a release of a minor fix of this for 8.X version? Are you planing a release of a minor fix of this for 8.X version? There are no plans on releasing a fix for version 8. I suggest you update to version 9.
2025-04-01T04:35:53.060519
2016-10-04T22:57:36
181026288
{ "authors": [ "christstuart", "lfarah", "vinnyoodles" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11886", "repo": "vinnyoodles/TRMosaicLayout", "url": "https://github.com/vinnyoodles/TRMosaicLayout/issues/7" }
gharchive/issue
Swift 3 compatibility Hey, I'd love to see this lib available in Swift 3 so I can implement it in my project. Thanks 😄 I'll try to merge in https://github.com/vinnyoodles/TRMosaicLayout/pull/6 this weekend Thanks, @vinnyoodles! 🎉 Sorry for the delay, I wasn't able to push it yet because I'm still on the old Xcode 7. Will get it out ASAP @vinnyoodles any progress in the swift 3 implementation? Just updated 😄 Thanks @vinnyoodles, you're awesome! 🎉
2025-04-01T04:35:53.132419
2023-11-04T14:34:03
1977370777
{ "authors": [ "ignatandrei", "vipwan" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11887", "repo": "vipwan/Biwen.AutoClassGen", "url": "https://github.com/vipwan/Biwen.AutoClassGen/issues/3" }
gharchive/issue
Does not generate files -please help I am trying to do an example at https://github.com/ignatandrei/RSCG_Examples/tree/143-biwenautoclassgen You can find the sources at v2\rscg_examples\Biwen.AutoClassGen\src\FromInterface.sln It cannot compile because it will not find [AutoGen("Person", "FromInterface")] ( The purpose of the example is to add to my list of RSCG , https://ignatandrei.github.io/RSCG_Examples/v2/docs/List-of-RSCG ) Yes, in order to use this library you also need to add a nuget reference dotnet add package Biwen.AutoClassGen.Attributes --version 1.0.0 I have added . Still not generate files into obj\GX folder <ItemGroup> <PackageReference Include="Biwen.AutoClassGen" Version="<IP_ADDRESS>" OutputItemType="Analyzer" ReferenceOutputAssembly="false" /> <PackageReference Include="Biwen.AutoClassGen.Attributes" Version="1.0.0" /> </ItemGroup> <PropertyGroup> <EmitCompilerGeneratedFiles>true</EmitCompilerGeneratedFiles> <CompilerGeneratedFilesOutputPath>$(BaseIntermediateOutputPath)\GX</CompilerGeneratedFilesOutputPath> </PropertyGroup> ``` Take a look at the test case scenarios I provided, GEN001: The interface marked [AutoGen] should be inherent one or more interface I have modified public interface IPerson { [StringLength(100), Description("person first name")] string FirstName { get; set; } // string LastName { get; set; } //public string FullName(); } and using Biwen.AutoClassGen.Attributes; namespace FromInterface; [AutoGen("Person", "FromInterface")] public interface IPerson2: IPerson { } And still no file generated pls download my demo code, which can be compiled, your repository is too big for me to download https://github.com/vipwan/Biwen.AutoClassGen/tree/master/Biwen.AutoClassGen.TestConsole I have done this to test with Nuget in your project Cloned your project replace in Biwen.AutoClassGen.TestConsole.csproj <ItemGroup> <ProjectReference Include="..\Biwen.AutoClassGen.Attributes\Biwen.AutoClassGen.Attributes.csproj" /> </ItemGroup> <ItemGroup> <ProjectReference Include="..\Biwen.AutoClassGen.Gen\Biwen.AutoClassGen.csproj" OutputItemType="Analyzer" ReferenceOutputAssembly="false" /> with their nuget definitions <ItemGroup> <PackageReference Include="Biwen.AutoClassGen" Version="<IP_ADDRESS>" OutputItemType="Analyzer" ReferenceOutputAssembly="false" /> <PackageReference Include="Biwen.AutoClassGen.Attributes" Version="1.0.0" /> </ItemGroup> Delete the bin and obj folders from Biwen.AutoClassGen.TestConsole Rebuild Biwen.AutoClassGen.TestConsole Biwen.AutoClassGen\Biwen.AutoClassGen.TestConsole\Program.cs(7,27,7,39): error CS0234: The type or namespace name 'QueryRequest' does not exist in the namespace 'Biwen.AutoClassGen.Models' (are you missing an assembly reference?) Nothing in obj\GX Could you reproduce ? global using Biwen.AutoClassGen.Attributes; global using Biwen.AutoClassGen.Models; Yes, there are in file _GloableUsings The problem is that Roslyn is not generating files in obj/GX ( QueryRequest is fully generated by your code ) Please replace in Biwen.AutoClassGen.TestConsole.csproj the reference to the projects with their NuGet counterparts. I have done this to test with Nuget in your project Cloned your project replace in Biwen.AutoClassGen.TestConsole.csproj <ItemGroup> <ProjectReference Include="..\Biwen.AutoClassGen.Attributes\Biwen.AutoClassGen.Attributes.csproj" /> </ItemGroup> <ItemGroup> <ProjectReference Include="..\Biwen.AutoClassGen.Gen\Biwen.AutoClassGen.csproj" OutputItemType="Analyzer" ReferenceOutputAssembly="false" /> with their nuget definitions <ItemGroup> <PackageReference Include="Biwen.AutoClassGen" Version="<IP_ADDRESS>" OutputItemType="Analyzer" ReferenceOutputAssembly="false" /> <PackageReference Include="Biwen.AutoClassGen.Attributes" Version="1.0.0" /> </ItemGroup> Delete the bin and obj folders from Biwen.AutoClassGen.TestConsole Rebuild Biwen.AutoClassGen.TestConsole Biwen.AutoClassGen\Biwen.AutoClassGen.TestConsole\Program.cs(7,27,7,39): error CS0234: The type or namespace name 'QueryRequest' does not exist in the namespace 'Biwen.AutoClassGen.Models' (are you missing an assembly reference?) Nothing in obj\GX Could you reproduce ? I've used it in my project and it works great https://github.com/vipwan/Biwen.QuickApi/blob/master/Biwen.QuickApi.DemoWeb/Apis/AutoClassGenApi.cs Oh, your API is .NET 8. I have .NET 7 ;-) . Maybe .... this is the difference Oh, your API is .NET 8. I have .NET 7 ;-) . Maybe .... this is the difference Hmm, it seems to me that Net6-8 can all pass the test ;-) Oh, your API is .NET 8. I have .NET 7 ;-) . Maybe .... this is the difference I'm not sure about this, it may have something to do with the environment of the IDE , I'm using VS2022 Preview This could be also a difference( I am using VS2022 Version 17.7.6 ). Let's wait for .NET 8 and latest VS2022 and I will be back with news... Works with .NET 8 https://ignatandrei.github.io/RSCG_Examples/v2/docs/Biwen.AutoClassGen Thanks!
2025-04-01T04:35:53.181081
2020-10-25T19:16:40
729092306
{ "authors": [ "MrGadget1024", "cosmoddd" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11888", "repo": "vis2k/Mirror", "url": "https://github.com/vis2k/Mirror/issues/2371" }
gharchive/issue
Mislaeding comment for the AddPlayer function based on outdated usage. https://github.com/vis2k/Mirror/blob/8c08ecf84d4734df4944771d88e7be70a3dcef42/Assets/Mirror/Runtime/ClientScene.cs#L124 This sentence in the comments is obsolete: "If an extra message was passed to AddPlayer, then OnServerAddPlayer will be called with a NetworkReader that contains the contents of the message." AddPlayer doesn't actually accept another parameter and the Migration Guide states this explicitly. Its use seems geared towards prefabs that don't require additional customization. This comment has caused confusion for my students attempting to implement spawning of custom characters in their projects. Suggestion: Delete this sentence from the linked comment line, delete line 125 below it, and possibly mention the use of NetworkMessages instead. Yep, you found a doc mistake leftover from our changing this method...thanks! Will fix it shortly for next release. fixed
2025-04-01T04:35:53.182220
2019-11-04T13:08:35
517140784
{ "authors": [ "paulpach" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11889", "repo": "vis2k/Mirror", "url": "https://github.com/vis2k/Mirror/pull/1203" }
gharchive/pull-request
refactor: remove redundant authority set on host This code should not be here. it calls OnStopAuthority on the server if it previously had authority. But that can only happen in host mode. This is redundant because the client will do it again when it receives the message. actually not working
2025-04-01T04:35:53.183034
2021-03-18T20:27:42
835225215
{ "authors": [ "JesusLuvsYooh", "MrGadget1024" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11890", "repo": "vis2k/Mirror", "url": "https://github.com/vis2k/Mirror/pull/2657" }
gharchive/pull-request
Added new syncScale boolean to NT Test writer. Added new syncScale boolean to NT Test writer. tests pass locally...appveyor is borked...merging.
2025-04-01T04:35:53.185132
2021-07-14T23:03:48
944858423
{ "authors": [ "MrGadget1024", "vis2k" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11891", "repo": "vis2k/Mirror", "url": "https://github.com/vis2k/Mirror/pull/2834" }
gharchive/pull-request
fix: Add get/set to NetworkServer dontListen I really hate negative bools. Fixes: #2536 thanks. commited a more simple fix for the issue in https://github.com/vis2k/Mirror/commit/08c74deca0eae53097bf86a68b9083135940c253 thanks. commited a more simple fix for the issue in 08c74de You totally missed the point of my PR, and yours does not fix either of the issues you closed. Reopening both.
2025-04-01T04:35:53.186980
2019-02-28T01:11:40
415400617
{ "authors": [ "MrGadget1024", "rodolphito", "vis2k" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11892", "repo": "vis2k/Mirror", "url": "https://github.com/vis2k/Mirror/pull/478" }
gharchive/pull-request
Moved NetworkStartPosition to Components. This is a component, and as such should be in Components. Nothing depends on this, get it out of 'core'. On hold pending internal decisions you aren't wrong. but from a practical point of view, people definitely need NetworkStartPosition in their projects. I would consider it 'core'. for example, in uMMORPG I have a custom start position, but it does inherit from NetworkStartPosition. unlike my custom prox checker, which doesn't inherit from mirror one. and unlike my custom transform, which doesn't inherit from mirror transform. closing this for now, sorry. we need to test if we can weaver mirror.dll - then we wouldn't have those discussions and could leave it all in one folder
2025-04-01T04:35:53.203368
2020-02-23T19:10:16
569542447
{ "authors": [ "Qix-", "coveralls", "profiprog" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11893", "repo": "visionmedia/debug", "url": "https://github.com/visionmedia/debug/pull/748" }
gharchive/pull-request
Fixes: Unable to take control over selectColor #747 Simple fix Coverage remained the same at 87.692% when pulling b593fdfa10d97f52f1a0e141843e932a37332c17 on profiprog:master into 0c1d5180ff9559b506c8b431b24842bed0e8a5e2 on visionmedia:master. Good catch :) Thank you! Published as 4.2.0 under the beta dist-tag. Please test and make sure nothing has broken for you before I send to latest.
2025-04-01T04:35:53.205665
2016-02-07T15:05:14
131974495
{ "authors": [ "montaro" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11894", "repo": "visionmedia/supertest", "url": "https://github.com/visionmedia/supertest/issues/309" }
gharchive/issue
expect(status, callback) doesn't work as expected only if done is passed it(\'allows an admin user to get all user's upvotes, [] when null\', (done) => { agent.get(``/login/test/${seedVars.adminUser.id}``).expect(200).end(() => { agent.get(``/interaction/by/${seedVars.user.id}``).end((error, result) => { expect(result.status).to.equal(200); expect(result.body).to.deep.equal([]); done(); }); }); }); The first 200 check is totally discarded, however the second form to check on the message in the end() body worked. I expected that to work as it's typical usage like the dos, Am I missing something? Only if done is passed, it works as expected. Thanks! I believe it is working as documented, my bad! the assertion of the status code happens if a callback passed, is passed as a first argument as an error object to the callback, which needs no much effort with done() as done() expects the first argument as failure
2025-04-01T04:35:53.212983
2019-02-26T21:16:08
414822818
{ "authors": [ "aowen87", "cyrush" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11895", "repo": "visit-dav/visit", "url": "https://github.com/visit-dav/visit/issues/323" }
gharchive/issue
install hdfview with hdf5 installations cqid: VisIt00008149cqsubmitter: Mark Millercqsubmitdate: 07/24/07 Customer would like someone to take charge of installing hdfview (java tool) when hdf5 is installed. -----------------------REDMINE MIGRATION----------------------- This ticket was migrated from Redmine. As such, not all information was able to be captured in the transition. Below is a complete record of the original redmine ticket. Ticket number: 311 Status: Pending Project: VisIt Tracker: Feature Priority: Normal Subject: install hdfview with hdf5 installations Assigned to: - Category: - Target version: - Author: Mark Miller Start: Due date: % Done: 0% Estimated time: Created: 08/04/2010 01:26 pm Updated: Likelihood: Severity: Found in version: Impact: 4 - High Expected Use: 4 - Common OS: All Support Group: DOE/ASC Description: cqid: VisIt00008149cqsubmitter: Mark Millercqsubmitdate: 07/24/07 Customer would like someone to take charge of installing hdfview (java tool) when hdf5 is installed. Comments: closing, we won't tackle deploying hdf5view
2025-04-01T04:35:53.222012
2022-06-23T16:24:58
1282660155
{ "authors": [ "markcmiller86" ], "license": "BSD-3-Clause", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11896", "repo": "visit-dav/visit", "url": "https://github.com/visit-dav/visit/pull/17811" }
gharchive/pull-request
Add text macros Description Resolves #5242 Refactors text annotation classes to put all text handling in one place Expands list of text anntation macros to include many things Adds database comment to avtDataAttributes so it can be included in text annotation macros Allows sprintf-style format specification of the macros Allows macros to appear multiple times in the same annotation Allows multiple macros to appear in the same annotation Still working on in-line comments, docs, relnotes and tests. Am attaching here a screen shot of annotation and string used to produce it. This demonstrates using $cycle twice in same string and setting formatting for the first intstance. The $dbcomment is displaying the database comment. Type of change [ ] Bug fix [x] New feature~~ [ ] Documentation update [ ] Other How Has This Been Tested? Checklist: [x] I have followed the style guidelines of this project.~~ [x] I have performed a self-review of my own code.~~ [x] I have commented my code where applicable.~~ [x] I have updated the release notes.~~ [ ] I have made corresponding changes to the documentation.~~ [ ] I have added debugging support to my changes.~~ [ ] I have added tests that prove my fix is effective or that my feature works.~~ [ ] I have confirmed new and existing unit tests pass locally with my changes.~~ [ ] I have added new baselines for any new tests to the repo.~~ [x] I have NOT made any changes to protocol or public interfaces in an RC branch.~~ [x] I have assigned reviewers (see VisIt's PR procedures for more information).~~ Ok, the compile is failing here... In file included from /__w/1/s/src/avt/VisWindow/Colleagues/avtText2DColleague.h:12:0, from /__w/1/s/src/avt/VisWindow/Colleagues/VisWinAnnotations.C:16: /__w/1/s/src/avt/VisWindow/Colleagues/avtAnnotationWithTextColleague.h:35:17: error: ‘unique_ptr’ in namespace ‘std’ does not name a template type static std::unique_ptr<avtDataAttributes> initialDataAttributes; ^~~~~~~~~~ avt/VisWindow/CMakeFiles/avtviswindow_ser.dir/build.make:80: recipe for target 'avt/VisWindow/CMakeFiles/avtviswindow_ser.dir/Colleagues/VisWinAnnotations.C.o' failed Looks like I am missing a #include <memory> there. Fixing now.
2025-04-01T04:35:53.242684
2015-07-17T05:59:59
95593552
{ "authors": [ "AlexDM0", "amithit", "cdjackson", "christophdebaene", "dylandechant", "mg1075" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11897", "repo": "visjs/angular-visjs", "url": "https://github.com/visjs/angular-visjs/issues/37" }
gharchive/issue
network.fit() for network graph behind hidden tab It might help if the directive is updated to include network.fit() so that a network graph behind a hidden tab is handled better in terms of network position. What do you mean by 'updated' to include this - exactly what would you propose to add? You are of course free to call network.fit if you want already? When the following line in the visNetwork directive is called, network = new vis.Network(element[0], scope.data, scope.options); I think calling network.fit() here would be necessary because otherwise what happens when you have a network graph behind a tab (like an angular-ui tab) is that the network graph gets positioned to the upper left corner. By calling network.fit() in the directive, this problem can be avoided. However, that looks like only part of the problem. I notice that when the window is resized, the network graph does not adjust its size/position, so I am wondering if the directive needs a listener for the window resize event as well. http://stackoverflow.com/questions/28044124/vis-graph-library-responsive-design-issue-with-twitter-bootstrap I prefer to avoid putting listeners like this in directives as it enforces a certain configuration that might not be to everyones liking. Personally, I agree - I have a directive that resizes the div that contains certain elements, but I would prefer to avoid adding it to the vis directive. I have the same problem when using a network graph behind a bootstrap tab that isn't positioned correctly and that the network.fit() should be called. Is it possible to provide some sample code how this can be accomplished by creating an extra custom directive? Can you put a listener to call network.fit when the tab is changed? I use the following directive to resize a bootstrap panel with a vis directive inside (just adding the element resize-panel to the panel). angular.module('ResizePanel', []) .directive('resizePanel', function ($window) { return { restrict: 'A', link: function ($scope, element, attrs) { var top = element[0].offsetTop; var w = angular.element($window); $scope.getWindowDimensions = function () { if ($(element).is(":visible") === false) { return; } var pa = element.parent('.panel'); var top = pa.offset().top; var h = pa[0].offsetHeight; var h1 = element[0].offsetHeight; $scope.headerSize = h - h1; var pHeight = (w.height() - $scope.headerSize - top - 25); element.css('height', pHeight + 'px'); return { 'h': w.height() }; }; $scope.$watch($scope.getWindowDimensions, function (newValue, oldValue) { }, true); w.bind('resize', function () { if(!$scope.$$phase) { $scope.$apply(); } }); } }; }) ; Oh - and I think you then need to ensure that the panel, and the div that contains the vis directive is set to width/height = 100%... I've not tried this with network, but you should (??) hopefully be able to customise it... Let me know how it goes. Hi All, I'll address this issue for the next release which should be within 1 or 2 weeks. I will make sure that the viewport will look exactly the same as it did before the change in container size but scaled correctly. Regards, Alex On 10 aug. 2015, at 22:14, Chris Jackson<EMAIL_ADDRESS>wrote: Can you put a listener to call network.fit when the tab is changed? I use the following directive to resize a bootstrap panel with a vis directive inside (just adding the element resize-panel to the panel). angular.module('ResizePanel', []) .directive('resizePanel', function ($window) { return { restrict: 'A', link: function ($scope, element, attrs) { var top = element[0].offsetTop; var w = angular.element($window); $scope.getWindowDimensions = function () { if ($(element).is(":visible") === false) { return; } var pa = element.parent('.panel'); var top = pa.offset().top; var h = pa[0].offsetHeight; var h1 = element[0].offsetHeight; $scope.headerSize = h - h1; var pHeight = (w.height() - $scope.headerSize - top - 25); element.css('height', pHeight + 'px'); return { 'h': w.height() }; }; $scope.$watch($scope.getWindowDimensions, function (newValue, oldValue) { }, true); w.bind('resize', function () { if(!$scope.$$phase) { $scope.$apply(); } }); } }; }) ; — Reply to this email directly or view it on GitHub. Wow, thank you for the quick response. I will try it out and looking forward for the next release. Regards, Christoph It's not the right place, but as a quick fix, I have added the javascript below in the directive and it works fine now. $('a[data-toggle="tab"]').on('shown.bs.tab', function (e) { network.fit(); }); Hi, Just to give you a heads up, the fix I plan on implementing will ensure that the view center and range are preserved (for as much as possible given that aspect ratio may change on a resize). This is different from a fit, as that zooms out to encompass the entire network. If a fit is what you're after than this fix will have to remain in place after my fix :). Regards On 11 aug. 2015, at 21:15, Christoph De Baene<EMAIL_ADDRESS>wrote: It's not the right place, but as a quick fix, I have added the javascript below in the directive and it works fine now. $('a[data-toggle="tab"]').on('shown.bs.tab', function (e) { network.fit(); }); — Reply to this email directly or view it on GitHub. Is there any update on this? Hi, It is not possible to fit on a hidden tab. You should manually call fit on showing the network. Regards Hey Thanks Alex, Sorry new to angular and just figuring this out, a little help would go a long way. in my view i have <div class="process-tabview" ng-controller="flowChartCtrl"> <div class="col s12"> <ul class="tabs"> <li class="tab col s3"><a href="#process-workspace" class="active">Process View</a></li> <li class="tab col s3"><a class="" href="#list-view">List View</a></li> <li class="tab col s3" ng-click="fitNetwork()"><a href="#neighborhood-view" >Neighborhood View</a></li> </ul> </div> </div> <div id="neighborhood-view"> <div ng-controller="flowChartCtrl" > <vis-network data="testdata" options="options" height="100%" resize-tab></vis-network> </div> </div> then in my controller I have $scope.fitNetwork = function(){ vis.network.fit(); }; i keep getting TypeError: vis.network.fit is not a function Does this need to be done in the directive? Thanks! Hi, I can't help you there. I don't use angular. Maybe Chris can help out for this specific question? It sounds like vis.network is undefined and I'd think it's scoping. Regards On 01 Mar 2016, at 22:13, dylan dechant<EMAIL_ADDRESS>wrote: Hey Thanks Alex, Sorry new to angular and just figuring this out, a little help would go a long way. in my view i have Process View List View Neighborhood View then in my controller I have $scope.fitNetwork = function(){ vis.network.fit(); }; i keep getting TypeError: vis.network.fit is not a function Does this need to be done in the directive? Thanks! — Reply to this email directly or view it on GitHub. It’s a bit hard to tell what you’re doing, but I suspect you should be using the onload callback to get the vis object and store it in your controller. I have a graph component in React app, <Graph graph={this.state.graph} options={graph_options} events={this.events} /> I hope to make it automatically zoom in/out when the graph changes, just like in vis.js document use network.fit() But how I can call this fit method?
2025-04-01T04:35:53.262723
2017-05-10T15:06:34
227712087
{ "authors": [ "Marahin", "kulte", "philnash" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11898", "repo": "visualitypl/textris", "url": "https://github.com/visualitypl/textris/issues/31" }
gharchive/issue
Question: Clean way to call Texter when User phone number is not a required field? Perhaps this is a nit-pick, but currently we always have to do something like: UserTexter.welcome(user).deliver_later if user.phone? Since the call to #welcome will fail without an E.164 compliant phone number, we cannot handle this at the job level. Also, returning nil from #welcome such that we now call: UserTexter.welcome(user)&.deliver_later doesn't seem like much of an improvement. I'm wondering if this is consistent behavior in terms of the API for ActionMailer, and we just don't have to deal with this case because email is a field that does have a not-null constraint. What is the way that you would imagine handling calling Texter methods in an app where phone is allowed to be null? I personally see no problem with you needing to guard against calling a method that will fail without a phone number. You wouldn't expect ActionMailer to send an email for an object without an email address, nor would you ask it to, so there should be no difference in Textris. I'd also argue that UserTexter.welcome(user)&.deliver_later is just obscuring your intention. Perhaps to make it even clearer, you should tell the job the arguments it needs rather than passing it an object to extract arguments from. The most obvious intention comes from something like: UserTexter.welcome(user.email).deliver_later if user.phone? Then your UserTexter just needs to receive an email address as an argument. Just an idea. There hasn't been any comments since, so I assume this issue is resolved. Thanks @philnash!
2025-04-01T04:35:53.270954
2023-10-21T11:28:27
1955450587
{ "authors": [ "barnagoz", "prisis" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11899", "repo": "visulima/visulima", "url": "https://github.com/visulima/visulima/issues/227" }
gharchive/issue
Import of next/router throws error in nextra-theme-docs Pre-Checks [X] Follow our Code of Conduct. [X] Read the Contributing Guidelines. [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [X] Make sure this is a Visulima issue and not related to a combination with another package. [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. [X] The provided reproduction is a minimal reproducible example of the bug. [ ] I am willing to provide a PR. Describe the bug Hey! I have a nextra project and I successfully found your theme for it, which I really like. Currently my site is accessible at info.e5vosdo.hu. When I try to install the theme (as the documentation shows me, except I just edit some files and don't create them) I get the following error: ⨯ Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/barnabasgoz/Development/do/web/node_modules/next/router' imported from<EMAIL_ADDRESS>Did you mean to import next/router.js? at new NodeError (node:internal/errors:399:5) at finalizeResolution (node:internal/modules/esm/resolve:226:11) at moduleResolve (node:internal/modules/esm/resolve:839:10) at defaultResolve (node:internal/modules/esm/resolve:1069:11) at DefaultModuleLoader.resolve (node:internal/modules/esm/loader:307:12) at DefaultModuleLoader.getModuleJob (node:internal/modules/esm/loader:156:32) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:33) at link (node:internal/modules/esm/module_job:75:36) { code: 'ERR_MODULE_NOT_FOUND', page: '/' } Minimal reproduction code Clone the nextra docs template (https://github.com/shuding/nextra-docs-template Install the deps your project needs npm i next react react-dom nextra @visulima/nextra-theme-docs Install other deps npm i Edit next.config.js const withNextra = require("nextra")({ theme: "@visulima/nextra-theme-docs", themeConfig: "./theme.config.tsx", }); module.exports = withNextra(); Run development server Additional Context Environment Info System: OS: macOS 12.6.8 CPU: (4) x64 Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz Memory: 1.50 GB / 16.00 GB Shell: 5.8.1 - /bin/zsh Binaries: Node: 20.1.0 - /usr/local/bin/node Yarn: 3.2.4 - /usr/local/bin/yarn npm: 9.8.1 - /usr/local/bin/npm pnpm: 8.6.1 - /usr/local/bin/pnpm Browsers: Safari: 16.6 npmPackages: @visulima/nextra-theme-docs: ^4.0.3 => 4.0.3 Which module system do you use? [ ] CJS [X] ESM Used Package Manager npm Hey @barnagoz, the newest version should fix all your issues :)
2025-04-01T04:35:53.278398
2024-12-23T13:13:03
2756050681
{ "authors": [ "krishnadadhirao", "vitabaks" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11900", "repo": "vitabaks/autobase", "url": "https://github.com/vitabaks/autobase/issues/858" }
gharchive/issue
Private IP conflict while deploying my own machine While using the UI console and deploying a single node server the etcd.conf and patroni.yml file is generating using the public IP where as it has to be on the Private IP, but I don't see an option to give both Public and Private IP Patroni is not starting because of that TASK [patroni : Start patroni service on the Master server] ******************** changed: [103.*.*.*] TASK [patroni : Wait for port 8008 to become open on the host] ***************** fatal: [103.*.*.*]: FAILED! => {"changed": false, "elapsed": 121, "msg": "Timeout when waiting for 103.**,.*:8008"} 8008 is already open and accessible In the current version of the UI, only private IP addresses can be specified. Doc: https://autobase.tech/docs/deployment/your-own-machines Understood, I have deployed the console in a dedicated server in the same network Still facing the issue with patroni TASK [patroni : Prepare PostgreSQL | generate default PostgreSQL config files] *** [WARNING]: Module remote_tmp /tmp/postgres/ansible did not exist and was created with a mode of 0700, this may cause issues when running as another user. To avoid this, create the remote_tmp dir with the correct permissions manually changed: [<IP_ADDRESS>] TASK [patroni : Prepare PostgreSQL | make sure the data directory "/var/lib/postgresql/15/main" is empty] *** changed: [<IP_ADDRESS>] => (item=absent) changed: [<IP_ADDRESS>] => (item=directory) TASK [patroni : Start patroni service on the Master server] ******************** changed: [<IP_ADDRESS>] TASK [patroni : Wait for port 8008 to become open on the host] ***************** fatal: [<IP_ADDRESS>]: FAILED! => {"changed": false, "elapsed": 120, "msg": "Timeout when waiting for <IP_ADDRESS>:8008"} NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* <IP_ADDRESS> : ok=105 changed=56 unreachable=0 failed=1 skipped=373 rescued=0 ignored=0 localhost : ok=2 changed=0 unreachable=0 failed=0 skipped=238 rescued=0 ignored=0 sudo journalctl -u patroni -f detailed logs Dec 24 19:16:40 <IP_ADDRESS> patroni[68313]: AttributeError: 'int' object has no attribute 'encode' Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: patroni.service: Main process exited, code=exited, status=1/FAILURE Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: patroni.service: Failed with result 'exit-code'. Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: patroni.service: Consumed 1.629s CPU time. Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: patroni.service: Scheduled restart job, restart counter is at 10. Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: Stopped Runners to orchestrate a high-availability PostgreSQL - Patroni. Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: patroni.service: Consumed 1.629s CPU time. Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: patroni.service: Start request repeated too quickly. Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: patroni.service: Failed with result 'exit-code'. Dec 24 19:16:41 <IP_ADDRESS> systemd[1]: Failed to start Runners to orchestrate a high-availability PostgreSQL - Patroni. Please attach patroni log sudo journalctl -u patroni -n 100 The issue is resolved now, it had nothing do with patroni or etcd for hostname and IP address I gave the IP address which was creating a conflict in patroni configuration, when I gave a different name it got deployed without any issue
2025-04-01T04:35:53.289732
2016-11-07T13:05:43
187706895
{ "authors": [ "BukicMicko", "ckosloski" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11901", "repo": "vitalets/angular-xeditable", "url": "https://github.com/vitalets/angular-xeditable/issues/571" }
gharchive/issue
e-ta-max-text to count html tags I am using editable-text-angular for rich editor. I am using e-ta-max-text attribute for counting max characters. This is working fine. However I was curious if I can somehow change this e-ta-max-text to count also html tags, for example: asd to count 10 characters and not 3. For text-angular part i added one more charcountall with taRegisterTool: taRegisterTool('charcountall', { display: '<div id="toolbarCC" style="display:block; min-width:120px;">Characters with markup: <span ng-bind="charcountall"></span></div>', disabled: true,, charcountall: 0,, activeState: function () { // this fires on keyup, var editor = this.$editor();, var html = editor.html;, var noOfChars = html.length;, this.charcountall = noOfChars;, editor.charcountall = noOfChars;, return false; } I am using this editable-text-angular in this way: <a class="clickable" editable-text-angular="vm.title" e-ta-max-text="1000" e-name="title" ng-click="editableTitleForm.$show(); edit = true" ng-show="!editableTitleForm.$visible"> I don't understand what your question is for xeditable? Counting is an issue for text-angular and not xeditable. @ckosloski you are right I should have add this question to textAngular github cause this ta-max-text is from that directive... Sorry for this. NP, please close this issue. Hey @ckosloski sorry for reopening this again, but I have one question. Can I use ng-maxlength for editable-text-angular? I was using e-ta-max-text but it is not counting html tags so my idea is to use ng-maxlength and to disable save button if we have maxalenth form error. Something like this: <form editable-form name="editableTitleForm"> <div> <a class="clickable" editable-text-angular="reviewvm.findingOrObservationTitle" e-name="title" ng-maxlength="5" ng-click="editableTitleForm.$show(); edit = true" ng-show="!editableTitleForm.$visible"> <div ng-if="reviewvm.findingOrObservationTitle" data-ng-bind-html="reviewvm.findingOrObservationTitle"></div> </a> </div> <span ng-show="editableTitleForm.$visible"> <button type="submit" class="btn btn-primary" ng-disabled="editableTitleForm.$waiting || editableTitleForm.title.$error.maxlength"> Save </button> </span> </form> You would have to use e-ng-maxlength="5" hm... I tried also with e-ng-maxlength but it is not working. I tried in in this way: <a class="clickable" editable-text-angular="reviewvm.findingOrObservationAddBac" e-name="background" e-ng-maxlength="5" ng-click="editableBackgroundForm.$show(); edit = true" ng-show="!editableBackgroundForm.$visible"> <button type="submit" class="btn btn-primary" ng-disabled="editableBackgroundForm.$waiting || editableBackgroundForm.background.$error.maxlength"> Save </button> And when I reach 5 characters button is not getting disabled. Is the ng-maxlength being placed on the input created by text-angular directive? hm...I was somehow thinking that this e-ng-maxlength can also work on a href tag on which we have this editable-text-angular. I suppose I cannot do that so will close this issue. Also I tried to somehow get this charcount from text-angular with textAngularManger.retireveEditor('title').charcount but it is not working with combination with angular-xeditable.... The only other thing you could try is maybe add a e-ng-change=countMethod($data) which calls a method to see the length of the current input and displays an error. Well that can be a good solution I will give a try, but I also just implement it in this way: I am using onbeforesave function on href tag and I am checking if characters together with html tags are more that max return string message that will be showin before reach text editor. <a class="clickable" editable-text-angular="reviewvm.findingOrObservationTitle" e-name="title" e-form="editableTitleForm" onbeforesave="reviewvm.checkCharacterLength($data, editableTitleForm)" function checkCharacterLength (data, form) { var length = data.length; switch (form.$name) { case 'titleForm': if (length > 1000){ return 'character length exceeded' } } }
2025-04-01T04:35:53.292135
2013-04-29T12:20:22
13757330
{ "authors": [ "AmaliDeveloper", "paeon" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11902", "repo": "vitalets/x-editable", "url": "https://github.com/vitalets/x-editable/issues/221" }
gharchive/issue
input mask not working? SOLVED Hi, I need to use an input mask, have tried with the on.shown event $('#username').on('shown', function () { $(this).data('editable').input.$input.mask('999'); }); Could only get this to work with jquery-1.8.2.min Tony Hey you can get the solution for this problem here Good Work Link
2025-04-01T04:35:53.319029
2024-01-05T17:53:51
2067795216
{ "authors": [ "Danones", "KermanX", "bluwy", "hi-ogawa" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11903", "repo": "vitejs/vite", "url": "https://github.com/vitejs/vite/issues/15516" }
gharchive/issue
Remix + Tailwind on hmr update and reload the CSS breaks Describe the bug When adding/editing a css property with tailwind classes, OR When adding, removing or chaning a JSX element, Vite HMR detects the change , and the page becomes stripped of css. So we basically loose all our styles. I was having this issue in my companies project, but I could easily reproduce it in a new project. Reproduction https://github.com/Danones/remix-vite-tailwind-repro Steps to reproduce Open the reproduction project. Get the project running by using the following command npm run dev; Get Tailwind running in watch mode: npx tailwindcss -i ./styles.css -o ./src/output.css --watch Open the Browser on http://localhost:5173/ and make sure all styles are ok. Check the content of the _index.tsx file. You will notice that there is some JSX commented out in line 41 {/* <p className="text-5xl bg-red-200 font-bold ">Test</p> */} Uncomment , and save. If you check the UI, should be now stripped from CSS. Momentarily I was able to get it working when I initially created the project, but when I restarted the server I could never get it working anymore. System Info System: OS: macOS 14.1.1 CPU: (8) arm64 Apple M1 Pro Memory: 94.33 MB / 16.00 GB Shell: 5.9 - /bin/zsh Binaries: Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node Yarn: 1.22.21 - /opt/homebrew/bin/yarn npm: 9.5.1 - ~/.nvm/versions/node/v18.16.0/bin/npm Browsers: Chrome: 120.0.6099.199 Safari: 17.1 npmPackages: vite: ^5.0.0 => 5.0.11 Used Package Manager npm Logs No response Validations [X] Follow our Code of Conduct [X] Read the Contributing Guidelines. [X] Read the docs. [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead. [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. [X] The provided reproduction is a minimal reproducible example of the bug. I found that when I manually edit the output.css, the page still loses its styles. Something interesting: I run the dev command with DEBUG="vite:hmr" and noticed that when Tailwind compiler changes output.css, Vite doesn't output [file change] src/output.css, but when manually modified output.css, Vite does. I personally think it is not a Vite bug, because in other projects Vite is OK to update CSS files that are changed. I think it is a Remix plugin bug. Your issue could be due to the unintended usage of tailwind on (Remix) Vite. For some time (since non Vite version), Remix supports tailwind/postcss out-of-box, so I don't think you need dedicated taiwlindcss --watch step in your setup and you can directly import raw tailwind css file. I updated your repro to illustrate this. Would this work for you? https://stackblitz.com/edit/github-4n9xrs?file=app%2Froutes%2F_index.tsx Here are few references from their documentation: https://remix.run/docs/en/main/styling/tailwind#tailwind https://remix.run/docs/en/main/future/vite#enable-tailwind-via-postcss (Btw, Remix Vite is still labelled as "unstable", so it might be better to report the issue there first for visibility of Remix's maintainer. I think it's more likely for people there to help the issue than people here) I couldn't reproduce the issue with the repro given. It seems to always update fine for me. If you could slim down the issue to a plain Vite project, we could probably look deeper if it's a Vite issue. Otherwise it might be a Remix issue. Your issue could be due to the unintended usage of tailwind on (Remix) Vite. For some time (since non Vite version), Remix supports tailwind/postcss out-of-the-box, so I don't think you need dedicated taiwlindcss --watch step anymore. Instead of that, you can directly import raw tailwind css file. I updated your repro to illustrate this. Would this work for you? https://stackblitz.com/edit/github-4n9xrs?file=app%2Froutes%2F_index.tsx //// in app/routes/_index.ts // import "../../src/output.css"; import '../../styles.css'; Here are few references from their documentation: https://remix.run/docs/en/main/styling/tailwind#tailwind https://remix.run/docs/en/main/future/vite#enable-tailwind-via-postcss (Btw, Remix Vite is still labelled as "unstable", so it might be better to report the issue there first for visibility of Remix's maintainer. I think it's more likely for people there to help the issue than people here) Your suggestion doesn't work. Please try it locally and you will see what I mean; Also I was able to find the issue. I have noticed that I get hydration issues both in Firefox and Chrome browsers. And in this two browsers, the issue with the HMR and styles remain. However , after trying with Safari, everything was fine. ( you can do the test yourself) I decided to update react and react-dom to "^18.3.0-next-fccf3a9fb-20230213" and this has solved my issue. However this isn't ideal since I am working on a larger scale project. So it seems like this isn't ready yet. Also, your reproduction fork isn't something that produces trusty results because the serving and rendering is being done by stackblitz. I have noticed that I get hydration issues Regarding hydration error, there are a few known issues tracked on Remix. Though you might have already discovered about React 18.3, I'll reference this issue and comment by Remix team https://github.com/remix-run/remix/issues/4822#issuecomment-1672040945 so that Vite team can also know potentially relevant context. Yes I am well aware of that by now. I have spent the last couple of hours reading all the issues both in React and Remix communities. Like I said, the canary version seems to work fine by me. I am just wondering if the guys at Remix can do something about it 🤔 I think this is a React / Remix issue (which has been reproduced pre-Vite era of Remix), so let me close this. I hope Remix can adopt stable React 18.3 soon.
2025-04-01T04:35:53.346649
2024-11-21T03:55:01
2677881902
{ "authors": [ "sapphi-red", "zheung" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11904", "repo": "vitejs/vite", "url": "https://github.com/vitejs/vite/issues/18726" }
gharchive/issue
dev server cannot fallback to the corresponding `index.html when MPA entry points are specified Describe the bug In latest version 5.4.11, under dev, if index.html is missing from the preview path, entry points could not fallback to corresponding index.html. It always fallbacks to index.html in the root. Minimal vite config: import { resolve } from 'path'; export default { build: { target: 'esnext', rollupOptions: { input: { 'a': resolve(__dirname, 'a', 'index.html'), 'b': resolve(__dirname, 'a', 'b', 'index.html'), }, }, }, }; Maybe the table will help me express issue more clearly: Request Expected Current Matched? / /index.html /index.html yes /a /a/index.html /index.html no /a/index.html /a/index.html /a/index.html yes /a/b /a/b/index.html /index.html no a/b/index.html /a/b/index.html /a/b/index.html yes The link for reproduction is also ready. Although adding index.html to the end of the path is fine for previewing and debugging. But I don't think it's very intuitive to use. This section of the official guide supports my view: Align dev and preview HTML serving behaviour Reproduction https://stackblitz.com/edit/vitejs-vite-n8tdia?file=vite.config.js Steps to reproduce No response System Info System: OS: Windows 11 10.0.22631 CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700 Memory: 15.24 GB / 31.70 GB Binaries: Node: 20.18.0 - D:\runtime\node\node.EXE npm: 10.8.2 - D:\runtime\node\npm.CMD pnpm: 9.14.2 - ~\AppData\Roaming\npm\pnpm.CMD Browsers: Edge: Chromium (127.0.2651.74) Internet Explorer: 11.0.22621.3527 npmPackages: vite: ^5.4.0 => 5.4.11 Used Package Manager pnpm Logs No response Validations [X] Follow our Code of Conduct [X] Read the Contributing Guidelines. [X] Read the docs. [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead. [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. [X] The provided reproduction is a minimal reproducible example of the bug. Your reproduction shows 404. This section of the official guide supports my view: Align dev and preview HTML serving behaviour I don't think so. Quoting the related rows of the table in that docs: Request Before (dev) Before (preview) After (dev & preview) /dir /index.html (SPA fallback) /dir/index.html /index.html (SPA fallback) /dir/ /dir/index.html /dir/index.html /dir/index.html If I expand your expectation table, it will be: Request Your Expectation Current / /index.html /index.html /a /a/index.html /index.html /a/ - /a/index.html /a/index.html /a/index.html /a/index.html /a/b /a/b/index.html /index.html /a/b/ - /a/b/index.html a/b/index.html /a/b/index.html /a/b/index.html The best way does not exist here as all hosting providers' behavior differs: https://github.com/slorber/trailing-slash-guide The current behavior is what we thought the safest. Your reproduction shows 404. This section of the official guide supports my view: Align dev and preview HTML serving behaviour I don't think so. Quoting the related rows of the table in that docs: Request Before (dev) Before (preview) After (dev & preview) /dir /index.html (SPA fallback) /dir/index.html /index.html (SPA fallback) /dir/ /dir/index.html /dir/index.html /dir/index.html If I expand your expectation table, it will be: Request Your Expectation Current / /index.html /index.html /a /a/index.html /index.html /a/ - /a/index.html /a/index.html /a/index.html /a/index.html /a/b /a/b/index.html /index.html /a/b/ - /a/b/index.html a/b/index.html /a/b/index.html /a/b/index.html The best way does not exist here as all hosting providers' behavior differs: https://github.com/slorber/trailing-slash-guide The current behavior is what we thought the safest. reproduction link has been fixed, refresh issuse pls. Your reproduction shows 404. This section of the official guide supports my view: Align dev and preview HTML serving behaviour I don't think so. Quoting the related rows of the table in that docs: Request Before (dev) Before (preview) After (dev & preview) /dir /index.html (SPA fallback) /dir/index.html /index.html (SPA fallback) /dir/ /dir/index.html /dir/index.html /dir/index.html If I expand your expectation table, it will be: Request Your Expectation Current / /index.html /index.html /a /a/index.html /index.html /a/ - /a/index.html /a/index.html /a/index.html /a/index.html /a/b /a/b/index.html /index.html /a/b/ - /a/b/index.html a/b/index.html /a/b/index.html /a/b/index.html The best way does not exist here as all hosting providers' behavior differs: https://github.com/slorber/trailing-slash-guide The current behavior is what we thought the safest. Oh this is my fault. Other mistakes in my actual project and not reading that quoted document carefully led me to the wrong conclusion. Thanks for the answer!
2025-04-01T04:35:53.371344
2022-07-19T08:44:06
1309186607
{ "authors": [ "BigFrontEnd-China", "Hrishikesh-K", "JiatLn", "guilhermeportela", "jonaskuske", "lingdu1234", "robokozo", "sapphi-red", "ydcjeff" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11905", "repo": "vitejs/vite", "url": "https://github.com/vitejs/vite/issues/9213" }
gharchive/issue
when i build the vue3 project, i got a output file name like [component].vue_vue_type_script_setup_true_lang.[hash].js Describe the bug when i npm run build, i got a output file name like [component].vue_vue_type_script_setup_true_lang.[hash].js Reproduction https://github.com/JiatLn/vite-build-demo.git System Info System: OS: Windows 10 10.0.19042 CPU: (4) x64 Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz Memory: 1.36 GB / 7.88 GB Binaries: Node: 14.19.0 - E:\software\nodejs\node.EXE Yarn: 1.22.18 - E:\software\nodejs\yarn.CMD npm: 6.14.16 - E:\software\nodejs\npm.CMD Browsers: Edge: Spartan (44.19041.1266.0), Chromium (103.0.1264.62) Internet Explorer: 11.0.19041.1202 Used Package Manager yarn Logs No response Validations [x] Follow our Code of Conduct [X] Read the Contributing Guidelines. [X] Read the docs. [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead. [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. [X] The provided reproduction is a minimal reproducible example of the bug. What is the problem here? I think the problem is the weird output (comp.vue_vue_type_script_setup_true_lang.[hash].js) instead of [name].[hash].js. The name is generated by rollup from id(comp.vue?vue&type=script&setup=true&lang.js). We could treat vue files specially and replace the filename in generateBundle hook. But I don't think this causes any problem. I think there is another underlying issue here. It seems that the file is larger than expected as well. It's probably not a problem, except the cause is unknown. I did not have a problem in any of my other Vite 3 + Vue 3 projects. I haven't made many, but not sure what's happening here. Here's how my chunks folder looks: My Vite config: import {defineConfig} from 'vite' import vue from '@vitejs/plugin-vue' export default defineConfig({ build: { rollupOptions: { output: { assetFileNames: 'assets/[name].[ext]', chunkFileNames: 'chunks/[name].js', entryFileNames: 'entries/[name].js' } }, sourcemap: true, target: 'esnext' } }) Note that, badge is the only file from my components folder that's ending up like that: while all the other chunks are from my pages directory: I know this is not really useful without me actually providing a reproduction (as I've said, this doesn't always happen), but providing a reproduction is most likely going to be tough. If someone has some pointers on what to check (try to add/edit) to avoid this, that would be great! I have a guess that it will happen when the component had use to many times. It's probably not a problem, except the cause is unknown. I did not have a problem in any of my other Vite 3 + Vue 3 projects. I haven't made many, but not sure what's happening here. Here's how my chunks folder looks: My Vite config: import {defineConfig} from 'vite' import vue from '@vitejs/plugin-vue' export default defineConfig({ build: { rollupOptions: { output: { assetFileNames: 'assets/[name].[ext]', chunkFileNames: 'chunks/[name].js', entryFileNames: 'entries/[name].js' } }, sourcemap: true, target: 'esnext' } }) Note that, badge is the only file from my components folder that's ending up like that: while all the other chunks are from my pages directory: I know this is not really useful without me actually providing a reproduction (as I've said, this doesn't always happen), but providing a reproduction is most likely going to be tough. If someone has some pointers on what to check (try to add/edit) to avoid this, that would be great! Note that, the badge component is nothing fancy. It's a super simple component which is using defineProps, computed and is one of my smallest components. button for example is a bit complex than that - with various states and props, it goes about 200 lines. So, I don't think "complexity" of the component is an issue (not sure if it ever was), but that's my only guess. I have a guess that it will happen when the component had use to many times. Thank you for your message! I have a guess that it will happen when the component had use to many times. I don't think it's being used too many times, but even if that's the case, it still doesn't explain the weird name that component is getting while others are working as expected. I have the same problem! // package.json { "name": "demo-components", "private": true, "version": "0.0.0", "type": "module", "scripts": { "dev": "vite", "build": "vue-tsc --noEmit && vite build", "preview": "vite preview" }, "dependencies": { "vue": "^3.2.37" }, "devDependencies": { "@vitejs/plugin-vue": "^3.1.0", "typescript": "^4.6.4", "vite": "^3.1.0", "vue-tsc": "^0.40.4" } } // vite.config.ts import { defineConfig } from "vite"; import vue from "@vitejs/plugin-vue"; // https://vitejs.dev/config/ export default defineConfig({ mode: "production", build: { lib: { entry: "./src/components/index.ts", formats: ["cjs"], name: "components", }, rollupOptions: { external: ["vue"], output: [ { dir: "dist/components", format: "cjs", entryFileNames: "[name].js", preserveModules: true, preserveModulesRoot: "components", }, ], }, }, plugins: [vue()], }); I'm also seeing the same thing: ... dist/assets/dates.32565151.js dist/assets/ConfirmationButton.vue_vue_type_script_setup_true_lang.db3c1ab5.js dist/assets/SubtleSortToggleButton.vue_vue_type_script_setup_true_lang.d7615288.js dist/assets/index.350ee0b4.css ... @robokozo are you using any images, fonts, other kinds of assets? All assets are inlined into the JS/CSS files if you build in lib mode, so the generated JS/CSS files can get huge. @jonaskuske its a normal vue app. I can show the details tomorrow but the file is a relatively simple. It's a button that uses different classes based on a Boolean. I believe it only has 1 dependency on a file with interface definitions. i have the same problem ,not all the file,and not found any reason
2025-04-01T04:35:53.385713
2022-07-25T20:59:29
1317362458
{ "authors": [ "argyleink", "dutchcelt", "romainmenke", "sapphi-red" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11906", "repo": "vitejs/vite", "url": "https://github.com/vitejs/vite/issues/9368" }
gharchive/issue
CSS @layer bundling misses selectors inside media queries Describe the bug @import 'layers.css' layer(demo); where layers.css contains: h1 { color: red; } @media (min-width: 100px) { h1 { color: green; } } incorrectly produces: @layer demo { h1 { color: red; } } @media (min-width: 100px) { h1 { color: green; } } instead of (this is just one correct way): @layer demo { h1 { color: red; } @media (min-width: 100px) { h1 { color: green; } } } This means any media queries are unlayered, giving them the top most precedence and specificity over styles in layers. Vanilla Vite example: https://stackblitz.com/edit/vitejs-vite-vlemhc?file=layers.css,style.css Demo: https://vitejs-vite-vlemhc--5173.local.webcontainer.io/ I'd like a way to disable it for now, but don't see one. Reproduction https://stackblitz.com/edit/vitejs-vite-vlemhc?file=layers.css,style.css System Info System: OS: macOS 12.4 CPU: (16) x64 Intel(R) Xeon(R) W-2140B CPU @ 3.20GHz Memory: 799.40 MB / 64.00 GB Shell: 3.2.57 - /bin/bash Binaries: Node: 18.2.0 - /usr/local/bin/node npm: 8.9.0 - /usr/local/bin/npm Browsers: Chrome: 103.0.5060.134 Chrome Canary: 106.0.5201.0 Firefox: 102.0.1 Firefox Developer Edition: 102.0 Firefox Nightly: 103.0a1 Safari: 15.5 Safari Technology Preview: 15.4 npmPackages: vite: 3.0.2 => 3.0.2 Used Package Manager npm Logs No response Validations [X] Follow our Code of Conduct [X] Read the Contributing Guidelines. [X] Read the docs. [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead. [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. [X] The provided reproduction is a minimal reproducible example of the bug. I suspect this will be fixed by : https://github.com/postcss/postcss-import/pull/496 Haven't verified this but it seems to be the same issue and vite uses postcss-import. Currently (v3.0.3), both in a <style> tag or in a linked CSS file the import rule: @import url("https://unpkg.com/open-props/") layer(designsystem); results in @import url("https://unpkg.com/open-props/"); Basically importing without the layer. A fix was released in postcss-import as v15.0.0 https://github.com/postcss/postcss-import/blob/master/CHANGELOG.md#1500--2022-08-30 @sapphi-red Does this require an update in vite before end users can use this updated version? @romainmenke Thanks! Yes, this requires an update in Vite. @sapphi-red I don't know anything about Vite so maybe this doesn't make sense, but can end users easily pass plugin options to postcss-import or does Vite do all the configuration? @romainmenke Vite does all the configuration and currently it does not allow any configuration from users. Also Vite is shipped with postcss-import bundled in. So users cannot use the new version until a new release is cut. In that case it is important to set a new plugin option for anonymous cascade layers : nameLayer postcss-import needs to desugar anonymous layers to uniquely named layers but it doesn't have enough information about how it is used to generate these unique names. example from the tests : https://github.com/postcss/postcss-import/blob/master/test/layer.js#L67-L80 example from the postcss-preset-env site : const crypto = require('crypto'); const cwd = process.cwd(); module.exports = ctx => { const isProd = ctx.env === 'production'; return { map: !isProd, plugins: { 'postcss-import': { nameLayer: hashLayerName, }, 'postcss-preset-env': { stage: 0, preserve: true, features: { 'custom-properties': false, 'custom-media-queries': { preserve: false, }, }, }, 'cssnano': isProd ? { preset: 'default', } : false, }, }; }; function hashLayerName(index, rootFilename) { if (!rootFilename) { return `import-anon-layer-${index}`; } // A stable, deterministic and unique layer name: // - layer index // - relative rootFilename to current working directory return `import-anon-layer-${crypto .createHash('sha256') .update(`${index}-${rootFilename.split(cwd)[1]}`) .digest('hex') .slice(0, 12)}`; } @romainmenke I see. Thank you very much for the explanation! @argyleink v3.1.0 was released today. Would be awesome if you could try this version to verify that this is now fully fixed. bug is fixed 👍🏻
2025-04-01T04:35:53.394904
2023-09-28T20:43:46
1918245631
{ "authors": [ "Tobbe", "bluwy", "hyf0", "marbemac", "patak-dev", "sapphi-red" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11907", "repo": "vitejs/vite", "url": "https://github.com/vitejs/vite/pull/14498" }
gharchive/pull-request
feat(ssr): support for ssr.resolve.conditions and ssr.resolve.externalConditions options Description fixes #14496 Related PRs: #14417 #13487 Currently the vite dev server (and thus ssrLoadModule) do not respect resolve.conditions, and target node even when ssr.target is webworker. This PR introduces a new ssr.resolve option to configure how internal and external imports are resolved during SSR. I attempted to follow the recommended behavior described in the comments of #13487. I didn't update any documentation - can do that if there's a good chance this change will be accepted. What is the purpose of this pull request? [x] Bug fix [x] New Feature [ ] Documentation update [ ] Other Before submitting the PR, please make sure you do the following [x] Read the Contributing Guidelines. [x] Read the Pull Request Guidelines and follow the PR Title Convention. [x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate. [x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123). [x] Ideally, include relevant tests that fail without this PR but pass with it. @sapphi-red should I add some notes to docs/guide/ssr.md outlining the new ssr.resolve options, or are you/somebody else going to tackle the docs later? It would be nice if you add it. Also in /docs/config/ssr-options.md. But I can add it later too. @sapphi-red @bluwy alrighty, I took a crack at some docs. There were two styles of links in the docs (relative file path .md style links, and what look to be absolute URLs) - I chose relative file paths. Let me know if I missed anything! Just want to ask when will this feature be released? This seems to be a key blocker for framework related to react server component. We don't usually backport features to v4, so this will come in v5. I can cut another beta for it today, but for stable that will come sometime between mid-late October. Redwood (and I) would love it if you could make an exception and back-port this to v4 🙏 @Tobbe you don't need to be ESM-only to use Vite 5, unless you're using the ssr.format option? Using the CJS node API will still work albeit with the warning message that can be suppressed if really needed. @bluwy we use legacy.buildSsrCjsExternalHeuristics: true @Tobbe @nksaraf @hyf0, we discussed with @bluwy and backported this PR (together with a few other minor features) and released vite 4.5.0 with it.
2025-04-01T04:35:53.399533
2020-06-18T16:17:18
641353222
{ "authors": [ "ilan-gold", "mccalluc" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11908", "repo": "vitessce/vitessce", "url": "https://github.com/vitessce/vitessce/issues/594" }
gharchive/issue
"Error: Offsets not found but provided." on Portal v0.0.29 Describe the bug Just pushed v0.0.29 to Dev. This dataset shows vitessce, but when I click on "Add Image layer" and select a TIFF, nothing happens in the UI. In the console, there is a warning: "raster" (RASTER) from data:text/plain;charset=us-ascii;base64,......................… [ { "keyword": "additionalProperties", "dataPath": "", "schemaPath": "#/additionalProperties", "params": { "additionalProperty": "schema_version" }, "message": "should NOT have additional properties" } ] and an error: Error: Offsets not found but provided. Expected behavior Select a tiff an you get a pretty picture! (If this is really a portal or pipeline problem, please move this issue to the right repo.) I think it might be a pipeline issue - can you provide a UUID? I suspect this is one of the new CODEX runs which have the offsets in the right spot but lack a lot of other things. I don't have a good handle on what's been run where when, but it would make sense that the latest pipelines would be reflected on dev before test. I don't think there's anything else I can add. From slack: Looking at the code, this error message happens when there is any problem fetching the files. Could we add the http status code to the message, and possibly the whole URL? I think we’re assuming these are 404s, but it could be something else. (I’ll start a PR.) If it is a 404, and the files just aren’t in place, then that’s a problem with the pipeline… Can you follow up with the pipeline people for this particular dataset? And would it make any sense to have an assertion at the end of the pipeline run, since these files have been missing before?
2025-04-01T04:35:53.405668
2024-04-18T14:02:53
2250785258
{ "authors": [ "hi-ogawa", "oliverschwendener" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11909", "repo": "vitest-dev/vscode", "url": "https://github.com/vitest-dev/vscode/issues/360" }
gharchive/issue
Debugger stops at at end of file when "stepping into" Describe the bug I'm trying to debug tests in Visual Studio Code. I followed this guide: https://vitest.dev/guide/debugging.html to set up the vscode debugger and everything works fine, until I "step into" a function or method. The debugger does not stop on the correct line, but at the end of the file. I created a minimal repo to reproduce the issue: https://github.com/oliverschwendener/vitest-vscode-debugging-issue. Does anyone have an idea what could cause this issue? Did I misconfigure something? Reproduction https://github.com/oliverschwendener/vitest-vscode-debugging-issue Output [INFO 15:58:09] [v0.8.4] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace. [INFO 15:58:09] [API] Running Vitest: v1.5.0 (vite.config.mts) [INFO 15:58:09] [API] Starting Vitest process with Node.js: /Users/oliverschwendener/.nvm/versions/node/v20.12.2/bin/node [INFO 15:58:10] [API] Vitest process 94273 created [INFO 15:58:11] [API] Collecting tests: src/Calculator.test.ts [INFO 15:58:11] [API] Collecting tests: src/Calculator.test.ts [INFO 15:58:33] [DEBUG] Starting debugging on localhost:53856 [INFO 15:58:33] Running 1 file(s) with name pattern: ^\s?add should add two numbers$ [Worker] Debugger listening on ws://<IP_ADDRESS>:53856/691b403d-7e0e-4ddc-8605-5c4ff72dd9f6 For help, see: https://nodejs.org/en/docs/inspector [Worker] Debugger attached. [INFO 15:58:33] [DEBUG] Debugging started Version v0.8.4 Validations [X] Check that you are using the latest version of the extension [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate. [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server. [X] The provided reproduction is a minimal reproducible example of the bug. Thanks for the reproduction. It looks like this is due to how Vite SSR transforms imports/exports internally. Vite replaces each named export with a getter of magic variable __vite_ssr..., so probably this getter call is making an weird jump. I'm not sure if there's a solution to this, but probably this issue is reproducible on plain Vite SSR, so actions need to be take there. Btw, you are using vscode debugger directly with own launch.json, so technically this is not vscode extension issue, which is what this repo is about. But, the same issue can reproduce either way.
2025-04-01T04:35:53.407927
2022-08-14T23:42:37
1338380583
{ "authors": [ "kaorukobo", "sheremet-va" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11910", "repo": "vitest-dev/vscode", "url": "https://github.com/vitest-dev/vscode/pull/73" }
gharchive/pull-request
feat: add additionalDebugConfiguration configuration As per the modification to README.md: vitest.additionalDebugConfiguration: Properties overlayed onto the run configuration to launch the vitest for debugging. For example: {"trace": true} Please, create an enhancement issue first with the reasoning for this option. I've forgotten why I needed the run configuration overlay. would like to wait for someone who needs it, and hope they raise the enhancement issue.
2025-04-01T04:35:53.410572
2017-10-17T13:53:18
266133595
{ "authors": [ "aadrian", "balkarov", "gamedevsam", "maucrvlh", "ray007" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11911", "repo": "vitmalina/w2ui", "url": "https://github.com/vitmalina/w2ui/issues/1690" }
gharchive/issue
Tag and release 1.5-RC1? Please Tag 1.5-RC1 and release it at least to NPM, so that others can simply integrate/use it. It's been more than 2 years since the last tag/release :( . Thank you. Agree. If and when it's ready, but I agree we should start the process. Any reason to not publish this with an @next tag for npm?
2025-04-01T04:35:53.422348
2020-12-16T14:06:11
768910232
{ "authors": [ "RibinMTC", "lucaro", "silvanheller" ], "license": "mit", "license_source": "bigquery", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11912", "repo": "vitrivr/cineast", "url": "https://github.com/vitrivr/cineast/issues/169" }
gharchive/issue
Persisting a vector of strings Dear devs, For a given segment I produce a vector of strings. Does cineast support storing this vector to the cottontail db? If yes, could you point me to an example? I have seen that there is vector support for ReadableFloatVector, but could not find something similar for strings. Otherwise, should I have multiple database entries for each vector element? Best, Ribin Hey, string vectors are not supported. If you want to store multiple strings, you would need to explicitly create a 'column' for each. For something different: we recently enabled github discussions for all main repos of the vitrivr organization, they are a more suitable place for questions. I'll just briefly add: You can use Text Retrieval in Cottontail, check out for example how we search OCR. As @lucaro said though, feel free to start a discussion on the discussions page.
2025-04-01T04:35:53.447683
2024-12-28T05:40:19
2761494487
{ "authors": [ "makscee", "vladbat00" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11913", "repo": "vladbat00/bevy_egui", "url": "https://github.com/vladbat00/bevy_egui/issues/343" }
gharchive/issue
Clipboard get should not always log an error https://github.com/vladbat00/bevy_egui/blob/69034c683f2c5bf03dcbfc6f8d05fa0479973231/src/lib.rs#L279 I made a system for static caching clipboard contents, but if the clipboard is empty I get an error in my console every frame. There seems to be no way of simply getting the content if there is any, without extra logging. Hi! Just to clarify: are you calling the EguiClipboard resource directly - did I get this right? If so, I guess I can change EguiClipboard::get_contents interface to return an error so that users can handle it themselves. The error printing on pressing Ctrl+V if the clipboard is empty will probably remain though, but I can move it to a function within a separate module so that users can just silence that module without losing error logging of whole bevy_egui.
2025-04-01T04:35:53.511759
2024-10-03T19:36:11
2564864582
{ "authors": [ "JalonSolov", "jeffangelion", "medvednikov" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11914", "repo": "vlang/coreutils", "url": "https://github.com/vlang/coreutils/issues/174" }
gharchive/issue
Feature request: cp/mv: implement advcpmv patches While this doesn't making cp and mv 100% compatible with GNU variants, this progress bar functionality is very useful Source: https://github.com/jarun/advcpmv I agree I could see adding a -progress option, or some such. So by default they worked like the coreutils versions, but would have the option of showing progress. Of course, I don't know that they collect all the info required up front to actually display the progress properly... seem like that would slow things down a bit, at least in some cases.
2025-04-01T04:35:53.524335
2019-12-29T02:55:07
543308790
{ "authors": [ "shiipou", "ulises-jeremias" ], "license": "MIT", "license_source": "github-api", "license_type": "permissive", "provenance": "gharchive-dolma-0004.json.gz:11915", "repo": "vlang/vsl", "url": "https://github.com/vlang/vsl/issues/7" }
gharchive/issue
Add plot libray Decide if this is better to use matplotlib-cpp or python-matplotlib as in gosl The matplotlib-cpp use the python-matplotlib. I'm wrong ? The difference is that gosl's approach is to generate the python code necessary to plot things. It would be useful to evaluate other possibilities that are better than those and to evaluate what other tools exist to define this module. will close this issue until more important stuff is finished will close this issue until more important stuff is finished