Filtering from Rails.configuration.filter_parameters does not work in URLs

In a Rails application, given the following configuration for filtering params:
Rails.configuration.filter_parameters
=> [:password, :access_token, :refresh_token]

Bugsnag does not properly filter URLs that get sent across in the Request tab. In particular, given that configuration, the Bugsnag railtie changes the Rails filters to strings that start with \A and end with \z, so we end up with:
Bugsnag.configuration.params_filters
=> #<Set: {"password",
 /\Aaccess_token\z/,
 /\Arefresh_token\z/}>

As a result, Bugsnag.cleanup_url does not match a URL that needs to be filtered properly:
Bugsnag::Helpers.cleanup_url("https://host.example/sessions?access_token=abc123", Bugsnag.configuration.params_filters)
=> "https://host.example/sessions?access_token=abc123"

If Rails parameters are picked up unchanged (simulated by the direct assignment in the first line), Bugsnag.cleanup_url works as expected:
Bugsnag.configuration.params_filters = ["password", "access_token", "refresh_token"]
Bugsnag::Helpers.cleanup_url("https://host.example/sessions?access_token=abc123", Bugsnag.configuration.params_filters)
=> "https://host.example/sessions?access_token=[FILTERED]"

I don’t know the motivation for modifying Rails.configuration.filter_parameters when including them in Bugsnag.configuration.params_filters, but I propose passing those values unmodified so filtering works properly everywhere.

We modify the Rails filters to do exact matching on the keys in the metadata, but unfortunately this seems to somewhat break cleanup_url. We should leave the filters as they are and simply deal with the \A and \z appropriately in there (possibly extracting out each parameter and testing it, rather than doing it as one huge string).
I'll try and get around to getting a fix out for this soon! Thanks for reporting!


function  formatOCObj: Death cycle

function  formatOCObj ：
when  obj is Kind of NSDictionary，there will be a Death cycle.
because obj has a key “__c”.

Could you give me more details? Is there test case?

I jush make a little change in the demo.js

Fixed, thank you!


Rendering HTML content as Response adonisjs

How can i bind html i.e
under P tag

This is some text

from database showing exactly in our view. Angularjs provide $sce.trustAsHtml method, Is there any helper method for this ..?

You should use the forums / discord for questions.
But...

If you don't want to escape the html data then output it with {{{ ... }}} instead of {{ ... }}
https://edge.adonisjs.com/docs/syntax-guide#_interpolation
Can never be sure if its just semantics or actual confusion. So.. Adonis is a server side framework as such there is no binding in the views, there is no reactive data, just data passed once to a view.

Thanks @tlgreg


Add code of conduct meeting notes

cc @zachlatta

@jonleung your tests fail :D

@paked, the spelling errors that seem to make this test fail seem to be in all these other documents that have nothing to do with this pull request. I'm assuming that this is the first pull request into this repo since spellcheck was added to Markcop? Is there a way to tell Markcop to ignore those other files for now since it is not in this pull request?
Right now I don't think I have the bandwidth to fix all the spelling and grammar errors in this repository.  If you rebase master into this pull request,
all the tests should pass.
On Thu, Jan 7, 2016 at 12:15 PM, Jonathan Leung<EMAIL_ADDRESS>wrote:

@paked https://github.com/paked, the spelling errors that seem to make
this test fail seem to be in all these other documents that have nothing to
do with this pull request. I'm assuming that this is the first pull request
into this repo since spellcheck was added to Markcop? Is there a way to
tell Markcop to ignore those other files for now since it is not in this
pull request?
Right now I don't think I have the bandwidth to fix all the spelling and
grammar errors in this repository. Are there any other suggestions for what
else I can do?
\cc @MaxWofford https://github.com/MaxWofford @zachlatta
https://github.com/zachlatta
—
Reply to this email directly or view it on GitHub
https://github.com/hackclub/meta/pull/454#issuecomment-169793192.

--
Zach Latta
http://zachlatta.com
https://github.com/zachlatta
https://twitter.com/zachlatta

<3

I noticed the code of conduct was added to the CONTRIBUTING.md. Was this on purpose? This file mentions it should be added to the SLACK.md, but not CONTRIBUTING.md

I think it was intentional and that the code of conduct should also be
added to SLACK.md.
On Sat, Jan 9, 2016 at 6:28 PM, Max Wofford<EMAIL_ADDRESS>wrote:

I noticed the code of conduct was added to the CONTRIBUTING.md. Was this
on purpose? This file mentions it should be added to the SLACK.md, but not
CONTRIBUTING.md
—
Reply to this email directly or view it on GitHub
https://github.com/hackclub/meta/pull/454#issuecomment-170301383.

--
Zach Latta
http://zachlatta.com
https://github.com/zachlatta
https://twitter.com/zachlatta


Test for fetching data using SFTP, DICT, GOPHER, LDAP, TFTP protocols via SSRF

I am submitting a pull request for the SSRF Protocol Vulnerability Check test related to https://github.com/akto-api-security/akto/issues/137
This test is designed to identify vulnerabilities in APIs that accept URLs as parameters, specifically targeting protocols like SFTP, DICT, GOPHER, LDAP, and TFTP for potential SSRF.
Changes Made:
Added a new SSRF test targeting various protocols (SFTP, DICT, GOPHER, LDAP, TFTP).
Included specific modifications to the query parameter for each protocol.
Validated responses for expected content related to each protocol.

LGTM


Allow to show protected screen rather than black screen

Is your feature request related to a problem? Please describe.
Some (protected) screens are not shown in scrcpy by default
Describe the solution you'd like
Can there be an option to just show the contents of a protected screen via scrcpy ?

Not possible without root since Android 12: #36 #2129

But I am rooted and there appears to be a scrcpy-root which just adds the --root option which obviously can only be used on rooted devices.
Can this option be built in into the general scrcpy ?


Support for-loop iteration over 1-dim memory views

Currently, efficient iteration over a memory views axis requires indexing. Iterating with a for-in-loop should result in the same code.
Convert the loop in IterationTransform._optimise_for_loop() in Optimize.py, similar to the range optimisation.
Additional idea: for multi-dimensional views, the iteration could yield borrowed slices, with their lifetime bound to the current loop iteration. That would avoid the refcounting overhead for them, which can hurt for very small slices (as found in #2987). Iteration seems to provide a natural frame for this.

Just to make sure I get it right:
We're trying to convert
for e in the_view:
	# do whatever on e

into
for (i = 0; i < length_of_the_view; i++) {
	// do whatever on some_view[i]
}

And in the case that e is actually another view, we convert it into a "borrowed slice" (I don't know what that means yet but I'll look into it)
Is this correct?

Yes. If the_view is a memoryview (which is the case that I'd like to support here), then you wouldn't have to type e, it would just be a view on the same buffer with one dimension less (or a simple item value for 1D views).
With "borrowed slice" I mean a slice that is not refcounted and thus relies on the main view to keep the buffer alive. But that seems safe in this specific case, since we're holding tight to it while we're iterating over it.
An unclear issue is: What happens on re-assignments to the loop variable? Can/should we allow that at all? Should we switch back to ref-counting if we detect that? (That seems the best way out for this.)
I think the semantics would be like this:
for item in a_view:
    …
else:
    …

would translate into
try:
    item = borrowed(None)
    for i in range(len(a_view)):
         item = borrowed(a_view[i])
        …
    else:
        …
finally:
    del item  # or incref(item), maybe?

And then, there could be a way to get prange() loops by saying
for item in cython.parallel.piter(a_view):
    …

as noted in #2628.

I've had an go at the easy bit of this (optimized iteration over memoryviews), not the "borrowed reference" side of it, which I think it quite a bit more involved. To work well it requires some changes to type inference of memoryviews, which could probably do with some more thought.
I think the borrowed reference side potentially a mess - you have to worry about reassignment (as you observe) but it's also inconsistent with the rest of Python if you can't access the loop target after the loop has finished.

Closing through #3617. Created #3715 as a follow-up regarding borrowed slices.


Prepare release 2.12.0

Signed-off-by: Yuri Shkuro<EMAIL_ADDRESS>

@black-adder am I correct that there's no risk from the throttler change? It looks like the throttler is never used.


azd up failing to open AI resource

We have followed the tutorial and updated GPT4 version in the code
Failing to create resources for Open AI
Open AI snapshot updated in bicep file.
name: gptDeploymentName
model: {
format: 'OpenAI'
name: gptModelName
version: '0613'
}
sku: {
name: 'Standard'
capacity: gptDeploymentCapacity
}
}
{
name: chatGptDeploymentName
model: {
format: 'OpenAI'
name: chatGptModelName
version: '0613'
}
Getting following error.
Deployment Error Details:
InvalidTemplateDeployment: The template deployment 'openai' is not valid according to the validation procedure. The tracking id is 'b5c0f524-df7e-4986-8975-acc87ca17afd'. See inner errors for details.
DeploymentModelNotSupported: The model 'Format: OpenAI, Name: gpt-4, Version: 2, Source: ' of account deployment is not supported.

Can you share the full infra/main.bicep? I'm guessing there's a mismatch between versions/model names. Unfortunately I don't have access to gpt-4 yet so have been unable to try it myself.

There's now an FAQ about enabling GPT-4, and I tested that it works, so I'll close this issue.


Initializer does not respect Nx default backend

Hi,
I've tried using Torchx with mps backend on an M1 machine but I get the following error.
** (ArgumentError) cannot perform operation across devices mps and cpu
    (torchx 0.5.3) lib/torchx.ex:467: anonymous fn/2 in Torchx.prepare_tensors_list!/2
    (elixir 1.14.4) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2
    (elixir 1.14.4) lib/enum.ex:1658: Enum."-map/2-lists^map/1-0-"/2
    (torchx 0.5.3) lib/torchx.ex:462: Torchx.prepare_tensors_list!/2
    (elixir 1.14.4) lib/enum.ex:1780: Enum."-map_reduce/3-lists^mapfoldl/2-0-"/3
    (torchx 0.5.3) lib/torchx.ex:244: Torchx.concatenate/2
    (torchx 0.5.3) lib/torchx/backend.ex:421: Torchx.Backend.concatenate/3
    (nx 0.5.3) lib/nx/defn/evaluator.ex:418: Nx.Defn.Evaluator.eval_apply/4

After some digging I found out that during initialization (probably bias initializer) there is a value being produced with BinaryBackend and Torchx will automatically backend copy to Torchex.Backend but it does not respect the default backend configuration and will copy to cpu instead of mps.
To reproduce you can run the following script
Mix.install(
  [
    {:torchx, "~> 0.5.3"},
    {:axon, "~> 0.5.1"}
  ],
  config: [nx: [default_backend: {Torchx.Backend, device: :mps}]]
)

model =
  Axon.input("input")
  |> Axon.dense(1)

{init_fn, _predict_fn} = Axon.build(model, debug: true)

init_fn.(Nx.template({1, 1}, :f32), %{})
|> IO.inspect()

I believe this is an issue in Torchx itself and not in Axon. The Axon initializers are in the end all implemented through Defn, so if the backend options aren't being fetched and passed on properly, chances are this is related to Torchx.
An easy way to test this is to use EXLA in a machine with cuda support and set the default backend to {EXLA.Backend, client: :cuda}.

Thanks @polvalente
I have investigated this issue a bit more and it seems like in the initiation process a tensor is being created using Nx.BinaryBacked and then this tensor get's passed to from_nx function in Torchx.Backend. Now based on torchx/backend.ex#L1808, Torchx will call Nx.backend_transfer but it does not know about the default options anymore and will create cpu tensor instead of mps or any other device that the user has specified.
I can see two possible solutions:

Investigate why the initializer is making a tensor in Nx.BinaryBackend and force it to use Nx.default_backend instead.
Create a new configuration parameter for Torchx which stores the default options for when the from_nx function wants to call backend_transfer(tensor, {Torchx.Backend, default_options}) in torchx/backend.ex#L1808

I just ran into the same issue - did you ever try out either of your two proposed solutions?

Hi @benswift
I actually changed a line in Torchex Backend to forcefully create tensors with the mps device for my test and it worked as expected.
But I don't yet understand why tensors are created in BinaryBackend in the first place...

Ah, ok, thanks for the update :)

Yes, this is a torchx issue, so closing for now!


Response body discarded with middleware

Using the below configuration
func StartAndServe() {

	logger := slog.Default()
	port := os.Getenv("PORT")

	slog.Info("Starting server on port", "port", port)
	app := fiber.New()

	group := app.Group("/api")
	group.Use(slogfiber.New(logger))

	group.Get("/lookup/:ipaddress", getGeoInfo)

	err := app.Listen(":" + port)
	if err != nil {
		slog.Error("Error starting server", "error", err)
	}
}

The call to getGeoInfo mapped above returns a simple 3 value JSON object
{
	"city": "Johannesburg",
	"region": "Gauteng",
	"country": "South Africa"
}

from the return call below.
	return c.Status(fiber.StatusOK).JSON(lresp)

With group.Use(slogfiber.New(logger)) included the JSON is truncated from the response and nothing but OK is returned.
Below is the information logged by slogfiber.
2023-09-14T20:13:00.410576+02:00 INF Incoming request time="2023-09-14 20:13:00.410563 +0200 SAST" latency=94.375µs method=GET host=localhost:3000 path=/api/lookup/<IP_ADDRESS> route=/api/lookup/:ipaddress status=200 ip=<IP_ADDRESS> user-agent=insomnia/2023.5.8 referer="" request-id=717e4157-3f6e-4d86-a51c-92e1c7015786

I have forked the repository and implemented the change from pull request #5. This fixes the issue.


[1232] Create courses from TTAPI

Context
https://trello.com/c/nPORPb0g/1232-m-retrieve-courses-from-ttapi
Changes proposed in this pull request
This PR:

Adds a scheduled job TeacherTrainingApi::CreateCoursesJob which is currently set to run every day 2am.

Unless the feature flag is on, this does nothing.
If the feature flag is on, the job fans out to one job per provider (currently all providers):

Adds a job TeacherTrainingApi::CreateProviderCoursesJob which takes a provider, and retrieves all of their courses from TTAPI via new service TeacherTrainingApi::RetrieveCourses
It then iterates over these returned course objects and find-or-creates a course for the provider via new service TeacherTrainingApi::CreateCourse.
Adds this new model Course, which currently only has a name and a provider_id

Guidance to review

You can test each of the services manually by running them from the command line. You'll need to ensure that your providers have their actual codes attached.

 [M] Retrieve Courses from TTAPI

@defong @gpeng @darokel thanks for the review - all updates from feedback here a8a665b5c0735a2271a7b604143dcc36ebf64917

Ummm I can kinda see that if api ain't playing nicely we going to flood ourselves with lots of errors

Is there anything we can do to mitigate this? I decided to fan out individual jobs to isolate errors per provider, but maybe there's other things we could do?
Or we just give it a go!


[commerce-sdk-react]  Update and invalidate cached queries on mutations

Description

Types of Changes

[ ] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Documentation update
[ ] Breaking change (could cause existing functionality to not work as expected)
[ ] Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

Removing a public function or component or prop
Adding a required argument to a function
Changing the data type of a function parameter or return value
Adding a new peer dependency to package.json

Changes

(change1)

How to Test-Drive This PR

(step1)

Checklists

General

[ ] Changes are covered by test cases
[ ] CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance
You must check off all items in one of the follow two lists:

[ ] There are no changes to UI

or...

[ ] Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
[ ] Changes comply with WCAG 2.0 guidelines levels A and AA
[ ] Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

[ ] Changes include a UI text update in the Retail React App (which requires translation)

@adamraya Brian and I were thinking this morning: what do we really want to test? We feel that because our useShopperCustomersMutation hook is simply passing passing things along to the commerce-sdk-isomorphic library, we don't really need to test every action thoroughly. We can safely assume that the actions/methods in the isomorphic library will function as expected.
On our end, one of the tests we can do is to make sure that our list of actions is accurate, meaning that each action exists as a method in the isomorphic library. Such test may look something like this:
Object.values(ShopperCustomersMutations).forEach((action) =>
    expect(apiClients.shopperCustomer[action]).toBeDefined()
)


Address review comments on prior patch

I pulled the trigger to land the previous patch too quickly and missed a
number of comments.

TBR @Hixie

Lgtm


boards: snps: nsim: Fix board usage for filenames

Fixes an issue where the board name variable has changed in hwmv2

Fixes #69752

Thanks, this fixes most problems with the support files.
I noticed two more problems that could be solved by renaming files:
mdb_hs3x_hostlink.args -> mdb_hs_hostlink.args
nsim_hs3x_hostlink.props -> nsim_hs_hostlink.props
nsim_sem_mpu_stack_guards.args -> mdb_sem_mpu_stack_guards.args
Can you add these changes, or should we fix it in a different PR?

Thanks, this fixes most problems with the support files. I noticed two more problems that could be solved by renaming files: mdb_hs3x_hostlink.args -> mdb_hs_hostlink.args nsim_hs3x_hostlink.props -> nsim_hs_hostlink.props nsim_sem_mpu_stack_guards.args -> mdb_sem_mpu_stack_guards.args
Can you add these changes, or should we fix it in a different PR?

Have applied here in a new commit


register(): make underscore legal in column name

Summary
fix for [client-v2] Underscore in column name is removed
Checklist
Delete items not relevant to your PR:

[ ] Unit and integration tests covering the common scenarios were added
[ ] A human-readable description of the changes was provided to include in CHANGELOG
[ ] For significant changes, documentation in https://github.com/ClickHouse/clickhouse-docs was updated with further explanations or tutorials

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

I'm canceling this PR because it solves only part of the problem. Out team will work on the fix and will create a new PR for this issue.


04_deeppavlov_chitchat.ipynb -  3 Questions

Hi! Loving de DeepPavlov idea!
In the Chitchat example as suggested, Im tring to run 3 things:

Use "teacher_forcing_rate":  It seams that anything other that 0 Activates this. But I see no effect on the loss. It goes just as slow as with 0. I did notice the teacher_forcing_rate = tf.random_uniform(shape=()) and wonder if that is a smarter way to set the value for teacer_forcing_rate, that could be use in the config.

Use "use_attention": True : But it activates a lot of things (kinda hard to follow, sorry...)
that end up in: InvalidArgumentError (see above for traceback): Restoring from checkpoint failed. This is most likely due to a mismatch between the current graph and the graph from the checkpoint. Please ensure that you have not altered the graph expected based on the checkpoint. Original error:
Assign requires shapes of both tensors to match. lhs shape= [550,500] rhs shape= [300,500]
And the suggestions i get for this error is to rewrite some things in Tensorflow... which I would not try and do... Is there a way to fix the example in the Tutorials?

At the end of the Tutorial you also suggest:
To improve the model you can try to use multilayer (use MultiRNNCell) encoder and decoder, try to use attention with trainable parameters (not dot product scoring function).
I wonder how to do this?
in the encoder def i find
encoder_cell = tf.nn.rnn_cell.GRUCell(
num_units=cell_size,
kernel_initializer=tf.contrib.layers.xavier_initializer(),
name='encoder_cell')
But I dont know if that is the correct place, or how to use MultiRNNCell in the Docs at deeppavlov.

I would love to get some help in this tutorial! Thanks!

Hi!
This tutorial is a bit outdated, we are going to fix our tutorials section.
I would suggest to check TensorFlow 2.0 Text and Sequences tutorials with more recent TF api: https://www.tensorflow.org/alpha/tutorials/sequences/text_generation


Add new target for internal browser modules

Motivation
At the moment, wasm-bindgen provides the --target web option to generate wasm bindings that will run in a browser tab. However, the javascript bindings generated with this target throw errors when used in internal browser code (for example, the javascript in the browser modules or browser components).
A new target that adheres to the stricter javascript validation required for the javascript used in browser development would allow developers to write browser code in rust and then call this code from within existing browser modules.
I'm requesting this because I'm currently working on a feature for Tor Browser that calls rust code to perform cryptographic operations needed to pre-populate the browser preferences with anti-censorship proxies. See the open issue on our Trial Lox Integration for more details.
Proposed Solution
Through trial and error, there are three changes that need to be made for the generated javascript to run from within internal browser code. Those are:

[ ] All imports and exports must be included at the top of the generated .js file
[ ] There is no access to import.meta.url so there must be a different way of finding and loading the wasm blob
[ ] There is no window object at self.self so this either needs to be passed in from the caller or just not generated/relied upon entirely

Rather than making these changes to the web target, I think it makes more sense to add a new target (perhaps browser-dev) particularly because requirements like not having access to a window make this case and generated js fundamentally different from the existing web use-case.
Alternatives
At the moment I'm maintaining a pretty hacky fork of wasm-bindgen so that we can generate the bindings from source as a part of Tor Browser's reproducible build process. This maintenance requires extra work and I think the option of integrating rust with this part of browser development would be beneficial to both Tor Browser and perhaps Firefox in the long run.
Additional Context
Specific error messages that I received from the browser console (ctrl+shift+J):

I think adding this target does not fit our current available maintenance bandwidth.
It would probably be really nice if one day we could have out-of-tree targets, which I think would be the way to go here. It would require a lot of work though.


Slider in browser full window instead of full screen

Is there a way to display slider-pro in browser full window instead of full screen?
Example: http://abcfolio.com/demos/fullscreen-slides/image-metadata-captions/

Yes: forceSize: 'fullWindow'

Maybe I'm missing something but the  forceSize: 'fullWindow' makes only the slider container 100%. It doesn't cover the full browser window. Website header and footer are still visible.
Slider-Pro container in fullWindow mode has style style="margin: 0px 0px 0px -372.5px; width: 1920px;.
The example I've provided a link to, has a slider container styled: style="position: fixed; top: 0px; left: 0px; width: 100%; height: 100%; z-index: 10000;".  It fills up the whole browser window and stays on the top of any other content.

When you set forceSize: 'fullWindow', the slider's width and height will become equal to the window's size. In the link you posted, there isn't a header or footer or any other content besides the slider; use the slider in the same context and it will look exactly the same. If, however, you have other content in the page and you want to have the slider displayed in the background and visible on the entire page, that's something else and for that it's important in what container you insert the slider. You need some HTML and CSS knowledge for this. You can try it first with a simple image and after you achieved placing it properly you can replace the image with the slider.

As long as I know that fullWindow resizes only the holding container I’m OK with it. It’s easy to overwrite.
Contrary to your explanation styling container position as fixed and using large z-index creates the full window effect on any kind of content including the one with header and footer.
Thank you for an excellent product and prompt support.


Fix editor and console colors

As title says.

Source editor

Console

Hey, thanks for this!
I actually realized that the colors look a bit different even though I used the same hex values as the other themes. Maybe I should redo the colors but using the color picker instead? That seems to be more accurate

@rmehri01 You mean colors for the keywords, etc.? Here I fixed only editor background, selection, cursor, invisibles and current line. If they are seem a little bit off you can try to do a hack as a did:

I just grab "Red" slider and pull it in whatever location and then I update "Hex Color". I don't know why, but this way it works and it applies exact hex color, otherwise it uses a different color 😠

Yeah, I meant for the other colors too. Ah okay interesting, I must've been doing something wrong with the hex values. I'll merge this and update some of the other colors too then 😃

@rmehri01 Thanks, I appreciate it.

No problem! Thanks for the contribution. I think this is looking much better now:

It looks amazing ❤


rados restructure singleton for downstream - mon-auth-caps

Signed-off-by: Rachanaben Patel<EMAIL_ADDRESS>

http://pulpito.ceph.redhat.com/racpatel-2020-05-19_00:43:47-rados:downstream:singleton-nautilus-distro-basic-argo/


mui-datatables does not render the table with supplied data, instead shows "Sorry, no matching records found"

Mui-datatables displays "Sorry, no matching records found" even when the dataArray variable is supplied to the data prop of the component.
Expected Behavior
Display the dataArray supplied to the data prop of the table.
## Current Behavior
Displays "Sorry, no matching records found" even when data is supplied.
## Steps to Reproduce (for bugs)

Initial set of data supplied to the table is rendered correctly.
Used the OnChangePage option to manipulate the data.
The dataArray variable which is supplied to the data prop is updated. (Did a console log on the dataArray variable supplied to the data prop, and it consoled the right data)
But the table displays "Sorry, no matching records found", which means the mui-datatable hasn't accepted the supplied variable to the data prop.

Material-UI  v4.9.14
MUI-datatables v2.14.0
React  v16.13.1

Can you create a CodeSandbox showing this? If so, I'll take a look. (ex: https://codesandbox.io/s/wy2rl1nyzl)

@patorjk thank you so much, but I think https://github.com/gregnb/mui-datatables/issues/189  ticket addressed my problem. And I got few insights from the same. I am sorry, I didn't find it earlier before creating this ticket and hence closing it now.


ValueError from 3_batchsize-8-compile.py

Hey there, thank you for sharing your work!
Describe the bug
I encountered a ValueError: wrapper has not been initialized while trying to replicate the code from src/3_batchsize-8-compile.py on Google Colab.
Stack trace
ValueError                                Traceback (most recent call last)
[<ipython-input-4-28220631b6f3>](https://localhost:8080/#) in <cell line: 77>()
    169
    170     start = time.time()
--> 171     train(
    172         num_epochs=1,
    173         model=model,

<31 frames>
[/usr/local/lib/python3.10/dist-packages/torch/_dynamo/convert_frame.py](https://localhost:8080/#) in has_tensor(obj)
    136         seen_ids[obj_id] = False
    137
--> 138         if isinstance(obj, (torch.Tensor, torch.nn.Module)):
    139             seen_ids[obj_id] = True
    140             return seen_ids[obj_id]

ValueError: wrapper has not been initialized

Versions
Python implementation: CPython
Python version       : 3.10.11
IPython version      : 7.34.0
torch       : 2.0.0+cu117
lightning   : 2.0.2
transformers: 4.29.0
Output

I have tried to sieve through the docs and the source code but I'm not too well versed in Python yet and unsure how to fix the problem.

Hm, that's weird. Maybe compilation is not supported on the Google Colab devices. I don't really have experience with Google Colab, and off the top of my head, I don't know how to fix this, sorry


Examples do not work in clusters > 1.21 due to CSI driver as new default

From 1.21 the default storage class is CSI driver, it will be used even if managed-premium is selected. If you apply the example YAMLs in a cluster > 1.21 it will fail with message:
FailedAttachVolume with rpc error: code = InvalidArgument desc = Volume capability not supported
This is because azure-disk does not support ReadWriteMany access mode and CSI enforces it, while previous sc did not. The YAMLs in these examples need to be changed to ReadWriteOnce like the ones used here: https://docs.microsoft.com/en-us/azure/aks/azure-disk-csi

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

ID: d1ac572f-c613-71fc-580a-2805b740b793
Version Independent ID: b4aeef15-7b0f-abc7-872e-28051e10d6ca
Content: Dynamically create Azure disks volume - Azure Kubernetes Service
Content Source: articles/aks/azure-disks-dynamic-pv.md
Service: container-service
GitHub Login: @zr-msft
Microsoft Alias: zarhoads

Actually, I see there is a note where it explains this, but maybe is worth to add a note saying that for some reason with previous sc you could mistakenly use the wrong access mode and not be notified.

Thanks for sharing the update.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


add depend people_msgs to pedestrian_plugin_msgs package

cabot-ros2を68276a2から更新してhost_wsでcolcon buildをすると以下のエラーが出た
(people関連だと思って)石原さんにみて頂いたところ、people_msgsの依存指定が必要だったようです
Starting >>> people_msgs
Starting >>> cabot_msgs
Starting >>> cabot_debug
Starting >>> mf_localization_msgs
Starting >>> odriver_msgs
Starting >>> pedestrian_plugin_msgs
Starting >>> tf_bag
Starting >>> track_people_msgs
--- stderr: pedestrian_plugin_msgs
CMake Error at CMakeLists.txt:7 (find_package):
  By not providing "Findpeople_msgs.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "people_msgs", but CMake did not find one.

  Could not find a package configuration file provided by "people_msgs" with
  any of the following names:

    people_msgsConfig.cmake
    people_msgs-config.cmake

  Add the installation prefix of "people_msgs" to CMAKE_PREFIX_PATH or set
  "people_msgs_DIR" to a directory containing one of the above files.  If
  "people_msgs" provides a separate development package or SDK, be sure it
  has been installed.

---
Failed   <<< pedestrian_plugin_msgs [0.32s, exited with code 1]
Aborted  <<< cabot_debug [0.33s]
Aborted  <<< odriver_msgs [0.33s]
Aborted  <<< people_msgs [0.36s]
Aborted  <<< cabot_msgs [0.36s]
Aborted  <<< mf_localization_msgs [0.41s]
Aborted  <<< track_people_msgs [0.42s]
Aborted  <<< tf_bag [0.55s]

ありがとうございます


Calendar filtering

Add filtering to calendar for:

Science classes
In person / Remote events
Grades

Codecov Report

Merging #74 (811cd57) into main (004b864) will increase coverage by 56.73%.
The diff coverage is 90.47%.

@@             Coverage Diff             @@
##             main      #74       +/-   ##
===========================================
+ Coverage   28.13%   84.87%   +56.73%
===========================================
  Files          24       11       -13
  Lines         654      271      -383
  Branches      181       36      -145
===========================================
+ Hits          184      230       +46
+ Misses        416       40      -376
+ Partials       54        1       -53

Flag
Coverage Δ

backend
84.87% <90.47%> (+9.46%)
:arrow_up:

frontend
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

backend/models/event.js
66.66% <ø> (ø)

backend/models/visit.js
60.00% <ø> (ø)

backend/services/mailer.js
72.72% <62.50%> (-27.28%)
:arrow_down:

backend/graphql/resolvers.js
87.01% <88.15%> (+10.49%)
:arrow_up:

backend/graphql/typeDefs.js
100.00% <100.00%> (ø)

backend/tests/testHelpers.js
100.00% <100.00%> (ø)

backend/utils/config.js
91.66% <100.00%> (+1.66%)
:arrow_up:

backend/utils/timeCalculation.js
100.00% <100.00%> (ø)

frontend/src/components/Custom/LumaWorkWeek.js

frontend/src/components/Message.js

... and 6 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 201a5b2...811cd57. Read the comment docs.


Request to make ImdsManagedIdentityCredential timeout configurable when used in DefaultAzureCredential

The timeout in question is currently limited to 1 second and in addition to that, is also set to private. In my case I've had to resort to a custom handler to circumvent this limitation. (which is way too strict) The convenience of DefaultAzureCredential makes it the go-to for many and anyone hoping to make use of the Managed Identity portion of it will be hamstrung by this limitation. Please consider making this configurable.
            DefaultAzureCredentialEnum::ManagedIdentity(credential) => {
                // IMSD timeout is only limited to 1 second when used in DefaultAzureCredential
                credential
                    .get_token(resource)
                    .timeout(Duration::from_secs(1))
                    .await
                    .context(
                        ErrorKind::Credential,
                        "getting managed identity credential timed out",
                    )?
                    .context(
                        ErrorKind::Credential,
                        "error getting managed identity credential",
                    )
            }

Thanks for reporting. I agree. The timeout is too short when it needs to be used. But it is too slow to be on by default in my opinion. I opened two other related issues. I hope to contribute something before the new year.


License?

Could a license be added to the code in this repository?
https://help.github.com/en/articles/adding-a-license-to-a-repository

Sure, but actually I'm no good with licenses! Which one means, essentially,
free for anything?
Additionally, I have better nested set code that works with EF Core
SPECIFICALLY and only with SQL as the database provider, if you'd prefer
that I could publish it.
Kind regards,
Josh
On Thu, 17 Oct 2019, 07:05 Nelson Chen<EMAIL_ADDRESS>wrote:

Could a license be added to the code in this repository?
https://help.github.com/en/articles/adding-a-license-to-a-repository
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/joshcomley/EfCore.NestedSets/issues/1?email_source=notifications&email_token=AAGIKNW6XVHFWN4ZT3HQ7HDQO76DDA5CNFSM4JBUUZP2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HSLLKPA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGIKNX6TKZEHSM7FPLNDMLQO76DDANCNFSM4JBUUZPQ
.

Free for anything would let anybody rip off your name and not provide attribution. That's not cool. So we want some protection at least. That said, I think choosing the MIT License like as used in .NET Core would be the one in your interest.
I'm interested in using this with PostgreSQL so an SQL Server-only version wouldn't interest me that much.

https://github.com/dotnet/corefx/blob/master/LICENSE.TXT
.NET Core didn't even bother with the year. So it can be even lower maintenance.

Actually, I am interested in the SQL server version. It wouldn't happen to be using hierarchyid would it which is making it SQL Server only? I would be interested in using it as a reference for a PostgreSQL using ltree or adding ltree support to it.
I'm looking at moving some model from using a Rails nested sets to ASP.NET Core nested sets then eventually to ltree.


SQL Queries don't display column names lined up with column content..

I just bumped up to the 0.1.5, and a query like below runs, but the column names don't match to the column fields!
%solr
select * from dev_raw_data limit 10

the search syntax still works properly!

I'm pretty sure select * is not supported in Solr SQL. Have you configured a different SQL backend?

Okay, I tried select metadata,status_str from dev_raw_data limit 10 and it worked as expected.  I swore that select * worked, as that is my default to explore a collection in 0.1.4.   Looking back at https://lucene.apache.org/solr/guide/7_7/parallel-sql-interface.html#solr-collections-and-db-tables (ready to prove you wrong), it does say * doesn't work...   I'd love to know why!!
Maybe since this is so common syntax, we should add it to https://lucene.apache.org/solr/guide/7_7/parallel-sql-interface.html#solr-sql-syntax?

Added https://issues.apache.org/jira/browse/SOLR-13461 and https://github.com/apache/lucene-solr/pull/671

This has been dealt with!

This has been dealt with!


Style Items Table should use human readable names in Name Field not SIDCs or Hierarchy Code

Noticed that the Name field for the many entries is using the SIDC or Hierarchy Code rather than a human readable name. Ex:
https://github.com/Esri/joint-military-symbology-xml/blob/master/samples/legacy_support/All_ID_Mapping_Original.csv#L751
Symbols_Root}\Legacy\2525C\I-U-SRU---.emf,64,I-U-SRU---
https://raw.githubusercontent.com/Esri/joint-military-symbology-xml/master/samples/imagefile_name_category_tags/Military-All-Icons.csv
Because this is the name a user will see in both the Pro style manager and more importantly the Pro symbol editor these should be changed to human-readable names (Note: the key field should likely remain the SIDC)
(Note: Updated original description to include Style Items)

I chose to use the hierarchy codes from 2525C for the legacy entities because they weren't being captured elsewhere and for legacy SVGs we had to build they are the closest equivalent in the older standards to the colon separated names we normally use for 2525D.  We derive the 2525D names from the formal entity/entity type/entity subtype hierarchy strings, which don't exist in the older standards.
2525C and 2525BC2 symbols that map to 2525D symbols use the 2525D colon separated symbol names.  2525C and 2525BC2 symbols that have to be represented by legacy SVGs, because they look different from their 2525D equivalent, or don't have a 2525D equivalent, currently use the dot separated hierarchy string as their name.
If we want to use more human readable text for the legacy entities/SVGs in the lookup, we'll need to either:

Use the closest name we can from 2525D for those symbols which are a close match to a 2525D symbol = less work.
Add more accurate names to JMSML for those legacy entities to reflect what they are actually called in 2525C = more work.

If this name is only used in this table I'm inclined not to worry about, but if this is the name the user will see in the style and elsewhere (like the ProSymbolEditor) then we should change and come up with a better naming convention (but certainly keep this as a tag).
I haven't yet looked at that style entries and tags to see if they are complete...i.e. able to completely create user-friendly symbols from the ProSymbolEditor when this supports legacy so I should do this now...

Looks like the legacy name is the SIDC - that probably won't work either (though that should be the Key which is correct)
Also - why is there a fill in the icons - is this a global issue? ( @abouffard  @Dbarnes1 ) -

The legacy symbol name is the SIDC because when you create a stylx from a style its the symbol's name that gets copied to the symbol's key field by Pro, where we need the SIDC.  If we use a different string for the symbol name then we'll have to use SQL code in a script to update the key field values.  I was trying to avoid that, but it may be unavoidable.
I certainly don't expect users to look inside the two mapping tables and I had largely hoped that, with the advent of an easier to use symbol editor that eventually supports all the versions of 2525, they would seldom need to look at the symbols in the style itself.
Yes, @Dbarnes1 and I are both aware of the color fill in those symbols and its on Daniel's list to fix in the SVGs.

Since the easier-to-use symbol editor actually presents this name to the user, the style item name is indeed important, see image at: https://github.com/Esri/military-symbol-editor-addin-wpf#military-symbol-editor-addin-wpf - Let's work on a naming convention that makes sense & once the style is stable we can add this task/work/fix to the sprint.
The mapping table name is less important (and you are right the end-user will never see this) - but is there any reason they can't both use the same simpler name as the style item?

Updated the title and original issue to include the style items - it is labeled enhancement but really something more than that in that it is a usability issue so after the 2525C style symbols problems are fixed this will likely be the next desired fix this sprint

@csmoore  - here is my suggestion for a naming convention.  Basically it is to use the closest equivalent to the names we have already.
WAR.SOFUNT.AVN.ROT, the current name for S-F-AH----, could instead be:
"Movement and Maneuver : Army Aviation/Aviation Rotary Wing : Special Operations Forces (SOF)"
This is the closest combination of 2525D symbol name and 2525D modifier name used together to make the symbol.  I would recommend this approach because these names are easily derived from what's already in JMSML so requiring very little new data entry.
I don't think we want to further identify the legacy symbols by putting the version of standard they are in in the name itself, because I'd think the tags are a better place to put that information,

That example looks better & more human readable to me - so long as:

it remains unique and won't be the same as any of the existing 2525D ones.
the 2525C domains use the same names
anything else we have forgotten since we last did this >2+ years ago (I remember it took numerous passes/iterations to get this all correct that time)

Once you do have the name and tags ready to review we do want you to create a brief writeup that steps us through the scenario of how the (1) symbol editor will use this name & style preview to do the things it does now (identify the target layer/symbol set, available fields, etc.) (2) how to create 2525C domains using these name.

@abouffard can you update this issue?

I believe this is resolved - I don't think I've seen any SIDCs in the symbol names for the released mil2525c_b2 style


Revert "Update troubleshooting-nextgen.md"

Reverts harness/developer-hub#2617

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Added support for localization using gettext.

A proof-of-concept spanish translation is in es.po; it is an incomplete
machine translation. But it demonstrates we can translate tutorial
dialog, character dialog, cutscenes, level information, messages,
buttons, and labels.
There is a new tool 'LocalizationDemo' which extracts some of these
strings for use in the PO template.

This messages.mo file shouldn't be here.

This file has been removed.


The network-manager service needs to be restarted/started at the exit point

Hi,
I recently try to flash couple Global smart plug and the tool works fantastic. The only issue I had was once the script finished to flash the firmware, it just exit by itself. If I am trying to run the script again, the docker process will be failed as no dns is working. I have to run "systemctl start network-manager" to run script again.
I hope you can add one more function at the end, either start the service or loop back to see if user like to flash another device.

Honestly, the answer is probably not.  While systemctl is the correct command for you system, it's not for all systems.  Starting and stopping isn't the same on all platforms, and we would have to remember all commands issued to stop and re-manipulate them to start, and that is edging on a bit too much work for this type of tool.
Looping isn't really feasible with the way variables and states are currently saved.
This will likely end up getting closed as #wontfix unless someone really wants to create a PR for it.

I see.. if possible just post a line at the end will be helpful.

For me, the script kill my systemd-resolved, which result in something like
ERROR: failed to solve: python:3.9.12-slim-buster: failed to do request: Head "https://registry-1.docker.io/v2/library/python/manifests/3.9.12-slim-buster": dial tcp: lookup registry-1.docker.io on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:55736-><IP_ADDRESS>:53: read: connection refused
Failed to build Docker image, stopping script

after stopping the script, and, e.g. run the script again.
A sudo systemctl start systemd-resolved solve this.


Various optimizations

Optimization when you build various versions and not storing the data for /etc/murmur twice (in different layers)

Thank for the optimization.


Add Prettier config and convert to yarn lint command to remove gulp lint command

This follows the linting config setup up in CCDB and complaint explorer.
Additions

Add Prettier configuration and VSCode Prettier settings.

Removals

Remove gulp lint command and related dependencies.

Changes

Lints files and auto and manually fix errors.

Testing

yarn lint should show no errors (it will show warnings).

Notes

Many changes were moving functions above where they were called, per https://eslint.org/docs/latest/rules/no-use-before-define

When I yarn this branch I get a bunch of new npm-packages-offline-cache packages. Do they need to be added or is my local cache being weird?


Result View

Could you please provide some information about the final result view. When I start monitoring D2C message, the output window just shows me these messages :
[IoTHubMonitor] Start monitoring D2C message for all devices ...
[IoTHubMonitor] Created partition receiver [1] for consumerGroup [$Default]
[IoTHubMonitor] Created partition receiver [0] for consumerGroup [$Default]
[IoTHubMonitor] Created partition receiver [2] for consumerGroup [$Default]
[IoTHubMonitor] Created partition receiver [3] for consumerGroup [$Default]
So, I actually can not observe any filtering massage on my Edge Device.
Thank you in advanced.

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

ID: a7852968-3c54-5584-df91-b01521efae43
Version Independent ID: c7340985-f6d2-2bf8-71e5-ee62dadb25e3
Content: Deploy Azure Function with Azure IoT Edge
Content Source: articles/iot-edge/tutorial-deploy-function.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: v-jamebr

@royaza Thanks for the feedback! We are currently investigating and will update you shortly.

Hi @royaza I walked through the Function tutorial again, and was able to see the D2C messages going through. I've included a screenshot below, where "issue5707" is my device name.
Perhaps you didn't set up VS Code with the correct IoT Hub connection string? Or your device modules aren't running? Or your deployment route wasn't configured correctly/was overwritten so that it's not sending the final message to $upstream?
@Mike-Ubezzi-MSFT can you refer royaza to some troubleshooting resources?

@royaza We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

This is all I get when I attempt to Start monitoring D2C messages:
Subscription selected: Azure CXP Community Internal Consumption IoT Hub selected: miubezzi-IoT-Hub [Edge] Start deployment to device [IoTEdge-Linux_001] [Edge] Deployment succeeded. [IoTHubMonitor] Start monitoring D2C message for all devices ... [IoTHubMonitor] Created partition receiver [1] for consumerGroup [$Default] [IoTHubMonitor] Created partition receiver [0] for consumerGroup [$Default]

So, no messages flowing to VS Code Integrated Terminal.

I had the same problem with the messages from Function not being sent to IoT Hub. To make it work I changed the Function route from:
"FROM /messages/modules/MyFilterFunction/outputs/output1 INTO $upstream"
to this:
"FROM /messages/modules/MyFilterFunction/* INTO $upstream"

@andrepodnozov are you still experiencing this issue?
@kgremban any insight on this?

yes I'm still experiencing this issue.

@andrepodnozov  Following the chain of linked issues, starting with outputName configured in edge function does not work, it looks like this was a product bug related to the AMQP communication protocol. The team has fixed the bug and it should be updated this week.
@femsulu Can you relabel this issue?

@andrepodnozov I think the issue of edgeHub not being reported as running in VS Code has been resolved. At least, I'm getting all greens in my deployments recently. Could you try again and close this issue if it's resolved?

I tried it with 1.0.1 agent and hub and I confirm that this issue is resolved.

But I don't know how to close issues here.

@andrepodnozov We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Update init.py

Update init.py file to solve log warning:
"Detected that custom integration 'ecowater_softener' calls async_forward_entry_setup for integration, ecowater_softener with title: Ecowater "serial number" and entry_id: xxxxxxxxxxxxxxxxxxx, which is deprecated and will stop working in Home Assistant 2025.6, await async_forward_entry_setups instead at custom_components/ecowater_softener/init.py, line 25: await hass.config_entries.async_forward_entry_setup(entry, "sensor"), please create a bug report at https://github.com/barleybobs/homeassistant-ecowater-softener/issues"

@barleybobs can it be merged and released? It looks that it will be deprecated sooner (2025.1) as error in my log is:
2024-09-17 07:53:48.132 WARNING (MainThread) [homeassistant.helpers.frame] Detected code that calls async_forward_entry_setup for integration ecowater_softener with title: Ecowater <redacted> and entry_id: <redacted>, during setup without awaiting async_forward_entry_setup, which can cause the setup lock to be released before the setup is done. This will stop working in Home Assistant 2025.1. Please report this issue.

Sorry for the late response, it has now been merged and I have released v3.4.0.
Thanks 👍


Set editor drag cursor texture to pan icon on Windows

The WIN32 platform lacks a DRAG cursor, and ARROW used by default so I think it's not a bad idea to set it up to pan mode icon instead.

Note: I've added this for the editor only, I guess on the apps users may implement it custom themself.

Meh, I think it's not looking good simply cuz the hand texture is not looking dragging + it does not correlate with dragging using the middle-mouse button.

Meh, I think it's not looking good simply cuz the hand texture is not looking dragging + it does not correlate with dragging using the middle-mouse button.


Made a small change in the Identifier and File Naming (Geekbench 4 v4.3.3)

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.
This change will just be here to follow the name structure we are talking about in https://github.com/microsoft/winget-pkgs/issues/15720

Microsoft Reviewers: Open in CodeFlow

Welp, there is another issue with the move
Addition and deletion only permitted in the same package directory.

Addition and deletion only permitted in the same package directory.

Addition and deletion only permitted in the same package directory.

Regarding what you stated on your first comment before the edit, I just tested the install using the new file structure etc for Geekbench 4 it works fine.
PS C:\> winget validate --manifest C:\manifests\p\PrimateLabs\Geekbench\4\4.3.3
Manifest validation succeeded.
PS C:\> winget install --manifest C:\manifests\p\PrimateLabs\Geekbench\4\4.3.3
Found Geekbench 4 [PrimateLabs.Geekbench.4]
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licences to, third-party packages.
Downloading https://cdn.geekbench.com/Geekbench-4.3.3-WindowsSetup.exe
  ██████████████████████████████  78.9 MB / 78.9 MB
Successfully verified installer hash
Starting package install...
Successfully installed

Yeeee i know, we either need to delete and recreate or someone higher up most allow the change

Yeeee i know, we either need to delete and recreate or someone higher up most allow the change

Yeah, I was thinking we could wait for a while. And if no response we can create Primate-Labs folder considering there is meant to be a space anyways.

I've made all the Manifests and PR's required to fix this, just needs to get approved :)
(you can close this one)

I've made all the Manifests and PR's required to fix this, just needs to get approved :)
(you can close this one)

Closed, refer to - https://github.com/microsoft/winget-pkgs/pull/15796.=


\Illuminate\Http\Request::validate() should throw exception

Larastan Version: 1.0.0
--level used: 8
Pull request with failing test: N/A

Description
When using the code below, PHPStan generates the following error:
Call to static method Illuminate\Http\Request::validate() on a separate line has no effect.

Since Request::validate() throws \Illuminate\Validation\ValidationException when validation fails, using the method without any assignment should be a valid usage.
I think the problem occurs because larastan doesn't define that Request::validate throws an exception?
Laravel code where the issue was found
public function method(\Illuminate\Http\Request $request)
{
    $request->validate([
        'key' => ['string'],
    ]);
}

I think that it has nothing to do with throwing an exception. Here is the same issue: https://github.com/nunomaduro/larastan/issues/995

Hi,
Thank you for the report. I think you are right Larastan doesn't know that validate can throw exception. I'll see what we can do.
@mabasic They are not the same issue. Completely different.

This
Call to static method Illuminate\Http\Request::validate() on a separate line has no effect.

is not the same as this:
Dynamic call to static method Illuminate\\Http\\Request::validate().

The same code triggers it:
$request->validate();

Yes, they are literally different error messages.

Aha, I see now. This issue has to do with $request->validate() (where there is nothing passed to the validate function) and the issue that I have linked has to do with treating $request->validate([]) as a static method call.
My bad, sorry.

But isn't it wrong that $request->validate() is treated as a static method?

Please continue in #995


how to catch error for autoUpdater

autoUpdater will throw a Javascript exception when network failed during auto update.
screenshot: http://postimg.org/image/nh06545kv/
how to catch this exception in app code .. I want to just ignore it silently..

You can catch it by:
autoUpdater.on('error', (error) => {
  console.log(error);
});


Update Auction.sol

Improved the functionality of only_owner and ongoing_auction modifier. Improved readability of errors for users.

ok


Move Profile configuration to json file

Replace Profile with new ContainerAdapter model

fixes #6

containers.json currently only contain wildfly 8 and 9 remote|managed|embedded configuration.

do you think we should extend it for EAP / JBoss AS as in Alpha1?

@lfryc of course. Just added a few to give the general idea of the format to see if anyone had any comments :)

pushed upstream https://github.com/arquillian/arquillian-container-chameleon/commit/b37fc6791dea46f519093320e2f0605c9a50c573


./go.test.sh error

OS:ubuntu; gcc version 7.3.0; go 1.10.4; and rocksdb master branch with shared lib: librocksdb.so.5.17
after export LD_LIBRARY_PATH=/usr/local/lib, the go.test.sh is running now,
but still fail for the below message:
ok      github.com/chrislusf/vasto/storage/binlog       0.097s  coverage: 82.4% of statements
ok      github.com/chrislusf/vasto/storage/codec        0.027s  coverage: 94.4% of statements
free(): invalid pointer
FAIL    github.com/chrislusf/vasto/storage/rocks        0.083s

No clue for your env. Please follow steps in here
https://github.com/chrislusf/vasto/blob/master/.travis.yml


Avalonia.Diagnostics in NuGet

The Dock.Avalonia NuGet package contains a reference to Avalonia.Diagnostics, see https://www.nuget.org/packages/Dock.Avalonia#dependencies-body-tab
This condition doesn't appear to be working, https://github.com/wieslawsoltes/Dock/blob/7cfc331db4a8d523f9de555ebaf7b65f9e0f947e/src/Dock.Avalonia/Dock.Avalonia.csproj#L19

Fixed in 11.0.10


exposures past 1 sec fail with ASI_ERROR_TIMEOUT

@maphilli14 is having problems with exposures greater than 1 second producing ASI_ERROR_TIMEOUTs.  This also happens with oacapture, which points to a hardware problem, not a problem with AllSky.
See also the end of Issue 417.

It does seem to work on windows - https://youtu.be/IN2qUpWdckc
Also recorded in FC briefly:

In the past I had used the SDK but was never proficient at installing them.  Please advise!

Also worth noting the oacapture messages as seen
https://user-images.githubusercontent.com/6034105/136716511-81053340-1d2a-4f9b-a076-ea8ebe759c8a.png
Transcribed to
 ASIGetExpStatus returned status 3

@maphilli14, ASIGetExpStatus doesn't return error 3 (ASI_ERROR_INVALID_CONTROL_TYPE, which means the camera was asked to do something it can't, like gamma, which most cameras don't support), so that might be a bug in oacapture.  The message above about "AutoExpMaxGain" are error 3.
Anyway, it works in Windows, and works in FireCapture (on the Pi, or Windows?), but does not work in oacapture and Allsky.   And on Allsky you can successfully take exposures < 1 second but not over 1 second, using either the version 0.8 exposure or the 0.7.  Is that correct?

@maphilli14,
This camera USED to work on this Pi, right?  Did anything change with the Pi?  Do you have access to a different one you can try?
If the camera did used to work on this same Pi, the only thing I can suggest is to try it with this version of the capture program, which is the version 0.7 one that knows about the newer options.  If THIS also doesn't work, it could be a problem with the Pi itself.  Perhaps the USB bus isn't getting enough power?
capture0.7with0.8arguments.zip

Just getting back to trying this again, it fails as follows:
capture                         capture0.7with0.8arguments.zip
capture0.7with0.8arguments.cpp  capture.cpp
pi@allsky:~/allsky $ cp NEW/capture0.7with0.8arguments.cpp ./capture.cpp
pi@allsky:~/allsky $ make capture
make[1]: Entering directory '/home/pi/allsky/src'
2021-11-05 22:06:21 Building capture program...
2021-11-05 22:08:18 Done.
make[1]: Leaving directory '/home/pi/allsky/src'
make[1]: Entering directory '/home/pi/allsky/config_repo'
2021-11-05 22:08:18 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/config_repo'
make[1]: Entering directory '/home/pi/allsky/notification_images'
2021-11-05 22:08:18 nothing to do for capture...
make[1]: Leaving directory '/home/pi/allsky/notification_images'
make[1]: Entering directory '/home/pi/allsky/scripts'
2021-11-05 22:08:18 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/scripts'

sudo service allsky stop ; sleep 5 ;  sudo service allsky start
pi@allsky:~/allsky $ tail /var/log/allsky.log
Nov  5 22:09:23 allsky allsky.sh[3556]:   > Sleeping from auto exposure: 200 ms (0 sec)
Nov  5 22:09:23 allsky allsky.sh[3556]: STARTING EXPOSURE at: 2021-11-05 22:09:23
Nov  5 22:09:27 allsky allsky.sh[3556]:      ***** Stopping AllSky *****
Nov  5 22:09:46 allsky allsky.sh[9016]:      ***** Starting AllSky *****
Nov  5 22:09:46 allsky allsky.sh[9016]: CAMERA: ZWO
Nov  5 22:09:46 allsky allsky.sh[9016]: CAMERA_SETTINGS: /etc/raspap/settings_ZWO.json
Nov  5 22:09:49 allsky allsky.sh[9016]: Starting allsky camera...
Nov  5 22:09:51 allsky allsky.sh[9016]: /home/pi/allsky/allsky.sh: line 166: /home/pi/allsky/capture: No such file or directory
Nov  5 22:09:51 allsky allsky.sh[9016]: 'capture' exited with RETCODE=127
Nov  5 22:09:51 allsky allsky.sh[9016]: *** After fixing, restart the allsky service. ***

Some things I tried ....

pi@allsky:~ $ cd allsky/
pi@allsky:~/allsky $ mkdir NEW
pi@allsky:~/allsky $ cd NEW/
pi@allsky:~/allsky/NEW $ wget https://github.com/thomasjacquin/allsky/files/7293039/capture0.7with0.8arguments.zip
--2021-11-05 22:04:59--  https://github.com/thomasjacquin/allsky/files/7293039/capture0.7with0.8arguments.zip
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-repository-files.githubusercontent.com/71661619/7293039?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211106%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211106T020500Z&X-Amz-Expires=300&X-Amz-Signature=946b98c0be0e16c5501970c64870f4a9f6e49844e4fc4930866665b7596f1382&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=71661619&response-content-disposition=attachment%3Bfilename%3Dcapture0.7with0.8arguments.zip&response-content-type=application%2Fx-zip-compressed [following]
--2021-11-05 22:05:00--  https://github-repository-files.githubusercontent.com/71661619/7293039?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211106%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211106T020500Z&X-Amz-Expires=300&X-Amz-Signature=946b98c0be0e16c5501970c64870f4a9f6e49844e4fc4930866665b7596f1382&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=71661619&response-content-disposition=attachment%3Bfilename%3Dcapture0.7with0.8arguments.zip&response-content-type=application%2Fx-zip-compressed
Resolving github-repository-files.githubusercontent.com (github-repository-files.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to github-repository-files.githubusercontent.com (github-repository-files.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 12773 (12K) [application/x-zip-compressed]
Saving to: ‘capture0.7with0.8arguments.zip’

capture0.7with0.8arguments.zi 100%[==============================================>]  12.47K  --.-KB/s    in 0.004s

2021-11-05 22:05:00 (2.76 MB/s) - ‘capture0.7with0.8arguments.zip’ saved [12773/12773]

pi@allsky:~/allsky/NEW $ ls
capture0.7with0.8arguments.zip
pi@allsky:~/allsky/NEW $ unzip capture0.7with0.8arguments.zi
unzip:  cannot find or open capture0.7with0.8arguments.zi, capture0.7with0.8arguments.zi.zip or capture0.7with0.8arguments.zi.ZIP.
pi@allsky:~/allsky/NEW $ unzip capture0.7with0.8arguments.zip
Archive:  capture0.7with0.8arguments.zip
  inflating: capture0.7with0.8arguments.cpp
pi@allsky:~/allsky/NEW $ ls
capture0.7with0.8arguments.cpp  capture0.7with0.8arguments.zip
pi@allsky:~/allsky/NEW $ cd ..
pi@allsky:~/allsky $ mv capture^C
pi@allsky:~/allsky $ ls capture*
capture  capture.cpp  capture_RPiHQ
pi@allsky:~/allsky $ ls -la
total 4468
drwxr-xr-x 14 pi   pi      4096 Nov  5 22:04 .
drwxr-xr-x 19 pi   pi      4096 Oct 29 06:17 ..
-rwxr-xr-x  1 pi   pi      5935 Oct  9 12:39 allsky.sh
-rwxr-xr-x  1 pi   pi   2155012 Oct  9 12:44 capture
-rwxr-xr-x  1 pi   pi     57358 Oct  9 12:43 capture.cpp
-rwxr-xr-x  1 pi   pi    524372 Oct  9 12:44 capture_RPiHQ
-rw-r--r--  1 pi   pi      1560 Oct  9 12:39 .clang-format
drwxr-xr-x  2 pi   pi      4096 Oct  9 15:26 config
drwxr-xr-x  2 pi   pi      4096 Oct  9 12:44 config_repo
drwxr-xr-x  9 pi   pi      4096 Oct  9 12:39 .git
-rw-r--r--  1 pi   pi       158 Oct  9 12:39 .gitattributes
-rw-r--r--  1 pi   pi       405 Oct  9 12:39 .gitignore
-rw-r--r--  1 pi   pi        97 Oct  9 12:39 .gitmodules
drwxr-xr-x  2 pi   pi      4096 Oct  9 12:53 gui
-rw-r--r--  1 pi   pi         0 Nov  5 22:05 image.jpg
drwxr-xr-x  4 pi   pi      4096 Nov  5 18:41 images
-rwxr-xr-x  1 pi   pi      1351 Oct  9 12:39 install.sh
-rwxr-xr-x  1 pi   pi    648664 Oct  9 12:44 keogram
-rw-r--r--  1 pi   pi      1070 Oct  9 12:39 LICENSE
-rw-r--r--  1 pi   pi    685777 Nov  5 22:05 liveview-image.jpg
-rw-r--r--  1 pi   pi      1291 Oct  9 12:39 Makefile
drwxr-xr-x  2 pi   pi      4096 Nov  5 22:05 NEW
drwxr-xr-x  2 pi   pi      4096 Oct  9 12:39 notification_images
-rw-r--r--  1 pi   pi     32172 Oct  9 12:39 README.md
drwxr-xr-x  2 pi   pi      4096 Oct 20 08:47 scripts
drwxr-xr-x  5 pi   pi      4096 Oct  9 21:41 src
-rwxr-xr-x  1 pi   pi    344864 Oct  9 12:44 startrails
drwxr-xr-x  2 root root    4096 Nov  5 22:05 TEMP
-rw-r--r--  1 pi   pi         5 Nov  5 22:05 temperature.txt
drwxr-xr-x  2 pi   pi      4096 Oct 29 11:59 tmp
-rwxr-xr-x  1 pi   pi      1019 Oct  9 12:39 uninstall.sh
-rw-r--r--  1 pi   pi      1789 Oct  9 12:39 variables.sh
drwxr-xr-x  2 pi   pi      4096 Oct  9 12:39 website
pi@allsky:~/allsky $ ls -la cap*
-rwxr-xr-x 1 pi pi 2155012 Oct  9 12:44 capture
-rwxr-xr-x 1 pi pi   57358 Oct  9 12:43 capture.cpp
-rwxr-xr-x 1 pi pi  524372 Oct  9 12:44 capture_RPiHQ
pi@allsky:~/allsky $ mv capture NEW/
pi@allsky:~/allsky $ mv capture.cpp NEW/
pi@allsky:~/allsky $ cp NEW/capture
capture                         capture0.7with0.8arguments.zip
capture0.7with0.8arguments.cpp  capture.cpp
pi@allsky:~/allsky $ cp NEW/capture0.7with0.8arguments.cpp ./capture.cpp
pi@allsky:~/allsky $ make capture
make[1]: Entering directory '/home/pi/allsky/src'
2021-11-05 22:06:21 Building capture program...
2021-11-05 22:08:18 Done.
make[1]: Leaving directory '/home/pi/allsky/src'
make[1]: Entering directory '/home/pi/allsky/config_repo'
2021-11-05 22:08:18 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/config_repo'
make[1]: Entering directory '/home/pi/allsky/notification_images'
2021-11-05 22:08:18 nothing to do for capture...
make[1]: Leaving directory '/home/pi/allsky/notification_images'
make[1]: Entering directory '/home/pi/allsky/scripts'
2021-11-05 22:08:18 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/scripts'
pi@allsky:~/allsky $ history | grep stop
  430  sudo service allsky stop ; sleep 5 ;  sudo service allsky start
pi@allsky:~/allsky $ !430
sudo service allsky stop ; sleep 5 ;  sudo service allsky start
pi@allsky:~/allsky $ tail /var/log/allsky.log
Nov  5 22:09:23 allsky allsky.sh[3556]:   > Sleeping from auto exposure: 200 ms (0 sec)
Nov  5 22:09:23 allsky allsky.sh[3556]: STARTING EXPOSURE at: 2021-11-05 22:09:23
Nov  5 22:09:27 allsky allsky.sh[3556]:      ***** Stopping AllSky *****
Nov  5 22:09:46 allsky allsky.sh[9016]:      ***** Starting AllSky *****
Nov  5 22:09:46 allsky allsky.sh[9016]: CAMERA: ZWO
Nov  5 22:09:46 allsky allsky.sh[9016]: CAMERA_SETTINGS: /etc/raspap/settings_ZWO.json
Nov  5 22:09:49 allsky allsky.sh[9016]: Starting allsky camera...
Nov  5 22:09:51 allsky allsky.sh[9016]: /home/pi/allsky/allsky.sh: line 166: /home/pi/allsky/capture: No such file or directory
Nov  5 22:09:51 allsky allsky.sh[9016]: 'capture' exited with RETCODE=127
Nov  5 22:09:51 allsky allsky.sh[9016]: *** After fixing, restart the allsky service. ***
pi@allsky:~/allsky $ ls -la
total 2592
drwxr-xr-x 14 pi   pi     4096 Nov  5 22:09 .
drwxr-xr-x 19 pi   pi     4096 Oct 29 06:17 ..
-rwxr-xr-x  1 pi   pi     5935 Oct  9 12:39 allsky.sh
-rw-r--r--  1 pi   pi    57358 Nov  5 22:06 capture.cpp
-rwxr-xr-x  1 pi   pi   524372 Oct  9 12:44 capture_RPiHQ
-rw-r--r--  1 pi   pi     1560 Oct  9 12:39 .clang-format
drwxr-xr-x  2 pi   pi     4096 Oct  9 15:26 config
drwxr-xr-x  2 pi   pi     4096 Oct  9 12:44 config_repo
drwxr-xr-x  9 pi   pi     4096 Oct  9 12:39 .git
-rw-r--r--  1 pi   pi      158 Oct  9 12:39 .gitattributes
-rw-r--r--  1 pi   pi      405 Oct  9 12:39 .gitignore
-rw-r--r--  1 pi   pi       97 Oct  9 12:39 .gitmodules
drwxr-xr-x  2 pi   pi     4096 Oct  9 12:53 gui
-rw-r--r--  1 pi   pi   672610 Nov  5 22:09 image.jpg
drwxr-xr-x  4 pi   pi     4096 Nov  5 18:41 images
-rwxr-xr-x  1 pi   pi     1351 Oct  9 12:39 install.sh
-rwxr-xr-x  1 pi   pi   648664 Oct  9 12:44 keogram
-rw-r--r--  1 pi   pi     1070 Oct  9 12:39 LICENSE
-rw-r--r--  1 pi   pi   248619 Nov  5 22:09 liveview-image.jpg
-rw-r--r--  1 pi   pi     1291 Oct  9 12:39 Makefile
drwxr-xr-x  2 pi   pi     4096 Nov  5 22:06 NEW
drwxr-xr-x  2 pi   pi     4096 Oct  9 12:39 notification_images
-rw-r--r--  1 pi   pi    32172 Oct  9 12:39 README.md
drwxr-xr-x  2 pi   pi     4096 Oct 20 08:47 scripts
drwxr-xr-x  5 pi   pi     4096 Nov  5 22:07 src
-rwxr-xr-x  1 pi   pi   344864 Oct  9 12:44 startrails
drwxr-xr-x  2 root root   4096 Nov  5 22:10 TEMP
-rw-r--r--  1 pi   pi        5 Nov  5 22:09 temperature.txt
drwxr-xr-x  2 pi   pi     4096 Nov  5 22:09 tmp
-rwxr-xr-x  1 pi   pi     1019 Oct  9 12:39 uninstall.sh
-rw-r--r--  1 pi   pi     1789 Oct  9 12:39 variables.sh
drwxr-xr-x  2 pi   pi     4096 Oct  9 12:39 website
pi@allsky:~/allsky $
pi@allsky:~/allsky $ sudo make capture
make[1]: Entering directory '/home/pi/allsky/src'
2021-11-05 22:12:02 Building capture program...
2021-11-05 22:12:38 Done.
make[1]: Leaving directory '/home/pi/allsky/src'
make[1]: Entering directory '/home/pi/allsky/config_repo'
2021-11-05 22:12:38 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/config_repo'
make[1]: Entering directory '/home/pi/allsky/notification_images'
2021-11-05 22:12:38 nothing to do for capture...
make[1]: Leaving directory '/home/pi/allsky/notification_images'
make[1]: Entering directory '/home/pi/allsky/scripts'
2021-11-05 22:12:38 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/scripts'
pi@allsky:~/allsky $ ls src/
capture      capture_RPiHQ      include  keogram.cpp  Makefile    startrails.cpp  sunwait-src
capture.cpp  capture_RPiHQ.cpp  keogram  lib          startrails  sunwait
pi@allsky:~/allsky $ rm -rf src/capture
pi@allsky:~/allsky $ rm -rf src/capture.cpp
pi@allsky:~/allsky $ cp capture.cpp src/
pi@allsky:~/allsky $ make capture
make[1]: Entering directory '/home/pi/allsky/src'
2021-11-05 22:13:22 Building capture program...
2021-11-05 22:13:46 Done.
make[1]: Leaving directory '/home/pi/allsky/src'
make[1]: Entering directory '/home/pi/allsky/config_repo'
2021-11-05 22:13:46 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/config_repo'
make[1]: Entering directory '/home/pi/allsky/notification_images'
2021-11-05 22:13:46 nothing to do for capture...
make[1]: Leaving directory '/home/pi/allsky/notification_images'
make[1]: Entering directory '/home/pi/allsky/scripts'
2021-11-05 22:13:47 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/scripts'
pi@allsky:~/allsky $ ls
allsky.sh      config_repo  install.sh          Makefile             scripts     temperature.txt  website
capture.cpp    gui          keogram             NEW                  src         tmp
capture_RPiHQ  image.jpg    LICENSE             notification_images  startrails  uninstall.sh
config         images       liveview-image.jpg  README.md            TEMP        variables.sh
pi@allsky:~/allsky $ ls src
capture      capture_RPiHQ      include  keogram.cpp  Makefile    startrails.cpp  sunwait-src
capture.cpp  capture_RPiHQ.cpp  keogram  lib          startrails  sunwait
pi@allsky:~/allsky $ cp src/capture .
pi@allsky:~/allsky $ ls
allsky.sh      config       images      liveview-image.jpg   README.md   TEMP             variables.sh
capture        config_repo  install.sh  Makefile             scripts     temperature.txt  website
capture.cpp    gui          keogram     NEW                  src         tmp
capture_RPiHQ  image.jpg    LICENSE     notification_images  startrails  uninstall.sh
pi@allsky:~/allsky $ sudo service allsky stop ; sleep 5 ;  sudo service allsky start
pi@allsky:~/allsky $ tail /var/log/allsky.log
Nov  5 22:14:59 allsky allsky.sh[9390]: Auto Exposure value: 1000 ms
Nov  5 22:14:59 allsky allsky.sh[9390]:   > Sleeping from auto exposure: 200 ms (0 sec)
Nov  5 22:15:01 allsky allsky.sh[9390]: Exposure value: 1,000,000 µs (1,000.0 ms)
Nov  5 22:15:01 allsky allsky.sh[9390]: 20211105 22:15:01
Nov  5 22:15:01 allsky allsky.sh[9390]:   > WARNING: currently saving an image; can't save new one.
Nov  5 22:15:01 allsky allsky.sh[9390]: Auto Exposure value: 1000 ms
Nov  5 22:15:01 allsky allsky.sh[9390]:   > Sleeping from auto exposure: 200 ms (0 sec)
Nov  5 22:15:01 allsky allsky.sh[9390]: /home/pi/allsky/allsky.sh: line 166:  9485 Segmentation fault      "${ALLSKY_HOME}/${CAPTURE}" "${ARGUMENTS[@]}"
Nov  5 22:15:01 allsky allsky.sh[9390]: 'capture' exited with RETCODE=139
Nov  5 22:15:02 allsky allsky.sh[9390]: *** After fixing, restart the allsky service. ***
pi@allsky:~/allsky $

@maphilli14, you want to copy the capture.cpp file to the allsky/src directory, and run "make capture" from within that directory, then run "make install".
The WARNING: currently saving an image; can't save new one. message is one I added in version 0.8.  It usually indicates your delay isn't long enough, so the system is still writing one image when the next one is ready to write.
Before trying the capture0.7with0.8arguments.zip file,  try the attached file instead.  If that doesn't help, then try capture0.7with0.8arguments.zip file.
capture.cpp.txt

With capture.cpp.txt compiled...

Nov  9 17:59:06 allsky allsky.sh[4846]:   > Sleeping: 251.0 ms
Nov  9 17:59:06 allsky allsky.sh[4846]:   > Saving NIGHT image 'image.jpg'
Nov  9 17:59:07 allsky allsky.sh[4846]: STARTING EXPOSURE at: 2021-11-09 17:59:07   @ 948,502 us
Nov  9 17:59:07 allsky allsky.sh[4846]:   > Saving NIGHT image 'image.jpg'
Nov  9 17:59:07 allsky allsky.sh[4846]:   > Sleeping: 251.0 ms
Nov  9 17:59:07 allsky allsky.sh[4846]: scripts/saveImageNight.sh: line 91: 12381 Aborted                 convert "$IMAGE_TO_USE" -resize "${THUMBNAIL_SIZE_X}x${THUMBNAIL_SIZE_Y}" "$THUMBNAILS_DI
R/$SAVED_FILE"
Nov  9 17:59:07 allsky allsky.sh[4846]: *** saveImageNight.sh: WARNING: THUMBNAIL resize failed with RET=134; continuing.
Nov  9 17:59:08 allsky allsky.sh[4846]: convert-im6.q16: Premature end of JPEG file `image.jpg' @ warning/jpeg.c/JPEGWarningHandler/387.
Nov  9 17:59:08 allsky allsky.sh[4846]: convert-im6.q16: Corrupt JPEG data: premature end of data segment `image.jpg' @ warning/jpeg.c/JPEGWarningHandler/387.
Nov  9 17:59:08 allsky allsky.sh[4846]: STARTING EXPOSURE at: 2021-11-09 17:59:08   @ 948,502 us
Nov  9 17:59:08 allsky allsky.sh[4846]:   > Saving NIGHT image 'image.jpg'
Nov  9 17:59:08 allsky allsky.sh[4846]:   > Sleeping 200.0 ms from auto exposure
Nov  9 17:59:09 allsky allsky.sh[4846]: STARTING EXPOSURE at: 2021-11-09 17:59:09   @ 1,024,382 us
Nov  9 17:59:09 allsky allsky.sh[4846]: convert-im6.q16: Premature end of JPEG file `image.jpg' @ warning/jpeg.c/JPEGWarningHandler/387.
Nov  9 17:59:09 allsky allsky.sh[4846]: convert-im6.q16: Corrupt JPEG data: premature end of data segment `image.jpg' @ warning/jpeg.c/JPEGWarningHandler/387.
Nov  9 17:59:10 allsky allsky.sh[4846]: convert-im6.q16: Premature end of JPEG file `image.jpg' @ warning/jpeg.c/JPEGWarningHandler/387.
Nov  9 17:59:10 allsky allsky.sh[4846]: convert-im6.q16: Corrupt JPEG data: premature end of data segment `image.jpg' @ warning/jpeg.c/JPEGWarningHandler/387.
Nov  9 17:59:16 allsky allsky.sh[4846]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #2 (with 0.8 exposure = NO) (11)
Nov  9 17:59:18 allsky allsky.sh[4846]: STARTING EXPOSURE at: 2021-11-09 17:59:18   @ 1,024,382 us
Nov  9 17:59:25 allsky allsky.sh[4846]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #3 (with 0.8 exposure = NO) (11)
Nov  9 17:59:27 allsky allsky.sh[4846]: STARTING EXPOSURE at: 2021-11-09 17:59:27   @ 1,024,382 us
Nov  9 17:59:34 allsky allsky.sh[4846]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #4 (with 0.8 exposure = NO) (11)
Nov  9 17:59:36 allsky allsky.sh[4846]: STARTING EXPOSURE at: 2021-11-09 17:59:36   @ 1,024,382 us
Nov  9 17:59:43 allsky allsky.sh[4846]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #5 (with 0.8 exposure = NO) (11)
Nov  9 17:59:45 allsky allsky.sh[4846]: STARTING EXPOSURE at: 2021-11-09 17:59:45   @ 1,024,382 us
Nov  9 17:59:52 allsky allsky.sh[4846]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #6 (with 0.8 exposure = NO) (11)
Nov  9 17:59:54 allsky allsky.sh[4846]: Maximum number of consecutive errors of 5 reached; exiting...
Nov  9 17:59:56 allsky allsky.sh[4846]:   > Saving NIGHT image 'image.jpg'
Nov  9 17:59:59 allsky allsky.sh[4846]:      ***** Stopping AllSky *****
Nov  9 18:00:04 allsky allsky.sh[4846]: 'capture' exited with RETCODE=2

the 0.7 with 08 args does this...

Nov  9 21:36:10 allsky allsky.sh[6527]:   > Sleeping from auto exposure: 200 ms (0 sec)
Nov  9 21:36:11 allsky allsky.sh[6527]: Exposure value: 1,000,000 µs (1,000.0 ms)
Nov  9 21:36:11 allsky allsky.sh[6527]: 20211109 21:36:11
Nov  9 21:36:11 allsky allsky.sh[6527]: Auto Exposure value: 1000 ms
Nov  9 21:36:11 allsky allsky.sh[6527]:   > Sleeping from auto exposure: 200 ms (0 sec)
Nov  9 21:36:13 allsky allsky.sh[6527]: Exposure value: 1,000,000 µs (1,000.0 ms)
Nov  9 21:36:13 allsky allsky.sh[6527]: 20211109 21:36:13
Nov  9 21:36:13 allsky allsky.sh[6527]: Auto Exposure value: 1000 ms
Nov  9 21:36:13 allsky allsky.sh[6527]:   > Sleeping from auto exposure: 200 ms (0 sec)
Nov  9 21:36:13 allsky allsky.sh[6527]: /home/pi/allsky/allsky.sh: line 166:  6628 Segmentation fault      "${ALLSKY_
HOME}/${CAPTURE}" "${ARGUMENTS[@]}"
Nov  9 21:36:13 allsky allsky.sh[6527]: 'capture' exited with RETCODE=139
Nov  9 21:36:14 allsky allsky.sh[6527]: *** After fixing, restart the allsky service. ***

FYI this is a mono camera, LMK if the settings should be changed at all...

@maphilli14, it shouldn't matter that it's a mono camera.  Try running vcgencmd get_throttled - it will give a code that states whether or not your Pi has low voltage, which could be the issue with your camera.
Can you attach (don't copy/paste) the complete /var/log/allsky.log file from the 0.7 with 08 args run?  You can do this:
# stop the service
sudo truncate -s 0 /var/log/allsky.log
# start the service
# let it run until you have issues, then attach the file.

It's very interesting that you go the "Segmentation fault" with the version 0.7 file.  Someone else is getting that with the newest version 0.8 file, and I've never seen it before.

@maphilli14, another thing to try if you can.
Stop the service.
In your home directory is a subdirectory called .ZWO (with a leading period).  It's hidden by default so you'll need to show the hidden files by pressing CTRL-H when in the explorer window.
Enter the .ZWO directory and open ASIconfig.xml, then change DebugPrint’s value from 00 to 01.
Then restart the service.  This will add a bunch of additional debugging statements from the camera driver to /var/log/allsky.log.  I'm hoping they'll give us an idea why you're getting the ASI_ERROR_TIMEOUTs.

I will try some of the other items  you suggested but here's what the capture0.7with0.8arguments.zip is doing for me tonight....
allsky-20211110.log
.

@maphilli14, 50005 means throttling and low voltage are currently happening, and happened in the past.
If you move the attached file (without the .txt on the end) to /var/www/html/includes, then go to the "System" link in the WebUI you'll see the throttle status.
If you are getting under-voltage, this power unit may help.  Or use a more powerful power supply or power cables with thicker wires.
system.php.txt

I'm happy to play with the hardware a bit more but it's confusing to me why the same hardware used to work and now does not.  could the camera be at any fault?
Throttle Status | Not able to get throttle status:sudo: no tty present and no askpass program specified

@maphilli14, to get the WebUI to correctly display the throttle status, download the latest includes/system.php from allsky-portal and the latest gui/sudoers from allsky.  Then:
sudo cp gui/sudoers /etc/sudoers.d/allsky
I don't know why things used to work but don't now.  One possibility is they didn't always work, but the software didn't tell you and the problems weren'tusually bad enough for most people to notice.  The 0.8 version added a LOT of error checking so problems are more noticable now.
It's also possible 0.8 added a lot of bugs, some of which are still present.
It would be interesting to revert to 0.7 and see if you are still having issues.  I know that's possible but don't know how.

@maphilli14 Are you sure you were running the version 7 with 8 arguments code when you got the Segmentation fault?  The was a bug introduced in 0.8 that caused a segmentation fault, but it wasn't in 0.7.
Could you do me a favor and set Debug Level to 4 and run with that version for a minute, then attach the log file?
Thanks

I pulled the setup off the roof and put it into the lab.  Yanking the uSD from the Pi3 and putting into a Pi4 with proper power supply on the wall, I find some odd behavior.  The issues of no exp >1s are consistent with the Pi4 and a new USB3 cable on the ASI174mm.  The issue goes away after replacing with an ASI290.  I'll test more but I'm thinking it's either drivers/config or hardware/camera issues.

@maphilli14, pretty strange.  The ASI174 works fine in Windows but not on either Pi using oacapture OR AllSky, which implies it's not a Pi hardware issue (although it could be).  It's very possible an issue with ZWO drivers.

That is my guess as well, this is long and extensive but likely no resolution since June 2021?   https://bbs.astronomy-imaging-camera.com/d/12315-libasicamera2-for-aarch64/58  I'll keep searching but that....
 Exposure Status: 3
sounds similar to what I had as well.  I wonder if some change in Buster made it malfunction beyond >1sec?

https://github.com/OpenPHDGuiding/phd2/issues/936
what's all this mean?

Just catching a daytime crash too....
Nov 15 09:27:55 allsky allsky.sh[21527]: [WorkingFunc]: drop frames:66
Nov 15 09:27:55 allsky allsky.sh[21527]: [WorkingFunc]: get len:0x0 drop:67  frametime:19520us waittime:89ms
Nov 15 09:27:55 allsky allsky.sh[21527]: [WorkingFunc]: nothing get count:1
Nov 15 09:27:55 allsky allsky.sh[21527]: [WorkingFunc]: head:0x1a1b COUNT:6426 tail:0x1b1c count:7453
Nov 15 09:27:55 allsky allsky.sh[21527]: [WorkingFunc]: drop frames:68
Nov 15 09:27:55 allsky allsky.sh[21527]: [WorkingFunc]: get len:0x0 drop:69  frametime:19520us waittime:89ms
Nov 15 09:27:55 allsky allsky.sh[21527]: [WorkingFunc]: nothing get count:1
Nov 15 09:27:56 allsky allsky.sh[21527]: [WorkingFunc]: get len:0x1a4084 drop:70  frametime:19520us waittime:89ms
Nov 15 09:27:56 allsky allsky.sh[21527]: [WorkingFunc]: get len:0x1a4084 drop:70  frametime:19520 waittime:89
Nov 15 09:27:56 allsky allsky.sh[21527]: [WorkingFunc]: drop frames:70
Nov 15 09:27:56 allsky allsky.sh[21527]: Maximum number of consecutive errors of 5 reached; exiting...
Nov 15 09:27:56 allsky allsky.sh[21527]: [WorkingFunc]: get len:0x0 drop:71  frametime:19520us waittime:89ms
Nov 15 09:27:56 allsky allsky.sh[21527]: [WorkingFunc]: nothing get count:1
Nov 15 09:27:56 allsky allsky.sh[21527]: [SaveSetting]: save REG
Nov 15 09:27:56 allsky allsky.sh[21527]: [StopCapture]: stop capture
Nov 15 09:27:56 allsky allsky.sh[21527]: [StopCapture]: >> wait Working thread exit
Nov 15 09:27:56 allsky allsky.sh[21527]: [Stop]: WaitForSingleObject >
Nov 15 09:27:56 allsky allsky.sh[21527]: [WorkingFunc]: head:0x1c1c COUNT:7197 tail:0x909 count:2313
Nov 15 09:27:56 allsky allsky.sh[21527]: [WorkingFunc]: drop frames:72
Nov 15 09:27:56 allsky allsky.sh[21527]: [ResetCirBuff]: Rst
Nov 15 09:27:56 allsky allsky.sh[21527]: [releaseAsyncXfer]: free transfer!
Nov 15 09:27:56 allsky allsky.sh[21527]: [Stop]: WaitForSingleObject >
Nov 15 09:27:56 allsky allsky.sh[21527]: [SetGainExpFunc]: Thread SetGainExpFunc Exit!
Nov 15 09:27:56 allsky allsky.sh[21527]: [Stop]: WaitForSingleObject <
Nov 15 09:27:56 allsky allsky.sh[21527]: [WorkingFunc]: working thread exit!
Nov 15 09:27:56 allsky allsky.sh[21527]: [Stop]: WaitForSingleObject <
Nov 15 09:27:56 allsky allsky.sh[21527]: [StopCapture]: << wait Working thread exit
Nov 15 09:27:59 allsky allsky.sh[21527]:      ***** Stopping AllSky *****
Nov 15 09:27:59 allsky allsky.sh[21527]: destructor called!
Nov 15 09:27:59 allsky allsky.sh[21527]: 'capture' exited with RETCODE=2

@maphilli14, Would you please attach the version of capture.cpp you are using, that's giving the errors?  I want to make a change and have you try it.
The OpenPHDGuiding/phd2#936 stuff is an issue in PHD2, not in AllSky.  They are calling some ZWO functions but not checking the return status.  I added a lot of that status checking in version 0.8.
I'm reading through the long ZWO post to see if there's anything that might help us.

I sure can!  I did a fresh git clone when I switched to the Pi4....
capture.cpp.txt

@maphilli14 thanks Mike.  Would you please try with this file.  All I did was change the timeout of a capture to "wait forever", and changed the version string to include "timeout=-1" so we know which version you are running.
Please stop the service, run sudo truncate -s 0 /var/log/allsky.log, then compile this and copy allsky/src/capture to allsky.  Then post a log.
Mike's capture.cpp.txt

seems to fail even at <=1sec still, but all day it was stable on oacapture with same hardware!  :(
allsky-log-20211115.txt

what are these?

  D:\E-Delete\allsky-log-20211115.txt (5 hits)
	Line 251: Nov 15 23:47:36 allsky allsky.sh[6448]: [WorkingFunc]: BAD delta time:7769 pkg:800
	Line 269: Nov 15 23:47:39 allsky allsky.sh[6448]: [WorkingFunc]: BAD delta time:2627 pkg:800
	Line 288: Nov 15 23:47:42 allsky allsky.sh[6448]: [WorkingFunc]: BAD delta time:2635 pkg:800
	Line 308: Nov 15 23:47:45 allsky allsky.sh[6448]: [WorkingFunc]: BAD delta time:2841 pkg:800
	Line 327: Nov 15 23:47:48 allsky allsky.sh[6448]: [WorkingFunc]: BAD delta time:3075 pkg:800

Linux allsky 5.10.63-v7l+ #1457 SMP Tue Sep 28 11:26:14 BST 2021 armv7l

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Nov 15 09:24:00 2021 from <IP_ADDRESS>
pi@allsky:~ $ sudo service allsky stop
pi@allsky:~ $ cd allsky/src/
pi@allsky:~/allsky/src $ rm capture
pi@allsky:~/allsky/src $ mv M
Makefile                Mike.s.capture.cpp.txt
pi@allsky:~/allsky/src $ mv Mike.s.capture.cpp.txt capture.txt
pi@allsky:~/allsky/src $ rm ../capture
pi@allsky:~/allsky/src $ cd ..
pi@allsky:~/allsky $ make capture
make[1]: Entering directory '/home/pi/allsky/src'
2021-11-15 23:44:24 Building capture program...
^Cmake[1]: *** [Makefile:122: capture] Interrupt
make: *** [Makefile:24: capture] Interrupt

pi@allsky:~/allsky $ ^C
pi@allsky:~/allsky $ ^C
pi@allsky:~/allsky $ ^C
pi@allsky:~/allsky $ sudo truncate -s 0 /var/log/allsky.log
pi@allsky:~/allsky $ make capture
make[1]: Entering directory '/home/pi/allsky/src'
2021-11-15 23:44:43 Building capture program...
2021-11-15 23:44:59 Done.
make[1]: Leaving directory '/home/pi/allsky/src'
make[1]: Entering directory '/home/pi/allsky/config_repo'
2021-11-15 23:44:59 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/config_repo'
make[1]: Entering directory '/home/pi/allsky/notification_images'
2021-11-15 23:44:59 nothing to do for capture...
make[1]: Leaving directory '/home/pi/allsky/notification_images'
make[1]: Entering directory '/home/pi/allsky/scripts'
2021-11-15 23:44:59 nothing to do for capture
make[1]: Leaving directory '/home/pi/allsky/scripts'
pi@allsky:~/allsky $ ls
allsky.sh      gui         keogram             notification_images  startrails       variables.sh
capture_RPiHQ  image.jpg   LICENSE             README.md            temperature.txt  website
config         images      liveview-image.jpg  scripts              tmp
config_repo    install.sh  Makefile            src                  uninstall.sh
pi@allsky:~/allsky $ ls src/
capture      capture_RPiHQ      capture.txt  keogram      lib       mode_RPiHQ_mean.cpp  startrails.cpp  sunwait-src
capture.cpp  capture_RPiHQ.cpp  include      keogram.cpp  Makefile  startrails           sunwait
pi@allsky:~/allsky $ cp src/capture .
pi@allsky:~/allsky $ cat /var/log/allsky.log
pi@allsky:~/allsky $ sudo service allsky start

@maphilli14, Hi, the log file you recently posted isn't from Mike's capture.cpp.txt; it's from the version you had been running.  After you do a cd src; make capture you need to cp capture .. then restart the service.  Sorry I forgot to mention that.  So the commands would be:
# stop the service
sudo truncate -s 0 /var/log/allsky.log
cd allsky/src
# Copy the new capture.cpp program here and rename to "capture.cpp"
make capture
cp capture ..
# restart the service

If you run "make capture" in the "allsky" directory it tries to make everything under the sun.
The version displayed near the top of the log file should be
*** Allsky Camera Software v0.8.1b, timeout=-1 |  2021 ***
I don't know what the BAD delta time messages are for.  It's not clear what most of the entries in ZWO's log file are...

I feel like a n00b for compiling, I've been doing it since slackware 2.4, but still don't get it all right!  😔
I think I did it right but don't see timeout=-1 in the logs...
it seemed to do a daytime capture for a bit longer than normal, but did eventually die.
I feel like there something underlying for libraries or drivers that is causing a difference between the 174 and the 290 on buster.  Both cameras are fine on Win10 with FC for exp > 1sec, but exhibit different behavior on the Pi 😭
Thanks for all the hard work making allsky better, hopefully for all not just me!
allsky-cli-20211116.txt
allsky-log-20211116.txt

@maphilli14 Try cd src; grep "Allsky Camera" capture.cpp and see if it has the correct version.
If you do another run, please set the Debug Level to 4.  It was 0 in your last run which hides almost all the output I need.
Thanks.

printf("%s *** Allsky Camera Software v0.8.1b |  2021 ***\n", KGRN);

and it seems pretty stable right now

allsky-log-20211116b.txt
with failure

@maphilli14, The "grep" for the file you want will return
printf("%s *** Allsky Camera Software v0.8.1b, timeout=-1 |  2021 ***\n", KGRN);
I attached that file.
maphilli14-capture.cpp.txt

@maphilli14, if the file I just attached doesn't help, something you can try is to add swiotlb=131072 to end of the line (NOT on a new line) in /boot/cmdline.txt, then reboot.

I hope I didn't confuse myself with capture.cpp and capture.txt in the src directory... I think i have the right one this time...

3hrs and stable for daytime!  🤞

@maphilli14 woo-hoo!  This is the best it's ever done, right?
Can you send me the log file?

allsky-log-20211117.txt

allsky-log-20211117b-nighterr.txt
now it just seems to stop new captures once it hits an error.  It doesn't error out, just holds the last known good image
IE froze on frame 18:28:45 and kept displaying that instead of any new ones and also didn't display the red stopped in liveview

@maphilli14, the change I made in the file was to have it wait forever for the camera to return an image.  This was on the off-chance that the ASI_ERROR_TIMEOUTs you were seeing were really timeouts.
What happened when you ran it is that all the sub-second pictures worked fine, but once it tried a picture > 1 second the camera never returned.  It went for about 1 hour 8 minutes, then I assume you stopped the service.
It looks like you restarted the service, and it was nighttime, and the exact same thing happened.
In both cases, the camera would display some log messages every second or two, then repeat.
Please try again but set the "Version 0.8 exposure" to OFF.  If it hangs, let it go a couple minutes then stop the service and send the log file.
Unless there's some setting that we're supposed to set before taking pictures that I'm not aware of, this looks like an issue with the ZWO driver or the camera itself.  Since it works on Windows, that would imply it's the ZWO Linux driver.

@maphilli14, try this version AFTER your current version with "Version 0.8 exposure" OFF.
The timeout in this newer version is back to normal
capture.cpp.txt

Will do, I'm eclipse tired today, hope to try this weekend!  Thanks much @EricClaeys

I had some initial good success <1s but it seems it might have died at some point... I am restarting and will try again tonight <1s and then later with >1s.... logs are 0bytes :(  stay tuned

I retested last night with exp=999 after finding I had set the exp to 1999ms and it failed... woke up this am to find it's in a "Allsky software is not running" state.  With logs.  I'm tempted to redo the entire uSD with fresh raspbian and use my old methods of pulling down the SDK and testing with oacapture before any allsky git clones..
allsky-log-20211123a.zip
..

@maphilli14, it was in the "Allsky software is not running" state because as soon as daytime came, the "night max exposure" of 999 you set didn't apply so it quickly tried to take a picture over 1 second and died due to ASI_ERROR_TIMEOUTs.
Attached is a version of the camera_options_ZWO.json file that supports a daytime max exposure.
Copy it to /etc/raspap (will need sudo), then in the WebUI go to the Camera Settings link (may need to refresh your browser) and you'll see it.  You can set it to 999 also.
camera_options_ZWO.json.txt

I tried a fresh copy of raspbian and the SDK with oacapture, which didn't recognize the camera as it usually did for me in the past.  I grabbed the openastro libasi-xxx.deb and then oacapture did find the camera.  NO allsky git clones at all.  Same issue.  I think this is a libASI problem and not sure where to take it next, but likely not related to allsky per se.

Trying the ASI forums - https://bbs.astronomy-imaging-camera.com/d/13593-asi174mm-stopped-working-on-pi34

@maphilli14   Are you still having this problem, or can we close the Issue?
Eric

I do still have this issue but it seems to be related to Linux and not to allsky I think we're safe to close this

From: EricClaeys @.>
Sent: Tuesday, May 17, 2022 12:43:00 AM
To: thomasjacquin/allsky @.>
Cc: maphilli14 @.>; Mention @.>
Subject: Re: [thomasjacquin/allsky] exposures past 1 sec fail with ASI_ERROR_TIMEOUT (#650)
@maphilli14https://github.com/maphilli14 Are you still having this problem, or can we close the Issue?
Eric
—
Reply to this email directly, view it on GitHubhttps://github.com/thomasjacquin/allsky/issues/650#issuecomment-1128404876, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABOBFOPOK4YM2FSTZJR67ALVKMPVJANCNFSM5F6ZAIRQ.
You are receiving this because you were mentioned.Message ID: @.***>

@maphilli14 one year later, have you resolved this ?

I've swapped to a QHY and indi-allsky we can close this.
Mike

From: Patrice Delorme @.>
Sent: Wednesday, August 23, 2023 11:34 PM
To: thomasjacquin/allsky @.>
Cc: maphilli14 @.>; Mention @.>
Subject: Re: [thomasjacquin/allsky] exposures past 1 sec fail with ASI_ERROR_TIMEOUT (#650)
@maphilli14https://github.com/maphilli14 one year later, have you resolved this ?
—
Reply to this email directly, view it on GitHubhttps://github.com/thomasjacquin/allsky/issues/650#issuecomment-1690942165, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABOBFOOCZ2K7S4UNPS72V4TXW3DUZANCNFSM5F6ZAIRQ.
You are receiving this because you were mentioned.Message ID: @.***>


how to auto zoom to the crop area when initiated (fit: BoxFit.contain)

Is there any way to auto zoom to the square crop area when the widget is initiated.  My image is 16:9, and i can only use BoxFit.contain to allow full image editing instead of BoxFit.cover (which only have square part), currently i use a work around (after build and rotate back and forth) to achieve this, but ugly...:
return ExtendedImage.memory(
      cachedOriFilters[filter?.name ?? "_"],
      fit: BoxFit.contain,
      mode: ExtendedImageMode.editor,
      extendedImageEditorKey: editorKey,
      initEditorConfigHandler: (state) {
        return EditorConfig(
          cornerSize: Size(0.0, 0.0),
          cropRectPadding: EdgeInsets.all(0.0),
          // maxScale: 2.0,
          cropAspectRatio: CropAspectRatios.ratio1_1,
          animationDuration: Duration(milliseconds: 0),
          tickerDuration: Duration(milliseconds: 0),
        );
      },
      loadStateChanged: (ExtendedImageState state) {
        switch (state.extendedImageLoadState) {
          case LoadState.loading:
            break;
          case LoadState.completed:
            SchedulerBinding.instance
                .addPostFrameCallback((_) => _onAfterBuild(context));
            break;
          case LoadState.failed:
            break;
        }
      },
    );

void _onAfterBuild(BuildContext context) {
    editorKey.currentState.rotate(right: true);
    editorKey.currentState.rotate(right: false);
  }

please provide runable demo, i didn't get your point

picture is more than a word:
this is normal setting, i put ExtendedImage in a square container with cropAspectRatio 1:1 and fit=BoxFit.contain :

this is after when i size the crop, picture fills entire square (which is what i want in the initial):

Is there any way i can fill the to the entire square at initial (not doing fit:BoxFit.cover)?
what i come out a workaround is to rotate back and forth to achieve it, which is ugly (shown in
above code)

reopen it, if it still has problem.