Unable to use Umi with Nuxt3

Hi, following Metaplex tutorials I was not able to use Metaplex npm packages with Nuxt3. Is there a way to setup Nuxt3 project without Polyfill issues?
these are my errors im facing when importing {createUmi}

experiencing almost the same problem, using umi always makes my nuxt stop working error
Cannot read properties of undefined (reading 'prototype')
at http://localhost:3000/_nuxt/node_modules/.cache/vite/client/deps/@metaplex-foundation_umi-bundle-defaults.js?v=eaf4a82e:2834:78

@viandwi24 I gave up on Solana and Metaplex... trash dx, really hated it. Never comming back.

@ASoldo I also think like that, previously I felt umi brought good changes, but it turns out there are still problems like this, I think it's still best to use metaples js.
my proboem when tryng to import @metaplex-foundation/umi-bundle-defaults
when import @metaplex-foundation/umi i thinks is fine

this how im try to solve this issue :
nuxt.config.ts
export default defineNuxtConfig({
  compatibilityDate: '2024-04-03',
  devtools: { enabled: true },
  modules: ["@nuxt/ui", "@hebilicious/vue-query-nuxt", "@pinia/nuxt"],
  ssr: false,
  vite: {
    esbuild: {
      target: "esnext",
    },
    build: {
      target: "esnext",
    },
    optimizeDeps: {
      include: [
<EMAIL_ADDRESS>        "@coral-xyz/anchor",
        "@metaplex-foundation/umi",
        "@metaplex-foundation/umi-bundle-defaults",
        "@metaplex-foundation/mpl-token-metadata",
        "@metaplex-foundation/digital-asset-standard-api",
        "@metaplex-foundation/mpl-bubblegum",
        "@metaplex-foundation/umi-rpc-web3js",
        "@metaplex-foundation/umi-program-repository",
        "buffer"
      ],
      esbuildOptions: {
        target: "esnext",
      },
    },
    define: {
      "process.env.BROWSER": true,
      "globalThis": "window",
      "global": "window",
    },
  },
}

and then to use umi in my nuxt im using this setup :
const umi = createUmi()
      .use(defaultProgramRepository())
      .use(web3JsRpc(this.options.rpc))
      .use(mplTokenMetadata())
      .use(mplBubblegum())
      .use(dasApi())

Umi bundle isn't the issue, the issue is on umi itself and that it tries to expose node-fetch even on browser.


test: change native-signals to alien-signals

change native-signals to alien-signals and update to version 0.2.0, the latest version handles more edge cases for a fairer comparison.

@johnsoncodehk thanks ... mind if I ask what happened to native-signals ? 🤔

Someones strongly object to the package name use of the word "native". 😅 So we use "alien" now because it's the opposite of "native".

have you considered passing it over?

If the polyfill wants to adopt alien-signals/native-signals I can submit a PR.


add bloomfilter index doc

add bloomfilter index doc
Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Code refactor (Modify the code structure, format the code, etc...)
[ ] Optimization. Including functional usability improvements and performance improvements.
[ ] Dependency. Such as changes related to third-party components.
[ ] Other.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[ ] I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If these changes need document changes, I have updated the document
[ ] Any dependent changes have been merged

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

How about move the doc to the place where bitmap index locate: administrator-guide/alter-table/alter-table-bitmap-index.md

No, I think that the index should be taken out of a directory separately, and the prefix index, Bitmap index and BloomFilter index should be put together


Applying the nodal fixation

Hi, I am trying to setup a simple linear elastic model for my further algorithm development. The following snippet does the read a bar model, and I am trying to fix the bottom side nodes, and pull the top size nodes in Z direction. The results looks quite wrong that the deformation shows a lot of randomness. I guess my way of applying nodal fixation could be wrong, or did I miss something important? The mesh "elastic_bar.med" is attached here.
Here is the code:

from skfem import *
from skfem.models.elasticity import *
import numpy as np

# read in an elastic bar model in med file format, meshio supports this file format
m = Mesh3D.load("elastic_bar.med")

basis = Basis(m, ElementVector(ElementHex1()))

# get coo_data object in order to access element-wise stiffness matrices
data = linear_elasticity(*lame_parameters(1e9, 0.3)).coo_data(basis)
# For future application that manipulates the element stiffness matrix
data = data.fromlocal(data.tolocal())
# assemble general stiffness matrix
K = data.tocsr()

# vertices index on top of elastic bar
group_btm = [17,51,85,119,153,187,221,255,34,68,102,136,170,204,238]
# vertices index on bottom of elastic bar
group_top = [1,35,69,103,137,171,205,239,18,52, 86,120,154,188,222]

u = basis.zeros()

# get the dofs for the top nodes
pulled = basis.get_dofs(group_top)
# dofs for the bottom nodes
fixed = basis.get_dofs(group_btm)

# pull the top nodes in Z direction by 0.001
u[pulled.nodal['u^3']] = 0.001

# solve the system,
# D for eliminated dofs, in our case, it meant fixed nodes, the bottom nodes group_btm
u = solve(*condense(K, x=u, D=fixed.flatten()))

# update mesh nodes with displacements.
sf = 1.0
m = m.translated(sf * u[basis.nodal_dofs])

# section calculating the system energy
elem_mats = data.tolocal()
obj = 0

for elem_i, elem_i_mat in enumerate(elem_mats):
     u_idx = basis.element_dofs[:,elem_i]
     u_i = u[u_idx]
     obj = obj + u_i.dot(elem_i_mat.dot(u_i))
# compare the element-wise energy calculation with the overall system calculation
# they should be identical
print(u.dot(K.dot(u)))
print(obj)

if __name__ == "__main__":
    from os.path import splitext
    from sys import argv

    #m.save(splitext(argv[0])[0] + '.med')
    m.save(splitext(argv[0])[0] + '.vtk')

This is the original shape, and bottom nodes shall be fixed, and top nodes were pulled.

The deformed states showed a random deformation.

elastic_bar.zip

The method basis.get_dofs requires a set of facets instead of a set of nodes because it is designed to work with general finite elements that have both nodal and facet DOFs.
Here you can use something like
basis.nodal_dofs[2, group_top].flatten()
to get the DOF indices of z-directional nodal displacement and
basis.nodal_dofs[:, group_top].flatten()
to get all DOF indices matching group_top.
I think *.med might not support facet sets but if you decide to use some more general format like *.msh then Mesh3D.load can read also the names of the facet sets.

The method basis.get_dofs requires a set of facets instead of a set of nodes because it is designed to work with general finite elements that have all nodal, facet and edge DOFs.
Here you can use something like
basis.nodal_dofs[2, group_top].flatten()
to get the DOF indices of z-directional nodal displacement and
basis.nodal_dofs[:, group_top].flatten()
to get all DOF indices matching group_top.
I think *.med might not support facet sets but if you decide to use some more general format like *.msh then Mesh3D.load can read also the names of the facet sets.

Thanks. I have changed my code as shown below. I found there is no deformation at all. The internal energy is 0.0, and result is exactly same as original state.

from skfem import *
from skfem.io import from_meshio
from skfem.models.elasticity import *
import numpy as np

import meshio

# read in an elastic bar model in med file format, meshio supports this file format
m = Mesh3D.load("elastic_bar.med")

#mio = meshio.read("elastic_bar.med")
#m = from_meshio(mio)

basis = Basis(m, ElementVector(ElementHex1()))

# get coo_data object in order to access element-wise stiffness matrices
data = linear_elasticity(*lame_parameters(1e9, 0.3)).coo_data(basis)
# For future application that manipulates the element stiffness matrix
data = data.fromlocal(data.tolocal())
# assemble general stiffness matrix
K = data.tocsr()

# vertices index on top of elastic bar
group_btm = np.array([17,51,85,119,153,187,221,255,34,68,102,136,170,204,238])-1
# vertices index on bottom of elastic bar
group_top = np.array([1,35,69,103,137,171,205,239,18,52, 86,120,154,188,222])-1

u = basis.zeros()

# fix the bottom nodes dofs
fixed = basis.dofs.nodal_dofs[:, group_btm]
# only get the dofs in Z direction
pulled = basis.dofs.nodal_dofs[2, group_top]
# top nodes move 0.01 in Z direction
u[pulled.flatten()] = 0.01

# solve the system,
# D for eliminated dofs, in our case, it meant fixed nodes, the bottom nodes group_btm
u = solve(*condense(K, x=u, D=fixed.flatten()))

# update mesh nodes with displacements.
sf = 1.0
m = m.translated(sf * u[basis.nodal_dofs])

# section calculating the system energy
elem_mats = data.tolocal()
obj = 0

for elem_i, elem_i_mat in enumerate(elem_mats):
     u_idx = basis.element_dofs[:,elem_i]
     u_i = u[u_idx]
     obj = obj + u_i.dot(elem_i_mat.dot(u_i))
# compare the element-wise energy calculation with the overall system calculation
# they should be identical
print(u.dot(K.dot(u)))
print(obj)

if __name__ == "__main__":
    from os.path import splitext
    from sys import argv

    #m.save(splitext(argv[0])[0] + '.med')
    m.save(splitext(argv[0])[0] + '.vtk')

In your code D=fixed.flatten() sets the Dirichlet nodes as only the fixed nodes so there is no load being applied. You must include all Dirichlet nodes, e.g., D=np.concatenate((fixed.flatten(), pulled.flatten())).

In your code D=fixed.flatten() sets the Dirichlet nodes as only the fixed nodes so there is no load being applied. You must include all Dirichlet nodes, e.g., D=np.concatenate((fixed.flatten(), pulled.flatten())).

Yes, that's the real root cause, I did not fully understand the D parameter. Now it works. Thank you very much! I will keep working on the algorithm.


Update callback-runner.js

Goal

Fix error causing crash. https://github.com/bugsnag/bugsnag-js/issues/1271
Design

Changeset

Testing

https://github.com/bugsnag/bugsnag-js/issues/1271

https://github.com/bugsnag/bugsnag-js/issues/1271

See #1271

See #1271


Debug configuration fails

When I compile debug configuration I get the following 846 errors like below (Release configuration works fine):
Severity	Code	Description	Project	File	Line	Suppression State Error	LNK2038	mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(ShaderLang.obj)	1	 Error	LNK2038	mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(ShaderLang.obj)	1	 Error	LNK2038	mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(PoolAlloc.obj)	1	 Error	LNK2038	mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(PoolAlloc.obj)	1	 Error	LNK2038	mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(Versions.obj)	1	 Error	LNK2038	mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(Versions.obj)	1	 Error	LNK2038	mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(Intermediate.obj)	1	 Error	LNK2038	mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(Intermediate.obj)	1	 Error	LNK2038	mismatch detected for '_ITERATOR_DEBUG_LEVEL': value '0' doesn't match value '2' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(IntermTraverse.obj)	1	 Error	LNK2038	mismatch detected for 'RuntimeLibrary': value 'MD_DynamicRelease' doesn't match value 'MDd_DynamicDebug' in vsgconv.obj	vsgconv	C:\projects\VulkanPBRT\build\external\vsgXchange\applications\vsgconv\MachineIndependent.lib(IntermTraverse.obj)	1

This looks like the vsgconv is not being compiled in debug mode even though the rest of the project is.
As the vsgconv is never used you can quickly fix this error by uncommenting https://github.com/Lachei/VulkanPBRT/blob/0ab8dce075ddd37098ee2debc0d4e3f4d737b135/external/vsgXchange/CMakeLists.txt#L56.
I will look a bit more into detail later as this error is not critical and seems to be not general...


Move material into a separate entity that can be attached to meshes.

Phong Material

https://github.com/Code-Gains/DX11-Engine/issues/11 (ECS)


Update Premier / Unified

Hi folks,
The TAM nomenclature was dropped this FY.  They are now CSAMs.  Can we add that in  please so we are using the current terminology?
Cheers,
Rhoderick
Microsoft Premier\Unified support training available
If you're interested in learning more about Azure AD Password Protection and deploying it in your environment, you can take advantage of a Microsoft proactive service available to those customers with a Premier or Unified support contract. The service is called Azure Active Directory: Password Protection. Contact your Technical Account Manager for more information.

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

ID: 0e6e009c-2e82-98ae-6a18-ce0e8991f3cc
Version Independent ID: 8e36df09-f7f1-dcbd-dc3d-93cbeed1b040
Content: On-premises Azure AD Password Protection FAQ
Content Source: articles/active-directory/authentication/howto-password-ban-bad-on-premises-faq.yml
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@r-milne
Thanks for your feedback! We will investigate and update as appropriate.

@r-milne
Thank you for pointing this out! I've created a PR to update the documentation and it's currently waiting for the author to review and sign off.
I will now close out this issue. Please allow some time for the author to review and the changes to reflect.
Thank you for your time and patience!


ADBDEV-5556 [PORT FROM 6X] Close COPY TO/FROM PROGRAM descriptors in case of error

Close COPY TO/FROM PROGRAM descriptors in case of error
This is a port of commit 75981ebc9c368ac26a231e376ab2edbb1e8928b6.
In case of error during COPY TO/FROM PROGRAM opened program pipe
descriptors weren't closed. That made the program hang until the end of session.
That behaviour occured due to absence of close_program_pipes() function call in
error cases. Originally, this call was present in catch block of DoCopy()
function (110b825), however it was removed in 25a9039.
This patch fixed the erroneous behaviour by adding a callback for closing
handles on errors, which is called before deleting the memory context of the
copy state.
Co-authored-by: Georgy Shelkovy<EMAIL_ADDRESS>

Why not simple cherry-pick with needed changes?

Why not simple cherry-pick with needed changes?

It was simplier to make changes by hand.

Why not simple cherry-pick with needed changes?

It was simplier to make changes by hand. But i'll try now to make cherry-pick version

I don't see any difference, but in case of cherry-pick the authorship is saved

please add this to commit description

Added, but i expect and it would be preferable that commit message will be taken from PR description.

commit message will be taken from PR description

No! in case of cherry-pick it will lead to loss authorship, so such patch should be merged by commit(s)


Copper rod recipe conflicts with lightning rod recipe.

Describe the bug
As said in the title, the recipe for the copper rod is the same as for the lightning rod, making lightning rods uncraftable.
Which side have you encountered the bug on?
Both
Steps to reproduce
Self-explanatory.
Logs
No response
Additional context
No response

This should be fixed in Arch-Ex v1.0.0+1.18.2 and v2.0.0+1.19.


Present the update mechanism proposal to other IOHK stakeholders

To get early feedback on the research results, and increase the chances of adoption of the update mechanism in Cardano.
This presentation will be basically about the FC 2019 paper.

This is part of the roadmap and not a technical issue.


Fix timeout parameter on messages

Fixes the issue discussed here.
With tests (async tests do add a second to the overall duration of the tests run, so we can consider lower timeout values if tests speed something important to you guys).

@amplicity, @ihorrusinko And the tests passed too 🎉

hey @v1adko good job!
i don't fully agree with you, your PR will destroy current tests for most users who use timeout feature.
i would like to suggest you to add compatibility for tiemout parameter,  implement timeoutAfter and timeoutBefore as part of message object.
what do you think?

Hm... it would make more sense then to add those kind of tests here too, I think. Otherwise there's no knowing if it breaks anything (apart from you telling me it will).
As I understand, what I needed in my case was timeoutAfter, does it mean then that timeout the way it is right now is "before"? What's the current use case of the parameter?

Hm... ok, it kinda makes sense, maybe I've misunderstood the docs, it says:

timeout  - set timeout for message in milliseconds (integer)

It wasn't clear for me that it's the timeout before the message is sent. Now that I've looked up the definition of the word timeout it does make more sense. 😬
I write most bot tests atomically (1 message - 1 reply), and missed out on that use case, now I get that timeout is mostly used for the sequence of messages, basically saying "wait up a little" before sending it... (And please correct me if I'm wrong).
So as for this PR... what would you propose for the API (parameter name on the message).
wait, waitAfter? Should we make up aliases for the current timeout to mach the new ones (like waitBefore)?

you are absolutely right.
let's make alias for timeout - waitBefore.
i'm agree with waitAfter.

@ihorrusinko Done. Please note that I gave waitBefore alias more priority than the older timeout because the naming seems more explicit.

@v1adko agree. thanks


Latest Post Summary doesn't work if "API calls" are disabled on a Jetpack blog

References: https://github.com/wordpress-mobile/WordPress-Android/issues/3187

Closing issue and migrating to new repo.


CASMINST-6099: VCS backup/restore: Linting and minor improvements

Backport of https://github.com/Cray-HPE/docs-csm/pull/3481

/backport release/1.0


Add Superset password hint to documentation

Type of change :

[x] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have tagged my reviewers below.

Reviewers
@harshach

Thanks @tomtor


checking answers

there needs to be a feedback presented to the user telling them if they got the answer right or wrong
pull req is here

its merged by imtiyaz. its on the main branch now its closing


fix Fix the error of Cloud forwarding SQL not finding the cluster #41819

cherry pick from #41819

run buildall


Use electron-rebuild in rebuild code

As discussed in https://github.com/atom-ide-community/atom/issues/111 and https://github.com/atom/apm/pull/889#issuecomment-671160524 the apm rebuild code is kind of wonky, and I can't trust it.
We should use electron-rebuild which is the official way to build Node modules against a specific Electron version.
Here is the documentation about Node modules in Electron.
electronjs.org/docs/tutorial/using-native-node-modules

No comment on this approach.
For the record, this is what apm is already doing: https://www.electronjs.org/docs/tutorial/using-native-node-modules#using-npm


Let FileSystem extensions set filetype icons in filesystem browser

Provides the feature I asked about in "Can a FileSystem extension set icons for files in the FileSystem viewer/browser?" https://github.com/NationalSecurityAgency/ghidra/discussions/6953
This solution involves the fewest modifications to the existing code.
In a FileSystem's getFileAttributes() method you just add a typeExt attribute which is just a file extension including the dot, as in .txt and in this way leverages the existing system which uses the file's extension to decide which icon to use. FileSystems which know the types of their files and which do not use the file extension convention can thus set the types of files:
@Override
public FileAttributes getFileAttributes(GFile file, TaskMonitor monitor) {
        Metadata metadata = fsIndex.getMetadata(file);
        FileAttributes result = new FileAttributes();
        if (metadata != null) {
                result.add(FileAttributeType.NAME_ATTR, metadata.name);
                result.add(FileAttributeType.SIZE_ATTR, metadata.size);
                if (metadata.filetypeCode == 4) {
                        result.add("typeExt", ".txt");
                }
        }
        return result;
}

The mapping of file extensions to icons is at Ghidra/Features/Base/data/base.file.extensions.icons.theme.properties and the icons themselves are in Ghidra/Features/Base/bin/main/images
(I would actually say a bunch of useful ones are still missing, such as .exe, .dll, .o, etc.)

I believe I've addressed all of your concerns. I'm not a Java guy so I wasn't sure if I should also add a getter for filenameExtOverride in FSBFileNode or if it's fine as-is being protected.
I'm logging an error with Msg.error if the filename extension override doesn't start with .. We could insert one or not require the FileSystem to include one, but lightweight logic seems better to me.
(I'm still learning Git & Github so let me know if I'm doing anything wrong please.)

re: getter for the filenameExtOverride value.  Yeah, there should be one.
The final step for this PR would be to squash your commits into 1 and then force-push overwrite your PR branch with that new commit, and then we'll merge that commit.

I struggle a lot with Git. I followed some guides to learn how to squash my commits but from looking at the above it looks wrong to me. Did I accidentally squash in the commit prior to my PR? Or is this just how GitHub makes it look?

I struggle a lot with Git.

I think that is many of us.  The concepts and interfaces are not as intuitive as I would like.   Not sure I could design it any better.

Did I accidentally squash in the commit prior to my PR? Or is this just how GitHub makes it look?

It does look suspicious because that previous commit from ghizard has your name as the committer, but I don't think any source code was comingled.  However, it will prevent a normal PR merge from happening from our side.
Its possible to fix your branch, but for something so small it may be easier for you to just create a new PR branch, manually migrate your code changes from the broken branch into the new one and then submit it again.

2nd attempt: #7070

Fixed by 860915d129eaae6460ee5bcf217f92ee0f7aa70d


Use item IDs for OneDrive file names in kopia

OneDrive files currently use the file name of the file in OneDrive as the file name in kopia. However, this is not compatible with using delta token information to update files during incremental backups. Delta tokens only give the ID of the file and if the file was deleted there's no way to retrieve the name of the file. Unless some other way of resolving IDs -> file names is created, it may be best to store files by ID in kopia

#2496 needs updated to use (reporef, filename) when generating shortref in backup details


Remove simplejson dependency.

Fix #6970.

@rht thanks for working on this!  It looks good, except for a test coverage gap.  I bet we can just steal the unit tests for this module from simplejson along with the function.
Also, can you move JsonEncoderForHTML in zerver/lib/json_extensions.py, rather than in the view code where it's used?  that's more where it belongs in the codebase.

Oh, and of course we should remove simplejson from the requirements/ directory.

@timabbott added the test but wasn't able to figure the cause of the Travis err.
I'm not sure why simplejson is in the lockfiles but not in the input files. I assume someone did remove from the input files but forgot to update the lockfiles. Currently running the ./tools/update-locked-requirements.

+./tools/run-mypy --linecoverage-report
Oct 18 01:41:13 zerver/views/home.py:96: error: Function is missing a type annotation
Oct 18 01:41:13 zerver/views/home.py:102: error: Function is missing a type annotation

I missed the lines somehow. Fixing.

Updated, but definitely needs a review. I'm not 100% sure of this implementation.

There might be a unicode stuff bug lurking, this is why I am unsure.

This looks good to me, assuming that the unicode stuff is correct.  @gnprice can you give this a good test + review?  Basically this mechanism is how we send most data from the backend to the webapp (generates the page_params structure).  If you're not sure how to test, I would recommend making changing a user to have a lot of unicode in their name; that should exercise it well.

I did some manual testing, and test-deployed this on chat.zulip.org, and it seems to work.  Can you fix the docs/THIRDPARTY thing I mentioned?

OK

Added.

Cool.  Looking at this, it became clear that we should put this code in its own file under zerver/lib, so I did that and merged this as 2606a109b5bbc5bdc5e0f660fd117bada3d30891.  Thanks @rht!


not working in vscode

I have added to settings.json(user), and restarted vscode
    "github.copilot.advanced": {
        "debug.testOverrideProxyUrl": "http://localhost:5001",
        "debug.overrideProxyUrl": "http://localhost:5001"
    }

but the plugin still reports needs an official subscription

same issues


added a complete basic system diagram to phase-1 log-clean-analyze

first PR'ed and merged from my dev to my master, then issued a PR from my master to master; I hope that's the way to do exactly the same PR

Perfect, thanks.


Ensure we avoid reaching max connections towards postgresql

Introduction
After doing some load tests, we seem to reach the max amount of connections.
https://digdir.slack.com/archives/C07R312076E/p1731587548451379
An exception has been raised that is likely due to a transient failure. 53300: remaining connection slots are reserved for azure replication users
We need a solution to ensure that we avoid hitting this limit.
Description
A possible solution to this problem is using a connection pooler such as pgBouncer, pgCat or Supavisor. A comparison can be found here. https://tembo.io/blog/postgres-connection-poolers
It also seem like the most performant is to utilize a combination of connection pooling on the application layer and using a connection pooler proxy. Ref: https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-pgbouncer#using-pgbouncer-with-other-connection-pools
A solution here could be to add a connection pooler proxy as a separate deployment per type of application. That way we reduce the bottleneck and ensure that we can scale the services horizontally without hitting the limit.
Implementation
TODO: Decide on architecture and the connection pooler solution.
What should be the connection pool limit be for the applications?
Do each container app job need a separate connection pool proxy, or just one for jobs?
Should it be possible to scale the connection pooler horizontally?
How to we monitor and act on high connection count?
### Tasks
- [ ] Implementation tasks are added here
- [ ] Prepare documentation (if relevant - either update working document, or add a new file in `docs`)
- [ ] Add e2e-test (if relevant)

### Threat modelling
- [ ] Does this change introduce any potential security issues?

Acceptance criteria
GIVEN ...
WHEN ....
THEN ...
GIVEN ...
WHEN ....
THEN ...

It appears it would be fairly easy to transition from one to the other, so I would suggest we start with pgbouncer, as this is fully supported and managed in Azure and will most likely deliver a sufficient level of scaling for now. Running any of the other non-managed options may delivery additional scaling potential, but at the cost of complexity and - according to the tests linked - higher latency. So opting for the low-complexity, low latency solution even though it has limitations in scale (which we as of now don't know if we need) seems like the best course of action.

Initially we just up max_connections to the default Azure suggests.


Cake alias doesn't work

When adding the the addin:
#addin Cake.GitVersioning

Then calling GetVersioningGetVersion() in your cake build script. When attempting to run the script it fails with:
Error: Error(s) occurred when compiling build script:
C:/git/AppCore/build.cake(24,1): error CS0103: The name 'GetVersioningGetVersion' does not exist in the current context

I see the addin is added in the tools folder. However, it appears like it isn't referenced for some reason.
I am trying this with Cake version 0.30.0
Cake also complains about Cake.GitVersioning is referencing an old version of cake:
The assembly 'Cake.GitVersioning, Version=<IP_ADDRESS>04, Culture=neutral, PublicKeyToken=null'
is referencing an older version of Cake.Core (0.26.0).
For best compatibility it should target Cake.Core version 0.28.0.

@clcrutch Can you help with this?

@Cheesebaron It turns out their was a typo in the documentation.  The proper alias is GitVersioningGetVersion instead of GetVersioningGetVersion.  I've submitted a PR to address the typo.
@AArnott As far as the warning about the newer version of Cake, I'll submit an additional PR to address the Cake version mismatch.


Unable to find section, when title has tag inside

Issue tracker is ONLY used for reporting bugs. New feature ideas should be discussed in the ideas section. Please use the Q&A section for supporting issues. Please use the search function.
If you encountered the issue after you installed, updated, or reloaded the tasks plugin, please try restarting obsidian before reporting the bug.
If you want to report a bug, please follow the guide lines below to help me resolve it.
Expected Behavior

find right section
Current Behavior

Steps to Reproduce

create the task under header which has tag inside
Context (Environment)

Obsidian version: v0.14.6
Tasks version: v1.5.1
[x] I have tried it with all other plugins disabled and the error still occurs

Possible Solution

may be obsidian update the recognition

or use the standard link

Hey @cxdongjack, thank you for the well written report!
I can confirm the issue. I checked how Obsidian does this, and they simply remove all hash symbols when linking to sections with hash symbols.
Example in Obsidian:

Note called Chores has a header Section with #tag and #tags
The link to that header is actually href="Chores#Section with tag and tags"

This means that if you have two headers: Head with tag and Head with #tag, both produce the same link that always points to the first matching header.
In order to fix this: remove all # symbols from the header for the href and data-href attributes of the link. (remember to keep the # that separates the note name from the header).

It works，cool!

It works，cool!

Did you test it locally? Would you be willing to open a PR for the fix?

Just test with inline html, it works.
Sorry，I can't open a PR.
I'm not code for a long time, nearly forget how to code.

It works，cool!

Did you test it locally? Would you be willing to open a PR for the fix?

Just test with inline html, it works.
Sorry，I can't open a PR.
I'm not code for a long time, nearly forget how to code.

OK, no problem. Thank you for reporting the issue and testing the potential fix.


libheif: 1.3.2 -> 1.4.0

@GrahamcOfBorg build libheif

This update was already merged into staging since it causes lots of rebuilds.
BTW: The sha256 was incorrect (you can use nix-prefetch-url -A libheif.src the next time to get the correct one).


"Duplicate document name" wrong error message

Create a new doc via publisher
The given name is not added, but it displays as "Duplicate document name"

added tag for the tittle

duplicate issue - https://github.com/wso2/product-apim/issues/5688
It's fixed now.


"is confidential" causes Grace.exe to become unresponsive

The "is confidential" keyword causes Grace.exe to become unresponsive until the process is killed instead of creating a warning for the user.

Hm, since you mention Grace.exe, are you sure that's on top of Moth?
Could it be that you're using Kernan?


Fixed ReadResource to handle absolute uris

readFile function in readResources.js handled absolute paths, but not absolute URIs, even though it was process URIs. It would see the absolute URI as a relative path and append it to the resourceDirectory which is obviously wrong. We end up with something like c:\path\to\resources\file:\\\c:\full\path\to\the\image.png
In addition we

Actually look at and test the secure flag.
Add fileURLToPath and pathToFileURL functions so we still work with older versions of node

The new process goes like this

resourceDirectory if specified is made absolute right off the bat.
In readFile we check if resourceDirectory is defined.

If it is, we convert it to a URL and resolve the resource uri with it
If it is not, we try to make the URL from just the resource uri. This fails if its not an absolute URL or absolute file path. We catch this and make it a friendly error.
Convert the URL to an absolute path, since it is now resolved correctly.

If resourceDirectory was defined we now check if the file is outside this directory if secure is true.
Then we read the file.

@lilleyse Do we still need secure. @mramato said we may be able to remove it.

Also, Node 8 has a URL class, so I'm not sure whats going on with the errors.

@lilleyse Do we still need secure. @mramato said we may be able to remove it.

I don't think it was ever even hooked up properly. If we don't need it it's fine by me to remove. There was  an old branch to fix it that never went anywhere which we can delete now: https://github.com/AnalyticalGraphicsInc/gltf-pipeline/commits/fixSecureResources.

Also, Node 8 has a URL class, so I'm not sure whats going on with the errors.

FileUrl.js needs to include it too like const { domainToUnicode, URL } = require('url');

@lilleyse I think this is ready.

Thanks @tfili


Fix style of hide-readme-header on GitHub Enterprise

relates to https://github.com/sindresorhus/refined-github/pull/4046

Test URLs
Screenshot

(from Github Enterprise v2.21.14)

ARIGATOUGOZAIMASU


Add arm source file into aws-checksums

According to https://github.com/tensorflow/tensorflow/issues/40463#issuecomment-647640030 , seem the aws libs need to add the arm related libs during build tensorflow package.

recheck

@bzhaoopenstack Thank you for your contribution. Can you please sign CLA? Thanks!

@gbaned Hi, I had signed the Individual CLA. But I'm not sure whether the cla:no label can not be removed.

@bzhaoopenstack Can you use please make sure to use same GitHub username and email-id associated with it.


Provide Chinese as UI language (i18n/internationalization)

Before the translation properties file can be merged, #780 "Support non latin alphabets in i18n" needs to be merged.
The current status of the translation can be found on POEditor (currently ~ 11 % for Chinese):
https://poeditor.com/projects/po_edit?id_language=31&id=126971

Reopening because the translation isn't complete yet :smile: .

If we wait until it is completed 100%, we will never close this because new messages are added every now and then and I don't expect (or wait) for all languages to catch up for each release.
Translation is now at 76%, this good enough to consider it "implemented" :)


Polish TreeItem description === true

The TreeItem API allows the description to be set to true, which indicates that the relative dirname of the resource should be used as the description. There are some problems with this:

A slash is prepended to the relative path
We don't include the root when in multiroot

Example from GHPRI where there are two PRs, each from a different workspace root:

Moved back to microsoft/vscode-pull-request-github since VS Code tree views actually do the right thing here already. The issue is that this view shows resources with the scheme filechange, which is an extension specific scheme. This scheme enables our file decorations, so we can't just switch over to the file scheme.

To verify:

Install the pre-release version of this extension.
Open a workspace with at least 2 folders, each with a GitHub repository.
Checkout a pull request in each of your open folders
In the "Changes in PR" view, verify that the description of each file doesn't start with a slash and that root folder is included in the description.


[HW]

Name:
Email<EMAIL_ADDRESS>Linkedin Profile: <https://www.linkedin.com/in/prathmesh-wavhal-39586319b/

Attach the homework step I screenshots below:

Attach the homework step II screenshots below:

![TIKTOK CLONE SS4](https://user-images.githubusercontent.com/23097791/119798339-adae9a00-bef8-11eb-950d-0b6f05460b77.png)
![TIKTOK CLONE SS](https://user-images.githubusercontent.com/23097791/119798340-aedfc700-bef8-11eb-8c71-32ea2b4ff9e0.png)
![TIKTOK CLONE SS1](https://user-images.githubusercontent.com/23097791/119798342-af785d80-bef8-11eb-8290-b98c467c499e.png)
![TIKTOK CLONE SS2](https://user-images.githubusercontent.com/23097791/119798343-af785d80-bef8-11eb-8dd0-176b3bd1738e.png)
![TIKTOK CLONE SS3](https://user-images.githubusercontent.com/23097791/119798345-b010f400-bef8-11eb-9e24-a8d806807847.png)

Not sure why name wouldn't show up, anyway it's Prathmesh Wavhal! Thank you

Well done, Prathmesh! And thank you for the kind feedback!

Thanks for posting your name as well. Good job and here's your badge -> https://api.badgr.io/public/assertions/HSXn5D4MQwiEsXHB1IWnmQ?identity__email=prathmeshwavhal%40gmail.com


Please update Box SSO setup instruction to box.net identifier only

This is a follow up to #16398 and internal Box Microsoft ticket
[REG:118111919360462]<PHONE_NUMBER>60462
Box App in Azure Single-Sign On seems to have two different Identifiers
Please change the pattern hint to reflect box.net only.
The current dual pattern is confusing for customer leading to a lot of tickets. Actually the URL  https://sso.services.box.net/sp/ACS.saml2 is only valid as an identifier if explicitly set as virtual server id on the box side, which is only used in rare cases. By default this is not the case and thus box.net is the default.
Just having box.net in the pattern will not mislead customers to go for the URL (which will fail if not set on the box side), decreasing the overall amount of tickets on both sides.

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

ID: 9a6d67a1-eade-6bdd-ab13-744a7c351c53
Version Independent ID: 9c1bce95-5f19-6175-7df6-a1e26368704f
Content: Tutorial: Azure Active Directory integration with Box
Content Source: articles/active-directory/saas-apps/box-tutorial.md
Service: active-directory
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@jmfrank63
Thanks for your feedback! We will investigate and update as appropriate.

@jmfrank63 We have updated the article based on your suggestion. Please review.

#please-close


Add EnzymeCore weakdep and an extension with a custom rule for the Levin transformation

This PR, which currently does not work, adds a custom EnzymeCore rule (see #96). I currently get the error that forward is not defined, which it is as EnzymeCore.EnzymeRules.forward. So something is happening that I'm not understanding.
@oscardssmith, would you be willing to take a look at this?
I'm not sure if this is necessary, but for what it is worth, I am using EnzymeCore#main. I don't think this is an Enzyme issue because when you run the code in #96 as a standalone file everything works. So I think something about how weakdeps work is eluding me right now.

Hah! That is hilarious. I should have caught that, sorry for wasting your time here. I'll make that name change, thanks!

no problem. It's a very silly error, but I can totally see myself making it and not noticing.

@heltonmc---this is all working now, and all tests pass. But before I write a real test file and ask for a merge, I just wanted to check in with you because it does change the Levin transformation code and I haven't touched base with you in a little while about how many other functions you've been developing to also use it.
Just as a reminder of the "point", your improved version here is re-organized to make sure that it takes as inputs the sequence values and weights so that the functions that produce that ntuple will not risk a divide-by-zero problem, and then we'll use the custom rule here to check for exact convergence before passing those tuples into the Levin transform.
Also, as far as tests go---I know we've discussed this in bits and pieces somewhere else, but considering that we don't really have the same level of quality reference value for the derivatives, maybe I'll just use a bigfloat+high-order central_fdm and check for something like isapprox(ref, candidate, atol=1e-15)?  I'm a bit nervous to ask for rtols of 1e-15 using a finite difference rule even with higher precision floats and a very high-order adaptive finite difference rule. Maybe @oscardssmith has some opinions on this as well?
If the answer isn't obvious to you guys, maybe for now I'll just put in a handful of the super expensive derivatives and check the atol for now while we discuss? Practically speaking, if it gives the right answer for any half-integer order and any full-integer order, I think we can be reasonably confident that the autodiff transformation is happening correctly, and maybe more subtle issues about accuracy to the last ulp should be a follow-up discussion.

the general rule for finite differencing is that you lose about half of the bits. As long as you have more 100 or so bits, rtol=1e-15 should be fine (you may need extra bits for other reasons).

Oh, great. That's a very helpful rule of thumb. I'll crank up to 150 bits to be safe and go for the real rtol metric then. Thanks!

I believe the problem is https://github.com/JuliaDiff/FiniteDifferences.jl#dealing-with-numerical-noise. Since the ARB routines aren't as accurate to as many digits as they are supposed to be accurate to, FiniteDiffereences is picking too small an epsilon.

This looks ready to merge to me.
I checked out locally and ran a few benchmarks it is pretty much exactly twice as slow to generate both the scalar and derivative which makes sense to me as we have to do them separate. This seems very optimal to me. The one thing is that it requires a large number of sequence terms Val(30) which is rather significant when I only found that the scalar value needed about 16 terms. That is something we can look more into next though when we piece everything together.
This right now is working great.

This last commit brings in the new near-integer power series stuff. I haven't written tests yet so certainly not ready to merge, and your new form of the power series in general seems to be causing some of the Float32 issues to fail. But it is so fast and I'm sure there is just a little thing to fix somewhere, so I'll look at that and at setting up the AD tests tomorrow.

Float32 errors are annoying. I went through and checked the versions and this new version is actually slightly more accurate. It seems like a cutoff issue.

Probably some weird cutoff issue that I'll track down... I mean it's a weird section because we are promoting the Float32 values to Float64 but using a different cutoff to avoid the intermediate routine. But now that Levin is so fast.. it makes it almost not worthwhile to do this.

Okay, so this newest commit gives code that has decent timings/optimizations (modulo the muladd conversions), and it passes the autodiff tests for order and arg....albeit with reduced precision for abs(v)<1e-8. But I think those derivatives are pretty hard and I'm almost suspicious of the Arb version too. So personally, I would still vote to merge for the moment and revisit.
The much bigger issues are:

The generic power series code, even with the sinpi fix, is still totally broken with Enzyme (but works great with ForwardDiff if I remove some type annotations in Bessels.gamma).
The new power series code has some Float32 failures.

I know @heltonmc would like to get this merged, so maybe it would be best to just merge and I will track down the power series issue in another PR, which can be smaller? The Float32 issues are less obvious. If you'd like, I can just go back to the old power series code that passes the tests and that can also be a separate PR.
Let me know!

I know @heltonmc would like to get this merged, so maybe it would be best to just merge and I will track down the power series issue in another PR, which can be smaller?

Ya I think as long as the power series is accurate for scalar evaluation then I'm ok merging because I need to change the routine in general. The derivative information if the scalar is accurate should be an issue in the AD system which we can track down in a different PR.
The Float32 issue though needs to be tracked down so will look at that now.

Actually ya just change it back to the prior power series and I will track it down when I edit the whole routine. I don't want to fix it here and then have to change the routine again :)


SSR doesn't use joinBase

SSR doesn’t seem to prepend dist/ using joinBase, so <img/> URLs come down 404ing until eventual client app reattachment which does finally update the tag srcs to properly prepend dist/.
Initial page as fetched from SSR:

Post client app reattachment (some milliseconds later):

Notice the unsightly 404 in the console.

Note that in the yellow Stache Variables part of the screenshots, this.env.NODE_ENV changes from production in SSR to development after reattachment. Could this be a hint as to what the issue may be? Anything I might be doing wrong, or a known bug? Any suggestions of what to try?
This is the last major bug in the starter app I'm trying to create (at least, AFAIK at the moment). I would appreciate any help getting this resolved, because then my little starter app will be nearing perfection.
I'd also take links of where to look at in the code if it's something I might be able to help myself debug.

You might be missing this configuration: https://github.com/donejs/place-my-order/blob/532aa2ef896065badf8382f6da26f54fbcea9b36/package.json#L39-L41

@matthewp Thanks for pointing me back in that direction. I found that example:
    "envs": {
      "server-production": {
        "renderingBaseURL": "https://place-my-order.firebaseapp.com/"
      }
    },

To be rather confusing at first, because my understanding is that setting renderingBaseURL to that https://place-my-order.firebaseapp.com/ doesn't really change anything; it's redundant because the app is already being served from that URL. So that example is a bit confusing for that reason.
Once I read up on server-production a bit more, and understood that means on the server (SSR) in production (as opposed to local development), I realized I have the tools to specifically target the URL used on the server to change it to exactly what it should be:
    "envs": {
      "server-production": {
        "renderingBaseURL": "https://bitcentivez.herokuapp.com/dist"
      }
    },

I still don't fully understand why window-production would prepend dist/, but server-production would not. It seems like window-production should have required the same kind of fix, or both window- and server-production should have worked out of the box. In the "following factors" section at the end of the joinBase docs:
https://canjs.com/doc/can-stache.helpers.joinBase.html
I don't necessarily see anything that would immediately suggest an answer as to why there would need to be a special separate config for how joinBase behaves on the server in SSR.
Anyways, I do think this is a nice feature, being able to specifically target the configuration not only using NODE_ENV, but also depending on window or server as well. At the very least it allows us to correct such kinds of unexpected behavior. I just wonder if this isn't a bug?

renderingBaseURL is sort of a weird feature. It only exists because on the server you don't want to point to where the files are on the server, but rather where the browser can download them from.  There's nothing else like this in steal config so it's not a great fit. We should maybe think of a better way to do this in the future.

@matthewp Thanks, that makes sense.
Also, are there are no docs for renderingBaseUrl on https://stealjs.com? All I could find were the docs for https://stealjs.com/docs/config.baseURL.html which isn't the same thing.
Anyways, I'll close this now as it's solved. Thanks again.


lightbox_canvas: Remove movementX, movementY polyfill.

This isn’t necessary in modern browsers and throws errors with "use strict".
Testing Plan: Dev server.

Yay for fixing a bug and deleting code :)


Question about New Posts

Hi,
I'm super new to hosting via Github and web technologies in general. Sorry if this is a stupid question but I'm trying to create new posts by creating a markdown in the directory posts (this right now is basically a copy of one of the sample posts with a different name). However, it doesn't show up when I deploy the website. I notice that the corresponding html for the post isn't generated under the _site directory.
What am I doing wrong? Do I have to register the name of this markdown in some other file?

Hi, same issue here. @karanchawla how you solve this?


Wifi Dongle: SoyosourceDisplay CRC Check failed!

Every few random minutes an following error message appeared in the log:  SoyosourceDisplay CRC Check failed! At the same time I can see error in HA Logbook (see screenshot).
Any advice what does it mean?
logs_soyo-wifi-dongle_upload.txt

Could you increase the log level to DEBUG and enable the debug output of the uart component?
uart:
  - id: uart0
    baud_rate: 9600
    tx_pin: ${tx_pin}
    rx_pin: ${rx_pin}
    debug:

I would like to see the raw frames at the logs.

[18:13:37][I][soyosource_display:350]:   Maximum PV voltage: 45 V
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! B6 != BE
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 43 != AE
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 10 != 37
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! A7 != 37
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! DF != 37
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 9B != BE
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 2B != 36
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 23 != 26
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! C8 != BB
[18:13:41][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 48 != BB
[18:13:41][W][soyosource_display:155]: Unhandled response received: A6.FE.37.B<IP_ADDRESS>.37.36.B<IP_ADDRESS>.B3 (14)
[18:13:42][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 7F != 37
[18:13:42][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! F8 != B3
[18:13:42][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 90 != 37
[18:13:42][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! BB != FF
[18:13:42][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! EF != 37
[18:13:42][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 88 != FE
[18:13:42][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 7B != 26
[18:13:43][E][soyosource_display:137]: No data from the Soyosource inverter received yet. This should never happen if the dongle is plugged into the inverter
[18:13:47][I][soyosource_display:163]: Status frame received
[18:13:47][I][soyosource_display:282]: Settings:

I don't see any debug messages. :-) Did you update your ESP?

My mistake. Wrong setup of Logger component. Better now?
18:34:16
logs_soyo-wifi-dongle_upload-3.txt

[18:34:16][D][uart_debug:114]: <<< 5A:01:93:40:D2:18:17:16:00:DF:64:46:37:06:1A:2D:07
[18:34:17][D][uart_debug:114]: >>> 55:01:00:00:00:00:00:00:00:00:00:FE
[18:34:18][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 7B != 26
[18:34:19][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 10 != 37
[18:34:19][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 03 != 36
[18:34:19][D][uart_debug:114]: <<< 60:BF:B3:B7:36:26:26:F3:37:36:26:26:77:77:7E:37:B6:26:26:B3:37:36:66:33:A6:BB:26:37:37:36:B7:B6:26:26:B3:37:36:26:26:37:37:36:37:36:26:26:37:37:36:B7:B6:26:27:B3:37:36:26:26:37:37:36:37:33:36:37:36:26:26:B3:37:36:26:26:37:37:36:37:36:26:26:B3:37:36:E7:7B:A7:FB:26:7F:37:36:37:36:26:26:B3:37:36:A6:26:37:B6:36:37:B7:A6:26:37:37:36:37:36:26:26:B3:37:36:26:26:37:37:36:A6:33:36:37:36:26:26:B3:37:36:26:26:37:37:36:37:B6:26:26:37:37:36:B7:B6:26:26:B3:37
[18:34:19][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! C8 != BB
[18:34:19][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 3F != BF
[18:34:20][D][uart_debug:114]: <<< 6E:66:37:36:66:B3:26:BB:A6:B7:BF:B6:37:36:26:AE:BB:37:36:26:66:26:BB:26:37:37:36:37:36:26:26:B3:37:36:26:26:37:37:36:37:FE:26:26:37:37:B6:37:36:26:AE:B3:B7:36:26:26:37:37:36:37:B6:66:26:37:37:36:B7:36:26:26:B3:37:36:26:A6:B7:B7:36:37:36:A6:6E:66:37:36:66:B3:26:BB:26:B7:B7:36:37:36:26:A6:B3:B7:36:26:76:26:BB:A6:B7:BF:B6:B7:B6:26:A6:B3:B7:36:A6:26:B7:37:36:37:EE:AE:A6:B7:BF:7E:66:37:36:66:33:26:BB:26:37:37:B6:37:36:A6:26:B3:37:36:26:66:26:BB:26:37
[18:34:20][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 24 != 7F
[18:34:20][D][uart_debug:114]: <<< FF:66:66:7F:77:7E:B7:B6:26:27:B3:37:36:26:26:37:37:36:37:B6:26:26:37:37:B6:37:36:A6:26:B3:37:36:26:26:37:37:36:37:B6:26:66:37:77:7E:B7:B6:26:27:B3:37:B6:26:26:37:37:36:B7:FF:26:26:37:37:36:B7:B6:26:26:F3:37:36:26:26:37:37:36:37:36:66:26:37:37:36:37:B6:26:26:B3:37:36:26:26:37:37:36:B7:36:26:F6:66:37:36:66:33:A6:BB:26:37:37:36:37:36:26:26:B3:37:B6:26:76:A7:BB:26:7F:37:36:37:B6:26:26:F3:37:36:26:26:37:37:36:37:FF:26:26:37:37:36:FF:FF:66:27:B3:37:36
[18:34:20][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 2B != AE
[18:34:21][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! FB != AE
[18:34:21][D][uart_debug:114]: <<< 26:37:37:36:37:EE:26:26:37:37:36:37:36:26:26:B3:37:36:26:26:37:37:36:B7:36:66:AE:B7:37:36:37:36:AE:AE:BB:37:36:26:26:37:37:36:37:36:AE:66:66:37:B6:36:B3:26:BB:BE:B7:B7:B6:37:36:A6:A6:B3:B7:36:AE:66:26:BB:AE:37:37:B6:37:36:AE:BE:BB:B7:36:26:AE:B7:37:B6:37:EE:AE:26:B7:BF:B6:37:36:BE:27:B3:B7:36:AE:A6:B7:BF:B6:37:36:66:AE:B7:BF:B6:37:36:BE:AE:B3:37:36:26:26:37:BF:B6:37:36:26:6E:66:BF:B6:66:33:26:BB:A6:B7:37:36:37:36:26:26:B3:37:36:AE:66:26:BB:A6:B7
[18:34:21][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 67 != 37
[18:34:21][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 40 != 26
[18:34:21][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 9B != A6
[18:34:22][D][uart_debug:114]: <<< BF:B6:37:36:AE:A6:B3:B7:36:AE:26:37:37:36:37:EE:26:AE:B7:BF:B6:37:36:26:A6:B3:37:36:BE:BE:B7:B7:B6:37:36:66:26:37:BF:B6:37:36:AE:BE:B3:B7:36:A6:26:37:37:B6:37:36:26:76:66:B7:36:66:B3:26:BB:AE:B7:BF:36:37:36:A6:26:B3:37:36:26:66:26:BB:26:37:37:36:37:37:26:26:B3:B7:36:26:A6:37:37:36:37:FE:A6:26:37:37:36:37:36:AE:A6:B3:B7:36:AE:AE:B7:B7:B6:37:36:DE
[18:34:22][D][uart_debug:114]: >>> 55:01:00:00:00:00:00:00:00:00:00:FE

Could you provide another log tomorrow? This time there was some CRC errors because of a lot of random noise but the sensor wasn't updated with garbage. I would like to see one case where the start voltage changes to 0 V.

In other words I would like to see the RAW traffic which is causing this:
[16:21:10][I][soyosource_display:163]: Status frame received
[16:21:10][I][soyosource_display:282]: Settings:
[16:21:10][I][soyosource_display:291]:   Operation mode setting: 12
[16:21:10][I][soyosource_display:305]:   Device model: 0 W, 110 V (0)
[16:21:10][W][soyosource_display:583]:   Device type: Unknown (0)
[16:21:10][I][soyosource_display:308]:   Device type: Unknown
[16:21:10][I][soyosource_display:309]:   Battery voltage: 0 V
[16:21:10][I][soyosource_display:313]:   Start voltage: 0 V
[16:21:10][I][soyosource_display:319]:   Shutdown voltage: 0 V
[16:21:10][I][soyosource_display:333]:   Output power limit: 0 W
[16:21:10][I][soyosource_display:342]:   Start delay: 0 s
[16:21:10][I][soyosource_display:347]:   Minimum PV voltage: 0 V
[16:21:10][I][soyosource_display:350]:   Maximum PV voltage: 0 V
[16:21:15][I][soyosource_display:163]: Status frame received
[16:21:15][I][soyosource_display:282]: Settings:
[16:21:15][I][soyosource_display:291]:   Operation mode setting: 12
[16:21:15][I][soyosource_display:305]:   Device model: 1000 W, 220 V (210)
[16:21:15][I][soyosource_display:308]:   Device type: PV 26-56V / BAT 24V
[16:21:15][I][soyosource_display:309]:   Battery voltage: 24 V
[16:21:15][I][soyosource_display:313]:   Start voltage: 23 V
[16:21:15][I][soyosource_display:319]:   Shutdown voltage: 22 V
[16:21:15][I][soyosource_display:333]:   Output power limit: 700 W
[16:21:15][I][soyosource_display:342]:   Start delay: 6 s
[16:21:15][I][soyosource_display:347]:   Minimum PV voltage: 26 V
[16:21:15][I][soyosource_display:350]:   Maximum PV voltage: 45 V

Here is one more log file. Full log in attachment. Tomorrow I can do another log.

Is there any way how to optimise scope of logging?
Is another way how to gather the log or I have to have esphome opened in browser and disable sleep mode?

PS> thanks for your proactive cooperation!
[19:31:53][D][sensor:126]: 'soyosource-wifi-dongle temperature': Sending state 39.00000 °C with 1 decimals of accuracy
[19:31:53][D][uart_debug:114]: <<< 5A:01:91:40:00:F6:00:1A:00:E2:32:00:37:04:E7:27:C0
[19:31:54][D][uart_debug:114]: >>> 55:03:00:00:00:00:00:00:00:00:00:FC
[19:31:55][D][uart_debug:114]: <<< 61:7F:B3:77:36:BE:BE:BB:B7:36:BE:BE:B7:BF:F6:37:36:BE:BE:BB:B7:B6:36:B3:36:BB:AE:B7:BF:B6:37:36:AE:AE:BB:B7:36:BE:FE:B7:BF:BE:B7:36:BE:BE:B7:BF:B6:37:36:BE:BE:BB:F7:36:AE:BE:B7:B7:B6:37:BB:B6:37:36:AE:BE:BB:B7:36:AE:AE:B7:BF:B6:37:36:BE:AE:BB:BF:B6:26:B3:26:BB:AE:B7:BF:B6:37:36:BE:BE:FB:B7:36:BE:AE:B7:36:BE:B7:36:26:AE:B7:BF:B6:37:36:BE:BE:BB:B7:36:BE:BE:B7:BF:F6:F6:BB:B6:37:36:AE:BE:BB:B7:F6:FE:FE:F7:FF:F6:77:F6:FE:FE:F7:BF:B6:37:36:A6:AE:B3:B7
[19:31:56][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 37 != BF
[19:31:56][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 40 != BB
[19:31:56][D][uart_debug:114]: <<< 66:66:BF:B6:66:B3:26:BB:BE:B7:BF:66:36:BF:B6:66:B3:26:BB:A6:37:37:B6:37:36:AE:A6:B3:B7:36:AE:66:26:BB:6E:36:BF:B6:66:33:26:BB:AE:B7:B7:B6:37:36:BB:37:36:AE:66:26:BB:AE:B7:37:36:37:36:A6:26:B3:37:36:26:26:37:37:B6:37:EE:AE:26:37:3F:36:37:36:26:26:B3:37:36:26:26:37:B7:B6:37:36:76:2E:37:B7:36:B7:B6:26:26:B3:37:36:2E:26:37:37:B6:37:36:26:66:66:37:36:66:33:26:BB:26:B7:37:36:37:36:26:26:B3:37:36:26:66:26:BB:A6:B7:BF:B6:37:36:26:26:B3:37:36:AE:AE:37:37
[19:31:56][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! F3 != 26
[19:31:57][D][uart_debug:114]: <<< 26:AE:BB:37:36:26:AE:B7:37:B6:37:36:26:36:66:37:36:66:33:26:BB:26:B7:37:B6:37:36:26:AE:BB:37:BF:26:33:A6:BB:26:37:BF:B6:37:36:26:26:B3:37:36:A6:26:26:26:B3:B7:36:26:26:37:37:36:37:36:26:F6:66:37:36:E6:33:A7:BB:26:37:37:36:37:36:26:26:B3:37:B7:26:33:26:BB:26:37:37:36:37:36:26:26:B3:37:36:A6:26:37:BF:36:37:36:26:26:7F:37:36:37:36:26:26:B3:37:36:AE:A6:37:BF:36:37:36:B3:37:36:26:26:B3:37:36:26:26:37:37:36:37:37:26:26:B3:37:37:E6:7B:A6:BB:26:37:37:36
[19:31:57][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! E7 != 37
[19:31:57][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 47 != 37
[19:31:57][D][uart_debug:114]: <<< 26:66:26:BB:AE:B7:37:36:37:36:26:26:B3:37:36:26:26:37:37:36:37:FE:26:26:37:37:36:37:36:26:2E:B3:37:36:BE:AE:F7:37:36:37:36:66:BE:37:37:B6:37:36:AE:A6:B3:B7:36:BE:26:B7:B7:36:37:36:26:F7:66:37:36:66:33:26:BB:26:37:37:36:37:B6:26:26:B3:37:36:26:FE:26:BB:AE:37:37:B6:37:36:26:26:BB:B7:36:26:26:37:B7:36:37:FE:A6:26:37:37:36:37:36:26:26:B3:37:BF:66:26:37:37:36:37:36:66:26:B7:B7:B6:37:36:AE:AE:B3:37:36:26:26:37:37:36:B7:B6:26:7E:66:37:36:66:33:26:BB:26
[19:31:58][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! B3 != 36
[19:31:58][D][uart_debug:114]: <<< 77:37:36:37:36:A6:AE:BB:B7:36:26:66:26:BB:AE:37:37:36:37:36:2E:26:B3:B7:36:26:26:37:37:36:37:EE:26:26:37:37:36:37:36:26:27:B3:37:36:26:26:37:3F:36:37:36:76:26:37:37:36:37:36:26:26:B3:37:B6:26:26:37:37:36:37:36:26:66:E6:37:36:66:33:26:BB:26:77:37:36:B7:FF:26:26:F3:37:B7:26:F6:EF:BB:26:37:37:36:37:36:26:26:B3:3F:BF:66:66:37:37:7E:FF:FE:26:26:37:37:76:FF:36:26:26:B3:37:BE:26:26:37:37:36:37:B6:D6
[19:31:58][D][uart_debug:114]: >>> 55:01:00:00:00:00:00:00:00:00:00:FE
[19:31:58][E][soyosource_display:137]: No data from the Soyosource inverter received yet. This should never happen if the dongle is plugged into the inverter
[19:31:58][D][uart_debug:114]: <<< 5A:01:00:20:00:00:00:00:00:00:10:00:00:04:E7:00:E3
[19:32:02][D][uart_debug:114]: >>> 55:01:00:00:00:00:00:00:00:00:00:FE
[19:32:02][I][soyosource_display:163]: Status frame received
[19:27:23][D][uart_debug:114]: <<< 5A:01:91:40:00:F6:00:1B:00:E1:32:00:39:04:E6:27:BF
[19:27:24][D][uart_debug:114]: >>> 55:03:00:00:00:00:00:00:00:00:00:FC
[19:27:25][D][uart_debug:114]: <<< B5:7F:B3:37:36:FE:FE:FB:F7:76:BE:FE:F7:BF:B6:37:76:BE:BE:BB:B7:B6:26:B3:26:BB:AE:B7:B7:B6:37:36:BE:AE:BB:B7:36:FE:FE:F7:FF:FE:B7:36:93:37:36:AE:AE:FB:F7:36:AE:AE:F7:FF:F6:37:36:BE:BE:36:FF:F6:B6:F3:F6:FB:FE:B7:7F:E6:F7:F6:BE:AE:BB:B7:36:BE:FE:36:FB:FE:B7:BF:B6:37:36:BE:FE:FB:B7:36:BE:FE:B7:BF:B6:37:76:FE:BE:B7:BF:F6:37:36:BE:FE:FB:F7:F6:FE:FE:F7:FF:E6:F7:F6:FE:FE:F7:FF:B6:F7:76:BE:BE:FB:B7:F6:FE:BE:F7:7F:F6:F7:76:FE:FE:B7:BF:F6:F7:F6:BE:FE:FB:F7
[19:27:26][D][uart_debug:114]: <<< F7:F6:FE:FE:FB:F7:76:FE:E6:76:BB:BE:B7:BF:B6:37:36:BE:BE:BB:B7:36:FE:FE:F7:FF:F6:F7:66:FE:FE:B7:BF:B6:37:36:BE:BE:BB:B7:36:BE:FE:B7:BF:B6:37:36:66:A6:B7:BF:B6:37:36:A6:BE:BB:B7:F6:BE:AE:B7:BF:B6:37:F6:BE:66:36:BF:B6:26:B3:26:BB:BE:F7:BF:B6:77:36:BE:BE:BB:B7:36:BE:66:36:BB:BE:B7:BF:B6:37:36:26:AE:B3:B7:36:26:AE:B7:BF:B6:37:6E:BE:BE:B7:BF:B6:37:36:BE:BE:BB:B7:36:BE:AE:B7:BF:B6:37:F6:66:AE:B7:BF:B6:37:36:FE:BE:BB:B7:36:BE:BE:B7:BF:B6:37:36:BE:6E:36
[19:27:26][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 20 != 36
[19:27:26][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! 0B != AE
[19:27:27][D][uart_debug:114]: <<< BF:B6:37:36:BE:A6:BB:B7:36:AE:AE:B7:B7:B6:37:36:6E:AE:B7:BF:B6:37:36:AE:BE:BB:B7:36:A6:AE:B7:BF:B6:37:36:A6:6E:26:BF:B6:36:B3:36:BF:B6:37:36:AE:A6:B3:B7:36:BE:A6:B7:BF:36:37:36:6E:AE:B7:B7:36:37:36:AE:AE:BF:B6:37:76:AE:AE:BB:B7:36:AE:26:37:37:B6:37:36:AE:36:66:37:B6:36:B3:26:BB:AE:B7:BF:B6:37:36:A6:26:B3:B7:36:26:33:26:BB:26:B7:37:B6:37:36:BE:AE:B3:37:36:26:26:37:37:36:37:36:26:A6:B7:BF:B6:37:36:AE:BE:BB:B7:36:AE:AE:B7:B7:B6:37:36:BE:BE:B7:BF:B6
[19:27:27][D][uart_debug:114]: <<< FB:F7:F6:FE:FE:F7:FF:B6:77:66:FE:FE:F7:BF:B6:37:36:BE:FE:BB:F7:F6:BE:BE:B7:FF:F6:77:36:66:FE:B7:BF:B6:37:36:FE:BE:BB:F7:36:BE:FE:F7:FF:E6:F7:36:BE:66:36:FF:B6:36:B3:F6:FB:B6:F7:76:BE:FE:BB:F7:F6:FE:BE:B7:BF:76:F7:F6:BE:FE:B7:FF:E6:F7:F6:FE:FE:BB:B7:36:FE:FE:B7:BF:B6:2F:36:BE:BE:F7:FF:B6:37:76:AE:FE:BB:B7:76:BE:FE:F7:BF:E6:F7:66:BE:FE:B7:BF:B6:77:36:FE:BE:BB:B7:36:BE:BE:B7:BF:B6:37:36:66:BE:B7:BF:B6:37:36:FE:FE:BB:B7:36:BE:FE:B7:BF:F6:F7:F6:FE:66
[19:27:27][W][soyosource_display:108]: SoyosourceDisplay CRC Check failed! D0 != F7
[19:27:28][D][uart_debug:114]: <<< B6:FF:F6:B6:F3:F6:FB:FE:F7:FF:E6:F7:76:FE:BE:BB:F7:76:FE:66:36:BB:AE:B7:BF:B6:F7:36:FE:BE:FB:F7:F6:FE:FE:F7:FF:E6:F7:66:FE:FE:F7:BF:B6:37:36:AE:AE:FB:F7:36:BE:FE:B7:BF:B6:37:36:66:AE:B7:BF:B6:37:36:FE:BE:BB:B7:36:BE:FE:B7:FF:B6:F7:F6:FE:EE:36:FF:F6:36:B3:76:BB:BE:F7:BF:F6:77:36:BE:FE:BB:B7:76:FE:66:F6:FB:FE:F7:FF:E6:77:36:A6:FE:BB:B7:36:FE:BE:B7:BF:B6:37:6E:FE:FE:F7:FF:B6:37:36:AE:BE:BB:B7:36:FE:BE:F7:FF:F6:77:76:66:BE:B7:BF:B6:37:76:BE:FE:BB:B7
[19:27:28][D][uart_debug:114]: <<< 36:BE:FE:F7:FF:E6:F7:F6:BE:6E:66:BF:B6:36:B3:36:BB:BE:B7:FF:F6:F7:F6:FE:FE:FB:F7:F6:FE:66:F6:FB:FE:F7:FF:F6:F7:F6:FE:FE:FB:F7:F6:FE:FE:F7:FF:E6:F7:DE
[19:27:28][D][uart_debug:114]: >>> 55:01:00:00:00:00:00:00:00:00:00:FE
[19:27:28][E][soyosource_display:137]: No data from the Soyosource inverter received yet. This should never happen if the dongle is plugged into the inverter
[19:27:28][D][uart_debug:114]: <<< 5A:01:00:20:00:00:00:00:00:00:10:00:00:04:E6:00:E4
[19:27:32][D][uart_debug:114]: >>> 55:01:00:00:00:00:00:00:00:00:00:FE
[19:27:32][I][soyosource_display:163]: Status frame received
[19:27:32][D][soyosource_display:171]: Unknown (raw): 01 (always 0x01?)
logs_soyo-wifi-dongle_upload-4.txt.zip

In other words I would like to see the RAW traffic which is causing this:
[16:21:10][I][soyosource_display:163]: Status frame received
[16:21:10][I][soyosource_display:282]: Settings:
[16:21:10][I][soyosource_display:291]:   Operation mode setting: 12
[16:21:10][I][soyosource_display:305]:   Device model: 0 W, 110 V (0)
[16:21:10][W][soyosource_display:583]:   Device type: Unknown (0)
[16:21:10][I][soyosource_display:308]:   Device type: Unknown
[16:21:10][I][soyosource_display:309]:   Battery voltage: 0 V
[16:21:10][I][soyosource_display:313]:   Start voltage: 0 V
[16:21:10][I][soyosource_display:319]:   Shutdown voltage: 0 V
[16:21:10][I][soyosource_display:333]:   Output power limit: 0 W
[16:21:10][I][soyosource_display:342]:   Start delay: 0 s
[16:21:10][I][soyosource_display:347]:   Minimum PV voltage: 0 V
[16:21:10][I][soyosource_display:350]:   Maximum PV voltage: 0 V
[16:21:15][I][soyosource_display:163]: Status frame received
[16:21:15][I][soyosource_display:282]: Settings:
[16:21:15][I][soyosource_display:291]:   Operation mode setting: 12
[16:21:15][I][soyosource_display:305]:   Device model: 1000 W, 220 V (210)
[16:21:15][I][soyosource_display:308]:   Device type: PV 26-56V / BAT 24V
[16:21:15][I][soyosource_display:309]:   Battery voltage: 24 V
[16:21:15][I][soyosource_display:313]:   Start voltage: 23 V
[16:21:15][I][soyosource_display:319]:   Shutdown voltage: 22 V
[16:21:15][I][soyosource_display:333]:   Output power limit: 700 W
[16:21:15][I][soyosource_display:342]:   Start delay: 6 s
[16:21:15][I][soyosource_display:347]:   Minimum PV voltage: 26 V
[16:21:15][I][soyosource_display:350]:   Maximum PV voltage: 45 V

Sorry I missed this comment. Just for sure I can remove and re-add the device to HA. Just to be sure. I fully reinstalled it few weeks a go.

Could you provide another log capture including the mentioned issue? Thanks in advance!

Sorry to be late.
soyo.yaml.zip
logs_soyo-wifi-dongle_logs-3.txt.zip

I've pushed a small change into main. Please build & flash your Dongle (via OTA) again.
This is some background about the phenomenon: The WiFi Dongle consists of two main components the ESP8266 and a second microcontroller called MS51. The MS51 tracks the total energy and acts like an gateway between the Soyo and the ESP8266. Every now and then the MS51 crashs. This incoming traffic / garbage
[19:27:25][D][uart_debug:114]: <<< B5:7F:B3:37:36:FE:FE:FB:F7:76:BE:FE:F7:BF:B6:37:76:BE:BE:BB:B7:B6:26:B3:26:BB:AE:B7:B7:B6:37:36:BE:AE:BB:B7:36:FE:FE:F7:FF:FE:B7:36:93:37:36:AE:AE:FB:F7:36:AE:AE:F7:FF:F6:37:36:BE:BE:36:FF:F6:B6:F3:F6:FB:FE:B7:7F:E6:F7:F6:BE:AE:BB:B7:36:BE:FE:36:FB:FE:B7:BF:B6:37:36:BE:FE:FB:B7:36:BE:FE:B7:BF:B6:37:76:FE:BE:B7:BF:F6:37:36:BE:FE:FB:F7:F6:FE:FE:F7:FF:E6:F7:F6:FE:FE:F7:FF:B6:F7:76:BE:BE:FB:B7:F6:FE:BE:F7:7F:F6:F7:76:FE:FE:B7:BF:F6:F7:F6:BE:FE:FB:F7
[19:27:26][D][uart_debug:114]: <<< F7:F6:FE:FE:FB:F7:76:FE:E6:76:BB:BE:B7:BF:B6:37:36:BE:BE:BB:B7:36:FE:FE:F7:FF:F6:F7:66:FE:FE:B7:BF:B6:37:36:BE:BE:BB:B7:36:BE:FE:B7:BF:B6:37:36:66:A6:B7:BF:B6:37:36:A6:BE:BB:B7:F6:BE:AE:B7:BF:B6:37:F6:BE:66:36:BF:B6:26:B3:26:BB:BE:F7:BF:B6:77:36:BE:BE:BB:B7:36:BE:66:36:BB:BE:B7:BF:B6:37:36:26:AE:B3:B7:36:26:AE:B7:BF:B6:37:6E:BE:BE:B7:BF:B6:37:36:BE:BE:BB:B7:36:BE:AE:B7:BF:B6:37:F6:66:AE:B7:BF:B6:37:36:FE:BE:BB:B7:36:BE:BE:B7:BF:B6:37:36:BE:6E:36

is the output of the MS51 bootloader at a different baud rate while booting up. After the reboot the MS51 has to warm-up.  This means the MS51 must receive a status and a settings frame from the Soyo. If the ESP8266 asks the MS51 about the current status/settings between the "reboot" and the "warm-up" the MS51 responds with a frame full of zeros. The proof this assumption I've added some more logging and a safe-guard to reject "empty frames". This should stabilize the sensor measurements pushed to Home Assistant. The CRC errors will pop up constantly every time the MS51 reboots (for unknown and unfixable reasons).


Universal navigation links undefined

Some of the links in the universal navigation don't seem to work on staging, I believe it might because of the function linked below which seems to be used for top level links, but top level links don't seem to have an external_link property as far as I can see?
https://github.com/mplusmuseum/mplusmuseum-stories/blob/master/src/components/AppHeaderDropdown.vue#L155-L158

@rdunk rightly observed and is an issue previously noted I believe. Please see solution in pull request #255

Hi @rdunk, @arnasziedavicius—
The issue regarding the universal nav links was previously fixed. It seems that on the new Staging Site (https://staging-stories.mplus.org.hk/en/) that these fixes have been overridden or not incorporated.
FE:

(note URL in bottom left hand corner)
CMS:

(note URL in CMS)

Am I right in saying that if pull request #255 is implemented this issue will be resolved?

Am I right in saying that if pull request #255 is implemented this issue will be resolved? Other tasks such as the blue effect bug and the menu collapse seem to be behaving as expected in the new iteration of Staging...

@chrismplus, you are correct, it should get resolved anew once #255 is implemented. Will keep an eye on things here and confirm once it's on staging.

Now resolved on staging.


Review calls of toHtml() with id

The change to toHtml() in #16 caused problems in the legacy system (and might cause problems in other places, too):
When rendering the meta description of a course page, we go up to the parent and render that description instead. But when the parent (i.e. the course) doesn't have a description either, the Normalizer just returns the id as description (I assume, to handle the "go to parent" in course pages). Problem though: the id is a valid json (since it's an int) but can't be rendered by the editor renderers.

In legacy, we still cover this with try-catch and just return the id as a string (after applying the quickfix)
In kubernetes, we pass it to the renderer which will fail and therefore return an empty response

We should review whether there are other ints we try to render with toHtml that should be rendered. And probably fix meta description handling of courses since the id as a description doesn't make sense.

As far as I can understand, this issue is outdated due to the migration


Incorrect syntax near 'LIMIT'

The Limit clause added by First() or FirstOrDefault() is not compatible with SQL Azure, as it throws this exception:
Incorrect syntax near 'LIMIT'

Not a bug, I was using the incorrect compiler.


JS Error on the wallet page (empty wallet)

JS Error
A non-serializable value was detected in an action, in the path: `payload.cancelToken`.

Preflight Checklist

[x] I have searched DeFiChain’s Github Issue Page and none matches my issue
[x] I have read through How To Submit Issues for DeFi App

Issue Details

Current DeFi App Version:

2.1.12

Previous DeFi App Version:

2.1.11

Operating System (OS):

MacOS

Screenshot(s) / screen recording(s) of issue
Video: https://siasky.net/_ATxUkS_PywvQ2XhBcHb1vQwPM9dTp7kSTbnLY0BvNRo7g
Screenshot: https://siasky.net/fAAZk55CuoyQqVP-kG6Skhvt_Gxlu_J-GVWED6IHIwcLnQ
Actual Behavior
1. Open the app
2. Open Developer Tools
3. Go to wallets page
4. Click on a wallet
5. See the console

Expected Behavior
No JS error occurs
Logs
Archiv.zip

Hi @sergejmueller
	, update v2.1.15 is out.
Do give a thumbs up to this comment if your issue has been resolved, otherwise, provide new information (include screenshots) and app logs. Thank you.

Hi @sergejmueller
	, update v2.1.15 is out.
Do give a thumbs up to this comment if your issue has been resolved, otherwise, provide new information (include screenshots) and app logs. Thank you.

@izzycsy Not fixed, just the same error.

@izzycsy Not fixed, just the same error.

@izzycsy Wich PR should solve this issue?

Hi @sergejmueller , this issue is not yet available in the current v2.1.15. Rest assured that your feedback has been sent to the team. I'll keep you updated when it's been fixed. Thank you for your patience.

This should be fixed on v2.1.17.


refactor refactor and upgrade dependency tree of FE and support AWS glue catalog

Proposed changes
Issue Number: close #xxx
Problem summary

Spark dpp
Move DppResult and EtlJobConfig to sparkdpp package in fe-common module.
So taht fe-core is longer depends on spark-dpp module, so that the spark-dpp.jar
will not be moved into fe/lib, which reduce the size of FE output.

Modify start_fe.sh
Modify the CLASSPATH to make sure that doris-fe.jar is at front, so that
when loading classes with same qualified name, it will be got from doris-fe.jar firstly.

Upgrade hadoop and hive version
hadoop: 2.10.2 -> 3.3.3
hive: 2.3.7 -> 3.1.3

Override the IHiveMetastoreClient implementations from dependency
ProxyMetaStoreClient.java for Aliyun DLF.
HiveMetaStoreClient.java for origin Apache Hive metastore.
Because I need to modified some of their method to make them compatible with
different version of Hive.

Exclude some unused dependencies to reduce the size of FE output
Now it is only 370MB (Before is 600MB)

Upgrade aws-java-sdk version to 1.12.31

Support AWS Glue Data Catalog

TODO: add doc in next PR
Checklist(Required)

Does it affect the original behavior:

[ ] Yes
[x] No
[ ] I don't know

Has unit tests been added:

[ ] Yes
[ ] No
[ ] No Need

Has document been added or modified:

[ ] Yes
[x] No
[ ] No Need

Does it need to update dependencies:

[ ] Yes
[x] No

Are there any changes that cannot be rolled back:

[ ] Yes (If Yes, please explain WHY)
[x] No

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 35.85 seconds
load time: 496 seconds
storage size:<PHONE_NUMBER>5 Bytes
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230119071607_clickbench_pr_83924.html


Using awesome-typescript-loader source file name is undefined

Check for state.file.opts.parserOpts.sourceFileName if the file name couldn't be found.
Change should be applied to https://github.com/darkyndy/babel-plugin-auto-logger/blob/master/src/arguments.js#L36

Implementation completed and is available in v0.6.0


Bootz FP

Pull Request Functional Test Report for #2325 / aa4c391603772c370fdbdfe23f9d93a60f41a9b6
No tests identified for validation.
Help

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 48.7%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1536

Relevant Lines:
3154

💛  - Coveralls


Plugin Radio does not recognize AAC+ radio streams

Hi just wanted to know if there's a way to make aac streams work on this plugin if possible by direct linking to m3u playlist that are mostly used by mp3 / aac or other. I tested it on my kiwi chat, but no luck to work. Would be appreciated if you could look into this. I tried on my radio station using the direct link from my server http://<IP_ADDRESS>:4272/live.m3u but nothing could be heard on the plugin.

If there is a possibility to have a way implementing aac in the player would be appreciated. I have found something that might help using howler.js might help to make it a better player? https://medium.com/crowdbotics/build-your-own-radio-streaming-app-with-howler-js-637f929decc0

The ability to play formats is limited by the browser. mp3 seems to be the best format to use from my limited testing (ff, chrome, ie11, edge).
I did initially try to use howler but ran into issues with chrome which have since been fixed, but howler uses html5 audio for audio streams so wouldnt add format support to the browser, it would also mean going back to the older webpack version and loosing the current simplicity and ease of modification.

Well I found a workaround for now. I added a parallel stream to my centova cast icecast 2 mount point and made it to work with mp3 streaming. I think that's the only workaround i could do for now, while i do hate mp3 streaming and always preferred aac+. But if there will ever be a way to make it work with aac and opus would be appreciated! :-)


BCNA Logo Revision

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

[x] Filename in the lowercase format
[x] Image format: png
[x] Image size: 256 by 256 px

Transparency for black background was very poor for the last image. This one is not prefect but much better than the last one.

Added here https://github.com/TrustWallet/tokens/commit/26a4460a153416d11237f1bb8a6bf6672542d063


docs/openapi: fix doc to update service by system_name

Documentation update to be consistent with last implementation updates

ping @mkudlej


Job failed due to copy

I received this error after running job ID 1640 for distiller ID:
"cp: cannot create regular file '/global/cfs/projectdirs/ncemhub/distiller/counted/2022.04.25/data_scan274_id1926_electrons.h5': Permission denied"
This is due to the existence of a file with the same name that was counted on mothership6 locally. The file was copied from that machine to the ncemhub/distiller/counted/2022.04.25 directory.
There is no need to account for this rare occurrence. I just wanted to mention this in case this error might happen when counting the same data set twice through Distiller.

@ercius I think this might also be resolved by a collab account/group.

Ill look into that!


feat: add testing and standalone mode

Problem: we should have a basic test that the plugin works with compspec.
Solution: add a test, along with refactoring the plugin organization so that it is possible to run a single function in a flux instance, "generate_cluster" that will dump out the node graph on the fly, and no need to be executed as an extraction plugin by the higher level compspec. I'm also adding:

an example for the standalone use case
a code of conduct
a fixed README example (I was only showing the nodes, oups)

https://youtu.be/3KDnrGdpNZY?si=fYwsHuVZLjZc2yzz
no, really!


After updating to every version above 2.9.1 the plugin vite-plugin-restart stops working

Describe the bug
I'm using the following config, but after updating vite.js to a version above 2.9.1 this is not working anymore.
The feedback I get back from vite with version 2.9.1 is
1:57:45 PM [vite] page reload templates/index.twig
After updating the feedback is empty.
2:00:43 PM [vite]
2:00:44 PM [vite]  (x2)
2:00:44 PM [vite]  (x3)
2:00:44 PM [vite]  (x4)
2:00:44 PM [vite]  (x5)
2:00:45 PM [vite]  (x6)

plugins: [
        ViteRestart({
            reload: [
                path.join(__dirname, './templates/**/*'),
            ],
        })
]

I can't pinpoint where this issue is coming from exactly, but the fact that it breaks after updating I would say it has something to do with the config?
I can't get the reproduction link to work with the restart plugin so i might need some help with that please :)
Reproduction
https://stackblitz.com/edit/vitejs-vite-p86mjd
System Info
System:
    OS: macOS 12.4
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
    Memory: 19.00 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 14.15.1 - /usr/local/bin/node
    npm: 7.20.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 102.0.5005.61
    Firefox: 99.0
    Safari: 15.5
  npmPackages:
    @vitejs/plugin-legacy: ^1.8.2 => 1.8.2
    vite: ^2.9.1 => 2.9.1
    vite-plugin-restart: ^0.1.1

Used Package Manager
npm
Logs
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I can't reproduce this locally, using macos too. The reload is working fine for me for 2.9.1, 2.9.2, and 2.9.9.

I was also not able to reproduce this.

I can't get the reproduction link to work with the restart plugin so i might need some help with that please :)

Remove "type": "module", from package.json to make it work.


Having issue installing python :  /install.sh

These info above are correct? (y/n) :y
wine: cannot find '/root/.wine/drive_c/Python27/python.exe'
Traceback (most recent call last):
File "bee.py", line 161, in
main()
File "bee.py", line 107, in main
os.rename('dist/k.exe', 'dist/' + name)
OSError: [Errno 2] No such file or directory
root@kali:~/BeeLogger#
./install.sh
-> Trys to download python in wine but never works. I did see a video on you-tube with this dude fixing it but I could not understand a single thing he was saying // but did understand mostly on how he fixed it but was having trouble on the way he did it. I'm going to try and watch that video again and see if I can fix this issue.
Can't figure out of the fix this issue. I know ti is dealing with the python not being able to download correctly. Any solutions. The solutions provided in the other Issue didn't work for me. I have try multiple things but can't get the python2.7 to download.

Has anyone figured out on how to fix this? If not got any suggestion on other programs that do what BeeLogger
does. Thank you!

Try to install python again. But when the dialog shows up. Select "Install just for me"

Try to install python again. But when the dialog shows up. Select "Install just for me"

didnt work for me any other thing i can do?


Extension issue

Issue Type: Bug
Extension Name: python
Extension Version: 2021.4.765268190
OS Version: Windows_NT x64 10.0.19041
VS Code version: 1.55.2

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Thanks for the bug report, but unfortunately we need some more information from you in order to triage this issue appropriately. Please create a new bug by providing a filled-in copy of our issue template.


Enable endpoint customization for each integration

Each AWS integration should provide a way to specify custom endpoint url via application.properties. For example:
cloud.aws.sqs.endpoint-url=http://localhost:4567

This would allow to set easily services to use Localstack (#333) for testing or VPC endpoints (#152) in production.

@maciejwalkowiak what would the prefered impl. of this? Given the relative complexity of how the modules are setup would it be easiest to just add new configuration properties to their relevant modules.
For example,
a new AwsSNSProperties class in spring-cloud-aws-messaging with two fields endpoint and region that would be applied to the SNS Client?

@DarrenForsythe it's still under investigation. One thing is endpoint customization but it also has to play nice with ClientConfiguration customisation and ideally properties should not require changes once we move to AWS SDK v2.
Properties will be placed in autoconfigure module for sure but quite a lot of changes in case of messaging are required to make it work with messaging module.
Don't jump on it (yet) please.

Since currently everyone who uses Spring Cloud AWS will currently have to choose between either not testing their code, or writing a custom solution to this problem, a quick resolution would trump a perfect resolution. Especially since as long as the parameter names stay the same, the underlying implementation can be swapped out for a better one at will.

Current idea: create base class all integrations would inherit from:
public abstract class AwsServiceProperties {
	private EndpointProperties endpoint;

	public static class EndpointProperties {
		private URI uri;
		private Regions signingRegion;
	}
}

Update AmazonWebserviceClientFactoryBean to accept EndpointConfiguration.
In each integration auto-configuration follow pattern:
// create `<service>EndpointConfiguration` bean only if property is present
@Bean(name = "sqsEndpointConfiguration")
@ConditionalOnProperty("cloud.aws.sqs.endpoint")
public EndpointConfiguration sqsEndpointConfiguration(SqsProperties sqsProperties) {
	return new EndpointConfiguration(sqsProperties.getEndpoint().getUri().toString(),
			sqsProperties.getEndpoint().getSigningRegion().getName());
}

// pass this bean as optional with Qualifier to bean factory creating AWS client
@Lazy
@Bean(destroyMethod = "shutdown")
public AmazonSQSBufferedAsyncClient amazonSQS(@Qualifier("sqsEndpointConfiguration") Optional<EndpointConfiguration> endpointConfiguration) throws Exception {
	AmazonWebserviceClientFactoryBean<AmazonSQSAsyncClient> clientFactoryBean = new AmazonWebserviceClientFactoryBean<>(
			AmazonSQSAsyncClient.class, this.awsCredentialsProvider,
			this.regionProvider);
	endpointConfiguration.ifPresent(clientFactoryBean::setEndpointConfiguration);
	clientFactoryBean.afterPropertiesSet();
	return new AmazonSQSBufferedAsyncClient(clientFactoryBean.getObject());
}

This is not exactly going to work for Secrets Manager and Parameter Store integration as they are detached from the autoconfigure module - meaning they wont be able to extend from AwsServiceProperties. Other than that they can follow similar pattern.
All of these should be possible to be done once #636 and #598 are merged.

Including the EC2 metadata service endpoint override, a.k.a. com.amazonaws.sdk.ec2MetadataServiceEndpointOverride?

I had in mind setting endpoint for AWS clients. Do you think it makes sense for EC2 metadata service too since it can be already relatively easily configured through system property?

It makes sense to make Spring Cloud applications as easily testable as other Spring applications, from a standard configuration, rather than throwing unexplained exceptions at test execution, and then requiring every user to solve the same issues with testing independently.

POC of a workaround while waiting for proper testing tools: https://github.com/mikaelhg/aws-test-conf-poc

Closed in #715


Link actions badge to main

Currently the github CI actions badge on the readme will show failing if the tests fail on any of the branches. I think this should be tidied to the main branch, following: https://docs.github.com/en/actions/monitoring-and-troubleshooting-workflows/monitoring-workflows/adding-a-workflow-status-badge#using-the-branch-parameter
Pretty sure this change should solve the problem

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

Project coverage is 94.88%. Comparing base (cd29ad7) to head (b528d61).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #60   +/-   ##
=======================================
  Coverage   94.88%   94.88%
=======================================
  Files          11       11
  Lines         469      469
=======================================
  Hits          445      445
  Misses         24       24

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


feat: ULID

Hey, it's my first time contributing to C++, so I may require some patience. I just added this implementation: https://github.com/suyash/ulid to the lib for ULID(https://github.com/cieslarmichal/faker-cxx/issues/997). I created a test and everything is building/passing. Just a note, when I run the format script, I get Invalid value for—style so it may be a version issue. Which version of clang-format should I use?

please check if we can remove some methods from this implementation, maybe we don't use every function from his repo?

Please also add a section in LICENSES file and mention this repo you used

Done

please check if we can remove some methods from this implementation, maybe we don't use every function from his repo?

Yes, I will keep only the minimum.

I have clang-format in version 18. please try to install newer than you have

and run formatting

and run formatting
I get the same error
Invalid value for -style
I am using version 18, any idea why?

$clang-format --version
Ubuntu clang-format version 18.1.8 (++20240731024944+3b5b5c1ec4a3-1~exp1~20240731145000.144)

Build also fails

Build also fails

Last commit should fix shared-lib builds.

I ran the format command manually and it worked, seems like the script has an issue

It works when I add the bash path, should I also commit this file?

Yes please commit

Yes please commit

Done


Google-v2 gcs fuse support

Some of our internal users have expressed interest in adding support for GCS FUSE mounting of buckets. The pipelines team has published an example of doing this in the v2alpha1 API. It should be possible to do this with dsub's "google-v2" provider.

Cloud Storage Fuse support was included for the google-v2 provider in release 0.2.1.
Will look into support for the local provider as well.
Will not be supported in the (deprecated) google provider.

Rather than supporting gcsfuse in the local provider, we have added support for mounting a local directory with the --mount flag. This enables local development and testing prior to scaling up running in cloud.
This was added to the local provicer in release 0.2.4.


bug: github pages caches files

gh pages caches files. hence already-retrieved notes don't get updates.

fixed by #7


 should automatically add an xi:include to the XML in memory.

Description
Note that I've used xxxx as a placeholder for any valid RFC number throughout this post.
When given an XML file that includes <xref target="RFCxxxx">, the xml2rfc tool returns this error:
Error: IDREF attribute target references an unknown ID "RFCxxxx", at None

Instead of returning an error the tool should use this as a signal to make the following changes the loaded XML in memory and then start again with that modified XML.

If not already present, add attribute xmlns:xi="http://www.w3.org/2001/XInclude" to the top level <rfc> element.
Look inside the <back> element for an element <references title="Normative References"> or add it if not present.
Add to the <references> element: <xi:include href="http://xml2rfc.tools.ietf.org/public/rfc/bibxml/reference.RFC.xxxx.xml"/>

The reference to another RFC is boilerplate and there's enough information in the xref element to know what's needed. Requiring authors to copy-and-paste the reference is a chore that can be automated.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

Author's source needs to be explicit - we can provide tools to generate the fixed-up source you suggest, but it would not be the right thing to do to quietly pass failing source.
nit: stop aiming at xml2rfc.tools.ietf.org - it no longer exists - aim at bib.ietf.org instead.

How is the tool supposed to guess whether it is supposed to be a normative or informative reference?
You could hack this with some sort of code in markdown but not in xml2rfc

You could hack this with some sort of code in markdown but not in xml2rfc

Easier with kramdown-rfc: https://github.com/cabo/kramdown-rfc#references

stop aiming at xml2rfc.tools.ietf.org

Thank you!


Using DeBERTa instead of ALBERT

Is it possible to reproduce results with DeBERTa?

Sure.
I only provide the scripts for ALBERT before, considering that this is only a sample of use, and somebody may not be able to run DeBERTa (which is much larger than ALBERT).
The scripts w.r.t. DeBERTa could be achieved easily by slightly modifying the file "scripts/run_pet.sh".
But to reduce your workload, I uploaded a file called "scripts/run_deberta_pet.sh". Some hyper-parameters are modified for a better baseline, which has been explained in Appendix A.1 of our paper.
To run with DeBERTa, you could follow the "readme", and substitute all "run_pet.sh" with "run_deberta_pet.sh".
One thing to note is that you should search the hyperparameters in Step3 according to appendix A.5 of our paper. The best config for ALBERT and DeBERTa is not the same. A better implementation or a larger search space is welcome :).
Last but not least, thanks for your attention.

Thank you!
And while running the baseline on ReCoRD with ALBERT, I saw this line "Token indices sequence length is longer than the specified maximum sequence length for this model (918 > 512). Running this sequence through the model will result in indexing errors". Does it matter?

Well, It doesn't matter.


publicize NIOFoundationCompat

Is there a reason this package was not added to the products array in the package manifest?
If that's just an oversight, I'm happy to submit a PR. :)

@tanner0101 its an oversight :( Yes please provide a pr @tanner0101 :)


[Icon Requests from Feather] sword

As per https://github.com/lucide-icons/lucide/issues/119 and https://github.com/feathericons/feather/issues/220:

Nice! I would say the right row!

The first on bottom looks like a syringe.
So a prefer the first one for sword and the second one for Battle.

Yeah, and the third column is also the one most in line with the Lucide aesthetic, so I think I'll make a PR.


Add FlatFiles

https://github.com/jehugaleahsa/FlatFiles
https://www.nuget.org/packages/FlatFiles

https://github.com/joelverhagen/NCsvPerf/pull/26

https://github.com/joelverhagen/NCsvPerf/pull/26


Minor readme fixes

This small PR will fix a few wrong Readme.md formatting here and there

Hi @giulio92 good catch!  Thanks for this PR.
All the readme.md files in this repo are generated from the readme_template.md template file.
Can you please make these changes to readme_template.md and create a new PR?
This way you'll be listed as a collaborator.  Otherwise these changes will be overwritten the next time I generate a new set of amalgamated hosts files, soon.
I'll wait for your revised PR.

Done 😊

Thanks @giulio92!


Export pkgs.nodePackages (for e.g. prettier) in nixpkgs.ts

How will this work? Will it be exported as a nested record? (It feels like we can’t export all these packages as the top level without a big risk of conflict.)

The implementation I have in #382 breaks each sub package up into its own file and uses export * from "...". This way pkgs matches as close as possible to the real nixpkgs in terms of structure, and we don't have conflicts.


pip install skips noisers

Hi,
Thanks for the work.
Any idea why pip install neuspell doesn't install noising methods also?

Followup: is it possible to add them to it, thanks.

Hi,
You can try using git clone instead of pip to install the neuspell, then you can import noising module.
I used Repo module from gitPython to install it, so far so good.

I'm having the same issue with neuspell installed through pip. Is anyone following up with the problem?

@shivashankarrs I have a workaround for the missing noising package through pip install.
After install neuspell through pip, navigate to its directory. For me (using macOS 11.5.2) it looks like this:
/Users/XXXXXX/miniconda3/envs/py37/lib/python3.7/site-packages/neuspell
Then manually copy the /noising folder of the repository under /neuspell.
I also noticed the files under /neuspell are not up to date. So you may have to replace them with those downloaded from GitHub.
Hope this helps


add syslog port to the list of used ports for Bare Metal provider

Description of changes:
Seems syslog messages are sent from the host that is getting provisioned to boots. Example logs from hubble observe (using host firewall with cilium community):
Jun  5 08:17:26.198: HOSTIP:56019 (remote-node) -> BOOTSIP:514 (host) policy-verdict:none INGRESS AUDITED (UDP)
Jun  5 08:17:28.266: HOSTIP:35963 (remote-node) -> BOOTSIP:514 (host) policy-verdict:none INGRESS AUDITED (UDP)

This PR will add the UDP 514 to the list of ports for bare-metal provider.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/ok-to-test

/approve