I'm pretty sure that it's a side effect of the non monotonic DTS thing--you probably missed an IDR. I'll see if I can figure it out. Certainly not a function of your shell


Fixed the timing issues, which includes mp4 timing, so it should work without jank.

I'm going to close this issue, if you still see the frame corruption issues open a new issue. Thanks for all the help guys!


I doublecheck your example and yes same principle issue. Object _foobar_ is referenced to another class and abaplint seems to identify the method call (signature) in line 23 as the method which is in the interface _if_srv_, but that's not true. Because w/o assigning _iv_docid_ no syntax issue. On the other hand you can typ _foobar_ ref to any kind of z-class e.g. and there is no error shown, that class is unknown. This is the expected behavior, also in your example above.


The README that you read is for a WIP newer version of the plugin that is not yet released. The `DenoisedPathTracer` is not in the 0.4.0 version of the plugin. This README is for the 0.4.0 version of the Denoiser plugin.


This may be fixed once we find out how to share code between client extensions, which is being investigated at URL


if you change the code to use functional writing, I think it should work, as a workaround.... URL


Here is why I think it is not working: The seed phrase is used by a core wallet already known/loaded to bitcoin core but not by specter desktop but a different software. The error is a little but misleading.


You are right - It's working with the functional writing. Thank you 👍 Is it planned to provide a long term fix?


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


The above comment is a SCAM link! Do not follow the link. Block/Report the user.


long term fix: yes, just takes time, and I need to concentrate for rewriting stuff 😅


Des nouvelles du développement Atos pour le SDIS 85 ? Et mise à disposition de la communauté ?


Hello,
I have rechecked with old calling variant and with the newest abaplint version (2.9.53) and finally the issue is fixed. So thanks a lot for providing also a bugfix for that :-) It was a very short term long term fix ;-)
Best regards,
Dominik


yea, well, sometimes its difficult to get stuff working, ABAP is a messed up language


We have recently moved over around 150 users to Bitwarden from Lastpass. Set the organization policy for Vault Timeout to 2 hours max, but users are reporting that their extensions are still unlocked on login after several days of being away from the device. This is a major concern for us. Any update on a timeline for a fix?


#1658 seems related. There can also be a stacktrace be found:

Traceback (most recent call last):
 File "flask\app.py", line 1950, in full_dispatch_request
 File "flask\app.py", line 1936, in dispatch_request
 File "flask_login\utils.py", line 269, in decorated_view
 File "cryptoadvance\specter\server_endpoints\devices.py", line 207, in new_device_mnemonic
 File "cryptoadvance\specter\util\mnemonic.py", line 42, in validate_mnemonic
 File "mnemonic\mnemonic.py", line 115, in detect_language
mnemonic.mnemonic.ConfigurationError: Language not detected

That feature has been implemented in fc6521f and c3ae3d9 . I don't think all languages are supported and i guess the error-message and UX should be improved here.
@moneymanolis can you qualify that better?


Just saw that you used the english language. So i just tried to reproduce on the master branch with

ghost ghost ghost ghost ghost ghost ghost ghost ghost ghost ghost machine

That worked without an issue. Can you test that?!


Here is the link to the error from the upstream library from Trezor:
 URL

Do you have a stacktrace?

If it looks like the one @k9ert posted (below again) it's rather unlikely. I am tagging @prusnak perhaps he can help us here to see in which direction to investigate.

Traceback (most recent call last):
 File "flask\app.py", line 1950, in full_dispatch_request
 File "flask\app.py", line 1936, in dispatch_request
 File "flask_login\utils.py", line 269, in decorated_view
 File "cryptoadvance\specter\server_endpoints\devices.py", line 207, in new_device_mnemonic
 File "cryptoadvance\specter\util\mnemonic.py", line 42, in validate_mnemonic
 File "mnemonic\mnemonic.py", line 115, in detect_language
mnemonic.mnemonic.ConfigurationError: Language not detected


@aphex3k just to make sure, all the words you use are from the BIP39 list and the checksum is correct?
You could check this by entering it on a signing device for example. If you are just testing around you can double-check here as well:
 URL


`detect_language` only uses the first word, so it would be best idea to share just the first word to narrow down the investigation


first word in the mnemonic I tried is `about` but it looks like my seed is invalid anyways? I'm checking...


My bad, apparently the mnemonic I tried is not BIP39. This can be closed...


Hi @DeskDude47 and welcome to Bitwarden. This issue is something we have been researching into, to ensure we tackle the root cause. Efforts are still being made to ensure it's resolved. I will update this thread once an ETA is confirmed. Thank you for the patience!


@heiglandreas can you help me a bit? I've seen that note you have copied from URL

and got surprised because I thought it is not how strict types are working.

So I've tried to do it myself at URL and cannot make it work the way it is - at least with my understanding - described in the note. What am I doing wrong?


from version 0.0.16 and up featmake is now not a binary but a raw shell script, you can open it with any text editor


Thanks for bringing that up.

And I have no good explanation for that issue that you are scetching out. Perhaps that is something for the bugtracker of the php-src.

The reason why I brought up that citation though was because the `declare_strict` is only relevant within files that actually **call** other functions. As an interface does - by definition - only **defines** function-signatures and **never** calls other functions, a `declare(stict_types)` is always unnecessary in an interface-file.


Suggestion: use `schema_version` instead of version. Version has other meanings in the API, so it might be confusing.

I would like to keep versioning similar to URL which uses the following:


@filip-szweda Our api is still in alpha thus it might be a little unstable , thats the main reason we are trying to implement this one : URL


FYI the approach taken in #2080 is to version the API using the URL (e.g. `/api/v1`, `/api/v2`...) and incrementing the version when there is breaking changes, such as field removal.

This approach makes more sense in our particular context. It allows us to have multiple and concurrent versions of the API to give time to our users to migrate. This would not be possible with a `version` field because endoflife.date is just a static site.

We could also add a `version` (or `schema_version`) field in the response. Maybe it would be useful when an older version of the API is removed and old API URLs are redirected to the new API URLs ? What do you think @filip-szweda, @usta, @captn3m0 ?


It would also be helpful when we make minor schema changes (such as field additions).


[Triage] @peternied Could you please provide some context around the limitations of the securityadmin tool relying on TLS/SSL?


onion alternates are not working again, same reason as described in URL


Bonjour,
Nous venons de commencer le développement de cette fonctionnalité. Il s'agira donc de pouvoir choisir via des cases à cocher dans Prevarisc les pièces jointes du dossier à renvoyer, et une commande sur la passerelle permettra de faire l'action.
Nous estimons pouvoir mettre cela à disposition sur notre GitHub pour fin Mars, et nous reverserons cette évolution dans ce GitHub.
Je mentionnerais la Pull Request lorsque ce sera d'acutalité.

Cordialement,
Maxime Merrien


I really like your approach in URL 👍

One thing I'm a bit concerned about are changes to the API that do not add / remove fields like e.g. URL
Do you think such changes could also increment the API version, perhaps only its minor part (i.e. /api/v1.1, /api/v1.2, /api/v1.3)?


There is a functional concern that the security plugin depends on the admin certificate to authenticate a super admin user, without support for this there are many scenarios that are not possible. If the certificate was removed as a requirement for these APIs then this could be opened up.

Related issues
- URL
- URL
- URL


Since this issue is still happening in the latest version of AllTheMods 8 (1.0.9), further research into this was done and it was found that EvilCraft is indeed at fault here despite the previous fix. The previously deployed fix doesn't achieve anything regarding this issue as the crash doesn't happen directly in any of the code touched by the fix since that code did use the correct `RandomSource` from the `Level` given by the caller. The actual crash always happens in Minecraft code when the `LevelRenderer` tries to apply some particle amount randomisation because it tries to use the client level's random from the server thread where your code unintentionally calls it from.

The underlying issue causing this crash is that the spawning of the blood splash particles ( URL does not check for the logical client side, it only checks for the physical client side, both explicitely via the helper call (checks `FMLEnvironment.dist == Dist.CLIENT`, which is purely the physical side) and implicitely via the `@OnlyIn(Dist.CLIENT)` annotation. This leads to the particle spawning code being called from the server thread in singleplayer as is visible in both the stacktrace linked by the OP and this log snippet where the logging of the `LegacyRandomSource` was extended via Mixins for debugging purposes. The proper fix for this is to replace the helper call with a call to `Level#isClientSide()` in the method linked above, which would prevent the code from reaching across logical sides and crashing in the `LevelRenderer`'s random shenanigans.

It's also worth noting that the previous fix is potentially unsafe since it deploys a global and completely unguarded `SingleThreadedRandomSource`, which may produce weird results when accessed from multiple threads, which is the reason why the `LegacyRandomSource` crashes in these concurrent access scenarios.


After 4 days of using 7.3.0 in my Jenkins pipeline (pwsh -c), 7.3.0 is now seg faulting on this command!

image

WTF? @SteveL-MSFT Any suggestions on a potential workaround - other than uninstalling and installing a different version? That only seems to work for a few days. This is impacting our product devops because we use PowerShell to orchestrate build & test on Mac M1.


I removed 7.3.0 and installed 7.3.2 (that must be pretty new) and now `pwsh -c` works again. Let's see how long 7.3.2 can go before it starts seg faulting. :-)


Projects using our new Node.js Extensions project can now be published to NuGet without further work.


Good evening 👋🏼

I see this has been ongoing for some time, I also see that some of the issues affected by this are still ongoing.

Is there any update on when a rewrite of the frontend will complete?
An issue that was opened about date order was closed as the fix is a rewrite, but thats still in progress.


Babel 2022-12 is still not released (link above contains only 2021-12 version).
However we can see it in update sites: URL

The roblem is that we can't use update site, we need archived zip with all translations. I think we need to contct Babel team and ask to publich the release.


It'll be done when it is done. You can't plan volunteer time and motivation.


Thanks for the findings @XFactHD! Will have a look at this soon.


Hi,
Any input on this issue ? The removal of this feature avoid us from migrating to version 24.
Is it possible to keep the setPreventInvalidInput method or at least keep a possibility to use it at a lower level ?
Thanks,


Alright, I've looked into this again. Not sure where my head was at before, but I've reverted my previous changes, applied the suggested changes, and released a new version.
Thanks again @XFactHD for your input!


Unfortunately, not able to repro this. Was able to find two PRs in dotnet/runtime that is related to the area given the stacktrace (thanks!) URL Need to look deeper next week.


@A709197 Maxime, voici la branche de travail sur l'export de pièces dans la passerelle URL ça vous aidera à vous raccrocher à nous.

Si vous devez pousser une mise à jour sur Prevarisc (notamment au niveau de la gestion des cases à cocher), veuillez faire la PR dans le dépôt officiel URL depuis la branche 2.x pour simplifier la mise à niveau des SDIS.


With IR, I get the following exception:

AssertionError: Expected transaction to be reverted with ABC, but other
exception was thrown: ProviderError: Error: Transaction reverted: function
was called with incorrect parameters

from a function as simple as:

function f() public {
 revert("ABC");
}

When IR is not used, or other parts of the contracts are tinkered, or YUL steps are tinkered, the issue resolves. This issue is very similar to URL so I suspect it's a Hardhat issue.

I tried many combinations of recent Solidity versions with Hardhat `2.12.6` and `2.12.1-ir.0`. My compiler settings are:

viaIR: true,
optimizer: {
 enabled: true,
 runs: 200
}

Currently working around the issue with a custom order of YUL optimization steps.

Let me know if you think if this's a Solidity issue.


This's the stack trace from Hardhat `2.12.6`:

eth_estimateGas
 Error: Transaction reverted: function was called with incorrect parameters
 at Contract.f
 at processTicksAndRejections (node:internal/process/task_queues:96:5)
 at async EthModule._estimateGasAction (node_modules/hardhat/src/internal/hardhat-network/provider/modules/eth.ts:429:7)
 at async HardhatNetworkProvider._sendWithLogging (node_modules/hardhat/src/internal/hardhat-network/provider/provider.ts:139:22)
 at async HardhatNetworkProvider.request (node_modules/hardhat/src/internal/hardhat-network/provider/provider.ts:116:18)
 at async JsonRpcHandler._handleRequest (node_modules/hardhat/src/internal/hardhat-network/jsonrpc/handler.ts:188:20)
 at async JsonRpcHandler._handleSingleRequest (node_modules/hardhat/src/internal/hardhat-network/jsonrpc/handler.ts:167:17)
 at async Server.JsonRpcHandler.handleHttp (node_modules/hardhat/src/internal/hardhat-network/jsonrpc/handler.ts:52:21)


This issue has been inactive for a long time, so I will close it.
Please pay attention to #14061 for future updates.


Closing as release 2.0.0 supports import via Swift Package Manager.


As a temporary **local fix**, I went to the gem dir and compile myself, using `make`.

/home/fidalgo/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/ffi-1.15.5/lib/ffi/library.rb:145:in `block in ffi_lib': Could not open library '/home/fidalgo/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/cld3-3.5.0/lib/cld3/../../ext/cld3/libcld3.so': /home/fidalgo/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/cld3-3.5.0/lib/cld3/../../ext/cld3/libcld3.so: cannot open shared object file: No such file or directory (LoadError)

So I went to `/home/fidalgo/.rbenv/versions/3.2.0/lib/ruby/gems/3.2.0/gems/cld3-3.5.0/lib/cld3/../../ext/cld3/` and just run `make` and voila, app loads again.

NOTE: This is a local workaround only.


Thanks @esenmx for the issue report.

Yes I am aware of this issue. It is a bug in Flutter 3.7, basically a regression, a bug that does not exist in Flutter 3.3 nor in Flutter master channel, since there is fix for it already in master channel.

Unfortunately that fix did not make it into Flutter 3.7 stable as cherry pick for the release. It would have needed an extra cherry pick for the 3.7 stable release, since 3.7 release had already had its code freeze when the fix was made. Now we have to wait and hope a fix for this is included in the first Flutter 3.7 hotfix (3.7.1).

The ink bug is only visible if the `NavigationBar` height is different than the default M3 height of 80dp. If you make the height lower than 80dp, the ink effect moves the diff amount from 80dp below it, if you make the height higher than 80dp, the effect moves up with same amount that it is higher than 80dp. So there is some kind of offset error on the ink ripple.

FlexColorScheme defaults to an opinionated design that is only 62 dp heighh in both M2 and M3. As a workaround, if you set its height to 80dp

dart
 subThemesData: const FlexSubThemesData(
 navigationBarHeight: 80.0,
 ),

The issue becomes invisible.

I will when I release the FCS 7.0 stable version introduce a with FCS 6.x style break, that sets the default when opting in on M3 to 80dp instead of 62dp. Which as said is the default for M3 design anyway. At least then this issue is not visible by default when opting in on M3. It will still be there when using M2 though, since I don't want to break past default for FCS when using M2. I will leave the manual workaround to set it to 80dp to be the choice of the developer when using M2. Well let's see, it depends a bit on the timeline for the fix to land.

The PR that fixes this issue can be found here:
 URL

The author of the fix @TahaTesser and @Piinks are aware that this might be a big enough issue to be included in the first hotfix to Flutter 3.7.

I will keep this issue open until there is a fix for it Flutter. I will also add it to known issues in the docs.


When you change the height from 80dp, the M3 default, the ink ripple shifts with offset amount up/down equal to height change diff and direction. It affects both M2 and M3 mode. The issue did not exist in stable 3.3 but has now regressed into stable 3.7.

See example here: URL


The puzzling part in the report is that the crash doesn't happen consistently -- it started to happen after using 7.3.0 for 4 days.

The stack trace suggests the crash happened when JIT start profile kicks in, which does early compilation on the methods that were used the last time `pwsh` going through the same code path -- in this case for `pwsh -c` or `pwsh -file`, non-interactive execution (_ProfileOptimization.StartProfile("StartupProfileData-NonInteractive")_).

So, it makes sense that running `pwsh` itself works, because that will be interactive execution, which will be using a different profile: _ProfileOptimization.StartProfile("StartupProfileData-Interactive")_.

@rkeithhill-keysight Can you please try the following when `pwsh -c "get-date"` results in segment fault, and see if the next run of `pwsh -c` works:
- remove the `StartupProfileData-NonInteractive` file under `/home/ /.cache/powershell`

Having this file removed will make CLR not attempt to do the early method compilation, so if this theory is correct, the next run of `pwsh -c "get-date"` should work again. If you can verify this is the case, I will open an issue on this in the .NET repo.


@daxian-dbw Yes, I'll give that a try if/when we encounter the seg fault again.


# Detailed Update

It looks like the root cause of this issue is the output generated for `App.vue` before it is passed to `vite:import-glob` does not correctly quote the "class" attribute, causing it to be interpreted by Acorn incorrectly. Here is the relevant snippet from my output:

js
function _sfc_ssrRender(_ctx, _push, _parent, _attrs, $props, $setup, $data, $options) {
 _push(` ${
 _ssrInterpolate(new Date())
 } `)
}

I'm not sure where exactly in the Vite/Rollup pipeline this code is generated. Would someone from the team be willing to jump in here?


@esenmx for information the fix to this Flutter 3.7 bug has been cherry-picked here URL it will thus most likely be included in the first Flutter hotfix release 3.7.1.


The `strip-literal` library used internally by Vite appears to be using the `acorn.tokenizer` function.

Here is my minimal reproduction:

js
import { tokenizer } from "acorn";

[...tokenizer("` `", {
 ecmaVersion: "latest",
 sourceType: "module",
 allowHashBang: true,
 allowAwaitOutsideFunction: true,
 allowImportExportEverywhere: true
})]

Which gives me the following error:

file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:3454
 var err = new SyntaxError(message);
 ^

SyntaxError: Unterminated regular expression (1:28)
 at Parser.pp$4.raise (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:3454:13)
 at Parser.pp.readRegexp (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:5134:47)
 at Parser.pp.readToken_slash (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:4929:51)
 at Parser.pp.getTokenFromCode (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:5092:17)
 at Parser.pp.readToken (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:4809:15)
 at Parser.pp.nextToken (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:4800:15)
 at Parser.pp.next (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:4761:8)
 at Parser.pp.getToken (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:4765:8)
 at Object.next (file:///Users/aryse/Projects/open-source/acorn-test/node_modules/acorn/dist/acorn.mjs:4776:30)
 at file:///Users/aryse/Projects/open-source/acorn-test/index.mjs:3:5 {
 pos: 28,
 loc: Position { line: 1, column: 28 },
 raisedAt: 33
}


I get the same `Unterminated regular expression` message when I run your minimal reproduction. More minimal:

js
[...tokenizer("`${{ class: 5 }}></`", {
 ecmaVersion: "latest",
})]


Today I got an update from Engineering: They continued the work and made progress since my last message, but they still don't have a more precise timeline to communicate, very unfortunately


Imagine being a PM and getting this response from engineering ⛈😉


How much RAM does your platform have? Building the Python bindings can be rather RAM hungry - at least 6GB is recommended.


I approached this issue slightly differently. I created a wrapper component for each general type of input field (text, checkbox, select, etc.) that combined the following features:

- Renders components using the UI framework of my choice (react-bootstrap here)
- Incorporates react-hook-form by passing in the **register** and **FieldError** objects for this particular field.

That way, I can pull whatever I need out of the RHF objects, and adapt to improvements in later versions without having to change my component's API.

Full source for a TextField component for this (I made a reusable library for this kind of thing):

 URL

Example of the use of this component in a form:


Thanks for the feature request, unfortunately, this is currently out of scope within this library. If you are using MUI, this library may just be your friend: URL


I think this is a fine implementation strategy, but it should really be an implementation detail IMO -- something Bazel does transparently behind the scenes.

I think the real goal for user experience should be a configured max size for the disk cache, just like ccache and other tools provide that users set and "forget".


Hi Zachary @zkingston , appreciate your timely reply. Our target platform is Nvidia Jetson AGX Orin Developer Kit, the memory is 32 GB 256-bit LPDDR5.


Thx for your reply.
As for the RAM, I think that's quite enough as shown below,
image


When ran without the parser, the tokenizer _will_ fail to distinguish regexps from division operators in some cases (because JavaScript cannot be tokenized without parsing). This is a known limitation, and not something that's fixable.


Sadly it did not make it to 3.7.1, maybe 3.7.2 then. Yes I know, quite disappointing, but I have no control over what lands when in the framework :smile:


Sadly it did not make it into 3.7.1, nor a bunch of other important M3 fixes that exist in master, oh well, later then... 😄


The Acorn author said the cause of this issue is "not fixable" on his end. That leaves us with a scenario where dynamic import cannot be used more than once (and maybe potentially other issues) if the root element of a component has a `class` attribute. I think this should be resolved by having Vue add quotes around the property name.


An analysis was made of the changes that are required on the wazuh-puppet repository in order to deploy a distributed environment:
Modify the use of the template for the config.yml. The config.yml file that is currently used is a fixed template that only contains this data:

 yaml
# config.yml
nodes:
 indexer:
 -name: indexer
 ip: 127.0.0.1
 server:
 - name: server
 ip: 127.0.0.1
 dashboard:
 - name: dashboard
 ip: 127.0.0.1

It is necessary to modify the wazuh::certificates class so that when creating the certificates it creates a config.yml file according to the environment that is going to be deployed.

Modify the movement of the `.pem` and `key.pem` keys of each node. These files are created on the same server where Wazuh indexer is going to be deployed, so when moving these files it only moves them to the corresponding directories. This process is generated with hard coded data, since just as the config.yml file is fixed, so are the names of the keys and that is why it performs a move of the exact files, without taking into account variables and so on.

In itself, the dynamics of the current AIO and the distributed environment are very different, since each current class of each product is almost independent, so at the time of installation they do not require previous steps as if the distributed environment requires and it is extremely necessary that the certificates of each domain are generated in one location and then moved, or at least a unique root-ca is generated. Then each node creates its certificates with this root-ca in common, which is currently not contemplated and is done in a very simple way on a single server.


@unrealiceyou both are rather uncommon in the wider spread of kits (or so I believe), so I'm not super concerned. I can probably just preface the text file containing the NBT with a note about the Infinity/NaN when needed, including how to properly import it.


oops, I also met the exactly same issue ! It f**ked me for nearly a month.
Quite strange, that Cannot build on ubuntu Arm platform.
@zkingston , could you help to check it ?
Thanks


^^ per a discussion on our slack, the package should be `apparmor`, not `apparmor-utils` (updated my comment above)


I opened URL to fix the `get.docker.com` installation script as well


Thanks for the detailed explanation! v1.0.1 should improve the regex to hand the cases. JS is complex 🤷


@heinrich-ulbricht I'm just the messenger who understands the frustration of people in this thread who are waiting for this fix for so long.
I take the time to chase Engineering and provide whatever update I have, even if it is a poor one.
I could have chosen to just remain silent


There are cases where it's not that simple.
eg

- using a Debian based host
- running a lxc container inside which is used as a gitlab-runner executor: here you can workaround by installing apparmor userland
- But then , if in your CI, you use DIND workflows, you wont be able to spawn the dind container as it will check on the same error.

rel #44902


Can confirm that. Today docker-ce 23.0.0 got pushed to centos repos.
We run dockerd in a centos lxd container on an ubuntu lxd host.
There is no way to install apparmor/-utils in this scenario.


I would like to emphasis that this bug is a bit critical as docker can be upgraded during an unattended upgrade and then break the workload running on the related host.


Hi @fr-Pursuit ,

Could you please recheck your problem with `{{ index .Labels \"podName\" }}.my-interdomain-vl3-network.`(added dot at the end)?


2023 now, and the flicker of hope for this feature is still alive!
See URL


Here a few pull requests or issues, where i need only file extensions (.js) so I could use them in browser:

 URL
 URL

I don't know why an extra option wich I created in my pull request could not be added...


I know use a js script to add the extension afterwards, see the pull I creaed here on how to do: URL


Can you please post the full output of trying to compile the docker image on your platform? #958 also had issues compiling on ARM.


A new manifest was created where the wazuh::indexer class is declared, which mainly removes many hardcoded options and allows using variables for indexer deployment with more than one node, such as the list of nodes to install.

A new template of the config,yml file was created, to be able to assign variables with the names and IPs of all the nodes for which a certificate is going to be generated. The previous template was too basic and was hardcoded with the names and IPs that belonged to localhost, the new template contemplates different variables assignable by the deployment manifest:

 yaml
nodes:
 indexer:
 - name: indexer-
 ip:
 - name: indexer-
 ip:
 - name: indexer-
 ip:
 server:
 -name: manager-master
 ip:
 node_type: master
 -name: manager-worker
 ip:
 node_type: worker
 dashboard:
 - name: dashboard
 ip:

A new opensearch.yml template was created since the previous one had the names of all the node certificates hardcoded, so it is necessary to change these values.

The section where the securityadmin was executed, which only has to be run on the main node of the cluster, was removed from within the indexer manifest, and a new class was created to perform this action later.

We worked on a new deployment script, it is not finished but its objective is to be able to assign the necessary variables for the deployment beforehand, such as the names of the nodes and their IPs:

 ruby
$node1-ip =
$node2-ip =
$node3-ip =
$master-ip =
$worker-ip =
$dashboard-ip =
$indexer_node1_name = 'node1'
$indexer_node2_name = 'node2'
$indexer_node3_name = 'node3'

class['wazuh::certificates-dist']

node "node1" {
 if $facts['os']['family'] == 'Debian' {
 Class['wazuh::repo'] -> Class['apt::update'] -> Package['wazuh-indexer']
 } else {
 Class['wazuh::repo'] -> Package['wazuh-indexer']
 }
 class { 'wazuh::indexer-dist':
 indexer_node_name => "$indexer_node1_name",
 indexer_network_host => "$node1-ip",
 }
}
node "node2" {
 if $facts['os']['family'] == 'Debian' {
 Class['wazuh::repo'] -> Class['apt::update'] -> Package['wazuh-indexer']
 } else {
 Class['wazuh::repo'] -> Package['wazuh-indexer']
 }
 class { 'wazuh::indexer-dist':
 indexer_node_name => "$indexer_node2_name",
 indexer_network_host => "$node2-ip",
 }
}
node "node3" {
 if $facts['os']['family'] == 'Debian' {
 Class['wazuh::repo'] -> Class['apt::update'] -> Package['wazuh-indexer']
 } else {
 Class['wazuh::repo'] -> Package['wazuh-indexer']
 }
 class { 'wazuh::indexer-dist':
 indexer_node_name => "$indexer_node3_name",
 indexer_network_host => "$node3-ip",
 }
}

Tests must be done and verification of running securityadmin at the end of the installation and subsequent transfer of the previously created certificates.


Here is the output of building the docker container,

log.out.txt


The error appears to be with CastXML on ARM, a number of these errors appear, indicating that it failed to generate output, and thus the rest of the Python binding pipeline failed:

In file included from /tmp/tmpapu0i3zy.h:1:
In file included from ./bindings/base.h:1145:
In file included from /usr/include/eigen3/Eigen/Core:214:
/usr/include/eigen3/Eigen/src/Core/arch/NEON/PacketMath.h:3096:10: error: use of undeclared identifier 'vrndn_f32'
{ return vrndn_f32(a); }

I'm surprised this error occurred with the latest CastXML - it appears to have been fixed in the past: URL
Can you verify that if you install the latest CastXML in Docker if things work?


@zkingston I've just verified castxml 0.5.0 from the official URL (the "castxml_v0.5.0-linux-aarch64.tar.gz"),

and updated the Dockerfile (only comment out the castxml and use COPY command),
ompl.Dockerfile.txt

After all, the output shows like,
log0206.out.txt


I would recommend looking into the `publish:github:pull-request` action instead, which would allow you create pull requests for each entity definition.

If you go to your backstage instance, `/create/actions` you should be able to see the options that you can pass into the action in the template definition.


This is also here: URL

I'm not sure why this isn't being fixed. Validating that arrays are defined seems like a pretty basic validation rule.


I believe this is now an issue with pygccxml ( URL - please make sure the most recent version is installed in the docker as well. Also take a look at the discussion in URL - the same error message appears there.


Eh... consider me one of those people whose workflow was broken without notification. I thought you might be able to prevent breakage by adding a branch alias, but it seems like that's not possible: URL


Hi!

This can be done in a couple different ways. For data in a version control system, ultimately the end result has to either be a push, or a pull request. That involves making requests using the relevant client library, eg octokit for the case of github. We have the helpers to get the auth set up for that so that it happens on behalf of the actual user performing the action, so that's good. You could make a web interface either for targeted actions as you mention, or in the form of a full YAML editor that helps you do validation and get the indentation right and all of that jazz.

Separate to this, there's an entire track to explore of having direct editor support, as in, building vscode / intellij plugins and thinking about leveraging schemas and/or querying the catalog for automatic validation as you type, and stuff like that.

Ping @taras here for info - these are topics that may be of interest to him, and to the Adoption SIG work that's underway.


@danepowell Out of curiosity: why were you using the `master` branch instead of a tagged release ?


Hi,

With the added dot at the end of the template, the DNS resolution partially works.
if I have a pod named `yelb-ui` connected to the vL3 network `nslookup yelb-ui.my-interdomain-vl3-network` fails after initially returning the expected IP:

# nslookup yelb-ui.my-interdomain-vl3-network. && echo success
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: yelb-ui.my-interdomain-vl3-network
Address: 172.16.0.3
** server can't find yelb-ui.my-interdomain-vl3-network: SERVFAIL

The same error also appears in the logs of the vL3 NSE that is in the same cluster as the `yelb-ui` pod:

Feb 6 23:18:25.908 [TRAC] [id:29292] [type:dnsServer] (1) ⎆ sdk/pkg/tools/dnsutils/dnsconfigs/dnsConfigsHandler.ServeDNS()
Feb 6 23:18:25.908 [TRAC] [id:29292] [type:dnsServer] (1.1) message-request={"Id":29292,"Response":false,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":true,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":0,"Question":[{"Name":"yelb-ui.my-interdomain-vl3-network.my-interdomain-vl3-network.","Qtype":28,"Qclass":1}],"Answer":null,"Ns":null,"Extra":null}
Feb 6 23:18:25.908 [DEBU] [id:29292] [type:dnsServer] (1.2) passed clientURLs: [{udp 172.16.1.1 false }]
Feb 6 23:18:25.908 [DEBU] [id:29292] [type:dnsServer] (1.3) passed SearchDomains: []
Feb 6 23:18:25.908 [TRAC] [id:29292] [type:dnsServer] (2) ⎆ sdk/pkg/tools/dnsutils/noloop/noloopDNSHandler.ServeDNS()
Feb 6 23:18:25.908 [TRAC] [id:29292] [type:dnsServer] (3) ⎆ sdk/pkg/tools/dnsutils/norecursion/norecursionDNSHandler.ServeDNS()
Feb 6 23:18:25.908 [TRAC] [id:29292] [type:dnsServer] (3.1) message-request-diff=[{"type":"update","path":["MsgHdr","RecursionDesired"],"from":true,"to":false}]
Feb 6 23:18:25.908 [TRAC] [id:29292] [type:dnsServer] (4) ⎆ sdk/pkg/tools/dnsutils/memory/memoryHandler.ServeDNS()
Feb 6 23:18:25.908 [TRAC] [id:29292] [type:dnsServer] (5) ⎆ sdk/pkg/tools/dnsutils/fanout/fanoutHandler.ServeDNS()
Feb 6 23:18:25.911 [TRAC] [id:29292] [type:dnsServer] (1) ⎆ sdk/pkg/tools/dnsutils/dnsconfigs/dnsConfigsHandler.ServeDNS()
Feb 6 23:18:25.911 [TRAC] [id:29292] [type:dnsServer] (1.1) message-request={"Id":29292,"Response":false,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":0,"Question":[{"Name":"yelb-ui.my-interdomain-vl3-network.my-interdomain-vl3-network.","Qtype":28,"Qclass":1}],"Answer":null,"Ns":null,"Extra":null}
Feb 6 23:18:25.911 [DEBU] [id:29292] [type:dnsServer] (1.2) passed clientURLs: [{udp 172.16.1.1 false }]
Feb 6 23:18:25.911 [DEBU] [id:29292] [type:dnsServer] (1.3) passed SearchDomains: []
Feb 6 23:18:25.911 [TRAC] [id:29292] [type:dnsServer] (2) ⎆ sdk/pkg/tools/dnsutils/noloop/noloopDNSHandler.ServeDNS()
Feb 6 23:18:25.911 [ERRO] [id:29292] [noloopDNSHandler:ServeDNS] [type:dnsServer] (2.1) loop is not allowed: query: ;; opcode: QUERY, status: NOERROR, id: 29292; ;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0; ; ;; QUESTION SECTION:; ;yelb-ui.my-interdomain-vl3-network.my-interdomain-vl3-network. IN AAAA; ;
Feb 6 23:18:25.911 [TRAC] [id:29292] [type:dnsServer] (2.2) message-response={"Id":29292,"Response":true,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":2,"Question":[{"Name":"yelb-ui.my-interdomain-vl3-network.my-interdomain-vl3-network.","Qtype":28,"Qclass":1}],"Answer":[],"Ns":[],"Extra":[]}
Feb 6 23:18:25.913 [TRAC] [id:29292] [type:dnsServer] (5.1) message-response={"Id":29292,"Response":true,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":2,"Question":[{"Name":"yelb-ui.my-interdomain-vl3-network.my-interdomain-vl3-network.","Qtype":28,"Qclass":1}],"Answer":[],"Ns":[],"Extra":[]}

In practice, this error seems to considerably increase the time it takes for a program to perform a DNS resolution in the `my-interdomain-vl3-network` zone. For example, every time I use the `ping yelb-ui.my-interdomain-vl3-network` command, I have to wait a significant while before the actual pings get exchanged (whereas if I use the IP, the pings are exchanged almost immediately).

PS: I changed the template to use a custom `domain` label instead of the default `podName` label to generate the domain name


@danepowell Interesting. That bug was never reported by anyone, but clearly people (you) did run into it. Thanks for letting me know.

The good news is, of course, that the bug fix is included in the 1.0.0 release, so you should be able to switch back to versioned updates now.


FYI, this was discussed in today's maintainer call and a revert to the apparmor startup logic is being fast-tracked for a 23.0.1 release: URL


HI, just followed the issue these days and tried your tips , but all failed! All failed.
We had absolutely 100% sure that we use the latset pygccxml(it's 2.2.1) and the latest commit of the pygccxml is May.25.2021
And
#725 is the same issue , but no one can solve it!!!!


@zkingston I am sure that the latest pygccxml is installed in the docker.
Also, I tried the solutions mentioned in #725 , but unfortunately they doesn't work.


iOS recorded video of the front camera is not mirrored as the default camera app in the iphone. This results to incorrect video output and very difficult to correct with postprocessing libraries of the video. This should be just a flag set in the SWIFT code. Can anybody help. I am able to test


Some updated:
pip3 list
Package Version
---------- -------
numpy 1.17.4
pip 20.0.2
pygccxml 2.2.1
pyplusplus 1.8.5

 $castxml --version
castxml version 0.5.0

CastXML project maintained and supported by Kitware (kitware.com).

clang version 13.0.0
Target: aarch64-unknown-linux-gnu
Thread model: posix


Thank you for the answer, but the main idea here is not to leave backstage UI during updates. Do not interact with other services like github to merge PR


Hey 👋🏼

A project I work on has also just been caught out by this change

One of the packages we use pushed a fix yesterday changing from `dev-master` to `dev-main` but they've not yet been able to tag and publish a new release yet...
- URL

Whilst we work to resolve these issues on our project, we'll create upstream updates for the packages we use and hoping they're maintained and can push new releases soon as this will be tricky for packages that are not so well maintained

A quick GitHub search shows 14 of the first 50 search results (3481 total results) use `dev-master`

Unsure of a workable solution, though a solution from Composer would be ideal, I've subscribed to URL and will be interested in replies there...


Thank you for the answer.
I understand, that I can do it on my own, but I want it to be a part of backstage and available out of the box.

Also, if backstage will support some database as a source of truth backend (not git), it will be very helpful for decoupling from code, easy migrations, and consistency checks.
E.g.: specify postgres as the source backend for storing entities. Add action in templates for entity creation. Implement CRUD API and interfaces for entity management directly in the backstage app. Implement entity provider to sync with the core database.

Disclaimer: I still understand, that all this is possible to do on my own, but I won't be able to support it on my own :)


about

It is nice to have this, but still, this requires some third-party tool to work with backstage. And my point is that backstage should be self-sufficient and user friendly


My point about this is described in a bit more detail at: URL


Actually, the slow `ping` initialization seems to be caused by slow, failing reverse DNS queries: the command temporarily freezes _after_ the IP associated with the domain is shown, but _before_ the first response appears.

In the meantime, the following appears in the remote NSE's logs:

Feb 7 12:06:14.957 [TRAC] [id:26676] [type:dnsServer] (1) ⎆ sdk/pkg/tools/dnsutils/dnsconfigs/dnsConfigsHandler.ServeDNS()
Feb 7 12:06:14.957 [TRAC] [id:26676] [type:dnsServer] (1.1) message-request={"Id":26676,"Response":false,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":0,"Question":[{"Name":"3.0.16.172.in-addr.arpa.","Qtype":12,"Qclass":1}],"Answer":null,"Ns":null,"Extra":null}
Feb 7 12:06:14.958 [DEBU] [id:26676] [type:dnsServer] (1.2) passed clientURLs: [{udp 172.16.0.1 false }]
Feb 7 12:06:14.958 [DEBU] [id:26676] [type:dnsServer] (1.3) passed SearchDomains: []
Feb 7 12:06:14.958 [TRAC] [id:26676] [type:dnsServer] (2) ⎆ sdk/pkg/tools/dnsutils/noloop/noloopDNSHandler.ServeDNS()
Feb 7 12:06:14.958 [ERRO] [id:26676] [noloopDNSHandler:ServeDNS] [type:dnsServer] (2.1) loop is not allowed: query: ;; opcode: QUERY, status: NOERROR, id: 26676; ;; flags:; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0; ; ;; QUESTION SECTION:; ;3.0.16.172.in-addr.arpa. IN PTR; ;
Feb 7 12:06:14.958 [TRAC] [id:26676] [type:dnsServer] (2.2) message-response={"Id":26676,"Response":true,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":2,"Question":[{"Name":"3.0.16.172.in-addr.arpa.","Qtype":12,"Qclass":1}],"Answer":[],"Ns":[],"Extra":[]}
Feb 7 12:06:15.011 [TRAC] [id:26676] [type:dnsServer] (5.1) message-response={"Id":26676,"Response":true,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":2,"Question":[{"Name":"3.0.16.172.in-addr.arpa.","Qtype":12,"Qclass":1}],"Answer":[],"Ns":[],"Extra":[]}

The same error appears several times in the logs, as the server seems to handle one PTR request per entry in the pod's DNS search path.

I've also noticed major slowdowns in the yelb app, but these don't seem to be caused by NSM: in order for the app to work regardless of how it is deployed, I added the `my-interdomain-vl3-network` domain in the pod's DNS search path. But since it was added at the end of the search path, the pod has to wait for several failing DNS queries to finish before sending the right query.


@fr-Pursuit
`nslookup` makes both ipv4 and ipv6 requests by default.

So, we can check:
`nslookup -debug yelb-ui.my-interdomain-vl3-network.`
or
`nslookup -type=a -debug yelb-ui.my-interdomain-vl3-network.`

For ping, force ipv4:
`ping yelb-ui.my-interdomain-vl3-network. -4`


@glazychev-art Indeed! The `nslookup` failure came from an AAAA request. Here's the output of the command you sent:

# nslookup -debug yelb-ui.my-interdomain-vl3-network.
Server: 127.0.0.1
Address: 127.0.0.1#53

------------
 QUESTIONS:
 yelb-ui.my-interdomain-vl3-network, type = A, class = IN
 ANSWERS:
 -> yelb-ui.my-interdomain-vl3-network
 internet address = 172.16.0.3
 ttl = 283
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
Name: yelb-ui.my-interdomain-vl3-network
Address: 172.16.0.3
------------
 QUESTIONS:
 yelb-ui.my-interdomain-vl3-network, type = AAAA, class = IN
 ANSWERS:
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
** server can't find yelb-ui.my-interdomain-vl3-network: SERVFAIL

I already tried to force IPv4 on ping though, which didn't change anything. I don't find this surprising though, since from what I saw the freeze came from reverse DNS queries.


I didn't see how `nslookup` could directly tell how long each request took, but using the `time` command, I got this:

root@yelb-appserver-55688766-pm8rf:/# time nslookup -debug yelb-ui.my-interdomain-vl3-network.
Server: 127.0.0.1
Address: 127.0.0.1#53

------------
 QUESTIONS:
 yelb-ui.my-interdomain-vl3-network, type = A, class = IN
 ANSWERS:
 -> yelb-ui.my-interdomain-vl3-network
 internet address = 172.16.0.3
 ttl = 3511
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
Name: yelb-ui.my-interdomain-vl3-network
Address: 172.16.0.3
------------
 QUESTIONS:
 yelb-ui.my-interdomain-vl3-network, type = AAAA, class = IN
 ANSWERS:
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
** server can't find yelb-ui.my-interdomain-vl3-network: SERVFAIL

real 0m0.905s
user 0m0.014s
sys 0m0.000s

Each request took more or less the same time, so I'd say around 400/500ms per request.

As for the `PTR` requests, they come from the `ping` problem itself. From what I can see, `ping` performs a reverse DNS query when you use it with a domain name instead of an IP:

% ping -4 google.com -c 4
PING (216.58.213.78) 56(84) bytes of data.
64 bytes from lhr25s01-in-f14.1e100.net (216.58.213.78): icmp_seq=1 ttl=110 time=4.92 ms
64 bytes from lhr25s01-in-f14.1e100.net (216.58.213.78): icmp_seq=2 ttl=110 time=4.91 ms
64 bytes from par21s18-in-f14.1e100.net (216.58.213.78): icmp_seq=3 ttl=110 time=4.98 ms
64 bytes from lhr25s01-in-f78.1e100.net (216.58.213.78): icmp_seq=4 ttl=110 time=5.00 ms

--- ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 4.909/4.950/5.000/0.038 ms

% ping -4 216.58.213.78 -c 4
PING 216.58.213.78 (216.58.213.78) 56(84) bytes of data.
64 bytes from 216.58.213.78: icmp_seq=1 ttl=110 time=4.86 ms
64 bytes from 216.58.213.78: icmp_seq=2 ttl=110 time=4.87 ms
64 bytes from 216.58.213.78: icmp_seq=3 ttl=110 time=4.96 ms
64 bytes from 216.58.213.78: icmp_seq=4 ttl=110 time=4.92 ms

--- 216.58.213.78 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 4.857/4.902/4.963/0.041 ms


Could you check please `time nslookup -debug -type=a yelb-ui.my-interdomain-vl3-network.` ?

Got it, thanks. Apparently we also need to process PTR requests.


Here's what I get when I only query `A` records:

# time nslookup -debug -type=a yelb-ui.my-interdomain-vl3-network.
Server: 127.0.0.1
Address: 127.0.0.1#53

------------
 QUESTIONS:
 yelb-ui.my-interdomain-vl3-network, type = A, class = IN
 ANSWERS:
 -> yelb-ui.my-interdomain-vl3-network
 internet address = 172.16.0.3
 ttl = 2402
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
Name: yelb-ui.my-interdomain-vl3-network
Address: 172.16.0.3

real 0m0.380s
user 0m0.008s
sys 0m0.008s


Well relying on named branches is fairly dangerous, as you can have major changes happening at any time. That's why we introduced the concept of branch aliases, so dev-main can be aliased to 1.x-dev in the dealerdirect/phpcodesniffer-composer-installer case for example, then you can require it as `1.x-dev` or even better `^1.1@dev` for example right now if you need unreleased new features (1.0.0 being latest stable), so that tells composer I need the 1.1 release of that package, but also I'll take a dev version if needed. `1.x-dev` (seen as `1.9999999.9999999` internally) matches `^1.1` so it'll install dev-main right now, but once 1.1.0 is tagged it would go back to stable tags if you have `prefer-stable:true`, or if a package using yours as dependency does not allow dev packages for example.

Requiring dev-main directly breaks all of this, so it is not a good idea.

If consumers require packages correctly, and the publisher had an alias for dev-master previously, then renaming should be pain-free as dev-main would get the same numeric alias as dev-master had, and everything keeps working.

I realize this may not help you solve anything right now because once it's done it's too late, but hopefully this clarifies things and you and others can learn from this.


This is the same issue as reported in #981, please keep discussion there.


I do not have an ARM platform to test on to replicate this, could you insert `traceback.print_exc()` at the bottom of `generate_bindings.py` to see where exactly the error is occuring?


You can also just copy the already-compiled file from the gem's lib/ directory. We ran into this on the `threatstack-agent-ruby` gem, which we can't fork and fix -.-


It has been **4 years** waiting for this feature. We don't even have an estimate on when this will be addressed.


The `addImportFromExportedSymbol` from grapesjs and nocodb is likely the same, and filed at #52662.


The echarts issue with `getMemberOverrideModifierStatus` and `getTextOfPropertyName` is filed at #52664.


@fr-Pursuit
In fact, the cache should work. Here are the logs, where we see that the response from the first request was cached, and the second one simply takes the result from this cache (dnsCacheHandler):

Feb 8 05:54:55.385 [TRAC] [id:40104] [type:dnsServer] (1) ⎆ sdk/pkg/tools/dnsutils/checkmsg/checkMsgHandler.ServeDNS()
Feb 8 05:54:55.385 [TRAC] [id:40104] [type:dnsServer] (1.1) message-request={"Id":40104,"Response":false,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":true,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":true,"CheckingDisabled":false,"Rcode":0,"Question":[{"Name":"alpine.my-interdomain-vl3-network.my.cluster3.","Qtype":1,"Qclass":1}],"Answer":null,"Ns":null,"Extra":null}
Feb 8 05:54:55.385 [TRAC] [id:40104] [type:dnsServer] (2) ⎆ sdk/pkg/tools/dnsutils/dnsconfigs/dnsConfigsHandler.ServeDNS()
Feb 8 05:54:55.385 [DEBU] [id:40104] [type:dnsServer] (2.1) passed clientURLs: [{udp 172.16.1.1 false } {udp 10.96.0.10 false }]
Feb 8 05:54:55.385 [DEBU] [id:40104] [type:dnsServer] (2.2) passed SearchDomains: [ns-floating-vl3-basic.svc.cluster.local svc.cluster.local cluster.local]
Feb 8 05:54:55.385 [TRAC] [id:40104] [type:dnsServer] (3) ⎆ sdk/pkg/tools/dnsutils/searches/searchDomainsHandler.ServeDNS()
Feb 8 05:54:55.385 [TRAC] [id:40104] [type:dnsServer] (4) ⎆ sdk/pkg/tools/dnsutils/noloop/noloopDNSHandler.ServeDNS()
Feb 8 05:54:55.385 [TRAC] [id:40104] [type:dnsServer] (5) ⎆ sdk/pkg/tools/dnsutils/cache/dnsCacheHandler.ServeDNS()
Feb 8 05:54:55.385 [TRAC] [id:40104] [type:dnsServer] (6) ⎆ sdk/pkg/tools/dnsutils/fanout/fanoutHandler.ServeDNS()
Feb 8 05:54:55.386 [TRAC] [id:40104] [type:dnsServer] (6.1) message-response={"Id":40104,"Response":true,"Opcode":0,"Authoritative":true,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":0,"Question":[{"Name":"alpine.my-interdomain-vl3-network.my.cluster3.","Qtype":1,"Qclass":1}],"Answer":[{"Hdr":{"Name":"alpine.my-interdomain-vl3-network.my.cluster3.","Rrtype":1,"Class":1,"Ttl":3600,"Rdlength":4},"A":"172.16.1.2"}],"Ns":[],"Extra":[]}

Feb 8 05:54:59.368 [TRAC] [id:23717] [type:dnsServer] (1) ⎆ sdk/pkg/tools/dnsutils/checkmsg/checkMsgHandler.ServeDNS()
Feb 8 05:54:59.368 [TRAC] [id:23717] [type:dnsServer] (1.1) message-request={"Id":23717,"Response":false,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":true,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":true,"CheckingDisabled":false,"Rcode":0,"Question":[{"Name":"alpine.my-interdomain-vl3-network.my.cluster3.","Qtype":1,"Qclass":1}],"Answer":null,"Ns":null,"Extra":null}
Feb 8 05:54:59.368 [TRAC] [id:23717] [type:dnsServer] (2) ⎆ sdk/pkg/tools/dnsutils/dnsconfigs/dnsConfigsHandler.ServeDNS()
Feb 8 05:54:59.368 [DEBU] [id:23717] [type:dnsServer] (2.1) passed clientURLs: [{udp 172.16.1.1 false } {udp 10.96.0.10 false }]
Feb 8 05:54:59.368 [DEBU] [id:23717] [type:dnsServer] (2.2) passed SearchDomains: [ns-floating-vl3-basic.svc.cluster.local svc.cluster.local cluster.local]
Feb 8 05:54:59.369 [TRAC] [id:23717] [type:dnsServer] (3) ⎆ sdk/pkg/tools/dnsutils/searches/searchDomainsHandler.ServeDNS()
Feb 8 05:54:59.369 [TRAC] [id:23717] [type:dnsServer] (4) ⎆ sdk/pkg/tools/dnsutils/noloop/noloopDNSHandler.ServeDNS()
Feb 8 05:54:59.369 [TRAC] [id:23717] [type:dnsServer] (5) ⎆ sdk/pkg/tools/dnsutils/cache/dnsCacheHandler.ServeDNS()
Feb 8 05:54:59.369 [TRAC] [id:23717] [type:dnsServer] (5.1) message-response={"Id":23717,"Response":true,"Opcode":0,"Authoritative":true,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":0,"Question":[{"Name":"alpine.my-interdomain-vl3-network.my.cluster3.","Qtype":1,"Qclass":1}],"Answer":[{"Hdr":{"Name":"alpine.my-interdomain-vl3-network.my.cluster3.","Rrtype":1,"Class":1,"Ttl":3597,"Rdlength":4},"A":"172.16.1.2"}],"Ns":[],"Extra":[]}

Could you also check the latest main branch of deployments-k8s? We slightly increased the query speed, at least `nslookup type=a` should work faster.


Trochu nás překvapilo, že nastavení sloupců stromu, které mají být vidět, funguje jen v Hledat, ale u stromu v panelu ne. Nedalo by se to přebírat i sem? Nebo to bude potřeba řešit jako extra nastavení?


The point of aliasing is to become compatible with numeric constraints. You don't really need an alias for named constraints because named constraints only ever match one exact name.

I can definitely see how it would lead to confusion though if you take it as a plain aliasing feature to alias anything. But I'd rather not add this at this stage. Improving docs definitely would be good I agree.


Weirdly, I get similar logs in the `cmd-nsc` container, but logs from the NSE indicate it stills handles the requests, even though they should be cache in the local `cmd-nsc` container.

I ran `dig yelb-appserver.my-interdomain-vl3-network` on the `yelb-appserver` container (so only the local NSE should get involved).

I'll retry with the latest main branch (I'm currently using v1.7.0), and I'll get back to you.


Great! With the latest branch, the DNS resolutions are quite faster:

# time nslookup -debug -type=a yelb-ui.my-interdomain-vl3-network.
Server: 127.0.0.1
Address: 127.0.0.1#53

------------
 QUESTIONS:
 yelb-ui.my-interdomain-vl3-network, type = A, class = IN
 ANSWERS:
 -> yelb-ui.my-interdomain-vl3-network
 internet address = 172.16.1.4
 ttl = 3408
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
Name: yelb-ui.my-interdomain-vl3-network
Address: 172.16.1.4

real 0m0.021s
user 0m0.009s
sys 0m0.009s

However, I have another issue... I deployed `yelb` using the same manifest as before, and for some reason `yelb-db.my-interdomain-vl3-network` cannot be resolved. The `yelb-db` pod was successfully connected to the vL3 network (with the address `172.16.0.2`), but the NSE fails when I try to resolve its associated name:

# nslookup -debug -type=a yelb-db.my-interdomain-vl3-network.
Server: 127.0.0.1
Address: 127.0.0.1#53

------------
 QUESTIONS:
 yelb-db.my-interdomain-vl3-network, type = A, class = IN
 ANSWERS:
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
** server can't find yelb-db.my-interdomain-vl3-network: SERVFAIL

The following error appears in the NSE's logs:

Feb 8 12:03:31.680 [TRAC] [id:40970] [type:dnsServer] (1) ⎆ sdk/pkg/tools/dnsutils/dnsconfigs/dnsConfigsHandler.ServeDNS()
Feb 8 12:03:31.681 [TRAC] [id:40970] [type:dnsServer] (1.1) message-request={"Id":40970,"Response":false,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":true,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":0,"Question":[{"Name":"yelb-db.my-interdomain-vl3-network.","Qtype":1,"Qclass":1}],"Answer":null,"Ns":null,"Extra":null}
Feb 8 12:03:31.681 [DEBU] [id:40970] [type:dnsServer] (1.2) passed clientURLs: []
Feb 8 12:03:31.681 [DEBU] [id:40970] [type:dnsServer] (1.3) passed SearchDomains: []
Feb 8 12:03:31.681 [TRAC] [id:40970] [type:dnsServer] (2) ⎆ sdk/pkg/tools/dnsutils/noloop/noloopDNSHandler.ServeDNS()
Feb 8 12:03:31.681 [TRAC] [id:40970] [type:dnsServer] (3) ⎆ sdk/pkg/tools/dnsutils/norecursion/norecursionDNSHandler.ServeDNS()
Feb 8 12:03:31.682 [TRAC] [id:40970] [type:dnsServer] (3.1) message-request-diff=[{"type":"update","path":["MsgHdr","RecursionDesired"],"from":true,"to":false}]
Feb 8 12:03:31.682 [TRAC] [id:40970] [type:dnsServer] (4) ⎆ sdk/pkg/tools/dnsutils/memory/memoryHandler.ServeDNS()
Feb 8 12:03:31.682 [TRAC] [id:40970] [type:dnsServer] (5) ⎆ sdk/pkg/tools/dnsutils/fanout/fanoutHandler.ServeDNS()
Feb 8 12:03:31.682 [ERRO] [id:40970] [fanoutHandler:ServeDNS] [type:dnsServer] (5.1) no urls to fanout
Feb 8 12:03:31.682 [TRAC] [id:40970] [type:dnsServer] (5.2) message-response={"Id":40970,"Response":true,"Opcode":0,"Authoritative":false,"Truncated":false,"RecursionDesired":false,"RecursionAvailable":false,"Zero":false,"AuthenticatedData":false,"CheckingDisabled":false,"Rcode":2,"Question":[{"Name":"yelb-db.my-interdomain-vl3-network.","Qtype":1,"Qclass":1}],"Answer":[],"Ns":[],"Extra":[]}

All the other names can be resolved fine: only `yelb-db` has a problem.

Any idea would could have gone wrong?


Is `yelb-db` another client as `yelb-ui` ?

Could you upload the full NSE log to which it is connected?


`yelb-db` is indeed another client. The logs of the `nsc-cmd-init` container contained errors about a timeout being exceeded.

I'm currently redeploying my clusters. It's probably better to restart with a clean setup, just to be sure my previous tinkering didn't affect anything.


It appears something was wrong with my setup. After a clean reinstall, everything works fine.

However, the resolution speedup only applies when I used the absolute DNS name:

#time nslookup -debug -type=a yelb-db.my-interdomain-vl3-network.
Server: 127.0.0.1
Address: 127.0.0.1#53

------------
 QUESTIONS:
 yelb-db.my-interdomain-vl3-network, type = A, class = IN
 ANSWERS:
 -> yelb-db.my-interdomain-vl3-network
 internet address = 172.16.1.3
 ttl = 3406
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
Name: yelb-db.my-interdomain-vl3-network
Address: 172.16.1.3

real 0m0.017s
user 0m0.005s
sys 0m0.009s

If I use the relative name (`my-interdomain-vl3-network` being in the DNS search path), it still takes around 400ms:

# time nslookup -debug -type=a yelb-db
Server: 127.0.0.1
Address: 127.0.0.1#53

------------
 QUESTIONS:
 yelb-db, type = A, class = IN
 ANSWERS:
 -> yelb-db.my-interdomain-vl3-network
 internet address = 172.16.1.3
 ttl = 3311
 AUTHORITY RECORDS:
 ADDITIONAL RECORDS:
------------
Name: yelb-db.my-interdomain-vl3-network
Address: 172.16.1.3

real 0m0.305s
user 0m0.006s
sys 0m0.012s


No, openapi-to-postman doesn't work for me. It's even worse because it generates only 2 levels when it comes to this situation.


Probably all related:

* URL
* URL
* URL
* URL
* URL
* URL
* URL
* URL

I'll try closing these and we'll revisit if they pop back up.


@esenmx the Flutter SDK fix for this landed in Flutter hotfix 3.7.2. Closing this issue.
 URL


@jrfnl Should we create a branch `master` from `main` for now until things are further resolved?


@Potherca I don't think so. Yes, the change is inconvenient for people, however:
* People shouldn't be using `dev-master` (or `dev-main`) anyway.
* Now the 1.0 release has been tagged, I expect we can go back to rapid releases for bug fixes (if any), which removes the need for anyone using `dev-master`/`dev-main`.
* Now the 1.0 release has been tagged, people won't need to update the version constraints on every 0.x minor release anymore either (as those are treated as majors).

It's also a one-time only change (at least that's the intention) and we executed it in the most considerate way possible:
* We has a long running open issue about the rename (this one).
* We did the rename _just_ before the release.
* The rename was mentioned in the changelog of the release.

I'd recommend for people who choose to use `dev-` branches of repos to watch the repo or, at the very least, watch release notifications of those repos, but that's not our responsibility.


The official suggestion from composer in URL is that you should create a 1.x branch alias for main and projects should use that instead of dev-master or dev-main. That means not keeping a duplicate branch.


Předělat dialog ukládání do objektu tak, aby zůstal označený poslední objekt, do kterého bylo uloženo. Pokud ukládám poprvé není označené nic, ale musím objekt vyhledat.


It didn't make it to the last release. :( Any update on the plan? @fvictorio


Hi @craigmcc, thanks for your suggestion. Perhaps I'm not understanding it right, but it looks like with the approach you took, you would still need to pass the error object to the `error` prop to your custom component.

While your approach eliminates one prop to pass (both the error state and the error text are handled in one prop), in this ticket, I was suggesting to include the `error` prop as one of the fields in the object that `register()` provides, in order to eliminate needing to pass the `error` prop entirely. RHF has the data of that `error` object anyway, just in a different place (`formState`), so all that would be needed to do is to also include it in `register()`'s return value.

Combining this `register()` function that I'm suggesting with your approach of custom text field component, one gets two benefits:

1. Reduce amount of props related to RHF to 1, namely the `register` prop.

js

2. No need to manually pick out the right error from the `errors` object based on the field's name, which is prone to error because it's up to the developer to make sure that the field name is the same as what they pick out from the `errors` object. There's nothing that would catch that oversight until it's deployed and noticed by a user entering the form. Especially bad for aria tags which might not be caught with the eye alone.

js
 // this mistake is easily possible with the current version of RHF

I'm guessing the reason why this library went with the a bit awkward approach of having to extract the errors from a separate object is because the idea was that `register()` would only include props that a native HTML `input` element can accept. Fair enough, but then perhaps a separate `registerAll()` function would be a nice idea, that would pass basically all the information that RHF has about a given field, and make it up to the developer to run it through a custom component and assign the right props to the right places? I'm not entirely sure about the specifics, but `registerAll()` could return an object with one field containing the original `register()` (so the props intended to be passed to the HTML input field) and some more fields like `error` (and potentially other in the future) that contain additional information about the field.

Example usage:

js
export const Form = () => {
 const { registerAll } = useForm();

 return (

 );
}

export const MyTextField = ({ registerAll: {
 inputProps,
 error,
}, label }) => (

 { label }

 {!!error && {error?.message}

);


After being upgraded on an Armbian system to 23.0.1 a couple of hours ago, docker-ce could no longer start containers. The error message was:

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container
 process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr
/apparmor/exec: no such file or directory: unknown

Installing the apparmor package didn't help. I had to downgrade it to 20.10.23.


Pour répondre à @A709197 ( URL

Pour lier la pièce à un avis, il faut qu'on puisse obtenir un identifiant de pièce (idsPieces), que l'on obtient avec l'endpoint POST /pieces. Je veux bien le retour du ticket pour voir plus clair.

Ps : je suis off pendant une semaine, je reprendrai ce ticket à mon retour pour aller plus loin


J'en profite, afin d'être assez clair, que l'ensemble des travaux initiés par le SDIS62 dans le développement de la fonctionnalité d'export de pièces doit servir de base pour les développements collaboratifs amenés par les différents acteurs, publics ou privés. La branche doit être mise à jour en fonction des avancées, pour que nous puissions l'intégrer dans la passerelle. Aussi nous travaillons en parallèle sur cette commande, n'hésitez donc pas à venir vers nous pour synchronisation.


If you're running into this issue, what do the following commands show on your system?

bash
ls /sys/kernel/security/apparmor

bash
cat /sys/module/apparmor/parameters/enabled

bash
apparmor_parser --version


I have the same problem as @wenzhuoz on my Debian system without AppArmor installed, resulting in:

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory: unknown

 Here's my output:

$ ls -l /sys/kernel/security/apparmor
total 0
drwxr-xr-x 15 root root 0 Feb 1 20:17 features
lr--r--r-- 1 root root 0 Feb 1 20:17 policy -> 'apparmorfs:[2154]'
-r--r--r-- 1 root root 0 Feb 1 20:17 profiles
-r--r--r-- 1 root root 0 Feb 1 20:17 revision

$ cat /sys/module/apparmor/parameters/enabled
Y

$ apparmor_parser --version
-bash: apparmor_parser: command not found


Hi!

We've built something like this internally for our Bitbucket repos:
- a Yaml Editor that is filled with the catalog-info.yaml content from the repo (using monaco-yaml: URL
- an endpoint within Backstage that outputs a dynamic JSON Schema based on the whole Backstage catalog data for the different entity types - therefor offering then some predefined Enums and autocomplete functionality to e.g. easier define the correct component name in the dependencies as well as to have some validation like the inbuilt Backstage restrictions e.g. metadata.name must have a certain format
- a save functionality that creates a pull request with the changes

I was thinking about open sourcing it, but there would be needed to do some generalization, since we have some specific scenarios just for us in there right now and it's all put together in one plugin. Might be considering to split the above mentioned functionalites up a bit into seperate plugins and have an "Editor" plugin, that can offers some extendable functionality so other plugins could integrate their own saving logic. There is probably quite a lot to consider to have it generalized.

Here is a screenshot to easier grasp what we've done:
image


we're seeing the same on all our hosts that've upgraded to `v23.0.x`, they all break on apparmor even though we definitely don't have the apparmor daemon installed or running. also, installing apparmor doesn't resolve the issue, it seems like the apparmor code in docker is broken with this release. we're on a mix of Ubuntu 20.04 and 22.04, all running from the official docker apt repo.

root@host-0:~# ls /sys/kernel/security/apparmor
features policy profiles revision
root@host-0:~# cat /sys/module/apparmor/parameters/enabled
Y
root@host-0:~# dpkg -l | rg apparmor
pi libapparmor1:amd64 2.13.6-10 amd64 changehat AppArmor library
root@linksharing-0:~# cd /opt/service/
root@linksharing-0:/opt/service# docker compose restart
[+] Running 0/0
 ⠋ Container service-service-1 Restarting 0.1s
Error response from daemon: Cannot restart container 00584aa5c7f75ada259a10d0ff951cce6eeaef921497b798aa30e2f57b68c34b: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory: unknown

we're going to roll back our packages for the time being, but this feels like a critical bug, at least to us.


It's possible this is a duplicate of URL and not a new/worse regression -- right now I am thinking that the attempted fix was incomplete and didn't actually fix the original regression in 23.0.0.

If you could test that this also occurred on 23.0.0, that would be very helpful. It would also be helpful to make sure to provide `docker info`, `docker version` and the additional information @thaJeztah mentioned if you are affected. Thanks!


@neersighted I can confirm that I had the problem described in #44900 when I upgraded to 23.0.0 few days ago. I had to rollback to 20.10.23. I was keen to try upgrade to 23.0.1 again when I saw its changelog, but unfortunatelly the fix is not complete.


Is the issue you see the same across 23.0.0, or is there any change in the error message? I think I am spotting an incomplete fix, but as I am unable to reproduce any of the actual errors here, I am trying to extrapolate from incomplete reports & a code walk.


Okay, that is quite helpful. Was this a crash, or just a failure to start a container?


oh, yeah, when I checked before I didn't restart docker after installing apparmor. if I do the following, then my containers keep working:

apt install -y apparmor && systemctl restart docker && cd /opt/service && docker compose restart

would definitely love confirmation from @pavelvodrazka, but I think you've found it, @neersighted!


Okay, the root cause is understood, and the mitigation is the same: if you're not in some nested containerization scenario, install `apparmor`. It is a `Reccomends:` dependency of the daemon; that means that is technically possible to live without it, but it:
* is not the happy path
* may require manual intervention
* will reduce the security profile of your contianers

The only question is whether we wait for containerd to accept a revert of the problematic change, or if we spread our in-tree check further. Given that there is a workaround (to not go out of your way to avoid apparmor), and we have not regressed further 23.0.0 (but rather failed to fix a regression), I am inclined to wait for containerd to accept/decline the fix, and to not hurry this.


@nergdron I can confirm that installing `apparmor` package and restarting docker service fixed the problem on my system.


Unfortunately AppArmor broke some of my containers, so I have to go back to 20.10.23 until I figure out how to fix it with a less restrictive profile.


You can set `--security-opt apparmor=unconfined` on the affected containers instead of taking a shotgun approach.


I can confirm too that installing apparmor prior to upgrading to 23.01 work around the issue.


The reason I went to passing error was a compile error that RHF caused me
around 7.33.1). I used to pass "errors: FieldErrors" so I could (for
example) pull out both error messages on something like a password mismatch
when updating your user profile.

I reported this on
 URL but, even
after supplying the requested CSB, it wasn't ever addressed. I was stuck
not being able to upgrade until I happened to see in a Stack Overflow post
that you could pass the individual error itself. That at least gave me a
way to upgrade RHF versions (albeit requiring me to adjust the props for
all my components in all my apps).

I agree that incorporating the error property into what already has to be
passed in would be an improvement.

Craig

On Fri, Feb 10, 2023 at 12:43 AM Lesik ***@***.***> wrote:


I'm wondering if this use case is better served by directly communication with the GitHub APIs from the client, rather than using the scaffolder? Bit in line with how the `catalog-import` client creates PRs.


Thinking out loud, and just as a side note: if this works with a "generic" HTTP CRUD API such as S3, Grist could run "backendless" on other "generic" HTTP CRUD APIs ("zero" data protocols), such as Solid or remoteStorage.

With using Minio's Secure Token Service (STS) it even appears within reach, that the Grist browser application talks to the object store directly.

Both options in return open up doors for #380, if state management within the service worker can be solved.

On another note I wonder, if this worked for you @yohanboniface, should we close here?


Is there an active/open discussion against ruby gems somewhere? I see that URL was linked, but is closed now.


I don't think so. There is a PR to document an API useful to fix the issue but it's kind of stale and does not provide an exact procedure to resolve the path: URL


Je viens d'avoir le même problème. Je me suis aperçu que ma config s'était vidée.

As-tu vérifié que tu avais de l'info dans le plan name et la case pour générer les sensors à ON?
image


OK

蓝笑灵晨
***@***.***

------------------ 原始邮件 ------------------
发件人: "dbeaver/dbeaver" ***@***.***>;
发送时间: 2023年1月17日(星期二) 晚上7:59
***@***.***>;
***@***.******@***.***>;
主题: Re: [dbeaver/dbeaver] close tab repeated (Issue #17697)

The latest build contains correct translation.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>


I have the same problem

docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory: unknown.
ERRO[0002] error waiting for container:

docker 23.0.1
Armbian 22.08.1 Jammy


Please refrain from "me too," which is unhelpful (sends needless notifications) and unnecessary (there is a :+1: button, and there is a mitigation).

You can `apt install apparmor` as already discussed in this thread (and then restart `docker`, e.g. `systemctl restart docker.service`), or simply set `apparmor=0` on the kernel command line.


FWIW, with 23.0.1:

$ apt list docker-ce docker-ce-cli
Listing... Done
docker-ce-cli/jammy,now 5:23.0.1-1~ubuntu.22.04~jammy amd64 [installed]
docker-ce/jammy,now 5:23.0.1-1~ubuntu.22.04~jammy amd64 [installed]
$ docker run -ti --rm 0ab66881fb24 bash
docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: unable to apply apparmor profile: apparmor failed to apply profile: write /proc/self/attr/apparmor/exec: no such file or directory: unknown.
$


Getting the very same error.

Here my info:

OS: Arch Linux ARM (Rolling Release)
Docker: v23.0.1, build a5ee5b1dfc
Docker compose: v2.16.0
Containerd: v1.6.16 31aa4358a36870b21a992d3ad2bef29e1d693bec.m
Ctr: v1.6.16


Oh, this could be why I've not encounted this previously.

GitHub redirects renamed branches, but only if they were renamed

 URL


I'll lock the conversation on this thread in favor of URL which is still open, and to prevent the conversation from diverging.

A short summary;

- `apparmor_parser` is needed for `dockerd` to provide AppArmor protection on a kernel that has apparmor enabled.
- `apparmor` (which provides `apparmor_parser`) is a _`Recommends:`_ dependency for `dockerd` (which is a _strong_ recommendation, and means that while `dockerd` is _able_ to run without, doing so may require manual intervention).
- Depending on your installation method and the package manager used, `apparmor` may not get automatically installed when upgrading; if that's the case, then make sure to (manually) install the `apparmor` dependency, and restart the docker daemon afterwards for it to detect that `apparmor_parser` is installed.
- This issue was caused by a regression in the containerd code we use; we made changes in this repository to work around this regression, and to improve handling of this situation, but additional changes are still needed in containerd; those changes have been merged, but have not yet been released.
- Subscribe to URL to get posted on updates (but please refrain from "me too" / "+1" comments if you don't have important details to add).


Thank you for the answer
It looks handy, but still not enough for backstage to be an independent tool for all team (not only developers)
Thanks for the link, I will try it. But if you decide to implement CUD UI for entities - I would like to use it.

BTW, backstage is really cool and powerful tool, but a bit complex sometimes


Seems that with URL implemented, this can be done pretty easily by Bazel now?


_After a bit more research, it's incredibly easy to paste a kit into IBE, provided it has `,tag:` appended._

### Breakdown:
- By default, items do not have a `tag:{}` field. For example:
 - An orange shulker box has the following: `{Count:1,id:"minecraft:orange_shulker_box"}`
 - If our NBT data starts with `,tag:`, followed by the actual NBT itself, then users can simply click between the closing quote of the item name and the closing curly bracket, and paste in the data.

- Relatively few items have naturally existing tag fields, with the majority falling in the Combat, Enchantment and Potion/Effects categories.

- While we do have some standalone items, including some that have natural tags, the majority of our archive is storage-based, thus prefixing all NBT with `,tag:` would render the mass majority of the archive instantly usable regardless of interface (IBE, Meteor, Wurst, etc).

This should (generally speaking), solve the issue of multi-interface compatibility. Appending everything with `,tag:` makes all the kits usable in any interface, and while some items won't be usable if you straight up copy-paste the entire file, users can simply exclude `,tag:` in their selection when copying.

There are however other standards that need to be set, including the following:
- Kits/Items without Authors
- Kits/Items without Names
- Kits/Items with NSFW or 18+ content including links, text, images, references.
- Books
- Kits/Items with the ability to significantly harm servers, primarily the Total Freedom network.

## **_Please give feedback either in this thread or on Discord for the NBT Standard as well as ideas for the other standards as I can not add more kits to the archives until (at the very least) the NBT Standard is set._**


This also happens without Docker installed but with containerd.io from the Docker repo.
Same fix, just install apparmor and restart containerd...


Yes, containerd also regressed (or rather, Moby was where people noticed, and containerd was also the root cause). The PRs in containerd point that out and will resolve the regression.


It looks like the remaining two issues blocking this have been fixed. Maybe we can enable MS extensions for Cygwin and MinGW by default now?


import 'package:ffmpeg_kit_flutter/ffmpeg_kit.dart';

...

await FFmpegKit.execute("-y -i " +
 videoFile.path +

 " -filter:v \"hflip\" -pix_fmt yuv420p -vcodec hevc_videotoolbox -b:v 1200k -tag:v hvc1 -c:a eac3 -b:a 64k " +
 applicationTemporaryDirectoryPath + '/video_roeid_mirror.mp4'
 );

tune the -b:v parameters for video quality

Inside XCode you should add this:

image

image


That error sounds very like URL

@vviers it looks like the client library we use (minio.js) has a `region` option that could be added here URL Sorry for not including that as an option.


Hey,

This should be fixed by #3415. I published a pre-release version of it as `hardhat@viair` and run your tests and now I get

Can you check if that error is correct?


@alcuadrado seems like something which can be correct for sure.


Well despite the absolute lack of feedback from anybody, I'm approving the `,tag:` standard, and will elaborate on other standards in the below comments.


# Kits/Items without Authors

This has become an increasingly problematic issue, as many of the kits saved in Antis plot lack credit of any sort.
Thus far, I've been listing unknown authors as 'Pending', but I feel this is both unclear, and a temporary measure.

### Proposed Solutions
- Switch 'Pending' to 'Unknown', 'Unknown Authors', or something clearer.
- Add a notice of some sort requesting information on kits with Unknown Authors.

In my opinion, there is no good solution to this issue, as I seriously doubt we will ever identify the authors of more than a handful of kits. However, we can certainly do a better job than at current with labeling these kits appropriately.


# Kits/Items without Names

Similar to "Kits/Items without Authors", this is a problematic issue with many kits in Antis plot, but one we can do a lot more to rectify.

### Proposed Solutions

- Names should be suggested based off the contents of the kit
- Chosen names should be agreed upon by 3 people (Kaddicus, Parsa and Anti at the very least)
- When added to the site, the name should have an asterisk (*) next to it to indicate the name is not the original
- A note should be provided in the kits description or above the list of kits stating that kits with an asterisk had no name, and the name given was chosen by the Archivists

This would allow a number of interesting kits currently sitting in Antis plot to be added to the archives.


# Kits/Items with NSFW or 18+ content including links, text, images, references.

Coincidentally this is an issue being currently discussed on the server: [[POLL] The Matter of NSFW Content]( URL

My views have already been expressed in that thread, but that's for the server as a whole.

My view of NSFW and the Archives is that anything goes, _provided it has suitable warning_.

### Proposed Solutions
- Add a neon red [NSFW] tag on kits containing NSFW
- Separate NSFW kits into a separate page, or add a checkbox to show/hide NSFW kits (hide by default)


Can confirm after testing that both `Infinity` and `NaN` just gets converted to `0.0` when added to an item as SNBT, and has to be manually changed.

Ultimately it seems Infinity/NaN items can't be stored as SNBT at all without removing the Infinity/NaN.

Unless there's another way to save these items beyond SNBT.... they can't be saved.


Is the current work-around still working?

I created a new Azure AD App + secret.
Next on the tenant-admin.sharepoint.com/_layouts/15/appinv.aspx added the FullControl rights to both the content and social scope.
Using Connect-PnPOnline with ClientId and ClientSecret, the Get-PnPUserProfileProperty command is working fine.
But Set-PnPUserProfileProperty returns the following error:

Set-PnPUserProfileProperty : De huidige gebruiker is niet gemachtigd om deze bewerking uit te voeren.
At line:1 char:1
+ Set-PnPUserProfileProperty -Account $acc.AccountName -PropertyName 'S ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : InvalidOperation: (:) [Set-PnPUserProfileProperty], PSInvalidOperationException
 + FullyQualifiedErrorId : InvalidOperation,PnP.PowerShell.Commands.UserProfiles.SetUserProfileProperty

The error text in this Dutch tenant translates the same but the CategoryInfo differs from the topic start.


Did you run the following on each Geo where you need to perform the Get/Set? Also, if multi-geo, you will need to so the ACS registration (AppInv.aspx) on each central admin site.

set-spotenant -DisableCustomAppAuthentication $false

 URL


Found the issue... the error was kind of misleading:
I tried to set SPS-Location but the location value was not yet available in the term store.
Since I first tried Set-PnPUserProfileProperty using certificate authentication instead of using secrets I figured it was still the same issue, but no.


Yes, for sync scenarios, I usually let those termsets remain open - following the model that OOB SharePoint uses for fields like Job Title, etc.


Hi @1ucian0 ,

We have been working on this issue. Instead of using theorem 5 in [ URL this issue motivated us to develop a new decomposition that requires a smaller number of gates for SU(2) multi-controlled gates [ URL PR#8710 is the first step to solve this issue and reduces the number of gates in the MCXRecursive (that now is not recursive).


@AlexisRalli: this issue and all the PRs that link to it above are what I was trying to find when you asked me about them the other day. For others' reference: Alexis had also had some ideas about the generalised MCU constructions (see #9574 for one part, but I think he had more in the works as well), who I then told @alexanderivrii and @ShellyGarion about.

I don't have much to contribute myself to the discussion, just trying to link up all the folks I know about working on this, or things adjacent to this.


Thanks @jakelishman,

We intend to contribute with an n-qubit multi-controlled su(2) decomposition that requires ~16n cx if the gate has one real diagonal and ~20n for any other su2 gate.


Can confirm, Hotbars work.

Any method involving SNBT will _**not**_ work, as SNBT causes NaN and Infinity to be reset to 0.0 when applied to an item.

My theory is when the SNBT gets converted to normal NBT, it can't map "NaN" or "Infinity", so resets it to default (0.0)


@fr-Pursuit
Thank you for your results and comments! We really appreciate it.

I think it's not quite right to solve all dns problems in one issue. Could you create a separate ones for other problems? For example, about PTR requests.


As of today, this issue still exists (Firefox V109.0.1, BW Add-on V2023.1.0), where my vault did not lock overnight. I have it set to Lock after 5 mins and reopen with PIN. Lock Now does not work. The only thing that seems to reset it, as mentioned by others, is to disable the Add-on and re-enable it in Firefox Add-ons and Themes. During the time this has occurred, I have basically been using Windows 10x64 to read PDF files using Acrobat Reader X Pro (v10.1.16) and reading email via Thunderbird V102.8.0), and have, at times, had two/three different instances of Firefox running, launched by moving a tab to another screen. The latter may be significant.


Still catching up on December, I'm tagging @e-kayrakli as string-/bytes-master to get his read on this.


yes pls add this option then finally i can switch from send anywhere .. btw love ur work i tried many but ur app was the one i ws looking for :) keep it up bro


Thanks for suggesting. I've investigated possible ways of implementing this, and I think I found a way that works without JavaScript! We would need a little support from the Highlight extension, provided by Python Markdown Extensions. The solution is similar to what we do with content tabs.

 HTML prototype

 html

 code {
 display: block;
 padding: 10px;
 background: #eee;
 overflow: auto;
 }
 code input {
 display: none;
 }
 .__collapse {
 display: none;
 }
 code input:checked + .__collapse {
 display: inline;
 }
 code label {
 background: blue;
 color: white;
 padding: 4px 10px;
 cursor: pointer;
 }
 code input:checked + .__collapse ~ [for=__open] {
 display: none; /* Hide expand button - could possible be kept */
 }

 markdown_extensions:

 # Python Markdown
 - abbr
 - admonition
 - attr_list
 - def_list
 - footnotes
 - md_in_html
 - toc:
 permalink: true

 # Python Markdown Extensions
 - pymdownx.arithmatex:
 generic: true
 - pymdownx.betterem:
 smart_enable: all
 - pymdownx.caret
 - pymdownx.details
 - pymdownx.emoji:
 emoji_index: !!python/name:materialx.emoji.twemoji
 emoji_generator: !!python/name:materialx.emoji.to_svg
 - pymdownx.highlight
 - pymdownx.inlinehilite
 - pymdownx.keys
 - pymdownx.mark
 - pymdownx.smartsymbols
 - pymdownx.superfences
 - pymdownx.tabbed:
 alternate_style: true
 - pymdownx.tasklist:
 custom_checkbox: true
 - pymdownx.tilde

 Expand

The prototype looks like this:

<img width="395" alt="Bildschirmfoto 2023-02-18 um 16 09 20" src=" URL

<img width="398" alt="Bildschirmfoto 2023-02-18 um 16 09 14" src=" URL

The next step would be to on-board @facelessuser, and check if he would be willing to implement something like this, given that it fits the tone and vision of the Highlight extension. When this is done, we could add styling support in Material for MkDocs. In any case, this needs to be taken upstream, and there are no actionables for us until support is added.

---

__Further considerations__:

- It makes no sense to add this functionality in JavaScript, since we would induce massive content shift when the page is rendered, especially when the page is long and has a lot of code blocks
- I've only found the `input` + `label` technique to work. Another candidate would be `details`, but that would induce a new block formatting context, breaking out of the `code` block, thus a dead-end. However, the solution I prototyped works beautifully and even keeps code annotations functional, because we're not inducing `overflow` on the container.


I'm not so sure how all this would work, but I'm willing to at least talk about it and see if it maybe could work somehow. I have concerns about this, especially when paired with Pygments. This is taking a very simple case and applying such logic, but what about when syntax highlighting is at play? What if we are applying this to a code block using the table format and line numbers?

Even if this is too convoluted for Highlight, we _might_ be able to provide a new general-purpose block that applies something like this to a given code block. General purpose blocks are getting closer and closer to being ready for the public to start trying. I guess there are always custom fences as well.

Anyways, while I see _maybe_ a possibility when done with a very simple example as shown above, there are definitely some concerns with this playing nice with other features enabled.


Couldn't this be done similar to / or with line spans? We could even make this configurable similar to `hl_lines`, e.g. `collapse_lines="4"` to collapse everything from the 4th line on, or `collapse_lines="4-8"` to only collapse lines 4-8. As I understand, only the line spans would need to be wrapped, so this should – in theory – be possible to implement as a post processor, not?


Hmm, no, not yet. I don't think it will work with tables. But I guess it might work with `pymdownx-inline`, right?


I'm still not sure why we couldn't use generic blocks to create a simple collapsible wrapper.

`
/// collapse

some
code
with a lot
of lines

///

`

If I'm being honest, I'm not a huge fan of wrapping lines with an input checkbox. Maybe it will grow on me?

I'm not saying I'm against the suggested approach, but I'm skeptical that there is no other way, and that this is the best and only way. That's not to discount the research you've put into this. If I were going to do something like this, it needs to work generally well and I'd probably want to explore some other avenues even if they lead to dead ends. If I'm to support such an approach, I want to be 100% sure I couldn't approach this in a better way.

I imagine it could work fine with `pymdownx-inline`.

I know there are some complications right now, but I know things like `:has()` are on the horizon. Browsers are moving forward with this where they weren't before. Granted, they will be somewhat limited for the sake of performance, but they are coming, granted, I don't know how many years until we can actually use them. So clearly, this isn't available now, but something to keep in mind as we are thinking forward.


I'm agnostic to how things are implemented – this was just a first rough sketch. Let's let that sit for a while and maybe come back to it later at some point. I think it would be a great addition to the toolbelt.


Yep, that makes sense. I may tinker with the idea myself. It may be that this is the only pure CSS approach right now, but that probably just highlights the weakness in the current, implemented CSS spec. I'm just hesitant a bit right now as it is an invasive approach and only works on some of the supported code block styles, and I'm certain the future will allow us to do this better if there isn't already a way now. I won't deny that many may find the feature useful though.

I have a feeling that if I did implement this as currently proposed, I'd be more willing to post-process it in some generic block as described above than make it an integrated part of Highlight. That would give me the ability to implement an approach native to Highlight at some future point when the landscape is a bit more attractive for a pure CSS, collapsible block. I could just bundle it in Material Extras or something like that.


I feel like something like this could work. No JS, just CSS. It's kind of sloppy right now, but the idea is simply that it sets the max height on the block and fades the text at the bottom. When you expand, it shows everything.

 URL

collapse


Pulled it off in Material using generic blocks:

<img width="789" alt="Screenshot 2023-02-18 at 8 53 50 PM" src=" URL


After tweaking it a bit, I'm thinking this is probably a fairly reasonable approach. If you wanted to not have it collapsable after expansion, the button could just be hidden after expansion. I think a reasonable alternative is just adding a class to a code block and making it shorter, but scrollable, but if expanding blocks is absolutely desired, I think this approach could work and wouldn't require us to deeply integrate it into Highlight. We just create a simple wrapper around the code blocks. Anyways, I think I'm done exploring this for now.

collapse


Does this work with code annotations? FWIW, setting `max-height` implies `overflow: hidden`, and this might mess with code annotations. Strangely, I thought it was definite, but it seems like it works in Webkit. Not sure about other browsers, though. This is why I resorted to the nested span solution, which I still find to be more flexible, as it would allow for supporting multiple foldable sections.

So, this still works in Chrome (to my surprise), but other browsers would need to be tested:

<img width="391" alt="Bildschirmfoto 2023-02-19 um 09 48 50" src=" URL


I had not tested annotations, in your test, do the annotations need to be wrapped in the container or outside?

I guess I missed this part. I've never seen this done anywhere.

I thought this was for posting large code blocks without taking up a ton of space. I didn't realize people wanted multiple foldable sections. This seems like it creates very complex code examples. I guess some your suggestions make more sense in context now.

If multiple, foldable code blocks is really what is desired, then we could still go with your idea, but I think approaching it with a special Material, generic block would be the ideal way to go as least for now. I'm not exactly sure how complicated I want Highlight to be. At the very least, it would allow me to ship the functionally as it's own experimental thing and have it mature in Material first. This may be a good candidate for the Material Extra repo that I already maintain.

So, I imagine we could have a block that you can wrap your code (and annotations?) in, and we could extract the HTML for the code block and then post process it with foldable sections.


Resolved the error for me.

`MultiSolcUserConfig` compiler entry

{
 version: "0.8.14",
 settings: {
 viaIR: true,
 optimizer: {
 enabled: true,
 runs: 200,
 details: {
 constantOptimizer: false,
 deduplicate: true,
 yul: true,
 },
 },
 outputSelection: {
 "*": {
 "*": [
 "metadata",
 "abi",
 "storageLayout",
 "evm.methodIdentifiers",
 "devdoc",
 "userdoc",
 "evm.gasEstimates",
 "evm.byteCode",
 ],
 },
 },
 },
},


Just a note, the simple expand option I provided worked fine in Firefox, Chrome, and Safari. As a simple option, it is more than sufficient and very quick and easy to get working as I technically already have a prototype.

But if we absolutely want multiple folding regions, that can be done. It's obviously more work in the post-processing realm, but I imagine doable.

Regardless of which direction we go, I'll probably utilize the generic block feature that should be available soon-ish. Deep integration into Highlight may or may not happen at some future time.


J'ai finalement réussi a faire marcher les compteurs d'énergie. J'ai repris la doc dans ReadMe.md et ca s'est mis a marcher. CODE 18!

Normalement, je fermerais cette issue. Je pense que c'est resolved.


As tu essayé ca? Ca pourrait confirmer que c'est resolved.

image


+1 for sure. To basically echo the sentiments of the original thread, #37, if you're already running all nodes and connections within a VPC, the SSL is redundant.


My current focus is to get out the generic block plugin out. I'll personally be using the basic fold in my own documents as I'm actually kind of liking the look and functionality. I can't see any negatives except that it isn't as quite as powerful as the per-line folding approach. FWIW I think it works well for what I personally need. If it turns out people are interested, I don't mind making it publically available.

<img width="804" alt="Screenshot 2023-02-19 at 9 21 48 PM" src=" URL

As far as the more complex folding approach, I'll probably look at it sometime after the generic blocks plugin is released. I'm not exactly sure when, but it would definitely be after that gets out. I think it is generally more complex than I personally need, but I can see people maybe wanting to utilize this approach as it does open up more possibilities. I think we can achieve everything in the suggested prototype without having to deeply integrate this into Highlight.


@squidfunk / @facelessuser thanks for the great discussion the this request.

The last screenshot shared looks like what I was imagining. If I got the discussion right, this is based on pure CSS and thereby could be already added using customization stylesheet file.

I would appreciate if you would share your current code so I could test it.


@facelessuser the last screenshot you posted looks pretty good. Could you create a PR with the necessary changes when the generic block plugin is out? And this is language agnostic, right?

Regarding multiple foldable regions – this might be something for the future, so no hurry.