Unable to delete assembly file after plugin uninstall

Describe the bug
When I use the sample code: https://github.com/dotnet/samples/tree/master/core/tutorials/Unloading
Then I want to remove the assembly file after the plugin is uninstalled and I get an exception:

Run Environment

.NET CORE 3.1
Windows 10

Thanks in advance to the .net core team for answering my questions. Thank you!

@zengqinglei thanks for contacting us.
We believe this issue is not related to ASP.NET and you will get a faster and better response by filing an issue in the dotnet runtime repository.
/cc: @davidfowl as you were interested in knowing about these things.

@zengqinglei thanks for contacting us.
We believe this issue is not related to ASP.NET and you will get a faster and better response by filing an issue in the dotnet runtime repository.
/cc: @davidfowl as you were interested in knowing about these things.

ok,thank you !


Windows 10 wallet crash

My wallet just crash when I clicked 'minting'.
I'm on Windows 10. Wallet had been running for about a day.

Log isn't showing anything special.
askfor block c164dd30c8fd7c541356<PHONE_NUMBER>000000
received block c164dd30c8fd7c541356
SetBestChain: new best=c164dd30c8fd7c541356  height=401258  trust=223028769207327  moneysupply=16439524.003292
ProcessBlock: ACCEPTED
Your balance is<PHONE_NUMBER> and reservebalance is 0
Your balance is<PHONE_NUMBER> and reservebalance is 0
Your balance is<PHONE_NUMBER> and reservebalance is 0

I'm guessing this is related to a memory issue, as I get a similar crash if I send a transaction after the wallet has been open for a few days. My log also shows nothing special

I'd say this relates to #176. And yes I think it's a memory issue as well as I experience both the minting tab crash and also the sending transaction crash.
@IngCr3at1on and I have put a few memory fixes in since the last release so we will see how that affects it all.

Closing in favor of #457 as we will be debugging this there.


Windows Subsystem for Linux error-- cannot communicate with local orca server process even though server process seems to be running

Hello all,
I am trying to write an image to .svg format using a jupyterlab setup on Windows Subsystem for Linux (WSL).  After installing gtk library, installing Xming, configuring env variable DISPLAY=:0, and disabling chrome sandbox, I am still running into issues.  Right now, I'm getting the following error output in my python terminal:
For some reason plotly.py was unable to communicate with the
local orca server process, even though the server process seems to be running.

Please review the process and connection information below:

orca status
-----------
    state: running
    executable: /usr/bin/xvfb-run --auto-servernum --server-args -screen 0 640x480x24 +extension RANDR +extension GLX /usr/bin/orca
    version: 1.2.1
    port: 60427
    pid: 29156
    command: ['/usr/bin/xvfb-run', '--auto-servernum', '--server-args', '-screen 0 640x480x24 +extension RANDR +extension GLX', '/usr/bin/orca', 'serve', '-p', '60427', '--plotly', '/home/tyler/.local/share/virtualenvs/thesis-WAlznkOk/lib/python3.7/site-packages/plotly/package_data/plotly.min.js', '--graph-only', '--mathjax', 'https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/MathJax.js']

Any pieces of advice?  Other than examining the server connection, which i'm not entirely sure what is meant by that, I'm wondering if there are any other WSL-compatibility shortcuts i might be able to take.  It would be great if this library could include additional documentation/support for WSL

closing for now while i troubleshoot... somehow missed a whole subsection of linux troubleshooting in the readme heh

Trying to get Orca to work on Windows Subsystem for Linux is rather brave @schlich :sweat_smile:! Please let us know if you succeed.
I also want to point out that Orca can be installed on Windows and isn't a Linux only product.

I did end up getting it working!  it took a lot of cobbling together and trying different things and reinstalling npm about 5 different times but I got there!  Went with Xming and had to disable xvbf.
My mac died a few days ago and I had to flip a coin as to where to port all my work ended up going with WSL.   Definitely getting a few lessons in technical expertise!

@schlich can you care to elaborate anymore on the steps you took to get orca to work on WSL?
This has been something that I've been struggling with for some time now and it would be really valuable to get this to work for me
Thus far I've just setup a separate computer with Ubuntu to export my plots to pdf/svg, far from ideal

Happy to help, could you outline the steps you've taken and any errors you're getting?

Thanks @schlich
My attempts have pretty much been limited to installation with conda
Attempting to write a .pdf file in a python script results in a generic error associated with orca not being installed (attached below)
plotly_python_orca_err.txt
Furthermore, there doesn't seem to be an orca executable installed via this route in the bin location that it should be located
So it seems that the conda installation procedure is a no-go, but it seems to me that you used the npm installation instructions so I'll give that a shot now.

Wow I can't believe it, I got it to work
My steps:

Install conda/anaconda (instructions available elsewhere)
Install nodejs (npm) through conda

conda install -c conda-forge nodejs

Install orca through npm via instructions on orca's README

npm install -g<EMAIL_ADDRESS>orca

Finally, I needed to install a library because of the missing shared libgconf-2.so.4 library

sudo apt-get install libgconf-2-4

After these steps, attempting to perform a fig.write_image("figure.pdf") worked properly!
@schlich I'm a bit puzzled by your initial comments on this thread:

After installing gtk library, installing Xming, configuring env variable DISPLAY=:0, and disabling chrome sandbox, I am still running into issues

I didn't really have to mess around with any of this, I do already have Xming setup properly but the gtk library and chrome sandbox bits are unfamiliar to me
If anybody else can try to confirm the procedure I outlined above and let everybody know if it works that would be great

Just tried here and can confirm your procedure works @raulf2012!
Some aditional missing shared libraries had to be installed:
sudo apt-get install libgtk2.0-0
sudo apt-get install libnss3-dev
Thanks for sharing!

Not sure which dependency changed but it looks like we now need
sudo apt-get install libgtk-3-0
which may or may not be taking the place of libgtk2.0-0

I just want to mention that we're basically replacing Orca with the new Kaleido project (https://github.com/plotly/Kaleido) which is significantly easier to install in docker containers and is our new recommended way forward for this kind of thing :)

I just want to mention that we're basically replacing Orca with the new Kaleido project (https://github.com/plotly/Kaleido) which is significantly easier to install in docker containers and is our new recommended way forward for this kind of thing :)


[topgen] Don't dump hjson by default

This might be handy for debugging, but it isn't really needed most of
the time. We're also currently checking it in: since it changes
frequently, this causes a whole host of merge conflicts for no real
benefit.

I think we have more dumps of hjson (e.g: xbar) . Do you think also it is good to move them optionally?

could we add a note to this in the topgen usage documentation (i honestly can't remember where it is)

could we add a note to this in the topgen usage documentation (i honestly can't remember where it is)

https://docs.opentitan.org/doc/rm/topgen_tool/
But don't overdo the docs there, I'm looking into rewriting some of it as well.

Just a note here that we may have to devise a way to access some of the generated RndCnsts for scripts like the ROM generation + scrambling.
If this generated Hjson is not checked in anymore, there are a couple of options I can think of:

always run topgen first, and then consume the generated debug Hjson in the script that needs access to the RndCnsts
write out the RndCnsts into a separate HJSON file and check it in
split out the RndCnsts generation into a class that can be imported in other scripts. As long as you provide that class with the seed and RndCnst definitions/order from top_*.hjson, you are able to regenerate the constants deterministically on the fly.
Don't use RndCnsts for the ROM scrambling. Instead, create a separate script that generates the netlist constant and the ROM contents.

For OTP/LC I have done something similar to 4), since I needed to impose some more constraints on the generated life cycle constants.
For the ROM checker scrambling key, one of the other methods could probably work as well, since there are no additional constraints that need to be imposed.

@msfschaffner Good point. I'm currently looking at restructuring some of topgen and I'll keep that in mind. I'll follow up with what I'm actually planning once I know myself (I thought I did a couple times now, and then always found another "interesting feature" that I forgot about).

If current Random Constants is consumed from top_*.gen.hjson, I think it would be better to hold this PR until we find solutions.

@eunchan, AFAIK we do not consume them from the generated hjson file at the moment. OTP/LC already uses a different mechanism, and the ROM generation / scrambling script does not yet exist.

OK. Thanks for explanation,

On Mar 4, 2021, at 2:21 PM, Michael Schaffner<EMAIL_ADDRESS>wrote:
@eunchan https://github.com/eunchan, AFAIK we do not consume them from the generated hjson file at the moment. OTP/LC already uses a different mechanism, and the ROM generation / scrambling script does not yet exist.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/lowRISC/opentitan/pull/5459#issuecomment-790985979, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJDG3TFFWSS22XYG2CDQJTTCABWDANCNFSM4YTTG7HA.

At the moment, the PR fails CI because of downstream stuff that depends on the contents of the hjson. I'll have a look this morning to see whether there's an easy fix.

Hmm, that's not going to work easily. Let's close this for now and put up with the churn. Hopefully, we can clean up some of the topgen stuff in future.


Road map of aligning the model generations between mgmt/HLC and DPG

Current issues:

https://github.com/Azure/autorest.csharp/issues/3230
https://github.com/Azure/autorest.csharp/issues/3178
https://github.com/Azure/autorest.csharp/issues/3406

To have the model factory (https://github.com/Azure/autorest.csharp/issues/2461), we need to resolve:

https://github.com/Azure/autorest.csharp/issues/3178
To let the model factory include more models (https://github.com/Azure/autorest.csharp/issues/3181), we need to resolve:
https://github.com/Azure/autorest.csharp/issues/3406

All the items Model Factory need is GA-Required

Now our code generator has 3 layers:

Spec -> input models. We have two versions of this:
a. Swagger Spec -> CodeModel Schemas
b. TypeSpec -> Input types
Input models -> Output models. We have two versions of this:
a. CodeModel Schemas -> SchemaObjectType (or derived MgmtObjectType for mgmt plane)
b. Input types -> ModelTypeProvider (for DPG)
Output models -> Writers. We only have one version of this, it works for both SchemaObjectType and ModelTypeProvider.

The differences between the generated models in mgmt/HLC and DPG comes from the differences on those 3 layers. The biggest differences come from the second layer between SchemaObjectType and ModelTypeProvider. Minor differences come from the first layer.
It will be a big change if we use our CodeModelConverter to convert all the CodeModel Schemas to Input Types first and then we all use ModelTypeProvider to generate the models, because we will get differences both from the first layer and the second layer. It might be difficult to distinguish where an unexpected change comes from therefore it is harder to fix them.
I plan to fix this in two steps. We will first re-implement SchemaObjectType to make it mimic everything we did in ModelTypeProvider. For instance, ModelTypeProvider is getting its properties by fields from ModelTypeProviderFields, we will re-implement SchemaObjectType to get its properties by fields from SchemaObjectTypeFields as well, and the implementation of SchemaObjectTypeFields will be exactly the same to ModelTypeProviderFields, etc. This should be done in this PR: https://github.com/Azure/autorest.csharp/pull/3200

FYI @m-nash

Close in favor of https://github.com/Azure/autorest.csharp/issues/3801


Can you make the beta.12 release?

Hello,
Can you please make the beta.12 release here:
https://github.com/react-toolbox/react-toolbox/releases
so I can upgrade cljsjs/react-toolbox to it?

Nevermind, it's not actually needed. The zip file is created even if not linked.


Removing the tooltip on the read-only editor that says 'cannot edit in read-only editor'

Hi,
I tried to remove the tooltip that says 'cannot edit in a read-only editor using CSS. But, it seems that the CSS although applied is not working.
Given below is the screenshot of the issue that I am facing:

Below given is the editor options that I am setting
value: this.configOriginal,     language: 'json',     theme: this.theme,     scrollBeyondLastLine: false,     contextmenu: false,     readOnly: true,     cursorWidth: 0,
And given below is the CSS that I am trying to use to hide the tooltip:
.monaco-alert {   display: none !important;   visibility: hidden !important; }
Can anyone please help me solve this? I have been struggling with this since a long time.
Thank you so much.

It would be nice, if the message tooltip could be customisable. This could be used for explanation of the "custom" reason, why the editor is in read-only state:

"You need to save the file locally before editing"
"Text is locked for editing"
"You are previewing the previous version of the file"

@kubocob Here is something that I tried and should work for your use case.
const editor = /* your editor instance */;
const messageContribution = editor.getContribution('editor.contrib.messageController');
const diposable = editor.onDidAttemptReadOnlyEdit(() => {
  messageContribution.showMessage('Your reason to not allow editing.', editor.getPosition());
});

This code will immediately override the default Cannot edit read-only editor with your custom message.

@rakhtar92 for your requirement, you can do this -
const editor = /* your editor instance */;
const messageContribution = editor.getContribution('editor.contrib.messageController');
const diposable = editor.onDidAttemptReadOnlyEdit(() => {
  messageContribution.closeMessage();
});

This will hide the tootltip immediately. There isn't even a flicker for a moment when closing the tooltip.

@kubocob & @brijeshb42  thanks for the help but it did not work out.
The editorr.getContribution() returns of type IEditorContribution and I checked the d.ts file for monaco-editor there is no such method closeMessage() for IEditorContribution

@rakhtar92 Yeah, typings are not complete also in my project ("monaco-editor": "^0.18.1", - could be fixed in 0.20.0). Therefore I'm ignoring it for now, and retyping toany.
(editor as any).onDidAttemptReadOnlyEdit(() => {
      (messageContribution as any).showMessage('Reason for blocked edit',  editor.getPosition());
});

@rakhtar92 for your requirement, you can do this -
const editor = /* your editor instance */;
const messageContribution = editor.getContribution('editor.contrib.messageController');
const diposable = editor.onDidAttemptReadOnlyEdit(() => {
  messageContribution.closeMessage();
});

This will hide the tootltip immediately. There isn't even a flicker for a moment when closing the tooltip.

I was trying to remove the tooltip, this solution works but I see a flickering. If I override the msg with an empty string, like this:   (messageContribution as any).showMessage('',  editor.getPosition());, it's a little better.
Eventually this is what worked for me (without any flickering):
const messageContribution = editor.getContribution(
  "editor.contrib.messageController"
);
editor.onDidAttemptReadOnlyEdit(() => {
  messageContribution.dispose();
});

Is there a way to access the harness for the tooltip for unit tests?

With https://github.com/microsoft/vscode/commit/052f02175f4752c36024c18cfbca4e13403e10c3, you can just skip the readOnlyMessage contribution (in particular when using the webpack plugin) and provide your own.
This will be available in the next monaco editor release.

@hediet how do you skip the contribution?  I tried to find some documentation on that but couldn't.
As for other suggestions on this thread, somehow none of them worked for me: setting to empty string pops up an empty tooltip, using closeMessage has flicker, and using dispose actually causes the tooltip stay on the screen.
On the other hand, .monaco-editor-overlaymessage { display: none !important; } works and I'll use it as a workaround until I can find a proper solution.


CaptureProtectionListener warning on iOS

Hi, I'm receiving warning every time that i open the app Sending CaptureProtectionListener with no listeners registered.
I think this is because the library is sending the event before the the bridge is ready.
"react-native": "0.73.5"
"react-native-capture-protection": "1.9.6"
iOS 17.4

@rokkoo thanks for report this. i will check it & fix asap


Ability to reliably run code AFTER all tasks have stopped but BEFORE service is registered as finished.

What is wrong
The previous API this library was based on had a _cleanup() method that you could implement that would allow you to implement logic that would run after all tasks have been stopped but before the service registers as finished.
At present, the asyncio service runs all of the background tasks as a DAG with the Service.run() method at the root of the dag.  Upon cancellation, any background task which is cancelled is guaranteed to have had all of it's children cancelled first.   This means that at the point where the Service.run() method is cancelled, it is guaranteed that all other background tasks have completed.  Because of this, the following is a reliable way to run code in the manner specified above.
class MyService(Service):
    async def run(self):
        self.manager.run_task(do_background_thing_a)
        self.manager.run_task(do_background_thing_b)

        try:
            await self.manager.wait_finished()
        finally:
            ...  # do cleanup

While this pattern accomplishes the goal, it requires intimate knowledge of how the service lifecycle functions to understand why this works.  Is this ok?
How can it be fixed.

We could just document this well.  Good documentation examples and guides as well as the explanation above to help explain why it works.
Create a new API where people can embed this logic.

With respect to option 1: I'm inclined to do it this way to keep the library as simple as possible.  I like that a service is just a function... that you can wrap up in a class or put in a plain function and use the as_service decorator.
With respect to option 2:  This would be pretty simple to implement.  I see two obvious options.
class MyService(Service):
    async def run(self):
        self.manager.run_task(do_background_thing_a)
        self.manager.run_task(do_background_thing_b)

        await self.manager.wait_finished()

    async def cleanup(self):
            ...  # do whatever cleanup and then re-raise

#
# OR MAYBE....
#

await run_service(service, cleanup_fn=...)

Both of these suffer from not having an easy way to get context into how/why the service exited where as the try/finally can be implemented as try/except or even if any(sys.exc_info()) to check if an exception is being handled.  In fact, it even allows easy implementation of something like this pattern when it's justified.
class MyService(Service):
    async def run(self):
        self.manager.run_task(do_background_thing_a)
        self.manager.run_task(do_background_thing_b)

        try:
            await self.manager.wait_finished()
        except:
            await self.on_error()
        finally:
            await self.on_exit()
        else:
            await self.on_success()

My inclination is to leave it simple and document these patterns well with good examples that are easy to copy/paste from.
We could even explore a metaclass based solution that keeps the manager unaware of this and implements the pattern above by manipulating the run method on class construction.

Looking at @ralexstokes issue it appears that the following is needed for this to work correctly in trio.
class MyService(Service):
    async def run(self):
        self.manager.run_task(do_background_thing_a)
        self.manager.run_task(do_background_thing_b)

        try:
            await self.manager.wait_finished()
        finally:
            with trio.CancelScope(shield=True):
                await self.on_exit()

Otherwise trio ends up raising another CancelledError upon the next await call since the current scope has been cancelled.

:+1: to document the try/finally for now, and add a cleanup feature if we think that approach becomes cumbersome.

yeah to chime in i think we can get away w/ just documenting the pattern here.
and thanks @pipermerriam for looking into this! i think especially given that we need some extra infrastructure to handle the trio case, its better to just explicitly document for now -- like @carver says if we need to find a more succinct abstraction down the road we can :)


Clarification needed: rejecting confchange

The docstring for apply_conf_change says:
https://github.com/tikv/raft-rs/blob/2357cb22760719bcd107a90d1e64ef505bdb1e15/src/raw_node.rs#L394-L399
Are there any examples when it makes sense to reject a conf change?
What restrictions are imposed on a rejection predicate implementation? Is it implied, that the decision (whether to accept of to reject the conf change) MUST be deterministic and consistent across all instances?

What restrictions are imposed on a rejection predicate implementation?

For example, in TiKV, there is an epoch mechanism, all commands have to match the epoch to be processed. If a confchange is bind to a stale epoch, it will be just skipped even it's committed. Application is free to use any conditions it wants.

Is it implied, that the decision (whether to accept of to reject the conf change) MUST be deterministic and consistent across all instances?

Yes, all nodes must take the same decision when apply the log at the same index.


slide animation broken on phone?

Hello,
This is a weird one... using latest jQTOUCH and DATAZOMBIES a basic "slide" (as in slide left") seems to be totally broken on phone when called via a jqt.goto command.
All other animations seem to work perfectly. Any ideas?
I apologize if this is an already documented issue but I was not finding a lot of specifics.

Sorry, don't have a clue. Try looking through the issues on the parent repo or browsing the google group.
https://github.com/senchalabs/jQTouch
https://groups.google.com/forum/#!forum/jqtouch


Create hrtor.register_command()

hrtor.register_command(
  hrtor.command.new {
    action = function()
      hrtor.api.echo('FooFoo!!')
      hrtor.api.quit()
    end,
    trigger = { 'q' },
  }
)

Perhaps the hrtor.api.echo() needs standard output, so hrtor must be implemented standard output?

well, now the hrtor has no configuration for stdio, so I should not create stdio. I can implement hrtor.api.echo() simply.


[Autocomplete] Streamline Mapping Value to Options

Summary
Currently, when using non-flattened options (e.g., an array of objects), if the value is set to a property such as the id, we must explicitly locate the corresponding option to set it as the selected value. This approach introduces boilerplate code and can lead to errors when interacting with the component. It negatively impacts the developer experience (DX).
It would be great to introduce a valueFromOption or a similar feature to streamline this process, removing the need for the additional code shown below. This enhancement would make the component more generic and adaptable to both flattened and non-flattened options.
Examples
 const selectedValue = flatOptions
  ? value
  : options.find((option) => option.id === value) ?? null;

  return (
    <Autocomplete
      // --- SNIP ---
      options={processedOptions}
      // --- SNIP ---
      value={selectedValue}
    />

Motivation
See above.
Search keywords: autocomplete, options, value

Hey @aress31, thanks for contributing. I'm closing this issue since https://github.com/mui/material-ui/issues/23708 already exists. Feel free to provide more context if you think is needed.

@aarongarciah the ticket you have linked is not related to my request. I would want to see a isValueEqualToOption.


feat: propagate non-dev npm dependencies in js_library deps to direct dependencies of downstream linked npm_package targets

This also fixes the bug where "dev" dependencies in the data attribute are incorrectly propagated to the direct dependencies of downstream linked npm_package targets.
Once landed, downstream build rules such as ts_project will be updated to follow the same pattern.

Needs rebase.


Is it possible to hook Dva store to Reactotron?

Reactotron
Anyone managed to achieve it?
I tried following the Reactotron-redux-saga plugin but it didn't work.

Reactotron need to create store use his method, so we can't use it with dva now.

@sorrycc, you could try an approach similar to https://github.com/rematch/rematch for integrating reactotron. See notes: https://rematch.gitbooks.io/rematch/docs/recipes/devtools.html.
Though I feel this is primarily an issue with Reactotron, rather than Dva.


Locations of bounding boxes in CSV

Include the corners of the bounding boxes in the exported CSV file as

normalised (i.e. between 0 and 1)
actual coords in thumbnail
actual coords in full-res image

Requested by Paul Flemons and Rhiannon Stephens at the Australian Museum.

Add columns to export

NormalisedLeft, NormalisedTop, NormalisedRight, NormalisedBottom
ThumbnailLeft, ThumbnailTop, ThumbnailRight, ThumbnailBottom
OriginalLeft, OriginalTop, OriginalRight, OriginalBottom


FIX: /auth redirects to / endpoint even if custom prefix setup

Description
Fixes (issue #) #1148
The issue is marked as fixed however the prefix still doesn't work if https://APP_HOST/ doesn't return 302 to auth endpoint.
Type of change

koa-shopify-auth: Patch: Bug

@TheMallen @alexandcote @vsumner @ismail-syed Could you please have a look at this one please? Really appreciate that.

@ismail-syed Could we merge this one please?

@dooman87 merged, sorry for the delay!

this causes https://github.com/Shopify/quilt/issues/1550

this causes #1550

Argh, you are right, sorry. I didn't wait until release and used my fork without latest changes to default value :(

From https://github.com/Shopify/quilt/pull/1428#discussion_r423024904:

I don't think we should set prefix here. The path that the application lives on is orthogonal to the paths that the OAuth logic lives on. (You can tell this because the verifyRequest middleware can be applied separately from the shopifyAuth middleware.)
In a separate PR, however, I'd be open to a couple alternatives:

A new applicationUrl configuration option that would specify the path to direct the user when cookie access is enabled.
Logic to pass a returnTo value through query params. (We do this in shopify_app, though it's pretty complex IIRC.)

and https://github.com/Shopify/quilt/pull/1440#issuecomment-628436387:

I agree with @ragalie that the prefix shouldn’t apply to appTargetUrl. E. g. my prefix is /api for all the back-end routes (requirement of Next.js API routes), but the front-end app lives under / and sending the user to /api would result in a 404.

Not that it bothers me greatly because I'm maintaining my own copy of koa-shopify-auth now, but you might want to re-consider this "fix".

From #1428 (comment):

I don't think we should set prefix here. The path that the application lives on is orthogonal to the paths that the OAuth logic lives on. (You can tell this because the verifyRequest middleware can be applied separately from the shopifyAuth middleware.)
In a separate PR, however, I'd be open to a couple alternatives:

A new applicationUrl configuration option that would specify the path to direct the user when cookie access is enabled.
Logic to pass a returnTo value through query params. (We do this in shopify_app, though it's pretty complex IIRC.)

and #1440 (comment):

I agree with @ragalie that the prefix shouldn’t apply to appTargetUrl. E. g. my prefix is /api for all the back-end routes (requirement of Next.js API routes), but the front-end app lives under / and sending the user to /api would result in a 404.

Not that it bothers me greatly because I'm maintaining my own copy of koa-shopify-auth now, but you might want to re-consider this "fix".

I see where you are coming from and I think having two separate prefixes would be a good solution. However, I think using prefix in appTargetUrl is better cause if your app is deployed under that prefix and you only have control over that prefix then you still could workaround the problem using redirects.

However, I think using prefix in appTargetUrl is better

Not sure how this is better than being able to configure api and app prefix separately? Or do you mean it's better than not applying any prefix to appTargetUrl? I get your point, I can create api/index.ts and redirect to /.
It's just that this is a breaking change not just a "fix", because I'm using a prefix for the api only (/api) and if I updated this patch version, it would suddenly break my app 😐
Also, if I used a prefix the way you are, I'd still need two separate prefixes, e. g. /shopify and /shopify/api.

However, I think using prefix in appTargetUrl is better

Not sure how this is better than being able to configure api and app prefix separately? Or do you mean it's better than not applying any prefix to appTargetUrl? I get your point, I can create api/index.ts and redirect to /.
It's just that this is a breaking change not just a "fix", because I'm using a prefix for the api only (/api) and if I updated this patch version, it would suddenly break my app 😐 (which is just another reason I'm not confident to use this package yet and rather maintain a copy)
Also, if I used a prefix the way you are, I'd still need two separate prefixes, e. g. /shopify and /shopify/api.

Yup, you would still need two separate routes for /app-prefix and /app-prefix/auth.
I think you are right and we did need to bump major version in this case. Sorry, I thought it's just a bug cause saw a ticket and then PR you mentioned above that's been closed because of big refactor. That was my first app and first experience with next.js and this package. Turned out to deploy the whole thing under prefix is quite challenging and I regret not using subdomain in the first place :)

Turned out to deploy the whole thing under prefix is quite challenging

https://nextjs.org/blog/next-9-5#customizable-base-path


Unzipping index on Android

Geode Issue

[X] I confirm that this bug is NOT related to a mod but directly to Geode Loader itself.

Platform
Android64
SDK commit
No response
Geode Version
V2.0.0-beta.16
Mods Installed
No response
Expected Behavior
Expected to get all mods listed after unzipping index.
Actual Behavior
Keeps on repeating "unzipping index..." Over and over after 5+ minutes.
Steps to Reproduce

open geode
launch GD
click the geode button
click the "download" tab

Additional Information
I do not know if this is a device issue or something directly related to geode. A short time ago I could still see the mods, but after one geode update, it just repeats unzipping index forever.

same problem here but with updating local cache

doesn't work on a fresh android install, now i have to download mods manually :((


How can I know if a field is nil (because .Optional()) or empty?

Now that I am about to finish my migration from Bun, I have discovered a terrible problem!
Given this schema:
type Player struct{ ent.Schema }

func (Player) Fields() []ent.Field {
  return []ent.Field{
    field.String("nick"),
    field.String("description").Optional(),
  }
}

If I get player from DB with:
player, err := tx.Player.Query().Where(entPlayer.ID(id)).First(ctx)
// handle err

though description is correctly NULL in the DB Ent instead of using *string for it on player uses "" an empty string!
This is a big, huge problem because our domain entities are using *string for this (like gqlgen) and in our adapters from/to domain we need to check nillness on ent structs, like:
func convertEntPlayerToDomain(entPlayer *ent.Player) *domain.Player {

  // I cannot do this:
  if entPlayer.Description != nil {
    //doSomething...
  }

  return domain.UnmarshalPlayerFromRepo(
    entPlayer.ID,
    entPlayer.CreatedAt,
    entPlayer.UpdatedAt,
    entPlayer.Nick,
    entPlayer.Description, // domain.Player.Description is *string, ent.Player.Description is string instead
  )
}

How can I know if ent.Player.Description is nil or an empty string?

Hey! Set the field to be both Optional() and Nillable(). This will solve your issues.
See: https://entgo.io/docs/schema-fields#nillable

Closing, but please open it if you still need help. Thanks 😎

Yeah. I think it works. How many things to set!

Thanks!


Speech Recognition not working

I am trying to use speech recognition on python 3.8 i am fairly new to programming and i have tried multiple solution such as using pip to install pyaudio but it says "Command 'pip' not found but there are 18 similar ones" the code i am using is:
import speech_recognition as sr
r = sr.Recognizer()
with sr.Microphone() as source:
print("Say something!")
audio = r.listen(source)
try:
print("You said: " + r.recognize_google(audio))
except sr.UnknownValueError:
print("Google Speech Recognition could not understand audio")
except sr.RequestError as e:
print("Could not request results from Google Speech Recognition service; {0}".format(e))
the error i get is:
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/isaac/.config/JetBrains/PyCharmCE2020.2/scratches/scratch.py", line 5, in
with sr.Microphone() as source:
File "/usr/local/lib/python3.8/dist-packages/speech_recognition/init.py", line 79, in init
self.pyaudio_module = self.get_pyaudio()
File "/usr/local/lib/python3.8/dist-packages/speech_recognition/init.py", line 110, in get_pyaudio
raise AttributeError("Could not find PyAudio; check installation")
AttributeError: Could not find PyAudio; check installation
Process finished with exit code 1
I am using Ubuntu 20.04 and using the software pycharm

@Dave234322 there’s probably configuration in pycharm that you need to do to point to the correct Python installation. Try to run it from the terminal and see if you get the same thing. If you do you probably need to install pip.
For Ubuntu it should just be
sudo apt install python3-pip

install pip and later that install pyaudio.
sudo apt install python3-pip
pip3 install pyaudio

Reinstall Python in your compuer .This time tick the check box Add Python 3.x to PATH(When installs you may have not given it

.Sometimes python command doesn't work because of it.)
Then install by using pip
pip install pyaudio-to install
pip uninstall pyaudio-to uninstall
if yhe above install didn't work try - pip install pipwin then pipwin install pyaudio


docs: move CodeIgniter 3 sample code to ci3sample folder

Description
See  #5765
Checklist:

[x] Securely signed commits
[ ] Component(s) with PHPDoc blocks, only if necessary or adds value
[ ] Unit testing, with >80% coverage
[x] User guide updated
[ ] Conforms to style guide

This makes sense. I will check how this affects the renumerste script


CORS

Issue #39
As mentioned in this issue, requests from web frontend fails because of CORS. It seems that this is because of position of common middleware in list of middlewares.

Codecov Report

Merging #40 (4c79b8c) into dev (c13b9a4) will increase coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev      #40      +/-   ##
==========================================
+ Coverage   70.89%   71.08%   +0.18%
==========================================
  Files          17       17
  Lines         536      536
==========================================
+ Hits          380      381       +1
+ Misses        156      155       -1

Impacted Files
Coverage Δ

backend/backend/settings.py
100.00% <ø> (ø)

backend/risk_factors/tests/test_setup.py
98.70% <0.00%> (+1.29%)
:arrow_up:

Continue to review full report at Codecov.

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


Run android emulator integration tests in one shard

There is non-trivial overhead in configuring and starting an AVD on LUCI. We should be able to run multiple flutter drive tests on a single shard called Linux android integration. This can be done after we bring more integration tests online.

@ricardoamador was this fixed with your work on emulators?

No I don't believe so. I am not sure if Gary was able to do any work here or if this was expected to be an infra only effort. I would think this is possible if the test runner is set up to run tests like this.

Removing infra label as the remaining work is in the test implementation side


The name of 'DevOps Project' is wrong in branch detail page

Versions Used
KubeSphere:  dev:latest

/priority low
/area devops
/cc @kubesphere/sig-devops
/kind bug
/milestone BackLog

hi @xuliwenwenwen, please point out which PR fixed this issue.

hi @xuliwenwenwen, please point out which PR fixed this issue.

https://github.com/kubesphere/console/pull/2133

issue fixed ks3.2-alpha.0


Automatically include emscripten libc headers when building on wasm32 targets

Currently, to build a sys crate with cc for for wasm32-unknown-emscripten and wasm32-unknown-unknown targets, it is necessary to vendor a copy of the emscripten libc headers for each crate using cc in its build.rs.
This also requires adding an explicit include path to pick up these headers.
Doing so results in lots of macro redefinition warnings.
Is it possible to replace the -isystem include path with emscripten headers when building wasm32 targets? This would make it much easier to support these targets and would not require forking each sys crate I depend on.

Thanks for the report! This is unfortunately work I'm not willing to do though. In general this crate purely tries to hook up existing system toolchains with Rust code. There's a ton of thorny questions in trying to vendor/include headers for targets, so I'd prefer to not do that.


releaser implicit deps

this additionally needs to explain:
deps missing:

build-essential
libssl-dev
pkg-config
 libgtk-3-dev (rfd)

build-essential
devscripts
debhelper version 13 or higher
needed to package deb packages

snapcraft needed for snap


add functionality for retrying failed HTTP requests

Description
I've updated the library so that it implements a "backoff" retry strategy when it comes to failed HTTP requests.
If a request fails, the process will delay for a specified amount of time before resubmitting the request a specified number of times. Both values are configurable, but the default retry count is 3 with a delay of 5 seconds. Each time the process retries the request, it will increase the delay.
As an example, an error scenario with the default values might look like this:

Submit HTTP request, which fails with an error code.
Wait 5 seconds.
Submit HTTP request, which again fails with an error code.
Wait 10 seconds.
Submit HTTP request, which again fails with an error code.
Process discontinues and reports the last error. If the retry count were higher, then the delay would increase to 15 seconds, then 20 seconds, then 25 seconds, etc.

A success scenario with the default values might look like this:

Submit HTTP request, which fails with an error code.
Wait 5 seconds.
Submit HTTP request, which succeeds.
Process continues.

In an error scenario, only the last error is reported. In both success and error scenarios, any failures that are not the last error will be reported in the results as a new "retry error."
The primary change is the addition of a new utility function called exponentialRetry(). The function accepts another function, which it will invoke using the retry functionality described. It receives options that control the number of times to retry, the retry delay, and an optional callback that will be invoked each time there is a retry error.
The majority of the remaining changes are related to reporting errors that cause a retry but don't fail the entire process. They are reported as a new item in the results. Additional code is for the new unit tests.
Related Issue
Issue #1
Motivation and Context
HTTP can be unreliable at times. By automatically retrying failed HTTP requests, the library can have some handling of (for example) intermittent network issues.
How Has This Been Tested?
Added unit tests for the new method that handles retrying a function. Also added unit tests for covering the success scenario described above for the "initiate," "part," and "complete" HTTP requests. Also verified that existing unit tests continue to pass.
Screenshots (if appropriate):
N/A
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

@FrancoisZhang @bobvanmanen Please note that tomorrow will mark 3 full days since this PR was opened, so I'll plan on merging by end of day tomorrow unless I hear otherwise. Feel free to provide any feedback (if you have any) before then. Thanks for your help!


Investigate weird oscillation in main

@chapulina @arjo129 Does this jittery oscillation also happen at depth or is it just on the surface? Is the buoyancy plugin accounting for partially submerged volumes etc? Thanks

Does this jittery oscillation also happen at depth or is it just on the surface? Is the buoyancy plugin accounting for partially submerged volumes etc?

We have uniform buoyancy everywhere right now, no distinction between water and air until #38 is addressed. So the depth shouldn't make a difference here.


shifted docker image link to FOSSASIA account

Fixes issue #39
Changes: shifted docker image link to FOSSASIA account

@betterclever @saurabhjn76 @dynamitechetan Kindly review this PR.


Improve support of rejections thrown from the CommandBus filters

This PR partially addresses https://github.com/SpineEventEngine/web/issues/6.
Currently, the Ack received from a command filter can contain either OK status, Error, or rejection Event.
While the first two cases are well-supported in the current implementation, the rejection field is not really expected to be populated.
Per vocal discussion, it was decided that receiving a rejection in a command filter is actually a valid use-case, and thus this PR tweaks the core to support such a case. The system context will post the corresponding system events when the command is rejected this way, and the provided rejection event will be posted to the EventBus.
Other changes

BusFilter interface is expanded with shortcut methods for the convenient Ack creation.
The command and event filters are included in the bounded context testingCopy() and can thus be specified on BlackBoxContext creation.
The AbstractCommandHandler will post the corresponding events when its handler method invocation leads to a rejection.

The library version advances to 1.5.27.

@armiol PTAL.

@armiol PTAL again.


[WIP] Testing Julia 0.6 compat

Just a test to know if tests are still passing with Julia 0.6
Related https://github.com/andrewadare/LibSerialPort.jl/issues/20#issuecomment-416032000

Closing as LibSerialPort does not support Julia < 0.7, and version prior to this are no longer maintained.


2024 University of Waterloo Fall Kickoff Race

@ProjectNeura/vec
Hi all,
Data and feedback from the 2024 University of Waterloo Fall Kickoff Race shall be posted here.

main.csv

@aforti86 Do we have the table of lap times?

dataset: "data/main.csv"

jobs:
  - name: Task 1
    uses: bake
  - name: Task 2
    uses: process
    with:
      vehicle_hit_box: 2  # default: 3
      min_lap_time: 50  # default: 30 (seconds)
  - name: Draw Lap 16
    uses: draw-lap
    with:
      lap_index: 15
  - name: Draw Comparison of Laps
    uses: draw-comparison-of-laps
    with:
      width: 0.3  # default: 0.3

Investigation of Controller Disconnections
Finally, I have some time to investigate the sensor system failure that occurred on October 5th. It is confirmed that the disconnections between controllers were caused by the USB socket overheating.


Clarification of bracketSpacing option

I'm not 100% sure what the bracketSpacing config does.
These explanations:

// Controls the printing of spaces inside object literals from the README.md
// Controls the printing of spaces inside arrays and objects from the atom package settings page

When using, the following code:
// source:
let list = [{
    name: "foo",
    value: "bar"
  },{
    name: "bar",
    value: "baz"
  }];

The output is always the same, wether bracketSpacing is used or not (cli or atom plugin):
// output:
let list = [
  {
    name: "foo",
    value: "bar"
  },
  {
    name: "bar",
    value: "baz"
  }
];

I'm assuming I'm just expecting something its not designed to do.  With bracketSpacing disabled, I would have expected it to stay more dense.  Any clarification would be great. Thanks!

That config only makes a difference when the object fits on a single line:
const obj1 = { a: 1, b: 2, c: 3 }; // bracketSpacing: true
const obj1 = {a: 1, b: 2, c: 3}; // bracketSpacing: false

Ahh... ok great.  Perhaps is just a README/doc update then.  I'd be happy to PR the README change if it would be helpful.

@benjaminapetersen would be awesome to give examples of what each options look like in the readme!

Cool.  So I'm curious, there are very few options (implying opinion is good), why even have bracketSpacing as an option at all?  Seems like this one & trailingComma (suppress) are just worth enforcing.  However, printWidth, tabWidth, and singleQuote seem like basic essential settings.

Making trailing commas the default seems like a good idea! @jlongster we could use that option for the es7 trailing commas. I don't think that trailing commas are very controversial

I'm also curious about why the bracketSpacing options exists at all. printWidth, tabWidth and singleQuote are things I could easily see people starting flame wars over, but bracketSpacing?

People are pretty opinionated about trailing commas, and I think it's worth having it as an option. However, I am open to removing the bracketSpacing option. I haven't seen many people talk about it or use it. I think it's mainly there because recast had that option.

The new docs have it clarified


Update ammonite-compiler, ammonite-repl, ... to 3.0.0-M2-9-88291dd8

About this PR
📦 Updates

com.lihaoyi:ammonite-compiler
com.lihaoyi:ammonite-repl
com.lihaoyi:ammonite-repl-api

from 3.0.0-M2-8-ba4429a2 to 3.0.0-M2-9-88291dd8
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.lihaoyi" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.lihaoyi" }
}]

labels: library-update, early-semver-pre-release, semver-spec-pre-release, commit-count:1

Superseded by #1379.


MSDKUI-1940: Clean up code

Removed unused code
Fixed spelling mistakse
Adapted time parsing to older Android API
Minor changes to code

Signed-off-by: Ants Peetsalu<EMAIL_ADDRESS>

Codecov Report

Merging #108 into master will increase coverage by 1.64%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #108      +/-   ##
===========================================
+ Coverage     73.06%   74.7%   +1.64%
+ Complexity     1640     995     -645
===========================================
  Files           129      69      -60
  Lines          5662    3938    -1724
  Branches        872     437     -435
===========================================
- Hits           4137    2942    -1195
+ Misses          856     749     -107
+ Partials        669     247     -422

Impacted Files
Coverage Δ
Complexity Δ

...e/msdkuiapp/routing/RoutingInstructionsFragment.kt

...java/com/here/msdkuiapp/common/PermissionsUtils.kt

.../com/here/msdkuiapp/routing/OptionPanelFragment.kt

...ere/msdkuiapp/routing/RouteManeuverListFragment.kt

.../here/msdkuiapp/routing/SubOptionPanelPresenter.kt

...m/here/msdkuiapp/routing/SubOptionPanelFragment.kt

...msdkuiapp/guidance/GuidanceNextManeuverFragment.kt

...com/here/msdkuiapp/routing/OptionPanelPresenter.kt

...m/here/msdkuiapp/position/AppPositioningManager.kt

...ain/java/com/here/msdkuiapp/about/AboutActivity.kt

... and 51 more

Continue to review full report at Codecov.

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


Request Transformer Plugin Not working properly

Summary
we are using Request/Response transformer plugin
kong for kubernetes
we are able to see response headers modified  after using the response-transformer plugin (created the kong plugin crd)
but we are unable to see the request header modification.
Steps To Reproduce
1.kong for kubernetes
2.created CRD for request transformer plugin
Name:         add-req-headers
Namespace:    kong
Labels:
Annotations:
API Version:  configuration.konghq.com/v1
Config:
Append:
Headers:
X-Forwarded-Proto: https
demo: test
Kind:  KongPlugin
Metadata:
Creation Timestamp:  2020-03-09T09:34:49Z
Generation:          3
Resource Version:    2371014
Self Link:           /apis/configuration.konghq.com/v1/namespaces/kong/kongplugins/add-req-headers
UID:                 082a0b0b-9b23-4348-9e9e-f3d9af35d7d0
Plugin:                request-transformer
Events:

not able to see any header modification
Not sure what am I missing ?

Additional Details & Logs

Kong version ($ kong version)
Kong debug-level startup logs ($ kong start --vv)
Kong error logs (<KONG_PREFIX>/logs/error.log)
Kong configuration (the output of a GET request to Kong's Admin port - see
https://docs.konghq.com/latest/admin-api/#retrieve-node-information)
Operating system

Forwarded headers are special, see alternative way:
https://github.com/Kong/kong/pull/5561#issuecomment-585868854


Facebook login from embedded browser error

🐛 Bug Report
I'm planning to integrate my app using Facebook login. But on some Android phone, when LoginManager.logInWithPermissions function is called, it often opening a Facebook Login page while the device is actually already had Facebook app installed and already in a logged in state. Even after I trying to log in using by email and password, it still won't let the user to log in. It show For your account security, logging into Facebook from an embedded browser is disabled.
(see attached video below)
I already set the LoginBehaviour to LoginManager.setLoginBehavior('NATIVE_WITH_FALLBACK') and the device already had native Facebook app installed and the Facebook app is also already in logged in state.
To Reproduce
Here's the code I use to login to Facebook
LoginManager.setLoginBehavior('NATIVE_WITH_FALLBACK');
LoginManager.logInWithPermissions(["ads_management", "pages_manage_ads", "leads_retrieval", "pages_manage_metadata", "pages_read_engagement"]);

Expected Behaviour
It should open a Facebook app with the current logged in state.
Environment
React Native version : 0.65.2
react-native-fbsdk-next version: 10.1.0
Android device used: Samsung Galaxy Note 20 Ultra
Android version: 12
Facebook app installed version: 3<IP_ADDRESS>.111
https://user-images.githubusercontent.com/47311555/197615710-db018481-cf4c-4351-956c-8f2c0b2d81b0.mp4

Upstream: https://github.com/facebook/facebook-android-sdk/issues?q=is%3Aissue++for+your+account+security+logging+into+facebook+from+an+embedded+browser+is+disabled

@mikehardy Hi Mike, thank you for the response. This issue is happened only to some device sometimes. Do you had any idea why it failed to login while I already had the Facebook app installed (and logged it) and I don't set the LoginBehaviour to using webview?
From the video that user sent to me (attached above) it's also look like it open a Facebook app instead of Chrome custom tab (it didn't show X button on top left) or a webview (it didn't show as a dialog). Why the app still think it logged in an embedded browser?

I'm sorry, I don't know. This might be something to approach the facebook-android-sdk team with, bearing in mind that they are a native SDK, not a react-native SDK, so you should be familiar with the way the module here uses the SDK API calls
https://github.com/thebergamo/react-native-fbsdk-next/blob/3ec1bd3d4512f1cf4aceb23c59724f4d1d17d4c5/android/src/main/java/com/facebook/reactnative/androidsdk/FBLoginManagerModule.java#L139-L163

@mikehardy okay, I'll try asking on the facebook-android-sdk github page. Thank you Mike. Really appreciate your help and quick responses. 🙏🏼

@ibrahim-musa Did you ever get to the bottom of this behavior?

From the video that user sent to me (attached above) it's also look like it open a Facebook app instead of Chrome custom tab (it didn't show X button on top left) or a webview (it didn't show as a dialog). Why the app still think it logged in an embedded browser?

I am able to recreate this myself; the Facebook native app is handling auth, however it is still complaining about the webview. Doesn't seem, then, like something that this SDK can do much about. This comment seems to imply that the issue is with Firefox (my default mobile browser) but AFAICT Firefox isn't being used by the Firefox app to handle the login.
Curious if you ever were able to figure this one out.

May I ask why this issue is closed? I can't get Facebook Login to work on Android no matter what.. Thanks for any hints


Write API key to disk

@Jin1L @jackparmer asked me to write getter and setter method in flojoy utils so that they can be imported from flojoy package and used by Django server. I'm done with that just waiting for approval. So the getter and setter method in LOADER node is redundant IMO.

Hey @Jin1L, @jackparmer asked me to write getter and setter method in flojoy utils so that they can be imported from flojoy package and used by Django server. I'm done with that just waiting for approval. So the getter and setter method in LOADER node is redundant IMO.

Hey @smahmed776, thanks for letting us know! Could you ping us on Slack when it is approved?

Hey @Jin1L, @jackparmer asked me to write getter and setter method in flojoy utils so that they can be imported from flojoy package and used by Django server. I'm done with that just waiting for approval. So the getter and setter method in LOADER node is redundant IMO.

Hey @smahmed776, thanks for letting us know! Could you ping us on Slack when it is approved?

Yes, I'll let you know once it is approved!


tests: try to stablize the deadlock integration test cases

Signed-off-by: cfzjywxk<EMAIL_ADDRESS>
What is changed and how it works?

Issue Number: Close #12619
What's Changed:

This commit intends to stabilize the deadlock detection integration test cases.

Though this might be a temporary solution because using sleep could not control lock orders accurately especially
if some commands are processed slowly in the CI environment, it introduces low cost.

Changes:
- The sleep time is increased to 300ms to avoid assertion failures in the issue.
- The retry limit is increased to 5 to avoid missing expected deadlock results.

Check List
Tests

Integration test

Release note
None

/merge

/test


Make the Laradock the official docker image from Laravel

The last Laravel survey reveal us, that one thing that the community would like to see in the next steps to the framework is having the official docker image.
Maybe we could adapt or even create a specific branch of Laradock to provide that.
This topic could be improve to plan it with more details.

@luciano-jr Very good idea, we should definitely investigate this further. We could contact the guys @ https://github.com/laravel/laravel to see if they would be open to it.
@laradock/admins What do you guys think?

What a great plan!  👍

Great news.

Yes it's great idea, it's the first thing I thought about when reading that survey 2 days ago.
Make Laradock official. Support this by retweeting https://twitter.com/Mahmoud_Zalt/status/818825430350315522

@Mahmoudz I am all for an official docker repo and this package is a great start. Curious if Taylor et al would make it happen though.  For most part, they follow the Not Invented Here syndrome much like other leaders.

@Mahmoudz well, looks like Taylor is keen on this repo, doesn't want to maintain.  What (if any) issues are open that need cleaning or fixing to clean up any rough edges

I'm not sure I understand the reservation on that point, LaraDock is self-sufficient. We can definitely clean up some more issues but is that the actual problem or just a nice to have?
From what I gather, the community is asking for Docker support of Laravel which is exactly we are doing. Is there a difference in ideology getting in the way?

@philtrep I don't have a problem with it at all.  I am merely stating how the Laravel community would react as a whole.  I don't care where it comes from so long as it works!

@mikeerickson I see, we'll do my best to clean up. I have to say that re-reading Taylor's tweet I think that it's the word Official he find implies too much responsibility. I'd be happy for this community even if we only got a single line under the Server Requirements.

Alternatively, you can use LaraDock (unofficial) for Docker support.

In the end I think most Laravel users think like you do: if it works, who cares where it's from.

@philtrep I have tried LaraDock in the past, but at the time, I had to decide quickly between using Docker and Vagrant as I had to get to work ASAP.   I do recall when trying it in the last, had some pain points and moved on to Vagrant (Homestead).
However, now I have more time to invest in getting the Docker implementation working and am doing that now.
I will report back and report where those pain points and you can decide accordingly how they will be addressed (if necessary).

@philtrep One thing that I recall needing in my previous attempt was better node support?  I will make notes as I progress today :-)

@mikeerickson Sounds great, I look forward to your feedback!

rather than making this an official repo, i think we should focus on Making this Production Ready...
And Ready for scalability , Also we Should Limit the number of stacks that we would maintain...
basically we can add unlimited images, but that would sucks and confuse many people...
maybe we can have a Core Stack, where we have the basic
php , mysql , redis , nginx , laravel, node
then a plugin stack , for example HAProxy and etc...
I think that would be a better approach to make this repo more maintainable...
rather than keep this thing expanding to the core...

Personally, I think it's should focus more to be the "the PHP default stack" than "Laravel default". Of course Laravel can adopt the "PHP default stack" has is "official stack"...
I know it started with laravel, but I think it will be greatly beneficial to have on tools to serve all major PHP app and framework. Most of use use more than just one framework.
In my vision, it's a matter of time before project like that will have GUI and replace stuff like MAMP.


Update aseprite to 1.2-beta12

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if updating a cask:

[ ] If the sha256 changed but the version didn’t,
provide public confirmation by the developer: {{link}}

Looks like 1.1.13 has been removed, download 404s. Updated to the beta on the homepage.


pianobar: 2016.06.02 -> 2018.06.22

Motivation for this change
Update pianobar to latest version.
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[X] Fits CONTRIBUTING.md.

Success on aarch64-linux (full log)
Attempted: pianobar
Partial log (click to expand)
install -m644 contrib/pianobar.1 /nix/store/gnilx195gx3n4yv6vb1b1f85ii5hfa53-pianobar-2018.06.22/share/man/man1/
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/gnilx195gx3n4yv6vb1b1f85ii5hfa53-pianobar-2018.06.22
shrinking /nix/store/gnilx195gx3n4yv6vb1b1f85ii5hfa53-pianobar-2018.06.22/bin/pianobar
gzipping man pages under /nix/store/gnilx195gx3n4yv6vb1b1f85ii5hfa53-pianobar-2018.06.22/share/man/
strip is /nix/store/y4ymnvgxygpq05h03kyzbj572zmh6zla-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/gnilx195gx3n4yv6vb1b1f85ii5hfa53-pianobar-2018.06.22/bin
patching script interpreter paths in /nix/store/gnilx195gx3n4yv6vb1b1f85ii5hfa53-pianobar-2018.06.22
checking for references to /build in /nix/store/gnilx195gx3n4yv6vb1b1f85ii5hfa53-pianobar-2018.06.22...
/nix/store/gnilx195gx3n4yv6vb1b1f85ii5hfa53-pianobar-2018.06.22

Success on x86_64-linux (full log)
Attempted: pianobar
Partial log (click to expand)
install -m644 contrib/pianobar.1 /nix/store/swvzssxffnqqvc7ic707drnla178b47v-pianobar-2018.06.22/share/man/man1/
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/swvzssxffnqqvc7ic707drnla178b47v-pianobar-2018.06.22
shrinking /nix/store/swvzssxffnqqvc7ic707drnla178b47v-pianobar-2018.06.22/bin/pianobar
gzipping man pages under /nix/store/swvzssxffnqqvc7ic707drnla178b47v-pianobar-2018.06.22/share/man/
strip is /nix/store/h0lbngpv6ln56hjj59i6l77vxq25flbz-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/swvzssxffnqqvc7ic707drnla178b47v-pianobar-2018.06.22/bin
patching script interpreter paths in /nix/store/swvzssxffnqqvc7ic707drnla178b47v-pianobar-2018.06.22
checking for references to /build in /nix/store/swvzssxffnqqvc7ic707drnla178b47v-pianobar-2018.06.22...
/nix/store/swvzssxffnqqvc7ic707drnla178b47v-pianobar-2018.06.22


add git-xcp

thanks

hello, maybe your ci build has some following issues.
It has nothing to do with my commit. (my url was passed)
Issues :-(

Links

https://www.localytics.com/ Connection reset by peer - SSL_connect
301 https://github.com/glock45/swifter → https://github.com/httpswift/swifter
https://www.rephrase.io SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

Dupes
None ✓

Checking, thanks

@metasmile confirmed, the issues found in CI do not have to do with your commit, will be fixed separately


pull request for e2e test at 11/27/2016 08:26:05

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


can this theme work on anther qt app

Yes.

why radio buttons and check boxes don't work

You mean that they don't change when you press on them?

i have updated the comment

How are you loading the theme?
Please take a look at https://github.com/mumble-voip/mumble/blob/master/src/mumble/Themes.cpp

Hey david, the theme wasn't built to be a complete QT gui replacement theme, but a specific theme for the elements Mumble uses. If you want to use it as a start go ahead (I'd also consider deleting any Mumble specific things) but you'll have to add the missing elements yourself. Cheers and good luck

How are you loading the theme?

        QFile styleFile( "s.qss" );
        styleFile.open( QFile::ReadOnly );
        QString style( styleFile.readAll() );
        qApp->setStyleSheet( style );

just the checkbox and the radiobuttons don't work

Please refer to the appropriate Qt styling documentation for that.
It has been pointed out if/how you can use it, and it seems you had success. It has been pointed out that this is not a Qt theme, but Mumble specific Qt style rules, and that you may have to implement additional style definitions if you use elements not used by Mumble.
As this is unrelated to our mumble theme, and it looks like there is no activity here anymore, and everything has been said, I'm closing this.


Feature/update process checklist

Description
New Process checks given mapping with 42001
Motivation and Context
[Explain the motivation or the context behind this pull request. Why is it necessary?]
Type of Change

feat: update process checklist
How to Test

Install updated process checklist aiverify.stock.process_checklist-0.9.3.zip.
Create new project with stock template
Verify that the changes has been made to the process checklist summaries and user inputs.

Checklist
Please check all the boxes that apply to this pull request using "x":

[x]  I have tested the changes locally and verified that they work as expected.
[ ]  I have added or updated the necessary documentation (README, API docs, etc.).
[ ]  I have added appropriate unit tests or functional tests for the changes made.
[ ]  I have followed the project's coding conventions and style guidelines.
[ ]  I have rebased my branch onto the latest commit of the main branch.
[ ]  I have squashed or reorganized my commits into logical units.
[ ]  I have added any necessary dependencies or packages to the project's build configuration.
[x]  I have performed a self-review of my own code.
[x]  I have read, understood and agree to the Developer Certificate of Origin below, which this project utilises.

Screenshots (if applicable)
[If the changes involve visual modifications, include screenshots or GIFs that demonstrate the changes.]
Additional Notes
[Add any additional information or context that might be relevant to reviewers.]

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
   have the right to submit it under the open source license
   indicated in the file; or

(b) The contribution is based upon previous work that, to the best
   of my knowledge, is covered under an appropriate open source
   license and I have the right under that license to submit that
   work with modifications, whether created in whole or in part
   by me, under the same open source license (unless I am
   permitted to submit under a different license), as indicated
   in the file; or

(c) The contribution was provided directly to me by some other
   person who certified (a), (b) or (c) and I have not modified
   it.

(d) I understand and agree that this project and the contribution
   are public and that a record of the contribution (including all
   personal information I submit with it, including my sign-off) is
   maintained indefinitely and may be redistributed consistent with
   this project or the open source license(s) involved.

Pending updates:

Fix line spacing for 12.7.1
Correct wording for 9.6.2

This should be released with PR #291

Pipeline Testing Passed. Screenshot Attached.
Pipeline Testing For Dev Script.zip
Pipeline Testing For Docker.zip


buildah/Dockerfile is broken

$ cat buildah/Dockerfile | docker build -
[+] Building 108.9s (5/5) FINISHED
 => [internal] load Dockerfile                                                                                0.0s
 => => transferring dockerfile: 1.09kB                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/centos:latest                                                                                2.0s
 => CACHED [1/2] FROM docker.io/library/centos@sha256:6f6d986d425aeabdc3a02cb61c02abb2e78e57357e92417d6d58332856024faf                                                  0.0s
 => ERROR [2/2] RUN   yum -y install     make     golang     bats     btrfs-progs-devel     device-mapper-devel     glib2-devel     gpgme-devel     libassuan-devel   106.8s
------
 > [2/2] RUN   yum -y install     make     golang     bats     btrfs-progs-devel     device-mapper-devel     glib2-devel     gpgme-devel     libassuan-devel     libseccomp-devel     ostree-devel     git     bzip2     go-md2man     runc     skopeo-containers &&   mkdir ~/b
uildah &&   cd ~/buildah &&   export GOPATH=`pwd` &&   git clone https://github.com/opencontainers/runc ./src/github.com/opencontainers/runc &&   cd /src/github.com/opencontainers/runc &&   git checkout  &&   make runc &&   mv runc /usr/bin/runc &&   cd / &&   git clone h
ttps://github.com/projectatomic/buildah ./src/github.com/projectatomic/buildah &&   cd /src/github.com/projectatomic/buildah &&   git checkout  &&   make &&   make install &&   buildah --help:
...
#5 106.1 go build -ldflags '-X main.gitCommit=e9d18fc -X main.buildInfo=1538546985 -X main.cniVersion=v0.7.0-alpha1' -o buildah -tags "    selinux seccomp" ./cmd/buildah
#5 106.4 cmd/buildah/addcopy.go:6:2: cannot find package "github.com/containers/buildah" in any of:
#5 106.4        /root/buildah/src/github.com/projectatomic/buildah/vendor/github.com/containers/buildah (vendor tree)
#5 106.4        /usr/lib/golang/src/github.com/containers/buildah (from $GOROOT)
#5 106.4        /root/buildah/src/github.com/containers/buildah (from $GOPATH)
#5 106.4 cmd/buildah/bud.go:9:2: cannot find package "github.com/containers/buildah/imagebuildah" in any of:
#5 106.4        /root/buildah/src/github.com/projectatomic/buildah/vendor/github.com/containers/buildah/imagebuildah (vendor tree)
#5 106.4        /usr/lib/golang/src/github.com/containers/buildah/imagebuildah (from $GOROOT)
#5 106.4        /root/buildah/src/github.com/containers/buildah/imagebuildah (from $GOPATH)
#5 106.4 cmd/buildah/addcopy.go:7:2: cannot find package "github.com/containers/buildah/pkg/cli" in any of:
#5 106.4        /root/buildah/src/github.com/projectatomic/buildah/vendor/github.com/containers/buildah/pkg/cli (vendor tree)
#5 106.4        /usr/lib/golang/src/github.com/containers/buildah/pkg/cli (from $GOROOT)
#5 106.4        /root/buildah/src/github.com/containers/buildah/pkg/cli (from $GOPATH)
#5 106.4 cmd/buildah/addcopy.go:8:2: cannot find package "github.com/containers/buildah/pkg/parse" in any of:
#5 106.4        /root/buildah/src/github.com/projectatomic/buildah/vendor/github.com/containers/buildah/pkg/parse (vendor tree)
#5 106.4        /usr/lib/golang/src/github.com/containers/buildah/pkg/parse (from $GOROOT)
#5 106.4        /root/buildah/src/github.com/containers/buildah/pkg/parse (from $GOPATH)
#5 106.4 cmd/buildah/unshare.go:14:2: cannot find package "github.com/containers/buildah/unshare" in any of:
#5 106.4        /root/buildah/src/github.com/projectatomic/buildah/vendor/github.com/containers/buildah/unshare (vendor tree)
#5 106.4        /usr/lib/golang/src/github.com/containers/buildah/unshare (from $GOROOT)
#5 106.4        /root/buildah/src/github.com/containers/buildah/unshare (from $GOPATH)
#5 106.4 cmd/buildah/commit.go:11:2: cannot find package "github.com/containers/buildah/util" in any of:
#5 106.4        /root/buildah/src/github.com/projectatomic/buildah/vendor/github.com/containers/buildah/util (vendor tree)
#5 106.4        /usr/lib/golang/src/github.com/containers/buildah/util (from $GOROOT)
#5 106.4        /root/buildah/src/github.com/containers/buildah/util (from $GOPATH)
#5 106.4 make: *** [buildah] Error 1
------
executor failed running [/bin/sh -c yum -y install     make     golang     bats     btrfs-progs-devel     device-mapper-devel     glib2-devel     gpgme-devel     libassuan-devel     libseccomp-devel     ostree-devel     git     bzip2     go-md2man     runc     skopeo-containers &&   mkdir ~/buildah &&   cd ~/buildah &&   export GOPATH=`pwd` &&   git clone https://github.com/opencontainers/runc ./src/github.com/opencontainers/runc &&   cd $GOPATH/src/github.com/opencontainers/runc &&   git checkout "${RUNC_REVISION}" &&   make runc &&   mv runc /usr/bin/runc &&   cd $GOPATH/ &&   git clone https://github.com/projectatomic/buildah ./src/github.com/projectatomic/buildah &&   cd $GOPATH/src/github.com/projectatomic/buildah &&   git checkout "${BUILDAH_REVISION}" &&   make &&   make install &&   buildah --help]: exit code: 2

commit: 6b33c13f0f10e95bc91af95347ee7d398dfcf1de
cc @ImJasonH @vbatts

question: why not just dnf install buildah?
https://github.com/containerbuilding/cbi/blob/master/Dockerfile.buildah
As of writing, dnf installs<EMAIL_ADDRESS>(Sep 19) on rawhide

@AkihiroSuda at the time the latest build for centos was not nearly new enough, and switching the base image to fedora inflated the by more than 500mb. Surely we could look into it again.

/assign


Requires dotnet 5.

Hi, I think this just needs to be added to the prerequisites. Version 3.1 of dotnet dev-certs https doesn't support the --import option as best I can tell.

Correct, I ran into that as well. If someone does not know that, they are puzzled.
Better to mention it.

Stuck on this as well. Maybe is this a workaround for dotnet 3.1?

Stuck on this as well. Maybe is there a workaround for dotnet 3.1?

Install net5, use net31.

 Thank you.

Wow, I just installed a new machine (manjaro) and am having issue with running dotnet dev-certs https.
Got net5 installed.
Could not find the dotnet tool.
Ran dotnet tool install --global dotnet-dev-certs
Now dotnet dev-certs https does not support the --import argument.
What is going on?

I ran into more problems when using the dotnet-install.sh script.
Problems I had were:

MSBuild.Sdk.SqlProj could not find dotnet
Microsoft.Azure.WebJobs.Script.ExtensionsMetadataGenerator.targets(37, 5): Metadata generation failed. Exit code: '134' Error: 'No usable version of the libssl was found'

This was most likely caused because dotnet got installed at ~/.dotnet.
The solution that does work is:
sudo ./dotnet-install.sh -c Current --install-dir /usr/share/dotnet
sudo ./dotnet-install.sh -c LTS --install-dir /usr/share/dotnet
sudo ln -sf /usr/share/dotnet/dotnet /usr/bin/dotnet

Hello,
I'm using Ubuntu and I installed the certificate following the pre requisites. Still when trying to run an asp.net core 5.0 application the browser says it is not secure. In Rider it doesn't even open the browser and stop program. In VS Code it starts listening on https://localhost:5001 but it doesn't open any browser as well. Entering the URL directly on the browser shows the not secure warning.
Am I missing something?
Thanks!

In the browser you can simply trust the certificate by using the rendered warning page.
The other issues are probably caused by incorrect launchsettings.
I would check those.

Thanks, I got it to work :)

Good point. Yes, dotnet dev-certs https --import needs .NET 5. I will update the README and add this to the prerequisites.
While it is technically possible to add the cert to .NET Core 3.1 SDK, I am not a bash specialist and don't know how to check and add this.
If someone is willing to this contact me and we can discuss this.

I guess we can close this. .NET 3.1 and .NET 5 are EOL and out of support.


Source and Header Templates got swapped for the DeveloperSettings files

Typo swapped the Header and Source Files for Developer Settings. Priority fix required!

Fixed. This won't require a recompile if anyone hits this before next release, just edit the DeveloperSettings templates.
Will be in next release.


[DevOps] Could NOT find PythonInterp: Found unsuitable version "1.4", but required is at least "2"

Describe the bug
By using Azure DevOps pipelines for CI, I added the steps like below:
jobs:
- job: Build
  pool:
    vmImage: 'vs2017-win2016'
  timeoutInMinutes: 240
  steps:
  - script: |
      choco sources add -n=roswin -s https://roswin.azurewebsites.net/api/v2/ --priority 1
      choco upgrade ros-melodic-ros_core -y
  - script: |
      call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars64.bat"
      call "C:\opt\ros\melodic\x64\setup.bat"
      pushd "%Build_StagingDirectory%\catkin_ws"
      catkin_make_isolated --only-pkg-with-deps xyz --install

Then, when I kicked off a build, this error shows up:
-- This workspace overlays: C:/opt/ros/melodic/x64
CMake Error at C:/opt/rosdeps/x64/share/cmake-3.11/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find PythonInterp: Found unsuitable version "1.4", but required
  is at least "2" (found C:/ProgramData/chocolatey/bin/python2.exe)

Expected behavior
Kick off a DevOps build without this error.

https://github.com/Kitware/CMake/blob/v3.11.0/Modules/FindPythonInterp.cmake#L90-L108
FindPythonInterp.cmake is using system registry key to search for PYTHON_EXECUTABLE. On machines with multiple pythons installed system-wide, it could eventually pick a wrong one than the one from ROS installation.
Adding -DPYTHON_EXECUTABLE=c:/opt/python27amd64/python.exe can override this behavior to get around this problem. For example,
  - script: |
      call "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Auxiliary\Build\vcvars64.bat"
      call "C:\opt\ros\melodic\x64\setup.bat"
      catkin_make_isolated -DPYTHON_EXECUTABLE=c:/opt/python27amd64/python.exe

Have you solved the mistake? I'm making the same mistake now. I hope I can get your help. thank you!

Hi @846524417 ,
I think you are asking about a different problem. This bug is about using Python in a ROS DevOps environment, which @seanyen offered a correction for.

@ooeygui Yes, but it's the same for me to report an error. I can't find a solution yet. Do you know what caused this mistake?

@ooeygui  My platform is Android studio, can I handle it like this?

@846524417 I'm sorry, we can't help you. This bug is unrelated. Perhaps try stack overflow or the android studio github.


you should use wget prior to curl to support download broken resume

Thanks for helping us to improve k3s! We welcome all feature requests. Please fill out each area of the template so we can better understand the request. You can delete this message portion of the bug report.
Is your feature request related to a problem? Please describe.
wget auto support broken resume but curl don't
Describe the solution you'd like
just change:
verify_downloader curl || verify_downloader wget || fatal 'Can not find curl or wg
et for downloading files'

to:
verify_downloader wget || verify_downloader curl || fatal 'Can not find curl or wg
et for downloading files'

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
no

We're not really calling the downloader in a way that would support resume anyway, so I don't think it makes a big difference. Are you experiencing connectivity issues such that you can't download a ~60MB file in a single go?

Hi @brandond,
Yes, I did experience the connectivity issue, maybe just temporary issue, but it affect the real experience...


wrap lines of the generated license

inject line breaks in long lines

https://github.com/jslicense/licensor.js


MAINT/STY: constants: remove E501 (line length) lint ignore

Reference issue
Towards gh-19479.
What does this implement/fix?
Follow-up to gh-19489 for constants. _codata.py remains ignored, while the rest of the module is dealt with.
Additional information
I can add in a git blame ignore if wanted once this is ready.
Feel free to wait for gh-19497 if you don't want to test locally.

Updated for conflicts. I don't think we need a blame-ignore here.


Log to stdout instead of log/debug.log when running in container

The chia/mainnet/config/config.yaml file generated by chia init has log_stdout: false and log_filename: log/debug.log.
In an ideal world, containers should log only to STDOUT, not to files inside the container.
One can manually change the config.yaml (IFF it's maintained outside the container, as proposed in #36), but in an ideal world, perhaps this container should set it up to log only the STDOUT out of the box?

I added a line to tail the log file for now in #77


Add ADU capabilities to feature branch

@danieljurek can you help with the cla check.  Unsure why this is blocked since the license/cla passed as part of the checks


feat: restructuring of connector Kit documentation

Added

documentation of the control-plane-adapter extension
openAPI documentation of the control-plane-adapter extension
documentation of the observability-api-customization
migration documentation
postman collection

Changed

helm chart version for the edc components is now 0.3.3
switched the whole documentation structure from product-edc to tractusx-edc
switched build tool from maven to gradle
restructured the whole documentation structure and order

@danielmiehle , @maximilianong Since this a huge PR (Restructuring the files) It's really hard to do the review here. That's why I provided a temporary generated page on my fork. Here you can find the representation of the current changes
Connector Kit
Currently, I am not sure about the current version and date here -> is this correct?
Thx


💬 [Question] Design "Table not found" Page

💬 Question

Design "Table not found Page"

See: https://stage1.app.dreammall.earth/table/1234

Closing in favor of https://github.com/dreammall-earth/dreammall.earth/issues/2533


Unknown encoder 'h264_omx'

Hello,
I have updated to the latest version 1.1.0 and get an error when using the h264_omx encoder:
..
Opening an output file: srtp://<IP_ADDRESS>:49388?rtcpport=49388&localrtcpport=49388&pkt_size=1316.
Unknown encoder 'h264_omx'
...

My configuration is as followed:
{
            "cameras": [
                {
                    "name": "Keno",
                    "videoConfig": {
                        "source": "-rtsp_transport tcp -re -i rtsp://<IP_ADDRESS>:554/onvif1",
                        "maxFPS": 5,
                        "vcodec": "h264",
                        "audio": false,
                        "debug": false
                    }
                }
            ],
            "platform": "Camera-ffmpeg"
        }

I used home bridge on a Debian 10 system in Proxmox
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Look over v1.0.0.

@Hasenpups Please double check your config.   Your config sample says  "vcodec": "h264", but your error message says Unknown encoder 'h264_omx'
Please try with debug mode enabled

I also have the same issue with this config :
"platform": "Camera-ffmpeg",             "cameras": [                 {                     "name": "XXX",                     "manufacturer": "XX",                     "model": "XXXX",                     "serialNumber": "XXXXX",                     "videoConfig": {                         "source": "-rtsp_transport tcp -i rtsp://XXX",                         "stillImageSource": "-i http://XXXX",                         "maxStreams": 2,                         "maxBitrate": 300,                         "packetSize": 188,                         "audio": false,                         "debug": true,                         "vcodec": "h264_omx"                     }                 }              }
Here is the debug logs :
Applying option vcodec (force video codec ('copy' to copy stream)) with argument h264_omx.
Applying option pix_fmt (set pixel format) with argument yuv420p.
Applying option r (set frame rate (Hz value, fraction or abbreviation)) with argument 24.
Applying option f (force format) with argument rawvideo.
Applying option vf (set video filters) with argument scale=1280:720.
Applying option b:v (video bitrate (please use -b:v)) with argument 299k.
Applying option f (force format) with argument rtp.
Successfully parsed a group of options.
Opening an output file: srtp://<IP_ADDRESS>:59614?rtcpport=59614&localrtcpport=59614&pkt_size=188.

Unknown encoder 'h264_omx'

Can you share the portion of the debug log that contains the ffmpeg details.
With version 1.1.0 we are bundling ffmpeg with this option compiled in, so it should work.
Also what are you running homebridge on?

Here is the full logs when i start the video streamaing :
[5/14/2020, 2:07:44 PM] [Camera-ffmpeg] Start streaming video from Axis - Cuisine with 1280:720@24fps (299kBit)
ffmpeg -rtsp_transport tcp -i rtsp://XXXXXXX/Sms=2.unicast -map 0:0 -vcodec h264_omx -pix_fmt yuv420p -r 24 -f rawvideo -tune zerolatency -vf scale=1280:720 -b:v 299k -bufsize 299k -maxrate 299k -payload_type 99 -ssrc 82683 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params lC30Hj+xO0YBijZNzkEMSeLMxaZpQhGM5arQQBy0 srtp://XXXXX?rtcpport=61884&localrtcpport=61884&pkt_size=188 -loglevel debug
ffmpeg version 4.2.git-47773f7 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.2.0 (Alpine 9.2.0)

  configuration: --pkgconfigdir=/build/workspace/lib/pkgconfig --prefix=/build/workspace --pkg-config-flags=--static --extra-cflags=-I/build/workspace/include --extra-ldflags=-L/build/workspace/lib --extra-libs='-lpthread -lm' --enable-static --disable-debug --disable-shared --disable-ffplay --disable-doc --enable-openssl --enable-gpl --enable-version3 --enable-nonfree --enable-pthreads --enable-libvpx --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libx264 --enable-runtime-cpudetect --enable-libfdk-aac --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --enable-decoder=h264 --enable-network --enable-protocol=tcp --enable-demuxer=rtsp
  libavutil      56. 40.100 / 56. 40.100

  libavcodec     58. 68.102 / 58. 68.102
  libavformat    58. 38.100 / 58. 38.100
  libavdevice    58.  9.103 / 58.  9.103
  libavfilter     7. 75.100 /  7. 75.100
  libswscale      5.  6.100 /  5.  6.100
  libswresample   3.  6.100 /  3.  6.100
  libpostproc    55.  6.100 / 55.  6.100

Splitting the commandline.
Reading option '-rtsp_transport' ...
 matched as AVOption 'rtsp_transport' with argument 'tcp'.
Reading option '-i' ... matched as input url with argument 'rtsp://XXXXX/Sms=2.unicast'.

Reading option '-map' ... matched as option 'map' (set input stream mapping) with argument '0:0'.
Reading option '-vcodec' ... matched as option 'vcodec' (force video codec ('copy' to copy stream)) with argument 'h264_omx'.
Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel format) with argument 'yuv420p'.
Reading option '-r' ... matched as option 'r' (set frame rate (Hz value, fraction or abbreviation)) with argument '24'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'rawvideo'.

Reading option '-tune' ...
 matched as AVOption 'tune' with argument 'zerolatency'.
Reading option '-vf' ...
 matched as option 'vf' (set video filters) with argument 'scale=1280:720'.
Reading option '-b:v' ... matched as option 'b' (video bitrate (please use -b:v)) with argument '299k'.
Reading option '-bufsize' ...
 matched as AVOption 'bufsize' with argument '299k'.
Reading option '-maxrate' ...
 matched as AVOption 'maxrate' with argument '299k'.
Reading option '-payload_type' ...
 matched as AVOption 'payload_type' with argument '99'.
Reading option '-ssrc' ...
 matched as AVOption 'ssrc' with argument '82683'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'rtp'.

Reading option '-srtp_out_suite' ...
 matched as AVOption 'srtp_out_suite' with argument 'AES_CM_128_HMAC_SHA1_80'.
Reading option '-srtp_out_params' ...
 matched as AVOption 'srtp_out_params' with argument 'lC30Hj+xO0YBijZNzkEMSeLMxaZpQhGM5arQQBy0'.
Reading option 'srtp://XXXXX?rtcpport=61884&localrtcpport=61884&pkt_size=188' ... matched as output url.

Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Successfully parsed a group of options.
Parsing a group of options: input url rtsp://XXXXX/Sms=2.unicast.
Successfully parsed a group of options.
Opening an input file: rtsp://XXXXX/Sms=2.unicast.

[tcp @ 0x2866dc0] No default whitelist set
[tcp @ 0x2866dc0] Original list of addresses:
[tcp @ 0x2866dc0] Address XXXXX port 554
[tcp @ 0x2866dc0] Interleaved list of addresses:
[tcp @ 0x2866dc0] Address XXXXX port 554
[tcp @ 0x2866dc0] Starting connection attempt to XXXXX port 554

[tcp @ 0x2866dc0] Successfully connected to XXXXX port 554

[rtsp @ 0x76f95010] SDP:
v=0
o=-<PHONE_NUMBER>834119 1 IN IP4 XXXXX
s=Session streamed by "ssrtspd"
i=1,2_high.unicast
t=0 0
a=tool:LIVE555 Streaming Media v2015.05.03
a=type:broadcast
a=control:*
a=range:npt=0-
a=x-qt-text-nam:Session streamed by "ssrtspd"
a=x-qt-text-inf:1,2_high.unicast
m=video 0 RTP/AVP 96
c=IN IP4 <IP_ADDRESS>
b=AS:500
a=rtpmap:96 H264/90000
a=fmtp:96 packetization-mode=1;profile-level-id=640032;sprop-parameter-sets=Z2QAMqwbGoAqAL//AW4CAgKAAAH0AABhqHQwABbjYAABAX313lxoYAAtxsAAAgL767y4b6g=,aO44MA==
a=control:track1

Failed to parse interval end specification ''
[rtsp @ 0x76f95010] video codec set to: h264
[rtsp @ 0x76f95010] RTP Packetization Mode: 1
[rtsp @ 0x76f95010] RTP Profile IDC: 64 Profile IOP: 0 Level: 32
[rtsp @ 0x76f95010] Extradata set to 0x3923d70 (size: 65)

[rtsp @ 0x76f95010] setting jitter buffer size to 0

[rtsp @ 0x76f95010] hello state=0

Failed to parse interval end specification ''

[h264 @ 0x76f98200] nal_unit_type: 7(SPS), nal_ref_idc: 3
[h264 @ 0x76f98200] nal_unit_type: 8(PPS), nal_ref_idc: 3

[h264 @ 0x76f98200] nal_unit_type: 7(SPS), nal_ref_idc: 3

[h264 @ 0x76f98200] nal_unit_type: 8(PPS), nal_ref_idc: 3

[h264 @ 0x76f98200] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3

[h264 @ 0x76f98200] Format yuvj420p chosen by get_format().
[h264 @ 0x76f98200] Reinit context to 2688x1520, pix_fmt: yuvj420p

[h264 @ 0x76f98200] Frame num gap 187 185

[h264 @ 0x76f98200] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3

    Last message repeated 74 times
[h264 @ 0x76f98200] nal_unit_type: 7(SPS), nal_ref_idc: 3
[h264 @ 0x76f98200] nal_unit_type: 8(PPS), nal_ref_idc: 3
[h264 @ 0x76f98200] nal_unit_type: 6(SEI), nal_ref_idc: 0

[h264 @ 0x76f98200] nal_unit_type: 5(IDR), nal_ref_idc: 3

[h264 @ 0x76f98200] nal_unit_type: 1(Coded slice of a non-IDR picture), nal_ref_idc: 3

    Last message repeated 5 times
[rtsp @ 0x76f95010] All info found

Input #0, rtsp, from 'rtsp://XXXXX/Sms=2.unicast':
  Metadata:
    title           : Session streamed by "ssrtspd"
    comment         : 1,2_high.unicast
  Duration: N/A
, start: 4.079000, bitrate: N/A
    Stream #0:0, 104, 1/90000: Video: h264 (High), 1 reference frame, yuvj420p(pc, bt709, progressive, left), 2688x1520 [SAR 1:1 DAR 168:95], 0/1, 25 fps, 25 tbr, 90k tbn, 50 tbc
Successfully opened the file.
Parsing a group of options: output url srtp://XXXXX?rtcpport=61884&localrtcpport=61884&pkt_size=188.
Applying option map (set input stream mapping) with argument 0:0.
Applying option vcodec (force video codec ('copy' to copy stream)) with argument h264_omx.
Applying option pix_fmt (set pixel format) with argument yuv420p.
Applying option r (set frame rate (Hz value, fraction or abbreviation)) with argument 24.
Applying option f (force format) with argument rawvideo.
Applying option vf (set video filters) with argument scale=1280:720.
Applying option b:v (video bitrate (please use -b:v)) with argument 299k.
Applying option f (force format) with argument rtp.
Successfully parsed a group of options.
Opening an output file: srtp://XXXXX?rtcpport=61884&localrtcpport=61884&pkt_size=188.

Unknown encoder 'h264_omx'

[5/14/2020, 2:07:49 PM] [Camera-ffmpeg] ERROR: FFmpeg exited with code 1

For the question about "what are you running homebridge on?" you mean what are the others plugins that are running on my homebrige ?

Ie a raspberryPI ?
The omx codec is only available on a raspberrypi

ok, i'm running on Raspberry Pi 3 B+

@Gunth Not sure what version of FFMPEG you are running, as the version of ffmpeg bundled with Homebridge-camera-ffmpeg version 1.1.0 has this version
ffmpeg version 4.2.git-47773f7 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1+deb9u1) 20170516
  configuration: --pkgconfigdir=/build/workspace/lib/pkgconfig --prefix=/build/workspace --pkg-config-flags=--static --extra-cflags=-I/build/workspace/include --extra-ldflags=-L/build/workspace/lib --extra-libs='-lpthread -lm' --enable-static --disable-debug --disable-shared --disable-ffplay --disable-doc --enable-openssl --enable-gpl --enable-version3 --enable-nonfree --enable-pthreads --enable-libvpx --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libx264 --enable-runtime-cpudetect --enable-libfdk-aac --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --enable-decoder=h264 --enable-network --enable-protocol=tcp --enable-demuxer=rtsp --enable-omx-rpi --enable-mmal

What's important is this compile flag enable-omx-rpi which enables the OMX codec

This is strange because i use the version 1.1.0

Does i need to add an extra parameter somewhere, like on the Homebridge docker ? Or is there some caching somewhere ?

I’m kinda stumped as to the cause of why this is occurring.
I created a pull request to troubleshoot further into this issue
https://github.com/homebridge-plugins/homebridge-camera-ffmpeg/pull/497/files https://github.com/homebridge-plugins/homebridge-camera-ffmpeg/pull/497/files
Are able to manually tweak the file to trouble shoot?  The change will show which ffmpeg the plugin is using.

On May 14, 2020, at 11:17 AM, Gunth<EMAIL_ADDRESS>wrote:
This is strange because i use the version 1.1.0
https://user-images.githubusercontent.com/1955976/81952115-59df5480-9606-11ea-817d-e4d3b94ba694.png
Does i need to add an extra parameter somewhere, like on the Homebridge docker ? Or is there some caching somewhere ?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/homebridge-plugins/homebridge-camera-ffmpeg/issues/492#issuecomment-628703027, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEXEFGBAQZJ6KFJQMZNN3ETRRQDPHANCNFSM4M72DXYQ.

This is from my machine, note the path for ffmpeg is from a sub-directory of Homebridge-camera-ffmpeg
/home/northernMan/npm/lib/node_modules/homebridge-camera-ffmpeg/node_modules/ffmpeg-for-homebridge/ffmpeg -max_delay 1000000 -i<EMAIL_ADDRESS>-map 0:0 -vcodec h264_omx -pix_fmt yuv420p -r 15 -f rawvideo -tune zerolatency -vf scale=1280:720 -b:v 299k -bufsize 299k -maxrate 299k -payload_type 99 -ssrc 2105935 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params IkYAxWpmM5vQ6QJ/uYpTLRd0P2fwkkqjDjERR4Ye srtp://<IP_ADDRESS>:51532?rtcpport=51532&localrtcpport=51532&pkt_size=1316 -map 0:1 -acodec libfdk_aac -profile:a aac_eld -flags +global_header -f null -ar 16k -b:a 24k -bufsize 24k -ac 1 -payload_type 110 -ssrc 13236752 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params XLWisXIiADJapS3bpjch1Ex5W1YDp/aOh5l0ENpM srtp://<IP_ADDRESS>:55072?rtcpport=55072&localrtcpport=55072&pkt_size=1316 -loglevel debug

This what has been returned :
/homebridge/node_modules/homebridge-camera-ffmpeg/node_modules/ffmpeg-for-homebridge/ffmpeg -rtsp_transport tcp -i rtsp://syno:d339e2aa097d733fd9a52e693e2778a1@xxxx:554/Sms=2.unicast -map 0:0 -vcodec h264_omx -pix_fmt yuv420p -r 24 -f rawvideo -tune zerolatency -vf scale=1280:720 -b:v 299k -bufsize 299k -maxrate 299k -payload_type 99 -ssrc 6326882 -f rtp -srtp_out_suite AES_CM_128_HMAC_SHA1_80 -srtp_out_params ryOOlQ0TuplVAYTMKCfpVZ0oI4ZuL9SYwo9Xp6Pi srtp://<IP_ADDRESS>:51349?rtcpport=51349&localrtcpport=51349&pkt_size=188 -loglevel debug
ffmpeg version 4.2.git-47773f7 Copyright (c) 2000-2020 the FFmpeg developers
  built with gcc 9.2.0 (Alpine 9.2.0)

I see the issue
https://github.com/homebridge/ffmpeg-for-homebridge#readme
omx is only enabled when you are not running in a container on raspberry pi


Add 4x4 functionality

Need to determine what columns to display (raw stats? category $ values?)

Draft functionality was closed in v1.1.0. Creation of values remains open.