With regard to `brandId` and a delay, I think 'delay' and the trade-off needs to be defined. If the API can be delivered within the next month without the brandId, then that would be worth doing. If its going to be delivered in 6 months, then brandId should be in-scope.

If faced with the above choice, I'd recommend delivering V1 of the API in one month's time without the `brandId` and then add it to the API in 6 months time as V2.

Not having `brandId` does create significant complexity and operational risk for anyone consuming the data, so its not an acceptable long-term solution.

Not having the API at all make the PRD largely unusable, and certainly unreliable.


@possan Might be related to #72, as both are very recent problems, and one might lead to the other, i suggest that we focus efforts there to address this issue, and close this one (and other similar issues) once it's solved


Yes, but this luckily seems to work.

@Route("email")
public class EmailView extends VerticalLayout {

 public EmailView() {
 final EmailField emailField = new EmailField("E-mail");
 emailField.addValueChangeListener(e -> {
 if (!emailField.isInvalid()) {
 Notification.show(e.getValue());
 }
 });
 add(emailField);
 }
}


The web component seems to do the checking after every key stroke. But I think it should be done only when intended value change is to happen.


IIUC, the whole problem is that Stork does not use the Kubernetes Client provided by the Kubernetes extension, correct?


Which browser are you using on which operating system? Seems like your language-setup is somehow screwed?


Thanks for the description of the problem.

Could Stork not have an SPI that basically allows the Kubernetes Client to be set and then in Quarkus when the Kubernetes Client capability is present have the SPI implemented by pulling the Kubernetes Client from CDI?


It could be done via QuarkusStorkInfrastructure: URL

Right now it's only used to reuse the Quarkus Vertx instance but it's easy to change the Kube service discovery to use it for kube client as well.

How does it help? Would you want the user to add the kubernetes client extension when they add the kube service discovery?


Pretty much, yeah. Similarly to how we expect users to add `quarkus-kotlin` if they plan to do Kotlin.
We can also easily warn about the missing extension at build time.


Hi there - boolean fields aren't yet supported for JSON or Hash, they'll likely appear in JSON first as boolean is a native type there vs a Redis Hash that understands strings, floats and ints.


Tried Warp now, and the font rendering in the application parts (that is, not the actual terminal but for example in the settings and similar) is very bad. I initially thought something must be wrong with the installation. Here is a screenshot of the sidebar menu in settings as an example.
Screenshot 2022-04-07 at 13 32 47


We can require adding kube client without sharing the client between the discovery and the other places. If someone adds it now, it will all work, right @aureamunoz ?


That worked! Now my Client instantiation looks like:

final client = Client(
 input: _ble.subscribeToCharacteristic(characteristic).asBroadcastStream(),
 output: (msg) => _ble.writeCharacteristicWithoutResponse(characteristic, value: msg),
);

I did notice that my App crashes when I disconnect from the peripheral. Is this the error you are referring to?

W/System.err(26516): io.reactivex.exceptions.UndeliverableException: The exception could not be delivered to the consumer because it has already canceled/disposed the flow or the exception has nowhere to go to begin with. Further reading: URL | com.polidea.rxandroidble2.exceptions.BleDisconnectedException: Disconnected from MAC='XX:XX:XX:XX:XX:XX' with status 0 (GATT_SUCCESS)


I was able to prevent the disconnect error by changing the Client instantiation as follows:

_client = Client(
 input: _ble.subscribeToCharacteristic(characteristic).asBroadcastStream(onListen: (subscription) {
 _subscription = subscription;
 }),
 output: (msg) => _ble.writeCharacteristicWithoutResponse(characteristic, value: msg),
);

And then calling

_subscription?.cancel();
_connection?.cancel();

When disconnecting from the peripheral.


The the flutter_reactive_ble FAQ contains a workaround for that exception.

I don't think canceling the subscription is enough, I still got that exception rarely (until I added that workaround in 0fe4cdcb029a8a47e1dc323e2711986002ca681a).

I also added some code to the example to completely ignore errors in the subscription stream because I occasionally got stale "disconnected" errors in the new connection after reconnecting to the device. Disconnecting causes the subscription stream to end anyways, so I'm not sure why that error even exists.


OS: Windows 10 Home 64-Bit
Version: 10.0.19043 Build 19043

Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:99.0) Gecko/20100101 Firefox/99.0
Build ID: 20220330194208


There's an aarch64 build for 64-bit ARM. I don't know if MacOS supports a Linux compat layer, though, to use it. I'm also pretty sure the Arduino IDE doesn't know what to do w/64b Mac on ARM, either (i.e. even for Win64 is still installs the 32b binaries!).

I do everything via a cross build process and haven't had a Mac since 1996, so if this is important I'll need some assistabnce.

If you look at URL and can add in something that will let Linux x64 build Mac64ARM bits, I'd be happy to include it in the standard release process.


macOS does not support ELF binaries, unfortunately, so those builds won't work.

Sure, I can take a look.

FWIW, I am using PlatformIO and followed the instructions, but it just hung there for a while not doing anything, so I thought something went wrong due to platform architecture. It turns out I was just impatient, and everything took a while to clone and install.

The existing x86_64 builds do work on ARM64 (probably using Rosetta to translate it), so in the meantime that will work. But would be nice to have native builds Eventually™


I've confirmed that the issue is with Vite `2.9.1` to get things working I recommend anchoring your Vite version to `2.8.6` which is the last working version for Vitebook


@joseaquino nope still doesnt work for me can you share me a sample repo?

I tested it by bumping vite to `2.8.6` in their example stackblitz URL


Sorry, my fault. This has nothing to do with the browser but with the seed-words. BIP39 allows the seed words to be in different languages. You don't specify the language when you write in the seed words. So the algorithm gets the first word from your list and tries to find them in the different lists. That's the way the language is detected.

So in you case it could not find the first word in any of these lists. Please double-check!


@joseaquino you're right! 👍🏻 hard fixing the dependencies of vite to `2.8.6` does fixes the solution. Guys Im going to mark this as the solution until vite solves the problem for us.


Have confirmed this behaviour, and have a simple fix for it.


Hi, is this a typo mistake? I find the bom version of 2.12 mentioned above is `2.12.6.1.20220326`, but in the release notes it's `2.12.6.20220326`.

image


@rockyzhang24 it looks like your figet.nvim is outdated, because L216 does not read like `vim.schedule`. Are you sure it is on the latest version?


Thanks.
No, it is the latest fidget. I update my plugins everyday. My neovim is the latest nightly (NVIM v0.7.0-dev+1439-gda31e953b)


Good idea to use the boolean `disposeHandler` of the `HttpClient` constructor. It saves us a flag in the `FhirClient` to remember not dispose the injected handler.

We will create a PR for this.


Btw, the issue info is not the same for different filetype.

In a `go` file, I got
<img width="1715" alt="image" src=" URL


Sorry, I misread the stacktrace. You are right -- I can also reproduce the bug.

Indeed `vim.schedule` is from L386 (the bottommost line) and L216 reads

api.nvim_win_set_option(self.winid, "winblend", options.window.blend)

The problem is that the "deferred" `fidget:fmt()` call can still be executed by the event loop during the execution of `getchar()` (see URL I am looking into why.


Thank you so much. I am not sure whether this issue is caused by `clever-f`. I already opened an issue there ( URL Also, I am not sure whether this issue is related to URL i.e., caused by ` ` and `getchar()`. I have no ideas.


Also worth checking out a comment by @kevinhwang91 ( URL -- I use a similar plugin that maps `f`, namely `quick-scope`. Or @kevinhwang91's `nvim-fFHighlight` might be another alternative.

Clever-f is not actively maintained these days, so you might want to switch to another similar plugin as a workaround. It's a bug that clever-f needs to fix, or neovim might be responsible for scheduling as `vim.schedule` is supposed to defer the execution *when it is available*.


Okay. Thank you for your suggestions.
I know this new plugin `nvim-fFHighlight` but it not supports `tT` highlight.
For `quick-scope`, I tried it shortly before and I am worried its performance because it analyze each word in a line, not just the char I want to jump to.


Thanks @brianpos, your fix solves the problem with the port exhaustion as the message handler can then be reused.

As a side note: It would be even easier if the constructor of the class FhirClient would take an HttpClient or an IHttpClientFactory as a parameter instead of an HttpMessageHandler, as this would allow using the HttpClientFactory-Pattern (see URL already mentioned in issue #2036.
The main benefit of this is that the HttpClientFactory handles the lifetime of the message handlers, which avoids DNS-Issues (which can occur when the message handlers live too long) as well as port exhaustion and performance problems (which may occur when too many message handlers are created in a short period of time).


Collaboration on this issue through maintenance iteration 10, has resulted in the following DSB proposal, expanding off of @ACCC-CDR's initial proposal.

Rather than duplicate the GetDataHolderBrands API for unauthenticated clients, a new API optimised for discovery of public data holder APIs (PRD, status, and outage and any future public endpoints) will be defined named: `Get Data Holder Brand Public Endpoints`

The schema will be optimised for presentation of Data Holder Brands and discovery of associated public endpoints. It will therefore have the following fields:

Name | Type | Required | Description
-- | -- | -- | --
brandName | String | true | Name of the data holder brand hosting the public endpoints
brandId | String | ~false~ true | ID of the data holder brand hosting the public endpoints
publicBaseUri | UriString | true | Public endpoints base URL
logoUri | UriString | true | Data Holder Brand logo URL
~industry~ industries | ~String~ [string] | true | The industries the Data Holder Brand belongs to. Please note that the CDR Register entity model is constrained to one industry per brand which is planned to be relaxed in the future.
lastUpdated | DateTime | true | Time when the record was last updated
abn | String | false | Australian Business Number for the organisation
acn | String | false | Australian Company Number for the organisation
arbn | String | false | Australian Registered Body Number. ARBNs are issued to registrable Australian bodies and foreign companies

The payload will be a shortened version of the data holder brands payload with a flat simplified structure.

The industries array will follow the same convention as GetDataHolderBrands URL Only one industry will initially be supported until multiple industry sectors per brand are supported on the CDR Register.

Discussion has occurred on whether the brandId can remain optional until the CDR Register is able to guarantee the field will be populated. The DSB does not seek to define an interim solution in the standards. This leaves the responsibility to the ACCC to coordinate the release of this API based on their release schedules. Any interim solution will also remain the responsibility of the ACCC.


@wookayin Thank you so much for your investigation. Both fidget and clever-f are my must-have. Hope this can be fixed soon. Thanks again.


Yes, it is perfectly fine. Because E523 errors happens due to a 'textlock' (see `:h textlock`) and it only pertains to drawing of the fidget windows. Any internal states and data will remain intact. As you could test out, the fidget windows will simply won't be updated nor be spinning while it is in the operator-pending mode.


@wookayin Okay, thank you for explaining it in detail. I just tested it, and I found another glitch.

To reproduce it:
1. Open a `lua` file (because `lua` LSP takes longer to initialize)
2. Press `d` followed by `f`, now we are entering `Operator Pending` mode
3. Wait here without giving a char to `f`. We can see that fidget progress update and spinning pause as expect. Keep waiting, and we can see fidget left some ghost chars even though it has finished in background.4.

 ` immediately after the ghost chars appear. The ghost will still be there and won't be removed any more. However, if we press ` ` after a while, the error shows again

<img width="1721" alt="image" src=" URL

Thank you!


@rockyzhang24 Good catch. Can you try again in the updated PR?


Because `nvim_get_mode` is only for RPC API, `blocking = true` is always for Lua.

I don't think it's appropriate for fidget to fix this bug. There're maybe a lot of other async functions to encounter this issue. From the upstream is too hard to fix. From the clever-f avoid using must be refactored the cost is too expensive.


ACCC strongly supports the proposed change outlined above and requests an earlier obligation date to support the introduction of Energy. ACCC proposes 15th September 2022 as the future dated obligation, to ensure Data Holders are responding correctly to data requests prior to the implementation of the Energy Sector.


This would be useful; User A develops the form, transfer Form to Users B,C,D... or Group. Then recipient users can share link to external people to answer/fill-in and collect their own answers.


@aoisummer did you find a solution to bellow?

@alexander-akait Could you please share the link of the documentation where it's referring about polyfills would fix this issue? We are struggling on this issue as we have a requirement to build the project into es5 and we use externals heavily


Hi @cowtowncoder, any way to determine if one is affected or not?
You write that UntypedObjectDeserializer needs to be used in combination with Collection / Map - at least this is what I understand.
I scanned my code and we are not using UntypedObjectDeserializer, however, it might be used by other jackson-databind code that we use. Could you please clarify how to determine if one is affected by this CVE?


@williamjacobszoon you should use dynamic import (`import()`) then.. As I said transforming top-level-await (async/await => promises) is not possible in current webpack design..

maybe you can use `babel` for this (for es5 builds transform chunks after compiling..)


The PR stalled, so the docs did not get updated to actually explain what is happening.
Please re-open the issue and/or fix up and merge the PR!

Specifically, this PR was supposed to address how to dynamically import absolute paths in the docs.

Even more specifically, this proposed change (rendered version here) is actually the solution (I tested it, and it works!):

js
import { pathToFileURL } from 'url';

const fileUrl = pathToFileURL('C:\\path\\to\\file.js').href;

await import(fileUrl)


Looking forward to this, the normal systray is buggy on fluxbox. using this module would likely solve my issues.


I'm talking to the maintainers of the other Redis OM Clients for different languages to make sure that when we do add booleans to Python there's a common approach where possible.


Which version of iOS are you testing with? Also, could you try out the demo page of this repo on the iOS device you're testing with and see if that works?

You might want to look through some of the previous issues here regarding iOS, if you haven't already. There might be some information in there you would find helpful.


Thank you for your reply. Using iOS 15.4 and latest cordova-ios@6.2. Tested with older cordova-ios versions, too.
The demo page works in the browser of the phone. I read all I could find about it. Been struggeling with it a couple of days now.


I'm not familiar with Cordova.

I would suggest putting together a test app using that tool with just a play button and a hardcoded stream URL and see if that works. Essentially to try narrowing down the issue if one exists in the library

There are also a few parameters you might for `IcecastMetadataPlayer` that you could try such as changing the `playbackMethod` and see if you get any more feedback from that.


Unfortunately the same. I build a very minimalistic app. Stream loads, no play. As it is working in browser I think its because of my setup with Cordova. Maybe somewhen somebody might post a solution here.


After incorporating feedback from the community through maintenance iteration 10, the proposal is being updated to move this requirement from a SHOULD to a MUST.

The DSB now proposes that the standards are updated to specify that:

_Data Holder Brands MUST ignore unsupported authorisation scopes presented in the SSA for the creation and update of Client Registrations._

Regarding changing the FDO to 15th September 2022, further discussion is required to consider having an FDO less the 6 months out. Changes to the FDO will not be considered as part of maintenance iteration 10 however, will be considered for maintenance iteration 11.

The DSB invites the community to comment on this change


This is still happening.

Btw found URL Maybe we need to contribute a PR.


@vankop Could you please share some input on how to use babel on runtime chunk? I tried it didn't work for runtime chunk. Appropriate your help on this matter


not sure about correct config.. I think `@babel/preset-env` will be enough


Is the issue saying we're trying to use the node SDK in the electron renderer?


Yeah in the renderer we get the `setTimeout` variant from `DOM` and not `node.js`. I was actually looking into whether we could simply shim the `unref()` method, but it didn't seem to easy, unless we would overwrite the entire `setTimeout` method for everyone.


Maybe we should be using the web SDK in the renderer then? We use the web telemetry reporter in the `/browser/` telemetryService so I'm surprised that we're using the node one in the renderer.


Yeah that sounds reasonable. Though the fact that the shared process is a browser window is a bit of a debt issue, eventually we probably want to go away from running it as hidden window and use a pure node.js process once URL landed.

Given that, maybe we should just ignore the issue for now until we get to a real node.js process.


@cowtowncoder

use with jackson-bom version `2.12.6.1.20220326`

the version for the bom here looks incorrect, should be `2.12.6.20220326` ?


@touhidurrr this should be fixed via #759, can you let us know if the webpack plugin works as expected?


Dunno actually. Already moved to `esbuild` cause the build time is much faster than webpack. 😅


@vankop still not working with babel loader as per my understanding the runtime is not loaded via loaders so it's not going through the babel loader.

I was expecting, Webpack would generate code according to the target option specified in the config in all aspects and seems like It is not.

Shouldn't this be a major bug in webpack as It's no honoring the target set by the config when it's generating the webpack related code (runtime/helpers)?


@williamjacobszoon not `babel-loader`, just use babel on output ( only for es5 )

______

better use `import()` instead of top-level-await


It does. By in case of top-level-await it is not possible in current design ( transform async to promises ), so you have 2 options URL


@vankop I'm kind of disappointed see your response. because non of these things are explained in the documentation about using externals will cause the output to be not compatible with es5. I'm getting to know all these things at the final phase of our application development now I have to restructure the whole app again 😭


yeah, sorry about this.. changing `import x from "x"` to `import("x")` should not be a big problem.


I try to reproduce that today, but it has been fixed in newer version. This issue still exists, which means the feature `externals script` cannot run when your browser does not support async function. Here is my test code:

// webpack.config.js
module.exports = {
 mode: 'development',
 target: ['web', 'es5'],
 externalsType: 'script',
 externals: {
 react: 'React@ URL
 'react-dom': 'ReactDOM@ URL
 },
};

webpack: 5.72.0
node: 16.14.2
browser: IE 11


@aoisummer Thanks for the update.

I just found out there is separate issue raised for top-level await generation on es5 target.

Compile top-level await to ES5 #11874

 URL


Hi, unfortunately it only updates MAL after you have actively watched something.
That being said I will add this to the main project as a possible addition later on down the line, as it seems to be a good feature to add to the plugin.


we discussed this internally so.. supporting promises on webpack side would require huge code transformation, that webpack in current version can not perform. There is a PR to add warning in case when output environment does not supports async/await.

As user you can:

- build for environment that supports async/await
- don't use top-level-await


Yea but I think it can be closed, the frontend urgently needs a complete rewrite as the technology it uses is no longer supported and bugs/security issues will stay open. If that is not done the problem will keep existing for forever.
If the frontend gets rebuild this issue will not be relevant anymore.


Since we now have experimental support in the feature branch we should probably add some documentation on how to use it. I think adding a new module in the wiki sidebar would probably be the best solution with a big experimental warning on top.
Another approach would be to wait with the documentation until the feature is stable.
How would you like to handle this?


@vankop Just wanted to make sure that this issue will be fixed in a future version of webpack right? adding a warning is a temporary solution I guess.


I don't think documentation is crucial at the moment. Especially since any settings inside the tray module may well change again. We should probably hold off writing documentation until at least the config settings are stable.


@derrickmehaffy We are not using `strapi-middleware-cache` will be removing that from dependencies. did you mean I should have same versions for `@strapi/plugin-graphql` ,`@strapi/plugin-i18n` ,`@strapi/plugin-sentry` and `@strapi/strapi`


Again, the problem is that a function deferred by `vim.schedule(..)` will still be executed while operator is pending. We could safely skipping rendering, but when it comes to kill or closing, this workaround doesn't seem to work because it will lead to resource leakage or weird race condition. Fidget cannot easily tell when it is really available, despite the use of `vim.schedule`.

I think this requires an upstream fix, so no good solution for now. For the time being, I think #69 can be still merged to avoid most of E523 errors, and we can later improve the remaining case when fidget is trying to close.

@j-hui Any thoughts?


@rockyzhang24 I rewrote the logic and we can ignore the error when fidgets would be closed as well. This will make the annoying error not happen any more. However it cannot 100% eliminate "ghost chars" as I explained earlier; but we have some workaround like `:FidgetClose` so this should be usable enough.


@wookayin Thank you so much for digging deeper into this issue and trying to come up with solutions. It looks like we have to wait for the upstream fix to make this issue solved completely. Could you please open an issue upstream? If I do, I'm afraid I cannot describe it clearly.


Could you still provide a short example of how to use it? I would like to try it.


Yes all packages prefixed with `@strapi/` should have the same version.


@strapi/developer-experience / @strapi/expansion I'm not sure the root cause on this and it could be either package so I've set it to both of your projects for now.


Already ideally admins (and others) will provide advice in public via an annotation.

Exposing per-request tags URL would enable the use of a tag to flag a request for help. Ideally we'd have a button to add the tag, and a page listing requests on which help has been sought.

Related:

Consider presenting the "next steps" / refusal advice publicly #6286

Previous discussion on offering help in public via a mailing list, an option it was decided not to pursue:

 URL


Often users who write to the support team seeking advice have not classified their response (or they've classified it as needing the attention of the team) whereas if they had classified it eg. rejected or awaiting a response the system would have automatically offered advice.

Doing more to encourage classification could prevent users seeking human help:

 URL


@flavioislima I think this can be closed, issue seems to be solved.


Imo this is a use-case for URL If Juju had anything like relation config, we could avoid a middleman configuration charm, but alas :-)


@voxpelli whats your thinking about removing outdated packages as mentioned by @Divlo and @Tofandel.
This currently seems to block the final shipment of v17?


I'm 👍 on that, though I want to go through them to see if the failures are because of an unintended change or because of eg. lack of maintenance on their path.

I'll try to find time soon to look at what eg. @Tofandel summarised here. Main blocker from my side has been my time 🙈


This issue was in the inbox of the platform team for some reason. However, there is not much the platform team can do here. Much rather
* the workspace team would need to set up a cluster in the desired region
* also, on the WebApp side newly starting workspaces would need to be routed to the new cluster based on latency. Not sure if this falls into the area of team workspace or team WebApp.

I'm moving the issue to the inbox of the workspace team so that they can handle prioritization/planning.


For anybody struggling with this issue using pnpm, I fixed by adding an override to my root package.json:

"pnpm": {
 "overrides": {
 "ethereumjs-abi": " URL
 }
 }

Reference: URL


The same on MacOS Monterey:
<img width="294" alt="Screenshot 2022-04-19 at 21 23 12" src=" URL
Common terminal on left, Warp on right.


As d799769188529abc6cbf035a10087a51f7832b6b also resolves #1594, I have started a thread about whether or not applying that change to stable is appropriate.


We should have a concurrency bound in the queue. This means how many tasks should be executed at the same time. By default unbounded meaning all tasks gets executed immediately without waiting to be done.

For IO bound tasks, you might as well have unbounded concurrency. For CPU-bound it can be sent to the web worker pool which is bounded by core count. Battery usage optimisation may also affect our limit too.


Glad it's not just me ;-) - the blurry fonts make it unusable for my eyes


Hi @SujayPrabhu96, thanks for writing in! To effectively investigate your issue we would need a little bit more information. Can you share which versions of Koa, Strapi, and the sentry SDK you are using and how exactly you set up the Sentry SDK (ie, how you configured the `Sentry.init()` call)?


Hi @lforst,
I have updated the versions in the issue. As Strapi is built on top of Koa, it is not installed separately.
Regarding setup I have created custom middleware `sentry` in Strapi to make `Sentry.init()` call.

For reference here is my PR: URL
Configured Sentry using sentry middleware


I'm seeing in the repository you linked that you have old Sentry dependencies in your lockfile: example

The particular version you have, has a bug that was reported in URL and got fixed in URL

Can you try and update those dependencies to at least version 6.3.2 and report back whether that fixed the issue? By the way, I strongly recommend using the same versions across all Sentry SDK dependencies, as having different versions might introduce unknown behaviour.


Feedback we have received from the ACCC indicates they will not be able to specify a delivery date for the proposed solution and an interim solution will be required. As highlighted from ACCC's feedback, a mandatory `brandId` will not be available in the short to medium term.

Feedback from industry during MI 10 has highlighted that an interim solution that provides a mandatory unique identifier in addition to the `brandId`, would meet the need to reconcile each record until a complete solution can be delivered.

In order to give the ACCC flexibility in delivering the full solution, provide partial value to API clients, and to simplify reading of the standards, the DSB has decided to propose an interim solution.

## Proposal

Based on the feedback received from stakeholders, the DSB proposed the following:

1. `brandId` moves from mandatory to optional
2. To enable clients to reconcile data holder brand records from this API with those retrieved in previous requests, an interim identifier (`interimId`) is proposed. This will allow for clients to use the following logic:
a. IF the record includes a `brandId`, use `brandId` as the record identifier ELSE use `interimId` as the record identifier
b. If in a future request the `brandId` is populated, move the record identifier from `interimId` to `brandId`
3. For each record, when `brandId` is finally populated, the `interimId` will be maintained for a minimum of 1 month prior to being retired.

This logic will provide a transition period, allowing clients to migrate records from referencing the `interimId` to the `brandId` in anticipation of `brandId` becoming the mandatory identifier. Once `brandId` becomes the defacto standard identifier, `interimId` can be phased out per record after the transition period of a minimum of 1 month has passed.

**Interim Solution (V1) - targeted latest dependency date of 01st October 2022**
_Note that this solution is intended to be a temporary solution until the ACCC is able to deliver the complete solution._

Name | Type | Required | X-Conditional | Description
-- | -- | -- | -- | --
brandName | String | true |   | Name of the data holder brand hosting the public endpoints
brandId | String | false | true | ID of the data holder brand hosting the public endpoints.  To be used to uniquely identify the record and not to be reused
interimId | String | false | true | Interim ID of the data holder brand hosting the public endpoints. This is to be used to uniquely identify the record when brandId is not populated and is not to be reused
publicBaseUri | UriString | true |   | Public endpoints base URL
logoUri | UriString | true |   | Data Holder Brand logo URL
industries | [string] | true |   | The industries the Data Holder Brand belongs to. Please note that the CDR Register entity model is constrained to one industry per brand which is planned to be relaxed in the future.
lastUpdated | DateTime | true |   | Time when the record was last updated
abn | String | false |   | Australian Business Number for the organisation
acn | String | false |   | Australian Company Number for the organisation
arbn | String | false |   | Australian Registered Body Number. ARBNs are issued to registrable Australian bodies and foreign companies

**Complete Solution (V2) - targeted release to be assessed in a future maintenance iteration**

Name | Type | Required | Description
-- | -- | -- | --
brandName | String | true | Name of the data holder brand hosting the public endpoints
brandId | String | true | ID of the data holder brand hosting the public endpoints.  To be used to uniquely identify the record and not to be reused
publicBaseUri | UriString | true | Public endpoints base URL
logoUri | UriString | true | Data Holder Brand logo URL
industries | [string] | true | The industries the Data Holder Brand belongs to. Please note that the CDR Register entity model is constrained to one industry per brand which is planned to be relaxed in the future.
lastUpdated | DateTime | true | Time when the record was last updated
abn | String | false | Australian Business Number for the organisation
acn | String | false | Australian Company Number for the organisation
arbn | String | false | Australian Registered Body Number. ARBNs are issued to registrable Australian bodies and foreign companies


This approach look fine. Key to success is to deliver the interim solution quickly. Thanks


A generic Queue class has been implemented here: URL

This queue is not persistent, or a priority queue, however, it is designed to be a generic queue that can eventually be used in all places that require this functionality (including the Discovery Queue). The generic Queue can be refactored to meet this issue and URL at some point in the future, potentially incorporating the DB.


Folks, does it have to do anything with URL

Strapi v4 by default adds sentry 6.3.0 to yarn lock file which has some bugs. Can we update sentry version to 6.3.2 as mentioned URL


The ACCC reiterates it’s previous commentary that if the solution the ACCC has previously proposed is not accepted then we’ll be unable to commit to a 1st of October 2022 delivery date. The ACCC does not support the inclusion of an `interimId` for the same reason it does not support a mandatory `brandId`, the additional solution delivery and operational effort. If the ACCC’s proposed solution cannot be agreed upon, the ACCC suggests deferring this GitHub issue to the next Maintenance Iteration so that the alternative options that the ACCC proposed on the 23rd March can be discussed.


I think with these changes to include the HttpClient via the constructor, then we don't need to do the HttpClientHandlerFactory stuff, and if someone wants to use that stuff, they can and we don't need to be involved.
(and we get the other unit testing benefits too as I've mentioned in the PRs.)


The HttpClientFactory creates and manages HttpClient instances and takes an available message handler from the pool. The HttpClient should be included in the constructor rather than the factory, so the consumer can reuse the same HttpClient.


@kodol73 : could you share an image of the text you are trying to recognize? I have been trying text recognizer and it works for me.


Here you have some screenshoot of the example app in iOS and it is working.

IMG_0050

IMG_0051


We're doing this with the URL project, WIP for full support of what Gulp Extensions does.


FYI this does still seem be happening with react-native 0.68.1 and react-native-reanimated 2.8.0. I really appreciate all the hard work you guys are doing!


This sounds a _lot_ like hostage taking by the regulator, perhaps if the ACCC engaged the community earlier it wouldn't be facing timeline issues. October is 6 months away, that's the time accepted by all the other participants in the ecosystem, I find it pretty hypocritical for the ACCC to enforce FDO obligations, request shorter timelines on Participants and then not accept the convention for its own delivery.

Is the ACCC _honestly_ suggesting that these records _don't_ already have a database identifier associated with them? If there isn't an identifier already present how else would the ACCC be administering the records? Hand coding them? Smoke signals from some tower in Canberra? I thought the `interimId` proposal was to allow for the id to change which seems to eliminate any architectural reason to oppose it.

I was at the last maintenance call and I don't believe ACCC bothered to show up, perhaps it should have. If the ACCC is going to throw its toys out of the pram whenever it doesn't get what it wants then perhaps the Minister should be called in to resolve _who exactly is responsible_ for Register related Standards since it seems increasingly ambiguous.

It isn't a reasonable nor sustainable solution for non-government technical implementers trying to plan activities based on guidance from multiple government bodies on delivery timelines that are, in the Register case, quite opaque.


Just want to highlight again that this API is already close to 3 years late - i.e. it should have been delivered on 1-Jul-2019 when the first PRD APIs were launched. Waiting another 6 months for this API really isn't an acceptable outcome for the industry or the success of the CDR.

This is a very simple API and shouldn't take more than a week to build. We therefore request that it be priorities and delivered within the next 4 weeks. Happy to have a conversation with the ACCC (assuming they are responsible for building the API) if technical advice is required.

Regarding the `interimId`, the suggestion above to use the ACCC's existing database identifier makes sense, assuming they have one. If the existing database has been implemented without a unique identifier (e.g. in an Excel spreadsheet), then the ABN should be a sufficient proxy - i.e. a company may rebrand, but they don't normally change their ABN. Otherwise, it would be very simple to add an 'interimId' the the existing database.


After a long time, is there still no progress on this issue?


Should stay open. Still some updating needed. See also #2398.


@aallan
Are you simply updating the vlc and omx examples according to the version?


OMX Player no longer works under Bullseye. All the examples using it in the documentation need to be replaced with an equivalent invocation for VLC (or other relevant software), see #2398 which is the linked issue.

However this issue is the more general "other things that Bullseye broke" issue. There are some other things beyond the OMX Player issue that haven't yet been fixed.


If there is something to be done externally, I would be happy to contribute.


Yes we're still working on this issue, a support ticket has already been sent to Algolia.


i have a same problem, it detect wrong text when run on IOS flutter


Renamed this issue to the general idea of non-blocking task management. It now has to solve for discovery, nodes management in terms of setting nodes, pinging nodes and garbage collection, as well as in relation to:

* #354
* #349
* #345
* #328
* #297

There's a relationship between the queue design and the `EventBus` system, as well as our `WorkerManager`.

Most important is for us to develop a `Task` abstraction. It can be a `class Task`, that represents a "lazy promise". Promises in JS are strictly evaluated, while these tasks will need to be lazily evaluated. Then our task management system can convert our lazy tasks to strict promises (which represents futures). More background info here: URL

Our task manager will need to have configurable:

* Concurrency limit - indicates the bound on the pool of currently executing tasks (can be 1 to unbounded/infinite)
* Executor - choosing to execute by Node's event-loop, or by passing it into the `WorkerManager` to be executed in a separate thread or core, the former should be used for IO-bound tasks, the latter should be used for CPU-bound tasks. This could be specified by the task creator, rather than the task manager itself.

Stretch goal is to also incorporate "time/calendar-scheduling" so that tasks can be executed at a point in time like cron.

Interaction between `EventBus` and task manager may be considered. The event bus is about communicating changes between domains, but the task manager is the one actually executing the tasks.

Tasks can be:

* Re-ordered or reprioritised or given priorities
* Can be observed for success or failure
* Can have errors handled
* Can be cancelled using our design for abort signal, and have their real side-effects cancelled
* Can be monitored for progress
* Can be persistent - backed by leveldb

This rabbit hole for this goes deep. So we should make sure not to feature creep our non-blocking task queuing needs.


Also to clarify, we are not creating a "generic distributed job queue", that's the realm of things like redis queue and URL There's so much of this already. We just need something in-process relative to Polykey.


It seems that some images of text are recognized correctly, but some other images of text are corrupted
I just tried with example app, but has the same result

The result of recognizing below image is corrupted
Please check with the below image

IMG_1391


Same issue here.

Left warp, right iTerm2:
<img width="1438" alt="image" src=" URL


@scleaver @deanmarcussen it might be interesting for you what we've progressed with Node.js Extensions here. While we don't have the full functionality of Gulp Extensions yet, we actually have an NPM script-containing NuGet package working!


@kodol73 : I tried your image with the example app and so far it does not look corrupted to me. It looks pretty much good to me.

IMG_0052


and sorry for weird build location i forgot to CD back before building when i tried to use a KDE plugin earlier.


You tried it on iPhone, right?
Can you please let me know your phone model and iOS version?


I tried with both an iPhone 11 and iPhone 6S, both with iOS 15 and I am using Xcode 13.3


Along with the configurable concurrency limit and executor, I think we should have an interface for the queue as well. Depending on the situation we may need just a simple queue, a priority queue, a persistent database queue like discovery uses, etc etc...
So far as the `Queue` cares it only needs to support `push` and `shift`. So we can make the `Queue` a generic class and pass it any implementation we want for storing the queue so long as it extends the interface.

It shouldn't be too hard to make the change. We just need to decide if this degree of control is desired. I can see a need for it though.


This all works now; we just need to add some tests and bump the minimum required version.


We shipped an **experimental** support of indexing for IntelliJ IDEA using Prebuilds.


I'll need some extra information. What DE are you using?
Could you please run it with GDB attached and give a backtrace of where the segfault is?


I am using gnome on x-11 as my DE, running on fedora. pardon me for asking but how do i run it with GDB and backtrace it?


Came here for the same. Line height needs to be configureable and also it would be nice to be able to get some of that iTerm 2 anti aliasing.🤓


After some discussion we decided that the API shouldn't be there in the first place, and that it should be removed. Instead developers should rely on the regular validation, or set custom pattern validation, and let users correct their changes.
Meanwhile we can deprecate the existing method, and add a note to the JavaDoc that it has no practical use for email field.


I agree, but then what's the point of having an EmailField - what does it offer on top of a regular TextField?


it's weird, I just upgraded iOS to 15.4.1, but the same result
It generated corrupted text like the following with the image

T
T
ooo
5

Just in case, I test with google_ml_kit 0.8.0 because example app uses google_ml_kit

Please help me to solve this issue


Not that I would want to make promises, that I will create a MR any time soon. But I at least implemented some of the minor changes as well as zip_view in URL
I could use some help with:
- 5.1 & 5.2: Constructors and assignment operators for `std::tuple` and `std::pair`
- 5.4: Not sure which changes this requires
- 5.6: Is implemented as described in the paper. But are there functions whose noexceptness should be strengthened?


Hello am looking to build for the pico on Mac. There is support for arm-eabi-gcc on macOS with a package from Homebrew . but it only supports gcc 11. Would GCC 11.3 support be possible? Thanks in advance.


It probably would work fine with pico-arduino but isn't something I can guarantee or test. You'd need to make adjustments to the platform.txt to use the system `arm-eabi-gcc` instead of the packaged one.


I had this same issue, but resolved it on iOS.

Still testing android but I am passing the File from camera plugin cameraController.takePicture() as the InputImage.fromFile(imageFile) and looking at text it had almost no relevant data, and any data it did have was like:
A
ooD
TM

After removing the google_ml_kit plugin, and replacing it with only the google_mlkit_text_recognition: ^0.2.0 it works fine. No idea why to be honest, but specifying just text recognition instead of the umbrella plugin resolved. Would like to hear some details on this if there are any.


Thanks @codyfilatov for the suggestion.

Do you still have issues with Android? both platforms are working okay?

@kodol73 : give it a try


Both platforms are working okay now.
Although I did not have this issue with Android to begin with.

The only issue I am having now on iOS is the orientation of my image when processing, it thinks it is in landscape when it is in portrait, so the bounding boxes are messed up, does not happen on Android. My image does not have any exif orientation data. I would be nice to have if no orientation data exists to predict based on the height/width, looks like it defaults to Landscape if no data exists. But that's another issue I can figure out.

Hope OP resolves issue with the dependency change.
Thanks


@codyfilatov: once you figure the orientation out, share here or create another issue if necessary. I have seen issues with different orientations as well.


I just had the same problem with the latest GitHub Desktop 3.0 and manually solved it following the advice from @CaptainJackey. This is an active bug and shouldn't be marked as closed.


Adding a "me too". I am considering Gitpod for my team in Singapore, Thailand and the Philippines - but the ping time to EU/US makes it extremely painful (I'm getting between 200-400ms and I am on gigabit fibre).


I just tested the newly released version of google_mlkit_text_recognition, 0.2.0, nothing else changed
The issue doesn't appear any more

Thanks


Sharing here just as a note.
The orientation issue was caused by no EXIF orientation data on the image in iOS taken from the camera plugin takePicture function. Since the image file had no EXIF orientation data I assume the text regognizer (and barcode scanner) was returning odd (not incorrect) values.

The values did not translate as expected as when I set a Container DecorationImage as the same file the image is displayed correctly as taken, but the values were printed mirrored and counter clockwise consistently.

After using the image package to set the EXIF orientation data to 1 and rewriting the bytes to a new file, then passing that file to MLkit the boundingBox values were as expected.


XFile imageCaptureXFile = await this.cameraController!.takePicture();
File imageFile = File(imageCaptureXFile.path);
this.imageFile = imageFile;
img.Image? image = img.decodeImage(await imageFile.readAsBytes());
if(image == null){
 Util.showToast('Image was not found.');
 this.isConfirming = false;
 this.imageFile = null;
 setState(() {});
 return;
}
if(!image.exif.hasOrientation){
 print('Baking orientation into image...');
 image.exif.orientation = 1;
 File orientatedImageFile = File((await getTemporaryDirectory()).path + Uuid().v4() + '.jpg');
 await orientatedImageFile.create();
 await orientatedImageFile.writeAsBytes(img.encodeJpg(image));
 await imageFile.delete();
 imageFile = orientatedImageFile;
 this.imageFile = orientatedImageFile;

 image = img.decodeImage(await orientatedImageFile.readAsBytes());
 if(image == null){
 setState(() {});
 return;
 }
}

This is what I use for my use case. Keep in mind I only want portrait.
I use the package:image/image.dart . Ignore the bad code, I'll clean it up later.

TextRecognizer textDetector = TextRecognizer(script: TextRecognitionScript.latin);
RecognizedText recognisedText = await textDetector.processImage(InputImage.fromFile(imageFile));


Same Problem here.

I am using the example app provided by the package author.
It works fine in portrait mode but if I rotate the device all the API's stop working or acting malfunction.

To be specific, I am using Samsung Galaxy Tab A7 SM-T505 right now and it is not working OK.

To test if there is a problem in imageOrientation I just added a log print over this function inside _processCameraImage:

...
final imageRotation = InputImageRotationValue.fromRawValue(camera.sensorOrientation) ?? InputImageRotation.rotation0deg;
 print('orientation: ${imageRotation.rawValue}');
...

and find that it is always 90 even if I rotate the device it will always detect my device in landscape mode.
I don't know if I am testing and point in correct direction but I think it is something related to the cameraOrientation which brings this bug.

I am using the last version of camera and recent update of ml_kit.

google_ml_kit: ^0.10.0
 camera: ^0.9.4+20


This issue has to do with the orientation of your device/camera/inputImage. The example app is not production code and only works on portrait mode. Feel free to modify the example app to support landscape, but you need to edit this method: URL

I have not played that much with the orientation and metadata, but you need to create the correct instance of `InputImagePlaneMetadata` and `InputImageData` to pass to `InputImage.fromBytes`.

Once you figure it out come back and share the fix here or create a PR, contributions are always welcome.


Another comment in another discussion that might help you to resolve your issue is here: URL


Closing this issue.

Fix: google_mlkit_text_recognition instead of `google_ml_kit`.

More details here: URL

Moving `InputImage` and `InputImageRotation` issues to: URL


As you mentioned earlier, I believe it is something related to camera package which cannot find the correct aspect ratio after orientation change.
To be exact, the imageProcess is working on something different than what you have in cameraPreview because, if you move the camera at the edge, where the barcode is merely outside the cameraPreview, you can see that it can detect the barcode correctly. SO, I think the image which is processing has different data than what we have in the cameraPreview.

I hope I could investigate further to see if I can match the zoom level of Landscape and Portrait in cameraPreview to see if the issue is resolved or not.

Any suggestion is highly appreciated.


From my view the current culprit is this widget from camera_view.dart:

` Widget _liveFeedBody() {
 if (_controller?.value.isInitialized == false) {
 return Container();
 }

 final size = MediaQuery.of(context).size;
 // calculate scale depending on screen and camera ratios
 // this is actually size.aspectRatio / (1 / camera.aspectRatio)
 // because camera preview size is received as landscape
 // but we're calculating for portrait orientation
 var scale = size.aspectRatio * _controller.value.aspectRatio;

 // to prevent scaling down, invert the value
 if (scale [

 Transform.scale(
 scale: scale,
 child: Center(
 child: _changingCameraLens
 ? Center(
 child: const Text('Changing camera lens'),
 )
 : CameraPreview(_controller),
 ),
 ),
 if (widget.customPaint != null) widget.customPaint,
 Positioned(
 bottom: 100,
 left: 50,
 right: 50,
 child: Slider(
 value: zoomLevel,
 min: minZoomLevel,
 max: maxZoomLevel,
 onChanged: (newSliderValue) {
 setState(() {
 zoomLevel = newSliderValue;
 _controller.setZoomLevel(zoomLevel);
 });
 },
 divisions: (maxZoomLevel - 1).toInt() < 1 ? null : (maxZoomLevel - 1).toInt(),
 ),
 )
 ],
 ),
 );
 }
`


We could start by exposing, and perhaps allowing the public to submit, tags relating to poor public body performance:

 URL

There is a potential moderation issue though.


I thought a bit about the remaining issues and I have some questions/comments.
1. Hiding the tray window. Was this already implemented? I'm not really sure which position you mean. The one we set in the context or the global position(left,center...)? When are the modules hidden?
2. `tray_postition = adaptive`: Is there a way to check in the tray_manager if the tray module was instantiated? I added `adaptive` because I didn't know how to figure out when no tray module was instantiated and therefor didn't know when not to set left, right, center.
3. pushed off bar: Has there been some prior work into something similar like this(Maybe with text)? Otherwise I imagine that this is going to be really difficult to implement since we never know in the renderer how much content will be added before or after the tray and how wide the tray is. I can't think of a way to approach this.
4. How do you want to manage the configs? I can think of two approaches. First would be to keep the config handling in the tray_manager and just read the config from the tray module instead of the bar. This is a bit messy. The other option would be to move the config handling to the tray module. This is a much cleaner solution but then it's quite hard to get the config settings to the tray_manager(Maybe with a signal?) since they are completely separate right now.

Right now a lot of logic is split between the tray_manager and the tray module with no way of them interacting(Besides signals). This complicates a lot but I can't think of a way to simplify this short of moving the tray_manager completely into the tray module. I'm unsure how "clean" we should implement these things since some(like the tray_position) will be removed later which cleans up a lot of code.


I didn't formulate that clearly, I meant whether the dispatch called `apply_tray_position` with a valid position. Tray hiding wasn't implemented before but since modules can be hidden, the tray should probably support it as well.
What currently happens, is that if the module is hidden, no `%{Pt}` tag is emitted, so the tray position isn't updated and the tray just stays wherever it was in the previous render cycle.

Modules can be hidden using module actions (for example using polybar-msg).

The tray can't really check this. But what we can do, is pass this information from the controller to `bar::start` which then passes it to `tray_manager::setup`. The controller can check this in the loop where it creates the modules.

For text that doesn't fit onto the bar, we render a fading out gradient at the end of the bar when the left, right, and center blocks are placed on the bar:

 URL

However, for the tray, my idea was to not have this logic in the renderer but in the tray itself.
The tray manager knows how wide the tray and the bar are, so when it receives the `tray_pos_change` signal, it can calculate whether the new position will place the tray window (partially) outside of the bar. And instead of hiding parts of the tray window when it goes outside of the bar, we keep it at the right end of the bar instead of letting it slide off. The calculation for the tray position would look something like this:

tray_pos = bar.x + max(0, min(tray_pos, bar.w - tray_width))

I think we should go with the first option, the tray manager should be responsible for loading its own configuration options. This could be achieved by passing the name of the tray module to `tray_manager::setup`.

---

If we didn't have to still support `tray-position = left|center|right`, we would create the tray manager instace inside the tray module and would not have any of these issues about communicating information between components. But even if it is going to be removed at some point, it will still be with us for some time, so we shouldn't just be sloppy here.


You will need to run the software with gdb, just like you'd do with sudo:

gdb ./wallengine /home/luke/.local/share/Steam/steamapps/workshop/content/431960/2677437153/

That should give you a command prompt, if you write start and press enter the software will run as normal, once it hits the segfault you'll be back to the gdb's command prompt.
You can use the command "bt" to get some better information of what happened.


I tried adding a test to check for python 3.9 syntax but apparently libcst has not yet added syntax checking for this python version. python39syntax


I tried adding a test to check for python 3.9 syntax but apparently libcst has not yet added syntax checking for this python version. URL


I tried adding adding a test to check for python 3.9 syntax but it failed. Apparently libcst has not yet added syntax checking for this python version. URL


There seems to have been some sort of line height related issues with Warp v0.2022.04.25.09.59.stable_03, although it is still not configurable


so far i have installed 2 sets of debug packages and it is asking me for more:
[luke@fedora build]$ gdb ./wallengine /home/luke/.local/share/Steam/steamapps/workshop/content/431960/2677437153/
GNU gdb (GDB) Fedora 11.2-2.fc35
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later < URL
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
< URL
Find the GDB manual and other documentation resources online at:
 < URL

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./wallengine...

This GDB supports auto-downloading debuginfo from the following URLs:
 URL
Enable debuginfod for this session? (y or [n])
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
(No debugging symbols found in ./wallengine)
"/home/luke/.local/share/Steam/steamapps/workshop/content/431960/2677437153/" is not a core dump: file format not recognized
(gdb) start
Temporary breakpoint 1 at 0x4c4276
Starting program: /home/luke/wallengine/build/wallengine
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Missing separate debuginfo for /lib64/libOpenCL.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/8b/1a5b9feb2f73098a0b3cc1fe1b7da5b32c1015.debug
Missing separate debuginfo for /lib64/libwbclient.so.0
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/7e/4d98ae1b739d161227923719ff0c12e2a4cf2b.debug

Temporary breakpoint 1, 0x00000000004c4276 in main ()
Missing separate debuginfos, use: dnf debuginfo-install LibRaw-0.20.2-3.fc35.x86_64 SDL2-2.0.20-1.fc35.x86_64 SDL_mixer-1.2.12-23.fc35.x86_64 bzip2-libs-1.0.8-9.fc35.x86_64 cairo-1.17.4-4.fc35.x86_64 cyrus-sasl-lib-2.1.27-14.fc35.x86_64 fftw-libs-double-3.3.8-11.fc35.x86_64 fontconfig-2.13.94-5.fc35.x86_64 freeglut-3.2.2-1.fc35.x86_64 freeimage-3.19.0-0.7.svn1889.fc35.x86_64 freetype-2.11.0-3.fc35.x86_64 fribidi-1.0.11-3.fc35.x86_64 gdk-pixbuf2-2.42.6-2.fc35.x86_64 glfw-3.3.4-3.fc35.x86_64 glib2-2.70.5-1.fc35.x86_64 glibc-2.34-30.fc35.x86_64 gmp-6.2.0-7.fc35.x86_64 gnutls-3.7.2-3.fc35.x86_64 gsm-1.0.19-6.fc35.x86_64 harfbuzz-2.9.1-1.fc35.x86_64 ilbc-1.1.1-21.fc35.x86_64 imath-3.1.5-1.fc35.x86_64 jasper-libs-2.0.33-1.fc35.x86_64 jbigkit-libs-2.1-22.fc35.x86_64 jxrlib-1.1-17.fc35.x86_64 keyutils-libs-1.6.1-3.fc35.x86_64 krb5-libs-1.19.2-6.fc35.x86_64 lame-libs-3.100-11.fc35.x86_64 lcms2-2.12-2.fc35.x86_64 libGLEW-2.1.0-10.fc35.x86_64 libICE-1.0.10-7.fc35.x86_64 libSM-1.2.3-9.fc35.x86_64 libX11-1.7.3.1-1.fc35.x86_64 libXext-1.3.4-7.fc35.x86_64 libXrandr-1.5.2-7.fc35.x86_64 libXrender-0.9.10-15.fc35.x86_64 libXxf86vm-1.1.4-17.fc35.x86_64 libaom-3.2.0-2.fc35.x86_64 libbluray-1.3.1-1.fc35.x86_64 libchromaprint-1.5.0-3.fc35.x86_64 libcom_err-1.46.3-1.fc35.x86_64 libdav1d-0.9.2-1.fc35.x86_64 libdrm-2.4.110-1.fc35.x86_64 libgcc-11.3.1-2.fc35.x86_64 libgcrypt-1.9.4-1.fc35.x86_64 libglvnd-1.3.4-2.fc35.x86_64 libglvnd-glx-1.3.4-2.fc35.x86_64 libgomp-11.3.1-2.fc35.x86_64 libgpg-error-1.43-1.fc35.x86_64 libicu-69.1-2.fc35.x86_64 libidn2-2.3.2-3.fc35.x86_64 libjpeg-turbo-2.1.0-3.fc35.x86_64 libldb-2.4.2-1.fc35.x86_64 libmodplug-0.8.9.0-13.fc35.x86_64 libmount-2.37.4-1.fc35.x86_64 libogg-1.3.5-2.fc35.x86_64 libopenmpt-0.5.15-1.fc35.x86_64 libpng-1.6.37-11.fc35.x86_64 librsvg2-2.52.8-1.fc35.x86_64 libsmbclient-4.15.6-0.fc35.x86_64 libssh-0.9.6-1.fc35.x86_64 libstdc++-11.3.1-2.fc35.x86_64 libtalloc-2.3.3-2.fc35.x86_64 libtdb-1.4.4-3.fc35.x86_64 libthai-0.1.28-7.fc35.x86_64 libtheora-1.1.1-30.fc35.x86_64 libudfread-1.1.2-2.fc35.x86_64 libunwind-1.5.0-1.fc35.x86_64 libuuid-2.37.4-1.fc35.x86_64 libva-2.13.0-3.fc35.x86_64 libvdpau-1.5-1.fc35.x86_64 libvmaf-2.1.1-3.fc35.x86_64 libvorbis-1.3.7-4.fc35.x86_64 libvpx-1.10.0-2.fc35.x86_64 libxcb-1.13.1-8.fc35.x86_64 libzstd-1.5.2-1.fc35.x86_64 lz4-libs-1.9.3-3.fc35.x86_64 mesa-libGLU-9.0.1-5.fc35.x86_64 mpg123-libs-1.26.5-2.fc35.x86_64 nettle-3.7.3-2.fc35.x86_64 openexr-libs-3.1.5-1.fc35.x86_64 openjpeg2-2.4.0-5.fc35.x86_64 openpgm-5.2.122-27.fc35.x86_64 openssl-libs-1.1.1n-1.fc35.x86_64 pango-1.50.4-1.fc35.x86_64 pixman-0.40.0-4.fc35.x86_64 rav1e-libs-0.5.0-1.fc35.x86_64 sdl12-compat-0.0.1~git.20211125.4e4527a-1.fc35.x86_64 speex-1.2.0-9.fc35.x86_64 srt-libs-1.4.4-1.fc35.x86_64 svt-av1-libs-0.8.7-2.fc35.x86_64 twolame-libs-0.3.13-18.fc35.x86_64 vapoursynth-libs-51-4.fc35.x86_64 xz-libs-5.2.5-9.fc35.x86_64 zlib-1.2.11-30.fc35.x86_64 zvbi-0.2.35-15.fc35.x86_64
(gdb)


ok after installing 3rd and 4th set of packages this is the output after start

(gdb) start
Temporary breakpoint 1 at 0x4c4276
Starting program: /home/luke/wallengine/build/wallengine
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Downloading separate debug info for /lib64/libOpenCL.so.1...
Missing separate debuginfo for /lib64/libOpenCL.so.1
Try: dnf --enablerepo='*debug*' install /usr/lib/debug/.build-id/8b/1a5b9feb2f73098a0b3cc1fe1b7da5b32c1015.debug

Temporary breakpoint 1, 0x00000000004c4276 in main ()
(gdb)


I've been trying to find a permanent fix for this since FS19, but have given up now. As a workaround you can either cut down the tree, then delete the stump and tree separately OR you can delete the tree directly, save the game and reload. Either of those should work as expected.


Is there anything that can be done about about the trees I've already, for lack of a better term, ghosted? I'm not afraid to dive in and get my hands dirty editing the files directly IF only I knew where to look. I can't find them anywhere.

In the future, I'll be sure to do as you say so thank you for confirming that part.


Try to format via a laptop if you used a phone, or just let tony hawk format it when prompted.

If detection fail you can simply press reset on console, also games give up too fast.

Play with the LX, RX maximum value in web config to fine tune joystick.

IMHO this is a waste of time, that test tool make people paranoid. Most games are programmed with a good play room.


@ewoutkramer, Now that the 3.8.3 and 4 beta release have the httpclient in the constructor of the fhirclient, I think we can close this issue as it enables the HttpClientFactory to be used without change in this library


version v0.2022.04.25.09.59.stable_03 seems a bit normal?
<img width="1147" alt="截屏2022-05-02 15 53 11" src=" URL


Can confirm that it looks way better now. The line height is pretty narrow now though, so it would be great if we could configure it.

The important part however is that the text should be centered in the line height and not at the top of it. Otherwise we will just reproduce the issue from before.


It's much better. Still would like more options for fonts. I would like to have some AA + configure font weight.


I just completely unistall and install it again as suggested and it worked!
Thanks


@FrancoLoco as-tu résolu tes problèmes avec 2022.5? La version officielle vient de sortir, peux-être qu'ils ont changé des choses depuis la beta?


Non j'étais revenu à 2022.4 et j'ai pas réessayé 2022.5 depuis..


It should be fine if you just save the game and reload. Once all of the trees are reloaded from the savegame, the deleted trees should not be in the far distance (LOD) view anymore. HOWEVER, I've actually spent some time on this over the last few days and now have a fix working in single player. Still need to rewrite and test for multiplayer, but thanks for reminding me about it! :D


That's really great news! I found that quitting and restarting the game does NOT fix the issue. (I did notice the LOD effect at first. It didn't bother me since I'm not a detailed oriented person, it was the terrain that was really messing up my plans). I did find a work around but it's not ideal. Removing a file in the saved game (I forget what one, but it's not a simple plain text file) restored all the default trees for the map. It took a LOT of time and work, but I was able to remove those tree properly and flatten or raise the terrain.

I'm really glad you found a solution to the bug, this is a great mod!


I just discussed this issue with @aureamunoz and @michalszynkiewicz

The plan of action is the following:

- in the stroke processor, detect if the kubernetes service discovery is used (looking at the provider class on the classpath).
- if it's used, detect if the kubernetes client extension is present (capability check)
- if not -> fail the build and ask the user to add the kubernetes client extension


I don't think we'll do this anytime soon. A workaround is to use a custom build using esbuild oneself, and then feed that to wrangler. Closing this.


@skimaniac as-tu essayé toi? est-ce que ca marche maintenant?


Bon j'ai réessayé avec la version officielle 2022.5 qui sortait aujourd'hui et ca marche toujours pas.. j'ai l'impression que c'est vraiment un détail que @valleedelisle pourrait régler... as-tu des idées rapides? Merci

Setup failed for custom integration hilo: Requirements for hilo not found: ['python-hilo>=2022.5.1'].
14:55:43 – (ERROR) setup.py

Logger: homeassistant.util.package
Source: util/package.py:99
First occurred: 14:52:30 (3 occurrences)
Last logged: 14:55:43

Unable to install package python-hilo>=2022.5.1: ERROR: Cannot install python-hilo==2022.5.1 because these package versions have conflicting dependencies. ERROR: ResolutionImpossible: for help visit URL WARNING: You are using pip version 22.0.3; however, version 22.0.4 is available. You should consider upgrading via the '/usr/local/bin/python3 -m pip install --upgrade pip' command.


Thanks for replying! I've tried the suggestions but F-Zero does not work at all with a blueretro device and Tony Hawk will not recognize the controller pak. Testing a random sample of other controller pak games shows a major issue with the current integration. I've also experienced odd rumble behavior. On Goldeney 007, the rumble will not work correctly when firing. It gives a brief rumble and then stops when firing, when it should continue to rumble when firing. This is a great product, and hopefully you'll be able to circle back around to the N64 to finish polishing the feature set. Thank you!


You might have some build related issues because I personally got none of those issues.

Sound like your data line is glitching somehow.


This was confirmed from others using the adapter purchased from Tindie so it is likely the build. I’ll follow up with the seller.


If you can ask others to report feedback in this GitHub issues.

Everyone with issue should list the following information if possible:
* N64 motherboard revision
* List of internal mods installed
* Other external peripheral used

It could be problem with the dongle itself but it could also be some interoperability issue with some motherboard or some other mods.


Je viens d'upgrader mon container ce matin et je n'ai pas eu ce probleme. Par contre, j'ai une erreur similaire avec une autre de mes integration [1] et j'ai une autre erreur [2] plus loin qui semble liée à un changement dans l'integration sensor de home assistant

[1]

2022-05-05 08:38:21 ERROR (SyncWorker_2) [homeassistant.util.package] Unable to install package paho-mqtt==1.5.1: ERROR: Cannot install paho-mqtt==1.5.1 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit URL
WARNING: You are using pip version 22.0.3; however, version 22.0.4 is available.
You should consider upgrading via the '/usr/local/bin/python3 -m pip install --upgrade pip' command.
2022-05-05 08:38:21 INFO (SyncWorker_3) [homeassistant.util.package] Attempting install of paho-mqtt==1.5.1
2022-05-05 08:38:28 ERROR (SyncWorker_3) [homeassistant.util.package] Unable to install package paho-mqtt==1.5.1: ERROR: Cannot install paho-mqtt==1.5.1 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit URL
WARNING: You are using pip version 22.0.3; however, version 22.0.4 is available.
You should consider upgrading via the '/usr/local/bin/python3 -m pip install --upgrade pip' command.
2022-05-05 08:38:28 INFO (SyncWorker_1) [homeassistant.util.package] Attempting install of paho-mqtt==1.5.1
2022-05-05 08:38:31 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [281472852626640] Received invalid command: mobile_app/push_notification_channel
2022-05-05 08:38:35 ERROR (SyncWorker_1) [homeassistant.util.package] Unable to install package paho-mqtt==1.5.1: ERROR: Cannot install paho-mqtt==1.5.1 because these package versions have conflicting dependencies.
ERROR: ResolutionImpossible: for help visit URL
WARNING: You are using pip version 22.0.3; however, version 22.0.4 is available.
You should consider upgrading via the '/usr/local/bin/python3 -m pip install --upgrade pip' command.
2022-05-05 08:38:35 ERROR (MainThread) [homeassistant.setup] Setup failed for custom integration jq300: Requirements for jq300 not found: ['paho-mqtt==1.5.1'].

[2]

2022-05-05 08:39:02 ERROR (MainThread) [homeassistant.components.sensor] Error while setting up hilo platform for sensor
Traceback (most recent call last):
 File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
 await asyncio.shield(task)
 File "/config/custom_components/hilo/sensor.py", line 171, in async_setup_entry
 create_energy_entity(d)
 File "/config/custom_components/hilo/sensor.py", line 148, in create_energy_entity
 device._energy_entity = EnergySensor(device)
 File "/config/custom_components/hilo/sensor.py", line 264, in __init__
 super().__init__(
TypeError: __init__() got an unexpected keyword argument 'unit_of_measurement'


@valleedelisle as tu vu ma pull request dans python-Hilo? J’ai l’impression que lousser les requirements aiderait..?


Non j'ai pas toucher à 2022.5 un peu à cause de ça, mais j'ai un home assistant (test) sur un docker lui je l'ai updater et j'ai tester Hilo sur lui ce matin et ça fonctionne pas (les mêmes erreurs que vous avez rapporter)

Donc je toucherai pas à mon HA principal pour tout de suite ;)


Moi qui d'habitude upgrade 2 fois par année, j'me suis fait mettre de la pression en écrivant ça 🤣 J'ai pu d'environment de test alors j'viens de mettre ma 'prod' à terre pour faire marcher ça.


@valleedelisle c'est quoi ton autre intégration qui ne fonctionne plus? Si c'est un intégrationnistes assez populaire ça se peux que les dévelopeur de HA corrige le problème de python ou je sais pas trop... ;)


Un autre developpeur qui fix son integration sans pousser une release 🙄 (ca m'est arrived quelques fois)


All right je confirme que ca marche avec le nouveau release v2022.5.2, party d'update d'Home Assistant! 🎉 Merci!!


I had mempak issues myself before, but they were resolved when I used a PC instead of a phone to change the config. These issues occured both on my adaptor as well as on an ESP32 Devkit which I used to compare functionality.
Regarding the other issues, both with a ESP32 Devkit as well as my own Adaptors I had sporadic rumble issues, close to the ones that you described.
Nothing gamebreaking though, the core functionality always worked. To be honest I always accepted it as minor issues in a great open source project, maybe depending on different controllers, console revisions and mods used. In the issues section on GitHub there are also several topics related to these small issues, so I did not look more into it and accepted it as small software bugs that don't really affect me.

Now of course I don't want to blame you @darthcloud for anything in your amazing project and I want to offer the most for everyone who bought my Adaptor, so I will look further into it.

Because I just moved last week, it will take more time than usual, I barely even have a TV set up at the moment, and my N64 consoles as well as the Adaptors are still in boxes.

I will try to get to it this weekend.


@bixxewoscht Anything is possible off course but the N64 is the original system BlueRetro was developed for and that I actually use myself a lot. I gone though GoldenEye a few time ever the last 3 years and never noticed any rumble issues. The way it is implemented makes the interface very robust as it is using the ESP RMT peripheral, (so no software bit bang). What you guys describe should not happen at all.

I'm using my own BlueRetro Devkit when playing but I did test with a few clone ESP-DevKit-C in December and this spring and didn't got any controller pak error myself. Controller pak was tested by going through Turok 1 and Tony Hawk 1.

The issue sound like the data line is glitching.

My own board got ESD protection on each line using a TPD6F002DSVR chip. This got an equivalent resistance of 100ohm. No idea if this help or not.

Maybe chip me one of your dongle for me to test.

I play with early N64 rev mostly but got a few more now that I could try on too. I got no mod in my console.


y a tu juste moi qui a ce bug là: dans HA SmartEnergyMeter Power 0w, dans l'app Hilo 0w, mais le total par heur dans l'app continu à monter. 🤨


Moi c'est ok ça se met à jour. Mais si tu as 0 dans l'app Hilo ta passerelle est probablement déconnecté du côté de l'antenne zigbee vers le compteur d'Hydro.

Les thermostats répondent?

Si oui reboot la paserelle.

Si ça se règle pas dans Hilo : j'ai du le ouvrir un case pour la mienne qui parlait plus au compteur. 3-4,jours.

Obtenir Outlook pour Android
Sent: Thursday, May 5, 2022 12:25:08 PM
To: dvd-dev/hilo ***@***.***>
Cc: Fox350 ***@***.***>; Comment ***@***.***>
Subject: Re: [dvd-dev/hilo] Incompatibilité Home Assistant 2022.5 (Issue #112)

y a tu juste moi qui a ce bug là: dans HA SmartEnergyMeter Power 0w, dans l'app Hilo 0w, mais le total par heur dans l'app continu à monter. 🤨

—
Reply to this email directly, view it on GitHub


J'avais aussi ce problème, je croyais à un problème Hilo, mais effectivement en rebootant la passerelle ca a fonctionné.


J'ai rien touché et c'est revenu. Mais la passerelle était verte et les données montaient quand même, donc elle devait être branché sur le compteur. Bizarre quand même 🤷🏻♂


C'est la faute à Jean Charest 😁

Obtenir Outlook pour Android
Sent: Thursday, May 5, 2022 3:09:59 PM
To: dvd-dev/hilo ***@***.***>
Cc: Fox350 ***@***.***>; Comment ***@***.***>
Subject: Re: [dvd-dev/hilo] Incompatibilité Home Assistant 2022.5 (Issue #112)

J'ai rien touché et c'est revenu. Mais la passerelle était verte et les données montaient quand même, donc elle devait être branché sur le compteur. Bizarre quand même 🤷🏻♂

—
Reply to this email directly, view it on GitHub


J'ai un autre bug depuis que je suis à 2022.5, mes compteurs d'énergie ne se remplissent plus et je vois constamment cette erreur dans les logs:
2022-05-05 16:11:02 WARNING (MainThread) [custom_components.hilo] check_tarif: Unable to find state for sensor.hilo_energy_total_daily_low


Yeah, line height was fixed but there were a couple other issues introduced so it got temporarily rolled back. I'm actively working on font rendering issues, so things should be improving soon.

One note about anti-aliasing, since many people seem to comment on it - we do actually use AA for font rendering, and my pixel-level comparisons with iTerm on both retina and non-retina displays indicates that both terminals render glyphs the same way (Courier New, 13pt, with "Use thin strokes for anti-aliased text" in iTerm set to "Never"), with a couple notable differences that I'm working on:
 * Warp computes cell sizes differently (this is the line height issue y'all have been discussing, and can be seen in the horizontal spacing of glyphs in the screenshots below)
 * Warp cuts the top row of pixels off of some glyphs (you can see this in the "l" below)
 * Warp occasionally renders glyphs at fractional y-values, leading to different/fuzzy glyph rendering
 * Warp doesn't render glyphs with thinner outlines on retina displays (hence disabling that in iTerm to make pixel-level comparisons)
 * Warp doesn't allow users to customize font metrics (e.g.: line density/spacing) - this is something I'd like to fix but will likely come after fixing core rendering issues

Screenshots of Warp (top, blue bg) and iTerm (bottom, black bg) on a non-retina external display:
image
image

If you're finding that Warp and iTerm have different pixel-level glyph rendering, I'd love it if you would reply with the following info:
 * A screenshot or two highlighting the differences
 * Which version of Warp you're running
 * Which font you're using and which font size
 * Whether you're using Warp on your laptop screen (which model?) or an external monitor (what resolution?)

Getting this right is important to us (and all of you, clearly!) :)


C'est un peu poche ça que les update de HA brise des intégrations qui fonctionnaient :(


Bah c'est un peu de ma faute, faudrait que je suive les updates de près mais j'ai pas le temps.

Ensuite, c'est pas une intégration officielle, donc elle n'est pas testée. De plus, je n'ai pas écrit de functional et unit test. Par contre, je suis ouvert aux PR, si ça tente à quelqu'un.


Moi j'ai dû changer tous mes energy sensors, mais je ne sais si j'ai remis me bon. Mes valeurs sont négatives.

Screenshot_2022-05-05-21-27-54-26_c3a231c25ed346e59462e84656a70e50


Bon finalement de mon côté j'ai réassocié manuellement mes energy meters dans les settings du dashboard energy car ca semblait lié à des trucs orphelins ou brisés (autant pour le compteur total que pour les devices individuels).. et avec le bout de code de la pull request ci-dessus, ca a réglé mon erreur (_check_tarif: Unable to find state for sensor.hilo_energy_total_daily_low_) et ca s'est remis à fonctionner correctement semblerait pour moi pour le moment.

Les nouveaux compteurs non brisés sont ceux avec une petite icone à côté:
image


You need to run the "bt" command once you get back to the (gdb) prompt so it can show you where it actually crashed. It might be deep within opengl or something, but the crash has to originate from somewhere in my code.


The issue still persists for me with Vite@2.9.8.

Vite@2.8.6 working well, I'm running Vitebook with Vitest and testing my components by using the preact testing library.


Hello! I am facing the same issue as the other person is. Here's the output of GDB

(gdb) run /hdd0/SteamLibrary/steamapps/workshop/content/431960/2638696675/
Starting program: /home/kris/git/linux-wallpaperengine/build/wallengine /hdd0/SteamLibrary/steamapps/workshop/content/431960/2638696675/
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Detected scene.pkg file at /hdd0/SteamLibrary/steamapps/workshop/content/431960/2638696675/scene.pkg. Adding to list of searchable paths
Found assets folder alongside the binary: /home/kris/git/linux-wallpaperengine/build/assets
[New Thread 0x7fffb827f640 (LWP 293361)]

Thread 1 "wallengine" received signal SIGSEGV, Segmentation fault.
0x000055555562d3b5 in WallpaperEngine::Audio::CAudioStream::loadCustomContent(char const*) ()
(gdb) bt
#0 0x000055555562d3b5 in WallpaperEngine::Audio::CAudioStream::loadCustomContent(char const*) ()
#1 0x000055555562d1fd in WallpaperEngine::Audio::CAudioStream::CAudioStream(void*, int) ()
#2 0x000055555565d7c3 in WallpaperEngine::Render::Objects::CSound::load() ()
#3 0x000055555565d673 in WallpaperEngine::Render::Objects::CSound::CSound(WallpaperEngine::Render::CScene*, WallpaperEngine::Core::Objects::CSound*) ()
#4 0x0000555555654693 in WallpaperEngine::Render::CScene::CScene(WallpaperEngine::Core::CScene*, WallpaperEngine::Assets::CContainer*, WallpaperEngine::Render::CContext*) ()
#5 0x000055555565322b in WallpaperEngine::Render::CWallpaper::fromWallpaper(WallpaperEngine::Core::CWallpaper*, WallpaperEngine::Assets::CContainer*, WallpaperEngine::Render::CContext*) ()
#6 0x000055555561c3b6 in main ()


I am at Tafe this week, so I will try running the BT command in GDB when I am back Friday night or Saturday


@t1stm your stack traces are interesting, both seem to happen on ffmpeg-related code (either audio or video) but I can load both backgrounds properly. What OS and version are you using? What ffmpeg version do you have installed?

@mihawk90 that's weird, you should at least be able to get the stacktrace up to the last call that happens in the wallpaper engine binary. I'm sorry but I'm no expert on GDB :/ Maybe you can try it in an IDE like VScode or CLion that have an interactive debugger?

@L-m-b no problem, ping me when you have it and i'll look into it ;)


@Almamu I use Arch Linux, and use Openbox as my window manager with the picom compositor. I am using the latest FFmpeg version on the AUR - ffmpeg-full, but the version from the official repo gives me the exact same error after removing the build directory and building again. The FFmpeg version is 5.0.1 from the AUR and 5.0.0 from the repo. FFmpeg works just fine encoding and decoding the videos. I tested the decoding using a pipe to MPV.


@Almamu I decided to start to look for problems, and found files in the /usr/local directory which came from an old FFmpeg build I compiled a year ago and removed some time after that. For some reason CMake was detecting these files and not the ones in the /usr directory, so if anyone here has compiled FFmpeg from source before, be sure to check your /usr/local directory for any old files. Anyways with that being fixed the wallpapers start normally, but my tint2 dock has an issue where the icons are flickering.


I was having this issue specifically when installing and deploying within an AWS Amplify build pipeline. Of the suggested fixes, moving from `npm` to `yarn` was the only thing that solved it for me.


Me neither :/
This is as far as I get:

z% gdb wallengine ~/.local/share/Steam/steamapps/workshop/content/431960/2677437153
GNU gdb (GDB) Fedora 11.2-3.fc36
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later < URL
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
< URL
Find the GDB manual and other documentation resources online at:
 < URL

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from wallengine...
Reading symbols from /usr/lib/debug/usr/bin/wallengine-0.0.1.28f0868-1.fc36.x86_64.debug...
"/home/tarulia/.local/share/Steam/steamapps/workshop/content/431960/2677437153" is not a core dump: file format not recognized
(gdb) start
Temporary breakpoint 1 at 0x22620: file /usr/src/debug/linux-wallpaperengine-0.0.1.28f0868-1.fc36.x86_64/main.cpp, line 95.
Starting program: /usr/bin/wallengine

This GDB supports auto-downloading debuginfo from the following URLs:
 URL
Enable debuginfod for this session? (y or [n]) y
Debuginfod has been enabled.
To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
Downloading separate debug info for /home/tarulia/system-supplied DSO at 0x7ffff7fc4000...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Downloading separate debug info for /lib64/liblzma.so.5...
Downloading separate debug info for /lib64/libcrypto.so.3...
Downloading separate debug info for /home/tarulia/.cache/debuginfod_client/00404b8982ab681e4d574a5fa286c28f3844aeb6/debuginfo...
Downloading separate debug info for /lib64/libssl.so.3...

Temporary breakpoint 1, main (argc=1, argv=0x7fffffffdce8) at /usr/src/debug/linux-wallpaperengine-0.0.1.28f0868-1.fc36.x86_64/main.cpp:95
95 {
(gdb) bt
#0 main (argc=1, argv=0x7fffffffdce8) at /usr/src/debug/linux-wallpaperengine-0.0.1.28f0868-1.fc36.x86_64/main.cpp:95
(gdb)

I'm on F36 KDE spin.


For me the font rendering is perfect on MacBook Pro built-in retina display, but the fonts become blurry when I close the laptop and use 2x full hd monitor via DisplayLink


Your backtrace is from a breakpoint placed on the start of the app, not from the actual crash. You should be able to continue execution until the app actually crashes (if I recall correctly the command is "continue").


@skimaniac moi aussi elles reviennent, pour le moment je les laisse là et les ignore...


Pour moi ça a arrêté de réapparaître après le 3e fois que je les ai enlevés.


@FrancoLoco je viens de voir dans la page des statistiques qu'elles apparaissent avec des erreurs, je vais les supprimer là aussi pour voir si ça corrige.

<img width="1261" alt="Capture d’écran, le 2022-05-09 à 10 26 18" src=" URL


Is there any expected time of arrival for other IDEs support?


@samurai00 As mentioned above, the fix for line height was rolled back temporarily while we fix a regression. A handful of font rendering improvements should go out next week. :)


Please let me know if this version has resolved the issue: URL

I guess it will not do anything to your terrain issue caused by previously removed trees, but hopefully should prevent the problem occuring again.


J'ai le même problème que toi ! Je viens tout juste d'installer cette intégration Hilo. Comment ça fonctionne pour réassocier manuellement mes energy meters ? Merci !


Issue #507 has been raised to investigate the opportunity for modifying the FDO date for this piece of work


Still not working with
ConnectPnPOnline -Url "myco-admin.sharepoint.com" -ClientId "ZZZZZZ" -Tenant "myco.onmicrosoft.com" -Thumbprint "XXXXXXX"

When will MSFT fix this ?

Set-PnPUserProfileProperty : This operation requires you to be managing your own data or have administrator privileges.
At line:12 char:5
+ Set-PnPUserProfileProperty -Account xxxxxx -Prope ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : WriteError: (:) [Set-PnPUserProfileProperty], ServerException
 + FullyQualifiedErrorId : EXCEPTION,PnP.PowerShell.Commands.UserProfiles.SetUserProfileProperty


That stacktrace isn't really that helpful... For some reason it's happening in one of the std::string methods, but there should be some calling code somewhere :/ Maybe
bt full
 will give some more precise information? @mihawk90


The landscape zoomed picture problem rooted from this part of the code:

 Transform.scale(
 scale: scale,
 child: Center(
 child: _changingCameraLens
 ? Center(
 child: const Text('Changing camera lens'),
 )
 : CameraPreview(_controller),
 ),
 ),

If you change the `scale: scale` to `scale:1` it will fix the landscape orientation zoom problem but with some drawbacks.
The main cons of doing this is the aspect ratio of the camera preview, which looks to be not the same as the main scaffold's body.
After all, I think passing 1 to `scale` may solve the problem for now.


An update. I've tried version 6.0.2 and it went through but with error:

[OK] Installer updated to latest version 3.2.3
[OK] Installer self update successful.
Downloading...
Checking FSL package
[OK] File downloaded
Installing FSL software version 6.0.2...
[OK] FSL software installed.
Performing post install tasks
Stage 1
By installing this python distribution you agree to the license terms in
/opt/fsl/fslpython/LICENSE.txt
100%
/opt/fsl/etc/fslconf/fslpython_install.sh: line 188: /opt/fsl/fslpython/bin/conda: No such file or directory
/opt/fsl/etc/fslconf/fslpython_install.sh: line 189: /opt/fsl/fslpython/bin/conda: No such file or directory
/opt/fsl/etc/fslconf/fslpython_install.sh: line 190: /opt/fsl/fslpython/bin/conda: No such file or directory
/opt/fsl/etc/fslconf/fslpython_install.sh: line 191: /opt/fsl/fslpython/bin/conda: No such file or directory
Stage 2
100%
Failed to create FSL Python environment - see /tmp/fslpythonvQ5d/fslpython_miniconda_installer.log for details
Post install setup failed
[OK] Post installation setup complete
Error processing tar file(exit status 1): write /opt/fsl/data/first/models_317_bin/R_Late_bin.bmv: no space left on device


<img width="350" alt="image" src=" URL
I've also noticed blurry fonts and bad kerning. For example here, the spacing between `p y` in Copy, `l e` in select, `u s` in user's. For some people I've shown this to they can't even see it and for others a deal breaker, including me unfortunately.


@mihawk90 that's a really useful stacktrace. I'll look into it today and fix it, seems a simple enough thing.


Update. I changed `RUN python3 fslinstaller.py -d /opt/fsl -V 6.0.2` into `RUN /usr/bin/python3 fslinstaller.py -d /opt/fsl -V 6.0.2`. It didn't change anything.


Cześć @kaczmarj :-) Thanks for the tip. Yes, I've seen this post but I'm trying to install FSL in Docker, so executing these steps is a little bit problematic. But I will try it next.

With version 6.0.2, Stage 2 doesn't last long. I think it stalls in newer versions because something goes wrong. I'm really surprised that the FSL developers don't fix these issues. But well, it is what it is.

Small update. I've added

ENV FSLDIR="/opt/fsl"
RUN [ -d "$FSLDIR/fslpython" ] && rm -r $FSLDIR/fslpython; \
 $FSLDIR/etc/fslconf/fslpython_install.sh -f $FSLDIR

as indicated in Troubleshooting section but it didn't change anything.


Funny thing, the `-L` option is in the newer FSL version of `fslpython_install.sh` but not 6.0.2. I added it in 6.0.2 and now "Stage 2" stalls as originally. That's the current Docker snippet:

# Install FSL for pydeface
RUN echo "INFO Installing FSL ..."
# file command is used by FSL installer
RUN apt-get -y install file
RUN curl -s URL -o fslinstaller.py
RUN /usr/bin/python3 fslinstaller.py -d /opt/fsl -V 6.0.2; \
 rm fslinstaller.py
# Try solution from URL
ENV FSLDIR="/opt/fsl"
RUN sed -i "s/dl_cmd_opts=\"--fail\"/dl_cmd_opts=\"--fail -L\"/g" $FSLDIR/etc/fslconf/fslpython_install.sh
RUN [ -d "$FSLDIR/fslpython" ] && rm -r $FSLDIR/fslpython; \
 $FSLDIR/etc/fslconf/fslpython_install.sh -f $FSLDIR
# Variables and config for FSL.
RUN . ${FSLDIR}/etc/fslconf/fsl.sh
ENV PATH="${FSLDIR}/bin:${PATH}"


the stall is normal. conda takes its time to create the environment :) from my experience, it could take around 15 minutes or more for the conda installation to complete. please let me know if your docker build succeeds


I've built a Dockerfile using Neurodocker with `neurodocker generate docker --pkg-manager apt --base-image debian:stable --fsl version=6.0.2 > Dockerfile.nd.fsl` It finished building but I don't have a detailed timestamp. It was less than 2.5h.

I'll try my Dockerfile again. It seems FSL takes a long time to install.


i think the neurodocker build is the way to go. but unfortunately, fsl does take a long time to install. first, the fsl binaries have to be downloaded, and then the conda environment has to be created. both of these processes take some time as you have seen. these will go slower is the internet speed is low.

regarding the progress `Stage 2 0%`, in my experience the percentage did not increase until the very end of the process... so i wouldn't rely on that as a marker of whether the installation has stalled. you could look at `htop` or your computer's activity monitor to see what processes are going on in the build.


Tout d'actualité
Bonjour Kevin
Je confirme comme les autres qu'il s'agit plus que d'une "amélioration possible", mais d'une amélioration attendue par obligation de réponse aux services instructeurs
Cdt Dellac Laurent. Chef service ERP SDIS33


so starting off today i redownloaded the package, build the cmake side of things, then ran make.
[ 41%] Building CXX object CMakeFiles/wallengine.dir/src/WallpaperEngine/Render/CFBO.cpp.o
/home/luke/linux-wallpaperengine-main/src/WallpaperEngine/Render/CFBO.cpp: In member function ‘virtual const std::vector & WallpaperEngine::Render::CFBO::getFrames() const’:
/home/luke/linux-wallpaperengine-main/src/WallpaperEngine/Render/CFBO.cpp:98:17: warning: returning reference to temporary [-Wreturn-local-addr]
 98 | return std::vector ();
 | ^~~~~~~~~~~~~~~~~~~~~~~~
[ 43%] Building CXX object CMakeFiles/wallengine.dir/src/WallpaperEngine/Render/Objects/Effects/CPass.cpp.o
this warning came up during the setup.
but aside from that program installed and launched OK, but window was not on the background, but luckily kde allowed me to make it so.
you must have fixed it.


some of the scenes i have result in seg fault still, actually, old reactor is a good one to test that on


none of the shaders work, all wallpapers that do work end up still because of the lack of shaders, and the ones not entirely reliant on it don't launch, at least out of my library. the non scene backgrounds or scenes that only rely on html and etc, don't play at all.


Reported. Don't you get tired of this? If you want support for a corner case, fork the code and do it yourself.
If the main developer abandons this great project, it will be because of you. You're boring stones.


I am considering closing the issue reports for good, too bad for other people but this constant trolling (or maybe it is just some foem of autism, I don't know... and don't care) is too annoying.

He has been reported at least twice to github but still comes back after a while. He is also apparently doing the same in other emulators repisitory, looking at the user history.


@ekeeke for the record, I am autistic. But, I would never go out of my way to harass someone like this individual has done. Usually, when someone bullies someone online, from a psychological standpoint, it is because they are trying to fill the gap over something they have no control over in life, be it divorce, problems with friends or family, etc.

There are certainly better things to do with one's free time. Just don't let this stuff get you down.
I have dealt with my own share of bullies when working on various online projects. But, you just gotta keep strong in mind at all times. And, you will prevail.

When I first got into working with the Mini Classics, another team decided to try to push me out of the scene with various tactics. In the end, me just being me, being nice to everyone, had way more people supporting my unorthodox and creative solutions and workarounds, emulation wise, and I am satisfied with the current state of things.

If you like movies or tv shows, find something you've been meaning to watch! Just know, people like me will always have your back and appreciate what efforts you put forth in anything and all you do, whether or not they are autistic:)


Can't replicate the issue on Flutter v3.0.0 and sticky_headers 0.3.0. Please retest and if it's still a problem provide example so we can resolve it.


I do think this case is exactly #111, in different clothing.

I think I agree? So to restate, then:

To find the signature of an abstract method inherited from multiple supertypes, use the intersection the supermethod return types, and the union of each set of corresponding parameter types.

I think we can resolve this.


C'est réglé dans la plus récente version, sinon voir mes explications pour faire le ménage dans le dashboard energy: URL


@MrKrabs07 Stop spamming the same request.

The spam links:

#432
#430
#425
#422
#420
#419
#417
#416
#415
#414
#413

Those are Master System games (with .sms file extension) They don't work on SG-1000 Hardware because SG-1000 has 1KB or 2KB RAM but they need 8KB Before. Master System & Game Gear mode with TMS9918 mode is Incorrect by SMS Plus. Including SMS Plus GX, Kega Fusion, MEKA, Gearsystem Always uses TMS9918. Gearsystem, Kega Fusion, MEKA, SMS Plus's SG-1000 Uses 16KB RAM.

The color look wrong on TMS9918 Content on Master System & Game Gear Hardware. Black Screen On Genesis/Mega Drive Hardware. Genesis/Mega Drive Has No TMS9918-Compatible. Master System Has 256-Colors (Z80 CPU). Like CRT TV CPUs Uses Z80.

**RULES:**

1. No spamming

2. No Not Safe For Work Content

3. No Copyrighted Content

@ekeeke Please lock this conversation and delete issue #432 #425 #422 #420 #419 #417 #416 #415 #414 #413


@SquidwardKrabs we all know it's just you under another account. It is so very nice to see you are such an upstanding individual that you spend all of your free time playing mental games. You realize, if you keep this up, you will only make it so ekeeke and others no longer have interest in bettering these emulators for the thousands upon thousands of people that use them. There are far better things you can do with your free time than bullying others online.

Also note, what you are doing is actually a crime, which can land you in jail if you keep it up.

@ekeeke Sorry to see you have to go through this nonsense due to an obviously mentally unstable individual who truly needs to get help.


I'd like to thank you @kaczmarj for help. I've build the Docker container using mine and Neurodocker-generated Dockerfile, both for FSL 6.0.5.1 Both work. Both take around 2.5h to install FSL (**not** due to the Internet bandwidth).

I generated Nerodocker Dockerfile with `neurodocker generate docker --pkg-manager apt --base-image debian:stable --fsl version=6.0.5.1 > Dockerfile.nd.fsl_6.0.5.1`.

Snippet from my Dockerfile:

FROM debian:stable
...
# Install FSL for pydeface
RUN echo "INFO Installing FSL ..."
RUN curl -s URL -o fslinstaller.py
RUN /usr/bin/python3 fslinstaller.py -d /opt/fsl -V 6.0.5.1; \
 rm fslinstaller.py
# Variables and config for FSL
ENV FSLDIR="/opt/fsl"
RUN . ${FSLDIR}/etc/fslconf/fsl.sh
ENV PATH="${FSLDIR}/bin:${PATH}"


@mateuszpawlik - i'm glad it's working now.

one note on the line `RUN . ${FSLDIR}/etc/fslconf/fsl.sh`. the sourced variables will not persist to future instructions. each `RUN` instruction starts up its own shell and then tears down that shell when it's finished.

you could get around this in two ways: either source the `fsl.sh` file when you start the container, or hardcode the environment variables in `fsl.sh` with `ENV` instructions.


Yes I'm having this issue now trying to deploy my project on vercel. how do you solve the issue when deploying to vercel?


Strapi version 4.11.1 upgraded to latest Sentry version. This fixed the issue. So, closing this