Effort import does not show error message

When the server returns 422, the Import Entrants button flashes red, but no error message is shown.
Reproduce by attempting to import any file that does not have a .csv extension.
The error message returned by the server should be displayed in the standard error alert box.

Done.

Addressed by #163


_alloca Requested memory may have edge problems causing exceptions

https://github.com/libuv/libuv/blob/2c153450162108a7f4105a5154592a2bb9e80ce1/src/win/process.c#L620
Has there been any consideration of replacing all all _alloca with uv__malloc
**The _alloca routine returns a void pointer to the allocated space, which is suitably aligned for storage of any type of object. If size is 0, _alloca allocates a zero-length item and returns a valid pointer to that item.
A stack overflow exception is generated if the space can't be allocated. The stack overflow exception isn't a C++ exception; it's a structured exception. Instead of using C++ exception handling, you must use Structured exception handling (SEH).**
https://learn.microsoft.com/en-us/cpp/c-runtime-library/reference/alloca?view=msvc-170#return-value

@vtjnash you introduced that in 2014 in 8db42383a, do you remember why?
It should normally allocate no more than 64 kiB in total but that may be just enough to push the stack over the edge, under the right circumstances.

I believe it was because CompareStringOrdinal wasn't implemented until Vista, so I made my own with this function. In hindsight it would probably have been easier to write my own case conversion for each character instead for XP


iOS: Login verified but not receiving accessToken

Followed all the steps mentioned here
Trying to log the token but not receiving seems like I am not receiving it.

What is the error you are receiving?

I am receiving "Error: The operation couldn’t be completed. (org.openid.appauth.general error -3.)"


Long-range should be be properly symmetric now

Difference is how constraints on the second order IFCs are created. I start by calculating how much the dipole-dipole long-range model deviate from proper symmetry, and I set the constraints to exactly cancel that.
Side effect is that I had to figure out how to calculate the elastic constant contribution from the dipole-dipole interactions. Not sure if useful for anything but doesn't hurt.
There is no chance whatsoever that this can break something, except for the off chance that it breaks everything.

Some results for GaN and BZS:
GaN before:

GaN after:

BZS before:

BZS after:

Comparison phonopy for BZS:


Add scylla-operator package/version information

add those to web run info
add those to issue template

Ref: https://github.com/scylladb/scylla-cluster-tests/pull/5512

@k0machi
seems like the github actions is broken
Version 3.10.3 was not found in the local cache
Error: Version 3.10.3 with arch x[6](https://github.com/scylladb/argus/actions/runs/3627446497/jobs/6117345629#step:3:7)4 not found

I think it's using an old version of get-python action

@fruch I think it just wants latest 3.10 hotfix, so just update the version to 3.10.8

@fruch I think it just wants latest 3.10 hotfix, so just update the version to 3.10.8

even better, we should be pining specific minor releases...

@fruch I think it just wants latest 3.10 hotfix, so just update the version to 3.10.8

even better, we should be pining specific minor releases...

and now it's works much better.


Fix: eslint warnings and errors

There are bunch of eslint waning in the website dir
` /home/punith/Desktop/lfx/arewefastyet/website/src/App.jsx
18:8  error  'React' is defined but never used  no-unused-vars
ueue.jsx
17:8    error  'React' is defined but never used                                                                                no-unused-vars
21:20   error  'data' is missing in props validation                                                                                react/prop-types
24:35   error  Using target="_blank" without rel="noreferrer" (which implies rel="noopener") is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations  react/jsx-no-target-blank
24:110  error  'data.git_ref' is missing in props validation                                                                                react/prop-types
24:127  error  'data.git_ref' is missing in props validation                                                                                react/prop-types
24:135  error  'data.git_ref.slice' is missing in props validation                                                                                react/prop-types
25:49   error  'data.source' is missing in props validation                                                                                react/prop-types
26:49   error  'data.type_of' is missing in props validation                                                                                react/prop-types
27:48   error  'data.pull_nb' is missing in props validation                                                                                react/prop-types
/home/punith/Desktop/lfx/arewefastyet/website/src/components/StatusComponents/PreviousExeResponsiveMobile/PreviousExeResMobile.jsx
17:8    error  'React' is defined but never used                                                                                no-unused-vars
23:26   error  'data' is missing in props validation                                                                                react/prop-types
23:32   error  'className' is missing in props validation                                                                                react/prop-types
38:53   error  'data.source' is missing in props validation                                                                                react/prop-types
39:63   error  'data.status' is missing in props validation                                                                                react/prop-types
39:102  error  'data.status' is missing in props validation                                                                                react/prop-types
57:46   error  'data.uuid' is missing in props validation                                                                                react/prop-types
57:51   error  'data.uuid.slice' is missing in props validation                                                                                react/prop-types
58:40   error  Using target="_blank" without rel="noreferrer" (which implies rel="noopener") is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations  react/jsx-no-target-blank
58:115  error  'data.git_ref' is missing in props validation                                                                                react/prop-types
58:132  error  'data.git_ref' is missing in props validation                                                                                react/prop-types
58:140  error  'data.git_ref.slice' is missing in props validation                                                                                react/prop-types
59:46   error  'data.type_of' is missing in props validation                                                                                react/prop-types
60:56   error  'data.started_at' is missing in props validation                                                                                react/prop-types
61:56   error  'data.finished_at' is missing in props validation                                                                                react/prop-types
62:46   error  'data.pull_nb' is missing in props validation                                                                                react/prop-types
63:45   error  'data.golang_version' is missing in props validation                                                                                react/prop-types
/home/punith/Desktop/lfx/arewefastyet/website/src/components/StatusComponents/PreviousExecutionResponsiveTablet/PreviousExeResTablet.jsx
17:8   error  'React' is defined but never used                                                                                no-unused-vars
27:33  error  'data' is missing in props validation                                                                                react/prop-types
27:39  error  'className' is missing in props validation                                                                                react/prop-types
45:11  error  Using target="_blank" without rel="noreferrer" (which implies rel="noopener") is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations  react/jsx-no-target-blank
47:69  error  'data.git_ref' is missing in props validation                                                                                react/prop-types
49:19  error  'data.git_ref' is missing in props validation                                                                                react/prop-types
49:27  error  'data.git_ref.slice' is missing in props validation                                                                                react/prop-types
52:45  error  'data.source' is missing in props validation                                                                                react/prop-types
53:56  error  'data.started_at' is missing in props validation                                                                                react/prop-types
54:56  error  'data.finished_at' is missing in props validation                                                                                react/prop-types
57:18  error  'data.status' is missing in props validation                                                                                react/prop-types
60:17  error  'data.status' is missing in props validation                                                                                react/prop-types
78:31  error  'data.uuid' is missing in props validation                                                                                react/prop-types
78:36  error  'data.uuid.slice' is missing in props validation                                                                                react/prop-types
79:31  error  'data.type_of' is missing in props validation                                                                                react/prop-types
80:31  error  'data.pull_nb' is missing in props validation                                                                                react/prop-types
81:31  error  'data.golang_version' is missing in props validation                                                                                react/prop-types
/home/punith/Desktop/lfx/arewefastyet/website/src/components/StatusComponents/PreviousExecutions/PreviousExe.jsx
17:8   error  'React' is defined but never used                                                                                no-unused-vars
22:24  error  'data' is missing in props validation                                                                                react/prop-types
25:43  error  'data.uuid' is missing in props validation                                                                                react/prop-types
25:48  error  'data.uuid.slice' is missing in props validation                                                                                react/prop-types
27:9   error  Using target="_blank" without rel="noreferrer" (which implies rel="noopener") is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations  react/jsx-no-target-blank
29:67  error  'data.git_ref' is missing in props validation                                                                                react/prop-types
31:17  error  'data.git_ref' is missing in props validation                                                                                react/prop-types
31:25  error  'data.git_ref.slice' is missing in props validation                                                                                react/prop-types
34:52  error  'data.source' is missing in props validation                                                                                react/prop-types
36:26  error  'data.started_at' is missing in props validation                                                                                react/prop-types
39:26  error  'data.finished_at' is missing in props validation                                                                                react/prop-types
41:43  error  'data.type_of' is missing in props validation                                                                                react/prop-types
43:15  error  'data.pull_nb' is missing in props validation                                                                                react/prop-types
46:11  error  Using target="_blank" without rel="noreferrer" (which implies rel="noopener") is a security risk in older browsers: see https://mathiasbynens.github.io/rel-noopener/#recommendations  react/jsx-no-target-blank
48:67  error  'data.pull_nb' is missing in props validation                                                                                react/prop-types
50:19  error  'data.pull_nb' is missing in props validation                                                                                react/prop-types
54:42  error  'data.golang_version' is missing in props validation                                                                                react/prop-types
56:48  error  'data.status' is missing in props validation                                                                                react/prop-types
58:15  error  'data.status' is missing in props validation                                                                                react/prop-types
/home/punith/Desktop/lfx/arewefastyet/website/src/components/footer/Footer.jsx
17:8  error  'React' is defined but never used  no-unused-vars
/home/punith/Desktop/lfx/arewefastyet/website/src/components/header/Header.jsx
17:8  error  'React' is defined but never used  no-unused-vars
/home/punith/Desktop/lfx/arewefastyet/website/src/pages/CRON/CRON.jsx
17:8   error    'React' is defined but never used                                                                                no-unused-vars
20:10  error    'ResponsiveLine' is defined but never used                                                                                no-unused-vars
87:6   warning  React Hook useEffect has a missing dependency: 'navigate'. Either include it or remove the dependency array                   react-hooks/exhaustive-deps
317:16  warning  Fast refresh only works when a file only export components. Use a new file to share constant or functions between components  react-refresh/only-export-components
/home/punith/Desktop/lfx/arewefastyet/website/src/pages/Compare/Compare.jsx
17:8   error    'React' is defined but never used                                                                            no-unused-vars
63:16  error    'isMicrobenchLoading' is assigned a value but never used                                                     no-unused-vars
64:12  error    'microbenchError' is assigned a value but never used                                                         no-unused-vars
80:6   warning  React Hook useEffect has a missing dependency: 'navigate'. Either include it or remove the dependency array  react-hooks/exhaustive-deps
/home/punith/Desktop/lfx/arewefastyet/website/src/pages/Home/Home.jsx
17:8  error  'React' is defined but never used  no-unused-vars
/home/punith/Desktop/lfx/arewefastyet/website/src/pages/Layout.jsx
17:8   error  'React' is defined but never used     no-unused-vars
17:17  error  'useState' is defined but never used  no-unused-vars
/home/punith/Desktop/lfx/arewefastyet/website/src/pages/Macro/Macro.jsx
74:10  warning  React Hook useEffect has missing dependencies: 'gitRefLeft' and 'gitRefRight'. Either include them or remove the dependency array  react-hooks/exhaustive-deps
96:8   warning  React Hook useEffect has a missing dependency: 'isFirstCallFinished'. Either include it or remove the dependency array             react-hooks/exhaustive-deps
105:8   warning  React Hook useEffect has a missing dependency: 'navigate'. Either include it or remove the dependency array                        react-hooks/exhaustive-deps
/home/punith/Desktop/lfx/arewefastyet/website/src/pages/MacroQueriesCompare/MacroQueriesCompare.jsx
17:8   error    'React' is defined but never used                                                                                no-unused-vars
29:22  error    'setcommitLeft' is assigned a value but never used                                                                                no-unused-vars
32:23  error    'setcommitRight' is assigned a value but never used                                                                                no-unused-vars
35:16  error    'settype' is assigned a value but never used                                                                                no-unused-vars
42:6   warning  React Hook useEffect has missing dependencies: 'commitLeft', 'commitRight', 'navigate', and 'type'. Either include them or remove the dependency array  react-hooks/exhaustive-deps
70:6   warning  React Hook useEffect has missing dependencies: 'commitLeft', 'commitRight', and 'type'. Either include them or remove the dependency array              react-hooks/exhaustive-deps
/home/punith/Desktop/lfx/arewefastyet/website/src/pages/Micro/Micro.jsx
75:6  warning  React Hook useEffect has missing dependencies: 'gitRefLeft' and 'gitRefRight'. Either include them or remove the dependency array  react-hooks/exhaustive-deps
74:3  error  'setChangeUrl' is defined but never used  no-unused-vars
✖ 854 problems (841 errors, 13 warnings)
5 errors and 0 warnings potentially fixable with the --fix option.`

Hey @frouioui I wanna participate in upcomming lfx program so I wanna take this as beginners issue is it ok?

I also have plans to run 'npm run lint' in CI preventing further eslint error

You are very welcome to open a Pull Request @punithnayak and @Camillemtd and I will then review it.

Hello @frouioui, can I work on this issue?

Hey @sivasathyaseeelan! It does not seem like @punithnayak has not picked this up yet, you're welcome to go ahead.

Hey@frouioui  will come up with pr by Tomorrow got stuck...a bit

I think #420 solves many of these errors and the warnings can be removed by removing unused codes some of which are still WIP.

Closing this for now.


add Jazzy-generated documentation

Background
Added .jazzy.yaml configuration file. Ran Jazzy to generate HTML documentation in "docs" directory, in preparation for turning on Github pages. Also generated docset in "docs/docsets".
To view documentation locally, open docs/index.html with your favorite browser. Firefox seems to cope better with the remote images than Safari does.
Breaking Changes
None
Meta

Tied to Version Release(s):

PR Checklist

[ ] CI runs clean?
[ ] Appropriate label has been added to this PR (i.e., Bug, Enhancement, etc.).
[ ] Documentation has been added to all open, and public scoped methods and properties.
[ ] Changelog has been updated
[ ] Tests have have been added to all new features. (not a requirement, but helpful)
[ ] Image/GIFs have been added for all UI related changed.

Tried Chrome first, saw three missing images.  Caveat: I haven't done any debugging to see what the problem is yet.

Not quite ready for prime time, I think, given the image troubles and the hackery I'm doing to use the Pods folder.

Just a guess here, but the image is enclosed in an HREF to link to that very image.  Remove the encompassing  and the three images should work.

Closed in favor of https://github.com/ProjectDent/ARKit-CoreLocation/commit/2f5a8bfb237b4806c2f8eddfcdf95414886627e3.


Add the ability to reopen closed tabs with a shortcut

Note that v1.13 now has the feature to reopen closed tabs (without full history, though).


Fix nested parametric timestamp compatibility with older clients

Some for DESCRIBE INPUT?

Some for DESCRIBE INPUT?

Yes. I'm on it

We need the same treatment for InformationSchemaPageSource.addColumnsRecords

presto-oracle failed due to network flakyness


Add tokyo-night storm and moon

Describe your request
as the title says, if possible please add tokyo night storm and moon variants as well
Resources
https://github.com/folke/tokyonight.nvim

+1

Can we please also add Day? (Or Light as it's known in VSCode.) Light mode users do exist.

I can work on this if possible. I can add the Storm and Day variants. However, I probably won't do the Moon variant as it doesn't seem to be a variant that is listed on the official repo.

@foster-hangdaan The moon variant is the most popular, as it is used by the author of folke/tokyonight.nvim himself.
While https://github.com/tokyo-night/tokyo-night-vscode-theme (enkia) was the original, you'll notice that https://github.com/folke/tokyonight.nvim is more widely adopted, and often serves as a reference for other implementations.

https://github.com/folke/tokyonight.nvim: 6.1k stars
https://github.com/tokyo-night/tokyo-night-vscode-theme: 1.7k stars

For any folke/tokyonight moon variant users, before it gets ported to Doom, you can use doom-moonlight, which is similar.

@foster-hangdaan The moon variant is the most popular, as it is used by the author of folke/tokyonight.nvim himself.
While https://github.com/tokyo-night/tokyo-night-vscode-theme (enkia) was the original, you'll notice that https://github.com/folke/tokyonight.nvim is more widely adopted, and often serves as a reference for other implementations.
* `https://github.com/folke/tokyonight.nvim`: 6.1k stars

* `https://github.com/tokyo-night/tokyo-night-vscode-theme`: 1.7k stars

I'll add the Moon variant to #835 when time permits in order to close this issue in one shot.

@foster-hangdaan The moon variant is the most popular, as it is used by the author of folke/tokyonight.nvim himself.
While https://github.com/tokyo-night/tokyo-night-vscode-theme (enkia) was the original, you'll notice that https://github.com/folke/tokyonight.nvim is more widely adopted, and often serves as a reference for other implementations.
* `https://github.com/folke/tokyonight.nvim`: 6.1k stars

* `https://github.com/tokyo-night/tokyo-night-vscode-theme`: 1.7k stars

I'll add the Moon variant to #835 when time permits in order to close this issue in one shot.

if possible, an even better option would be to probably tweak all themes according to the neovim theme since ngl those themes look really beautiful

if possible, an even better option would be to probably tweak all themes according to the neovim theme since ngl those themes look really beautiful

Yeah, this what I also had in mind.


Implement interface and struct tags for structural information.

The vast majority of da's output a status response of some kind, this can be simplistic from a "On/Off" or more complicated for "Power Supply".
At the moment any consumer (shimmeringbee/controller especially) has to have code to convert these structures into JSON, infact there is an developer overhead with added any new Capability.
However, for forethought (or dumb luck), all capabilities that have data to return do so via a function that looks a bit like:
func Status(context.Context, da.Device) interface{} (though not actually an interface{})
Using struct tags and reflection it would be possible to instruct consumers (such as shimmeringbee/controller) on how to display these structures.
While we absolutely could use json tags, JSON may not be our only output format - further the MQTT and Websocket outputs of the controller have the ability to output specific messages for individual field or smallest grouping of fields. A specific struct tag could permit us to calculate where these lines are.
With a little more thinking on the function prototype, or figuring out how to invoke Status generically on all capabilities it may be possible to remove large amounts of the controller code and reduce developer overhead adding new capabilities.

The existing Status function with its capability specific return type is great for small scale, however it should be possible to generify.
The typing information IS helpful for developing directly against a da, but not that useful when used more generically. I don't think there are any other users of da or zda to be honest, so we could breaking change (major version bump), or add another function to every da that returns interface{}.
Unless there's something we can do with generics? Will have to read up.


ImageUpload in asp net core on Debian Error

Hello,
I'm need some help.
I deployed the application based on Srenity to a Debian server with Kestrel and running a service to redirect do localhost:5000.
The application is working, but, when I try set de UserImage, I get the error status 500 on TemporaryUpload method....
{"Error":{"Code":"Exception","Message":"An error occured while processing your request."}}

@fabio-basedev have you changed the permitions to correct ones, please try to 777 just to see if that is your problem.

Closing due to inactivity.


Make the @yamada-ui/select component headless

script: make-component-headless
package: @yamada-ui/select
Description
Currently, the @yamada-ui/select component has minimal styles set within the component's source code.
We want to make this style transferable to the theme and make the component headless, enabling more flexible UI customization.
Problem Statement/Justification
By making the @yamada-ui/select component headless, we can achieve more flexible styling tailored to the project.
Proposed Solution or API
The styles within the component are mostly defined by css: CSSUIObject and set to a prop named __css. We will transfer these styles to the packages/theme/src/components.
The code below is just an example and not the actual code.
packages/components/input/src/input-group.tsx
const css: CSSUIObject = {
- width: "100%",
- display: "flex",
- position: "relative",
  ...styles.container,
}

packages/theme/src/components/input.ts
baseStyle: {
  container: {
+   width: "100%",
+   display: "flex",
+   position: "relative",
  },
  field: {
    width: "100%",
    minWidth: 0,
    outline: 0,
    position: "relative",
    appearance: "none",
    transitionProperty: "common",
    transitionDuration: "normal",
    _disabled: {
      opacity: 0.4,
      cursor: "not-allowed",
    },
  },
  element: {
    color: ["blackAlpha.600", "whiteAlpha.700"],
  },
},

[!TIP]
In cases where the styles within the component are dynamically changed, there may be instances where it is not possible to transfer the styles to the theme.
In such cases, it needs to be discussed in this issue. Please feel free to send comments to this issue.

Additional Information
The @yamada-ui/select component exists in packages/components/select/src. You need to check all the components in this folder and if they contain styles internally, you need to modify them.
This change could have a significant impact on projects using Yamada UI, so we will work on it within the scope of v2.0.
Please create the branch for working on this issue from the remote branch v2.0, and direct your pull requests to the v2.0 branch as well.
Please select major for the changeset and create a pull request.

@108yen Can I try this issue?

Fixed #1935


Rework hero image block

What
Rework hero image block
See https://trello.com/c/bdr8UDPd/147-rework-hero-image-block
Why
Design requirements.
Screenshots
Before
...
After
...

One additional thought - the changes in height for the hero on desktop (400px) aren't yet applied to the mid page variant. Is it possible to make the mid page consistent with the top of page? Otherwise we'll need to specify different image sizes for each, which will get complicated.


[BUG] - Error: Selected codec was not a supported codec, falling back to negotiating codecs…

UE Version:
UE 5.3.0
Frontend Version:
Latest React
Problem component
Signalling Server, Frontend
Description
Error: Selected codec was not a supported codec, falling back to negotiating codecs…
So i am connecting to the signalling server from another frontend server. While i can connect  and everything seems good, every 60s its disconnecting with code 1006 and in the webconsole i am getting DOMException: Failed to execute 'setCodecPreferences' on 'RTCRtpTransceiver': Invalid codec preferences: invalid codec with name "H264", and its connecting back. I have tested connecting to the signalling server without a frontend server and i have no errors and no disconnects but this only happens when i am connected to the signalling server from another frontend server. I am using the react module
Expected behavior
Connect from the frontend server to the signalling server without disconnecting for 1s and reconnecting back
Platform (please complete the following information):

OS: Linux
Browser: chrome

This sounds strange to me. Am I correct in my understanding that you are running the signalling server on one server and the frontend is hosted on another server that is pointing to the signalling server?
It's not a usual setup but it should be fine. What's interesting to me is that it works fine (I assume you mean it's streaming fine and you can see the video) and then suddenly stops.
It sounds like to me that the connection between the streamer and the frontend is actually being force closed after some time and that the setCodecPreferences error might actually be a side effect of the connection being closed.
Can you verify that the streamer is working fine and there are no errors or log messages relating to disconnections? Can you try the same streamer and try to run the typescript frontend on the signalling server and see if you get the same behaviour?
If you could provide actual logs of each component too, that might help us diagnose what's going on.

I can confirm that using only the signalling server webserver no error at all. There seems likely a problem from my frontend server itself. It seems i am not using the latest react thing. I will try use typescript in the frontend server just for the test. I will keep you informed. Thanks!!


SD card and ENC28J60 Ethernet Interface with ESP32 (IDFGH-8514)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[x] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
I am facing some problem in integrating SD card and Ethernet both on ESP32 over SPI interface.
Hardware setup -
SD card/Etherent - Common Pins
MOSI - 23
MISO - 19
SCK - 18
SD Card - CS - 5, Ethernet CS - 4
DMA Channel - SD Card - 1, Ethernet - 2
Software -
First SD card is initialised successfully and fetch the data from it and then Ethernet is initialised and got the IP address successfully. Now when I try to open the file with fopen command to write some data, get error -
E (936695) diskio_sdmmc: Check status failed (0x107)
I am stuck in the problem and not able to proceed further in developments. If anyone could help me urgently in giving some insights, that would be highly appreciated.
Please let me know if need more details.
Thank you.

SD-SPI uses HSPI(SPI2) Host Bus by default.
ENC28J60 may be using the same bus.
Try isolating the SPI bus.

@nopnop2002, Thank you for your support.
I checked in my code and already isolating the SPI Bus.
For ENC28J60 -     ESP_ERROR_CHECK(spi_bus_initialize(2, &buscfg, 2));
And for SD Card - it is 1 by default.
Still facing the same error.

SD card Initialisation function -
void sdCard_init()
{
    esp_vfs_fat_sdmmc_mount_config_t mount_config = {
#ifdef CONFIG_EXAMPLE_FORMAT_IF_MOUNT_FAILED
        .format_if_mount_failed = true,
#else
        .format_if_mount_failed = false,
#endif // EXAMPLE_FORMAT_IF_MOUNT_FAILED
        .max_files = 5,
        .allocation_unit_size = 16 * 1024};
    sdmmc_card_t *card;
    const char mount_point[] = MOUNT_POINT;
    ESP_LOGI(TAG, "Initializing SD card");

    ESP_LOGI(TAG, "Using SPI peripheral");

    sdmmc_host_t host = SDSPI_HOST_DEFAULT();
    spi_bus_config_t bus_cfg = {
        .mosi_io_num = PIN_NUM_MOSI,
        .miso_io_num = PIN_NUM_MISO,
        .sclk_io_num = PIN_NUM_CLK,
        .quadwp_io_num = -1,
        .quadhd_io_num = -1,
        .max_transfer_sz = 10000,
    };

    printf("Default SPI Host is %d \n", host.slot);

    esp_err_t ret = spi_bus_initialize(host.slot, &bus_cfg, SPI_DMA_CHAN);
    if (ret != ESP_OK)
    {
        ESP_LOGE(TAG, "Failed to initialize bus.");
        return;
    }
    // This initializes the slot without card detect (CD) and write protect (WP) signals.
    // Modify slot_config.gpio_cd and slot_config.gpio_wp if your board has these signals.
    sdspi_device_config_t slot_config = SDSPI_DEVICE_CONFIG_DEFAULT();
    slot_config.gpio_cs = PIN_NUM_CS;
    slot_config.host_id = host.slot;

    ESP_LOGI(TAG, "Mounting filesystem");
    ret = esp_vfs_fat_sdspi_mount(mount_point, &host, &slot_config, &mount_config, &card);

    if (ret != ESP_OK)
    {
        if (ret == ESP_FAIL)
        {
            ESP_LOGE(TAG, "Failed to mount filesystem. "
                          "If you want the card to be formatted, set the EXAMPLE_FORMAT_IF_MOUNT_FAILED menuconfig option.");
        }
        else
        {
            ESP_LOGE(TAG, "Failed to initialize the card (%s). "
                          "Make sure SD card lines have pull-up resistors in place.",
                     esp_err_to_name(ret));
        }
        return;
    }
    ESP_LOGI(TAG, "Filesystem mounted");

    // Card has been initialized, print its properties
    sdmmc_card_print_info(stdout, card);
}

And ENC Initialisation function -
void ethernet_enc28j60_connection(void){
    ESP_ERROR_CHECK(gpio_install_isr_service(0));
    ESP_ERROR_CHECK(esp_netif_init());
    ESP_ERROR_CHECK(esp_event_loop_create_default());
    esp_netif_config_t netif_cfg = ESP_NETIF_DEFAULT_ETH();
    esp_netif_t *eth_netif = esp_netif_new(&netif_cfg);
    ESP_ERROR_CHECK(esp_eth_set_default_handlers(eth_netif));
    // Register user defined event handers
    ESP_ERROR_CHECK(esp_event_handler_register(ETH_EVENT, ESP_EVENT_ANY_ID, &eth_event_handler, NULL));
    ESP_ERROR_CHECK(esp_event_handler_register(IP_EVENT, IP_EVENT_ETH_GOT_IP, &got_ip_event_handler, NULL));

    spi_bus_config_t buscfg = {
        .miso_io_num = 19,
        .mosi_io_num = 23,
        .sclk_io_num = 18,
        .quadwp_io_num = -1,
        .quadhd_io_num = -1,
        .max_transfer_sz = 10000,
    };
    ESP_ERROR_CHECK(spi_bus_initialize(2, &buscfg, 2));

    /* ENC28J60 ethernet driver is based on spi driver */
    spi_device_interface_config_t devcfg = {
        .command_bits = 3,
        .address_bits = 5,
        .mode = 0,
        .clock_speed_hz = 5 * 1000 * 1000,
        .spics_io_num = 4,
        .queue_size = 20,

    };

    spi_device_handle_t spi_handle = NULL;
    ESP_ERROR_CHECK(spi_bus_add_device(2, &devcfg, &spi_handle));

    eth_enc28j60_config_t enc28j60_config = ETH_ENC28J60_DEFAULT_CONFIG(spi_handle);
    enc28j60_config.int_gpio_num = 22;

    eth_mac_config_t mac_config = ETH_MAC_DEFAULT_CONFIG();
    mac_config.smi_mdc_gpio_num = -1; // ENC28J60 doesn't have SMI interface
    mac_config.smi_mdio_gpio_num = -1;
    mac = esp_eth_mac_new_enc28j60(&enc28j60_config, &mac_config);

    eth_phy_config_t phy_config = ETH_PHY_DEFAULT_CONFIG();
    phy_config.autonego_timeout_ms = 0; // ENC28J60 doesn't support auto-negotiation
    phy_config.reset_gpio_num = -1;     // ENC28J60 doesn't have a pin to reset internal PHY
    esp_eth_phy_t *phy = esp_eth_phy_new_enc28j60(&phy_config);

    esp_eth_config_t eth_config = ETH_DEFAULT_CONFIG(mac, phy);
    esp_eth_handle_t eth_handle = NULL;
    ESP_ERROR_CHECK(esp_eth_driver_install(&eth_config, &eth_handle));

    mac->set_addr(mac, (uint8_t[]){
                           0x02, 0x00, 0x00, 0x12, 0x34, 0x56});

    /* attach Ethernet driver to TCP/IP stack */
    ESP_ERROR_CHECK(esp_netif_attach(eth_netif, esp_eth_new_netif_glue(eth_handle)));

    /* start Ethernet driver state machine */
    ESP_ERROR_CHECK(esp_eth_start(eth_handle));
}

ESP-IDF also supports W5500.
If you change ENC28J60 to W5500, you may find some cause.

I don't have this here. I will place an order for this but this will take another a week to be delivered to us.
Meanwhile, can we check what can be the issue using ENC28J60. I don't see hardware fault as they (SD card and ENC) both are working perfectly fine independently.
Facing problem when working together.

        .mosi_io_num = PIN_NUM_MOSI,
        .miso_io_num = PIN_NUM_MISO,
        .sclk_io_num = PIN_NUM_CLK,
    slot_config.gpio_cs = PIN_NUM_CS;

Are these GPIOs used by SDSPI overlapping with the GPIOs below?
        .miso_io_num = 19,
        .mosi_io_num = 23,
        .sclk_io_num = 18,
        .spics_io_num = 4,
    enc28j60_config.int_gpio_num = 22;

MISO, MOSI, CLK are same for both.
CS pin is different - for SDSPI it is 5, and for ENC it is 4.

MISO, MOSI, CLK are same for both.

I don't know if the same pins can be used on different SPI-BUSes.

You do not need to initialize SPI  Bus twice, probably it is a problem (you over init previos settings)!
Comment out
 ESP_ERROR_CHECK(spi_bus_initialize(2, &buscfg, 2));
SPI bus could have multiple device connected.
Just use same SPU Bus / Host for Ethernet.

@Maksons , Thank you very much for your response. This absolutely solves the problem. I am now able to use both on same bus.
@nopnop2002 , thanks for your help too.


Add back connect function

Currently we get quite some issues where people used mongojs.connect which is gone in 1.0.x versions. We could easily bring this function back. Question is: should we?
What do you think @mafintosh @watson @sorribas

:-1: thats why we bump the major version. We could at notice to the README though

:+1: for your :-1: will add a breaking changes section

Added "upgrading from 0.0.x to 1.0.x" section: https://github.com/mafintosh/mongojs/commit/e1157b04628d83f41b3e2ca3710c2cdec89a7dd8#diff-04c6e90faac2675aa89e2176d2eec7d8

Yeah, people should just learn to use the new API.
In extreme cases I've previously had success with writing an upgrade guide and linking to it from the readme when refactoring/breaking an API:
Case of point from the opbeat-node README.md:

Important: If you've been using version 0.3.x or earlier, please read our upgrade guide.


Create 2 services for brokers: a headless service with publishNotReadyAddresses and an ordinary clusterip service for lookups

Is your feature request related to a problem? Please describe.
Pulsar brokers use Zookeeper for publishing the membership to other brokers.
The Pulsar load manager will detect a new broker and assign new namespace bundles to the new broker.
One of the gaps with Pulsar and k8s is that the broker registers itself to Zookeeper and the broker pod
cannot be accessed before the broker pod's readiness probe check has passed and k8s marks the pod ready
and makes it available in DNS. There's also additional delay from DNS caches. This delay will cause a short service disruption for all topics belonging to the namespace bundles that have been assigned to the new broker.
For the brokers, there's also other reasons: the headless service has "publishNotReadyAddresses: true" and other service (which would be used for lookups) doesn't, so that lookups go only to healthy brokers.
Headless broker services with a lot of brokers could cause issues with Pulsar clients that are running on Alpine <3.18. k8s  docs have something about this too: https://kubernetes.io/docs/tasks/administer-cluster/dns-debugging-resolution/#known-issues  .
"If you are using Alpine version 3.17 or earlier as your base image, DNS may not work properly due to a design issue with Alpine. Until musl version 1.24 didn't include TCP fallback to the DNS stub resolver meaning any DNS call above 512 bytes would fail. Please upgrade your images to Alpine version 3.18 or above."
Since headless services return all hosts in the DNS response, it could exceed 512 bytes.
Describe the solution you'd like
The way to mitigate this is to have a separate ClusterIP service to be used for lookups and have a headless service with
"publishNotReadyAddresses: true". This is a common way to address the problem. One example of this is the
Bitnami Zookeeper Helm chart, https://github.com/bitnami/charts/tree/main/bitnami/zookeeper/templates
there's svc.yaml and svc-headless.yaml
"StatefulSets currently require a Headless Service to be responsible for the network identity of the Pods."
https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/#limitations
Since brokers use a statefulset, the headless service cannot be removed.
The DNS names of the 2 services will be different. Since clients don't need to know the direct DNS names of the brokers, it's better to change the current headless service to be the ClusterIP service and add a new headless service for handling the stable names of the brokers. Admin scripts that connect directly to individual brokers might break, but that's could be made clear in the release notes when this feature is released.

It's possible that making a change to use podManagementPolicy: OrderedReady for the broker statefulset could be a partial mitigation to this issue until this is resolved. #474 adds a solution where podManagementPolicy: OrderedReady is used when the function worker is enabled in the broker. it's not currently possible to configure to use this explicitly in the Helm chart without modifications.

the podManagementPolicy workaround is implemented in #525


feat(instrumentation-pino): add log sending to Logs Bridge API

This adds "log sending" -- sending log records to the Logs SDK -- for the pino logger.
(The same was done for Bunyan in #1713 and Winston in #1837.)

When a Pino logger is created, this wraps the logger instance's output stream with a pino.multistream that sends to the original and to the Logs SDK (class OTelPinoStream).
This adds disableLogSending and disableLogCorrelation options, the same as in instr-bunyan and instr-winston

Limitations:

This does not yet add support for the logSeverity option. I prefer to do that in a separate change, because it might be involved with Pino loggers configured with custom levels.
This does not yet test log sending in the ESM tests. I'll add that separately, because it requires some updates to the contrib-test-utils package.

reviewer notes
The test file changes on this PR assume that https://github.com/open-telemetry/opentelemetry-js-contrib/pull/2247 gets merged first. Please review that PR first. After that is merged, then the test file changes here will be additive and more clear.
Update (2024-06-10): This is done now, so this PR is now ready for review.
checklist

[x] passing CI
[x] TAV tests
[x] discuss pino-opentelemetry-transport alternative and trade-offs
[ ] separate issue for logSeverity
[ ] separate issue for log-sending tests with ESM
[ ] consider a separate issue for translating the default Pino errSerializer format to https://github.com/open-telemetry/semantic-conventions/blob/main/docs/exceptions/exceptions-logs.md (ditto for Bunyan and Winston?)

@hectorhdzg Would you be interested in reviewing this as well? I'm not sure if Pino is as important to some of the work you are doing as Winston.

@trentm changes look good, my only question is related to pino-opentelemetry-transport usage , sorry if this was discussed somewhere else, why not using this package and patching the logger construction similar to Winston? is this related to having older pino version support?

my only question is related to pino-opentelemetry-transport usage , sorry if this was discussed somewhere else, why not using this package and patching the logger construction similar to Winston? is this related to having older pino version support?

@hectorhdzg It hasn't been discussed elsewhere, so it is a good question.
The decision to not just suggest users use pino-opentelemetry-transport (POT) for log sending was not about having older pino version support.  The log-sending support implemented here requires pino@7 or later.  The current POT requires pino@8 or later, so I guess there is a difference in Pino versions supported. However, that wasn't a reason for my choice. (Pino 7 isn't being maintained anymore -- last release was in 2022 -- so there isn't much value is in support it with a new feature.)

why not using this package and patching the logger construction similar to Winston?

Please correct me if I miss something, but I see this as two separate questions.
instrumentation no longer patches the logger constructor args
First, why I moved away from patching the logger constructor to instead creating the Logger instance and then tweaking it.
I found that coping with all the possible input combinations to pino(...) and patching them to a form that does what we need was difficult.  https://getpino.io/#/docs/api?id=destination describes a lot of possible inputs:

destination (Number | String | Object | DestinationStream | SonicBoomOpts | WritableStream)

This is the Pino internal code for normalizing the given pino() args: https://github.com/pinojs/pino/blob/a41b4d3c409b31529c8bcb4bf3cd4e016da8a8de/lib/tools.js#L290-L340
It has been a few weeks, but IIRC, because that buildSafeSonicBoom is internal I'm not sure that it is possible to accurately patch the input arguments and never change the semantics. As a minor example, the current instrumentation-pino throws on pino(2) -- which granted is an invalid pino() argument, but the instrumentation shouldn't break usage:
% cat sadpino.js
const pino = require('pino')
const log = pino(2)
log.info('hi')

% node sadpino.js
{"level":30,"time":1719270084687,"pid":83775,"hostname":"peach.local","msg":"hi"}

% node -r @opentelemetry/auto-instrumentations-node/register sadpino.js
OTEL_TRACES_EXPORTER is empty. Using default otlp exporter.
OpenTelemetry automatic instrumentation started successfully
/Users/trentm/tmp/asdf.20240624T155854/node_modules/@opentelemetry/instrumentation-pino/build/src/instrumentation.js:122
            options.mixin = this._getMixinFunction();
                          ^

TypeError: Cannot create property 'mixin' on number '2'
    at PinoInstrumentation._combineOptions (/Users/trentm/tmp/asdf.20240624T155854/node_modules/@opentelemetry/instrumentation-pino/build/src/instrumentation.js:122:27)
    at /Users/trentm/tmp/asdf.20240624T155854/node_modules/@opentelemetry/instrumentation-pino/build/src/instrumentation.js:55:47
    at Object.<anonymous> (/Users/trentm/tmp/asdf.20240624T155854/sadpino.js:2:13)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1310:10)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:86:12)
    at node:internal/main/run_main_module:23:47

Node.js v18.18.2

After the pino logger is created, it has a well-defined shape that can be patched cleanly.
why not just use 'pino-opentelemetry-transport'?
This could either mean that we get instrumentation-pino to automatically use
'pino-opentelemetry-transport' (POT), or just document to users that they should
use POT for log-sending with Pino.
On the "for using pino-opentelemetry-transport" side:

It is maintained by the Pino community. In addition to being associated with Pino, it also would theoretically mean less maintenance for OTel JS. Both are positives.
The design of using a worker thread means that in most situations (environments that aren't constrained to a single CPU), there will be less JSON.parse and OTLP serialization CPU work on the main thread.

My arguments for implementing it without POT are:

Architecturally, POT differs a lot from our other instrumentations. It runs code in a separate worker-thread. AFAIK no other OTel instrumentations do that. In depends on (https://gist.github.com/trentm/95c1821bf84335eac0ba8c9a5dbf948d) and starts its own OTel SDK components. I think the dependencies alone rule it out as something that we could include by default in auto-instrumentations-node.
Also on the architectural difference: There is a lot more complexity with POT that I worry would lead to more support effort. It starts its own OTel SDK components in the separate thread. The current usage of node -r @opentelemetry/auto-instrumentations-node/register ... with also start an SDK in any worker threads, because -r ... preload modules are passed to worker threads unless the code starting the worker does something special. Granted this is an issue orthogonal to Pino transport usage, that we should discuss separately. (E.g. Should the auto-instrumentations-node/register entry point have a guard to only run in the main thread?)
A lesser complexity: For POT to include traceId/spanId in LogRecords, it relies on the trace_id / span_id fields to be on the log record. The implementation in this PR does not. The fairly-recently added logKeys option to instrumentation-pino allows users to change the log fields to myTraceId or whatever. This will break having span context fields in LogRecords in POT.
This is perhaps more my personal opinion: I'm not convinced that most users of a logger need the more complex design of a sending on a separate thread to free up CPU cycles on the main thread.
Assuming that we cannot include POT in instrumentation-pino by default, then the current implementation (not using POT) offers the benefit of being something that can be enabled by default -- for "zero-code" instrumentation. Granted we could get instrumentation-pino to "do log-sending only if require('POT') works" -- but I think that is subtle behaviour that is best avoided if possible.

Downsides of adding log-sending support to instrumentation-pino:

It adds some potential confusion for users wanting to use Pino and OTel. They may need to now understand both options and choose between them, or ensure they work together.

Sorry, that got long.


Kiosk Selector highlighting

I'm really liking this fluorescent yellow outline selector for the Kiosk!
Could we use that same styling for everything?  Add Game, Delete Game, Retry, Return to Menu, etc.

I also like it a lot! I agree it would be nice to use it everywhere. I'll mock it in the Figma to make sure it works well on all screens.


[Store config 4 of 4] UsersStore, UserStore, VirtualNetworksStore, VisibilityStore, MesosStateStore

This PR moves registering of stores their respective constructors instead of it being handled in StoreConfig.
Functionally there is no change from this PR.
Includes the following stores:

UsersStore
UserStore
VirtualNetworksStore
VisibilityStore
MesosStateStore

Reviewer: @jfurrow

mesosphere-ci Retest this please

This PR:

Master:

Same tests are failing

This PR fixes the broken tests: https://github.com/dcos/dcos-ui/pull/885

Looks good! yay!

I'm a big fan of tell, don't ask, I'm a big fan of these PRs.


prepare for 0.12

Closes #2203

#2204  👈 (View in Graphite)
main

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


Adds koa route

The options you added (endpoint and prefix) could be useful in the existing router.  Still would like to hear how the existing router didn't work for koa users before merging this.
Thanks! 👍

@seanadkinson Express routers don't work at all in Koa. Koa is similar, but uses generators, and instead of req and res, it uses this.
There are a few other differences in here I should fix, like I took out the forward slash check on the key for some reason. But if there's interest I'll clean it up. Also the /s3/img stuff should be tested by someone else since I don't really use that in my app.

Yeah, I think we can merge.  Ideally this package is split up into s3-uploader-react and s3-uploader-express (and s3-uploader-koa with this addition), but I just haven't gotten around to it, nor do I think I will anytime soon.
So we can just provide the router code that someone may or may not use, if you'd like to make the couple changes you mentioned.  The main thing I want is to not download the koa package if I'm not using it, so just cleaning up package.json.  Side note, I think optionalDependencies is where you could specify express and koa in these cases, meaning don't download it, but people should have it if they use certain features of the package.

@OKNoah Has any more work been done on this? I'm in favour of splitting this out into 3 packages as @seanadkinson suggested. I need this for a project, so I'm going to take the work you did and publish it separately. I'll reference this PR to give you credit

Published as a separate package: https://www.npmjs.com/package/koa-s3-sign-upload


More network info

Hi Guys
We wanted to include more info in about the networks so added some more data.
Also fixed the two if statements to just make one if statement.
Thanks for opening a Pull Request!
Here's a handy checklist to ensure your PR goes smoothly.

[x] I signed Google's Contributor License Agreement
[x] My code conforms to Google's python style.
[x] My PR at a minimum doesn't decrease unit-test coverage (if applicable).
[x] My PR has been functionally tested.
[x] All of the unit-tests still pass.
[x] Running pylint --rcfile=pylintrc passes.

These guidelines and more can be found in our contributing guidelines.

im confused why all the other commits are  listed as commits but they dont show up in the diff and it was only one commit that i did :/


tdLoading until star syntax gives error in A2 Language Service: the template context does not have an implicit value

This repository's issues are reserved for feature requests and bug reports.
Do you want to request a feature or report a bug?
Bug
Bug Report
On the tdLoading documentation page (https://teradata.github.io/covalent/#/components/loading) under header '[tdLoading] until star syntax with variable reference and observables', the code tab, the first line of the template is currently
<div *tdLoading="let items until listObservable | async; type: circle; color: accent">
This gives an error in the Angular Language Service 'the template context does not have an implicit value'.
Adding the single quotes to this:
<div *tdLoading="'let items until listObservable | async; type: circle; color: accent'">
fixes the error of the Language Service, but does not work.
Is this a bug in the Language Service or in Covalent?
I'm using Angular Language Service v0.1.4 in VSCode 1.13.1 with Covalent version 1.0.0-beta.5-1

I saw this a few days ago, need to figure out if we are missing something that the language service is looking for.
You can the demo code even if the language service complains, its not gonna affect compilation.

Found the issue 😄
This PR will take care of it https://github.com/Teradata/covalent/pull/734


Use Local Appdata for Settings & AutoUpdate

https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx?f=255&MSPPError=-2147217396

Will there be an option to keep using the local .json file? Maybe some sort of portable mode? That'd be great. :)

@karasuhebi Unlikely. I don't think too many users care to look at the .json currently.
The AppData directory is the preferred place to store application related files. The application will still remain 100% portable, just changes the directory of settings.
I will consider adding and "Open Location" button which will take the user directly to the json file.

I wasn't implying I wanted to look at the .json file, I was just asking if there was going to be a portable mode option that I could click or something that would make it so the .json file would be stored along with the application itself so it's easy to move from place to place. An "Open Location" button isn't necessary I don't think. I agree with you that most people won't care to look at the .json file.

Under what scenarios would you be wanting to move the json file?
The .json contains information specific to the current PC/User. These identifiers are likely to cause undefined behaviour when moved to a new PC, especially when using hotkeys.
I don't really see an issue with requiring the user to reselect options when the application is run under a new environment.
The open location, would be only for those who want to move/make a copy of the json file.

Oh I didn't realize there was that kind of specific information in the .json file to where it would potentially cause issues to move it around between systems. Never mind then. I just thought it would have been nice to have a portable mode.

Yeah each and every sound device gets a unique identifier, and that identifier is used for hotkeys, favourites, startup etc...
Best that they don't wander from PC to PC unless the user intentionally wants to.

unless the user intentionally wants to.

Well that's a valid reason to have "portable mode" as an option then haha ;)


accuracy format

Hello,
First of all, I would like to thank you for your work. I have a question concerning accuracy format. I do not understand why there is more than one value

If you look at meta>forward, results are in the following order.
accuracy before the first update, accuracy after the first update, accuracies for each update steps (set in args)


issue #339 (Replace package.json in .mdw folder with package.yaml)

The package.json for com.centurylink.mdw.tests.routing is having the grouped attributes like below
"attributes": {"mdw.task.resume.notify.endpoint": {"mdw.task.resume.notify.endpoint": "http://mdwapp:ldap_012@localhost:8989/mdw"}},
Since mdw6 does not support grouped attributes , I changed it as non grouped attribute in package.yaml
attributes:
mdw.task.resume.notify.endpoint: http://mdwapp:ldap_012@localhost:8989/mdw

Hi Don,
I have made the requested changes. Designer works fine with package.json for versions equal or higher 6.0.13 but if there is any new package created/imported from mdwhub, it will be the package.yaml that gets created by default. App teams need to upgrade their designer plugin to support this format.


⚠ Secret Website 3 has degraded performance

In 0c8f910, Secret Website 3 ($SECRET_WEBSITE_3) experienced degraded performance:

HTTP code: 200
Response time: 2555 ms

Resolved: Secret Website 3 performance has improved in 8aa59aa.


Pr/compass handlers

Added a decorator for placing a target block in the world. The type of block may be specified, and may be randomly placed according to an origin and radius. When a compass spawns in the agent's inventory, the compass points to it.
Added observations from compass, taking in compass location and outputting relative coordinates and offsets. If no compass is in the agent's inventory, the information is curtailed, even if the same information could be relayed.
Added forced world generation for a single specified biome. The biome is specified by the official biome ID for Minecraft. If the ID is -1, the world generates like normal.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: ccodel sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Closed because made new commit removing binary files


Deactivate colors when running on a console that does not support ansi escape chars

A simple (but far from perfect) fix would be to disable the colors if the code is run on windows.

Actually I think that the first thing to do would be to just have the option to manually activate or deactivate the colors. Maybe later we can work on making that automatic but from a quick research it looks like it's really hard to make it work on all consoles.


build: Add version details to binary

Generate a version string containing version number and commit that the
agent logs in when initialising the logger.
Signed-off-by: James O. D. Hunt<EMAIL_ADDRESS>

Once this lands, I'll do something similar for the shim and proxy.

Hi @jcvenegas - branch updated.

LGTM

LGTM


Zoom out one level, rather than an entire document?

Right now this can only be done by the mouse. Would love to add a command with keyboard shortcut to it.

@tonyxiao thank you for your feedback! Closing this issue because it duplicates https://github.com/vslinko/obsidian-zoom/discussions/28


Invoke Argo Rollouts AnalysisRuns as part of Freight verification

Proposed Feature
Today, verifying a Freight is equivalent to waiting for the Argo CD application (if specified) to reach a healthy state.
We want to extend this to do other things, including:

running user-defined tests/scripts (e.g. kicking off a Kubernetes Job that must return success)
querying metrics (prometheus, datadog, custom API endpoints, etc...) and ensuring KPIs are met

The way we should support the above is to re-use Argo Rollout's Analysis feature which does pretty much exactly what we want.
Motivation
Today, CI is commonly handling the testing aspect of post-promotion. If Kargo is to replace all facets of promotion in a deployment pipeline, it must be able to run user-defined tests.
Suggested Implementation
The approach will be very similar to our Argo CD integration, which does the following:

After freight is promoted, we sync the ArgoCD app
Then we wait until the app is healthy before marking the freight as verified in the stage

The Argo Rollouts Analysis would be done similarly:

After freight is promoted, and after the Argo CD app is healthy, we kick off an AnalysisRun
Then we wait until AnalysisRun is successful before marking the freight as verified in the stage

Kargo will need to add an analysis stanza to the stage spec, where it references one or more AnalysisTemplates:
      analysis:
        templates:
        - templateName: success-rate
        args:
        - name: service-name
          value: guestbook-svc.default.svc.cluster.local

When the Stage reconcile is trying to verify Freight after promotion, it would create an AnalysisRun from the referenced AnalysisTemplate(s). This is how it is done in Rollouts (we would have similar logic):
https://github.com/argoproj/argo-rollouts/blob/54d83d676b10d8246766bdbd5d407c0d39e3d9d0/utils/analysis/helpers.go#L291-L322
One difference from the above logic, is that we should avoid import dependency on Argo Rollouts. So the above logic will need to be translated to deal with unstructured objects, so we preserve all fields of an AnalysisTemplate when converting it to an AnalysisRun.
We would also need an informer on analysisruns that waits until AnalysisRun status.phase is completed (just like we have an informer on applications that waits until applications are healthy.

I can think of several:

Rollouts operate on a single workload and during the update. You may need analysis to be performed at a conceptually higher level (e.g. after multiple microservices are deployed and reach healthy, or after the whole Argo CD application becomes healthy)
If you aren't using Argo Rollouts
If promotion is not even Kubernetes based, but is promoting config for something else (e.g. terraform, uploading assets to CDN).

The first point is super valid! at least in our case. Fingers crossed!

This was closed by #1259


Minor punctuation correction in comments.

This PR should probably be directed at visualfsharp. Changes flows from there to here, and from here to FSharp.Compiler.Service. We're trying to keep diffs between these repos minimal. Changes targeted at improving cross-platform issues should go here.

Thanks ... will make it over there along with the issue I filed.


wait for cloud to be ready

looks ok. Would be better if we can add some tests for it.

@wei-lee test is here https://github.com/feedhenry/fh-js-sdk/blob/master/test/tests/test_push.js


Development: Adds basis for detecting flaky E2E tests with coverage

Checklist
General

[ ] I tested all changes and their related features with all corresponding user types on a test server.
[ ] This is a small issue that I tested locally and was confirmed by another developer on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

I have not changed actual application code.
Motivation and Context

As part of my thesis I want to bring the flaky test detecting version of E2E tests online in the regular Artemis development flow. Currently it should be run in parallel to see if there might be unintended disadvantages such as more failures or longer build times.
Description

Adds a new docker compose and related files to run E2E tests with full coverage across both server and client. This allows detecting flaky tests by comparing the covered files to changed files since the last time the build was green.
All changes where made in a way that ensures, the regular E2E tests are not affected check them here
You can check the flake detection enabled plan here
Review Progress

Code Review

[ ] Review 1
[ ] Review 2

Manual Tests

[ ] Test 1
[ ] Test 2

Exam Mode Test

[ ] Test

Screenshots

Changes allow tagging failing Bamboo builds as suspected flaky and will report a positive status to GitHub if all fails are suspected to be flaky.

This PR already includes the flake detection plan and will report it's feedback

Codecov Report

Merging #5950 (ef11b27) into develop (e46bd43) will increase coverage by 0.00%.
The diff coverage is n/a.

Additional details and impacted files
@@            Coverage Diff             @@
##             develop    #5950   +/-   ##
==========================================
  Coverage      79.90%   79.90%
  Complexity     12366    12366
==========================================
  Files           2126     2126
  Lines          84342    84342
  Branches       12652    12652
==========================================
+ Hits           67393    67396    +3
+ Misses          9417     9414    -3
  Partials        7532     7532

Impacted Files
Coverage Δ

...pp/app/lti/lti13-dynamic-registration.component.ts
86.36% <0.00%> (-0.60%)
:arrow_down:

...webapp/app/shared/metis/post-overview.directive.ts
86.48% <0.00%> (+0.18%)
:arrow_up:

...ce/scheduled/ParticipantScoreSchedulerService.java
83.44% <0.00%> (+1.32%)
:arrow_up:

...e/scheduled/WeeklyEmailSummaryScheduleService.java
68.96% <0.00%> (+3.44%)
:arrow_up:

Flag
Coverage Δ

client
75.70% <ø> (ø)

server
84.56% <ø> (+<0.01%)
:arrow_up:

Continue to review full report at Codecov.

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

Adding jars to the repo is not recommended. Could we also add this as test dependency?

Adding jars to the repo is not recommended. Could we also add this as test dependency?

That's actually something I wanted to look into after the general idea works, they are needed during regular execution so a test dependency is probably the wrong place.
I'm not too familiar with how I can add them as a normal dependency but will make sure to have a look before moving this out of draft.

@krusche I have removed the jars from the repo and added the jacoco agent as a regular dependency.
For the flaky tests I extract it from the Artemis .war file and attach it as a java agent.
Other changes in this PR should be good to go. The regular E2E tests are still passing and are not affected

@heddendorp I just had a thought which could lead to problems. So far, I think we are just starting up Artemis instances for the E2E tests on the bamboo agents. If we start up the same named containers also for this new bamboo task, we could potentially run into problems. Not sure how docker names the containers and volumes for the old cypress setup. We should maybe take a look at that before merging.

@heddendorp I just had a thought which could lead to problems. So far, I think we are just starting up Artemis instances for the E2E tests on the bamboo agents. If we start up the same named containers also for this new bamboo task, we could potentially run into problems. Not sure how docker names the containers and volumes for the old cypress setup. We should maybe take a look at that before merging.

@4ludwig4 I think the bamboo plan runs are sufficiently separated as we run both plans multiple times in parallel already I do not expect any issues.

@heddendorp I just had a thought which could lead to problems. So far, I think we are just starting up Artemis instances for the E2E tests on the bamboo agents. If we start up the same named containers also for this new bamboo task, we could potentially run into problems. Not sure how docker names the containers and volumes for the old cypress setup. We should maybe take a look at that before merging.

@4ludwig4 I think the bamboo plan runs are sufficiently separated as we run both plans multiple times in parallel already I do not expect any issues.

Just looked it up and Bamboo seems to just run one task at a time per agent, so we should be good!

@Mtze thanks for your feedback, should be resolved now


Add ruff to DEFAULT_UTILS in python

Ruff is currently one of the fastest growing tools in terms of adaption in the Python community. Many large projects have adopted it.
For example, it has many more stars than many of the other projects listed here.

devcontainers:main

@microsoft-github-policy-service agree

@samruddhikhandale, I believe I have addressed all suggestions.
Can we get this merged? 😄


[#85] Removed redundant "lambda$" filter.

@rultor merge

@rultor merge

@skapral OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@skapral Done! FYI, the full log is here (took me 3min)


question: How to Diagnose Overfitting and Underfitting of Tesseract Models?

Is there a way to diagnose Overfitting and Underfitting of Tesseract Models?
@stweil had suggested in a different thread that one should evaluate all models to find the best fit for the eval data.
Is there a way to extract the checkpoint details of number of iterations and training CER and CER from lstmeval  to find the best model and graph the results, similar to the output shown in this article for Keras.

@Shreeshrii Not sure about lsmeval but the file names of the checkpoints itself encode training CER and number of iterations:
$ ls -lrt
total 891036
-rw-rw-r-- 1 kmw kmw 34427398 Sep  2 13:13 boernerianus_checkpoint
-rw-rw-r-- 1 kmw kmw 17212641 Sep  2 13:13 boernerianus_71.96_9294_9300.checkpoint
-rw-rw-r-- 1 kmw kmw 17212665 Sep  2 13:13 boernerianus_68.251_9493_9500.checkpoint
-rw-rw-r-- 1 kmw kmw 17212689 Sep  2 13:13 boernerianus_64.962_9689_9700.checkpoint
-rw-rw-r-- 1 kmw kmw 17212713 Sep  2 13:13 boernerianus_62.498_9889_9900.checkpoint
-rw-rw-r-- 1 kmw kmw 17212737 Sep  2 13:13 boernerianus_61.812_10087_10100.checkpoint
-rw-rw-r-- 1 kmw kmw 17212749 Sep  2 13:13 boernerianus_59.662_10185_10200.checkpoint
-rw-rw-r-- 1 kmw kmw 17212785 Sep  2 13:13 boernerianus_57.284_10471_10500.checkpoint
-rw-rw-r-- 1 kmw kmw 17212821 Sep  2 13:13 boernerianus_54.814_10761_10800.checkpoint
-rw-rw-r-- 1 kmw kmw 17212857 Sep  2 13:13 boernerianus_52.799_11221_11300.checkpoint
-rw-rw-r-- 1 kmw kmw 17212917 Sep  2 13:13 boernerianus_49.958_11685_11800.checkpoint
-rw-rw-r-- 1 kmw kmw 17212941 Sep  2 13:13 boernerianus_45.862_11873_12000.checkpoint
-rw-rw-r-- 1 kmw kmw 17212953 Sep  2 13:13 boernerianus_44.034_11965_12100.checkpoint
-rw-rw-r-- 1 kmw kmw 17212965 Sep  2 13:13 boernerianus_41.24_12054_12200.checkpoint
-rw-rw-r-- 1 kmw kmw 17212977 Sep  2 13:13 boernerianus_38.882_12145_12300.checkpoint
-rw-rw-r-- 1 kmw kmw 17212989 Sep  2 13:13 boernerianus_36.6_12242_12400.checkpoint
-rw-rw-r-- 1 kmw kmw 17213001 Sep  2 13:13 boernerianus_32.697_12328_12500.checkpoint
-rw-rw-r-- 1 kmw kmw 17213013 Sep  2 13:13 boernerianus_30.751_12416_12600.checkpoint
-rw-rw-r-- 1 kmw kmw 17213025 Sep  2 13:13 boernerianus_28.325_12509_12700.checkpoint
-rw-rw-r-- 1 kmw kmw 17213037 Sep  2 13:13 boernerianus_26.503_12602_12800.checkpoint
-rw-rw-r-- 1 kmw kmw 17213049 Sep  2 13:13 boernerianus_24.218_12681_12900.checkpoint

You can always “finish” a checkpoint and convert it into a working Tesseract model via lstmtraining --stop_training. In doing so, you can create a set of models which than can be tested against an evaluation set but may also be used for superior calamari-like application of different training stages at once.

you can create a set of models which than can be tested against an evaluation set

I have recently tried, splitting the training data into three sets. Eg. Using 80% for training and keeping 10% for eval during training and 10% for validation test with the traineddata files from checkpoints.
I find that there are differences in the training CER for a checkpoint and the validation set CER for traineddata from same checkpoint. The CER from the eval set used during training is not easily available.
Earlier I thought that the model with the lowest training CER was the best. However after running tests with the validation set, that does not seem to be true, because that might have been overfitted to the training set.
Hence my question ...

used for superior calamari-like application of different training stages at once.

I am not familiar with this. Please elaborate or provide a link with further info.

Here are my results from a validation run:
At iteration 0, stage 0, Eval Char error rate=3.5101527, Word error rate=9.2906778 ***** iast_0.706_419620_1359700.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.5149699, Word error rate=9.0415867 ***** iast_0.576_444984_1500100.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.5472042, Word error rate=9.4882442 ***** iast_0.879_361194_1071400.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.5526628, Word error rate=9.5266959 ***** iast_0.922_361153_1071200.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.6000142, Word error rate=9.2806764 ***** iast_0.598_438064_1461300.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.6119001, Word error rate=9.6337073 ***** iast_0.817_366009_1094100.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.6328469, Word error rate=9.6109486 ***** iast_0.651_419705_1360200.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.6358543, Word error rate=9.7243117 ***** iast_1.113_296390_804400.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.6379109, Word error rate=9.5886973 ***** iast_1.063_297779_809900.checkpoint-fast.traineddata **** gt/list.test
At iteration 0, stage 0, Eval Char error rate=3.6440435, Word error rate=9.4520018 ***** iast_0.786_383730_1177900.checkpoint-fast.traineddata **** gt/list.test

The CER from the eval set used during training is not easily available.

I was able to extract it from the training log file.

At iteration 13291/15800/15800, Mean rms=0.696%, delta=2.443%, char train=8.304%, word train=21.54%, skip ratio=0%,  New worst char error = 8.304
At iteration 7443, stage 0, Eval Char error rate=10.111046, Word error rate=26.474236 wrote checkpoint.

At iteration 16083/19800/19800, Mean rms=0.661%, delta=2.288%, char train=7.113%, word train=19.995%, skip ratio=0%,  New worst char error = 7.113
At iteration 12273, stage 1, Eval Char error rate=7.6912357, Word error rate=21.70712 wrote checkpoint.

At iteration 19430/24800/24800, Mean rms=0.645%, delta=2.155%, char train=6.618%, word train=19.316%, skip ratio=0%,  New worst char error = 6.618
At iteration 15033, stage 1, Eval Char error rate=6.892947, Word error rate=20.06269 wrote checkpoint.

At iteration 21959/28800/28800, Mean rms=0.603%, delta=1.953%, char train=6.338%, word train=19.004%, skip ratio=0%,  New worst char error = 6.338
At iteration 18400, stage 1, Eval Char error rate=6.493667, Word error rate=18.827539 wrote checkpoint.

At iteration 25842/35100/35100, Mean rms=0.6%, delta=2.055%, char train=6.291%, word train=17.961%, skip ratio=0%,  New worst char error = 6.291
At iteration 20948, stage 1, Eval Char error rate=6.2389766, Word error rate=18.548224 wrote checkpoint.

At iteration 28482/39500/39500, Mean rms=0.573%, delta=1.864%, char train=5.943%, word train=17.403%, skip ratio=0%,  New worst char error = 5.943
At iteration 24784, stage 1, Eval Char error rate=5.6843931, Word error rate=16.798239 wrote checkpoint.

At iteration 31742/45000/45000, Mean rms=0.56%, delta=1.862%, char train=6.286%, word train=16.177%, skip ratio=0%,  New worst char error = 6.286
At iteration 27814, stage 1, Eval Char error rate=5.2523296, Word error rate=15.64968 wrote checkpoint.

At iteration 34953/50700/50700, Mean rms=0.531%, delta=1.617%, char train=4.942%, word train=14.97%, skip ratio=0%,  New worst char error = 4.942
At iteration 30103, stage 1, Eval Char error rate=5.283013, Word error rate=16.057397 wrote checkpoint.

At iteration 37589/55500/55500, Mean rms=0.496%, delta=1.382%, char train=4.285%, word train=14.018%, skip ratio=0%,  New best char error = 4.285
At iteration 33926, stage 1, Eval Char error rate=5.0264877, Word error rate=15.354675 wrote checkpoint.

The eval iterations lag behind the training iterations.

I was able to pull out the training CER and eval CER data from the lstmtraining log and then plot it.
Here is the script to extract the data and plot it.
grep 'Eval Char' /home/ubuntu/tess5training-iast/LAYER.log | sed -e 's/^.*[0-9]At iteration //' | \sed -e 's/,.*=/\t/'  | sed -e 's/ wrote.*$//' | sed -e 's/^/\t\t\t/'> plot-eval.txt
grep 'best model' /home/ubuntu/tess5training-iast/LAYER.log |  sed  -e 's/^.*\///' |  sed  -e 's/\.checkpoint.*$//' | sed  -e 's/_/\t/g' > plot-best.txt
grep 'At iteration' /home/ubuntu/tess5training-iast/LAYER.log |  sed -e '/^Sub/d' |  sed -e '/^Update/d' | sed  's/, Mean.*char train=/\t\t/g' |  sed  -e 's/%, word.*$//' | sed  -e 's/At iteration.*\//\t\t\t/g' > plot-iteration.txt
cat plot-header.txt plot-best.txt plot-eval.txt plot-iteration.txt > plot.csv
python plot.py

plot.py
import pandas as pd
import matplotlib.pyplot as plt
dataframe = pd.read_csv("plot.csv",sep='\t', encoding='utf-8')
x = dataframe.TrainingIteration
y = dataframe.TrainingCER
z = dataframe.EvalCER
w = dataframe.IterationCER
plt.title('tess5training-iast - Training and Evaluation CER')
plt.xlabel('Iterations')
plt.ylabel('Character Error Rate')
plt.plot(x, y, 'b', label='Training CER at best model checkpoints')
plt.scatter(x, w, s=1, c='magenta', label='Training CER')
plt.scatter(x, y, c='blue', s=10, label='Best model checkpoint CER')
plt.plot(x, z, 'r', label='Evaluation CER during lstmtraining')
plt.scatter(x, z, c='red', s=10, label='Evaluation CER')
plt.legend()
xcoords = [150000]
for xc in xcoords:
    plt.axvline(x=xc, color='k', linestyle='dotted', ymin=0.0, ymax=0.25)
plt.savefig("plot.png")

Looks like my problem might be using too many lines of training data (about 150000+) and then killing the training process without allowing for enough epochs.

Wow, that's a great tool. Could you add it to the repo and we could think about utilizing it in the Makefile?

Looks like my problem might be using too many lines of training data

The diifference between test and eval is remarkable and could be an indicator for having lines the evaluation set which are very different from what is seen during training. Why is the number of data points for Evaluation CER so small?

I am not familiar with this. Please elaborate or provide a link with further info.

Calamari writes a number of models during its training process (not only the best as Tesseract does). In their papers, @chreul and colleagues propose a strategy called voting -- which is more or less a majority decision over the outputs of multiple models during the recognition stage -- and use all the models created during training as voters.
Now, Tesseract used a different kind of combination of multiple OCR models. It returns the character (or character sequence) which received the highest probability from one of the models. Usually you use e.g. a Greek, a Latin and a Fraktur model when running Tesseract. What one could try to do instead/in addition is the combination of Tesseract models from different stages of the training process (i.e. checkpoints).

What one could try to do instead/in addition is the combination of Tesseract models from different stages of the training process (i.e. checkpoints).

Yes, if I remember correctly, @stweil had recommended using last three checkpoints models to get better results.

The diifference between test and eval is remarkable

The CER is from lstmtraining and the async eval that it runs during training using the eval list.

@wrznr Thanks for pointing out the difference between the evaluation and training error rates. I had accidentally used the WER from the log file instead of CER, for the evaluation run. Have fixed it now.
I can submit the python script as a PR but it has hardcoded values pertaining to my data. It will need to be generalized for use with makefile.
Here are the plots from two different runs of training for Sanskrit which has support for Devanagari, English and IAST (Diacritics to support Sanskrit).

In the old run displayed above, I restarted training a few times, that may account for sharp changes in the eval values. It also has the plot from the validation run.

@Shreeshrii Great stuff!
Since the evaluation error is still on par or even below the training error, you can rule out overfitting and go on to train more iterations.

New improved version of plotting in PR https://github.com/tesseract-ocr/tesstrain/pull/218#issuecomment-747466387

The CER from the eval set used during training is not easily available.

I was able to extract it from the training log file.

At iteration 13291/15800/15800, Mean rms=0.696%, delta=2.443%, char train=8.304%, word train=21.54%, skip ratio=0%,  New worst char error = 8.304
At iteration 7443, stage 0, Eval Char error rate=10.111046, Word error rate=26.474236 wrote checkpoint.

At iteration 16083/19800/19800, Mean rms=0.661%, delta=2.288%, char train=7.113%, word train=19.995%, skip ratio=0%,  New worst char error = 7.113
At iteration 12273, stage 1, Eval Char error rate=7.6912357, Word error rate=21.70712 wrote checkpoint.

At iteration 19430/24800/24800, Mean rms=0.645%, delta=2.155%, char train=6.618%, word train=19.316%, skip ratio=0%,  New worst char error = 6.618
At iteration 15033, stage 1, Eval Char error rate=6.892947, Word error rate=20.06269 wrote checkpoint.

At iteration 21959/28800/28800, Mean rms=0.603%, delta=1.953%, char train=6.338%, word train=19.004%, skip ratio=0%,  New worst char error = 6.338
At iteration 18400, stage 1, Eval Char error rate=6.493667, Word error rate=18.827539 wrote checkpoint.

At iteration 25842/35100/35100, Mean rms=0.6%, delta=2.055%, char train=6.291%, word train=17.961%, skip ratio=0%,  New worst char error = 6.291
At iteration 20948, stage 1, Eval Char error rate=6.2389766, Word error rate=18.548224 wrote checkpoint.

At iteration 28482/39500/39500, Mean rms=0.573%, delta=1.864%, char train=5.943%, word train=17.403%, skip ratio=0%,  New worst char error = 5.943
At iteration 24784, stage 1, Eval Char error rate=5.6843931, Word error rate=16.798239 wrote checkpoint.

At iteration 31742/45000/45000, Mean rms=0.56%, delta=1.862%, char train=6.286%, word train=16.177%, skip ratio=0%,  New worst char error = 6.286
At iteration 27814, stage 1, Eval Char error rate=5.2523296, Word error rate=15.64968 wrote checkpoint.

At iteration 34953/50700/50700, Mean rms=0.531%, delta=1.617%, char train=4.942%, word train=14.97%, skip ratio=0%,  New worst char error = 4.942
At iteration 30103, stage 1, Eval Char error rate=5.283013, Word error rate=16.057397 wrote checkpoint.

At iteration 37589/55500/55500, Mean rms=0.496%, delta=1.382%, char train=4.285%, word train=14.018%, skip ratio=0%,  New best char error = 4.285
At iteration 33926, stage 1, Eval Char error rate=5.0264877, Word error rate=15.354675 wrote checkpoint.

The eval iterations lag behind the training iterations.

Hi @Shreeshrii
I'm referring to Ray Smith blog https://tesseract-ocr.github.io/tessdoc/tess4/TrainingTesseract-4.00.html
In the blog there it is mentioned to use following command for training
training/lstmtraining --debug_interval 100
--continue_from ~/tesstutorial/eng_from_chi/eng.lstm
--traineddata ~/tesstutorial/engtrain/eng/eng.traineddata
--append_index 5 --net_spec '[Lfx256 O1c111]'
--model_output ~/tesstutorial/eng_from_chi/base
--train_listfile ~/tesstutorial/engtrain/eng.training_files.txt
--eval_listfile ~/tesstutorial/engeval/eng.training_files.txt
--max_iterations 3000 &>~/tesstutorial/eng_from_chi/basetrain.log
I'm mentioning the eval_listfile but I'm not getting eval char error rate while training like you get in training.
How can I get such logs in training so that it would be better for me to evaluate the model?

Meanwhile, it turned out that the error values estimated during the training process are not to be trusted: #261

Meanwhile, it turned out that the error values estimated during the training process are not to be trusted: #261

This has been mitigated to some extent by https://github.com/tesseract-ocr/tesseract/pull/3644, which changed the descriptions given during training to reflect more honestly what is calculated.
Regarding the OP's question and @Shreeshrii's proposal for a plotting facility, #377 is the latest incarnation of this.


Allow creating more than one cluster under the same AD

Hi,
I need to create more than one cluster under the same AD and I found out it didn't work as Configure-WSFC.ps1 had the hard coded cluster name.
So, I changed the template and the script to use the stack name instead of the hard coded cluster name.
Thanks.

Going to Close this out, have an update coming out that will parameterize this through the Quick Start.


[Subtask] Optimize CI pipeline tasks to avoid executing unrelated modules.

Describe the subtask
Optimize the pipeline for modules unrelated to gvfs-fuse, such as non-fileset catalogs, Spark connectors, and Trino connectors ...
Parent issue
#5504

@diqiu50 Hi, I want to take this issue, but I want to clarify this first. Does it means that I need to modify the github workflows to skip workflows unrelated to gvfs-fuse?

Yes, we need to check the others' workflow too.


cmsis_dsp: transofrm: error during building cf64.fpu and rf64.fpu for mps2_an521_remote

Describe the bug
Tests libraries.cmsis_dsp.transform.cf64.fpu and libraries.cmsis_dsp.transform.rf64.fpu from tests/lib/cmsis_dsp/transform cannot be built for mps2_an521_remote platform.
To Reproduce
Steps to reproduce the behavior:

Run Twister by command:

./scripts/twister --inline-logs -v -v --overflow-as-error -p mps2_an521_remote -T tests/lib/cmsis_dsp/transform -s tests/lib/cmsis_dsp/transform/libraries.cmsis_dsp.transform.cf64.fpu -s tests/lib/cmsis_dsp/transform/libraries.cmsis_dsp.transform.rf64.fpu

Observe output logs - especially those from building process

Expected behavior
Test should be able to build on mps2_an521_remote platform, or limits in test scenario definition (in testcase.yaml file) should be changed to exclude this platform (then also integration_platform entry should be changed).
Impact
Test introduce misleading information, that cf64.fpu and rf64.fpu tests can be run on mps2_an521_remote, but in fact they can't be.
Logs and console output
From libraries.cmsis_dsp.transform.cf64.fpu:
[ 90%] Linking C executable zephyr_pre0.elf
/home/redbeard/zephyr-sdk-0.13.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
/home/redbeard/zephyr-sdk-0.13.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `FLASH' overflowed by 444604 bytes
collect2: error: ld returned 1 exit status
make[2]: *** [zephyr/CMakeFiles/zephyr_pre0.dir/build.make:123: zephyr/zephyr_pre0.elf] Error 1
make[1]: *** [CMakeFiles/Makefile2:3147: zephyr/CMakeFiles/zephyr_pre0.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

From libraries.cmsis_dsp.transform.rf64.fpu:
[ 90%] Linking C executable zephyr_pre0.elf
/home/redbeard/zephyr-sdk-0.13.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr_pre0.elf section `rodata' will not fit in region `FLASH'
/home/redbeard/zephyr-sdk-0.13.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/10.3.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `FLASH' overflowed by 44116 bytes
collect2: error: ld returned 1 exit status
make[2]: *** [zephyr/CMakeFiles/zephyr_pre0.dir/build.make:123: zephyr/zephyr_pre0.elf] Error 1
make[1]: *** [CMakeFiles/Makefile2:3147: zephyr/CMakeFiles/zephyr_pre0.dir/all] Error 2
make: *** [Makefile:91: all] Error 2

Environment (please complete the following information):

OS: Linux
Toolchain: zephyr-sdk-0.13.1
Commit SHA: b029bfd65c2c4cf0dfb1ffaee381c9236da0b7e2

Same as https://github.com/zephyrproject-rtos/zephyr/issues/44947#issuecomment-1102671532

Okay, so is there any sense to keep in integration_platform entry with mps2_an521_remote platform?

will fix this after https://github.com/zephyrproject-rtos/zephyr/issues/45319 by replacing mps2_an521_remote with mps2_an386.


[question] z2m: Zwave Driver Failed with Aotec USB stick

Hi all, I'm totally new to this project. Got the Docker container for 3.4.1 running on my Raspberry Pi Zero W using an ARMv6 build by @samsonnguyen, made sure I had the correct serial device, etc., but I see the following on startup:
docker-compose up Starting dan_zwave2mqtt_1 ... done Attaching to dan_zwave2mqtt_1 zwave2mqtt_1  |   z2m:Store scenes.json not found +0ms zwave2mqtt_1  |   z2m:Store nodes.json not found +85ms zwave2mqtt_1  |   z2m:Gateway No customDevices file found +0ms zwave2mqtt_1  |   z2m:App Zwave2Mqtt version: 3.4.1 +0ms zwave2mqtt_1  |   z2m:App Application path:/usr/src/app +7ms zwave2mqtt_1  | Initialising OpenZWave 1.6.0 binary addon for Node.JS. zwave2mqtt_1  |         OpenZWave Security API is ENABLED zwave2mqtt_1  |         ZWave device db    : /usr/local/etc/openzwave zwave2mqtt_1  |         User settings path : /usr/src/app/store zwave2mqtt_1  |         Option Overrides : --Logging undefined --ConsoleOutput undefined --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration false --PollInterval 1000 --AutoUpdateConfigFile true zwave2mqtt_1  |   z2m:Zwave Connecting to /dev/ttyAMA0 +0ms zwave2mqtt_1  | 2020-08-23 21:41:30.917 Always, OpenZwave Version 1.6.-1 Starting Up zwave2mqtt_1  | 2020-08-23 21:41:31.077 Always, Using Language Localization  zwave2mqtt_1  | 2020-08-23 21:41:31.136 Warning, Failed - Network Key Not Set zwave2mqtt_1  |   z2m:Zwave Zwave connected, Openzwave version: 1.6.0 +6s zwave2mqtt_1  |   z2m:App Listening on port 8091 +0ms zwave2mqtt_1  |   z2m:Mqtt MQTT client connected +0ms zwave2mqtt_1  |   z2m:App New connection nYTGx3OHCg8WTJBTAAAA +12s zwave2mqtt_1  | 2020-08-23 21:41:45.223 Warning, Download of http://download.db.openzwave.com/images/leviton/vrpa1.png Failed (Node: 0) zwave2mqtt_1  | 2020-08-23 21:41:45.234 Warning, Download of http://download.db.openzwave.com/images/inovelli/lzw36.png Failed (Node: 0) zwave2mqtt_1  |   z2m:Zwave Driver failed { version: '1.6.0' } +8s
The last helpful message I see is the "z2m:Zwave Driver Failed { version: '1.6.0' }" message, so that's basically what I have to go on right now. The web UI shows the Controller status as "unknown" as well. I do not yet have any Z-Wave devices to test with yet, those come later this week.
What are my next steps here?

 I had to use /dev/serial/by-id/ rather than /dev/ttyAMA0 as the device. Weird but hey, it works!

@dbrandesky Sorry for the late reply @dbrandesky , glad you fixed it, sincerly never heard about this bug but good to know hope this can help other users :)


CAMEL-21249 - Camel-Kamelets: Move Kamelets utils in Camel Kamelets component - Move DDB2 part to AWS DDB

Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[x] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally from root folder and I have committed all auto-generated changes.

Done. For the Jackson dependency I need to check if I can remove the component


Ergast ShuttingDown

Proposed new feature or change:
Are you familiar with any alternatives to Ergast? The reason I ask is because Ergast is scheduled to shut down later this year. Even now, the library remains inaccessible.
Does someone have backed up all the data from latest years at least ?

We are working on that already. Currently, the plan is to continue running Ergast in some form but with new maintainers, and potentially with updated infrastructure and an improved server. See #445


Create developer namespace only works for default. Anything else fails it.

The default value for developer namespace is "default". But the user changes it to something else eg:"dev-space" it is reported (in the slack channel) it developer NS fails to install.
Investigate and fix.

fixed. Added grep -w to find the exact name of the dev NS if exiting during ns creation.


Requiring namespace 'Gdk' version '3.0', but '4.0' is already loaded

I have the next error:
Sep 11 11:02:11 LIM-B68SPN2 /usr/lib/gdm-wayland-session[283958]: file:///usr/share/ulauncher/preferences/dist/static/js/app.c7a36559c1151f811a88.js:4919:18: CONSOLE ERROR TypeError: e.cancel is not a function. (In 'e.cancel()', 'e.cancel' is undefined)
Sep 11 11:02:14 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]: 2020-09-11 11:02:14,797 | ERROR | ulauncher.api.server.ExtensionRunner: _run_process() | Extension "com.github.ceroprogramming.ulauncher-pulsecontrol" exited instantly with code 1
Sep 11 11:02:14 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]: 2020-09-11 11:02:14,797 | ERROR | ulauncher.api.server.ExtensionRunner: _run_process() | Extension "com.github.ceroprogramming.ulauncher-pulsecontrol" failed with an error: ImportError: Requiring namespace 'Gdk' version '3.0', but '4.0' is already loaded

Sep 11 11:02:27 LIM-B68SPN2 /usr/lib/gdm-wayland-session[285707]: method return time=1599840147.140305 sender=:1.30 -> destination=:1.900 serial=46 reply_serial=2
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]: 2020-09-11 11:03:08,340 | ERROR | ulauncher.ui.windows.PreferencesUlauncherDialog: on_scheme_callback() | Unexpected API error. KeyError: 'com.github.ceroprogramming.ulauncher-pulsecontrol'
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]: Traceback (most recent call last):
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]:   File "/usr/lib/python3.8/site-packages/ulauncher/ui/windows/PreferencesUlauncherDialog.py", line 198, in on_scheme_callback
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]:     resp = rt.dispatch(self, scheme_request.get_uri())
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]:   File "/usr/lib/python3.8/site-packages/ulauncher/utils/Router.py", line 49, in dispatch
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]:     return callback(context, url_params)
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]:   File "/usr/lib/python3.8/site-packages/ulauncher/ui/windows/PreferencesUlauncherDialog.py", line 436, in prefs_extension_update_prefs
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]:     controller = ExtensionServer.get_instance().get_controller(ext_id)
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]:   File "/usr/lib/python3.8/site-packages/ulauncher/api/server/ExtensionServer.py", line 76, in get_controller
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]:     return self.controllers[extension_id]
Sep 11 11:03:08 LIM-B68SPN2 /usr/lib/gdm-wayland-session[1964]: KeyError: 'com.github.ceroprogramming.ulauncher-pulsecontrol'

Hey, thanks for the report!
I think the second part is just the consequence of the first error.
Anyway, I am not really able to reproduce the error yet. Can you quickly tell me distribution and version you are using?
Wayland, gnome and python3.8 are obvious from the log :)
If you can think of anything else important to reproduce the error I am glad if you share!
Thanks and regards,
Simon

My distribution is arch linux, but I already found the solution, I had installed gtk4-git, I already removed it and everything works fine