Proposal: Revert override of jest default resetMocks

About
Hey what's up!
I found myself trying to work out why all my tests broke when upgrading react-scripts and then realized it's because of the change to enabling resetMocks by default.
I wanted to challenge this decision because, especially when react-scripts is targeted at newer users looking to use react, this causes fundamental jest examples online to break.
App-wide mocks
It also means app-wide mocks such as these don't work.
// some-mocked-module.js
export const useSomeHook = jest.fn(() => true);

// setupTests.js
jest.mock('some-mocked-module', () => ({
  useSomeHook: jest.fn(() => true)
}))

For new users, I can see why it would be very confusing.

This also breaks mock functions in manual mocks

Is it possible to reflect the impact of this change in defaults more explicitly in the release notes?
Manual mocks no longer working send us a bit down the rabbit hole until stumbling on this issue. It is not something one would expect from a change in default settings by upgrading react-scripts from v3 to v4.

@petermylemans I also spent a chunk of time trying to work out the cause - but in fairness, they did document this under breaking changes on the 4.0.0 release.

Jest
We've upgraded to Jest 26 and now set resetMocks to true by default in the Jest config.

Fair enough! That's how I also figured it out.
I was just pointing out that for more basic users like me (and I suspect many other CRA users), the global and manual mocks thing might merrit an explicit mention as well.

is there a way override resetMocks to be false in CRA 4.0? CRA ignores "resetMocks": false in the jest config

@k-yle Are you sure? Adding this to package.json solved it for us using CRA 4.0.1:
  "jest": {
    "resetMocks": false
  }

@lithammer apologies, our issue was caused by a different breaking change in jest 26.
"resetMocks": false does work

The default of false has also tripped people up as well. Our sense is that true is the best starting place to encourage better testing practices. It's one of those settings where not everyone will agree (hence why we make it configurable). See https://github.com/facebook/create-react-app/pull/7899 for more context.
I'll leave this open to gather more feedback. If we were to change it back it wouldn't be until the next major version of CRA.
@kentcdodds thoughts? I know you were in favor of this default.

Resetting a mock will reset it's mock implementation, this could make it confusing if you tried to do this:
beforeAll(() => {
  const originalError = console.error
  jest.spyOn(console, 'error')
  console.error.mockImplementation((...args) => {
    if (args?.[0]?.includes('something to ignore')) return
    originalError(...args)
  })
})

With resetMocks that mock implementation will only work for the first test, then it will get reset. The fix for this would be to require folks to do this:
beforeAll(() => {
  const originalError = console.error
  jest.spyOn(console, 'error')
})

beforeEach(() => {
  console.error.mockImplementation((...args) => {
    if (args?.[0]?.includes('something to ignore')) return
    originalError(...args)
  })
})

That works, but it can be confusing.
However, there are great reasons to get the mocks cleared between runs. So I think I'd suggest using clearMocks: true instead of resetMocks: true. The only big difference is that the mock implementation remains. This comes with its own set of trade-offs though because it means that if I do this:
beforeAll(() => {
  const originalError = console.error
  jest.spyOn(console, 'error')
})

test('some test thing', () => {
  console.error.mockImplementation((...args) => {
    if (args?.[0]?.includes('something to ignore')) return
    originalError(...args)
  })
})

test('some other test thing', () => {
  // with resetMocks, calling console.error will call the underlying console.error always
  // with clearMocks, calling console.error will call the mock implementation in the previous test 😬
})

With that context, I'm not certain which to suggest. I think resetMocks is probably the best between the two, but there are foot guns for both.
Last thing I'd say is that we should configure at least one of them. You never want to have the mock state preserved between tests. So it should at least do clearMocks.

It just feels like it will break any tests using beforeAll() with mocks. Are there plans to deprecate beforeAll() and only use beforeEach()?

See https://github.com/jefflau/jest-fetch-mock/issues/184 for a similar situation. This comment sums it up: https://github.com/jefflau/jest-fetch-mock/issues/184#issuecomment-718058715.
It's an easy enough workaround, but definitely has bigger ramifications than just suggesting people use beforeEach(), because other libraries may depend on the default jest behavior too, not just the tests written in the project.

Definitely agree with using clearMocks instead of resetMocks as the default. I'm all for encouraging better testing practices, but this seems to be also discouraging things that aren't necessarily inferior. What's so bad about providing mock implementations inside jest.mock?
Ran into this when trying to mock react-transition-group, similar to this example: https://testing-library.com/docs/example-react-transition-group/
Only being able to provide .mockImplementation() in beforeEach and not the mock block itself seems unnecessary, and gets awkward with TypeScript, since you lose the jest.Mock type and have to cast it somewhere.

I also agree with using clearMocks instead of resetMocks.
Currently I had to disable this behavior in package.json after upgrading:
"jest": {
  "resetMocks": false
}

and I already have this in every test file:
  afterEach(() => {
    jest.clearAllMocks(); // clear all mock.calls and mock.instances (not implementations)
  });

This helps SOOO much to clear the mocks so I can explicitly test something and make sure the mock calls are correct, but it doesn't break if I want global mock behavior for that test suite, and I don't have to worry about clearing mocks after they're used.
It'd be nice not to need the clearAllMocks in each test file, but I definitely don't want to resetMocks every time

My issue with this is it's taking a strong positive action; removing mocks defined outside of a specific test (__mocks__/** for example) and making it into an implicit behaviour that can only be understood by close examination of the CRA documentation. Seems like a huge beginner/tired programmer trap.
It doesn't help that the Jest documentation for resetMock, (which you would need to know exists in order to realise it could be the cause of mock implementations disappearing) leads to a description with this line in it:

This is useful when you want to completely reset a mock back to its initial state.
[Bold added for emphesis]

To me, that line is quite ambiguous; does it mean the initial implementation of a jest.fn (i.e. nothing) or does it mean the initial implementation of a mock within my code? I appreciate this isn't an issue for everybody, but it seems like taking a change with such a strong impact on tests, making it implicit, and making it different to the Jest default is setting up people for failure. In order to diagnose issues caused by this one would need to:

Intuit that the issue they're having is caused by their mock implementations being reset, and not any other mock inclusion mistake
Know that there's a setting in Jest that causes Mock implementations to be completely wiped between tests
Understand that initial implementation means no implementation
Know that same setting is changed from its default value of false within CRA

I'm positing this here because I was fortunate enough to know 1-3. but without knowing about 4, I lost a number of hours trying to debug this.


Calculating similarity of faces best approach

I am using Stable Diffusion training to generate my own images
Generated over 5k and I want to utilize DeepFace to sort them by most similar to my trained original face image
If you wonder what I mean by this you can check out my below tutorials
Now I made this below script but I am not sure is that the best way to calculate similarity
Can I improve it?
Can I make it use my GPU RTX 3090 ?
1.jpg is my original training image and others are AI generated images
from deepface import DeepFace
import cv2
import os

img1path = "1.jpg"
imgsfolder = "D:/86 se courses youtube kanali/09 face compare/generated_imgs"
models = ['Facenet512'] # list of models to use

# load the first image
img1 = cv2.imread(img1path)

# calculate distance score for each image in the folder
distance_scores = []
count = 0
for filename in os.listdir(imgsfolder):
    if filename.endswith('.jpg') or filename.endswith('.png'):
        try:
            img_path = os.path.join(imgsfolder, filename)
            img2 = cv2.imread(img_path)
            distance_score = DeepFace.verify(img1, img2, model_name=models[0])["distance"]
            distance_scores.append((filename, distance_score))
            count += 1
            print(str(count) + " - "+str( distance_score))
        except Exception as e:
            print("Error occurred while processing "+filename+": "+str(e))

        if count == 5000:
            break

# sort the distance scores in ascending order
distance_scores.sort(key=lambda x: x[1])

# rename the images based on their distance score
for i, (filename, _) in enumerate(distance_scores):
    new_filename = f"{i+1}.png" # rename to 1.png, 2.png, 3.png, ...
    os.rename(os.path.join(imgsfolder, filename), os.path.join(imgsfolder, new_filename))

Here example images
org img

AI images

Also when I use detect image and save in the drive, it is changing direction of image which doesnt make sense
Here example

And here my Stable Diffusion tutorials not related to this question but I am planning a tutorial for DeepFace  for this approach
1.) Automatic1111 Web UI - PC - Free
How To Install Python, Setup Virtual Environment VENV, Set Default Python System Path & Install Git

2.) Automatic1111 Web UI - PC - Free
Easiest Way to Install & Run Stable Diffusion Web UI on PC by Using Open Source Automatic Installer

3.) Automatic1111 Web UI - PC - Free
How to use Stable Diffusion V2.1 and Different Models in the Web UI - SD 1.5 vs 2.1 vs Anything V3

4.) Automatic1111 Web UI - PC - Free
Zero To Hero Stable Diffusion DreamBooth Tutorial By Using Automatic1111 Web UI - Ultra Detailed

5.) Automatic1111 Web UI - PC - Free
DreamBooth Got Buffed - 22 January Update - Much Better Success Train Stable Diffusion Models Web UI

6.) Automatic1111 Web UI - PC - Free
How to Inject Your Trained Subject e.g. Your Face Into Any Custom Stable Diffusion Model By Web UI

7.) Automatic1111 Web UI - PC - Free
How To Do Stable Diffusion LORA Training By Using Web UI On Different Models - Tested SD 1.5, SD 2.1

8.) Automatic1111 Web UI - PC - Free
8 GB LoRA Training - Fix CUDA & xformers For DreamBooth and Textual Inversion in Automatic1111 SD UI

9.) Automatic1111 Web UI - PC - Free
How To Do Stable Diffusion Textual Inversion (TI) / Text Embeddings By Automatic1111 Web UI Tutorial

10.) Automatic1111 Web UI - PC - Free
How To Generate Stunning Epic Text By Stable Diffusion AI - No Photoshop - For Free - Depth-To-Image

11.) Python Code - Hugging Face Diffusers Script - PC - Free
How to Run and Convert Stable Diffusion Diffusers (.bin Weights) & Dreambooth Models to CKPT File

12.) NMKD Stable Diffusion GUI - Open Source - PC - Free
Forget Photoshop - How To Transform Images With Text Prompts using InstructPix2Pix Model in NMKD GUI

13.) Google Colab Free - Cloud - No PC Is Required
Transform Your Selfie into a Stunning AI Avatar with Stable Diffusion - Better than Lensa for Free

14.) Google Colab Free - Cloud - No PC Is Required
Stable Diffusion Google Colab, Continue, Directory, Transfer, Clone, Custom Models, CKPT SafeTensors

15.) Automatic1111 Web UI - PC - Free
Become A Stable Diffusion Prompt Master By Using DAAM - Attention Heatmap For Each Used Token - Word

16.) Python Script - Gradio Based - ControlNet - PC - Free
Transform Your Sketches into Masterpieces with Stable Diffusion ControlNet AI - How To Use Tutorial

17.) Automatic1111 Web UI - PC - Free
Sketches into Epic Art with 1 Click: A Guide to Stable Diffusion ControlNet in Automatic1111 Web UI

18.) RunPod - Automatic1111 Web UI - Cloud - Paid - No PC Is Required
Ultimate RunPod Tutorial For Stable Diffusion - Automatic1111 - Data Transfers, Extensions, CivitAI

19.) RunPod - Automatic1111 Web UI - Cloud - Paid - No PC Is Required
RunPod Fix For DreamBooth & xFormers - How To Use Automatic1111 Web UI Stable Diffusion on RunPod
20.) Automatic1111 Web UI - PC - Free
Fantastic New ControlNet OpenPose Editor Extension & Image Mixing - Stable Diffusion Web UI Tutorial

21.) Automatic1111 Web UI - PC - Free
Automatic1111 Stable Diffusion DreamBooth Guide: Optimal Classification Images Count Comparison Test

22.) Automatic1111 Web UI - PC - Free
Epic Web UI DreamBooth Update - New Best Settings - 10 Stable Diffusion Training Compared on RunPods

23.) Automatic1111 Web UI - PC - Free
New Style Transfer Extension, ControlNet of Automatic1111 Stable Diffusion T2I-Adapter Color Control

24.) Automatic1111 Web UI - PC - Free
Generate Text Arts & Fantastic Logos By Using ControlNet Stable Diffusion Web UI For Free Tutorial

25.) Automatic1111 Web UI - PC - Free
How To Install New DREAMBOOTH & Torch 2 On Automatic1111 Web UI PC For Epic Performance Gains Guide

26.) Automatic1111 Web UI - PC - Free
Training Midjourney Level Style And Yourself Into The SD 1.5 Model via DreamBooth Stable Diffusion

27.) Automatic1111 Web UI - PC - Free
Video To Anime - Generate An EPIC Animation From Your Phone Recording By Using Stable Diffusion AI

28.) Python Script - Jupyter Based - PC - Free
Midjourney Level NEW Open Source Kandinsky 2.1 Beats Stable Diffusion - Installation And Usage Guide

29.) Automatic1111 Web UI - PC - Free
RTX 3090 vs RTX 3060 Ultimate Showdown for Stable Diffusion, ML, AI & Video Rendering Performance

Can I improve it > it seems you did what is required.

Also when I use detect image and save in the drive, it is changing direction of image which doesnt make sense > alignment is an important step for a facial recognition pipeline which totally makes sense. if you set align argument to false, then this step is going to be skipped.

Can I make it use my GPU RTX 3090 > if you install tensorflow-gpu dependency, then it will use gpu directly. but this is tensorflow thing. you may have memory problems in that case (search gpu in closed issues.)

I have installed torch and cuda
what packages do i need to as tensorflow-gpu dependency can you give me direction?
which pip etc?


bug: Cody Pro chat limit does not reset daily data chat messages even though 3 days have passed

version cody: v1.14.0
IDE: Code-Oss
Account: Cody-Pro || @langbach364

i using cody pro and have paid the rental


add: solomon

Description

Related Issues

Changes Proposed

Checklist

[ ] I have read and followed the Contribution Guidelines.
[ ] All new and existing tests passed.
[ ] I have updated the documentation to reflect the changes I've made.
[ ] My code follows the code style of this project.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots
Note to reviewers

@solomonx-star Thank you so much for your contribution! Your efforts are greatly appreciated and will go a long way in improving our project. Please feel free to share it with others and help us grow even further!


layers: Change size of D32_SFLOAT_S8_UINT

Change the size of the other format with 'optional' bytes, to be
consistent with the X8_D24_UNORM_PACK32 change. We'll now assume
the optional bytes when calculating buffer/image sizes for these
formats.
Complement to Tony's PR 1713.
Change-Id: I7c194b85611795cc680f76de04513c3b45a88c4b

Hang on a minute. The X8_D24 case was easy. In almost all cases we special-case this format anyway rather than using the value from FormatSize(), but:

We'll be more conservative in validating total size of the image against VkImageFormatProperties::maxResourceSize in vkCreateImage. This seems "safe" but we'll get false positives on HW that does packed separate stencil. [The check vs maxResourceSize is pretty terrible in general-- at CreateImage time we really don't know what this number should be.]. One might say that if you're operating that close to maxResourceSize you're probably doing something else wrong though...

What about D16_UNORM_S8_UINT? That's currently defined to be 3.

These two cases X8_D24 and D32_S8 are the only ones where the spec contains language about "optional" bits. The D16_S8 case is different because according to spec it is unambiguously 3 bytes.
We were previously assuming the optional bytes were not there (i.e. 3 / 5 bytes size) when computing buffer or image sizes, leading to the possibility of false positive validation failures on copies.  If we pick the larger "optional-bits-included" size we switch to the possibility of false negatives, where the memory area is smaller than we calculate and we miss an overflow. We kicked this around quite a while here until settling on the latter as the better option - with neither being especially good.
The whole idea of listing 'optional' format bits in the spec is a nightmare IMO.  I asked the WG for a clarification (https://gitlab.khronos.org/vulkan/vulkan/issues/768), but didn't get a clear answer back.

Ok, sounds good to me.
On May 2, 2017 10:35 AM, "Dave Houlton"<EMAIL_ADDRESS>wrote:

These two cases X8_D24 and D32_S8 are the only ones where the spec
contains language about "optional" bits. The D16_S8 case is different
because according to spec it is unambiguously 3 bytes.
We were previously assuming the optional bytes were not there (i.e. 3 / 5
bytes size) when computing buffer or image sizes, leading to the
possibility of false positive validation failures on copies. If we pick the
larger "optional-bits-included" size we switch to the possibility of false
negatives, where the memory area is smaller than we calculate and we miss
an overflow. We kicked this around quite a while here until settling on the
latter as the better option - with neither being especially good.
The whole idea of listing 'optional' format bits in the spec is a
nightmare IMO. I asked the WG for a clarification (
https://gitlab.khronos.org/vulkan/vulkan/issues/768), but didn't get a
clear answer back.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KhronosGroup/Vulkan-LoaderAndValidationLayers/pull/1715#issuecomment-298705930,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH3bYGSjVXAQNMH9aW2iTcgz11ZBNnaks5r12lIgaJpZM4NL7Mc
.


Change .Platform$GUI to vscode on session start

This PR replaces .Platform$GUI to vscode for user to check. By default, .Platform$GUI is X11 under linux and macOS, which is not the case when init.R is sourced and all viewer are handled by vscode-R.
This is also similar with RStudio which replaces .Platform$GUI with RStudio.

@renkun-ken This looks correct to me. Is there anything in particular I should test?

Just a minor change. The only thing to test is whether init.R could be successfully sourced and whether .Platform$GUI is successfully changed to vscode.
I tested it on macOS and Linux and it works as expected.

Great, I will verify on Windows later today.


Allow metrics update to be tolerant to uninitalized metric containers.

This preserves the behavior before PR #10044.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Run Python PostCommit


Flat fees for IBC transactions

Background
IBC relayers are paying the gas price of the destination chain, and with the volume of Osmosis, relayer can perform thousands of transactions per day. The introduction of minimum gas fees that many validators have done to fight 0fee spam transactions, relayers face problem of choosing gas fees that will get included into block fast but does not end up costing too much. And this is very hard when validators have min gas prices varying a lot.
Suggested Design
I suggest that we set a flat for IBC transactions, similar to what is done with arbitrage fees. This IBC fee can be set to 0 or small fee that still guarantees that IBC transactions are included into block rapidly. This would take the balancing/guessing game out of setting the relayer fees.
Acceptance Criteria

[ ] IBC transactions are accepted with flat fee

Hey sorry this went without a reply for so long.
Theres an overarching issue of chain DOSability in this regard, IBC txs are actually the most computationally expensive per byte, due to the amount of signature verifications involved in their verification today.
I think what I'd like to do is have an adaptive fee market with a base fee, and have IBC txs perhaps get a small reduction in base fee they have to pay.
My suggested direction for this would be to get high level alignment on adaptive fee market design (and that we will likely need to trial and error a lot), and get that integrated. Then secondly, later-on consider "reduction" costs for things like relaying. TBH, I think focus on making the batch signature verification cheaper may be an easier time/utility tradeoff though.
WDYT?


Listen on socket instead of port?

I have an elixir app running on prod and it currently listens on port 8000 and I have an nginx running on port 80. The elixir app is available both on domainname.com and domainname.com:8000 if someone directly connects to the cowboy port.
Since, I intend to run many webapps on the same server, I need nginx to use vhosts + others. Is it possible to use have cowboy listen to a socket so that it's not directly accessible over direct urls? If so, how would I go about configuring it?
Thanks

If by socket you mean unix domain socket, then it's not possible directly in Erlang today, and the most informative place about this is this ticket: https://github.com/erlang/otp/pull/612 -- it also has some workarounds.
If you do manage to open one from Erlang, then you can pass it to Cowboy using the 'socket' transport option.

You can also have your application listen only to localhost by passing {ip, {127,0,0,1}} or {ip, {0,0,0,0,0,0,0,1}} as part of the transport options (third argument of cowboy:start_http).

thanks @essen, yes I mean unix domain socket.
thakns @acammack. This should at least solve my immediate need of not having my app available to public on cowboy port used by nginx.

Closing, cheers!

@essen

If you do manage to open one from Erlang, then you can pass it to Cowboy using the 'socket' transport option.

Can you please explain how to do that or point me to any docs regarding this ?

See the Ranch manual.

From https://groups.google.com/forum/#!topic/phoenix-talk/dV94pYLvdx8
config :hello_phoenix, HelloPhoenix.Endpoint,
  http: [port: 0, ip: {:local, "/tmp/phoenix"}]

works in Phoenix 1.2.x, but not in 1.3.0-rc

What's the status on this with the latest Phoenix version?

I read https://github.com/erlang/otp/pull/612 and couldn't really tell what the outcome was.
Is this possible yet?

Yes they've added support for unix sockets a while back. I haven't tried it personally.

@cjbottaro It works by simply passing {local, Path} as address. Haven't tried on cowboy per se but it works on Ranch which cowboy is based on.


Support STM32L4P5CETx

This is a naive attempt to add support for the STM32L4P5CETx, the brother to the STM32L4P5CGTx.
The only relevant difference I've been able to find between the two is that the CETx now has 512KB of RAM, rather than 1MB.
I also take the opportunity to fix the RAM mapping of the CGTx. Again, let me know if there's a specific reason why it is at 0x20020000.
I submit this because I'm trying to use cargo embed on the CETx, but hitting the error below still after having made the changes I'm pushing here. I'm totally able to run a dummy executable on it, but when I go to a bigger executable, it crashes like this. So I first want to get some feedback on those potential changes before investigating other avenues as the source of this problem.
Thanks for your time and your review.
       DEBUG probe_rs_cli_util > Running '/home/yellowcar/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/bin/cargo' in directory /home/yellowcar/code/validating-lightning-signer/embedded
    Finished dev [optimized + debuginfo] target(s) in 0.07s
warning: unused import: `cortex_m_semihosting::hprintln`
  --> src/tests.rs:11:5
   |
11 | use cortex_m_semihosting::hprintln;
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default
help: consider adding a `#[cfg(test)]` to the containing module
  --> src/main.rs:7:1
   |
7  | mod tests;
   | ^^^^^^^^^^

warning: unused import: `hprintln`
 --> src/entry.rs:8:35
  |
8 | use cortex_m_semihosting::{debug, hprintln};
  |                                   ^^^^^^^^

warning: 2 warnings emitted

      Config default
      Target /home/yellowcar/code/validating-lightning-signer/embedded/target/thumbv7em-none-eabihf/debug/embedded
       DEBUG probe_rs::probe::cmsisdap::tools > Searching for CMSIS-DAP probes using libusb
       DEBUG probe_rs::probe::cmsisdap::tools > Found 0 CMSIS-DAP probes using libusb, searching HID
       DEBUG probe_rs::probe::cmsisdap::tools > Found 0 CMSIS-DAP probes total
       DEBUG jaylink                          > libusb <IP_ADDRESS>84
       DEBUG jaylink                          > libusb has capability API: true
       DEBUG jaylink                          > libusb has HID access: true
       DEBUG jaylink                          > libusb has hotplug support: true
       DEBUG jaylink                          > libusb can detach kernel driver: true
       TRACE probe_rs::probe::cmsisdap::tools > Attempting to open device matching 0483:3748:55C3BF6A06C283C288575533430967
       TRACE probe_rs::probe::cmsisdap::tools > Trying device Bus 002 Device 001: ID 1d6b:0003
       TRACE probe_rs::probe::cmsisdap::tools > Error opening: Access
       TRACE probe_rs::probe::cmsisdap::tools > Trying device Bus 001 Device 003: ID 0408:5365
       TRACE probe_rs::probe::cmsisdap::tools > Error opening: Access
       TRACE probe_rs::probe::cmsisdap::tools > Trying device Bus 001 Device 002: ID 0bda:b00c
       TRACE probe_rs::probe::cmsisdap::tools > Error opening: Access
       TRACE probe_rs::probe::cmsisdap::tools > Trying device Bus 001 Device 008: ID 0483:3748
       TRACE probe_rs::probe::cmsisdap::tools > Trying device Bus 001 Device 004: ID 0461:4e22
       TRACE probe_rs::probe::cmsisdap::tools > Error opening: Access
       TRACE probe_rs::probe::cmsisdap::tools > Trying device Bus 001 Device 001: ID 1d6b:0002
       TRACE probe_rs::probe::cmsisdap::tools > Error opening: Access
       DEBUG probe_rs::probe::cmsisdap::tools > Attempting to open 0483:3748 in CMSIS-DAP v1 mode
       DEBUG probe_rs::probe::stlink::usb_interface > Acquired libusb context.
       DEBUG probe_rs::probe::stlink::usb_interface > Aquired handle for probe
       DEBUG probe_rs::probe::stlink::usb_interface > Active config descriptor: ConfigDescriptor { bLength: 9, bDescriptorType: 2, wTotalLength: 39, bNumInterfaces: 1, bConfigurationValue: 1, iConfiguration: 0, bmAttributes: 128, bMaxPower: 50, extra: [] }
       DEBUG probe_rs::probe::stlink::usb_interface > Device descriptor: DeviceDescriptor { bLength: 18, bDescriptorType: 1, bcdUSB: 512, bDeviceClass: 0, bDeviceSubClass: 0, bDeviceProtocol: 0, bMaxPacketSize: 64, idVendor: 1155, idProduct: 14152, bcdDevice: 256, iManufacturer: 1, iProduct: 2, iSerialNumber: 3, bNumConfigurations: 1 }
       DEBUG probe_rs::probe::stlink::usb_interface > Claimed interface 0 of USB device.
       DEBUG probe_rs::probe::stlink::usb_interface > Succesfully attached to STLink.
       DEBUG probe_rs::probe::stlink                > Initializing STLink...
       TRACE probe_rs::probe::stlink                > Getting current mode of device...
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f5] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 2 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                > Current device mode: Jtag
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f1] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 6 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                > STLink version: (2, 37)
        INFO cargo_embed                            > Protocol speed 1800 kHz
       DEBUG probe_rs::config::registry             > Searching registry for chip with name STM32L4P5CETx
       DEBUG probe_rs::config::registry             > Exact match for chip name: STM32L4P5CETx
       DEBUG probe_rs::probe::stlink                > attach(Swd)
       TRACE probe_rs::probe::stlink                > Getting current mode of device...
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f5] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 2 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                > Current device mode: Jtag
       DEBUG probe_rs::probe::stlink                > Switching protocol to SWD
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f7] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 8 bytes, 0 bytes remaining
        INFO probe_rs::probe::stlink                > Target voltage (VAPP): 3.24 V
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 30, a3, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 2 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                > Successfully initialized SWD.
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 43, 1] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 2 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Reading register IDR
       DEBUG probe_rs::probe::stlink                > Opening AP 0
       TRACE probe_rs::probe::stlink                > JTAG_INIT_AP 0
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 4b, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 2 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 45, 0, 0, fc, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 8 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Read register    IDR, value=0x24770011
       DEBUG probe_rs::architecture::arm::ap        > Reading register IDR
       DEBUG probe_rs::probe::stlink                > Opening AP 1
       TRACE probe_rs::probe::stlink                > JTAG_INIT_AP 1
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 4b, 1] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 2 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 45, 1, 0, fc, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 8 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Read register    IDR, value=0x0
       DEBUG probe_rs::architecture::arm::ap        > Reading register IDR
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 45, 0, 0, fc, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 8 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Read register    IDR, value=0x24770011
       DEBUG probe_rs::architecture::arm::ap        > Reading register BASE
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 45, 0, 0, f8, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 8 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Read register    BASE, value=0xe00ff003
       DEBUG probe_rs::architecture::arm::ap        > Reading register BASE2
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 45, 0, 0, f0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 8 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Read register    BASE2, value=0x0
       DEBUG probe_rs::architecture::arm::ap        > Reading register CSW
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 45, 0, 0, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 8 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Read register    CSW, value=0x23000052
       DEBUG probe_rs::architecture::arm::ap        > Writing register CSW, value=CSW { DbgSwEnable: 1, HNONSEC: 1, PROT: 6, CACHE: 3, SPIDEN: 0, _RES0: 0, MTE: 0, Type: 0, Mode: 0, TrinProg: 0, DeviceEn: 0, AddrInc: Single, _RES1: 0, SIZE: U8 }
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 46, 0, 0, 0, 0, 10, 0, 0, e3] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 2 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Reading register CSW
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 45, 0, 0, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 8 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::ap        > Read register    CSW, value=0x23000050
       DEBUG probe_rs::architecture::arm::ap        > Writing register CSW, value=CSW { DbgSwEnable: 0, HNONSEC: 0, PROT: 2, CACHE: 3, SPIDEN: 0, _RES0: 0, MTE: 0, Type: 0, Mode: 0, TrinProg: 0, DeviceEn: 1, AddrInc: Single, _RES1: 0, SIZE: U32 }
       TRACE probe_rs::probe::stlink::usb_interface > Sending command [f2, 46, 0, 0, 0, 0, 52, 0, 0, 23] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface > Read 2 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::communication_interface > HNONSEC supported: false
       DEBUG probe_rs::probe::stlink                              > AP ApAddress {
    dp: Default,
    ap: 0x0,
}: MemoryAp(MemoryApInformation { address: ApAddress { dp: Default, ap: 0 }, only_32bit_data_size: false, debug_base_address:<PHONE_NUMBER>, supports_hnonsec: false })
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e000edf0, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, f0, ed, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::sequences               > Core is already in debug mode, no need to enable it again
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e000edf0, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, f0, ed, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e000ed30, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 30, ed, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::architecture::arm::core::armv7m            > Core was halted when connecting, reason: Unknown
       TRACE probe_rs::probe::stlink                              > write_mem_32bit
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 8, 30, ed, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Wrote 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > USB write done!
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002000, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 0, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002000, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 0, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002008, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 8, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002000, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 0, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e000200c, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, c, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002000, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 0, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002010, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 10, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002000, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 0, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002014, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 14, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002000, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 0, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002018, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 18, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e0002000, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 0, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       DEBUG probe_rs::probe::stlink                              > Read mem 32 bit, address=e000201c, length=4
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 7, 1c, 20, 0, e0, 4, 0, 0] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 4 bytes, 0 bytes remaining
       TRACE probe_rs::probe::stlink::usb_interface               > Sending command [f2, 3e] to STLink, timeout: 1s
       TRACE probe_rs::probe::stlink::usb_interface               > Read 12 bytes, 0 bytes remaining
       Error failed to flash /home/yellowcar/code/validating-lightning-signer/embedded/target/thumbv7em-none-eabihf/debug/embedded

             Caused by:
                 0: Error while flashing
                 1: The execution of 'program_page' failed with code 1. This might indicate a problem with the flash algorithm.

Rebase: add changelog entry.

I also take the opportunity to fix the RAM mapping of the CGTx. Again, let me know if there's a specific reason why it is at 0x20020000.

The RAM mappings are usually automatically extracted from CMSIS-Pack files, which are provided by ARM or STM. It can very well be that there are mistakes in those files.
The error code you get indicates that the flash algorithm encountered an error, but unfortunately this doesn't tell us much. The flash algorithms are also extracted, so we don't have any information about what the algorithm does. Do you have any indication if this happen at a specific binary size, which is maybe at the boundary of some flash sector?
It might also be worth it to check if there is a new CMSIS-Pack file which supports STM32L4P5CETx, and then extracting the target description file using the target-gen tool. Maybe that works better. See https://probe.rs/docs/knowledge-base/cmsis-packs/ for more details.

Hey could you check if #1086 fixes your issue to? :)

@Yatekii thanks for the ping! That PR hasn't fixed it as far as I can see so far.
I made the following diff on a local cargo-embed repo:
diff --git a/Cargo.toml b/Cargo.toml
index b890c44..4dc341b 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -18,10 +18,10 @@ ftdi = ["probe-rs/ftdi"]
 sentry = ["probe-rs-cli-util/sentry"]

 [dependencies]
-probe-rs = { version = "0.12.0", git = "https://github.com/probe-rs/probe-rs" }
-gdb-server = { version = "0.12.0", git = "https://github.com/probe-rs/probe-rs"  }
-probe-rs-cli-util = { version = "0.12.0", git = "https://github.com/probe-rs/probe-rs", default-features = false, features=["anyhow"] }
-probe-rs-rtt = { version = "0.12.0", git = "https://github.com/probe-rs/probe-rs" }
+probe-rs = { git = "https://github.com/probe-rs/probe-rs.git", branch = "master" }
+gdb-server = { git = "https://github.com/probe-rs/probe-rs.git", branch = "master" }
+probe-rs-cli-util = { git = "https://github.com/probe-rs/probe-rs.git", branch = "master" }
+probe-rs-rtt = { git = "https://github.com/probe-rs/probe-rs.git", branch = "master" }

 git-version = "0.3.5"
 env_logger = "0.9.0"

Then launched cargo install --path ., and confirmed that the probe-rs crates where pulling the latest commit d44e174
Then I get the same error again, with the progress bars as shown below ( I do seem to be breaking when crossing into another bank ):
     Erasing sectors ✔ [00:00:15] [#################################################] 424.00KiB/424.00KiB @ 88.55KiB/s (eta 0s )
 Programming pages   ✔ [00:00:10] [##############################-------------------] 258.00KiB/424.00KiB @ 16.56KiB/s (eta 0s )
       Error failed to flash /home/yellowcar/code/validating-lightning-signer/embedded/target/thumbv7em-none-eabihf/debug/embedded

             Caused by:
                 0: Error while flashing
                 1: The execution of 'program_page' failed with code 1. This might indicate a problem with the flash algorithm

Now that support for the CETx has been pulled in, let me know if you'd like me to close this PR and open a proper issue :)
Thanks again for the help here.

Hey, sorry for letting this rot so long. Support for the CETx  has been pulled in, so I'll close this, but feel free to open any issue if this is persisting :)


WIP: feedback from my current project

I opened this as a direct feedback channel for every component import I create in my current project.
I included a clone of the repo as a git sub-module in my project and use the currently available component import through files. Also, I wasn't able to use the imports from NuGet package.

thank


order following by... not found

What happened:
The order button to order the people I am following in a descending order is not found and thus gramaddict continue without sorting the following 's list.
What you expected to happen:
It should be able to find the ordering button by itself.
How to reproduce it (as minimally and precisely as possible):
Just start an unfollow action
Anything else we need to know?:
By looking at what it is doing, it happens because after entering the following's page, gramaddict swipe down too far and the sorting button is then out of screen over the top.
By manually swiping up myself, gramaddict is able to find the sorting button and use the sorting option correctly.
I tried modifying the resolution and dpi, it doesn't correct the problem.
Environment:

GramAddict version: v1.2.0
Device Model/Emulator Type: AVD
Android Version: 8.0
Instagram Version: <IP_ADDRESS>.116

Relevant Logs:

Hold on, I fixed that like 4 months ago.. Unfortunately, we had some trouble with the organization.. I'll release something new soon.. Join discord in the meantime.

Same error here. Any Solution?

That problem was from version 1.2.. are you using the 2.0.9 ?

Yes version 2.0.9

Well, it can't be the same error, it can have the same behavior.
I need a description of what the console says in debug mode (debug: true  in config file / --debug in console) and that you describe to me what's going on with your eyes (or you can record a video (screen-record: true / --screen-record) but that needs you to install some dependencies.
imageio-ffmpeg
websocket-client
websocket
imageio
opencv-python

Up to you.
Don't paste your personal information there (github), you can open a ticket on discord if you need to.

I attached you the console output as screenshots (debub mode enabled). The script crashes after pressing the sorting button.

Should I open a seperate issue for this?

I attached you the console output as screenshots (debub mode enabled). The script crashes after pressing the sorting button.

Should I open a seperate issue for this?

No it is OK. Can you send me that crash report? (the line in green show you the name)
Before sending you can remove your nickname inside that if you want to.. Or send me in discord


Add support for FluentIterable

Having fluent iterable support would be great :)

It is actually a good idea although I will check it out first and see if not many guava dependencies are required in order to make it work. I do wanna keep the library tiny for the moment.
Closing the issue. I will add a "nice to have features" milestone. Thanks!


Replace OSGI and Felix with pf4j

Issue Description
We have faced enough issues with Felix and OSGI. The most awesome PR #110 is left unmerged because of the OSGI  class loader issue. The learning curve is steep for Felix (We have our felix expert inactive for a while). Lets put this to an end - get rid off all xmls and configs (use convention over configuration)
pf4j seems like a better fit. So lets swap felix with pf4j and then make way to merge #110.

Why not have a look at OSGi Declarative Services.
You cant get rid of (probably all) your Activators in the project. The annotations provided by DS are only build-time (yes they produce xml, but no developer has to care about them) and it is as easy as CDI in JavaEE (just more powerfull).
Another nice benefit, you dont force any constraints on the plugins except OSGi itself. You can cleanup your code without affecting any existing plugin.

Thanks. I will have a look at the Declarative Services. Seems like a good one.

The first major issue with maven-bundle-plugin is that it replaces Maven’s default plugin for JAR generation (the maven-jar-plugin). This means that it must use a different packaging type – “bundle” instead of “jar” – and must use the extensions=true setting to override Maven’s default lifecycle. As a result, the output artifacts are harder to consume in ordinary non-OSGi projects. Therefore, many Maven developers either don’t bother to release OSGi bundles at all because of the hassle, or they release both a “plain JAR” and a separate OSGi bundle. This is deeply frustrating because OSGi bundles already are plain JARs!… they can be used unalterered in non-OSGi applications.

Woah, someone explained my pain precisely. Thanks again.


[Bug] StorageReferenceInternal::GetFile path argument is not copied

[REQUIRED] Please fill in the following fields:

Pre-built SDK from the website
Firebase C++ SDK version: 11.9.0
Problematic Firebase Component: Storage
Other Firebase Components in use: Auth, App, Analytics, Remote Config, Dynamic Links
Platform you are using the C++ SDK on: Mac
Platform you are targeting: iOS

[REQUIRED] Please describe the issue here:
The argument path of StorageReferenceInternal::GetFile is not copied and passed verbatim as a pointer to another thread in:
download_task = [my_impl writeToFile:[NSURL URLWithString:@(path)] completion:completion];
This would not work if path was passed from a C++ temporary and the expectation that the caller must ensure the lifetime of path supersedes the download time is unrealistic. Most developers would expect path to be copied if you need to carry it to another thread.
Stack trace during EXC_BREAKPOINT (code=1, subcode=0x1bc5fa4b0) as it processes garbage after temporary:
#0	0x00000001bc5fa4b0 in static URL._unconditionallyBridgeFromObjectiveC(_:) ()
#1	0x00000001064caf5c in @objc StorageReference.write(toFile:completion:) ()
#2	0x0000000101c6622c in invocation function for block in firebase::storage::internal::StorageReferenceInternal::GetFile(char const*, firebase::storage::Listener*, firebase::storage::Controller*) at /Users/me/Projects/firebase-cpp-sdk/storage/src/ios/storage_reference_ios.mm:149
#3	0x00000001067ac08c in _dispatch_call_block_and_release ()
#4	0x00000001067ad8c4 in _dispatch_client_callout ()
#5	0x00000001067bc428 in _dispatch_main_queue_drain ()
#6	0x00000001067bc080 in _dispatch_main_queue_callback_4CF ()
#7	0x00000001c2013828 in __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ ()
#8	0x00000001c1ff74a8 in __CFRunLoopRun ()
#9	0x00000001c1ffbb58 in CFRunLoopRunSpecific ()
#10	0x00000001f81fb984 in GSEventRunModal ()
#11	0x00000001c43a6628 in -[UIApplication _run] ()
#12	0x00000001c43a62a0 in UIApplicationMain ()
#13	0x0000000100ea697c in main at /Users/me/path/to/main.m:24
#14	0x00000001decc5df0 in start ()
Enqueued from com.apple.NSXPCConnection.m-user.com.apple.ondemandd.client (Thread 5) Queue : com.apple.NSXPCConnection.m-user.com.apple.ondemandd.client (serial)
#0	0x00000001067b1dc0 in dispatch_async ()
#1	0x0000000101cb8708 in firebase::util::DispatchAsyncSafeMainQueue(void () block_pointer) ()
#2	0x0000000101c65c58 in firebase::storage::internal::StorageReferenceInternal::GetFile(char const*, firebase::storage::Listener*, firebase::storage::Controller*) at /Users/me/Projects/firebase-cpp-sdk/storage/src/ios/storage_reference_ios.mm:145
#3	0x0000000101c5af6c in firebase::storage::StorageReference::GetFile(char const*, firebase::storage::Listener*, firebase::storage::Controller*) at /Users/me/Projects/firebase-cpp-sdk/storage/src/common/storage_reference.cc:150
#4	0x0000000100b35fa0 in start_download(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&,std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) at my/path/myfile.cpp:3967

Steps to reproduce:
No. Your Firebase C++ quickstarts is useless in reproducing real-world issues as it busy-waits after each call, hiding all the multi-threading issues you guys have. This is just one of them, more to follow. Rewrite it to include multi-threading scenarios.
What's the issue repro rate? 100%
Just use the following function to reproduce the problem:
Relevant Code:
void start_download(const std::string& local_path, const std::string& remote_path)
{
    firebase::storage::StorageReference path_reference = firebase::storage::Storage::GetInstance(::firebase::App::GetInstance())->GetReference(remote_path);
    path_reference.GetFile(("file://" + local_path).c_str(), listener.get(), &listener->m_controller); // Temporary ("file://" + local_path) is destroyed after ;
}

Never mind, Objective-C blocks seem to handle that differently. The actual error I was getting was that local file url was not url encoded (e.g. it had spaces in the path).
I'm still getting an error upon second download of the same file, which seems to be in Firebase code not specifying file:// when deleting previous temporary:
2024-04-18 00:33:49.256306-0700 Metal-App-mobile[6336:956788] CFURLCopyResourcePropertyForKey failed because it was passed a URL which has no scheme
2024-04-18 00:33:49.258400-0700 Metal-App-mobile[6336:956788] Could not remove previous file at /private/var/mobile/Containers/Data/Application/058E5B75-6B15-441E-8487-4BA8A38108B4/tmp/CFNetworkDownload_OZ4ZxN.tmp due to Error Domain=NSCocoaErrorDomain Code=262 "The file couldn’t be opened because the specified URL type isn’t supported."  I don't know Objective-C well enough to vouch whether its runtime makes a proper copy of C-string inside its block. Here is additionally a slightly different call stack from the recent EXC_BREAKPOINT I see, which seem to point to the fact it happens due to processing of garbage in the path string:
#0	0x00000001bc5fa4b0 in static URL._unconditionallyBridgeFromObjectiveC(_:) ()
#1	0x0000000106906f5c in @objc StorageReference.write(toFile:completion:) ()
#2	0x00000001020f122c in invocation function for block in firebase::storage::internal::StorageReferenceInternal::GetFile(char const*, firebase::storage::Listener*, firebase::storage::Controller*) at /Users/me/Projects/firebase-cpp-sdk/storage/src/ios/storage_reference_ios.mm:149
#3	0x0000000106be808c in _dispatch_call_block_and_release ()
#4	0x0000000106be98c4 in _dispatch_client_callout ()
#5	0x0000000106bf8428 in _dispatch_main_queue_drain ()
#6	0x0000000106bf8080 in _dispatch_main_queue_callback_4CF ()
#7	0x00000001c2013828 in __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ ()
#8	0x00000001c1ff74a8 in __CFRunLoopRun ()
#9	0x00000001c1ffbb58 in CFRunLoopRunSpecific ()
#10	0x00000001f81fb984 in GSEventRunModal ()
#11	0x00000001c43a6628 in -[UIApplication _run] ()
#12	0x00000001c43a62a0 in UIApplicationMain ()
#13	0x0000000101330f44 in main at /Users/me/path/to/main.m:24
#14	0x00000001decc5df0 in start ()
Enqueued from com.apple.NSXPCConnection.m-user.com.apple.ondemandd.client (Thread 27) Queue : com.apple.NSXPCConnection.m-user.com.apple.ondemandd.client (serial)
#0	0x0000000106beddc0 in dispatch_async ()
#1	0x0000000102143708 in firebase::util::DispatchAsyncSafeMainQueue(void () block_pointer) ()
#2	0x00000001020f0c58 in firebase::storage::internal::StorageReferenceInternal::GetFile(char const*, firebase::storage::Listener*, firebase::storage::Controller*) at /Users/me/Projects/firebase-cpp-sdk/storage/src/ios/storage_reference_ios.mm:145
#3	0x00000001020e5f6c in firebase::storage::StorageReference::GetFile(char const*, firebase::storage::Listener*, firebase::storage::Controller*) at /Users/me/Projects/firebase-cpp-sdk/storage/src/common/storage_reference.cc:150

I probably was just lucky a few times when crash didn't happen last night and I closed this bug. Reopening for you to decide.

Looks like this actually is a bug if your C++ code is running outside of the main (UI) thread:
https://github.com/firebase/firebase-cpp-sdk/blob/e877b22faf5d4b2ad8080179369050ef6c15a2d8/storage/src/ios/storage_reference_ios.mm#L149
This code uses the path that was passed in, but if GetFile was called from a secondary thread, then this is dispatched to the main thread and the function will have returned already.
Shouldn't be too difficult a fix, thanks for raising the issue.

I can confirm the issue is resolved in 12.0.0


Allow arcgis to treat empty fields layers as valid

Fixes #2210

@rafatower CR please

Frontend tests were OK :+1: (details)

:+1:


WIP - GraphQL

Change folder it saves to to fullname: aka data/RichardLitt/name-your-contributors

I've since gotten rid of the data directory. It's not needed.
Otherwise the only thing left to do is deal with paginated requests (github only lets you get 100 entries of any given thing at a time).
Everything should be in working order but only the first 100 issues get queried for a repo and the first 100 comments from each issue, etc.. This will be fixed shortly.
Also the CI server needs a token. The v4 API requires one.

An update on pagination: I've run into a couple of issues with the API. The error messages from the server say it's probably a problem on their end, so I've sent off an email to support. I'll post any updates.

Also the CI server needs a token. The v4 API requires one.

So each user will have to get their own? That's OK, I'm cool with that.
Thanks for checking on pagination.
What do you think about this little module, so far?

LMK when this is ready to review!

Ready to review. The main features are all in, the pagination code is somewhat boilerplaty, but since we only have a couple of queries it doesn't much matter.
Careful with the -o org-name option since it can make a lot of requests. A single -o wikimedia will exhaust your hourly quota. The before and after flags don't effect this since the graphql API gives no way to filter in the query; the filtering all happens on the query response.
As for CI, I don't know how you want to do it. Giving travisci a token in the source is just asking for it to get abused, and hitting a third party api in an automated test is boarderline spammy. I'd say just test against hard coded queries and dummy responses (to check the queries don't get mangled, and the post-processors still work). That will break if the API changes, but things will break in that event no matter what. What's your opinion here?

Awesome. Boilerplate pagination is fine.
Add a note about the orgname possible exhausting the quota to the README, if you could.
I added a token to Travis, but it won't be seen in the source. Tests passed locally - let's see if they pass again. I wouldn't worry about hitting GitHub in the API, I think that's OK. Unless I'm committing a grievous sin, there? We could spoof the API, but not sure how to spoof a GraphQL api.

Any chance we could easily get normal contributions in this, too? People who commit code, for instance. Or through GitHub's API.
Same for people who make reactions (:+1:).

Note added. I also removed the section of the readme regarding other apps using the same auth token, since I gather that those other apps will no longer be necessary.
CI is still failing with auth errors. What's the token exported as?
It would be very straight forward to add more branches into the query.  Currently you have to match those with pagination, parsing, and aggregation, which as I said before is more boilerplate than I'd like. Easy, but repetitive. For just those two additions it's probably still worth it, but if we're going to want a lot of changes we'll eventually want a better graphql library. I couldn't find one that served our purpose very well: shopify's is the best as far as I can see, but it still doesn't have any capacity for automatic depaginating, filtering, or custom aggregations. I'm generally loath to write my own libraries for things but there seems to be a big gap in the space. The clients I saw all target browsers doing something relayish, whereas we're doing analytics.
Hopefully there's a better library that I missed, I didn't spend all that much time scouring.  Any ideas?

CI is still failing with auth errors. What's the token exported as?

Looks like Travis doesn't allow this for forks. It runs locally just fine.

It would be very straight forward to add more branches into the query. Currently you have to match those with pagination, parsing, and aggregation, which as I said before is more boilerplate than I'd like. Easy, but repetitive. For just those two additions it's probably still worth it, but if we're going to want a lot of changes we'll eventually want a better graphql library. I couldn't find one that served our purpose very well: shopify's is the best as far as I can see, but it still doesn't have any capacity for automatic depaginating, filtering, or custom aggregations. I'm generally loath to write my own libraries for things but there seems to be a big gap in the space. The clients I saw all target browsers doing something relayish, whereas we're doing analytics.

Hopefully there's a better library that I missed, I didn't spend all that much time scouring. Any ideas?

Can you open an issue for this? We can track it as we go. Right now, I would like to get commits too, for sure, although I guess I can write a thing to track git authors and merge them. (Maybe another issue for this?)
Regarding a better library: hmm. We could write a better one, but I want to make sure it is used for more than just this repository. Let's just track it in an issue.


QC: bslib cards

QC Details
Implement {bslib} throughout the package. Cards should be bslib::card()s, for example.
Additional Comments
I'm adding this ticket so I can feel ok not fixing everything as I go!

Gilead's stylesheet is here: https://www.gilead.com/Areas/GileadCorporate/Content/dist/main.css?v=20240812121745
That's bs4. Provide a path to implement that (and things like it), including a spike to see if we can upgrade that ~easily to bs5.

#r&d, nice find!


Add DataPointList for Scatterplot, to add a label for each marker.

#2141

This looks great @Cubikon, thanks! If you make the change I requested I'll merge this in good time 👍 🚀

@swharden If you think my change requests are too minor to block merging over than feel free to push it through and I can make a small PR later with them.

@swharden If you think my change requests are too minor to block merging over than feel free to push it through and I can make a small PR later with them.

I'd make the changes myself and merge but I don't have write access to the branch...
If we don't hear back from @Cubikon by tomorrow night I'll merge it as it is 👍

i did the new requested changes. And you have now access to the branch, if you want to change something else.

Looks great, thanks! 🚀


kubuntu23.04 ,qt5.5.1 编译失败

platformsupport_linux.cpp:299:10: error: ambiguating new declaration of ‘QString gtkSettings(const char*)’
platformsupport_linux.cpp:493: error: ‘g_object_get’ was not declared in this scope; did you mean ‘g_object_unref’?

是qt6.5.1

需要安装libxcb-dev和libgtk-3-dev

谢谢


Error while transmitting: Card was reset

I often get a WriteError but can't really find a workaround for this. I also have no clue what the error message even means. Does someone have a clue how I can solve this?
{ WriteError: An error occurred while transmitting.
    at /Users/sam/Projects/playground/usb/node_modules/nfc-pcsc/dist/Reader.js:573:11
    at throw (native)
    at step (/Users/sam/Projects/playground/usb/node_modules/nfc-pcsc/dist/Reader.js:16:191)
    at /Users/sam/Projects/playground/usb/node_modules/nfc-pcsc/dist/Reader.js:16:402
  name: 'WriteError',
  code: null,
  previous:
   { TransmitError: An error occurred while transmitting.
       at reader.transmit (/Users/sam/Projects/playground/usb/node_modules/nfc-pcsc/dist/Reader.js:271:20)
     name: 'TransmitError',
     code: 'failure',
     previous:
      Error: SCardTransmit error: Card was reset.(0x80100068)
          at Error (native) } }

Hi @SamVerschueren,
firstly, could you please provide more details?

What operating system do you use?
What is your Node.js version?
What card (which type – Mifare Classic, Ultralight, DESFire, or something else?) are you trying to access?
What card reader do you use?
your code – create a gist/repo or post here
Does the error occur by every run, or is it rather a random behaviour?
Also make sure, the card is closely attached to the reader, while running your code. If it is removed/reattached during the writing process, it could lead to similar errors.

According to my quick search, it looks like a strange error connected to Windows OS.
Also I have found an interesting thread related to this problem.
I believe, we can find a solution together.
So, please answer my questions.
Hope it helps.

Hi @pokusew, thanks for the quick reply. I know, my initial post was very brief but didn't have much time to provide more details, so here we go.

Operating System: macOS Sierra (10.12.4)
Node.js version: 6.9.1
Card: Mifare Ultralight
Card reader: ACR122U

Here is the code that shows the behaviour
'use strict';
const NFC = require('nfc-pcsc').default;

const nfc = new NFC();

nfc.on('reader', reader => {
	reader.on('card', card => {
		console.log(`Card detected (${card.type})`);

		const data = Buffer.from([0xa0, 0xa0, 0xa0, 0xa0, 0xa0, 0xa0, 0xa0, 0xa0, 0xa0, 0xa0, 0xa0, 0xa0]);

		reader.write(6, data)
			.then(result => {
				console.log('done!');
				console.log(result);
			})
			.catch(err => {
				console.log('error');
				console.error(err);
			});
	});
});

Save that file as index.js and run it. Put a tag on the card reader and then it should fail with the error message that I gave in my initial post. If you kill the program, put the tag on the card reader and then start the program while the tag is already detected by the reader, it works perfectly fine. It just doesn't work if the reader detects the tag while my code is already running.
When I reduce the size of the data buffer to 8 bytes, it seems to work perfectly fine. So I tried to chop my data array in chunks of 4 bytes each and wrote them sequentially to the tag. The first 2 or 3 chunks work, but then I get the same error or another one indicating that the card is unpowered.
So maybe I'm doing something wrong here, but I need to write 64 bytes (or more) to the tag and am not sure how I can achieve that.


Your article says that you only need one EEG and one EOG channel. Will key information be missed?

According to some literatures, vertex sharp transient, spindle wave and K-complex mainly appear in specific brain regions, or most significantly in a certain brain region. Your article says that you only need one EEG and one EOG channel. Will key information be missed? How to prove that it won't?
Spindle activity was best recorded by central electrode, while K complex and K complex were the best δ The best recording method is frontal electrode (Rodenbeck et al., 2006; Silber et al.，2007）； On the one hand, the integration of frontal, central and occipital leads improved the reliability of IRR. In fact, the reliability of the arousal score was particularly low in the absence of increased submental EMG activity.

Hi TL730,
This is a very interesting question, which we also wondered ourselves. It is very possible that the model is not always able to detect certain features / events in the available channels. It was an open question when we designed this system if it would be able to learn robust sleep staging based on just the 2 input channels (with randomly varying electrode positions even). However, based on the extensive evaluation we have done it seems the model is either 1) able to robustly detect such patterns even in channels where humans find it difficult / are not able to, or 2) relies on other features entirely when scoring. It is possible that the model (e.g., using its ability to consider quite long-range patterns in the signals both back and forth in time) has learned features that are more robustly observable across channels. We are not really sure yet and  hope to learn more from future studies.
Cheers,
Mathias


Build Issue with v6.4.1 min build file

We are using Ionic version 5.4.16 in tandem with angular version 12.1.4. When building our app in a development environment, we have no issues with v6.4.1 as it directly uses the source files of the node package. However, when we build and deploy our app in a production environment, the minified build file for three mesh UI is used.
When we attempt to create a Block component, we get the following reference error:
ReferenceError: Must call super constructor in derived class before accessing 'this' or returning from derived constructor
    at new <anonymous> (three-mesh-ui.module.min.js:1:2853)
    at new re (three-mesh-ui.module.min.js:1:31134)

We have a lot of investigating to still perform, but I was hoping to see if there was any insight into what might be causing this. I noticed that the 6.4 version updates webpack, and was curious if there was a clash there possibly.
I will update this issue as we come across any new information related to this issue.

Hey @JoeCoppola-HIA , You did well to ask.
There were indeed some changes that occured.
I added some samples and sandboxes to be sure of what I was releasing, but we can't anticipate everything
I've tested the minified builds you refer to on those sandboxes :
https://codesandbox.io/s/module-build-demo-minified-6-4-1-q6wybs?file=/index.html
https://codesandbox.io/s/npm-package-demo-6-4-1-2onzpo
But I can't notice anything. I've print the code behind Block constructor on npm-package-demo. It is called re same a your error.
Maybe one hint, how do you handle dependencies in your project? Especially threejs which is now externalized from three-mesh-ui bundle, so it needs to load it prior to three-mesh-ui.

Hello
Yes there is a major webpack upgrade version 4 to 5.
See there (bottom of the page)
https://github.com/felixmariotto/three-mesh-ui/commit/06402a488faa16b97e45896b710e1a799dabbf00
What is your build command please ?
A problem with ES15 support ? it's an old issue but ..
https://github.com/angular/angular-cli/issues/7799
I didn't find interesting things webpack side.
Did you try/can you try a ionic update ?
i can't find the version here https://github.com/ionic-team/ionic-framework/releases?page=7

Hello @eviltik and @swingingtom,
I am currently putting together a codesandbox example from the follow minimal reproducing example that mirrors our app environment:
https://github.com/JoeCoppola-HIA/SimpleIonicThreeJSApp
This repo should be public and accessible to anyone to fork or pulldown and test. Maybe this would help spot anything we might be handling incorrectly.
To reproduce, simply npm install and run ionic serve --prod.
I will update this issue with the codesandbox when I have it running as well as try out the suggestions provided already. Thank you for the quick response.

Unfortunately it always happen on fridays...

Ain't that the truth hahaha. Locking our version to 6.3.2 for the time being has our production issue resolved. But I would hate to miss out on future updates of Three Mesh UI because of this. We will figure it out, that I'm sure of it. Always appreciate your help.

Well it took me a little longer than I anticipated, but I was able to get an example of the behavior in a codesandbox example. The below link will load a node based sandbox that builds a simple production ionic app, creates a three js scene, places a blue cube and then tries to create a yellow three mesh ui block. On creation attempt it will throw the error I linked above. This will be alerted, and if you hit ok you will see the blue cube but not the yellow block.
https://codesandbox.io/s/broken-threemeshui-6-4-1-ionic-angular-15nti4?file=/src/app/home/home.page.ts
I also made a sandbox example of the exact same code, but this is building the ionic app without the prod flag, in this example, the error is not thrown:
https://codesandbox.io/s/threemeshui-6-4-1-ionic-angular-dev-build-h3c9zw?file=/src/app/home/home.page.ts
Hopefully this helps spot any issues with the way we handle dependencies here, or how Ionic Angular does. We attempted to update to the latest Angular locally, 13.3.3, as that version of build-angular uses the same version of Webpack that Three Mesh UI upgraded to. However we continue to get the same issue.

Hey @JoeCoppola-HIA, I was able to reproduce it from the github repository you shared.
Issue location
The resulted issue may not lay on  ThreeMeshUI.Block itself. I've built the ionic serve --prod with both
import ThreeMeshUI from "three-mesh-ui/build/three-mesh-ui.module.min";
// which is currenlty the same of
// import ThreeMeshUI from "three-mesh-ui";

and
import ThreeMeshUI from "three-mesh-ui/build/three-mesh-ui.module";
// or even the un-built source file
// import ThreeMeshUI from "three-mesh-ui/src/three-mesh-ui";

The produced outputs of console.log(ThreeMeshUI.Block.toString() ); were exactly the same for both imports (except names that are optimized). So it can be on one of inherited constructors. Which I didn't analysed.
Please note, the later didn't suffer from the issue.
Workaround - Not Acceptable
I was able to get rid of this issue simply by setting projects.app.architect.configurations.production.optimization = false in angular.json file.
Even when forcing the minified module build in home.page.ts
import ThreeMeshUI from "three-mesh-ui/build/three-mesh-ui.module.min";

So troubles comes with combination of minified module build and angular optimisation.  I didn't succeed to quickly find a list of angular optimisation options.
I did the same process with a webpack repository using terser optimisation, and didn't succeed to reproduce the issue
Workaround - Acceptable (IMO)
Previous v6.4.1, the module property defined in three-mesh-ui/package.json was three-mesh-ui/src/three-mesh-ui.js.
v6.4.1 changed it to rely on three-mesh-ui/build/three-mesh-ui.module.min.js.
So you could get back your imports to :
// As the module build will still be optimized from angular side
import ThreeMeshUI from "three-mesh-ui/build/three-mesh-ui.module";

or
// Same results as < v6.4.1
import ThreeMeshUI from "three-mesh-ui/src/three-mesh-ui";

Next releases ??
Should we revert the module of three-mesh-ui/package.json to three-mesh-ui/src/three-mesh-ui.js ? (same as other libs such as three-mesh-bvh, etc...)
Should we downgrade the module of three-mesh-ui/package.json to three-mesh-ui/build/three-mesh-ui.module.js ? (same as threejs, etc...)
Both options won't remove the ability of module builds (unminified and minified).

The build (prod) generate a class calling a constructor without super(). It's BoxComponent.
Consider this change:
https://github.com/felixmariotto/three-mesh-ui/commit/13b25ec9555ce3b27f435c519ced7f7035ab2879
Search for "// @TODO: Replace .bind() when webpack update to allow class methods as fat arrow"
I can't make the test on my side, the idea should be to target ES5 in three-mesh-ui webpack config file using
target: ['web', 'es5'] to see if it's better or not (see https://webpack.js.org/migrate/5/)
My 2 cents

Thank you for looking into this. I am glad there are some workarounds that allow us to use the latest and greatest. Tomorrow I can test @eviltik's suggestion of building three mesh UI with the updated target in the config to see if that helps.

Modifying the browswerConfig in webpack.config.js to use target: ['web', 'es5'] results in the same super call error unfortunately.
However, updating all our import calls to import ThreeMeshUI from "three-mesh-ui/build/three-mesh-ui.module"; indeed resolved the issue, and still resulted in Angular optimizing the module in a minified fashion. This method does not use Types.d.ts, but that is acceptable as we weren't using them before due to their unfinished state. One day we would love to use them, but we aren't hindered by this for the time being.
As for what should be done in future releases, I ran a test to see if downgrading the module of three-mesh-ui/package.json to three-mesh-ui/build/three-mesh-ui.module.js would also fix our issue. It indeed fixes our Angular prod build, and if we opted to, would allow us to use Types.d.ts. While this works for us, as you said, we can't anticipate everything. But if a repo such as three js employs this strategy, with a user base as large as them, it might be proven more cross compiler safe?

I've update the package.json and pushed a new version v6.4.2
It comes with other improvements, meaning maybe more surprises... (see diff)

Thanks a bunch! We will work on getting this version into our app this week and evaluate any potential issues.

... as long as you don't break your production on next friday ;) 🪓 🔨

hahaha
@swingingtom just want to let you know that we upgraded to 6.4.2 in our dev environment. Running with the prod flag work now, and the overall updates I had to make to accommodate the main API changes were pretty straight forward and painless. Thank you a bunch again for this update. I feel more confident about being ready for 7.x.x.


Error while building

I get the following error while building mintab
~/.config/mintab ❯❯❯ python build.py
Traceback (most recent call last):
  File "build.py", line 17, in <module>
    subprocess.run(autoprefix_cmd.split(), stdout=subprocess.PIPE).stdout.decode('utf-8')
  File "/usr/lib/python3.6/site-packages/run/__init__.py", line 145, in __new__
    process = cls.create_process(command, stdin, cwd=cwd, env=env, shell=shell)
  File "/usr/lib/python3.6/site-packages/run/__init__.py", line 121, in create_process
    shlex.split(command),
  File "/usr/lib/python3.6/shlex.py", line 305, in split
    return list(lex)
  File "/usr/lib/python3.6/shlex.py", line 295, in __next__
    token = self.get_token()
  File "/usr/lib/python3.6/shlex.py", line 105, in get_token
    raw = self.read_token()
  File "/usr/lib/python3.6/shlex.py", line 136, in read_token
    nextchar = self.instream.read(1)
AttributeError: 'list' object has no attribute 'read'

Hmm not sure about that one. This project is kind of deprecated though, I would recommend using taab instead. This (mintab) and the original tab startpage are no longer being worked on.
That said, if you do figure out why you're getting an error when building, feel free to open a PR.


Metadata: Information from schema:description missing in the UI

Describe the Enhancement
metadata is still missing on certain filters and legends in both the published chart and editor mode.
Reference: https://gitlab.ldbar.ch/bafu/umweltdatenkiosk-planning/-/issues/350#note_8705
To Reproduce
Steps to reproduce the behavior:

Go to 'https://int.visualize.admin.ch/en/create/n9fdoq_th318?dataSource=Int'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Metadata should be shown on the following filters and legends (see yellow highlighted areas in screenshots below)

Environment (please complete the following information):

Visualize environment and version: INT v3.9.2 ([3fc980f], Datasource: INT
Browser and version [e.g. Chrome 95]

Additional context
Add any other context about the problem here.

@ortnever I created a new issue in github for the metadata so we can track the issue (also see: https://gitlab.ldbar.ch/bafu/umweltdatenkiosk-planning/-/issues/350. We will try to tackle this issue this week, so it can be tested before we deploy to production next week.


Settings to protect the default branch

[x] Set master as default branch
[x] Disable direct push and force push for master branch
[ ] Enable PR for master branch and enforce at least approval from 2 writers or maintainers

I have done the first two items from the list above.


Include dependencies in pom

I think it should include all required dependencies so that users only need to depend on puree-android, so how about include dependencies in pom?
refs. https://github.com/cookpad/puree-android/pull/67

Thanks!


inconsistent behavior with ### (h3 tags) between Firefox and Safari

This is a weird one:
The URL is http://lightgraphsjl.readthedocs.org/en/docs/linalg/.
Here's the markdown code:
*LightGraphs.jl* provides the following matrix operations on undirected graphs:

### Adjacency

`adjacency_matrix(g)`

Returns a sparse boolean adjacency matrix for a graph, indexed by `[src, dst]`
vertices. `True` values indicate an edge between `src` and `dst`.

Here's what it looks like in Firefox (as expected):

And here's what Safari renders (notice, there's no h3 for Adjacency):

It only seems to be happening on this one page, and only when the text is "Adjacency" (I tried "Foo", "Bar", and "Baz" and they all showed up).
What's weirder is that it's in the HTML (taken from Safari):

LightGraphs.jl provides the following matrix operations on undirected graphs:

Adjacency

adjacency_matrix(g)

Returns a sparse boolean adjacency matrix for a graph, indexed by [src, dst]
vertices. True values indicate an edge between src and dst.

adjacency_spectrum(g)

Returns the eigenvalues of the adjacency matrix for a graph, indexed by vertex.

I'm stumped, which probably means it's something really stupid that I did. Can someone point me in the right direction?

Turns out it was Adblock for Safari (Adblock Plus does the same thing). Closing this out.


Session data seems to not be saved between requests

Hi,
It seems my session is not being saved, question is am I doing this right? I am not entirely sure so here's a little more context.
I am implementing a simple session-based login like this:
storage := sqlite3.New()
store := session.New(session.Config{
  Storage: storage,
})

then I save it
sess.Set("email"<EMAIL_ADDRESS>defer sess.Save()

and then I try to read the value:
email := sess.Get("email")
log.Println(email)
log.Println(sess.Keys())

So my first question is: am I doing it right?

if you want to save and read the session in the middlewares then try it without "defer" at the sess.Save call
defer is executed only at the end of the run, but our middlewares are nested by the ctx.Next call, which sometimes causes problems there

need more code with the connections and the handlers to help you

sure, just share the link

I added you to the repo, you should receive an invitation. Here's the repo link repo

its just a GET request not a POST request.
i think you miss the method

As I assumed, it was my mistake. I ran the entire thing on the wrong domain. Thank you for your time.  Please let me know.
Closing the issue.


Bump version to 0.11.0

We really should have remembered this would happen because of all the drama we had in bitcoinconsensus, face palm.
Bump the verison and add a changelog entry explaining the yank and re-release for those that don't know.

Tagged and published.


chore(docs): add more detailed credits and license info

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 61.18%. Comparing base (6e0fb63) to head (6b79f6b).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   61.18%   61.18%
=======================================
  Files           2        2
  Lines         304      304
  Branches       30       30
=======================================
  Hits          186      186
  Misses         88       88
  Partials       30       30

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add group by and sort by to asciidoc report generation

Ok. Thanks. Let's await approval from @lfvbarcus as well.


wierd post repeat

Strangest thing ever...
I'm using hyperclient to find a link in a root document, and then doing a _post on it with some json.
On one server this works fine.
On another, hyperclient posts the data correctly, the server returns a 200 OK with a json response body.  Then hyperclient repeats the POST to the same URL, but includes the response body it got from the first response.
This then fails with a 422 as it is not a valid request body.
Any idea why hyperclient would decide to repeat a post and send the newly received body instead of what it was told to?

Strange. Is this consistently reproducible on that machine? Some ideas:

I would compare gem versions first, just in case something newer slipped in.
Hyperclient uses Futuroscope, which is a bit of magic. I would try setting the pool to no pool like here and see if it changes anything.
I would try to reduce this to a spec and record what's going on with VCR so that we can rerun it, it's likely a bug.

it's all running on the same machine, but the different behavior shows up depending on which server I am talking to.  The servers are two different rails server apps.  Luckily the one that is causing the problem is my own app that I control.
My server works fine with CURL, the HAL browser, and doing my POST directly with Faraday, but with hyperclient I see this behavior.
I tried updating my bundle to the latest hyperclient from this repo and see the same results. I'll futz with futuroscope too.
I'm continuing to debug it.  It smells to me like either a content type or encoding problem where HC can't parse the results, or HC is updating it's own internal state of the resource, spotting an error and triggering retry logic, but keeping POST as the method.
This line makes me wonder
https://github.com/codegram/hyperclient/blob/7e7dad25dbe6eace10ef13f0136705f190e6145b/lib/hyperclient/link.rb#L180
Is there any case where Resource.new will cause some HTTP action to happen?

I don't think so, but did you try to turn this into a spec? If you can repeat that behavior you can record the spec with VCR and we can repro/fix.

Im still troubleshooting it, turning it into a spec isn't trivial and I'm not there yet


Powershell command is misleading/wrong

The Powershell command to convert the "Digicert Global Root CA https://cacerts.digicert.com/DigiCertGlobalRootCA.crt" certificate is misleading/wrong.
I have not tried other certs, only the the "DigiCertGlobalRootCA.crt", if you try to convert this to ".pem" format to use in mysql workbench you give the following example:
openssl x509 -in certificate.crt -out certificate.pem -outform PEM
this results in this error:
OpenSSL> x509 -in DigiCertGlobalRootCA.crt -out DigiCertGlobalRootCA.pem -outform PEM unable to load certificate<PHONE_NUMBER>6:error:0909006C:PEM routines:get_name:no start line:crypto/pem/pem_lib.c:745:Expecting: TRUSTED CERTIFICATE error in x509
instead you have to use this command:
OpenSSL> x509 -inform der -in DigiCertGlobalRootCA.crt -out certificate.pem
afaik this is because the cert is in ".der" format and the file only ends in ".crt"
without certificate knowledge this can take hours of troubleshooting to find out why this is being caused and could be solved by simply adding a second Powershell command to the site or at least a notice that the certificates can be formatted in ".der" too.

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

ID: 527dd8d1-89d8-098f-dcdf-031f222195f6
Version Independent ID: 99f7ef3a-a767-98b5-0a79-2ae0d85390c2
Content: Networking overview using SSL and TLS - Azure Database for PostgreSQL - Flexible Server
Content Source: articles/postgresql/flexible-server/concepts-networking-ssl-tls.md
Service: postgresql
Sub-service: flexible-server
GitHub Login: @GennadNY
Microsoft Alias: gennadyk

@Jeremia-H
Thanks for your feedback! We will investigate and update as appropriate.

Hello @Jeremia-H
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated! Now we are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.


[cookie.chrome] Crash when not using default chrome profile

Chrome provides support for profiles. When you do not have a Default profile or are using a profile that is not the Default profile, the Cookies db file will either be not found (causing a crash) or you won't be able to retrieve the leetcode cookie.
The currently active profile can be seen in chrome using chrome://version/.

@ilaskaev could you try the latest plugin to see if it meets your need?

@skygragon All works well now. Thank you.


Update chart victoria-logs-single to 0.6.6

This PR contains the following updates:

Package
Update
Change

victoria-logs-single
patch
0.6.5 -> 0.6.6

Release Notes

VictoriaMetrics/helm-charts (victoria-logs-single)
v0.6.6
Compare Source
Release notes for version 0.6.6
Release date: 2024-10-11

Human-readable error about Helm version requirement

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.


refactor: removing RecipeStatusRegistry and recipeStatusUtils

What does this PR do?
The RecipeStatus was an interface made of modelid: number, recipeid: number and tasks[]. Its interest was to access quickly the tasks related to given pair of model/recipe.
However, having this shortcut was causing issue, as the tasks was not in a single place, to keep the TaskRegistry as the single source of truth, we needed to remove completely this RecipeStatus and related utility classes.
The TaskRegistry has been enhanced with some new methods, allowing to fetch the requested tasks based on their labels.
Screenshot / video of UI

What issues does this PR fix or reference?
Fixes https://github.com/projectatomic/ai-studio/issues/382
How to test this PR?

[x] Existing unit tests ensure no regression
[x] New unit tests has been added

Manual testing required
Ensuring no visual regression is important, please test some scenarios

pulling an application
restarting application
deleting manually
download model(s) from model page

LGTM, just some console.log that you forgot i guess

@lstocchi yes thanks for noticing! I was too focus avoiding regression I forgot removing the logs I added to debug! 👀


Redefinition of ARRAY_SIZE macro

Hello everyone,
while working on integrating the TMC2300 into one of our projects, we got a redefinition warning of the above mentioned macro, because our microcontroller sdk implements this too. After a quick glimpse into your code, it turns out there is a missing #ifndev...#endif around ARRAY_SIZE.

Thank you for the suggestion and your valuable feedback. We have fixed this issue now.


Missing blank line when using POST

RestClient::request() adds a blank line between headers and request body if the method is GET, but this blank line is needed for other methods too, such as POST.

@bullestock thanks for reporting this - its crazy to think that this has been an issue for this long!  I verified the format here: https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html and it clearly says there should be a CRLF between the headers and message body.  I have fixed this issue.


Missing dependency

You also need xlrd to open Excel files in Python.

@philip-mach yes you are right. I have added it to the environment.yml. I will now add it to the README as well. Thanks


Fix budgets

Apparently it is
mem = 14000000L
on main-net, not 16000000L
This raises interesting question if we should be keeping default or rather read default from Aiken... all defaults.
data source: https://cexplorer.io/params

Thanks @matiwinnetou. Let's merge this for now.
We can add another method in Aiken JNA wrapper layer without InitialBudget and remove default from java code.
So, a Java app can use

TxEvaluator() - This will use default initial budget config defined in Aiken. Need to check if Aiken also has a default SlotConfig?
TxEvaluator(slotConfig, initialBudgetConfig) - Use application provided slotConfig and initialBudgetConfig

Issue

Yes but I am not sure which one is the correct approach, relying on SlotConfig and InitialBudget from Aiken or managing this in java layer. Keep in mind that Aiken team will likely forget to keep this updated.
These params can be updated on main-net within one epoch and in addition when running devnets, on Hydra, these parameters can be vastly different than defaults.
IMHO, ideal approach would be to always read those params in an app (based on live settings + some cache) and always pass them down the invocation stack.


Update challenge example in README.md

Looking at the code, it seems the method is actually called confirmate https://github.com/huttarichard/instagram-private-api/blob/1dc5ae2194fac32c53166828fca9df3ff47eca86/client/v1/web/challenge.js#L243
I guess confirm is more correct, but since that is a backwards compat breaking change, I thought it was easier to just change the documentation :). Of course you could also expose the method under both names

(y)


[Bug]: No password handling dialog when executing openshift local initialize action on linux

I am not sure how did I get into this state. Will try to do proper clean up.

Stack trace:
main ↪ [openshift-local] level=info msg="Using bundle path /home/odockal/.crc/cache/crc_libvirt_4.12.13_amd64.crcbundle"
level=info msg="Checking if running as non-root"
level=info msg="Checking if running inside WSL2"
level=info msg="Checking if crc-admin-helper executable is cached"
level=info msg="Caching crc-admin-helper executable"
level=info msg="Using root access: Changing ownership of /home/odockal/.crc/bin/crc-admin-helper-linux"
Unable to set ownership of /home/odockal/.crc/bin/crc-admin-helper-linux to root:  exit status 1: sudo: a terminal is required to read the password; either use the -S option to read from standard input or configure an askpass helper
sudo: a password is required

(anonymous) @ index.ts:1335
emit @ VM4 sandbox_bundle:2
onMessage @ VM4 sandbox_bundle:2

As per documentation, the setup on Linux is to be performed from the command line using crc setup. This might be resolved in future version, but at the moment an automated installation flow on Linux is not the priority yet.


Data Constructors for Fixed Effects

This PR adds the data_response and data_fixed_effects functions that creates the response y and matrix X from a @formula and a Tables.jl-compatible interface.
The tests are mostly done with NamedTuples and DataFrames.
Related to #2.

Changed everything TuringGLM.YADA to T.YADA thanks!