text:
Compile fails

Describe the bug
I have installed go and nodejs:
go version
go version go1.20.4 linux/amd64
dpkg -l |grep node
ii  nodejs                                20.2.0-deb-1nodesource1        amd64        Node.js event-based server-side javascript engine

I try to make the UI:
For a brief moment an X11 window pops up and closes again. Then the install fails.
Steps to reproduce
make ui
npm run build

> build
> vite build

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
(./src/core/Core.cpp l.710): Opening the file: build
Cannot open file build
Aborted
make: *** [Makefile:44: ui] Fehler 134

I have used both the current master and https://github.com/evcc-io/evcc/archive/refs/tags/0.117.4.zip.
Configuration details
Not applicable, as it fails during compile

Log details
not applicable

What type of operating system are you running?
Linux
Version
not running yet

Hello!
I think that you need to run
npm install

to install all the dependencies first.
Regards
Jens

authors: henfri jheinitz


text:
Homematic: add power reading

/cc @thierolm das schien noch zu fehlen?

Hm, das hat im charger bisher auch ohne die explizite CurrentPower function funktioniert.
Beim Shelly, Tasmota, FritzDect also allen switchsocket Chargern funktioniert es bisher auch ohne die explizite Function.

Replaced by https://github.com/evcc-io/evcc/pull/6576

source: gharchive/pull-request

authors: andig thierolm

repo: evcc-io/evcc

license: MIT

license_type: permissive

license_source: github-api


text:
Update Fail example for anchor-has-content rule

closing </a> tag is missing

Coverage remained the same at 99.467% when pulling c74db1ff9814c116880056f5771005619f9796c4 on liubko:patch-1 into 750b8943b01e5ff1fa35504b241082f6d447bd78 on evcohen:master.

I'm glad to contribute 😃

authors: coveralls liubko

license: mit

license_source: bigquery


text:
[Feature Request] Scanning Reports

I would like a page where I can view scanning data with the following toggleable filters:

Limit to map or maps
Limit to date range
Limit to user or group
Added POS
Removed POS
Added system
Removed system
Imported signatures
Updated signatures
Scanned signatures
Any other data the mapper can provide

I would also like this report to sum up the number of actions the selected filters so I know who to pay out every week.

When I finally get my silly shattered statics done I'll take this on as a long-term learning project.
Seems like it would have to be a whole new app in django, which would be very educational to build from the ground up.

I have a small/simple GUI-less tool for this which does pretty much all you want, minus the limits to map, user/group and POS: https://github.com/Unsettled/Mapper-Tally

I'll use that as a guide but I'm pretty bad at reading PHP.

It's just the SQL query you need probably. For a lot of log entries advanced logging needs to be enabled (not sure what default is)
On Wed, Jan 27, 2016 at 8:21 PM, AceMgy notifications@github.com wrote:

I'll use that as a guide but I'm pretty bad at reading PHP.
Reply to this email directly or view it on GitHub:
https://github.com/evewspace/eve-wspace/issues/230#issuecomment-175808408

source: gharchive/issue

authors: AceMgy Zumochi andrewd18

repo: evewspace/eve-wspace


text:
Start with rounded tips

hello, there is the possibility of adding a parameter to round the tips of the stars?

Hi, thanks for the proposal. It is of course possible (everything is) to add ability to draw stars with rounded tips. This will require a change in the way the stars are drawn. Let me explain how the stars are drawn right now and what needs to be done to introduce rounded corners.
Right now the star is drawn as a shape by connecting ten point with straight lines. The points for the star can be changed by setting the cosmosView.settings.starPoints property. Currently the shape of a star is defined as an array of points drawn in a box with size 100 by 100 units:
  cosmosView.settings.starPoints = [
    CGPoint(x: 49.5,  y: 0.0),
    CGPoint(x: 60.5,  y: 35.0),
    CGPoint(x: 99.0, y: 35.0),
    CGPoint(x: 67.5,  y: 58.0),
    CGPoint(x: 78.5,  y: 92.0),
    CGPoint(x: 49.5,  y: 71.0),
    CGPoint(x: 20.5,  y: 92.0),
    CGPoint(x: 31.5,  y: 58.0),
    CGPoint(x: 0.0,   y: 35.0),
    CGPoint(x: 38.5,  y: 35.0)
  ]

One can change the coordinates of the points or the number of them. Unfortunately, the library will still connect the points with straight lines so it will be hard to achieve a perfectly rounded corner. To make the library draw rounded tips one needs to do the following.

Firstly, one needs to modify the function that draws the star to make it draw curves in addition to lines. The function that does that is called createStarPath and located in StarLayer.swift file. One can modify it to do path.addCurveToPoint or path.addQuadCurveToPoint in addition to path.addLineToPoint.

Secondly, one needs to change the way the points for the star are defined. As I demonstrated above, right now a star is defined by an array of points. This data structure needs to be extended to specify the control points for the curves.

After the change is made, one needs to test the drawing performance to make sure that introduction of curves does not significantly impact the drawing time.

In general, I think the work is doable and it can be fun. If anyone wants to implement it feel free to declare it here.

Ok ty man.

One can now provide a custom image for a star, so it is possible to use rounded tips, or any other shapes. Instructions and links to images are in the readme.

authors: evgenyneu xXUlquiXx

repo: evgenyneu/Cosmos


text:
Result Documentation

This is to add the documentation for Result per https://github.com/evilsoft/crocks/issues/42
Not ready for review, but happy for input

Coverage remained the same at 100.0% when pulling 145333aac71b204a01a26bd837cf83ac32a28c63 on docs/Result into 3c25e5a098ab1c2e5e2e3d066d8740d32baec626 on master.

Hey @evilsoft or @HenriqueLimas I'd love an initial set of 👀 on this. I think everything is ready for review except the tryCatch example which i'll get onto tomorrow, assuming I don't REALLY enjoy new years 😄

Think this will do it. Amazing work on this @dalefrancis88!
Thank you so much for your time and dedication getting this through.

No problem, thanks for your limitless patience :)

authors: coveralls dalefrancis88 evilsoft

repo: evilsoft/crocks

license: ISC


text:
🛑 BMS ID is down

In 70ae294, BMS ID (https://id.bookmyshow.com/) was down:

HTTP code: 403
Response time: 121 ms

Resolved: BMS ID is back up in b917c4e after 7 hours, 4 minutes.

repo: evintoh/upptime


text:
:sparkles: Feat: Add blob fields to receipts

Description
Concise description of proposed changes
Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1032
#1031  👈
#1030
#1029
#1028
#1027
#1026
#1025
#1024
#1023
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @roninjin10 and the rest of your teammates on  Graphite

repo: evmts/tevm-monorepo


text:
Remove visual errors for Example

Replaced single quotes with double quotes.

eh... any benefits?

While seeing react-native-fcm/Examples/simple-fcm-client/app/App.js on browser it has some red marks because of single quotes. Just I would like to remove that to give better readability on browser. NO OTHER BENEFITS.

what browser are you using? My chrome works just fine. I use single quotes everywhere and never got the issue

Even I'm using Chrome.

I mean this one as "visual error". If it is misleading title & unwanted PR please ignore.

i see. How about just change line 158?

I thought it would be better to remove all single quotes. Some styles also has single quotes. It may give that red mark. I'm not sure about that.

try it and see.
It is just chrome change parse jsx. single quotes in standard js should be fine

I think this PR is useless. Closing it.

authors: Ajith-Pandian evollu

repo: evollu/react-native-fcm


text:
Update scalatest to 3.1.0

Updates org.scalatest:scalatest from 3.0.8 to 3.1.0.
Release Notes/Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalatest", artifactId = "scalatest" } ]

Applied Migrations

https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.0.x/rules/src/main/scala/org/scalatest/autofix/v3_0_x/RenameDeprecatedPackage.scala
https://raw.githubusercontent.com/scalatest/autofix/e4de53fa40fac423bd64d165ff36bde38ce52388/3.1.x/rules/src/main/scala/org/scalatest/autofix/v3_1_x/RewriteDeprecatedNames.scala

labels: semver-minor, scalafix-migrations

Pull Request Test Coverage Report for Build 23

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.643%

Totals

Change from base Build 22:
0.0%

Covered Lines:
53

Relevant Lines:
56

💛  - Coveralls

Pull Request Test Coverage Report for Build 23

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 94.643%

Totals

Change from base Build 22:
0.0%

Covered Lines:
53

Relevant Lines:
56

💛  - Coveralls

authors: coveralls scala-steward

repo: evolution-gaming/cassandra-launcher


text:
docs: Demo content rework

demo page content restructured and updated
page folders cleanup
11ty collection tags updates
small design updates
add utils basic documentation

:tada: This PR is included in version 3.0.0-beta.20 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: exadel-inc/esl


text:
Documentation: Adapter API - document the interface type of the api

https://github.com/exasol/virtual-schemas/blob/master/doc/development/api/virtual_schema_api.md
I miss the information which interface is documenteted here? Is it an http interface? Who are the two parties using this protocol?

An additional point for API enhancement: links from the createVirtualSchema and refresh request to the explanation of schemaMetaData[Info]

Here an idea for the pushdown sequence diagram:

authors: AnastasiiaSergienko jakobbraun

repo: exasol/virtual-schemas


text:
【Ansible-Driver】機器一覧のPioneer利用情報が、Legacy/LegacyRoleのファイルに反映される問題

基本コンソール＞機器一覧　のPionner利用情報の「プロトコル」の情報が、
Ansible-Legacy、Ansible-LegacyRoleを実行時に作成されるhost_vars配下のファイルに、
不要に記載されてしまう。
Movement実行に影響はない。
[「telnet」入力の場合]
loginprotocol: telnet
[空白の場合]
loginprotocol: undefinesymbol

Legacy/Roleは、機器一覧の「プロトコル」が未登録の場合、ホスト変数に__loginprotocol__を記載しないようにします。

Legacy/Roleは、機器一覧の「プロトコル」が未登録の場合、ホスト変数に__loginprotocol__を記載しないようにします。

完了

authors: enoman sinatommy

repo: exastro-suite/it-automation


text:
Extreme sluggishness when drawing slowly in collaboration mode

I think https://github.com/excalidraw/excalidraw/discussions/3150 may be describing a similar issue.
To minimize potential latency differences, I tested it by opening two Chrome browser windows on the same computer and putting them in the same excalidraw.com live collaboration session. (Tested with both Chrome and Chrome Canary.)
Using the Draw tool, if I move my cursor quickly, there isn't much perceived latency or slowness in the other browser window. This is the case whether I quickly draw a straight line, or quickly move my mouse in circles to scribble with all sorts of shapes with different kinds of twists and turns. It seems to be about what you'd expect from the network round trip. The faster it is, the less sluggishness is noticed.
However, if I move my cursor more slowly to draw, there's an extreme amount of awkward sluggishness and latency in the other window. It's proportionally much more than I'd expect when just accounting for the fact that the drawing is happening more slowly due to moving my mouse more slowly.
Once it fully catches up to the very last bit of slow movement, if I move my cursor more quickly again, the sluggishness issue instantly goes away and everything seems smooth again.
To be clear, I understand that things will obviously appear more slowly if I draw more slowly. The degree of sluggishness just seems to be much more than should be occurring when accounting for that fact.
I don't know anything about the codebase, but just to describe how I perceive the behavior, to me it almost seems like it might be undershooting what the actual average drawing velocity should be, with it undershooting more severely the slower the drawing is.

The trouble is we're getting too much traffic and will need to either buy more CPUs or more machines, but both will require also setting up a Redis proxy to allow for socketIO to work with multiple nodes.
We should get around to it soon(ish).
It can of course also be a case of the client not being able to handle all the incoming messages, which could be alleviated by support backpressure. But the fact you're not experiencing a severe lag with mouse events doesn't necessarily indicate a backpressure issue (mouse events are cheaper).

authors: Tozuko dwelle

repo: excalidraw/excalidraw


text:
Excalidraw export image to clipboard is broken on MacOS Safari

Problem occurs on Safari 15.2 (17612.3.6.1.6) on MacOS 12.1 (Apple M1).
Digging into the exception with the debugger, we see that we get a NotAllowedError. Reading a bit around the internet it seems that Safari has a different implementation of how it detects user events to allow writing to the clipboard? Is it possible to fix this?

@orlp oops, I've had a WIP fix for this and then completely forgot about this. Will need a rewrite at this point, but last I checked it's def solvable. Safari just doesn't like setting the clipboard in the async way we're currently doing it.
I'll try to look at this over the weekend.

Sorry for the delay. You can test the fix here: https://excalidraw-eb319ldm3-excalidraw.vercel.app — we'll deploy tomorrow!

@dwelle Thanks!

authors: dwelle orlp


text:
Suggestion: snap to nearby shapes when dragging / resizing

It would be really useful if I could easily align shapes by dragging them around. If I want some shapes to be left / right / top / bottom aligned I can select them and then align. This works, albeit less convenient than just dragging them and have them snap to an automatically detected guide, as in this video:
https://github.com/excalidraw/excalidraw/assets/776358/14cc448f-a09f-4563-acfb-920072c20aee
However, when trying to resize shapes to be the same width / height, there's currently no way to do that. See this video to get a sense of what I mean:
https://github.com/excalidraw/excalidraw/assets/776358/1b8248d1-3b50-4cd1-935a-d7190233c7ac
This is pretty standard in many visual editing tools (these videos are from Google Slides) but if it's too hard to implement or undesired for some other reason, I would really appreciate if there was some other way to make existing shapes the same height / width as other shapes and/or align one side of them by resizing rather than moving the whole shape.

BTW, when snapping is undesired, a modifier key can disable this behavior. In the case of Google Slides, holding down command prevents snapping.


text:
Mouse tracking with two touches is flickering

On mobile, if you have two fingers to zoom/pan, it sends both updates one by one, so you see the cursor flickering on the other side.

We should probably just not show the cursor when there are more than two pointers down at once.


text:
convert to web service

A web service would make managing movies/series a lot easier for a lot of people, it would also make managing the config file more error-proof given that it would be managed by the webserver and we could implement new functionalities, like filtering lists before they reach Radarr/Sonarr.
I also want to keep it runnable just by using a config file like it is now to maintain as much backwards compatibility as we can without limiting the progress of the project.
please share any thoughts

Just to make sure I'm following, are you referring to adding an http API and a web app?

I kinda wish there were plugins into sonarr and radarr we could build this functionality into, so it lives inside those apps, respectively.

I started converting the project to django, my idea is pretty similar to what the original author was trying to achieve with his v2.
The path I had in mind is:

convert it to Django with a basic ui to view/change settings in the config file and see logs
Add the ability to handle multiple sonarr/radarr instances
Make a good UI (someone will have to step in, I'm not a FE dev and can't make good UIs lol)
Add the ability to add a list to excludarr that will filter out unwanted entries and serve the list to radarr/sonarr like it was the original list (this will need various integrations to support all/some of the services supported by sonarr/radarr

All this should also be while maintaining retro compatibility as much as we can with the current config file we have (maybe by adding a --legacy flag).
There are some interesting suggestions in the issues of the original project (like the filtering before serving part) that I'd like to work on, I just need some time as I've been pretty busy the last couple of weeks. I'll make issues for each enhancement so we will be able to discuss each one when we'll reach that point.

I kinda wish there were plugins into sonarr and radarr we could build this functionality into, so it lives inside those apps, respectively.

Yea totally, this stuff would be so much easier to do that way

Could add a version: 2 for new yaml schema so code can differentiate from original schema, and if we ever need a v3 we already have a pattern to support that :)

Could add a version: 2 for new yaml schema so code can differentiate from original schema, and if we ever need a v3 we already have a pattern to support that :)

Yea, I like that solution

repo: excludarr/excludarr


text:
Update status of Concept Exercises

This issue is part of the migration to v3. You can read full details about the various changes here.
Concept Exercises can have a status specified in their "status" field in their config.json entry, as specified in the spec. This status can be one of four values:

"wip": A work-in-progress exercise not ready for public consumption. Exercises with this tag will not be shown to students on the UI or be used for unlocking logic. They may appear for maintainers.
"beta": This signifies active exercises that are new and which we would like feedback on. We show a beta label on the site for these exercise, with a Call To Action of "Please give us feedback."
"active": The normal state of active exercises
"deprecated": Exercises that are no longer shown to students who have not started them (not usable at this stage).

The "status" key can also be omitted, which is the equivalent of setting it to "active".
Goal
The "status" field of Concept Exercises in the config.json file should be updated to reflect the status of the Concept Exercises. See the spec for more information.
If your track doesn't have any Concept Exercises, this issue can be closed.
Example: removed wip status
{
  "exercises": {
    "concept": [
      {
        "uuid": "93fbc7cf-3a7e-4450-ad22-e30129c36bb9",
        "slug": "cars-assemble",
        "name": "Cars, Assemble!",
        "concepts": ["if-statements", "numbers"],
        "prerequisites": ["basics"]
      },
      ...
    ]
  }
}

Example: replaced wip status with active
{
  "exercises": {
    "concept": [
      {
        "uuid": "93fbc7cf-3a7e-4450-ad22-e30129c36bb9",
        "slug": "cars-assemble",
        "name": "Cars, Assemble!",
        "concepts": ["if-statements", "numbers"],
        "prerequisites": ["basics"],
        "status": "active"
      },
      ...
    ]
  }
}

Tracking
https://github.com/exercism/v3-launch/issues/14

Closing this as this track has no (active) Concept Exercises

repo: exercism/erlang


text:
The Farm: Improve introduction

Follow up from #2009
The tests for "The Farm" currently don't cover what should happen when a negative fodder amount and a non-scale error is returned. Go's general guideline is to not use the result if there was an error so passing on the error takes precedence over handling the negative amount.
Tasks

[x] Add a test case for a negative fodder amount and a non-scale error. The expected outcome of DevideFood is 0 and the error that was returned from FodderAmount.
[ ] Make sure the errors concept and the exercise introduction mention the guideline for usually not using the result in case there was error.

A quote from @andrerfcsantos on Slack regarding the topic of the open task here:

In Go, when you return a non-nil error in a function that also returns other things, the caller of the function is supposed to ignore all the other things except the error. This is unless the documentation of the function says otherwise, but I never really saw a function return an error but make you pay attention to the other values.
This means that n theory, when you return an error, you can return anything in the other values - those other values aren't supposed to be looked at anyway because you are returning an non-nil error. But returning the zero value makes the code easier to read, as you are signaling there's nothing special going on there.

To be quite honest, I think this might be a problem with the errors introduction, that it does not support or show learners the "Handle specific errors, but defer others" explicitly.
    if err != nil && err != ErrScaleMalfunction {
    	return 0.0, err
    }

I Was most frustrated as I did not see language I recognised as saying "Hey, we want to handle this error, but early exit all others."
I'd in-fact read the exercise as "We will only expect this error".
How to communicate this...

Defining behavior for specific error types
While we can and should, early return most errors that occur. We may in some special cases, wish to define behavior upon a specific type of error, that we know we can handle. When that happens, we still return all other errors early (code example from above). But we might choose to return a value without error for a specific error.

@Lewiscowles1986 You raise a good point there. However, I think what you are bringing up is unrelated to the open task in this issue. It would be great, if you could open a new issue instead and copy your comment in there. Then we can discuss a bit more in that new issue.

This issue and #2080 lead me to the question whether it is such a good idea to have the unusual pattern of "continue working with the result even though there was an error" as part of the concept exercise. As this is very rare, it might not be a good fit for the concept exercise that first introduces the student to the errors concept. It might even set a bad example. @andrerfcsantos How do you feel about this? Do you think we should change the exercise? That might avoid some bending the introduction around it.

@junedev I agree we should change the exercise to not use the normal result of the function even though there was a non-nil error. Not only is a bit unrealistic like you said, but it might also unnecessarily make the exercise more complex.
I think the idea is to show how to check for specific errors, but that's probably best done in the Error Wrapping concept.

So, While I think this should leave this exercise, I also think it could be a separate exercise to wrapping, which to my mind serves a different purpose and is not encapsulation.
Encapsulating an error and providing domain-specific knowledge / behavior is it's own standalone take on errors to wrapping. It is not a general concept, that people have a nephew who can't be fixed / changed cheaper than code. This is almost directly the opposite thing to wrapping the error, where for some reason that error detail would leak out to the world. You are not embedding past errors when encapsulating; you are exchanging an error for either another error, or providing a behavior for an error, that does not return an error.
The original github.com/pkg/errors basically attempts to implement manual stack unwrapping ALA exceptions by-proxy. Like an Exception, it captures a stack trace for all errors; and provides a Cause, which seems similar to sub-type sniffing, common among exceptions. I Know it comes from Dave Cheney, but I Really dislike the pattern and am glad that the golang core implementation strips back this. It's smearing leaky details all over the place, rather than encapsulate them. It's not encapsulation if you pass every last error in a chain down to a consumer that then has to deal with a lot more details.

I'm happy to help on this task

@mantrobuslawal If you want to make some small change related to the original open issue at the top, feel free to go ahead and create a PR. However, I would advise against bigger rework as we are planning to structurally change this exercise in the future (move interfaces into its own exercise and instead teach errors and error wrapping in one exercise).

Here the issue for the rework I mentioned above: https://github.com/exercism/go/issues/2492
I am closing this issue in favor of the more general one. As said above, PRs are ok but I don't want to encourage too much "patching it up" work on this exercise.

authors: Lewiscowles1986 andrerfcsantos junedev mantrobuslawal

repo: exercism/go


text:
Implement new Concept Exercise: net/http

Getting Started
If you have not yet contributed to concept exercises before, this task requires some upfront reading to acquire the necessary background knowledge.
Here you can read about what Concept Exercises are and how they are structured:

What are Concept Exercises?
Concept Exercises
Concepts

If you have not done so yet, it is probably also helpful to do a couple of "Learning Exercises" (this is how they are called on the site) yourself. You can also look at the code of an existing concept exercise like welcome-to-tech-palace for reference.
Also be aware of these general guidelines.

Exercism Markdown Specification
Exercism Formatting and Style Guide

Goal
The goal here is to create a new concept exercise to teach how to use Go's built-in http server.
The concept and exercise need to be written from scratch.
Concepts
The following concept needs to be created. You can use the introduction.md file of the concept also as introduction.md file of the exercise. No need to create different content at this point. Additionally, if you want to save some time it is ok to not have an extensive about.md for now. It can also be mainly the introduction.md content, maybe with some additions you would like to make.

http

Learning Objectives
In the concepts the student should learn about the following topics and then practice them in the concept exercise.

... [tbd]

Out of Scope

... [tbd]

Prerequisites

... [tbd]

Other prerequisites should be added as needed to solve the specific exercise.
Story Idea
It's a good idea for concept exercises to have a story that gives some flair and context to the tasks.
Create a new story for this exercise. The story doesn't need to be highly complex, even a small story goes a long way to make the tasks more interesting. For some inspiration for the story, check the other exercises on the track or the page Exercism docs: Stories for an overview of stories used across tracks.

This issue is claimed by @MikaeelMF.

@MikaeelMF Just bouncing some ideas about this. There was discussion about if it would be possible to have a client program communicate with a server program on localhost (eventually server and client can be the same program). Asking around, it seems that this is possible.
Our containers run with networking disabled --network none and I did a little test to see if this could influence the capacity of a client and server to communicate on localhost and this seems to not be the case - a client and a server can still communicate on localhost even with --network none.
For reference, this is what I used to test this: simple-client-server.zip

Thanks @andrerfcsantos for checking this out! My initial ideas are exactly revolving around testing solutions using a client/server structure as well.

@MikaeelMF Just bouncing some ideas about this. There was discussion about if it would be possible to have a client program communicate with a server program on localhost (eventually server and client can be the same program). Asking around, it seems that this is possible.
Our containers run with networking disabled --network none and I did a little test to see if this could influence the capacity of a client and server to communicate on localhost and this seems to not be the case - a client and a server can still communicate on localhost even with --network none.
For reference, this is what I used to test this: simple-client-server.zip
I thought of this idea of a client and a server because I'm imagining that if the exercise wants to teach about sending requests, our tests might want to start a server to validate the request the student does. The same if we want to teach about servers, probably the tests might act as a client to validate the server.
With this I don't want necessarily to force the exercise into a particular direction - just exploring some options :)

Thanks @andrerfcsantos for checking this out! My initial ideas are exactly revolving around testing solutions using a client/server structure as well.

Getting Started
If you have not yet contributed to concept exercises before, this task requires some upfront reading to acquire the necessary background knowledge.
Here you can read about what Concept Exercises are and how they are structured:

What are Concept Exercises?
Concept Exercises
Concepts

If you have not done so yet, it is probably also helpful to do a couple of "Learning Exercises" (this is how they are called on the site) yourself. You can also look at the code of an existing concept exercise like welcome-to-tech-palace for reference.
Also be aware of these general guidelines.

Exercism Markdown Specification
Exercism Formatting and Style Guide

Goal
The goal here is to create a new concept exercise to teach how to use Go's built-in http server. The concept and exercise need to be written from scratch.
Concepts
The following concept needs to be created. You can use the introduction.md file of the concept also as introduction.md file of the exercise. No need to create different content at this point. Additionally, if you want to save some time it is ok to not have an extensive about.md for now. It can also be mainly the introduction.md content, maybe with some additions you would like to make.

http

Learning Objectives
In the concepts the student should learn about the following topics and then practice them in the concept exercise.

... [tbd]

Out of Scope

... [tbd]

Prerequisites

... [tbd]

Other prerequisites should be added as needed to solve the specific exercise.
Story Idea
It's a good idea for concept exercises to have a story that gives some flair and context to the tasks. Create a new story for this exercise. The story doesn't need to be highly complex, even a small story goes a long way to make the tasks more interesting. For some inspiration for the story, check the other exercises on the track or the page Exercism docs: Stories for an overview of stories used across tracks.

Great! Thank you for the instructions.

Learning Objectives:
The general objective is to get someone who knows nothing about network programming to start to get curious and get introduced to resources to follow up on given subjects if they wish to learn more. Therefore I have tried to give a short introduction on the following topics:

what is HTTP?
What makes a client request in HTTP?
What makes a server response in HTTP?
How to use the go net/http package to write a basic HTTP client?
How to use the go net/http package to write a basic HTTP server?

Out of Scope:
Since this is an introduction, I will not go into any detail about the http headers. Also, it does not seem beneficiary to explain all request methods.
Also on the implementation side, I don't think it is a good idea to explain the defer, io.Reader, and io.Writer in this exercise. Since these concepts are used in the network programming using net/http quite a lot, it would have been great if we currently had these concepts taught in the roadmap. Labeling these concepts as a prerequisite seems a bit overboard but not talking about them anywhere in the roadmap might make things a little bit difficult to fully understand this exercise. I would really appreciate it if you could let me know what you think is the best path to take here.
I think a basic version of the concept introduction will be available in the coming days, when it is representable, I will create a PR and set it as a draft, so anyone who wishes to participate or take a look at it and suggest new ideas would do so easily.
Please do not hold back any suggestions that you may have, I would truly appreciate it if you share with me any ideas or thoughts that you have.

@MikaeelMF Please keep in mind that Exercism concepts/concept exercises are always about "How to do X in language Y? (for someone that already knows X)". They are not about "What is X?". In this case that means 1-3 would not be part of the concept, the concept would only be about 4+5 (How to make an http request in Go? How to set up an http server in Go?). For 1-3 you can say some brief introductory words and include links for people that are not yet familiar with the topic in general. In the future, we will have out own Exercism wide content for explaining these general programming concepts but it will take a while until we get there.
As part of 5, I would recommend to explain how Go uses Go routines so that the code in an http handler can be written in a synchronous fashion without blocking any other requests from being processed.
Since the scope of the learning objectives is now reduced, maybe you have space to include setting headers. Might be a good idea.
Regarding io.Reader/io.Writer: Handwaving over something a little bit to keep the scope of the concept/exercise managable is totally fine. Also that some some prerequisite concept is not available yet happens quite often. You can still go ahead with your concept though. What we do in the JavaScript track in these cases is that we include links where people can read up on those things. Then later when the concept exists within the Syllabus, we replace the links to external resources with links to the Exercism concept.

@MikaeelMF Please keep in mind that Exercism concepts/concept exercises are always about "How to do X in language Y? (for someone that already knows X)". They are not about "What is X?". In this case that means 1-3 would not be part of the concept, the concept would only be about 4+5 (How to make an http request in Go? How to set up an http server in Go?). For 1-3 you can say some brief introductory words and include links for people that are not yet familiar with the topic in general. In the future, we will have out own Exercism wide content for explaining these general programming concepts but it will take a while until we get there.
As part of 5, I would recommend to explain how Go uses Go routines so that the code in an http handler can be written in a synchronous fashion without blocking any other requests from being processed.
Since the scope of the learning objectives is now reduced, maybe you have space to include setting headers. Might be a good idea.
Regarding io.Reader/io.Writer: Handwaving over something a little bit to keep the scope of the concept/exercise managable is totally fine. Also that some some prerequisite concept is not available yet happens quite often. You can still go ahead with your concept though. What we do in the JavaScript track in these cases is that we include links where people can read up on those things. Then later when the concept exists within the Syllabus, we replace the links to external resources with links to the Exercism concept.

Ah I see!
Thank you for letting me know!
I will change my outline to better match exercism policies!

I have created a draft PR for this issue. I have written the client section and would really appreciate it if you could look at it and share your thoughts and ideas with me.
P.S. I don't know if it is OK to create a draft PR and check things step-by-step in exercism, so please let me know if it is against here's working manners and I will close the PR right away. I just thought the concept will become more robust and better this way.

@MikaeelMF It would help if in the description of the PR you could add some indication of the status of the PR. With this I mean a brief list of things you consider done (hence we can give feedback on), what is in progress and what is planned. This makes us avoid giving feedback on something that is not finished and avoid suggestions of things you've already planned.

@MikaeelMF It would help if in the description of the PR you could add some indication of the status of the PR. With this I mean a brief list of things you consider done (hence we can give feedback on), what is in progress and what is planned. This makes us avoid giving feedback on something that is not finished and avoid suggestions of things you've already planned.

Oh My bad! I will do so right away!

I have completed my To-Do list for sections that I am going to cover about the server. I initially wanted to cover middlewares as well but figured maybe it becomes too long and also is not really beneficial to the general goals of the concept.
Please let me know if there are any sections that you believe must be discussed and it is missing from my list.

Hi!
Just wanted to let you know that the main text for introduction is completed. I just need to do some formatting and add the appropriate reference for a code snippet that I've used. So I would appreciate it if you would check it out and see if anything comes to your mind that is missing.

I have fixed the formatting based on exercism guidelines and I think the content is ready to get merged.
Only one problem that I have encountered for using configlet to change the main config.json, I couldn't install it using the script in go/bin. I encounter error "curl: (23) Failure writing output to destination".(btw I'm using a macOS 12.4)

authors: MikaeelMF andrerfcsantos junedev


text:
Resistor Color Duo not testing at all

I'm having an issue in the exercise Resistor Color Duo in the JavaScript track. Every time I try the "npm test" , it returns this message:
"internal/modules/cjs/loader.js:1175 throw err; ^
SyntaxError: C:\Users\Fernando\Exercism\javascript\resistor-color-duo\node_modules\ci-info\vendors.json: Unexpected token in JSON at position 0 at parse () at Object.Module._extensions..json (internal/modules/cjs/loader.js:1172:22) at Module.load (internal/modules/cjs/loader.js:986:32) at Function.Module._load (internal/modules/cjs/loader.js:879:14) at Module.require (internal/modules/cjs/loader.js:1026:19) at require (internal/modules/cjs/helpers.js:72:18) at Object. (C:\Users\Fernando\Exercism\javascript\resistor-color-duo\node_modules\ci-info\index.js:3:15) at Module._compile (internal/modules/cjs/loader.js:1138:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1158:10) at Module.load (internal/modules/cjs/loader.js:986:32) npm ERR! Test failed. See above for more details.""
I tried the other exercises and they run ok, just this one that is given me this error. I'm using Visual Studio Code, by the way.

If you delete the node_modules folder and redownload via npm install, does the error persist?

Good afternoon!
Deleting and reinstalling the node_modules  made the exercise works! Thanks for the help!

No problem! Glad it worked!

authors: Fmoraesb neenjaw

repo: exercism/javascript


text:
Clarify instruction for Task 3

Added some more instruction for the task Compose transformation functions.

okay I understand , I will close this pull request

@Tribhuwan-Joshi Thank you for your understanding!

authors: Tribhuwan-Joshi junedev


text:
Clarify twelve days exercise instructions

There was some discussion in Slack about making the instructions more explicit so students build up the solution programatically and do not use the test.txt file as part of the solution.
Update the README to provide clearer instructions on this.

see PR https://github.com/exercism/ruby/pull/957

Should be closed via #957

authors: kenliu kotp

repo: exercism/ruby


text:
Luhn: Update test of non-digit

While implementing these tests for Rust I found that the final test was
not well written (my fault!)
https://github.com/exercism/xrust/pull/247
I added the alphabetical character to an already-invalid string. So the
test doesn't show anything useful.
Instead the test should show that a known-valid string is made invalid
by the inclusion of a non-digit

As mentioned earlier, all of this can be passed with a single equality check. https://github.com/exercism/x-common/pull/474#issuecomment-269943166
But I think the current tests work well to cover the problem.

The difference is that the equality check would never pass code review since it is clearly not even trying to solve the problem, whereas it is the above wrong code looks to at least be making a reasonable attempt.

s/the problem/the general problem, just the specific cases/

Far more dangerous to allow reasonable-looking code that is still wrong, who knows what things could be hidden there... there are entire contests dedicated to underhanded code.
What I have just said is not relevant to this PR.

... unless we think that a student might mistakenly submit code like the above: they think is correct, but it is in fact wrong, but it passes the tests since the tests don't expose its wrongness.

Edited:
The difference is that the equality check would never pass code review since it is clearly not even trying to solve the general problem, just the specific cases. A student submitting the equality check will probably understand that they are submitting code that is just for these specific cases. They will correctly understand that their code won't work for any other cases.
In contrast, the above wrong code looks to at least be making a reasonable attempt. A student submitting that code might very reasonably and incorrectly think that the code works for all cases. They would be wrong, but there is not test case to show them they are wrong.
Far more dangerous to allow reasonable-looking code that is still wrong, who knows what things could be hidden there... there are entire contests dedicated to underhanded code.
What I've said is only relevant to this PR if we believe a student might submit code like the above.

In contrast, the above wrong code looks to at least be making a reasonable attempt. A student submitting that code might very reasonably (but incorrectly) think that the just-submitted code works for all cases.

Oh, erm, would the student actually think that? Surely they would know something is up, given that they see that their own code doesn't handle that a character?!?! So what I said is only a problem if the student doesn't look at the test cases at all.

[acc + (double ? (d * 2 % 9) : d), !double]

wow, bug. that doubles 9 -> 0. it should be 9 -> 9, so I'm just going to do double && d != 9

authors: IanWhitney petertseng

repo: exercism/x-common


text:
kindergarten-garden:  verify ordering of actual/expected

In the Jasmine testing framework, it is convention to:
expect(actual).fn(expected)

But some test suites have the following:
expect(expected).fn(actual)

This causes the error messages to be confusing.
Please verify the kindergarten-garden exercise to make sure that the expectations are ordered correctly. If they are, then this can be closed.
This issue will help to close #111

Got it

This one is OK and can be closed

Excellent!

authors: ireddick rchavarria

repo: exercism/xjavascript


text:
Added track specific documentation

See exercism/x-common#69 and exercism/rossconf#1.

Thanks!

authors: groyoh kytrinyx

repo: exercism/xobjective-c


text:
Override probot/stale defaults, if necessary

Per the discussion in https://github.com/exercism/discussions/issues/128 we
will be installing the probot/stale integration on the Exercism organization on
April 10th, 2017.
By default, probot will comment on issues that are older than 60 days, warning
that they are stale. If there is no movement in 7 days, the bot will close the issue.
By default, anything with the labels security or pinned will not be closed by
probot.
If you wish to override these settings, create a .github/stale.yml file as described
in https://github.com/probot/stale#usage, and make sure that it is merged
before April 10th.
If the defaults are fine for this repository, then there is nothing further to do.
You may close this issue.

I made a mistake.
This was not explicitly documented in the README, but probot/stale requires the presence of a .github/stale.yml file.
If you want the default behavior, you need to add an empty .github/stale.yml file to this repo, otherwise the bot will not be active.

repo: exercism/xpurescript


text:
Updated Documentation Links

Closes #90

Merged. Thanks 🎉

authors: ErikSchierboom hkbertoson


text:
Feature/codecov

This PR adds coverage output in the terminal for our test pipeline. Next step would be to host it at codecov.io and display it in the PR.

Have a look here to see the new output https://github.com/experimental-design/bofire/actions/runs/4143187958/jobs/7164742831

repo: experimental-design/bofire


text:
wip fix terminal renderer

Need help on this one. github terminalrenderer deprecated

@duluca abandoning this per new direction of design.

repo: expertly-simple/angular-evergreen


text:
Issue with import LangchainLLM in Databricks

While running on Databricks, the following error is encountered when running from ragas.llms import LangchainLLM
ImportError: cannot import name 'AzureOpenAIEmbeddings' from 'langchain.embeddings' (/databricks/python/lib/python3.10/site-packages/langchain/embeddings/init.py)
It works perfectly well on my PC.
Ragas version: 0.0.22
Python version: 3.10.12
Langchain ver:  0.0.217
Code to Reproduce
from ragas.llms import LangchainLLM
Error trace
----> 4 from ragas.llms import LangchainLLM
5 from ragas.testset import TestsetGenerator
6 from langchain.chat_models.azure_openai import AzureChatOpenAI
File /local_disk0/.ephemeral_nfs/envs/pythonEnv-e45e8563-0586-47e9-a096-aedc15631cbc/lib/python3.10/site-packages/ragas/init.py:1
----> 1 from ragas.evaluation import evaluate
3 try:
4     from ._version import version as version
File /local_disk0/.ephemeral_nfs/envs/pythonEnv-e45e8563-0586-47e9-a096-aedc15631cbc/lib/python3.10/site-packages/ragas/evaluation.py:10
7 from datasets import Dataset, concatenate_datasets
9 from ragas._analytics import EvaluationEvent, track
---> 10 from ragas.metrics.base import Metric
11 from ragas.metrics.critique import AspectCritique
12 from ragas.validation import (
13     remap_column_names,
14     validate_column_dtypes,
15     validate_evaluation_modes,
16 )
File /local_disk0/.ephemeral_nfs/envs/pythonEnv-e45e8563-0586-47e9-a096-aedc15631cbc/lib/python3.10/site-packages/ragas/metrics/init.py:1
----> 1 from ragas.metrics._answer_correctness import AnswerCorrectness, answer_correctness
2 from ragas.metrics._answer_relevance import AnswerRelevancy, answer_relevancy
3 from ragas.metrics._answer_similarity import AnswerSimilarity, answer_similarity
File /local_disk0/.ephemeral_nfs/envs/pythonEnv-e45e8563-0586-47e9-a096-aedc15631cbc/lib/python3.10/site-packages/ragas/metrics/_answer_correctness.py:11
8 from langchain.callbacks.manager import CallbackManager, trace_as_chain_group
9 from langchain.prompts import ChatPromptTemplate, HumanMessagePromptTemplate
---> 11 from ragas.metrics._answer_similarity import AnswerSimilarity
12 from ragas.metrics.base import EvaluationMode, MetricWithLLM
13 from ragas.utils import json_loader
File /local_disk0/.ephemeral_nfs/envs/pythonEnv-e45e8563-0586-47e9-a096-aedc15631cbc/lib/python3.10/site-packages/ragas/metrics/_answer_similarity.py:9
6 import numpy as np
7 from datasets import Dataset
----> 9 from ragas.embeddings.base import (
10     HuggingfaceEmbeddings,
11     OpenAIEmbeddings,
12     embedding_factory,
13 )
14 from ragas.exceptions import OpenAIKeyNotFound
15 from ragas.metrics.base import EvaluationMode, MetricWithLLM
File /local_disk0/.ephemeral_nfs/envs/pythonEnv-e45e8563-0586-47e9-a096-aedc15631cbc/lib/python3.10/site-packages/ragas/embeddings/init.py:1
----> 1 from ragas.embeddings.base import (
2     AzureOpenAIEmbeddings,
3     FastEmbedEmbeddings,
4     HuggingfaceEmbeddings,
5     OpenAIEmbeddings,
6     RagasEmbeddings,
7 )
9 all = [
10     "HuggingfaceEmbeddings",
11     "OpenAIEmbeddings",
(...)
14     "FastEmbedEmbeddings",
15 ]
File /local_disk0/.ephemeral_nfs/envs/pythonEnv-e45e8563-0586-47e9-a096-aedc15631cbc/lib/python3.10/site-packages/ragas/embeddings/base.py:9
6 from typing import List
8 import numpy as np
----> 9 from langchain.embeddings import AzureOpenAIEmbeddings as BaseAzureOpenAIEmbeddings
10 from langchain.embeddings import OpenAIEmbeddings as BaseOpenAIEmbeddings
11 from langchain.embeddings import FastEmbedEmbeddings as BaseFastEmbedEmbeddings
Additional context
only encountered on databricks

Hi @zohaibdr , can you update langchain and try again?

Hi @zohaibdr , can you update langchain and try again?

Thanks a lot. Its working now with langchain 0.0.352

repo: explodinggradients/ragas


text:
Tiny typo fix: it's -> its

A non-urgent, non-critical fix from contraction to possessive.
Elsewhere there is also an "it's" in Question: Where is France and what is it's capital?, but since that's a prompt a human might reasonably type, and in the answer "its" is used correctly, I thought it didn't need to be fixed.

thanks for the PR!

authors: jjmachan peterkaminski


text:
Text corresponds to multiple labels

python:3.6.5
spacy:2.1.8
spacy_pytorch_transform:0.4.0

offer eg:
All year round "Taste of Love" with Gelato, Chocolate and Coffee. From them, they have developed a picky palate for gelato; but it was until they met seasoned gelatiere Vincenzo, another key figure of 3 ITALIANI, that the duo aspired to plant their feet in Asia, promoting authentic centuries-old gelato culture in this part of the world and beyond 鈥?with LOVE!
label eg:
{"cats": {"Experiences": false, "Services": false, "Fashion Trends": false, "Entertainment": false, "Luxury": false, "Travel": false, "Hotels": false, "Resorts": false, "Holiday": false, "Vacations": false, "Family Vacations": false, "Islands": false, "Honeymoons": false, "Weekend Getaways": false, "Personal Care": false, "Spas": false, "Sports and Fitness": false, "Accessories": false, "Adventure Activities": false, "Airlines": false, "Airports": false, "Arts and Crafts": false, "Attractions": false, "Beauty": false, "Booking Services": false, "Car Rentals": false, "Clothes": false, "Clubs/Nightclubs": false, "Concerts and Music": false, "Cruises": false, "Department Stores": false, "Electronics": false, "Exhibitions": false, "Fishing": false, "Gambling": false, "Games": false, "Gold Beach": false, "Golf": false, "Grocery": false, "Health Care": false, "Household": false, "Market Places": false, "Movies": false, "Museums": false, "Nightlife": false, "Parks": false, "Shopping": false, "Souvenir": false, "Sports Fan": false, "Theme": false, "Tickets": false, "Travel Insurance": false, "Travel Services": false, "Vacation Rentals": false, "Weddings": false, "Michelin": false, "Celebrity Chef": false, "Restaurants": true, "Cuisine": false, "Cooking": false, "Dining": false, "Food & Beverage": true, "Beverages": false, "Alcoholic Beverages": false, "Wineries": false, "Champagne": false, "Bars": false, "Teas": false, "Coffee": false, "Bakeries": false, "Desserts": true, "Barbecue": false, "Breakfast": false, "Buffets": false, "Fast Food": false, "Fruit": false, "Health Foods": false, "Meat": false, "Seafood": false, "Sushi": false}}

First method：
en_core_web_lg + spacy textcat
reuslt: converge
2019-09-26 16:50:47,195 - 27136 - auto_training - INFO - Using 1711 examples (1368 training, 343 evaluation)
2019-09-26 16:50:48,536 - 27136 - auto_training - INFO - Training the model...
2019-09-26 16:50:48,536 - 27136 - auto_training - INFO - LOSS 	  P  	  R  	  F
2019-09-26 16:51:10,290 - 27136 - auto_training - INFO - 60.966	0.805	0.526	0.636
2019-09-26 16:51:30,251 - 27136 - auto_training - INFO - 16.321	0.847	0.588	0.694

second method:
en_pytt_bertbaseuncased_lg+spacy_pytorch_transform+spacy
+https://github.com/explosion/spacy-pytorch-transformers/blob/master/examples/Spacy_Transformers_Demo.ipynb

result :has not converge
2019-09-26 16:50:47,195 - 27136 - auto_training - INFO - Using 1711 examples (1368 training, 343 evaluation)
2019-09-26 16:50:48,536 - 27136 - auto_training - INFO - Training the model...
 LOSS 	  P  	  R  	  F
 6.451	0	0	0
16.321     0	0	0
.......

please tell me:
this data structure references transform model, what changes need to be made

I'm sorry but we can't help with questions like this.

authors: honnibal jameszlj

repo: explosion/spacy-pytorch-transformers


text:
Dev tools web UI not showing

Hi ! Thanks for the amazing tools !
I have problem when using them, for example, with @dev-plugins/react-query
When selecting it in the terminal, I have nothing showing, no chrome, nothing
✔ Dev tools (native only) › Open @dev-plugins/react-query
› Press ? │ show all commands

I have just this checkmark saying that it worked but it didn't, wan can I do ?
note: I have Chrome installed and it works well when open with JS debugger

I had BROWSER variable env set to none to prevent open chrome when npx expo start --web
removing it fix the issue

repo: expo/dev-plugins


text:
Getting error: "Error: GraphQL request failed." while running "eas login"

Summary
I am trying to login using the command eas login but keep getting this error: Error: GraphQL request failed.
It came out of nowhere after I updated the eas cli to the latest version. After that I downgraded to version 9.0.7 which I was using previously but still getting the same error. I have tried resetting my router as well as changing internet connections as well as trying after a gap of 3 hours. Nothing is working. Keep in mind I am not running my react native expo code as of now. I am just trying to login into eas using the cli command and getting the error. The same error is happening with all the commands of eas cli but for now I just want to login and eas login is not working.
What platform(s) does this occur on?
Android
SDK Version
51
Environment
expo-env-info 1.2.0 environment info:
System:
OS: macOS 14.5
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.1.0 - /opt/homebrew/bin/node
npm: 10.7.0 - /opt/homebrew/bin/npm
Watchman: 2024.05.06.00 - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.15.2 - /opt/homebrew/bin/pod
SDKs:
Android SDK:
API Levels: 30, 31, 33, 34
Build Tools: 34.0.0
System Images: android-34 | Google APIs ARM 64 v8a
IDEs:
Android Studio: 2023.3 AI-233.14808.21.2331.11709847
Xcode: /undefined - /usr/bin/xcodebuild
npmPackages:
expo: ~51.0.6 => 51.0.8
react: 18.2.0 => 18.2.0
react-dom: 18.2.0 => 18.2.0
react-native: 0.74.1 => 0.74.1
npmGlobalPackages:
eas-cli: 9.0.7
Expo Workflow: managed
Minimal reproducible example
Run eas login on version 9.0.7 of the eas cli.

Hi @raahimkhan,
Can you try to run EXPO_DEBUG=1 eas login? It should reveal the underlying error and therefore help us check what the issue is.

authors: raahimkhan szdziedzic

repo: expo/eas-cli


text:
undefined is not an object (evaluating '_this._key = guid()')

Using the following versions
"@exponent/react-native-action-sheet": "git://github.com/exponentjs/react-native-action-sheet.git",
// or
"@exponent/react-native-action-sheet": "0.2.3",
"react": "15.3.1",
"react-native": "0.33.0"

When using the the component:
// other imports...
import ActionSheet from '@exponent/react-native-action-sheet';

export default class MyApp extends Component {
  static childContextTypes = {
    actionSheet: PropTypes.func,
  };

  getChildContext() {
    return {
      actionSheet: () => this._actionSheetRef,
    };
  }

  render() {
    return (
        <ActionSheet ref={component => this._actionSheetRef = component}>
          <TabBar/>
        </ActionSheet>
      );
  }
}

I get the error in the title:

Sorry, this doesn't appear to be an issue with this library.

repo: exponentjs/react-native-action-sheet


text:
clearer documentation

I am looking for something that will actually halt processing requests which take beyond a certain amount of time - e.g. the CPU will stop executing any commands for that request. As far as I can tell the library simply fires the given callback when requests take longer than the given amount but does not do anything to cancel or halt execution of that request.
Assuming the latter is close to impossible in node, but it would be great if the README for this library would be clearer on this point.

I thought it was clear, but I guess not? It's hard to think of a way to make it clear for you, so a PR to us with what text changes you think will help clarity would be most welcome :)

I looked and the package's description itself was not great, so I made it more explicit the module is for Connect/Express frameworks. Please feel free to offer up a PR at anytime with suggested wording changes, though, and we can look over it :) The biggest problem we have is what can sound clear to us doesn't mean it sounds clear to you, so getting your suggested wording it the only way we can know what would make it clear for you :)

maybe something like

While the library will emit a 'timeout' event when requests exceed the given timeout, node will continue processing the request until execution completes. Requests will continue to use CPU and memory even if you are returning a HTTP response in the timeout callback. For better control over CPU/memory, you may need to find the events that are taking a long time (3rd party HTTP requests, disk I/O, database calls) and find a way to cancel them, and/or close the attached sockets.

?

Hi @kevinburkeshyp , sorry, I missed your comment somehow! I went ahead and added it verbatim to the readme, with you as the author :) If you would like me to remove you as the author of the comment, just let me know, but I want to give you credit :)!

authors: dougwilson kevinburkeshyp

repo: expressjs/timeout


text:
Limit manifest:allowed_paths to a single file

Loving extism so far!
I have a usecase where I want my plugin to be able to load a file from the filesystem. It's currently possible to use the allowed_paths option within the manifest to give access to a directory. However, it doesn't seem to be possible to limit to a specific file as the following error is present when specifying a file: Not a directory (os error 20).
Alternatively would it be possible to specify that the access is read only?

Last time I checked there wasn't enough support for mounting a single file across all the runtimes we support to allow that. Allowing paths to be readonly should be possible though, I will look into it!

Hi @alex-way, we merged a PR that allows you to specify a directory as read only, it should be in the next release:
https://github.com/extism/extism/pull/733

authors: alex-way mhmd-azeez zshipko

repo: extism/extism


text:
🛑 Jellyfin is down

In efa5b8d, Jellyfin ($SITE_JELLYFIN) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Jellyfin is back up in a0b202f after 5 minutes.

repo: eyenx/upptime


text:
🛑 AUR Repo is down

In ff8fe64, AUR Repo (https://aur.eyenx.ch/x86_64/eyenx.db.tar.gz) was down:

HTTP code: 404
Response time: 403 ms

Resolved: AUR Repo is back up in 2422845.


text:
fix: update to eye v10.16.2

fix: update to eye v10.16.2

:tada: This PR is included in version 16.15.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v16.15.1

Your semantic-release bot :package::rocket:

repo: eyereasoner/eye-js


text:
Fixes build issues of Android example project

Migrates Android's Gradle plugins appliance from imperative to declarative way

Fixing build issues of Android example project

fix #86

@eyoeldefare


text:
Problème actualisation automatique des chaines

Bonjour,
J'ai un soucis avec ce plugin depuis que j'ai changé de box android.
Je l'utilisais avant sur une box Xiaomi et tout fonctionnais correctement.
Or depuis que je suis passé sur Chromecast TV j'ai un soucis d'actualisation : je suis obligé d'actualiser manuellement les chaines 1 fois par jour depuis les options du plugin (cf photo jointe en fin de message).
Sinon la liste des chaines reste vide dans l'onglet TV.
C'est assez pénible... Quelqu'un aurait il une idée pour régler ce problème ?
Merci par avance pour votre aide :)
https://ibb.co/DDwXKzK

Salut @Dragon548 !
Le plugin vient d'être mis à jour, pour ne supporter maintenant plus que l'intégration via IPTV Manager. Si tu as encore des soucis par la suite, c'est sûrement de leur côté (ce plugin ne renvoie des informations que quand IPTV Manager le demande).


text:
Allow multiple brands and add Unbranded utility

fixes #87
I found UnionToIntersection type in keyof.ts and decided to just copy it in brand.ts. Should it imports type for code deduplication?

I will review the PR next week.

I have now checked your code. We can extend the Brand type so that brand can be applied multiple times. However, currently I would not add Brands and Unbranded as it complicates Valibot's source code and testing and I don't quite understand the benefit yet. I have not found any issue or PR at Zod in this regard. So I assume that this feature is rarely needed. If you disagree here, please let me know.

authors: fabian-hiller zkulbeda

repo: fabian-hiller/valibot


text:
Pyro import fails in 1.2.1 netcal.scaling

In 1.2.1 importing netcal.scaling results in the following error:
Traceback (most recent call last):
  File "/path_to_script/ecal.py", line 3, in <module>
    from netcal.scaling import TemperatureScaling, LogisticCalibration
  File "/path_to_miniconda/lib/python3.8/site-packages/netcal/scaling/__init__.py", line 28, in <module>
    from .AbstractLogisticRegression import AbstractLogisticRegression
  File "/path_to_miniconda/lib/python3.8/site-packages/netcal/scaling/AbstractLogisticRegression.py", line 26, in <module>
    import pyro
  File "/path_to_miniconda/lib/python3.8/site-packages/pyro/__init__.py", line 4, in <module>
    import pyro.poutine as poutine
  File "/path_to_miniconda/lib/python3.8/site-packages/pyro/poutine/__init__.py", line 4, in <module>
    from .handlers import (
  File "/path_to_miniconda/lib/python3.8/site-packages/pyro/poutine/handlers.py", line 60, in <module>
    from .collapse_messenger import CollapseMessenger
  File "/path_to_miniconda/lib/python3.8/site-packages/pyro/poutine/collapse_messenger.py", line 7, in <module>
    from pyro.distributions.distribution import COERCIONS
  File "/path_to_miniconda/lib/python3.8/site-packages/pyro/distributions/__init__.py", line 4, in <module>
    import pyro.distributions.torch_patch  # noqa F403
  File "/path_to_miniconda/lib/python3.8/site-packages/pyro/distributions/torch_patch.py", line 87, in <module>
    @patch_dependency("torch.distributions.constraints._CorrCholesky.check")
  File "/path_to_miniconda/lib/python3.8/site-packages/pyro/distributions/torch_patch.py", line 18, in patch_dependency
    module = getattr(module, part)
AttributeError: module 'torch.distributions.constraints' has no attribute '_CorrCholesky'

This is with pytorch 1.7.1, python 3.8, pyro-ppl 1.7.0. Reproduction is as simple as import netcal.scaling.

Reinstalling pyro (pip install pyro-ppl --upgrade) seems to have fixed the issue. For future reference, the error described above happened after upgrade from 1.2.0 to 1.2.1.

repo: fabiankueppers/calibration-framework


text:
Lower FSharp.Core dependency from 6.0.0 to 4.7.2 for better compatibility

Fable.Python right now depends on FSharp.Core v6.0.0 which means that existing projects might need to update their FSharp.Core version when using Fable.Python package. Is it possible to lower the required version of FSharp.Core to 4.7.2 for best compatiblity? especially given the fact that this bindings library doesn't require latest F# features iirc

I thought I had limited it to 5 by using >= 5 but I guess it doesn't work that way. Setting it to ~> 4.7 instead.

authors: Zaid-Ajaj dbrattli


text:
Fixes RHOARDOC-1163

procedure for building a Spring boot app from scratch

@Ladicek  @tradej Thank you for the feedback. I have incorporated your suggestions, Please take a look and let me know your thoughts.

Thank you @inoxx03 for the updates. Merging.


text:
Use unique index instead of constraint

The uniqueness should consider deleted_at column

@baijum snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1633-1


text:
2 fixes which I need: E2506 from Delphi 2010 compiler, Indy makes up useless authentication data.

Doesn't compile in Delphi 2010 anymore. Using RestJsonUtils from SuperObject even in the implementation section breaks D2010's Generics leading to a E2506 pointing to RestJsonGenerics: Result := ctx.AsType(SuperObject.SO(text));
One can't supply (basic) authentication data by SetHeaders in a way that would survive a 40x error from the server using the Indy implementation. Indy tries to use it's user name and password fields to construct an authentication object to retry the connection  and stores that. This data supersedes every authentication header set by SetHeaders if it exists. As user name and password are both '' a (hopefully) invalid basic auth header is sent instead of the one supllied with SetHeaders.

Now I have merge permissions on this repository. I will start to merge/close all pull requests.
As I commented before, will be better send only your changes.

repo: fabriciocolombo/delphi-rest-client-api


text:
[android][okhttp] Fix the crash from okhttp interceptor

Add a null check before creating a new response
Fixes #166

Thanks for the contribution, @thomsontomy!

authors: passy thomsontomy

repo: facebook/Sonar


text:
Dependency conflict on npm run build with react-scripts v2.1.3 and react-gtm-module v1.0.5

Is this a bug report?
Yes

Did you try recovering your dependencies?

Yes, I use npm and recovering my dependencies everytime
Which terms did you search for in User Guide?

(Write your answer here if relevant.)
Environment

Environment:
OS:  macOS 10.14.2
Node:  10.14.1
Yarn:  1.7.0
npm:  6.4.1
Watchman:  Not Found
Xcode:  Xcode 10.1 Build version 10B61
Android Studio:  Not Found
Packages: (wanted => installed)
react: 16.7.0 => 16.7.0
react-dom: 16.7.0 => 16.7.0
react-scripts: 2.1.3 => 2.1.3
Steps to Reproduce

(Write your steps here:)

npx create-react-app create-react-app-dependency-conflict
cd create-react-app-dependency-conflict
modify package.json as follow

{
  "name": "create-react-app-dependency-conflict,
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "react": "16.7.0",
    "react-dom": "16.7.0",
    "react-gtm-module": "1.0.5",
    "react-scripts": "2.1.3"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": "react-app"
  },
  "browserslist": [
    ">0.2%",
    "not dead",
    "not ie <= 11",
    "not op_mini all"
  ]
}

rm -rf node_modules/
npm install
npm run build

Expected Behavior

npm run build should build the app normally
Actual Behavior

Build fail with dependency conflict on "babel-jest"
react-scripts required to fix my local dependency with this dependency "babel-jest" gettings conflicts
The react-scripts package provided by Create React App requires a dependency:
"babel-jest": "23.6.0"....

Looking into the package-lock.json
a dependency of "babel-jest" v21.2.0 is required in global since react-gtm-module required jest-cli 21.1
But react-scripts required babel-jest v23
Actually I can solve this issue by using the latest react-gtm-module v2.0.2
However, I would like to show how this conflict is created and you may fix this issue to prevent similar issue happening in future.
Reproducible Demo

https://github.com/terrylks/create-react-app-dependency-conflict
git clone and npm run build

Hi @terrylks,
Thanks for sharing this. It looks like it was a mistake that they included that as a dependency, and I can see they've fixed that.
Did you try following the steps indicated there? Did that solve it for you?

@mrmckeb
Actually I can solve this issue by using the latest react-gtm-module v2.0.2
However, I am not sure about this issue comes from which side.
If you got nothing to do with this issue, please close this ticket. Thanks.

OK, thanks for the update. We'll keep an eye on this issue to see if it occurs again :)

authors: mrmckeb terrylks

repo: facebook/create-react-app


text:
Error while installing create-react-app

npx create-react-app myapp
npx: installed 98 in 26.252s
Creating a new React app in D:\Web Development\myapp.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@svgr%2Fwebpack - Not found
npm ERR! 404
npm ERR! 404 '@svgr/webpack@4.3.3' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'react-scripts'
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User\AppData\Roaming\npm-cache_logs\2020-08-06T09_38_58_553Z-debug.log
Aborting installation.
npm install --save --save-exact --loglevel error react react-dom react-scripts cra-template has failed.
Deleting generated file... package.json
Deleting myapp/ from D:\Web Development
Done.

Same here, this happens to me on a fresh install (I tested it in Google Cloud Console). There seems to be some problem with the registry?

It's not a CRA problem but in the registry. I guess they are already working to solve it.

Same Issue!

Same issue:
New Ubuntu 20 installation.
Nvm install latest node.

same issue:
yarn install v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@typescript-eslint/eslint-plugin/-/eslint-plugin-1.6.0.tgz: Request failed "404 Not Found"".

Same here. Ubuntu 18.04 fresh install (Google Cloud VM).

Same issue here
Node version: 10.16.0
NPM version: 6.14.4
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@svgr%2fwebpack - Not found
npm ERR! 404
npm ERR! 404  '@svgr/webpack@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

Same issue

Same issue with react-scripts
npm ERR! code E404
npm ERR! 404 Not Found - GET http://registry.npmjs.org/@typescript-eslint%2feslint-plugin - Not found
npm ERR! 404
npm ERR! 404  '@typescript-eslint/eslint-plugin@^2.10.0' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404 It was specified as a dependency of 'react-scripts'

Thank God I thought it was a problem on my local machine. I hope they fix it fast I want to start a new project.

Same issue:
node: v12.18.1
npm: 6.14.5
yarn: 1.22.4
npx create-react-app app
Creating a new React app in ...
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
yarn add v1.22.4
[1/4] Resolving packages...
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/@svgr/webpack/-/webpack-4.3.3.tgz: Request failed "404 Not Found"".
Aborting installation.
yarnpkg add --exact react react-dom react-scripts cra-template --cwd
Deleting generated file... package.json
Deleting generated file... yarn.lock
Done.

Guys, why don't you read the first 2-3 comments before posting? What is the idea of writing "Same issue". Of course you will have the same issue while npm registry is not fully operational...

https://status.npmjs.org/

Same issue when trying to create react app with using npm.
npm ERR! code E404 npm ERR! 404 Not Found - GET https://registry.npmjs.org/@svgr%2fwebpack - Not found npm ERR! 404  npm ERR! 404  '@svgr/webpack@4.3.3' is not in the npm registry. npm ERR! 404 You should bug the author to publish it (or use the name yourself!) npm ERR! 404 It was specified as a dependency of 'react-scripts' npm ERR! 404  npm ERR! 404 Note that you can also install from a npm ERR! 404 tarball, folder, http url, or git url.

@TheMuyu It's an npm issue.

same thing😕
hope it will not take so long..

@TheMuyu It's an npm issue.
Yes now I saw their status site about this error

Update - We are continuing to work on a fix for this issue.
Aug 6, 10:55 UTC

yups same issus....😞

It's fixed right now! I was able to create a project just now... 👍

It's fixed right now! I was able to create a project just now... 👍

Yes can confirm. I created an app now

its working now  .....😍

Still failing here. I'm following a tutorial and it says npx create-react-app . but I get the E404 message


text:
Update available-scripts.md

I updated some part of the docs so that it is more understandable for beginners learning React.

Thanks for the PR but I don't think this is more clear. Create React App is not just for local development.

Create react app is not just for local development bro you can deploy it and use it in production


text:
SSR support

This adds optional SSR support for create-react-app.
It takes a similar approach to TypeScript support -- the existence of a src/index.node.js file enables SSR support. When src/index.node.js does not exist, the behavior does not change compared to the current master branch.
I haven't yet added docs/tests, but you can try it out following the instructions below. If there's any chance of this being merged, I'm happy to add tests/docs -- but I'd like to see some discussion before doing the work.
This PR does not attempt to solve routing or code splitting, as streaming SSR should eventually remove the need for anything extra for handling these, and it's still possible to handle these right now using things like Apollo, react-ssr-prepass or Navi.
How to try it
# first clone the branch, then
yarn
yarn create-react-app ssrtest --universal # also can stack with --typescript
cd ssrtest
yarn start # view source to see that it's server rendered
yarn build
yarn serve # starts a server that loads the node bundle

Alternatively, I've published a version of this to npm as universal-react-scripts, so you can try it out using the standard create-react-app script:
npm init react-app my-ssr-app --scripts-version=universal-react-scripts

The node bundle
When src/index.node.js does exist, a Node version of the bundle will be built alongside the Web version, using src/index.node.js as the entry point instead of src/index.js. Here's my proposed default:
import fs from 'fs';
import React from 'react';
import { renderToString } from 'react-dom/server';
import './index.css';
import App from './App';

const renderer = async (request, response) => {
  // This environment variable points to the location of the *output* of the HTML file
  // generated by webpack, including <script> and <link> tags. It's location will change
  // between development and production.
  let template = fs.readFileSync(process.env.HTML_TEMPLATE_PATH, 'utf8');

  let [header, footer] = template.split('%RENDERED_CONTENT%');
  let body = renderToString(<App />);
  let html = header+body+footer;
  response.send(html);
}

export default renderer;

When this file exists, two bundles of the app will be built: one in build/web, and one in build/node. The version in build/node is a commonjs module, so you can do anything with it, but the above default has been chose to be easily usable from Express, and from Lambda function on services such as ZEIT Now and Firebase. It also allows for SSR during development, using the dev middleware.
The dev middleware
This adds a new middleware that is enabled when src/index.node.js exists. This middleware loads the default export of src/index.node.js, and uses it to render each page during development -- ensuring that server rendering "just works" during development. This should cause no user-facing changes at all.
Other changes

While there was already support for .web.js extensions, I've added support for .node.js extensions as well, which are given preference for the node build.
In order to allow process.env to be used within the Node files, I've modified env.js to pass through any existing value of process.env.
A --universal option is passed through from create-react-app to the init script.
The init script uses existing templates, but also looks for a [templatename]-universal template which can be used to override specific files. This is used to add the src/index.node.js or src/index.node.tsx file when --universal is enabled, and to switch to ReactDOM.hydrate() instead of ReactDOM.render().

Thanks for the PR! This looks promising. We're 100% focused on getting the 3.0 release out right now but as soon as that's done we'll take a closer look at this.

Glad to hear that :-)
About the test suite, it seems to be failing due to filenames in error messages being prefixed by (undefined) , e.g.
 - ./src/App.js
 + (undefined) ./src/App.js
     Line 3:  'foo' is defined but never used  no-unused-vars

I'm pretty sure that the reason for this is that the PR adds source map support within the dev server, so that we can get proper stack traces for the server rendering part:
require('source-map-support').install()

Eventually I think it'd be better to pass stack traces and source maps for errors from index.node.js to the error overlay and handle them there, although this is fiddly because you need to serialize the error, need to somehow fetch sourcemaps for a different build, and then need a way of calling the error overlay imperatively. For the moment, the simplest solution is to just use the source-map-support package, although this adds (undefined) to the error outputs.
Will it be okay to just regenerate the snapshots and leave the (undefined) before the filenames for now? Or will we need another approach?

You will also want to fix the babel config in the webpack.config. I have a PR that outlines one approach to solving this: https://github.com/facebook/create-react-app/pull/6505
Generally you will want to target commonjs when building for node :)

I've just rebased this onto master now that CRA 3 has been released. I've also updated the babel preset to target node correctly, as suggested by @heygrady.
(Sorry about the notification spam -- was trying to clean up unchanged files that had been prettiered in the precommit hook.)
Re: performance issues, perhaps the way to test this is to start by publishing a universal-react-scripts package that can be passed to --scripts-version, so that performance can be tested in the wild?

Okay, universal-react-scripts is available to test out. Will try it in a medium-sized app of my own over the coming few weeks and see how performance goes.
https://github.com/jamesknelson/create-react-app/tree/universal-react-scripts

any timeframe for this?

For what it's worth, I've been using this fork (via the universal-react-scripts package) in a medium sized app, and build performance has been great. I have not run into the issues mentioned by @heygrady.
I still get ~instant rebuilds in an app with ~25 routes and many more components, and that's with styled-components and all the extra weight added by needing to render the page to HTML after each save. The whole development flow is actually pretty nice. It really just feels like create-react-app – you don't even need to think about SSR 95% of the time.
So I guess what I'm saying is that we'd need to add tests before any merge, but it all seems to work pretty well from my experience so far.

Thats awesome! Do you have any documentation on how to upgrade to your version?
Or when do we expect the tests to be fully completed?

@alexvandervegt Big disclaimer here: I won't promise any support for this fork into the future. But with that said, there's some documentation in the README on this branch:
https://github.com/jamesknelson/create-react-app/tree/universal-react-scripts
Re: tests, I'm not sure when I'll be able to find the time. If there's still interest amongst the maintainers in merging this, tests may be something you could take a look at. But I'd wait for confirmation from @iansu before doing any work.

Do you use your code with react-router v.5.0?
Because i get this error:
An error occured while server-rendering your app:
Error: Invariant failed: You should not use  outside a

I’m using Navi, but yeah, you’ll need to use a StaticRouter in index.node.js and a normal router in index.js if you’re using react-router.

I got it all working now and its awesome. Only thing I can not seem to get working is the react-loadable on the server.
How did you manage this?

I'm not using react-loadable, as Navi handles the same thing in my setup. If you can get it working though, it'd be great to see how handle it!

I need to add a plugin to webpack.config but I dont want to eject the react-scripts. If you know a way how to handle it I can make it work and post it here.

Can you give me your example with Navi?

Is it possible the node server is not yet supporting ES2015 modules?
I have this error, while implementing react-loadable:

@alexvandervegt it might be best to move this conversation over to the issues on my forked repository, so that we're not spamming everyone with notifications.
You're right in that node does not currently support ES2015 modules, but this shouldn't be an issue so long as you only import commonjs format packages. As for an example with Navi, it's coming but not quite ready.

For future reference, there's been some interesting discussion around this on a reddit thread today.
After reading through it and using this PR personally for a couple months, my gut feeling is that SSR support can be a lot simpler than existing solutions make it out to be.
The major difference with this approach is that it treats routing, data fetching and the server itself as application code, so it doesn't need to make any decisions about them. All it needs to do is provide a way to build a commonjs module, and make some decisions about the format of the exported middleware (so that rerender-on-file-save works).
This then gives people the freedom to use whatever tools they want, and importantly, it gives people the freedom to come up with new tools as React itself evolves (e.g. with the streaming renderer). For example, it lets you use react-router for routing, Apollo for data fetching, and Express for the server on one hand -- or universal-router, Firebase Functions and raw Suspense for data fetching (once it's ready). Either way works great, because all this PR takes care of is the build itself.
The one issue I see with this design is that the rerender-on-file-save middleware needs to make some assumption about the commonjs module's exports. But given that everyone seems to support express style Request/Response objects, I don't think it would be too controversial to just say "if you want rerender-on-file-save, you need to export a (request, response) => Promise<void>" and let that be that (which is the current behavior).

@jamesknelson, would you be interested in helping to support this feature over the coming months if it gets added in?

@mrmckeb Sure. Even if it doesn't get merged, I'm supporting cura anyway (already merged in and published the changes for 3.1.0). Would definitely prefer to support it here if possible.

@jamesknelson  Any update ?  I hope this gets official support and then I can use it. I am very excited.

@jamesknelson Any update on this? Would love to start using it once it's officially supported :)

I doubt this will be merged, given that the React team seem to be looking into server integration inside of React itself now. Some communication would have been appreciated instead of the "we want to merge this" and then radio silence, but I think it might be best to close this for now to prevent further confusion/wasted time.

Sorry @jamesknelson, this obviously fell off of our radar - which was our fault 100%.
As we're a very small team of volunteers, features like this add complexity that we don't feel we can currently support.
Instead, we recommend using something like Next.js for SSR (or SSG), or Gatsby for SSG. There are obviously other great solutions available too.

So why did you tell @jamesknelson you would have loved to get this merged?

So why did you tell @jamesknelson you would have looked into it?

We should never stop exploring ideas. Investing how SSG would fit into CRA was a good idea at some point but then we discovered things like complexity down the road.
next.js and gatsby already are great alternatives. At this point its better for create-react-app focus on being an option for client side rendered apps only and we will se in the future if it changes depending on how react it self evolves.

I see, the fact it took 2 years to "look into it" is worrying though. Don't expect the community to get involved if that's the respect you give to contributors' time.

Hi @FezVrasta, when I said "I'd love to see us get this in", I meant that I would personally love to see SSR in CRA. I definitely should have worded it differently as we had only just started discussing it, and it wasn't meant as a commitment.
Since that time we've discussed SSR in more detail, and as @andriijas said it proved to be more complicated than we first thought. Mainly, the issue is that we don't have a big enough team (or perhaps a team with enough time) to support the complexity it introduces.

Don't expect the community to get involved if that's the respect you have for contributors' time.

Please remember that we're also part of the community. We all do this in our personal time, and we also contribute to other projects. We encourage contributors to raise PRs only after we discuss new features in issues, as we never want anyone to spend time on something that doesn't end up being merged.
It was a failure on my side that I didn't close the communication loop on this topic, and I'm sincerely sorry that time was wasted and really appreciate the effort that @jamesknelson put into this.

Let me add my 2c here. Razzle is another great alternative to support SSR and it gives the same experience as CRA and supports React Router. https://github.com/jaredpalmer/razzle. It took me no time to move my CRA-based app to Razzle.

authors: FezVrasta alexvandervegt andriijas heygrady iansu jamesknelson marnixhoh mrmckeb nomadus sessionboy


text:
Fix indentation in react-app.d.ts

Only the *.webp module in react-app.d.ts was indented with 4 spaces, everything else is 2 spaces. Introduced in #5978.

🤖 not stale

🤖 not stale

🤖 not stale

🤖 not stale


text:
Fail to upgrade to docusaurus3.5 with theme-search-algolia

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

Prerequisites

[X] I'm using the latest version of Docusaurus.
[ ] I have tried the npm run clear or yarn clear command.
[ ] I have tried rm -rf node_modules yarn.lock package-lock.json and re-installing packages.
[ ] I have tried creating a repro with https://new.docusaurus.io.
[ ] I have read the console error message carefully (if applicable).

Description
Maybe I am not alone. The 3.5 release is out and a PR is created to upgrade to the new version (from 3.4 to 3.5) but the build failed with error message
[ERROR] Client bundle compiled with errors therefore further build is impossible.
Module not found: Error: Can't resolve '@docusaurus/core/src/client/exports/useDocusaurusContext' in '/Users/jove/Dev/timeplus-io/docs/node_modules/@docusaurus/theme-search-algolia/lib/client'
You may check more details at https://github.com/timeplus-io/docs/pull/206
This can be reproduced on CI or local build.
I also tried to remove the "@docusaurus/theme-search-algolia": "^3.5.0", dependency but same error. Please check. Thanks.
Reproducible demo
No response
Steps to reproduce
Check https://github.com/timeplus-io/docs/pull/206
Expected behavior
Upgrade from 3.4 to 3.5 smoothly
Actual behavior
yarn run build failed with error for theme-search-algolia
Your environment

Public source code: https://github.com/timeplus-io/docs
Public site URL: https://docs.timeplus.com
Docusaurus version used: 3.4->3.5
Environment name and version (e.g. Chrome 89, Node.js 16.4): Node 21.1.0
Operating system and version (e.g. Ubuntu 20.04.2 LTS): Mac

Self-service

[ ] I'd be willing to fix this bug myself.

Thanks, should be fixed by https://github.com/facebook/docusaurus/pull/10382

Fixed in v3.5.1 release

authors: Josh-Cena jovezhong slorber

repo: facebook/docusaurus


text:
refactor(theme): split admonitions, make swizzle easier, better retrocompatibility

Breaking change

By default: admonition.keywords are appended to the default list of keywords instead of replacing the default list of keywords

Motivation

It should be easier to customize the layout/view of an admonition
it should be easier to add a custom admonition type
:::important should display label "important" (as it used to be), fix https://github.com/facebook/docusaurus/issues/7767

Test Plan
preview
Test links

Deploy preview:

https://deploy-preview-7945--docusaurus-2.netlify.app/docs/markdown-features/admonitions
https://deploy-preview-7945--docusaurus-2.netlify.app/tests/pages/markdownPageTests

Local:

http://localhost:3000/docs/markdown-features/admonitions
http://localhost:3000/tests/pages/markdownPageTests

Yes, it's not finished yet.
I'm also trying to see what can be shared, so that it's easier later to add a Tailwind theme without too much duplication. I guess we'll also want to share things such as the default labels and icons which are not really theme-specific.

Ready for review.
Satisfied with the current implementation: will merge soon unless I get feedback

I'll try reviewing this tonight.

Looks good enough: marked as safe to swizzle.
Note: as we have more "mapping objects" in themes, we should probably add a way to declare a theme module is an object. This way we could support swizzle --wrap such objects. Showing "wrap is forbidden" to the user is a bit confusing considering we encourage wrapping (manually) in our doc
We'll probably do some more admonition options breaking changes in the future but probably not before v4.0. It looks good enough for me to commit to respecting semver

FYI I kept this PR retrocompatible and plan to backport it.
The breaking change (extendDefaults: true) will be isolated in a separate PR. Also a good time to eventually do other related breaking changes 🤷♂

@slorber all admonitions are broken:

not sure what happened but it has not been backported correctly as I thought it was 😅 will be in v3

authors: Josh-Cena slorber


text:
Show examples of deprecated and updated API for entities

Problem:
The examples included on the current master use the updated-but-undocumented API for Entity state.
We are in the process of releasing a version of Draft that supports both, which will be followed by a version which only supports the new API.
In the mean time, having 'examples' that don't match the current version or documentation is creating confusion. See issues #805, #794, and #778.
Solution:

Comment here and tell us you are working on this - otherwise I'll do it sometime soon.
Create two directories under 'examples' - 'draft-0-9-1' and 'draft-0-10-0'
Move the examples present on the latest 'master' branch into the 'draft-0-10-0' directory.
Copy the examples that were present in version 0.9.0 into the 'draft-0-9-1' directory.

Note that some examples may currently be buggy - see issue #815.

I've created a PR for this now, see #824.

Thanks again for fixing this @tobiasandersen

authors: flarnie tobiasandersen

repo: facebook/draft-js


text:
Building a markdown editor with Draft?

I love https://typora.io however it is not open-source, so spent the day looking at what could accomplish its seamless switching of markdown, content, and code blocks - and support for autocomplete.
It seems based off of https://codemirror.net/mode/gfm/index.html
For draft, I did find https://github.com/ngs/draft-js-markdown-shortcuts-plugin demo which is fairly basic.
As codemirror seems to support all the Typora features (code highlighting, multi-mode editing, markdown mode, autocomplete, etc) and even features that aren't in typora (realtime collaboration) is it feasible for draft to ever get these features?
There is a thread for syntax highlighting on this issue tracker - however it seems that the prime example there is syntax highlighting using prism rather than support for code indentation and whatnot.
There is also a thread for realtime collaboration, but seems early days.
So I'm wondering what the intended feature parity is with codemirror, and whether things like markdown editors make sense for contenteditable editors (draft, prosemirror) or should stick to code editors like codemirror that supports widgets and whatnot

I write down now my thoughts and experience related your issue (it covers a little bit more than your question).
Regard draft.js:
In my opinion markdown could be implemented well in draft.js - because markdown is not really complex and uses several draft.js features which becomes a big plus. The direction of draft-js-markdown-shortcuts-plugin is a good starting point.
However I'm not sure if draft.js is the best framework for everything more in this direction - when it becomes more and more complex editors/IDE's.
(I don't tested the typora product so I speak now more generally)
I would describe it this way:
draft.js is a framework which is ideal to build richtext from simple to medium complexity content especially focused on simply & static api, flat data structure and meta data (entities).
I would think first which functionality of draft.js the editor would really use and what's could be on the roadmap. If it becomes more and more complex and you reach the limits of draft.js (just think about tables) - it could be very difficult to proceed.
Also keep in mind that draft.js is built by facebook mainly for their product. When it differ to much from to their needs or visionary direction of draft.js, it's doubtful if it get merged.

There was a discussion about "realtime collaboration" but it currently it looks like it lands nowhere on the roadmap.
Tree blocks with PR is pending since some month - it's future is unclear.

Maybe think about slat which is much more low level. The learning phase could pay out.
https://github.com/ianstormtaylor/slate
Especially when someone build a product (even a business) which core product is based on the editor - I would be very careful.
Just a side note. When it comes to online code editing I found https://microsoft.github.io/monaco-editor/ is one of the best and also have intelligent auto completion. Yes it's from microsoft, but check it out first ;)

If you don't mind a little bit code wiggling, this exists and works well enough for my MD<-> DraftJS needs
https://github.com/kadikraman/draftjs-md-converter

authors: MarcelCutts aight8 balupton