ImportError: cannot import name 'Markup' from 'jinja2'

Tutorial Cell:
service_name = 'my-diabetes-model'

service = Model.deploy(ws, service_name, [model], inference_config, overwrite=True)
service.wait_for_deployment(show_output=True)

Follows with error:
Tips: You can try get_logs(): https://aka.ms/debugimage#dockerlog or local deployment: https://aka.ms/debugimage#debug-locally to debug if deployment takes longer than 10 minutes.
Running
2022-08-20 06:12:13+00:00 Creating Container Registry if not exists.
2022-08-20 06:12:13+00:00 Registering the environment.
2022-08-20 06:12:15+00:00 Use the existing image.
2022-08-20 06:12:15+00:00 Generating deployment configuration.
2022-08-20 06:12:15+00:00 Submitting deployment to compute.
2022-08-20 06:12:20+00:00 Checking the status of deployment my-diabetes-model..
2022-08-20 06:12:41+00:00 Checking the status of inference endpoint my-diabetes-model.Service deployment polling reached non-successful terminal state, current service state: Failed
Operation ID: 1b60f146-6d64-45a6-b8a3-a3e45d16376b
More information can be found using '.get_logs()'
Error:
{
  "code": "AciDeploymentFailed",
  "statusCode": 400,
  "message": "Aci Deployment failed with exception: Error in entry script, ImportError: cannot import name 'Markup' from 'jinja2' (/azureml-envs/azureml_38f054dd5f1263b8e94a45fd0d8e321f/lib/python3.8/site-packages/jinja2/__init__.py), please run print(service.get_logs()) to get details.",
  "details": [
    {
      "code": "CrashLoopBackOff",
      "message": "Error in entry script, ImportError: cannot import name 'Markup' from 'jinja2' (/azureml-envs/azureml_38f054dd5f1263b8e94a45fd0d8e321f/lib/python3.8/site-packages/jinja2/__init__.py), please run print(service.get_logs()) to get details."
    }
  ]
}

See also https://github.com/MicrosoftDocs/azure-docs/issues/90567
While this may contain a solution, it is for a different environment and not appropriate at the 'tutorial level'
Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c3dfa0c7-942e-7120-1f84-aeec42f9b10a
Version Independent ID: 18a7dc7e-11f3-f612-d239-1682f283aff5
Content: Tutorial: Create the predictive model with a notebook (part 1 of 2) - Azure Machine Learning
Content Source: articles/machine-learning/tutorial-power-bi-custom-model.md
Service: machine-learning
Sub-service: core
GitHub Login: @samuel100
Microsoft Alias: samkemp

@mkrasmus Thanks for the feedback. We are investigating the issue and will update you shortly.

@ram-msft
I believe your recommendations are too obscure for someone who at the 'tutorial level'. This is what I noted when I raised the issue. Why not just update the script in the tutorial for others to access and not have to dig around github for a solution - if they even know what this is?
from azureml.core.model import InferenceConfig
from azureml.core import Environment
from azureml.core.conda_dependencies import CondaDependencies

conda = CondaDependencies()

# add channels
conda.add_channel('conda-forge')

# add conda packages
conda.add_conda_package('python=3.8')
conda.add_conda_package('numpy')
conda.add_conda_package('pandas')
conda.add_conda_package('scikit-learn==0.22.1')

# add pip packages
conda.add_pip_package('azureml-defaults')
conda.add_pip_package('joblib')
conda.add_pip_package('inference-schema')

# create environment
environment = Environment('my-sklearn-environment')
environment.python.conda_dependencies = conda

inference_config = InferenceConfig(entry_script='./score.py',environment=environment)


'content-disposition: ' should be 'content-disposition: inline; filename='

Link to problem area:
https://matrix.org/docs/spec/client_server/r0.6.1#get-matrix-media-r0-download-servername-mediaid
and
https://matrix.org/docs/spec/client_server/r0.6.1#get-matrix-media-r0-download-servername-mediaid-filename

Response headers:

Parameter
Type
Description

Content-Disposition
string
The fileName requested or the name of the file that was previously uploaded, if set.

Issue
What is wrong?
It suggests to write:
content-disposition: Screenshot_2021-05-29_12.24.32.png

The result is that people with clients that show these not inline but as links that you are expected to open in a browser. This is probably most common when bridging to IRC.
Expected behaviour
content-disposition: inline; filename=Screenshot_2021-05-29_12.24.32.png

Synapse already does the right thing. Conduit does not, and that's how @timokoesters and I found the issue.
Link to spec: https://datatracker.ietf.org/doc/html/rfc6266#section-4
Yes, it's a seperate document, so it's technically not even the HTTP spec we're violating but the Internet is weird like that.

Aside from the fact that the suggested Content-Disposition is malformed by missing the filename= part, this seems mostly like a dup of https://github.com/matrix-org/matrix-doc/issues/2578

Oops, forgot to use the search. Sorry. Will add insights over there.


Mic muting doesn't work

The mute button that shows when you are in a voice channel doesn't actually mute you. It only toggles whether or not the muted icon shows up next to your name in the voice channel, even though everyone can still hear you.

This is the same with deafening yourself.


Add section layout toggle to post section detail view

There is a UX issue with the current dashboard.  When I am viewing the detail of a post section, I have to navigate back to the sections list to edit the section's layout.  I propose we add a toggle to the page header to show the section settings.

Completed on grommet-cms-boilerplate/brand-central


Setup Fingerprinting and Metadata Tracking

Story: https://app.shortcut.com/smileid/story/13073/collect-metadata-on-mobile-sdk-v10-ios
Summary
A few sentences/bullet points about the changes
Known Issues
Any shortcomings in your work. This may include corner cases not correctly handled or issues related
to but not within the scope of your PR. Design compromises should be discussed here if they were not
already discussed above.
Test Instructions
Concise test instructions on how to verify that your feature works as intended. This should include
changes to the development environment (if applicable) and all commands needed to run your work.
Screenshot
If applicable (e.g. UI changes), add screenshots to help explain your work.

Can you point this to a new base branch? We don't have the backend set up to accept these values yet


Try some aesthetics changes in story page

Move the status on the top right of the grey frame
Move the username of the assignee in the frame

@benja-M-1 about time ! ;)


"CIRA: Failed to add trusted root certificate" when LMS installed on Linux

HW: Dell Optiplex 7000
AMT:
Version                 : 16.1.27
Build Number            : 2176
SKU                     : 16392
Features                : AMT Pro Corporate
OS: Ubuntu 22.04.2 LTS
LMS installed via snap
When lms is installed, and activating a device with a CIRA profile with ACM remotely, i get the following status upon activation:
time="2024-01-09T14:51:33-07:00" level=info msg="Status: already enabled in admin mode."
time="2024-01-09T14:51:33-07:00" level=info msg="Network: Wired Network Configured"
time="2024-01-09T14:51:33-07:00" level=info msg="CIRA: Failed to add trusted root certificate"
time="2024-01-09T14:51:33-07:00" level=info msg="TLS: unconfigured"
time="2024-01-09T14:51:33-07:00" level=debug msg="closing connection to lms"

If i remove LMS, then activation proceeds normally and without issue.
time="2024-01-09T15:14:30-07:00" level=info msg="Status: Admin control mode."
time="2024-01-09T15:14:30-07:00" level=info msg="Network: Wired Network Configured"
time="2024-01-09T15:14:30-07:00" level=info msg="CIRA: Configured"
time="2024-01-09T15:14:30-07:00" level=info msg="TLS: unconfigured"

I have not established if this applies to Windows as well.

FWIW, using LMS from https://github.com/rgl/lms-binaries works here. I do not use the snap.


Uniswap && sushiswap code mockup of two-pools

Try to simulate the running mode of Uniswap and Sushiswap and represent it with executable code

申请开发 deadline: 2021-04-17 size: 2 @fushang318


Bottom popup loading issue

I have integrated bottom popup into one of my application.
Which do have tableview on selected and row i am trying to pop up exampleViewController.
its loading first time  quickly as per given inputs, on second time its takes time.
On double click on tableviewcell its loading quickly.  Did not understand what went wrong.
    func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {

        print("Selected Index",indexPath.row)
        guard let popupVC = storyboard?.instantiateViewController(withIdentifier: "StatusDetailViewController") as? StatusDetailViewController else { return }
        popupVC.height = 600
        popupVC.topCornerRadius = 30
        popupVC.presentDuration = 0.3
        popupVC.dismissDuration = 0.3
        popupVC.shouldDismissInteractivelty = true
        popupVC.popupDelegate = self
        present(popupVC, animated: true, completion: nil)

    }

StatusDetailViewController is same as  ExamplePopupViewController.

@arishanapalli ,
Present your popupvc into dispatchqueue like,
DispatchQueue.main.async {
self.present(popupVC, animated: true, completion: nil)
}


drivers: watchdog: Add gpio based watchdog support

Add gpio based watchdog(SP706) basic support.
Signed-off-by: qianfan Zhao<EMAIL_ADDRESS>

Codecov Report

Merging #11332 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master   #11332   +/-   ##
=======================================
  Coverage   51.58%   51.58%
=======================================
  Files         216      216
  Lines       27671    27671
  Branches     6938     6938
=======================================
  Hits        14274    14274
  Misses      10648    10648
  Partials     2749     2749

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 84f9dc7...065bf05. Read the comment docs.

A sample dts patch to tested this PR:
diff --git a/boards/arm/nucleo_f070rb/nucleo_f070rb.dts b/boards/arm/nucleo_f070rb/nucleo_f070rb.dts
index 920304295a..d2ef957aab 100644
--- a/boards/arm/nucleo_f070rb/nucleo_f070rb.dts
+++ b/boards/arm/nucleo_f070rb/nucleo_f070rb.dts
@@ -17,14 +17,6 @@
 		zephyr,flash = &flash0;
 	};

-	leds {
-		compatible = "gpio-leds";
-		green_led_2: led_2 {
-			gpios = <&gpioa 5 GPIO_INT_ACTIVE_HIGH>;
-			label = "User LD2";
-		};
-	};
-
 	gpio_keys {
 		compatible = "gpio-keys";
 		user_button: button {
@@ -33,9 +25,19 @@
 		};
 	};

+	gpio_watchdogs {
+		compatible = "wdt-gpio";
+		watchdog0: wdt-gpio {
+			label = "wdt_gpio";
+			gpios = <&gpioa 5 GPIO_INT_ACTIVE_HIGH>;
+			hw-margin-ms = <1600>;
+			status = "ok";
+		};
+	};
+
 	aliases {
-		led0 = &green_led_2;
 		sw0 = &user_button;
+		wdt_gpio0 = &watchdog0;
 	};
 };

@ydamigos Could you please review the dts?

stale, closing. Reopen when there are updates...


Generating client code

Would it be possible to also generate client code? Take the ArgResource path_multi_str example, would be awesome if we could generate something like:
ArgResourceClient::path_multi_str(foo: String, bar: String) -> Result<String, ()>

Double awesome if we could generate multiple versions for different platforms, like using normal reqwest for CLI apps, and then using yew for wasm.

Related to: https://github.com/carllerche/tower-web/issues/63


[FEATURE] change text color of links in "See Also"

Describe the feature you want 描述你的功能需求
I recommand adding the feature that users can configure the text color of links in "See Also".
Now the default color is black and I don't find any configuration entry to change it.
Is this feature possible? Thanks.
Useful reference 有价值的参考
No response

You can chang any color in your assets/css/_custom.scss
#see-also {
  color: red;
}


Process level breakdown of CPU/Memory

named job objects may just do the trick - lets investigate

Tried implementing what David suggested but got a 503 during the smoke test, so will need to investigate further

In my opinion this looks like a very large undertaking that we may determine to be worth taking but I don't think it is right now.


add support for named grid areas

Description
I use named grid areas all the time to simplify complex responsive layouts. I thought it'd be nice to be able to define these simply.

Adds a template prop to the Grid component to set the grid-template CSS property
Adds a gridArea layout prop

Testing steps
Example usage in apps/playground/app/test-grid-area/page.tsx

@vladmoroz Any further comments?

@vladmoroz Any more to do here?

@fauxparse I took a closer look and adjusted a few things so that it works inline with the rest of the layout API
Basically, instead of the larger grid-template shorthand and <Grid template="..."> prop, I changed to grid-template-areas and <Grid areas="...">. This feels more complementary alongside the existing grid-template-columns and grid-template-rows; also defining the track lengths in grid-template is just too much in JSX.
I'll merge now and release—thanks for the contribution


[Adaptive] botbuilder-dialogs-adaptive-tests package name is incorrect

Versions
branch: master
Describe the bug
botbuilder-dialogs-adaptive-tests should be botbuilder-dialogs-adaptive-testing
Per C#, it should be botbuilder-dialogs-adaptive-testing (master)
When this issue is fixed, the CI needs to be updated with the new package name.

[bug]

We have two different packages in C# sdk:

Microsoft.Bot.Builder.Dialogs.Adaptive.Tests
Microsoft.Bot.Builder.Dialogs.Adaptive.Testing

Testing is for testing framework and other test related components, while Tests only have test cases. Our package botbuilder-dialogs-adaptive-tests covers both testing framework and test cases, do we need to split this package into two? Thanks. @stevengum

adaptive-testing/
src/
tests/

Per 7/2/20 sync-up, this packageisn't a "preview" ship blocker and has been accordingly de-prioritized.
It would still be better to get this done ahead of time so that we avoid any future issues through memory loss.


Space Invaders Effect

Three types of space invaders, squid, crab, and octopus, march down the sky/field.
I've put the alien_color and background_color variables near the top of run() so it is easier to change the colors if the intensity is too high on the LED screen.

Just added matrix-like effect that draws lines that move down the screen with static.  Variables near top of code allow for color change, max speed, and percent chance of static of each pixel in a matrix line.

Added a new tic tac toe effect.


conll2012 setup issue

Hello, thanks for raising this question.
We used pre-trained word embeddings (Glove and ELMo). You can use the script scripts/data_setup.sh to download them and place them in a data folder.
Other datasets are also expected to be in the data folder (see the paths in the configuration files configs/*.json).
For instance, we compile the CoNLL2012 coreference data using this script from AllenNLP: https://github.com/allenai/allennlp/blob/master/scripts/compile_coref_data.sh
It compiles the CoNLL2012 data, and dump the coreference annotations into a single file.
For NER CoNLL, it is basically the same data as coreference which have not been dumped into the same single file (we can probably do something quick to avoid this data duplication).
Concerning the ACE data, we pre-process them so that the Mention Detection data match a CoNLL-NER format and the Relation Extraction task match a CoNLL-SRL format. Both are saved in a data/ace2005 folder.
If you want to use other datasets, it seems coherent to place them in the data folder, and use (if not modify) the dataset_readers classes.
Victor

Hi,
I want to reproduce your NER result. However,  I met a problem when I set up conll2012 data.
I used this script https://github.com/allenai/allennlp/blob/master/scripts/compile_coref_data.sh. But it warned that there is no .parse file in the folder.
could not find the gold parse [.//data/files/data/english/annotations/bc/cctv/00/cctv_0001.parse] in the ontonotes distribution ... exiting ...

cat: 'conll-2012/v4/data/development/data/english/annotations/*/*/*/*.v4_gold_conll': No such file or directory
cat: 'conll-2012/v4/data/train/data/english/annotations/*/*/*/*.v4_gold_conll': No such file or directory
cat: 'conll-2012/v4/data/test/data/english/annotations/*/*/*/*.v4_gold_conll': No such file or directory

Originally posted by @djshowtime in https://github.com/huggingface/hmtl/issues/2#issuecomment-481519182

You will have to get the CoNLL-2012 data from http://conll.cemantix.org/2012/data.html

Hello @djshowtime,
As @Evpok said, you need to get the data first. I cannot distribute the data. But the script you use is also the one i used!
Victor


Theming : UX

The theme settings set by an admin should be saved and should be retrieved on application boot

[ ] Theme settings loaded at application boot
[ ] Theme form to set settings

[ ] Colors can be set
[ ] Brand images can be uploaded, removed (requires #1066)
[ ] Theme can be undone

[ ] Theme resource to talk to endpoint

Belongs to #1067

should this issue also reference #1066 or is that implied by the parent ?

Yes, I've updated the ask.


add SCOOP to the list

https://dtai-kg.github.io/SCOOP/
to the section "Shape convertors" or was it "Shape generators"

Please retitle this from capture SCOOP to a more accurate add SCOOP to the list(s).

Based on current classified items (if these sections are some sort of classes for their items) it should belong to the "Shape generators" (xxx -> shapes), not to the "Shape convertors" (shapes -> xxx).
And rudof-convert should be in both sections.

@amivanoff "generator" also means "from the structure of an RDF graph" (shape induction). Eg Hanami (a commercial tool).
Make a PR for these section descriptions and I'll add a bit.


angular-cli doesn't respond

OS?
macOS 10.12
Versions.
ng --version doesn't respond as well but the installed version is<EMAIL_ADDRESS>➜  ~  node -v
v6.7.0

The log given by the failure.
There is actually no error message ng new my-app or ng --version just hang forever with no output until I hit Control-C.
➜  ~  ng new my-app
^C

@Fahrradflucht -- do you have a npm-debug.log? If so, cat it...  And what does your /var/log/messages say when this happens?

do you have a npm-debug.log?

No

And what does your /var/log/messages say when this happens?

There is no /var/log/messages
--
As far as I can see there isn't even a node process that gets spun up.

Same issue here... no logs either.

So I had this issue just now, I did some tracing and saw that the process was hanging shortly after trying to access /usr/local/var/run/watchman/<myusername>-state - it looks like it was trying to connect to the sock domain socket within that directory. The only problem is, I don't have any watchman process running, so it was just hanging. I was tracing system calls, and I couldn't spot where the code that was causing it to try and do this was.
I fixed it by removing my /usr/local/var/run/watchman directory. It's possible the problem I hit is a separate issue.

Deleting /usr/local/var/run/watchman/<myusername>-state fixed it! 🎉
Any idea why this is?

Not too sure of why this happens. Maybe some internal ember-cli machinery is hooking up into your local watchman dir. Need to look into it.

Issue has been resolved, closing.

@Brocco still cannot CTRL-C to stop ng serve . It hands and and have to do kill -9
I am using angular cli v1.0.0-beta.26

As of 1.4.4 CTRL-C still does not stop ng serve on Mac.  It would be really nice if we didn't have to kill the listening process.

same on win10, ctrl+c never stops the node process. it's a joke.


Spelling Error

[Enter feedback here]
There is a spelling error. It reads "files hare" instead of "file share". Thank you!

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 4d07acc7-3a8c-13f9-abf7-f7effb7700f2
Version Independent ID: c236823a-06c3-2803-9cde-5dc5cc95059f
Content: Tutorial: Migrate SQL Server to Azure SQL Managed Instance online using Azure Data Studio - Azure Database Migration Service(DMS)
Content Source: articles/dms/tutorial-sql-server-managed-instance-online-ads.md
Service: dms
GitHub Login: @mokabiru
Microsoft Alias: mokabiru

Hi @serverbaba Thanks for your findings,We will investigate and update as appropriate

This is fixed and will be published on 06/14. Thanks for the feedback.


Update to Laravel 6

Heads up!
I have updated Latex.php with the new helper Str::random but I don't know if this works with the requirements "illuminate/support": "5.4.x|5.5.X|5.6.X|5.7.X|5.8.X|6.0.X".
(I am just using this package in a new laravel 6 installation. I found that the original repo was unmantained and check that your fork works fine).

Thank you for your contribution!

Hey, have you check what I said about "illuminate/support": "5.4.x|5.5.X|5.6.X|5.7.X|5.8.X|6.0.X"...?
I don't know if it is working in laravel 5.8!
:)

Thank you @hhummell81, actually, the very reason I made laravel-pdf-latex instead of using the old one is that I am using Laravel 5.8, so yes, it works in Laravel 5.8.


Could not find JS function u'gr'

youtube-dl -v https://www.youtube.com/watch?v=Depf1gKhBno
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v', u'https://www.youtube.com/watch?v=Depf1gKhBno']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2<IP_ADDRESS>
[debug] Python version 2.7.11 - Linux-<IP_ADDRESS>111-x86_64-with-debian-stretch-sid
[debug] exe versions: avconv 2.8.3, avprobe 2.8.3, ffmpeg 2.8.3, ffprobe 2.8.3, rtmpdump 2.4
[debug] Proxy map: {}
[youtube] Depf1gKhBno: Downloading webpage
[youtube] Depf1gKhBno: Downloading video info webpage
[youtube] Depf1gKhBno: Extracting video information
[youtube] {22} signature length 43.43, html5 player en_US-vflrSqbyh
[youtube] Depf1gKhBno: Downloading player https://s.ytimg.com/yts/jsbin/player-en_US-vflrSqbyh/base.js
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 856, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 771, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 834, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/lib/python2.7/dist-packages/youtube_dl/jsinterp.py", line 241, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'gr'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Could not find JS function u'gr'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 856, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 771, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 834, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/lib/python2.7/dist-packages/youtube_dl/jsinterp.py", line 241, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'gr'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 663, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 290, in extract
return self._real_extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 1410, in _real_extract
encrypted_sig, video_id, player_url, age_gate)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 866, in _decrypt_signature
'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 856, in _decrypt_signature
video_id, player_url, s
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 771, in _extract_signature_function
res = self._parse_sig_js(code)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/youtube.py", line 834, in _parse_sig_js
initial_function = jsi.extract_function(funcname)
File "/usr/lib/python2.7/dist-packages/youtube_dl/jsinterp.py", line 241, in extract_function
raise ExtractorError('Could not find JS function %r' % funcname)
ExtractorError: Could not find JS function u'gr'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Could not find JS function u'gr'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

You are using an outdated version of youtube-dl. Read our FAQ if you have troubles updating.


Hot Reload stopped working with React "^17.0.1"

Describe the bug
Hot reloading when the redux-state change stopped working when I use CRA to get the last React version. Noticed that it is due to React version and I made a test creating a new react project, as a result the package.json shows
"dependencies": {
    "@testing-library/jest-dom": "^5.11.5",
    "@testing-library/react": "^11.1.0",
    "@testing-library/user-event": "^12.1.10",
    "react": "^17.0.1",
    "react-dom": "^17.0.1",
    "react-redux": "^7.2.1",
    "react-scripts": "4.0.0",
    "redux": "^4.0.5",
    "web-vitals": "^0.2.4"
  },

then change it to a previous version of react (copied from an old project)
"dependencies": {
    "@testing-library/jest-dom": "^4.2.4",
    "@testing-library/react": "^9.5.0",
    "@testing-library/user-event": "^7.2.1",
    "react": "^16.13.1",
    "react-dom": "^16.13.1",
    "react-redux": "^7.2.1",
    "react-scripts": "3.4.3",
    "redux": "^4.0.5"
  },

And it continue to works as always.
Did you try recovering your dependencies?
yes
Environment
current version of create-react-app: 4.0.0
running from C:\Users\stewa\AppData\Roaming\npm\node_modules\create-react-app
System:
OS: Windows 10 10.0.19041
Binaries:
Node: 12.9.1 - C:\Program Files\nodejs\node.EXE
Yarn: Not Found
npm: 6.14.8 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 86.0.4240.111
Edge: Spartan (44.19041.423.0), Chromium (86.0.622.51)
Internet Explorer: 11.0.19041.1
npmPackages:
react: ^17.0.1 => 17.0.1
react-dom: ^17.0.1 => 17.0.1
react-scripts: 4.0.0 => 4.0.0
npmGlobalPackages:
create-react-app: Not Found
Steps to reproduce
(Write your steps here:)

I have a file with a state with this value in my Redux reducer

const initialState = [
  {
    id: Date.now(),
    task: "new todo ",
    completed: false,
  }
];

Modify the object in the file to this

const initialState = [
  {
    id: 1,
    task: "new todo ",
    completed: false,
  },
  {
    id:123,
    task: "new todo ",
    completed: false,
  }
];

As previous versions of React / CRA the page force a reload, displaying in the page the new object added, but it's not anymore

Expected behavior
Even if you change the text of one of the objects in the reducer it used to reload the page. I'm expecting to see the new state in the page as I save a file when the state change
Actual behavior

Here you can see I saved the file and the page is not showing the new state, and the new data.
Reproducible demo
https://github.com/StewartGF/todo-test
I created this clean project with CRA, it has react v17
You can change the version in the package.json to what I paste in the description and use npm install in order to see the project working as it was working in previous versions.

CRA 4 uses Fast Refresh instead of Hot Reload, the page doesn't reload on file changes.

@FezVrasta Fast refresh is currently opt-in only and you must specify the environment variable FAST_REFRESH, I don't think @StewartGF set it, but it would be good to know whether he did to make sure it's not that.

@FezVrasta Fast refresh is currently opt-in only and you must specify the environment variable FAST_REFRESH, I don't think @StewartGF set it, but it would be good to know whether he did to make sure it's not that.

I'm not using Fast refresh, this is a new project. But from what I read about Fast refresh the behaviour seems similar (I've never used it, so im not 100% sure).
Maybe now it's enabled by default and I have to disable it?

fast refresh is enabled by default.

So is hot reloading removed entirely?
I'm having trouble refreshing the app at all, adding or removing components does nothing, I have to manually refresh the page to get the updates.Only the styles update when changed.
I'm using is the config folder and start script from react-scripts, nothing else.

@RosenTomov hot reloading does not appear to be working from changes to the root index.js. At least that's what I'm seeing in my project and in the unaltered app created from create-react-app. But further down from index.js in a component, hot reloading does appear to be working. At least that's what I'm seeing so far in my limited testing.

@FezVrasta fast refresh is definitely NOT enabled by default, or I'm not able to read code anymore, have a look: https://github.com/facebook/create-react-app/pull/8582/files
For example, one comment explicitly mentions:
        // Whether or not react-refresh is enabled.
        // react-refresh is not 100% stable at this time,
        // which is why it's disabled by default.

For me, hot reloading (without the FAST_REFRESH flag) also doesn't work, with the FAST_REFRESH flag it works for me.

@FezVrasta fast refresh is definitely NOT enabled by default, or I'm not able to read code anymore, have a look: https://github.com/facebook/create-react-app/pull/8582/files
For example, one comment explicitly mentions:
        // Whether or not react-refresh is enabled.
        // react-refresh is not 100% stable at this time,
        // which is why it's disabled by default.

The comment is outdated, fast refresh is enabled by default, in fact the checks is FAST_REFRESH !== 'false' because they assume any value different than false is going to be true

npm run start -FAST_REFRESH=true
hot reload working

Fast refresh also doesn't work for me. I have to manually refresh the page to see any updates.

+1

The worst (but quite logical) thing about this is that everything that's imported in index is ignored too.
Since I'm wrapping my app in an I18nextProvider there, I need to manually refresh each time I change a translation.
Same goes for my Material UI theme, and I can only guess that Redux users suffers from this too.

I'm facing the same issue  "react-scripts": "4.0.0", "react-dom": "^17.0.1", "react": "^17.0.1",

npm run start -FAST_REFRESH=true

This works on Chrome/Windows 10. Thanks @lyqline 👍🏽

I can also confirm that this is happening and that enabling FAST_REFRESH will get some hot reloading, but the concern is that this is not fully backed, but it seems like it's the only option to have hot reloading. Is this really the right answer?

npm run start -FAST_REFRESH=true does NOT work for me on Chrome/MacOS Catalina.
As @Sheparzo mentioned though, the problem seems to be happening only with changes to the root index.js file. With .css & other .js files, hot reload is working fine for me.

Greetings, a solution to the problem is given on the stackoverflow https://stackoverflow.com/questions/42189575/create-react-app-reload-not-working

Just duplicated and older project and updated the packages to c-r-a 4.0.1, react 17.0.1, typescript 4.1.2.
Running in Firefox on Windows 8.1.
Browser was not updating when code was changed.
Added FAST_REFRESH=true to .env, restarted the node process - browser now updates automatically when code is changed.

It looks like the issue is in react-hot-loader. It relies on React internal API which is no longer available in React 17: instance._reactInternalFiber.
See (here)[https://github.com/gaearon/react-hot-loader/blob/22328398ac8235cb0bcae6021b69cdc4c0d6fdf3/src/internal/reactUtils.js#L33] - when react-hot-loader detects changes and tries to figure out what to re-render (getReactStack =>getInternalInstance ), it tries to read instance._reactInternalFiber, but it's not available in React 17 anymore because of (this PR)[https://github.com/facebook/react/pull/18377/files#diff-1c9c9fd4cfb4774ae7ca1cd75c675c2a694381644be4135941bafe2d328936a8]. I've changed react-hot-loader locally and this resolves the issue. So react-hot-loader has to be fixed

console.dir(process.env); placed at the root of the app will confirm right away whether FAST_REFRESH and other settings are set.

I am not sure everyone is having the same problem.
For me, when i have nothing on .env or FAST_REFRESH=true, i will get the fast refreshes for components change, but other files changes will not reload the page, despite my console showing that it recompiled.
When i have FAST_FRESH=false, everything is hot-reloading and everything works.

I am not sure everyone is having the same problem.
For me, when i have nothing on .env or FAST_REFRESH=true, i will get the fast refreshes for components change, but other files changes will not reload the page, despite my console showing that it recompiled.
When i have FAST_FRESH=false, everything is hot-reloading and everything works.

Worked! With React 17.0.1 and react-scripts 4.0.0  and with FAST_REFRESH=true (default) changes to components are reflected seemlessly, but changes to other dependencies are not reflected in the UI at all without manual refresh. Setting the flag to false in .env didn't change anything but when I updated to react-scripts 4.0.1 setting FAST_REFRESH=false in .env brought back the hot reload.

For me, when i have nothing on .env or FAST_REFRESH=true, i will get the fast refreshes for components change, but other files changes will not reload the page, despite my console showing that it recompiled.

Thank you! Creating a .env file and adding FAST_REFRESH=false to my project root fixed my issue of hot-reloading not working on Windows 10

same here

FAST_REFRESH=true/false does not work for me (create-react-app v4.0.1). I see the app recompiling, and something appears to be happening in my browser (I see a scrollbar for a milisecond) but no actual component rerender. Tested in Chrome and Firefox on Windows 10.

@brense please ensure you do kill the "npm start" process between each .env change.
FAST_REFRESH=false should work

I have a .env file in my root with FAST_REFRESH=false, killed npm start and restarted, but its still not working.

Where exactly can I find the FAST_REFRESH option so I can change it.  I console.dir(process.env) and see it. How can I change it? If I need to find that file or another file please show me the way. Thanks for the help !

You just create your own .env file in the root of your project (where the package.json is) and put FAST_REFRESH=false in it

Thank you Brense

Is anyone working on fixing it so that hot reload works correctly on all files in the project?

Is anyone working on fixing it so that hot reload works correctly on all files in the project?

Did you notice it not working on any specific files? So far, with react 17.0.1 and react-scripts 4.0.1, FAST_REFRESH=false in a .env file has fixed the issue for me on a Windows 10 machine using Firefox. If there are some instances where you saw it failing, I'd appreciate it if you shared. Cheers!

Is anyone working on fixing it so that hot reload works correctly on all files in the project?

Did you notice it not working on any specific files? So far, with react 17.0.1 and react-scripts 4.0.1, FAST_REFRESH=false in a .env file has fixed the issue for me on a Windows 10 machine using Firefox. If there are some instances where you saw it failing, I'd appreciate it if you shared. Cheers!

I have not tried creating the .env folder with "FAST_REFRESH = false", but leaving everything by default, with an "npx create-react-app my-app" and entering the project from VSC, starting the server with an "npm start ", removing all the files from" src "and creating new files, when I save the changes it does not refresh in Chrome.
You can see from the inspector how it does try to refresh and change the colors of the elements of the inspector, on the other hand, if you do not press F5 or Ctrl + F5 it does not refresh the content in the browser.
Tested as of yesterday.

Autorefresh on change only works in Firefox for me... I've also upgrade my react-scripts package from ^4.0.0 to 4.0.1. FAST_REFRESH=false doesnt work for me... Chrome has still problems with auto refresh...

Adding FAST_REFRESH=false to .env or .env.development works for me on OS X using react-scripts 4.0.1, thank you @brense!

creating your own .env file and putting FAST_REFRESH=false in it works! I am on windows 10,  "react": "^17.0.1" and "react-scripts": "4.0.1" and chrome for my browser. Thanks, @NicolasCharpentier, @brense, and everyone else.

I also experienced this issue but after creating a new project with parcel instead of webpack everything works perfectly. Hope this helps.
FYI you can use: CreateApp Frontend build config generator to quickly get things setup.

create .env file and add FAST_REFRESH=false is also works for me. thank you @brense , i just start learning reactjs and it's already confusing.

npm run start -FAST_REFRESH=true
hot reload working

that works for me.
thanks @lyqline!

npm run start -FAST_REFRESH=true
hot reload working

that works for me.
thanks @lyqline!

This thread is totally confused. My conclusion,
nothing => nothing
FAST_REFRESH=false => live reloading
FAST_REFRESH=true  => hot reloading

This thread is totally confused. My conclusion,
nothing => nothing
FAST_REFRESH=false => live reloading
FAST_REFRESH=true  => hot reloading

Create .env file
Add FAST_REFRESH=false

Works for me on windows 10, react: 17.0.1 - react-dom: 17.0.1 - react-scripts: 4.0.1 and chrome for my browser.

Create .env file
Add FAST_REFRESH=false

Works for me on windows 10, react: 17.0.1 - react-dom: 17.0.1 - react-scripts: 4.0.1 and chrome for my browser.

Thanks anybody who advised the .env file with FAST_REFRESH=false
My tip: dont forget to create the .env file outside for your src folder
windows 10, react: 17.0.1 - react-dom: 17.0.1 - react-scripts: 4.0.1 chrome/firefox

Thanks anybody who advised the .env file with FAST_REFRESH=false
My tip: dont forget to create the .env file outside for your src folder
windows 10, react: 17.0.1 - react-dom: 17.0.1 - react-scripts: 4.0.1 chrome/firefox

creating .env file in root and adding FAST_REFRESH=false doesnt work for me both in Chrome and Firefox. When I save the changes in index.js, vsc terminal is compiling the changes and it takes almost 10 seconds.. And then I can see the changes in browser

creating .env file in root and adding FAST_REFRESH=false doesnt work for me both in Chrome and Firefox. When I save the changes in index.js, vsc terminal is compiling the changes and it takes almost 10 seconds.. And then I can see the changes in browser

issue still persist...it takes few seconds to hot reload

issue still persist...it takes few seconds to hot reload

These fixes haven't worked for me.
Windows 10 version 20H2 (build 19042.746). WSL2 Ubuntu.
Linux Bigbox 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
I've tried setting FAST_REFRESH to both true and false in:

The .env file
the environment variable using export and set
the start scripts line ("start": "react-scripts start -FAST_REFRESH=false")
appending it to the command line: npm run start -FAST_REFRESH=false (also with yarn)

The biggest clue is that the terminal output never shows a recompile whether I edit App.js or a component file. The browser console has a single line [HMR] Waiting for update signal from WDS.... Webpack reports that it disconnects when I kill the server.

These fixes haven't worked for me.
Windows 10 version 20H2 (build 19042.746). WSL2 Ubuntu.
Linux Bigbox 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
I've tried setting FAST_REFRESH to both true and false in:

The .env file
the environment variable using export and set
the start scripts line ("start": "react-scripts start -FAST_REFRESH=false")
appending it to the command line: npm run start -FAST_REFRESH=false (also with yarn)

The biggest clue is that the terminal output never shows a recompile whether I edit App.js or a component file. The browser console has a single line [HMR] Waiting for update signal from WDS.... Webpack reports that it disconnects when I kill the server.

Make absolutely sure that you have react scripts version 4.0.1 or higher, in package.json it should show: "react-scripts": "^4.0.1"
If that is not the case, execute npm i --save react-scripts.

Make absolutely sure that you have react scripts version 4.0.1 or higher, in package.json it should show: "react-scripts": "^4.0.1"
If that is not the case, execute npm i --save react-scripts.

When I saved the changes in files except index.js, it compiled and refreshed the page in seconds. But in index.js, it compiled but didn't refresh the page. I have finally solved the problem as follows;
1)In package.json change to 'react-scripts':'3.4.4'
2) Delete package-lock.json
3) rm -rf node_modules
4) npm install
5) npm start
You don't have to change react and react-dom version. It works now just fine.
Secondly, I have switched from Windows 10 to Ubuntu. I don't have to apply these steps anymore. It works in Ubuntu without problem

When I saved the changes in files except index.js, it compiled and refreshed the page in seconds. But in index.js, it compiled but didn't refresh the page. I have finally solved the problem as follows;
1)In package.json change to 'react-scripts':'3.4.4'
2) Delete package-lock.json
3) rm -rf node_modules
4) npm install
5) npm start
You don't have to change react and react-dom version. It works now just fine.
Secondly, I have switched from Windows 10 to Ubuntu. I don't have to apply these steps anymore. It works in Ubuntu without problem

You should never delete your package-lock unless there's a merge conflict in it. If you change your react-scripts version to ^4.0.1, it will work as well and you will be on the latest version :) Executing npm i --save react-scripts should fix this for you. Stop and restart your app. If it still doesnt work, delete your node_modules and run npm i again.

You should never delete your package-lock unless there's a merge conflict in it. If you change your react-scripts version to ^4.0.1, it will work as well and you will be on the latest version :) Executing npm i --save react-scripts should fix this for you. Stop and restart your app. If it still doesnt work, delete your node_modules and run npm i again.

Mac OS Big Sur, Chrome 87.0.4280.141.
Adding FAST_REFRESH=false to an env file doesn't change anything.

Mac OS Big Sur, Chrome 87.0.4280.141.
Adding FAST_REFRESH=false to an env file doesn't change anything.

While I'm sure this is probably true for WSL 2 users shown here , an alternative I have found while still having my project in the /mnt (so windows file system instead of WSL2 system), follow this SO link
React: 17.0.1
React-Scripts 4.0.1
Command: CHOKIDAR_USEPOLLING=true npm start

While I'm sure this is probably true for WSL 2 users shown here , an alternative I have found while still having my project in the /mnt (so windows file system instead of WSL2 system), follow this SO link
React: 17.0.1
React-Scripts 4.0.1
Command: CHOKIDAR_USEPOLLING=true npm start

If that is not the case, execute npm i --save react-scripts.
I am on react / react-dom v16.13.1 and I only upgraded to "react-scripts": "^4.0.1" because npm audit told me to fix a security vulnerability.
So my combo is v16.13.1 and react-scripts 4.0.1 and my pages are not reloading/refreshing, even though the server is re-starting I can see the Cmd prompt restarts (I'm on Windows 10).

If that is not the case, execute npm i --save react-scripts.
I am on react / react-dom v16.13.1 and I only upgraded to "react-scripts": "^4.0.1" because npm audit told me to fix a security vulnerability.
So my combo is v16.13.1 and react-scripts 4.0.1 and my pages are not reloading/refreshing, even though the server is re-starting I can see the Cmd prompt restarts (I'm on Windows 10).

@danimal-johnson
You nailed it. I have the WSL2/Win10 here and moving to a 100% Linux folder solved all hot/fast reload issues and enourmoulsy improved compiling performance.

@danimal-johnson
You nailed it. I have the WSL2/Win10 here and moving to a 100% Linux folder solved all hot/fast reload issues and enourmoulsy improved compiling performance.

@brense please ensure you do kill the "npm start" process between each .env change.
FAST_REFRESH=false should work

It worked for me, even when I make changes on the index.js files, thank you

@brense please ensure you do kill the "npm start" process between each .env change.
FAST_REFRESH=false should work

It worked for me, even when I make changes on the index.js files, thank you

For anyone else running into this issue who still hasn't been able to solve it with everything above, if while updating to React 17 you also updated to Webpack 5 and are using webpack-dev-server, see the footnote of this troubleshooting guide for what finally solved the issue for me.
(Tldr; add target: 'web' to your development webpack config).
https://github.com/pmmmwh/react-refresh-webpack-plugin/blob/main/docs/TROUBLESHOOTING.md

For anyone else running into this issue who still hasn't been able to solve it with everything above, if while updating to React 17 you also updated to Webpack 5 and are using webpack-dev-server, see the footnote of this troubleshooting guide for what finally solved the issue for me.
(Tldr; add target: 'web' to your development webpack config).
https://github.com/pmmmwh/react-refresh-webpack-plugin/blob/main/docs/TROUBLESHOOTING.md

A summary of this very long and confusing thread for anyone coming in:

CRA used to use something called "Hot Reload."
CRA v4 switched to "Fast Refresh".

Fast refresh can update some components without reloading the whole page, unlike hot reload, which reloads the whole app every time you make any change. (With the exception of CSS, I think.) The downside of Fast Refresh is that, for some changes (I'm going to hazard a guess - changes that would actually require a reload to implement?), it won't implement them, and won't tell you it hasn't, either. So you have to manually refresh or, I've found, manually restart the development server to see all changes. This can outweigh the convenience of Fast Refresh in many cases.
So, if you'd like to revert to Hot Reload behavior, create a .env file in the root folder of your project, and add
FAST_REFRESH=false
to it. Make sure to close any running development server, and restart. If that doesn't work, check to make sure you have the latest version of CRA, not 4.0.0 but 4.0.1; search react-scripts in your project's package.json file to see. If you need to upgrade, npm i --save react-scripts..

Modify your react-scripts line (package.json) like so:
"start": "FAST_REFRESH=false react-scripts start",

that wont work cross platform, better to use the .env file otherwise you'd have to use something like cross-env to make your solution work cross platform.

I had the same issue with WSL2.
.env with the content of CHOKIDAR_USEPOLLING=true helped.

I'm using Ubuntu 20.04 on VirtualBox for dev. React fails to reload when I make file changes.
The only way I observe changes is by manually refreshing the browser or setting FAST_REFRESH=false in my .env.
You'd think Ubuntu LTS would be supported by this feature... Gosh, I and many others, would love to use to be able to set FAST_REFRESH=true.
Will you please patch / expand support? Please :)

For me, when i have nothing on .env or FAST_REFRESH=true, i will get the fast refreshes for components change, but other files changes will not reload the page, despite my console showing that it recompiled.

Thank you! Creating a .env file and adding FAST_REFRESH=false to my project root fixed my issue of hot-reloading not working on Windows 10

Same here, on Ubuntu 20.04

I added FAST_REFRESH=false in my .env file and it worked like a charm
Tested on macOS Big Sur 11.2.3

I added FAST_REFRESH=false in my .env file and it worked like a charm
Tested on macOS Big Sur 11.2.3

Disabling fast refresh through the environment variable worked with Yarn however what "fixed" it for me completely was me switching to using NPM. Now I can use fast refresh again without any hacks.

FAST_REFRESH=false is working on BigSure 11.2.2, React ^17.0.1

In my case it works in Safari, but not in Chrome, Im using FAST_REFRESH=false

In my case it works in Safari, but not in Chrome, Im using FAST_REFRESH=false

It seems that the issue is in Chrome, closing and opening the browser fixes the issue.

Create the .env file with FAST_REFRESH=false is no use since the whole page is reloaded even clearing the current state.
Using FAST_REFRESH=true in the .env is not working either. Only style changes are reloaded, not even texts reload.
This "incompatibility issue" seems like a huge step backwards compared to the old approach using hot reload...

In my case, FAST_REFRESH=false did not solve the problem.
Reloading worked for tsx and css files imported in index.tsx, so if you export default the file I created (e.g. List.tsx) and import it in index.tsx, it will now reload.

FAST_REFRESH=false Is a hack. Please give the working configuration for all main platforms and browsers. cra v3 + rewired + customize-cra-react-refresh working like a charm - but it is necessary to have new major CRA.

Will do that ..

FAST_REFRESH=false Is a hack. Please, give the working configuration for
all main platforms and browsers without any additional envs to make this
work. CRA v3 + rewired + customize-cra-react-refresh working like a charm -
but it is necessary to have new major CRA.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/create-react-app/issues/9904#issuecomment-817211246,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AS3AD2CAMNQ6GEPWWYUJ2N3TIDHHTANCNFSM4S54YZJQ
.

For my system at least, this was down to a minor error of boolean logic in the CRA config.
This is what config/env.js looks like by default for v4 of CRA in Typescript:
// Whether or not react-refresh is enabled.
// react-refresh is not 100% stable at this time,
// which is why it's disabled by default.
// It is defined here so it is available in the webpackHotDevClient.
FAST_REFRESH: process.env.FAST_REFRESH !== 'false',

This can never result in FAST_REFRESH being set to false, for two reasons.
Boolean logic

If `FAST_REFRESH` is undefined, as it will be for most people here, then **config/env.js** will set it to true, even though the intention here is to set it to false by default. It's just a mistake of boolean logic.
Strings are truthy
If that error were not present, we would still not have FAST_REFRESH disabled by default. The default value is not being set to the boolean value of false, it is being set to the string 'false'. So if evaluated as a boolean, it will be interpreted as truthy, and give a true value.

This is why setting FAST_REFRESH=false in the dotfiles worked for so many people, wheras the disabled-by-default config didn't. They were setting entirely different values. I don't know why it didn't work for everyone, possibly a difference of dependency versions or OS.
Fix
The solution is to convert the environment variable to a boolean before trying to evaluate it as one, and then using a boolean for false instead of a string:
FAST_REFRESH: (!!process.env.FAST_REFRESH) !== false

Im getting the same problem.   Just wanted to let the devs know that they can add one more person to list.

Yeah, same for me. It's working if I add the FAST_REFRESH: false but would appreciate another fix.

Hi folks. I've solved this issue in my above comment, explained it in detail, and created a PR to fix it. That PR will go stale in 5 days. Not really sure what else to do from here if the maintainers aren't interested in solving the problem.

Hi folks. I've solved this issue in my above comment, explained it in detail, and created a PR to fix it. That PR will go stale in 5 days. Not really sure what else to do from here if the maintainers aren't interested in solving the problem. If the maintainers would be more interested in a PR from someone with a more masculine name I'd be happy to temporarily alter my profile to facilitate their comfort.

When will be the next release?)))

I can confirm hot-reloading still doesn't work on Ubuntu 20 LTS, on VirtualBox.
Still forced to keep fast refresh disabled, in order to do any kind of development.
Can someone from the @React team confirm if @phazel's patch passes tests and solves the issue?

Here's how I fixed fast refresh for my VM, running in VirtualBox.
In your .env, add:
CHOKIDAR_USEPOLLING=true

Greetings, a solution to the problem is given on the stackoverflow https://stackoverflow.com/questions/42189575/create-react-app-reload-not-working. Tested to Ubuntu 18.04.5 LTS, work

As suggested in https://stackoverflow.com/a/68257526/621659:

create .env file in your root folder of the project
and put there FAST_REFRESH=false ?!

I'm on Ubuntu 20.04.2 LTS and React 17.

Greetings, a solution to the problem is given on the stackoverflow https://stackoverflow.com/questions/42189575/create-react-app-reload-not-working. Tested to Ubuntu 18.04.5 LTS, work

As suggested in https://stackoverflow.com/a/68257526/621659:

create .env file in your root folder of the project
and put there FAST_REFRESH=false ?!

Worked for me on Ubuntu 20.04.2 LTS and React 17.

not the best one, the best one is simply install and it works =)

Any updates on this?

@RosenTomov hot reloading does not appear to be working from changes to the root index.js. At least that's what I'm seeing in my project and in the unaltered app created from create-react-app. But further down from index.js in a component, hot reloading does appear to be working.

That is the correct answer!!
Just  put the logic code elsewhere, index.js is only responsible for quoting.
Fast Refresh instead of Hot Reload
Use FAST_REFRESH=false, hot reload will become fast refresh.I think hot reload is better

If you want to disable, do the comment above, if you want it to work on VMs, do the solution that I wrote. Problem is resolved on my end

Just edit start script in scripts in package.json this and add this:
"start": "react-scripts start --watch"

The point is not that we're lacking solutions, but that it should work out of the box.

@RenanZX At first it worked, but after some time stop working. I solve this problem with FAST_REFRESH=false in .env temporary and looking for best solution.

I'm using WSL, you can create a .env file and just put
CHOKIDAR_USEPOLLING=true
Or in your package.json
....
scripts:{
"start": "CHOKIDAR_USEPOLLING=true react-scripts start",
....

THANK you. You mentioning wsl made me try and it works. I had this problem for 2 days now.
   "start": "CHOKIDAR_USEPOLLING=true react-scripts start",

This still doesn't work...  I'm using Docker Desktop for Windows, with WSL 2.  I have to rebuild the docker container to get it to update...  Refreshing the page doesn't even do it...

adding FAST_REFRESH=false to the .env file works for javascript but when doing changes on .module.scss files the app breaks. Throws this error.
VM16335:2 Uncaught ReferenceError: process is not defined
    at Object.4043 (<anonymous>:2:13168)
    at r (<anonymous>:2:306599)
    at Object.8048 (<anonymous>:2:9496)
    at r (<anonymous>:2:306599)
    at Object.8641 (<anonymous>:2:1379)
    at r (<anonymous>:2:306599)
    at <anonymous>:2:315627
    at <anonymous>:2:324225
    at <anonymous>:2:324229
    at HTMLIFrameElement.e.onload

I don't understand why is this issue closed. All the solutions on this thread are hacky and don't actually work.
FAST_FRESH=false in an.env file works for javascript files but not for .css files.
When  I change .css files there's an iframe covering the html and preventing any interaction with the page.

WITH CRA5 Fast refresh simply stopped working for me, fantastic. Where should I start looking into?

Same with me. Just migrated to Vite.js. Recommend the same.

Same with me. Just migrated to Vite.js. Recommend the same.

I certainly will give it a go, thanks.

Can confirmFAST_REFRESH=false only works on js file changes. When I try to change css file an iframe would just pop up freezing the screen...

almost 1.5 years awaiting for issue fix to upgrade from stable cra3 =)

CRA v5 fixed this issue

nope

Why is this closed ?
Still not working with CRA5 ?  w/ Ubuntu 20.04.3 LTS
Tried everything above.

OK solved by adding WDS_SOCKET_PORT=YOURBUILDPORT in package.json, scrips : { build: }
CRA advanced configuration
    "scripts": {
        "start": "WDS_SOCKET_PORT=3000 rimraf ./build && react-scripts start",
        "build": "WDS_SOCKET_PORT=9001 react-scripts --max_old_space_size=4096 build",
        "test": "cross-env CI=true react-scripts test --env=jsdom",
        "eject": "react-scripts eject",
        "lint": "eslint ./src/"
    },

OK solved by adding WDS_SOCKET_PORT=YOURBUILDPORT in package.json, scrips : { build: } CRA advanced configuration
    "scripts": {
        "start": "WDS_SOCKET_PORT=3000 rimraf ./build && react-scripts start",
        "build": "WDS_SOCKET_PORT=9001 react-scripts --max_old_space_size=4096 build",
        "test": "cross-env CI=true react-scripts test --env=jsdom",
        "eject": "react-scripts eject",
        "lint": "eslint ./src/"
    },

Why do you use it in build command ?

@mihanizm56 oops, forget to mention that I have also downgraded react-scripts to 3.4.4 to make it work.
I run it with a .NET Core backend project, but there's a temporary fix because the project was initially and somehow bootstraped  with the new CRA but an old (legacy 3.4.4) backend CRA configuration.
So the dotnet run need to be customised in my case. Didn't know about it yesterday.

@mihanizm56 oops, forget to mention that I have also downgraded react-scripts to 3.4.4 to make it work.
I run it with a .NET Core backend project, but there's a temporary fix because the project was initially and somehow bootstraped with the new CRA but an old (legacy 3.4.4) backend CRA configuration.
So the dotnet run need to be customised in my case. Didn't know about it yesterday.

Cra v3 works stable without WDS_SOCKET_PORT env in my projects

Yes sure, in my specific case it's just because the project was bootstraped with CRA 5 but the .NET Core build is still configured with CRA3, so I had to find a temporary workaround for now. (react-scripts 5 is still very new so it come with backwards incompatibilities I guess)

Had a same problem after upgrading to CRA 5.0.
Project uses .NET Core as backend and UseProxyToSpaDevelopmentServer as a poxy.
Project have a homepage setting in package.json: "homepage": "arm/" and .env file with WDS_SOCKET_PATH=arm/sockjs-node
After upgrading to CRA 5.0 WebSocket used for hot reloading could not be established, and after comparing with fresh new React project created with CRA 5.0 it figured out that a URL changed from /sockjs-node to /ws.
Fixing .env with WDS_SOCKET_PATH=ws fixed the issue with hot reloading.

If you're using ASP.NET Core's "UseReactDevelopmentServer()" function, you will find that CRA5's webpack hot reloader cannot connect to its websocket because it determines the wrong port on start-up. You can fix this by setting WDS_SOCKET_PORT to the value of ASPNETCORE_HTTPS_PORT in the start script in package.json, e.g.:
"scripts": {
    "start": "set WDS_SOCKET_PORT=%ASPNETCORE_HTTPS_PORT% && rimraf ./build && react-scripts start",
    "build": "react-scripts build",
    "test": "cross-env CI=true react-scripts test --env=jsdom",
    "eject": "react-scripts eject",
    "lint": "eslint ./src/"
}

This works on Windows, may require some tweaks to work on Linux.
The reason for this failure is that UseReactDevelopmentServer creates a proxy to the actual NodeJS instance that's hosting webpack's services, and loads your app via this proxy. Webpack does not know about the proxy so it injects the wrong websocket port into the scripts for your app. Luckily ASP.NET Core puts its HTTPS port in a convenient environment variable that gets inherited by the child NodeJS process that runs "npm run start".
If you don't use HTTPS in development this won't work for you, but you could probably set your own environment variable to the current HTTP port in Startup.cs before calling UseReactDevelopmentServer.

I am not sure everyone is having the same problem.
For me, when i have nothing on .env or FAST_REFRESH=true, i will get the fast refreshes for components change, but other files changes will not reload the page, despite my console showing that it recompiled.
When i have FAST_FRESH=false, everything is hot-reloading and everything works.

Worked! With React 17.0.1 and react-scripts 4.0.0 and with FAST_REFRESH=true (default) changes to components are reflected seemlessly, but changes to other dependencies are not reflected in the UI at all without manual refresh, despite obvious recompilation in the console. Setting the flag to false in .env didn't change anything but when I updated to react-scripts 4.0.1 setting FAST_REFRESH=false in .env brought back the hot reload.

It worked for me but after uninstalling react-hot-reload :(

For anyone that have React sits on a remote dev server, I have a pull request here which you could modify the react-scripts package if you'd like to.
https://github.com/facebook/create-react-app/pull/12091

@demedos Yes I have. I am on windows, maybe that's why.

For anyone that have React sits on a remote dev server, I have a pull request here which you could modify the react-scripts package if you'd like to. #12091

To anyone working with Vagrant...
Just setup a new React app and this was the only way I managed to get webpack to capture changes and recompile.
"CHOKIDAR_USEPOLLING=true" did not work for me or any other suggestions.
I merged the changes submitted by @hoangle4 in #12091 and then created a .env file with the following option:
WDS_POLLING=true
My setup:
ubuntu/focal64 Vagrant box with VirtualBox
  "dependencies": {
    "@testing-library/jest-dom": "^5.16.2",
    "@testing-library/react": "^12.1.3",
    "@testing-library/user-event": "^13.5.0",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "react-scripts": "5.0.0",
    "web-vitals": "^2.1.4"
  },

Nothing mentioned above worked for me
I use WSL2 (Ubuntu) with Windows 10.
using Remote WSL extension to run VSCode.
I have created symlink to my project location to map it under $HOME path of WSL.
So that i can open the folder directly in VSCode as wsl path (Optional)
$HOME/app <= /mnt/e/workspace/app

But I have a strange solution which is working, But not effective solution.
I have to make changes to my application code, then I need to simply comment some lines in package.json
and uncomment the change.
In browser we see error, when we comment.
when we uncomment the error goes, and when we refresh the page it reloads with the changes made in actual code.
Really strange solution!!  🙄
Dependency I use
 "dependencies": {
    "@testing-library/jest-dom": "^5.16.2",
    "@testing-library/react": "^12.1.3",
    "@testing-library/user-event": "^13.5.0",
    "bootstrap": "^5.1.3",
    "fontawesome": "^5.6.3",
    "react": "^17.0.2",
    "react-bootstrap": "^2.2.1",
    "react-dom": "^17.0.2",
    "react-scripts": "^5.0.0",
    "web-vitals": "^2.1.4"
  },

When commented:

When Uncommented:

balamt

Really strange solution!! roll_eyes Dependency I use

how funny!

How has this not been fixed?  I wasted 3 days thinking this was an issue of another UI package that used this as a dependency?

npm run start -FAST_REFRESH=true

I am also having this issue of an iframe covering the page after making css changes

I face this issue with react app structured from scratch with webpack. So I have to mention below code snippest in the index.js file.
if (module.hot) {   module.hot.accept(); }
Additional info about my setup,

My start command is webpack-dev-server no additional arguments.
I used HotModuleReplacementPlugin in webpack config.
Set hotOnly:true in devServer block.

module.hot.accept() is work for me.

I face this issue with react app structured from scratch with webpack. So I have to mention below code snippest in the index.js file. if (module.hot) { module.hot.accept(); } Additional info about my setup,

My start command is webpack-dev-server no additional arguments.
I used HotModuleReplacementPlugin in webpack config.
Set hotOnly:true in devServer block.

module.hot.accept() is work for me.

I face this issue with react app structured from scratch with webpack. So I have to mention below code snippest in the index.js file. if (module.hot) { module.hot.accept(); } Additional info about my setup,

My start command is webpack-dev-server no additional arguments.
I used HotModuleReplacementPlugin in webpack config.
Set hotOnly:true in devServer block.

module.hot.accept() is work for me.

I was troubled by this issue but after I disabled why-did-you-render, hot reload has begun to work again.
My environment: React 18 & CRA5
If you have some npm dependencies which patches/modifies/replaces original React code, try to disable them and see the result.

still facing trouble even after adding .env with FAST_REFRESH=false in it.
please update on a solution

I have the similar issue in node.js v18.
After some search, discovered it is because I am running node.js with docker in WSL. Hot reloading issues can arise due to how WSL handles file system events.
The issued is solved after I add the two environment variables:

WATCHPACK_POLLING=true
CHOKIDAR_USEPOLLING=true

The final docker script  looks like below:
docker run -it \
    -v "$(pwd)":/app \
    -w /app \
    --network=host \
    -e WATCHPACK_POLLING=true \
    -e CHOKIDAR_USEPOLLING=true \
    node:18 /bin/bash


remove unused import

Removes the unused imports of serial_print/ln from heap allocation example code

Thanks!

Thanks!


[HW] Gaurav Khapli

Name: Gaurav Khapli
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/gaurav-khapli/
Attach the homework step I screenshots below:

Attach the homework step II screenshots below:
-----------------------------------------

Hey Gaurav Khapli, great job! Congrats! Here is your badge! https://api.badgr.io/public/assertions/nNB70IspSRSNKItdHJ_Zhw


Call super during test setup

As mentioned over on https://github.com/alexreisner/geocoder/pull/1582, there appears to be some test leakage in this project. One instance of this I found was this test file relying on some setup from another test file. You can see this like so:
$ ruby -I test test/unit/lookups/maxmind_geoip2_test.rb
Loaded suite test/unit/lookups/maxmind_geoip2_test
Started
E
================================================================================
Error: test_dynamic_localization(MaxmindGeoip2Test): Geocoder::ConfigurationError: When using MaxMind GeoIP2 you must specify a service and credentials: Geocoder.configure(maxmind_geoip2: {service: ..., basic_auth: {user: ..., password: ...}}), where service is one of: [:country, :city, :insights]
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:34:in `configured_service!'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:18:in `query_url'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:24:in `cache_key'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:245:in `fetch_raw_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:196:in `fetch_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:59:in `results'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:46:in `search'
/Users/jon/code/geocoder/lib/geocoder/query.rb:11:in `execute'
/Users/jon/code/geocoder/lib/geocoder.rb:22:in `search'
test/unit/lookups/maxmind_geoip2_test.rb:34:in `test_dynamic_localization'
     31:   end
     32:
     33:   def test_dynamic_localization
  => 34:     result = Geocoder.search('<IP_ADDRESS>').first
     35:
     36:     result.language = :ru
     37:
================================================================================
E
================================================================================
Error: test_dynamic_localization_fallback(MaxmindGeoip2Test): Geocoder::ConfigurationError: When using MaxMind GeoIP2 you must specify a service and credentials: Geocoder.configure(maxmind_geoip2: {service: ..., basic_auth: {user: ..., password: ...}}), where service is one of: [:country, :city, :insights]
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:34:in `configured_service!'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:18:in `query_url'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:24:in `cache_key'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:245:in `fetch_raw_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:196:in `fetch_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:59:in `results'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:46:in `search'
/Users/jon/code/geocoder/lib/geocoder/query.rb:11:in `execute'
/Users/jon/code/geocoder/lib/geocoder.rb:22:in `search'
test/unit/lookups/maxmind_geoip2_test.rb:44:in `test_dynamic_localization_fallback'
     41:   end
     42:
     43:   def test_dynamic_localization_fallback
  => 44:     result = Geocoder.search('<IP_ADDRESS>').first
     45:
     46:     result.language = :unsupported_language
     47:
================================================================================
..E
================================================================================
Error: test_result_attributes(MaxmindGeoip2Test): Geocoder::ConfigurationError: When using MaxMind GeoIP2 you must specify a service and credentials: Geocoder.configure(maxmind_geoip2: {service: ..., basic_auth: {user: ..., password: ...}}), where service is one of: [:country, :city, :insights]
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:34:in `configured_service!'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:18:in `query_url'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:24:in `cache_key'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:245:in `fetch_raw_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:196:in `fetch_data'
/Users/jon/code/geocoder/lib/geocoder/lookups/maxmind_geoip2.rb:59:in `results'
/Users/jon/code/geocoder/lib/geocoder/lookups/base.rb:46:in `search'
/Users/jon/code/geocoder/lib/geocoder/query.rb:11:in `execute'
/Users/jon/code/geocoder/lib/geocoder.rb:22:in `search'
test/unit/lookups/maxmind_geoip2_test.rb:10:in `test_result_attributes'
      7:   end
      8:
      9:   def test_result_attributes
  => 10:     result = Geocoder.search('<IP_ADDRESS>').first
     11:     assert_equal 'Los Angeles, CA 90001, United States', result.address
     12:     assert_equal 'Los Angeles', result.city
     13:     assert_equal 'CA', result.state_code
================================================================================

Finished in 0.010555 seconds.
--------------------------------------------------------------------------------
5 tests, 2 assertions, 0 failures, 3 errors, 0 pendings, 0 omissions, 0 notifications
40% passed
--------------------------------------------------------------------------------

I tracked down the leakage to this file:
https://github.com/alexreisner/geocoder/blob/master/test/unit/lookup_test.rb
If that test is run prior to the maxmind_geoip2 then it passes, if not it fails. So then I realized it was a missing call to super in the setup method and added that with this PR. I think this gets us on the path to fixing the test leakage but it's far from the end. Still, why not chip away at it, right?

Thanks for this. Calling super does fix the issue but I'm looking at what super does and noticing some Maxmind-specific code in the parent test case. I think it would be better to move that code to the lookup-specific test cases where it belongs.

@alexreisner good thought! I just took a stab at moving the setup code from the general case to the specific one but it didn't work. I think it's because there's the test/unit/result_test.rb and test/unit/lookup_test.rb files that ALSO end up calling into that same code path. Maybe that's why this ended up in the test_helper.rb file? Anyway, I'm open to other suggestions but it seems like there's some stubborn shared config here. 🤷

This was addressed more globally by b05c967569105dcbaa129b143d03dd283f132b30.

(However I'd still love to move the maxmind-specific config out of the parent setup method.)

Love it thanks for the fix!! 😍


Draw new functionality

https://github.com/eklem/nowcontent.xyz/issues/32
--> Just listing out endpoints added
This will give easy CRUD functionality and indexedDB will be master.
Should show small buttons to drag to the bookmark toolbar.

The new drawings are here: https://github.com/eklem/nowcontent.xyz:

[x] Add new endpoint / bookmarklet
[x] List out existing ones
[x] Ability to edit / delete
[x] Button-ish for drag and drop


CallBack accidentally calling twice

The callback in the event calls more than twice causing double credit on the system

I am having the same issue. @FireSwitchTech were you able to solve it?


Rebuild, upgrade

Lots of changes needed here.
Conda briefly was able to handle the ATNF FTP server, but has gone back to being unable to interact with it. Sigghhhhhhh.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


[Bug]: Expo SDK 49

Version
v1.2.3
Which operating systems have you used?

[X] Android
[ ] iOS

Environment that reproduces the issue
Any expo build for android.
Is it reproducible in the example application?
No
RTMP Server
<IP_ADDRESS>:1935
Reproduction steps
Reproduction: https://github.com/BlueBazze/expo-49-livestream-build-error/tree/master
Trying to build the reproduction throws the error mentioned in the Relevant logs output.
Building the reproduction is descriped in the reproductions' README
Expected result
Build succeeds
Actual result
Build throws the error mentioned in relevant logs output.
Additional context
Trying to use this package with Expo SDK 49 throws the error.
SDK 49 runs on React Native version 0.72.3
Haven't tested iOS
Found this related issue on another RN package: https://github.com/margelo/react-native-quick-crypto/issues/186
At the moment of writing this i would consider this low priority.
Google's latest requirement is android target api 33 which takes effect in 9 days relative to the creation of this github issue.
Expo SDK 48 is supported until SDK 50 is released. And SDK 48 is android targeting api 33
Relevant logs output
[stderr]
FAILURE: Build failed with an exception.

[stderr]
* What went wrong:

[stderr]
Execution failed for task ':app:mergeDebugNativeLibs'.

[stderr]
> A failure occurred while executing com.android.build.gradle.internal.tasks.MergeNativeLibsTask$MergeNativeLibsTaskWorkAction

[stderr]
   > 2 files found with path 'lib/arm64-v8a/libcrypto.so' from inputs:

[stderr]
      - /home/expo/.gradle/caches/transforms-3/96aa0437b2be82ab10ada7819631979e/transformed/jetified-flipper-0.182.0/jni/arm64-v8a/libcrypto.so

[stderr]
- /home/expo/.gradle/caches/transforms-3/4f404765331db8d43fd810e44289770b/transformed/jetified-rtmpdroid-1.0.5/jni/arm64-v8a/libcrypto.so

[stderr]
     If you are using jniLibs and CMake IMPORTED targets, see

[stderr]
     https://developer.android.com/r/tools/jniLibs-vs-imported-targets

Hi,
Thank for reporting this issue.
This is something we are aware of but the solution is not easy.
I started to upgrade the project with new architecture and new RN version in https://github.com/apivideo/api.video-reactnative-live-stream/pull/67
But I am kind of stuck for now.

Is there an update? We tried to get everything working but unfortunately it's not working. :-( Do you know if downgrading to expo 38 will help?

@b4rtt Downgrading to 38 will yeet you into 2019.
This library works with SDK 48. I am using this version.
Unfortunately this project needs to support fabric to be used in SDK 49 or higher.

having the same issue, any updates?

Thanks @BlueBazze for the answer.
As long as Fabric does not support swift and openssl 3, there won't unfortunately be anything released.

@ThibaultBee do we have any luck yet? is there any alternative or workaround right now that is as good as this?

@BlueBazze
I have fixed this issue in https://github.com/apivideo/api.video-reactnative-live-stream/pull/67

Cool. What did you end up doing about OpenSSL?

I made a single large shared library librtmpdroid.so that embed libssl.so and libcrypto.so instead of having multiple shared libraries.
The counterpart is that the RN library will embed twice libssl.so and libcrypto.so, so the application will be larger.

Noticed you mentioned some annoyances with iOS in https://github.com/apivideo/api.video-reactnative-live-stream/pull/67. I have a few days available next week if you want any help.

Cool, I would appreciate if you could help on the iOS new arch. 🙏

@ThibaultBee I've played around with it.
Havent been able to get the project started.
Keep getting The Swift pod react-native-livestreamdepends uponglog, which does not define modules.
Tomorrow i will try to initiate a new demo project and try get the bridge to work.
Hopefully it can work. Cause Haishinkit has some strong opinions about objc.
Btw, i found this package that uses swift and seems to have a working bridge. https://github.com/mateusz1913/react-native-avoid-softinput/blob/main/packages/react-native-avoid-softinput/ReactNativeAvoidSoftinput.podspec

oh, thanks. I had a look on the project, there might a start of a solution
Unfortunately, on my side, it seems that RCT_NEW_ARCH_ENABLED is never defined when I try to build for the new arch even when I use RCT_NEW_ARCH_ENABLED=1 bundle exec pod install
🤷
This new architecture is really a pain to implement :(

The dev is done. I will tackle a last issue with the Android preview.
But... the release is not ready yet. We are expecting feedbacks/tests from the community before releasing. See https://github.com/apivideo/api.video-reactnative-live-stream/pull/67

The dev is done. I will tackle a last issue with the Android preview.
But... the release is not ready yet. We are expecting feedbacks/tests from the community before releasing. See #67

I've set a few days within the next 10 days for testing, hopefully before this friday.
I imagine that ill create a demo expo app that you can have afterwards if you want it.
Since this issue was created Expo has been updated to SDK 50 being the latest at the moment.
SDK 50 has updated to React Native 0.73 and support for older versions than SDK 49 has been dropped.

Hi,
Is it solved with release 2.0.0?

Theoretically yes. I built the expo demo just fine in the other issue. But haven't ran any builds after the release with fabric

Ok. Thanks for the answer.
We are closing it for now. Please reopen if it is not fixed.


Change debug messages in verbose to use log crate

Use log crate for debug messages, so we can add timestamps.
Also use log crate for standard messages (i.e. those filtered in quiet mode).

Easy enough to do. This is a binary, so you'll need a log outputter as well. Common options are env_logger, pretty_env_logger, fern, log4s, and others. Any preference?

I've used pretty_env_logger before but I'm happy with any of them really.

Works great thanks! :slightly_smiling_face:


Keep the same "shadow" environment between runs

Currently, we generate a randomly-named Conda environment every time we call .save(). It would be good to keep a single one and re-use it between runs.

Change flow so we don't create temporary conda env


Table with ellipsis + lineClamp is not vertically centered

Describe the bug
when using the table column with ellipsis config with a tooltip and lineClamp, the text is not vertically centered in the td.
with lineClamp:

without lineClamp:

Steps to reproduce

use ellipsis with lineClamp config:

      ellipsis: {
        tooltip: true,
        lineClamp: 4
      },

the text is not aligned

Link to minimal reproduction
https://codesandbox.io/s/gifted-lena-k53rqr?file=/src/Demo.vue
System Info
System:
    OS: macOS 14.4.1
    CPU: (8) arm64 Apple M2
    Memory: 73.92 MB / 24.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.2.0 - /opt/homebrew/bin/node
    Yarn: 4.0.2 - /opt/homebrew/bin/yarn
    npm: 10.2.3 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 126.0.6478.127
    Edge: 126.0.2592.87
    Safari: 17.4.1
  npmPackages:
    naive-ui: ^2.38.2 => 2.38.2
    vue: ^3.4.21 => 3.4.21

Used Package Manager
yarn
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.

Use this style to solve the problem:
.n-ellipsis {
    overflow: hidden;
    vertical-align: middle;
}

@Nakus0426 thank you :)

This issue does not have any recent activity. If you are still experiencing similar problems, open a new error, including a minimal copy of the problem


Try to clone again and commit. Did it work ?

Looks like everything is ok. I'll merge it now. It should be public in about 8 minutes


Has anyone successfully compiled this on ARM Linux (aarch64)?

I want to use this on a newer AWS Graviton server but anything I've done to try to get it to compile from sources has completely hung the process until I abort. No error output. I'm used to longer compile times and don't believe this is the issue. CPU usage hovers around 1% so it's not doing anything. Not even sure how to go about debugging it.

Actually, just noticed this PR.
https://github.com/Dao-AILab/flash-attention/pull/757
Seems like exactly what I'm looking for. Hopefully the PR can be approved.

Does either #757 or #724 work for you?

Does either #757 or #724 work for you?

757 did end up working for me.


Changing splash page display name

See Issue #21

@danderson00 @lindydonna - If this looks good can you merge it?

Looks fine. Merged!


vSphere cloud provider code restructuring

Issue: https://github.com/vmware/kubernetes/issues/134
At present https://github.com/kubernetes/kubernetes/blob/master/pkg/cloudprovider/providers/vsphere/vsphere.go is huge. It has 1800+ lines of code dumped into single file, and as we add new feature, file size is increasing. It's already difficult to manage and debug code. Plan is to make the code modular and unit testable.
This PR is segregating vSphere cloud provider code into distinguishable vSphere Objects, such as VSphereConnection, DataCenter, DataStore and VirtualMachine.
These objects inherits and extends govmomi objects, which allows govmomi functions readily available in cloud provider code, without requiring to re-create objects.
Code change for Integration with cloud provider will be sent in separate PR, after all functions are thoroughly unit tested.
@BaluDontu  @SandeepPissay @luomiao @tusharnt @pdhamdhere

Me and @divyenpatel had a 1 hr meeting to go through the code and provided many of my review comments during that meetings which @divyenpatel had already noted down.
We are planning to have multiple meetings before we can sign off this entirely.

@BaluDontu Addressed review comments.

@rohitjogvmw, can you help review this PR?


Add Namespace to message, add .dockerignore

This PR adds the Namespace to which the event belongs into the Slack message.  I also added a .dockerignore file so that the examples and images directories are not included in the docker image.

Cherry picked the commit associated with the namespace addition and the .dockerignore file. Thanks!


Move visualizer uniform block to a different set

Texture/Sampler uniforms are expected to be in their own uniform sets, separate from uniform blocks.
Related papertrail: https://discord.com/channels/188630481301012481/589331078574112768/1115308889794158643

Yes, they do (or should anyways). The only other shader that uses both texture/sample uniforms and uniform blocks is this one:
https://github.com/taulazer/tau/blob/master/osu.Game.Rulesets.Tau/Resources/Shaders/sh_Slider.fs#L11-L20C61, which already did things correctly.


Refine flexible support for owners_after

Current coverage is 100% (diff: 100%)

Merging #168 into master will not change coverage

@@           master   #168   diff @@
====================================
  Files           9      9
  Lines         191    200     +9
  Methods         0      0
  Messages        0      0
  Branches        0      0
====================================
+ Hits          191    200     +9
  Misses          0      0
  Partials        0      0

Powered by Codecov. Last update 6dfc602...4ccee5b


fix connect basic auth

This change fixes https://github.com/tchiotludo/kafkahq/issues/119

Thanks for PR !
To be honest, I don't have a Kafka connect with basic auth, but it seems to be the right way !

Thanks for the merge ! It works fine on our dev cluster


Drag and Drop from outside is not working when distributeEvenly prop is set.

When a user drags and drops a GridItem from outside and the distributeEvenly prop is set, the new item is not added to the GridLayout.

Issue fixed in version 1.2.3


Cannot type types.Tuple

@njit
def test():
    x = Tuple((int64, int64))

That crashes saying it's unable to type Tuple. The main motivation for wanting it to work is to make a typed.Dict that has tuples for the key type. At the moment my hack is to make the dictionary and then to pass it to a function that is njit.

Thanks for the report. The direct use of non-scalar Numba types in JIT functions is unsupported, there is however a work around (define the key type outside the function scope):

In [42]: from numba.types import Tuple, int64, float64

In [43]: from numba import njit

In [44]: from numba.typed import Dict

In [45]: key_ty = Tuple((int64, int64))

In [46]: key_ty
Out[46]: tuple(int64 x 2)

In [47]: @njit
    ...: def foo():
    ...:     d = Dict.empty(key_ty, float64)
    ...:     d[(5, 10)] = 12.34
    ...:     return d
    ...:

In [48]: foo()
Out[48]: DictType[tuple(int64 x 2),float64]({(5, 10): 12.34})

type inference should also be able to just work it out in some cases, for example:
In [49]: @njit
    ...: def bar():
    ...:     d = {}
    ...:     d[(5, 10)] = 12.34
    ...:     return d
    ...:
    ...:

In [50]: bar()
Out[50]: DictType[tuple(int64 x 2),float64]({(5, 10): 12.34})

Closing this as it seems like the original question is answered and no further response has been received. If there are further discussions to have or questions to resolve, the Discourse group https://numba.discourse.group would be a good place to post them.


Choices js max 5 limit

Hi, I'm using you theme in my project.
The issue I'm having is that when using a choices js component, I'm unable to select more than 5 items.
I checked choices.js file and couldn't find any setting that limits to 5 items...
How can I configure it to allow more than 5?
Its supposed to be unlimited by default right?
Also, is it possible to allow items that are not already there in the pre defined list??
Thanks

It should be the issue of Choices.js, not this template instead. Check out Choices.js repository (https://github.com/Choices-js/)

Hi Zuramai, I did that already.. And then came here... I checked the documentation for choices js and according to that, the property "max_allowed_items" is set to -1 by default, which means unlimited, and even in the choices.js supplied with the theme, I checked the DEFAULT_CONFIG object, the property max_allowed_items is set to -1.
Considering that you chose choices.js for your project, I assumed that you must have had experience with it, hence I asked you.

I think there's no configuration in it.
Because max_allowed_items is how many items you can put in the select, not how many items you can select.
In the mazer example, I can do select more than 5 items. Is this what you referring to?

Hi @zuramai
Thank you for the response, sry my system was at my workplace during the weekend, hence couldn't reply.
I'm sry I forgot to mention that I was referring to Multiple Select with Remove Button component

this is from your demo link :  https://zuramai.github.io/mazer/demo/form-element-select.html

I'm sorry, it was my bad. Now you can edit the maxItemCount in dist/assets/js/pages/form-element-select.js.
Check it out the demo link now https://zuramai.github.io/mazer/demo/form-element-select.html

Hey @zuramai ... Thank you for the quick fix... :)
BTW, any idea on allowing dynamic items by user input?
I know it's a choices.js thing...
But asking you since you have experience with the library...and in hopes of saving myself some efforts.... 😬😬

Check this out https://github.com/Choices-js/Choices#setchoiceschoices-value-label-replacechoices

@zuramai ... Thank you, with a bit of JS trickery, this might just work!! 😀😀


step StepLinkable

hi, how I make the step is linkable please ?
thanks

protected $allowDynamicStepNavigation = true;  thanks


addrindexrs_1        | WARN - failed to connect daemon at <IP_ADDRESS>:8332: Connection refused (os error 111)

Describe the Problem
while starting bitcoin node, addrs indexer cant connect
addrindexrs_1        | WARN - failed to connect daemon at <IP_ADDRESS>:8332: Connection refused (os error 111)
after a certain time the bitcoin node synchronization is terminated and prints this on the screen.
addrindexrs_1        | WARN - failed to connect daemon at <IP_ADDRESS>:8332: Connection refused (os error 111) addrindexrs_1        | WARN - failed to connect daemon at <IP_ADDRESS>:8332: Connection refused (os error 111) counterparty-core_1  | [2024-03-20 09:01:57][INFO] AddrIndexRs connecting...
Steps To Reproduce
Steps to reproduce the behavior:

docker-compose -f simplenode/compose.yml up

Screenshots and Logfiles

AMD EPYC 7401P | NIC 1 Gbit- Intel I350
2x SSD SATA 256 GB |
2x SSD SATA 1,92 TB Datacenter |
4x RAM 32768 MB DDR4 ECC reg.

Os: Ubuntu 22.04.2 LTS base

shoud be fixed on the branch develop with https://github.com/CounterpartyXCP/counterparty-core/commit/23a99bcee9372365c1a31d672b4a0b3d6b993a6d

need also https://github.com/CounterpartyXCP/addrindexrs/pull/20


Implement Dynamic Reset of Quest App

IMPORTANT: Where possible all PRs must be linked to a Github issue
Fixes #1571
Checklist

[ ] I have written Unit tests for any new feature(s) and edge cases for bug fixes
[ ] I have added any strings visible on UI components to the strings.xml file
[ ] I have updated the  CHANGELOG.md file for any notable changes to the codebase
[ ] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the project's style guide
[ ] I have built and run the fhircore app to verify my change fixes the issue and/or does not break the app

Tested this out. LGTM based on the convo we have on once reset, go to config page and sync configs/data afresh

Merging dependent on PRs

Geo widget PR https://github.com/opensrp/fhircore/pull/1548
Profile menu config PR https://github.com/opensrp/fhircore/pull/1562

To close this , lets add a config to make this visible only in development mode and should not be visible in production to avoid accidental purge of production data


Unable to click the 41 element in a list

Hi,
I have a list of 100 items and the require is to click on on each of the element. WinAPP driver succeeds to clicking till 40th element, but from 41st it says unable to find the element after that,
Is anyone alse also facing the same problem?

Hi Can you please check whether inspect shows value for properties detailed at this link #570 (comment)
It could be that all 100 checkboxes have same runtimeId. In that case WinAppDriver can have issue identifying check boxes.
Also, you might want to save out the page source for the page having check boxes. I have observed that for a page having lots of UI controls, the page source is often incomplete which results in behavior like what you have mentioned. Please confirm this.

Hi Ketan,
Thanks you for the details.
I just checked the control using insepct.exe tool, and observed that 'ControlType:' is set to 'UIA_CheckBoxControlTypeId()xC352)' and 'RuntimeId:' is set to a unique value [2A:101DD04.IE2] and it is not changing in same session. Also observed that every checkbox has unique RuntimeId.
Also there are not too many controls on the GUI.  We have around 14 - 15 control which includes Labels, text entry, date picker, check box and dropdowns.
Thanks & regards,
Srinivas

@srinivaspantla
Is there a scroll action just before the 41st item is clicked? Just guessing if the scrolling could somehow cause the "unable to find the element". You probably already tried some small sleep between scroll and click to see if this would be the problem?

Hi Ketan,
Sorry for the confusion. I think I responded in wrong chain. Please ignore. I have moved my response to https://github.com/Microsoft/WinAppDriver/issues/586.
Thank you.
Srinivas


turn on k8s feature we added to transfer proxy settings from master t…

…o agents
@openshift/sig-developer-experience fyi / ptal
Another Boehringer action item.  This turns on the new bit I added to the k8s plugin that allows any proxy/no_proxy related env vars on the master to be set on any agent launched.
Reminder, if you look high enough up generate_kubernetes_config() you'll see the has_service_account check.  This ensures that this image is running as an openshift pod, which is when we would like to have this behavior enabled.  But if the user is running the image outside a pod, we leave the default behavior.

/lgtm


updated the HTML and CSS file and added a new HTML file

kindly describe, the thing you are adding


Optimize available quantity loader.

I want to merge this change because optimizing AvailableQuantityByProductVariantIdCountryCodeAndChannelSlugLoader.

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-4020 Long-running queries by dataloader AvailableQuantityByProductVariantIdCountryCodeAndChannelSlugLoader


Bevy not compiling because of issues with ALSA and CPAL

Bevy version
I also tried using version 0.8.1 but the same error came up.
[package]
name = "my_bevy_game"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
bevy = { version = "0.8.0", features = ["dynamic"] }

[profile.dev]
opt-level = 1

[profile.dev.package."*"]
opt-level = 3

[Optional] Relevant system information
cargo/rust version:
cargo 1.64.0 (387270bc7 2022-09-16)
operating system:
EndeavourOS Linux x86_64
kernel:
6.0.1-zen2-1-zen
What you did
Hi, I'm trying to compile the sample app in the documentation.
I also used the recommended linker LLD and created a .cargo/config file in my project directory
[target.x86_64-unknown-linux-gnu]
rustflags = [
    "-C", "link-arg=-fuse-ld=lld",
]

I'm pretty sure this is not an issue with the linker because this problem also comes up when I switch to mold or use the default linker.
What went wrong
When I do cargo run it seems to be working fine until the following comes up error.txt
At first I thought that this was an issue with dependencies so I installed the following
sudo pacman -S libx11 pkgconf alsa-lib pipewire-alsa pulseaudio-alsa vulkan-intel
But the error keeps coming up. I tried removing the target directory but the same error came up.
I'm not sure what's going on.

This is due to a non-semver-compliant breaking change in the upstream ALSA dependency: see https://github.com/diwic/alsa-rs/issues/90.

I was able to work around this by adding alsa = "=0.6.0" to my dependencies. Note the = before the version.

I was able to work around this by adding alsa = "=0.6.0" to my dependencies. Note the = before the version.

Thanks! It's working now, when do you suspect this issue will be fixed?

when do you suspect this issue will be fixed?

I suspect when the authors of alsa-rs yanks 0.6.1 and published a new 0.7.0 version instead. In the meanwhile, I think this shouldn't be closed until diwic/alsa-rs#90 is closed.


I need help

latest.log
I tried to start a world with this mod, even after many attempts, the game still crashes

Looks like an issue with Tamango, a version of zenith on the new porting lib is coming and tamango won't be necessary anymore