Support for multiple nginx proxies

Is it possible to combine multiple nginx containers with this letsencrypt image,
for example if i have multiple ipv4-adresses on a single docker-host?

Is it even possible to have multiple nginx-proxy on the same host ? I don't get how you would do that with the vanilla version.

I have the same question: is it possible to use two or more images for two or more nginx-proxy sets for different IPs?
And yes, it is possible to have multiple nginx-proxy on the same host.
In case you are using separate nginx-proxy containers you will need to slightly change default nginx.tmpl per each additional instance: change VIRTUAL_HOST to some different variable (VIRTUAL_HOST_1) and then use that variable for your virtual host containers (instead of standard VIRTUAL_HOST)

@oktango if you follow the same logic you should be able to edit the letsencrypt_service_data.tmpl to use LETSENCRYPT_HOST_1 instead of LETSENCRYPT_HOST, then bind the nginx-proxy container to a specific host IP by using -p IP:host_port:container_port or -p IP::port.
Having the ability to run multiple disctint nginx-proxy stack each bound to a specific host ip without modification to either nginx.tmpl or letsencrypt_service_data.tmpl would be a nice feature to both projects.


Video of a user doing the installation

In order to make installation hassle-free. We need to add a quick guide video to explain the installation process.
I would like to work on this issue.

Good idea... Waiting for it! 😊

Hey Praveen, I have created the video. How to share it? Do I need to upload the video here or on YouTube and sharing the link?

Start with uploading here in GitHub, it supports videos... Let me have a look and give you ideas... 😊

Here is the edited video I made: https://drive.google.com/file/d/17CQ0Jaxj3n00rZfbsxAkEEmj3D2UsfjR/view?usp=sharing
The video size is around 50MB, so it is not possible to upload here on github directly (as there is file size limit of 10MB)
Please do check out the video I have given access.

Some corrections and suggestions:

Don't just fork only the main branch, because you need website branch as well.
Can we add Star the repo too? Pweez? 🙏🏻

This video is extremely amazing, just shows App on Windows, so I am gonna do both App and Website on Mac.

And you can tell me what point level you want on this? 😊

Sure, I will update the video as per the suggestion.
For points, I would say it's an intermediate level of work for me. So provide me the points that are given for intermediate level of work.


[monitor-query] Prepping monitor-query for first beta release.

Normal release updates - changelog date and adjusting package.json metadata so the generated file's user agent version are also updated.

@KarishmaGhiya  - this includes the update to the package.json so it passes the right paths to PrepareRelease.ps1.


Question regarding N/A optional elements

Summary
For optional data elements such as workersPresent, reducedSpdPosted, or the enumerated field roadRestrictions, what is expected if no data is available?
I have seen that some data producers are utilizing the text 'N/A' when there is no data for a optional data element, while others are simply leaving the data element blank, and others are omitting the enumerated element if unavailable.
Motivation
I am currently undergoing the process of creating the specification plan for Oregon DOT's WZDx feed and want to ensure that it closely models and complies with other data producer's feeds for easy plug-in-play use by data consumers.
Desired Result
Direction on what is the standard for these situations where data is unavailable would be appreciated. If the decision is to use the text 'N/A', or leave the element blank, or omit the element, then this should be denoted in the documentation so that data producers follow the same behavior.

I also foresee this as a potential issue, especially if someone later tries to use the data for metrics of some kind. Typically, an XML element is optional if not always known/required. For an enumerated field, only the enumerations should be used in which case roadRestrictions should either have "None" added to the list or it should be make optional. For the ones which are simple types (like workersPresent or reducedSpdPosted), having random values filled in does not seem like a good idea.

Closed to consolidate with #73. Please add new discussion there.


Sound effects pools

Add a proper sound system for handling sounds, with pooling. I tried to call different random sfx (for example in components/bullets.js:43) but that doesn't feel and work fine.

I think we won't need this anymore with the current implemetation, I'll close and we could leave that idea for future demos.


Fix typo in llvm.ml

AcqiureRelease -> AcquireRelease

Sorry but we don't use github for PR.
instead, please submit the patch here:
https://reviews.llvm.org/


Issue resolving package/installation (see #3356)

Environment
System:

OS: Windows 10 10.0.19043
CPU: (12) x64 Intel(R) Core(TM) i7-9850H CPU @ 2.60GHz
Memory: 13.98 GB / 31.79 GB

Binaries:

Node: 16.15.1 - C:\nodejs\node.EXE
npm: 8.12.1 - C:\nodejs\npm.CMD

NOTE (might not be the issue, but might even be worth mentioning): node+npm environment is managed through NVM for Windows.
Reproduction
I can reproduce the problem everytime with these steps below.
Steps to reproduce

I've created a new React Native project from scratch, usingnpx react-native init AwesomeTSProject --template react-native-template-typescript

I've installed react-i18next (optional: I see the same error even without this step) usingnpm install react-i18next --save

The resulting package.json from these steps above is:
{
  "name": "awesometsproject",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint . --ext .js,.jsx,.ts,.tsx"
  },
  "dependencies": {
    "react": "17.0.2",
    "react-i18next": "^11.17.0",
    "react-native": "0.68.2"
  },
  "devDependencies": {
    "@babel/core": "^7.12.9",
    "@babel/runtime": "^7.12.5",
    "@react-native-community/eslint-config": "^2.0.0",
    "@types/jest": "^26.0.23",
    "@types/react-native": "^0.67.3",
    "@types/react-test-renderer": "^17.0.1",
    "@typescript-eslint/eslint-plugin": "^5.17.0",
    "@typescript-eslint/parser": "^5.17.0",
    "babel-jest": "^26.6.3",
    "eslint": "^7.32.0",
    "jest": "^26.6.3",
    "metro-react-native-babel-preset": "^0.67.0",
    "react-test-renderer": "17.0.2",
    "typescript": "^4.4.4"
  },
  "resolutions": {
    "@types/react": "^17"
  },
  "jest": {
    "preset": "react-native",
    "moduleFileExtensions": [
      "ts",
      "tsx",
      "js",
      "jsx",
      "json",
      "node"
    ]
  }
}

I've ran npm install --save styled-components to installa styled-components, as described in https://styled-components.com/docs/basics#installation

Expected Behavior
Styled components should've been installed.
Actual Behavior
Node/NPM unable to resolve dependency tree with this error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!   peer react@">= 16.8.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/styled-components
npm ERR!     styled-components@"*" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/react-dom
npm ERR!   peer react-dom@">= 16.8.0" from<EMAIL_ADDRESS>npm ERR!   node_modules/styled-components
npm ERR!     styled-components@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\marco.bresciani\AppData\Local\npm-cache\eresolve-report.txt for a full report.

npm ERR!      C:\Users\marco.bresciani\AppData\Local\npm-cache\_logs\2022-06-09T06_37_45_051Z-debug-0.log

Further note: current experiments and errors are seen in a project with a space in the path, but it also happens with same sequence applied in a path without spaces.
Adding noted attachments:

eresolve-report.txt
2022-06-09T06_37_45_051Z-debug-0.log

Workarounds/solutions listed in #3356 are not working.

Problem solved by running npm install --save react-dom@17.

For those, who can't figure out the problem: this is not styled-components error. As the console said it's an NPM Error.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree

To solve this problem, you can run this command:
-    npm install --save --legacy-peer-deps styled-components
To understand better, I highly recommended to read this stackoverflow article.


Add a Way to Dynamically Update CSS for Components

Currently, there is no straightforward way to update the CSS of a component after it has been loaded, even if it has an ui.update function. The only workaround I found involves removing the element with the old style and re-rendering it with the new style, which is not ideal.
Suggested Enhancement:
Introduce functionality to dynamically update the CSS of components without requiring a full re-render. This could be particularly useful for components like cards and value boxes.

Is it technically possible to restyle without re-rendering the component with a clever use of ui.tags.style() and reactivity. For example, the button here toggle  red on/off for the <body>:
from shiny.express import input, render, ui

ui.input_action_button("btn", "Press me")

@render.ui
def style():
    if input.btn() % 2 == 1:
        return ui.tags.style("body { background-color: red; }")
    else:
        return None


Recommended tabs

The recommended tabs page isn't implemented yet.  That should be implemented.

Done!


Option to support CloudFront-Forwarded-Proto

Add a new option or extend the exsiting configuration option ModPagespeedRespectXForwardedProto to also cover the header 'CloudFront-Forwarded-Proto'. This header serves the same function as the X-Forwarded-Proto header.
Documentation on this option
http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorCustomOrigin.html

If you have the headers-more module [1] available you could transform CloudFront-Forwarded-Proto to X-Forwarded-Proto:
        more_set_input_headers 'X-Forwarded-Proto: $http_cloudfront_forwarded_proto';
        pagespeed RespectXForwardedProto on;

Would that work for you?
[1] https://github.com/openresty/headers-more-nginx-module#name

Oh, wait, I see I made a mistake. The configuration I posted was for nginx and is not going to work for Apache. Sorry!
Perhaps mod_headers is able to perform the required request-header manipulation, but I'm not sure.

I'll take a look, thanks for the suggestion.

mod_header worked, thank you for the suggestion oschaaf. My settings:
SetEnvIf CloudFront-Forwarded-Proto https HTTPS_PROTO
RequestHeader set X-Forwarded-Proto "https" env=HTTPS_PROTO


SR questions

How did you arrive at plus 12 and minus 12 mels?  Was this just just a random choice or did you test 3,6, 20 etc to find the optimal range?
Why did you choose to convert to mels, and then resize, and vocode back to wav? Why not just process the audio file and change the pitch?
you had mentioned in another post that you had gotten better results with a custom trained vocoder, but retrained with the standard VCTK for compatibility with other models. Could you share your custom trained vocoder model?
Thanks,
Steven

kind of random. just a number that is neither too small nor too large.
the main reason is that the implementation is easier and theory is simpler and does not require complicated signal processing knowledge. and i personally think it sounds better than dsp ways.
that 'better' is very trivial and i'm a bit lazy to search that vocoder, it's just a normal hifigan trained with 16k VCTK.

Ahh ok.
Yeah no problem, no need to look for it.
Thank you for always replying to all of the questions!


Getting a warning in 'make upload'

Is this normal (especially the line at the bottom)?
make upload
make[1]: Entering directory '/home/sqazi/fpga/litex-rowhammer-tester'
python rowhammer_tester/targets/zcu104.py --load --ip-address <IP_ADDRESS> --mac-address 0x10e2d5000001 --udp-port 1234
INFO:SoC:        __   _ __      _  __
INFO:SoC:       / /  () /___ | |//
INFO:SoC:      / /__/ / __/ -)>  <
INFO:SoC:     ///_/_//|_|
INFO:SoC:  Build your hardware, easily!
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:Creating SoC... (2020-12-04 19:09:09)
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:FPGA device : xczu7ev-ffvc1156-2-i.
INFO:SoC:System clock: 125.00MHz.
INFO:SoCBusHandler:Creating Bus Handler...
INFO:SoCBusHandler:32-bit wishbone Bus, 4.0GiB Address Space.
INFO:SoCBusHandler:Adding reserved Bus Regions...
INFO:SoCBusHandler:Bus Handler created.
INFO:SoCCSRHandler:Creating CSR Handler...
INFO:SoCCSRHandler:32-bit CSR Bus, 32-bit Aligned, 16.0KiB Address Space, 2048B Paging, big Ordering (Up to 32 Locations).
INFO:SoCCSRHandler:Adding reserved CSRs...
INFO:SoCCSRHandler:CSR Handler created.
INFO:SoCIRQHandler:Creating IRQ Handler...
INFO:SoCIRQHandler:IRQ Handler (up to 32 Locations).
INFO:SoCIRQHandler:Adding reserved IRQs...
INFO:SoCIRQHandler:IRQ Handler created.
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:Initial SoC:
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:32-bit wishbone Bus, 4.0GiB Address Space.
INFO:SoC:32-bit CSR Bus, 32-bit Aligned, 16.0KiB Address Space, 2048B Paging, big Ordering (Up to 32 Locations).
INFO:SoC:IRQ Handler (up to 32 Locations).
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoCCSRHandler:ctrl CSR allocated at Location 0.
INFO:SoCBusHandler:io0 Region added at Origin: 0x00000000, Size: 0x100000000, Mode: RW, Cached: False Linker: False.
INFO:SoCCSRHandler:identifier_mem CSR allocated at Location 1.
INFO:SoCCSRHandler:uart_phy CSR allocated at Location 2.
INFO:SoCCSRHandler:uart CSR allocated at Location 3.
INFO:SoCCSRHandler:timer0 CSR allocated at Location 4.
INFO:USMMCM:Creating USMMCM, speedgrade -2.
INFO:USMMCM:Registering Differential ClkIn of 125.00MHz.
INFO:USMMCM:Creating ClkOut0 pll4x of 500.00MHz (+-10000.00ppm).
INFO:USMMCM:Creating ClkOut1 idelay of 500.00MHz (+-10000.00ppm).
INFO:USMMCM:Creating ClkOut2 uart of 125.00MHz (+-10000.00ppm).
INFO:SoCCSRHandler:leds CSR allocated at Location 5.
INFO:SoCCSRHandler:ddrphy CSR allocated at Location 6.
INFO:SoCCSRHandler:controller_settings CSR allocated at Location 7.
INFO:SoCCSRHandler:sdram CSR allocated at Location 8.
INFO:SoCBusHandler:main_ram Region added at Origin: 0x40000000, Size: 0x40000000, Mode: RW, Cached: True Linker: False.
INFO:SoCBusHandler:main_ram added as Bus Slave.
INFO:SoCBusHandler:uartbone added as Bus Master.
INFO:SoCCSRHandler:rowhammer CSR allocated at Location 9.
INFO:SoCBusHandler:pattern_data Region added at Origin: 0x20000000, Size: 0x00000400, Mode: RW, Cached: True Linker: False.
INFO:SoCBusHandler:pattern_data added as Bus Slave.
INFO:SoC:RAM pattern_data added Origin: 0x20000000, Size: 0x00000400, Mode: RW, Cached: True Linker: False.
INFO:SoCBusHandler:pattern_addr Region added at Origin: 0x21000000, Size: 0x00000040, Mode: RW, Cached: True Linker: False.
INFO:SoCBusHandler:pattern_addr added as Bus Slave.
INFO:SoC:RAM pattern_addr added Origin: 0x21000000, Size: 0x00000040, Mode: RW, Cached: True Linker: False.
INFO:SoC:BIST pattern: Length: 16, Data Width: 512-bit, Address width: 32-bit
INFO:SoCCSRHandler:writer CSR allocated at Location 10.
INFO:SoCCSRHandler:reader CSR allocated at Location 11.
INFO:SoCBusHandler:payload Region added at Origin: 0x30000000, Size: 0x00000400, Mode: RW, Cached: True Linker: False.
INFO:SoCBusHandler:payload added as Bus Slave.
INFO:SoC:RAM payload added Origin: 0x30000000, Size: 0x00000400, Mode: RW, Cached: True Linker: False.
INFO:SoCBusHandler:scratchpad Region added at Origin: 0x31000000, Size: 0x00000400, Mode: R, Cached: True Linker: False.
INFO:SoCBusHandler:scratchpad added as Bus Slave.
INFO:SoC:RAM scratchpad added Origin: 0x31000000, Size: 0x00000400, Mode: R, Cached: True Linker: False.
INFO:SoC:Instruction payload: Length: 256, Data Width: 32-bit
INFO:SoC:Scratchpad memory: Length: 16, Data Width: 512-bit
INFO:SoCCSRHandler:payload_executor CSR allocated at Location 12.
INFO:USMMCM:Config:
divclk_divide : 1
clkout2_freq  : 125.00MHz
clkout2_divide: 8
clkout2_phase : 0.00°
clkout0_freq  : 500.00MHz
clkout0_divide: 2
clkout0_phase : 0.00°
clkout1_freq  : 500.00MHz
clkout1_divide: 2
clkout1_phase : 0.00°
vco           : 1000.00MHz
clkfbout_mult : 8
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:Finalized SoC:
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoC:32-bit wishbone Bus, 4.0GiB Address Space.
IO Regions: (1)
io0                 : Origin: 0x00000000, Size: 0x100000000, Mode: RW, Cached: False Linker: False
Bus Regions: (5)
pattern_data        : Origin: 0x20000000, Size: 0x00000400, Mode: RW, Cached: True Linker: False
pattern_addr        : Origin: 0x21000000, Size: 0x00000040, Mode: RW, Cached: True Linker: False
payload             : Origin: 0x30000000, Size: 0x00000400, Mode: RW, Cached: True Linker: False
scratchpad          : Origin: 0x31000000, Size: 0x00000400, Mode: R, Cached: True Linker: False
main_ram            : Origin: 0x40000000, Size: 0x40000000, Mode: RW, Cached: True Linker: False
Bus Masters: (1)

uartbone
Bus Slaves: (5)
main_ram
pattern_data
pattern_addr
payload
scratchpad
INFO:SoC:32-bit CSR Bus, 32-bit Aligned, 16.0KiB Address Space, 2048B Paging, big Ordering (Up to 32 Locations).
CSR Locations: (13)
ctrl                : 0
identifier_mem      : 1
uart_phy            : 2
uart                : 3
timer0              : 4
leds                : 5
ddrphy              : 6
controller_settings : 7
sdram               : 8
rowhammer           : 9
writer              : 10
reader              : 11
payload_executor    : 12
INFO:SoC:IRQ Handler (up to 32 Locations).
INFO:SoC:--------------------------------------------------------------------------------
INFO:SoCBusHandler:csr Region added at Origin: 0x00000000, Size: 0x00010000, Mode: RW, Cached: False Linker: False.
INFO:SoCBusHandler:csr added as Bus Slave.
INFO:SoCCSRHandler:bridge added as CSR Master.
INFO:SoCBusHandler:Interconnect: InterconnectShared (1 <-> 6).

****** Vivado v2019.2 (64-bit)
**** SW Build 2708876 on Wed Nov  6 21:39:14 MST 2019
**** IP Build 2700528 on Thu Nov  7 00:09:20 MST 2019
** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.
WARNING: 'open_hw' is deprecated, please use 'open_hw_manager' instead.
open_hw_manager
INFO: [Labtools 27-2285] Connecting to hw_server url TCP:localhost:3121
INFO: [Labtools 27-2222] Launching hw_server...
INFO: [Labtools 27-2221] Launch Output:
****** Xilinx hw_server v2019.2
**** Build date : Nov  6 2019 at 22:13:42
** Copyright 1986-2019 Xilinx, Inc. All Rights Reserved.
INFO: [Labtools 27-3415] Connecting to cs_server url TCP:localhost:3042
INFO: [Labtools 27-3417] Launching cs_server...
INFO: [Labtools 27-2221] Launch Output:
****** Xilinx cs_server v2019.2.0
**** Build date : Nov 06 2019-21:41:48
** Copyright 2017-2019 Xilinx, Inc. All Rights Reserved.
INFO: [Labtoolstcl 44-466] Opening hw_target localhost:3121/xilinx_tcf/Xilinx/25683A
INFO: [Labtools 27-3164] End of startup status: HIGH
program_hw_devices: Time (s): cpu = 00:00:11 ; elapsed = 00:00:11 . Memory (MB): peak = 1469.859 ; gain = 0.000 ; free physical = 5844 ; free virtual = 23135
INFO: [Labtools 27-1434] Device xczu7 (JTAG device index = 0) is programmed with a design that has no supported debug core(s) in it.
INFO: [Common 17-206] Exiting Vivado at Fri Dec  4 19:09:39 2020...

Also, the documentation mentions a correct USB port.  How do I know which one?  I see three ttyUSB*, and neither seem to work.

Hi, as for uploading the bitstream, the warning is normal, and is not a problem. You can verify that the bitstream has been uploaded by checking the LEDs next to the 4 push buttons (near the FTDI chip connected to microUSB). They should start flashing in a circular pattern (out[3:0] <= {out[2:0], ~out[3]}).
Indeed the number of USB ports may be confusing. There is an FTDI chip on the board that actually has 4 channels, those are (from UG1267, ZCU104 Board User Guide):
* Channel A is configured to support the JTAG chain.
* Channel B implements UART0 MIO18/19 connections.
* Channel C implements UART1 MIO20/21 connections.
* Channel D implements UART2 PL-side bank 28 4-wire interface.

Currently we are using the UART connected to PL, so channel D. The channels should generally (but I am not entirely sure if this is guaranteed) show up as subsequent /dev/ttyUSBx devices, so if you have no other devices connected then channel D should be /dev/ttyUSB3. More specifically it should be the device on USB interface 3 of the FTDI (you could search in ls /sys/bus/usb/devices/*.3/ with * being the device - there should be e.g. ttyUSB3 directory inside.
Then you should run litex_server --uart --uart-port /dev/ttyUSB3 --uart-baudrate 1e6. To test that it's working, you can run python rowhammer_tester/scripts/dump_regs.py. I noticed that sometimes it hangs at first time, and only after I restart the litex_server and try again it works properly. This will not be an issue after we merege https://github.com/antmicro/litex-rowhammer-tester/pull/19, which should be ready today.
If you have any other issues, feel free to write them here. After finishing https://github.com/antmicro/litex-rowhammer-tester/pull/19 I'll update the README and include info about the USB ports.

Thank you.  It worked on the second try:
$ python ./dump_regs.py
Using generated target files in: ../../build/zcu104
0x00000000: 0x00000000 ctrl_reset
0x00000004: 0x12345678 ctrl_scratch
0x00000008: 0x00000000 ctrl_bus_errors
0x00001800: 0x00000000 uart_rxtx
0x00001804: 0x00000001 uart_txfull
0x00001808: 0x00000001 uart_rxempty
0x0000180c: 0x00000003 uart_ev_status
0x00001810: 0x00000000 uart_ev_pending
0x00001814: 0x00000000 uart_ev_enable
0x00001818: 0x00000001 uart_txempty
0x0000181c: 0x00000001 uart_rxfull
0x00002000: 0x00000000 timer0_load
0x00002004: 0x00000000 timer0_reload
0x00002008: 0x00000000 timer0_en
0x0000200c: 0x00000000 timer0_update_value
0x00002010: 0x00000000 timer0_value
0x00002014: 0x00000000 timer0_ev_status
0x00002018: 0x00000000 timer0_ev_pending
0x0000201c: 0x00000000 timer0_ev_enable
0x00002800: 0x00000000 leds_out
0x00003000: 0x00000000 ddrphy_rst
0x00003004: 0x00000001 ddrphy_en_vtc
0x00003008: 0x0000009e ddrphy_half_sys8x_taps
0x0000300c: 0x00000000 ddrphy_wlevel_en
0x00003010: 0x00000000 ddrphy_wlevel_strobe
0x00003014: 0x00000000 ddrphy_cdly_rst
0x00003018: 0x00000000 ddrphy_cdly_inc
0x0000301c: 0x00000000 ddrphy_cdly_value
0x00003020: 0x00000000 ddrphy_dly_sel
0x00003024: 0x00000000 ddrphy_rdly_dq_rst
0x00003028: 0x00000000 ddrphy_rdly_dq_inc
0x0000302c: 0x00000000 ddrphy_rdly_dq_bitslip_rst
0x00003030: 0x00000000 ddrphy_rdly_dq_bitslip
0x00003034: 0x00000000 ddrphy_wdly_dq_rst
0x00003038: 0x00000000 ddrphy_wdly_dq_inc
0x0000303c: 0x00000000 ddrphy_wdly_dqs_rst
0x00003040: 0x00000000 ddrphy_wdly_dqs_inc
0x00003044: 0x00000002 ddrphy_rdphase
0x00003048: 0x00000002 ddrphy_wrphase
0x00003800: 0x00000001 controller_settings_refresh
0x00004000: 0x00000001 sdram_dfii_control
0x00004004: 0x00000000 sdram_dfii_pi0_command
0x00004008: 0x00000000 sdram_dfii_pi0_command_issue
0x0000400c: 0x00000000 sdram_dfii_pi0_address
0x00004010: 0x00000000 sdram_dfii_pi0_baddress
0x00004014: 0x00000000 sdram_dfii_pi0_wrdata
0x00004024: 0x00000000 sdram_dfii_pi0_rddata
0x00004034: 0x00000000 sdram_dfii_pi1_command
0x00004038: 0x00000000 sdram_dfii_pi1_command_issue
0x0000403c: 0x00000000 sdram_dfii_pi1_address
0x00004040: 0x00000000 sdram_dfii_pi1_baddress
0x00004044: 0x00000000 sdram_dfii_pi1_wrdata
0x00004054: 0x00000000 sdram_dfii_pi1_rddata
0x00004064: 0x00000000 sdram_dfii_pi2_command
0x00004068: 0x00000000 sdram_dfii_pi2_command_issue
0x0000406c: 0x00000000 sdram_dfii_pi2_address
0x00004070: 0x00000000 sdram_dfii_pi2_baddress
0x00004074: 0x00000000 sdram_dfii_pi2_wrdata
0x00004084: 0x00000000 sdram_dfii_pi2_rddata
0x00004094: 0x00000000 sdram_dfii_pi3_command
0x00004098: 0x00000000 sdram_dfii_pi3_command_issue
0x0000409c: 0x00000000 sdram_dfii_pi3_address
0x000040a0: 0x00000000 sdram_dfii_pi3_baddress
0x000040a4: 0x00000000 sdram_dfii_pi3_wrdata
0x000040b4: 0x00000000 sdram_dfii_pi3_rddata
0x00004800: 0x00000000 rowhammer_enabled
0x00004804: 0x00000000 rowhammer_address1
0x00004808: 0x00000000 rowhammer_address2
0x0000480c: 0x00000000 rowhammer_count
0x00005000: 0x00000000 writer_start
0x00005004: 0x00000001 writer_ready
0x00005008: 0x00000000 writer_count
0x0000500c: 0x00000000 writer_done
0x00005010: 0x00000000 writer_mem_mask
0x00005014: 0x00000000 writer_data_mask
0x00005800: 0x00000000 reader_start
0x00005804: 0x00000001 reader_ready
0x00005808: 0x00000000 reader_count
0x0000580c: 0x00000000 reader_done
0x00005810: 0x00000000 reader_mem_mask
0x00005814: 0x00000000 reader_data_mask
0x00005818: 0x00000000 reader_error_count
0x0000581c: 0x00000000 reader_skip_fifo
0x00005820: 0x00000000 reader_error_offset
0x00005824: 0x00000000 reader_error_ready
0x00006000: 0x00000000 payload_executor_start
0x00006004: 0x00000001 payload_executor_status
0x00006008: 0x00000000 payload_executor_read_count

Also, is mem.py supposed to work?  I am getting this?
$ python ./mem.py
Using generated target files in: ../../build/zcu104
SDRAM initialization:
(ctl) Release reset
(ctl) Bring CKE high
(cmd) Load Mode Register 2, CWL=5
(cmd) Load Mode Register 3
(cmd) Load Mode Register 1
(cmd) Load Mode Register 0, CL=6, BL=8
(cmd) ZQ Calibration
Write leveling:
Cmd/Clk delay: 271
Module 0: delay 9
Module 1: delay 9
Module 2: delay 43
Module 3: delay 49
Module 4: delay 81
Module 5: delay 88
Module 6: delay 127
Module 7: delay 93
Read leveling:
Module 0: bitslip=2, delay=184
Module 1: bitslip=2, delay=184
Module 2: bitslip=2, delay=136
Module 3: bitslip=2, delay=136
Module 4: bitslip=3, delay=368
Module 5: bitslip=3, delay=360
Module 6: bitslip=3, delay=328
Module 7: bitslip=3, delay=296
Memtest (basic)
FAIL: errors = 8192
Memtest (random)
FAIL: errors = 8192

Yes, mem.py should work. Could you try running it with the newest change https://github.com/antmicro/litex-rowhammer-tester/commit/75f7c93d446283a7d672ac073a1de3ec3c560473? It will perform full read leveling, which may take some time over UART, but should fix the problem.
Also, just to be sure, you are using this module :https://github.com/antmicro/litex-rowhammer-tester/blob/master/rowhammer_tester/targets/zcu104.py#L70? (I remember that you said you have that one, but just want to double check).

No luck with the specified commit ID.  I re-verified the part number.  It is the same.  The behaviour of mem.py with and without the memory seems to be identical.
$ python ./mem.py
Using generated target files in: ../../build/zcu104
SDRAM initialization:
(ctl) Release reset
(ctl) Bring CKE high
(cmd) Load Mode Register 2, CWL=5
(cmd) Load Mode Register 3
(cmd) Load Mode Register 1
(cmd) Load Mode Register 0, CL=6, BL=8
(cmd) ZQ Calibration
Write leveling:
Cmd/Clk delay: 271
Module 0: delay 9
Module 1: delay 9
Module 2: delay 43
Module 3: delay 49
Module 4: delay 81
Module 5: delay 88
Module 6: delay 127
Module 7: delay 93
Read leveling:
Module 0
Bitslip 00: |00000000000000000000000000000000|
Bitslip 01: |00000000000000000000000000000000|
Bitslip 02: |00000000000000000000000000000000|
Bitslip 03: |00000000000000000000000000000000|
Bitslip 04: |00000000000000000000000000000000|
Bitslip 05: |00000000000000000000000000000000|
Bitslip 06: |00000000000000000000000000000000|
Bitslip 07: |00000000000000000000000000000000|
Read leveling failed
Module 1
Bitslip 00: |00000000000000000000000000000000|
Bitslip 01: |00000000000000000000000000000000|
Bitslip 02: |00000000000000000000000000000000|
Bitslip 03: |00000000000000000000000000000000|
Bitslip 04: |00000000000000000000000000000000|
Bitslip 05: |00000000000000000000000000000000|
Bitslip 06: |00000000000000000000000000000000|
Bitslip 07: |00000000000000000000000000000000|
Read leveling failed
Module 2
Bitslip 00: |00000000000000000000000000000000|
Bitslip 01: |00000000000000000000000000000000|
Bitslip 02: |00000000000000000000000000000000|
Bitslip 03: |00000000000000000000000000000000|
Bitslip 04: |00000000000000000000000000000000|
Bitslip 05: |00000000000000000000000000000000|
Bitslip 06: |00000000000000000000000000000000|
Bitslip 07: |00000000000000000000000000000000|
Read leveling failed
Module 3
Bitslip 00: |00000000000000000000000000000000|
Bitslip 01: |00000000000000000000000000000000|
Bitslip 02: |00000000000000000000000000000000|
Bitslip 03: |00000000000000000000000000000000|
Bitslip 04: |00000000000000000000000000000000|
Bitslip 05: |00000000000000000000000000000000|
Bitslip 06: |00000000000000000000000000000000|
Bitslip 07: |00000000000000000000000000000000|
Read leveling failed
Module 4
Bitslip 00: |00000000000000000000000000000000|
Bitslip 01: |00000000000000000000000000000000|
Bitslip 02: |00000000000000000000000000000000|
Bitslip 03: |00000000000000000000000000000000|
Bitslip 04: |00000000000000000000000000000000|
Bitslip 05: |00000000000000000000000000000000|
Bitslip 06: |00000000000000000000000000000000|
Bitslip 07: |00000000000000000000000000000000|
Read leveling failed
Module 5
Bitslip 00: |00000000000000000000000000000000|
Bitslip 01: |00000000000000000000000000000000|
Bitslip 02: |00000000000000000000000000000000|
Bitslip 03: |00000000000000000000000000000000|
Bitslip 04: |00000000000000000000000000000000|
Bitslip 05: |00000000000000000000000000000000|
Bitslip 06: |00000000000000000000000000000000|
Bitslip 07: |00000000000000000000000000000000|
Read leveling failed
Module 6
Bitslip 00: |00000000000000000000000000000000|
Bitslip 01: |00000000000000000000000000000000|
Bitslip 02: |00000000000000000000000000000000|
Bitslip 03: |00000000000000000000000000000000|
Bitslip 04: |00000000000000000000000000000000|
Bitslip 05: |00000000000000000000000000000000|
Bitslip 06: |00000000000000000000000000000000|
Bitslip 07: |00000000000000000000000000000000|
Read leveling failed
Module 7
Bitslip 00: |00000000000000000000000000000000|
Bitslip 01: |00000000000000000000000000000000|
Bitslip 02: |00000000000000000000000000000000|
Bitslip 03: |00000000000000000000000000000000|
Bitslip 04: |00000000000000000000000000000000|
Bitslip 05: |00000000000000000000000000000000|
Bitslip 06: |00000000000000000000000000000000|
Bitslip 07: |00000000000000000000000000000000|
Read leveling failed
Memtest (basic)
FAIL: errors = 8192
Memtest (random)
FAIL: errors = 8192
Also, I tried the top of the tree, but I got stuck, because I don't know where to obtain the zcu104.img file.

I merged an update that adds a minimal CPU that will perform the DRAM initialization. It should solve the problem, as I suspect the issues you experience are due to improper write leveling. It will probably be a better solution, especially in terms of maintainability, as we will reuse even more of the infrastructure of LiteDRAM/LiteX.
You will need to re-run make deps and generate a new bitstream. The rest should be the same as before, mem.py script will wait for the CPU to finish. Currently you may see malformed stdout from the CPU, this is most likely due to the way our AXI->WishBone connection works and the way we retrieve UART output from CPU. CPU provides a CSR that we read to retrieve subsequent characters, but as we have a wide AXI bus, each read access actually reads multiple characters from CPU and some of them are dropped. Nevertheless initialization should work correctly, and you should be able to run the rest of the scripts the same as on Arty.

One thing I forgot, you will also need gcc-riscv64 toolchain, on Ubuntu you could install the gcc-riscv64-linux-gnu package, I added a note about it in the README.

mem.py works now.  Thank you for all your help.  I will close this, and complain about something else in a different bug :).


how to test sort ordered collection when dom elements are not same order as visual order

I am curious about this one because it's kind of neat-o that ember collection uses the matrix css property to place dom elements in the visual world, but this makes testing a 'sort ordered' list .. really hard .. is it impossible? Don't know.
Assuming each element in the ember collection kinda looks like this:

Title-1

So Visually, you might see on a page:
Title-1
Title-2
Title-3
and the dom order will be same as visually the first time ember-collection renders and lays the elements out.
Then after doing a few sorts, rerenders .. etc .. you go back to original sort and see:
Title-1
Title-2
Title-3
but when you look at the dom you see the elements are in this order:
Title-2
Title-3
Title-1
so doing a query like:  $('.title') .. to test .. do I have the right order on my titles?  will not work.
I think this is a puzzler of epic proportions ...

Ember collection uses some test helpers currently to do this. I would start there.
https://github.com/emberjs/ember-collection/blob/master/tests/helpers/helpers.js

Holy cow .. those are some fancy a-- test helpers .. that is my ticket to happiness. thanks :)


[HUDI-3116]Add a new HoodieDropPartitionsTool to let users drop table partitions through a standalone job.

https://issues.apache.org/jira/browse/HUDI-3116
Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
(For example: This pull request adds quick-start document.)
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@hudi-bot run azure

@hudi-bot run azure

cc @xiarixiaoyao @nsivabalan  @xushiyan  Could you please take a look at this patch at your convince? Thanks a lot!

this might have to hold until we cleanly fix https://github.com/apache/hudi/pull/4489 . We are discussing on how to do delete partition cleanly here. cleaner has to take care of deleting the partition directory lazily. We will have ocnsensus on how to go about it in few days and then we can come back and fix this PR based on that. What do you think ?

this might have to hold until we cleanly fix #4489 . We are discussing on how to do delete partition cleanly here. cleaner has to take care of deleting the partition directory lazily. We will have ocnsensus on how to go about it in few days and then we can come back and fix this PR based on that. What do you think ?

Agree! Wait for  #4489 fix then let us get this tool landing.
Thanks nsivabalan :)

@nsivabalan Thanks for your attention. Sure I will keep an eye on https://github.com/apache/hudi/pull/4489 and modify this patch as your suggestions.

@zhangyue19921010 : we have landed the other patch. You can let me know once this patch is ready to review again.

@zhangyue19921010 : we have landed the other patch. You can let me know once this patch is ready to review again.

Thanks @nsivabalan I am working on it.

Hi @nsivabalan Sorry to bother you. Just modified this PR as your suggestion.
Now this tool support two kinds of modes: dry_run and delete
Also delete mode will call client.deletePartitions() api creating a replaced commit.
PTAL :)

If you can rebase w/ master and once CI passed, we can land.

Okay, Just merge from master and waiting for ci green :)

Hi @nsivabalan  Sorry to bother you. Is there anything i can do? Or could we land this PR :)

Hello, sorry to trouble you, it seems that there are some test failures, e.g.
/hudi-utilities/src/main/java/org/apache/hudi/utilities/HoodieDropPartitionsTool.java:[359,27] cannot find symbol

for the details: https://github.com/apache/hudi/runs/7189136734?check_suite_focus=true

Hi @f7753 and  @danny0405 PR https://github.com/apache/hudi/pull/6043 fixed this java building issue. PTAL

We may need some instruction on community how to reduce the merging conflicts.

We may need some instruction on community how to reduce the merging conflicts.

In this case, the Java and Azure CI are both green for the PR from quite some time ago and the meta sync has been refactored by then.  However, there are no merging conflicts with the master, yet the API usage is incompatible.  In the future, we should merge the approved PR soon or the PR must be rebased again if the CI runs are stale.


fix: 修复文档 SplitLine 参数错误 close #1836

👀 PR includes

✨ Feature

[ ] New feature

🎨 Enhance

[ ] Code style optimization
[ ] Refactoring
[ ] Change the UI
[ ] Improve the performance
[ ] Type optimization

🐛 Bugfix

[x] Solve the issue and close #0

🔧 Chore

[ ] Test case
[x] Docs / demos update
[ ] CI / workflow
[ ] Release version
[ ] Other ()

📝 Description
🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self-Check before the merge

[x] Add or update relevant docs.
[ ] Add or update relevant demos.
[ ] Add or update test case.
[ ] Add or update relevant TypeScript definitions.

默认就是1呢，0.2和0.25是怎么来的？

 默认就是1呢，0.2和0.25是怎么来的？

cell 的透明度默认是 1，但是 splitLine 分割线的水平和垂直分割线透明度是 0.2 和 0.25

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add bash shell

Installing bash into ansible container prevents this issue:
https://github.com/ansible-community/ansible-vault/issues/151

Hi, why would we need bash if the container relies on sh?

Your container itself doesn't need bash, but you're using
https://galaxy.ansible.com/brianshumate/vault solution, which checks SHA256
for vault binary on one of the setup steps.
If using your container, this step fails with an error:
*TASK [brianshumate.vault : Get Vault package checksum (local)]
****************************************************************************************************************************************************************************************************************fatal:
[server01.consul -> <IP_ADDRESS>]: FAILED! => {"changed": false, "cmd":
"/bin/bash -c 'set -o pipefail\ngrep "vault_1.3.2_linux_amd64.zip"
"/etc/ansible/roles/brianshumate.vault/files/vault_1.3.2_SHA256SUMS" |
awk '"'"'{print $1}'"'"'\n'", "msg": "[Errno 2] No such file or
directory: b'/bin/bash'", "rc": 2}
It means that hashistack.yml playbook run tends to be failed and hosts to
be half-configured.
--
Best regards, Alex Morozenko
чт, 16 квіт. 2020 о 17:51 Marco Lancini<EMAIL_ADDRESS>пише:

Hi, why would we need bash if the container relies on sh?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marco-lancini/offensive-infrastructure/pull/6#issuecomment-614701817,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJ5H5K3RV5XB2EZRSN7E2PTRM4LNTANCNFSM4MI32RUQ
.


Fix dist deploy

Rename the apm-dist artifact id.

Coverage remained the same at 19.473% when pulling 73f108a7de8edaf57a7725df0b0d269bbea3b8de on fix/dist into eee27e0459ebdd60c893027a672ebf3ff0fa6e1c on master.


Try/catch block failing in Jenkins build

Environment
React app, bundled with Webpack, deployed with Jenkins. Using p-limit through terser-webpack-plugin.
Issue
Jenkins build fails with console output:
/path/to/repo/node_modules/terser-webpack-plugin/node_modules/p-limit/index.js:30
		} catch {}
		        ^

SyntaxError: Unexpected token {

Suggestion
I think it's expecting a condition to follow the catch keyword on index.js:30
Perhaps changing the following might work.
try {
  await result;
} catch {}

to
try {
  await result;
} catch (error) {}

Thanks! Please let me know if I can help further

Duplicate of #33


Pre-processing documents in Sphinx Pipeline

I haven't found an obvious preprocessor pipeline for treating documents before Sphinx gets to work on them, but we could create a package to act as a custom handler that will do the preprocessing steps.
For example, Jupyter Book docs suggest:
# The string should be a Python function that will be loaded by: import nbformat.reads
# (additional parameters can then also be passed in)
# The function should take a file’s contents (as a str)
# and return an nbformat.NotebookNode
# https://nbformat.readthedocs.io/en/stable/api.html
sphinx:
  config:
    nb_custom_formats:
        .ipynb:
            - nbformat.reads
            - as_version: 4

I think we can pass extra parameters in the same way as as_version.
The following fragment may also be handy for coding up a notebook preprocessor (the sphinx loader should use nbformat.from_dict(json.loads(nb_body)) as the response, perhaps?)
# Via: https://stackoverflow.com/a/58574138/454773

import json
from traitlets.config import Config
from nbconvert import NotebookExporter
import nbformat

c = Config()
c.TagRemovePreprocessor.enabled=True # Add line to enable the preprocessor
c.TagRemovePreprocessor.remove_cell_tags = ["del_cell"]
c.preprocessors = ['TagRemovePreprocessor'] # Was previously: c.NotebookExporter.preprocessors

nb_body, resources = NotebookExporter(config=c).from_filename('notebook.ipynb')
nbformat.write(nbformat.from_dict(json.loads(nb_body)),'stripped_notebook.ipynb',4)

Docs for creating a custom nbconvert preprocessor here.
The example given is to create the preprocessor class:
from traitlets import Integer
from nbconvert.preprocessors import Preprocessor

class PelicanSubCell(Preprocessor):
    """A Pelican specific preprocessor to remove some of the cells of a notebook"""

    start = Integer(0,  help="first cell of notebook to be converted").tag(config=True)
    end   = Integer(-1, help="last cell of notebook to be converted").tag(config=True)

    def preprocess(self, nb, resources):
        self.log.info("I'll keep only cells from %d to %d", self.start, self.end)
        nb.cells = nb.cells[self.start:self.end]
        return nb, resources

There also looks to be a preprocess_cell method that can be overwritten; presumably, each cell is iterated through and you can then process each cell in turn.
Then configure the pipeline:
# Create a new config object that configures both the new preprocessor, as well as the exporter
c =  Config()
c.PelicanSubCell.start = 4
c.PelicanSubCell.end = 6
c.RSTExporter.preprocessors = [PelicanSubCell]

# Create our new, customized exporter that uses our custom preprocessor
pelican = RSTExporter(config=c)

# Process the notebook
print(pelican.from_notebook_node(jake_notebook)[0])

For processing rich md, such as tagged md cells readable by Jupytext format, we could have a custom .md handler to read the doc into a notebook format using jupytext, then preprocess.
sphinx:
  config:
    nb_custom_formats:
        .Rmd:
            - jupytext.reads
            - fmt: Rmd


discovery: skip chanann validation for assumechanvalid

AssumeChannelValid toggles whether or not the router will verify
signatures for incoming channel announcements. We skip this to increase
performance on low powered devices, and since we are not checking
unspentness of the channel in this mode, they are easily spoofed anyway.

Actually meant to close this after offline discussion, sorry.


Added comments

Codecov Report

Merging #82 into master will decrease coverage by 0.17%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #82      +/-   ##
==========================================
- Coverage    66.8%   66.63%   -0.18%
==========================================
  Files          20       20
  Lines        1175     1175
==========================================
- Hits          785      783       -2
- Misses        351      352       +1
- Partials       39       40       +1

Impacted Files
Coverage Δ

db/batchDeleter/batchDeleter.go
86.84% <ø> (ø)
:arrow_up:

cipher/key_types.go
100% <ø> (ø)
:arrow_up:

db/postgresql/db.go
37.36% <ø> (ø)
:arrow_up:

cipher/boxLoader.go
55.55% <ø> (ø)
:arrow_up:

blacklist/blacklist.go
39.21% <ø> (ø)
:arrow_up:

cipher/loader.go
53.84% <ø> (ø)
:arrow_up:

cipher/cipher.go
76.22% <ø> (ø)
:arrow_up:

db/retry/retry.go
97.59% <ø> (ø)
:arrow_up:

db/batchInserter/batchInserter.go
90.36% <ø> (-2.41%)
:arrow_down:

cipher/rsaLoader.go
50% <ø> (ø)
:arrow_up:

... and 3 more

Continue to review full report at Codecov.

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


Where is the img2video model of Vchitect-2.0?

Hi，it looks only support text2video?

Yes, as we mentioned in README, only the t2v model has been released.


support storage class

currently s3proxy allows x-amz-storage-class but ignores it and subsequent HEAD does not return the storage class. Instead the value should be propagated.

Other providers like Azure, GCS, and Swift support storage policies at the container level instead of the object level like S3.  S3Proxy could special-case storage class for the filesystem and transient providers by storing this in user metadata.

Another frustration is S3Proxy returns it in LIST but not HEAD:
<?xml version='1.0' encoding='UTF-8'?><ListBucketResult<EMAIL_ADDRESS>

AWS head object only returns x-amz-storage-class when it is not STANDARD.

so weird but you are right!

Amazon and Google both support object-level storage classes and Azure has a public preview of this feature.  S3Proxy can add support after jclouds resolves JCLOUDS-1337.


Add BrowserStack cross-platform, cross-browser testing

BrowserStack is free for open source projects, and lets you connect TravisCI to real-devices/browsers and run automated tests.  This would be good for us, since we currently only test in Chrome in CI.  It would be good to make sure Filer works on various browsers/devices per commit.

Doing a bit of research on this, it seems like we'd have to update our tests to work in Selenium, but I'm not 100% sure if that's right.
Some good blog posts on this, https://nehalist.io/selenium-tests-with-mocha-and-chai-in-javascript/ is one.

I've done https://github.com/filerjs/filer/pull/587 instead, which doesn't require redoing all our tests, and gets us running tests in both Firefox and Chrome.  We can revisit this later if we need it.


Support upgrades to the new OVN IC implementation

Update should be supported

when submariner moves from old implementation to new
when Openshift moves from an non-ic to ic version

More changes needs to be done.

Code will be added to operator to cleanup in case of upgrade from Submariner 0.15 to 0.16
Operator will no longer add ovnnb db connect information to daemonset. Instead routeagents will fetch it form their own nodes by themselves on startup. This will allow rollin upgrade of nodes in a cluster from nonIC to IC. Each routeagent will be able to detect which OVN it is using and operator will not have to track node upgrades.
The expectation is that any cluster undergoing upgrade from OCP <4.14 to 4.14 will be unreachable from other clusters because of possible datapath issues while some nodes are IC and others non IC. Connectivity should be restored once all nodes are IC without any extra effort required from user or submariner.


Update codegen for breaking changes in libsyntax

@slapresta Just wanted to ping you before I merge/release this. We were affected by actual breakage, which means I need to bump the version of codegen and macros to 0.9.0. I know you had mentioned maybe wanting to keep them in sync, but I'd like to argue for separating them so that we don't have to bump the version on the main crate unnecessarily. Since codegen/macros are entirely dealt with at compile time, which version of dotenv they use underneath is actually not relevant, and can be separate from the application.

Any update on this? Trying to build with current rust nightly is still failing for me

0.9 should be released and working. I just have forgotten to push to Github but it should be on crates.io

That's cool @sgrif. I just thought it would be less confusing to keep them in sync, but it is also confusing to release empty versions, so I'm fine with it either way.

I'm still only seeing <= 0.8.0 on crates.io

there is no v0.9 on crates.io.

https://crates.io/crates/dotenv_codegen/0.9.0
On Tue, Aug 9, 2016 at 1:20 PM chpio<EMAIL_ADDRESS>wrote:

there is no v0.9 on crates.io.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/slapresta/rust-dotenv/pull/44#issuecomment-238624955,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABdWKzR_fc3X7093KwRlgrQF67urW-0Rks5qeLbmgaJpZM4JJZbn
.


[WIP] Ajaxified system info tabs (task #5460)

Codecov Report

Merging #481 into master will decrease coverage by 0.05%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #481      +/-   ##
============================================
- Coverage     28.23%   28.18%   -0.06%
- Complexity      809      810       +1
============================================
  Files            72       73       +1
  Lines          2787     2792       +5
============================================
  Hits            787      787
- Misses         2000     2005       +5

Impacted Files
Coverage Δ
Complexity Δ

src/Controller/Api/V1/V0/SystemController.php
0% <0%> (ø)
1 <1> (?)

Continue to review full report at Codecov.

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


[jvm-packages] build xgboost4j fail ,no jni.h

hi, i want build XGBoost4J on my machine. i did below steps
1 git clone --recursive https://github.com/dmlc/xgboost
2. cd jvm-packages
3. ./create_jni.sh
after a moment, report error messages:
make[1]: Leaving directory `/home/liyong/test/xgboost/rabit'
g++ -std=c++0x -Wall -O3 -msse2  -Wno-unknown-pragmas -funroll-loops -Iinclude   -Idmlc-core/include -Irabit/include -fPIC -fopenmp -I/include -I./java -I/include/linux -shared -o jvm-packages/lib/libxgboost4j.so jvm-packages/xgboost4j/src/native/xgboost4j.cpp build/logging.o build/learner.o build/common/common.o build/metric/metric.o build/metric/rank_metric.o build/metric/elementwise_metric.o build/metric/multiclass_metric.o build/objective/multiclass_obj.o build/objective/objective.o build/objective/rank_obj.o build/objective/regression_obj.o build/data/sparse_page_dmatrix.o build/data/sparse_page_source.o build/data/sparse_page_writer.o build/data/simple_csr_source.o build/data/data.o build/data/sparse_page_raw_format.o build/data/simple_dmatrix.o build/tree/updater_prune.o build/tree/tree_updater.o build/tree/updater_histmaker.o build/tree/updater_refresh.o build/tree/updater_sync.o build/tree/updater_skmaker.o build/tree/updater_colmaker.o build/tree/tree_model.o build/gbm/gbtree.o build/gbm/gblinear.o build/gbm/gbm.o build/c_api/c_api.o build/c_api/c_api_error.o dmlc-core/libdmlc.a rabit/lib/librabit.a -pthread -lm  -fopenmp -lrt  -lrt
In file included from jvm-packages/xgboost4j/src/native/xgboost4j.cpp:18:0:
jvm-packages/xgboost4j/src/native/./xgboost4j.h:2:17: fatal error: jni.h: No such file or directory
#include <jni.h>
seems jni.h fil not exist. but why?

i have found the reason, my machine jdk version is openjdk, after uninstall openjdk and install jdk1.8 from oracle, build xgboost4j successed.

by the way, what's the main purpose of create_jni.sh ? can i  mvn package directly without run create_ini.sh first ?

even with OpenJDK, you can set JAVA_HOME to your OpenJDK directory, that shall work
create_jni.sh builds the native libs, and copies the native libraries and test resource files to the directory

@CodingCat Maybe we need a instruction in the installation part to explain what create_jni.sh does

yeah, I feel so....on the TODO list today

FYI, now, it only requires to run mvn package under jvm-packages directory to build XGBoost4J....


RFC Aplication process is too hard...

Well... isn't it? I've just gone through Readme.... and it looks like I'm pressured/forced to do all the aplication processing work instead of RFC Repo maintainers... and it does not inspire to propose anything that way!
Please, consider using Issues tab in this Appwrite RFC  repo as primary entry point for new issues and feature requests... that will drastically improve UX, and a good will to get easily involwed and be heard... thanks.

Hey @sshyran you don't have to write the RFC. Feel free to open an issue or discussion on the main Github repo with your idea. If accepted by the team, we can also write the RFC for it. The RFC is used as the final step before implementing new features, and we use it as our spec for actual implementation.

Hey @sshyran  Sorry if the information was misleading 😄 . The RFC process is the final step before implementation of BIG features. You can get an idea of BIG by going through some of our already merged RFCs.
Github issues continue to be the primary place for raising issues, bugs, and even feature requests :)

okay...

So,  if I get it well, this repo is for Maintainers,  then please.... explicitly specify it in Readme!

When/if done - maintainers are welcome to close this issue...

So, if I get it well, this repo is for Maintainers,

@sshyran  Absolutely not 😄  We haven't had any major feature proposal coming in from the community yet hence you see that the RFCs are from maintainers so far. But we definitely want to change that.
Please let us know if there is a feature you'd like to see in Appwrite and we can decide between a Github issue or an RFC for it . Also if you feel you could help improve the README we would love a PR


DefEndAlignment Cop does not autocorrect

Expected behavior
Expected Rubocop to correct the offense to proper style since the cop responds_to :autocorrect
https://github.com/rubocop-hq/rubocop/blob/9a4d88f53305cabbc79cd510ca3fcb6cdb4637df/lib/rubocop/cop/layout/def_end_alignment.rb#L64-L70
Actual behavior
The offense remains as is at the end of session.
Steps to reproduce the problem
# frozen_string_literal: true

def my_method
  'foobar'
  rescue StandardError
   'foobaz'
  end

$ bundle exec rubocop -a test.rb
Inspecting 1 file
W

Offenses:

test.rb:7:3: W: Layout/DefEndAlignment: end at 7, 2 is not aligned with def at 3, 0.
  end
  ^^^

1 file inspected, 1 offense detected

RuboCop version
Include the output of rubocop -V or bundle exec rubocop -V if using Bundler. Here's an example:
$ bundle exec rubocop -V
0.58.2

The auto-correct of this Layout/DefEndAlignment cop is false by default.
https://github.com/rubocop-hq/rubocop/blob/v0.58.2/config/default.yml#L283
It is enabled by setting to true in .rubocop.yml.
Layout/DefEndAlignment:
  AutoCorrect: true

Thank you @koic :+1:

You are welcome!


pip install ethyca-fides fails - cchardet having install issues

Bug Description
pip install ethyca-fides appears to not be working
Steps to Reproduce

Use latest version of python
pip install ethyca-fides

Expected behavior
Fides installs
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

OS: OSX
Python Version: 3.10.8
Docker Version: not applicable

Additional context
After troubleshooting with @sanders41 it appears that in his repro theres an asynchronous postgres driver issue. In Simon's logs:
error: subprocess-exited-with-error
  × Running setup.py install for cchardet did not run successfully.
  │ exit code: 1
  ╰─> [22 lines of output]
      running install
      /Users/simonkeane/fides-2-2-5/venv/lib/python3.10/site-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
        warnings.warn(
      running build
      running build_py
      creating build
      creating build/lib.macosx-12-x86_64-cpython-310
      creating build/lib.macosx-12-x86_64-cpython-310/cchardet
      copying src/cchardet/version.py -> build/lib.macosx-12-x86_64-cpython-310/cchardet
      copying src/cchardet/__init__.py -> build/lib.macosx-12-x86_64-cpython-310/cchardet
      running build_ext
      building ‘cchardet._cchardet’ extension
      creating build/temp.macosx-12-x86_64-cpython-310
      creating build/temp.macosx-12-x86_64-cpython-310/src
      creating build/temp.macosx-12-x86_64-cpython-310/src/cchardet
      creating build/temp.macosx-12-x86_64-cpython-310/src/ext
      creating build/temp.macosx-12-x86_64-cpython-310/src/ext/uchardet
      creating build/temp.macosx-12-x86_64-cpython-310/src/ext/uchardet/src
      creating build/temp.macosx-12-x86_64-cpython-310/src/ext/uchardet/src/LangModels
      clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -Isrc/ext/uchardet/src -I/Users/simonkeane/fides-2-2-5/venv/include<EMAIL_ADDRESS>-c src/cchardet/_cchardet.cpp -o build/temp.macosx-12-x86_64-cpython-310/src/cchardet/_cchardet.o
      xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
      error: command ‘/usr/bin/clang’ failed with exit code 1
      [end of output]
  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure
× Encountered error while trying to install package.
╰─> cchardet

Another issue:
Error response from daemon: invalid mount config for type “bind”: bind source path does not exist: /usr/local/lib/python3.10/site-packages/fides/data/sample_project/privacy_center/config


Config System & Traits

The config system does seem recognise traits.
trait Foobar {
    private static $hello = 'World';
}
class Foo extends Object { use Foobar; }
class Bar extends Object { use Foobar; }

so, the way I see it, both Foo and Bar now the following statement should be true:
Config::inst()->get('hello') === 'World'

but currently is not.
and since statics configs are now also managed by the config system, the same counts for $db, $has_one, ....

Just had a quick look, master now seems to support loading traits and private statics from them (perhaps the PR for replacing the config static parser with reflection enabled that?). The only problem - though not a bug - with using traits to augment config values is that you can’t overwrite/merge things, as they obviously don’t work like extensions do:
trait MyTestTrait {
	private static $db = array(
		'TestField' => 'Varchar(255)'
	);
}

class Page extends SiteTree {
	use MyTestTrait;

	private static $db = array(
		'AnotherField' => 'Varchar'
	);
}

Fatal error: Page and MyTestTrait define the same property ($db) in the composition of Page. However, the definition differs and is considered incompatible.

I know there’s a uservoice ticket for replacing extensions with traits entirely, this is something we’d need to consider if we’re still looking at that option. At the very least I think there’d need to be a change in how we think about extensions and config.

Classes shouldn't inherit config from traits unless the config system is re-thought imo. Its already slow enough trying to merge YAML, class hierarchy, DataExtensions and all the variants (environment type, defined constants, config::update() etc), without adding traits.

Are we happy with the way config is currently working with 4.0? Traits seem to work as-expected (copy of code into parent class) and I agree with @micmania1 that we shouldn't have a magic "merge" from the trait into the parent of overlapping configs, as that's not how traits are meant to work (if I have understood your argument correctly).

I’m happy. I think you’re right - what I was originally suggesting would go against how traits work so forget that


[TACHYON-1700] Improve unit test coverage in tachyon.security.{login, authentication, authorization}

https://tachyon.atlassian.net/browse/TACHYON-1700

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8481/
Test PASSed.

+1 LGTM


Apache PHP mod not present in older Drupal VM release

OS X El Capitan
Virtualbox 5.0.14
Vagrant 1.81

Cloned the repo
Checked out tag 2.1.2
(because of https://github.com/geerlingguy/drupal-vm/issues/357)
Edited drupal.make.yml and config.yml
Created directory on my local system
Ran vagrant

When the build is done I only see below code when I visit http://drupalvm.dev/
<?php

/**
 * @file
 * The PHP page that serves all page requests on a Drupal installation.
 *
 * All Drupal code is released under the GNU General Public License.
 * See COPYRIGHT.txt and LICENSE.txt files in the "core" directory.
 */

use Drupal\Core\DrupalKernel;
use Symfony\Component\HttpFoundation\Request;

$autoloader = require_once 'autoload.php';

$kernel = new DrupalKernel('prod', $autoloader);

$request = Request::createFromGlobals();
$response = $kernel->handle($request);
$response->send();

$kernel->terminate($request, $response);

Looks like php isn't running?
When I ssh into the box I can run
$ php --version
and it gives
PHP 5.6.18-1+deb.sury.org~trusty+1 (cli)

Seems like php module for apache is not running
I did
vagrant@drupalvm:~$ a2query -m php5 No module matches php5
And I can't find it on the list when
apache2ctl -M

If you're using an older version of Drupal VM and want to use PHP with mod_php, you need to explicitly add the package for it in extra installs or in the php_packages list. On mobile so can't easily grab the package name.

It doesn't really make any difference for me if mod_php is used or something else that does the same. But my box isn't working when I follow the instructions right now. If this change always is needed, maybe add it to the repo?
Or am I missing something? =)

If you use the latest version or master of Drupal VM, then PHP-FPM is used by default (for better performance, memory management, easier configuration across Apache or Nginx, etc.).
I have abandoned using mod_php and recommend the same for anyone else :)
Are you on Mac, Linux, or Windows?

Mac, OS X El Capitan

Okay; and do you have Ansible installed? If so, you can run master or the latest tag and it should work properly. Make sure your vhosts are configured with the proxy pass definition as seen in example.config.yml

No I hadn't, so
I installed Ansible
Deleted my old repo for drupal-vm and cloned a new one
Emptied the local storage folder
Ran the setup as instructed on the Quick Start Guide drupal-vm page
The setup worked this time, though
TASK [Generate Drupal site with drush makefile.]
Took a very very long time.

Yeah, that task can take a while the first time you run it :)
Also, I just updated Drupal VM to use its own local provisioner so you don't have to have Ansible installed and you can use master/latest version now.

Thank you for the help!

@banezaka - No problem!


Update saveSolidDatasetAt to correct misleading overwrite statement

Suggested improvement to documentation.
On solidcommunity.net, saveSolidDatasetAt allows you to overwrite the data.  On inrupt.com you have to delete the data first (or fetch first -- I have not tested this yet) and save to overwrite the data.
I think the wording could be improved.

Superseded by https://github.com/inrupt/solid-client-js/pull/1429


Add layout 11 for ALC221 for HP Compaq Pro 4300/Pro 6300/Elite 8300

Realtek ALC221 layout 11 for HP Compaq Pro 4300/Pro 6300/Elite 8300 desktops. Tested and verified working on an Elite 8300 CMT and a Pro 6300 SFF, though it should work with any of the form factors. Tested and verified working on 10.8 Mountain Lion and beyond.
This layout may also work with the HP ProDesk 400 G1, ProDesk 400 G2, ProDesk 600 G1, ProDesk 400 G2, EliteDesk 800 G1, and/or the EliteDesk 800 G2, as those use the same ALC221 and port arrangements. I do not own any of those models, so those remain untested.
Other notes:

IRQs for HPET, etc must be fixed for AppleHDA to detect the codec. This can be done with the FixHPET, FixRTC, and FixTMR in Clover, or by hand.
Internal speaker will stop working after sleep unless CodecCommander or similar is present and configured.

Thanks

Just saw this added to the wiki. The codec does support 10.8 as the minimum version so shouldn't that be listed instead of 10.9?

OK))


slacker.Error message

Installed slack-cleaner via pip without an issue. Goal is to remove all files in the account, however when running the command I get the following feedback:
$ sudo slack-cleaner --token SECRET --file --user "*" --rate=1
Running slack-cleaner v0.3.0
Traceback (most recent call last):
  File "/usr/local/bin/slack-cleaner", line 7, in <module>
    from slack_cleaner.cli import main
  File "/Library/Python/2.7/site-packages/slack_cleaner/cli.py", line 61, in <module>
    init_user_dict()
  File "/Library/Python/2.7/site-packages/slack_cleaner/cli.py", line 52, in init_user_dict
    res = slack.users.list().body
  File "/Library/Python/2.7/site-packages/slacker/__init__.py", line 164, in list
    return self.get('users.list', params={'presence': int(presence)})
  File "/Library/Python/2.7/site-packages/slacker/__init__.py", line 90, in get
    api, **kwargs
  File "/Library/Python/2.7/site-packages/slacker/__init__.py", line 72, in _request
    raise Error(response.error)
slacker.Error: invalid_auth

+1

how did you create the secret token?

Same issue. URL https://api.slack.com/apps/<redacted>/oauth?success=1

Added both user and bot scopes as a troubleshooting step. Tried both bot and user tokens, and with, without --bot.


update monitoringEvent with machineEvent

update monitoringEvent with machineEvent, delete monitoringEventType, update monitoringEvent unitTest

Changes Unknown when pulling ac9f92db9346843b241d29b10c926fa2ca1c4e87 on vfenk:dev into ** on danliris:dev**.


Remove if condition root from rstudio-sparkr chart

Remove the if to be in line with rstudio chart

Hi, thanks for the pr !
Can you please bump the chart version in the Chart.yaml file so that the new chart can be published using github actions ?

Yes sorry, I just did it

I'm going to close this pull request to redo a clean one and no longer be in conflict.


Mat 5927 ratio component rewrite

MADiE PR
Jira Ticket: MAT-5927
(Optional) Related Tickets:
Summary
All Submissions

[x] This PR has the JIRA linked.
[x] Required tests are included
[x] No extemporaneous files are included (i.e Complied files or testing results)
[x] This PR is into the correct branch.
[ ] All Documentation as needed for this PR is Complete (or noted in a TODO or other Ticket)
[ ] Any breaking changes or failing automation are noted by placing a comment on this PR.

DevSecOps
If there is a question if this PR has a security or infrastructure impact, please contact the Security or DevOps engineer assigned to this project to discuss it further.

[x] This PR has NO significant security impact (i.e Changing auth methods, Adding a new user type, Adding a required but vulnerable package)
[ ] All CDN/Web dependencies are hosted internally (i.e MADiE-Root Repo)

Reviewers
By Approving this PR you are attesting to the following:

Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
The tests appropriately test the new code, including edge cases
If you have any concerns they are brought up either to the developer assigned, security engineer, or leads

Before merging, any way we can get the coverage diff up? Our overall test coverage is falling.
npm run coverage can help with identifying coverage gaps with your changes.


FeedAHelp: Possible to Login and Register using 6 different Social login using NextAuth

/Blocked by #76 once that is complete do the following:
Depends on #100

NextAuth.js is a popular authentication library for Next.js applications. It allows you to implement various social logins, but the number of supported social logins may vary depending on the provider support and updates to the library.
As of version 4.0.0 of NextAuth.js, it supported a variety of social providers, including but not limited to:

[ ] Google
[ ] Facebook
[ ] Twitter
[ ] GitHub
[ ] LinkedIn
[ ] Discord

These providers allowed users to log in to your application using their existing social media accounts.
Our nextAuth version: "next-auth": "^4.22.1",


Remove Debian 9 code, since this role does not support Debian 9

🗣 Description
This pull request corrects an erroneous hostname in the inventory section of the molecule configuration.
💭 Motivation and Context
The name of the Debian 9 host is debian9_systemd, not debian9.
🧪 Testing
All pre-commit hooks and molecule tests pass.
🚥 Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (causes existing functionality to change)

✅ Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[x] All new and existing tests passed.

FYI, you have the wrong PR description in here.

FYI, you have the wrong PR description in here.

Fixed.  I am falling apart in my dotage!


Uncaught ReferenceError: GosSocket is not defined

Following javascript client instructions here:
https://github.com/GeniusesOfSymfony/WebSocketBundle/blob/3.x/docs/javascript-client.md
I got this error on my firefox
Uncaught ReferenceError: GosSocket is not defined
This the final html I have (simplified at maximum) is this:

Welcome!

@mbabker  I am also facing the same issue. I am using this plugin first time and got stuck due to this issue. cc: @AbrahamCovelo
This is what I have in my layout.html.twig file:
    <script src="{{ asset('bundles/goswebsocket/js/vendor/autobahn.min.js') }}"></script>
    <script src="{{ asset('bundles/goswebsocket/js/websocket.min.js') }}"></script>
    <script>
     console.log("dd", GosSocket);
    var webSocket = GosSocket.connect('ws://{{ gos_web_socket_server_host }}:{{ gos_web_socket_server_port }}');
    </script>

Change GosSocket to WS and it will work. Using WS is deprecated but it still functions, the documentation must be out of date with the most recent commit.
<script> var websocket = WS.connect('ws://<IP_ADDRESS>:8080'); </script>


[bug report] autocomplete does not work properly

Element UI version
2.13.1
OS/Browsers version
mac/Google Chrome80.0.3987.163
Vue version
2.6.11
Reproduction Link
https://codepen.io/lliuxs/pen/ExVPMaE
Steps to reproduce
1.将官网上的demo中 输入文字  离开
2.autocomplete的离开触发handleChange事件 这里的event应该是el-input的value值 没有target属性 这样会报错
handleChange: function handleChange(event) {
this.$emit('change', event.target.value);
},
Error in v-on handler: "TypeError: Cannot read property 'value' of undefined"
found in
 at packages/input/src/input.vue
 at packages/autocomplete/src/autocomplete.vue

What is Expected?
1.不报错
2.正常显示
What is actually happening?
1.handleChange中的event是value 不是event对象 会报错
2.element大佬应该不会犯这种低级错误 感觉是哪个实习生改的吧 这么重要的项目希望大佬们重视下呀

same problem here

Same here. Found this bug from 2.13.1.
Fix the version to 2.13.0 and wait for the 2.13.2 or later.
Hope it will help !

same problem

same problem

same problem

same problem

same problem

same issue here in 2.13.1.
fixed in 2.13.0.
and waiting for a later version.

+1

+1

+1

+1
自己测试
仿佛是:trigger-on-focus="false"属性影响的，如果不设置的话控制台不会报错

+1

in 2.13.2 issue solved


Only allow scrolling of a scroll pane if it has scroll focus

This PR addresses the issue of a user using the scrollwheel inside a ScrollPane nested inside of another ScrollPane causing both to scroll at the same time. If you look at web browsers and other user interfaces, scrolling a nested scroll pane never scrolls the parent at the same time. Advanced layouts with lots of scrollable content will benefit from this.

I agree the currently scrolling behavior isn't good, only the inner scrollpane should scroll when it has focus.
Normally only the scroll focus actor gets the scroll event. When scrollpanes are nested, the event bubbles up to the parent and it reacts too. Your fix is fine, or it could be fixed using event.cancel(); so the event doesn't reach the parent. The difference is minimal but I think I prefer that, so the logic is done with the event system and doesn't need to check external state.

Thank you so much!


Increase number of CPUs for BPs during test runs

The "zk-apps nonce integration tests" are failing intermittently likely because of the time taken to produce a block. The request is to increase the number of CPUs for these tests from 6 to 10
Slack thread here:
https://o1-labs.slack.com/archives/C02ASV6BZCY/p1679624652155949?thread_ts=1679360104.761129&cid=C02ASV6BZCY

On closer inspection this does not seem like the root cause (CPU resources are not bottle necked on the node in question). Parking this for now.


Add missing directives

All good, thanks.
I'm working on the a new version of the plugin, which will also have the '@stack' directive.

@haidubogdan hi, still missing
https://laravel.com/docs/11.x/blade#session-directives

Sorry, yes, it escaped, I've re-added @session from 2.1.40


How use tsx component in Vuejs project

Hello,
First, thanks for you awesome works !
How can I use Navbar with JS in Nuxtjs project ? Do i need to adapt the react component, or it's possible with other way ?
Thanks for you support.

Hi Sorrow and thanks for the support !
Yes you need to adapt the react component for VueJS.
If you want help don't hesitate to contact me ;)
Charlie

Hi Sorrow and thanks for the support !
Yes you need to adapt the react component for VueJS.
If you want help don't hesitate to contact me ;)
Charlie


Repo's title/name

Please, consider changing this repo's name to Rossmann Time Series Analysis or Time Series Prediction - Rossmann

Ok


use bibtex in plot_time_frequency_global_field_power.py

convert references in examples/time_frequency/plot_time_frequency_global_field_power.py to use footcite / footbibliography

Hi, can I be assigned to this one? I'll work on this


I added the AWI-ESM-2-1 model information; actually, I see that there are also older changes I made that still get committed now. Not sure why is that. Shall I just send the modified version by mail so that the admin can put this into the repo? Kind regards

Before submitting your pull request be sure that:

You haven't deleted any existing information
You haven't eliminated unnecessary blank lines or spaces during your work.
That makes our reviewing work harder and it could introduce unnecessary
conflicts with other pull requests.

Note: You can safely remove this text before submitting your work.

Hi @christian-stepanek we have no AWI-ESM-2-1 registered, so please open a new issue at https://github.com/WCRP-CMIP/CMIP6_CVs/issues/new and spec out the details required. I'll close this PR in preparation.
FYI, we have 5 registered models that list AWI as a contributing institution: AWI-CM-1-1-HR, AWI-CM-1-1-LR, AWI-CM-1-1-MR, AWI-ESM-1-1-LR and MPI-ESM1-2-LR (which lists MPI-M as the primary institution). See CMIP6_source_id.html for all the details


Add error traits for communication interfaces

There has been a lengthy discussion about this in #229.
This implements proposal 3 by @TeXitoi which was the latest for I2C, SPI and Serial interfaces.
See here for the analysis
I included a minimal number of variants for each protocol, mostly borrowed from embedded-error.
This raises the MSRV to Rust 1.40.0 as well in order to mark the ErrorKinds as #[non_exhaustive] so that adding a new variant is not a breaking change.
I am also fine with not marking the ErrorKinds as #[non_exhaustive].

r? @therealprof
(rust-highfive has picked a reviewer for you, use r? to override)

@eldruin Is this in line with the plans of the Rust error handling project group? Haven't had time to check, just making sure that we're not working contrary to what's coming up in upstream Rust...

Good point.
This proposal is simpler than that and only includes the already standard Error::kind() mechanism, without any kind of chaining, which is what the error WG described here.
If we were to offer a mechanism somewhat similar to Error::source, I think we would need to make the errors contain a generic parameter for the source error, which we have already discussed.
Nevertheless, with this proposal users and HALs can continue to create an error chaining mechanism however they like.
The only thing this proposal does is requiring that whatever error type the HAL implementation returns, a mapping to a set of common error variants exists, upon which generic drivers can act.

this seems to me like a good synthesis of the work in the related issue! as with @therealprof i wonder how this aligns with the error-handling WG and existing std:error::Error / failure::Fail infrastructure.
it doesn't seem like it'd be useful to enforce those bounds through our API, but, it might be helpful to add (feature-gated) implementations for either std:error::Error or failure::Fail to our ErrorKinds for if/when they're used directly?

Hmm, ErrorKinds would not be part of the error chain themselves as I do not understand them as a std::error::Error::source().
Rather, the original HAL-defined error types are the sources and those would form the error chain.
What we would add here is requiring that those errors could be translated into a predefined subset: ErrorKinds, similar to std::io::Error.
If those HAL-defined error types implement std::error::Error, they get failure::Error for free IIUC.
I have implemented core::fmt::Display for the ErrorKinds, though. Which I guess could be useful.

Hmm, ErrorKinds would not be part of the error chain themselves as I do not understand them as a std::error::Error::source().
Rather, the original HAL-defined error types are the sources and those would form the error chain.
What we would add here is requiring that those errors could be translated into a predefined subset: ErrorKinds, similar to std::io::Error.

I believe there was talk about allowing ErrorKind to directly be as the HAL error type where it fits for a specific HAL. It's fine to explicitly disallow or discourage this use, but if we would still like to support this then I would ask that std::error::Error be conditionally implemented for ErrorKind.

HALs can indeed use ErrorKind as their error type if that is enough for them. I have implemented the embedded-hal::<protocol>::Error traits for those in this PR.
A different topic would be implementing std::error::Error for ErrorKind as well. That would be an independent addition but only really useful for linux-embedded-hal or so, which I highly doubt would adopt ErrorKind as its protocol error type.
The main point against it being that std::error::Error requires memory allocation so it is uninteresting for no_std HALs.
Anyway if there would really be interest, we could add this in a future release via an opt-in feature, but I would not hold the merge of this since that would be a hypothetical non-breaking addition.

This PR is just waiting for a final review and a quick update to update the change-log, correct?

+1 to having official "error kinds" that generic drivers can react to. This is sorely needed!
Maybe this PR should enforce that the Error associated types impl the Error trait? The original proposal does so.

Maybe this PR should enforce that the Error associated types impl the Error trait? The original proposal does so.

The std::error::Error trait is only in std, not core.

@Dirbaio @yodaldevoid I missed re-adding the Error trait requirement on the associated types today by mistake as I re-did this PR completely on top of the current master branch. Sorry for the confusion.

Still not too much of a fan of the Other kind and would have preferred an ImplError instead as I've done in embedded-error. Anyway, this PR is fine with me.

Should this PR (or #229) be added to the "1.0" milestone, now that it's listed in #177?

Is this still awaiting further reviews?


Michael Monday Alfred

Name
Michael Monday Alfred
Profile Image

Country
Uganda
Region
Wester Nile Rhino Camp refugee settlement
Organisation
No response
Languages
Bari,Arabic, English, lugbara
Skill 1
Open Source & Knowledge
Qualifications for Skill 1
Certificate
Skill 2
No response
Qualifications for Skill 2
No response
Skill 3
No response
Qualifications for Skill 3
No response
Skill 4
No response
Qualifications for Skill 4
No response
describe yourself
Am a refugee in Uganda I have attended a training on the following radio presentation and journalism, prycho socialist.
E-Mail
<EMAIL_ADDRESS>Phone
+256775205230
WhatsApp
+256775205230
Website
No response
Telegram
No response
GitHub
No response
LinkedIn
No response
Twitter
No response
Facebook
No response
Instagram
No response
Mastodon
No response
WikiFab
No response
Other
No response

I'm curious: in the description "prycho socialist" is mentioned. I don't know that, what is it? Or is it a spelling mistake?

I think it's mistake
On Feb 3, 2022 4:20 PM, "MartinSchott" @.***> wrote:
I'm curious: in the description "prycho socialist" is mentioned. I don't
know that, what is it? Or is it a spelling mistake?
—
Reply to this email directly, view it on GitHub
https://github.com/ASKnetCommunity/LEAD/issues/161#issuecomment-1028984004,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXPHJPCEBYMAQR3CVCCXGQDUZJ6I7ANCNFSM5NMSZW5A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

The description here is too short,please members help,I think age ,current place of residence,maybe district,and if a refugee ,from which settlement and simplify prycho socialist, if not spelling error.may add weight to your description @alorogordonpaul  ,can you be of help?


Added Count Down Timer

Developer Checklist

[x] Followed guidelines mentioned in the readme file.
[x] Followed directory structure. (e.g. ProjectName/{USERNAME}/...yourfiles)
[x] Starred ⭐ the Repo (Optional)

Screenshot

@NitkarshChourasia @PBJI @thinkswell pls check and merge

@NitkarshChourasia @PBJI @thinkswell pls check and merge


ESP8266 has solid blue light after flash, no wifi connection

No matter what I do to the firmware code in platform.ini and defines.h (I've tried the website auto writer and manually), every time I flash the code to the board, it absolutely will not connect to my network. I am now 100% sure all the pins are connected and configured correctly in defines.h. I did install the USB to UART driver by Silabs and restarted my PC multiple times in case it needed it (idk).
Some information I know right now:

Board: HiLetgo ESP8266 (NodeMCU V2)
IMU: MPU6050
When the ESP is connected via micro USB, the devices shows in PlatformIO under COM4
upload_port does not come specified in platform.ini on the current commit, so I added it myself with the value COM4
Flashing returns as "SUCCESS"
ESP doesn't connect to WiFi, which I've tried both hardcoding and via SlimeVR Server (which failed)
SlimeVR Server doesn't recognize I2C device on COM4 (assuming it works correctly)

Things I've tried:

Commenting upload_speed
Flashing the firmware stock (defines.h still configured)
Hardcoding WiFi credentials, both on home network and PC hotspot

I swear, the board is just doing nothing, the only time that LED flashes for any reason other than being flashed, is the exact moment I open the port with SlimeVR Server, and that's it. As I said, SlimeVR doesn't recognize, but more specifically: "Can't find an I2C on specified address, scanning for other I2C devices and returning" then I assume it returned with no result.

Update: I flashed a fresh, unwired board and it worked just fine. I suspect I may have damaged the processor of the other board; I touched it a few times with the iron, possibly too long, and another time was that i touched a pin for too long causing heat conduction through that pin and damaging the internals. These are suspicions on my part, but I will try to wire the new one with minimal damage.

Update: I connected a new board to a battery and connected just fine, also turns out the first board did not take any damage. However, connecting an MPU6050 to either of them causes it not to connect to wifi with the same blue light.

Turns out the INT can't be connected tp the ESP8266 when the IMU is an MPU. Thanks, @stardestro#9167 (Discord)


[Feature]: Allow Windows user do not have administrative rights to install/use Node.js

Description of the new feature / enhancement
Some users might not have administrative rights to use their PC especially if they are work for a Enterprise. I hope nvm-windows able to support a way to install/use Node.js without have administrative rights.
Scenario when this would be used?
Many of the Enterprise devs doesn't have administrative rights due to company policies.
Supporting information
No response

NVM4W uses dynamic symlinks to modify which version of Node is active. As a result, you only need permission to create/modify symlinks. In older versions of Windows, Microsoft restricted this to administrative accounts. In newer versions of Windows, you can enable Developer Mode to grant these permissions. Corporations can leverage Active Directory Group Policy to grant users appropriate privileges too.
Regardless, Windows requires these permissions.
For more information on how enterprise developers can use NVM4W now, see common issues - permissions.
Enterprise users should follow the news about Runtime. Runtime is the successor to NVM4W and has been designed with enterprise needs as a top priority.


visionOS support

📚 AppMetrica SDK Version
4.5.2
🛠 Xcode Version
15.4
📱 Device Information
Apple Vision Pro Simulator
⚙ Installation Method
Swift Package Manager
📝 Description
Good afternoon. I'm trying to run the visionOS simulator, but I get an error in the YandexMobile libraries that there is no support for this platform. What can I do to fix this?

🔍 Reproducing the issue

Remove default "Apple Vision (Designed for iPad)"
Add "Apple Vision"
Set Apple Vision Pro simulator and run project
Errors

📋 Relevant AppMetrica Log Output or Crash Logs

Expand to view logs

// Your logs go here

📦 Attach Package.resolved (Swift Package Manager Users)

Click to expand Package.resolved

// Replace with your Package.resolved contents

🍫 Attach Podfile.lock (CocoaPods Users)

Click to expand Podfile.lock

// Replace with your Podfile.lock contents

Hello!
Unfortunately, the 4.x version of the AppMetrica SDK does not support visionOS, and there won't be any updates for this version.
The official 5.x version does not support visionOS through Swift Package Manager or CocoaPods. However, you might try compiling it locally to see if you can get it to work. We are planning to include support for visionOS, but it will only be available in the 5.x version.
Thank you for understanding, and we appreciate your patience!


Added a new option to the plugin

With this option it is now possible to hide the slider while the video is playing.
This feature has been requested by my team for one of our experiments, and I hope it can be added to this plugin for our future experiments.
Please let me know if there is anything else I can do to help make it happen.
Thank you in advance,
Gali Geller

Thanks @gali1998 !
One quick idea and one request:

What about naming the parameter hide_slider_while_playing to be consistent with response_allowed_while_playing?
Would you be willing to implement this in the audio_slider_response plugin as well?

One more thought: I wonder if the button should hide too when the slider is hidden?

Hi @jodeleeuw !
I have already changed the name of the parameter- I will commit it as soon as Github will let me (they seem to have some technical challenges at the moment).
I will add it to the audio plugin as well- this might take me a bit of time.
About the button- this actually came up in our lab meeting as well.
My team thinks the slider is quite distracting, which is why they asked me to remove it while the video is playing. They said that they don't mind the button for now, which is why I haven't removed it yet.
The question is, are the slider and the button always related? I am thinking about a situation where there's a video playing, and the participant can either watch it all (and then rate using the slider), or skip. If I were to conduct an experiment like that I guess it would have been useful to me if the slider and the button weren't attached.
Let me know what you think,
Gali

The question is, are the slider and the button always related? I am thinking about a situation where there's a video playing, and the participant can either watch it all (and then rate using the slider), or skip. If I were to conduct an experiment like that I guess it would have been useful to me if the slider and the button weren't attached.

This makes sense, but I don't think is something that the plugin really supports yet. In the current implementation any response with the button will measure the slider value and add it to the data. Given the lack of a skip feature right now, I think hiding the button with the slider makes sense. I also think the skip feature would be used by researchers less often than the hiding slider feature, so it makes sense as a default option to hide the button when the slider is hidden.

Hi,
Sorry it took me so long- I have hidden the continue button as well, and added the change to the audio slider response plugin as well.
Gali


LimitRange transformer behavior inconsistent with our documentation

Behavior described in docs
If a taskrun is created with resource requirements inconsistent with a limitrange (e.g. requests < min or limits > max),
the resource requirements will be adjusted to fit within the limitrange constraints.
Actual Behavior
If a taskrun is created with resource requirements inconsistent with a limitrange, the resulting pod will fail to schedule.
The pod may also have requests > limits and be invalid.

@skaegi curious about your opinion on whether we should change the docs or the behavior

Even if we decide to allow TaskRuns to fail when they don't meet limitrange requirements, we should definitely stop creating invalid pods. (This happens when e.g. a taskrun's requests are larger than the limitrange max or its limits are smaller than the limitrange min.)

My feeling is that other than the resource spreading algorithm for step "requests" we should not interfere. We should not change the "requests" for init containers or side-car containers, and we should not change "limits" in any containers.
We should create a valid schema-wise pod but don't try to second guess the admin's intent for limitranges and what other policy they might have in place. Let the pod or limitrange errors happen as they would for a Job, Deployment, etc.


keybinding for cancel execution

control-C?

https://github.com/twosigma/beaker-notebook/pull/4458


fixed timeout reporting on server status endpoint

Processing this pull request

Merged into branches master in a1ec5197a27f986cf97ab1fac3c7b1cd62bb64c4

Processing #5935.


Semi-automated way to update icons

I realized that the materialdesignicons were a bit outdated, so I created a semi-automated way to update them.
The way the update works is that you need to download the webfont .zip package from https://materialdesignicons.com/
From that zip, we take two files:

materialdesignicons-webfont.ttf: this file is just placed in kivymd/fonts/ dir, replacing the old one.
preview.html: this file is placed in kivymd/utils/res/ dir.

Next step is to run the script kivymd/utils/parse_icons.py, which will read preview.html and generate a new kivymd/icondefinitions.py file.
If theres something I'm overlooking or this doesn't make much sense, please let me know.

@payala And where is the script for downloading the html file?

@payala Or is it a one-time update?

That's done manually atm, that's why it's not fully automated. Downloading the zip file and placing the .html and .ttf from the zip file in its place is manual.
Generating the icondefinitons.py file is what is automated.
So yeah, it's more like a one time update thing.
It would not be very difficult to fully automate it. But I don't have much time, so I thought it's better to push this today, and we can refine it later.

I don't know how the icondefinitions.py was created in the first place. Maybe there is already a way to generate it and I'm missing it.

@payala Then just make a new pool with updated materialdesignicons-webfont.ttf and icondefinitions.py file.

Ok, but if I leave out the parse_icons.py file and someone wants to update the icons in the future, he would have to find a way to update the icondefinitions.py file.

@payala I can do it. But it should be as automated as possible and run as a single command.

Ok, I will push only those two files and make it a one-time only update.

I think it's done now.

ok, will create another PR.

Sorry, I didn't see that you merged it.


Added event listeners cleanup in the React example

Issue
I noticed that in the React example event listeners are only being added to the anno, but never cleaner. So it may lead to the memory leaks on MockStorage re-renders.
Changes made
Added cleanup function for the existing event listeners. Hopefully, it'll help other devs to immediately use the same pattern in their projects too

Oh-oh... The duplicated event listeners addition may be the issue not only for the example...
In my app that has 2 re-renders in the parent component of the TextAnnotator the selectstart event is being processed 2 times:
https://github.com/recogito/text-annotator-js/blob/054ca425b2957c9184565595ff40bfbd5c26a835/packages/text-annotator/src/SelectionHandler.ts#L64

So now, 2 annotations always painted over each other

I realized why it works that way in my app!

Which brings a questions, why the condition to call the createTextAnnotator is if (setAnno) and not the if (setAnno && !anno)?.. 🤔
I suppose it'll fix the issue with redundant creation of the duplicate annotator instances and event listeners

Good point. Although when the context (which provides setAnno) gets re-mounted, so should the annotation layer I guess. setAnno shouldn't normally change, because its from a state hook in the conetxt. Therefore I believe a cleaner fix would be to destroy anno in a cleanup function that gets returned in the effect hook?
I believe I added an anno.destroy() method meanwhile. That may not yet have existed at the time I started the React binding.

Yeah, destroying the might be the best solution on re-renders. But there's a nuance 😆
https://github.com/recogito/text-annotator-js/blob/054ca425b2957c9184565595ff40bfbd5c26a835/packages/text-annotator/src/TextAnnotator.ts#L86-L88

I think I can try to work on the destroy method tomorrow. As the creation of duplicated annotations blocks me from moving forward 🤷🏻♂
As I won't be able to predictably discard a highlight or delete it

Or, if you already have a vision of how the destroy method should look like for the TextAnnotator, I can proceed with just a ref hack:

You can take a look at what Annotorious does here: https://github.com/annotorious/annotorious/blob/main/packages/annotorious/src/Annotorious.ts
It's basically a matter of housekeeping (like destroying the undo stack, unregistering listeners) plus reverting the DOM manipulations that were made. (Mainly the inserted Canvas elements.) I think both the SelectionHandler and the Highlighter would need their own destroy methods, and then these would be called from the Annotator.

Anyway... I suppose this PR should be reviewed individually. As the change was only for the example and it fixes the duplicated events logs there

Great! And agreed - this PR looks good, independently of the discussion.

Just a quick heads-up: I need to make a few changes to the text annotator & will add a destroy method to the highlightLayer!

Ok, I believe most should be there now. Proper unregistering of listeners + destroying the highlight layer Canvases (not tested though ;-)

Just a quick heads-up: I need to make a few changes to the text annotator & will add a destroy method to the highlightLayer!

Thanks for the heads-up 🙌🏻
Luckily, I haven't started working on the destroy method yet. Yesterday I got sworn into non-anno related tasks

Oh-oh... There might be some bug in the highlighter resing handler now. As the handler gets fired a bazillion time despite the page being fully stating and I'm not even touching anything 👁

All those resize calls were coming from the MutationObserver!

And it main issue is the attributes property in the observe config:

After I removed it - the constant handler calls stopper

Ah, I think I see what's going on. The mutation observer triggers a redraw (as it should). But that also resets the Canvas elements' width and height attributes. Yes, removing the attributes will work. But probably not the final solution. In my use case, I need to redraw the canvas as parent elements in the layout change their size due to style prop changes. So I assume the mutation observer has to listen to all events (incl. attribute changes) but then ignore changes to the drawing canvases. Will require a bit more work...

Quick update on this one: the infinite loop is fixed. (Turned out the solution was easier than thought. I didn't have to do a resize + canvas reset. A simple redraw was totally sufficient, and doesn't cause a DOM mutation which would then throw the observer into an infinite loop.)

Sounds great! Thanks!