controller should debounce reconcile requests

It looks to me as if the controller triggers exactly one event for each change that was detected on e.g. an "owned resource".
Assume you have 10 owned resources for each resource, and 10 managed resources. That makes 100 events and thus 100 reconciliations on the startup of an operator.
The same for scheduled/delayed reconcile outcomes.
IMHO the controller queue should queue up a reconcile request if there is no event yet scheduled for this resource, or if the scheduled event is further in the future than the new request.
EDIT: (clux): See https://github.com/kube-rs/kube/issues/318#issuecomment-1500611234

Assume you have 10 owned resources for each resource, and 10 managed resources. That makes 100 events and thus 100 reconciliations on the startup of an operator.

No, the scheduler ensures that each object can only have one spot in the queue.
This considers the controller's root objects, not the triggering objects (so 5 Pods owned by 1 Controller would still be debounced based on the Controller).
Once slight caveat is that objects can be rescheduled as soon as the reconciler has started (you don't need to wait for it to finish). This means that depending on timing, you might end up with ~3 reconciles per object on startup (one gets started immediately since the queue is empty, one gets queued based on a secondary trigger, one gets queued because you updated the object's status).
If you /are/ able to reproduce the OP's behaviour reliably then that's probably a bug, and I'd appreciate seeing it.

This is what I can see in the log:
[2020-09-07T13:00:29Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:29Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:29Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:29Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:30Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:30Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:30Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:30Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:30Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
[2020-09-07T13:00:30Z INFO  hawkbit_operator::controller] Reconcile: hawkbit-operator/default
…

It goes on for a while like this.
Taking a look at the code you referenced, it looks to me as if that has an issue in the case you return with a requeue-delay, as you currently have to.
Assume you return in the first reconcile loop with requeue=10s … then he next event would still be queued, before it is earlier. Resulting in the same 10s, that loop could go on for a while.

In that case, the old queue entry should be reused. Is hawkbit_operator public?

In that case, the old queue entry should be reused. Is hawkbit_operator public?

Yes: https://github.com/ctron/hawkbit-operator

Maybe it would make sense do add some rate limiting feature, as in the Go version of the controller runtime:

https://github.com/kubernetes-sigs/controller-runtime/blob/master/pkg/ratelimiter/ratelimiter.go
https://github.com/kubernetes/client-go/blob/master/util/workqueue/rate_limiting_queue.go

Revisiting this old issue to ensure we are doing everything we can. Here is a brief overview of what we do:

[x] deduplication in scheduler. yes, provided it happened before it ran
[ ] debouncing of events by a few seconds in the scheduler. could be better
[x] allow opt-in predicates to hard-filter per-input stream

For anything else there are still the standard approaches;

use annotations on secondary streams to set checkpoints for the reconciler
use status fields on the primary stream to create checkpoints for the reconciler
gate check in the reconciler work that is guaranteed to be done to avoid duplicate heavy work

but these approaches are scarier since you run the risk of creating less idempotent reconcilers that can get into bad states (reconciler thinks it is done, and you cannot re-trigger it because it gate checks itself out of correcting the problem).
Debouncing
I feel the key question left for this issue is:
Is our debouncing as good as it can be? Judging by the code comments, probably not, but this stuff is also hard.
Ideally we want classical debouncing behavior:

event comes in? schedule a reconciliation for the relevant object at now() + N seconds
another event comes in before reconciliation is due? reschedule, for now() + N seconds
N second elapses after last event? reconcile

5 seconds is probably OK given the heavy work that usually works, but if we ever manage to expose options for the Controller, then this would be a good thing to expose.
Leaving this open and resolving older comments that are now out of date.

Closing this. Better scoped issue about how to improve scheduler debouncing linked in #1247


ddl: Fix exchange partition across databases (release-7.1)

What problem does this PR solve?
Issue Number: close https://github.com/pingcap/tiflash/issues/7296
Problem Summary:
What is changed and how it works?
Check List
Tests

[ ] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-all-tests

/run-all-tests

/cherry-pick release-6.5


Documents without. Github link

Why is there not an GitHub repository with the code.
Greeting,
Martin.

@martin-scheringa all the code samples for the EF Core documentation can be found here - there's a single solution you can open for all samples.
On most pages, we have an explicit section linking to the samples for that page, see e.g. this page.


while loop

I'm not sure if this is my fault or gore's, but I believe I am typing the same code into go run and gore:
func power(base int, exponen tint) int {
	monad := 1
	for exponent > 0 {
		monad *= base
		exponent--
		}
	return monad
	}

I think gore is thinking there is an unmatched ( or { in here, but go run disagrees.
HTH

The issue is resolved now. Note that you have a typo in the first line.


Viewport Support

Add support for rendering to viewports in the rendergraph

This is now done via dynamic state in command buffers (as part of the backend rewrite)

This is now done via dynamic state in command buffers (as part of the backend rewrite)


pypi: normalize name in pypi_info

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

This is just another small QoL improvement to the PyPI helpers: we now normalize the package name that gets returned in pypi_info, which means that PyPI resource names are now consistent and a little easier to search for throughout formulae that are updated with update-python-resources.

Thanks again @woodruffw!


Fides ints 116 twilio sms access erasure

Closes #
Description Of Changes
Write some things here about the changes and any potential caveats
Code Changes

[ ] list your code changes here

Steps to Confirm

[ ] Add/configure the connector in UI
[ ] Verify config and icon UI looks good
[ ] Ensure the test integration button works
[ ] Create an Access DSR with the identity value
[ ] Verify email sent by Fides with customer data is correct

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation:

[ ] documentation complete, PR opened in fidesdocs
[ ] documentation issue created in fidesdocs
[ ] if there are any new client scopes created as part of the pull request, remember to update public-facing documentation that references our scope registry

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md
[ ] For API changes, the Postman collection has been updated
If there are any database migrations:

[ ] Ensure that your downrev is up to date with the latest revision on main
[ ] Ensure that your downgrade() migration is correct and works

[ ] If a downgrade migration is not possible for this change, please call this out in the PR description!

Closed in favour of https://github.com/ethyca/fides/pull/4979


My idea is to remove all classes besides background and add a new class called face. This means I obviously have to modify the last layer. What I don't understand is how I can train on my own data.
I followed the advice given in #221 and I tried to store my image dataset in a PASCAL VOC format, so that I can use the already implemented class Pascal Voc. I also generated xml-files, where the bounding box coordinates are stored. However I get some really strange bugs and I think I have to further modify the code to get it running on my own data. Since I am relatively unexperienced in neural network programming, I am having a hard time and I don't know where to start.
Can someone tell me how I can train on my own data?

sounds like you need to either check your xml, images, dataset itself, or post the bugs here

Actually I have my own dataset in format of ["filename" "boxes label values Like x-min y-min x-max y-max" "class-name"] and filename consist the path of the image, so how can given this dataset to model for testing and training , please  help me ..

@devendraswamy I have the exact same issue. The advice given in #221 didn't help either. Isn´t there a easy way to use faster rcnn for just ["filename", "x1","y1","x2","y2","class-name"] annotatione? If anyone knows I`d be happy to hear some suggestions. Thank you in advance!

@stadtgiraffe that would be very very painful the second you have images with multiple objects.. I suggest you try building your dataset in coco with something like https://github.com/jsbroks/coco-annotator , set this project to coco , and try again

I already had a dataset, but I encrypt that data in the form of .txt only, here I want to access the data from that .txt file because my data not in the form of coco or pascal, so please give me any suggestion
Thanking you!

not sure what you mean by encrypting data into a text file.
if you dont want to use the data loaders provided, you'd likely need to interface your own.. I cannot recommend that since I haven't tried it, but it is likely possible
You'd likely craft one based on the others, then pick it up via commandline arguements
https://github.com/jwyang/faster-rcnn.pytorch/blob/master/trainval_net.py#L41-L43
again, don't recommend it but if you need to.. it is possible

Thank you for your valuable information, one more doubt please help me . i want to increase the model accuracy , now  its giving good results that OK but getting better accuracy , which parameters i have to tune ( tell me about parameter tuning).
Thanking you!

you likely need to review your data, not just the hyper parameters... for the latter, I suggest the following
https://www.coursera.org/learn/deep-neural-network

Thank you very much for your support , could you please tell me about how can i decrease the loss value in this project ?? kindly give me the suggestion.

there are too many factors in order for me to know that... you need to review your data, review the parameters... this is the challenge of ML projects quite frankly.
if you can, use the tensorboard https://github.com/lanpa/tensorboardX

Thank you so much for your support !
On Fri, Dec 20, 2019 at 2:04 AM Erik<EMAIL_ADDRESS>wrote:

there are too many factors in order for me to know that... you need to
review your data, review the parameters... this is the challenge of ML
projects quite frankly.
if you can, use the tensorboard https://github.com/lanpa/tensorboardX
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jwyang/faster-rcnn.pytorch/issues/480?email_source=notifications&email_token=ALLD6LXO6T23WH2QGPT2VULQZPLGVA5CNFSM4G7FTZGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHK3CXQ#issuecomment-567652702,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALLD6LSWSP3CSBMDN37WPWDQZPLGVANCNFSM4G7FTZGA
.

sir i successfully run tensorboardx and  one more doubt , i want to check the object detection for coco dataset but demo.py is only applicable for pascal voc dataset, could you please suggest the solution for testing the 80 classes of coco with demo.py code, in this demo.py which lines i have to modify ??
Thanking you !

Sir i solved this and i modified the demp.py code , thanking you.

sir any suggestions for data augmentation ??


Dataset Availability

We are developing a multi eye gaze detecting system. We need iris dataset for that. how can we get the dataset?

Any response on this issue/request?

Hi @shashimalcse, We opensource only the solutions. Thanks!


chore: pbft sync while block cert voted

Checking reward votes in PbftSyncPacketHandler can sometimes fail if we are moving to the next period at the same time which should not be handled as malicious behaviors. If it does fail, a check is added if we actually moved to next period and in that case we restart syncing because it is very likely that we are already synced and restartSyncingPbft will verify this.

prnet cleaned-up successfully


Latest compile closing error

./VERGEd stop
VERGE server stopping
*********$ VERGEd: /usr/include/boost/thread/pthread/recursive_mutex.hpp:104: boost::recursive_mutex::~recursive_mutex(): Assertion `!pthread_mutex_destroy(&m)' failed.
Repeatable: yes.
Debug seems to close al right.
wallet.dat closed
DBFlush(false) ended              37ms
StopNode()
Flushed 7386 addresses to peers.dat  62ms
Flush(true)
DBFlush(true) ended               0ms
VERGE exited
edit: ubuntu 16.04 64bit amd processor

Replicated this. Same warning upon termination.

looks like we need to switch some boost code around. will do that next

Latest ubuntu compile doesn't give the error anymore, I think we can close this. Congrads on the update.


Parser unit tests

Add unit tests on parser.

I am commenting on this because it is tagged with documentation, and it may be an easy first task for someone to get involved :)
My question is: what would be the recommended way to get involved in the project? Any good-first-issues that can be a nice starting point. What other prerequisites may be there? Feel free to remove this if there is a better place to ask this type of questions.

@novica thank you!
I apologise for the late reply, I'm drowning in work at the moment.
I probably used the wrong label on this here I'm afraid. It's about writing unit tests for the parser and not documentation. You're of course welcome to do that if you want but one reason I've not done it myself is that it's not the most pleasant or exciting of tasks.
If you want to contribute to the documentation that's totally fine (it already received a few PRs/issues, it's more than welcome)

Hi @JohnCoene I am not nececeraly looking to do this particular task. I was not sure what is the best place to ask so I asked here.
But the question is really what is a good place to start, what would you consider to be a getting-started issue in the project, if any?


Portkey AI integration with Anthropic

This PR adds documentation for integrating Portkey AI with Anthropic's LLMs. Portkey AI offers an AI Gateway and Observability Suite, enabling teams to build reliable and efficient AI applications.
Key Features

[x] Enhanced observability with 42+ metrics and logs
[x] Advanced routing features (retries, fallbacks, load balancing)
[x] Semantic caching for cost optimization
[x] Guardrails for input/output verification

Hey @alexalbertt can you take a look at this? thanks!

@maheshmurag can you take a look at this?

Hey @maheshmurag! Noticed the PR was closed—just curious if there was any specific reason? Happy to make any tweaks if needed. Thanks!


Add RSpec/Rails/TravelAround and RSpec/RedundantAround cops

Since Rails 5.2, travel_back is called automatically, so you can easily do that by just calling it in before instead of using around with nested blocks.

https://github.com/rails/rails/pull/29860

In response to this change, I thought it would be a good idea to add a cop recommending the easier way when possible.
# bad
around do |example|
  freeze_time do
    example.run
  end
end

# good
before { freeze_time }

Unlike a typical Pull Request, the exception here is the addition of two cops.
RSpec/Rails/TravelAround applies the following autocorrection:
# before
around do |example|
  freeze_time do
    example.run
  end
end

# after
before { freeze_time }

around do |example|
  example.run
end

This may result in a meaningless around. As a measure to remove this, I have also added RSpec/RedundantAround cop to remove this kind of redundant around. I thought it would be more orthogonal to leave it to an independentcCop rather than have each cop take care of such a redundant around. This is why the both two cops are included in this one Pull Request.
For further reference, another possible idea related to this Rails change would be to remove the redundant travel_back as shown below:
# bad
after { travel_back }

# good

# bad
around do |example|
  foo
  example.run
  bar
  travel_back
end

# good
around do |example|
  foo
  example.run
  bar
end

In some cases, there may be travel-dependent hooks after this, so this would be an unsafe autocorrection.

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[ ] Squashed related commits together.
[x] Added tests.
[x] Updated documentation.
[x] Added an entry to the CHANGELOG.md if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

If you have created a new cop:

[x] Added the new cop to config/default.yml.
[x] The cop is configured as Enabled: pending in config/default.yml.
[x] The cop is configured as Enabled: true in .rubocop.yml.
[x] The cop documents examples of good and bad code.
[x] The tests assert both that bad code is reported and that good code is not reported.
[x] Set VersionAdded: "<<next>>" in default/config.yml.

If I recall it correctly, travel_back is called from teardown, which is only called when RSpec's MinitestLifecycleAdapter is included. This is the case for Rails example groups, but not in general. Can you please confirm or refute this?
References https://github.com/rspec/rspec-rails/issues/2263 https://github.com/rubocop/rubocop-rails/pull/38

Oh, it's true. There are cases where #after_teardown is not called. Specifically, if the ExampleGroup does not have one of the following metadata[:type], then this Cop is not applicable because of this reason.

:controller
:feature
:generator
:helper
:job
:mailbox
:mailer
:model
:request
:request
:request
:routing
:system
:view

So, would it be better to add the above explanation and set Safe: false?
Or, instead, maybe we could limit Include to spec/{controllers,features,...}/**/*.rb, expecting config.infer_spec_type_from_file_location! to be enabled.

If the cop is focused to specs with Rails metadata it might be fine.
Just one scenario that is risky:

a spec has Rails metadata, but doesn't have really, like a type: :model for MyService spec
we suggest removing travel_back
they clean up metadata as redundant when it turns out the spec works without it
travel_back is now not called automatically on teardown :boom:

What happens if the example is using freeze_time, is travel_back still called automatically? In other words, can we now avoid:
it 'does something' do
  freeze_time do
    # whole body of the test
  end
end

and just call freeze_time in the beginning? Note that this is valid only if the block is the last thing in the example, e.g. we don't rely on time being restored for next statements.
Also, in the above case, perhaps someone would prefer to still use the block, instead of just freeze_time statement

@r7kamura I'm sorry, there were few releases around the capybara extraction.
Would you mind bringing the Changelog up to date and I'll merge the PR

Thank you, @r7kamura !


stop() doesn't stop the rain the first time it's called after start()

I'd modified your sample HTML and used some JS:
<emoji-rain id="rain"></emoji-rain>

var rain = document.getElementById('rain');
rain.start();
setTimeout(function(){ rain.stop(); }, 5000);

The rain didn't stop. I manually called stop() and it worked. It always works in the second call.

Of course I'm just learning about web components 😄

It worked when autostarted and called stop() manually.

Ah, thanks for filing this. There's probably a bug in the start method -- I'll take a look at it...soon..ish :)


git binary patch explore

The pull request fixes #4 partially.
Suppose, we have diff only (without original repo), then only literal type can be valuable.

@babenek thanks!  Is this ready to merge?  I just want to make sure since the title contains "explore" and the branch is named "tmp" :smile:

@cscorley,
Yes, the pull request is ready. Sorry for confused branch name :)

Thanks!  As always, you're contributions are very appreciated.


Adding Vlan manager implementation and test cases

This PR added Vlan manager implementation and test cases to provide tenets isolation between different VPCs. The change includes:

new vlan manager class
changes in ACA_OVS_Programmer to use the vlan manager class
new two machine (manual) test case to test tenet isolation in different VPC

This is awesome! Delivered as promised and right on time 👍


Lag in applying dark theme at startup

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.301
Where did you get the app from?
F-Droid
Android version
8.1.0
Device model
noname (echo Feeling)
Steps to reproduce
Choose Dark theme.
Close the app.
Start the app.
Expected behavior
When the app starts the background should immediately be dark.
Actual behavior
For a few moments (1 or 2 seconds) the theme is Light. During this time only the header bar is displayed. The theme turns Dark at the same moment as the mail folder contents appears.
Enough time for my eyes to die XD
The problem appeared when I updated to 6.301, but I do not update apps very frequently. Last time was "a few months ago". Sorry for not being able to provide the working version I used before :-(
Logs
No response

Duplicate of #6057


May be able to avoid need for user adding IMD force manually

Problem is that forces added after the system is constructed aren't recognised, but it seems we can reinitialise the context after adding it in the runner? https://github.com/IRL2/nanover-protocol/blob/main/python-libraries/nanover-omni/src/nanover/omni/openmm.py#L19-L44

nanover.omni.omm.OpenMMSimulation now does this


Feature request: Python edition

Hey,
Seeing the python SDK/framework is in preview now, can we get all the bot documentation pages like this and others have python documentation added?
Currently I just have to use the code samples provided and the generic parts of these docs to try understand the python SDK.
Thanks.

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

ID: 4ccf81d0-a7a0-1e2a-5b35-8cfd723c1225
Version Independent ID: e3ebe0a1-a22f-1535-c649-3f79158b4ece
Content: How bots work - Bot Service
Content Source: articles/v4sdk/bot-builder-basics.md
Service: bot-service
Sub-service: sdk
GitHub Login: @johnataylor
Microsoft Alias: johtaylo

While in preview, most of the info about it will live in the GitHub repo. Once released from preview, it'll have most of the accompanying docs - we're in the process of putting them together.
If you have specific questions about Python, try asking her or on stack overflow (with the botframework tag) and our support team should be able to help out. For official docs, we hear your request and are working on it!


Use AccessExclusiveLock for truncating Babelfish catalogs

Description
When truncating certain Babelfish catalogs, we use the
heap_truncate_one_rel function which expects the caller to hold the
AccessExclusiveLock on the catalog.
This commit updates the lock used for opening/closing the catalog from
RowExclusiveLock to AccessExclusiveLock.
Task: BABEL-5439
Signed-off-by: Sharu Goel<EMAIL_ADDRESS>Check List

[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the Apache 2.0 and PostgreSQL licenses, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

4 of 4 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.003%) to 73.683%

Totals

Change from base Build<PHONE_NUMBER>5:
0.003%

Covered Lines:
43087

Relevant Lines:
58476

💛  - Coveralls


Add mocha.min.js file to stacktrace filter

Requirements

Filling out the template is required. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
All new code requires tests to ensure against regressions.

Description of the Change
Adds a check for the minified version of mocha.js to the StackTraceFilter.

Alternate Designs
A regex pattern could be implemented instead of indexOf(), not sure if that's preferred.

Why should this be in core?
Utils would have to be overloaded to provide the same behavior otherwise.

Benefits
Allows the minified mocha version to exhibit the same filter behavior as designed.

Possible Drawbacks
Can't think of any.

Applicable issues
#3921

Coverage increased (+0.07%) to 91.897% when pulling 442f38d977fff7624d48d657bc425913cf0c85ac on brian-lagerman:master into 750c5f81625f4f67d0d3a4602e344dac8663ee07 on mochajs:master.


Environment list duplicate tags (resourceReferences)

According to the docs Environments - List
GET https://dev.azure.com/{organization}/{project}/_apis/distributedtask/environments/{environmentId}?expands=resourceReferences&api-version=7.1-preview.1
Should return the environment's info, including each resource's tags, which it does but repeats the same tag instead of enumerating them.
URI enterred:
https://dev.azure.com/redacted/redacted/_apis/distributedtask/environments/62?expands=resourceReferences&api-version=7.1-preview.1
JSON returned:
{"resources":[{"tags":["app-nlb1","app-nlb1","app-nlb1","app-nlb1"],"id":123,"name":"WVM0TDAPPWB1","type":"virtualMachine"},{"tags":["app-nlb2","app-nlb2","app-nlb2","app-nlb2"],"id":124,"name":"WVM0TDAPPWB2","type":"virtualMachine"}],"id":62,"name":"Dev","description":"Automatically created environment","createdBy":"redacted","createdOn":"2022-06-03T15:01:25.7033333Z","lastModifiedBy":"redacted","lastModifiedOn":"2022-06-03T15:10:50.06Z","project":"redacted"}

As you can see, the tags are duplicated: (for ..WB1) app-nlb1, app-nlb1, app-nlb1, app-nlb1
But in reality, the tags are: (for ..WB1) app, app-nlb1, nlb1, node1
Expected result:
{"resources":[{"tags":["app","app-nlb1","nlb1","node1"],"id":123,"name":"WVM0TDAPPWB1","type":"virtualMachine"},{"tags":["app","app-nlb2","nlb2","node2"],"id":124,"name":"WVM0TDAPPWB2","type":"virtualMachine"}],"id":62,"name":"Dev","description":"Automatically created environment","createdBy":"redacted","createdOn":"2022-06-03T15:01:25.7033333Z","lastModifiedBy":"redacted","lastModifiedOn":"2022-06-03T15:10:50.06Z","project":"redacted"}

I tried:

api-version=7.1-preview.1
api-version=6.0-preview.1

Same results

@patware Thanks for reporting that looks like a bug, I tried to reproduce but didn't find any environment with tags. I will forward you feedback to the team owning this API though.


For each environment standardize the parameters for a canonical version of the environment.

This is now supported in environments/registry.py


Allow for previewing 3D in the 2D editor

Bugsquad edit, implements (partially):

https://github.com/godotengine/godot-proposals/issues/7513

Is there a proposal for this open? Otherwise this needs a proposal, as we require them for new features like this, so please open one in that case.

There's this proposal: https://github.com/godotengine/godot-proposals/issues/7513
The PR implements the 3D in 2D part.

I've read the proposal and this PR's solution is very limited to what was proposed. Which brings a question whether the feature is useful in the current state. It just displays a non-interactive snapshot of the 3D view. Though it's probably useful for designing UI at least.
Found a couple of problems.
When higher viewports are disabled, their preview displays some garbage:
https://github.com/godotengine/godot/assets/2223172/e4e5062c-cd65-48d8-a15b-a1be14f27884
Also the stretching mentioned above:
https://github.com/godotengine/godot/assets/2223172/7ebac556-ccc5-4b0f-b021-1ead5411bd42
For the former I think the buttons could be disabled if a viewport is inactive. For the latter not sure, with the current functionality it's probably expected. Although resizing the viewport could maybe update the 3D view even if it's currently inactive, to prevent the issue I recorded.


RF connectivity component

hey @fsdavid , I did some refactoring of the connectivity component, but I am not 100% confident that the component still works in all circumstances.
Can you pull the branch and give some feed back on what doesn't work?

Sure, I will look at it

I see 2 major bugs:
1 - connectivity colors does not restore when region deselected from both - sidebar top close icon and from layer widget
2 - if we deselect region and then select any region again, connectivity automatically applies - also if we select and return from other parcellation

@fsdavid I have fixed the bugs you mentioned... I think
Wouldlove to hear if there are other bugs

Great, I think it has not more bugs.


Errors with vitest

Describe the bug
I'm struggling to create vitest unit tests for pages/components that use $t
To Reproduce
Steps to reproduce the behavior:

Go to https://stackblitz.com/edit/github-mag9gj-h2v1xa?file=README.md,app%2Fpages%2Findex.vue,package.json,locales%2Fen-GB.json,nuxt.config.ts,app%2Fcomponents%2FTestComponent.vue,app%2Fcomponents%2FTestComponent.nuxt.spec.ts,tests%2Fvitest.unit-config.ts
Run npm run test
See errors with loading _locals and $t is not a function

Errors
[nuxt] error caught during app initialization FetchError: [GET] "/_locales/general/en-GB/data.json?v=1733229424546": 404 Cannot find any path matching /_locales/general/en-GB/data.json?v=1733229424546.
    at $fetch2 (file:///home/projects/github-mag9gj-tnstob/node_modules/ofetch/dist/shared/ofetch.03887fc3.mjs:333:15)
    at loadTranslationsForRoute (/home/projects/github-mag9gj-tnstob/node_modules/nuxt-i18n-micro/dist/runtime/plugins/01.plugin.js:232:20)
    at eval (/home/projects/github-mag9gj-tnstob/node_modules/nuxt-i18n-micro/dist/runtime/plugins/01.plugin.js:255:118)
    at applyPlugin (/home/projects/github-mag9gj-tnstob/node_modules/nuxt/dist/app/nuxt.js:146:25)
    at executePlugin (/home/projects/github-mag9gj-tnstob/node_modules/nuxt/dist/app/nuxt.js:183:9)
    at Module.applyPlugins (/home/projects/github-mag9gj-tnstob/node_modules/nuxt/dist/app/nuxt.js:197:5)
    at initApp (/home/projects/github-mag9gj-tnstob/node_modules/nuxt/dist/app/nuxt-vitest-app-entry.js:55:7)

TypeError: $setup.$t is not a function
 ❯ Proxy._sfc_render components/TestComponent.vue:23:76
      5| <template>
      6|
Test from component: {{ $t('welcome') }}

      7| </template>
       |            ^

I'm not sure if this is an issue with the library or something I'm going to have to manually mock on reflection.

OK resolved the missing $t function by mocking it:
import { mockNuxtImport } from '@nuxt/test-utils/runtime';
import { type Mock, vi } from 'vitest';

type MockedI18n = {
  $getLocale: () => string;
  $t: Mock;
};

export function createFakeI18n(): MockedI18n {
  return {
    $getLocale: () => 'en-GB',
    $t: vi.fn((...args: unknown[]) =>
      args
        .map((arg) => (typeof arg === 'object' ? JSON.stringify(arg) : arg))
        .join(', ')
    )
  };
}

mockNuxtImport<() => ReturnType<typeof createFakeI18n>>('useI18n', () =>
  vi.fn(() => createFakeI18n())
);

I've updated the stackblitz.
Still not sure what to do about the 404 on the json files though "/_locales/general/en-GB/data.json"

Hello, I usually test everything through Playwright, and I work with Vitest very rarely. If you could write a couple of simple tests, I will try to prepare a set of test utilities or simply reconfigure the project for testing.

Sure, here are a few exmaples of different ways I've used vitest before:
https://stackblitz.com/edit/github-mag9gj-h2v1xa?file=app%2Fcomponents%2FTestComponent.nuxt.spec.ts

wow you are on fire! Thank you so much! I'll test it later this afternoon.
Side note, the new docs contain my example but my excludes config is very specific to my setup so we might want to reduce that to avoid confusing others:
export default defineVitestConfig({
  test: {
    setupFiles: ['./tests/unit-setup.ts'],
    include: ['./**/*.spec.ts'],
  },
})

wow you are on fire! Thank you so much! I'll test it later this afternoon.
Side note, the new docs contain my example but my "excludes" config is very specific to my project so we might want to reduce that to avoid confusing others:
export default defineVitestConfig({
  test: {
    setupFiles: ['./tests/unit-setup.ts'],
    include: ['./**/*.spec.ts'],
  },
})

fixed. thx

Posted update 1.0.1, forgot that postinstall runs during installation, thanks!

Gave it a test, seems to be working great thanks. Still getting that error but it's not preventing tests from passing:

https://stackblitz.com/edit/github-mag9gj-h2v1xa?file=app%2Fcomponents%2FTestComponent.nuxt.spec.ts
run npm run test above to see the error

try v1.38.4
After deployment, it doesn't recognize import.meta.env.

yeah import.meta.env is a vite runtime/build time thing only works when running/building the app. process.env. otherwise

Thanks error isn't showing now in latest version!
I noticed this line will fatal error if undefined is accidently passed to $t()
https://github.com/s00d/nuxt-i18n-micro/blob/168f6ac1442634c96f10deca112cca308d8f6fe2/packages/core/src/translation.ts#L31
Maybe it should be:
if (translations === null || !key) {
    return null
}

fixed v1.38.5

All working great, thank you! Loving the library.


Cache Todos with pickle

This is an optimization I've been playing around. It scrapes 0.05s from the
execution speed in my case (with warm cache), so I guess it does something
right. The improvement may be bigger on different datasets.
I wonder where to store the pickle cache, storing it in vdir seems unsafe.

It scrapes 0.05s from the execution speed in my case (with warm cache)

I'm really not sure if the time difference warrant this. Do you have a very very small test vdir? I think that skipping non-VTODO entries by caching them as well might give a larger boots (since we might avoid opening dozens of irrelevant files).

I think that skipping non-VTODO entries by caching them as well might give a larger boost (since we might avoid opening dozens of irrelevant files).

I tried that one as well. It doesn't have any effect. The conditional that checks whether \nBEGIN:VTODO is contained in the file helps massively though.

I fixed a bug where it didn't store entries for non-VTODO files.

Ok now it scrapes 0.12s from time todo list

Nice. Skipping non-VTODO files is a massive difference.

LGTM, feel free to merge this.


feat: fix core contracts storage check

Resolves #972

No storage updates, CI passing

here

Storage update, no collision, CI passing

here

Storage update, collision, CI failing

here

New contract added, CI passing

here


Added slugs per cubic foot to density

I hope I'm doing this right!

You need to close the solution, then run generate-code.bat, then edit DensityTests.cs to implement values for the new test case.

If you missed it, there is a section on https://github.com/anjdreas/UnitsNet#want-to-contribute

Thanks!  I knew I had seen that somewhere a long time ago, but couldn’t quickly find it today.  PEBKAC  ☺
Brad.
From: Andreas Gullberg Larsen<EMAIL_ADDRESS>Sent: March 8, 2017 12:22 PM
To: anjdreas/UnitsNet<EMAIL_ADDRESS>Cc: PLETT, Bradley (BETA-Machinery<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [anjdreas/UnitsNet] Added slugs per cubic foot to density (#235)
If you missed it, there is a section on https://github.com/anjdreas/UnitsNet#want-to-contributehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_anjdreas_UnitsNet-23want-2Dto-2Dcontribute&d=DwMCaQ&c=TIOfIC5RJMrWnrHy3gMA_uzZorHPsT2JAZ4ovvKrwfU&r=u5DmgK0C1bkj2a_NV6Bn53eSTjnbMtLo2GL9v-DT7aU&m=_Uxu48ISByeR8cVMSi4rAYbY0JLjrIVd6anYOnVo1cU&s=jCBHC2ozAcfvf_p0OtmBgXvAJPCeyo-UWzkIjh7Bzz0&e=
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_anjdreas_UnitsNet_pull_235-23issuecomment-2D285140637&d=DwMCaQ&c=TIOfIC5RJMrWnrHy3gMA_uzZorHPsT2JAZ4ovvKrwfU&r=u5DmgK0C1bkj2a_NV6Bn53eSTjnbMtLo2GL9v-DT7aU&m=_Uxu48ISByeR8cVMSi4rAYbY0JLjrIVd6anYOnVo1cU&s=T6dYntqooeqxrDAfYX-x8rkiqQOmAgOEW8pnPJb3YO8&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AK7pcYaZoyIRVia4maEIR8seG3KFB-2DXrks5rjv-2D-2DgaJpZM4MXLK6&d=DwMCaQ&c=TIOfIC5RJMrWnrHy3gMA_uzZorHPsT2JAZ4ovvKrwfU&r=u5DmgK0C1bkj2a_NV6Bn53eSTjnbMtLo2GL9v-DT7aU&m=_Uxu48ISByeR8cVMSi4rAYbY0JLjrIVd6anYOnVo1cU&s=uf2YcjYanOENiHB_LP4eQbNoVtpr--S_jJbXn7HPF50&e=.
Please consider the environment before printing this email.
This email and its attachments may contain information which is confidential and/or legally privileged. If you are not the intended recipient of this e-mail please notify the sender immediately by e-mail and delete this e-mail and its attachments from your computer and IT systems. You must not copy, re-transmit, use or disclose (other than to the sender) the existence or contents of this e-mail or its attachments or permit anyone else to do so.

OK, I think I've completed everything requested.  Do I need to close this pull request and open a new one, or what happens next?

Next up is for me to release nuget, will do later today.

COOL!!!  Thanks a lot!

Nuget 3.53 is now out


Job update fails with error (Exec[reload-jenkins] not in catalog)

Hi!
I pulled the latest source today and now I get the following error:
"""
Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid relationship: Exec[jenkins update-job puppet] { notify => Exec[reload-jenkins] }, because Exec[reload-jenkins] doesn't seem to be in the catalog
"""
A bug or a misconfiguration on my side?

This is likely a regression caused by.  https://github.com/jenkinsci/puppet-jenkins/commit/979cb012c12bc80306a88465f8cd78f43b32f70d  Do you have class { 'jenkins': cli => false }`?

I have no ::cli stuff defined at all :-/
Shall I try to define it? Earliest tomorrow...

Adding cli => true to my jenkins class resolved the error!
So maybe you want to add this as a default and not allow disabling it!?

I suspect that jenkins::cli needs to include jenkins::cli::reload to fix the regression.  I'll need to do some testing to make sure that doesn't reintroduce the dependency loop for jenkins::cli::exec that commit resolved.

this change broke my CD. fix: sed -i 's/include\ jenkins::cli/include\ jenkins::cli\ninclude\ jenkins::cli::reload/' /etc/puppet/modules/jenkins/manifests/job/present.pp

@ofalk / @nand0p It turns out there are multiple issues here.

This module implements "the anchor" pattern for resource ordering which is not  enabled for usage of the "cli" unless class { 'jenkins': cli => true }.  As the module is currently designed, it should really disallow the usage of any class/define that uses the cli.  We need to try to support the defacto API but a breaking change will likely be needed to fix this properly.
Even if cli => true, the defined types are not safely ordered not are they contained but the Anchor[jenkins::end] resource.
Due to \1, none of the unit tests inspect resource ordering
There are no acceptance tests that cover any of the defined types.

I have attempted to fix the inclusion problem reported in this issue, fix \2 which I just described, and add a simple acceptance test for jenkins::job.  That later appears to be non-idempotent with jenkins 1.1613.
It would be fantastic if either of you would be willing to contribute acceptance tests for the other interface classes and types.
@rtyler #298 should fix this issue, so there's likely some urgency to get a patch release out, but I'd advise careful review for fear of introducing new ordering problems.

#298 has been merged -- is this issue still present?


argo-server manifest missing --secure flag cause ReadinessProbe handshake failed

Summary
According to #5228 , argo-server deployment enable HTTPS probe by default, but does not specify --secure options in args. This cause readiness probe failed with tls: first record does not look like a TLS handshake, deployment argo-server keeps unhealthy.
Diagnostics
What version of Argo Workflows are you running?
v3.0.0-rc6
Readiness probe failed: Get https://xx.xxx.xxx.xxx:2746/: tls: first record does not look like a TLS handshake

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

already fix in #5212 , but not in v3.0.0-rc6, will this pr be picked in next rc? @alexec

#5409


🚀 | "next_song" performing no action when no next song is available

Feature
I would like the next_song GPIO button to do nothing, when there is no next song available (last track of a folder or single track without any folder). Currently this will stop the playback.
User perspective
I imagine my (very young) child will pretty randomly press all of the available buttons, so this behaviour would be better suited.
Further information
using Jukebox Core Version 3.5.2

Good feature request. It would be great if that above is the standard behavior

I think this is what the following PR is trying to solve?!

#2326

Hrm, the linked PR will behave in the following way:

When the last song of a playlist is being played and next() is called, the default will be to stop playing (this is configurable).
When the player is stopped (e.g. because the last song of a playlist finished) and the next() is called, the player will rewind the playlist (i.e. it will start playing the first song of the playlist again).

@IgorWalton Is that what you're after? If not, we would have to make (2) configurable as well.

I personally would prefer if the default is "no action" in this situation
The way I think would make the most sense is during a stop in the middle of a track "next" jumps to the next track in the current playlist, and at the end of a playlist it there's either "no action" or "start playing the first song of the playlist"
I don't have the developer perspective (yet), so just 2 Cents from a User's perspective...

As #2326 seems to be merged soonish, I can prepare another PR to add the no action behavior for (1).
Regarding (2), this can certainly be implemented as well. I was a bit hesitant to make this configurable, because every option adds code and config complexity, but I guess it's worth it if there are people who want to use it like that. :)

You can still add it, if you want

I personally would prefer if the default is "no action" in this situation

#2326 should now technically cover this.

The way I think would make the most sense is during a stop in the middle of a track "next" jumps to the next track in the current playlist

Done.

at the end of a playlist it there's either "no action" or "start playing the first song of the playlist"

This should now behave similar to the case when running next() while playling the last song of the playlist (= it's configurable).

#2326 has been merged to future3/develop


tippecanoe: 2.70.0 -> 2.72.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/felt/tippecanoe/releases.
meta.description for tippecanoe is: Build vector tilesets from large collections of GeoJSON features
meta.homepage for tippecanoe is: https://github.com/felt/tippecanoe
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.72.0 in filename of file in /nix/store/7injgingv5rfz11rvdqnya0g1k3g6bva-tippecanoe-2.72.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

tippecanoe

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/7injgingv5rfz11rvdqnya0g1k3g6bva-tippecanoe-2.72.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A tippecanoe https://github.com/r-ryantm/nixpkgs/archive/cc0941133bb27566c97a53032bc5803bc2fac6c8.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/cc0941133bb27566c97a53032bc5803bc2fac6c8#tippecanoe

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/7injgingv5rfz11rvdqnya0g1k3g6bva-tippecanoe-2.72.0
ls -la /nix/store/7injgingv5rfz11rvdqnya0g1k3g6bva-tippecanoe-2.72.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

tippecanoe

Maintainer pings
cc @autra @imincik @l0b0 @nh2 @nialov @sikmir @willcohen for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 363522

x86_64-darwin

:white_check_mark: 1 package built:

tippecanoe


543/Test cleanup

Issue Number: 543
Summary
Cleanup up our tests of "test" prefix and consolidated some tests into test cases.
Changes

Removed "test" prefix from tests
Consolidated some tests in test cases
improved some test names
Ran code coverage to analyze if we were missing any tests

Checklist

[ ] Local Tests Passing?
[ ] CICD and Pipeline Tests Passing?
[ ] Added any new Tests?
[ ] Documentation Updates Made?
[ ] Are there any API Changes? If yes, please describe below.
[ ] This is not a breaking change. If it is, please describe it below.

Are there API Changes?
If yes, what are the expected API Changes? Please link to an API-Comparison workflow with the API Diff.
Is this a breaking change?
If yes, what workflow does this break?
Anything else?
Other comments, collaborators, etc.
This PR Closes Issue #

Codecov Report

Merging #148 (f6449b8) into dev (bb79dcb) will increase coverage by 0.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #148      +/-   ##
==========================================
+ Coverage   85.73%   85.85%   +0.11%
==========================================
  Files          52       52
  Lines        1711     1711
  Branches      194      194
==========================================
+ Hits         1467     1469       +2
+ Misses        191      189       -2
  Partials       53       53

Impacted Files
Coverage Δ

src/CarbonAware/src/Model/EmissionsData.cs
75.00% <0.00%> (-12.50%)
:arrow_down:

...e.LocationSources.Azure/src/AzureLocationSource.cs
78.12% <0.00%> (+4.68%)
:arrow_up:

In going through these tests I also noticed some swaths we don't have tests. That may be intentional but figured I'd note them here.

Web API filter for swagger doesn't have tests - not sure if it's something that is testable @bderusha? I remember we went through this in our PR for params
CLI Extensions Exception Handler code - I imagined this is something that could maybe be grabbed by upcoming CLI integration tests @bderusha / @pritipath ?
CarbonAwareCore - This is actually not called by anything anymore since the CLI got updated to point to the new code. Do we just want to delete this file and its tests @gfmatthews?
Validate function on WattTimeClientConfiguration isn't called by anything anymore - maybe this is a ghost validation left over or was it unintentionally unhooked from something @bderusha ?

Closing for now, will re-open to point to gsf dev when time is right


File paths not resolving correctly in extract_frames_ldm_ff++.py

In  extract_frames_ldm_ff++.py the default parameter for the variable NUM_FRAMES is 1. In this case there is no problem, in terms of corresponding frames, if only one frame is taken from each video, for a given fake video, its frame 0 will correspond perfectly with its source video frame 0. The problem comes when NUM_FRAMES is not 1. Let's consider NUM_FRAMES = 30. In this case, according to this code the frame index that will be taken will follow a linear distribution so if there are 300 frames and 30 frame are desired, frames 0,10,20,...,290,300 are taken. This is a problem since source videos and fake videos don't always have the same length so ifi 30 frames are desired for video fake A, frames 0,10,20,30,...300 are taken but if video source B has, for example 270 frames, then frames 0,9,18,27,37...270 will be taken. It is a small detail and to some extent is not even a problem because the frames will be very similar but the source paths are not entirely accurate.

Same Problem, have you solved it?


Mobile: dark theme: white border top

There seems to be a white border on top when the dark theme is active.

Only seems to happen when scrolling back and forth on Firefox on Android.
No issues using Chrome


Running configure_shc_captain.yml multiple times yields different results

Ansible tasks should be idempotent. If the search head cluster already had a captain this task should be able to figure that out and skip.

Need to run the show shcluster-status command and if captain already elected do not run the init captain command again.

That is what I do now
- name: Check If Captain is Already Elected
  hosts:
    - shc
  run_once: true
  tasks:
  - name: Get SHC Captain Status
    shell: "/opt/splunk/bin/splunk show shcluster-status -auth {{ splunk_admin_username }}:{{ splunk_admin_password }} | grep label | head -n1 | cut -d ':' -f2 | xargs"
    become: true
    become_user: "{{ splunk_nix_user }}"
    register: shc_response
    no_log: false
    until: shc_response.stdout != "" and shc_response.rc == 0
    retries: 10
    delay: 5
    ignore_errors: yes
  - name: Setting SHC Captain Fact
    set_fact:
      shc_captain: "{{ shc_response.stdout }}"

It could take a few minutes after restart for this to detect if a captain has been elected already.

Yeah I also ran into timing issues with that. I ended up checking if server.conf shclustering has the id option using btools to work out if the bootstrap captain command is already run.


Replaced boost::launch::async continuation with thread pool based continuation

Replaced boost::launch::async continuation with thread pool based continuation. The boost::basic_thread_pool by default uses thread_count = thread::hardware_concurrency()+1 as the number of executing threads, hence it will try utilize all the cpus available.
fixes https://github.com/hazelcast/hazelcast-cpp-client/issues/764

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test PASSed.

Linux test PASSed.

Windows test FAILed.

Windows test FAILed.

Linux test FAILed.

Linux test FAILed.

Windows test FAILed.

Windows test FAILed.

Linux test PASSed.

Linux test PASSed.

Windows test PASSed.

Windows test PASSed.


mfaLockExpire

Anyway around this like this: https://github.com/albertogeniola/meross-homeassistant/issues/510#issuecomment-2309001414

You can look at my fork. I tired to make some improvements to get rid of warnings and build errors but at the moment the container keeps crashing because of s6-test

Hi,
last version (alpha50) should have this fixed. Can you please test it and report back?

Yes, everything seems like it's working as expected! Thank you!


Automatically reflect changes to SARIF files in the viewer

If a SARIF file is open in the viewer, any changes to that file should be automatically reflected.
Scenario:

Static analysis run produces a SARIF file; SARIF Viewer is opened
After fixing some of the issues, the static analysis tool is run again and updates/overwrites the existing SARIF file

Expected behavior: the SARIF viewer automatically reflects the changes in the file.
Actual behavior: nothing changes :(.

Hi @jeffersonking, is this something you think you'll get to soon or would you like us to send a PR instead?

This is already released. If you're using the APIs to open SARIF files programmatically, you should see those files update automatically. If not, please open a new issue!


Dump/Load nested SDBs in JSON format

foo=bar
cow=123
low={"pop":123,"jiji":456}

will be dumped as:
{"foo":"bar","cow":123,"low":{"pop":123,"jiji",456}}

The nested Sdbs thing should be discussed

Looks good to me


unable to parse url having multiple question mark (?)

I have a URL, and if the user is not logged in, I store that URL in query param.
Here is how the URL looks like
http://localhost:3000/?redirectTo=https://devs-homed.mart.xyz/new-project?type=badminton&code=pitchford&sessionExpired=true
const url = http://localhost:3000/?redirectTo=https://devs-homed.mart.xyz/new-project?type=badminton&code=pitchford&sessionExpired=true

const { redirectTo } = query.parse(url);

console.log(redirectTo)
Output => https://devs-homed.mart.xyz/new-project?type=badminton

Expected => https://devs-homed.mart.xyz/new-project?type=badminton&code=pitchford&sessionExpired=true

How can I get the expected output?
I know this issue is because there is multiple question mark (?) in the URL any way I can solve this issue?

You have to encode https://devs-homed.mart.xyz/new-project?type=badminton&code=pitchford&sessionExpired=true using encodeURIComponent.


Running on an embedded platform

May I ask, what is the average processing time for an image on an embedded platform? I spent about 700 milliseconds on Nvidia Orin nx

tensorrt ？


Translation to SCASP

To test, run for instance:
stack run l4 scasp l4/cr.l4
stack run l4 all -- l4/rps.l4


Something wrong with #2670

Environment:

Cython 0.29.1
Python 3.7, 3.6
OS: Windows 10
Compiler: GCC 8.1.0, 7.3.0
Language mode: c++

The changes of 55861ed7698382af7799013466cfbb2bae08b97d caused an error:
#if CYTHON_USE_PYLONG_INTERNALS
  #include "longintrepr.h"
  #undef SHIFT
  #undef BASE
  #undef MASK
  #ifdef SIZEOF_VOID_P
    enum { __pyx_check_sizeof_voidp = 1/(SIZEOF_VOID_P == sizeof(void*)) };
  #endif
#endif

src\xxx.cpp:201:40: warning: division by zero [-Wdiv-by-zero]
     enum { __pyx_check_sizeof_voidp = 1/(SIZEOF_VOID_P == sizeof(void*)) };
                                       ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src\xxx.cpp:201:72: error: division by zero is not a constant expression
     enum { __pyx_check_sizeof_voidp = 1/(SIZEOF_VOID_P == sizeof(void*)) };
                                                                        ^
src\xxx.cpp:201:40: error: '(1 / 0)' is not a constant expression
     enum { __pyx_check_sizeof_voidp = 1/(SIZEOF_VOID_P == sizeof(void*)) };
                                       ~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src\xxx.cpp:201:72: error: enumerator value for '__pyx_check_sizeof_voidp' is not an integer constant
     enum { __pyx_check_sizeof_voidp = 1/(SIZEOF_VOID_P == sizeof(void*)) };
                                                                        ^

Yep, detecting these problems is exactly what this code is there for. Your build environment is broken. See #2670, specifically https://github.com/cython/cython/issues/2670#issuecomment-432212671.


(PA-7959) Fix apache2 dependent package list in service test

On SLES, the apache2-worker package is not a dependency of apache2, and
so doesn't get installed at the start of this test. Our new Power8
platform is based on SLES 12 SP2 and now causes zypper to return a
non-zero error when you explicitly try to uninstall a package that is
not already installed, which fails this test without this fix.

CLA signed by all contributors.

👍


change settings freezes the connection

If i change some settings, i have to restart Pokemon Bot Visualizer cause it cant regrab the position data

Which bot are you using ? necro or mobbot ?
Which version ? Compiled or from the source ?

latest necrobotvisualizer seems to fixed it.


Fix incorrect redirection for "PersistentVolumes" in "Running ZooKeeper"  tutorial

Incorrect link redirection in "Running ZooKeeper" tutorial page for "PersistentVolumes" #44378

This is a fix for issue https://github.com/kubernetes/website/issues/44378
(Would be nice to include it in the description of the PR (here))
/retitle Fix incorrect redirection for "PersistentVolumes" in "Running ZooKeeper"  tutorial

/assign @nate-double-u for approval

Hey @rohan-kapse , are you assigned to the issue for which you have raised this PR here?

@kumarankit999 did'nt see that 👀

Can you edit the description to change the reference to the issue so it is:
Closes #44378
That will properly associate this PR with the issue and make sure it is auto-resolved once this PR merges.

Sure I can do that!

/approve


redshift auto-tag owner

more generically if a resource supports tagging we want it to support auto tagging on create


Clarity on where config parameters should be defined

Spun out from discussion in https://github.com/AdoptOpenJDK/openjdk-build/pull/2125#pullrequestreview-504661752
The location for changes to config parameters is something we need to provide guidance on. I came across it when putting this section of the FAQ together as things are currently in one of three places. Which to use depends on who we want to be affected and to me knowledge we've avoided being clear on where changes should be made which has already lead to confusion in the past. Quick summary:

Location
Impact

groovy files (as per this PR)
Only when run through our jenkins pipelines

platform-specific-configurations scripts
Those using build-farm/make-adopt-build-farm.sh (inc. our pipelines) - should be stuff specific to our machines

build.sh
Anyone (including end users) who are running makejdk-any-platform.sh

So it depends what we want the last line of those to be. If it's to allow users to replicate the adopt builds with the same configuration options as us as far as possible, then I think it ought to be in build.sh but if we want it to be optional for users building it themselves then the jenkins pipelines aren't a bad choice. But we should really make it clear for new people to the project where changes should be made e.g. via an update to the FAQ.
We should discuss when to use each type, citing examples of when things should be added in each of the above three places.
I would suggest:

The platform scripts when it affects environment variables for the bulids, and including config parameters to override memory usage for our specific build machines. We do currently have things like CUDA and OpenSSL enablement for OpenJ9 in there - they could be moved into build.sh is we want to have VM specifics in there (Putting it into the groovy would result in lots more editing if they change).
The groovy scripts currently have things like dtrace and other openJ9 options such as JITserver in there (I was never a fan of putting them in here to be honest) although the argument in favour of it is that it's a clean way to add things specific to a java version or VM, however the definitions are somewhat opaque if you're not using jenkins. Perhaps we should keep these for jenkins-specific things like which tests suites to run by default and perhaps the options to differentiate normal and large heap builds and strip out everything else?
build.sh sets things like our vendor information etc. which indicates who built it, wher eto report bugs as well as separate flags for GA builds. We have things like freetype alsa, and X11 dev paths defined in there (perhaps they should be in the platform scripts). I would suggest that for maximum impact if we want adoptopenjdk consistently built in a specific way that developers can replicate most of our default configure options that impact how OpenJDK is built should be in here (or one of the scripts called form it)

Understanding where to make changes to the build scripts overall is also part of https://github.com/AdoptOpenJDK/openjdk-build/issues/957 but I'm creating this to limit scope a little to get this important issue clarified

We also had an issue open to split up our files between repos, I think that would help...

I wasn't too convinced by fragmenting like that, but regardless we'd need to decide what should be where, and documenting it would be a trivial first step (Well, deciding would be a good first step, then we can document)

I argue that the configure options set into both the build.sh and the groovy scripts should be merged into the platform scripts, and I think the scripts should then be moved under makejdk-any-platform.sh. Passing in a single flag (e.g. --use-default-config-args) could trigger them, or omitting that flag would disable them (so the scripts only use the user's config arguments).
These things are a good idea because:

There would only be one location where arguments are set, making it easier to find and change them.
Moving the platform scripts under makejdk-any-platform.sh means that a docker build using our docker images only has to clone the one repo (after we're done dividing the build repo up).
A user can launch makejdk-any-platform.sh without having to set any configure arguments, and be assured that the build config will have all the options it needs, assuming they're using one of our docker files to build in.
We can set version "ranges" for each configure argument, rather than copying the same config files for each release. This means fewer files, less code duplication, and also reduces the number of things that can go wrong when we're copying files for new releases.

When I tried to implement the build-jdk action I started from readme and used makejdk-any-platform.sh to build jdk, which means platform-specific-configurations is invisible.
I wondered if we could move files under platform-specific-configurations to be same level of build.sh so jenkins, git-hub actions, users to build jdk natively, etc., no matter what build system environments it is, could also use it? Those platform-specific-configurations are platform specific, not jenkins specific, I suppose.
Groovy scripts are jenkins specifc build scripts, which will be split to separate repo https://github.com/AdoptOpenJDK/openjdk-build/issues/1108?

Groovy jenkins parameters have been clarified in the README.md of the jenkins repo via https://github.com/AdoptOpenJDK/ci-jenkins-pipelines/pull/67. Users should now have a good sense of scope regarding what parameters are available and where new ones should be created.
I now intend on adjusting the FAQ of this (the openjdk-build) repo to clarify that jenkins specific parameters should be done over at https://github.com/AdoptOpenJDK/ci-jenkins-pipelines/pull/67 where machine based params and global params should be done in the platform files and build.sh respectively


Feature/beneficiaries support on post

It is now possible to add beneficiaries while using .post() method.

This should be added to the docs.


Merge final Sidecar debugging changes to master

PR #902 needs to be cherrypicked over to master.
PR #906 also needs merging.
PR #907 also needs merging.
This is a placeholder to remember to do that.

@johnataylor AAAHHHEEEEMMMM!!!!!!


Upgrade pinejs-client

This repo also needs the CI config change to not run both push and pr builds. I think the same is true for all other resin-io-modules repos as well.

I've added the header: true fix.
We can do the CI changes, but they're not as important for modules other than resin-sdk - the build's pretty quick anyway, and it doesn't hammer any of our real running services. Could do it regardless, but there's no much benefit, depends how much we're bothered.
If we want to do it, it's a manual change: we need to go into both the travis and the github webhooks for this repo (settings -> webhooks) and disable builds for push events. I can do that for Travis, but somebody with admin permissions on Github for this repo will need to do the repo settings.

Yeah I understand that it was the most critical in the SDK. OK let's leave
as is for now.
On Tue, Jan 3, 2017 at 8:21 PM, Tim Perry<EMAIL_ADDRESS>wrote:

I've added the header: true fix.
We can do the CI changes, but they're not as important for modules other
than resin-sdk - the build's pretty quick anyway, and it doesn't hammer any
of our real running services. Could do it regardless, but there's no much
benefit, depends how much we're bothered.
If we want to do it, it's a manual change: we need to go into both the
travis and the github webhooks for this repo (settings -> webhooks) and
disable builds for push events. I can do that for Travis, but somebody with
admin permissions on Github for this repo will need to do the repo settings.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/resin-io-modules/resin-pine/pull/26#issuecomment-270169353,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgGCLFgmB-ZrwKNg60Bct3lkBnr-CTMks5rOoOngaJpZM4LZz6F
.

--
Eugene Mirotin
Senior Frontend Engineer
site: Resin.io https://resin.io/, twitter: @resin_io
https://twitter.com/resin_io


Improve Android mouse input and restructure Android input handlers

This brings us one step closer to resolving https://github.com/ppy/osu-framework/issues/4373.
In addition to separating mouse from touch events, AndroidMouseHandler enables the following:

support for all mouse buttons (including forward and back)
support for scrolling
starting point for implementing pointer capture.

Tested on Realme 6, Android 11 (API 30) with a bluetooth mouse.
On-screen keyboard input works as expected.
Test works with:

[ ] touchpad (not required, but would be nice to test)

Test existing behaviour isn't broken for:

[ ] physical keyboard
[ ] stylus

Code looks good now. I'll try and give it a test today against touch and stylus.

Stylus and touch work as expected here 👍


added dataset mt

Is this all I need to do to add a new datatset? I then tried to use mt to create a scatter plot with mpg on the X axis and hp on the Y axis and it only showed one point in the graph. Also the show table block is not wide enough to show the whole table.

If you look at the javascript console output, it will surface parsing errors on the CSV.

Also watch out that merge branches are automatically deleted... always start a new branch

Looks good ready to merge.


Active development? What is missing for 1.0?

I would like to use a stable mixin-module. However, I can only find the PoC by Justin Fagnani and your implementation. Instead of creating yet another module, I would like to build on top of your solution. That's why I want to know, if you still actively develop the project (and plan to continue doing so) and why your package is not v1.0: what stuff is still missing?

Hi @minecrawler, sorry for the late response. It seems I'm not always getting the notifications in the Github control panel.
Anyway, development is still active in the sense that this code is intended to go into production.
The reasons it is still 0.x are:

It's not yet in production
I still have some plans to change it
There is an upcoming issue still
I always like to take it slow with moving to 1.0 so when I do publish the 1.0 version, I'm pretty sure I can keep it at that version for a while. I wouldn't want to send the wrong message to people about the status of this module.

That said, the module has some extensive tests on them that are run in the CB and I plan to add more tests whenever I change stuff, so I expect it to be relatively stable.
The upcoming issue is that currently this module checks whether the given argument is an ES6 class. This can be feature tested in ES6 compliant browsers, but is trickier with transpiled code. At the moment this module checks whether some babel specific transpiled code is present to detect if the argument is a transpiled ES6 class. However, Babel is currently optimizing their output with a loose mode that gives much compacter code (jay!), but that change will break this package. So I want to tackle that as well before going to 1.0.
About what's missing. Not much I think. This lib is very minimalistic, but should give you exactly the stuff needed to start using and building mixins in your project.
I do still have this dilemma. Currently mics has two functions: mix and is. The result of is exposes three more functions: a, an (just an alias for a), and as. My doubt is, is the fluid syntax really worth it? Maybe mics should just expose 3 functions? mix, is and as ?
What do you think?
Also, can you tell me about your ideas what you would build on top of it? I would really like it if you would want to collaborate with me on this lib.

Hi @Download , wow, that's a very detailed response, thank you a lot. I can understand if you want to take it slow with releasing version 1, so that it remains stable.
As for the Babelized-code dilemma, I do not think that it will affect me, as I mostly build Node.JS and Cordova applications, and limit the minimum versions on which my software runs. As a result, I will probably be able to use mics even though it won't work after being transpiled to <=ES5. That's an advantage for me, because I can confidently use mics while you still work on supporting that.
The point about the API, however, might be a bit problematic, since when I use mics, I do not want to change my code every time I update the lib, because for at least one of the projects, which should use mics, that would mean that I have to change 20 packages in several places.
Since I plan to use mics, I plan to collaborate with you on this lib. Only by usage, many problems and missing features can be found (which I need), so I will gladly implement them and send them upstream. However, before doing that step, I think it is important to at least decide on the API. I have no problems changing my project once or twice later on, if there are real reasons to change the API. However, how you want to style the API is entirely up to you. To answer your question, though: I don't really like fluid style. The method names tell me so little about what is going on or how I could complete the chain. I would prefer an interface like
/**
 * Mix classes
 * Any class can be transformed to a mixin (by calling `.mix()`, but can be instantiated on its own
 */
class Mics {
  /**
   * Create a mixin from a class
   * Multiple classes or mixins can be mixed into the resulting mixin
   */
  static mix(superclass, ...mixins, factory) {}

  /**
   * Check if an object was created with a certain mixin
   */
  static hasMixin(obj, mixin) {}

  /**
   * Check if an object can be used as if it was created with a certain mixin
   */
  static likeMixin(obj, mixin) {}
}

But, again, that's personal taste and you will have to decide on the actual interface. If you are not sure about it, maybe open an issue others can track and close it once you feel confident with the interface. You could also discuss different approaches there ;)
What would I build on top of it? Among commercial products, I am working on an open-source application-host, which provides certain basic features, but focuses on security, speed and scalability. I am currently in a major redesign-phase (for SHPS v5 X), in which I would like to use mixins for various purposes, like sandbox-features or preparing a central foundation for the separate modules. I think, mixins are a lot more stable than testing available methods, hence the right way to go.

Ah yes I think I see where you want to use it. As a way to implement features to compose modules/plugins with, right? That would be awesome!
SHPS looks very interesting. It's sorta sad that WordPress is still the king of the hill as far as CMS' go, even though it's actually an overgrown blogging system. Would be really cool to see it get some competition.
When I did some research for WordPress alternatives a stumbled on one system that used plugins a la WordPress, but they had this really cool thing. Instead of having to download zip files, you could actually link to a GitHub repo of a plugin and it would pick it up automatically. That was an awesome feature I think. Anyway....
I understand the concerns about the API. I don't like changing them and breaking everyone. Which is why, once we go 1.0, it should be stable. Also, I'll give you a heads-up and possibly even help you upgrading if something did break,

I don't really like fluid style.

Yes I can understand that. It sorta evolved like this from the original blog article, which uses mix(..),with(..). I already decided that I think that just always using mix(..., ..., ...) is easier, so I probably should go all the way and do the same for is..a.
I like your idea of hasMixin and likeMixin as well... But is does a bit more besides checking for mixins. It also works for regular classes and even some strings. E.g.
is(function test(){}, 'function')  // true

I have been doubting about as especially. It is pretty clear in the context is(subject).as(Type), but when it stands on it's own it's a lot less clear:
as(subject, Type)

This looks like it might be performing a conversion or cast. I know e.g. Object Pascal actually has keyword as to perform checked cast... So maybe I can use like from your suggestion:
like(subject, Type)

I think this is more clearly a test that returns a boolean.
What do you think about this export structure:
mics {
  mix,
  is,
  like,
}

I think it may be very readable like this:
import { mix, is, like } from 'mics'

var viewer = {                 // create an object with the
  look(){}                         // same interface as Looker
}
is(viewer, Looker)           // false, but
like(viewer, Looker)        // true

I like this actually. I'm a big sucker for (really) short names, but sometimes it's just not descriptive enough. I think like has better balance in that regard than as.
I can see if I can whip out an 0.6 version with this API this weekend. You can test it a bit.

Only by usage, many problems and missing features can be found

Exactly! right? Which is why it was 'stuck' at 0.5. Still working on other parts of my code so this did not yet get that testing and usage. But if you are also testing it we can move to 1.0 quicker.
Let me know what you think. Since, besides from myself, you would be the first serious user of this lib I very much value your input.

SHPS looks very interesting. It's sorta sad that WordPress is still the king of the hill as far as CMS' go, even though it's actually an overgrown blogging system. Would be really cool to see it get some competition.

I do not want to compete with Wordpress, as SHPS is not a CMS. It is a lot more fundamental and meant for real web developers, although I've been planning to add an elaborate GUI (for several years now >.<). SHPS might, however, be transformed into a CMS by plugins, which are installable on top. Btw, downloading and installing plugins should work via cli > plugin add Download/samplePlugin from npm and github, however I first have to define certain stuff about plugins and implement the dependency-module, so that it can actually interface with the sources and packages properly.
Back to topic. As for your interface proposal, I think we agree more or less on how the functionality should be exposed. So, what's left is to consolidate the API and update the unit tests. As soon as you did that, I could set up the mixin stuff on my side and give you some feedback on the feeling and if I need different functionality and edge-cases I encounter. Well, I probably made that sound too easy.
I also think that this issue is not really the right place to discuss all those things, since I only wanted to ping you to see if I can use this lib. That question has been answered, thank you! I will close this issue and open dedicated issues for better tracking.


Creating react-native project with typescript template fails.

Description
I tried to create new react-native project with typescript template.
But after running npx react-native init Sample --template react-native-template-typescript command, it failed.
React Native version:
0.63
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Run the following command in the terminal.
npx react-native init Sample --template react-native-template-typescript

Expected Results
Create a new react-native project with typescript template.
Snack, code example, screenshot, or link to a repository:
Arguments:
  /usr/local/Cellar/node/15.3.0/bin/node /usr/local/Cellar/yarn/1.22.10/libexec/bin/yarn.js add react-native-template-react-native-template-typescript

PATH:
  /Volumes/Data/WORK/devHabit/AAAAA/node_modules/.bin:/Volumes/Data/WORK/devHabit/node_modules/.bin:/Volumes/Data/WORK/node_modules/.bin:/Volumes/Data/node_modules/.bin:/Volumes/node_modules/.bin:/node_modules/.bin:/usr/local/Cellar/node/15.3.0/bin:/Volumes/Data/WORK/devHabit/node_modules/.bin:/Volumes/Data/WORK/node_modules/.bin:/Volumes/Data/node_modules/.bin:/Volumes/node_modules/.bin:/node_modules/.bin:/usr/local/lib/node_modules/npm/node_modules/@npmcli/run-script/lib/node-gyp-bin:/usr/local/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin:/Users/topmaster/Library/Android/sdk/emulator:/Users/topmaster/Library/Android/sdk/tools:/Users/topmaster/Library/Android/sdk/tools/bin:/Users/topmaster/Library/Android/sdk/platform-tools

Yarn version:
  1.22.10

Node version:
  15.3.0

Platform:
  darwin x64

Trace:
  Error: https://registry.yarnpkg.com/react-native-template-react-native-template-typescript: Not found
      at Request.params.callback [as _callback] (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:66988:18)
      at Request.self.callback (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:140749:22)
      at Request.emit (node:events:376:20)
      at Request.<anonymous> (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:141721:10)
      at Request.emit (node:events:376:20)
      at IncomingMessage.<anonymous> (/usr/local/Cellar/yarn/1.22.10/libexec/lib/cli.js:141643:12)
      at Object.onceWrapper (node:events:482:28)
      at IncomingMessage.emit (node:events:388:22)
      at endReadableNT (node:internal/streams/readable:1294:12)
      at processTicksAndRejections (node:internal/process/task_queues:80:21)

@DevHabit it's yarn bug, sometimes it can not found packages. Please try this: https://github.com/yarnpkg/yarn/issues/5865

@DevHabit it's yarn bug, sometimes it can not found packages. Please try this: yarnpkg/yarn#5865

I think so.
But as you can see from log - it is finding  react-native-template-react-native-template-typescript package.

I could clone typescript template project by using command npx react-native init <PROJECT_NAME> --template typescript

I use npx react-native init <PROJECT_NAME> --template react-native-template-typescript and it works. I think s we do not have template typescript.


Linting workflow added

Commonalities release 0.3.0 defines the linting integration guidelines for automated testing via Github actions. This PR adds the files and configuration to achieve this.

^ note the error above is the result of the linter running against the commit, i..e the linter files themselves.

I would like we get this PR merged sooner rather than later. Could we merge it?
What I see from the errors of the mega linter, most the issues are fixed by https://github.com/camaraproject/EdgeCloud/pull/222
Here a resume of the errors:

83 issues with line-length
37 issues with trailing-spaces
Some other issues:

  Error: 8:16 [colons] too many spaces after colon
  Error: 105:1 [empty-lines] too many blank lines (3 > 2)
  Warning: 375:9 [comments-indentation] comment not indented like content
  Error: 549:5 [indentation] wrong indentation: expected 6 but found 4
  Warning: 639:2 [comments-indentation] comment not indented like content
  Warning: 672:2 [comments-indentation] comment not indented like content
  Error: 743:10 [indentation] wrong indentation: expected 10 but found 9
  Error: 759:15 [indentation] wrong indentation: expected 10 but found 14
  Warning: 858:2 [comments-indentation] comment not indented like content
  Warning: 889:2 [comments-indentation] comment not indented like content
  Warning: 978:2 [comments-indentation] comment not indented like content
  Warning: 1540:2 [comments-indentation] comment not indented like content

@nicolacdnll thanks and agree - you should be able to merge the PR  (I can't merge because I created the PR)


Export Angular provider

Prerequisites

Version: 0.176.0
Are you running from source/main: no
Are you using a released build: yes

Step to reproduce
Try to import LucideIconProvider and LUCIDE_ICONS injection token from lucide-angular.
Actual behavior
Error: Module not found: Error: Package path ./lib/lucide-icon.provider is not exported from package
Notes
I have a custom directive which creates a lucide-angular icon.  I'd like to access the injected icons from the new provider.  To do that, I need the provider to be exported.

Thanks for report, yeah, these definitely should've been exported and fell victim to refactoring.
I've pushed a fix, this should be resolved in v0.177.0 in a matter of minutes as soon as the release script finishes running.


Problem Receiving data and commands from the cloud

I use ESP32-C3-AWS-EspressLink-DevKit to testing. The ExpressLink board is connect over a USB serial interface. I followed your "Getting Starde Guide https://github.com/espressif/esp-aws-expresslink-eval#6-connecting-and-interacting-with-aws-cloud".
All the steps went well, but at step "6.3 Receiving data and commands from the cloud", after entered the command: AT + GET1, I do not receive the message "OK Hello from the AWS IoT" at the console.
Could you help me to understand what did I do wrong? P.s. In attached file find our log file. Thank you
Related Files: https://www.espressif.com/sites/default/files/webform/salesquestions/log_0.txt
log.txt

Hi @claudiomas, from the log it seems you might be publishing to the wrong MQTT topic from the AWS IoT console.
Can you please confirm if you are publishing to topic: <ThingName>/MyTopic as shown below:

Another quick test that you can do, to verify if PubSub is working correctly is:
AT+CONNECT
AT+CONF Topic1=MyTopic
AT+SUBSCRIBE1
AT+SEND1 Test message
AT+GET1

You should see "OK Test message"


install path VidCod error

why install VidCod error
Get-Content : Cannot find path 'D:\Applications\Scoop\apps\vidcoder\6.41\VidCod
er.exe.config' because it does not exist.
At line:1 char:17
+ $config = [xml](Get-Content "$dir\VidCoder.exe.config")
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (D:\Applications...oder.exe.conf
   ig:String) [Get-Content], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetCo
   ntentCommand

You cannot call a method on a null-valued expression.
At line:2 char:1
+ $elem = $config.CreateElement('add')
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

You cannot call a method on a null-valued expression.
At line:3 char:1
+ $elem.SetAttribute('key', 'SettingsDirectory')
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

You cannot call a method on a null-valued expression.
At line:4 char:1
+ $elem.SetAttribute('value', "$persist_dir\home")
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

You cannot call a method on a null-valued expression.
At line:5 char:1
+ $config.configuration.appSettings.appendChild($elem) | Out-Null
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

You cannot call a method on a null-valued expression.
At line:6 char:1
+ $config.Save("$dir\VidCoder.exe.config")
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

Edit your issue to fill out the Bug Report template, or the issue will be closed.

Can reproduce the bug
scoop install vidcoder
Installing 'vidcoder' (6.44) [64bit]
Starting download with aria2 ...
Download: Download Results:
Download: gid   |stat|avg speed  |path/URI
Download: ======+====+===========+=======================================================
Download: a96dbb|OK  |   8.3MiB/s|C:/Users/Rithvij/scoop/cache/vidcoder#6.44#https_github.com_RandomEngy_VidCoder_releases_download_v6.44_VidCoder-6.44-Po
rtable.exe_dl.7z
Download: Status Legend:
Download: (OK):download completed.
Checking hash of VidCoder-6.44-Portable.exe ... ok.
Extracting dl.7z ... done.
Running pre-install script...
Get-Content: Cannot find path 'C:\Users\Rithvij\scoop\apps\vidcoder\6.44\VidCoder.exe.config' because it does not exist.
InvalidOperation:
Line |
   2 |  $elem = $config.CreateElement('add')
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | You cannot call a method on a null-valued expression.
InvalidOperation:
Line |
   3 |  $elem.SetAttribute('key', 'SettingsDirectory')
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | You cannot call a method on a null-valued expression.
InvalidOperation:
Line |
   4 |  $elem.SetAttribute('value', "$persist_dir\home")
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | You cannot call a method on a null-valued expression.
InvalidOperation:
Line |
   5 |  $config.configuration.appSettings.appendChild($elem) | Out-Null
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | You cannot call a method on a null-valued expression.
InvalidOperation:
Line |
   6 |  $config.Save("$dir\VidCoder.exe.config")
     |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | You cannot call a method on a null-valued expression.

Can you make a PR for fixing it?

No

VidCoder appears to persist its settings in a sqlite database in %APPDATA%\VidCoder.sqlite.
Is there any reason to have the pre_install or persist sections in the scoop manifest?

https://github.com/RandomEngy/VidCoder/issues/639#issuecomment-615884800

The config file that tells VidCoder to where to store the config databasefile (named VidCoder.exe.config) does not exist in the download.  What do you do in this case?  Create it?

The manifest was added in https://github.com/ScoopInstaller/Extras/pull/3057
I'm not really familiar with the software, I just searched their bug tracker for relevant links. I'd suggest opening an issue there to ask the author.

I'm not really familiar with the software

I'm the same - not really interested in VidCode so much as improving the quality of the buckets.
To me it is only a minor issue that VidCode uses the %APPDATA% folder.

@rashil2000, How this is fixed depends on how important "strict" portability is for scoop?
I'll start by saying VidCoder is not "strictly" portable. It will always create log files in the %APPDATA%\VidCoder folder.  It is not unprecedented for scoop apps to use the %APPDATA% folder.  I don't see it as an issue, but others might.  I don't think strict portability is a core philosophy of scoop.
To get VidCoder to use scoop's persist folder, it must be run using the portable version.  The portable version extracts its files to %APPDATA%\Temp\ each time it runs. It's not ideal but the config is then stored in the apps\vidcode\current folder next to the executable, which can then be persisted.
If it is acceptable for VidCoder to store its config in %APPDATA%\VidCoder, we can permanently extract the files to apps\vidcoder\current\ which would just save startup time by skipping the extraction.
@RandomEngy - did I get that right?

Portability is highly preferred, but not a strict requirement.
If an application is not able to work portably without breaking stuff, then we should avoid it. There are plenty of applications in the buckets which have no way to become portable.

@amreus you got that pretty much right. Though it extracts to %TEMP%\RarSFX0, or %LOCALAPPDATA%\Temp\RarSFX0 . That's the default behavior of the WinRar self-extracting executable.

VidCoder portable creates the config file in the same (temporary) folder as the executable. The folder is removed on VidCoder exit. I I can not think of a way to have a persistent config in scoop when using the portable executable.
So the options appear to be

Include VidCoder and allow it to use %APPDATA% to store the config file
Include VidCoder but do not have any persistent config for the user
Remove VidCoder from scoop.

So getting back to the subject of this issue which is that VidCoder doesn't install at all, I'll submit a pull request for the 1st option with a note as it seems the most reasonable compromise.

Sure, thanks


Link to try_gluon is dead

The link to try_gluon server in the readme is dead:
http://ec2-52-29-1-213.eu-central-1.compute.amazonaws.com/

Restarted the server. It went down from what looks like a segfault in the garbage collector. Will investigate.


meta: truncate trash entry name if it's too long

close #2046

Codecov Report

Merging #2049 (237ddc3) into main (4a0a55c) will decrease coverage by 0.06%.
The diff coverage is 86.66%.

@@            Coverage Diff             @@
##             main    #2049      +/-   ##
==========================================
- Coverage   61.58%   61.52%   -0.07%
==========================================
  Files         137      137
  Lines       23871    23877       +6
==========================================
- Hits        14701    14690      -11
- Misses       7452     7465      +13
- Partials     1718     1722       +4

Impacted Files
Coverage Δ

pkg/meta/interface.go
56.19% <ø> (ø)

pkg/vfs/vfs.go
77.88% <ø> (ø)

pkg/meta/sql.go
64.99% <33.33%> (-0.10%)
:arrow_down:

pkg/meta/base.go
70.00% <100.00%> (+0.28%)
:arrow_up:

pkg/meta/redis.go
71.84% <100.00%> (-0.05%)
:arrow_down:

pkg/meta/tkv.go
76.78% <100.00%> (ø)

pkg/vfs/reader.go
77.18% <0.00%> (-3.11%)
:arrow_down:

pkg/vfs/writer.go
78.64% <0.00%> (-1.02%)
:arrow_down:

... and 1 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 30cdf5c...237ddc3. Read the comment docs.


Public domain POSIX make

https://github.com/rmyorston/pdpmake

In the future, with a rewrite of GNU Make, we will have no GNU software at all.

Maybe you could send patches to pdpmake or even fork from it.

pdpmake can't build the linux kernel.

pdpmake can't build the linux kernel.

Yes. This is the reason why I said you need to send patches to the developer or even fork it. I think it's still better than writing your own implementation of gmake from scratch.

Btw, you could try to patch bmake or schilytools also has various implementations of make for you to choose.

pdpmake can't build the linux kernel.

I am seconding this and adding that pdpmake can't build a lot of things..


Convert aten.fill.Scalar to ttnn.full

Ticket
None
Problem description
Convert aten.fill.Scalar to ttnn.full. It first generates a tensor aligned to 32x32 in TILE_LAYOUT then crop the results into the required shape.
What's changed

Add conversion from aten.fill.Scalar to ttnn.full
Add a new fx.wrap function target_wrappers.getitem to crop tensor into the target shape
Test cases for the conversion

It can support non-aligned size now


common-io: Refactoring Watchdog test cases

Description

Refactored test cases to use TEST_PROTECT sections to guard against cascading failures.
Moved to a single shared bark/bite callback with separate semaphores. This allows for the status to be evaluated as part of the callback instead of waiting for the semaphore to go back.
Added a WD reset in the case of a bite interrupt, this as some devices require a reset in order to escape the interrupt.
Added global test instance variable to allow the test framework to define which WD instance to test.

Checklist:

[ ] I have tested my changes. No regression in existing tests.
[ ] My code is Linted.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/bot run checks


IDF 4.2 HTTPS Client SSL issue (IDFGH-3468)

Environment:

IDF version: ESP-IDF v4.2-dev-1660-g7d7521367 (marked as latest)
Hardware: ESP32-SOLO-1,  ESP32-S2-Wrover(Saola)
Compiler version: (crosstool-NG esp-2020r1) 8.2.0
OS: Linux
IDE: Eclipse 2020-03 (4.15.0)
SDK Config: defaults from the examples

The isuue
Running the examples "https_request" and "https_x509_bundle" on Saola and Solo ends up with the following error:
E (25843) esp-tls-mbedtls: mbedtls_ssl_handshake returned -0x7680
with meaning: No CA Chain is set, but required to operate.
Additional tests on stable IDF 4.0.1
The examples are running fine on ESP32-SOLO-1

@kotkis1 Thanks for reporting, we will look into.

Hi @kotkis1,
This issue has already been fixed on our internal repo (commit: a2d7e8cbba35a9d44f2ae833cfd12e8743511e88) and should be available here as soon as Github is synced with our internal repo.
Unfortunately there's been some issue with this lately so it's been a while since the last sync, hopefully it will happen soon!
If you want to fix it yourself before this, you can apply the following change in components/mbedtls/CMakeLists.txt:
Change: target_link_libraries(${COMPONENT_LIB} INTERFACE ${mbedtls_targets})
To: target_link_libraries(${COMPONENT_LIB} PUBLIC ${mbedtls_targets})

The fix worked, thank you.


Add bot configurations

Adds the configurations for the following bots:

dependabot
kodiak
stale

The bots will have to be enabled by an admin in order to get activated.
Fixes guacsec/guac#55
Signed-off-by: Rémy Greinhofer<EMAIL_ADDRESS>

The PR size bot will also need to be activated, but does not have any configuration.

The PR size bot will also need to be activated, but does not have any configuration.

bots enabled!