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 |
|---|---|---|---|---|---|
101699433
|
Allow launching a repo directly from a URL
It would be nice if people could add a button to their repo that directly launches it with everware.
We should come up with a way to implement this.
maybe make repo_url an http GET parameter ?
e.g. http://everware.xyz?repo_url=https://github.com/everware/everware-dimuon-example
The form on the homepage could then simply make a GET request as well.
I've quickly put together a button we can use:
+:100: for a button in people's README that let's me launch their analysis!
What happens if we have to do a OAuth detour? Do the parameters surive?
Shouldn't be difficult to do. You can park them in a ?next= query parameter, let the authenticator do its business and send us to our desired destination.
Think I figured it out. Aside: we should use the state parameter to 'sign' our OAuth requests (and contribute that to @rgbkrk who we took the OAuth stuff from)
Modify OAuthLoginHandler.get() like so:
self.authorize_redirect(
redirect_uri=redirect_uri,
client_id=self.authenticator.client_id,
scope=[],
response_type='code',
extra_params={'state': self.create_signed_value('state', '141414')})
where 141414 is some value you check for in GitHubOAuthHandler with something like so:
state = self.get_argument('state', '')
assert '141414' == self.get_secure_cookie('state', state)
(right where it says "TODO: check if state argument needs checking" :grinning: )
Wondering if we even need to put something in there at all, but presumably it needs some kind of message to 'sign'. So we either put in some string like yayayay or the repo_url we are saving for later. I think the *OAuthHandler doesn't need to know what the message should be, we will know we made the request by the fact that we can decode the signed message. At least that is how I understand it.
I'll make a PR tomorrow morning.
First proposal in #15
The code from #15 got lost somehow, at least it isn't in the current master.
really? for example look at line 15 of everware/homelander.py
it is the line from the commit
+1 for launch button
fixed by #45.
the link should be like this:
http://babushk.in:8000/hub/oauth_login?repourl=https://github.com/betatim/everware-demo
|
gharchive/issue
| 2015-08-18T16:50:57 |
2025-04-01T04:34:12.333871
|
{
"authors": [
"anaderi",
"betatim",
"cranmer",
"ibab"
],
"repo": "everware/everware",
"url": "https://github.com/everware/everware/issues/10",
"license": "bsd-3-clause",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1265471518
|
Project name settings, ship components with template
Implements editing project title.
Rolls @evidence-dev/components into the template
Creates project name store as well as api for changing it
What do we expect companies to use this feature?
For example, if they were part of Acme Inc., would they call the project "Acme" or "Acme reports", or "Acme data" etc.
If I was making a personal project I'd know what to call it, eg Canada Covid 19 Dashboard. Or whatever the topic.
This also makes me think: should there be a character limit I'm on projectName to prevent overflow from Sidebar?
@archiewood -- "Acme, Inc." perhaps a team name, possibly an internal project name "Acme Data Portal" etc.
Philosophy is that teams should be able to brand their projects however they see fit.
Excel doesn't put Powered by Excel all over your model when you print it out 😆
Good point about sizing/ some sort of validation there.
I'd propose we close this for the moment, but I think we should revisit both the title feature, and the more substantial "ship components with the template" relatively soon, perhaps once we've made some more progress on the testing suite.
To make this work outside of the monorepo, I think that we'll need to sync the dependencies from the component library up into @evidence-dev/evidence, otherwise @evidence-dev/evidence will still need to import the components package.
|
gharchive/pull-request
| 2022-06-09T01:13:20 |
2025-04-01T04:34:12.344827
|
{
"authors": [
"archiewood",
"eleweek",
"mcrascal"
],
"repo": "evidence-dev/evidence",
"url": "https://github.com/evidence-dev/evidence/pull/308",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
488748335
|
'random mutagenesis evidence' vs. 'induced mutation evidence'
This issue stems from #174.
Hi @ivanerill and @pgaudet,
In reviewing the 'experimental phenotypic evidence' branch I have questions about a two similar terms that I am hoping you might be able to answer. The terms are 'random mutagenesis evidence' and 'induced mutation evidence'.
'random mutagenesis evidence':
A type of experimental phenotypic evidence where radiation or a DNA-damaging agent in vivo, or PCR with degenerate primers in vitro, are used for non-targeted mutagenesis.
'induced mutation evidence':
A type of genetic transformation evidence resulting from a mutation induced by a mutagenic compounds or irradiation.
Are these terms really meant to be distinct?
Both terms imply or state an intentional attempt to cause/induce mutations. Is this a correct assumption?
'random mutagenesis evidence' implies that the position of the mutation within the genome is random (as opposed to specifically targeting a region), while 'induced mutation evidence' does not state whether the mutations are random or targeted. Is there supposed to be a difference?
As a child of 'genetic transformation evidence', 'induced mutation evidence' inherits from the parent definition "...resulting from the conversion of one genotype into another by the introduction of exogenous DNA.", i.e. in addition to a mutagenic compound or radiation, exogenous DNA is involved.
-- Is 'induced mutation evidence' supposed to imply the introduction of exogenous DNA?
Is this the original intent of the term that DNA originating from outside the organism is introduced?
-- If not, shouldn't this term be a child of 'mutant phenotype evidence'?
Is there perhaps a better term for 'random mutagenesis evidence'?
To me it sounds very much like "random mutation" which conveys the idea that the mutations (point mutation, nonsynonymous mutation, etc.) occur at any random position in the genome and that such mutations are not intentional or "guided" - mutations occur "naturally". As noted above, 'random mutagenesis evidence' seems to intentionally induce mutations.
Should 'random mutagenesis evidence' be moved from 'experimental phenotypic evidence' to 'mutant phenotype evidence'? Currently there is no mention of observing the phenotypic expression of a mutation but am I correct in assuming that this was the intent?
Thanks.
James
Hi James,
I think the two terms are indeed the same. I would merge.
Should 'random mutagenesis evidence' be moved from 'experimental phenotypic evidence' to 'mutant phenotype evidence'? Currently there is no mention of observing the phenotypic expression of a mutation but am I correct in assuming that this was the intent?
Yes I think so. I wanted to add more structure to the terms we had requested a few years back, but we never got to it.
Thanks, Pascale
Hi @jbmunro ,
I would probably opt to keep them separate, but with a re-write.
I agree that given its inheritance from "genetic transformation evidence" ECO:0005027, the current wording of "induced mutation evidence" ECO:0001056 does not make a lot of sense. But there are techniques wherein researchers do introduce exogenous DNA to induce mutations, such as transposon mutagenesis and the derived Transposon sequencing (Tn-seq). These techniques, beyond causing knockouts, often incorporate markers or reporters, so they are bona fide "genetic transformation". I believe ECO:0005027 should capture these. Alternatively, you can merge the two existing terms as proposed (for compatibility with existing annotations) and add a new branch for the transposon mutagenesis-like terms.
I would also split 'random mutagenesis evidence' ECO:0005529 to differentiate between in vivo (e.g. radiation) and in vitro (e.g. PCR) protocols. Several reasons for this. The in vitro protocol requires that the mutated fragment be cloned back into the target organism. It also targets a specific DNA fragment, so it is not "random" in the same sense than irradiating a cell and hitting any segment of DNA.
Cheers,
Ivan
Right, I was thinking that after I wrote the comment. I think random mutagenesis is done by PCR, with an inbalanced pool of nucleotides. The definition is confusing, we should remove ' radiation or a DNA-damaging agent in vivo'.
Thanks, Pascale
Hi @pgaudet and @ivanerill
Thank you both for the advice! I'll get to work on this and touch base with everyone.
James
Hi @ivanerill and @pgaudet
Here is an update from our discussions. Your thoughts and suggestions are welcome.
James
Obsolete term: induced mutation evidence
This term will be made obsolete for a couple of reasons: the def doesn’t make sense as the suggested means of mutagenesis fail to introduce exogenous DNA (it is a child of genetic transformation evidence) and the def. is too much like random mutagenesis evidence.
Update term: random mutagenesis evidence -> random mutagenesis phenotypic evidence
old def.: A type of experimental phenotypic evidence where radiation or a DNA-damaging agent in vivo, or PCR with degenerate primers in vitro, are used for non-targeted mutagenesis.
new def.: A type of mutant phenotype evidence where a mutagenic product or process is used to alter the nucleotide sequence and thus induce genetic mutation. Examples include, but are not limited to mutagenic compounds, irradiation, PCR w/ degenerate primers, etc.
narrow syn.: random mutagenesis evidence
New term: random mutagenesis of specific target DNA evidence
new def.: A type of random mutagenesis evidence resulting from the random mutation of a specifically targeted region of DNA.
Ivan’s point about transposon sequencing and especially transposon mutagenesis, sparked a lot of discussion: it can be random or site-specific, it is indeed a type of ‘genetic transformation evidence’ as exogenous DNA is introduced, yet a second (inferred) parent could be ‘random mutagenesis evidence’ or ‘random mutagenesis of specific target DNA evidence’, etc. However, after much deliberation, we decided that transposon mutagenesis and Tn-seq are more of a protocol/technique and the actual type of evidence - that upon which an assertion is based - can vary greatly. (Additionally, we are striving to focus on evidence rather than protocol.)
For now, we have decided not to add any transposon-related terms and to address this issue in the future should a request for such terms arise.
Sounds good to me.
Sounds good to me too, thanks !
Thank you!
Proposed changes made and pushed to GitHub. Closing this ticket.
James
|
gharchive/issue
| 2019-09-03T18:09:44 |
2025-04-01T04:34:12.359197
|
{
"authors": [
"ivanerill",
"jbmunro",
"pgaudet"
],
"repo": "evidenceontology/evidenceontology",
"url": "https://github.com/evidenceontology/evidenceontology/issues/234",
"license": "CC0-1.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
353263046
|
add auth for etcdkeeperv3
move assets/etcdkeeperv3 to pages/etcdkeeperv3
/v3 is the entrance of etcdkeeperv3
/v3/login is the login page
-v3pwd is the config for login password
./httpserver -v3pwd 123456
123456 is the password for login.
There is a question, etcd can set user permissions, this feature I have not added. This and etcd permissions may be somewhat conflicting in understanding. Of course, I know that this function is to add a security mechanism to the client. It seems that there are some problems in both.
If need authentication, please enable etcd authentication for etcdkeeper 0.7.3.
|
gharchive/pull-request
| 2018-08-23T07:46:26 |
2025-04-01T04:34:12.361781
|
{
"authors": [
"evildecay",
"magicdvd"
],
"repo": "evildecay/etcdkeeper",
"url": "https://github.com/evildecay/etcdkeeper/pull/13",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1800399604
|
Seems like the perception module (especially prediction) not work
Hi evshary!
I'm currently running the Autoware universe on Carla with your bridge, but I got a question regarding the perception module of Autoware.
To my knowledge, Autoware is capable of predicting the trajectory of objects(like NPC Vehicle, ...) moving around, and I remember that I saw the expected trajectory drawn with dotted line on RViz when I run the Autoware on AWSIM.
However, when I run Autoware on Carla with the bridge, I cannot see any of the dotted lines in RViz as below:
I saw that the ego vehicle stops when the NPC Vehicle or other obstacles are in front of him, but in the case of the video below, the ego vehicle does not stop and eventually collide to the tail of the NPC Vehicle.
https://github.com/evshary/autoware_carla_launch/assets/50267797/476c7c5b-44a9-4de2-84b5-26d5dba34f56
Could you please check whether the expected trajectory shows well on your screen?
Thanks in advance! I always appreciate to your hard work!
No, I didn't see that before, because I haven't tried to add NPC in my scenario.
Actually, there is still something worth investigating in the bridge.
For example, Autoware can't detect the traffic light in Carla and follow the traffic rules.
These topics are pretty interesting. Maybe I can dive deep into them after tuning the bridge performance and dealing with version issues.
Thank you for answering me! I think I should test the bridge more too.
By the way, aren't the traffic light and traffic rules(especially speed limit and stop line) encoded in the map?
I read .osm file of nishishinjuku map and saw the code as below:
traffic light
<way id="1062" version='1'>
<nd ref="122948"/>
<nd ref="122949"/>
<tag k="type" v="traffic_light"/>
<tag k="subtype" v="red_yellow_green"/>
<tag k="height" v="0.450000"/>
</way>
stop line
<way id="1078" version='1'>
<nd ref="15115"/>
<nd ref="9285"/>
<tag k="type" v="stop_line"/>
</way>
speed limit
<relation id="4" version='1'>
<member type="way" role="left" ref="361"/>
<member type="way" role="right" ref="362"/>
<member type="relation" role="regulatory_element" ref="1292"/>
<tag k="type" v="lanelet"/>
<tag k="subtype" v="road"/>
<tag k="speed_limit" v="50"/>
<tag k="location" v="urban"/>
<tag k="one_way" v="yes"/>
<tag k="participant:vehicle" v="yes"/>
</relation>
I do not know whether Autoware perceives stop lines, but I saw the traffic light detection module is enabled when I run Autoware, so maybe he can abide by the rules if the map provides enough information.. I think.
|
gharchive/issue
| 2023-07-12T07:53:42 |
2025-04-01T04:34:12.392512
|
{
"authors": [
"Kim-mins",
"evshary"
],
"repo": "evshary/autoware_carla_launch",
"url": "https://github.com/evshary/autoware_carla_launch/issues/15",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2296694003
|
Use alpine images on Swoole and Docker
This is a PR for issue https://github.com/exaco/laravel-octane-dockerfile/issues/76, "add alpine images".
I have not altered the FrankenPHP.Dockerfile as I don't use FrankenPHP and am not sure which image to select or how to reliably test it.
The changes in this PR are pretty straightforward, and nearly identical on the RoadRunner and Swoole docker files.
Potential Issues:
not sure if changing the #!/usr/bin/env sh line on top of start-container will effect the FrankenPHP image.
haven't tested RoadRunner fully enough yet
As for next steps, assuming everything works well on you guys' end, I'm not sure if it would be best to:
Replace the original files
Create separate "alpine" branch/release
Add additional files to this repo
Thanks for your contribution! I think creating new Dockerfiles like Swoole.Alpine.Dockerfile instead of modifying our existing Debian-based Dockerfiles. After that, we can think about moving Dockerfiles to a new directory.
@smortexa I have altered the PR to make the Alpine files separate!
The start-container is still the same with the alteration of Line 1
#!/usr/bin/env bash -> #!/usr/bin/env sh
|
gharchive/pull-request
| 2024-05-15T01:57:46 |
2025-04-01T04:34:12.433175
|
{
"authors": [
"dir",
"smortexa"
],
"repo": "exaco/laravel-octane-dockerfile",
"url": "https://github.com/exaco/laravel-octane-dockerfile/pull/77",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1757273349
|
compreface-core error: E tensorflow/stream_executor/cuda/cuda_driver.cc:351] failed call to cuInit: UNKNOWN ERROR (303)
Hi, for some reason my compreface docker doesn't work anymore. I am using double-take to get compreface process the images. Whenever an images needs to be processed compreface-core shows the captioned error message and never process anything.
I have tried to docker system prune -a and re-download compreface docker images again, and also remove the postgresql database volume. Any idea what's going on please?
Could you provide:
Your GPU name
your CompreFace build and version
Hello,
I am using CPU at the moment
I have tried both
#CORE_VERSION=1.1.0-arcface-r100
CORE_VERSION=1.1.0-facenet
Right now mainly using facenet.
@pospielov sorry for late reply. here is the logs after startup docker
Attaching to compreface-ui, compreface-admin, compreface-api, compreface-core, compreface-postgres-db compreface-admin | Listening for transport dt_socket at address: 5005 compreface-admin | compreface-admin | . ____ _ __ _ _ compreface-admin | /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ compreface-admin | ( ( )\___ | '_ | '_| | '_ \/ _ | \ \ \
compreface-admin | \/ )| |)| | | | | || (| | ) ) ) )
compreface-admin | ' || .__|| ||| |_, | / / / /
compreface-admin | =========||==============|/=////
compreface-admin | :: Spring Boot :: (v2.5.13)
compreface-admin |
compreface-admin | 2023-07-15 15:10:53.925 INFO 7 --- [kground-preinit] o.h.validator.internal.util.Version : HV000001: Hibernate Validator 6.2.3.Final
compreface-admin | 2023-07-15 15:10:53.961 INFO 7 --- [ main] com.exadel.frs.FrsApplication : Starting FrsApplication v0.0.1-SNAPSHOT using Java 11.0.8 on fac46ff53d70 with PID 7 (/home/app.jar started by root in /)
compreface-admin | 2023-07-15 15:10:53.962 DEBUG 7 --- [ main] com.exadel.frs.FrsApplication : Running with Spring Boot v2.5.13, Spring v5.3.19
compreface-admin | 2023-07-15 15:10:53.962 INFO 7 --- [ main] com.exadel.frs.FrsApplication : The following 1 profile is active: "dev"
compreface-api | Listening for transport dt_socket at address: 5005
compreface-api |
compreface-api | . ____ _ __ _ _
compreface-api | /\ / ' __ _ () __ __ _ \ \ \
compreface-api | ( ( )__ | ' | '| | ' / _ | \ \ \ \ compreface-api | \\/ ___)| |_)| | | | | || (_| | ) ) ) ) compreface-api | ' |____| .__|_| |_|_| |_\__, | / / / / compreface-api | =========|_|==============|___/=/_/_/_/ compreface-api | :: Spring Boot :: (v2.5.13) compreface-api | compreface-api | 2023-07-15 15:10:53.856 INFO 7 --- [kground-preinit] o.h.validator.internal.util.Version : HV000001: Hibernate Validator 6.2.3.Final compreface-api | 2023-07-15 15:10:53.905 INFO 7 --- [ main] com.exadel.frs.TrainServiceApplication : Starting TrainServiceApplication v0.0.1-SNAPSHOT using Java 11.0.8 on dc208165642e with PID 7 (/home/app.jar started by root in /) compreface-api | 2023-07-15 15:10:53.907 INFO 7 --- [ main] com.exadel.frs.TrainServiceApplication : The following 1 profile is active: "dev" compreface-api | 2023-07-15 15:10:54.082 WARN 7 --- [ main] o.s.b.c.config.ConfigDataEnvironment : Property 'spring.profiles' imported from location 'class path resource [application.yml]' is invalid and should be replaced with 'spring.config.activate.on-profile' [origin: class path resource [application.yml] from app.jar - 94:13] compreface-postgres-db | 2023-07-15 15:10:50.252 UTC [1] LOG: listening on IPv4 address "0.0.0.0", port 5432 compreface-postgres-db | 2023-07-15 15:10:50.252 UTC [1] LOG: listening on IPv6 address "::", port 5432 compreface-postgres-db | 2023-07-15 15:10:50.260 UTC [1] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" compreface-postgres-db | 2023-07-15 15:10:50.282 UTC [25] LOG: database system was shut down at 2023-07-15 15:10:44 UTC compreface-postgres-db | 2023-07-15 15:10:50.289 UTC [1] LOG: database system is ready to accept connections compreface-core | [uWSGI] getting INI configuration from uwsgi.ini compreface-core | *** Starting uWSGI 2.0.19 (64bit) on [Sat Jul 15 15:10:50 2023] *** compreface-core | compiled with version: 10.2.1 20210110 on 07 October 2022 10:36:44 compreface-core | os: Linux-5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 compreface-core | nodename: 5f6d0b944310 compreface-core | machine: x86_64 compreface-core | clock source: unix compreface-core | detected number of CPU cores: 8 compreface-core | current working directory: /app/ml compreface-core | detected binary path: /usr/local/bin/uwsgi compreface-core | !!! no internal routing support, rebuild with pcre support !!! compreface-core | setgid() to 33 compreface-core | setuid() to 33 compreface-core | your memory page size is 4096 bytes compreface-core | detected max file descriptor number: 1048576 compreface-core | lock engine: pthread robust mutexes compreface-core | thunder lock: disabled (you can enable it with --thunder-lock) compreface-core | uwsgi socket 0 bound to TCP address 0.0.0.0:3000 fd 3 compreface-core | Python version: 3.7.14 (default, Oct 5 2022, 16:16:25) [GCC 10.2.1 20210110] compreface-core | Python main interpreter initialized at 0x55c8daa7bc60 compreface-core | python threads support enabled compreface-core | your server socket listen backlog is limited to 100 connections compreface-core | your mercy for graceful operations on workers is 60 seconds compreface-core | mapped 218712 bytes (213 KB) for 2 cores compreface-core | *** Operational MODE: preforking *** compreface-core | {"severity": "INFO", "message": "{'BUILD_VERSION': 'dev', 'CALCULATION_PLUGIN': 'facenet.Calculator', 'EXTRA_PLUGINS': ['facenet.LandmarksDetector', 'agegender.GenderDetector', 'agegender.AgeDetector', 'facenet.facemask.MaskDetector', 'facenet.PoseEstimator'], 'FACE_DETECTION_PLUGIN': 'facenet.FaceDetector', 'GPU_IDX': -1, 'IMG_LENGTH_LIMIT': 640, 'INTEL_OPTIMIZATION': False, 'IS_DEV_ENV': False, 'LOGGING_LEVEL_NAME': 'DEBUG', 'ML_PORT': 3000, 'RUN_MODE': True}", "request": null, "logger": "src.app", "module": "app", "traceback": null, "build_version": "dev"} compreface-core | {"severity": "DEBUG", "message": "Creating new app for WSGI", "request": null, "logger": "src.app", "module": "app", "traceback": null, "build_version": "dev"} compreface-core | WSGI app 0 (mountpoint='') ready in 3 seconds on interpreter 0x55c8daa7bc60 pid: 1 (default app) compreface-core | *** uWSGI is running in multiple interpreter mode *** compreface-core | spawned uWSGI master process (pid: 1) compreface-core | spawned uWSGI worker 1 (pid: 23, cores: 1) compreface-core | spawned uWSGI worker 2 (pid: 24, cores: 1) compreface-ui | /docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration compreface-ui | /docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/ compreface-ui | /docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh compreface-ui | 10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist compreface-ui | /docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh compreface-ui | 20-envsubst-on-templates.sh: Running envsubst on /etc/nginx/templates/nginx.conf.template to /etc/nginx/conf.d/nginx.conf compreface-ui | /docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh compreface-ui | /docker-entrypoint.sh: Configuration complete; ready for start up compreface-admin | 2023-07-15 15:10:57.507 INFO 7 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode. compreface-admin | 2023-07-15 15:10:57.720 INFO 7 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 195 ms. Found 11 JPA repository interfaces. compreface-api | 2023-07-15 15:10:58.101 INFO 7 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode. compreface-admin | 2023-07-15 15:10:58.210 INFO 7 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=87eecb33-b947-31b8-bbb7-8d063df92185 compreface-api | 2023-07-15 15:10:58.409 INFO 7 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 278 ms. Found 8 JPA repository interfaces. compreface-admin | 2023-07-15 15:10:59.498 INFO 7 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http) compreface-admin | 2023-07-15 15:10:59.520 INFO 7 --- [ main] o.a.coyote.http11.Http11NioProtocol : Initializing ProtocolHandler ["http-nio-8080"] compreface-admin | 2023-07-15 15:10:59.521 INFO 7 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] compreface-admin | 2023-07-15 15:10:59.522 INFO 7 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.62] compreface-admin | 2023-07-15 15:10:59.676 INFO 7 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext compreface-admin | 2023-07-15 15:10:59.676 INFO 7 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 5584 ms compreface-api | 2023-07-15 15:11:00.339 INFO 7 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=9776d44d-52e1-38dc-b671-bd86977f22bf compreface-admin | 2023-07-15 15:11:00.648 INFO 7 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting... compreface-admin | 2023-07-15 15:11:00.829 INFO 7 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed. compreface-admin | 2023-07-15 15:11:01.073 INFO 7 --- [ main] liquibase.database : Set default schema name to public compreface-admin | 2023-07-15 15:11:01.203 INFO 7 --- [ main] liquibase.lockservice : Successfully acquired change log lock compreface-api | 2023-07-15 15:11:01.463 INFO 7 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'cacheConfig' of type [com.exadel.frs.core.trainservice.config.CacheConfig$$EnhancerBySpringCGLIB$$b9639fd0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) compreface-admin | 2023-07-15 15:11:02.388 INFO 7 --- [ main] liquibase.changelog : Reading from public.databasechangelog compreface-api | 2023-07-15 15:11:02.651 INFO 7 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 8080 (http) compreface-api | 2023-07-15 15:11:02.679 INFO 7 --- [ main] o.a.coyote.http11.Http11NioProtocol : Initializing ProtocolHandler ["http-nio-8080"] compreface-api | 2023-07-15 15:11:02.681 INFO 7 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] compreface-api | 2023-07-15 15:11:02.681 INFO 7 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.62] compreface-admin | 2023-07-15 15:11:02.816 INFO 7 --- [ main] liquibase.lockservice : Successfully released change log lock compreface-api | 2023-07-15 15:11:02.951 INFO 7 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext compreface-api | 2023-07-15 15:11:02.951 INFO 7 --- [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 8867 ms compreface-postgres-db | 2023-07-15 15:11:03.214 UTC [32] WARNING: there is no transaction in progress compreface-admin | 2023-07-15 15:11:03.428 INFO 7 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default] compreface-admin | 2023-07-15 15:11:03.599 INFO 7 --- [ main] org.hibernate.Version : HHH000412: Hibernate ORM core version 5.4.33 compreface-admin | 2023-07-15 15:11:03.917 INFO 7 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.2.Final} compreface-api | 2023-07-15 15:11:04.072 INFO 7 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default] compreface-admin | 2023-07-15 15:11:04.185 INFO 7 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL10Dialect compreface-admin | 2023-07-15 15:11:04.301 INFO 7 --- [ main] Hibernate Types : This framework is proudly powered by: compreface-admin | compreface-admin | >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> compreface-admin | _ _ _ _ compreface-admin | | | | | (_) | | compreface-admin | | |__| |_ _ _ __ ___ _ __ ___ _ ___| |_ ___ _ __ ___ ___ compreface-admin | | __ | | | | '_ \ / _ \ '__/ __| / __| __/ _ \ '_ \ / __/ _ \ compreface-admin | | | | | |_| | |_) | __/ | \__ \ \__ \ || __/ | | | (_| __/ compreface-admin | |_| |_|\__, | .__/ \___|_| |___/_|___/\__\___|_| |_|\___\___| compreface-admin | __/ | | compreface-admin | |___/|_| compreface-admin | compreface-admin | At Hypersistence, we only build amazing tools, like Hibernate Types, Flexy Pool, or Hypersistence Optimizer. compreface-admin | compreface-admin | What if there were a tool that could automatically detect JPA and Hibernate performance issues? compreface-admin | compreface-admin | Hypersistence Optimizer is that tool! For more details, go to: compreface-admin | compreface-admin | https://vladmihalcea.com/hypersistence-optimizer/ compreface-admin | <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< compreface-admin | compreface-api | 2023-07-15 15:11:04.435 INFO 7 --- [ main] org.hibernate.Version : HHH000412: Hibernate ORM core version 5.4.33 compreface-api | 2023-07-15 15:11:04.442 INFO 7 --- [ main] org.hibernate.cfg.Environment : HHH000205: Loaded properties from resource hibernate.properties: {hibernate.bytecode.use_reflection_optimizer=false, hibernate.types.print.banner=false} compreface-api | 2023-07-15 15:11:05.124 INFO 7 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.1.2.Final} compreface-admin | 2023-07-15 15:11:05.912 INFO 7 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform] compreface-admin | 2023-07-15 15:11:05.928 INFO 7 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' compreface-api | 2023-07-15 15:11:06.440 INFO 7 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting... compreface-api | 2023-07-15 15:11:06.880 INFO 7 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed. compreface-api | 2023-07-15 15:11:06.991 INFO 7 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.PostgreSQL10Dialect compreface-admin | 2023-07-15 15:11:08.460 INFO 7 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path '/actuator' compreface-admin | 2023-07-15 15:11:08.569 INFO 7 --- [ main] pertySourcedRequestMappingHandlerMapping : Mapped URL path [/v2/api-docs] onto method [springfox.documentation.swagger2.web.Swagger2Controller#getDocumentation(String, HttpServletRequest)] compreface-admin | 2023-07-15 15:11:09.215 WARN 7 --- [ main] o.s.s.c.a.web.builders.WebSecurity : You are asking Spring Security to ignore Ant [pattern='/v2/api-docs']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead. compreface-admin | 2023-07-15 15:11:09.217 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will secure Ant [pattern='/v2/api-docs'] with [] compreface-admin | 2023-07-15 15:11:09.217 WARN 7 --- [ main] o.s.s.c.a.web.builders.WebSecurity : You are asking Spring Security to ignore Ant [pattern='/configuration/ui']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead. compreface-admin | 2023-07-15 15:11:09.218 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will secure Ant [pattern='/configuration/ui'] with [] compreface-admin | 2023-07-15 15:11:09.218 WARN 7 --- [ main] o.s.s.c.a.web.builders.WebSecurity : You are asking Spring Security to ignore Ant [pattern='/swagger-resources/**']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead. compreface-admin | 2023-07-15 15:11:09.218 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will secure Ant [pattern='/swagger-resources/**'] with [] compreface-admin | 2023-07-15 15:11:09.218 WARN 7 --- [ main] o.s.s.c.a.web.builders.WebSecurity : You are asking Spring Security to ignore Ant [pattern='/configuration/**']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead. compreface-admin | 2023-07-15 15:11:09.218 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will secure Ant [pattern='/configuration/**'] with [] compreface-admin | 2023-07-15 15:11:09.219 WARN 7 --- [ main] o.s.s.c.a.web.builders.WebSecurity : You are asking Spring Security to ignore Ant [pattern='/swagger-ui**']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead. compreface-admin | 2023-07-15 15:11:09.220 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will secure Ant [pattern='/swagger-ui**'] with [] compreface-admin | 2023-07-15 15:11:09.220 WARN 7 --- [ main] o.s.s.c.a.web.builders.WebSecurity : You are asking Spring Security to ignore Ant [pattern='/webjars/**']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead. compreface-admin | 2023-07-15 15:11:09.220 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will secure Ant [pattern='/webjars/**'] with [] compreface-admin | 2023-07-15 15:11:09.220 WARN 7 --- [ main] o.s.s.c.a.web.builders.WebSecurity : You are asking Spring Security to ignore Ant [pattern='/lms/**']. This is not recommended -- please use permitAll via HttpSecurity#authorizeHttpRequests instead. compreface-admin | 2023-07-15 15:11:09.220 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will secure Ant [pattern='/lms/**'] with [] compreface-admin | 2023-07-15 15:11:09.283 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will not secure Or [Ant [pattern='/oauth/token'], Ant [pattern='/oauth/token_key'], Ant [pattern='/oauth/check_token']] compreface-admin | 2023-07-15 15:11:09.301 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will not secure org.springframework.security.oauth2.config.annotation.web.configuration.ResourceServerConfiguration$NotOAuthRequestMatcher@28d16af8 compreface-admin | 2023-07-15 15:11:09.306 INFO 7 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Will not secure any request compreface-admin | 2023-07-15 15:11:09.421 INFO 7 --- [ main] org.quartz.impl.StdSchedulerFactory : Using default implementation for ThreadExecutor compreface-admin | 2023-07-15 15:11:09.436 INFO 7 --- [ main] org.quartz.core.SchedulerSignalerImpl : Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl compreface-admin | 2023-07-15 15:11:09.436 INFO 7 --- [ main] org.quartz.core.QuartzScheduler : Quartz Scheduler v.2.3.2 created. compreface-admin | 2023-07-15 15:11:09.439 INFO 7 --- [ main] o.s.s.quartz.LocalDataSourceJobStore : Using db table-based data access locking (synchronization). compreface-admin | 2023-07-15 15:11:09.442 INFO 7 --- [ main] o.s.s.quartz.LocalDataSourceJobStore : JobStoreCMT initialized. compreface-admin | 2023-07-15 15:11:09.442 INFO 7 --- [ main] org.quartz.core.QuartzScheduler : Scheduler meta-data: Quartz Scheduler (v2.3.2) 'statistics scheduler' with instanceId 'NON_CLUSTERED' compreface-admin | Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. compreface-admin | NOT STARTED. compreface-admin | Currently in standby mode. compreface-admin | Number of jobs executed: 0 compreface-admin | Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 1 threads. compreface-admin | Using job-store 'org.springframework.scheduling.quartz.LocalDataSourceJobStore' - which supports persistence. and is not clustered. compreface-admin | compreface-admin | 2023-07-15 15:11:09.442 INFO 7 --- [ main] org.quartz.impl.StdSchedulerFactory : Quartz scheduler 'statistics scheduler' initialized from an externally provided properties instance. compreface-admin | 2023-07-15 15:11:09.443 INFO 7 --- [ main] org.quartz.impl.StdSchedulerFactory : Quartz scheduler version: 2.3.2 compreface-admin | 2023-07-15 15:11:09.443 INFO 7 --- [ main] org.quartz.core.QuartzScheduler : JobFactory set to: org.springframework.scheduling.quartz.SpringBeanJobFactory@2f82e3cf compreface-admin | 2023-07-15 15:11:09.489 INFO 7 --- [ main] o.s.s.quartz.LocalDataSourceJobStore : Freed 0 triggers from 'acquired' / 'blocked' state. compreface-admin | 2023-07-15 15:11:09.491 INFO 7 --- [ main] o.s.s.quartz.LocalDataSourceJobStore : Recovering 0 jobs that were in-progress at the time of the last shut-down. compreface-admin | 2023-07-15 15:11:09.491 INFO 7 --- [ main] o.s.s.quartz.LocalDataSourceJobStore : Recovery complete. compreface-admin | 2023-07-15 15:11:09.492 INFO 7 --- [ main] o.s.s.quartz.LocalDataSourceJobStore : Removed 0 'complete' triggers. compreface-admin | 2023-07-15 15:11:09.492 INFO 7 --- [ main] o.s.s.quartz.LocalDataSourceJobStore : Removed 0 stale fired job entries. compreface-admin | 2023-07-15 15:11:09.495 INFO 7 --- [ main] org.quartz.core.QuartzScheduler : Scheduler statistics scheduler_$_NON_CLUSTERED started. compreface-admin | 2023-07-15 15:11:10.560 INFO 7 --- [ main] o.a.coyote.http11.Http11NioProtocol : Starting ProtocolHandler ["http-nio-8080"] compreface-admin | 2023-07-15 15:11:10.581 INFO 7 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path '' compreface-admin | 2023-07-15 15:11:10.583 INFO 7 --- [ main] d.s.w.p.DocumentationPluginsBootstrapper : Context refreshed compreface-admin | 2023-07-15 15:11:10.604 INFO 7 --- [ main] d.s.w.p.DocumentationPluginsBootstrapper : Found 1 custom documentation plugin(s) compreface-admin | 2023-07-15 15:11:10.664 INFO 7 --- [ main] s.d.s.w.s.ApiListingReferenceScanner : Scanning for api listing references compreface-admin | 2023-07-15 15:11:10.884 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: regenerateApiKeyUsingPUT_1 compreface-admin | 2023-07-15 15:11:10.966 INFO 7 --- [ main] com.exadel.frs.FrsApplication : Started FrsApplication in 18.459 seconds (JVM running for 20.043) compreface-api | 2023-07-15 15:11:11.008 INFO 7 --- [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000490: Using JtaPlatform implementation: [org.hibernate.engine.transaction.jta.platform.internal.NoJtaPlatform] compreface-api | 2023-07-15 15:11:11.068 INFO 7 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' compreface-api | 2023-07-15 15:11:17.159 INFO 7 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 1 endpoint(s) beneath base path '/actuator' compreface-api | 2023-07-15 15:11:17.433 INFO 7 --- [ main] pertySourcedRequestMappingHandlerMapping : Mapped URL path [/v2/api-docs] onto method [springfox.documentation.swagger2.web.Swagger2Controller#getDocumentation(String, HttpServletRequest)] compreface-api | 2023-07-15 15:11:17.511 INFO 7 --- [ main] org.quartz.impl.StdSchedulerFactory : Using default implementation for ThreadExecutor compreface-api | 2023-07-15 15:11:17.533 INFO 7 --- [ main] org.quartz.core.SchedulerSignalerImpl : Initialized Scheduler Signaller of type: class org.quartz.core.SchedulerSignalerImpl compreface-api | 2023-07-15 15:11:17.533 INFO 7 --- [ main] org.quartz.core.QuartzScheduler : Quartz Scheduler v.2.3.2 created. compreface-api | 2023-07-15 15:11:17.534 INFO 7 --- [ main] org.quartz.simpl.RAMJobStore : RAMJobStore initialized. compreface-api | 2023-07-15 15:11:17.536 INFO 7 --- [ main] org.quartz.core.QuartzScheduler : Scheduler meta-data: Quartz Scheduler (v2.3.2) 'quartzScheduler' with instanceId 'NON_CLUSTERED' compreface-api | Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally. compreface-api | NOT STARTED. compreface-api | Currently in standby mode. compreface-api | Number of jobs executed: 0 compreface-api | Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with 10 threads. compreface-api | Using job-store 'org.quartz.simpl.RAMJobStore' - which does not support persistence. and is not clustered. compreface-api | compreface-api | 2023-07-15 15:11:17.536 INFO 7 --- [ main] org.quartz.impl.StdSchedulerFactory : Quartz scheduler 'quartzScheduler' initialized from an externally provided properties instance. compreface-api | 2023-07-15 15:11:17.536 INFO 7 --- [ main] org.quartz.impl.StdSchedulerFactory : Quartz scheduler version: 2.3.2 compreface-api | 2023-07-15 15:11:17.537 INFO 7 --- [ main] org.quartz.core.QuartzScheduler : JobFactory set to: org.springframework.scheduling.quartz.SpringBeanJobFactory@73da303e compreface-api | 2023-07-15 15:11:17.544 INFO 7 --- [ main] org.quartz.core.QuartzScheduler : Scheduler quartzScheduler_$_NON_CLUSTERED started. compreface-api | 2023-07-15 15:11:18.466 INFO 7 --- [ main] o.a.coyote.http11.Http11NioProtocol : Starting ProtocolHandler ["http-nio-8080"] compreface-api | 2023-07-15 15:11:18.485 INFO 7 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 8080 (http) with context path '' compreface-api | 2023-07-15 15:11:18.487 INFO 7 --- [ main] d.s.w.p.DocumentationPluginsBootstrapper : Context refreshed compreface-api | 2023-07-15 15:11:18.557 INFO 7 --- [ main] d.s.w.p.DocumentationPluginsBootstrapper : Found 2 custom documentation plugin(s) compreface-api | 2023-07-15 15:11:18.752 INFO 7 --- [ main] s.d.s.w.s.ApiListingReferenceScanner : Scanning for api listing references compreface-api | 2023-07-15 15:11:19.293 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: recognizeBase64UsingPOST_1 compreface-api | 2023-07-15 15:11:19.295 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: downloadImgUsingGET_1 compreface-api | 2023-07-15 15:11:19.379 INFO 7 --- [ main] s.d.s.w.s.ApiListingReferenceScanner : Scanning for api listing references compreface-api | 2023-07-15 15:11:19.402 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: getConfigUsingGET_1 compreface-api | 2023-07-15 15:11:19.405 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: getCheckDemoUsingGET_1 compreface-api | 2023-07-15 15:11:19.420 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: detectUsingPOST_1 compreface-api | 2023-07-15 15:11:19.425 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: detectBase64UsingPOST_1 compreface-api | 2023-07-15 15:11:19.430 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: addEmbeddingUsingPOST_1 compreface-api | 2023-07-15 15:11:19.433 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: addEmbeddingBase64UsingPOST_1 compreface-api | 2023-07-15 15:11:19.435 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: deleteEmbeddingByIdUsingDELETE_1 compreface-api | 2023-07-15 15:11:19.439 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: deleteEmbeddingsByIdUsingPOST_1 compreface-api | 2023-07-15 15:11:19.441 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: downloadImgUsingGET_2 compreface-api | 2023-07-15 15:11:19.446 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: listEmbeddingsUsingGET_1 compreface-api | 2023-07-15 15:11:19.459 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: recognizeBase64UsingPOST_2 compreface-api | 2023-07-15 15:11:19.463 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: recognizeFileUsingPOST_1 compreface-api | 2023-07-15 15:11:19.465 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: removeAllSubjectEmbeddingsUsingDELETE_1 compreface-api | 2023-07-15 15:11:19.467 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: migrateUsingPOST_1 compreface-api | 2023-07-15 15:11:19.472 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: handleUsingGET_1 compreface-api | 2023-07-15 15:11:19.483 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: recognizeUsingPOST_1 compreface-api | 2023-07-15 15:11:19.486 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: recognizeBase64UsingPOST_3 compreface-api | 2023-07-15 15:11:19.488 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: downloadImgUsingGET_3 compreface-api | 2023-07-15 15:11:19.492 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: createSubjectUsingPOST_1 compreface-api | 2023-07-15 15:11:19.494 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: deleteSubjectUsingDELETE_1 compreface-api | 2023-07-15 15:11:19.495 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: deleteSubjectsUsingDELETE_1 compreface-api | 2023-07-15 15:11:19.497 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: listSubjectsUsingGET_1 compreface-api | 2023-07-15 15:11:19.499 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: renameSubjectUsingPUT_1 compreface-api | 2023-07-15 15:11:19.513 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: verifyUsingPOST_1 compreface-api | 2023-07-15 15:11:19.516 INFO 7 --- [ main] .d.s.w.r.o.CachingOperationNameGenerator : Generating unique operation named: verifyBase64UsingPOST_1 compreface-api | 2023-07-15 15:11:19.552 INFO 7 --- [ main] com.exadel.frs.TrainServiceApplication : Started TrainServiceApplication in 27.435 seconds (JVM running for 28.993)
I don't see any errors in logs you provided.
Could you add logs where you see "failed call to cuInit: UNKNOWN ERROR"?
2023-12-20 14:12:46 [uWSGI] getting INI configuration from uwsgi.ini
2023-12-20 14:12:46 *** Starting uWSGI 2.0.19 (64bit) on [Wed Dec 20 06:12:46 2023] ***
2023-12-20 14:12:46 compiled with version: 10.2.1 20210110 on 14 August 2023 20:24:09
2023-12-20 14:12:46 os: Linux-5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023
2023-12-20 14:12:46 nodename: 1d2ec035cb59
2023-12-20 14:12:46 machine: x86_64
2023-12-20 14:12:46 clock source: unix
2023-12-20 14:12:46 pcre jit disabled
2023-12-20 14:12:46 detected number of CPU cores: 8
2023-12-20 14:12:46 current working directory: /app/ml
2023-12-20 14:12:46 detected binary path: /usr/local/bin/uwsgi
2023-12-20 14:12:46 setgid() to 33
2023-12-20 14:12:46 setuid() to 33
2023-12-20 14:12:46 your memory page size is 4096 bytes
2023-12-20 14:12:46 detected max file descriptor number: 1048576
2023-12-20 14:12:46 lock engine: pthread robust mutexes
2023-12-20 14:12:46 thunder lock: disabled (you can enable it with --thunder-lock)
2023-12-20 14:12:46 uwsgi socket 0 bound to TCP address 0.0.0.0:3000 fd 3
2023-12-20 14:12:46 Python version: 3.8.17 (default, Jul 28 2023, 06:10:22) [GCC 10.2.1 20210110]
2023-12-20 14:12:46 *** Python threads support is disabled. You can enable it with --enable-threads ***
2023-12-20 14:12:46 Python main interpreter initialized at 0x5647850126c0
2023-12-20 14:12:46 your server socket listen backlog is limited to 100 connections
2023-12-20 14:12:46 your mercy for graceful operations on workers is 60 seconds
2023-12-20 14:12:46 mapped 145808 bytes (142 KB) for 1 cores
2023-12-20 14:12:46 *** Operational MODE: single process ***
2023-12-20 14:12:48 {"severity": "INFO", "message": "{'BUILD_VERSION': 'dev', 'CALCULATION_PLUGIN': 'facenet.Calculator', 'EXTRA_PLUGINS': ['facenet.LandmarksDetector', 'agegender.AgeDetector', 'agegender.GenderDetector', 'facenet.facemask.MaskDetector', 'facenet.PoseEstimator'], 'FACE_DETECTION_PLUGIN': 'facenet.FaceDetector', 'GPU_IDX': -1, 'IMG_LENGTH_LIMIT': 640, 'INTEL_OPTIMIZATION': False, 'IS_DEV_ENV': False, 'LOGGING_LEVEL_NAME': 'DEBUG', 'ML_PORT': 3000, 'RUN_MODE': True}", "request": null, "logger": "src.app", "module": "app", "traceback": null, "build_version": "dev"}
2023-12-20 14:12:48 {"severity": "DEBUG", "message": "Creating new app for WSGI", "request": null, "logger": "src.app", "module": "app", "traceback": null, "build_version": "dev"}
2023-12-20 14:12:48 WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x5647850126c0 pid: 1 (default app)
2023-12-20 14:12:48 *** uWSGI is running in multiple interpreter mode ***
2023-12-20 14:12:48 spawned uWSGI master process (pid: 1)
2023-12-20 14:12:48 spawned uWSGI worker 1 (pid: 22, cores: 1)
2023-12-20 14:14:11 2023-12-20 06:14:11.090500: E tensorflow/stream_executor/cuda/cuda_driver.cc:313] failed call to cuInit: UNKNOWN ERROR (303)
2023-12-20 14:14:11 {"severity": "DEBUG", "message": "Found: BoundingBoxDTO(x_min=49, y_min=47, x_max=199, y_max=224, probability=0.9400066137313843, _np_landmarks=array([[104, 124],\n [153, 124],\n [131, 157],\n [106, 177],\n [146, 177]]))", "request": {"method": "GET", "path": "/", "filename": "", "api_key": "", "remote_addr": "172.17.0.1"}, "logger": "src.services.facescan.plugins.facenet.facenet", "module": "facenet", "traceback": null, "build_version": "dev"}
2023-12-20 14:14:59 Starting to load ML models
2023-12-20 14:14:59 {"severity": "WARNING", "message": "404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.", "request": {"method": "GET", "path": "/", "filename": "", "api_key": "", "remote_addr": "172.17.0.1"}, "logger": "root", "module": "error_handling", "traceback": "Traceback (most recent call last):\n File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1950, in full_dispatch_request\n rv = self.dispatch_request()\n File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1926, in dispatch_request\n self.raise_routing_exception(req)\n File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1908, in raise_routing_exception\n raise request.routing_exception\n File "/usr/local/lib/python3.8/site-packages/flask/ctx.py", line 350, in match_request\n result = self.url_adapter.match(return_rule=True)\n File "/usr/local/lib/python3.8/site-packages/werkzeug/routing.py", line 1945, in match\n raise NotFound()\nwerkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.\n", "build_version": "dev"}
I don't see any errors in logs you provided. Could you add logs where you see "failed call to cuInit: UNKNOWN ERROR"? Also, please attach logs in a text file next time
2023-12-20 14:12:46 [uWSGI] getting INI configuration from uwsgi.ini
2023-12-20 14:12:46 *** Starting uWSGI 2.0.19 (64bit) on [Wed Dec 20 06:12:46 2023] ***
2023-12-20 14:12:46 compiled with version: 10.2.1 20210110 on 14 August 2023 20:24:09
2023-12-20 14:12:46 os: Linux-5.15.133.1-microsoft-standard-WSL2 #1 SMP Thu Oct 5 21:02:42 UTC 2023
2023-12-20 14:12:46 nodename: 1d2ec035cb59
2023-12-20 14:12:46 machine: x86_64
2023-12-20 14:12:46 clock source: unix
2023-12-20 14:12:46 pcre jit disabled
2023-12-20 14:12:46 detected number of CPU cores: 8
2023-12-20 14:12:46 current working directory: /app/ml
2023-12-20 14:12:46 detected binary path: /usr/local/bin/uwsgi
2023-12-20 14:12:46 setgid() to 33
2023-12-20 14:12:46 setuid() to 33
2023-12-20 14:12:46 your memory page size is 4096 bytes
2023-12-20 14:12:46 detected max file descriptor number: 1048576
2023-12-20 14:12:46 lock engine: pthread robust mutexes
2023-12-20 14:12:46 thunder lock: disabled (you can enable it with --thunder-lock)
2023-12-20 14:12:46 uwsgi socket 0 bound to TCP address 0.0.0.0:3000 fd 3
2023-12-20 14:12:46 Python version: 3.8.17 (default, Jul 28 2023, 06:10:22) [GCC 10.2.1 20210110]
2023-12-20 14:12:46 *** Python threads support is disabled. You can enable it with --enable-threads ***
2023-12-20 14:12:46 Python main interpreter initialized at 0x5647850126c0
2023-12-20 14:12:46 your server socket listen backlog is limited to 100 connections
2023-12-20 14:12:46 your mercy for graceful operations on workers is 60 seconds
2023-12-20 14:12:46 mapped 145808 bytes (142 KB) for 1 cores
2023-12-20 14:12:46 *** Operational MODE: single process ***
2023-12-20 14:12:48 {"severity": "INFO", "message": "{'BUILD_VERSION': 'dev', 'CALCULATION_PLUGIN': 'facenet.Calculator', 'EXTRA_PLUGINS': ['facenet.LandmarksDetector', 'agegender.AgeDetector', 'agegender.GenderDetector', 'facenet.facemask.MaskDetector', 'facenet.PoseEstimator'], 'FACE_DETECTION_PLUGIN': 'facenet.FaceDetector', 'GPU_IDX': -1, 'IMG_LENGTH_LIMIT': 640, 'INTEL_OPTIMIZATION': False, 'IS_DEV_ENV': False, 'LOGGING_LEVEL_NAME': 'DEBUG', 'ML_PORT': 3000, 'RUN_MODE': True}", "request": null, "logger": "src.app", "module": "app", "traceback": null, "build_version": "dev"}
2023-12-20 14:12:48 {"severity": "DEBUG", "message": "Creating new app for WSGI", "request": null, "logger": "src.app", "module": "app", "traceback": null, "build_version": "dev"}
2023-12-20 14:12:48 WSGI app 0 (mountpoint='') ready in 2 seconds on interpreter 0x5647850126c0 pid: 1 (default app)
2023-12-20 14:12:48 *** uWSGI is running in multiple interpreter mode ***
2023-12-20 14:12:48 spawned uWSGI master process (pid: 1)
2023-12-20 14:12:48 spawned uWSGI worker 1 (pid: 22, cores: 1)
2023-12-20 14:14:11 2023-12-20 06:14:11.090500: E tensorflow/stream_executor/cuda/cuda_driver.cc:313] failed call to cuInit: UNKNOWN ERROR (303)
2023-12-20 14:14:11 {"severity": "DEBUG", "message": "Found: BoundingBoxDTO(x_min=49, y_min=47, x_max=199, y_max=224, probability=0.9400066137313843, _np_landmarks=array([[104, 124],\n [153, 124],\n [131, 157],\n [106, 177],\n [146, 177]]))", "request": {"method": "GET", "path": "/", "filename": "", "api_key": "", "remote_addr": "172.17.0.1"}, "logger": "src.services.facescan.plugins.facenet.facenet", "module": "facenet", "traceback": null, "build_version": "dev"}
2023-12-20 14:14:59 Starting to load ML models
2023-12-20 14:14:59 {"severity": "WARNING", "message": "404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.", "request": {"method": "GET", "path": "/", "filename": "", "api_key": "", "remote_addr": "172.17.0.1"}, "logger": "root", "module": "error_handling", "traceback": "Traceback (most recent call last):\n File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1950, in full_dispatch_request\n rv = self.dispatch_request()\n File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1926, in dispatch_request\n self.raise_routing_exception(req)\n File "/usr/local/lib/python3.8/site-packages/flask/app.py", line 1908, in raise_routing_exception\n raise request.routing_exception\n File "/usr/local/lib/python3.8/site-packages/flask/ctx.py", line 350, in match_request\n result = self.url_adapter.match(return_rule=True)\n File "/usr/local/lib/python3.8/site-packages/werkzeug/routing.py", line 1945, in match\n raise NotFound()\nwerkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again.\n", "build_version": "dev"}
Hello, my computer does not have a GPU, I want to use CPU, but in Docker desktop after booting e Tensorflow/stream/Cuda/Cuda. CC: 313] failed call to cuInit: UNKNOWN ERROR (303) , I think this is because I don't have a GPU problem with my graphics card, now I want to use CPU OK? How Do I start it if I can?
|
gharchive/issue
| 2023-06-14T16:31:51 |
2025-04-01T04:34:12.480655
|
{
"authors": [
"ishangxue",
"pospielov",
"sirhideo"
],
"repo": "exadel-inc/CompreFace",
"url": "https://github.com/exadel-inc/CompreFace/issues/1088",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1287171990
|
[🐛for options]: RTL option does not work correctly in some cases
Description of what the bugs are and how reproduce them:
RTL doesn't work in ESL
Open the example with Playground with Playground inside. After you chose the RTL option you can see that options from Playground which is inside is not on the left. It should be on the left side. Moreover the Snippet dropdown menu appears on the left.
Note: If it's something that will be fixed after the ticket https://github.com/exadel-inc/ui-playground/issues/324 is resolved, we can either skip it or wait until it's done.
:tada: This issue has been resolved in version 1.0.0-beta.12 :tada:
The release is available on:
npm package (@beta dist-tag)
GitHub release
Your semantic-release bot :package::rocket:
:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on:
npm package (@latest dist-tag)
GitHub release
Your semantic-release bot :package::rocket:
|
gharchive/issue
| 2022-06-28T11:02:55 |
2025-04-01T04:34:12.488670
|
{
"authors": [
"yadamskaya"
],
"repo": "exadel-inc/ui-playground",
"url": "https://github.com/exadel-inc/ui-playground/issues/350",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1012722816
|
🛑 My Site is down
In c115656, My Site ($SECRET_SITE) was down:
HTTP code: 0
Response time: 0 ms
Resolved: My Site is back up in 4a31eb8.
|
gharchive/issue
| 2021-09-30T23:39:39 |
2025-04-01T04:34:12.498330
|
{
"authors": [
"exand"
],
"repo": "exand/upptime",
"url": "https://github.com/exand/upptime/issues/1257",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
599966607
|
【基本コンソール】Symphonyクラス名称が一意になっていない
Symphonyクラス名称が一意になっていないため、
同じ名称でいくつでも登録できてしまう。
【対象画面】
基本コンソール
（Symphonyクラス編集）
「Symphonyクラス名称」の各メニューの項目名が不一致になっている。
「Symphonyクラス名称」に統一する。
「Symphonyクラス一覧」メニュー・・・Symphony名称
「Symphonyクラス編集」メニュー・・・Symphonyクラス名称
「Symphony作業一覧」メニュー・・・Symphonyクラス名
「定期作業実行」メニュー・・・Symphonyクラス名
払戻完了。
|
gharchive/issue
| 2020-04-15T02:04:38 |
2025-04-01T04:34:12.507030
|
{
"authors": [
"a-koizumi",
"ta-matsuo"
],
"repo": "exastro-suite/it-automation",
"url": "https://github.com/exastro-suite/it-automation/issues/98",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1106323114
|
Feature Request: Bidirectional arrow in the Arrow heads section
What is the Feature?
Bidrectional arrow
What is Your Proposal?
1. Allow user to either create a bidirectional arrow
2. Allow the user to convert an arrow into a bidirectional arrow if the have it selected
What is the use case for this?
Having a bi-directional arrow would allow users to adjust and use just 1 arrow instead of 2 for many common uses cases:
Hello. How does it differ from what we already support with the arrowheads settings?
Hi @dwelle ,
O wow, I totally missed this 😅
To be honest,
I'm still finding it a bit confusing on how to enable the bidirectional arrow in the user interface.
User Journey
Creating a undirectional arrow
I arrive in Excalidraw click the arrow Icon & it generates the uni-directional arrow. Perfect, intuitive ✅
Creating a bi-directional arrow
when wanting to create a bidrectional arrow, its a bit less intuitive (in my personal opinion & I also blame my experience not knowing the in's & out's of the tool). I have created a very brief demo of my experience creating a bidrectional arrow
https://user-images.githubusercontent.com/6743796/149992523-815dcf68-1e96-4a6f-b91a-bf9cba146350.mp4
Idea(s)?
1. Create a bidirectional arrow option, in the arrowheads section.
If there is a unidirectional arrow that is selected & the user clicks the bi-directional arrow icon turn it into a bidrectional arrow.
if it's a bidrectional arrow & the bidirectional arrow is clicked; do nothing
OR if there is some way to detect that this is a bidirectional arrow in the code logic (I'm not too familiar with the codebase) perhaps not show the bi-directional arrow icon since the arrow is already of that type
I also thought bidirectional arrows were not supported, found this issue, and still had trouble figuring it out.
I just found this. How do you do it?
I just needed this today and found this issue, couldn't figure out how to add arrowheads in both sides and it seems I wasn't the only one.
So for everyone that ends up in the same situation and finds this issue there is a youtube video that explains how to do that and more:
https://www.youtube.com/watch?v=XW2ydQLKM6I
|
gharchive/issue
| 2022-01-17T23:01:52 |
2025-04-01T04:34:12.519449
|
{
"authors": [
"cliffordfajardo",
"davidfowl",
"dliu-workos",
"dwelle",
"nmofonseca"
],
"repo": "excalidraw/excalidraw",
"url": "https://github.com/excalidraw/excalidraw/issues/4618",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1419833674
|
feat: changed text copy/paste behaviour
#5783 Changed text copy/paste behaviour by creating one element per line by default and added shortcut to create a single element from multiple lines
TODOS
[x] Write tests.
[x] Have enough spacing between lines to not make bounding boxes overlap.
[x] Show plain text paste toast only once per application lifetime.
We can actually still only handle the paste event, we just need to know whether shift was pressed which we can't do from the ClipboardEvent. So we need to set a flag in the keydown event, which occurs before paste. It's kinda hacky, but AFAIK not much else we can do (apart from using the async clipboard API as you did, which isn't ideal).
If within the scope of this PR, I would suggest an option for lines to be separate elements, but auto-grouped.
If within the scope of this PR, I would suggest an option for lines to be separate elements, but auto-grouped.
I need a clarification: do you mean to add a different set of commands for this feature, or to change the current behaviour?
My 2 cents on changing the current behaviour: I bealive this would be a little confusing since the user expectation is to have separate lines. They arleady are selected after pasting so I don’t se the reason to have them grouped on top of that.
What do @dwelle and @vjeux think about it?
I just played with it and it does exactly what I want. Thanks so much for building this, it's going to help me so much. I used it today for pasting an event schedule I was working on, was nice to be able to get it line by line so that I could move things around.
I'll let @dwelle review the code itself.
Pushed a few changes:
remove changelog. We only write changelog for package-related changes. The rest is autogenerated from the commit log.
reverted inlining of probablySupportsClipboardReadText. Tests keep working fine. Otherwise, the course of action would be to try 1) mock tests, or 2) make the probablySupportsClipboardReadText into a callable function, instead of inlining, which is error prone if we used that check elsewhere.
changed how we handle plaintext pasting, so that it doesn't prevent pasting images or elements
I've also changed the line spacing a bit:
keep spacing consistent regardless of zoom. We don't want to increase/decrease spacing just because you happen to be zoomed in/out.
add at most one empty line between elements — I've read the comments above, but I think we should not keep multiple empty lines even if in source text. Again, it's about consistency (similar to how e.g. CommonMark handles whitespace) and so that if you copy/paste a spreadsheet or similar data with potentially lots of empty lines, there won't be a huge unnecessary holes. If people show up with counter use cases, we can revert back.
instead of always using a default line height for spacing, make line space account for current line height. For example, when you paste emoji, the line height is bigger, so the space show be bigger.
Plus some refactor and other small tweaks.
I have realized that this would not be ideal if we could paste from another source other than key-pressing. That would mean that we should remember every time to set that variabile before calling the pasteFromClipboard function.
We should do both actually. The setTimeout IMO is slightly redundant if we reset on each paste, though as you say it won't cover possible future cases of non-keyboard plaintext-pasting so I kept it.
Alright, sorry for the delay folks. Merging now, tweeting later! 🚀 ❤️
|
gharchive/pull-request
| 2022-10-23T15:36:26 |
2025-04-01T04:34:12.527062
|
{
"authors": [
"DanielJGeiger",
"adarkforce",
"dwelle",
"vjeux"
],
"repo": "excalidraw/excalidraw",
"url": "https://github.com/excalidraw/excalidraw/pull/5786",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
910738733
|
Conflict with Kaminari?
I use kaminari (1.2.1) in my app to handle pagination, and when I install the simple_discussion gem, and try navigate to any page of my app I get the following error:
undefined method 'per' for #<ActiveRecord::AssociationRelation []>
I saw that the simple_discussion gem added will_paginate to the Gemfile.lock and I assume this is causing the conflict.
Is there any way to get simple_discussion working with Kaminari?
You can use them together if you apply a monkeypatch. Been a long time since I've done that. Something like this: https://github.com/kaminari/kaminari/issues/162#issuecomment-73953413
Thanks @excid3 - you're a champion.
|
gharchive/issue
| 2021-06-03T18:07:21 |
2025-04-01T04:34:12.542244
|
{
"authors": [
"chrisedington",
"excid3"
],
"repo": "excid3/simple_discussion",
"url": "https://github.com/excid3/simple_discussion/issues/36",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
1342482067
|
빈 채팅방 삭제
owner(최초 방을 만든 사람)이 나가면 모든 참여자를 내보내고 방 삭제
마지막 남은 참여자가 나가면 방 삭제
문제점
두 방법 모두 누군가 명시적으로 방을 나가지 않고 그냥 탭을 닫는다거나 하면 채팅방이 영원히 남아있습니다.
소켓 연결 종료시 방을 나간 걸로 간주한다면, 다시 로그인 또는 새로고침했을 때 기존 채팅방에서 빠져나가버릴 것 같습니다.
2 번이 나을것 같습니다.
다시 접속 시 접속중인 채팅방은 남아있기 때문에 유저가 나가지 않는다면 채팅방이 영원히 남아있는건 문제되지 않는 것 같습니다.
다만 오너가 나가면 다른 누군가에게 오너를 이전해줘야하는 로직이 추가되어야 하겠네요
1번 결정-> 각 참여자는 NOTICE 이벤트로 LEAVE를 받는 것.
|
gharchive/issue
| 2022-08-18T02:18:48 |
2025-04-01T04:34:12.550557
|
{
"authors": [
"hoikii",
"peas856"
],
"repo": "exciting-transcendence/transcendence",
"url": "https://github.com/exciting-transcendence/transcendence/issues/137",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
824106848
|
[v3] new concept exercise: flight-to-mars (exceptions, a couple enum methods)
This is the start of an exercise for the exceptions concept (which seems to be present already without an exercise). It also includes a few enum methods as well.
TODO:
test suite
introduction
hints
concepts that may be incomplete
@kotp Thanks for the suggestions, I have committed them both!
(I will get back to this eventually btw)
It's been 18 months since the last movement on this PR.
Does someone who was involved at the time have an idea of what it would take to get this over the finish line?
|
gharchive/pull-request
| 2021-03-08T02:27:24 |
2025-04-01T04:34:12.598777
|
{
"authors": [
"iHiD",
"kytrinyx",
"neenjaw"
],
"repo": "exercism/ruby",
"url": "https://github.com/exercism/ruby/pull/1111",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
124343204
|
Inconsistency in triangles test
There is some inconsistency in the tests for triangle exercise.
The tests do expect to throw an DomainError when all sides of the triangle are 0, but to return triangle::illegal when we have negative length sides or don't fullfil the triangle inequality.
To make this consistent, we should either throw something in all three cases or return triangle::illegal in all cases.
To line up with other tracks that support some kind of throwing, I think we should throw in every case and get rid of triangle::illegal.
This seems like a good idea to me. Pull requests are welcome :smile_cat:
|
gharchive/issue
| 2015-12-30T12:46:51 |
2025-04-01T04:34:12.607431
|
{
"authors": [
"LegalizeAdulthood",
"NobbZ"
],
"repo": "exercism/xcpp",
"url": "https://github.com/exercism/xcpp/issues/59",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
119325478
|
Add new exercise accumulate
As described in #94
Only one left for tonight!
Great job @matthewmorgan!
Killin' it! This is great.
@kytrinyx I love your encouraging phrases. The most imaginative I usually come up with is a plain Thanks. I think I need to build a list and I pick one at random.
I'm sure there's a bot for that :)
I just get really excited to see so much activity in a track that has been practically orphaned for so long. The two of you have a really great rhythm going--good discussions and lots of really great work. It is lovely to see.
Yeah, I'm enjoying it a lot.
@kytrinyx I looked for a bot but didn't find it!
@rchavarria Thanks to both of you-- having fun and learning a lot. 👊
:)
It's not exactly a bot, and it doesn't generate the most appropiate compliments for Github contributions, but it's fun: ComplimentBot 4000
Hah. All your colleagues miss you when you call in sick.
|
gharchive/pull-request
| 2015-11-29T00:01:57 |
2025-04-01T04:34:12.611157
|
{
"authors": [
"kytrinyx",
"matthewmorgan",
"rchavarria"
],
"repo": "exercism/xecmascript",
"url": "https://github.com/exercism/xecmascript/pull/95",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
177635217
|
Move hints from test suites and stub solutions to HINTS.md
Currently we have some exercises with hints as comments in the test suite and/or in the stub solution.
Hints in the stub solutions are convenient - users are almost forced to read them - but proved to be a mess, because most users submit the code with the comments.
Hints in the test suite are not that bad, but they force the users to inspect it. I think that, ideally, users should get feedback running the tests, not studying them.
Anyway, considering that the contents of HINTS.md is automatically included in the README.md, it is the perfect place for hints. We just need to make it happen!
All the exercises that already have a HINTS.md file share the same formatting,
## Hints
so we are using this as a standard for now.
This issue will track the migration's progress as soon as we have a complete list of exercises to be changed.
Tracking changes
[x] allergies #324
[x] bank-account #325
[x] binary-search-tree #329
[x] clock #330
[x] custom-set #331
[x] forth #343
[x] go-counting #344
[x] grade-school #332
[x] lens-person #381 (comments removed when ported to hspec)
[x] linked-list #333
[x] matrix #334
[x] meetup #335
[x] octal #383
[X] pov (nothing to fix)
[x] queen-attack #336
[x] rna-transcription #382 (comments removed)
[x] robot-name #337
[x] robot-simulator #338
[x] sgf-parsing #300 (fixed when ported to hspec)
[x] simple-linked-list #339
[x] space-age #340
[x] sublist #341
[x] trinary #384
[x] wordy #342
[x] zipper #385 (comments removed when ported to hspec)
Hints' migration to HINTS.md files finished. :smile:
|
gharchive/issue
| 2016-09-18T07:16:21 |
2025-04-01T04:34:12.618877
|
{
"authors": [
"rbasso"
],
"repo": "exercism/xhaskell",
"url": "https://github.com/exercism/xhaskell/issues/302",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
133206305
|
Change version pinning to only use minor versions
Instead of pinning to an exact release (X.Y.Z) this way we pin to a minor version which will include the bug-fix releases automatically.
As requires.io detected the first update, I thought we improve the version pinning a bit. Pinning to minor versions should be enough.
This looks good to me. I suppose that technically patch releases could go above 99, but it seems like that is unlikely to happen (and if it does we can fix it manually).
|
gharchive/pull-request
| 2016-02-12T10:42:53 |
2025-04-01T04:34:12.620506
|
{
"authors": [
"behrtam",
"kytrinyx"
],
"repo": "exercism/xpython",
"url": "https://github.com/exercism/xpython/pull/308",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
102065127
|
Fix timezone error in meetup
Don't merge, since this doesn't fix anything yet.
The meetup test fails when run like this:
TZ=America/Chicago bin/check-exercises.sh
[x] fix style (https://github.com/exercism/xracket/pull/5#issuecomment-132736968)
[ ] make travis fail (https://github.com/exercism/xracket/pull/5#issuecomment-132737618)
[ ] fix meetup so that travis doesn't fail
Found it. The problem is that your use of seconds->date is also doing local timezone conversion. Pass #f as the second argument and it passes fine. I also have some other changes to the tests to make them more idiomatic. I'll try to figure out how to do a PR on your PR. :)
Added mbertheau/xracket#1
@exercism/lisp Would one of you have a moment to review this, please?
I've kicked off CI again.
@mbertheau ping. can you merge my PR to your PR?
I'll give this another week or so, and then if necessary I'll submit my own PR to supplant this one.
@zenspider I'm busy with other things, please make a new PR :)
Thanks!
Will do. Thanks!
|
gharchive/pull-request
| 2015-08-20T05:25:15 |
2025-04-01T04:34:12.624994
|
{
"authors": [
"kytrinyx",
"mbertheau",
"zenspider"
],
"repo": "exercism/xracket",
"url": "https://github.com/exercism/xracket/pull/9",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
151644498
|
Passing a tuple to new in Queen attack exercise feels weird
Passing a pair to a new function feels unidiomatic.
There is a discussion started on the site:
http://exercism.io/submissions/05c66333b1b44c12a224e8fe4884a50d
We can continue here.
For me personally I think y'all have convinced me. Passing two tuples to a function might make sense to show the more logical grouping, but a single tuple seems an unnecessary extra level of grouping (and I still believe that despite the fact that you can destructure in the argument list)
Here was my thought process when making that a tuple.
A co-ordinate on the board is the same as a point on a grid.
A point on a grid is the canonical example of a (data clump)[http://martinfowler.com/bliki/DataClump.html]
You get rid of data clumps by encapsulating them.
The simplest way to do that in this exercise was with a tuple.
I don't quite follow the argument that passing in a single tuple is odd. This could be an idiomatic thing in Rust (or systems languages) that I'm unfamiliar with. I feel the same way about passing tuples into new. Seems fine to me, but there may be an idiomatic reason to not do so.
Also, from a design perspective, one of the more interesting things about the current Queen Attack is what you do with the tuple once you pass it in. Yes, you can just use it as a tuple, or you can encapsulate it, name it and give it behavior
To me it sounds like there are two points of view that make sense based on the context.
In isolation, one may see the tuple as an unneeded extra level of grouping. It's possible to say "if all the Queen tests are just testing queens with certain ranks and files that are sourced form somewhere we need not care about, why should it be that they values passed to us get packed up in a tuple? Especially if I'm just going to have to unpack the tuple immediately to operate on its two members anyway?"
On the other hand, as part of a larger system that may pass coordinate points around, tuples make sense if tuples are the representation of the coordinate points (and they indeed are a very reasonable representation).
If I had a list of coordinates that I wanted to turn into queens, it's likely that I would want to have them as a list of (i8, i8), rather than two lists of i8.
And only if Queen::new takes a single (i8, i8) can you do something like Queen::new(give_me_some_coordinates()) (obviously give_me_some_coordinates() would be some function that gives you an (i8, i8)). I currently do not know of a way to make this work if Queen::new was (rank: i8, file: i8), and my attempts on the playground were unsuccessful; I don't think Rust has a splat operator that will splat the tuple in in that case.
Another potential thought: Maybe I didn't want to internally represent a position as a tuple! Notice that earlier I said (with emphasis added):
tuples make sense if tuples are the representation of the coordinate points
What if the conditional in that sentence were false? What if I wanted to represent my position as a struct with named members instead of a tuple? I'm out of luck, it has to be a tuple since that's what Queen::new expects.
If the exercise would separate out the "Create and validate a position given a rank and file" versus "Given a queen at a certain position, can it attack a queen at this other position", we could envision a world where students are free to choose whatever internal representation of position makes sense. My memory is getting a bit fuzzy, but I think that was one of the iterations considered when Queen Attack was implemented for Rust but there was a concern about - how do we order the tests in a good way to allow the student to get to the first passing test quickly and iterate quickly from there?
I'll review the discussion around the initial implementation and see if I get any ideas.
we could envision a world where students are free to choose whatever internal representation of position makes sense
That's the winning argument as far as I'm concerned. (Of course, I wouldn't be surprised if you had an argument tomorrow that convinced me of the opposite, but still. This is a good one.)
the tests would get a bit more verbose
I'm personally OK with that, if it allows more freedom at the level of the implementation.
we could envision a world where students are free to choose whatever internal representation of position makes sense
That's the winning argument as far as I'm concerned. (Of course, I wouldn't be surprised if you had an argument tomorrow that convinced me of the opposite, but still. This is a good one.)
I'm not sure I follow. How would this look? Since the tests would include functions with specific signatures, I don't see how students could choose their own internal representations.
Yeah, you've essentially got it. Note that, whereas currently Queen::new returns a Result, I would think ChessCoord (which I might bikeshed as Position, but eh) return a Result. Queen::new would take an unconditional ChessCoord and unconditionally return a Queen, so the assumption is ChessCoords can only hold valid chess coordinates.
Coord is a terrible name, I just threw it there for an example. I can put together a sample of this and we can see if we like it.
@petertseng When you say that Queen::new takes an unconditional Position, I'm not sure exactly what you mean. Do you think the tests will look like:
fn test_queen_creation() {
let position = ChessPosition::new(1,2);
let queen = Queen::new(position.unwrap());
//etc.
}
When you say that Queen::new takes an unconditional Position, I'm not sure exactly what you mean. Do you think the tests will look like:
Yup, this tells me I should accompany my suggestions with code (I would have were I not otherwise occupied), but you do have the right of it.
What do you think, @ijanos?
I am usually cautious about speaking for others, but notice the thumbs up on https://github.com/exercism/xrust/issues/118#issuecomment-215800847 and who it comes from
Sorry for the late response, I'm from Europe and I guess that is responsible for the longer delays between messages, you are sleeping while I'm awake an vice versa :)
@IanWhitney I like your proposed code, I think it is a better API for this exercise.
BTW: I mentioned this conversation in today's "Behind the Scenes" newsletter. http://tinyletter.com/exercism/letters/exercism-it-s-about-the-conversations
|
gharchive/issue
| 2016-04-28T13:42:50 |
2025-04-01T04:34:12.641597
|
{
"authors": [
"IanWhitney",
"ijanos",
"kytrinyx",
"petertseng"
],
"repo": "exercism/xrust",
"url": "https://github.com/exercism/xrust/issues/118",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1809811399
|
Dev
Added some small features
added argparse
readme update
FIX THAT GOD DAMN PRINT BUG
|
gharchive/pull-request
| 2023-07-18T12:18:13 |
2025-04-01T04:34:12.643446
|
{
"authors": [
"exersalza"
],
"repo": "exersalza/FivemCipherFinder",
"url": "https://github.com/exersalza/FivemCipherFinder/pull/7",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1009129331
|
Mainnet-beta Mint issue
Hello! I'm sure I did everything right. Everything was working fine in dev-net anyway but, I am getting this error when mint on mainnet;
Transaction simulation failed: Error processing Instruction 4: custom program error: 0x2d
Program 11111111111111111111111111111111 invoke [1]
Program 11111111111111111111111111111111 success
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA invoke [1]
Program log: Instruction: InitializeMint
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA consumed 2390 of 200000 compute units
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA success
Program ATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knL invoke [1]
Program log: Transfer 2039280 lamports to the associated token account
Program 11111111111111111111111111111111 invoke [2]
Program 11111111111111111111111111111111 success
Program log: Allocate space for the associated token account
Program 11111111111111111111111111111111 invoke [2]
Program 11111111111111111111111111111111 success
Program log: Assign the associated token account to the SPL Token program
Program 11111111111111111111111111111111 invoke [2]
Program 11111111111111111111111111111111 success
Program log: Initialize the associated token account
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA invoke [2]
Program log: Instruction: InitializeAccount
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA consumed 3449 of 164402 compute units
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA success
Program ATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knL consumed 39696 of 200000 compute units
Program ATokenGPvbdGVxr1b2hvZbsiqW5xWH25efTNsLJA8knL success
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA invoke [1]
Program log: Instruction: MintTo
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA consumed 2879 of 200000 compute units
Program TokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA success
Program cndyAnrLdpjq1Ssp1z8xxDsB8dxe7u4HL5Nxi2K5WXZ invoke [1]
Program 11111111111111111111111111111111 invoke [2]
Program 11111111111111111111111111111111 success
Program metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s invoke [2]
Program log: Instruction: Create Metadata Accounts
Program log: Transfer 5616720 lamports to the new account
Program 11111111111111111111111111111111 invoke [3]
Program 11111111111111111111111111111111 success
Program log: Allocate space for the account
Program 11111111111111111111111111111111 invoke [3]
Program 11111111111111111111111111111111 success
Program log: Assign the account to the owning program
Program 11111111111111111111111111111111 invoke [3]
Program 11111111111111111111111111111111 success
Program log: Share total must equal 100 for creator array
Program metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s consumed 36981 of 174972 compute units
Program metaqbxxUerdq28cj1RbAWkYQm3ybzjb6a8bt518x1s failed: custom program error: 0x2d
Program cndyAnrLdpjq1Ssp1z8xxDsB8dxe7u4HL5Nxi2K5WXZ consumed 200000 of 200000 compute units
Program cndyAnrLdpjq1Ssp1z8xxDsB8dxe7u4HL5Nxi2K5WXZ failed: custom program error: 0x2d
what could cause this?
thank you so much for info. I forgot to set it
@justinpezzack Also another question I want to ask; How can I withdraw sol from my Token account to Owner account?
|
gharchive/issue
| 2021-09-28T03:39:43 |
2025-04-01T04:34:12.645498
|
{
"authors": [
"MelandriST"
],
"repo": "exiled-apes/candy-machine-mint",
"url": "https://github.com/exiled-apes/candy-machine-mint/issues/86",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
507152912
|
500 Server Error on FastCGI
40 FastCGI sent in stderr: "PHP message: Argument 1 passed to Model\Universe\SystemModel::Model\Universe{closure}() must be an instance of Model\Universe\object, instance of stdClass given [/var/www/pathfinder/pathfinder/app/main/model/universe/systemmodel.php:146]
Will check details and update...
Thx,
-Micky
Had to comment the "object" type in the closure definition:
$data->shattered = count(array_filter($planetsData, function(/*object*/ $planetData){
return property_exists($planetData, 'type') &&
(strpos(strtolower($planetData->type->name), '(shattered)') !== false);
})) == count($planetsData);
Then it worked. Maybe that helps ...
Thank you !
-Micky
@der-micky Thanks for the report. Type hints for object was introduced in PHP 7.2 https://blog.tekmi.nl/php-7-2-and-object-typehint/
I´ll remove the type and keep 7.1 support for the next release.
|
gharchive/issue
| 2019-10-15T10:26:13 |
2025-04-01T04:34:12.648763
|
{
"authors": [
"der-micky",
"exodus4d"
],
"repo": "exodus4d/pathfinder",
"url": "https://github.com/exodus4d/pathfinder/issues/863",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
450873737
|
Be able to rollback upgrades
(Backup package.json to package.json.bak before --force upgrade)
or
git reset, rimraf node_modules and re-run npm install
A better strategy might be to remember the git commit hash before starting the upgrade and rollback using git commands. This is partially implemented in #34, but not the interesting part of remembering the git commit hash to rollback to.
|
gharchive/issue
| 2019-05-31T16:10:11 |
2025-04-01T04:34:12.662701
|
{
"authors": [
"duluca"
],
"repo": "expertly-simple/angular-evergreen",
"url": "https://github.com/expertly-simple/angular-evergreen/issues/14",
"license": "ISC",
"license_type": "permissive",
"license_source": "github-api"
}
|
147392100
|
import type * as ExRoute from './ExRoute';
I'm trying to make a bundle with babel + webpack, and I'm constantly getting this unexpected token error:
ERROR in ./~/@exponent/react-native-navigator/ExNavigator.js
Module parse failed: /Users/Arbor/Desktop/ArborMobileApp/backend/node_modules/@exponent/react-native-navigator/ExNavigator.js Unexpected token (21:12)
You may need an appropriate loader to handle this file type.
| import * as ExNavigatorIcons from './ExNavigatorIcons';
|
| import type * as ExRoute from './ExRoute';
|
| export default class ExNavigator extends React.Component {
@ ./logic/initialize.js 14:175-218
The problem is, I don't know which babel plugin to include in order to solve this problem. Here is my .babelrc file:
{
"presets": ["react-native"],
"plugins": ["transform-class-properties"]
}
I used "babel-preset-react-native" to enable all the es features used by react, and I also added"babel-plugin-transform-class-properties" in order to support static class properties.
Please help! Thanks.
This "import type *" thing looks like Flow annotations, could you please tell me which babel transforms did you use to bundle and run this code? There is no .babelrc file in this repo so I cannot figure it out by myself, or dependencies set in package.json..
That is Flow syntax. Search the Babel site for "flow" or grep the babel code base and I think you'll be pointed in the right direction.
I was able to resolve it with. Development server restart as mention on this post
https://www.npmjs.com/package/babel-preset-react-native-stage-0
|
gharchive/issue
| 2016-04-11T11:02:56 |
2025-04-01T04:34:12.897053
|
{
"authors": [
"anupkale1984",
"ide",
"pavlelekic"
],
"repo": "exponentjs/ex-navigator",
"url": "https://github.com/exponentjs/ex-navigator/issues/107",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2198015017
|
"fileURLToPath" is not exported by "__vite-browser-external", imported by "node_modules/astro-expressive-code/dist/index.js".
I'm currently building an Astro theme for documentation. It has support for mdx files.
When I ran npm run build I got an error:
https://prnt.sc/3zftl5zYf2z4
The problem is in astro-expressive-code package, because when I removed it I could build the app normally.
Additional Info:
WIndows 10
Node version: 18.16.0
Package.json: https://prnt.sc/BYWZOh_Oo46p
Astro config: https://prnt.sc/1kvFjT1fY5YW
Example markdown file from project (in case I'm not using the package in the right way):
https://prnt.sc/zQ7Pce3JPkkl,
https://prnt.sc/ejzM2aFSET2q
Hello! Could you maybe share the link to your repo? I cannot reproduce this issue with the given information.
I assume that you're having an issue in your repo with how you are importing content. The error messages looks as if server-side scripts end up in your client-side bundle. This can happen if you accidentally import server-side code (like Content Collection APIs from astro:content) inside the content of MDX files, or inside the HTML template part of Astro files.
Hi Tibor, I've sent you an invite link to the repo.
I think I know what's wrong. Inside both src/components/navigation/Nav.astro and src/components/navigation/MobileNav.astro, there is a function called getDocs where inside switch statement I'm getting all markdown files frontmatter with Astro.glob(), and then returning title, descirption, and url.
Then inside both files, I'm passing that docs array to a React component called Search.tsx
I don't have any idea how to implement search in a different way than this. Do you have any ideas?
Thank you for the invite! I had a look at the repo and found the location where you're importing server-side code in a client script:
In your src/layouts/Base.astro, you have a client-side <script> that contains the following:
import {
LIGHT_MODE_CODE_BLOCK_THEME,
DARK_MODE_CODE_BLOCK_THEME,
} from '@/config'
In the imported src/config.ts, you have the following statement:
import { type ThemeObjectOrShikiThemeName } from 'astro-expressive-code'
This is a tricky one. This syntax imports the type, AND runs any base code from the module (if any). This is why it gets bundled into the client-side. You need to replace it with the following slightly different syntax:
import type { ThemeObjectOrShikiThemeName } from 'astro-expressive-code'
This will truly only import the type and not bring in the entire backend code into your client bundle.
It works now! Thank you so much :))))))))))))))))
|
gharchive/issue
| 2024-03-20T16:43:56 |
2025-04-01T04:34:12.915895
|
{
"authors": [
"ekmas",
"hippotastic"
],
"repo": "expressive-code/expressive-code",
"url": "https://github.com/expressive-code/expressive-code/issues/179",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
138074732
|
Exposing session variables to template.
This is a request for a change I'd like to see in Express. It exposes session variables to the template engine.
Currently the template engine is passed a map of variables obtained by combining the variables of app.locals, res.locals, and those passed directly to res.render. In the case of conflicts, variables of res.locals override app.locals, and variables passed to res.render override both. The template cannot reference session variables directly; they must be explicitly copied into res.locals or into the map passed to res.render.
This change adds the properties of the req.session object to the variables map passed to the template engine so that they may be referenced directly by the template. In the case of conflicts, variables of req.session override those of app.locals, but variables of res.locals and those passed to res.render override those of app.session. FYI: this is consistent with the behavior of JSP. The idea is that app.locals holds global variables, req.session holds variables specific to the user, res.locals holds variables specific to the request, and variables specific to the template are passed to res.render.
Furthermore, all four variable maps are exposed through variables _application for app.locals, _session for req.session, _request for res.locals, and _template for variables passed to res.render. This allows explicit name-conflict resolution (and, again, follows the behavior of JSP).
This change does not require req.session to exist; in the case where it doesn't, no session variables will be added to the map. Note that all enumerable properties of the session are exposed. In the case of express-session, this would include object methods such as save, reload, and destroy. I have submitted a separate pull request to express-session that would make all such methods non-enumerable.
This change does have the potential to break existing applications in rare cases where there is a conflict between a session variable and a variable in app.locals. Prior to the change the variable name would result in the value from app.locals, after the change it will result in the value from req.session. This can be fixed in the template by explicitly referencing the desired scope (e.g., _application.x instead of just x). However, if this is a concern, a configuration option could be used to determine whether or not session variables are exposed to the template engine.
This change uses res.req to access the request object via the response object in order to access the session object. This property is not listed in the official API documentation. If there are plans to remove that property, an alternative approach to accessing the session would be required.
Thanks.
Thanks for bringing us these ideas, @gfoust! I have a couple asks real quick:
Can you please split this request into the two discrete requests I see here, so the discussions on the two points can happen independently, as well as allow us to accept one of them before both are fleshed out? The two discrete ideas I see here are mixing in of req.session and providing underscore-prefixed values for merge resolutions by the view?
The property req.session is hard-coded in this pull request, but that is only from convention by a few other modules, while other session modules for Express out there either also allow you to choose any property for the session by configuration, or use their own property name altogether (typically for conflict resolution between modules). If we are going to mix in objects on properties not set by Express core itself, perhaps it should be in some generic fashion, where a user can choose to add req.session to the mix (or even req.fooBar)?
To build on top of what Doug said, seems like it might be better to keep the res.session part out of express core and open an issue to make this configurable in the standard session package. Then you would just be able to do something like:
app.use(session({
sessionKey: 'res.locals.session'
}));
** the above is just a quick and dirty example, there is probably a better way to do that.
Where the above would just set the session right where you need it instead of adding more code to express core make it happen.
I don't mind splitting it into two requests, but I'm a little unsure as how to proceed since one of those pull requests will have to be based on the other. Can I make a pull request that depends on another pending pull request? (Sorry, I'm new at this.)
To continue the discussion on configuration: suppose each request had some sort of "variables stack"---an array of variable maps. At the beginning of the request the stack might contain just app.locals; calling res.render might result in pushing first res.locals, then the variables passed to res.render. Then the stack gets flattened into a single variable map---with maps higher-up in the stack overriding maps lower-down---and passed to the template engine.
So, ultimately every variable stack would begin with apps.locals and end with res.locals and the variables passed to res.render. In between, other middleware could add variable maps to the stack. So, e.g., when the express-session middleware is triggered, it could first create req.session, then push it onto the variables stack. Other middleware could likewise push variables onto the stack; the order of execution for the middleware would affect which variables get overridden.
+1 Thanks for bringing us these ideas, @gfoust!
|
gharchive/pull-request
| 2016-03-03T04:48:59 |
2025-04-01T04:34:12.927392
|
{
"authors": [
"dougwilson",
"gfoust",
"kelthenoble",
"wesleytodd"
],
"repo": "expressjs/express",
"url": "https://github.com/expressjs/express/pull/2924",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
752986021
|
Documenting req.route in relation to route handlers vs middleware
This request for docs comes from expressjs/express#4193, where the person is trying to understanding why req.route is undefined.
The answer in response wrote:
That is a distinguishing feature between middlewares and routes; routes (like app.all) have a route (visible in req.route) and middlewares do not have a route.
I encountered a similar error to the person who raised the issue, and although I understand the high-level differences between middleware and a route handler, it hadn't occurred to me that the shape of the req object is different within a route handler vs within a middleware.
I believe the docs would benefit by explaining this as explicitly as the responder did in that issue thread.
Same here. Please update the docs, I also wasted a lot of time trying to figure out what's wrong..
|
gharchive/issue
| 2020-11-29T19:16:27 |
2025-04-01T04:34:12.930006
|
{
"authors": [
"arnaudoff",
"womcauliff"
],
"repo": "expressjs/expressjs.com",
"url": "https://github.com/expressjs/expressjs.com/issues/1227",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
191142343
|
Add Node Interactive details
WORK IN PROGRESS, DO NOT MERGE!
You can take a look at what's coming up, on this PR/branch.
@expressjs/express-tc ok, this is ready to be reviewed and merged. Tested on Firefox, Chrome, and Safari. Optimized for mobile devices. It should most likely be fine on Edge too.
Apart from adding the Node Interactive section, I have cleaned up the footer, and added the current version number next to the "Express" header.
@crandmck It would be great if we can get it reviewed and merged today in your morning.
Corresponding issue: https://github.com/expressjs/expressjs.com/issues/737
LGTM, thanks @hacksparrow
I'm going to create an issue to remind us to remove this after the conference. :-)
|
gharchive/pull-request
| 2016-11-22T22:30:24 |
2025-04-01T04:34:12.932874
|
{
"authors": [
"crandmck",
"hacksparrow"
],
"repo": "expressjs/expressjs.com",
"url": "https://github.com/expressjs/expressjs.com/pull/740",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
253101788
|
ES2015 standards support
#167
hello, i'd like to help , but support for ES2015 is about to change, var for const and let ? it's possible to think something with es7 and js generated by babel ? or I'm out of reality?
Closing since OP never updated the PR (or responded) to the raised concerns. If OP (or anyone) wants to address, please feel free to open a new PR with the fixes 👍
|
gharchive/pull-request
| 2017-08-26T15:36:25 |
2025-04-01T04:34:12.934239
|
{
"authors": [
"dougwilson",
"sisisin",
"webmobiles"
],
"repo": "expressjs/generator",
"url": "https://github.com/expressjs/generator/pull/170",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
263496933
|
Add support to prefix
It will allow to set a prefix and allow to run a server index behind a proxy for example
I am going to fix the issues with old node versions.
|
gharchive/pull-request
| 2017-10-06T16:07:47 |
2025-04-01T04:34:12.935063
|
{
"authors": [
"rodrigowirth"
],
"repo": "expressjs/serve-index",
"url": "https://github.com/expressjs/serve-index/pull/66",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
849311696
|
Can R be called from Rust?
Say I wanted to use qnorm() in Rust. Is it possible to expose the functions from stats::* in Rust cargo package?
This is probably more appropriate for the discord channel. I am closing.
|
gharchive/issue
| 2021-04-02T16:14:37 |
2025-04-01T04:34:12.936011
|
{
"authors": [
"git314"
],
"repo": "extendr/extendr",
"url": "https://github.com/extendr/extendr/issues/204",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2522974508
|
Fix issue with --user-data-dir
Fixes https://github.com/extension-js/extension.js/issues/176
I don't have permissions to merge 😄
I gotchu
Available in v2.0.0-alpha.28
|
gharchive/pull-request
| 2024-09-12T17:35:01 |
2025-04-01T04:34:12.937574
|
{
"authors": [
"cezaraugusto",
"karaggeorge"
],
"repo": "extension-js/extension.js",
"url": "https://github.com/extension-js/extension.js/pull/179",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1726514933
|
feat: add SLIs to dashboard
Fixes #2301
This PR adds the SLIs documented here to the dashboard.
It shows:
reconciler error rate per CRD (including SecretStore)
webhook error rate + latency
reconciler total error rate and total latency
table of ExternalSecrets that are in Ready=false state
There are no metrics for SecretStore conditions, hence we can not draw a table with the failed SecretStores as requested in #2301. This could be a great enhancement - though out of scope.
@sagikazarmark, please take a look if you have some time as you have initially reported it. I looked what i can get out of the existing metrics and added the documented SLIs from our docs to the dashboard :pray:
/approve
Waiting for Mark to have a look tho :D
I'm going to merge this for now, please raise an issue if something is not working/missing
Sorry, I completely missed this one. I'm gonna take a look.
Looks great, thanks for making the change!
|
gharchive/pull-request
| 2023-05-25T21:30:33 |
2025-04-01T04:34:12.941447
|
{
"authors": [
"knelasevero",
"moolen",
"sagikazarmark"
],
"repo": "external-secrets/external-secrets",
"url": "https://github.com/external-secrets/external-secrets/pull/2360",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
222336183
|
Warn about collisions right before slicing
If there's a collision when trying to slice, put up a confirmation dialog.
Fixed by https://github.com/eyal0/OctoPrint-Slicer/tree/collision_detector_before_slice2
|
gharchive/issue
| 2017-04-18T08:13:52 |
2025-04-01T04:34:12.979406
|
{
"authors": [
"eyal0"
],
"repo": "eyal0/OctoPrint-Slicer",
"url": "https://github.com/eyal0/OctoPrint-Slicer/issues/4",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
715614590
|
Add a type declaration file for support typescript
A current use your lib on my project and I would like to use typescript, but there is no type declaration file.
Hi, to use vue-awesome-notifications in my typescript project, I declare the module in a modules.d.ts file like this: declare module 'vue-awesome-notifications'; and I declare $aws too in shims-vue.d.ts:
declare module 'vue/types/vue' {
interface Vue {
$awn: any
}
}
|
gharchive/issue
| 2020-10-06T12:13:34 |
2025-04-01T04:34:13.027801
|
{
"authors": [
"Pochwar",
"henry-ns"
],
"repo": "f3oall/vue-awesome-notifications",
"url": "https://github.com/f3oall/vue-awesome-notifications/issues/18",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
345902383
|
update syntax for parrot worker
updating parrot plugin worker to use ES6 syntax
added .spec file to allow rpmbuild (npm run build)
updated readme for parrot worker to show API and how to build
'class'y...
|
gharchive/pull-request
| 2018-07-30T19:29:54 |
2025-04-01T04:34:13.029108
|
{
"authors": [
"elv1s",
"npearce"
],
"repo": "f5devcentral/f5-rest-examples",
"url": "https://github.com/f5devcentral/f5-rest-examples/pull/14",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
2128136486
|
UI install not working
I am unable to install using 1) HACS link or 2) copy repository url into custom repositories in HACS UI. Only method working is manual cloning.
returns “ Repository faanskit/ha-checkwatt not found”
returns “ Repository 'faanskit/ha-checkwatt' exists in the store.” yet it is nowhere to be found, despite reboot etc.
On HAoS, odroid blue. All up to date.
Mimer-SVK integration works by method 2, for instance.
Hard to help with so little info. We have at minimum 20+ successful installations made via the button on ha-checkwatt. The method is used by ha-esolar with 100+ installations made.
Having said that, I'll check the suggested integration and reach out to @angoyd to see if he can find something.
Meanwhile, feel free to propose a solution and submit a PR.
homeassistant-svk-mimer uses a different, and more complex, installation method than ha-checkwatt.
We use a much simpler method. Just click this button and follow the instruction:
@kalaws , please report back else it will be closed with no action.
Sorry, I don’t have anything new to report. That link is what I tried. Very odd, I’ve installed many integrations successfully through such a link.
Can you please try to install it by klicking the button, or by clicking this link:
It will look like this and your URL to HA should be pre-filled:
You should not do this within Hacs ecosystem as proposed in the original report.
/Marcus
@kalaws how does it look if you look in hacs under integrations and Custom Repositories ?
i have the same problem.. when pressing the link it only ask if i want to add repository and then it shows unkown error
Closing due to inactivity.
|
gharchive/issue
| 2024-02-10T06:25:12 |
2025-04-01T04:34:13.035045
|
{
"authors": [
"angoyd",
"faanskit",
"kalaws",
"shqipesson"
],
"repo": "faanskit/ha-checkwatt",
"url": "https://github.com/faanskit/ha-checkwatt/issues/65",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
943497342
|
Fix segmentation fault on big message serialization
I'm not entirely sure why the original code crashes with SIGSEGV on some messages in my testing, but Variable-Length Arrays aren't generally standard C++ anyway and this fix also has the benefit of having one less copy of the serialized message.
Nice one, LGTM, cheers @kubasz !
|
gharchive/pull-request
| 2021-07-13T14:45:29 |
2025-04-01T04:34:13.036406
|
{
"authors": [
"Shillaker",
"kubasz"
],
"repo": "faasm/faabric",
"url": "https://github.com/faasm/faabric/pull/128",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1146629197
|
Multiple files support
Feature description
So far, we are just supporting types declared in one file. The plan will be to follow any import statement.
To solve different use cases, we should provide different resolving options:
"flat" -> all the dependencies are flatten in one output file (perfect for #30 usecase)
"multi" -> we have a 1-1 mapping between (perfect for #70 usecase)
Input
// bar.ts
import { Foo } from "./foo"
export type Bar {
foo: Foo
}
// foo.ts
export type Foo = number
Output (flat)
import { z } from "zod"
export const fooSchema = z.number()
export const barSchema = z.object({foo: fooSchema})
Output (multi)
// bar.zod.ts
import { z } from "zod"
import { fooSchema } from "./foo"
export const barSchema = z.object({foo: fooSchema})
// foo.zod.ts
import { z } from "zod"
export const fooSchema = z.number()
Related issues
#30 #70
Wondering if any work has been undertaken on this? Would potentially be be happy to spend sopme time on it.
This is extremely important because it currently limits the use of ts-to-zod to only the simplest files.
There's no way for users to produce a single file containing all the types you'd want to pass to ts-to-zod because the rollup functionality of api-extractor produces a .d.ts file. When tying to use a d.ts ts-to-zod silently fails, producing bad output by incorrectly including the declare keyword in the output.
Are there any updates on multifile support? I may be capable to develop this feature, but would like to discuss it first.
@fabien0102 Do you have any ideas on how this should be done?
I started something on my last plane trip but needed more time to make something usable.
It’s actually not an easy problem, the main challenge is to compute the dependencies tree.
I’m also not totally sure what to do if you have some types picked from node_modules for example. But keeping this edge case aside, the idea is:
Transforms all the import type statements to generated schema imports
List all the files used by the entry point, so we can add them to a generation queue
Make sure the type validator works (nice to have, but still)
Enjoy! 🎉
I had a quick look at the pull request and it looks like you're heading down the "build a bundler" route. Can I suggest to keep things simple that you keep ts-to-zod as a compiler only? This is how typescript compiler itself works, and does not provide bundling. It works because the output directory has a mirrored structure of the input directory.
Also not sure if it's helpful, but this is the script I've built using a glob pattern to produce a generated dir. I am temporarily replacing any imported identifiers with a string literal (a uuid) and after ts-to-zod has done it's things, I go back through and replace the z.liter("<uuid>") call expressions with the original identifier
https://gist.github.com/mattfysh/6a071d5b2150bdb6fb10be5be715402c
I had a quick look at the pull request and it looks like you're heading down the "build a bundler" route. Can I suggest to keep things simple that you keep ts-to-zod as a compiler only? This is how typescript compiler itself works, and does not provide bundling. It works because the output directory has a mirrored structure of the input directory.
Actually most of the work in this PR is to retrieve the relevant types from the import clauses and aggregate the schema in order not to modify the return of the generate function.
So the result of having all the schemas bundled in one file is more a convenience decision rather than an architectural one.
IMO, for a first iteration, this could be good enough.
I do agree with you that splitting the schemas up in multiple file would be a nice option to offer in the future.
To do so we would probably need to generate a dependency graph associating the paths to the relative schemas, coordinate the imports between files, and then dump everything to disk (adjusting integrations test, etc.).
It is certainly not as easy/linear as writing everything to a single file.
Also not sure if it's helpful, but this is the script I've built using a glob pattern to produce a generated dir. I am temporarily replacing any imported identifiers with a string literal (a uuid) and after ts-to-zod has done it's things, I go back through and replace the z.literal("<uuid>") call expressions with the original identifier
https://gist.github.com/mattfysh/6a071d5b2150bdb6fb10be5be715402c
Thanks for sharing, your script is interesting but it would need some polishing to be used in production.
Any update here? I saw a few PRs(#148, #135, #118) that appear to be related to this issue. This feature is really the one big thing holding us back from adopting ts-to-zod(and zod).
Great library by the way. Thanks for your work!
Quite a busy life those days, I will try to have a look when this is getting calmer. If one of those PR are working for you, please try them on your projects (the easiest is to clone the project, add your name as prefix in the package name and publish to npm 😉 )
Every feedbacks are appreciate :) Thanks for the support 😃
For some reasons, I had missed this issue so started working on 2 successives PRs:
https://github.com/fabien0102/ts-to-zod/pull/135 supports any import statement and will handle it as an third party import, outputting the same import statement in the generated file + a const importSchema = z.instanceof(importType) statement
https://github.com/fabien0102/ts-to-zod/pull/148 will add support for the multi case mentioned in this issue, but will not do it systematically for all imports, only for those referenced in the ts-to-zod.config.js file. I think it's a non-breaking good first step to handle zod file imports: one can decide to add it or not to the config, it's less intrusive than a global holistic approach.
Import support has been added to ts-to-zod in 3.7 (and fixed in 3.7.3 😅).
Right now, it relies on having all the files in the configuration files and generation must be ordered "manually".
Thanks for building this great package!
In our project, we automatically generate types for GQL queries adjacent to their definitions in __generated__/gql.generated.ts files. Now, I'm looking for a way to take these generated files, and additionally generate a __generated__/schemas.generated.ts file for each generated types file, which should contain zod schemas for all type definition that has been generated.
That way, we always have a zod schema available to parse GQL responses with — which we need specifically because we sometimes cache query results on redis, and don't necessarily want to blindly trust that the cached data has the required shape at runtime.
As-is, I understand that the only way to do this with this package would be to dynamically generate an ephemeral config that lists all the generated files explicitly, and discarding it after the zod types were generated. That's a bit convoluted. I was hoping that I could just configure the package to run for all files matching a glob, and an output filename relative to the matched input file's location.
Does this match your vision?
glob sounds like a nice idea
My vision for the next step (because that would ease my work 😅) was to generate for all files in a given directory (or set of files), with ts-to-zod being able to work out the right generation order based on a toposort of import dependencies.
I was hoping that I could just configure the package to run for all files matching a glob, and an output filename relative to the matched input file's location.
That would be an interesting next step: it would work out-of-the-box only for "independent" files. If the files matching the glob reference each other in a way, then validation would fail.
It would look something like ts-to-zod __generated__/*.generated.ts outputFolder/ ?
It would look something like ts-to-zod generated/*.generated.ts outputFolder/ ?
In our case, the files are spread all over the repo, because they're generated adjacent to the query definitions. So the glob would be something like src/**/__generated__/gql.generated.ts, and the output files would have to be named sth like schemas.generated.ts and placed next to the respective matched file.
If the files matching the glob reference each other in a way, then validation would fail.
Again in our case, the files don't reference each other, but they do reference a "global types file" which has the basic GQL types in it, like scalars etc. I'm not sure how unique this setup is, but it's the result of using graphql-codegen with the near-file-preset preset, which seems pretty popular.
The graphql codegen preset in question is here
... as I'm writing this, I'm starting to realize that having a graphql-codegen plugin that uses this package to transform types to schemas would probably be the neatest solution, and would offload all the complex glob matching logic to graphql-codegen itself. For our specific usecase at least.
|
gharchive/issue
| 2022-02-22T09:00:01 |
2025-04-01T04:34:13.056869
|
{
"authors": [
"anthony-dandrea",
"efstajas",
"fabien0102",
"fracalo",
"mattfysh",
"nlundquist",
"schiller-manuel",
"then3rdman",
"tvillaren"
],
"repo": "fabien0102/ts-to-zod",
"url": "https://github.com/fabien0102/ts-to-zod/issues/71",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
356111518
|
Ken Burns for images?
I want to have one image per slide, faded in and animated with ken burns effect (pan + zoom),
can I do this with Crelly slider? Should I assign the image as slide background image or
add the image as separate element to the slide (how?)?
Hi, unfortunately such effect is not available on Crelly Slider :(
|
gharchive/issue
| 2018-08-31T20:16:26 |
2025-04-01T04:34:13.058772
|
{
"authors": [
"fabiorino",
"strarsis"
],
"repo": "fabiorino/crelly-slider",
"url": "https://github.com/fabiorino/crelly-slider/issues/58",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
295959704
|
feat(git): Add possibility to use a 'secret' when creating a git hook
Where to find those in git apis:
config key to add secret for github "secret":
https://developer.github.com/v3/repos/hooks/#create-a-hook
url param to add secret for gitlab "token":
https://docs.gitlab.com/ee/api/projects.html#add-project-hook
Update tests in accordance.
Fixed version of #72, closes #59
Can one of the admins verify this patch?
test this please
@centos-ci retest this please
add to whitelist
@centos-ci retest this please
|
gharchive/pull-request
| 2018-02-09T18:08:31 |
2025-04-01T04:34:13.113777
|
{
"authors": [
"centos-ci",
"gastaldi",
"quintesse"
],
"repo": "fabric8-launcher/launcher-backend",
"url": "https://github.com/fabric8-launcher/launcher-backend/pull/74",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
134291877
|
Camel forge - Lets default to the current java route builder if its o…
…pen and current file in the gui editor.
[merge]
|
gharchive/pull-request
| 2016-02-17T14:18:52 |
2025-04-01T04:34:13.125814
|
{
"authors": [
"davsclaus"
],
"repo": "fabric8io/fabric8-forge",
"url": "https://github.com/fabric8io/fabric8-forge/pull/121",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
219820871
|
Create Iteration: Parent Dropdown broken
The parent dropdown needs more love:
it has the default value "null". Should be something like "None" in disabled (grey/italics) to indicate this is the "no parent" selector.
the dropdown can not be closed without selecting a value. Clicking on the down caret does not do anything.
on prod, I currently have an entry in the select box named "//Demo", with two "/" at the beginning.
the field is editable. It should not.
the down caret button is not flush with the input box border. The bottom has a gap.
most of the above applies to the dialog on the "plus" button as well as the "create child" dialog on the current iteration.
it has the default value "null". Should be something like "None" in disabled (grey/italics) to indicate this is the "no parent" selector. Fix in #1520
the down caret button is not flush with the input box border. The bottom has a gap. Fix in #1520
@michaelkleinhenz can you please explain this point?
the field is editable. It should not.
@michaelkleinhenz UX specifies the field to be a type ahead drop down.
Verified !
|
gharchive/issue
| 2017-04-06T08:20:54 |
2025-04-01T04:34:13.129584
|
{
"authors": [
"michaelkleinhenz",
"naina-verma",
"nimishamukherjee",
"vikram-raj"
],
"repo": "fabric8io/fabric8-planner",
"url": "https://github.com/fabric8io/fabric8-planner/issues/1523",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
90101647
|
Add quickstarts to vagrant when we have a release
Add quickstarts here
https://github.com/fabric8io/fabric8-installer/blob/master/vagrant/openshift-latest/Vagrantfile#L140
As it downloads from mvn central we need a release first
Done now
|
gharchive/issue
| 2015-06-22T13:42:37 |
2025-04-01T04:34:13.136287
|
{
"authors": [
"davsclaus"
],
"repo": "fabric8io/quickstarts",
"url": "https://github.com/fabric8io/quickstarts/issues/534",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
374064598
|
Stanford University's iOS course
Youtube link to the Stanford University's iOS course is also present, besides being on iTunes. Shall I add that as well?
Yes please do add this course.
Btw where is it present? In YouTube? Or where?
@swatisingh45 is the iTunes one less accessible on some platforms or something like that?
@saranshkataria @swatisingh45 yes the iTunes one is less accessible as people with android devices cannot access the iTunes tutorial -- therefore for the sake of group members using Android devices (= 95% of group members) who want to see tutorial on the go (say in metro) -- I request to please put the iOS tutorial on the group
@saranshkataria, @nsnsns is totally correct. Shall add the link below the iTunes link and submit a PR?
|
gharchive/issue
| 2018-10-25T18:02:09 |
2025-04-01T04:34:13.179741
|
{
"authors": [
"nsnsns",
"saranshkataria",
"swatisingh45"
],
"repo": "facebook-developer-circle-delhi/Community-Curated-Resources",
"url": "https://github.com/facebook-developer-circle-delhi/Community-Curated-Resources/issues/54",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
354540991
|
fix: transformation of url to cleanUrl / pretty url
Motivation
Fix #922 and https://github.com/babel/website/issues/1780
cc @hzoo
Changes
Pretty/cleanUrl should only remove html extension and not other extension
Stronger test for the getPath function that transform url to clean url.
cleanUrl of /react/index.html should be /react/ and not /react
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
//2018-08-27-7.0.0.md
---
layout: post
title: "Babel 7 Released"
author: Henry Zhu
authorURL: https://twitter.com/left_pad
date: 2018-08-27 18:00:00
categories: announcements
share_text: "Babel 7 Released"
---
After almost 2 years, 4k commits, over 50 pre-releases, and a lot of help we are excited to announce the release of Babel 7. It's been almost [3 years](https://babeljs.io/blog/2015/10/29/6.0.0) since the release of Babel 6! There's a lot of moving parts so please bear with us in the first weeks of release.
<!-- truncate -->
> If you appreciate the work we're doing on Babel, you can sponsor Babel on [Open Collective](https://opencollective.com/babel), support me on [Patreon](https://www.patreon.com/henryzhu), or get you or your company involved with Babel as part of work. We'd appreciate the collective ownership of this vital project in the JavaScript community!
## It's Happening! 🎉
Software is never going to be perfect but we're ready to ship something that's already been used in production for some time now! [`@babel/core`](https://www.npmjs.com/package/@babel/core) is already at 5.1 mil downloads/month because of its usage in tools like [Next.js 6](https://zeit.co/blog/next6), [vue-cli 3.0](https://medium.com/the-vue-point/vue-cli-3-0-is-here-c42bebe28fbb), [React Native 0.56](https://facebook.github.io/react-native/blog/2018/07/04/releasing-react-native-056), and even [Wordpress's frontend](https://github.com/Automattic/wp-calypso) 🙂!
## Babel's Role
I'd like to start this post by re-introducing Babel's [role](https://www.youtube.com/watch?v=fntd0sPMOtQ) in the JavaScript ecosystem over the last few years.
Header title URL should be correct now.
@endiliey thanks for the quick fix!
Awesome!
|
gharchive/pull-request
| 2018-08-28T01:58:15 |
2025-04-01T04:34:13.190547
|
{
"authors": [
"endiliey",
"existentialism",
"hzoo"
],
"repo": "facebook/Docusaurus",
"url": "https://github.com/facebook/Docusaurus/pull/923",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1878192412
|
Adding duplicate entries check in publish
Ensures that duplicate label entries cannot be submitted to Directory::publish successfully
Codecov Report
Patch coverage: 91.66% and project coverage change: +0.02% :tada:
Comparison is base (be1055e) 87.73% compared to head (4de9a4e) 87.75%.
:exclamation: Current head 4de9a4e differs from pull request most recent head 76bf50b. Consider uploading reports for the commit 76bf50b to get more accurate results
:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@ Coverage Diff @@
## main #400 +/- ##
==========================================
+ Coverage 87.73% 87.75% +0.02%
==========================================
Files 39 39
Lines 8771 8803 +32
==========================================
+ Hits 7695 7725 +30
- Misses 1076 1078 +2
Files Changed
Coverage Δ
akd/src/errors.rs
3.64% <0.00%> (-0.06%)
:arrow_down:
akd/src/tests.rs
95.46% <95.00%> (-0.01%)
:arrow_down:
akd/src/directory.rs
83.51% <100.00%> (+0.23%)
:arrow_up:
... and 1 file with indirect coverage changes
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Lgtm
|
gharchive/pull-request
| 2023-09-02T00:08:42 |
2025-04-01T04:34:13.199749
|
{
"authors": [
"codecov-commenter",
"kevinlewi",
"slawlor"
],
"repo": "facebook/akd",
"url": "https://github.com/facebook/akd/pull/400",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
1667469038
|
Make rustc configurable
This makes the built-in system rust toolchain configurable, matching system_python_toolchain:
https://github.com/facebook/buck2/blob/main/prelude/toolchains/python.bzl#L75
I need this personally because I want to use a toolchain from rustup instead of my real system toolchain, but I don't want to manually configure the toolchain
I'll just use rustup override
|
gharchive/pull-request
| 2023-04-14T03:56:59 |
2025-04-01T04:34:13.208586
|
{
"authors": [
"bigfootjon"
],
"repo": "facebook/buck2",
"url": "https://github.com/facebook/buck2/pull/167",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
}
|
83599597
|
Use register aliases
:warning: I haven't tested this on arm :warning:
Use lldb's register aliases instead of specific architecture register names. The main reason for this change is that some commands, like bmessage, will print out the results that include the output of these functions. I think it would be beneficial to surface the aliases to users, to spread their existence and availability.
Todo:
[ ] Test on arm32
[ ] Test on arm64
Depends on #97
We should ship this. @kastiglione did you check it works on ARM yet?
Thanks for the ping, will put this on my todo list.
|
gharchive/pull-request
| 2015-06-01T16:49:51 |
2025-04-01T04:34:13.210710
|
{
"authors": [
"kastiglione",
"mattjgalloway"
],
"repo": "facebook/chisel",
"url": "https://github.com/facebook/chisel/pull/98",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
64155351
|
Conceal Help
I'm currently working on a project and i've been tasked to make sure the contents/data inside the apk is secure from been accessed by users, i'm been research for a couple of days now and i finally find this library, please do you think this will provide solution for this task (Encrypting the data, so user will not have access to it), if not? is there any alternative...? (i'll appreciate your suggestion). lastly. To encrypt data with this library? data must be on SD card or inside the internal memory?
Any data you give to the user in the APK and that you need to use locally for other purposes will always be accessible to the user, you can't prevent it. With conceal you can encrypt data anywhere, but encrypting data in the internal memory does not seem that useful to me. I don't know what your application is or what your threat model is, so I can't make specific recommendations.
@siyengar appreciate, actually the data to be encrypted is bundle with the apk and its upto 400MB which reside on assets folder, no plan to put it on Google play because it will be distribute on a android phone for an organisation from the factory. i need to find a way to encrypt the data, so when user have access to it... it'll be useless because this are high level data that must be secure and they want this data offline. I know any data given to the user in the apk can be accessed but i need to find a way to make the data useless when they have access to it.. only the application will be able to read it!
|
gharchive/issue
| 2015-03-25T02:42:32 |
2025-04-01T04:34:13.213044
|
{
"authors": [
"samsoft00",
"siyengar"
],
"repo": "facebook/conceal",
"url": "https://github.com/facebook/conceal/issues/65",
"license": "bsd-3-clause",
"license_type": "permissive",
"license_source": "bigquery"
}
|
432993321
|
scss @import directive doesn't work
I am triying yo use @import directive but it does't work with: "react-scripts": "2.1.8"
I follow this steps: https://facebook.github.io/create-react-app/docs/adding-a-sass-stylesheet
I have two files: App.scss and _vars.scss both into the src folder. When I import _vars.scss into App.scss I get this error:
Failed to compile.
./src/App.scss (./node_modules/css-loader??ref--6-oneOf-5-1!./node_modules/postcss-loader/src??postcss!./node_modules/sass-loader/lib/loader.js??ref--6-oneOf-5-3!./src/App.scss)
.App {
^
Media query expression must begin with '('
in /Users/farv/repos/pr-components/src/App.scss (line 3, column 1)
// App.scss
@import 'var.scss'
.App {
text-align: center;
}
....
//_vars.scss
$colorRed: 'red'
Was my foult because I forget to add ";" at the end of the @import line. This is working fine:
// App.scss
@import 'var.scss';
.App {
text-align: center;
}
....
//_vars.scss
$colorRed: red
|
gharchive/issue
| 2019-04-14T15:37:02 |
2025-04-01T04:34:13.215593
|
{
"authors": [
"pacorampas"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/6819",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
437752190
|
Space in folder names of local create-react-app copy fails new project creation
previous issues closed (https://github.com/facebook/create-react-app/issues/5963 https://github.com/facebook/create-react-app/issues/1652) but I am still getting this error
yarn create v1.15.2
[1/4] Resolving packages...
[2/4] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Installed "create-react-app@3.0.0" with binaries:
- create-react-app
'C:\Users\Tarek' n’est pas reconnu en tant que commande interne
ou externe, un programme exécutable ou un fichier de commandes.
error Command failed.
Exit code: 1
Command: C:\Users\Tarek BAZ\AppData\Local\Yarn\bin\create-react-app
Arguments: qanoun-tech_doc-search-web
Directory: C:\Users\Tarek BAZ
Output:
info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command.
Working for me.
Windows 10
C:\Users\Saibamen\Desktop\test 6923>npx create-react-app my-app
npx: installed 91 in 16.805s
Creating a new React app in C:\Users\Saibamen\Desktop\test 6923\my-app.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts...
yarn add v1.13.0
(not important)
Done in 93.83s.
Initialized a git repository.
Success! Created my-app at C:\Users\Saibamen\Desktop\test 6923\my-app
Inside that directory, you can run several commands:
(not important)
Happy hacking! (the most important :D)
I would never use spaces in file or folder names. It doesn't translate well to Unix environments because it's not allowed.
While you may be working in Windows, I would suggest never assuming your code will stay in Windows.
|
gharchive/issue
| 2019-04-26T16:31:17 |
2025-04-01T04:34:13.218278
|
{
"authors": [
"Saibamen",
"methodbox",
"terryBaz"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/6923",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
487284607
|
console.error node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/virtual-console.js:29
During writing of unit testing. i'm facing following warning and error.
` console.error node_modules/react-dom/cjs/react-dom.development.js:545
Warning: An update to Query inside a test was not wrapped in act(...).
When testing, code that causes React state updates should be wrapped into act(...):
act(() => {
/* fire events that update state */
});
/* assert on the output */
This ensures that you're testing the behavior the user would see in the browser. Learn more at https://fb.me/react-wrap-tests-with-act
in Query (at CustomFields/index.js:109)
in CustomFieldsQyery (at CustomFieldsQyery.test.js:25)
in ApolloProvider (created by MockedProvider)
in MockedProvider (created by WrapperComponent)
in WrapperComponent
console.error node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/virtual-console.js:29
Error: Uncaught [TypeError: Cannot read property 'additionalData' of undefined]
`
Same issue!!!
Do you think this error message isn't correct or do you not understand what it means?
Fixed.
|
gharchive/issue
| 2019-08-30T04:51:07 |
2025-04-01T04:34:13.220927
|
{
"authors": [
"heyimalex",
"marco476",
"vineet-agrawal96"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/7610",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
555187550
|
create-react-app doesn't generate public and src folders thus cannot get started
create-react-app doesn't generate public and src folders thus cannot get started.
I am create react project using below steps:
npx create-react-app my-app
cd my-app
npm start
Versions:-
"Node": 10.14.2
"npm": 6.13.4
Dependencies
"react": "^16.12.0",
"react-dom": "^16.12.0",
"react-router-dom": "^5.1.2",
"react-scripts": "3.3.0"
Steps:
remove create-react-app using npm uninstall -g create-react-app
and check then also exist do rm -rf /usr/local/bin/create-react-app
then do npx create-react-app my-app
@sirshikher About the second step i am in windows :)
and check then also exist do rm -rf /usr/local/bin/create-react-app
How to do that in Windows ?
@sirshikher About the second step i am in windows :)
and check then also exist do rm -rf /usr/local/bin/create-react-app
How to do that in Windows ?
Elevated cmd prompt: where create-react-app it must be somewhere in the system files under yarn. follow that path and delete both the files.
@sirshikher I get this on the end of create-react-app
...
└─ yargs-parser@13.1.1
Done in 117.92s.
A template was not provided. This is likely because you're using an outdated version of create-react-app.
Please note that global installs of create-react-app are no longer supported.
Hm i am searching inside npm root , it's not inside node_modules also npm list -g -- depth = 0 doesn't show it there . I will burn this laptop .
@sirshikher I get this on the end of create-react-app
...
└─ yargs-parser@13.1.1
Done in 117.92s.
A template was not provided. This is likely because you're using an outdated version of create-react-app.
Please note that global installs of create-react-app are no longer supported.
Hm i am searching inside npm root , it's not inside node_modules also npm list -g -- depth = 0 doesn't show it there .
I am ready to burn the laptop .
@sirshikher I get this on the end of create-react-app
...
└─ yargs-parser@13.1.1
Done in 117.92s.
A template was not provided. This is likely because you're using an outdated version of create-react-app.
Please note that global installs of create-react-app are no longer supported.
Hm i am searching inside npm root , it's not inside node_modules also npm list -g -- depth = 0 doesn't show it there .
I am ready to burn the laptop .
have you tried with npx. i.e npx create-react-app my-app
@sirshikher Yes :(
@sirshikher npm init react-app my-app this works , i mean it shouldn't because create-react-app shouldn't be globally installed.
@sirshikher Yes :(
before that install this npm install create-react-app@latest otherwise its a cache problem.
@sirshikher This installed create-react-app on my desktop
Seems like a cache problem or something .
@sirshikher Now i have to do that everytime when a new create-react-app update comes out ? I mean install it on desktop and go from there :) ?
Download yarn from here https://www.npmjs.com/package/yarn after that run this command:
yarn create-react-app my-app
|
gharchive/issue
| 2020-01-26T07:08:48 |
2025-04-01T04:34:13.232890
|
{
"authors": [
"Alan4747",
"goxr3plus",
"sedhalsoni",
"sirshikher"
],
"repo": "facebook/create-react-app",
"url": "https://github.com/facebook/create-react-app/issues/8374",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
689095933
|
Proposal: prevent @docusaurus package version mismatches
💥 Proposal
As seen here: https://github.com/facebook/docusaurus/issues/3363
If you have some @docusaurus/* packages on alpha 61, and some on alpha 62, the site might not work correctly.
Sometimes users try to upgrade but one dep is left to an older version, and we have cryptic error messages at dev/build time.
We should prevent running a Docusaurus site if the @docusaurus packages do not have the exact same version, with a proper error message.
Note: dependabot and other deps upgrade bots will submit PRs to repos asking you to upgrade doccusaurus packages one at a time, so all these PRs should fai on purpose. We should upgrade Docusaurus deps all at once, in a single PR.
Note: dependabot and other deps upgrade bots will submit PRs to repos asking you to upgrade doccusaurus packages one at a time, so all these PRs should fai on purpose. We should upgrade Docusaurus deps all at once, in a single PR.
I believe (although not tested) a solution to this is packages outside of @docusaurus/core makings sure the peerDependency is pinned to a particular version. This should ensure dependabot and friends realise the two packages need updating in one PR rather than allowing them to update independently. E.g. for preset-core-classic:
"peerDependencies": {
- "@docusaurus/core": "^2.0.0",
+ "@docusaurus/core": "2.0.0-alpha62",
"react": "^16.8.4",
"react-dom": "^16.8.4"
},
Yes, we should do that for all ^2.0.0 refs.
The problem is also that Lerna publish does seem to add back the ^ on every publish, so even if we prevent users from using an older deps, we should also ensure that they don't get a newer version that mismatch with the others (ie all at alpha 62 except one at alpha 63)
I think a runtime check would be more reliable.
We had this idea of "docusaurus doctor", that can also be part of it (https://github.com/facebook/docusaurus/issues/2267)
Should be fixed by https://github.com/facebook/docusaurus/pull/3386
|
gharchive/issue
| 2020-08-31T10:27:40 |
2025-04-01T04:34:13.238510
|
{
"authors": [
"TomBrien",
"slorber"
],
"repo": "facebook/docusaurus",
"url": "https://github.com/facebook/docusaurus/issues/3371",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
710634101
|
Error running the docusaurus site
🐛 Bug Report
(A clear and concise description of what the bug is)
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce
(Write your steps here:)
Install the docusaursus init command (npm install --global docusaurus-init)...
Scaffold the site(docusaurus-init)..
Run cd website to go into the website directory....
Run npm start
Expected behavior
A browser window was suppose to open up at http://localhost:3000.
Actual Behavior
got this error in the command line
LiveReload server started on port 35729
Docusaurus server started on port 3000
Your Environment
Docusaurus version used: 1.14.6
Environment name and version (e.g. Chrome 85.0.4183.121, Node.js 12.18.4):
Windows OS:
Reproducible Demo
(https://docusaurus.io/docs/en/tutorial-setup)
Is the v1 site not working, or it's just the browser window that does not open automatically?
For me it works, so maybe it's your env that makes it unable to get the browser opened?
Do you have the issue with v2 as well?
It's v1 and seems not critical to me, unless many others also have the issue?
This is my first time setting it up and after running npm start, the browser refuses to open automatically on the port 3000 as specified in the setting up guide
You are right that the doc page says:
By default, a browser window will open at http://localhost:3000.
We are not coding this feature ourselves, it comes from a dependency: "react-dev-utils": "^10.2.1", that comes from create-react-app.
Can you run this node script locally and see if it works for you?
import openBrowser from 'react-dev-utils/openBrowser';
openBrowser("http://localhost:3000");
If it does not work, then it's either a problem on your computer, or on this lib
In order to reduce staled issues, I am closing this issue, but feel free to open it again if needed.
|
gharchive/issue
| 2020-09-28T23:06:00 |
2025-04-01T04:34:13.246485
|
{
"authors": [
"Boluwatifeh",
"lex111",
"slorber"
],
"repo": "facebook/docusaurus",
"url": "https://github.com/facebook/docusaurus/issues/3495",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1082443243
|
[2.0] RFC: Improve theming DX (swizzle)
As part of https://github.com/facebook/docusaurus/issues/6113, we want to improve the swizzle DX
The docusaurus swizzle command works fine but still has some major DX problems.
These are various proposals that we can work on before 2.0.
Not all these features are mandatory for v2, but for me the minimum is:
Refactor code
Refactor doc
docusaurus theme wrap
docusaurus theme override
Refactor getSwizzleComponentList
Code
The swizzle CLI command code is not the best part of our codebase, it is quite hard to read, not very well tested and easy to read
Proposal: as part of the current RFC, we should rewrite everything in a better way, designing a whole new DX at the same time. It should be easier than modifying the current code.
Naming
swizzle is a term that is a bit confusing. At least to me, and already saw other feedback
As a non-native English speaker, I've discovered this term in Docusaurus for the first time and had to translate it to understand what it means. Today, I'm still not sure that this translation is even correct 😅 (I translate it as melt or re-arrange 🤷♂️ )
Proposal: rename to docusaurus theme override or docusaurus theme copy
Documentation
The swizzle doc is part of the advanced guides, interleaved with other docs such as how to author a theme. It does not feel right to me.
We should have a dedicated place that group all the possible ways to customize a Docusaurus site in a single place: using CSS file, environment variables, swizzle...
Proposal: probably move that doc to https://docusaurus.io/docs/styling-layout#styling-approaches
wrap
docusaurus swizzle is something that you should rather use as a last resort, as you copy internal source code in your own project.
A better pattern is to use wrap a component so that you can add some logic before/after the original component.
import OriginalFooter from "@theme-original/Footer";
import React from "react";
export default function Footer(props) {
return (
<>
<div>Before footer</div>
<OriginalFooter {...props} />
</>
);
}
This reduces the API surface maintained by the user, ensuring retro-compatibility as long as the public API of the component (props) does not change.
Proposal: docusaurus theme wrap command. Eventually maintain
getSwizzleComponentList
This theme lifecycle is not flexible enough to convey what is our public theme API surface.
For example:
some components might be safe to wrap but not to override (some layout items...)
some components might be safe to wrap and override (icons...)
If swizzle is renamed to docusaurus theme override, this lifecycle name should also be updated.
It may be useful to provide more than 2 levels of safety? 🤔 (safe, warn, unsafe?)
When adding a new theme component, a test should ensure that we never forget to declare the level of safety for wrap/override, to prevent having an unclear public API surface.
Proposal: this needs a complete redesign. We can safely remove the existing getSwizzleComponentList, it is optional and probably not used by many community plugins anyway.
diff
When overriding theme components, we should have a way to easily inspect how our local implementation has changed compared to the upstream theme implementation.
Proposal: docusaurus theme diff to see a diff of all overridden files, with options for all at once or focusing on a single file
Problem: how to clearly identify comps that override from comps that wrap?
upgrade
Can we provide tooling so that on Docusaurus upgrades, users that override our theme are able to patch their local files?
Already mentioned in https://github.com/facebook/docusaurus/issues/5734#issuecomment-946934365
It could work like this:
on docusaurus theme override, store the current version (let's say 2.3.1) in the copied file (user is expected to keep this comment)
on docusaurus theme upgrade: use current version (2.4.8) create a theme file diff between 2.4.8 & 2.3.1 => apply this diff to the copied file + upgrade comment to 2.4.8
Other proposed solution here: https://github.com/facebook/docusaurus/issues/5734
Proposal: docusaurus theme upgrade
Problem: it might be complex to build, probably not a top priority atm 🤷♂️
Upgrade Helper website
Users should be able to easily inspect the changes we did in our themes.
React-Native has such a helper website, allowing to see changes across 2 versions: https://react-native-community.github.io/upgrade-helper/?from=0.62.0&to=0.67.0-rc.0
When publishing changelogs and major release blog posts, we could allow our community to browse changes easily with a simple link. Users could understand faster if the upgrade requires theme changes.
Proposal: build a helper website to browse a diff online, with some useful filters (theme/plugin...)
Problem: duplicate of the diff command? Which one is the most important to build first, with the best ROI?
debug
Having a CLI command to easily inspect what are the unsafe overrides of a theme that are currently in use might be useful (particularly when we might change what is safe/unsafe over time).
This cli could do multiple things:
print a diff of unsafe overridden files
show various recommendations like replacing an override by wrap...
provide more useful features later
Proposal: docusaurus theme debug, docusaurus theme inspect, docusaurus theme doctor...
Problem: naming? builds on top of other features: later?
Let me know what you think, this is just a draft for now and all these proposals are very incomplete in term of design.
My two cents.
Naming
My first time seeing this term as well, and your understanding is generally correct: it's to "stir" or "mix". In the documentation there's a brief explanation: "In iOS, method swizzling is the process of changing the implementation of an existing selector (method). In the context of a website, component swizzling means providing an alternative component that takes precedence over the component provided by the theme."
I like this term very much. It's playful, unique, and not coming out of thin air either. If you look at its Objective-C origin, it's exactly the same as what we are doing.
swizzle --eject and swizzle --wrap would be enough to differentiate them. I like --eject better than --copy since it also alludes to the danger: CRA treats eject as the ultimate customization.
@yangshun As the original implementer, what do you see here?
Documentation
Swizzling should always be considered advanced, since nowhere in our "Guides" do we actually ask you to write JavaScript to implement a core feature! We should certainly refactor our advanced guides into more Recipes / Key concepts style.
Wrap
Very easy to implement, pretty easy to understand, should definitely be prioritized
Diff
Agree. For now I have a header comment to remind myself of what I have changed. We should try to have a git merge kind of DX, like what yarn patch offers.
Problem: how to clearly identify comps that override from comps that wrap?
Just check if it imports @theme-orginal. Nothing else would have this.
getSwizzleComponentList
I don't dislike this and would like it kept. We can change the API to exporting a list of objects, each with the component's name, safety, even file path, etc.
(Also, this isn't a lifecycle, this is a metadata of the theme itself.)
upgrade
Complicated, but certainly worth the effort. It's also going to help users migrate some config options that we discourage / deprecate.
Upgrade Helper website
Duplicate of the diff command, indeed, and I think diff should come first since it's more limited in scope.
debug
Even later. We can have a Docusaurus linter.
In summary, my alternative proposal is:
docusaurus swizzle --eject # Outputs a complete file
docusaurus swizzle --wrap # Outputs a wrapper component
docusaurus swizzle --patch # Opens a temporary file for you to edit, and then saves it as a diff file. At runtime, we merge the diff file with the actual theme component, and throw if they don't reconcile.
docusaurus upgrade theme # Try to merge the new component with the existing one, lets you solve a git conflict if they don't
That seems reasonable thanks
For v2 we should probably just focus on --eject and --wrap.
I'd like to change a bit the behavior of getSwizzleComponentList (maybe rename it) because some components might be safe to wrap, but not to eject, and we should probably be able to assign more config (and even a description) to each component
--patch and upgrade may be more complicated to achieve in the short term, let's figure out
Yes, that sounds like my plan as well! This issue would be good to be worked on. For specific details about --wrap let's discuss in #5380
Wild thought: is it possible to not specify themeName when running swizzle? Since Docusaurus knows which component is actually used at runtime, can we do the same in swizzling and automatically resolve the right component to be swizzled?
For example, currently, if the user uses live-codeblock, but chooses to swizzle theme-classic/CodeBlock (maybe because she wasn't aware of the internal inheritance), the @theme/CodeBlock would point to the swizzled one and the live function will be entirely lost.
Wild thought: is it possible to not specify themeName when running swizzle? Since Docusaurus knows which component is actually used at runtime, can we do the same in swizzling and automatically resolve the right component to be swizzled?
Yes that makes sense to me to swizzle the "final component" (ie live-codeblock) in priority, as long as there's an option to eventually swizzle the original theme component (ie we should still be able to swizzle both as one might extend the other)
Another little detail is to support the shorthand names like classic and probably display classic first in the list
|
gharchive/issue
| 2021-12-16T17:05:18 |
2025-04-01T04:34:13.272507
|
{
"authors": [
"Josh-Cena",
"slorber"
],
"repo": "facebook/docusaurus",
"url": "https://github.com/facebook/docusaurus/issues/6114",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
726647180
|
fix(v2): docusaurus start --poll 500 should work + better config load failure error
Motivation
Fixes https://github.com/facebook/docusaurus/issues/3620
docusaurus start --poll 500 should accept 500 as poll interval value
Also we should use polling for both webpack dev server and chokidar file watchers
Also improve the error message in such weird case so that user can understand we try to load the config from 500/docusaurus.config.js and that 500 is interpreted as the cli siteDir arg.
Have you read the Contributing Guidelines on pull requests?
yes
Test Plan
Local test and checking the correct args are forwarded to Webpack config
yarn start:v2
yarn start:v2 --poll
yarn start:v2 --poll 500
Any idea what I should add? As we already ref the webpack watchOption link, maybe I should just make it more obvious that we can pass an arg?
(btw we don't do that for port/host neither currently)
Any idea what I should add? As we already ref the webpack watchOption link, maybe I should just make it more obvious that we can pass an arg?
Yes, that will be enough.
|
gharchive/pull-request
| 2020-10-21T16:05:12 |
2025-04-01T04:34:13.277905
|
{
"authors": [
"lex111",
"slorber"
],
"repo": "facebook/docusaurus",
"url": "https://github.com/facebook/docusaurus/pull/3622",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
163419141
|
option to clone entities on paste
I just noticed that if I paste a block with entities in it, the newly created block has entities with the same key. I have an inline equation entity type where each equation is represented by content in it's data hash, not the content it's decorating (a single space). So pasting an equation should result in a new, independent equation that is editable on it's own.
That is, if I edit a pasted equation, it updates both the pasted equation and the one it was copied from.
It looks like these might be the relevant places:
https://github.com/facebook/draft-js/blob/master/src/component/handlers/edit/editOnPaste.js#L59
https://github.com/facebook/draft-js/blob/master/src/component/handlers/edit/editOnPaste.js#L164
Maybe this could be handled with new DraftEntityMutability values?
eg.
MUTABLE_UNIQUE
IMMUTABLE_UNIQUE
SEGMENTED_UNIQUE
Thoughts?
Good question. This is in the gray area between feature and bug. :) In some scenarios, one might want the same entity to apply to the pasted content, but this is a clear case where one would not.
One thing I have been thinking about is whether it makes sense to define a "paste config" object that can be passed as a prop to Editor. This would allow stripPastedStyles to have a proper home rather than being a first-class prop, would allow better flexibility for keeping/discarding certain styles, and would make something like this pretty trivial to configure -- e.g. pasteUniqueEntities: true to force duplication of all entity objects for the pasted output.
Has this only been an issue for you within paste behavior, or have you encountered any other trouble with duplicated entities?
This has only been an issue with pasting. I can't really think of any other ways that draft might need to handle duplicating entities for me, but then again, I'm pretty new to using it.
A similar case could me made for pasting media. A user who copies and pastes a media object into a different part of the document may intend to modify that object. e.g. pasting a video player embed and wanting to change the start/end time.
I like the idea of a pasteConfig it solves my problem more elegantly and makes a home for other paste configurations. What about the other paste handlers: handlePastedText and handlePastedFiles ...would it make sense to move them in as well?
@hellendag I've forked the repo and am beginning to work on this.
Would this likely be accepted in a PR?
I addition to pasteUniqueEntities, I'm going to be doing some additional work to fix pasting of inline equation entities. Here's my strategy
Ensure 'internal paste' is detected for selections within a block that contain an Entity
Modify Draft Entity id scheme so we can detect when an Entity is pasted based off of it's DOM id
If Draft Entity ids are found in the pasted HTML, use the internal clipboard.
Relevant updates will be made here: https://github.com/facebook/draft-js/blob/master/src/component/handlers/edit/editOnPaste.js#L109-L140
Use pasteUniqueEntities to ensure pasted Entities are cloned.
Would this additional work likely be accepted in a PR?
I just want to get a feel for how cleanly I should try to implement these features.
@afraser This is definitely something I’d like to see. If you need someone to test out the implementations you’re looking at then let me know.
@makenosound I have a PR for this here: https://github.com/facebook/draft-js/pull/525
I've also cooked up a solution that doesn't require any changes to Draft and uses the editor onPaste callback. You can find that here: https://github.com/facebook/draft-js/issues/390#issuecomment-235005692
@afraser That’s great, thanks for doing the leg-work and for sharing your interim solution.
Another situation I've seen specifically with link entities is where you can drag part of the link and move it and now the "new" link and the old share the same entity key. Right now I have UI that allows you to modify the link text and url based on the entity key, which obviously break in these scenarios
@jasonenglish The comment I referenced in the comment above has the following gist which actually addresses that very problem.
https://gist.github.com/afraser/6dedbe486d9a254ab490c2df6ca3abd2
search for cloneEntitiesInFragment
@afraser, fixed a little bug in your gist, where blocks with only plaintext are not copied/pasted.
https://gist.github.com/bryanph/17a805449a0937156965ee55c755ed41
@afraser, I'm now trying to get this to work for pastes between editor (so not internal). No idea how to approach this since the required data is stored in the entity store itself. Do you have any ideas maybe?
is there any way to clone entities on paste other than waiting for a new build that allows it?
|
gharchive/issue
| 2016-07-01T15:26:01 |
2025-04-01T04:34:13.289945
|
{
"authors": [
"afraser",
"bryanph",
"hammadmlk",
"hellendag",
"jasonenglish",
"makenosound"
],
"repo": "facebook/draft-js",
"url": "https://github.com/facebook/draft-js/issues/504",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
173729223
|
editorState.getCurrentContent is not a function
Hi,
I'm trying to get Draft.js to work with Redux and Reselect in my React project.
I'm setting the initial editorState in my reducer and then use it in my component.
import { fromJS } from 'immutable';
import { EditorState } from 'draft-js';
import {
RECEIVE_EDITOR_CHANGE,
} from './constants';
const initialState = fromJS({
editorState: EditorState.createEmpty(),
});
function writePageReducer(state = initialState, action) {
switch (action.type) {
case RECEIVE_EDITOR_CHANGE:
return state
.set('editorState', action.editorState);
default:
return state;
}
}
<Editor editorState={this.props.editorState} onChange={this.props.editorChange} />
When I load the page I always get editorState.getCurrentContent is not a function as an error.
Hi,
I think you couldn't convert EditorState by fromJS.
EditorState isn't plain object.
"fromJS() - Deeply converts plain JS objects and arrays to Immutable Maps and Lists."
We have the same problem in our react-redux project.
So is there any way around this?
You can save ContentState in redux store with convertToRaw, convertFromRaw.
In your component:
constructor(props) {
super(props);
const contentState = convertFromRaw(this.props.contentState);
this.state.editorState = EditorState.createWithContent(contentState);
}
componentWillUnmount() {
const contentState = this.state.editorState.getCurrentContent();
// You can save contentState here or somewhere else.
// this.props.onSave(convertToRaw(contentState));
}
this.onChange = (editorState) => this.setState({editorState});
<Editor editorState={this.state.editorState} ... onChange={this.onChange} />
in your code, if you update
const initialState = fromJS({
editorState: EditorState.createEmpty(),
});
to
const initialState = Map({
editorState: EditorState.createEmpty(),
});
That would fix your problem.
As @reme3d2y suggested, you could also use convertFromRaw, if the editorState is coming from the outside
Hey stopachka I am getting the same issue I tried
const initialState = Map({ editorState: EditorState.createEmpty(), });
It giaves me the followwing error massage
×
TypeError: Constructor Map requires 'new'
|
gharchive/issue
| 2016-08-29T09:05:35 |
2025-04-01T04:34:13.295580
|
{
"authors": [
"jonathanwilke",
"ramisalem",
"reme3d2y",
"stopachka"
],
"repo": "facebook/draft-js",
"url": "https://github.com/facebook/draft-js/issues/621",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
245778443
|
Generic "object as map" type isn't checked properly
/* @flow */
type Hash<T> = {[string]: T}
const f = (val: Hash<number>): Hash<string> => val
gives no errors: https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoALgTwA4FMwASAhgM4AWAPACoB8YAvGAN4DaJ6ATgJYB2A5gF0AXGCoBfVKgDGcHuzBQGYABQA3IjBHFyFHgFcAtgCNcHGgEotpSu27869OupiogA
If I change it to explicit
/* @flow */
const f = (val: {[string]: number}): {[string]: string} => val
It gives the expected error:
2: const f = (val: {[string]: number}): {[string]: string} => val
^ number. This type is incompatible with the expected return type of
2: const f = (val: {[string]: number}): {[string]: string} => val
^ string
https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoAxnAdgZwC5hRgC8YAFAG4CGMAXGAN4Da+ATgJZYDmAuvVgFcAtgCMApqwC+ASnrM2nXvQXdJJAHxhqMVEA
This seems to be fixed now (on flow.org/try, using 0.85)
|
gharchive/issue
| 2017-07-26T16:21:21 |
2025-04-01T04:34:13.331249
|
{
"authors": [
"Hypnosphi",
"kangax"
],
"repo": "facebook/flow",
"url": "https://github.com/facebook/flow/issues/4469",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
252712208
|
Bug with HoC + React Component class + ES6 Exports
First of all thanks so much for 0.53.0 team! This addressed a lot of the issues my team was facing with using Flow. Specifically we want Flow typing for React component props and I noticed this issue.
If you take the example from your HoC doc and put it in the flow playground (see here) everyting works great. However if you have the HoC have it's own file, import it into a file that exports a component that's wrapped with the HoC and use that component in another file you get an error. Note that if you convert MyComponent from a React Component class to a stateless functional component the error goes away. Seems like a bug, right? 🤔
Repro Setup
// hoc.js
// @flow
import * as React from 'react'
export function injectProp<Props: {}>(
Component: React.ComponentType<{ foo: number } & Props>,
): React.ComponentType<Props> {
return function WrapperComponent(props: Props) {
return <Component {...props} foo={42} />;
};
}
// component.js
// @flow
import * as React from 'react';
import { injectProp } from './hoc'
class MyComponent extends React.Component<{
a: number,
b: number,
foo: number,
}> {}
export default injectProp(MyComponent);
// other-component.js
// @flow
import MyComponent from './component.js'
...
<MyComponent a={3} b={4}
....
Error
$ flow
Error: src/js/apps/main-future/views/rfps/my/view.js:90
v--------------------
90: <MyOpportunitiesTable
91: a={3} b={4}
92: />
-^ React element `MyOpportunitiesTable`
v
6: class MyComponent extends React.Component<{
7: a: number,
8: b: number,
9: foo: number,
10: }> {}
^ property `foo`. Property not found in. See: src/js/apps/main-future/views/rfps/my/components/table/index.js:6
v--------------------
90: <MyOpportunitiesTable
91: a={3} b={4}
92: />
-^ props of React element `MyOpportunitiesTable`
Found 1 error
error Command failed with exit code 2.
~/buildingconnected/client (flow-upgrades) $ yarn flow
yarn flow v0.27.5
$ flow
Error: src/js/apps/main-future/views/rfps/my/components/table/index.js:14
14: <Foo a={3} b={4} />
^ Unexpected identifier
Found 1 error
error Command failed with exit code 2.
I think this is the same issue as in #4644. The solution there might be instructive for you.
@asolove thanks for the pointer, I'll try to work around this for now! That said since it's only happening to React Component classes (not stateless functional components) and only when imported and exported from files (not when all in the same file) I think this seems like something that warrants a fix so :crossed_fingers:!
Hah, you're totally right. It seems to work if I change { foo: number } & Props to { foo: number, ...Props }. Does that work in your project?
It does work for me :)
Awesome! In that case, I think we can close this issue.
@asolove @samwgoldman thanks for looking into this and giving me feedback so quickly! Good news: no more errors! Bad news: it doesn't error when it should!
So if you change the intersection ( React.ComponentType<{ foo: number } & Props>) to a spread ( React.ComponentType<{ foo: number, ...Props }>) then you somehow lose all type safety in the last mentioned file of the example (see below). Any tips?
// other-component.js
// @flow
import MyComponent from './component.js'
...
<MyComponent b={4} /> // no errors about prop "a" being missing
....
Ugh, damnit. Let me look some more.
@calebmer
I’m working on a fix for this bug. Thanks for reporting!
You’ll notice that these examples work fine when they are in the same file because Flow does local type inference. However, Flow does not infer types across modules and so converts types that would have been inferred to any. There are a couple different fixes for this. I’ll update you when we have a fix.
@calebmer any estimations?
BTW, I think it should be explicitly pointed in the docs that there's no possibility to type HoCs currently.
This should have been fixed since 0.55 😊. In 0.57 we are going to update the docs to recommend that you use $Diff<> instead:
import * as React from 'react'
export function injectProp<Props>(
Component: React.ComponentType<Props>,
): React.ComponentType<$Diff<Props, { foo: number }>> {
return function WrapperComponent(props: Props) {
return <Component {...props} foo={42} />;
};
}
Nice!
Thanks for the answer!
@calebmer it's always hard for me to understand what the flow team are working on and what to expect and when. Do you have some publicly available info about it?
Do you have somebody who work as a maintainer of this github repo and who is responsible for issues' statuses / labels / answers / etc?
@calebmer but it seems that such usage of $Diff can't help with the problem (on flow 0.56 at least)
Why was this issue closed? It's not working at all, even with the new example.
I made a example with create-react-app here: https://github.com/kennethaasan/flow-hoc/blob/master/src/components/Link.js#L41
@calebmer the example from docs works if everything is in one file, but does not when the HOC is exported from a different file: https://github.com/facebook/flow/issues/5064
|
gharchive/issue
| 2017-08-24T19:51:45 |
2025-04-01T04:34:13.342984
|
{
"authors": [
"AugustinLF",
"alurim",
"apsavin",
"asolove",
"calebmer",
"kennethaasan",
"samwgoldman",
"vonovak"
],
"repo": "facebook/flow",
"url": "https://github.com/facebook/flow/issues/4709",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
436449368
|
$TupleMap<Array<T: Union>, ...> has unexpected handling
Flow version: 0.97.0
Expected behavior
I expected that the in the TupleMap, the seperate union members were mapped, and then a new union was created.
Actual behavior
Only one mapping was made, with the full union, resulting in type errors due to bug #4211.
Potential solution: Supply a $UnionMap function, mapping each union member seperately.
Link to Try-Flow
It is expected actually
fair enough? Though I tried the following, and that failed too:
example on flow.org/try
Flow team currently against adding new $ types, so I don't know if this is would be possible, but maybe it is easier to create $UnionToTuple
After more research, the both example's issues seem to be missing disjoint union type detection for tuples, which I hadn't seen the issues for. Therefore, the issue I'm having specifically is #4296.
Regarding UnionToTuple, that would probably be difficult to implement as it will imply an order in the union, which does not exist (as object | number === number | object). A better alternative would probably have a Set as the target type or something like that, but that will probably not be nescessary once #5048 is merged
This now works under inference_mode=lti
|
gharchive/issue
| 2019-04-24T00:52:51 |
2025-04-01T04:34:13.348801
|
{
"authors": [
"MMeent",
"SamChou19815",
"goodmind"
],
"repo": "facebook/flow",
"url": "https://github.com/facebook/flow/issues/7665",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
648939704
|
The Readme should provide a reason why I should use Flow
I would like to know which benefits Flow has.
Please state this to potential users in the README.
Maybe add a comparison why Flow is better than TypeScript.
I'd see the documentation on Flow's website about why and how they built Flow: https://flow.org/en/docs/lang/.
In general, I don't think READMEs for big projects need to make such an argument -- normally that is better done on a website, wiki, or external blog posts, for example.
Flow focuses on soundness
TypeScript focuses on completeness
Which one you prefer is up to you, but personally I use it because it helps me write more predictable and robust applications. Being 100% sound means that I'm very confident that I don't get runtime errors that can crash the application. Though it means I need to write a lot more checks to validate types. It's up to you whether this is a pro or con for you.
|
gharchive/issue
| 2020-07-01T12:23:39 |
2025-04-01T04:34:13.351498
|
{
"authors": [
"Brianzchen",
"dylanirlbeck",
"guettli"
],
"repo": "facebook/flow",
"url": "https://github.com/facebook/flow/issues/8424",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
364894742
|
docs(search): add docsearch
This is the simplest way i found to add it, it can be improved, but I chose to lazy load docsearch; and didn't want to change too much in the css
closes #1501
cc @leebyron, does this what you want? :)
Whoops, I just realised I left my debugging br's in there. I'm done with this for today, but maybe it's fine?
here's how it looks: https://priceless-volhard-23828e.netlify.com/docs/#/
ping @leebyron, did you get a chance to look at this?
Nice! Looks like we could use a follow up to add some styling so it's more clear that it's a search box, but otherwise looking nice
|
gharchive/pull-request
| 2018-09-28T13:43:26 |
2025-04-01T04:34:13.381441
|
{
"authors": [
"Haroenv",
"leebyron"
],
"repo": "facebook/immutable-js",
"url": "https://github.com/facebook/immutable-js/pull/1610",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
}
|
649213305
|
Jest does not exit properly when using supertest and only 1 test file
🐛 Bug Report
When using Jest in combination with Supertest and only having 1 (!) test file, Jest will not exit properly.
This bug was already reported in an already closed issue, here: https://github.com/facebook/jest/issues/5783#issuecomment-436896949
I can confirm this behaviour with the latest version 26.1.0. It will tell me Jest did not exit one second after the test run has completed..
To Reproduce
Steps to reproduce the behavior:
I am using request = supertest(app); in my beforeAll function, then using request in my test(s). It doesn't matter how many tests there are in my file, however, it is important, that I only have 1 (!) test file. As soon as I duplicate my test file (to get 2 test files) the error is gone, and Jest exits properly.
Expected behavior
Jest should exit properly.
hello @maks-io same here i just playing with jest i use everthing i know ----detectOpenHandles shows nothing
in result , its ruined my day
tnx for ur bug Report
hello @maks-io same here i just playing with jest i use everthing i know ----detectOpenHandles shows nothing
in result , its ruined my day
tnx for ur bug Report
|
gharchive/issue
| 2020-07-01T18:50:52 |
2025-04-01T04:34:13.385554
|
{
"authors": [
"maks-io",
"rozi98"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/issues/10220",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
218376355
|
Feature request: replace "-w" CLI option to be "--watch" shorthand
Many CLIs use -w as a shorthand for --watch. Currently, the Jest CLI doesn't have a shorthand for --watch; it would be nice if -w could become the --watch shorthand, and the current -w (shorthand for --maxWorkers) could change to -m.
I like this idea, -w feels natural for watch mode... Breaking change, but really interesting
I don't think it's necessary to break this. How about mapping "yarn w" to "jest --watch" in the scripts section?
From: Rogelio Guzman notifications@github.com
Sent: Friday, March 31, 2017 3:00:48 PM
To: facebook/jest
Cc: Subscribed
Subject: Re: [facebook/jest] Feature request: replace "-w" CLI option to be "--watch" shorthand (#3233)
I like this idea, -w feels natural for watch mode... Breaking change, but really interesting
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/facebook/jest/issues/3233#issuecomment-290624534, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAA0KEB6H6mcWugNWEmSBjkfx0tOePHdks5rrJaQgaJpZM4MvIW7.
It's not about an individual project, but CLI use in general. -w for watch seems to be a standard:
babel: https://babeljs.io/docs/usage/cli/
webpack: https://webpack.js.org/api/cli/
Post CSS: https://www.npmjs.com/package/postcss-cli
Mocha: https://mochajs.org/
AVA: https://github.com/avajs/ava
etc.
They do, and maybe jest should have, but it's a pretty trivial reason for a breaking change.
No worries, just thought I'd suggest it :) Thanks for all the great work with Jest.
|
gharchive/issue
| 2017-03-31T01:55:01 |
2025-04-01T04:34:13.394184
|
{
"authors": [
"cpojer",
"rogeliog",
"trevordmiller",
"wtgtybhertgeghgtwtg"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/issues/3233",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
225756491
|
Error: Error watching file for changes: EMFILE
I know others have posted this issue, but it seems that they are aging and using old versions. I have tried everything from other issues.
Here is the error I get:
$ jest --watch # or with $ jest --watch --no-watchman
2017-05-02 09:49 node[8980] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-05-02 09:49 node[8980] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-05-02 09:49 node[8980] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:163
throw er; // Unhandled 'error' event
^
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1050:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1376:11)
error Command failed with exit code 1.
Versions:
node: v7.9.0
jest: 19.0.2
watchman: 4.7.0 (installed via brew)
mac: Sierra 10.12.4 (16E195)
This problem exists with the following versions
19.0.2
19.0.1
19.0.0
It works again in
18.1.0
Does it happen in v20?
Yes, the error is present in v20.0.0.
2017-05-08 05:30 node[6062] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-05-08 05:30 node[6062] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-05-08 05:30 node[6062] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:163
throw er; // Unhandled 'error' event
^
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1050:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1376:11)
error Command failed with exit code 1.
And have you tried it with watchman (brew install watchman)?
Yes
Any chance for a repro? It's hard to debug without it :(
brew install watchman worked for me.
Same here, it did not work with jest --watch or jest --watch --no-watchman (watchman was not installed):
2017-05-28 18:57 node[17087] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-05-28 18:57 node[17087] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
2017-05-28 18:57 node[17087] (FSEvents.framework) FSEventStreamStart: register_with_server: ERROR: f2d_register_rpc() => (null) (-22)
events.js:163
throw er; // Unhandled 'error' event
^
Error: Error watching file for changes: EMFILE
at exports._errnoException (util.js:1050:11)
at FSEvent.FSWatcher._handle.onchange (fs.js:1374:11)
I installed watchman using brew, and jest --watch now works. jest --watch --no-watchman still fails.
Jest v20.0.4
Node v7.10.0
MacOS 10.12.5
I get similar error when i install "pact" and then i tried to run npm test. I using create-react-app to setup my project and using node v7.9.0
new sane version fixed this error for me see https://github.com/amasad/sane/pull/97#issuecomment-309203580
Same problem,
MAC OS X Sierra
Node v7.8.0
Jest ^20.0.4
brew install watchman worked for me too using NodeJS v6.9 but what I don't understand is the watchman dependence itself. Is this a dependency of the NodeJS version on Mac OS X Sierra? Where does this fit in the dependency tree?
https://github.com/facebook/jest/issues/1767#issuecomment-313434888
brew install watchman worked for me.
I had this error, but found that if I changed the command I used to run jest in watch mode, it worked.
"test": "jest",
"test:watch": "npm run test -- --watch",
became:
"test": "jest",
"test:watch": "npm run test --watch",
brew install watchman worked... until it didn't... :-/ quit my tests and ran it again. And we're back at square one. uninstalled watchman, reinstalled watchman. no-dice.
brew install watchman worked for me. And I think watchman had gotten broken somehow because I accidentally closed a terminal window while installing a react package using npm. Clean installing everything both in the project and globally didn't seem to help, but re-installing watchman did.
Yeah! brew install watchman for work (2)
ditto to watchman
I had this error, but found that if I changed the command I used to run jest in watch mode, it worked.
"test": "jest",
"test:watch": "npm run test -- --watch",
became:
"test": "jest",
"test:watch": "npm run test --watch",
The extra -- is the delimiter that tells npm to forward the remaining parameters to the referenced script.
npm run test -- --watch would run jest --watch but npm run test --watch would ignore the argument and just run jest. You can verify this in your console output.
|
gharchive/issue
| 2017-05-02T16:55:19 |
2025-04-01T04:34:13.407365
|
{
"authors": [
"Premjeet-Singh",
"amandapouget",
"carmanchris31",
"darylshy",
"fitfab",
"gazzwi86",
"joevandyk",
"kirkstrobeck",
"melkristian",
"renchap",
"thisconnect",
"thujone",
"thymikee",
"wayneseymour",
"zxzl"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/issues/3436",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
272184045
|
Hooks for describe and test blocks in a custom environment
Background
I've been using Mocha with a custom interface I wrote that allows me to have a custom wrapper describeComponent block that takes in some config to do some internal setup for each test suite. It can then be nested with standard describe and it blocks.
I want to try using Jest instead, and take advantage of some powerful features available. However, I'm struggling to get the above configuration in Jest. There's limited documentation regarding this too.
I've extended the NodeEnvironment class, which provides setup, teardown and runScript hooks (see Environment. Is there any way to hook into the current test and describe context, for example, to get the name of the test or suite. Is it also possible to create a wrapper describe?
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions. Thank you :)
I was asking if something is possible with the follow up of it being a feature request if not. It’s not a “I’m stuck making my test work”. This would have avoided going around in circles but fair enough.
You should be able to overwrite the global describe, it or test, but I don't think a custom environment is correct.
See http://facebook.github.io/jest/docs/en/configuration.html#setuptestframeworkscriptfile-string
|
gharchive/issue
| 2017-11-08T12:39:35 |
2025-04-01T04:34:13.411940
|
{
"authors": [
"SimenB",
"cpojer",
"gidztech"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/issues/4860",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
456290149
|
Resolve alias in dependecy monorepo package
💬 Questions and Help
Right now we are developing a react application that makes use of a monorepo using yarn workspaces and typescript paths.
I have two packages both whom have jest tests. Package A depends on Package B and B is independent.
Running tests on package B (a component library) is no problems and within package B I have typescript aliases aka compilerOptions.paths. Jest has no problems handling these with moduleNameMapper.
However the issue arises when I try to run jest tests on Package A which imports components from Package B. When the component in B is imported it has its own local dependencies and jest seems unable to resolve Package B alias mappings when running tests in A.
Example:
Root jest.config.js:
module.exports = {
transform: {
"^.+\\.tsx?$": "ts-jest",
},
testRegex: "(/tests/.*|(\\.|/)(test|spec))\\.tsx?$",
roots: ['<rootDir>/tests'],
moduleNameMapper: {
"@someAlias/(.+)$": "<rootDir>../src/$1",
"@foo/packageB(.*)$": "<rootDir>/../packageB/src/$1",
},
moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node"],
};
Package B.
./packages/packageB/src/components/Component1.tsx
export const Component1 = () => <div>helloWorld </div>
src/components/Component2.tsx
import Component1 from '@someAlias/components'
export const Component2 = () => <div><Component1/></div>
./packages/packageB/jest.config.js
module.exports = {
...baseConfig,
displayName: 'packageB',
moduleNameMapper: {
...baseConfig.moduleNameMapper,
},
rootDir: './'
};
Running tests for Package B is NO PROBLEMS :D
Package A
./packages/packageA/src/components/Component1.tsx
import {Component2} from '@foo/packageB'
export const Component1 = () => <div><Component2/></div>
./packages/packageA/jest.config.js
module.exports = {
...baseConfig,
displayName: 'packageA',
moduleNameMapper: {
...baseConfig.moduleNameMapper,
},
rootDir: './'
};
When running tests from here I get an error
● Test suite failed to run
TypeScript diagnostics (customize using `[jest-config].globals.ts-jest.diagnostics` option):
../packageB/src/components/Component2/Component2.tsx:5:26 - error TS2307: Cannot find module '@someAlias/components'.
5 import { ListItem } from '@someAlias/components';
So it appears as though jest is not able to resolve module name aliases outside of its own rootDirectory. If this is the case, is there a canonical way of resolving this issue? How do i get a dependency packages own aliases to resolve in order to run my tests?
Please note that this issue tracker is not a help forum and this issue will be closed.
For questions or help please see:
The Jest help page
Our discord channel in Reactiflux
The jestjs tag on StackOverflow
Remove roots: ['<rootDir>/tests'] from your config. roots tells Jest where to find tests and files.
Also in your root config, if you want other configs to apply, you need to use projects option: https://jestjs.io/docs/en/configuration#projects-array-string-projectconfig.
I think that all should help.
Ah I swear I read the documentation a 1000 times about roots. I didn't realize it affected what files would be imported. Thought it was just relevant for the test files.
Ive tried configuring with projects and the rootDir pointing to my root directory and to be honest its been kind of a nightmare. Have experimented a lot to try and get things right.
Im not really sure as to how to configure this. As far as I understand it if I have several jest.configs listed in my projects field it will run separate so called "runners" for each config. Yet they don't seem to be read properly as none of them are finding they're local respective tsconfig files and none of the module mappings work.
My config for packageB now looks like this:
const baseConfig = require("../../../jest.base");
module.exports = {
...baseConfig,
displayName: 'packageB',
rootDir: '../../../',
globals: {
'ts-jest': {
tsConfig: './tsconfig.json'
}
},
setupFilesAfterEnv: ['@testing-library/react/cleanup-after-each'],
snapshotSerializers: ['jest-emotion']
};
Have also tried setting my .tsconfig path to an absolute path with rootDir to no avail
my root jest.base looks like this:
module.exports = {
transform: {
"^.+\\.tsx?$": "ts-jest",
},
testRegex: "(/tests/.*|(\\.|/)(test|spec))\\.tsx?$",
moduleNameMapper: {
"@someAlias(.*)$": "<rootDir>packages/packageB/src$1",
"@foo/packageA(.*)$": "<rootDir>packages/packageA/src/$1",
"@foo/packageB(.*)$": "<rootDir>packages/packageB/src/$1"
},
moduleFileExtensions: ["ts", "tsx", "js", "jsx", "json", "node"],
};
And finally my root jest.config:
module.exports = {
projects: ['<rootDir>/packages/packageA/jest/jest.config.js', '<rootDir>/packages/packageB/jest/jest.config.js'],
};
If I run jest from the root I just get bombarded by jsx flag issues and all of the module imports not finding their modules. If I run from packageB all of my tests will however pass (not weird I guess), and it also runs the failing packageA test now (I guess because the rootDir is set for the whole monorepo?)... which still fails regardless of what I've done I've never got this test to pass.
Does the projects field not allow importing of other jest.config files or something? The errors I get from jest say so little about the problem. Where am I going wrong??
-<rootDir>packages
+<rootDir>/packages
Man your response time is amazing and soo appreaciated. The change made no difference. Ill see if I can't get an example repo up for an example.
Sure! We are aware that setting up Jest projects is quite cumbersome at times, but it should eventually work. We'd also like to re-think this setup to be more intuitive (because it definitely isn't right now).
Ok I have create an example repo here
Illustrates the issues im having.
I'd say it's an issue with ts-jest. If I turn off diagnostics, tests pass:
diff --git a/packages/foo-packagea/jest.config.js b/packages/foo-packagea/jest.config.js
index ae89670..ee34fcf 100644
--- a/packages/foo-packagea/jest.config.js
+++ b/packages/foo-packagea/jest.config.js
@@ -6,7 +6,8 @@ module.exports = {
rootDir: '../../',
globals: {
'ts-jest': {
- tsConfig: '<rootDir>/packages/foo-packagea/tsconfig.json'
+ tsConfig: '<rootDir>/packages/foo-packagea/tsconfig.json',
+ diagnostics: false
}
},
modulePathIgnorePatterns: [
diff --git a/packages/foo-packageb/jest.config.js b/packages/foo-packageb/jest.config.js
index 42e4135..9f4325e 100644
--- a/packages/foo-packageb/jest.config.js
+++ b/packages/foo-packageb/jest.config.js
@@ -6,7 +6,8 @@ module.exports = {
rootDir: '../../',
globals: {
'ts-jest': {
- tsConfig: '<rootDir>/packages/foo-packageb/tsconfig.json'
+ tsConfig: '<rootDir>/packages/foo-packageb/tsconfig.json',
+ diagnostics: false
}
},
modulePathIgnorePatterns: [
I'd consider disabling diagnostics and file an issue there :)
Thats super interesting! I've been digging and playing around with it the whole time as well. I also got onto the the ts-loader scent and started logging out what ts-loaders pathsToModuleNameMapper mapped my tsconfig paths to. Using this I was able to write the correct regex that satisfied jest as far as module mapping goes.
I pushed my changes to the repo now and all tests pass as is. I basically hoist any needed shared mapped modules to my base config and keep the internal modules local to the package. I also added roots to each of the packages to stop the tests from running 2 or more times for each config I add to jest.configs projects.
Looking forward to improving the documentation so that someone else doesn't have to go through the same journey. But I think if I can find time ill try and open an issue with ts-jest as well.
|
gharchive/issue
| 2019-06-14T14:53:26 |
2025-04-01T04:34:13.426665
|
{
"authors": [
"cygnichris",
"draftitchris",
"thymikee"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/issues/8568",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
257509853
|
Improve docs for
Summary
Make it clear how to use the .toThrow method.
Test plan
Just docs.
Codecov Report
Merging #4478 into master will not change coverage.
The diff coverage is n/a.
@@ Coverage Diff @@
## master #4478 +/- ##
=======================================
Coverage 56.84% 56.84%
=======================================
Files 186 186
Lines 6298 6298
Branches 3 3
=======================================
Hits 3580 3580
Misses 2717 2717
Partials 1 1
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 c4844a6...9c0d129. Read the comment docs.
|
gharchive/pull-request
| 2017-09-13T20:24:32 |
2025-04-01T04:34:13.433226
|
{
"authors": [
"codecov-io",
"diegofaria"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/pull/4478",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
349586479
|
Fixed bug in example code
Summary
Fixed bug in example code: mutated the previous state without the use of a callback in setState
Codecov Report
Merging #6828 into master will not change coverage.
The diff coverage is n/a.
@@ Coverage Diff @@
## master #6828 +/- ##
=======================================
Coverage 63.43% 63.43%
=======================================
Files 235 235
Lines 9115 9115
Branches 3 4 +1
=======================================
Hits 5782 5782
Misses 3332 3332
Partials 1 1
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 9093a3c...bcee3f9. Read the comment docs.
|
gharchive/pull-request
| 2018-08-10T16:50:43 |
2025-04-01T04:34:13.438459
|
{
"authors": [
"codecov-io",
"davidblnc"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/pull/6828",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
388831341
|
Update sane package to avoid a security warning
An underlying library has a security vulnerability
https://www.npmjs.com/advisories/722
Note: this file should be refresh in general as a whole.
Hey! Thanks for the PR but it's a duplicate of https://github.com/facebook/jest/pull/7322.
Also, I can see that you're only updating yarn.lock which does not affect npm nor Yarn in userland.
|
gharchive/pull-request
| 2018-12-07T22:07:57 |
2025-04-01T04:34:13.440417
|
{
"authors": [
"gkohen",
"thymikee"
],
"repo": "facebook/jest",
"url": "https://github.com/facebook/jest/pull/7484",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2020204469
|
fixed issue 4692 where 'www' would be accepted as domain name
Fixed issue https://github.com/facebook/lexical/issues/4692.
The problem occurred when manually typing a link with www, ie: https://www.12345.com instead of https://12345.com for domains with up to 6 characters.
In this case the Regex would match www as the domain and the actual domain as the TLD, because the TLD matches up to 6 characters.
We can get around this problem by not allowing www as the domain part using a negative lookahead.
Hi,
You are right in that this does not address the root problem. The original regex does match both URLs in the example I gave.
This was supposed to be a work around. However, I had not considered other subdomains, which this hot fix does not address. I think you should close this PR, my apologies.
|
gharchive/pull-request
| 2023-12-01T06:33:41 |
2025-04-01T04:34:13.455088
|
{
"authors": [
"mbongard"
],
"repo": "facebook/lexical",
"url": "https://github.com/facebook/lexical/pull/5318",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
144233598
|
When trying to use in Programmatic API es7 errors
Just using provided example produces:
async function downloadFileAsync(url: string, cookies: ?string): Promise<string> {
^^^^^^^^
SyntaxError: Unexpected token function
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
at Module._extensions..js (module.js:416:10)
at Object.require.extensions.(anonymous function) [as .js] (****/node_modules/babel-register/lib/node.js:134:7)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (****/node_modules/mention-bot/run-mention-bot.js:12:18)
at Module._compile (module.js:409:26)```
I'm sorry but I don't have the time to help you investigate what is going wrong :( I'm going to close down this issue, but feel free to keep posting here and others to help out.
|
gharchive/issue
| 2016-03-29T11:25:17 |
2025-04-01T04:34:13.464218
|
{
"authors": [
"Nikamura",
"vjeux"
],
"repo": "facebook/mention-bot",
"url": "https://github.com/facebook/mention-bot/issues/100",
"license": "bsd-3-clause",
"license_type": "permissive",
"license_source": "bigquery"
}
|
241423866
|
Passing path to .babelrc as a packager option (programmatic and CLI)
In the transformer there's this comment referring to the .babelrc lookup:
// In the future let's look into adding a command line option to specify
// this location.
https://github.com/facebook/metro-bundler/blob/master/packages/metro-bundler/src/transformer.js#L54
At Expo we use a different .babelrc internally (for monorepo reasons) than in our OSS repos so being able to specify a different .babelrc without having to fork the default transformer is helpful. I was going to work on a PR for this, is this still a feature you'd want? I was thinking it'd probably be a CLI option like --babelrc and programmatic option like babelRCPath that gets passed through to the transformer.
I'm in favor of this. Ideally this would be part of TransformOptions and entirely generic, but I'm also fine if this is actually babelRCPath or something.
|
gharchive/issue
| 2017-07-08T04:17:10 |
2025-04-01T04:34:13.466346
|
{
"authors": [
"cpojer",
"ide"
],
"repo": "facebook/metro-bundler",
"url": "https://github.com/facebook/metro-bundler/issues/24",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
251666968
|
SpellCheck broken on Samsung devices (S8)
Is this a bug report?
yes
Have you read the Contributing Guidelines?
yes
Environment
react-native -v: 0.46.4
node -v: v6.9.5
npm -v: 3.10.10
yarn --version: 0.21.3
Then, specify:
Target Platform: Android (Samsung)
Development Operating System: MacOS
Build tools: using create-react-native-app and Expo
Steps to Reproduce
(Write your steps here:)
Use Samsung S8 with latest firmware (should be reproducible S6 and above)
Enable Spell Checker in the phone menu
Create controlled <TextInput value={this.state.val} onChangeText={this.onChange} editable={true} spellCheck={true} />
Run the app and input some obviously wrong spelled text, (e.g. aiefsjaliesfj or adsjfaleifjlaisef :))
Expected Behavior
I would expect the text input to underline the invalid text with red line, allowing me to click it and select from close correctly spelled candidates.
Actual Behavior
The red line just flashes and then disappears, breaking the system spell check feature.
Reproducible Demo
https://snack.expo.io/B1-6Lw_uW
Fire this up and insert some text.
The red line just flashes and then disappears, breaking the system spell check feature.
spell check is ios only.
Well even though the prop might not be supported, TextInput still breaks the native functionality.
|
gharchive/issue
| 2017-08-21T14:02:23 |
2025-04-01T04:34:13.499842
|
{
"authors": [
"chirag04",
"george-cz"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/15590",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
259568626
|
Installation issue in: 'react-native-tab-view'
Main Error during installation of react-native-tab-view: Couldn't find any versions for "react-native-background-geolocation-android" that matches "2.7.1"
Is this a bug report?
yes
Have you read the Contributing Guidelines?
yes
Environment
OS: macOS Sierra 10.12.5
Node: 6.11.0
Yarn: 1.0.2
npm: 5.3.0
Watchman: 4.9.0
Xcode: Version 8.3.3 (8E3004b)
Steps to Reproduce
I was trying to add the react-native-tab-view library in one of my existing project. So I did:
yarn add react-native-tab-view
inside my project directory.
Expected Behavior
The library should get installed/Add in my project.
Actual Behavior
It threw an unexpected error:
yarn add react-native-tab-view
yarn add v1.0.2
info No lockfile found.
[1/4] 🔍 Resolving packages...
warning polyline@0.2.0: This module is now under the @mapbox namespace: install @mapbox/polyline instead
warning connect@2.30.2: connect 2.x series is deprecated
warning node-uuid@1.4.7: Use uuid module instead
Couldn't find any versions for "react-native-background-geolocation-android" that matches "2.7.1"
? Please choose a version of "react-native-background-geolocation-android" from
this list: (Use arrow keys)
❯ 0.0.1-security
###Furthur,
If I proceed by selecting the '0.0.1-security', I get an error in the installation.
To get full error log: click here
This is an issue in your project setup.
|
gharchive/issue
| 2017-09-21T17:10:47 |
2025-04-01T04:34:13.507659
|
{
"authors": [
"prasang7",
"satya164"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/16058",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
298201565
|
StatusBar BackgroundColor not working
Is this a bug report?
Yes
Have you read the Contributing Guidelines?
Yes
Environment
Environment:
OS: Win 10
Node: 8.9.2
Yarn: 1.3.2
Packages: (wanted => installed)
react-native: 0.52.0 => 0.52.0
react: 16.2.0 => 16.2.0
Target Platform: Android
Steps to Reproduce
<StatusBar backgroundColor = "blue" />
Expected Behavior
StatusBar color must be blue
Actual Behavior
Reproducible Demo
https://snack.expo.io/BJtpkfOwG
If you're using Expo, try configuring it in app.json instead: https://docs.expo.io/versions/latest/guides/configuring-statusbar
|
gharchive/issue
| 2018-02-19T09:04:06 |
2025-04-01T04:34:13.514318
|
{
"authors": [
"jpotterm",
"salihkiraz"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/18018",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
404801125
|
jsireact headers are not found during build
Environment
React Native Environment Info:
System:
OS: macOS 10.14.2
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Memory: 1.59 GB / 32.00 GB
Shell: 5.7 - /usr/local/bin/zsh
Binaries:
Node: 11.8.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.7.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5199772
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.6.3 => 16.6.3
react-native: ^0.58.3 => 0.58.3
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-create-library: 3.1.2
react-native-wahed-onfido-sdk: 1.0.0
Description
Building react-native fails as it cannot find the jsireact headers in the correct location.
They are referenced as jsireact/*.h, however the directory is under ReactCommon/jsiexecutor/jsireact (has it been moved?).
Copying the directory to ReactCommon/jsireact solves the build.
Reproducible Demo
I met the same problem
There are a couple workarounds that can get you unstuck. One is to prepend all the failing imports with jsiexecutor/ ... the other is you can update the header search paths for the JSIExecutor to include the new folder which IMO would be the preferred approach because it doesn't require you to change source code. After doing that just run pod install again and you should be good to go.
@hramos I created a new library project using react-native-create-library, then added the React libs to my Podfile and did a pod install. After that it doesn't build from Xcode. The error is very clear.
👍 4
Same issue here after upgrade to .58.3 :/
How do i fix that error? To me still happening :/, now with .58.4
|
gharchive/issue
| 2019-01-30T14:39:16 |
2025-04-01T04:34:13.522115
|
{
"authors": [
"amccarri",
"andresmtz98",
"fsfhiyg",
"jantebeest",
"xiaoyangrun"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/23217",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
505423121
|
React Native doesn't support newest Node (12.11.1)
React Native version: 0.61
(System:
OS: Windows 10
CPU: (16) x64 Intel(R) Xeon(R) CPU E5-2630 v3 @ 2.40GHz
Memory: 10.17 GB / 31.91 GB
Binaries:
Node: 12.11.1 - C:\Program Files\nodejs\node.EXE
Yarn: 1.17.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.11.3 - C:\Users\SOMEONE\AppData\Roaming\npm\npm.CMD
SDKs:
Android SDK:
API Levels: 19, 21, 22, 23, 24, 27, 28, 29
Build Tools: 19.1.0, 21.1.2, 22.0.1, 23.0.1, 23.0.2, 23.0.3, 27.0.3, 28.0.3, 29.0.2
System Images: android-19 | ARM EABI v7a, android-19 | Intel x86 Atom, android-23 | Google APIs ARM EABI v7a, android-23 | Google APIs Intel x86 Atom, android-24 | Android TV Intel x86 Atom, android-24 | Android Wear ARM EABI v7a, android-24 | Android Wear Intel x86 Atom, android-24 | ARM 64 v8a, android-24 | ARM EABI v7a, android-24 | Intel x86 Atom, android-24 | Intel x86 Atom_64, android-28 | Intel x86 Atom_64, android-29 | Google APIs Intel x86 Atom
Android NDK: 17.1.4828580
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.2 => 0.61.2)
Steps To Reproduce
Follow "Getting Started" guide to install latest Node version
Attempt to run "react-native run-android" on Windows using Emulator or physical device
Fails
Describe what you expected to happen:
Sample app works
Snack, code example, screenshot, or link to a repository:
Related issue here was closed prematurely by author: https://github.com/facebook/react-native/issues/26598
After some investigation i found the bug and already created a pull request for the Metro Bundler
https://github.com/facebook/metro/pull/464
hopefully this gets accepted soon.
Is it clearly fixed?
@gluons @NyauIf
Just update metro-react-native-babel-preset to latest 0.59.0 version and issue will be fixed.
I'm on latest NodeJS 12.18.0 and react-native 0.62.2
I believe this has been fixed and can be closed.
In addition to @oleksandr-dziuban 's report above: our project has been using Node 12 for some time, with RN v0.61.5, and we've seen no sign of problems related to the Node version.
|
gharchive/issue
| 2019-10-10T17:59:07 |
2025-04-01T04:34:13.529648
|
{
"authors": [
"Coruscate5",
"NyauIf",
"gluons",
"gnprice",
"oleksandr-dziuban"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/26808",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
64684282
|
[Text] Text component does not highlight
Text components with onPress handlers don't highlight. The RCTIsHighlightedAttributeName attribute is set on the attributed string but it is unused afterwards.
See the "Touchable* and onPress" demo in the UIExplorer for a test case.
Yup, I think this only work in our internal text component - hopefully we can get this working soon in OSS.
On Mar 26, 2015, at 8:24 PM, James Ide notifications@github.com wrote:
Text components with onPress handlers don't highlight. The RCTIsHighlightedAttributeName attribute is set on the attributed string but it is unused afterwards.
See the " and onPress" demo in the UIExplorer for a test case.
—
Reply to this email directly or view it on GitHub.
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.
This has been fixed in master.
|
gharchive/issue
| 2015-03-27T03:24:18 |
2025-04-01T04:34:13.532920
|
{
"authors": [
"facebook-github-bot-3",
"ide",
"sahrens"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/303",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1929734356
|
[UPDATED] Free Instagram Followers Generator Updated 2023 Free Latest Version Work 100% Now All Time
Description
Followers generator for instagram without human verification - Anyone and everyone are on Instagram, and with all of those people available sharing and commenting on posts and pictures, you'd think gaining followers would have been a little bit of cake. But, like the majority of things in life, developing a well-established social media marketing presence takes patience and determination. Even the experts say it's hard work.
CLICK HERE TO GET FREE NOW
CLICK HERE TO GET FREE NOW
In respect with Social Media Growth Specialist, Talia Koren, developing a healthy following on any social media marketing platform is a huge commitment, and gaining those precious likes and followers takes strategy, skill, and a lot of time. free instagram followers and likes unlimited,free instagram followers apk 2020,free instagram followers app download,free instagram followers apkpure,free instagram followers begeni,free instagram followers boost,free instagram followers by malik vasid,free instagram followers bot
Instagram is getting bigger each day, so boosting your profile's fame and visibility gets even harder. New people are signing up and starting to post content on Instagram as you read this article, so the competition gets extremely tough. But you do not need to worry, because we, InstaFollowers, are here to help you with excellent products. If you want to buy or learn more about how to buy Instagram followers. If you wish to try our high-quality product without spending any money, continue reading to find out how to do so.
The follower feature is one of the central elements of social media platforms like Instagram, Facebook, Twitter, and many more. The purpose of this element is to keep you connected with the people and brands you love so that you can access the most recent news. Vice versa, your followers can see what you are doing on that platform.
When Instagram first launched, it was an entertainment platform. Now, it is beyond entertainment. It is possible to find all kinds of businesses and their advertisements on Instagram. You can get free Instagram followers for your business account as well. Not only are organic followers interested in your follower number, but also other businesses as well. If you don't want to fall behind your competitors on Instagram, you should grow your account with followers. This way, you will create a rivalry between your account and the others. However, it is always better to be one step ahead. It will gain you more than you can think of.
Why Should You Try Free Instagram Followers Service?
Social media platforms have been increasing their influence and value since the last decade. With social media, people can reach millions of users worldwide using that app/platform almost instantly. The more they get organic reach to their profiles, the more they get popular, sell their products or services, and increase their visibility. Increase Instagram followers freely and achieve
People and companies try different methods to reach larger audiences, and buying followers are one of them. When they buy a service that provides them with Instagram followers, their audience widens, and they have a better chance of making people involved in their business and profile. Try our free Instagram followers trial and start taking steps forward.
Our service is one of a kind because it offers you free Instagram followers with no survey. There are many other providers that give you free Instagram followers bots with surveys or other stuff, InstaFollowers gives you free Instagram followers with no verification at all.
React Native Version
new
Output of npx react-native info
new
Steps to reproduce
new
Snack, screenshot, or link to a repository
new
ghfghgfh
|
gharchive/issue
| 2023-10-06T09:02:48 |
2025-04-01T04:34:13.539626
|
{
"authors": [
"arifs077",
"dfhtfghftj"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/39890",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2226375730
|
When Nesting a Flatlist inside a Flatlist both are horizontal child flatlist in not rendering horizontally
Description
Flatlist inside a horizontal flatlist is not rendering horizontally
Steps to reproduce
Create a component below
import React from 'react';
import { FlatList, View, Text } from 'react-native';
const ParentComponent = () => {
const parentData = [{ id: 'a' }, { id: 'b' }]; // Example parent data
const childData = [{ id: '1' }, { id: '2' }, { id: '3' }]; // Example child data
const renderChildItem = ({ item }) => (
<View style={{ width: 100, height: 100, margin: 10, backgroundColor: 'lightblue' }}>
{item.id}
);
const renderChildFlatList = () => (
<FlatList
data={childData}
renderItem={renderChildItem}
keyExtractor={item => item.id}
horizontal={true}
showsHorizontalScrollIndicator={false}
/>
);
const renderParentItem = ({ item }) => (
<View style={{ width: 200, height: 200, margin: 10, backgroundColor: 'lightcoral' }}>
Parent Item {item.id}
{renderChildFlatList()}
);
return (
<FlatList
data={parentData}
renderItem={renderParentItem}
keyExtractor={item => item.id}
horizontal={true}
showsHorizontalScrollIndicator={false}
/>
);
};
export default ParentComponent;
React Native Version
0.72.0
Affected Platforms
Runtime - Android, Runtime - iOS
Output of npx react-native info
System:
OS: macOS 14.0
CPU: (8) arm64 Apple M2
Memory: 106.58 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 21.7.1 - /opt/homebrew/bin/node
Yarn: 1.22.19 - ~/.nvm/versions/node/v18.16.0/bin/yarn
npm: 10.5.0 - /opt/homebrew/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.15.2 - /Users/hardik/.rbenv/shims/pod
SDKs:
iOS SDK:
Platforms: DriverKit 23.2, iOS 17.2, macOS 14.2, tvOS 17.2, visionOS 1.0, watchOS 10.2
Android SDK: Not Found
IDEs:
Android Studio: 2022.3 AI-223.8836.35.2231.10671973
Xcode: 15.2/15C500b - /usr/bin/xcodebuild
Languages:
Java: 11.0.21 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.2.0 => 18.2.0
react-native: 0.71.16 => 0.71.16
react-native-macos: Not Found
npmGlobalPackages:
*react-native*: Not Found
(node:51862) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
npm notice
npm notice New patch version of npm available! 10.5.0 -> 10.5.1
npm notice Changelog: https://github.com/npm/cli/releases/tag/v10.5.1
npm notice Run npm install -g npm@10.5.1 to update!
npm notice
Stacktrace or Logs
Not an crash
Reproducer
added above
Screenshots and Videos
⚠️ Missing Reproducible Example
ℹ️ We could not detect a reproducible example in your issue report. Please provide either:
If your bug is UI related: a Snack
If your bug is build/update related: use our Reproducer Template. A reproducer needs to be in a GitHub repository under your username.
https://snack.expo.dev/N5AAb_ERRXBHw7sY6vIa1
hey, @hardikamber! try comment horizontal={true} in parent Flatlist
Same issue here
|
gharchive/issue
| 2024-04-04T19:44:06 |
2025-04-01T04:34:13.550785
|
{
"authors": [
"cavaalex",
"hardikamber",
"mensonones"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/43875",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2235248143
|
TypeError: _reactNative.AccessibilityInfo.announceForAccessibilityWithOptions is not a function
Description
When using AccessibilityInfo.announceForAccessibility no problems come when I run jest, but when I change it to AccessibilityInfo.announceForAccessibilityWithOptions I get: TypeError: _reactNative.AccessibilityInfo.announceForAccessibilityWithOptions is not a function
I checked node_modules/react-native/jest/setup.js file I can see that under AccessibilityInfo there is no announceForAccessibilityWithOptions mocking, but when I change announceForAccessibility -> announceForAccessibilityWithOptions in that file then tests run without issues (not going to obviously leave it like this, just tested if that helps).
I tried to mock announceForAccessibilityWithOptions within my own jest.setup file, but that created a lot of different issues.
Steps to reproduce
Use AccessibilityInfo.announceForAccessibilityWithOptions() and run jest and you'll get an issue TypeError: _reactNative.AccessibilityInfo.announceForAccessibilityWithOptions is not a function
React Native Version
0.73.6
Affected Platforms
Build - MacOS
Output of npx react-native info
info Fetching system and libraries information...
System:
OS: macOS 14.2.1
CPU: (10) arm64 Apple M2 Pro
Memory: 613.63 MB / 32.00 GB
Shell:
version: "5.9"
path: /bin/zsh
Binaries:
Node:
version: 20.11.0
path: ~/.nvm/versions/node/v20.11.0/bin/node
Yarn:
version: 1.22.19
path: /opt/homebrew/bin/yarn
npm:
version: 10.2.4
path: ~/.nvm/versions/node/v20.11.0/bin/npm
Watchman:
version: 2023.12.04.00
path: /opt/homebrew/bin/watchman
Managers:
CocoaPods:
version: 1.14.2
path: /Users/jonnesten/.asdf/shims/pod
SDKs:
iOS SDK:
Platforms:
- DriverKit 23.2
- iOS 17.2
- macOS 14.2
- tvOS 17.2
- visionOS 1.0
- watchOS 10.2
Android SDK: Not Found
IDEs:
Android Studio: 2023.1 AI-231.9392.1.2311.11076708
Xcode:
version: 15.2/15C500b
path: /usr/bin/xcodebuild
Languages:
Java:
version: 17.0.9
path: /usr/bin/javac
Ruby:
version: 3.2.2
path: /Users/jonnesten/.asdf/shims/ruby
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.73.6
wanted: 0.73.6
react-native-macos: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: true
newArchEnabled: false
Stacktrace or Logs
`TypeError: _reactNative.AccessibilityInfo.announceForAccessibilityWithOptions is not a function`
Reproducer
n/a
Screenshots and Videos
No response
Was able to mock it in my own jest.setup.ts file like this:
jest.mock('react-native/Libraries/Components/AccessibilityInfo/AccessibilityInfo', () => {
return {
_esModule: true,
default: {
addEventListener: jest.fn(),
announceForAccessibilityWithOptions: jest.fn(),
isScreenReaderEnabled: jest.fn(() => Promise.resolve(false)),
},
};
});
I am also facing similar issuw with react native version 0.73.5.
Here how my jest.config.js looks like:
`
module.exports = {
preset: 'react-native',
moduleFileExtensions: ['ts', 'tsx', 'js', 'jsx', 'json', 'node'],
clearMocks: true,
transform: {
'^.+\.(js|jsx|ts|tsx)$': 'babel-jest'
},
transformIgnorePatterns: [
'node_modules/(?!@codler|(?!(jest-)?react-native)|@react-navigation|@sentry/react-native|native-base-shoutem-theme|@react-native-community|native-base)'
],
collectCoverage: true,
collectCoverageFrom: ['src/**/*.{js,jsx}'],
coverageReporters: ['html'], // json-summary
setupFilesAfterEnv: ['/jest.setup.js'],
coverageDirectory: './coverage',
moduleNameMapper: {
'\.(jpg|jpeg|png|gif|otf|webp|svg|ttf|mp4|webm|wav|mp3|m4a|aac)$':
'identity-obj-proxy'
},
moduleDirectories: ['node_modules', __dirname],
modulePathIgnorePatterns: ['node_modules']
`
Can someone look itno this issue please or do I need to change anything in jest config?
+1
+1
|
gharchive/issue
| 2024-04-10T10:22:44 |
2025-04-01T04:34:13.560913
|
{
"authors": [
"Jonnboy91",
"Shivangi2909",
"anabeatrizzz",
"chancesmith"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/44014",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
125135370
|
[WebView] WebView on android can`t execute javascript
<WebView
style={[styles.webview, {
height: this.state.height || 400
}]}
javaScriptEnabled={true}
bounces={false}
onNavigationStateChange={this._onNavigationStateChange}
html={this._getHTML(content)}
/>
javascript inside WebView page do not execute.
On iOS it works fine.
You need to enable JavaScript via a a prop - http://facebook.github.io/react-native/docs/webview.html#javascriptenabled
@satya164
I have tried that.
Didnt work. Tried to use injectedJavaScript didnt work either
I tried to use react-native-webview-android
Javscript inside page didn`t execute.
But javascript through injectedJavaScript worked
Can you give a minimal reproducable example of the code that's not working?
cc @mkonicek
We don't provide supports third party plugins Have you tried the one included in React Native?
@satya164
yes.
after I tried everything in React Native.it didn`t work out,then I tried the third party plugin.
/**
* Sample React Native App
* https://github.com/facebook/react-native
*/
'use strict';
var React = require('react-native');
var {
AppRegistry,
StyleSheet,
Text,
View,
WebView
} = React;
let html = `
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="format-detection" content="telephone=no" />
<meta name="viewport" content="width=device-width, initial-scale=1, user-scalable=no" />
<style>
html,
body{
overflow: hidden;
}
*{
padding: 0;
margin: 0;
font-size: 14px !important;
color: #666 !important;
max-width: 100% !important;
}
</style>
</head>
<body>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
<div>test</div>
</body>
<script>
(function () {
document.write('nothing');
}());
</script>
</html>
`;
var marry = React.createClass({
render: function() {
return (
<View style={styles.container}>
<WebView
style={[{
height: 400,
width: 320
}]}
javaScriptEnabled={true}
bounces={false}
onNavigationStateChange={this._onNavigationStateChange}
html={html}
/>
</View>
);
}
});
var styles = StyleSheet.create({
container: {
flex: 1,
justifyContent: 'center',
alignItems: 'center',
backgroundColor: '#F5FCFF',
},
welcome: {
fontSize: 20,
textAlign: 'center',
margin: 10,
},
instructions: {
textAlign: 'center',
color: '#333333',
marginBottom: 5,
},
});
AppRegistry.registerComponent('marry', () => marry);
same code.
different result.
closed
The attribute should be javaScriptEnabledAndroid instead of javaScriptEnabled as document said.
javaScriptEnabledAndroid is only used on 0.17.0
0.18.0 javaScriptEnabled works fine
Is there a resolution for this problem? As of 0.20 I still can't get Javascript to work on Android.
Also can't get it to work... Here's my render:
render() {
let html = '<div id="myContent">This is my name</div>';
let jsCode = 'document.querySelector("#myContent").style.backgroundColor = "red"';
return (
<View>
<WebView
source={{html: html}}
injectedJavascript={jsCode}
javaScriptEnabled={true}
style={this.props.style}
/>
</View>
);
}
And the result:
The div background should be red.
It seems to work if I include the javascript as a script in html like this:
render() {
let html = `
<div id="myContent">This is my name</div>
<script>
document.querySelector("#myContent").style.backgroundColor = "red"\
</script>
`;
return (
<View>
<WebView
source={{html: html}}
javaScriptEnabled={true}
style={{ width: 100, height: 100}}
/>
</View>
);
}
Nothing is working is there is any other method to do it
Worked for me by adding baseUrl like this:
<WebView
javaScriptEnabled={true}
source={{html: myHtml, baseUrl: "/"}}
/>
Set true both javaScriptEnabled and domStorageEnabled
javaScriptEnabled={true}
domStorageEnabled={true}
on android I got it finally to work after I've put semicolon ";" at the end of every command, for example;
this works:
let jsCode = `
document.body.style.backgroundColor = \'#6DAF45\';
var menuButton = document.getElementById("responsive-menu-button");
menuButton.parentNode.removeChild(menuButton);
var header = document.getElementById("header");
header.style.visibility = \'hidden\';
header.style.height = 0;
var innerBannerArea = document.getElementById("inner-banner-area");
innerBannerArea.style.height = 1;
innerBannerArea.style.opacity = 0.0;
var footer = document.getElementById("footer");
footer.style.visibility = \'hidden\';
`
and this breaks the whole javascript, check line 2 in "jsCode" in the variable:
let jsCode = `
document.body.style.backgroundColor = \'#6DAF45\';
var menuButton = document.getElementById("responsive-menu-button");
menuButton.parentNode.removeChild(menuButton)
var header = document.getElementById("header");
header.style.visibility = \'hidden\';
header.style.height = 0;
var innerBannerArea = document.getElementById("inner-banner-area");
innerBannerArea.style.height = 1;
innerBannerArea.style.opacity = 0.0;
var footer = document.getElementById("footer");
footer.style.visibility = \'hidden\';
`
The issue seems to depend on the android SDK version.
using 23 fails and it works using version 24 and 25 .
this might require more testing on real device like samsung to see if it works on 23 on some real devices.
@iineva You saved me. I searched whole day. My opencart checkout page is not working in android webview. But by adding setDomStorageEnabled(true) it's worked like charm. Thank you so much.
@Goran1708 Thanks. Solved my problem.
I've figured out Android WebView bug.
Even in Android API >= 23 and react-native 0.52.
=> If your JavaScript code contain any comment => javascript will not run
I have to remove every comments in order for JavaScript to run.
I can confirm that WebView Javascript code is not executed on android 4.4.2 device (API 19) and maybe some higher versions of android. Neither inside blocks in html, neither inside injectedJavaScript prop. Tried everything described here. I use RN 0.50.0.
Have someone faced with this issue and solved it somehow?
In my case, I was using let instead of var and webview was not able to execute my javascript. Which makes sense. Please double check that you are using plain javascript not ES6 syntax. This is just one of the possibilities.
It’s working on real device but not on emulator
|
gharchive/issue
| 2016-01-06T08:44:16 |
2025-04-01T04:34:13.577174
|
{
"authors": [
"Goran1708",
"ThomasXu18",
"atulamuwa",
"bomalley",
"ggsrivas",
"if4lcon",
"iineva",
"jcsmesquita",
"jpoutrin",
"magicismight",
"nopopon",
"satya164",
"solominh",
"uc-des",
"ziks21"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/5143",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
171699177
|
Duplicate files copied in APK error when integrating with existing Android project
I'm trying to add React Native to an existing Android project using Gradle. I followed the instructions here: https://facebook.github.io/react-native/docs/integration-with-existing-apps.html
When I try to run my app from Android Studio I get this error:
> com.android.build.api.transform.TransformException: com.android.builder.packaging.DuplicateFileException: Duplicate files copied in APK lib/armeabi-v7a/libgnustl_shared.so
File1: .../build/intermediates/exploded-aar/com.facebook.react/react-native/0.20.1/jni
File2: .../build/intermediates/exploded-aar/com.spotify/spotify-player/1.0.0-beta12/jni
It looks like both React Native and the Spotify dependencies require the same file: libgnustl_shared.so.
There is a Stack Overflow post with a hacky fix for this, but I'm guessing there should be a more elegant solution than this: http://stackoverflow.com/a/37201791/62
It would be nice to document the solution for this in the React Native page I linked above, as this could happen to many people when first trying to integrate React Native.
I'm on Mac OS X 10.11.6.
I was able to resolve this and documented my solution here: http://stackoverflow.com/a/39584838/62
It would be nice if React Native could solve this though.
is there any solution? i have meet this problem too, need some help
Two workarounds:
Follow my link above: http://stackoverflow.com/a/39584838/62
Delete libgnustl_shared.so from the node_modules React Native AAR file. You'll have to extract the AAR and then recreate it. It's just a zip with the extension renamed. Unfortunately this approach won't work directly if you use version control as node_modules is typically ignored. If you go with this approach you could add the AAR to version control.
after delete and recreate aar file, the android studio doesnt find react-native.jar.It seems aar file can not use after zip and rename
What did you rename? You should rename the zip back to .aar after you re-zip it. Also make sure that you perserve the folder structure so it's the same before and after removing that .so file.
My rename step is as you said, back to .aar and perserve same folder structure,but it doesn't work,and android studio indicated that could not find react-native.jar @lyahdav
I check it again and find its my fault, using macOS rename doesn't see all file name, it became react-native-0.49.5.aar.zip, after I fixed this problem and put .aar again, android studio went wrong, the log is below:
Execution failed for task ':improvider:processDebugResources'.
java.io.IOException: Failed to read manifest /Users/eflake/.android/build-cache/6bbb02a443ad92e64d8e56ea09538e468780ea03/output/AndroidManifest.xml
Finally i found the mistake cause by the step of re-zip, I should re-zip all files instead of outer folder, it was success now, thanks for you help @lyahdav
|
gharchive/issue
| 2016-08-17T16:15:43 |
2025-04-01T04:34:13.586593
|
{
"authors": [
"EflakeEver",
"lyahdav"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/issues/9454",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
209796408
|
CLI: Add support for templates fetched from npm
This PR allows anyone to publish templates for React Native.
It's possible for people to publish modules for React Native, we should also support custom templates. A suggestion from a Cordova mantainer where they did the same thing suggests this is useful:
https://github.com/mkonicek/AppTemplateFeedback
How it works
I published a sample template react-native-template-demo.
(GitHub: https://github.com/mkonicek/react-native-template-demo)
With this PR anyone can then use that template:
react-native init MyApp --template demo
The convention is: if someone publishes an npm package called react-native-template-foo, people can use it by running react-native init MyApp --template foo.
Test plan
Published the stock 'navigation' template to npm under the name 'demo':
https://www.npmjs.com/package/react-native-template-demo
Also added a native dependency (react-native-vector-icons) to the template to test that linking native dependencies works.
Generated app works:
react-native init MyApp --template demo
MyApp/package.json contains all the dependencies of the template (react-navigation, react-native-vector-icons)
Xcode and Gradle build files of MyApp contain react-native-vector-icons
Checked that existing workflows still work:
Built-in template (local-cli/templates/HelloNavigation):
react-native init MyApp --template navigation
The app works (screenshots are the same as above).
Checked that existing workflows still work:
No template:
react-native init MyApp
Code looks great! Philosophically, I'm wondering if you should keep built in templates. Since a template being built in would be extra management and need to be exclusive. You'll have to have a rule-set on who's PRs can be built in and who's not. Regardless of size implications, this puts an interesting onus on the PR team.
My suggestion is go 100% npm, with a purely documentation based guide of examples. This feels more OSS and keeps the templates as proper tool for the community.
Also, as a code management initiative, templates being in their own repo and outside the local-cli feels right.
Thanks for the review @GantMan. Addressed comments, merging.
is it in future plan to be able to add devDependencies and additional scripts to the template?
@mkonicek Will there be documentation for how to create a template? Are custom native folders such as Android and iOS allowed for template projects. Suppose I want my template to have a custom native Android Activity/iOS ViewController, is that possible, or is only JS related files observed by the template?
Couple notes: @mkonicek doesn't work with Facebook anymore, but I'm not sure, he might still be supporting this feature.
@jpshelley - if you want to use Ignite, we have docs etc on using our template/plugin system, and any gaps you find I'd be happy to help with. https://github.com/infinitered/ignite/blob/master/docs/advanced-guides/creating-boilerplates.md
Disclaimer: It doesn't come with react-native, but it has quite a few features to help plugins etc.
|
gharchive/pull-request
| 2017-02-23T15:35:59 |
2025-04-01T04:34:13.596939
|
{
"authors": [
"GantMan",
"amoghbanta",
"jpshelley",
"mkonicek"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/12548",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
470685339
|
Fix/revamp rn tester
Summary
Revamp of RNTester.
Removed non-core components for Android that will be moved to react-native-community soon.
Fixed status bar style in iOS for the first launch.
Removed non-core components for iOS that will be moved to react-native-community soon.
Changelog
[General] [Deprecated] - Removed non-core components from RNTester for Android & iOS
Test Plan
Tested the RNTester app after changes.
Fixed all unit tests that might fail after this change.
Screenshots
iOS
Android
Thank you for your PR. I would prefer to keep these examples around until we remove each individual component which we can only do from Facebook's side.
Would you mind changing your PR to only include the status bar change? Thank you!
Closing due to inactivity. Please create a new PR if you have time to get back to this with the feedback from me.
|
gharchive/pull-request
| 2019-07-20T15:21:36 |
2025-04-01T04:34:13.601267
|
{
"authors": [
"cpojer",
"satheeshwaran"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/25746",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
1359657476
|
feat: Add support for verticalAlign style
Summary
This adds support for the verticalAlign style attribute, mapping the already existing textAlignVertical attribute as requested on https://github.com/facebook/react-native/issues/34425. This PR also updates the TextExample.android on the RNTester in order to facilitate the manual QA of this.
Changelog
[Android] [Added] - Add support for verticalAlign style
Test Plan
On Android open the RNTester app and navigate to the Text page
Check the text alignment through the Text alignment section
https://user-images.githubusercontent.com/11707729/188051914-bf15f7eb-e53f-4de5-8033-d1b572352935.mov
Sorry, this needs someone from Meta to import the PR
@cipolleschi @cortinico would you mind importing this?
Sorry, I missed it! But now it has been imported.
Hi @gabrieldonadel, thanks for all your work with these PRs. We recently started to maintain the TypeScript types and it looks like that this PR touches the Flow types in the StyleSheetTypes.js. Could you update also the TypeScript definitions in this file?
Thanks for the update! :D Could you also take care of the lint errors, please? 🙏
Thanks for the update! :D Could you also take care of the lint errors, please? 🙏
@cipolleschi I believe there is some problem with the Danger configuration, all these warnings are about react-native/no-inline-styles even though this rule is disabled here -> https://github.com/facebook/react-native/blob/8edf4e9e3adcc85743e3c86a25ab3748b276a3da/packages/rn-tester/.eslintrc#L3
Could you rebase on main, please? We should have fixed the CI! :D
Could you rebase on main, please? We should have fixed the CI! :D
Sure, done
|
gharchive/pull-request
| 2022-09-02T03:24:06 |
2025-04-01T04:34:13.607838
|
{
"authors": [
"cipolleschi",
"gabrieldonadel",
"necolas"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/34567",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2006675668
|
Schedule a Choreographer callback only if there is ongoing animation
Summary: From sammy-SC, we would like to minimize the number of times that React Native schedules Choreographer calls. For animations, we do not need choreographer running on every frame, it only needs to run on frames that have an animation active. This diff modifies the frame callbacks such that Choreographer calls are only enqueued if there is an ongoing animation.
Reviewed By: sammy-SC
Differential Revision: D50647971
Committed with f9315c6ee13709d3dd1788090237d92fd92ef456
|
gharchive/pull-request
| 2023-11-22T16:09:35 |
2025-04-01T04:34:13.609398
|
{
"authors": [
"cortinico",
"sammy-SC"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/41606",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
147270935
|
showcase- fixed hello dating link to app store
Hi
the link wasn't clickable before, now it is.
Thanks
Why change the URL?
Campaign link to keep track of installation source
@facebook-github-bot shipit
OK cool :)
|
gharchive/pull-request
| 2016-04-10T21:44:22 |
2025-04-01T04:34:13.611072
|
{
"authors": [
"aharons",
"mkonicek"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/6908",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
164506349
|
Android: Implement cancelable option for Alerts
Motivation
In iOS you cannot dismiss alerts by clicking outside of their box, while on Android you can. This can create some inconsistency if you want to have identical behavior on both platforms. This change makes it possible for Android apps to have irremovable/required alert boxes just like in iOS.
This adds an additional parameter to the Alert method. The way to use it is by providing an object with the cancelable property. The cancelable property accepts a boolean value.
This utilizes the Android DialogFragment method setCancelable
Usage example
Alert.alert(
'Alert Title',
null,
[
{text: 'OK', onPress: () => console.log('OK Pressed!')},
],
{
cancelable: false
}
);
Test plan (required)
I added an additional alert to the UIExplorer project where it can be tested. I also added a part in the Dialog Module test to make sure setting cancelable works as it should.
By analyzing the blame information on this pull request, we identified @mkonicek and @foghina to be potential reviewers.
It's been a while since the last commit was reviewed and the labels show this pull request needs review. Based on the blame information for the files in this pull request we identified @mkonicek as a potential reviewer. Could you take a look please or cc someone with more context?
LGTM
cc @dmmiller
Can you please rebase this against master?
Seems good. Looks like it might need a rebase, but then let's do it.
Sounds awesome, looking forward to it!
@kraffslol updated the pull request.
@facebook-github-bot shipit
Thanks for importing.If you are an FB employee go to Phabricator to review internal test results.
|
gharchive/pull-request
| 2016-07-08T10:51:34 |
2025-04-01T04:34:13.616587
|
{
"authors": [
"dmmiller",
"facebook-github-bot-0",
"facebook-github-bot-1",
"facebook-github-bot-3",
"facebook-github-bot-5",
"kraffslol",
"mmazzarolo",
"satya164"
],
"repo": "facebook/react-native",
"url": "https://github.com/facebook/react-native/pull/8652",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
310269575
|
Cannot install reason on mac os x
Hi,
I cannot install reason on a fresh mac osx (Sierra 10.13.3)
Installing node via the official installer 'node-v9.10.1.pkg'
During the installation I have to give the admin password for:
Node.js v9.10.1 to /usr/local/bin/node
npm v5.6.0 to /usr/local/bin/npm
That worked, node is installed, now lets proceed with reason.
The installation according to the description on the web page fails.
$ npm install -g bs-platform
npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules
npm ERR! path /usr/local/lib/node_modules
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall access
npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR! { Error: EACCES: permission denied, access '/usr/local/lib/node_modules'
npm ERR! stack: 'Error: EACCES: permission denied, access \'/usr/local/lib/node_modules\'',
npm ERR! errno: -13,
npm ERR! code: 'EACCES',
npm ERR! syscall: 'access',
npm ERR! path: '/usr/local/lib/node_modules' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.
According to the last line on the error message I go as root,
sudo npm install -g bs-platform
Password:
/usr/local/bin/bsb -> /usr/local/lib/node_modules/bs-platform/lib/bsb
/usr/local/bin/bsc -> /usr/local/lib/node_modules/bs-platform/lib/bsc
/usr/local/bin/bsrefmt -> /usr/local/lib/node_modules/bs-platform/lib/bsrefmt
> bs-platform@2.2.3 postinstall /usr/local/lib/node_modules/bs-platform
> node scripts/install.js
checkoutput: The OCaml compiler, version BuckleScript 2.2.3 (Using OCaml4.02.3+BS )
Standard library directory: /usr/local/lib/node_modules/bs-platform/lib/ocaml
/usr/local/lib/node_modules/bs-platform/lib/bsb.darwin -----> /usr/local/lib/node_modules/bs-platform/lib/bsb.exe
No working prebuilt compiler
No matched compiler found, may re-try
Build a local version of OCaml compiler, it may take a couple of minutes
touch: s.h: Permission denied
touch: m.h: Permission denied
touch: Makefile: Permission denied
./configure: line 200: Makefile: Permission denied
./configure: line 204: Makefile: Permission denied
./configure: line 206: Makefile: Permission denied
./configure: line 211: Makefile: Permission denied
./configure: line 215: Makefile: Permission denied
./configure: line 217: Makefile: Permission denied
./configure: line 221: Makefile: Permission denied
mkdir: /usr/local/lib/node_modules/bs-platform/cg67187-8163: Permission denied
mkdir: /usr/local/lib/node_modules/bs-platform/cg-67187: Permission denied
config.guess: cannot create a temporary directory in /usr/local/lib/node_modules/bs-platform
[ERROR!] Cannot guess host type. You must specify one with the -host option.
touch: s.h: Permission denied
touch: m.h: Permission denied
touch: Makefile: Permission denied
./configure: line 200: Makefile: Permission denied
./configure: line 204: Makefile: Permission denied
./configure: line 206: Makefile: Permission denied
./configure: line 211: Makefile: Permission denied
./configure: line 215: Makefile: Permission denied
./configure: line 217: Makefile: Permission denied
./configure: line 221: Makefile: Permission denied
mkdir: /usr/local/lib/node_modules/bs-platform/cg67187-8163: Permission denied
mkdir: /usr/local/lib/node_modules/bs-platform/cg-67187: Permission denied
config.guess: cannot create a temporary directory in /usr/local/lib/node_modules/bs-platform
Building a local version of the OCaml compiler failed, check the output above for more information. A possible problem is that you don't have a compiler installed.
/usr/local/lib/node_modules/bs-platform/scripts/install.js:111
throw e;
^
Error: Command failed: /usr/local/lib/node_modules/bs-platform/scripts/buildocaml.sh
touch: s.h: Permission denied
touch: m.h: Permission denied
touch: Makefile: Permission denied
./configure: line 200: Makefile: Permission denied
./configure: line 204: Makefile: Permission denied
./configure: line 206: Makefile: Permission denied
./configure: line 211: Makefile: Permission denied
./configure: line 215: Makefile: Permission denied
./configure: line 217: Makefile: Permission denied
./configure: line 221: Makefile: Permission denied
mkdir: /usr/local/lib/node_modules/bs-platform/cg67187-8163: Permission denied
mkdir: /usr/local/lib/node_modules/bs-platform/cg-67187: Permission denied
config.guess: cannot create a temporary directory in /usr/local/lib/node_modules/bs-platform
at checkExecSyncError (child_process.js:575:11)
at Object.execFileSync (child_process.js:593:13)
at tryToProvideOCamlCompiler (/usr/local/lib/node_modules/bs-platform/scripts/install.js:106:27)
at non_windows_npm_release (/usr/local/lib/node_modules/bs-platform/scripts/install.js:156:9)
at Object.<anonymous> (/usr/local/lib/node_modules/bs-platform/scripts/install.js:179:5)
at Module._compile (module.js:649:30)
at Object.Module._extensions..js (module.js:660:10)
at Module.load (module.js:561:32)
at tryModuleLoad (module.js:501:12)
at Function.Module._load (module.js:493:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! bs-platform@2.2.3 postinstall: `node scripts/install.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the bs-platform@2.2.3 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
╭─────────────────────────────────────╮
│ │
│ Update available 5.6.0 → 5.8.0 │
│ Run npm i -g npm to update │
│ │
╰─────────────────────────────────────╯
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/bkb/.npm/_logs/2018-03-31T20_19_01_997Z-debug.log
Any ideas?
Thanks
Thanks for the link.
solution #2 worked for me. For future reference here is what I did (taken for the link : https://docs.npmjs.com/getting-started/fixing-npm-permissions)
Make a directory for global installations:
mkdir ~/.npm-global
Configure npm to use the new directory path:
npm config set prefix '~/.npm-global'
Open or create a ~/.profile file and add this line:
export PATH=~/.npm-global/bin:$PATH
Back on the command line, update your system variables:
source ~/.profile
And then finally:
npm install -g bs-platform
Thanks for the link.
solution #2 worked for me. For future reference here is what I did (taken for the link : https://docs.npmjs.com/getting-started/fixing-npm-permissions)
Make a directory for global installations:
mkdir ~/.npm-global
Configure npm to use the new directory path:
npm config set prefix '~/.npm-global'
Open or create a ~/.profile file and add this line:
export PATH=~/.npm-global/bin:$PATH
Back on the command line, update your system variables:
source ~/.profile
And then finally:
npm install -g bs-platform
I had the same issue. After the above recipe BS installed successfully, but for anything I'm trying to build now I consistently get "Unbound module Pervasives" (even after clean bsc -init x). Searched and tried various things but gave up after an hour. Hints would be welcome. ;)
@rossberg Have you tried install bs-platform locally to a project and calling it locally? ./node_modules/.bin/bsb -make-world?
sudo chown -R $USER /usr/local
|
gharchive/issue
| 2018-03-31T20:25:57 |
2025-04-01T04:34:13.649951
|
{
"authors": [
"bentxt",
"bsansouci",
"rossberg",
"srctxt",
"zhiyilee"
],
"repo": "facebook/reason",
"url": "https://github.com/facebook/reason/issues/1888",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
273145579
|
Fix refmt.js example and add important information about avoiding mis…
…sing module error wiht webpack
Thanks!
|
gharchive/pull-request
| 2017-11-11T13:30:09 |
2025-04-01T04:34:13.651597
|
{
"authors": [
"chenglou",
"glennsl"
],
"repo": "facebook/reason",
"url": "https://github.com/facebook/reason/pull/1633",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
268642053
|
Assertion failure in -[ReporterTask publishDataForEvent:]
when i use xctool to run a test.i got this error:
2017-10-26 11:34:50.088 xctool[3417:348156] *** Assertion failure in -[ReporterTask publishDataForEvent:], /tmp/xctool-20170901-19829-1s5ox9o/xctool-0.3.3/xctool/xctool/ReporterTask.m:193
2017-10-26 11:34:50.093 xctool[3417:348156] *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Failed while write()'ing to the reporter's pipe: Invalid argument (22)'
*** First throw call stack:
(
0 CoreFoundation 0x00007fffb7dc52cb __exceptionPreprocess + 171
1 libobjc.A.dylib 0x00007fffccbd048d objc_exception_throw + 48
2 CoreFoundation 0x00007fffb7dca042 +[NSException raise:format:arguments:] + 98
3 Foundation 0x00007fffb9812c80 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4 xctool 0x0000000108265472 -[ReporterTask publishDataForEvent:] + 787
5 xctool 0x0000000108224b44 PublishEventToReporters + 604
6 xctool 0x000000010821e304 -[TestRunState publishEventToReporters:] + 75
7 xctool 0x000000010821ea78 -[TestRunState endTest:] + 824
8 xctool 0x000000010821bf6d -[Reporter handleEvent:] + 1123
9 xctool 0x000000010821bae8 -[Reporter parseAndHandleEvent:] + 151
10 xctool 0x0000000108262950 __LaunchTaskAndFeedSimulatorOutputAndOtestShimEventsToBlock_block_invoke + 365
11 libdispatch.dylib 0x00007fffcd488524 _dispatch_call_block_and_release + 12
12 libdispatch.dylib 0x00007fffcd47f8fc _dispatch_client_callout + 8
13 libdispatch.dylib 0x00007fffcd4959a0 _dispatch_queue_serial_drain + 896
14 libdispatch.dylib 0x00007fffcd488306 _dispatch_queue_invoke + 1046
15 libdispatch.dylib 0x00007fffcd4816b5 _dispatch_root_queue_drain + 476
16 libdispatch.dylib 0x00007fffcd48148c _dispatch_worker_thread3 + 99
17 libsystem_pthread.dylib 0x00007fffcd6ce5a2 _pthread_wqthread + 1299
18 libsystem_pthread.dylib 0x00007fffcd6ce07d start_wqthread + 13
)
libc++abi.dylib: terminating with uncaught exception of type NSException
Abort trap: 6
please help me
Do you always see this error? Or did it happen once and that's it?
|
gharchive/issue
| 2017-10-26T06:21:10 |
2025-04-01T04:34:13.672334
|
{
"authors": [
"ExtremeMan",
"niuemperor"
],
"repo": "facebook/xctool",
"url": "https://github.com/facebook/xctool/issues/742",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
}
|
2751487382
|
Column mean_exposure doesn't exist."
Hey, I i came across this issue in robyn and it's not going away:
Run all trials and iterations. Use ?robyn_run to check parameter definition
OutputModels <- robyn_run(
InputCollect = InputCollect, # feed in all model specification
cores = NULL, # NULL defaults to (max available - 1)
iterations = 10000, # 2000 recommended for the dummy dataset with no calibration
trials = 8, # 5 recommended for the dummy dataset
ts_validation = TRUE, # 3-way-split time series for NRMSE validation.
add_penalty_factor = FALSE # Experimental feature. Use with caution.
)
Input data has 42 weeks in total: 2023-08-14 to 2024-05-27
Initial model is built on rolling window of 42 week: 2023-08-14 to 2024-05-27
Time-series validation with train_size range of 50%-80% of the data...
Using geometric adstocking with 14 hyperparameters (14 to iterate + 0 fixed) on 15 cores
Starting 8 trials with 10000 iterations each using TwoPointsDE nevergrad algorithm...
Running trial 1 of 8
| | 0%Timing stopped at: 0.73 0.11 0.86
Error in { : task 1 failed - "Can't select columns that don't exist.
✖ Column mean_exposure doesn't exist."
I'd really appreciate if anyone can help me out with this one.
dt_input
A tibble: 65 × 6
DATE Call RESPONSIVE_SEARCH VIDEO_TRUEVIEW_IN_STREAM FB Conversion
1 2023-09-18 00:00:00 0 818. 75.0 501. 220
2 2023-09-25 00:00:00 0 805. 74.2 450. 198
3 2023-10-02 00:00:00 0 781. 70.2 500. 211
4 2023-10-09 00:00:00 0 802. 55.9 509. 194
5 2023-10-16 00:00:00 0.241 801. 69.6 483. 240
6 2023-10-23 00:00:00 2.87 797. 102. 462. 206
7 2023-10-30 00:00:00 18.9 713. 64.4 460. 224
8 2023-11-06 00:00:00 5.99 740. 82.3 510. 238
9 2023-11-13 00:00:00 2.86 818. 72.0 519. 193
10 2023-11-20 00:00:00 0 718. 81.3 481. 187
ℹ 55 more rows
ℹ Use print(n = ...) to see more rows
All sign control are now automatically provided: "positive" for media & organic
variables and "default" for all others. User can still customise signs if necessary.
Documentation is available, access it anytime by running: ?robyn_inputs
InputCollect <- robyn_inputs(
dt_input = dt_input,
dt_holidays = dt_prophet_holidays,
date_var = "DATE", # date format must be "2020-01-01"
dep_var = "Conversion", # there should be only one dependent variable
dep_var_type = "conversion", # "revenue" (ROI) or "conversion" (CPA)
prophet_vars = c("trend", "season", "holiday"), # "trend","season", "weekday" & "holiday"
prophet_country = "US", # input country code. Check: dt_prophet_holidays
paid_media_spends = c( "Call", "RESPONSIVE_SEARCH", "VIDEO_TRUEVIEW_IN_STREAM", "FB"
), # mandatory input
paid_media_vars = c( "Call", "RESPONSIVE_SEARCH", "VIDEO_TRUEVIEW_IN_STREAM", "FB"), # mandatory.
paid_media_vars must have same order as paid_media_spends. Use media exposure metrics like
impressions, GRP etc. If not applicable, use spend instead.
#context_vars = c("events"),
#factor_vars = c("events"), # force variables in context_vars or organic_vars to be categorical
#window_start = "2021-05-03",
#window_end = "2023-12-25",
adstock = "geometric" # geometric, weibull_cdf or weibull_pdf.
)
Warning message:
In check_datadim(dt_input, all_ind_vars, rel = 10) :
There are 7 independent variables & 65 data points. We recommend row:column ratio of 10 to 1
print(InputCollect)
Total Observations: 65 (weeks)
Input Table Columns (6):
Date: DATE
Dependent: Conversion [conversion]
Paid Media: Call, RESPONSIVE_SEARCH, VIDEO_TRUEVIEW_IN_STREAM, FB
Paid Media Spend: Call, RESPONSIVE_SEARCH, VIDEO_TRUEVIEW_IN_STREAM, FB
Context:
Organic:
Prophet (Auto-generated): trend, season, holiday on US
Unused variables: None
Date Range: 2023-09-18:2024-12-09
Model Window: 2023-09-18:2024-12-09 (65 weeks)
With Calibration: FALSE
Custom parameters: None
Adstock: geometric
Hyper-parameters: Not set yet
Default media variable for modelling has changed from paid_media_vars to paid_media_spends.
Also, calibration_input are required to be spend names.
hyperparameter names are based on paid_media_spends names too. See right hyperparameter names:
hyper_names(adstock = InputCollect$adstock, all_media = InputCollect$all_media)
[1] "Call_alphas" "Call_gammas" "Call_thetas"
[4] "FB_alphas" "FB_gammas" "FB_thetas"
[7] "RESPONSIVE_SEARCH_alphas" "RESPONSIVE_SEARCH_gammas" "RESPONSIVE_SEARCH_thetas"
[10] "VIDEO_TRUEVIEW_IN_STREAM_alphas" "VIDEO_TRUEVIEW_IN_STREAM_gammas" "VIDEO_TRUEVIEW_IN_STREAM_thetas"
1. IMPORTANT: set plot = TRUE to create example plots for adstock & saturation
hyperparameters and their influence in curve transformation.
plot_adstock(plot = FALSE)
plot_saturation(plot = FALSE)
4. Set individual hyperparameter bounds. They either contain two values e.g. c(0, 0.5),
or only one value, in which case you'd "fix" that hyperparameter.
Run hyper_limits() to check maximum upper and lower bounds by range
hyper_limits()
thetas alphas gammas shapes scales
1 >=0 >0 >0 >=0 >=0
2 <1 <10 <=1 <20 <=1
Example hyperparameters ranges for Geometric adstock
hyperparameters <- list(
FB_alphas = c(0.5, 3),
FB_gammas = c(0.3, 1),
FB_thetas = c(0, 0.3),
Call_alphas = c(0.5, 3),
Call_gammas = c(0.3, 1),
Call_thetas = c(0, 0.3),
RESPONSIVE_SEARCH_alphas = c(0.5, 3),
RESPONSIVE_SEARCH_gammas = c(0.3, 1),
RESPONSIVE_SEARCH_thetas = c(0, 0.3),
VIDEO_TRUEVIEW_IN_STREAM_alphas = c(0.5, 3),
VIDEO_TRUEVIEW_IN_STREAM_gammas = c(0.3, 1),
VIDEO_TRUEVIEW_IN_STREAM_thetas = c(0, 0.3)
)
InputCollect <- robyn_inputs(InputCollect = InputCollect, hyperparameters = hyperparameters)
Running feature engineering...
Warning message:
In check_hyperparameters(InputCollect$hyperparameters, InputCollect$adstock, :
Automatically added missing hyperparameter range: 'train_size' = c(0.5, 0.8)
print(InputCollect)
Total Observations: 65 (weeks)
Input Table Columns (6):
Date: DATE
Dependent: Conversion [conversion]
Paid Media: Call, RESPONSIVE_SEARCH, VIDEO_TRUEVIEW_IN_STREAM, FB
Paid Media Spend: Call, RESPONSIVE_SEARCH, VIDEO_TRUEVIEW_IN_STREAM, FB
Context:
Organic:
Prophet (Auto-generated): trend, season, holiday on US
Unused variables: None
Date Range: 2023-09-18:2024-12-09
Model Window: 2023-09-18:2024-12-09 (65 weeks)
With Calibration: FALSE
Custom parameters: None
Adstock: geometric
Hyper-parameters ranges:
FB_alphas: [0.5, 3]
FB_gammas: [0.3, 1]
FB_thetas: [0, 0.3]
Call_alphas: [0.5, 3]
Call_gammas: [0.3, 1]
Call_thetas: [0, 0.3]
RESPONSIVE_SEARCH_alphas: [0.5, 3]
RESPONSIVE_SEARCH_gammas: [0.3, 1]
RESPONSIVE_SEARCH_thetas: [0, 0.3]
VIDEO_TRUEVIEW_IN_STREAM_alphas: [0.5, 3]
VIDEO_TRUEVIEW_IN_STREAM_gammas: [0.3, 1]
VIDEO_TRUEVIEW_IN_STREAM_thetas: [0, 0.3]
train_size: [0.5, 0.8]
Check spend exposure fit if available
if (length(InputCollect$exposure_vars) > 0) {
lapply(InputCollect$modNLS$plots, plot)
}
Run all trials and iterations. Use ?robyn_run to check parameter definition
OutputModels <- robyn_run(
InputCollect = InputCollect, # feed in all model specification
cores = NULL, # NULL defaults to (max available - 1)
iterations = 5000, # 2000 recommended for the dummy dataset with no calibration
trials = 5, # 5 recommended for the dummy dataset
ts_validation = TRUE, # 3-way-split time series for NRMSE validation.
add_penalty_factor = FALSE # Experimental feature. Use with caution.
)
Input data has 65 weeks in total: 2023-09-18 to 2024-12-09
Initial model is built on rolling window of 65 week: 2023-09-18 to 2024-12-09
Time-series validation with train_size range of 50%-80% of the data...
Using geometric adstocking with 14 hyperparameters (14 to iterate + 0 fixed) on 15 cores
Starting 5 trials with 5000 iterations each using TwoPointsDE nevergrad algorithm...
Running trial 1 of 5
| | 0%Timing stopped at: 0.88 0.05 0.94
Error in { : task 1 failed - "Can't select columns that don't exist.
✖ Column mean_exposure doesn't exist."
The codes were running fine for me before but started giving me problem today. Please help me with this issue @gufengzhou
I found the error! you need to have an organic variable column as well in the input column now for the model to run. This was not the case before, kindly look into it.
Thanks! Will look into it. @laresbernardo would you have time for this one?
@mahaja1 I can't reproduce your error. I can run the demo without organic using the latest version.
I am still getting it. What options do i have? When i ran the model using traffic column, it is assigning large contribution value to traffic. I want to run it without any organic variable.
I really need help around this. Please look into this.
which version are you using? you can do so by running packageVersion("Robyn"). Your copy paste message above is quite messy. I might need your dataset as well as your robyn_inputs() configs to debug
I wasn't able to reproduce the error either. Potentially changing a hard select(...)' to select(any_of(...))could fix it if that's the case @gufengzhou. There are only 4mean_exposure`'s in the code.
|
gharchive/issue
| 2024-12-19T21:44:32 |
2025-04-01T04:34:13.711799
|
{
"authors": [
"gufengzhou",
"laresbernardo",
"mahaja1"
],
"repo": "facebookexperimental/Robyn",
"url": "https://github.com/facebookexperimental/Robyn/issues/1191",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
}
|
2382100093
|
Supprt Option and Option
The main issue with supporting these structs is that they are both 3 pointers wide, while the existing code relied on Option being precisely 1 pointer wide (and thus only worked for pointer types). To resolve this, this PR has 2 commits:
Instead of using a single RustOption type to represent the C++ binding, using traits I defined different structs for the FFI representation of Option depending on T. For the old pointer types like &T and Box this is the old RustOption, but this now allows me to define new types (with a different size) to use for Option and Option
Actually implement Option and Option using the indirection above
Does is_direct correspond with needs_indirect_abi? Or are they unrelated? I was a bit confused by the naming there.
Hrmm is_direct was referring to the fact that set took in T instead of T* but now I'm not sure why I did that. It seems like I don't need to make that distinction, but now I'm not entirely sure how the code was working...
How about Option<&str>. Is that supported here? I see impl for Option<&String> but not str.
Option<&str> is not yet implemented because it is a fat pointer. Planning on doing it in a future diff though
|
gharchive/pull-request
| 2024-06-30T05:57:45 |
2025-04-01T04:34:13.716357
|
{
"authors": [
"kuecks"
],
"repo": "facebookexperimental/cxx",
"url": "https://github.com/facebookexperimental/cxx/pull/14",
"license": "Apache-2.0",
"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.