id
stringlengths 4
10
| text
stringlengths 4
2.14M
| source
stringclasses 2
values | created
timestamp[s]date 2001-05-16 21:05:09
2025-01-01 03:38:30
| added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| metadata
dict |
|---|---|---|---|---|---|
284929227 | file.isSymbolic update vinyl package to v2.1.0
#192
Hi @evilebottnawi,
I have adjusted the package.json file to reference the new v2.1.0 of vinyl which fixes the issue of error file.isSymbolic within gulp after the release of alpha 3.
I ran the test which completes successfully. Although I discovered that the tests fail on the data returned from the request function of the helpers-es5.js file with the following message:
}) : callback(result.result.error_message);
^
TypeError: Cannot read property 'result' of undefined
at /Users/craigpryde/Documents/Websites/favicons/helpers-es5.js:476:46
at Object.handleResponse (/Users/craigpryde/Documents/Websites/favicons/node_modules/node-rest-client/lib/node-rest-client.js:448:5)
at Object.handleEnd (/Users/craigpryde/Documents/Websites/favicons/node_modules/node-rest-client/lib/node-rest-client.js:421:10)
at IncomingMessage.<anonymous> (/Users/craigpryde/Documents/Websites/favicons/node_modules/node-rest-client/lib/node-rest-client.js:587:13)
at emitNone (events.js:111:20)
at IncomingMessage.emit (events.js:208:7)
at endReadableNT (_stream_readable.js:1056:12)
at _combinedTickCallback (internal/process/next_tick.js:138:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
This was happening in the original master version that I cloned without making any updates. Unfortunately, i don't have the time to investigate the realfavicongenerator API to assist in debugging this other issue.
let me know your thoughts
Cheers
Craig
Thanks for the patch, it shipped in v5.0!
| gharchive/pull-request | 2017-12-28T14:48:39 | 2025-04-01T06:38:37.445223 | {
"authors": [
"brunocodutra",
"craigpryde"
],
"repo": "evilebottnawi/favicons",
"url": "https://github.com/evilebottnawi/favicons/pull/193",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
124640363 | File not found if default steam does not exist
I don't have any games install on the c drive eq. C:\Program Files (x86)\Steam\SteamApps\common does not exist and the script fails:
Checking C:\Program Files (x86)\Steam\SteamApps\common
Traceback (most recent call last):
File "", line 368, in
File "", line 139, in find_redist
FileNotFoundError: [WinError 3] The system cannot find the path specified: 'C:\Program Files(x86)\Steam\SteamApps\common'
steamclean returned -1
Can you check the file explorer for the path to ensure it is valid please? On my system I also did not install anything to C:\ as that is my SSD which I do not wish to clutter up.
C:\Program Files (x86)\Steam\steamapps\common>dir
Volume in drive C has no label.
Volume Serial Number is XXXX-XXXX
Directory of C:\Program Files (x86)\Steam\steamapps\common
08/22/2015 12:09 <DIR> .
08/22/2015 12:09 <DIR> ..
0 File(s) 0 bytes
2 Dir(s) 98,086,707,200 bytes free
I manually created the common directory in steamspps on c:\ and it worked
just fine
On Jan 3, 2016 08:19, "evitalis" notifications@github.com wrote:
Can you check the file explorer for the path to ensure it is valid please?
On my system I also did not install anything to C:\ as that is my SSD which
I do not wish to clutter up.
C:\Program Files (x86)\Steam\steamapps\common>dir
Volume in drive C has no label.
Volume Serial Number is XXXX-XXXX
Directory of C:\Program Files (x86)\Steam\steamapps\common
08/22/2015 12:09 .
08/22/2015 12:09 ..
0 File(s) 0 bytes
2 Dir(s) 98,086,707,200 bytes free
—
Reply to this email directly or view it on GitHub
https://github.com/evitalis/steamclean/issues/6#issuecomment-168501115.
I do not expect that it should have errored out though. I am going to set it as a bug for the moment and will review the code again. I might just be missing a check somewhere.
I added some extra tests for the missing or invalid directory in commit 14867e4117898. This should be resolved but will leave open until the next build is posted and tested.
v0.6.0 allows for less restrictions on directory names and additional logging was added which should resolve this. Merge commit cf1a0ba .
| gharchive/issue | 2016-01-03T09:52:51 | 2025-04-01T06:38:37.465869 | {
"authors": [
"caboose0013",
"evitalis"
],
"repo": "evitalis/steamclean",
"url": "https://github.com/evitalis/steamclean/issues/6",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
326342800 | Possible incompatibility with react-native-firebase v4
Issue: clicking on the notification banner while the app in foreground will not trigger FCM.on(FCMEvent.Notification, (notif) => {}).
I was able to reproduce the issue I was having on the sample project. All I had to do was install react-native-firebase (4.2.0) and the issue would start happening. When I revert react-native-firebase to version (3.3.1) the issue doesn't seem to happen. I'm wondering at this point if its better to completely migrate to using Messaging from react-native-firebase or if there was a workaround for this issue?
if you are using react-native-firebase, I would recommend migrating to them. I have created a migration example project https://github.com/evollu/react-native-fcm/tree/firebase/Examples/firebase-migration
| gharchive/issue | 2018-05-25T00:35:08 | 2025-04-01T06:38:37.468890 | {
"authors": [
"evollu",
"jnrepo"
],
"repo": "evollu/react-native-fcm",
"url": "https://github.com/evollu/react-native-fcm/issues/947",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1046085471 | Update cats-helper to 2.6.2
Updates com.evolutiongaming:cats-helper from 2.3.0 to 2.6.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!
Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.evolutiongaming", artifactId = "cats-helper" } ]
labels: library-update, early-semver-minor, semver-spec-minor
Superseded by #200.
| gharchive/pull-request | 2021-11-05T17:34:28 | 2025-04-01T06:38:37.475066 | {
"authors": [
"scala-steward"
],
"repo": "evolution-gaming/stracer",
"url": "https://github.com/evolution-gaming/stracer/pull/199",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
45458744 | Suggested to have splash screen for "confusing apps"
Some apps need a further info text in the form of a splash screen; e.g.
"this apps requires the TI Sensor tag"
"this is a companion app for the BLE On/Off example"
"this app needs an external gps"
et cetera when required. We don't want people to run an app,
nothing happens and in worst case they'd walk away
Suggestions proposed by Sionarch have been implemented in some of the examples, and should be done for the rest or the examples:
Descriptive title
Image of the device used by the example
When applicable update UI texts to mention the device used
| gharchive/issue | 2014-10-10T08:44:13 | 2025-04-01T06:38:37.481702 | {
"authors": [
"divineprog",
"mazekeeper"
],
"repo": "evothings/evothings-examples",
"url": "https://github.com/evothings/evothings-examples/issues/73",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
49950130 | Chef example (Chapter 3.3.2) doesn't work (Missing Role(s) in Run List)
solo.rb: root point to the correct directory
"sudo chef-solo -j node.json -c solo.rb" exits with the following error
[2014-11-24T23:13:44+01:00] ERROR: Role tomcatserver.json (included by 'top level') is in the runlist but does not exist. Skipping expand.
Error expanding the run_list:
Missing Role(s) in Run List:
tomcatserver.json included by 'top level'
Original Run List
role[tomcatserver.json]
[2014-11-24T23:13:44+01:00] FATAL: Stacktrace dumped to /home/testserver/user-registration/chef/chef-stacktrace.out
Chef Client failed. 0 resources updated in 6.273272457 seconds
[2014-11-24T23:13:44+01:00] ERROR: The expanded run list includes nonexistent roles: tomcatserver.json
[2014-11-24T23:13:44+01:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
In Version 2 you need to change root = '/home/ubuntu/user-registration-V2/chef' into all lower case '/home/ubuntu/user-registration-v2/chef' Otherwise you will receive the same error message.
@Electronic-Junkie This is actually expected. I clarified the documentation, see https://github.com/ewolff/user-registration-V2/tree/master/chef#chef-solo-on-ubuntu-1604 . Please open an issue in https://github.com/ewolff/user-registration-V2 if you feel this does not solve the problem.
| gharchive/issue | 2014-11-24T22:16:58 | 2025-04-01T06:38:37.502535 | {
"authors": [
"Electronic-Junkie",
"ewolff",
"jevin36"
],
"repo": "ewolff/user-registration",
"url": "https://github.com/ewolff/user-registration/issues/5",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
2492613555 | Address retry bug for HighThroughputExecutor.
This PR addresses a bug in the task retry logic causing it to fail for HighThroughputExecutor.
Updates
The main update was to resolve the result future prior to checking it's failure info.
The previous release only tested it for ThreadPoolExecutor, however the result lives in shared memory in that case so the failure info was present. Using HighThroughputExecutor the future result object needs to be used.
Address CI issues.
I'm taking a look at this soon. Fixing up some flake8 issues first
Thanks, @braceal !
| gharchive/pull-request | 2024-08-28T17:11:21 | 2025-04-01T06:38:37.507583 | {
"authors": [
"WardLT",
"braceal"
],
"repo": "exalearn/colmena",
"url": "https://github.com/exalearn/colmena/pull/142",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1486581313 | Update generators.md
The output of the generator example is the other way round.
Thanks for the PR -- I updated that example in https://github.com/exaloop/codon/pull/85/commits/91272b1580b0face2bd816ab76e55879e397367b. in this case I think it makes more sense to modify the gen function itself as the current version is a bit unintuitive, which is what's done in that commit.
Thank you for this very exciting project! I really hope, it takes off.
| gharchive/pull-request | 2022-12-09T11:21:20 | 2025-04-01T06:38:37.509724 | {
"authors": [
"apahl",
"arshajii"
],
"repo": "exaloop/codon",
"url": "https://github.com/exaloop/codon/pull/78",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
986108453 | 🛑 My Site is down
In 4cc3334, My Site ($SECRET_SITE) was down:
HTTP code: 0
Response time: 0 ms
Resolved: My Site is back up in d5a70ad.
| gharchive/issue | 2021-09-02T04:28:59 | 2025-04-01T06:38:37.520319 | {
"authors": [
"exand"
],
"repo": "exand/upptime",
"url": "https://github.com/exand/upptime/issues/822",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
436046776 | any changes in es index between 4.x and the .net core version?
i am using the .net framework verion which is 4.x
if i upgrade to the lastest .net core version.
do i need to do something in elasticsearch index ?
There should be no changes to the Elasticsearch indexes for 5.x, you'll just need to run the docker containers that are currently up with our ci label. We're finalizing the docs and then well be pushing the official feeds. Please let us know if you have any questions.
good job，that’s good news for everyone who want to upgrade to .net core version.
+1
The only changes needed are to host the site in docker and point elastic connection string to your existing elastic instance :). See this for more information: https://github.com/exceptionless/Exceptionless/wiki/Self-Hosting-Docker
| gharchive/issue | 2019-04-23T07:50:36 | 2025-04-01T06:38:37.544376 | {
"authors": [
"cuibty",
"niemyjski",
"witskeeper"
],
"repo": "exceptionless/Exceptionless",
"url": "https://github.com/exceptionless/Exceptionless/issues/415",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
520658133 | No weekend exchange rates?
Hi,
I'm not entirely sure if this is an issue or just me not understanding something. I can't seem to get any exchange rates for dates on weekends. For example, using the following URL for 2019-11-10, I am returned the results for 2019-11-08:
https://api.exchangeratesapi.io/2019-11-10?&base=EUR
{
"rates": {
"CAD": 1.4561,
"HKD": 8.6372,
"ISK": 137.7,
"PHP": 55.809,
"DKK": 7.4727,
"HUF": 333.37,
"CZK": 25.486,
"AUD": 1.6065,
"RON": 4.7638,
"SEK": 10.7025,
"IDR": 15463.05,
"INR": 78.652,
"BRL": 4.5583,
"RUB": 70.4653,
"HRK": 7.4345,
"JPY": 120.72,
"THB": 33.527,
"CHF": 1.0991,
"SGD": 1.5002,
"PLN": 4.261,
"BGN": 1.9558,
"TRY": 6.3513,
"CNY": 7.7115,
"NOK": 10.0893,
"NZD": 1.7426,
"ZAR": 16.3121,
"USD": 1.1034,
"MXN": 21.1383,
"ILS": 3.8533,
"GBP": 0.86158,
"KRW": 1276.66,
"MYR": 4.5609
},
"base": "EUR",
"date": "2019-11-08"
}
Thanks in advance :)
Hello - This API exposes the exchange rates from the European Central Bank. Those are reported only on workdays.
You can read more about it on https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html
| gharchive/issue | 2019-11-10T21:11:00 | 2025-04-01T06:38:37.547411 | {
"authors": [
"ash-jc-allen",
"madisvain"
],
"repo": "exchangeratesapi/exchangeratesapi",
"url": "https://github.com/exchangeratesapi/exchangeratesapi/issues/66",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1662028204 | Concept for Basics
Add a concept exercise for the Basic concept. It should cover:
Variable Declaration
Variable Initialization
Calling Functions
Comments
[x] Pick a fitting exercise
[x] Add code files
[x] Add documentation files
[ ] Update the list of implemented exercises
[x] Get feedback
[x] Implement Feedback
The exercise of choice shall be Lasagna. It is widely adopted and covers everything we need.
I still have to write about.md and think about how it should be different to the introduction.md.
One point is whitespace. I think it is important to know how it is handled in c++, but not necessary before the first concept.
One of the hardest things to grasp about (any) languages is its relation to its runtime. I.e. the machine. C++ (as with C) is an imperative language, it has statements that instructs the machine to do things. We're not talking of IO, but statements such as int i{1}; is an instruction. Not merely some idea of a name bound with a value. Most (if not all that I came across) language tutorials quickly skip this core fact, try to lay down fundamental constructs of the language and move on to a game of problem solving given those tools. This grows into a game of framework usage tweaking trying to achieve some application result. This is all high level and desired (most of the time) but that missing fundamental link makes all code magic. Say the write word, and it will (magically) happen.
| gharchive/issue | 2023-04-11T08:44:29 | 2025-04-01T06:38:37.590612 | {
"authors": [
"gomain",
"vaeng"
],
"repo": "exercism/cpp",
"url": "https://github.com/exercism/cpp/issues/589",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
796905425 | Add tags
This issue is part of the migration to v3. You can read full details about the various changes here.
In Exercism v3, tracks can be annotated with tags. This allows searching for tracks with a certain tag combination, making it easy for students to find an interesting track to join.
Tags are specified in the top-level "tags" field in the track's config.json file and are defined as an array of strings, as specified in the spec.
Goal
The "tags" field in the config.json file should be updated to contain the tags that are relevant to this track. The list of tags that can be used is listed in the spec.
Example
{
"tags": [
"runtime/jvm",
"platform/windows",
"platform/linux",
"paradigm/declarative",
"paradigm/functional",
"paradigm/object_oriented"
]
}
Tracking
https://github.com/exercism/v3-launch/issues/1
This seems to have been tackled in #47 .
| gharchive/issue | 2021-01-29T14:00:15 | 2025-04-01T06:38:37.610540 | {
"authors": [
"ErikSchierboom",
"Pamplemousse"
],
"repo": "exercism/nix",
"url": "https://github.com/exercism/nix/issues/10",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1194989687 | Update Instructions For "Twelve Days"
Overview
We should update the instructions of the "Twelve Days" to better explain what the exercise is asking the student to do. I listed specific things to focus on in the checklist below. I'll also be opening a PR with my suggestions for this change.
https://exercism.org/tracks/ruby/exercises/twelve-days
Details
My team uses this exercise as a code challenge for developer candidates from several different countries. I've learned a lot from watching people see this exercise for the first time. The current instructions of Output the lyrics to 'The Twelve Days of Christmas'. do not seem to be adequate. We can add some additional text to explain what is going on in this challenge, so non-native English speakers and non-Christians have an easier time understanding what to do.
One specific issue I have is that I think the spirit of the "Twelve Days" challenge implies that you should not just be reading and outputting the available text file (example of this), you should be writing an algorithm that programmatically generates the song. The text file should just be available for the test runner to compare to the output of TwelveDays.song. If we cannot prevent the student from just reading and returning the contents of the text file in their song method, then we should at least suggest in the instructions that they should be generating the song themselves and focusing on a few specific things when doing so, for learning purposes.
TODO
[ ] Update Instructions.md
[ ] To prompt the student with some more help to get started
[ ] Give some thought to the cultural unfamiliarity of this song - not everyone just "gets it" when seeing this for the first time - I run into this when using this exercise in interviews with non-western non-christian candidates who have never heard of it before
[ ] Write test to assert that the text file is not being read by the TwelveDays class
[ ] expect File not_to receive :read or something like that - not sure if this is possible. The test is a nice-to-have for me, I'm mostly interested in adding copy to the instructions that discourage the student from trying to just output the same exact file the test runner is using.
# Instructions
Your task in this exercise is to write a method that returns the lyrics of the song: 'The Twelve Days of Christmas'.
"The Twelve Days of Christmas" is a common Christmas carol. Each subsequent verse of the song builds on the previous verse.
Each verse of the song has several elements that are repeated from verse to verse. Identify these elements and try to re-use them when writing your code. Remember to be "DRY" (Don't Repeat Yourself)!
The lyrics your method returns should exactly match the text shown below.
# The Twelve Days Of Christmas
```text
On the first day of Christmas my true love gave to me: a Partridge in a Pear Tree.
On the second day of Christmas my true love gave to me: two Turtle Doves, and a Partridge in a Pear Tree.
On the third day of Christmas my true love gave to me: three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the fourth day of Christmas my true love gave to me: four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the fifth day of Christmas my true love gave to me: five Gold Rings, four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the sixth day of Christmas my true love gave to me: six Geese-a-Laying, five Gold Rings, four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the seventh day of Christmas my true love gave to me: seven Swans-a-Swimming, six Geese-a-Laying, five Gold Rings, four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the eighth day of Christmas my true love gave to me: eight Maids-a-Milking, seven Swans-a-Swimming, six Geese-a-Laying, five Gold Rings, four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the ninth day of Christmas my true love gave to me: nine Ladies Dancing, eight Maids-a-Milking, seven Swans-a-Swimming, six Geese-a-Laying, five Gold Rings, four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the tenth day of Christmas my true love gave to me: ten Lords-a-Leaping, nine Ladies Dancing, eight Maids-a-Milking, seven Swans-a-Swimming, six Geese-a-Laying, five Gold Rings, four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the eleventh day of Christmas my true love gave to me: eleven Pipers Piping, ten Lords-a-Leaping, nine Ladies Dancing, eight Maids-a-Milking, seven Swans-a-Swimming, six Geese-a-Laying, five Gold Rings, four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
On the twelfth day of Christmas my true love gave to me: twelve Drummers Drumming, eleven Pipers Piping, ten Lords-a-Leaping, nine Ladies Dancing, eight Maids-a-Milking, seven Swans-a-Swimming, six Geese-a-Laying, five Gold Rings, four Calling Birds, three French Hens, two Turtle Doves, and a Partridge in a Pear Tree.
One idea I had was to add an extra test case, ensuring that the solution does not call any of the typical Ruby methods that would read from a file
Because Twelve Days exercise is not only for Ruby, these suggestions should be discussed in the problem-specifications repository, and so I am going to transfer this to there.
| gharchive/issue | 2022-04-06T18:35:41 | 2025-04-01T06:38:37.634784 | {
"authors": [
"RTurek",
"kotp",
"simonbacquie"
],
"repo": "exercism/ruby",
"url": "https://github.com/exercism/ruby/issues/1311",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
286566540 | ERROR 502: Bad Gateway
Howdy folks!
I'm looking for some help with an issue that I currently have with Pathfinder.
Every time I try to log in with my account, I get the following error: http://prntscr.com/hx6n0c
If I just press "Restart", the page reloads, I log in again, and I get the very same error again, and again and again, no matter how many times I try this.
Is there any way to fix this issue?
Thank you!
@levialex , as @dkrotil already said. We can´t provide support for self hosted installations without having deeper knowledge about the setup/server.
If there is something buggy and reproducible on the public installation please let us know.
If you can get more information about the server setup regarding your issue please let us know.
| gharchive/issue | 2018-01-07T12:47:07 | 2025-04-01T06:38:37.670062 | {
"authors": [
"exodus4d",
"levialex"
],
"repo": "exodus4d/pathfinder",
"url": "https://github.com/exodus4d/pathfinder/issues/575",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1996738026 | Spacy-llm bedrock issue
I am getting the below error
[2023-11-16 17:39:57,111] ERROR in app: Exception on /watsonnlu [POST]
Traceback (most recent call last):
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/flask/app.py", line 2077, in wsgi_app
response = self.full_dispatch_request()
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/flask/app.py", line 1525, in full_dispatch_request
rv = self.handle_user_exception(e)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/flask/app.py", line 1523, in full_dispatch_request
rv = self.dispatch_request()
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/flask/app.py", line 1509, in dispatch_request
return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nlu_service.py", line 62, in message
resp = predict(data["input"], data["bot_id"])
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nlu/assistant_nlu.py", line 250, in predict
intent_result=predict_intent(bot_id,user_query,sql_connection,language,session,Is_FAQ_present)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nlu/predict_intent.py", line 498, in predict_intent
spacy_llm_output_list=predict_spacy_llm(user_query,file_name)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nlu/predict_intent.py", line 349, in predict_spacy_llm
Spacy_LLM_model = assemble(config_file_path)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/spacy_llm/util.py", line 48, in assemble
return assemble_from_config(config)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/spacy_llm/util.py", line 28, in assemble_from_config
nlp = load_model_from_config(config, auto_fill=True)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/spacy/util.py", line 587, in load_model_from_config
nlp = lang_cls.from_config(
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/spacy/language.py", line 1847, in from_config
nlp.add_pipe(
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/spacy/language.py", line 814, in add_pipe
pipe_component = self.create_pipe(
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/spacy/language.py", line 702, in create_pipe
resolved = registry.resolve(cfg, validate=validate)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/confection/__init__.py", line 756, in resolve
resolved, _ = cls._make(
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/confection/__init__.py", line 805, in _make
filled, _, resolved = cls._fill(
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/confection/__init__.py", line 860, in _fill
filled[key], validation[v_key], final[key] = cls._fill(
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/confection/__init__.py", line 877, in _fill
getter_result = getter(*args, **kwargs)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/spacy_llm/models/langchain/model.py", line 90, in langchain_model
return LangChain(
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/spacy_llm/models/langchain/model.py", line 34, in __init__
self._langchain_model = LangChain.get_type_to_cls_dict()[api](
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/langchain/load/serializable.py", line 97, in __init__
super().__init__(**kwargs)
File "/Users/Naveen/04102023/assistant_nlu_service_proprietary/nav-spacy-test/lib/python3.9/site-packages/pydantic/v1/main.py", line 341, in __init__
raise validation_error
pydantic.v1.error_wrappers.ValidationError: 1 validation error for Bedrock
model_name
extra fields not permitted (type=value_error.extra)
where my config file is as follows,
[nlp]
lang = "en"
pipeline = ["llm"]
batch_size = 128
[components]
[components.llm]
factory = "llm"
[components.llm.model]
@llm_models = "langchain.Bedrock.v1"
name = "amazon.titan-text-express-v1"
config = {"model_id": "amazon.titan-text-express-v1"}
[components.llm.task]
@llm_tasks = "spacy.TextCat.v2"
labels = What_can_you_do, Unlock_Account, More_questions
exclusive_classes = false
[components.llm.task.examples]
@misc = "spacy.FewShotReader.v1"
path = "models/nav_testing_3fed4208-dad-4635-8419-b4kumar002_selective_examples.jsonl"
[components.llm.task.normalizer]
@misc = "spacy.LowercaseNormalizer.v1"
Hi @NaveenKumarStark, please always format your code and console output. Thanks for bringing this up, langchain seems to expect different keyword args for Bedrock than for other models. We'll patch this up shortly.
| gharchive/issue | 2023-11-16T12:21:05 | 2025-04-01T06:38:37.704448 | {
"authors": [
"NaveenKumarStark",
"rmitsch"
],
"repo": "explosion/spacy-llm",
"url": "https://github.com/explosion/spacy-llm/issues/372",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1361749227 | [eas-cli] bump oclif help plugin
Checklist
[X] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.
Why
Refs ENG-6204
How
This PR bumps our fork of the oclif help plugin, which includes corrected description for the help command in the help prompt
Test Plan
The change has been tested locally by running yarn eas.
Preview
/changelog-entry bug-fix Fix description of help command in help prompt.
| gharchive/pull-request | 2022-09-05T10:48:29 | 2025-04-01T06:38:37.710390 | {
"authors": [
"Simek"
],
"repo": "expo/eas-cli",
"url": "https://github.com/expo/eas-cli/pull/1341",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1525314811 | [eas-cli] validate chosen build in eas build:run command
Checklist
[ ] I've added an entry to CHANGELOG.md if necessary. You can comment this pull request with /changelog-entry [breaking-change|new-feature|bug-fix|chore] [message] and CHANGELOG.md will be updated automatically.
Why
When adding a paginated select prompt to the eas build:run I introduced a new bug.
When you have no emulator/simulator builds in your project you will get this strange assertion error message.
EDIT: I noticed that I wasn't sanitizing builds selected by id or as latest. This is also fixed now.
Now I sanitize every selected build to make sure it is valid in the context of the eas build:run command.
How
Throw a custom error if there are no simulator/emulator builds for a given platform.
Test Plan
Manual tests.
/changelog-entry bug-fix Validate chosen build in the eas build:run command
| gharchive/pull-request | 2023-01-09T10:32:45 | 2025-04-01T06:38:37.714588 | {
"authors": [
"szdziedzic"
],
"repo": "expo/eas-cli",
"url": "https://github.com/expo/eas-cli/pull/1614",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1329120244 | [question] Is this project being maintained?
Hi! I'm currently working on a new Expo project and would like to be able to deploy to desktop via Electron at some point.
I've found this project, but it looks like there's not been anyone maintaining it since its creation (15 months ago).
Are there any plans by Expo to improve support for Electron in the future?
We are moving towards a unified bundling process with Metro, but likewise, we also want to use a unified native runtime as well. Mac Catalyst enables React iOS to run natively on macOS machines, and React Native Windows supports the same on windows. We don't have the bandwidth to support any more platforms outside of iOS, Android, and web right now but if we did, it would be proper native.
This package is a light wrapper around electron-webpack if anyone wants to go more upstream.
Fair enough! I do agree it would be awesome to support desktop native platforms. However, I feel like the problem with that (and I noticed the same in frameworks like Flutter) is that most native packages you'll use in your app won't support desktop platforms, so even if Expo and RN supported those fully, it could still be a problem.
I see Electron as a "quick" win in wrapping the web app into a desktop app, and packages for Node are much easier to find.
So, at least for our first release, we'd like to try and get a quick win here by using electron to build the desktop version of our apps, and later on maybe consider switching to native.
| gharchive/issue | 2022-08-04T20:02:53 | 2025-04-01T06:38:37.735436 | {
"authors": [
"EvanBacon",
"matallui"
],
"repo": "expo/expo-electron-adapter",
"url": "https://github.com/expo/expo-electron-adapter/issues/19",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1073034423 | ThemeProvider is not working for external packages.
Summary
I created a component library on top of styled-components.
Library: https://github.com/sangameshsomawar/test
Npm: https://www.npmjs.com/package/@sangameshsomawar/test
When I install the library in any new react-native project or expo project, the theme is getting passed correctly to the external package, and colors are properly rendered. But when I test the same code in snack, the theme is not working. This issue is only happening in the snack.
Please find below snack examples:
Output when Typography Component is written directly in snack
Output when Typography code is fetched from the library and then referred in snack
Snack Link:https://snack.expo.dev/@sangamesh.somawar/typography
Snack Link: https://snack.expo.dev/@sangamesh.somawar/typography2
I think context is not getting passed correctly in the snack.
What platform(s) does this occur on?
Android, iOS, Web
SDK Version
No response
Reproducible demo or steps to reproduce from a blank project
see above
@IjzerenHein Please Help.
Hi @sangameshsomawar, your library is a full bare react native app. It contains another react native instance which is causing issues here. If you want to add this lib to your project in Snack, you have to create a package with just the JS files you want, not the whole app. (e.g. only the files in lib)
Hope this helps.
@byCedric: I have tried that as well. Let me create a snack example with that approach. I will share it with you here.
| gharchive/issue | 2021-12-07T08:00:41 | 2025-04-01T06:38:37.837677 | {
"authors": [
"byCedric",
"sangameshsomawar"
],
"repo": "expo/snack",
"url": "https://github.com/expo/snack/issues/238",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2621379945 | refactor: upgrade to Expo SDK 52
Why
This is a maintenance release, to upgrade to SDK 52. Note, this PR does not turn SDK 52 into the default SDK yet. We still need more testing for that.
[!IMPORTANT]
This PR should be merged after upgrading to the first stable SDK 52 version.
How
See commits, followed the upgrade guide.
Test Plan
See staging.
Going to merge this, and open a PR to upgrade the snack-runtime package separately.
| gharchive/pull-request | 2024-10-29T14:08:15 | 2025-04-01T06:38:37.840125 | {
"authors": [
"byCedric"
],
"repo": "expo/snack",
"url": "https://github.com/expo/snack/pull/614",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
113823833 | add images as base64 encoded data
make the navigator more resilient to network outages
Thanks!
| gharchive/pull-request | 2015-10-28T13:44:27 | 2025-04-01T06:38:37.850567 | {
"authors": [
"despairblue",
"ide"
],
"repo": "exponentjs/ex-navigator",
"url": "https://github.com/exponentjs/ex-navigator/pull/14",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
330931804 | chrome lighthouse text compression
i have searched the closed issues and found some others that have the same problem. but no solution
i enabled compression with
app.use(compression({ threshold: 0 }));
chrome networktab says: no compression, no content-encoding.
HTTP/1.1 200 OK
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Sun, 10 Jun 2018 00:30:44 GMT
ETag: W/"1a526-163e71a33c0"
Content-Type: text/css; charset=UTF-8
Vary: Accept-Encoding
Date: Sun, 10 Jun 2018 01:14:59 GMT
Connection: keep-alive
Transfer-Encoding: chunked
chrome lighthouse extension says: Enable Text Compression!
firefox networktab: no content-encoding on the response
i turned debugging on set DEBUG=compression
i see on every request:
compression gzip compression +1m
GET /dist/bundles/medicalpad/index.css 200 1.590 ms - -
if i used curl -i --compressed http://localhost:3000/dist/bundles/medicalpad/index.css
i see
TP/1.1 200 OK
X-Powered-By: Express
Accept-Ranges: bytes
Cache-Control: public, max-age=0
Last-Modified: Sun, 10 Jun 2018 00:30:44 GMT
ETag: W/"1a526-163e71a33c0"
Content-Type: text/css; charset=UTF-8
Vary: Accept-Encoding
Content-Encoding: gzip <<<-------
Date: Sun, 10 Jun 2018 01:13:40 GMT
Connection: keep-alive
Transfer-Encoding: chunked
so i dont know whats going on there.
i am using:
express 4.16.0
compression: 1.7.2
node: 8.11.2
i have made a demo https://github.com/pYr0x/express-gzip
even on that simple example, chrome and other browers dont show the Content-Encoding.
if i visit other global website e.g. https://www.nytimes.com/ i see a content-encoding: gzip so a bug in chrome can be excluded.
the only difference on the respone headers i found is that:
content-length is missing
and there is a Transfer-Encoding: chunked header.
can Transfer-Encoding: chunked be the reason why the Content-Encoding is not shown or ignored by chrome?
@dougwilson is the demo shown you the Content-Encoding? i am on windows 10 with chrome 67.0.3396.79
Thanks for providing a repo! I an getting Content-Encoding: gzip in the Chrome Console just as I would expect from your project:
you are on windows right?
what node and npm version do you have installed?
Yes, I am on Windows 10. I used Node.js 8.11.2 (installed fresh just for this) so we would be using the exact same Node.js to try and keep every as similar as possible from what you said so far.
So I have no glue what’s going on... :(
Same. Variations of this issue have been report many times but either it suddenly started working and the reported doesn't know why or I had to close due to no further progress. If I could reproduce it I could try to track it down, otherwise since you can reproduce it we're all awaiting to hear what the issue is that you're having and where the bug is located.
ok one last try:
can you disable all chrome extensions and try it with a clean chrome browser?
can you tell me the file size that chrome gets with gizp? i will compare that with the filesize i will get.
Hi @pYr0x sorry I didn't get back to you earlier. I just tried out your additional suggestions and everything is still working fine for me.
I did the following:
Installed a brand new Windows 10 on an old machine.
Installed a new copy of Google Chrome
Installed a fresh copy of Node.js
Ran the code I posted above and opened Chrome
This means that nothing I had on my machine before was preset. There were no extensions in Chrome now, as it's a fresh install on a fresh Windows 10 install.
The file size that Chrome is showing with gzip is 87.9 kb.
Closing stale issue.
| gharchive/issue | 2018-06-10T01:21:41 | 2025-04-01T06:38:37.862095 | {
"authors": [
"dougwilson",
"pYr0x"
],
"repo": "expressjs/compression",
"url": "https://github.com/expressjs/compression/issues/142",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
38590049 | promises
now that promises are going mainstream, i'm trying to think of how to make express more async friendly. an idea is to use promises.
next() now returns a promise
if middleware returns a promise, that promise is resolved and propagated up next()s
app.use(function (req, res, next) {
// a promise must be returned,
// otherwise the function will be assumed to be synchronous
return User.get(req.session.userid).then(function (user) {
req.user = user
})
.then(next) // execute all downstream middleware
.then(function () {
// send a response after all downstream middleware have executed
// this is equivalent to koa's "upstream"
res.send(user)
})
})
Error handlers are now more koa-like:
app.use(function (req, res, next) {
return next().catch(function (err) {
// a custom error handler
if (res.headerSent) return
res.statusCode = err.status || 500
res.send(err.message)
})
})
app.use(function (req, res) {
throw new Error('hahahah')
})
Pros:
it should be backwards compatible since you don't have to resolve the promise returned from next()
much easier error handling including throwing
solves issues shown in https://github.com/visionmedia/express/issues/2255
no more fn.length checking ~_~
could probably easily upgrade to es7 async functions
Cons:
promises
upgrading middleware and supporting both signatures might be a pain in the ass
probably a lot slower
Looks promising! (sorry)
Just as a data point, here is a framework that uses a WSGI-like setup. Basically, you make a chain of middlewares that optionally modify the request before passing it down the chain and then optionally modify the response before passing it up the chain.
The response is a simple object with the headers and an iterable body, and once the entire chain ran it is sent to the user. You can't have "headers already sent" errors, and error handling is a lot cleaner.
The interesting bit is that middleware can return promises for the header or body parts, and they are sent as soon as they resolve. This makes for very simple code.
I wonder if Express can be made to do the same while retaining the res API for middleware.
Why not giving users the ability to set our own trigger handler?
Something like this would be easy to implement, and wouldn't hit the performance (and could have other interesting usages, such as intercepting the routing and monitoring action perfs):
app.wrap(function (action, req, res, next) {
var res = action(req, res, next);
if (res && res.then) {
res.then(function () {
next();
}, function () {
res.status(500);
});
}
})
It would be a simple feature which would allow us to start using promise, until you decide if/how you want to support promises in the Express core. Would you consider a PR?
This issue is pretty old. Promise support will be coming in Express 5.
Really? It has not been listed on the related issue. Are they already supported, or just planned?
@arcanis sorry, I didn't add it. Promise support should be listed in the 5.0 issue now.
@arcanis I must admit I don't understand how your code works (what does app.wrap do?)
I use promises with Express by wrapping handlers (easy in coffeescript):
Q = require 'q'
class HTTPError extends Error
name: "HTTPError"
constructor: (status, message) ->
if +status >= 100
@status = status
else
@status = 500
if status
message = status
@message = message
class NotFoundHTTPError extends HTTPError
name: "NotFoundHTTPError"
constructor: (message) -> super 404, message
httpErrorHandler = (err, req, res, next) ->
if err instanceof HTTPError
res.send err.status, err.message
else
next err
promiseJson = (fn) ->
(req, res) -> res.json Q.fcall fn, req
app.use (require 'express-promise')()
app.use httpErrorHandler
app.get '/foo/', promiseJson (req) ->
if idontwanttoanswer
throw new NotFoundHTTPError "these are not the droids you're looking for"
# some code that returns a value or a promise
...
@wmertens It's only a proposal. It would define how should the middlewares be called by the router. The default one would just pass the parameters to the actual middleware functions, but a more sophisticated one could just as well expect the middleware to return a promise, and 'convert' that promise to a callback.
But it's not so important if core promise support are on their way. Just something that I think could be interesting.
In case anybody ends up on this thread looking to use promises in Express right now, I've written an article here on exactly that, using express-promise-router.
Might be a useful stop-gap solution for some people, even if it doesn't completely implement them as described here :)
+1
i.m.o we can't really have it until joyent/node#7714 is fixed (or at least, promised to be fixed).
Why not Bluebird?
https://www.npmjs.com/package/native-or-bluebird
Any update on this?
And btw since no one mentioned it, the .catch() error handler style could be achieved with next() callback style too in theory, by allowing to pass a callback to next().
I've been trying to get this merged into pillarjs/router (see
Any updates on this? Would be nice if middleware could return a promise as an alternative to calling next()/next(err).
Can I take care of it if nobody is working on it?
There are a few PRs both here and in https://github.com/pillarjs/router . I plan to merge in basic support to 5.0 over the weekend, likely https://github.com/pillarjs/router/pull/32 without the upstream support (for now), since upstream has a lot more kinks to work out.
In the mean time, for express 4, we have monkey patched Layer to wrap handlers with code that does exactly what we want:
https://gist.github.com/q42jaap/f2fb93d96fda6384d3e3fc51977dec90
We have been using https://www.npmjs.com/package/async-middleware for quite a while now, it just wraps middlewares explicitely without any monkey patching
Hoping to add something like this into kraken-js https://github.com/krakenjs/kraken-js/issues/495
Any word on this? There's a ton of middlewares and such, but this would be nice to get in mainline express.
https://github.com/pillarjs/router/pull/60
It is lined up for the 2.x version of router, which will land in express 5.
Any updates on when promise support will land in Express 5?
The basic support is merged to the router 2.x branch. https://github.com/pillarjs/router/pull/60
There is one other open PR over there, but nce the beta for that is released I think we can release another prerelease version of express 5. I am not sure if @dougwilson has a concrete timeline on that.
I'm going to close this issue now that Express.js 5.0.0-alpha.7 has been published which includes the initial support for Promises in the router. Middleware and handlers can now return promises and if the promise is rejected, next(err) will be called with err being the value of the rejection. The implementation is seeking feedback from real usage, and please open any feedback as a new issue, either in this issue tracker or in the router issue tracker.
I am currently working on writing up Express.js-specific documentation on this feature, but in the meantime, the documentation can be found in the router repository:
https://github.com/pillarjs/router/tree/v2.0.0-alpha.1#middleware
The function can optionally return a Promise object. If a Promise object is returned from the function, the router will attach an onRejected callback using .then. If the promise is rejected, next will be called with the rejected value, or an error if the value is falsy.
Is there a single example of a route using Promises? I've read the router changelogs etc, from alpha 2 to alpha 7, but I can't find anything.
I know, eg, https://arc.codes uses
exports.handler = async function http(request) {
return {
status: 201,
type: 'text/html; charset=utf8',
body: `
<!doctype html>
<html>
<body>hello world</body>
</html>
`
}
}
Does express 5 allow me to return a response from a route?
Asked a question about generally getting rid of callbacks here (so we can just return a response) but deleted it - filed it as a new issue #3884 instead.
| gharchive/issue | 2014-07-24T01:27:09 | 2025-04-01T06:38:37.887167 | {
"authors": [
"ChiperSoft",
"JessieAMorris",
"affanshahid",
"ahmetatar",
"arcanis",
"calebmer",
"dougwilson",
"felixfbecker",
"gtomitsuka",
"joepie91",
"jonathanong",
"listepo",
"mikemaccana",
"olalonde",
"q42jaap",
"wesleytodd",
"wmertens",
"xjamundx"
],
"repo": "expressjs/express",
"url": "https://github.com/expressjs/express/issues/2259",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
2203905446 | Regression bug when exception is thrown
There seems to be a regression around the core engine handling exceptions. Given this test program:
function greet() {
throw new Error('hello')
}
module.exports = { greet }
Output is:
2024/03/23 09:33:11 No runtime detected
2024/03/23 09:33:11 Calling function : greet
Error: wasm error: unreachable
wasm stack trace:
.$1151(i32,i32,i32,i32,i32,i32)
.$1290(i32,i32)
.$1309(i32,i32,i32,i32,i32)
.$1357(i32) i32
.$1374() i32
We should see the exception
Should be fixed in #57
| gharchive/issue | 2024-03-23T14:35:35 | 2025-04-01T06:38:37.914786 | {
"authors": [
"bhelx"
],
"repo": "extism/js-pdk",
"url": "https://github.com/extism/js-pdk/issues/58",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
196061485 | [NERDTree] "Press ? for help" appear in the wrong buffer
Hi! First, let me thank you a lot for your awesome GUI, even if it is still in development/beta, it looks really cool (I tried first Nyaovim, and was a bit disappointed x) ).
Now, when I open neovim, I have automatically NERDTree opened, but there is a little graphic issue when using Oni:
When I write on the buffer, it replaces these letters, so it really looks like a graphical issue as it is not in the buffer. I have updated to the latest npm package for oni, and for neovim and NERDTree too
(By the way, I am on Linux Mint 18)
Here is my .vimrc if you need https://github.com/Ilphrin/.vim/blob/master/vimrc
Hi @Ilphrin ! Thanks for the kind words!
Yes, this definitely looks like a rendering bug. I believe I hit this on Windows too on startup - it seems like the beginning of the first line is always problematic. It might be we're missing or not handling one of the neovim msgpack-RPC actions correctly.
You're welcome! When i'll have time, i'll try to give some help on Oni, this really deserves more hands =D
BTW, when i run Ctrl+L it is refreshing the page and the glitch doesn't appear anymore, as my NERDTree is has a plugin to be launched in every tab and on startup, maybe it is because the browsers draws too soon the content? (Just suppositions, I don't know a thing about what's is happening!)
Awesome, would be great to have the help! :)
I just checked out this issue... It looks like it was a bug that was caused by a couple of contributing factors:
On startup, we would tell Neovim that we had a fixed size screen (80 cols x 40 rows), and then we would always resize to the proper size based on the font afterwards
During resize, Neovim sends a CLEAR action via the msgpack-rpc API. For that action, the cursor position wasn't being reset - so after clearing, it would just start rendering the first line whereever the cursor had been previously. So that was the root problem, and easy to fix.
Should be addressed now by PR #115
| gharchive/issue | 2016-12-16T13:40:14 | 2025-04-01T06:38:37.921226 | {
"authors": [
"Ilphrin",
"extr0py"
],
"repo": "extr0py/oni",
"url": "https://github.com/extr0py/oni/issues/106",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
899012983 | 🛑 XYZ is down
In 7f9854c, XYZ (https://davidblue.xyz) was down:
HTTP code: 0
Response time: 0 ms
Resolved: XYZ is back up in acf45f3.
| gharchive/issue | 2021-05-23T12:48:11 | 2025-04-01T06:38:37.923768 | {
"authors": [
"extratone"
],
"repo": "extratone/up",
"url": "https://github.com/extratone/up/issues/161",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
574057117 | 填入自定义规则后应用闪退
你正在使用哪个版本？
1.8.0
使用最新版本是否还遇到同样的问题？
是
你的手机型号和手机操作系统版本是多少？
一加7p h2os10
你遇到了什么问题？
填入自定义规则https://github.com/Loyalsoldier/v2ray-rules-dat/raw/release/geosite.dat
后应用频繁闪退，无法连接，点规则集闪退
你遇到的问题可以用固定步骤重现吗？
你正使用的配置
<!-- 请把你的配置文件复制至此 (建议把服务器和用户信息去掉) -->
你可以点击上面你提交的链接，就会发现啥都没有
你可以点击上面你提交的链接，就会发现啥都没有
有内容啊 怎么会啥都没有
| gharchive/issue | 2020-03-02T15:36:10 | 2025-04-01T06:38:37.926740 | {
"authors": [
"Chocolateyk",
"hunao0221"
],
"repo": "eycorsican/kitsunebi-android",
"url": "https://github.com/eycorsican/kitsunebi-android/issues/146",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
196095399 | Call to undefined function SEOstats\Config\env()
I get this error when trying to access the GooglePageSpeesAnalysis
$dotenv = new Dotenv\Dotenv('path to your .env'); $dotenv->load(); function env($config, $default) { $config_value = getenv($config); if(is_string($config_value) && (strlen(trim($config_value)) > 0)) { return $config_value; } else { return $default; } }
All you need to write this code where you are calling the Google Page Speed Analysis
Fix in https://github.com/eyecatchup/SEOstats/pull/150
Same issue here.
Same issue with examples : get-mozscape-metrics.php or get-google-pagespeed-analysis.php
| gharchive/issue | 2016-12-16T16:16:19 | 2025-04-01T06:38:37.929342 | {
"authors": [
"barryvdh",
"besens",
"fbarrento",
"fnagel",
"merajsiddiqui"
],
"repo": "eyecatchup/SEOstats",
"url": "https://github.com/eyecatchup/SEOstats/issues/146",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
592327708 | 不支持taro next
问题描述
不支持taro next
复现步骤
[复现问题的步骤]
期望行为
运行正常
报错信息
系统信息
Taro CLI 3.0.0-beta.1 environment info:
System:
OS: macOS 10.15.2
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.14.1 - /usr/local/bin/node
Yarn: 1.21.1 - /usr/local/bin/yarn
npm: 6.13.4 - /usr/local/bin/npm
npmPackages:
@tarojs/components: 3.0.0-beta.2 => 3.0.0-beta.2
@tarojs/taro: 3.0.0-beta.2 => 3.0.0-beta.2
@tarojs/webpack-runner: 3.0.0-beta.2 => 3.0.0-beta.2
eslint-config-taro: 3.0.0-beta.2 => 3.0.0-beta.2
react: ^16.10.0 => 16.13.0
npmGlobalPackages:
typescript: 3.7.5
补充信息
Chart/index.js 因为react的引用问题已经改了
import React, {Component} from 'react';
import Taro from '@tarojs/taro'
上面的报错是改了之后的报出的
我升级了taro next也的确是同样的报错 2.x是正常
@BinZhiZhu
推荐使用 https://github.com/elvinzhu/techarts ，直接用taro写的，没有引用原生组件那些麻烦事
@BinZhiZhu
推荐使用 https://github.com/elvinzhu/techarts ，直接用taro写的，没有引用原生组件那些麻烦事
可以 我真准备不直接依赖taro 谢谢老哥
| gharchive/issue | 2020-04-02T03:14:02 | 2025-04-01T06:38:37.935869 | {
"authors": [
"BinZhiZhu",
"yz1311"
],
"repo": "eyelly-wu/taro-echarts",
"url": "https://github.com/eyelly-wu/taro-echarts/issues/8",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
181422749 | Set milestones and goals
ping @lucasmezencio and @pedrochaves
Which type of milestones/goals do you think we can have?
I think this issue must be discussed internally.
| gharchive/issue | 2016-10-06T13:59:31 | 2025-04-01T06:38:37.954717 | {
"authors": [
"lucasmezencio",
"pedrommone"
],
"repo": "ezdeliveryco/snorlax",
"url": "https://github.com/ezdeliveryco/snorlax/issues/44",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
141254054 | [dcc32 Fatal Error] F2084 Internal Error: DBG3198
Hi, I tried build SpringAndMVC and I have this error final.Why?:)
Ales
You have installed and configured the latest versions of DMVC and Spring4D (release 1.2)?
Has this link Embarcadero that can help you: http://docwiki.embarcadero.com/RADStudio/Seattle/en/F2084_Internal_Error_-%25s%25d(Delphi)
Yes I have,I have the same problem in other project with TSession,
I have same problem with today Spring release/1.2 without DMVC.In Debug mode I get this error,in Release mode compiled ok.Delphi XE6
This is an error in the compiler (reported as https://quality.embarcadero.com/browse/RSP-14974)
The circumstances to cause this are listed in my comment on that issue.
If you follow my recommendation to build Spring4D and then only point to the dcu directory instead of adding the source directories to the library or search path it will not appear as far as I know.
However I removed the inline from the TCollections.Create* methods as they did not have much of a beneficial effect anyway so this error should be gone once you update to the latest commit in release/1.2
Thank you for response Stefan. Very enlightening.
| gharchive/issue | 2016-03-16T12:08:08 | 2025-04-01T06:38:37.960203 | {
"authors": [
"egroups",
"ezequieljuliano",
"sglienke",
"talpa"
],
"repo": "ezequieljuliano/DelphiLaboratory",
"url": "https://github.com/ezequieljuliano/DelphiLaboratory/issues/1",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
709564859 | Initial Pi VideoCore and DMA support
DMA is just memory to memory transfers for now
VideoCore mailbox is functional
Very cool! Here's the output of the functions for boards I have lying around. It seems this "interrogation" can indeed be used to detect the available RAM like suggested in https://github.com/f-secure-foundry/tamago/pull/13#issuecomment-699247428.
However, other values, such a BoardModel/MACAddress/Serial/CPUAvailableDMAChannels look fishy.
Raspberry Pi 1 A
FirmwareRevision: 8 (dec)
BoardModel: 0
MACAddress: 0xb827ebc95629
Serial: 0
CPUMemory: 0x0, 0xc000000
GPUMemory: 0xc000000, 0x4000000
CPUAvailableDMAChannels: 0x7f35
Raspberry Pi 1 B
FirmwareRevision: 13 (dec)
BoardModel: 0
MACAddress: 0xb827ebf4f296
Serial: 0
CPUMemory: 0x0, 0x1c000000
GPUMemory: 0x1c000000, 0x4000000
CPUAvailableDMAChannels: 0x7f35
Raspberry Pi 1 B+
FirmwareRevision: 0x10
BoardModel: 0
MACAddress: 0xb827eb32d0cc
Serial: 0
CPUMemory: 0x0, 0x1c000000
GPUMemory: 0x1c000000, 0x4000000
CPUAvailableDMAChannels: 0x7f35
Heya, any thoughts on my change request?
Hey - the comments look good. Got distracted with another project. I'll work on making the changes.
I've pushed a change that I think addresses the review comments.
| gharchive/pull-request | 2020-09-26T16:11:36 | 2025-04-01T06:38:38.050906 | {
"authors": [
"abarisani",
"kenbell",
"prusnak"
],
"repo": "f-secure-foundry/tamago",
"url": "https://github.com/f-secure-foundry/tamago/pull/14",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
1568453735 | unhandled exception: Login failed エラーが出てしまいます
（以下、「DMMGamePlayerFastLauncher」を「FastLauncher」と略させて頂きます）
Windowsを10から11にし、FastLauncherをまた使用しようとして
DMMGamePlayer5がインストールして正常に動作する状態でFastLauncherを
以前と同じ様にインストールしました。
しかし、どうやってもFastLauncherがログイン出来ないという様なエラーになり、
どのゲームをFastLauncherから実行してもログイン出来ないとエラーが出て、
0byteのcookie.bytesが作成されます。
正常にログイン出来ていた頃はサイズが13Kbyteほどありました。
DMMGamePlayer.exeは「C:\Program Files\DMMGamePlayer」、
データ類は「C:\Users\（ユーザー名）\AppData\Roaming\dmmgameplayer5」にインストールされていて、
ゲームデータ類は他のドライブにインストールしています。
バージョンは5.1.39です。
DMMGamePlayerFastLauncher.exeの場所は
「C:\Users\（ユーザー名）\AppData\Roaming\DMMGamePlayerFastLauncher」にインストールされています。
バージョンは4.6.0で、正常に起動出来ていた頃に使用していたものは1つ前の4.5.2ですが、
そのバージョンに戻してみてもダメでした。
DMMGamePlayerでログイン出来るのに何故FastLauncherでログイン出来ないのかまったく分かりません…。
よろしくお願いします。
DMMGamePlayer5、ログアウトしてログインしなおしたらデバイス認証が出て1/5になりました。
しかし、やはりFastLauncherは同じエラーが出てしまいます。
DMMGamePlayerでログイン出来るのにFastLauncherでログイン出来ないのかまったく分かりません…。
DMMGamePlayer ver.5.1.39 でこの不具合が発生するようです
ふぁ様
お返事ありがとうございます。
DMMGamePlayerがバージョンアップしたからなのですね…。
（余計な所ばかり改悪して、使いやすい様には改良しないんですねDMMの開発）
修正版作成、よろしくお願いします。
いつも使わせて頂いて感謝しております。
| gharchive/issue | 2023-02-02T17:16:59 | 2025-04-01T06:38:38.069218 | {
"authors": [
"fa0311",
"negimiku"
],
"repo": "fa0311/DMMGamePlayerFastLauncher",
"url": "https://github.com/fa0311/DMMGamePlayerFastLauncher/issues/52",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
262687787 | Work item types vanish from work-item-quick-add list
To reproduce click on the empty space (next to labels) of any work item.
Good one @jarifibrahim
Tracking via https://openshift.io/openshiftio/openshiftio/plan/detail/1549
| gharchive/issue | 2017-10-04T07:10:39 | 2025-04-01T06:38:38.097636 | {
"authors": [
"jarifibrahim",
"rgarg1"
],
"repo": "fabric8-ui/fabric8-planner",
"url": "https://github.com/fabric8-ui/fabric8-planner/issues/2207",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
130650798 | Force fileMode for executable script
Fixes fabric8io/fabric8#5686
[merge]
| gharchive/pull-request | 2016-02-02T11:12:31 | 2025-04-01T06:38:38.107084 | {
"authors": [
"jimmidyson"
],
"repo": "fabric8io/fabric8-devops",
"url": "https://github.com/fabric8io/fabric8-devops/pull/270",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
258219436 | S2I not yet supported for the webapp-generator - for artefacts created from swagger-codegen
I decided to use swagger-codegen on a swagger.json I created
java -jar modules/swagger-codegen-cli/target/swagger-codegen-cli.jar generate -DdebugModels=true -i audit/swagger.json -l jaxrs -o samples/server/ob/jaxrs-spec
then used mvn io.fabric8:fabric8-maven-plugin:3.5.28:setup
then fabric8:run gave me the error:
[ERROR] Failed to execute goal io.fabric8:fabric8-maven-plugin:3.5.28:build (fmp) on project swagger-jaxrs-server: Execution fmp of goal io.fabric8:fabric8-maven-plugin:3.5.28:build failed: S2I not yet supported for the webapp-generator. Use -Dfabric8.mode=kubernetes or -Dfabric8.buildStrategy=docker for OpenShift mode. Please refer to the reference manual at https://maven.fabric8.io for details about build modes. -> [Help 1]
I seem to remember hitting this problem a few years ago and got around it by hacking on the pom file but it would nice not to have to
Possibly related PR: https://github.com/fabric8io/fabric8-maven-plugin/pull/1060
@stevef1uk does it work with mvn fabric8:run -Dfabric8.mode=kubernetes?
| gharchive/issue | 2017-09-16T09:01:36 | 2025-04-01T06:38:38.110882 | {
"authors": [
"jsight",
"nicolaferraro",
"stevef1uk"
],
"repo": "fabric8io/fabric8-maven-plugin",
"url": "https://github.com/fabric8io/fabric8-maven-plugin/issues/1053",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
219903438 | fix(iteration): show date picker in create interation modal (fix #1341)
Previously we didn't allow the user to choose iteration date interval while creating the new iteration. Now this PR will allow the user to select the iteration date interval while creating the new iteration.
The date pickers should be empty on new iterations, not filled with a default date. Is that the case with this change? If no, can you add that? Thanks!
@michaelkleinhenz No, now date picker filled with a current date. and yes, I am adding that.
Current date/default does not show up when creating a new iteration:
| gharchive/pull-request | 2017-04-06T13:43:57 | 2025-04-01T06:38:38.113115 | {
"authors": [
"michaelkleinhenz",
"nimishamukherjee",
"vikram-raj"
],
"repo": "fabric8io/fabric8-planner",
"url": "https://github.com/fabric8io/fabric8-planner/pull/1534",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
54302048 | add ppath command
Print application's 'Documents' directory path.
@dopcn What do you think about having option flags to allow the desired directory to be opened in Terminal, or maybe Finder as well? For example ppath -t to open in Terminal. These don't need to be added to this pull request, but they'd be nice to add sooner or later.
@dopcn What do you think of the comments I made?
@kastiglione sorry, back and working on it now...
Update copy to the pasteboard before print
Thanks @dopcn, I'm happy to accept this. Before that, can you merge from master because there are now conflicts.
Thanks @dopcn!
| gharchive/pull-request | 2015-01-14T09:44:17 | 2025-04-01T06:38:38.181685 | {
"authors": [
"dopcn",
"kastiglione"
],
"repo": "facebook/chisel",
"url": "https://github.com/facebook/chisel/pull/72",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1257896587 | Can't run project
I can't run the server in this project. Please help me. This error bellow. Thank you so much
express-session deprecated req.secret; provide secret option index.js:64:9
/home/lap12703/Code/kahoot-clone/node_modules/passport-auth0/lib/index.js:36
throw new Error('You must provide the ' + k + ' configuration value to use passport-auth0.');
^
Error: You must provide the domain configuration value to use passport-auth0.
This is not an issue with create-react-app, you're probably running an express server and forgot to pass the express-session middleware a secret option. Refer to the express-session package documentation.
| gharchive/issue | 2022-06-02T08:56:37 | 2025-04-01T06:38:38.189494 | {
"authors": [
"josecarneiro",
"todinhvin"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/12459",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
325574607 | Service Controller not rendering
Is this a bug report?
Yes
Did you try recovering your dependencies?
Yes, no issue with dependency.
Package.json
{
"name": "public",
"version": "0.1.0",
"private": true,
"homepage": "./",
"dependencies": {
"bootstrap": "^3.3.7",
"lodash": "^4.17.5",
"prop-types": "^15.6.1",
"react": "^16.3.2",
"react-dom": "^16.3.2",
"react-render-html": "^0.6.0",
"react-router-dom": "^4.2.2",
"react-scripts": "1.1.4",
"reactstrap": "^5.0.0-beta.3"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "jest",
"eject": "react-scripts eject"
},
"devDependencies": {
"babel-jest": "^22.4.3",
"babel-preset-env": "^1.6.1",
"babel-preset-react": "^6.24.1",
"jest": "^22.4.3",
"react-test-renderer": "^16.3.2"
}
}
12:22:10 › npm --version
5.6.0
Environment
Development
Steps to Reproduce
You launch react application
Let's say react is running on localhost:3000
Setup a proxy server which takes the request on localhost:4000.
All the request coming from localhost:4000/xyzabc should redirect to localhost:3000
Expected Behavior
Whatever coming on localhost:3000 should come on localhost:4000/xyzabc
Actual Behavior
JS CSS everything is getting downloaded but nothing is showing on UI. UI is totally blank
Reproducible Demo
(Paste the link to an example project and exact instructions to reproduce the issue.)
Closing as a duplicate of #4468, this is a known issue. Sorry!
It should be fixed in v2.
| gharchive/issue | 2018-05-23T07:06:31 | 2025-04-01T06:38:38.198851 | {
"authors": [
"Timer",
"vishu9219"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/4506",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
486763991 | Failed to compile after configuring rules
{
"extends": "react-app",
"rules": {
"no-unused-expressions": "off"
}
}
Failed to compile.
./src/components/Tree/index.js
Line 24: Expected an assignment or function call and instead saw an expression no-unused-expressions
Search for the keywords to learn more about each error.
Can you post your index.js file?
@bullettrang
class TreeItem extends PureComponent {
render() {
const { item, selected, isFirst, isLast, folded, onFold, onClickItem } = this.props;
const { children, text } = item;
let fragment;
// 节点块样式
let itemCls = isFirst
? isFirst === isLast
? 'l-onlychild'
: 'l-first'
: isLast
? 'l-last'
: '';
if (children) { // 文件夹
const lastIndex = children && (children.length - 1);
// 节点样式
let expandCls = '';
let folderCls = '';
// eslint-disable-next-line no-unused-expressions
folded
? (expandCls = 'l-expandable-close', folderCls = 'l-tree-icon-folder')
: (expandCls = 'l-expandable-open', folderCls = 'l-tree-icon-folder-open');
const isLastFolder = isLast;
where is the return statement for your render()?
https://stackoverflow.com/questions/53996916/unable-to-turn-off-eslint-no-unused-expressions
Did you already take a look at above link?
Also what happens if you put 'folded' on the same line with the ternary expression like below?
// eslint-disable-next-line no-unused-expressions folded ? (expandCls = 'l-expandable-close', folderCls = 'l-tree-icon-folder') : (expandCls = 'l-expandable-open', folderCls = 'l-tree-icon-folder-open'); const isLastFolder = isLast;
Seems like putting certain statements on a separate line throws the 'Expected an assignment or function call and instead saw an expression no-unused-expressions' as explained by the link below with the return statement.
https://stackoverflow.com/questions/53013437/expected-assignment-or-function-call-no-unused-expressions-reactjs
@bullettrang The issue means I disabled this eslint rule, but it was compiled failed.
| gharchive/issue | 2019-08-29T06:31:01 | 2025-04-01T06:38:38.203924 | {
"authors": [
"bullettrang",
"fengxinming"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/7606",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
408491235 | [docs] revert removal of newlines from html
An unintended change was merged in #6062
I'm not seeing the changed files here on GitHub. Can you clarify what snuck through?
@ianschmitz it seems to be something that husky is doing automatically, and unfortunately I'm unable to override it. The form tag is being converted to one line:
https://github.com/facebook/create-react-app/pull/6062/files#diff-167d7aa95e8f35443e07dd102611e442L48
Ah yes you mean prettier. I wasn't aware they format code blocks inside of markdown files: https://twitter.com/bohdan_kh/status/1012367393656483841.
You should be able to get prettier to ignore that code block and restore the formatting to how it was previously: https://prettier.io/docs/en/ignore.html#range-ignore
Do you mind using the range ignore instead to just cover the code block?
@ianschmitz, should be ready now (FYI). Cheers.
Hmm, i'm not sure why but something looks off in the docs in this PR:
https://deploy-preview-6386--create-react-app.netlify.com/create-react-app/docs/adding-custom-environment-variables
You'll see the section that was edited here looks broken compared to master:
https://facebook.github.io/create-react-app/docs/adding-custom-environment-variables
I was able to fix the new issue with the code displaying properly by adding space above and below the code block, but prettier is not being ignored. I think it may make sense to just leave this as is and close the PR, thoughts?
| gharchive/pull-request | 2019-02-10T01:52:48 | 2025-04-01T06:38:38.208938 | {
"authors": [
"JBallin",
"ianschmitz"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/pull/6386",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
618717299 | ZEIT Now → Vercel
ZEIT has rebranded to Vercel.
This PR updates the deployment section to reflect the new name.
#9099 is a more comprehensive version of this
| gharchive/pull-request | 2020-05-15T05:53:26 | 2025-04-01T06:38:38.210261 | {
"authors": [
"eddiemonge",
"sarupbanskota"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/pull/9013",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1986134557 | Navigate to page sections using # doesn't work
Have you read the Contributing Guidelines on issues?
[X] I have read the Contributing Guidelines on issues.
Prerequisites
[X] I'm using the latest version of Docusaurus.
[X] I have tried the npm run clear or yarn clear command.
[X] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[X] I have read the console error message carefully (if applicable).
Description
when you paste the url including the section, the browser doesn't navigate to the section mentioned after # in th URL
https://dev2-everoed.evero.com/docs/-screen-descriptions/billing/billing_billing_claimbatchpending#raise-issue-button
You can notice the scroll doesn't move down to the bottom of the page.
Reproducible demo
No response
Steps to reproduce
Open https://dev2-everoed.evero.com/docs/-screen-descriptions/billing/billing_billing_claimbatchpending
Click Videos on the right side
Copy the URL
https://dev2-everoed.evero.com/docs/-screen-descriptions/billing/billing_billing_claimbatchpending#raise-issue-button
Paste in new tab (Doesn't scroll to videos) as original page does
Expected behavior
scroll down to the section mentioned from the URL # value
Actual behavior
The scroll doesn't move down to the section
Your environment
Public source code: NA
Public site URL: https://dev2-everoed.evero.com/
Docusaurus version used: 3.0.0
Environment name and version (e.g. Chrome 89, Node.js 16.4): Chrome Version 118.0.5993.89
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Windows
We have created Test user account for you
Username: etester
Password: DocusaurusTest123!
Self-service
[ ] I'd be willing to fix this bug myself.
This is not a Docusaurus bug, but a bad config of your host.
Your host should serve the appropriate static html file built by Docusaurus, but does not currently and always serve first the html of your homepage. It's only React that finally fixes the UI by rendering the correct page client-side.
This can easily be seen because your homepage "flashes" when you load any page.
This is what I see if I disable JS for example.
If your host is configured properly then you should see the good page content even with JS disabled.
If you don't know how to host a static deployment, then use Vercel, Netlify or another CDN that does it correctly for you out of the box. We can't help you configuring appropriately your custom setup.
we have built custom compoenent to serve dynamic content.
This is our docusourus config file., package if you have can spot an issue please let me know.
The project was setup many years ago and I don't know what's the correct setup for it.
docusaurus.config.js
const path = require("path");
const isDevelopment = process.env.NODE_ENV == "development";
module.exports = {
onBrokenLinks: "ignore",
title: "Our Digital Learning Repository",
tagline:
"eVero Ed is home to eVero-made resources and provides quick access to guidance documents, videos and recordings, a listing of scheduled webinars, and detailed release notifications.",
url: "https://evero.com",
baseUrl: "/",
baseUrlIssueBanner: false,
favicon: "img/Ed_MorePolished2.svg",
organizationName: "evero",
projectName: "ed",
customFields: {
isDev: isDevelopment,
devServer: "https://localhost:44312",
},
scripts: [
{
src: "/external/accessibe.js",
async: true,
},
{
src: "https://static.evero.com/evero-shared-all.js",
async: true,
},
],
themeConfig: {
navbar: {
title: "eVero Ed",
logo: {
alt: "eVero Ed Logo",
src: "img/FlatEd.png",
},
items: [
{
type: "doc",
label: "Guidance",
position: "left",
className: "spacing-nav-item",
docId: "home",
},
{
type: "docSidebar",
position: "left",
label: "Screen Descriptions",
sidebarId: "barScreenDescriptions",
className: "spacing-nav-item",
}
,
{
to: "videos-v2",
label: "Videos",
position: "left",
className: "spacing-nav-item",
},
{
to: "webinars",
label: "Webinars",
position: "left",
className: "spacing-nav-item",
},
{
type: "doc",
label: "Release Notifications",
position: "left",
className: "spacing-nav-item",
sidebarId: "barNotifications",
docId: "releases",
},
{
to: "contact-us",
label: "Contact Us",
position: "left",
className: "spacing-nav-item",
},
].filter((x) => !!x),
},
footer: {
style: "dark",
links: [
],
copyright: `Copyright © ${new Date().getFullYear()} eVero Corporation`,
},
},
presets: [
[
"@docusaurus/preset-classic",
{
docs: {
sidebarPath: require.resolve("./sidebars.js"),
// editUrl: "https://github.com/facebook/docusaurus/edit/master/website/"
},
blog: {
showReadingTime: true,
// editUrl: "https://github.com/facebook/docusaurus/edit/master/website/blog/",
},
theme: {
customCss: require.resolve("./src/css/custom.css"),
},
},
],
],
plugins: [
require.resolve("docusaurus-lunr-search"),
path.resolve(__dirname, "./plugins/event-plugin"),
// '@docusaurus/plugin-google-gtag'
],
};
package.json
{
"name": "evero-da-documentation",
"version": "0.0.0",
"private": true,
"scripts": {
"start": "docusaurus start",
"build": "docusaurus build",
"swizzle": "docusaurus swizzle",
"deploy": "docusaurus deploy",
"prodtest":"rm -r build & npm run build & cd build & npx http-server & explorer http://192.168.222.52:8081/"
},
"dependencies": {
"@docusaurus/core": "2.4.1",
"@docusaurus/plugin-content-pages": "2.4.1",
"@docusaurus/plugin-google-gtag": "2.4.1",
"@docusaurus/preset-classic": "2.4.1",
"@fortawesome/fontawesome-svg-core": "^1.2.36",
"@fortawesome/free-solid-svg-icons": "^5.15.4",
"@fortawesome/react-fontawesome": "^0.1.15",
"@mdx-js/react": "^1.6.21",
"autocomplete.js": "^0.38.0",
"clsx": "^1.1.1",
"docusaurus-lunr-search": "^2.1.14",
"lodash.debounce": "^4.0.8",
"moment": "^2.29.1",
"react": "^16.8.4",
"react-big-calendar": "^0.33.5",
"react-debounce-input": "^3.2.4",
"react-dom": "^16.8.4",
"react-router-dom": "^5.2.0",
"use-debounce": "^7.0.0"
},
"browserslist": {
"production": [
">0.2%",
"not dead",
"not op_mini all"
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version"
]
}
}
The bug is likely not in your docusaurus project, but in your hosting config. We can't help fixing it.
If you run docusaurus serve it should work fine.
| gharchive/issue | 2023-11-09T17:55:31 | 2025-04-01T06:38:38.224427 | {
"authors": [
"mohamedsaleh1984",
"slorber"
],
"repo": "facebook/docusaurus",
"url": "https://github.com/facebook/docusaurus/issues/9524",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
413788567 | Using SSR with Next.js: TypeError: undefined is not an object (evaluating 'editorState.getBlockTree(anchorBlockKey).getIn')
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
When using server side rendering, Rich Text example ( https://github.com/facebook/draft-js/tree/master/examples/draft-0-10-0/rich ) throws this error when pressing enter and at other times.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem. You can use this jsfiddle to get started: https://jsfiddle.net/stopachka/m6z0xn4r/.
Use Next.js to setup SSR.
Create a component called RichText from example here ( https://github.com/facebook/draft-js/tree/master/examples/draft-0-10-0/rich )
When page refreshes from server using next.js development server, start typing in the rich text editor and hit enter.
You'll see these errors appear multiple times.
What is the expected behavior?
Not to have errors in the browser console.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
Draft.js version: 0.10.28
Browser: Chrome 71 & Safari 12.0.3
OS: Mac OS: 10.14.3
Not sure if this worked in previous version of Draft.js
This is a problem with server-side rendering. Not sure about the reason, but you can work around this by rendering the editor only on client side.
import dynamic from 'next/dynamic';
const NoSSREditor = dynamic(() => import('../components/Editor'), { ssr: false });
render() {
return <NoSSREditor .... />
}
Works for me.
Thanks @svitekpavel! Working for me as well.
Hi @svitekpavel
I've tried your solution but unfortunately, I have an infinite loop when I'm starting my server. My memory is getting consumed very fast, and I cannot render a single page, until the server crashes.
Windows 10 x64 - 16 GB of RAM
Node.JS 12.8.0
Next.JS 9.0.3
Draft 0.11.0
Hi @svitekpavel
I've tried your solution but unfortunately, I have an infinite loop when I'm starting my server. My memory is getting consumed very fast, and I cannot render a single page, until the server crashes.
The rendering should not be called on server, so my best guess is that something else is wrong. Try to revert changes and get the server running normally. Then again try to change it.
| gharchive/issue | 2019-02-24T06:42:00 | 2025-04-01T06:38:38.233052 | {
"authors": [
"BrodaNoel",
"CommerceOwl",
"MBach",
"svitekpavel"
],
"repo": "facebook/draft-js",
"url": "https://github.com/facebook/draft-js/issues/2013",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
405416703 | Support for arrays in disjoint unions refinements
Flow version: v0.91.0
Expected behavior
With the following code, I would expect flow to understand how control flow interacts with the union type, and refine the associated function type to be compatible with the function invocations. That is, I would expect this code to not error.
type Args =
[false, () => void] |
[true, (number) => number];
function applyTheThing(...args: Args): number | void {
const [acceptsMore, fn] = args;
if (acceptsMore) return fn(100);
fn();
}
Actual behavior
The above code snippet produces (see flow.org/try) the following error:
9: if (acceptsMore) return fn(100);
^ Cannot call `fn` because no arguments are expected by function type [1].
References:
4: [false, () => void] |
^ [1]
10: fn();
^ Cannot call `fn` because function [1] requires another argument.
References:
5: [true, (number) => number];
^ [1]
The same applies if the array entries are dereference directly instead of first re-bound to local bindings (see flow.org/try).
@skeggse Correct. It errors to show you that flow isn’t smart enough to know it shouldn’t error. I realize it may seem unusual for this behavior to be expected but Flow tends to error when it can’t be sure something is safe.
Yeah that makes perfect sense - I wasn't sure how that example was intended to differ from the example I gave, as it was producing the same error.
This is one of the more frustrating parts of Flow that I've encountered. I would personally expect Flow to be able to refine the type of this:
const x: Array<string> | Array<Array<string>> = ['a'];
Similarly, I can understand why Flow isn't able to refine x to a specific type in the following example, but it's unclear to me why an error would be surfaced prior to me trying to do something with x that isn't valid for all possible types in the union.
const x: Array<string> | Array<Array<string>> = [];
Try Flow
| gharchive/issue | 2019-01-31T20:07:27 | 2025-04-01T06:38:38.244343 | {
"authors": [
"jimmydief",
"skeggse",
"vicapow"
],
"repo": "facebook/flow",
"url": "https://github.com/facebook/flow/issues/7422",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
226109448 | Test if object, array or string.
Is there a way to check if a component is an object, array or string? This would be similar to chai's 'should.be.a' Ex.: validationResult.SSN[0].should.be.a('string').
No, there isn't. You'll find the list of all available matchers here: https://facebook.github.io/jest/docs/en/expect.html
You can also use plain JavaScript or helper library like lodash for that:
test('name', () => {
// array
expect(Array.isArray(['value'])).toBe(true);
// string
expect(typeof 'value').toBe('string');
// object
expect({value: 'value'}).toBeTruthy();
expect(typeof {value: 'value'}).toBe('object');
})
Minor point - this doesn't help with promise results.
expect(somePromise).resolves.toBe(...) at this point there is no way to check type. If you don't care what the contents are but just that it is a string. I hoped expects.stringContaining("") to be a work around but that doesn't work either.
@abritinthebay I am in exact that situation and this is the first result in Google, maybe this should be reopened?
Certainly it should be thought about a bit more. My workaround was to add to the chain so that does the typeof part. eg:
expect(somePromise.then(data => typeof data)).resolves.toBe("object");
it works, but it's not exactly clean.
@thymikee Checking types of things is a common enough use case (universal) that there isn't really any excuse for a testing framework that lacks them. Your alternatives are unacceptable as we lose all context of what we are testing.
This expect(Array.isArray(['value'])).toBe(false); fails with
expect(received).toBe(expected)
Expected value to be (using ===):
false
Received:
true.
So we either get terrible assertion messages or we have to extend Jest to support these sorts of checks. Doesn't it make more sense for the maintainers of Jest to do this once as opposed to every person that uses requires these features implementing them on their own?
Create your own matchers with expect.extend then and publish as an npm module. If it gets popular, we may merge it to Jest core eventually ;)
A simple toBeType extension for those who want it
expect.extend({
toBeType(received, argument) {
const initialType = typeof received;
const type = initialType === "object" ? Array.isArray(received) ? "array" : initialType : initialType;
return type === argument ? {
message: () => `expected ${received} to be type ${argument}`,
pass: true
} : {
message: () => `expected ${received} to be type ${argument}`,
pass: false
};
}
});
describe("testing extended expect", () => {
it("tests normal types correctly", () => {
expect("").toBeType("string");
expect({}).toBeType("object");
expect(1).toBeType("number");
});
it("tests array types correctly", () => {
expect([]).toBeType("array");
});
it("works with promises", () => {
expect(Promise.resolve([])).resolves.toBeType("array");
});
});
Pretty simple to implement. Really should be in core tbh.
Thanks @abritinthebay
So I wrapped that up in an npm module if people want it:
https://www.npmjs.com/package/jest-tobetype
describe("assertion framework", ()=> {
it("should check primitive types", () => {
expect(expect.toBeA).toBeA("function")
})
})
Failed: expect(...).toBeA is not a function
TypeError: expect(...).toBeA is not a function
I've been using toBeInstanceOf in my tests:
expect($wrapper.vm.countries).toBeInstanceOf(Array);
Create your own matchers with expect.extend then and publish as an npm module. If it gets popular, we may merge it to Jest core eventually ;)
Yeah, and might write your own jest framework, while you're at it.
This one just might top the worst answers you can get on GitHub.
So @abritinthebay did exactly what was requested by @thymikee (which was far more than the standard pull request).
Now that that brave soul did all the work, when can the rest of us finally get this matcher (without having to install yet another library)? Are the maintainers still pushing the idea that this doesn't belong in Jest, or did this just fall off their radar?
We are pretty strict with what makes it into core and don't typically add sugar matchers. Jest core is a fairly large architecture and every matcher we add increases the maintenance cost
For sugar, we generally recommend https://github.com/jest-community/jest-extended
One man's sugar is another man's (or in this case, at least seven other people's) really useful and logical feature that belongs in the core library.
Obviously as a maintainer your vote trumps all of ours, and you have all sorts of concerns we don't so I fully respect that. But I'd simply ask that you look at why everyone here considers this feature to belong in the core library (so strongly that one person jumped through multiple hoops to write the code for you). There's a need here, and if you ignore it Jest core library users (and let's be honest, 90% of them will never even hear about jest-extended) will lose out.
As abritinthebay suggested, it's not really about sugar, it's about "necessary" and "unnecessary" (for the core library) sugar. You've got a bunch of people in this thread saying "hey, being able to check all types is something that should be in the core of a testing library".
Listen to us or don't, again as maintainer you have lots of other concerns. But I don't think the right response is to come say "your's is just inherently unnecessary sugar" when it's not inherent: it's 100% your call whether Jest can check all types or not.
I think this is the way to go :)
describe('type check', () => {
test('should be type string', () => {
expect(typeof '').toBe('string')
})
test('should be type number', () => {
expect(typeof 10).toBe('number')
})
test('should be type boolean', () => {
expect(typeof true).toBe('boolean')
})
test('should be type undefined', () => {
expect(typeof undefined).toBe('undefined')
})
test('should be type object', () => {
expect(typeof { foo: 'bar' }).toBe('object')
})
test('should be type function', () => {
expect(typeof function() {}).toBe('function')
})
test('should be type null', () => {
expect(typeof null).toBe('object')
})
})
I refactored the implementation provided by @abritinthebay. It seems for me a little bit comfortable to work with.
`expect.extend({
toBeType(received, arg) {
const initialType = typeof received;
const type = initialType === 'object'
? Array.isArray(received)
? 'array'
: initialType
: initialType;
return {
pass: type === arg,
message: () => `Expected '${received}' to be type '${arg}'`
};
}
});`
You should check out my module (linked above). It does a bit more than that. But if that works for you: use it!
I think this is the way to go :)
describe('type check', () => {
test('should be type string', () => {
expect(typeof '').toBe('string')
})
test('should be type number', () => {
expect(typeof 10).toBe('number')
})
test('should be type boolean', () => {
expect(typeof true).toBe('boolean')
})
test('should be type undefined', () => {
expect(typeof undefined).toBe('undefined')
})
test('should be type object', () => {
expect(typeof { foo: 'bar' }).toBe('object')
})
test('should be type function', () => {
expect(typeof function() {}).toBe('function')
})
test('should be type null', () => {
expect(typeof null).toBe('object')
})
})
It's works like a charm as well as more readable and maintainable for the future.
I think this is the way to go :)
describe('type check', () => {
test('should be type string', () => {
expect(typeof '').toBe('string')
})
test('should be type number', () => {
expect(typeof 10).toBe('number')
})
test('should be type boolean', () => {
expect(typeof true).toBe('boolean')
})
test('should be type undefined', () => {
expect(typeof undefined).toBe('undefined')
})
test('should be type object', () => {
expect(typeof { foo: 'bar' }).toBe('object')
})
test('should be type function', () => {
expect(typeof function() {}).toBe('function')
})
test('should be type null', () => {
expect(typeof null).toBe('object')
})
})
test('should be type object', () => {
expect(typeof { foo: 'bar' }).toBe('object')
// passes
expect(typeof ['foo', 'bar']).toBe('object')
// passes
expect(typeof null).toBe('object')
})
😞
This is why I suggest my addon above: takes care of this.
InstanceOf is slightly better but prone to similar issues.
thanks for solution @abritinthebay
Another solution:
expect('example').toEqual(expect.any(String));
expect(123).toEqual(expect.any(String));
The second one would fail with:
Expected: Any<String>
Received: 123
It's extremely weird that Jest doesn't provide so basic functionality out of the box. It's a nonsense that you need to install a third-party library just to check the type of a variable in a clear and semantic manner.
| gharchive/issue | 2017-05-03T20:45:49 | 2025-04-01T06:38:38.413188 | {
"authors": [
"Billy-",
"Temirtator",
"abramz",
"abritinthebay",
"ahtashamabbasse",
"alex-dixon",
"amiteshore",
"balovbohdan",
"ecoker",
"franciscop",
"machineghost",
"nithrm",
"rickhanlonii",
"slavafomin",
"tfoxy",
"thymikee",
"vitaly-t"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/issues/3457",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
288607879 | feat(jest-cli): return results object from jest.run
Summary
This makes it easier to run Jest directly, like when wrapping it in a custom script.
Test plan
Tests passes as before.
The major disadvantage is that runCLI does not process the command line arguments and the functions that do that are not exported. I'd like to use run but unfortunately there is no way to find out if it was successful or not, unless I missed something.
| gharchive/pull-request | 2018-01-15T14:15:07 | 2025-04-01T06:38:38.415667 | {
"authors": [
"dlmr",
"manu-st"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/pull/5316",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
393966665 | Remove duplicate 'the'.
Summary
before:
the the
after:
the
Codecov Report
Merging #7546 into master will not change coverage.
The diff coverage is n/a.
@@ Coverage Diff @@
## master #7546 +/- ##
=======================================
Coverage 67.91% 67.91%
=======================================
Files 248 248
Lines 9507 9507
Branches 6 6
=======================================
Hits 6457 6457
Misses 3048 3048
Partials 2 2
Impacted Files
Coverage Δ
packages/expect/src/matchers.js
99.39% <ø> (ø)
:arrow_up:
packages/jest-snapshot/src/index.js
52.63% <ø> (ø)
:arrow_up:
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 bfdd4e1...0d92c27. Read the comment docs.
| gharchive/pull-request | 2018-12-25T05:50:48 | 2025-04-01T06:38:38.423854 | {
"authors": [
"H1Gdev",
"codecov-io"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/pull/7546",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2727550083 | Bug: RTE components when resizing or scroll doesn't seem to be contained or collapsed
RTE components when resizing or scroll doesn't seem to be contained or collapsed.
Lexical version: 0.18.0
Steps To Reproduce
Go to the lexical playground and add lengthy texts to make it scrollable and table
Click on table dropdown and scroll the editor.
Now you'll see that dropdown is not being contained and not getting attached with table dropdown.
https://github.com/user-attachments/assets/cd24854e-8966-4cde-bc9f-abe4a399309d
Link to code example: https://playground.lexical.dev/
The current behavior
Components are not getting contained.
The expected behavior
Make it contained.
Impact of fix
can I work on this issue ?
| gharchive/issue | 2024-12-09T16:02:20 | 2025-04-01T06:38:38.427864 | {
"authors": [
"Srishtihere",
"ritikaGupta4"
],
"repo": "facebook/lexical",
"url": "https://github.com/facebook/lexical/issues/6926",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1928606100 | Update anchor selection if split by patching style
Problem
Setting styles using $patchStyleText does not update the selection when the anchor node is split. This causes the selection to contain a node that is not part of the selection. As a result, the toolbar/$getSelectionStyleValueForProperty is not able to determine the correct selection style.
https://github.com/facebook/lexical/assets/1575198/e438e605-4d4d-4c78-9967-e3176ed531f8
Solution
Update the selection anchor with the new text node after splitting.
https://github.com/facebook/lexical/assets/1575198/22c177ae-fd17-4b30-bb68-2adab21a9b78
Failed tests seem spurious 😏
| gharchive/pull-request | 2023-10-05T15:53:07 | 2025-04-01T06:38:38.430185 | {
"authors": [
"Piliuta"
],
"repo": "facebook/lexical",
"url": "https://github.com/facebook/lexical/pull/5087",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
17035427 | Add BSER load/dump support for variants
BSER is a local-IPC only serialization format for dynamic data:
https://github.com/facebook/watchman/blob/master/BSER.markdown
Adding support for this to Phenom requires adding load/dump APIs similar to the JSON load/dump API.
It also means adding API support for "Array of Templated Objects". In Watchman, this is achieved simply by storing the template definition as a special property of the object type.
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.
| gharchive/issue | 2013-07-22T08:24:50 | 2025-04-01T06:38:38.432210 | {
"authors": [
"facebook-github-bot-1",
"wez"
],
"repo": "facebook/libphenom",
"url": "https://github.com/facebook/libphenom/issues/1",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
455316403 | Issue with hotfix for w3c chromeOptions
What are you trying to achieve? (Expected behavior)
Adapt acceptance testing with Codeception for ChromeDriver v75, using webdriver v1.7.0.
What do you get instead? (Actual behavior)
In the code of the hotfix for w3c I get an error toArray() called on Array for Facebook\WebDriver\Remote\RemoteWebDriver line 112.
if (!isset($chromeOptions->toArray()['w3c'])) {
How could the issue be reproduced? (Steps to reproduce)
Using Codeception pass capabilities to chromeOptions
modules:
enabled:
- WebDriver:
url: http://localhost:8000
browser: chrome
port: 9515
restart: true
capabilities:
chromeOptions:
args: ["--headless", "--disable-gpu", "--no-sandbox"]
Details
Php-webdriver version: 1.7.0
PHP version: 7.3
Operating system: Linux
Browser used + version: ChromeDriver v75
I believe the cause is that the hotfix assumes the class Facebook\WebDriver\Chrome\ChromeOptions is always used, but before the hotfix it allowed passing an array instead.
Ah, nevermind I see now it is fixed in main branch, just not released yet.
Yes, fixed in 1.7.1.
Ref. #642 .
Still no substance
| gharchive/issue | 2019-06-12T16:40:05 | 2025-04-01T06:38:38.453797 | {
"authors": [
"OndraM",
"riotCode",
"temptationdrops"
],
"repo": "facebook/php-webdriver",
"url": "https://github.com/facebook/php-webdriver/issues/646",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
126228593 | Fix theoretical memory tracking leak
DriverFactory is not guaranteed to be closed. It's only closed when all
splits have been received and drivers created for them. However,
several OperatorFactories rely on close() being called.
For example, LookupJoinOperatorFactory will "leak" memory in the memory
tracking system, if close() is not called.
looks good
| gharchive/pull-request | 2016-01-12T17:21:10 | 2025-04-01T06:38:38.457665 | {
"authors": [
"cberner",
"dain"
],
"repo": "facebook/presto",
"url": "https://github.com/facebook/presto/pull/4319",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
1194489457 | update Docusaurus and other deps, fix broken styles
Why & how
Superseeds:
#3022
This PR updates Docusaurus to latest beta (beta.18) and most of the other dependencies.
Due to changes in Docusaurus code, I had to adjust the config and add a bunch of fixes to our custom styles, which become broken after the update. I also had to duplicate the GA move in the config, otherwise the website won't start.
Test plan
I have run the updated version of the website on localhost and I used the currently shipped website as a 1:1 comparison, so the style issues was easier to spot, however, there still might be small display problems which I was not able to catch. If you see any regression in preview deploy, please let me know!
I think this looks good! Are there particular places we should look for breakages? I guess, also should we confirm that GA tracking is working (tbh not sure how to do that)
Are there particular places we should look for breakages?
Generally every layout have at least one issue, sidebars too, only home page looks correct after upgrade, so it's hard to point on the specific thing. I usually test few pages, with focus on the origin diversity:
homage (custom JS)
versioned doc page (docs plugin)
blog post list and blog post (blog plugin)
community page (custom MD)
I guess, also should we confirm that GA tracking is working (tbh not sure how to do that)
The fix has been deployed yesterday in separate PR, so you probably should see a data spike on the GA dashboard now, if everything is working correctly.
Oh actually I do think I found an issue -- I thought it was a general issue but it's not reproing off prod: https://github.com/facebook/react-native-website/issues/3061
I have fixed the mobile menu hover issue and the deploy preview should be updated.
Please let me know, if now it looks fine for you.
| gharchive/pull-request | 2022-04-06T11:41:50 | 2025-04-01T06:38:38.462980 | {
"authors": [
"Simek",
"lunaleaps"
],
"repo": "facebook/react-native-website",
"url": "https://github.com/facebook/react-native-website/pull/3059",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
210259933 | Jest coverage is throwing packager errors
Description
What I did
I added Jest to my project and started generating code coverage reports, which creates a folder named "coverage" at the project root.
What you expect to happen
I expected nothing to happen with the code.
What actually happens
Packager is looking at it for some reason, and it is causing an error.
TransformError /PATH/coverage/lcov-report/sort-arrow-sprite.png: Unexpected character '�' (1:0)
Reproduction
Having trouble reproducing.
Solution
The coverage folder should not be included in the packager logic or I should be able to ignore it. It’s unclear why it is looking in there as I have not linked to any files in the folder.
Additional Information
React Native version: 0.39.2
Platform: iOS
Operating System: OS X 10.12.3
cc @cpojer
I have since upgraded to 0.41.2 and am still experiencing the issue, so any additional notes may be applicable to only this newer version
Tried https://github.com/facebook/react-native/issues/7271#issuecomment-215375355 and it didn’t work
It throws the error when the coverage report is generated. If I hit reload, I can use my app just fine even though the offending .png is still present. It seems to be that the Packager file watcher is having/starting/causing the issue.
This worked for me http://stackoverflow.com/a/41963217/537998
This still feels like a bug to me, but I’ll close since the issue can be resolved.
this is more like a bug. Quite unintuitive to do this with every react native project
| gharchive/issue | 2017-02-25T20:32:26 | 2025-04-01T06:38:38.468794 | {
"authors": [
"ericvicenti",
"kirkstrobeck",
"rogerkerse"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/12582",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
214779457 | Prevent system font from overriding app font
I need to force app font inside the app and not to be overridden by system font. Namely font size and fontFamily. I also added the font I am using in assets and resources for android and iOS respectively.
rn: 0.42
Hey, thanks for reporting this issue!
It looks like your description is missing some necessary information. Can you please add all the details specified in the template? This is necessary for people to be able to understand and reproduce the issue being reported.
I am going to close this, but feel free to open a new issue with the additional information provided. Thanks!
| gharchive/issue | 2017-03-16T17:23:36 | 2025-04-01T06:38:38.470798 | {
"authors": [
"damathryx",
"hramos"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/12978",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
351838748 | Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'double java.lang.Double.doubleValue()' on a null object reference
Environment
Binaries:
Node: 8.0.0 - /usr/local/bin/node
npm: 6.3.0 - /usr/local/bin/npm
SDKs:
Android SDK:
Build Tools: 23.0.1, 25.0.0, 25.0.1, 25.0.2, 25.0.3, 26.0.2, 26.0.3, 27.0.1, 27.0.3
API Levels: 23, 25, 26, 27
IDEs:
Android Studio: 3.1 AI-173.4907809
npmPackages:
react: ^16.4.2 => 16.4.2
react-native: ^0.56.0 => 0.56.0
Description
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'double java.lang.Double.doubleValue()' on a null object reference
at com.facebook.react.bridge.ReadableNativeArray.getDouble(ReadableNativeArray.java:114)
at com.facebook.react.bridge.JavaMethodWrapper$4.extractArgument(JavaMethodWrapper.java:64)
at com.facebook.react.bridge.JavaMethodWrapper$4.extractArgument(JavaMethodWrapper.java:60)
at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:359)
at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:160)
at com.facebook.react.bridge.queue.NativeRunnable.run(NativeRunnable.java)
at android.os.Handler.handleCallback(Handler.java:836)
at android.os.Handler.dispatchMessage(Handler.java:103)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:29)
at android.os.Looper.loop(Looper.java:232)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$3.run(MessageQueueThreadImpl.java:192)
at java.lang.Thread.run(Thread.java:761)
+1
| gharchive/issue | 2018-08-18T17:48:32 | 2025-04-01T06:38:38.475135 | {
"authors": [
"evoquelab",
"nes123"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/20727",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
404205560 | Error calling JSTimers.CallTimers
Environment
[skip envinfo]
Description
I am trying to run my app on Android (One plus 6t). This was working fine before making a call to firebase but as soon as I add the line onSend={Fire.shared.send} to Chat.js, the app crashes. The logs just show Uncaught Error: Error calling JSTimers.CallTimers. Haven't seen this error anywhere else. Does anyone know what's the issue?
Reproducible Demo
Here's the snack: https://snack.expo.io/@adititipnis/community
i have same issue as you, any help?
Does anyone know a solution to this issue?
React Native Version: 0.59.9;
Platform: Android
Reproduce step:
1、 start an animation in react native view!
Animated.timing(translateX, {
toValue: 10,
duration: 200,
easing: Easing.inOut // this config crash and throw Error calling JSTimers.callTimers
// easing: Easing.in //this config work well.
}
)
render() {
const { translateX } = this.state;
const marginRight = translateX.interpolate({
inputRange: [0,1],
outputRange: [-100, 0]
})
return <Animated.View style={{marginRight}}>...</Animated.View>
}
my same problem fixed by this way :
if (!isNaN(toValue)) {
//start animation
}
//full code may be help you
const { duration, marqueeDelay, loop, isInteraction, useNativeDriver, easing, children, scrollingSpeed } = this.props
this.setTimeout(() => {
if (!isNaN(this.distance)) {
Animated.sequence([
Animated.timing(this.animatedValue, {
toValue: this.distance,
duration: duration || (this.distance) * scrollingSpeed,
easing: easing,
isInteraction: isInteraction,
useNativeDriver: useNativeDriver
}),
Animated.timing(this.animatedValue, {
toValue: 0, //-this.distance ,
duration: duration || (this.distance) * scrollingSpeed,
easing: easing,
isInteraction: isInteraction,
useNativeDriver: useNativeDriver
})
]).start(({ finished }) => {
if (finished) {
this.hasFinishedFirstLoop = true
}
if (loop) {
this.animateBounce()
}
})
} else {
this.start()
}
}, this.hasFinishedFirstLoop ? 0 : marqueeDelay)
| gharchive/issue | 2019-01-29T09:51:23 | 2025-04-01T06:38:38.479627 | {
"authors": [
"adititipnis",
"cinder92",
"eleallegue",
"luoyushouchai",
"saeedhassankhan"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/23200",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1732887513 | Could not find module ... for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator,
Description
Hello.
Context
We have RN iOS project with CocoaPods dependecies, but we want to add some dependencies via SPM.
In our Podfile, we have following lines:
installer.pods_project.build_configurations.each do |config|
config.build_settings["EXCLUDED_ARCHS[sdk=iphonesimulator*]"] = "arm64"
end
Without this lines — build fails by different errors from Pods
Right now if we will try to add SPM package to project, we have two scenarios:
Option 1 : Rosetta — turn on, project with connected SPM + Pods builds correctly. We don't want to use Rosetta at all
Option 2 : Rosetta — turn off, project build with connected SPM + Pods fails with an error Could not find module PACKAGE NAME for target 'x86_64-apple-ios-simulator'; found: arm64-apple-ios-simulator
What we want to achive
We want to be able to add SPM packages to Xcode project, continue to use Pods and don't use Rosetta . Does any one faced with this problem or has some solutions?
React Native Version
0.7
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 13.1
CPU: (10) x64 Apple M1 Pro
Memory: 227.15 MB / 32.00 GB
Shell: 5.8.1 - /bin/zsh
Binaries:
Node: 16.20.0 - /usr/local/opt/node@16/bin/node
Yarn: 1.22.11 - ~/Documents/WORK/Breadfast/ReactNative-customer-app/node_modules/.bin/yarn
npm: 6.14.13 - ~/Documents/WORK/Breadfast/ReactNative-customer-app/node_modules/.bin/npm
Watchman: 2023.04.10.00 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 22.2, iOS 16.2, macOS 13.1, tvOS 16.1, watchOS 9.1
Android SDK: Not Found
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 14.2/14C18 - /usr/bin/xcodebuild
Languages:
Java: Not Found
Python: Not Found
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Xcode project generated by RN tools
Any SPM package
Turn off Rosetta on Mac
Snack, code example, screenshot, or link to a repository
Hi, you can use this in your podfile :
post_install do |installer|
installer.pods_project.targets.each do |target|
target.build_configurations.each do |config|
config.build_settings["ONLY_ACTIVE_ARCH"] = "NO"
end
end
end
| gharchive/issue | 2023-05-30T19:43:15 | 2025-04-01T06:38:38.488294 | {
"authors": [
"rvasseur31",
"solveit-andrey-savich"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/37627",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
258374796 | uniq with an iteratee is uniqBy
The wrong version of the function was being used which was resulting in flow errors.
See https://lodash.com/docs/4.17.4#uniqBy for reference.
Test Plan
There should probably be a test for this. According to the lodash source, calling uniq with a second argument is not supported.
Flow correctly picks up on this, and is causing errors in my project.
I believe we merged similar PR a couple of weeks ago 🤔
Just found it. Seems we already have a PR that has been opened for a while (26 days). I don't want to discourage you, but I would prefer merging it that PR as far as it was the first one and we already reviewed it. Thanks for pointing out that we didn't merge it yet (in my mind we did haha)!
Hope to see more contributions from you in the future!
That's all good, just want to get it merged :)
| gharchive/pull-request | 2017-09-18T05:43:06 | 2025-04-01T06:38:38.491810 | {
"authors": [
"Kureev",
"deecewan"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/15979",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
106323494 | [TextInput] Add controlled selection prop
For prior discussion with @brentvatne @sahrens @yelled3 see #2478
Again, some notes and points for discussion:
I think using a NSDictionary is fine for the native prop type.
Should RCTTextView and RCTTextField share the implementation of setSelectionRange, or would that not be worth the effort? There's a little bit of duplication there.
In iOS you can set selectedTextRange to nil. It removes the cursor but keeps the input focused and available for inputs from the keyboard. I decided not to support it in this PR.
I'd love to follow this up with a PR for selection change events :smile:
Looks like some flow version change makes the e2e build fail: https://travis-ci.org/facebook/react-native/jobs/80185569#L929
I guess I'll just wait until that's resolved in master and re-run the build or rebase the PR?
LGTM @ehd
By the way, if there's any feasible way to offer the same functionality via an external npm package I'd also love to do that. I'm not sure whether it's possible to tie into native internals (I doubt it). I know that the maintainers are super busy right now and I'd like to test the API for a bit, let people try this out and maybe have someone contribute android parity.
Was curious about the status on this. Really excited about this feature! Hope to see it soon.
I'm going to rebase these changes on top of the current master soon.
@sahrens Since we talked in #2478, anything you want me to do to get this to review?
I merged these changes into my own branch and it worked great. The example in UIExplorer was helpful. The only gotcha for me was that at first I was trying to call setSelectionRange immediately after calling setState (in order to auto-insert a forward slash for a date). This did move the cursor properly which I'm guessing is due to the asynchronous nature of setState. This was solved by calling setSelectionRange either in componentDidUpdate or the setState callback.
This will be super helpful to start building some higher order text inputs with auto-insert and auto-complete. Nice job @ehd.
@brentvatne you think this could this be included in v0.14.0?
One question I have is whether the selection range should be a controlled prop. I bet there are some lessons learned from <Input> elements in the browser and whether a prop or an imperative method is preferable. Someone from FB UIE should take a look.
Otherwise this feature looks good... cc @sahrens
@ide I updated the PR to resolve the merge conflicts and update the warning log message text. Would be great to get some feedback regarding controlled prop vs. imperative method!
Have you looked into how this is going to work on Android? Ideally it should have the same API on both.
Have you looked into how this is going to work on Android? Ideally it should have the same API on both.
@mkonicek I haven't yet. I was thinking it would be great if someone familiar with Android development could look into this. Also, if they could comment on the user-facing API that would already help a lot, I think.
I'm really excited about the new rich text in TextInput support on iOS! Going to rebase this code on top of v0.15.0-rc and master tonight.
The implementation looks good to me as far as it goes. But I'm curious how this is used though without having an equivalent "onSelectionChange" event. It seems like you'd have no way of knowing what selection the user currently has, so you'd be overriding blindly, without being able to extend or restore the original values.
@ide's idea of making it a controlled property is also interesting - that would certainly make sense given how setting the text value works currently, as you'd probably want to implement text and selection updates in lock-step if you were doing something like real-time text replacement.
The implementation looks good to me as far as it goes. But I'm curious how this is used though without having an equivalent "onSelectionChange" event. It seems like you'd have no way of knowing what selection the user currently has, so you'd be overriding blindly, without being able to extend or restore the original values.
That is correct. This would make a lot more sense with the selection change event working. Can I ask: Is there any internal version on this? I've seen references to DocumentSelectionState. I'm happy to implement that event in this PR.
@ide's idea of making it a controlled property is also interesting - that would certainly make sense given how setting the text value works currently, as you'd probably want to implement text and selection updates in lock-step if you were doing something like real-time text replacement.
Like this, for example?
<TextInput
selectionRange={[0, 3]} // Array variant
selectionRange={{start: 0, end: 3}} // Object variant
value='Foobar'
/>
Yeah, we do have a selectionChanged event internally. I'll add that to the open source version so we're consistent
Yeah, we do have a selectionChanged event internally. I'll add that to the open source version so we're consistent
That sounds great. So how about this:
onSelectionChange event and prop are added to the open source version
I make a controlled-prop version of selectionRange as @ide suggested, which is feasible with the event. I think I prefer that as an API.
Thats sounds good to me. @sahrens ?
I've landed the onSelectionChange event: https://github.com/facebook/react-native/commit/5a34a097f2d2324e5515e876a20fd5b7a376aa3e
@nicklockwood Thank you! I'll see to the controlled-prop API for selectionRange.
Apologies for the delay, I'm finally getting to this. Let me know if someone's got a better idea or a hot commit sitting somewhere. Otherwise I'll update the branch head to a new commit on top of the current master with this API:
class ControlledSelectionRange extends React.Component {
state = {
selectionRange: {start: 0, end: 0}
}
render() {
return (
<TextInput
selectionRange={this.state.selectionRange}
onSelectionChange={selectionRange => this.setState({selectionRange})}
/>
)
}
}
cc @nicklockwood @sahrens
Just resolved some merge conflicts with master. Now working on the API changes.
Since we're not going with the DOM API inspired naming anymore I'm changing the prop's name to just selection.
This turns out to be more difficult than I thought. I can't find a way to set selections programatically that won't also trigger the onSelectionChange event handler and thus cause a loop.
Similar to setText I'm comparing the input's current selectedTextRange, but this can't solve the problem of different selection change events causing overlaps and an change event -> set state -> change event -> set state loops.
Any ideas? I also commented here: https://github.com/facebook/react-native/commit/5a34a097f2d2324e5515e876a20fd5b7a376aa3e
Can't you filter out events that don't actually change anything? That
should be able to break any loops.
In general this seems like the right approach.
On Thursday, December 3, 2015, Stephan Seidt notifications@github.com
wrote:
This turns out to be more difficult than I thought. I can't find a way to
set selections programatically that won't also trigger the
onSelectionChange event handler and thus cause a loop.
Similar to setText I'm comparing the input's current selectedTextRange,
but this can't solve the problem of different selection change events
causing overlaps and an change event -> set state -> change event -> set
state loops.
Any ideas? I also commented here: 5a34a09
https://github.com/facebook/react-native/commit/5a34a097f2d2324e5515e876a20fd5b7a376aa3e
—
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/pull/2668#issuecomment-161814405
.
@sahrens I tried doing that by comparing the requested selection range's start and end offsets with the textField or textView's current selectedTextRange start and end offset, but under certain circumstances they always perfectly did not match up properly. I also tried comparing with _previousSelectedRange but that didn't work either. I'll push what I tried in a bit.
:+1:
@ehd Any updates on this?
@satya164 I would get back to this next week, in vacation mode right now.
@ehd Awesome. looking forward to it.
Happy new year :wink: I'm on this again, @janmonschke is in, too! :smile:
Ouch, I think I got it... It works quite nicely, without a loop now. Here's what I did wrong in my setSelection method:
BAD:
_textView.selectedTextRange = selectedTextRange;
_previousSelectionRange = selectedTextRange;
GOOD (set the previous value first so the event handler won't trigger):
_previousSelectionRange = selectedTextRange;
_textView.selectedTextRange = selectedTextRange;
I didn't anticipate that the event handler would be called in the former case.
Polishing this now, then pushing to my branch and we can bikeshed on the API. Yay :fireworks:
This is the API:
<TextInput
selection={{start: 0, end: 5}}
value="Hello, World"
/>
There's an extensive demo in UIExplorer -> .
@satya164: This is working now!
@sahrens: Thanks for the hint again.
@nicklockwood: What do you think?
Hmm. How to handle changing the selection and value props at the same time, actually?
@ehd the selection should presumably always be applied after the value? It might make sense to use the didUpdateProps method instead of overriding the setText and setSelection setters, then you can ensure they are applied in the correct order.
Yeah, what @nicklockwood says. :+1:
the selection should presumably always be applied after the value?
Yep, that was my intuition. I think this would be the least surprising behaviour:
Set text only: Keep sensible selection (current behaviour from #4716)
Set selection only: Change selection
Set text and selection: Change text and selection
It might make sense to use the didUpdateProps method instead of overriding the setText and setSelection setters, then you can ensure they are applied in the correct order.
Oh yeah, that sounds interesting! This is what I understand the text setter is doing right now:
Ignore text update if there's event lag
Ignore text update if native text is the same value
Manage cursor and selection, changed recently in #4716 to "keep the distance of the cursor from the end of the text constant"
@nicklockwood I was trying to come up with a plan, but I'd like to clarify a few things first:
If we don't override the setters, where are we going to coordinate text and selection management in the native component? Where to compensate for lag and same-value updates?
Should there be a single native setter for changing both text and selection?
If possible I would also like to do something about the almost duplicate setText code in UITextField.m and UITextView.m.
@ehd you may still want to override one or both of the setters, but just do some extra logic in didUpdateProps (like actually applying the selection to the view).
Regarding duplicate logic - I suggest creating an RCTTextUtils file and moving any common logic into there as static C functions (much as we've done with RCTImageUtils).
Eventually, I'd like to combine RCTTextField and RCTTextView into a single class, but that's a big job that I don't think we're ready to do just yet.
@ehd you may still want to override one or both of the setters, but just do some extra logic in didUpdateProps (like actually applying the selection to the view).
@nicklockwood Could you give me an example of how to do that? For example, if I overwrote both setters I wouldn't know how to use them properly in didUpdateProps. Maybe didUpdateProps is something other than componentDidUpdate?
@ehd didUpdateProps: is a native method that you can define on RCTTextView. It will be called after the native prop setters have been called, and its parameter contains an array of all props that were updated.
@ehd Ah, sorry, it's called didSetProps:, not didUpdateProps:. My bad 😬
Example:
(void)didUpdateProps:(NSArray<NSString *> *)changedProps
{
if ([changedProps containsObject:@"selection"]) {
//set the selection
}
}
@nicklockwood Holy cow, exactly what we need, thanks!
@nicklockwood Do we need to implement both setters in any case, just so we can intercept the prop value and store it in an instance variable? Or is there another way to access the props (since changedProps just contains key names)?
@ehd Declaring NSDictionary *_selection; along with the other ivars in RCTTextView.m (line 64) should be sufficient. If the ivar exists, it will be set automatically by the view manager.
@nicklockwood Yup, that works nicely for storing the prop values!
So now most of setText is in didSetProps (event lag guard, set text, maintain selection). I'm adjusting it so it works for setting just text, just selection or both text and selection. I think that is the only way, because if text or selection are changed before didSetProps it's a mess to save intermediate values for those in more ivars (old selection, old length).
When that code works it'll move into a helper that's used from both TextView and TextField, probably also the rich text input handling in TextView.
One thing I haven't fully understood yet is _previousSelectedRange. Is it to prevent selection change loops?
@ehd it's just because textViewDidChangeSelection: sometimes fires in situations where the range hasn't actually changed, so I use that to verify that the new range is different before sending the event.
@nicklockwood I see, good to know! While working on this I've also observed selection changing to place the cursor at the end of the text when setting the selection prop, not sure yet why.
I did some research on the current onSelectionChange event behaviour comparing UITextField and UITextView. It seems to be inconsistent :cry:
How to reproduce:
Create a <TextInput>
Set value to "Hello World"
Focus by tapping on area right of text
Place cursor at "Hello| World" by hand
Set value to "Well, Hello World"
Results in cursor at "Well, Hello| World" (as per #4716)
The onSelectionChange events of a single line TextInput (UITextField):
{start: 5, end: 5} (from step 4)
{start: 11, end: 11} (from step 5)
Note that there is no selection change event caused by step 3 which is not what I expected. Imagine a Twitter-like completion UI where the value is "Hi @" with the cursor at "Hi @|", the completion would not know about the cursor position on focus and not provide a completion. A solution could be having to set a controlled selection prop to {start: value.length, end: value.length} in JS when needed.
The onSelectionChange events of a multiline TextInput (UITextView):
{start: 11, end: 11} (from step 2, not caused by step 3!)
{start: 5, end: 5} (from step 4)
{start: 17, end: 17} (from step 5)
{start: 11, end: 11} (also from step 5)
I did not expect the 17,17 event to appear, and it causes flickering & other problems when selection is a controlled prop. I haven't yet found out whether that behaviour is exhibited by UITextView itself or RCTTextView. The 11,11 event is originating from RCTTextView's cursor placement. The multiline TextInput emits selection events even if the field isn't focused, the single line TextInput doesn't. I suggest we consolidate these behaviours:
First: Can an unfocused field have a selection at all?
TextInput should emit an initial event when it's focused
TextInput shouldn't emit selection change events if field isn't focused
TextInput shouldn't emit multiple events on cursor correction
@nicklockwood Should single line and multiline emit the same events and behave the same way?
Any opinions on this?
@ehd, sorry I thought I'd replied :-/
Thanks for doing that research, and yes, ideally we'd want single line and multiline events to behave the same, and I agree with your suggestions for what the expected behavior should be.
@nicklockwood No worries, I really appreciate all your help and input! I'm going to look into normalizing the events :smile:
Thanks for working on this feature! I've been looking into what is needed for Android parity, has anyone taken a stab at it yet?
@ehd Since no one has chimed in, I've pushed a branch to do the most basic setting of text selection on Android. It currently sets the text selection directly in the property setter, as opposed to doing the event normalization described above:
https://github.com/Ginger-Labs/react-native/tree/text-input-set-selection-android
Let me know if this is useful. It does contain a bug that keeps the selection from sticking when the selection change immediately follows a user tapping to place the cursor. I found a suboptimal workaround for this (https://github.com/Ginger-Labs/react-native/tree/hack-to-fix-android-text-input-selection), but it is not the proper way to address the issue, which appears to come from somewhere deep in the redraw/input lifecycle.
Any update on whether / when this might get merged? This would be very helpful.
@cgilboy Thanks for doing the Android work :)
@joel100 Currently I got stuck before normalizing the selection change events. The selection prop won't work properly unless the events are emitted in a sound way, regardless of whether it's a single line or a multiline input.
@sahrens would you mind taking a look at this pull request? It's been a while since the last commit was reviewed.
I'll try assigning this to @sahrens as Nick has too many PRs to review. Do we want to proceed with this?
I did a really quick implementation for setting the selection on Android in https://github.com/exponentjs/react-native/commit/7a59fba694ee0bdeaa9f63e97033abdb2ea7c807 -- I'm happy to flesh it out to work the same as this one once this PR lands.
@brentvatne Do you know if this PR needs changes? Spencer commented 15 days ago and I added the Needs revision label based on his comment.
I'm actually not sure @mkonicek -- @sahrens @ehd - what's the status here?
FWIW this looks good to me. Nice work @ehd! @mkonicek The only change requested that is left was to switch to dot notation.
@brentvatne do you have a PR in for the Android side? 😁
Would love to see this land. Can't really do any input masking without this feature.
@ekryski - no PR for this yet but I'm going to have some cycles soon to clean up some of the stuff we've done on our internal fork so I made a note to come back to this one
Closing in favour of @janicduplessis PR's.
I can't figure out how to programatically call setSelection. It's not on the ref like .focus and .blur, would I have to use setNativeProps? Or is using the selection property the only way? I just needed a one time thing so I was trying the method call way.
Oh figured it out. Yep setNativeProps does the trick. Super cool thanks guys!
this.input.setNativeProps({ selection:{ start:1, end:1 } })
| gharchive/pull-request | 2015-09-14T11:36:53 | 2025-04-01T06:38:38.542195 | {
"authors": [
"Noitidart",
"brentvatne",
"cgilboy",
"ehd",
"ekryski",
"esauter5",
"facebook-github-bot-7",
"ide",
"janmonschke",
"javache",
"joel100",
"mkonicek",
"nicklockwood",
"sahrens",
"satya164",
"webgoudarzi",
"yelled3"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/2668",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1243115202 | Fix hermes compilation in the react-native package
Summary
When releasing the latest RC, we have noticed pod install is broken since the downloaded react-native package is missing hermes scripts and shelljs dependency (needed by hermes-utils.js).
Changelog
[Internal] - Fix compiling hermes in the release version.
Test Plan
Run test-manual-e2e.sh with template and Hermes on iOS
Ooof, thank you for fixing this!
| gharchive/pull-request | 2022-05-20T12:57:44 | 2025-04-01T06:38:38.546424 | {
"authors": [
"fortmarek",
"hramos"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/33881",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
150538869 | [CI] Exit with the error status code from xcodebuild
See https://github.com/supermarin/xcpretty#usage -- xcpretty will suppress xcodebuild's status code so we need to add && exit ${PIPESTATUS[0]}.
Test Plan: Look at Travis CI results and see that an error with the Obj-C tests is properly reported as a CI error.
Let's see the CI results
Travis tests are green because the 2nd retry of the Obj-C tests actually succeeded. Not sure if this diff truly fixes the status code, but it can't make things worse.
Shipit :)
We will monitor stability over time
On Saturday, 23 April 2016, James Ide notifications@github.com wrote:
Travis tests are green because the 2nd retry of the Obj-C tests actually
succeeded. Not sure if this diff truly fixes the status code, but it can't
make things worse.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/facebook/react-native/pull/7172#issuecomment-213714716
@facebook-github-bot shipit
| gharchive/pull-request | 2016-04-23T10:07:12 | 2025-04-01T06:38:38.550433 | {
"authors": [
"bestander",
"ide"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/7172",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
159631386 | Update docs for textDecorationStyle
This PR fixes the documentation for the textDecorationStyle prop in the Text component documentation.
textDecorationLine and textDecorationStyle were added for Android in https://github.com/facebook/react-native/releases/tag/v0.25.1
Only textDecorationLine was updated at the time https://github.com/facebook/react-native/commit/2039be9d32a52552db02239040bd8e7257bb80f0#diff-8d238dc2c74635b2aaca431551873addL55
By analyzing the blame information on this pull request, we identified @trave7er and @Kudo to be potential reviewers.
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks!
As far as I can see, textDecorationStyle is still not available on Android. The release notes also no longer mention this.
Hi @javache,
maybe I did not link it but in the 0.27 release it's already in the android examples and in my project using 0.26 it's working :)
Could you link to the native code that implements this?
@javache you are right, I cannot find anything for textDecorationStyle that is like like the implementation for setTextDecorationLine . And, at the moment, it's working only the solid value for textDecorationStyle. Sorry about that.
| gharchive/pull-request | 2016-06-10T13:08:16 | 2025-04-01T06:38:38.556200 | {
"authors": [
"facebook-github-bot-7",
"javache",
"p16"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/8045",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
163480285 | Add post documentation lockdown survey link
We did a survey prior to the doc lockdown to get an idea of what we should focus on. Now we have a yes/no style survey to ensure that we met the user needs when it came to our start of improving the docs.
This diff adds the survey link to the bottom of each page. And we will cherry-pick it into 0.29 as well, which will be the first official release with the new doc content
NOTE: The content via the links in this survey will not be valid until 0.29 is actually released. So I have not enabled the questions for the survey until then.
Test Plan:
http://localhost:8079/react-native/docs/getting-started.html
By analyzing the blame information on this pull request, we identified @Andreyco and @caabernathy to be potential reviewers.
LGTM. Minor nit regarding the use of lockdown but I don't feel too strongly about it.
@hramos Ah - good point. Fixed.
@facebook-github-bot shipit
Something went wrong when importing this pull request. Please cc someone from the team at fb to help with importing this.
@facebook-github-bot shipit
Thanks for importing. If you are an FB employee go to Phabricator to review.
| gharchive/pull-request | 2016-07-01T21:53:26 | 2025-04-01T06:38:38.560751 | {
"authors": [
"JoelMarcey",
"facebook-github-bot-2",
"facebook-github-bot-5",
"facebook-github-bot-8",
"hramos"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/8530",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
302185857 | Better syntax error for return foo
Something like "return doesn't exist in Reason; blabla"
What if someone names a function return, as with monads (although that's a terrible name, it's still used)
We could make it a hint, like we’ve done in the past. The hints are 100% accurate but they help give some idea of what caused the problem. Like “did you miss a semicolon” etc
return foo is invalid syntax, not a function
Reason does not need something like this :/
Folks, please read the title. It's to provide better syntax error message when people attempt to do return foo, which is invalid in reason. Right now the error message is <UNKNOWN SYNTAX ERROR>
| gharchive/issue | 2018-03-05T06:30:00 | 2025-04-01T06:38:38.583131 | {
"authors": [
"bsansouci",
"chenglou",
"mrkaspa",
"ubsan"
],
"repo": "facebook/reason",
"url": "https://github.com/facebook/reason/issues/1845",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
155431257 | Add eval opam config env
I followed the installation instructions, but the rebuild command didn't work - but after running eval opam config env everything worked.
Good catch. One does need to eval opam config env to make new opam configs take effects in the current shell. We should definitely put this instruction in the doc.
The instruction to add opam config env is a few line above (in case you didn't see it)
(Hey again!)
@chenglou I think we need to be explicit that people have to type it in the current shell.
@SanderSpies Could you move the line right below opam switch 4.02.3 ? If someone was using another switch before he switched to 4.02.3, the package pinned below will be pinned to the original switch instead of 4.02.3 unless he types eval opam config env.
@yunxing Will do.
@chenglou (Hey!) Right, my mistake indeed.
| gharchive/pull-request | 2016-05-18T07:11:44 | 2025-04-01T06:38:38.586342 | {
"authors": [
"SanderSpies",
"chenglou",
"yunxing"
],
"repo": "facebook/reason",
"url": "https://github.com/facebook/reason/pull/476",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
66243487 | Upgrade gh-pages to reflect v1.1.0
This adds an elements screenshot and bumps the version numbers.
looks good (y)
| gharchive/pull-request | 2015-04-03T23:02:21 | 2025-04-01T06:38:38.603591 | {
"authors": [
"jasta",
"rickbrew"
],
"repo": "facebook/stetho",
"url": "https://github.com/facebook/stetho/pull/137",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
256042615 | From React
I am getting this issue:->
ERROR in ./client/index.js
Module build failed: SyntaxError: 'import' and 'export' may only appear at the top level (6:1)
4 | render components from here
5 | */
6 | import react from 'react';
| ^
7 | import reactDom from 'react-dom';
8 | import APP from './components/App.js';
9 | reactDom.render(, document.getElementById('app'));
@ multi main
Please provide the complete code.
I'll close this as it's been a day and it's likely you resolved it.
Effectively, you are not allowed to run any code before an import. They must be first.
Please move any code that is not an import below the imports.
| gharchive/issue | 2017-09-07T19:19:47 | 2025-04-01T06:38:38.639214 | {
"authors": [
"Timer",
"gaearon",
"radhey113"
],
"repo": "facebookincubator/create-react-app",
"url": "https://github.com/facebookincubator/create-react-app/issues/3093",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
225017163 | :art: add first class debugging support
continuation of #1360. re-implemented per code review remarks, and conflicts resolved. needs 👀 re-review :).
problem statement
react-scripts does not offer ready-to-roll jest debugging.
solution
add it!
closes #594
test
checkout this feature branch
/path/to/this/branch/create-react-app/bin/create-react-app dummy-app
cd dummy-app
modify npm test to add a debug flag ^^
tell your editor to honor source maps
npm test
connect the remote debugger
go.
back at cha
good news! debugging is working reliably! good enough where i think we should ship, after any polish requested is applied.
bad news, --inspect* is no bueno. essentially facebook/jest#1652 prevents us from using JSDom in jest & the inspector protocol simultaneously. i'm not enough of a jest+JSDOM wizard to figure that out.
the code has been annotated, and --debug-brk still works great :), even in watch mode!
note, jest in watch mode in master is really, painfully slow on OSX for whatever reason. unrelated to this PR, but woof!
i'm not sure when react-scripts is targeting another release, but i would really like to be able to bump my projects and start debugging asap! go team ⚽️
When can we expect a release including this issue?
BTW, I think the build needs to be kicked started again. I don't think my pathes are the source of failure. An extra set of :eyes: would be appreciated
@cdaringe I don't want to leave this hanging, but I don't know if we're going to ship this until https://github.com/facebook/jest/issues/1652 is resolved.
I feel very uncomfortable relying on a flag that's already deprecated 😞; are there workarounds we can implement to get inspect working?
I’m going to push this back to 0.11 so we can have the time to figure this out.
@Timer @gaearon,
why is node's flag deprecation a threat? i don't see any risk here. we only add value/capability in this PR. there's zero loss to stakeholders. we can rev react-scripts later when the jest team gets this sorted out.
i do not think there's a jest hack to make --inspect work in the interim
i'm not sure what more we need to figure out. there's a known open issue against our dependency stack, but there is a reliable, non-hacky workaround--just limit usage to the older, but well tested & supported protocol.
debug capability, IMHO, is super important, & this is the 2nd time I've implemented it. i'm not upset, but i do not want to have to do it a 3rd time. can you speak more to why you feel we shouldn't get this in sooner?
I strongly agree with @cdaringe, this is very important for productivity and one of the worst parts of CRA testing.
I agree, with @cdaringe also. My team needs this capability as soon as
possible.
On Mon, May 8, 2017, 6:35 PM Caio Balthazar notifications@github.com
wrote:
I strongly agree with @cdaringe https://github.com/cdaringe, this is
very important for productivity and one of the worst parts of CRA testing.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebookincubator/create-react-app/pull/2041#issuecomment-300010026,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgWoPOhKMtJexaWThVfx5D9uuBG-fvlks5r35iUgaJpZM4NLNqS
.
https://github.com/facebook/jest/issues/1652 has been closed with no action taken.
There is nothing Jest can do to fix it. Please express your support for https://github.com/nodejs/node/issues/7593.
At this point we just need somebody to help push this through.
https://github.com/nodejs/node/pull/9272#issuecomment-304365983
Any volunteers?
@cdaringe sorry I didn't respond earlier
why is node's flag deprecation a threat? i don't see any risk here. we only add value/capability in this PR. there's zero loss to stakeholders. we can rev react-scripts later when the jest team gets this sorted out.
It's not so much that it's a threat, but if it becomes something we support, it's turns into our job to maintain that feature going forward.
When Node 8 is released, it is highly likely that --debug will not exist anymore and the only option will be --inspect.
Jest doesn't work with --inspect, so we'd have to tell users to not upgrade their Node versions if they'd like to debug.
This puts us in a bad position because people will expect test debugging to work across all LTS versions of Node (as they should).
IMO, this is plunging us back into the era of JavaScript F***gue where environment matters and tools don't work reliably.
Secondly, Create React App is a toolchain focused at beginners first, but we still consider advanced users and try to accommodate their needs.
Teaching beginners how to debug using a deprecated method and then telling them they have to switch to --inspect (external of our control [based on their environment]) would be painful and cause a potentially poor/confusing experience.
debug capability, IMHO, is super important, & this is the 2nd time I've implemented it. i'm not upset, but i do not want to have to do it a 3rd time.
I'm really sorry that you feel your development efforts are being wasted.
We try really hard to incorporate as many changes as we can and try to ensure developers feel valued. (and we do value your contributions very much, really.)
We will use your work (and not waste it 😄) as a foundation for building out this feature in the future if you are unable to allocate time, but I hope you can understand our position.
I would feel comfortable adding support for --debug if we had a solid timeline and plan for Jest supporting --inspect (which is blocked by Node currently).
I think any effort here should be directed towards unblocking Node. Let's just fix it there.
Just dropping this here, speculation was correct and --debug is dead:
Joes-MacBook-Pro:16s-website joe$ node --debug
(node:70606) [DEP0062] DeprecationWarning: `node --debug` and `node --debug-brk` are invalid. Please use `node --inspect` or `node --inspect-brk` instead.
Really looking forward to https://github.com/nodejs/node/issues/7593 and https://github.com/nodejs/node/pull/9272#issuecomment-304365983 progressing.
Doesn’t seem like anybody wants to take ownership 😞 .
My support hath been cast!
This and various related issues have been open since fall 2016. It seems like debugging is a second class citizen in the react/jest/CRA community? I know some folks think if tests are so complicated you need to debug them, then you are doing it wrong, but I personally think a debugger (with good tests) is one of the most productivity enhancing tools of all times. It would give me great confidence in the react community if debugging was a first-class concern.
We'd really like to implement this feature but Node does not support it. See https://github.com/nodejs/node/issues/7593 and https://github.com/nodejs/node/pull/9272#issuecomment-304365983.
If you can help implement the feature in Node, that'd be great!
@timer can we move forward on this yet now that inspector has been merged in node?
FYI, debugging Jest tests with inspector is now possible as of Node 8.4.0 (https://github.com/nodejs/node/pull/14465).
@jgoz Thank you for mentioning that here! I'll upgrade and try it again. I'm very happy to see this fixed!
This and various related issues have been open since fall 2016. It seems like debugging is a second class citizen in the react/jest/CRA community?
No. We were just as frustrated about this. Unfortunately we lacked the necessary knowledge (knowing C, understanding of how contexts work in Node and V8) to fix this. We are also glad the fix has landed! Sometimes a hard fix is just a hard fix, and not some intentional choice. :-)
I don't understand what you mean about profiles.
Can any provide guidance as to how to debug Jest tests using Node.js 8.4.0? I've so far tried:
npm test -- --inspect-brk
and:
node --inspect-brk node_modules/jest/bin/jest.js -i
with no joy.
Can any provide guidance as to how to debug Jest tests using Node.js 8.4.0? I've so far tried:
npm test -- --inspect-brk
and:
node --inspect-brk node_modules/jest/bin/jest.js -i
with no joy.
@dchambers, see https://github.com/facebookincubator/create-react-app/issues/594#issuecomment-322842515. make sure you're using version 1.0.11+
Thanks @cdaringe, upgrading 'react-scripts' to 1.0.11 then running ./node_modules/.bin/react-scripts --inspect --inspect-brk test --env=jsdom --runInBand did it for me 🎉
Closing this as support has been added in 1.0.11, thanks for all of your hard work!
Hey all,
I think this is broken. I'm having issues with debugging my thinks.
Here's repro branch
https://github.com/TheTFo/cria/tree/jest-debug?files=1
Attempt to debug tests from vscode launcher, placing a break point on the line indicated in comment in this file:
https://github.com/TheTFo/cria/blob/jest-debug/src/actions/todoActions.js
Breakpoints don't appear to hit the appropriate lines. Not sure what's causing it. I don't see transpiled code, just wierd breakpoints hits.
@TheTFo had the same problem. Comment https://github.com/facebookincubator/create-react-app/issues/594#issuecomment-245426594 fixed it for me
| gharchive/pull-request | 2017-04-28T08:46:52 | 2025-04-01T06:38:38.668459 | {
"authors": [
"TheTFo",
"Timer",
"bgard6977",
"caiobalthazar",
"cdaringe",
"dchambers",
"gaearon",
"jgoz",
"lifeiscontent",
"valorize"
],
"repo": "facebookincubator/create-react-app",
"url": "https://github.com/facebookincubator/create-react-app/pull/2041",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
443661774 | EchoClient and EchoServer unable to establish connection
I can successfully compile the project on Ubuntu. 18.04,but when I run the sample client I get the following error:
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=server -host=127.0.0.1 -port=6666 -colorlogtostderr=true -alsologtostderr=true
I0514 08:35:31.092536 28271 EchoServer.h:80] Echo server started at: [::]:6666
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=client -host=127.0.0.1 -port=6666 -colorlogtostderr=true -log_dir="/home/vmtest/Documents/ietf_quic/mvfst/_build/build/quic/samples/" -alsologtostderr=true
I0514 08:36:33.769158 28283 EchoClient.h:127] EchoClient connecting to 127.0.0.1:6666
E0514 08:36:33.771145 28283 EchoClient.h:82] EchoClient error: Connect failed
It seems that the handshake method failed. (ClientHandshake::connect() )
What should I do to make the client and server connect successfully?
Can you include the verbose log from both the client and the server?
i.e. ./echo -mode=server -host=127.0.0.1 -port=6666 -colorlogtostderr=true -alsologtostderr=true --v=10
@udippant
vmtest@vmtest-virtual-machine:~/Documents/ietf_quic/mvfst/_build/build/quic/samples$ ./echo -mode=client -host=127.0.0.1 -port=6666 -colorlogtostderr=true -log_dir="/home/vmtest/Documents/ietf_quic/mvfst/_build/build/quic/samples/" -alsologtostderr=true --v=10
I0514 09:01:18.038892 28311 EventBase.cpp:117] EventBase(): Created.
I0514 09:01:18.039906 28312 EventBase.cpp:280] EventBase(): Starting loop.
I0514 09:01:18.040313 28312 QuicClientTransport.cpp:50] client created client CID=b1fbc0e40a8a05dc server CID=None peer address=
I0514 09:01:18.040407 28312 EchoClient.h:127] EchoClient connecting to 127.0.0.1:6666
I0514 09:01:18.041589 28312 StateMachine-inl.h:41] Transition from Uninitialized to ExpectingServerHello
I0514 09:01:18.041658 28312 QuicTransportFunctions.cpp:862] Client writing data using scheduler=CryptoAndAcksScheduler client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.041740 28312 QuicPacketScheduler.cpp:487] Wrote crypto frame offset=0 bytesWritten=234 client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042423 28312 QuicTransportFunctions.cpp:184] Client sent packetNum=0 in space=InitialSpace size=1255 client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042490 28312 QuicTransportFunctions.cpp:71] Client sent packetNum=0 space=InitialSpace client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042683 28312 QuicTransportFunctions.cpp:559] Client written crypto and acks data type=Initial packets=1 client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042752 28312 QuicLossFunctions.h:189] setLossDetectionAlarm setting transmission alarm=99ms method=Handshake outstanding=1 handshakePackets=1 pureAckPackets=0 Client client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042807 28312 QuicTransportBase.cpp:1974] schedulePathValidationTimeout cancel timeout client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042855 28312 QuicTransportBase.cpp:1038] Client stopping write looper client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.042981 28312 AsyncUDPSocket.cpp:491] AsyncSocket::handleErrMessages(): recvmsg returned 1
I0514 09:01:18.043046 28312 AsyncUDPSocket.cpp:491] AsyncSocket::handleErrMessages(): recvmsg returned -1
I0514 09:01:18.043131 28312 QuicTransportBase.cpp:274] Stopping read looper due to immediate close client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.043187 28312 QuicTransportBase.cpp:692] Stopping read looper client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.043282 28312 QuicTransportBase.cpp:1000] Stopping peek looper client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
I0514 09:01:18.043331 28312 QuicTransportBase.cpp:1025] Client stopping write looper because conn closed client CID=b1fbc0e40a8a05dc server CID=None peer address=127.0.0.1:6666
E0514 09:01:18.043413 28312 EchoClient.h:82] EchoClient error: Connect failed
I was able to reproduce this as well with the echo client / server examples:
./echo -mode=client -host=127.0.0.1 -port=6666 -colorlogtostderr=true -log_dir="/home/agnosticdev/Documents/code/cpp/mvfast/_build/build/quic/samples/logs" -alsologtostderr=true
./echo -mode=server -host=127.0.0.1 -port=6666 -colorlogtostderr=true -alsologtostderr=true --v=10
I0513 21:20:21.171392 14234 EchoServer.h:80] Echo server started at: [::]:6666
I0513 21:20:21.171388 14241 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d74f0 thread=139644201064192 processId=0
I0513 21:20:21.171394 14240 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d7210 thread=139644209456896 processId=0
I0513 21:20:21.171360 14236 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6680 thread=139644450768640 processId=0
I0513 21:20:21.171360 14237 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6960 thread=139644442375936 processId=0
I0513 21:20:21.171406 14242 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d77d0 thread=139644192671488 processId=0
I0513 21:20:21.171408 14234 EventBase.cpp:280] EventBase(): Starting loop.
I0513 21:20:21.171394 14238 QuicServerWorker.cpp:69] Registered read on worker=0x55fb000d6c20 thread=139644433983232 processId=0
It looks like after resumeRead() calls out to AsyncUDPSocket and nothing else is recorded after that.
void QuicServerWorker::start() {
CHECK(socket_);
if (transportSettings_.pacingEnabled && !pacingTimer_) {
pacingTimer_ = TimerHighRes::newTimer(
evb_, transportSettings_.pacingTimerTickInterval);
}
socket_->resumeRead(this);
VLOG(10) << "Registered read on worker=" << this
<< " thread=" << folly::getCurrentThreadID()
<< " processId=" << (int)processId_;
}
void AsyncUDPSocket::resumeRead(ReadCallback* cob) {
CHECK(!readCallback_) << "Another read callback already installed";
CHECK_NE(NetworkSocket(), fd_)
<< "UDP server socket not yet bind to an address";
readCallback_ = CHECK_NOTNULL(cob);
if (!updateRegistration()) {
AsyncSocketException ex(
AsyncSocketException::NOT_OPEN, "failed to register for accept events");
readCallback_ = nullptr;
cob->onReadError(ex);
return;
}
}
Will keep digging.
there looks to be something off with bind. can you try remove the —client and —server arguments from your commands?
@lnicco
After updating the commands to:
Echo Server: ./echo --v=10
Echo Client: ./echo -mode=client --v=10
I am now able to see data being echoed on the server side:
I0514 05:09:48.316179 25235 QuicTransportBase.cpp:1143] Delivered eof to app for stream=0 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316190 25235 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316202 25235 QuicTransportBase.cpp:1023] Stopping peek looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316215 25235 QuicTransportBase.cpp:1043] Server stopping write looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316227 25235 EchoHandler.h:73] Got len=5 eof=1 total=5 **data=mvfst**
I0514 05:09:48.316241 25235 QuicTransportBase.cpp:1038] Server running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316254 25235 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316267 25235 QuicTransportBase.cpp:1038] Server running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316282 25235 QuicTransportFunctions.cpp:865] Server writing data using scheduler=FrameScheduler client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:51044
I0514 05:09:48.316308 25235 QuicWriteCodec.cpp:118] writing frame stream=0 offset=0 data=10 fin=1
Client:
b90af82c7 peer address=[::1]:6666
I0514 05:09:41.108058 25237 QuicTransportBase.cpp:1979] schedulePathValidationTimeout cancel timeout client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108064 25237 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108070 25237 QuicTransportBase.cpp:1023] Stopping peek looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:41.108076 25237 QuicTransportBase.cpp:1043] Client stopping write looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
mvfst
I0514 05:09:48.315528 25237 QuicTransportBase.cpp:581] Setting setReadCallback for stream=0 cb=0x7ffcd4996c48 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315577 25237 QuicTransportBase.cpp:717] Stopping read looper client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315599 25237 QuicTransportBase.cpp:1038] Client running write looper thisIteration=1 client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315615 25237 **EchoClient.h:167] EchoClient wrote "mvfst", len=5 on stream=0**
I0514 05:09:48.315644 25237 QuicTransportFunctions.cpp:865] Client writing data using scheduler=FrameSchedulerWithoutCrypto client CID=db2ee4d1754f2aa7 server CID=400001db90af82c7 peer address=[::1]:6666
I0514 05:09:48.315671 25237 QuicWriteCodec.cpp:118] writing frame stream=0 offset=0 data=5 fin=1
Do you want me to put a PR up to switch the echo example on the README?
I have a feeling like it’s something wrong with the binding to the v4 interface on the host. By default we bind to the v6 localhost which is ::1.
Ya please feel free to put up a pr to fix it to v6 localhost.
Ahh, yes. I see it now. It looks like the client() takes the FLAGS_host argument while the server is started with just FLAGS_port and FLAGS_port, so the server is then by default binding to ::1. Thank you!
if (FLAGS_mode == "server") {
EchoServer server(FLAGS_port, FLAGS_port);
server.start();
} else if (FLAGS_mode == "client") {
if (FLAGS_host.empty() || FLAGS_port == 0) {
LOG(ERROR) << "EchoClient expected --host and --port";
return -2;
}
EchoClient client(FLAGS_host, FLAGS_port, FLAGS_pr);
client.start();
} else {
LOG(ERROR) << "Unknown mode specified: " << FLAGS_mode;
return -1;
}
The update above does include passing in a IPv4 or IPv6 host argument to the echo server as well as a README fix.
Addressed on https://github.com/facebookincubator/mvfst/pull/13
| gharchive/issue | 2019-05-14T00:50:47 | 2025-04-01T06:38:38.719278 | {
"authors": [
"DavidWangW",
"agnosticdev",
"lnicco",
"siyengar",
"udippant"
],
"repo": "facebookincubator/mvfst",
"url": "https://github.com/facebookincubator/mvfst/issues/11",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
2693312943 | Remove the BloomFilter classes from dwio/parquet/writer/arrow/tests/
Description
The classes were moved from Arrow Parquet writer to dwio/parquet/common in "Move arrow parquet bloom filter code to velox dwio (#10516)", but there is still another copy in velox/dwio/parquet/writer/arrow/tests/. The references in velox/dwio/parquet/writer/arrow/tests/ shall be updated to the ones in dwio/parquet/common
cc @pedroerp @nmahadevuni
| gharchive/issue | 2024-11-26T06:14:14 | 2025-04-01T06:38:38.724804 | {
"authors": [
"yingsu00"
],
"repo": "facebookincubator/velox",
"url": "https://github.com/facebookincubator/velox/issues/11661",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1701850022 | Update Types documentation
Update Decimal and Interval Day to Second type documentation since they
are now logical types.
Add documentation for Presto Types.
@mbasmanova I addressed your comments. Can you make another pass? Thanks.
I added a note for OPAQUE and UNKNOWN types as well.
@mbasmanova thank you for your feedback. I addressed all of them.
| gharchive/pull-request | 2023-05-09T10:55:59 | 2025-04-01T06:38:38.726544 | {
"authors": [
"majetideepak"
],
"repo": "facebookincubator/velox",
"url": "https://github.com/facebookincubator/velox/pull/4875",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1952168490 | Add ContainerRowSerde::compareWithNulls API for ByteStream compare
Presto aggregate functions that compare values of complex types must detect
cases when complex values contain nulls. The new
ContainerRowSerde::compareWithNulls API allows signaling the case when a complex
type value contains a null when comparing ByteStream with ByteStream.
Similar to https://github.com/facebookincubator/velox/pull/6419.
I'm getting Diff too old error. Would you rebase?
I'm getting Diff too old error. Would you rebase?
@mbasmanova Got it, done.
@duanmeng Thanks.
| gharchive/pull-request | 2023-10-19T12:43:03 | 2025-04-01T06:38:38.728957 | {
"authors": [
"duanmeng",
"mbasmanova"
],
"repo": "facebookincubator/velox",
"url": "https://github.com/facebookincubator/velox/pull/7138",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
691903308 | Train models config directory path
Shouldn't the model config path in the configs table in the README.md Training models section contain model_configs directory as shown below?
Model
Config directory
ANS(rgb)
configs/model_configs/ans_rgb
ANS(depth)
configs/model_configs/ans_depth
OccAnt(rgb)
configs/model_configs/occant_rgb
OccAnt(depth)
configs/model_configs/occant_depth
OccAnt(rgbd)
configs/model_configs/occant_rgbd
OccAnt(GT)
configs/model_configs/occant_ground_truth
The pre-models that are available do not obey this directory structure. The above was just an indication pointing to sample config files for each model. In each case, the paths for the following must be changed based on the user's needs:
TENSORBOARD_DIR
EVAL_CKPT_PATH_DIR
VIDEO_DIR
CHECKPOINT_FOLDER
Got it.
In my humble opinion, it's a bit confusing because we have the configs directory in the project root.
And I initially thought that the path is specified relative to the configs directory.
Maybe it would be better to add some explanation and angle brackets around config like this
Model
Config directory
ANS(rgb)
<configs>/ans_rgb
ANS(depth)
<configs>/ans_depth
OccAnt(rgb)
<configs>/occant_rgb
OccAnt(depth)
<configs>/occant_depth
OccAnt(rgbd)
<configs>/occant_rgbd
OccAnt(GT)
<configs>/occant_ground_truth
where <config> is an indication pointing to sample config files for each model.
All paths in the repo are relative the main directory. So, the paths specified are valid paths for example config files. Is it an issue with the pre-trained models?
No no, I just got confused, because the paths specified in the Config directory column don't exist.
For example, there is a configs directory in the project root, but the path configs/ans_rgb doesn't exist (but the path configs/model_configs/ans_rgb does exist).
That's why I suggested either change it to the correct path or to add an explanation that the config is an indication pointing to sample config files for each model.
Oh, got it. The model_configs was missing. Yes, I will fix this in my next update. Thanks!
| gharchive/issue | 2020-09-03T11:52:51 | 2025-04-01T06:38:38.804923 | {
"authors": [
"rpartsey",
"srama2512"
],
"repo": "facebookresearch/OccupancyAnticipation",
"url": "https://github.com/facebookresearch/OccupancyAnticipation/issues/2",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
476053815 | Where is fairseq-preprocess
When I run following command in the shell script
for input_index in $(seq 1 2); do
fairseq-preprocess \
--only-source \
--trainpref $processed_data_dir/train.${input_index}.bpe \
--validpref $processed_data_dir/dev.${input_index}.bpe \
--testpref $processed_data_dir/test.${input_index}.bpe \
--destdir $processed_data_dir/Input.${input_index} \
--workers 4 \
--srcdict ${roberta_vocab_dir}/dict.txt
done
There is an issue that command not found
fairseq-preprocess: command not found
You need to run “pip install --editable .” to install the fairseq-preprocess executable.
sorry, from which directory shall I run “pip install --editable .” ?
You need to run “pip install --editable .” to install the fairseq-preprocess executable.
@myleott
Even after running this and having fairseq successfully installed the fairseq-preprocess is not found
@Skylixia Were you able to fix this?
| gharchive/issue | 2019-08-02T08:11:45 | 2025-04-01T06:38:38.846291 | {
"authors": [
"Skylixia",
"chengfx",
"myleott",
"nonononanana",
"yarakhater"
],
"repo": "facebookresearch/fairseq",
"url": "https://github.com/facebookresearch/fairseq/issues/955",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
666534732 | accessing build/viewer
❓ Questions and Help
How does one access build/viewer code? It does not seem to be on GitHub.
Just pass -DBUILD_GUI_VIEWERS=ON to CMake.
Forgive me, but how is CMake involved? I know it it a dependency, but I have installed it without specifically in invoking it.
How does one access build/viewer code
Is this what you are looking for: https://github.com/facebookresearch/habitat-sim/blob/master/src/utils/viewer/viewer.cpp?
How to build this viewer as it is already not there in build folder?
You'll need to build habitat-sim for a system with display as described here: https://github.com/facebookresearch/habitat-sim/blob/master/BUILD_FROM_SOURCE.md (i.e., do not include the --headless argument).
Hii @aclegg3 thank you for response , I installed habitat-sim using the same .But, still got error as :
./build/viewer no such file or directory exists.
@KenaHemnani then we'll need more info from your build before we can move forward. You should see an alias to viewer in the habitat-sim/build directory and a habitat-sim/utils/viewer/ directory containing the viewer application.
Hii @aclegg3 I reinstalled habitat-sim using conda . The headless version is working fine , but with display I am not able to visualize even with VNC , Yes I do have habitat-viewer inside habitat-sim/utils/viewer/ directory .So, I run following command
./habitat-viewer ~/DIR/habitat-lab/data/scene_datasets/hitat-test-scenes/skokloster-castle.glb
It shows following `error:
Is there any other way to visualize the performance of agents as how it is navigating inside 3D habitat environment? locally on small dataset.
`
| gharchive/issue | 2020-07-27T19:35:08 | 2025-04-01T06:38:38.902157 | {
"authors": [
"KenaHemnani",
"Skylion007",
"VladislavHrosinkov",
"aclegg3",
"erikwijmans"
],
"repo": "facebookresearch/habitat-sim",
"url": "https://github.com/facebookresearch/habitat-sim/issues/703",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2483681211 | --[BE][WIP] - Dataset Diagnostics and Attributes Deduplication
Motivation and Context
This PR introduces a transparent dataset diagnostics protocol that can be controlled by setting flags using the optional tag "request_diagnostics" placed in the scene dataset config, followed by either an individual string or a list of strings, each specifying a desired diagnostic to be performed.
As a proof of concept, as well as to address an existing issue with the base hssd scene instances, the following tags are currently supported :
SaveCorrected : save any files that have been tested and corrected. Ignored if no tests specified
TestForSceneInstanceDuplicates : test for duplicate rigid/articulated object instances on scene instance load, not loading duplicates if found.
TestForSemanticRegionDuplicates : test for duplicate semantic region definitions on semantic attributes load, not loading duplicates if found.
This PR will perform conditional de-duplication of any loaded subconfiguration, such as Object Instances from the Scene Instance configuration file, if the appropriate test (TestForSceneInstanceDuplicates) is requested. If multiple such object instances are loaded that have identical data, then the extra duplicates will not be saved as part of the internal representation of the scene instance.
If SaveCorrected is specified, the scene instance, in this case, minus the extra duplicates, will be saved to disk. Otherwise, it will just be retained in memory for the lifetime of the execution.
This functionality is also available for SemanticAttributes/configs, should identical SemanticRegion definitions exist within the original json config description.
This PR is currently set up to prevent any duplicate SceneObjectInstanceAttributes or SceneAOInstanceAttributes from being saved when a SceneInstanceAttributes is being created for manual save to disk.
This PR also includes a renaming refactor for attributes and attributes manager base classes to fall in line with standard naming protocol and be less confusing.
Still needed :
Actually saving the modified attributes if the diagnostics indicate it and the user requested saving.
Tests
How Has This Been Tested
Locally c++ and python tests pass (currently transparent pass-through)
Types of changes
[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.
So currently to request a diagnostic, say on duplicate scene object instances, you would add the following line to the scene dataset config :
"request_diagnostics":"TestForSceneInstanceDuplicates",
or
"request_diagnostics":["TestForSceneInstanceDuplicates"],
if you wanted to save the scene instances that were corrected by the diagnostic process, you would use
"request_diagnostics":["TestForSceneInstanceDuplicates", "SaveCorrected"],
and when you do not wish for any diagnostics anymore, you would just delete the line from the scene dataset config.
Other mechanisms for performing these diagnostics would be easy to implement, this was just the mechanism I started with.
| gharchive/pull-request | 2024-08-23T18:43:15 | 2025-04-01T06:38:38.911964 | {
"authors": [
"jturner65"
],
"repo": "facebookresearch/habitat-sim",
"url": "https://github.com/facebookresearch/habitat-sim/pull/2457",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2453359549 | Problems opening GUI
Does anyone know how to open gui for the ovmm?
Hey this is the script for GUI: https://github.com/facebookresearch/habitat-lab/blob/ovmm_v0.2.5/examples/interactive_play.py.
| gharchive/issue | 2024-08-07T12:26:34 | 2025-04-01T06:38:38.913617 | {
"authors": [
"RanDing2000",
"yvsriram"
],
"repo": "facebookresearch/home-robot",
"url": "https://github.com/facebookresearch/home-robot/issues/514",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
376217113 | Reduce the training loss
❓ Questions and Help
Is it necessary to reduce the training losses through multiple processes in trainer.py?
I think current reduction on losses only work for logging instead of backward.
Could anyone explain about which parts of codes average the gradients from all processes when doing distributed training?
The reduction in the losses is indeed only needed for logging purposes, and not for training.
The gradient averaging is handled by DistributedDataParallel, and is done automatically for us when we call .backward.
I'm closing this issue as I believe I have answered your question, but let me know if something isn't clear.
| gharchive/issue | 2018-11-01T01:16:26 | 2025-04-01T06:38:38.922673 | {
"authors": [
"Jiayuan-Gu",
"fmassa"
],
"repo": "facebookresearch/maskrcnn-benchmark",
"url": "https://github.com/facebookresearch/maskrcnn-benchmark/issues/84",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
384618269 | Where is envs buffers?
I encounter a problem when trying to find the JSON files of all the visdom envs.
First of all, I can not find where the visdom server save all the envs buffer path. I use buffer path" referring to the path where all the unsaved envs are kept. This buffer seems to be automatically cleared when the visdom server is shut down. However I need to find and use it when the server is still on.
Its path is definitely not "~/.visdom", and I would like to know where it is
The other thing is that I need to save some of the good envs and reload them freely. So far, the save button can save the envs file to "~/.visdom", but I can not find anyway to use these JSON files other than simply reboot the server.
How can I use another server (That say new IP new port) to load all the JSON file I pick(I would get the file from save button and move them elsewhere) from any path I set?
This 'buffer' is entirely in the server's python local memory in self.state[eid], it doesn't exist as a file. Hard saves are the only thing that push data to a file.
For the latter question you can move the files to a different folder and start the server with the -env_path <directory> option to point to that folder.
@JackUrb Thanks~ This is what we are doing now. ^_^
| gharchive/issue | 2018-11-27T04:33:13 | 2025-04-01T06:38:38.925780 | {
"authors": [
"JackUrb",
"luzhilin19951120"
],
"repo": "facebookresearch/visdom",
"url": "https://github.com/facebookresearch/visdom/issues/514",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
998771139 | Even better upgrades to playground
Allow loading notebook pages
Add spinner to show pyodide is loading and/or working
@gir-bot lgtm
| gharchive/pull-request | 2021-09-16T23:43:00 | 2025-04-01T06:38:38.937084 | {
"authors": [
"facelessuser"
],
"repo": "facelessuser/coloraide",
"url": "https://github.com/facelessuser/coloraide/pull/70",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1040430077 | 🛑 fiscaliadeestado.misiones.gob.ar is down
In 6fc729e, fiscaliadeestado.misiones.gob.ar (https://fiscaliadeestado.misiones.gob.ar/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: fiscaliadeestado.misiones.gob.ar is back up in 3751ec0.
| gharchive/issue | 2021-10-31T10:18:23 | 2025-04-01T06:38:38.952712 | {
"authors": [
"facundomdu"
],
"repo": "facundomdu/mdu-github-glb-monitor-01",
"url": "https://github.com/facundomdu/mdu-github-glb-monitor-01/issues/419",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1051612966 | 🛑 htc.misiones.gob.ar is down
In 83a7531, htc.misiones.gob.ar (https://htc.misiones.gob.ar/) was down:
HTTP code: 0
Response time: 0 ms
Resolved: htc.misiones.gob.ar is back up in 4bd7cdc.
| gharchive/issue | 2021-11-12T05:59:35 | 2025-04-01T06:38:38.955826 | {
"authors": [
"facundomdu"
],
"repo": "facundomdu/mdu-github-glb-monitor-01",
"url": "https://github.com/facundomdu/mdu-github-glb-monitor-01/issues/618",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2181362222 | test: update tests for wasmhooks
Notes
update simapp and tests to be compatible with sdk 50, and make all tests pass
Tests pass
@faddat hey, i'm implementing ibc-hooks for eve, and since there is no completed version of ibc-hooks v8, i will continue working on your branch
@faddat hi sir, tests and lint passed, please review this PR
thank you!
| gharchive/pull-request | 2024-03-12T11:17:54 | 2025-04-01T06:38:38.957739 | {
"authors": [
"faddat",
"kienn6034"
],
"repo": "faddat/ibc-apps",
"url": "https://github.com/faddat/ibc-apps/pull/1",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
701821135 | Add authorization token to be allowed to access the backend
Change endPoint to Access to platform backend to get dynamic projects list
Proposed Changes
Add endPiont to evirioment
Add header to include valid token to access
Get project list from server
Pull request checklist
Please check if your PR fulfills the following requirements:
[ ] Tests
[x] Build locally
[ ] Code format / lint
[ ] Docs have been reviewed and added
Pull request type
Please check the type of change your PR introduces:
[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):
What is the current behavior?
Issue Number: N/A
The sistem access to backend to get the list of project available using a valid token
Fixes #81
What is the new behavior?
Does this introduce a breaking change?
[ ] Yes
[x] No
Other information
Be careful with the blank spaces in the checkbox of the PR. Try to put labels, use the issue in the Kanban project and assign the PR to someone
| gharchive/pull-request | 2020-09-15T10:45:16 | 2025-04-01T06:38:38.981550 | {
"authors": [
"carloscaverobarca",
"miquinti"
],
"repo": "fair4health/f4h-portal-ui",
"url": "https://github.com/fair4health/f4h-portal-ui/pull/83",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1326344540 | Issues while fetching data, latest and previous fdp-storage versions
When I'm fetching / downloading
// read directory
const items = await this.fdp.directory.read(
TODOS_NAMESPACE,
`/${TODOS_PATH}`
);
// only add new todos
for (const i in items.content) {
if (!this.todos.find((t) => t.id === i.split(`.`)[1])) {
const data = await this.fdp.file.downloadData(
TODOS_NAMESPACE,
`/${TODOS_PATH}/${(i as any).name}`
);
// fails with "Data not found"
const payload = new TextDecoder().decode(data.buffer);
const obj = JSON.parse(payload);
this.todos.push(obj);
}
}
I get the following error in Chrome
vue.runtime.esm.js?c320:3020 Error: Data not found
at t.lookup (index.browser.min.js?fb75:2:1)
at async t.getRawMetadata (index.browser.min.js?fb75:2:1)
at async s (index.browser.min.js?fb75:2:1)
at async t.downloadData (index.browser.min.js?fb75:2:1)
at async VueComponent.loadItems (App.vue?38a5:107:1)
This is in the supertodos repository
developers should use async/await
| gharchive/issue | 2022-08-02T20:04:59 | 2025-04-01T06:38:38.983334 | {
"authors": [
"molekilla",
"tfius"
],
"repo": "fairDataSociety/fdp-storage",
"url": "https://github.com/fairDataSociety/fdp-storage/issues/104",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
608293669 | [sway systemd setup] unable to re-login after exiting sway
Hello,
thank you for making this beautiful display manager!
OS: manjaro with latest linux55 kernel
$ sway --version
sway version 1.4
wlroots version 0.10.1-1
ly version: installed via yay -S ly-git v0.5.0.r9.gaa25ede-1
When trying to logout and then re-login with sway I see the following errors:
Click to expand!
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: unable to locate daemon control file
Apr 28 14:53:59 teutates-laptop audit[657]: USER_AUTH pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:authentication grantors=pam_securetty,pam_tally2,p>
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: stashed password to try later in open session
Apr 28 14:53:59 teutates-laptop audit[657]: USER_ACCT pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:accounting grantors=pam_tally2,pam_access,pam_unix>
Apr 28 14:53:59 teutates-laptop audit[657]: CRED_ACQ pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shell>
Apr 28 14:53:59 teutates-laptop ly[657]: pam_unix(ly:session): session opened for user teutates by (uid=0)
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: unable to locate daemon control file
Apr 28 14:53:59 teutates-laptop ly[657]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring
Apr 28 14:53:59 teutates-laptop audit[657]: USER_START pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:session_open grantors=pam_loginuid,pam_keyinit,pa>
Apr 28 14:53:59 teutates-laptop systemd[1037]: Started sway - SirCmpwn's Wayland window manager.
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] Linux teutates-laptop 5.5.19-1-MANJARO #1 SMP PREEMPT Tue>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:168] Contents of /etc/lsb-release:
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_ID=ManjaroLinux
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_RELEASE=20.0
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_CODENAME=Lysia
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] DISTRIB_DESCRIPTION="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:168] Contents of /etc/os-release:
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] NAME="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ID=manjaro
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ID_LIKE=arch
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] PRETTY_NAME="Manjaro Linux"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] ANSI_COLOR="1;32"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] HOME_URL="https://www.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] SUPPORT_URL="https://www.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] BUG_REPORT_URL="https://bugs.manjaro.org/"
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:152] LOGO=manjarolinux
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] LD_LIBRARY_PATH=(null)
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] LD_PRELOAD=(null)
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] PATH=/home/teutates/.local/bin:/sbin:/bin:/usr/local/sbin:/us>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/main.c:140] SWAYSOCK=/run/user/1000/sway-ipc.1000.1062.sock
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/server.c:40] Preparing Wayland server initialization
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/wayland/backend.c:255] Creating wayland backend
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/wayland/backend.c:271] Could not connect to remote display: No such fi>
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [backend/noop/backend.c:51] Creating noop backend
Apr 28 14:53:59 teutates-laptop sway[63955]: 2020-04-28 14:53:59 - [sway/server.c:47] Unable to create backend
Apr 28 14:53:59 teutates-laptop systemd[1037]: sway.service: Main process exited, code=exited, status=1/FAILURE
Apr 28 14:53:59 teutates-laptop systemd[1037]: sway.service: Failed with result 'exit-code'.
Apr 28 14:53:59 teutates-laptop ly[657]: pam_unix(ly:session): session closed for user teutates
Apr 28 14:53:59 teutates-laptop audit[657]: USER_END pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:session_close grantors=pam_loginuid,pam_keyinit,pam>
Apr 28 14:53:59 teutates-laptop audit[657]: CRED_DISP pid=657 uid=0 auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_securetty,pam_tally2,pam_shel
Steps to reproduce:
I have setup sway to start with systemd as described in the sway wiki (follow the whole page, also setup sway itself as a --user service)
setup ly as a systemd service as well
exit sway with swaymsg exit
get logged out and redirected correctly to ly
try to login again: ly seems to refresh itself and does not open sway. in the logs the mentioned error messsages show up
Expected:
ly should start a new sway session successfully.
I am very curious if this is reproducable for others and would be happy to provide more debugging info as needed.
I cannot reproduce with Sway 1.5 on Arch Linux, but I'm not running Sway as a systemd service.
Consider trying the sway-services project instead, available as sway-services-git package in the Arch Linux AUR.
One thing it does is to clean up some environment variables set by Sway upon exit. Perhaps if these are not unset it could cause a problem upon re-login:
https://github.com/xdbob/sway-services/blob/master/bin/sway-user-service
You see the sway.service file also contains code to clean-up environment vars:
https://github.com/xdbob/sway-services/blob/5ccb33b92c78a0b95216b3c3470d0d45e76cea2c/systemd/sway.service
Consider trying the sway-services project instead, available as sway-services-git package in the Arch Linux AUR.
One thing it does is to clean up some environment variables set by Sway upon exit. Perhaps if these are not unset it could cause a problem upon re-login:
https://github.com/xdbob/sway-services/blob/master/bin/sway-user-service
You see the sway.service file also contains code to clean-up environment vars:
https://github.com/xdbob/sway-services/blob/5ccb33b92c78a0b95216b3c3470d0d45e76cea2c/systemd/sway.service
Thank you @markstos, I'll definitely check that out and report back how it goes.
Thank you @markstos, I'll definitely check that out and report back how it goes.
Nice! This little detail in sway.service does the trick:
https://github.com/xdbob/sway-services/blob/eab69fa5253ad494921833e46b6476d7bf675ed4/systemd/sway.service#L19
ExecStopPost=/usr/bin/systemctl --user unset-environment SWAYSOCK DISPLAY I3SOCK WAYLAND_DISPLAY
Nice! This little detail in sway.service does the trick:
https://github.com/xdbob/sway-services/blob/eab69fa5253ad494921833e46b6476d7bf675ed4/systemd/sway.service#L19
ExecStopPost=/usr/bin/systemctl --user unset-environment SWAYSOCK DISPLAY I3SOCK WAYLAND_DISPLAY
There seems to be an similiar issue with River WM
| gharchive/issue | 2020-04-28T12:53:29 | 2025-04-01T06:38:39.012707 | {
"authors": [
"kardwen",
"markstos",
"teutat3s"
],
"repo": "fairyglade/ly",
"url": "https://github.com/fairyglade/ly/issues/205",
"license": "WTFPL",
"license_type": "permissive",
"license_source": "github-api"
} |
1087517040 | fal installation instructions with dbt 1.0
Trying fal now after a recommendation through Slack. I installed dbt 1.0 by pip install dbt-core, as well as fal by pip install fal.
I ran into a few snags when installing fal in a clean python 3.9 environment, and it might be worth adding a note about dbt 1.0 to the fal readme.
fal currently doesn't install dbt. I assume this is because of the change from dbt to dbt-core.
fal relies on bigquery here, which means that one needs to run pip install dbt-bigquery. This should be explicitly stated on the readme, and preferably not be a requirement.
For the second point, it would be much better to use:
from dbt.adapters.factory import load_plugin
load_plugin("bigquery") # returns dbt.adapters.bigquery.connections.BigQueryCredentials
Hi @thomasaarholt! Thanks for raising this issue. We are actively working on supporting dbt 1.0 (see #69) and should release the new version soon. You're right, we should add a note about dbt 1.0 in README.
Ah! I searched for 1.0 and didn't find the PR (I had to type 1.0.0...) :)
My bigquery fix above works on 0.20 as well, I just checked:
Should I make a PR?
Ah, I see you have a fix as well in the 1.0.0 PR :) I'll leave that to you!
@thomasaarholt, we have just released a version compatible with dbt 1.0.0.
pip install fal==0.1.35
Please let us know how it goes and if anything else comes up!
| gharchive/issue | 2021-12-23T09:07:19 | 2025-04-01T06:38:39.025608 | {
"authors": [
"chamini2",
"mkam039",
"thomasaarholt"
],
"repo": "fal-ai/fal",
"url": "https://github.com/fal-ai/fal/issues/87",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1222871186 | Driverkit Debian/Ubuntu builder wrong kernel version
Describe the bug
Basically, kernel-crawler kernels list is exporting fields like:
"kernelrelease": "5.10.103-1-amd64",
(https://github.com/falcosecurity/kernel-crawler/blob/main/kernels/x86_64/list.json#L7368),
whose url is http://security.debian.org/pool/updates/main/l/linux/linux-headers-5.10.0-12-amd64_5.10.103-1_amd64.deb
But Driverkit is reading those as 5.10.0-12 kernelversion instead, using a regex that expects:
href="(linux-headers-5\.10\.103-1-(amd64)_.*(amd64|all)\.deb)"
This means that running driverkit with:
driverkit docker --output-module /tmp/falco.ko --kernelversion=1 --kernelrelease=5.10.103-1-amd64 --target=debian
will fail, because it expects 5.10.0-12 kernelrelease.
Fact is, kernel-crawler is right because it is using packages metadata, eg (notice the Version line):
Package: linux-headers-5.10.0-12-common
Source: linux
Version: 5.10.103-1
Installed-Size: 51854
Maintainer: Debian Kernel Team <debian-kernel@lists.debian.org>
Architecture: all
Description: Common header files for Linux 5.10.0-12
Homepage: https://www.kernel.org/
Description-md5: ab592fb1c299fa53a862c8eecd4486e6
Multi-Arch: foreign
Section: kernel
Priority: optional
Filename: pool/updates/main/l/linux/linux-headers-5.10.0-12-common_5.10.103-1_all.deb
Size: 8940952
SHA256: 9753625d0256066b37dd92d55621ebb5a76c3a9e6c2579607531b0809f6b3552
Of course, changing the way driverkit behaves would break every existing config.
I am not sure whether "breaking" kernel-crawler to match driverkit output would be a good idea.
I can try to add a new parameter to driverkit configs header_urls[], that when set, would force certain headers instead of trying to fetch the correct one programmatically.
Moreover, i could even try to double the matching pattern, trying the current driverkit before, and if it fails, fallbacking at trying the new pattern.
What would you think?
Do you have any idea?
/cc @zuc @maxgio92
Proposed PR for arm support (https://github.com/falcosecurity/driverkit/pull/143) address this issue using both evaluated options:
adds a kernelurls param
doubled the matching pattern
| gharchive/issue | 2022-05-02T13:12:17 | 2025-04-01T06:38:39.039074 | {
"authors": [
"FedeDP"
],
"repo": "falcosecurity/driverkit",
"url": "https://github.com/falcosecurity/driverkit/issues/142",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
732190830 | update(data/en): correct and update gRPC config description
What type of PR is this?
/kind bug
/kind cleanup
/kind content
Any specific area of the project related to this PR?
/area documentation
What this PR does / why we need it:
Which issue(s) this PR fixes:
The gRPC config description was not updated w.r.t the unix socket binding type.
Fixes #
Special notes for your reviewer:
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leogr
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
LGTM label has been added. Git tree hash: 332d7cb66b9919b5415f0854bc947fbf6b345fe8
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS [fntlnz]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
| gharchive/pull-request | 2020-10-29T10:27:32 | 2025-04-01T06:38:39.047554 | {
"authors": [
"leogr",
"poiana"
],
"repo": "falcosecurity/falco-website",
"url": "https://github.com/falcosecurity/falco-website/pull/307",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1800591408 | wip: new(rules): add rule for detecting fileless execution via memfd_create
What type of PR is this?
Uncomment one (or more) /kind <> lines:
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
Any specific area of the project related to this PR?
Uncomment one (or more) /area <> lines:
/area rules
/area registry
/area build
/area documentation
What this PR does / why we need it:
This PR takes advantage of a new incoming Falco feature for detecting fileless execution via memfd_create. This is a very well known defense evasion technique that threat actors might use to execute malware on victim machines. It has been used in the past, but also pretty recently as reported by these two articles:
https://cybersecurity.att.com/blogs/labs-research/malware-using-new-ezuri-memory-loader
https://www.wiz.io/blog/pyloose-first-python-based-fileless-attack-on-cloud-workloads
Putting this on wip until the feature lands in Falco.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: loresuso
Once this PR has been reviewed and has the lgtm label, please assign andreagit97 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
OWNERS
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@loresuso we can soon start with merging rules that make the rules file incompatible with the current Falco as the next release is planned for end of Sep.
After merging this rule at maturity_incubating we can bump to maturity_stable in a follow up PR. That way we honor our new guidelines. CC @darryk10 @leogr
After merging this rule at maturity_incubating we can bump to maturity_stable in a follow up PR. That way we honor our new guidelines. CC @darryk10 @leogr
:+1:
Rules files have been split. @loresuso could you rebase this PR and address the above suggestions, please? :pray:
IMO it makes sense to uniformly bump the engine version. In this way, when we graduate rules, we don't need to bother or remember how the version should be bumped, and just move the rule between files, but I'm open to discuss!
/hold
We need to bump the required engine version. @leogr @LucaGuerra do we bump the rules engine uniformly in all rules files? I would vote for that!
What's the benefit of having the same required_engine_version?
The only two consequences I see
We will have to bump the minor version in all rules files https://github.com/falcosecurity/rules/blob/main/RELEASE.md#versioning-a-ruleset
We will make all files not compatible with a previous Falco engine (even if they are)
Moreover, the CI should already be able to check (and inform us) when an engine version bump is required. Indeed, this jobs matrix indicates that falco-incubating_rules.yaml is no longer compatible with 0.35.0 because the missing field
In the end, I don't have a strong opinion and am open to any solution. I just don't see the benefit of doing this (perhaps am I missing something? :thinking: )
In case we decide to bump all files, I still would avoid bumping falco-deprecated_rules.yaml, since it does not make much sense to me.
@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?
@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?
The required_engine_version applies at the single file level only (@jasondellaluce correct me if I'm wrong). It acts as a validation condition when loading the rules files, so it won't be overridden by other rules files. Basically, files will be validated one by one, the first failure will stop the whole process, regardless of the loading order.
@leogr will the required engine version be overriden in the order the rules files are loaded? If we don't bump in all files, we at least should make sure the highest required version in any files has the final say?
The required_engine_version applies at the single file level only (@jasondellaluce correct me if I'm wrong). It acts as a validation condition when loading the rules files, so it won't be overridden by other rules files. Basically, files will be validated one by one, the first failure will stop the whole process, regardless of the loading order.
ok then let's just bump it in the respective file for now, thanks!
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: incertum, loresuso
The full list of commands accepted by this bot can be found here.
The pull request process is described here
Needs approval from an approver in each of these files:
OWNERS [incertum]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
LGTM label has been added. Git tree hash: 01650113bdbe0bb5383a3ee06151604fd4526b6b
/unhold
| gharchive/pull-request | 2023-07-12T09:43:26 | 2025-04-01T06:38:39.068513 | {
"authors": [
"incertum",
"leogr",
"loresuso",
"poiana"
],
"repo": "falcosecurity/rules",
"url": "https://github.com/falcosecurity/rules/pull/98",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
258211317 | 您要的产品目前在中国商店不提供
下载不了，可以提供一个dmg安装包吗
这个软件现在有些小问题，作者还没修改！下了也登录不上！等作者修改吧！
@Noah1991 后续会上架，最近太忙了
#179
| gharchive/issue | 2017-09-16T06:03:04 | 2025-04-01T06:38:39.106641 | {
"authors": [
"Noah1991",
"fancymax",
"joenil"
],
"repo": "fancymax/12306ForMac",
"url": "https://github.com/fancymax/12306ForMac/issues/178",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
2093236603 | Nerd font and color scheme used for mac-os preview ?
@fang2hou Thanks for the preset, it looks amazing 🌟
Just one more thing, if you wouldn't mind could you please also share the nerd font and terminal color scheme used in the Mac-OS preview ? as it looks the best among all the previews
I am using alacritty now.
The font is JetBrainsMono Nerd Font, you can download it from here.
My alacrity TOML
[colors.bright]
black = "#4b4b4b"
blue = "#9ac2bb"
cyan = "#aedea0"
green = "#c8c847"
magenta = "#eaa4b7"
red = "#ff5f4f"
white = "#ffffff"
yellow = "#ffc24b"
[colors.normal]
black = "#282828"
blue = "#80aa9e"
cyan = "#8bba7f"
green = "#b0b846"
magenta = "#d3869b"
red = "#f2594b"
white = "#e2cca9"
yellow = "#e9b143"
[colors.primary]
background = "#282828"
foreground = "#e2cca9"
[font]
size = 15.0
[font.bold]
family = "JetBrainsMono Nerd Font"
style = "Bold"
[font.bold_italic]
family = "JetBrainsMono Nerd Font"
style = "Bold Italic"
[font.italic]
family = "JetBrainsMono Nerd Font"
style = "Italic"
[font.normal]
family = "JetBrainsMono Nerd Font"
style = "Light"
[font.offset]
x = 0
y = 1
[window]
decorations = "full"
dynamic_padding = false
option_as_alt = "OnlyLeft"
resize_increments = true
[window.dimensions]
columns = 180
lines = 35
[window.padding]
x = 12
y = 12
Thank you for sharing the color scheme. I figured it out, I was using a regular styled mono version of the JetBrains Mono font, after changing to a non-mono medium styled version it looks similar
| gharchive/issue | 2024-01-22T07:08:45 | 2025-04-01T06:38:39.109849 | {
"authors": [
"VPraharsha03",
"fang2hou"
],
"repo": "fang2hou/starship-gruvbox-rainbow",
"url": "https://github.com/fang2hou/starship-gruvbox-rainbow/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1486016795 | feat: support nft urls in reactions and replies
What is the feature you would like to implement?
Allow reactions and cast-replies to point to an NFT as their parent. We will eventually want to expand this to work for generic web URLs as well, though that can be cut if it adds a lot of complexity.
Why is this feature important?
Merkle supports NFT likes in a centralized manner, and NFT comments is one of the most requested features from users. If the protocol doesn't support it, clients will continue doing it in a centralized manner. Doing it in a decentralized way, makes this data more portable and available to other clients.
Will the protocol spec need to be updated??
Yes, we'll need to change the specification for the message fields for cast parents and reaction targets.
How should this feature be built? (optional)
TBD
Closing in favor of existing ticket https://github.com/farcasterxyz/hub/issues/231
| gharchive/issue | 2022-12-09T05:13:52 | 2025-04-01T06:38:39.147187 | {
"authors": [
"pfletcherhill",
"varunsrin"
],
"repo": "farcasterxyz/hub",
"url": "https://github.com/farcasterxyz/hub/issues/280",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2099235591 | Month, Year select
Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch react-native-ui-datepicker@1.0.11 for the project I'm working on.
Here is the diff that solved my problem:
diff --git a/node_modules/react-native-ui-datepicker/src/DateTimePicker.tsx b/node_modules/react-native-ui-datepicker/src/DateTimePicker.tsx
index 5a55cf2..3958bdd 100644
--- a/node_modules/react-native-ui-datepicker/src/DateTimePicker.tsx
+++ b/node_modules/react-native-ui-datepicker/src/DateTimePicker.tsx
@@ -137,7 +137,7 @@ const DateTimePicker = ({
useEffect(() => {
dispatch({
type: CalendarActionKind.SET_CALENDAR_VIEW,
- payload: mode === 'time' ? CalendarViews.time : CalendarViews.day,
+ payload: mode === 'time' ? CalendarViews.time : mode === 'year' ? CalendarViews.year : mode ==='month' ? CalendarViews.month : CalendarViews.day ,
});
}, [mode]);
diff --git a/node_modules/react-native-ui-datepicker/src/types.ts b/node_modules/react-native-ui-datepicker/src/types.ts
index 7783b3f..4229093 100644
--- a/node_modules/react-native-ui-datepicker/src/types.ts
+++ b/node_modules/react-native-ui-datepicker/src/types.ts
@@ -5,7 +5,7 @@ import type { ReactNode } from 'react';
export type DateType = string | number | Dayjs | Date | null | undefined;
-export type CalendarModes = 'datetime' | 'date' | 'time';
+export type CalendarModes = 'datetime' | 'date' | 'time' | 'month' | 'year';
export type HeaderButtonPositions = 'around' | 'right' | 'left';
This issue body was partially generated by patch-package.
this is fixed in this commit 653daa8
| gharchive/issue | 2024-01-24T22:41:48 | 2025-04-01T06:38:39.150318 | {
"authors": [
"farhoudshapouran",
"spaske1991"
],
"repo": "farhoudshapouran/react-native-ui-datepicker",
"url": "https://github.com/farhoudshapouran/react-native-ui-datepicker/issues/52",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
268343123 | Fixed and extended Dead ReLU detector callback
Initially 'DeadReLUDetectorCallback was only working for Dense layers and the percentage of dead relu neurons was incorrect.
Corrected the percentage calculations
Extended for all layers with a ReLU activation (tested for conv2d and dense)
Tested on python 3.5 TF and Theano
For testing I had 1 fail, however I'm quite certain it is independent of my additions.
`self = <backend_test.TestBackend object at 0x7f4f68019470>
def test_moments(self):
input_shape = (10, 10, 10, 10)
x_0 = np.zeros(input_shape)
x_1 = np.ones(input_shape)
x_random = np.random.random(input_shape)
th_axes = [0, 2, 3]
tf_axes = [0, 1, 2]
for ip in [x_0, x_1, x_random]:
for axes in [th_axes, tf_axes]:
for keep_dims in [True, False]:
ip_th = KTH.variable(ip)
th_mean, th_var = KCTH.moments(ip_th, axes, keep_dims=keep_dims)
ip_tf = KTF.variable(ip)
tf_mean, tf_var = KCTF.moments(ip_tf, axes, keep_dims=keep_dims)
th_mean_val = KTH.eval(th_mean)
tf_mean_val = KTF.eval(tf_mean)
th_var_val = KTH.eval(th_var)
tf_var_val = KTF.eval(tf_var)
assert_allclose(th_mean_val, tf_mean_val, rtol=1e-4)
assert_allclose(th_var_val, tf_var_val, rtol=1e-4)
E AssertionError:
E Not equal to tolerance rtol=0.0001, atol=0
E
E (mismatch 100.0%)
E x: array([[[[ 0.]],
E
E [[ 0.]],...
E y: array([[[[ 6.938894e-18]],
E
E [[ 6.938894e-18]],...
If people need a return vallue/callback, the request will come naturally.
Now... My check failed multiple times. For a test that worked on my pc (both py2.7 Tensorflow and py3.5 Tensorflow) an never by the 'ravis CI build'. In the end I just commented that part of the test, but now it gives errors about an other package. I don't know what I can/should do about that
@infelane I took a look at the errors and it seems they aren't related to your changes. Does that seem correct to you?
@ahundt The errors that raised were indeed outside my additions. I checked the code that raised the error and might have found a bug overthere. Do you think the dead_relu_detector can be merged? Maybe reopen the backend_test?
LGTM, merging, thanks for the contribution! 👍
Congrats for getting it merged
| gharchive/pull-request | 2017-10-25T10:19:20 | 2025-04-01T06:38:39.156363 | {
"authors": [
"ahundt",
"arodiss",
"infelane"
],
"repo": "farizrahman4u/keras-contrib",
"url": "https://github.com/farizrahman4u/keras-contrib/pull/174",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
440280792 | Notes
1
For an @-subcard during a local quiz, the prompt sentence will be shown but with a piece of it replaced with the @-subprompt. In order to know which piece of the prompt sentence to hide, the @-subcard's pieces will be examined for cloze marks.
if no cloze marks found, look for the prompt, and if that fails, look for the responses, and if that fails, throw.
if cloze marks found in one item (or more, though that's probably an error), hide that in the sentence.
We can have a "linter" that will warn when no clozes are present in @-subcard and the prompt/response chosen is repeated in the sentence. Also if more than one item has a cloze mark.
2
Two Ebisu models are associated each global card. One global one shared by all instances of it. And one local one personal to it and this sentence. When you do a global review (all by itself), the local ones all get an active update. When you do a local review (with a single sentence), the global get a passive update.
3
Exponential decay and SRS might optimize long-term just-about-to-forget, hard-to-recall recall, but what if you want to optimize rapid recall? You see kanji on the subway, and sure if you've been doing your SRS you'll likely eventually get the answer (with a probability given by Ebisu), but you'll have rolled past it. The only way to do that is regular exposure.
When you do a local review (with a single sentence), the global get a passive update, and all other local reviews get an active update.
| gharchive/issue | 2019-05-04T03:44:32 | 2025-04-01T06:38:39.172514 | {
"authors": [
"fasiha"
],
"repo": "fasiha/curtiz-japanese-nlp",
"url": "https://github.com/fasiha/curtiz-japanese-nlp/issues/1",
"license": "Unlicense",
"license_type": "permissive",
"license_source": "github-api"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.