Rework --organize command

[x] I am using the latest version of PyInstaLive: 3.2.0.
[x] I have installed either Python 2.7.x or 3.5+: 3.8
[x] I have read the README.
[x] I have read the FAQ.
[x] I have checked all existing issues, none of which could solve my issue.

I am using:

[x] Windows 10
[ ] Windows 8.1
[ ] Windows 8
[ ] Windows 7
[ ] Linux (distribution: )
[ ] macOS (version: )
[ ] Other (device & OS name: )

Required files
PyInstaLive information
$ pyinstalive --info
---------------------------------------------------------------------------
[I] PYINSTALIVE (SCRIPT V3.2.0 - PYTHON V3.8.0) - 04-19-2020 09:21:08 PM
---------------------------------------------------------------------------
[I] To see all the available arguments, use the -h argument.

[I] PyInstaLive version:        3.2.0
[I] Python version:             3.8.0
[I] FFmpeg framework:           Available
[I] Cookie files:               1 (*****.json matches config user)
[I] CLI supports color:         No
[I] Command to run at start:    None
[I] Command to run at finish:   None
[I] Config file contents:

    [pyinstalive]
    username = *****
    password = *****
    download_path = *****
    download_lives = True
    download_replays = True
    download_comments = True
    show_cookie_expiry = True
    log_to_file = True
    ffmpeg_path =
    run_at_start =
    run_at_finish =
    use_locks = True
    clear_temp_files = False
    do_heartbeat = True
    proxy =
    verbose = False
    skip_merge = False

[I] End of PyInstaLive information screen.
---------------------------------------------------------------------------

Command used
pyinstalive -o
Behavior
Video files were moved to named folders like mentioned in the MOREHELP.md, but comment log files were not. Besides the video files were renamed (this wasn't even mentioned in the help) but the comment log files were not, making it a bummer to still know which comment log files belong to which video.
Steps to reproduce issue
I simply ran the script with the above mentioned command in the download folder.
No further steps taken.

Question
Can please either both files (video and comments) be renamed and moved to the user-specific folders or - which I would prefer - the merged video files and comment logs get a timestamp exact to the second of the recording the live started and are then moved to the user folder?
Now the downloaded files only have the timestamp in Unix epoch time format, but after organizing them the timestamps are converted to Human date.

Working on rewriting it, apologies for the inconvenience. Organized files (logs and videos) will be moved to the user folder with for example the following format:
19-04-2020 18:02:10 uesaka_sumire (replay).mp4

I have pushed the changes, but don't have a lot of livestreams and replays right now to see how reliable it is. If you wish to try the latest code reinstall PyInstaLive without specifying a version tag.

Actually now it returns
---------------------------------------------------------------------------
[I] PYINSTALIVE (SCRIPT V3.2.0 - PYTHON V3.8.0) - 04-22-2020 12:09:58 AM
---------------------------------------------------------------------------
[E] Could not organize files: 'NoneType' object is not subscriptable

with pyinstalive -o.

The new release should be working for the most part, but if there were multiple streams on the same day and those were saved as replays then those won't be sorted yet since the epoch timestamp is currently taken from system at the time of saving instead of the replay broadcast date itself
Will be doing some more work on it when i have the time but there are likely a few kinks to be worked out still so don't use it yet if you don't feel like making a backup copy of the files first

Seems to work fine in further tests, feel free to reopen if you do encounter any more issues

In my opinion the parameter -o / —organize was not really reconsidered, because PyInstaLive does not use the date & time from the live stream, but the current information in which I enter pyinstalive -o.  Possibly PyInstaLive could look at the metadata of the video and generate the date & time from it.


Expand k8s-upstream-tests to validate KPR

The following test script runs the kubernetes upstream tests against Cilium:
https://github.com/cilium/cilium/blob/master/test/kubernetes-test.sh#L11
These tests can be initiated with a /test-upstream-k8s command as a comment against a PR. Currently this appears to rely on an existing kube-proxy deployment and runs Cilium on top. This allows us to validate whether there is a mode where Cilium satisfies the upstream conformance tests (with upstream kube-proxy), but we do not get feedback about the conformance status with Cilium without kube-proxy.
This issue tracks adding CI support for Cilium with KPR.

Thanks for the issue. Is it just KPR=on|off, or you want to test other Cilium configurations?

@brb A large chunk of the upstream k8s tests validate Service functionality, and our users use a mix of kube-proxy or kube-proxy replacement. The idea behind this request is to help to identify regressions in conformance over time as we make changes to either of these modes. So KPR=on|off is probably enough. I would also settle for periodic (1/day? 1/week?) runs for one of the combinations as long as we have people watching the results.


feat: project governance llm checks

[!IMPORTANT]
Adds project governance LLM checks to APIClient, integrates them into project-health CLI command, and updates DBTInsightGenerator to include these checks in reports.

Behavior:

Adds get_project_governance_llm_checks() and run_project_governance_llm_checks() to APIClient in client.py for governance checks.
Integrates LLM checks into project_health() in cli.py, displaying results in CLI.

CLI:

Adds --token, --instance-name, and --backend-url options to project-health command in cli.py.
Displays LLM check results with detailed insights in project-health command.

Utils:

Adds utility functions get_project_governance_llm_checks() and run_project_governance_llm_checks() in utils.py for API interaction.

Constants:

Adds LLM constant to constants.py for categorizing LLM insights.

Executor:

Updates DBTInsightGenerator in executor.py to run LLM checks and include results in reports.

This description was created by  for a499fee798ecec698b983fffef8c75638c312961. It will automatically update as commits are pushed.

@gaurpulkit Some tests are failing, Please have a look

@gaurpulkit : The checks are failing, can you PTAL?

Also is following scenario property handled:
The user has a config that has LLM checks but forgets to provide the api key and tenant?


Project's improvements part2

Fixes #3306
Fixes #3195
Fixes #3319
Fixes #3320
Fixes #3325
Fixes #3335
Fixes #3327
Partial Fixes #3331

@frjo we can put this on the test so that @abhiXII can test out the things. This PR contains some inline css code at a few places, I'll convert them into css classes after the testing.


Questions about the function calculate_phase_and_cyclic_error

Hi, excellent work! The program finishes the simulation of TOF camera wiggling error, but I have some questiones about the function(calculate_phase_and_cyclic_error). First of all, in this function, to compute the DFT in sampled_corr_signal, and then the phase angle (frequency domain) is calculated by DFT. Why choose one of the phase angles as simulated_phase?

Thank you for your comment and question. I suppose your question is related to L127 of ./functions/signal.py:
np.angle(fft_sampled_corr_signal)[1]
Here, the first element is selected because it corresponds to the first order harmonic.

emm..... ,Sorry I found it is difficult for me to understand(Perhaps It take up some of your time).Can you please give an email for communication (won't waste too much time，or my email "fengxiaowei@buaa.edu.cn").The main question is still about the L125 to L136(I tried to explain this logicallly, But I'm finding it harder and harder to explain.)
In the Setup Parameters section, you solved for the true phase at each distance, then solved for the cross-correlation function for the different phase delays, by extracting the four cross-correlations corresponding to each time sampling point, and then restoring the true phase. I was thinking about it myself last week, and I still don't understand something either: the true phase corresponds at each distance, but shouldn't the resulting simulated phase get 0 in the absence of phase delays due to distance? But the actual is a trigonometric function (that is, the problem with the actual result obtained, hmmm... . the ToF camera measures the distance by measuring the phase difference, but here the output at a certain phase is trigonometric)? There is also the question of the reduction method, I mainly refer to the article by Rapp [2007], but it's hard to find to explain it (probably based on a sine wave)

I'm really sorry to trouble you.

Can you please give an email for communication
I prefer having discussion here to communicating through my personal e-mail. I am sorry for any inconvenience, and thank you for your understanding.

the ToF camera measures the distance by measuring the phase difference, but here the output at a certain phase is trigonometric.
My apologies in advance if I incorrectly interpret your statement. One simulated phase value corresponds to one ground-truth depth or ground-truth phase. However, the simulated phase value is suffered from the wiggling error, which is also known as cyclic error. With this simulator, you can obtain multiple simulated phase values at different ground-truth phases from 0 to 2*pi. If you plot phase error (i.e., the difference between simulated phase and ground-truth phase) against ground-truth phase, you will see the wiggling error, which follows a cyclic pattern.

If the concept of the wiggling error is not clear to you, you can refer to the article by Chronoptics.

If there are no further questions, I will close this thread in a few days.

I appreciate the help you've provided, and based on previous chats have resolved the existing confusion. Thank you very much.

You are welcome.


Varying GraphQL Endpoint env var name doesn't work for deployments

Environment information
System:
  OS: macOS 13.6.6
  CPU: (10) arm64 Apple M1 Pro
  Memory: 167.00 MB / 16.00 GB
  Shell: /bin/zsh
Binaries:
  Node: 20.10.0 - /usr/local/bin/node
  Yarn: 1.22.22 - /usr/local/bin/yarn
  npm: 10.2.3 - /usr/local/bin/npm
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 0.13.0
  @aws-amplify/backend-cli: 0.12.0
  aws-amplify: 6.0.28
  aws-cdk: Not Found
  aws-cdk-lib: 2.138.0
  typescript: 5.4.5
AWS environment variables:
  AWS_STS_REGIONAL_ENDPOINTS = regional
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
No CDK environment variables

Description
When creating backend functions that require access to the GraphQL API, an ALLEGRO_DATA_API__GRAPHQL_ENDPOINT environment variable is created so that the function can include it inl Amplify.configure(...)
The problem is that when deploying this, the  is going to be different depending on the amplify identifier. This means that the code which is referencing the local  is not going to have the right  for the production deployment(or even other sandboxes). I am wondering if this can be a standard name instead, so we can simply reference it while having its value modified between branches/sandboxes. This way our Lambda code can always reference the same variable name to avoid this issue.

Turns out this is caused by setting the defineData name value to something that includes the sandbox identifier. Removing that fixed it and generates standard environment variable names. This does bring up the issue that the backend resource names for Gen-2 are not as clear as Gen-1 resources. I will open a separate issue for that.


Add examples demonstrating how to follow the player with a camera

What problem does this solve or what need does it fill?
Following a player with the camera is an essential task for a large fraction of games. However, there are several pitfalls for new game devs:

the obvious way to write the system to do this will lead to conflicting borrows on the Transform of Player and Camera
the camera should move via delta-time, to ensure approximate frame-rate independence
the camera should be eased towards the player, rather than simply using direct parenting to avoid jerk
the camera movement and player movement systems must be precisely ordered to avoid jitter

What solution would you like?
Add two examples that :

A simple top-down 2D camera controller with WASD player movement and a simple environment.
A first person camera with a simple fly cam player controller.

What alternative(s) have you considered?
We could ship first-party camera controllers. This is not as good of a solution, as these tend to need to be heavily modified by the end user.
It's better to teach the developer how to fish, and possibly link to other resources on designing good camera controllers.
Additional context
Once this is done, we can consider adding other camera controller examples in follow-up PRs: e.g. RTS-style cameras, or a third person over the shoulder camera.

I'm definitely interested by this! I will need some camera logic in my game and I'm currently using Dolly. Would be great to explore alternatives with the Bevy API. We could also add some user documentation/guide maybe ?

Assigned! Feel free to open up a draft PR early and ask for help :)

Thanks, I'll do that :)

A first person camera with a simple fly cam player controller.

Hi @alice-i-cecile , regarding this example do we want to just control the camera or create some kind of character with some behaviours and attach the camera to it?

I'd like to have a simple character with basic movement. The camera shouldn't be controlled directly by the player, only the character.

I think the previous example is enough to cover the needs of a first person camera - that's pretty much what I had in mind to attach the camera to the player. If it's ok we can close this issue as resolved. But if you need something else let me know 👍


JQuery One Page Issue

I seem to be having an issue. For some reason the JQuery isn't working. I know it's something to do with JQuery file, I just can't figure out what the problem is.

I only have it running on a local host. I can record a video and show you exactly whats going on.

Here is the live code. I think It's actually work, however the smooth effect isn't
http://codepen.io/anon/pen/wBqgBz

None of the JS files are linked up in the codepen.

Oh yeah that's true, sorry I just woke up.

@davist11 Now the JQuery files are included on Codepen.
http://codepen.io/anon/pen/wBqgBz

Looks like it's working to me.

@davist11 I got it working. I was missing the JQuery.nav.js file.


Automatically generated CHANGELOG looks weird

Only contains a list of changes in 0.1.1 but listed mutiple times

Oh yeah; that's a known bug changelog. We should probably stop using it. Thanks for raising!

done!


S3 - is-log-target

What does the 'is-log-target' use to identify S3 buckets that are used for logging?
Just trying to verify that the policy is working correctly in terms of the results it returns.

its primarily elb, cloudtrail, and s3 at the moment. It looks like we should extend this for a few other s3 logged resources

[ ] alb
[ ] redshift debug logging
[ ] ?

Thanks Kapil - I was really asking which fields are used from these items - e.g. is it LogFileValidationEnabled in Cloudtrail?


Allow flake8 executable to be set to pipenv.

It appends  run flake8, analogously to the Ruby tools when the executable is set to bundle

Cheers! :beers:


#1020 Correction of doctring for plot.py for sample_kwargs

 Just changed `plot_curves` to `plot_samples`
Description
 Sample Kwargs now has plot_samples instead of plot_curve -
    curve : xr.DataArray
        Curve to plot
    non_grid_names : set[str]
        The names to exclude from the grid. HDI and samples both
        have defaults of hdi and chain, draw, respectively
    subplot_kwargs : dict, optional
        Addtional kwargs to while creating the fig and axes
    sample_kwargs : dict, optional
        Kwargs for the :func:`plot_sample` function
    hdi_kwargs : dict, optional
        Kwargs for the :func:`plot_hdi` function
    same_axes : bool
        If all of the plots are on the same axis
    colors : Iterable[str], optional
        Colors for the plots
    legend : bool, optional
        If to include a legend. Defaults to True if same_axes
    sel_to_string : Callable[[Selection], str], optional
        Function to convert selection to a string. Defaults to
        ", ".join(f"{key}={value}" for key, value in sel.items())

Related Issue

[x] Closes #1020
[x] Related to #1020

Checklist

[x] Checked that the pre-commit linting/style checks pass
[ ] Included tests that prove the fix is effective or that the new feature works
[x] Added necessary documentation (docstrings and/or example notebooks)
[ ] If you are a pro: each commit corresponds to a relevant logical change

Modules affected

[x] MMM
[ ] CLV

Type of change

[ ] New feature / enhancement
[ ] Bug fix
[ ] Documentation
[x] Maintenance
[ ] Other (please specify):

📚 Documentation preview 📚: https://pymc-marketing--1060.org.readthedocs.build/en/1060/

Thanks @Ishaanjolly


Quality: Rename type implicit to library

I would like to create this sub RFC and propose to rename the quality type implicit to quality
quality:
- type: implicit
  rule: rowCount

to
quality:
- type: library
  rule: rowCount

Forcing merge as it affects schema


Unable to comment on any issue or PR

Whenever I try to comment on an issue or PR, I get a "Something went wrong" error message and the message doesn't send.
If it matters: This is on a public repo within an organization that has not been granted access to githawk ( https://github.com/CodaProtocol/coda ).
Please let me know if you need any more info. Thanks!

Bug Report Dump (Auto-generated)

Version 1.22.0<PHONE_NUMBER>)
Device: iPhone X (iOS 12.0)
TestFlight: false

@bkase could you try the TestFlight build and see if this still occurs? Also we have Flex enabled so we can get the raw response if necessary.
https://testflight.apple.com/join/QIVXLkkn

@rnystrom this probably relates to the credential stuff. I’ve been seeing this a lot

Although you appear to have the correct authorization credentials, the CodaProtocol organization has enabled OAuth App access restrictions, meaning that data access to third-parties is limited. For more information on these restrictions, includeing how to whitelist this app, visit https://help.github.com/articles/restricting-access-to-your-organization-s-data/

So I guess I need to authorize Githawk in order to post? Any advice for justifying access to my organization?

(the quote was the error message when posted in the test-flight build)

@rnystrom this probably relates to the credential stuff. I’ve been seeing this a lot

@ijm8710 my thoughts
Sent with GitHawk

Yup, closing in favor of #2165
@bkase if you sign out and sign back in using a PAT w/ repo+user+notification scopes it'll go away. Atm appears to be an auth issue w/ the GraphQL API.


Update packages, eslint, and fix missing packages.

This update outdated packages, updates eslint, and adds a few missing packages
Fix missing packages
Build tools, like eslint, should be added as dev dependencies to JS projects. Then it's the concrete version in your project used when building; rather than depending on an uncontrollable context; which plugins developers or build servers have installed globally.
Update eslint
The .eslintrc format is obsolete. It has been updated to the new flat file format
Update packages
Many packages were very old; including TypeScript that was at 4.x.
Eslint is only updated to version 8; rather than 9 - because the typescript eslint module doesn't support eslint@8 as a peer dependency; making npm fail during install.
@types/node should be of the same major version as the actual node.js runtime. In my local Obsidian developer console, process.versions reveals that it uses version 18 (not 20?), which is why I updated that module to version 18.

The oldest node version that a user can run, and still have a supported installer version is 16.13.2
You also have listed @types/node twice
And when using typescript-eslint one should not use the JS presets, since they overlap somewhat.

Allright, I rolled back the @types/node update
But it is correct that Obsidian comes bundled with a version of node.js? Is there an overview which Obsidian versions use which node versions? E.g. if I decided to use a feature that only exists in node 18, I should make sure that my minAppVersion is set accordingly. (hypothetical right now - not something I have any plans of)
I'll take a look at the eslint settings later today, but I didn't write the configuration; I just used the migration tool to migrate the existing config from the original tempalte.
> npx @eslint/migrate-config .eslintrc.json

As documented here: https://eslint.org/docs/latest/use/configure/migration-guide
That also mentioned that I needed the other eslint packages, that I added.

The Obsidian installer comes bundled with Electron & Node, among other things.
The app version is seperate from that, and thus minAppVersion can't be used to make sure a specific Node.js version is installed.
See also: https://help.obsidian.md/Getting+started/Update+Obsidian#Installer+updates

Allright, a bit of searching made me understand the steps in the auto-converted file does; as well that there's a new typescript plugin compatible with the flat format, simplifying the configuration; and removing the necessity for some of the added packages.
Seems to work, i.e. linter errors are generated when I deliberately create them; both in my editor; and from command line. I'll take the modified config for a spin in my WIP plugin project.
Btw, maybe it would make sense to include a 'lint' step in the 'build' script?

I'm also interested in updating some deps, esbuild in particular. Is there any danger in updating esbuild in our own plugins, or does that potentially introduce incompatibilities at runtime?

The Obsidian installer comes bundled with Electron & Node, among other things. The app version is seperate from that, and thus minAppVersion can't be used to make sure a specific Node.js version is installed.
See also: https://help.obsidian.md/Getting+started/Update+Obsidian#Installer+updates

there was a breaking change once that requires a minimum client version to receive updates.
it's definitely a newer target than ES6.
ES2018 is safe as far as I know because of that.
feel free to ask around but unless you want to write plugins that target EOL obsidian versions, feel free to use ES6.

Yes, that happens every now and then.
The last time this happened was Obsidian 0.14.5, the Electron version at that time was 18.0.3 and the Node version corresponding to that is 16.13.2.
See this file: https://github.com/obsidianmd/obsidian-releases/blob/master/desktop-releases.json.
The minimumVersion there is what we still support as the installer version.
And there are certainly users using installer versions that old.


west: rtt: console output is non-functional with openocd runner

Describe the bug
RTT console support for openocd was added to west in 18f45b5f063 .
It wasn't immediately clear how to use it on any board. Luckily some folks on Discord provided some pointers.

The west rtt command should be used as a drop-in replacement for west debug (sort of). Although west debug drops you down into the gdb console, west debug simply sets up a gdb service on port 3333, and drops you down into a telnet session with RTT output.

There was some concensus that the documentation could be improved.
Aside from that, there are additional technical shortcomings:

west build -t rtt does not work (requiring separate west build and west rtt steps)
west rtt by itself does not attempt to see if any available runners support rtt, requiring a runner to be specified (west rtt -r openocd)
west rtt -r openocd does not actually work due to a race condition (requiring the target to be running so that firmware can execute SEGGER_RTT_Init() and initialize the RTT control block).

To Reproduce

west build -p -S rtt-console -b <board> samples/hello_world
west rtt -r openocd

Expected behavior

RTT console output with west and openocd
The ability to run twister (I also used JLink for this and it was extremely flakey)

To be honest, it would be great if twister used a built-in handler for the RTT console. It doesn't make sense to have every user come up with their own --device-serial-pty script.
Impact
Showstopper for anyone who does not have a dedicated serial port for seeing RTT console output via west or for anyone wishing to use RTT for device testing with twister.
Logs and console output
No rtt runner available (although openocd is available, it just isn't enabled).
zephyr % west rtt
FATAL ERROR: no rtt runner available for board nucleo_l496zg/stm32l496xx. Check the board's documentation for instructions.
FAILED: zephyr/cmake/flash/CMakeFiles/rtt /Users/cfriedt/zephyrproject/zephyr/build/zephyr/cmake/flash/CMakeFiles/rtt
cd /Users/cfriedt/zephyrproject/zephyr/build && /opt/homebrew/Cellar/cmake/3.29.0/bin/cmake -DTARGET=rtt -DDEPENDENCIES="" -P /Users/cfriedt/zephyrproject/zephyr/cmake/flash/check_runner_dependencies.cmake && /opt/homebrew/Cellar/cmake/3.29.0/bin/cmake -E env /opt/zephyr/.venv/bin/python3.12 -m west rtt

Cannot run rtt start before target is running.
% west rtt -r openocd
-- west rtt: rebuilding
ninja: no work to do.
-- west rtt: using runner openocd
-- runners.openocd: OpenOCD GDB server running on port 3333; no thread info available
Open On-Chip Debugger 0.12.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD
Info : clock speed 500 kHz
Info : STLINK V2J35M26 (API v2) VID:PID 0483:374B
Info : Target voltage: 3.233202
ERROR: runners.openocd: [Errno 22] Invalid argument
Info : [stm32l4x.cpu] Cortex-M4 r0p1 processor detected
Info : [stm32l4x.cpu] target has 6 breakpoints, 4 watchpoints
Info : starting gdb server for stm32l4x.cpu on 3333
Info : Listening on port 3333 for gdb connections
    TargetName         Type       Endian TapName            State
--  ------------------ ---------- ------ ------------------ ------------
 0* stm32l4x.cpu       hla_target little stm32l4x.cpu       running

Info : Unable to match requested speed 500 kHz, using 480 kHz
Info : Unable to match requested speed 500 kHz, using 480 kHz
[stm32l4x.cpu] halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x08000888 msp: 0x20001180
Info : Listening on port 5555 for rtt connections
Info : rtt: Searching for control block 'SEGGER RTT'
Info : rtt: No control block found
Info : Listening on port 6333 for tcl connections
Info : Listening on port 4444 for telnet connections
shutdown command invoked

Environment (please complete the following information):

OS: Any
Toolchain: Zephyr SDK (0.17.0, and 0.16.5-1, but likely all versions)
Commit SHA or Version used: 2b5ee0ca91e34944f75580317274c135a5d7c855

Additional context
Script I used for testing twister with --device-serial-pty /tmp/rtt.sh
#!/bin/sh

set -e

OPENOCD_PID=""

cleanup() {
  if [ "$OPENOCD_PID" != "" ]; then
    kill $OPENOCD_PID >/dev/null 2>&1 || true
    wait $OPENOCD_PID >/dev/null 2>&1 || true
  fi
  exit 0
}

trap cleanup EXIT

# let the openocd flashing process proceed first, otherwise it will fail with "Device Flash Error"
sleep 2

openocd \
  -s /Users/cfriedt/zephyrproject/zephyr/boards/st/nucleo_l496zg/support \
  -s /opt/zephyr/zephyr-sdk-0.16.5-1/sysroots/arm64-pokysdk-linux/usr/share/openocd/scripts \
  -f /Users/cfriedt/zephyrproject/zephyr/boards/st/nucleo_l496zg/support/openocd.cfg \
  -c 'tcl_port 6333' -c 'telnet_port 4444' -c 'gdb_port 3333' \
  -c init \
  -c targets \
  -c 'rtt setup 0x20001010 0x10 "SEGGER RTT"' \
  -c 'rtt server start 5555 0' \
  -c 'reset run' \
  -c 'rtt start' \
  >/dev/null &
OPENOCD_PID=$!

# let the rtt server begin
sleep 1

# cat output of the RTT channel
nc localhost 5555

Changes needed to get both west and twister to work
diff --git a/cmake/flash/CMakeLists.txt b/cmake/flash/CMakeLists.txt
index 8fe7380695b..36eb3a33df6 100644
--- a/cmake/flash/CMakeLists.txt
+++ b/cmake/flash/CMakeLists.txt
@@ -154,7 +154,7 @@ endif()

 # Generate the flash, debug, debugserver, attach targets within the build
 # system itself.
-foreach(target flash debug debugserver attach)
+foreach(target flash debug debugserver attach rtt)
   if(target STREQUAL flash)
     set(comment "Flashing ${BOARD}")
   elseif(target STREQUAL debug)
@@ -168,6 +168,8 @@ foreach(target flash debug debugserver attach)
     endif()
   elseif(target STREQUAL attach)
     set(comment "Debugging ${BOARD}")
+  elseif(target STREQUAL rtt)
+    set(comment "Debugging ${BOARD}")
   endif()
   string(TOUPPER ${target} TARGET_UPPER)

diff --git a/scripts/west_commands/runners/openocd.py b/scripts/west_commands/runners/openocd.py
index 2569371ff9b..7c9e78f9ff5 100644
--- a/scripts/west_commands/runners/openocd.py
+++ b/scripts/west_commands/runners/openocd.py
@@ -418,6 +418,7 @@ class OpenOcdBinaryRunner(ZephyrBinaryRunner):
         rtt_cmds = [
             '-c', f'rtt setup 0x{rtt_address:x} 0x10 "SEGGER RTT"',
             '-c', f'rtt server start {self.rtt_port} 0',
+            '-c', 'reset run',
             '-c', 'rtt start',
         ]

@@ -426,31 +427,13 @@ class OpenOcdBinaryRunner(ZephyrBinaryRunner):
                        '-c', f'telnet_port {self.telnet_port}',
                        '-c', f'gdb_port {self.gdb_port}'] +
                       pre_init_cmd + self.init_arg + self.targets_arg +
-                       ['-c', self.reset_halt_cmd] +
                        rtt_cmds
                       )
         self.print_gdbserver_message()
         server_proc = self.popen_ignore_int(server_cmd)
-        # The target gets halted after all commands passed on the commandline are run.
-        # The only way to run resume here, to not have to connect a GDB, is to connect
-        # to the tcl port and run the command. When the TCL port comes up, initialization
-        # is done.
+
         try:
-            sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
-            # As long as the server process is still running, keep retrying the connection
-            while server_proc.poll() is None:
-                try:
-                    sock.connect(('localhost', self.tcl_port))
-                    break
-                except ConnectionRefusedError:
-                    time.sleep(0.1)
-            # \x1a is the command terminator for the openocd tcl rpc
-            sock.send(b'resume\x1a')
-            sock.shutdown(socket.SHUT_RDWR)
-            # Run the client. Since rtt is initialized before the tcl rpc comes up,
-            # the port is open now.
-            self.logger.info("Opening RTT")
-            time.sleep(0.1) # Give the server a moment to output log messages first
+            time.sleep(1) # Give the server a moment to output log messages first
             self.run_telnet_client('localhost', self.rtt_port)
         except Exception as e:
             self.logger.error(e)

Discussion on Discord

@cfriedt I get that this is annoying, but I do not think this is a medium priority bug.

@henrikbrixandersen - it affects multiple platforms. That was my main consideration for making it a medium. Currently, I'm looking at ARC, ARM, and RISC-V systems.
The fact that lots of users are also hitting this issue (but did not have a bug to comment on until now) was another consideration.
cc @dkalowsk @pdgendt @topisani


Enabled crossbuild for Scala 2.12.

Coverage remained the same at 93.976% when pulling 1c0ba4e17679b280ea8d25658c2025889e38319e on ArchDev:patch-1 into b076a336ca67f4e181d9aab3b6bfd3999bf6f804 on AutoScout24:master.


Issue where websocket connection to Twitch PubSub occasionally drops without reconnecting.

After being connected for long periods of time, TAU will occasionally lose its websocket connection without properly reconnecting. Have noticed the result, but have not been able to reproduce yet.

This will be fixed when moving to new sub EventSub webhooks, which will remove need to use PubSub at all.

PubSub completely removed in PR #81


[Feature Request]: Add autoFocus prop on TagPicker

Component that this feature request involves
TagPicker
Is your feature request related to a problem? Please describe
No response
Describe the solution you'd like
I want to be able to set an autoFocus prop on the TagPicker.
Describe alternatives you've considered
No response
Additional context
No response

Thanks!


Admin cli without any options returns error

When run as below the admin CLI returns an error. Ideally it should be printing the help message and exit.
Admin CLI with "-h" option:
python /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py -h
usage: vmdkops_admin.py [-h] {role,ls,status,policy} ...
Manage VMDK Volumes
positional arguments:
{role,ls,status,policy}
role                Administer and monitor volume access control
ls                  List volumes
status              Show the status of the vmdk_ops service
policy              Configure and display storage policy information
optional arguments:
-h, --help            show this help message and exit
Admin CLI without any options:
python /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py
Traceback (most recent call last):
File "/usr/lib/vmware/vmdkops/bin/vmdkops_admin.py", line 583, in
main()
File "/usr/lib/vmware/vmdkops/bin/vmdkops_admin.py", line 39, in main
args.func(args)
AttributeError: 'Namespace' object has no attribute 'func'

Fixed by #593

Fixed via #593


add UI for help with GitHub authentication

I imagine there's a better way to organize things than I did; let me know if
things should get moved around.

looks like this (but a little nicer):

i say merge!

:cat2: :sparkles: :sparkles: :sparkles:

nice!


ngx-oauth2-access-token version 0.0.1-pre.7

The main feature is verifying JWT service. Actually it is not necessary on client-side but in some rarely cases, it may be useful.

We want to make this library simple and small. So we just implement the recommended algorithms that are supported by SubtleCrypto from Web API. The supported algorithms are:

HMAC with alg = HS256 (check supported browsers). If it is not too hard, HS384 and HS512 would be supported.
RSASSA-PKCS1-v1_5 with alg = RS256 (check supported browsers). If it is not too hard, RS384 and RS512 would be supported.
ECDSA with alg = ES256 (check supported browsers). If it is not too hard, ES384 and ES512 would be supported.

The required EdDSA will be separated to another library.
References:

MDN SubtleCrypto
JSON Web Algorithms (JWA)
JSON Web Key (JWK)

This PR doesn't sync with main branch. So close it and re-open again.


Enable convolution of model cubes

It is sometimes necessary to convolve model cubes to a target resolution, but they don't have beams so convolution fails:
mod.convolve_to(psf.beams[0])
---------------------------------------------------------------------------
NoBeamError                               Traceback (most recent call last)
<ipython-input-84-510cae9ff8ae> in <module>
----> 1 mod.convolve_to(psf.beams[0])

/blue/adamginsburg/adamginsburg/casa/casa-6.4.0-16/lib/py/lib/python3.8/site-packages/spectral_cube/dask_spectral_cube.py in wrapper(self, *args, **kwargs)
     75     def wrapper(self, *args, **kwargs):
     76         save_to_tmp_dir = kwargs.pop('save_to_tmp_dir', False)
---> 77         cube = function(self, *args, **kwargs)
     78         if save_to_tmp_dir and isinstance(cube, DaskSpectralCubeMixin):
     79             if not ZARR_INSTALLED:

/blue/adamginsburg/adamginsburg/casa/casa-6.4.0-16/lib/py/lib/python3.8/site-packages/spectral_cube/dask_spectral_cube.py in convolve_to(self, beam, convolve, **kwargs)
   1381
   1382         # Check if the beams are the same.
-> 1383         if beam == self.beam:
   1384             warnings.warn("The given beam is identical to the current beam. "
   1385                           "Skipping convolution.")

/blue/adamginsburg/adamginsburg/casa/casa-6.4.0-16/lib/py/lib/python3.8/site-packages/spectral_cube/base_class.py in beam(self)
    818     def beam(self):
    819         if self._beam is None:
--> 820             raise NoBeamError("No beam is defined for this SpectralCube or the"
    821                               " beam information could not be parsed from the"
    822                               " header. A `~radio_beam.Beam` object can be"

NoBeamError: No beam is defined for this SpectralCube or the beam information could not be parsed from the header. A `~radio_beam.Beam` object can be added using `cube.with_beam`.

This can be worked around with some hackery that should be formalized:
delta = radio_beam.Beam(0*u.deg)
mod.beam = delta
mod.convolve_to(beam)

However, what if we want to convolve each plane to a different resolution?  There's not even a workaround for that right now:
mod.convolve_to(beams) # won't work
mod.spatial_smooth(beams) # also wont, expects a single kernel

I dug a bit deeper and there are no obvious, easy ways to achieve this by writing special functions to pass to apply_function_parallel_spatial.  I think we need to special-case this.

I suggest we should make a special-case radio_beam.DeltaBeam() in radio_beam to make the Beam(0) make more sense to users.

For the single beam case:
mod_wbeam = mod.with_beam(delta)

should work, I think

We have with_beams in: https://github.com/radio-astro-tools/spectral-cube/blob/c3a9eceb5ace5cab774fe4fce58a4a40c2b1b024/spectral_cube/base_class.py#L467
But we don't have a SC -> VSRC method.
Agreed on a DeltaBeam to avoid confusion.

right, it should - but, we should also probably initialize CASA models with Delta beams if we can find a way to uniquely identify them

agreed. Is there something in the header to identify a clean model?

the header unit is Jy pix-1 - can that reliably be treated as a Delta beam?  I think yes?

I thought about this more, and I don't think there is so much reason to add this functionality.  For what I'm doing, it would be better just to find a commonbeam and smooth to that anyway.
Nonetheless, the ability should be there.  That would enable things like per-plane-beam-merging with uvcombine, which we (and CASA) don't support right now.  @urvashirau mentioned needing this coincidentally (?) today.

https://github.com/ALMA-IMF/reduction/commit/9d3846ff08e80a8c1fe1771d4ff87c3c628ead78#diff-91c493e486904d56f624b0744a0257ec2603050401cdb71aaa9d535316ecc8adR118 shows a key use case we should make sure is well-supported

https://github.com/ALMA-IMF/reduction/blob/master/misc/beam_volume_tools.py


Create ORDER_MANAGEMENT.md

I have added the basics of order management, please have a look at it.
Regards
Shiladitya

Thanks for the contribution
Regards
Abhradip


Feature Request: Support for 2D lighting

What problem does this solve or what need does it fill?
Currently, 2D games do not support Lighting such as PointLight and SpotLight, but could greatly benefit from them. The current solution for 2D games is to convert to a 3D camera, and convert all their sprites, etc to 3D.
What solution would you like?
It would be great to be able to use lighting in 2D settings; supporting PointLight and SpotLight along X and Y axis would be great. Im not sure how much further we could take this support, i'm not an expert on lighting in games, and it might be better to convert to a 3D setting for more advanced lighting usage (for example, bouncing lights off collidable objects, walls, etc)
What alternative(s) have you considered?
Currently, I will be converting my game to 3D to support lights.
Additional context
This is in the context of wanting to make a top down 2D/2.5D tile-based open world survival game, akin to Core Keeper. I would love to support lights to allow for a more 3D feel while in a top down 2D setting. I'm now convinced going the 3D route is a great option for my game as a whole, but It got me thinking about the possibility of 2D light support for other use-cases :)

To Bevy maintainers: are there plans to pursue support for 2D lighting in the engine? If yes, what would be the next steps towards this goal?

Good question - I would certainly welcome it. I don't know what 2D lighting approaches there are, although I've seen lots of ray-tracing demos.


Error: Do you have azure>=2.0.0 installed?

I am getting below error when I run ansible playbook:

Do you have azure>=2.0.0 installed? Try pip install 'azure>=2.0.0' --upgrade- No module named containerservice

Ansible version:
ansible <IP_ADDRESS>
config file = /var/www/Ansible/ansible.cfg
configured module search path = [u'/home/vagrant/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /usr/local/lib/python2.7/dist-packages/ansible
executable location = /usr/local/bin/ansible
python version = 2.7.12 (default, Jul 18 2016, 15:02:52) [GCC 4.8.4]
Azure:
Name: azure
Version: 2.0.0rc5
Summary: Microsoft Azure Client Libraries for Python
Home-page: https://github.com/Azure/azure-sdk-for-python
Author: Microsoft Corporation
Author-email<EMAIL_ADDRESS>License: MIT License
Location: /usr/local/lib/python2.7/dist-packages
Requires: azure-servicemanagement-legacy, azure-batch, azure-servicebus, azure-mgmt, azure-storage, azure-graphrbac
I tried to install this: pip install azure-mgmt-containerservice But, now below error is coming:

Installed resource client version is 0.30.0rc5. The supported version is 1.1.0. Try pip install azure>=2.0.0 --upgrade

do you have a solution ? @rnkhouse

no @flemzord

no @flemzord

try sudo easy_install ansible[azure]


Update Community - Proof of Contribution.md

I am adding my proof of contribution for community efforts. I developed a website with much of the common information requested by capital providers. This includes details around contributions, emissions, rewards, market cap, price, etc. I will continue to monitor the capital provider channel for common questions as well as add additional analytics and calculations. Thanks!

Thanks for being awesome. However Community rewards go live in phase 3.
Did you mean to put this in here or in the Code section that is live now?


no message hint when deno cache failed to fetch remote bundles

[ ] deno cache failure checking
[ ] vim and nvim testing

https://github.com/jayli/vim-easycomplete/blob/9c3175ad59da2f89696c1fe54fe6bbd25bdbebc1/autoload/easycomplete/sources/deno.vim#L102-L105

related to #142

-  let sign_placed_list = sign_getplaced(current_fn)
+  try
+    let sign_placed_list = sign_getplaced(current_fn)
+  catch /^Vim\%((\a\+)\)\=:E158/
+    let sign_placed_list = []
+  endtry


[SUGGESTION] More realistic steel production

Steel should be made from iron ore directly instead of iron ingots. I suppose the iron to steel option could be there for those who want to convert their stockpiles of iron into steel, but the main method should be turning iron ore into steel.
If you think that that would be OP, there is one way to gate it, and that is to make it require iron oxide (i.e. crushed iron ore), that way people will need to construct at least a crusher and some power source to be able to do that.

No


ENH: write node errors to a log file

@CJ-Wright commented on Tue Sep 12 2017
Would help with debugging.

Push to half release


Port listening / firewall issues?

Hey, so I had a bit of an issue getting the homebridge accessory to show up in homekit. I noticed that the logs say:
[1/12/2022, 3:31:44 PM] [WLED] Setting up Accessory Kitchen Cabinet with Host-IP: XXX.XXX.XX.XXX Single WLED-Host configured
[1/12/2022, 3:31:44 PM] [WLED] Adding effects: Fireworks 1D
[1/12/2022, 3:31:45 PM] [WLED] WLED Strip finished initializing!
[1/12/2022, 3:31:45 PM] Kitchen Cabinet 656F is running on port XXXXX.
[1/12/2022, 3:31:45 PM] Please add [Kitchen Cabinet 656F] manually in Home app. Setup Code: XXX-XX-XXX
I have a firewall on my homebridge with all ports closed as it is was once accessible over the internet and I just like firewall security I guess. Any way, it took me forever to figure this out because EVERY restart of the homebridge cause the WLED plugin to pull a different port. (specifically in my case, a blocked port that needed to be allowed.)
Can I specify a single port? My homebridge has all its ports closed except for the ports I need open. I also noticed that this port changes on every restart of the homebridge.
Any help on this as I would only like one port open and no others and I would like it to stay static...
Thanks for reading and any help you have.

Due to limitations of homebridge, it is not possible for developers to specify a port for a acessory. But you can set a range of ports the accessories should use.
For that just add this json-object to the config.json of your homebridge instance and there you can specify the start and the end range of the ports, which the accessories can use.
"ports": {
"start": 52100,
"end": 52150
},
So you can add a rule to your firewall to allow this range of ports.
I hope this solves your question.
Best regards
Jonathan

Thanks! This worked perfectly!


Integrate OneClick with Microservice-Connector

Determine best approach and implement.
Dependency: Please wait to do this after the genAI components are moved to their new home to get the right directory paths.

use the manifests provided via oneclick


Manifest V3 tab-sets

This PR identifies spots where Engineering needs to look at Manifest V3 vs V2 code, and related clarifications such as differentiating other types of manifest files.

Learn Build status updates of commit 82a8976:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/aad-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/developer-policies.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 6d7e021:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/aad-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/developer-policies.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 210c946:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/aad-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 381371c:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: CannotMergeCommit] Cannot merge commit 381371c8795181422974a49dfa7e6aaf1a8bc395 in branch user/mikehoffms/exten-tabs of repository https://github.com/mikehoffms/edge-developer into branch main (commit 70a7d9a400c766fb94520705a32de0cefdf7b63f). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 2e1923e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 349fde4:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: CannotMergeCommit] Cannot merge commit 349fde405263c7ede4e656fe4d016c27c399a5c3 in branch user/mikehoffms/exten-tabs of repository https://github.com/mikehoffms/edge-developer into branch main (commit cf0489ab8c75131b1b3f3a31f1b831e43054002d). Please follow this documentation: https://help.github.com/articles/resolving-a-merge-conflict-using-the-command-line/ to use git.exe to resolve you content conflicts locally and then push to remote.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Learn Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 3dea158:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit d40cb37:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 6c2fe64:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit fd5e87d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

Learn Build status updates of commit 69513fc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/developer-guide/alternate-distribution-options.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/native-messaging.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/developer-guide/port-chrome-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/extension-sideloading.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/manifest-format.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/getting-started/media/part1-threedots.png
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/index.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/addons-api-reference.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/api/using-addons-api.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/create-dev-account.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/extensions-analytics.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/publish-extension.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/publish/verify-microsoft-edge-program.md
:white_check_mark:Succeeded
View

microsoft-edge/extensions-chromium/store-policies/csp.md
:white_check_mark:Succeeded
View

microsoft-edge/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel


Licence ?

Hello,
Thanks for your script, nice work!
What's the licence ?
Thanks in advance!

It is not completed :)
License MIT
please use it, if you want

Awesome. Thanks.
Will do a MR soon 😁


Updating to 3.2 breaks usage of node-polyfill-webpack-plugin

Have you read the Contributing Guidelines on issues?

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

Prerequisites

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

Description
When writing mdx components using external dependencies, it might be necessary to use polyfills. One way to do that is to create a docusaurus plugin leveraging node-polyfill-webpack-plugin.
After migrating to docusaurus 3.2 an exception is thrown when building the final website.
Note: it's not clear to me if this is the recommended approach to polyfill node.
Reproducible demo
https://github.com/jeluard/lodestar/tree/jeluard/docusaurus-lc
Steps to reproduce

cd docs
Run yarn
Run yarn build

Expected behavior
Compilation should finish and node specifics should be polyfilled.
Actual behavior
The following error is thrown:
[ERROR] Error: Unable to build website for locale en.
    at tryToBuildLocale (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:53:19)
    at async /Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:64:9
    at async mapAsyncSequential (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/utils/lib/jsUtils.js:20:24)
    at async Command.build (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:62:5) {
  [cause]: Error: Docusaurus static site generation failed for 1 paths:
  - "/lodestar/"
      at generateStaticFiles (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/ssg.js:85:15)
      at async executeSSG (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:146:23)
      ... 4 lines matching cause stack trace ...
      at async Command.build (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:62:5) {
    [cause]: AggregateError
        at generateStaticFiles (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/ssg.js:86:20)
        at async executeSSG (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:146:23)
        at async buildLocale (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:126:31)
        at async tryToBuildLocale (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:46:13)
        at async /Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:64:9
        at async mapAsyncSequential (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/utils/lib/jsUtils.js:20:24)
        at async Command.build (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/commands/build.js:62:5) {
      [errors]: [
        Error: Can't render static file for pathname "/lodestar/"
            at generateStaticFile (/Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/@docusaurus/core/lib/ssg.js:119:15)
            at processTicksAndRejections (node:internal/process/task_queues:95:5)
            at runNextTicks (node:internal/process/task_queues:64:3)
            at process.processImmediate (node:internal/timers:449:9)
            at async /Users/julien/Documents/Projects/jeluard/lodestar/docs/node_modules/p-map/index.js:57:22 {
          [cause]: TypeError: Cannot read properties of undefined (reading 'id')
              at DocItem (server.bundle.js:20550:89)
              at Uc (server.bundle.js:32879:44)
              at Xc (server.bundle.js:32881:253)
              at Z (server.bundle.js:32887:89)
              at Xc (server.bundle.js:32885:231)
              at Z (server.bundle.js:32887:89)
              at Xc (server.bundle.js:32881:481)
              at Z (server.bundle.js:32887:89)
              at Vc (server.bundle.js:32879:473)
              at Xc (server.bundle.js:32881:210)
        }
      ]
    }
  }
}

Note that with docusaurus 3.1 a different error is thrown.
Your environment

Public source code: https://github.com/jeluard/lodestar/
Docusaurus version used: 3.2
Environment name and version (e.g. Chrome 89, Node.js 16.4): node 20
Operating system and version (e.g. Ubuntu 20.04.2 LTS): OSX

Self-service

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

Hi

When writing mdx components using external dependencies, it might be necessary to use polyfills.

I'm not sure to follow, why exactly? How is this different from using external dependencies in React page components? How are external dependencies requiring a node polyfill different from first-party code you write that requires the exact same polyfill?

After migrating to docusaurus 3.2 an exception is thrown when building the final website.

Note that with docusaurus 3.1 a different error is thrown.

It's not clear from which version you are upgrading exactly. If it didn't work before, then how can we consider the new v3.2 breaks things?

jeluard/lodestar@jeluard/docusaurus-lc

This repro is not very actionable from my perspective. I can't investigate your monorepo in its entirety to look for problems because it's not minimal and many things on it could be the source of problems (for example, a dependency/hoisting problem related to the package manager)
Please create a minimal repro using https://docusaurus.new/stackblitz
I need to see a minimal project that works on a specific version before the upgrade, despite including a lib requiring polyfill. And I need to see it failing after the upgrade.

I'm not sure to follow, why exactly? How is this different from using external dependencies in React page components? How are external dependencies requiring a node polyfill different from first-party code you write that requires the exact same polyfill?

What is different is the way things are configured in docusaurus. How can I tweak webpack's configuration in docusaurus?

I need to see a minimal project that works on a specific version before the upgrade, despite including a lib requiring polyfill. And I need to see it failing after the upgrade.

I can look at providing a minimal reproducing issue definitely. What is the recommended approach to hook polyfill, if any?
If I don't provide any polyfill, an error very similar to this one is thrown by webpack.
Note that in dev mode (i.e. docusaurus start), everything works as expected with my current approach. It only fail when building (via docusaurus build).

I'm not sure to follow, why exactly? How is this different from using external dependencies in React page components? How are external dependencies requiring a node polyfill different from first-party code you write that requires the exact same polyfill?

What is different is the way things are configured in docusaurus. How can I tweak webpack's configuration in docusaurus?

https://docusaurus.io/docs/api/plugin-methods/lifecycle-apis#configureWebpack

I need to see a minimal project that works on a specific version before the upgrade, despite including a lib requiring polyfill. And I need to see it failing after the upgrade.

I can look at providing a minimal reproducing issue definitely.

That would help me help you 👍

What is the recommended approach to hook polyfill, if any? If I don't provide any polyfill, an error very similar to this one is thrown by webpack.

"very similar" does not help. If you have an error, please share it exactly as is.
We don't have a recommended approach for now, because most sites don't need it and this is not different from any other Webpack app. If you can make it work outside Docusaurus, you can probably make it work similarly inside.
I still don't even know what contains your code to require such polyfill.
None of the 2 reported errors in this issue (v3.1 or v3.2) look related to polyfills.

Note that in dev mode (i.e. docusaurus start), everything works as expected with my current approach. It only fail when building (via docusaurus build).

Probably because the problem is due to using browser APIs in Node.js, which is likely not a polyfill issue. I will only be able to help if I see a minimal repro.

You can find a minimal repository here. First commit just uses the lib w/o polyfill, then the second adds a polyfill.

https://docusaurus.io/docs/api/plugin-methods/lifecycle-apis#configureWebpack

This is what I did here by providing a plugin, so I would assume that this is the right approach.

I still don't even know what contains your code to require such polyfill.

Some libraries relies on node code (e.g. path, Buffer or crypto) and expect polyfills to run in a browser.

Probably because the problem is due to using browser APIs in Node.js, which is likely not a polyfill issue. I will only be able to help if I see a minimal repro.

That's the other way around, those libs use node APIs e.f. crypto or path. Historically browserify or others have been used to address that.
I've seen a number of workaround in the wild, so looks like others people have those needs:

https://gist.github.com/sibelius/24f63eef7f43b15dc73c4a0be11bbef8
https://gist.github.com/rohit-gohri/59d0e6a9b4f51d1dd39f5e8894050f74
https://github.com/JayaKrishnaNamburu/docusaurus-node-polyfills

You are using this component inside your homepage:
<LatestOptimisticHeader>
import {useEffect, useState} from "react";
import {getClient} from "@lodestar/api";
import {createChainForkConfig} from "@lodestar/config";
import {networksChainConfig} from "@lodestar/config/networks";

import {Lightclient, LightclientEvent} from "@lodestar/light-client";
import {LightClientRestTransport} from "@lodestar/light-client/transport";
import {getFinalizedSyncCheckpoint, getGenesisData, getLcLoggerConsole} from "@lodestar/light-client/utils";

const config = createChainForkConfig(networksChainConfig.mainnet);
const logger = getLcLoggerConsole({logDebug: true});
const api = getClient({urls: ["https://lodestar-mainnet.chainsafe.io"]}, {config});

const lightclient = await Lightclient.initializeFromCheckpointRoot({
  config,
  logger,
  transport: new LightClientRestTransport(api),
  genesisData: await getGenesisData(api),
  checkpointRoot: await getFinalizedSyncCheckpoint(api),
  opts: {
    allowForcedUpdates: true,
    updateHeadersOnForcedUpdate: true,
  },
});

await lightclient.start();

export function LatestOptimisticHeader(): React.JSX.Element {
  const [head, setHead] = useState<string | undefined>();
  const [updated, setUpdated] = useState<boolean>(false);
  useEffect(() => {
    lightclient.emitter.on(LightclientEvent.lightClientOptimisticHeader, (optimisticUpdate) => {
      setHead(optimisticUpdate.beacon.slot.toString());
      setUpdated(true);
      setTimeout(() => setUpdated(false), 1000);
    });
  }, []);
  return (

      Latest optimistic header: {head}

  );
}

Again, this is not minimal at all. You are expecting me to retro-engineer your code.
This has never worked in Docusaurus, not in v3.2 or any previous versions, simply because we don't support ESM and top-level await.
I'm closing because I doubt there is a bug in Docusaurus. We'll re-open when a truly minimal repro is provided, not involving the complexity of your custom dependencies and the code above which can't work.


V0.3

https://github.com/miracl/casper/pull/16/commits/78b5e4ce3229b2ed41d12e32f905ab490c67fe30 is the essence.

Coverage decreased (-1.3%) to 84.114% when pulling 7613b1e05442cabefed9feba5c8dc88656b32ac2 on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.

Coverage decreased (-1.3%) to 84.114% when pulling 15d8d8c21a773489b769fe636b99d3c7caea2c86 on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.

Coverage increased (+2.05%) to 87.486% when pulling de1c3f9b4d7edbfb1c4d9d8cba9effddf62141df on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.

Coverage increased (+3.0%) to 88.399% when pulling 1b811d06b541a741830b258f0939ed9e4432fced on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.

Coverage increased (+3.2%) to 88.631% when pulling 997604f8a96a103c479427d3b13c50a3ea48fa2e on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.

Coverage increased (+3.2%) to 88.631% when pulling 20f9dc7c8ba6c4c1975a4aaf93e9726be4cdfd2b on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.

Coverage increased (+4.01%) to 89.443% when pulling 654ede3afcb626805ad67db67c3882c22d55f08c on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.

Coverage increased (+4.0%) to 89.419% when pulling eabd3c4e49f6a19c3b0f813d4e830e90dfbe98da on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.

Coverage increased (+4.8%) to 90.217% when pulling 552d835b06d704b82b396fb359d706386747edaf on v0.3 into f69c629fd3a8a5dd4080a54844aa4f6d3c96c712 on master.


Update faq.yml

Grammar fix: added "and" in sentence

Docs Build status updates of commit cc5e587:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/azure-data-studio/faq.yml
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Flash player download is broken (404s) again

Issue description
these paths will be fetched (0.61 MiB download, 2.47 MiB unpacked):
  /nix/store/06dlgkv81i9sgkjvj9l9jniz54xkh46f-nghttp2-1.32.0-dev
  /nix/store/4dkl9cpjdgys7q3dyry5nmsgvl3n8y93-nghttp2-1.32.0-bin
  /nix/store/5f4p2zfhbfhp75m6p29wl4x360c5ld9y-nghttp2-1.32.0
  /nix/store/ncvn44kqw3jcjsfi62n43ki932zyyhps-libssh2-1.8.0-dev
  /nix/store/qdcc6418a2xxlmfamm6ai1rrckxcia7f-mirrors-list
  /nix/store/sp9y40cncwvs6zip70wij05lin95c931-curl-7.61.0-dev
copying path '/nix/store/qdcc6418a2xxlmfamm6ai1rrckxcia7f-mirrors-list' from 'https://cache.nixos.org'...
copying path '/nix/store/5f4p2zfhbfhp75m6p29wl4x360c5ld9y-nghttp2-1.32.0' from 'https://cache.nixos.org'...
copying path '/nix/store/ncvn44kqw3jcjsfi62n43ki932zyyhps-libssh2-1.8.0-dev' from 'https://cache.nixos.org'...
copying path '/nix/store/4dkl9cpjdgys7q3dyry5nmsgvl3n8y93-nghttp2-1.32.0-bin' from 'https://cache.nixos.org'...
copying path '/nix/store/06dlgkv81i9sgkjvj9l9jniz54xkh46f-nghttp2-1.32.0-dev' from 'https://cache.nixos.org'...
copying path '/nix/store/sp9y40cncwvs6zip70wij05lin95c931-curl-7.61.0-dev' from 'https://cache.nixos.org'...
building '/nix/store/hd40xqh22v2ghkg3k2rn92f5364d58hw-flash_player_npapi_linux.x86_64.tar.gz.drv'...

trying https://fpdownload.adobe.com/get/flashplayer/pdc/<IP_ADDRESS>/flash_player_npapi_linux.x86_64.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (22) The requested URL returned error: 404 Not Found
error: cannot download flash_player_npapi_linux.x86_64.tar.gz from any mirror

Seems like Flash Player once again got updated, and they removed the old version. It would be nice to have a mirror somewhere for more permanent access.
Steps to reproduce
nix-shell -p flashplayer
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

system: "x86_64-linux"
host os: Linux 4.18.6-ck1, NixOS, 19.03.git.52b9e64 (Koi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1
channels(root): ""
nixpkgs: /etc/nixos/nixpkgs

see https://github.com/NixOS/nixpkgs/pull/46643

Can confirm that it solves the problem. Thanks!


using ShardingTransactionTypeScanner to create proxy bean which include transaction type annotation

for #4937

ShardingTransactionTypeScanner
scanner will create proxy automatically if using @ShardingTransactionType annotation in class or method
ShardingTransactionTypeAdvisor
this advisor is spring original way to proceed AOP which include poinctcut and advice
ShardingTransactionTypeInterceptor
interceptor is a implement of advice which invoke TransactionTypeHolder class

Pull Request Test Coverage Report for Build 2240

25 of 25 (100.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 58.102%

Totals

Change from base Build 1175:
0.05%

Covered Lines:
11915

Relevant Lines:
20507

💛  - Coveralls


About the configuration

Laravel's config system is base on 'key', the key is custom definition, it let developer can't understand in first feel.
Like yii2 config system, it base on Object property, you know it will effect so easy.
My English is not well. Forgive me. :)

Thank you but we try to keep this repo for bug reporting only, for suggestions and feature requests please use the https://github.com/laravel/internals repo.


Add indonesian clean tech companies

Add Indonesian companies in energy sector:

Kaltimex Energy
Surya Energi Indotama

Add Indonesian technopreneur movement in social impact category:

Lentera Bumi Nusantara

Hey @djiwandou, thank you for your contribution!
Could you rebase your branch to get rid of the conflicts please?
Running the following commands should do the trick:
git remote add upstream https://github.com/nglgzz/awesome-clean-tech
git fetch upstream
git rebase upstream/master
git push --force-with-lease origin add-indonesian-clean-tech-companies

thanks Angelo @nglgzz , just did it 🙏


3 widget variants

we are adding a new "carbon offset" product (called "green"). we will now have configuration option for shield: true/false, and green: true/false.
as a result there will be 3 versions of widget/modal:

shield only (current widget)
green only (new widget)
shield + green (new widget)

designs will be shared when they are ready. new API endpoints:
/v1/shield_offers (existing endpoint)
/v1/green_offers (new endpoint)
/v1/offers (new endpoint)
recommend using only /v1/offers endpoint which provides combined fee information. client is responsible for filtering out/ignoring fee if configuration is off (e.g. if shield: false, then client should ignore shieldFee from API).
the rest of the SDK interface is basically the same. greenFee should be added to the callback object if configuration for green is enabled.

@jasmineic please provide iOS designs for new widgets/modals.

@catalin-invisible to help ensure interface/implementation is consistent between JS and mobile SDKs

We're keeping the existing switch button.

@jasmineic do we have any changes on this page?

Yes, there's minor copy update on the bottom. https://www.figma.com/file/ryeFqjwQeMqdFzL8a8hrFz/Shipped-•-Design-System-(VD)?node-id=25959%3A29701

@jasmineic The existing Learn more modal is used for shipped Shield only. If it is Green or Green + Shield, I am not sure what kind of display it should be. The new design has a lot of changes, I'm not sure if I need to make it like this.

@hoyelo final 3 variant designs.
https://www.figma.com/file/ryeFqjwQeMqdFzL8a8hrFz/Shipped-•-Design-System-(VD)?node-id=26269%3A30371


Allow passing own map

I have a map elsewhere, and I'd like to pass that same map, which could also default the lat/lng to that map's center position if they aren't supplied.
{{street-view map=myMap}}

I do not understand what you want to do. If you have a street view map already then I do not see the reason to use the component. If what you want to do is use the lat/lng of another map you already have then you would have to pass in the lat and lng in the component call because the map property is only a google map street view.

I think I understand what @knownasilya is trying to do.
Basically every map instance also has an associated panorama. If you could pass in an existing map, this component could retrieve the corresponding panorama from it.
This way, all the markers from the map, for example, would be shared.
I think this is easy to implement and could lead to a superior flexibility of the component.
I can tackle this along with other minor action improvements I'm planning to PR today.


My asset is present in my Pool.pm, my jpg.store wallet (which is my nami), but NOT present in my ACTUAL Nami Wallet

I minted a Chilled Kong Vox NFT today and the transaction is on chain, the NFT is present in my pool.pm as well as my jpg.store wallet which is my nami wallet. However when I try and list or send the NFT it is not actually present in my Nami wallet. How can I get my asset to where I have actual possession of it and can sell or send it. Thank you

@Cardatson Talk to Cardano Support on the Live support page so that your issue can be looked into.

I am experiencing the same issue. Also Chilled Kong Vox nft, minted with nmkr.io.

Bros same here. I can't see my tokens on Nami wallet but they're here in Pool.pm. WTF is going on ?

I precise i connect my Ledger device with. it Show my ada in Ledger Live. but not in Nami

Kindly get in touch to get this issue resolved

Hello, i've just sent you a DM on twitter. I'm Lord $Beerus. i can show you wallet and more. i can't see my tokens. Thanks.

De : officialsupport-ui @.>
Envoyé : mardi 26 juillet 2022 19:26
À : Berry-Pool/nami-wallet @.>
Cc : MurphyBones @.>; Comment @.>
Objet : Re: [Berry-Pool/nami-wallet] My asset is present in my Pool.pm, my jpg.store wallet (which is my nami), but NOT present in my ACTUAL Nami Wallet (Issue #629)
Kindly get in touch to get this issue resolved
—
Reply to this email directly, view it on GitHubhttps://github.com/Berry-Pool/nami-wallet/issues/629#issuecomment-1195768250, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AWBHSMKCLJCZFY7OQ7GTRS3VWANTHANCNFSM53XFCT6A.
You are receiving this because you commented.Message ID: @.***>

Just happened to me tonight but was able to retrieve my old wallet. Steps I did was click on delegate, enter password, enter the seed phrase and l got my assets back.

I've tried many things to recover my tokens. Bad news is that i can't access some of my funds for now BUT they're still present. Downloaded Etrnl, Yoroi, Gero wallet and Nami Still the same. BUT i successfully can access my wallet through Ledger Live. So i was able to get back some of my tokens as Sundae, Minswap, Dana, and others but can't withdraw C3 and GERO for now. Still waiting for this issue to be solved.
I've unstake and it did nothing.

@MurphyBones Talk to Cardano Support on the Live support page so that your issue can be looked into.

Still no way to retreive my C3 and GERO

Talk to Cardano Support on the Live support page so that your issue can be looked into.

@MurphyBones @Cardatson @Stimp737 Talk to Cardano  Support on the Cardano Live Support so that your issue can be looked into.
Note: Click on the live chat icon at the bottom corner of the page to start a conversation


Errors definition — Fix specified message for malformed_payload error

Summary
I noticed the :syntaxErrorHelper has always been at the end of the malformed_payload error message.
I don't think we specifically wanted the current specified behaviour. I think it's more like we made a typo when writing the spec the first time. Thus, I put this as a Catch-up PR.
Let me know if I'm wrong.

Closing this PR in favor of https://github.com/meilisearch/specifications/pull/180. Simply because we do not wants new PR to start from develop but from release-vX.X.X. if I try to rebase that one on release-v0.30.0 I got so much old conflicts that it's faster to start from scratch.


[Task]: Optimise the performance of getClientPertinentTenant() method by removing the isSuperUser() check

SubTasks

Remove the isSuperUser() check from all the places within the code just keep the check in /v1/tenants/current (GET).

For consolidated API get and edit, change the DTO from Tenant to Tenant without subscriptionDetails object which ensures we do not return this object in the consolidated APIs.
Check for all the other places in the code where this method is getting invoked and set the subscriptionDetails object accordingly. So, this will optimise all the other areas of code from where we are doing the isSuperUser() check unnecessarily.

Why is this Necessary?
https://www.notion.so/appsmith/Tenants-Consolidated-View-04fded2685d345f5a1b0de964d9940d4?pvs=4#d1680684684844c9a91383d4dc1a6015

Added the changes in this EE PR

This is waiting for the past 4 days on the instrumentation PRs https://github.com/appsmithorg/appsmith/pull/34516 and https://github.com/appsmithorg/appsmith-ee/pull/4539 to be in production, as we can view some metrics and then do this optimisation.
Unfortunately, the promotion is failing every day.
https://theappsmith.slack.com/archives/C02GAUE9P5H/p1719926433808089?thread_ts=1719909864.823359&cid=C02GAUE9P5H


Improve Troubleshooting Docs

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/3401
Originally created by @pnadolny13 on 2022-04-14 22:01:55

We had some discussions in https://gitlab.com/meltano/meltano/-/issues/3394 about logging differently to help users solve their own problems faster and avoid having to come to slack for common issues like bad configs or credential. It sounds like the logs are probably fine and it might be more about the users not knowing how to easily debug on their own.
Theres a troubleshooting guide in the docs but its pretty simple - maybe adding a few common cases like discovery failed and a step by step to debug it so we can point users there before helping in slack.
@pandemicsyn let me know if you have any thoughts here? I usually just skim the logs so I probably dont have the best recommendations for users.
cc @edgarrmondragon @tayloramurphy @aaronsteers @cjohnhanson @kgpayne if you guys have any good debugging tips and tricks

We've added a bunch of documentation on https://docs.meltano.com/guide/troubleshooting


Request a call - User receives two error messages after inputting an invalid number & deleting

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open the New Expensify App
Sign into a valid user with a workspace
Tap on Profile > Workspace > "?" icon
Tap on Request a setup call
Input an invalid number in the Phone number section (For example: 1111111) and tap Call me button
Delete the number leaving only one digit

Expected Result:
The user expects to receive only one error message for invalid number during the entire process
Actual Result:
The user ends up receiving a second error message for no apparent reason
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/201394212-c941b984-6a49-4f52-a121-6b07a88e0a9e.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Doesn't look like a bug to me.

Same. I'm confused how this is a bug? They didn't clear the invalid input fully and resubmit the form, so the error message remained?

They didn't clear the invalid input fully and resubmit the form, so the error message remained?

Correct, let's close this?

Yup, closing!


The "scope" attribute for scoped slots has been deprecated

Hey!
Just want to notify that in the docs you still use the scope attribute which results in following warning:
(Emitted value instead of an instance of Error) the "scope" attribute for scoped slots have been deprecated and replaced by "slot-scope" since 2.5. The new "slot-scope" attribute can also be used on plain elements in addition to <template> to denote scoped slots.
for example when using footer code example
<template slot="footer" scope="props">...
Cheers! :)

Hello @silvio-e Although I am aware of the upcoming depcration, many people still use older versions of vue. Will change this after some more time so people don't have issues with scoped slots not working on older versions due to the new syntax


the-farm: teach about interfaces

Addresses #1638

For some reason I can't push my fixes to the branch here. I will merge this as is and create an additional PR for the updates.


Is there a way to auto  scale containers deployed in docker swarm, using portainer-ce?

Hi,
I have a 2 nodes docker swarm environment managed from portainer-ce. I'm looking for a way to automatically scale (horizontaly and/or vertically, up or down) the running containers, based on their load.
Is it possible to achive this with portainer-ce?
Thanks.

Swarm does not support Auto-scaling out of the box.
Portainer does not have that additional functionality either.
https://soumyadeeppaul.medium.com/auto-scaling-services-on-swarm-cd1f6fafd7ac
You could instead look at using Portainer webhook or docker api proxy to change the replicas instead of using Jenkins etc.


How can we use PivotTable.js for a moving average?

I would like to do this: https://en.wikipedia.org/wiki/Moving_average
I will use for sales, expenses and time worked, and there are so many other potential uses! I'd like to see trends and reduce spikes.
I saw this thread, which is similar but not the same:
https://github.com/nicolaskruchten/pivottable/issues/120
Any pointers? We would contribute any code needed for this. Just not sure where is best place to add it.
Thanks!

Some example code:
https://github.com/kaelzhang/finmath#smoothed-moving-average-smadata-size-times
Example UI:
https://github.com/rajasharan/moving-averages-chartjs
I have daily/weekly/monthly reports in Pivot Tables and it's hard to see trends with the spikes.
Thanks!

Related discussions:

https://github.com/nicolaskruchten/pivottable/issues/140
https://github.com/nicolaskruchten/pivottable/issues/355
https://github.com/nicolaskruchten/pivottable/issues/655
https://github.com/nicolaskruchten/pivottable/issues/863