Not able to control Midea AC from home assistant.

Although I have successfully  add a card on Home assistant, I am not able to perform any actions to the A/C, i am not able to change to cool/head/fun/ or to set ON/OFF

Home Assistant version: 0.98.1

error logs
Log Details (ERROR)
Fri Aug 30 2019 11:26:34 GMT+0300 (Eastern European Summer Time)
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/core.py", line 1260, in _execute_service
await handler.func(service_call)
File "/usr/src/homeassistant/homeassistant/helpers/entity_component.py", line 210, in handle_service
self._platforms.values(), func, call, service_name, required_features
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 349, in entity_service_call
future.result()  # pop exception if have
File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 371, in _handle_service_platform_call
await getattr(entity, func)(**data)
File "/config/custom_components/midea/climate.py", line 266, in async_set_hvac_mode
await self.apply_changes()
File "/config/custom_components/midea/climate.py", line 98, in apply_changes
await self.hass.async_add_executor_job(self._device.apply)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/midea/device.py", line 168, in apply
data = self._cloud_service.appliance_transparent_send(self.id, data)
File "/usr/local/lib/python3.7/site-packages/midea/cloud.py", line 173, in appliance_transparent_send
'applianceId': id
File "/usr/local/lib/python3.7/site-packages/midea/cloud.py", line 95, in api_request
raise RecursionError()
RecursionError
Log Details (WARNING)
Fri Aug 30 2019 15:05:55 GMT+0300 (Eastern European Summer Time)
Update of climate.midea_16492674444494 is taking over 10 seconds
Log Details (ERROR)
Fri Aug 30 2019 15:05:57 GMT+0300 (Eastern European Summer Time)
Update for climate.midea_16492674444494 fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 261, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 439, in async_device_update
await self.async_update()
File "/config/custom_components/midea/climate.py", line 111, in async_update
await self.hass.async_add_executor_job(self._device.refresh)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/midea/device.py", line 146, in refresh
data = self._cloud_service.appliance_transparent_send(self.id, data)
File "/usr/local/lib/python3.7/site-packages/midea/cloud.py", line 173, in appliance_transparent_send
'applianceId': id
File "/usr/local/lib/python3.7/site-packages/midea/cloud.py", line 93, in api_request
return self.api_request(endpoint, args)
File "/usr/local/lib/python3.7/site-packages/midea/cloud.py", line 93, in api_request
return self.api_request(endpoint, args)
File "/usr/local/lib/python3.7/site-packages/midea/cloud.py", line 95, in api_request
raise RecursionError()
RecursionError
Connection lost. Reconnecting…

Confirm. I have this  error:
2019-12-20 11:30:26 ERROR (MainThread) [homeassistant.helpers.entity] Update for climate.midea_18691697719260 fails
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 281, in async_update_ha_state
await self.async_device_update()
File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 459, in async_device_update
await self.async_update()
File "/config/custom_components/midea/climate.py", line 107, in async_update
await self.hass.async_add_executor_job(self._device.apply)
File "/usr/local/lib/python3.7/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.7/site-packages/midea/device.py", line 168, in apply
data = self._cloud_service.appliance_transparent_send(self.id, data)
File "/usr/local/lib/python3.7/site-packages/midea/cloud.py", line 173, in appliance_transparent_send
'applianceId': id
File "/usr/local/lib/python3.7/site-packages/midea/cloud.py", line 95, in api_request
raise RecursionError()
RecursionError

Confirm too.
The problem was from the beginning of the project.

Same as #23, closing this one as there's more discussion there.


Choosing the best configuration after an exploration run using run_designs.py.

Prompt
In the readme file explaining the regression and exploration run: https://github.com/The-OpenROAD-Project/OpenLane/blob/master/regression_results/README.md. It was mentioned that the best configuration is chosen based on the least number of violations. In the example I've attached all of the successful runs had 0 violations so the function just chose the first successful run as the best one.
Proposal
The selection of the best design could be based first on the number of violations, if they are the same then take a look on the antenna violations (which were not taken into consideration in my case), after that if they are also equal you could look into other metrics such as the configuration that gave the least diearea, or the least physical cells. After that if all these metrics were identical you could also compare the power consumption of each configuration. In that way the process of choosing the best configurations would be much more accurate and more helpful for the user.
[reg_20_06_2022_13_13.csv]
(https://github.com/The-OpenROAD-Project/OpenLane/files/8955918/reg_20_06_2022_13_13.csv)
[reg_20_06_2022_13_13_best.csv]
(https://github.com/The-OpenROAD-Project/OpenLane/files/8955919/reg_20_06_2022_13_13_best.csv)

@ZeyadZaki
Missing make survey || python3 ./env.py issue-survey

@vijayank88 That's for issues, not enhancement proposals


Suggestion

Hi,
I have a react based webapp integrated with Django as a backend, the current challenge we are facing in file uploads like we are expecting 3-5lac file upload of average size say 5Mb each file. Currently we are implemented using celery and redis but it is not efficient to handle this much request. I wanted to know if dask queue can handle this efficiently. Can anyone please help me on this.

Hi @NonlinearNimesh ,
As I understand you have a file upload endpoint with a large number of requests of files ~5Mb. Are those files processed in a backend service using celery workers? Or do you want to scale the upload?
Dask can be used as a computational engine similar to Celery, but while still maintaining a high degree of concurrency and not blocking needlessly. You can start a dask cluster with queuepool and consumerpool and connect to it using a dask async client in your routes. Take a look at this:
https://distributed.dask.org/en/stable/asynchronous.html

Thanks for the response @AmineDiro

Are those files processed in a backend service using celery workers
==> Yes, we take the file and return to the front end that "file upload successfully" and then there are 8-9 task (which include DB operation, conversion, etc.) that is done in the backend. We are using 4 workers but I have seen that queue getting blocked the moment it receives a file over than a threshold (currently I don't know the exact number of file uploads).  So i am guessing this is also a scaling problem. So to answer your 2nd Question, Yes we want to scale the upload also.

Also, one more problem that exists is let's say I gave a request of 500 files to upload and you have given 5 after me. So you have to wait till my 500 uploads are finished. This cant happen. Do you think scaling can solve this problem?

Ok I see, queues are used to offload some processing-heavy workload in the background and return a waiting result for the user. In my opinion, uploading files doesn't fit this pattern. You should block the user until the whole file is uploaded. You should just horizontally scale your uploading API and use multi-part upload with async capability. Hope this is useful 😸 !

Noted, Thanks


fix: sometimes can not render new table content when scrolling in h5 …

…close #985
👀 PR includes

✨ Feature

[ ] New feature

🎨 Enhance

[ ] Code style optimization
[ ] Refactoring
[ ] Change the UI
[ ] Improve the performance
[ ] Type optimization

🐛 Bugfix

[ ] Solve the issue and close #0

🔧 Chore

[ ] Test case
[ ] Docs / demos update
[ ] CI / workflow
[ ] Release version
[ ] Other ()

📝 Description
尝试修复mobile端表画布内容滚动不流畅，统一mobile和pc端表滚动逻辑
🖼 Screenshot

Before
After

❌
✅

🔗 Related issue link

🔍 Self Check before Merge

[ ] Add or update relevant Docs.
[ ] Add or update relevant Demos.
[ ] Add or update relevant TypeScript definitions.

麻烦完善一下 pr 描述

ping @bobby-ai


Running trimmomatic with example code

I had some trouble running the example trimmomatic code but realized (eventually) that there were some typos. Posting here in case anyone had similar issues:
#ID
ID=PM6-S
#Values for R1 and R2:
R1=${indir}/${ID}_R1.fastq
R2=${indir}/${ID}_R2.fastq
Lastly, I had to create a /summary_files directory in the outdir location in order for the code to run correctly.

thank you! i think i have updated the markdown.


Duplicate deregister in Nested Object GC

What happened:
When performing garbage collection (GC) on nested objects, the deregister process leads to redundant operations on child nodes. This issue arises because the deregister iterates over children, while getDescendants also performs a similar traversal, resulting in unnecessary duplication.
https://github.com/yorkie-team/yorkie-js-sdk/blob/a714e662ebfcfd6c2080ac8c67ea0ebd7d306699/src/document/crdt/root.ts#L168-L191
https://github.com/yorkie-team/yorkie-js-sdk/blob/a714e662ebfcfd6c2080ac8c67ea0ebd7d306699/src/document/crdt/object.ts#L215-L231
What you expected to happen:
Garbage collection should efficiently iterate over children only once, deregistering them, and returning the accurate count of garbage-collected nodes.
How to reproduce it (as minimally and precisely as possible):
Execute the following test code:
it.only('test', async function ({ task }) {
  type TestDoc = { shape?: { point?: { x?: number; y?: number } } };
  const docKey = toDocKey(`${task.name}-${new Date().getTime()}`);
  const doc = new yorkie.Document<TestDoc>(docKey);

  doc.update((root) => {
    root.shape = { point: { x: 0, y: 0 } };
    delete root.shape;
  });
  assert.equal(doc.getGarbageLen(), 4); // shape, point, x, y
  assert.equal(doc.garbageCollect(MaxTimeTicket), 4); // The number of GC nodes must also be 4. (It's 6 for now.)
});

Anything else we need to know?:
This issue was reported in #714 .
The deregisterElements logic has been modified in #691 .
Environment:

Operating system:
Browser and version:
Yorkie version (use yorkie version): v0.4.11
Yorkie JS SDK version: v0.4.11

I'll give it a try 😀

sure :)

@chacha912
It looks like the issue has been resolved. The provided test code has already been added to gc_test.ts, and it returns the expected result of 4.

@gwbaik9717 Thank you for confirming. We close issues labeled with sdk ⚒ once they've been implemented across all SDKs: Go, JS, Android, and iOS.
The current issue involves a bug fix related to changes in the deregisterElements logic, which occurred when improving the ability to set and add nested elements(#691). This bug fix has already been applied to the JS and Go SDKs.

[x] js: https://github.com/yorkie-team/yorkie-js-sdk/pull/716
[x] go: https://github.com/yorkie-team/yorkie/pull/756

However, for the Android and iOS SDKs, the improvement to set and add nested elements hasn't been implemented yet. Therefore, it might be better to address this bug fix later when we work on that enhancement for these platforms.


Syntax Errors while running the script in termux

Hi,
I cloned the script in termux and while running in mobile I am getting error that in print statement parantheses missing.
Steps I followed :

git clone https://github.com/faizann24/XssPy
python XssPy.py google.com

You are running through python 3 whereas this script is made with python 2
Use docker as a workaround !


Lower iPhone camera position leads to bad result

Hi,
Thanks for your great work!
I have a problem that when I attach my iPhone to my tool car (remote control), which the height of iPhone camera position is 5 cm with respect to the ground, neural recon gives me a bad result. But if I hold my iPhone in hand (height is 1.5m) and sample the same place, the result is great. Do I need to modify something in data preprocessing or something else?
Thank you!

5cm to the ground is too far away from the poses in the training data. You will have to train the network with similar data in order to make it work.


UI Components

Impelmentierung der folgenden UI Components + Storybook:

[x] Button
[x] ButtonLink
[ ] LinkButton (tbd)
[x] TextField
[ ] Disclosure
[ ] Treeview (?)
[x] Popover
[ ] Modal dialog
[ ] Combobox
[ ] Select
[ ] Multiselect
[ ] Radiobutton
[ ] Checkbox
[ ] Tabs
[x] Toast: https://react-hot-toast.com/
[ ] Splitter (Allotment)
[ ] Label

Colors:

Primary

(Secondary)

Accent

Muted

Error/Warning/Success

New Intavia UI components using radix-ui and other libraries: https://github.com/InTaVia/ui


Provide a "finding the right documentation" tutorial

Documentation can be a minefield for newcomers - a section with useful links and guidance on which documentation to follow and where to find it would be useful.

*Such as where to find pyspark documentation

No longer needed


Use BroadcastReceiver to update app list

Update app list when a new app is installed by listening to ACTION_PACKAGE_ADDED

Instead of querying package manager randomly, query once a day (or something) and use BroadcastReceiver to listen for app installs and uninstalls?
https://stackoverflow.com/questions/17674439/android-difference-between-action-package-fully-removed-and-action-package-remo

Better solution to use LauncherApps


Tips and advice are not available in VUE3

Volar does not have reacttive Ref Watch useRoute related tips and import
https://user-images.githubusercontent.com/20943608/183295784-6831f7e6-9805-4a94-853a-ae3d119881a8.mp4

Can we do it like Vetur

@jahnli try to installing version v0.37.2 , I guess its bug and at this version it works well

I adjusted the version to 0.37.2, but I still couldn't get the router and Watch suggestions

probably the best course is to stick with Volar v0.39.5 and wait for new release after v0.40.1

Not fixed in v0.40.1 @sadeghbarati

@johnsoncodehk

Do you have disable / enable typescript.suggest.autoImports VSCode setting?

@johnsoncodehk I have similiar issues and have both for typescript and normal javascript enabled autoimports, should that be turned off?

If v1.0 still not working, please try re-install VSCode. (Yes this is weird, but someone actually got fix after do this)


Bug when searching for alphanumeric characters or words with dashes

Hello again,
This is a great repository, and as I'm starting to use it more widely, I've noticed some further bugs.
If a word is made up by both letters AND numbers, the autocomplete stops working after we hit our first different (letter vs. number) character. See example below with item "012345abc678".
Attempt 1: searching only initial numbers
from fast_autocomplete import AutoComplete
words = {'012345abc678': {}}
autocomplete = AutoComplete(words=words)
print(autocomplete.search(word='012345'))

Result is [['012345abc678']] as expected.
Attempt 2: searching numbers and first letter
print(autocomplete.search(word='012345a'))

Result is still [['012345abc678']] as expected.
Attempt 3: going further into the item and including the first two letters
print(autocomplete.search(word='012345ab'))

Result is []. Everything has disappeared.
Moreover, if I instead put spaces into the original word and do the search without spaces, then it works fine
from fast_autocomplete import AutoComplete
words = {'012345 abc 678': {}}
autocomplete = AutoComplete(words=words)
print(autocomplete.search(word='012345ab'))

returns [['012345 abc 678']]. Is this a bug that you would be able to fix?
I have also noticed a similar problem with hyphenated words (I suspect the issues might be related so I'm putting them in a single bug report). Take the example of "user-generated content". See behaviour below
Attempt 1: search up to the hyphen but excluding it
from fast_autocomplete import AutoComplete
words = {'user-generated content': {}}
autocomplete = AutoComplete(words=words)
print(autocomplete.search(word='user'))

Result is [['user-generated content']] as expected.
Attempt 2: search one letter past the hyphen
print(autocomplete.search(word='user-g'))

Result is still [['user-generated content']] as expected.
Attempt 3: search two letters past hyphen
print(autocomplete.search(word='user-ge'))

Result is []. Everything has disappeared.
Following a similar behaviour to alphanumeric characters, if I remove the hyphen from the indexed words but keep the hyphen in the search, then it works fine, see below
from fast_autocomplete import AutoComplete
words = {'user generated content': {}}
autocomplete = AutoComplete(words=words)
print(autocomplete.search(word='user-ge'))

returns [['user generated content']]
I would be grateful if you could confirm if this is a bug or a known issue / behaviour and if there are any plans to fix it.
Many thanks

i have similar issue with brackets:
from fast_autocomplete import AutoComplete
words = {'user content (2 off)': {}}
autocomplete = AutoComplete(words=words)
print(autocomplete.search(word='user content (2 o'))
returns nothing

Regarding things like dashes and brackets, you should tell autocomplete to accept those characters: https://github.com/seperman/fast-autocomplete#unicode
I should update the doc so it is clear it is not just unicode and it includes special characters.
Autocomplete does put a space between alphabets and numbers by design as a part of normalization. That was because it could handle user inputs like “bmw3series” better. You could put back the original word in the context dictionary.
Im typing this on my phone. If the above doesn’t help, please let me know and I will look into it further.
Sep Dehpour

On Jul 7, 2021, at 10:42 PM, sataz-ehl @.***> wrote:

i have similar issue with brackets:
from fast_autocomplete import AutoComplete
words = {'user content (2 off)': {}}
autocomplete = AutoComplete(words=words)
print(autocomplete.search(word='user content (2 o'))
returns nothing
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi seperman, thanks for your reply.
I tried the following and the issue persists.
from fast_autocomplete import AutoComplete
import string
words = {'user content (2 off)': {}}
valid_chars = string.ascii_letters + string.punctuation
valid_chars_num = string.digits
autocomplete = AutoComplete(words=words, valid_chars_for_string=valid_chars, valid_chars_for_integer=valid_chars_num)
autocomplete.search(word='user content (2 o')
returns nothing
Appreciate if you could take a look. Maybe I still miss out something.
Thank you!
EH

@seperman I can confirm what @sataz-ehl said, this doesn't seem to make a difference to me either.
Example 1:
import string
from fast_autocomplete import AutoComplete
words = {'abcd(efgh)ijk': {}}
autocomplete = AutoComplete(words=words, valid_chars_for_string=string.ascii_letters+string.punctuation)
print(autocomplete.search(word='abcd(efgh)'))

returns []
Example 2:
import string
from fast_autocomplete import AutoComplete
words = {'0123(45)': {}}
autocomplete = AutoComplete(words=words, valid_chars_for_integer=string.digits)
print(autocomplete.search(word='0123(4'))

also returns []
It would be great if you could take a look into it, just in case we're missing on something.
Thanks a lot!

Sorry for the long delay. This is a bug. Let me fix it now.


v3.0 Unable to disable read-only _users database with the "users_db_security_editable" option

Description
When I set "users_db_security_editable" to true, I still get an error message when editing the permissions in _users.
Steps to Reproduce

Go to the config page (http://localhost:5984/_utils/#_config/couchdb@localhost)
Set "users_db_security_editable" to true
Go to the permissions in the _users database (http://localhost:5984/_utils/#/database/_users/permissions)
Remove the _admin role
See the "Could not update permissions - reason: Error: You can't edit the security object of the user database" at the top of the page

Expected Behaviour
I expect to be able to remove the _admin role from the members. I want to be able to allow anybody to sign up to my app without exposing the admin password to the user.
Your Environment

CouchDB version used: 3.0
Browser name and version: Chrome 79.0.3945.130
Operating system and version: Mac OS

Hi @danielbarbarito thanks for the report.
This looks like a bug in default.ini, because the setting has been put into the [purge]  section when it should be in the [couchdb] section. Your PR is changing things the wrong way; this was never meant to be in purge.
Can you please try adding the following text to your local.ini file, then restarting CouchDB and test if you can edit the _users DB permissions?
[couchdb]
users_db_security_editable = true

If that works, would you submit a new PR that moves the setting line into the [couchdb] section of the default.ini section?

@wohali That worked! Just submitted a new PR.

PR is merged.


[ios] mapReady called with default map values rather than given properties

Description
On iOS the map is initialized within the constructor of MapView, which causes mapReady to be called with the default values defined in map-view.common.ts and not the properties provided in template.
For me it caused a problem with Google Maps iOS Utils, rendering clusters with zoom level 0, and then render the clusters with the provided zoom level of 9.
Reproduce

Download this repo
Get the demo app running on iOS (did not try in demo-vue)
In demo/app/main-page.js add this: console.log("What is zoom really? ", mapView.zoom);. just below mapView = args.object; in function onMapReady(args) {...}
Check the console on map initialization - the value is 0.

Example code in demo/app/main-page.js:
var mapView = null;

function onMapReady(args) {
    mapView = args.object;
    console.log("What is zoom really? ", mapView.zoom);

    // ... Rest of impl.
}

Output: What is zoom really? 0
Solution
Change the initialization to use NativeScripts view lifecycle - like in the android implementation.
createNativeView() {...}
initNativeView() {...}
I have a PR ready in few minutes.

Hello,
feel free to try this and give feedback on any bugs :
https://github.com/j20mc/Nativescript-Danem-Google-Maps-Utils#readme
IOS and Android support


Fixed some typos in the readme

Found some typos while reading the readme, might as well fix them eh? :)

Thanks!


USHIFT-946: remove obsolete topolvm role manifests

Remove role and rolebinding manifests that are no longer part of the
TopoLVM deployment.
/assign @copejon

Verified the manifests are no longer included in the operator bundle
/lgtm

/hold

This is obsoleted by #1494
/close


support caching for certgen services

This is useful for both the in-memory issuer as well as the external service.
Goal would be to support caching so that certs for common domains do not all the time have to be generated (per connection).

Gonna implement something now already as this is otherwise eating CPU, generating certs isn't cheap


proposal: AuthPolicy resource

Relates to
#1492
#1821
#1846
What is this?
UpstreamTrafficPolicy is a proposal for a new policy attachment resource that can be applied to Gateways and xRoute resources. It is meant to supplement a lot of config that Gateway API currently lacks while also providing a way to specify global defaults. It is similar to the proposal for an UpstreamTrafficPolicy with the notable difference that this tackles authentication based features and will thus support overrides and defaults.
How would I use this resource?
You can attach an AuthPolicy to a Gateway to set global defaults that will apply to all children xRoute objects of that Gateway. You can also create an AuthPolicy to attach to an xRoute object to configure things on a route-to-route basis and override global defaults if needed.
How will the overrides and defaults work?
If there is an AuthPolicy X attached to a Gateway, and an AuthPolicy Y attached to an HTTPRoute:

overrides from policy X will win in a conflict with overrides from policy Y.

This is to support the use-case of a cluster admin/operator setting some global overrides that are not allowed to be changed on a route level

defaults from policy Y will win in a conflict with defaults from policy X.

While cluster admins/operators might want to provide sane defaults, developers creating xRoute objects should still be able to override those defaults on a route-to-route basis (unless otherwise enforced by Gateway level overrides in the above scenario)

What if Gateway API implements a GEP that delivers the same functionality as some of the fields of this resource?
If Gateway improves any of their existing resources to deliver functionality that meets all of the needs of any of the below config,
then we will deprecate the field in this resource and use the Gateway API config instead. Ideally, a lot of this config can be
upstreamed into Gateway API in some form eventually since this resource only exists to solve areas where Gateway API is lacking for the needs of Envoy Gateway.
Can you use multiple AuthPolicy resources at the same time?
You may use multiple AuthPolicies that target different resources, but you may not attach multiple AuthPolicies
to the same resource. For example, it is invalid to attach two AuthPolicies to the same Gateway. Merging config in this scenario would quickly become convoluted and confusing, and there are many edge-case scenarios that make supporting this undesirable.
How will this be developed/implemented?
This issue serves as a proposal for the high-level design and fields of the API, but that does not mean that every field included below will be immediately available. My plan for the implementation is to add and implement one high-level field at a time until the whole resource is implemented.
API outline
---
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: AuthPolicy
metadata:
  name: example-policy
spec:
  # defaults and overrides will have the same configuration options.
  # If there is an AuthenticationPolicy A attached to a Gateway, and an AuthenticationPolicy B
  # attached to an xRoute, `overrides` from policy A win and `defaults` win for policy B
  # This allows for global defaults, changing those defaults on a route to route basis and enforcing
  # certain settings at a Gateway level.
  defaults:
  overrides:
    connections: # optional
      ipBlocking: # optional
        mode: Enum(allow-list/deny-list) # required
        ips: # required, minItems=1
        - type: Enum(peer/remote) # required
          value: string # required (example: <IP_ADDRESS> or <IP_ADDRESS>/16)
    cors: # optional
      allowedOrigins: []string # required
      allowedMethods: []string # optional
      allowedHeaders: []string # optional
      allowCredentials: bool # optional
      exposedHeaders: []string # optional
      maxAge: string # optional
    authentication: # optional
      bypassAuth: bool # optional
      filters: # optional (allows setting default auth filter(s) or forcing them)
        # action controls how the filter is added. add will add the filter to the list of existing filters,
        # replace will remove any existing AuthenticationFilters first.
        action: Enum (add/replace) # optional, default=add
        # priority determines the ordering of the filter if there are other filters on the resource.
        # The derfault priority of all filters is interpreted as 0 which will cause the filter to be
        # appended to the list if other filters exist. negative values can prepend the filter(s) to any existing ones.
        priority: int # optional, default=0.
        targetRef: # required
          group: string
          kind: string # only Envoy Gateway's AuthenticationFilter will be supported for now
          name: string
  targetRef: # required
    group: string
    kind: string # must be a Gateway or xRoute object reference
    name: string

Open questions

This resource can be attached to a Gateway, but you can configure multiple listeners on a single Gateway. Realistically, this resource makes the most sense targeting listeners instead of forcing this to apply to the entire gateway. There should be a way to specify which listeners it applies to so that you can have different config for each listener.

After discussion with @arkodg in the Gateway meeting today, we agree that the best approach is likely to start with making this apply to the entire Gateway and then adding in support for @zhaohuabing's  SectionName to PolicyTargetReference enhancement when it lands and becomes available.

@AliceProxy this looks overall good. I have a few questions:

EG will also need to support Authorization, for example, define which identify can access which Gateway/Listener/Route/Path. Do you plan to incorporate authorization in the AuthPolicy API, or add a separate Authorization Policy?
I don't understand the filters part inside the authentication. Is it a Envoy filter reference or a Gateway API resource or an EG resource? Could you please elaborate on that?

Thanks.

wanted to highlight that the usage of overrides & defaults here and not in UpstreamTrafficPolicy feels weird and adds cognitive load on user to remember that some Inherited Policy Attachments APIs use overrides and defaults and some dont.
I would vote to just introduce overrides and defaults in the UpstreamTrafficPolicy and combine the 2 APIs

@zhaohuabing

EG will also need to support Authorization, for example, define which identify can access which Gateway/Listener/Route/Path. Do you plan to incorporate authorization in the AuthPolicy API, or propose a separate Authorization Policy?

I'm sure this policy isn't exhaustive, but yes, I would like to use this resource for any authorization/authentication features and config knobs we would like to support in the future adding any additional top-level fields or expanding existing fields.

I don't understand the filters part inside the authentication. Is it a Envoy filter reference, or a Gateway API resource, or an EG resource? Could you please elaborate on that?

The filters is currently meant to reference our AuthenticationFilter resource so that you could specify default filters that you want to run on all children xRoutes of a Gateway unless otherwise overridden, or even to configure Gateway level filters that must be enforced on all routes and cannot be removed by any other config.
@arkodg was mentioning that if this resource is implemented and is successful, we might even deprecate the AuthenticaitonFilter and only use this policy resource to in-line the same configuration so that we reduce the total number of CRDs we are adding on top of Gateway API.

The filters is currently meant to reference our AuthenticationFilter resource so that you could specify default filters that you want to run on all children xRoutes of a Gateway unless otherwise overridden, or even to configure Gateway level filters that must be enforced on all routes and cannot be removed by any other config.

I personally don't like this combination of AuthPolicy and Filter approach. If we would like to achieve all auth related configurations inside the AuthPolicy, I suggest we just include the specs of
AuthenticationFilter here and deprecate the AuthenticationFilter.

thinking about this again, it makes sense to have a separate API for authn & authz instead of collapsing this into UpstreamTrafficPolicy to provide flexibility in authorship, allowing the platform admin persona to be split up into net admin and sec admin .
Reg naming, prefer SecurityPolicy over AuthPolicy

After discussion with @AliceProxy at this week's EG meeting, we agreed that the OIDCAuthenticationPolicy should be merged with this one to provide users a more unified auth AP. I would also like to suggest incorporating the JwtAuthenticationFilter in this Policy.
kind: SecurityPolicy
metadata:
  name: example-policy
spec:
  # defaults and overrides will have the same configuration options.
  # If there is an SecurityPolicy A attached to a Gateway, and an SecurityPolicy B
  # attached to an xRoute, `overrides` from policy A win and `defaults` win for policy B
  # This allows for global defaults, changing those defaults on a route to route basis and enforcing
  # certain settings at a Gateway level.
  defaults:
  overrides:
    connections: # optional
      ipBlocking: # optional
        mode: Enum(allow-list/deny-list) # required
        ips: # required, minItems=1
        - type: Enum(peer/remote) # required
          value: string # required (example: <IP_ADDRESS> or <IP_ADDRESS>/16)
    cors: # optional
      allowedOrigins: []string # required
      allowedMethods: []string # optional
      allowedHeaders: []string # optional
      allowCredentials: bool # optional
      exposedHeaders: []string # optional
      maxAge: string # optional
    authentication: # optional
      bypassAuth: bool # optional
      oidc: # oidc authentication configuration
        provider: # the information of the OIDC identity provider
          issuer: string # The OIDC identity provider's issuer identifier. It’s also an URL which can be used by EG to discover the provider’s AuthorizationEndpoint and TokenEndpoint. An example: "https://accounts.google.com"
          AuthorizationEndpoint: string # optional The URL to which users are redirected in the authentication flow. If not provided,TEG will obtain it from the provider's Well-Known Configuration Endpoint through the OIDC discovery mechanism.
          TokenEndpoint: The URL where your application exchanges the authorization code for an access token. It’s an optional field.  If not provided,EG will obtain it from the provider's Well-Known Configuration Endpoint through the OIDC discovery mechanism.
        clientID: string # This is an unique identifier assigned to your application by the OIDC identity provider. An Example "xxx.apps.googleusercontent.com"
        clientSecret: The Kubernetes secret which contains the OIDC client secret, which is a confidential token shared between your application and the OIDC identity provider to authenticate your application.
          name: "oidc-client-secret"
          namespace:  string # optional
        scopes: []string # optional, if not specified, "openid" is used.
      jwt: # jwt authentication configuration
      issuer: # optional Issuer is the principal that issued the JWT and takes the form of a URL or email address.If not provided, the JWT issuer is not checked.
      audiences: # optinal Audiences is a list of JWT audiences allowed access. If not provided, JWT audiences are not checked.
      remoteJWKS: # RemoteJWKS defines how to fetch and cache JSON Web Key Sets (JWKS) from a remote HTTP/HTTPS endpoint.
        uri: https://raw.githubusercontent.com/envoyproxy/gateway/main/examples/kubernetes/authn/jwks.json
      claimToHeaders: # optinal A list of JWT claims that must be extracted into HTTP request headers
        targetRef: # required
          group: string
          kind: string # only Envoy Gateway's AuthenticationFilter will be supported for now
          name: string
  targetRef: # required
    group: string
    kind: string # must be a Gateway or xRoute object reference
    name: string

was chatting with @ZackButcher about this earlier today and summarizing some of our discussions

here are the relevant features that could get clubbed into the same SecurityPolicy API

jwt
oidc
ext authz
basic auth
api key
cors

some of above features likes jwt & ext authz can be used for authn and authz which makes it hard to divide it into explicit authn and authz APIs or even top level fields.
implicit overrides similar to BackendTrafficPolicy makes sense here i.e. a Gateway / Platform admin can set a SecurityPolicy with a cors value set and attach it to the Gateway. If the platform admin has provided access to the app owner to also create a SecurityPolicy in their app namespace, its okay for the app owner to create another SecurityPolicy with a new cors value that implicitly overrides the more generic value.
we agreed that ipBlocking doesnt fit in this API because its something that will never be relevant for App Owners, instead the ClientTrafficPolicy might be a good home for it.

Should multiple authn/authz be allowed to coexist in the SecurityPolicy API? For example, can users specify both the OIDC and ext auth configurations?
Should RBAC aslo be included in the SecurityPolicy?

was chatting with @ZackButcher about this earlier today and summarizing some of our discussions

here are the relevant features that could get clubbed into the same SecurityPolicy API

jwt
oidc
ext authz
basic auth
api key
cors

some of above features likes jwt & ext authz can be used for authn and authz which makes it hard to divide it into explicit authn and authz APIs or even top level fields.

implicit overrides similar to BackendTrafficPolicy makes sense here i.e. a Gateway / Platform admin can set a SecurityPolicy with a cors value set and attach it to the Gateway. If the platform admin has provided access to the app owner to also create a SecurityPolicy in their app namespace, its okay for the app owner to create another SecurityPolicy with a new cors value that implicitly overrides the more generic value.

we agreed that ipBlocking doesnt fit in this API because its something that will never be relevant for App Owners, instead the ClientTrafficPolicy might be a good home for it.

Some of the above combinations work, while others may not make sense. For example:  CORS can work with others, but specifying both OIDC and ext authz isn't meaningful.

Should RBAC aslo be included in the SecurityPolicy?

@zhaohuabing specifying OIDC and ext authz may make sense, if OIDC is being used for authn and ext authz is being used for authz (using OPA).

from the Envoy RBAC filter, which feature fields do you think we should be exposing that we haven't planned to do so yet ?

@zhaohuabing specifying OIDC and ext authz may make sense, if OIDC is being used for authn and ext authz is being used for authz (using OPA).

from the Envoy RBAC filter, which feature fields do you think we should be exposing that we haven't planned to do so yet ?

Maybe I missed something, but I didn't see any authz regarding RBAC in the SecurityPolicy.

the openapi spec's security section https://spec.openapis.org/oas/v3.1.0#security-scheme-object is another good datapoint which has outlined all features mentioned in https://github.com/envoyproxy/gateway/issues/1845#issuecomment-1724495012

I would concur with removing the defaults/overrides separation and simply relying on K8s RBAC for that sort of thing, and with moving IP blocking into ClientTrafficPolicy.
I think it probably makes sense to leave CORS in the SecurityPolicy: Ana is likely to care a lot about things like how to do load balancing for her specific workloads, but I'm not sure she's ever in a great position to be messing with CORS, IP blocking, etc.


reboot command causes crash inside a session

I get an error when  using the reboot command inside a session
session 1
session started with [1] <IP_ADDRESS> thomas-VirtualBox Linux
$ sudo reboot
$ d
#<Thread:0x0000562aaee41ef0 /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:23 run> terminated with exception (report_on_exception is true):
/home/chrisbasinger/RubymineProjects/mechtron/server/client.rb:39:in `gets': undefined method `chomp' for nil:NilClass (NoMethodError)
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:53:in `block (3 levels) in session'
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:52:in `loop'
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:52:in `block (2 levels) in session'
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:26:in `loop'
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:26:in `block in session'
/home/chrisbasinger/RubymineProjects/mechtron/server/client.rb:39:in `gets': undefined method `chomp' for nil:NilClass (NoMethodError)
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:53:in `block (3 levels) in session'
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:52:in `loop'
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:52:in `block (2 levels) in session'
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:26:in `loop'
	from /home/chrisbasinger/RubymineProjects/mechtron/server/commands.rb:26:in `block in session'

I tried a lot of fixes and all of them propagated nil errors upwards. Okay. So, obviously the work around is to use the reboot command.

i did
response = @sock.gets
unless response
return nil
end
return response.chomp


Add global rate limiter to s3 proxy v2 attribute

What changes are proposed in this pull request?
Add global rate limiter to s3 proxy v2 attribute.
Why are the changes needed?
The global rate limiter does not work in s3 proxy v2, because we didn't add it to the attribute of servletContext.
Does this PR introduce any user facing changes?
Please list the user-facing changes introduced by your change, including

change in user-facing APIs
addition or removal of property keys
webui

@humengyu2012 is the PR ready for review?


[Removal]: Mysterious Chili Dalmatian

Hotspot Name
Mysterious Chili Dalmatian
Hotspot b58 Address
11pV3sFKZF9R1Pk2RUxLdEANiU9GrpyrdPmx9q4mVVLAfjjm91t
Discord Handle
No response
Hotspot Manufacturer
Deeper
Removal Reason
This hotspot doese not even assert location, did not send any poc or witnesses, why deny?

These "controllers" ban without knowing how to distinguish between a Chinese scammer and an honest operator who has invested a lot of money in helium!
Not to mention that lately the Helium network also sucks in terms of performance and pays less and less just because it wants to speculate on the number of connected HS and then sell to someone who buys the whole hut.

I am very disgusted by the cowardly and unprofessional attitude of these "controllers" and Helium executives who steal our honest money and get rich behind us by stealing our work !!!


[Experimental] - Max resource lifetime controller

This PR adds a simple utility that sets maximum resource lifetime by scanning and finding the oldest resource.  If the oldest instance's age is greater than the set max lifetime, and that the system is in steady-state (ie, the successive counts of instances are not decreasing over time), then destroy the instance.   Once the instance is destroyed, the other controller (specifically the Group plugin) will detect the change and replace the instance with a new one.
This is useful for rotating compute nodes / workers in a cluster such that no instances can exceed a certain lifetime and can be subjected to attacks.   This serves as a POC for combining container and infrastructure orchestration to improve security of a compute cluster.
It's possible to add interaction with a flavor plugin to force a "Drain" of the targeted resource before destruction.  It will be done in a future PR.
A new subcommand x for experimental is added to the CLI so that this feature is added as a subcommand of the experimental features.
Signed-off-by: David Chung<EMAIL_ADDRESS>

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "maxlife" git@github.com:chungers/infrakit.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842353806272
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.


Visual indicator for focused field missing

Discovered while tabbing on a MC question page.
To replicate:

Create quiz and select to add MC question
Use tab & shift +tab to move through page
Notice as you tab down, which field visual focus indicator says you are on. Easiest to see if you start at first answer choice field and then tab down. One tab should get you to correct answer radio button. Two tabs to Remove link. Three tabs to next answer field

Occurs on Duke 19.x; not on Nightly trunk

Ex: https://warpwire.duke.edu/w/vXMDAA/

fixed in 20.x upstream


make  pebble the clear choice

Closes: #90

add pebbledb
use latest pebble
added a ton of test rigor and fixed linting
if always false we don't need the param
let's go fast

All I can say is:

informal never merged it
ICF never funded it
notional never optimized it

faddat@Whites-MacBook-Pro cometbft-db % GOARCH=arm64 go test -bench=BenchmarkPebbleDBvsGoLevelDB
goos: darwin
goarch: arm64
pkg: github.com/cometbft/cometbft-db
BenchmarkPebbleDBvsGoLevelDB/PebbleDB-8                   322890              3930 ns/op
BenchmarkPebbleDBvsGoLevelDB/GoLevelDB-8                  315639              4425 ns/op
PASS
ok      github.com/cometbft/cometbft-db 7.470s

faddat@Whites-MacBook-Pro cometbft-db % GOARCH=arm64 go test -bench=BenchmarkPebbleDBvsGoLevelDB
goos: darwin
goarch: arm64
pkg: github.com/cometbft/cometbft-db
BenchmarkPebbleDBvsGoLevelDB/PebbleDB-8                   348592              3866 ns/op
BenchmarkPebbleDBvsGoLevelDB/GoLevelDB-8                  307240              4261 ns/op
PASS
ok      github.com/cometbft/cometbft-db 7.409s

However if tested against iavl, this would be even more superieor.

we've decided to license this code.  Please don't merge it.  SDK team granted perpetual license.

Please use this mainly for the benchmarks as I think I made a kind of significant finding here with regard to high bandwidth situations.

I'll pull benchmarks from here.

to: maintiner (idk who this is) please run benchmarks on a solidly fast machine.
I fear if we don't it wont match the real world.

sometimes pebble is a few million times faster.
Flakiness, anyone?

the big worry here is that goleveldb does not act in a predictable manner.

preparing a branch of cometbft's main to see if we can eliminate time based flakiness with pebble.

I'm a fan. How is pebbleDB handling workload in Berachain?
Really wish you didn't do unnecessary changes here so we could review it easier. But aside from that, concept ACK and we'll review this ASAP, thanks for patience!

Closing in favor of https://github.com/cometbft/cometbft-db/pull/112. Let's focus on a single PR. After it's merged, we can do linting.


Clean up docker failing during tests?

I wish there was a better way to fail if docker wasn't/isn't running.
[2207] ERR docker/executor.go:389 > Docker executor stop error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
=== RUN   TestExecutorDockerExecutorSuite/TestGrepFile
    docker_executor_test.go:82:
        	Error Trace:	/Users/daaronch/code/bacalhau/pkg/test/executor/docker_executor_test.go:82
        	            				/Users/daaronch/code/bacalhau/pkg/test/executor/docker_executor_test.go:120
        	            				/Users/daaronch/code/bacalhau/pkg/test/executor/docker_executor_test.go:141
        	Error:      	Should be true
        	Test:       	TestExecutorDockerExecutorSuite/TestGrepFile

Maybe this is working as intended.

what would you like it to do?

meh, i dunno - good question. IDEALLY maybe start docker? Or stop all tests from running (across everything) if docker isn't running since it'll likely lead to hidden errors?


Plugin pipedrive-import version 0.9.1

will there be an easter egg around version <IP_ADDRESS>, or at least <IP_ADDRESS>.1?

@JoachimZ : If I can insert some javascript in the plugin, of course :)


The following string occured many times in sources: "description: "

commands/configurations.go:128:30:1 other occurrence(s) of "description: " found in: commands/profiles.go:87:30
commands/profiles.go:87:30:1 other occurrence(s) of "description: " found in: commands/configurations.go:128:30

Fixed in https://github.com/RedHatInsights/insights-operator-cli/pull/499


Fix the readme, missing ')'

In the documentation there is missing parentheses, so if anybody try to copy the code it will fail because of syntax error.

Good catch! Somehow everyone else missed it for so long :D


mxnet.base.MXNetError  on gpus

I'm trying to run mxnet on an multi-label problem using self defined MakeLoss, the code runs fine on cpu, but fails on gpus, I cannot find any related information online.
Environment info
Operating System: Centos
Compiler: gcc 5.3.0
Package used (Python/R/Scala/Julia): python 3.6
MXNet version: 0.9.5
Or if installed from source:
MXNet commit hash (git rev-parse HEAD):
If you are using python package, please provide
Python version and distribution:
If you are using R package, please provide
R sessionInfo():
Error Message:
[21:55:20] /home/ubuntu/mxnet-distro/mxnet-build/dmlc-core/include/dmlc/logging.h:304: [21:55:20] /home/ubuntu/mxnet-distro/mxnet-build/mshadow/mshadow/././././cuda/tensor_gpu-inl.cuh:118: Check failed: err == cudaSuccess (11 vs. 0) Name: MapPlanLargeKernel ErrStr:invalid argument
Stack trace returned 10 entries:
[bt] (0) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0x184dfc) [0x2b4cd8067dfc]
[bt] (1) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0x17e3b2e) [0x2b4cd96c6b2e]
[bt] (2) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0x17f4a7a) [0x2b4cd96d7a7a]
[bt] (3) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb45646) [0x2b4cd8a28646]
[bt] (4) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb201f7) [0x2b4cd8a031f7]
[bt] (5) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb2431c) [0x2b4cd8a0731c]
[bt] (6) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb24c4d) [0x2b4cd8a07c4d]
[bt] (7) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb47472) [0x2b4cd8a2a472]
[bt] (8) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(MXExecutorForward+0x15) [0x2b4cd89ca475]
[bt] (9) /mnt/home/yangshao/.linuxbrew/lib/libffi.so.6(ffi_call_unix64+0x4c) [0x2b4c97755ff6]
Traceback (most recent call last):
File "mlp.py", line 178, in
num_epoch=3
File "/mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/module/base_module.py", line 472, in fit
self.forward_backward(data_batch)
File "/mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/module/base_module.py", line 193, in forward_backward
self.forward(data_batch, is_train=True)
File "/mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/module/module.py", line 538, in forward
self.exec_group.forward(data_batch, is_train)
File "/mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/module/executor_group.py", line 379, in forward
exec.forward(is_train=is_train)
File "/mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/executor.py", line 124, in forward
ctypes.c_int(int(is_train))))
File "/mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/base.py", line 84, in check_call
raise MXNetError(py_str(_LIB.MXGetLastError()))
mxnet.base.MXNetError: [21:55:20] /home/ubuntu/mxnet-distro/mxnet-build/mshadow/mshadow/././././cuda/tensor_gpu-inl.cuh:118: Check failed: err == cudaSuccess (11 vs. 0) Name: MapPlanLargeKernel ErrStr:invalid argument
Stack trace returned 10 entries:
[bt] (0) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0x184dfc) [0x2b4cd8067dfc]
[bt] (1) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0x17e3b2e) [0x2b4cd96c6b2e]
[bt] (2) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0x17f4a7a) [0x2b4cd96d7a7a]
[bt] (3) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb45646) [0x2b4cd8a28646]
[bt] (4) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb201f7) [0x2b4cd8a031f7]
[bt] (5) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb2431c) [0x2b4cd8a0731c]
[bt] (6) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb24c4d) [0x2b4cd8a07c4d]
[bt] (7) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(+0xb47472) [0x2b4cd8a2a472]
[bt] (8) /mnt/home/yangshao/mxnet/lib/python3.6/site-packages/mxnet/libmxnet.so(MXExecutorForward+0x15) [0x2b4cd89ca475]
[bt] (9) /mnt/home/yangshao/.linuxbrew/lib/libffi.so.6(ffi_call_unix64+0x4c) [0x2b4c97755ff6]
[21:55:21] src/engine/naive_engine.cc:35: Engine shutdown
Minimum reproducible example
if you are using your own code, please provide a short script that reproduces the error.
Steps to reproduce
or if you are running standard examples, please provide the commands you have run that lead to the error.

What have you tried to solve it?

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


Ability to specify ingest node pipeline

Describe the feature:
Elasticsearch 5.0+ supports adding an ingest processor.  It would be neat if Rally could support adding the pipeline=foo parameter as part of its indexing parameters, ala PUT my-index/my-type/my-id?pipeline=my_pipeline_id

Rally 0.4.3 will support a new parameter pipeline for the index operation in a track. This will only work if users define the pipeline before-hand, i.e. Rally is currently not able to setup an ingest node pipeline (but #105 will help with that).


bump-formula-pr: handle additional edge cases

[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 tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

Allow bump-formula-pr to work with formulae that:

use a URL that specifies only a revision, and a version (e.g. acme, colortail, pytouhou)
brew bump-formula-pr -f -n acme --version=0.98 --revision=277
use a repository URL providing an autodetected version (e.g. smpeg)
brew bump-formula-pr -f -n smpeg --url=svn://svn.icculus.org/smpeg/tags/release_0_4_6/ --revision=400

Fixes #9462.
Currently exposes an issue with formulae that specify the revision as an integer rather than a string, i.e. fuego, netpbm, spim.
$ brew bump-formula-pr -f -n spim --version=9.2 --revision=800
==> replace 732 with "800"
Error: wrong argument type Integer (expected Regexp)
/usr/local/Homebrew/Library/Homebrew/utils/string_inreplace_extension.rb:36:in `gsub!'
/usr/local/Homebrew/Library/Homebrew/utils/string_inreplace_extension.rb:36:in `gsub!'
/usr/local/Homebrew/Library/Homebrew/utils/inreplace.rb:78:in `block in inreplace_pairs'
/usr/local/Homebrew/Library/Homebrew/utils/inreplace.rb:71:in `each'
/usr/local/Homebrew/Library/Homebrew/utils/inreplace.rb:71:in `inreplace_pairs'
/usr/local/Homebrew/Library/Homebrew/dev-cmd/bump-formula-pr.rb:332:in `bump_formula_pr'
/usr/local/Homebrew/Library/Homebrew/brew.rb:119:in `<main>'

Review period will end on 2020-12-10 at 03:16:03 UTC.

Review period ended.


Need method for manual camera pointing control other than RC Override

Currently, the only way to have full manual camera pointing control, such as tilt on a joystick, is to use an RC Override. My understanding is RC Overrides are planned to be eliminated.
Use-case is something like, flying around in Loiter mode, and wishing to look around manually rather than giving aiming points or ROI.

AFAIK this is correct. The MAVLink command for manually controlling camera position (MAV_CMD_DO_MOUNT_CONTROL) can only be used in missions (the set of commands that can be  used in guided mode on copter are here.)
I have raised request https://github.com/diydrones/ardupilot/issues/2670 for the command to be added in ardupilot for guided mode. This is a precondition for adding an API in dronekit.


Make it compatible with dependabot bump messages

Thanks for stopping by to let us know something could be better!
Is your feature request related to a problem? Please describe.
Sort of yes, I use conventional commits with release-please Github actions throughout various projects as well were dependabot is under use, but release-please is unable to parse/understand dependabot dependencies bumps messages.
Describe the solution you'd like
I can customize dependabot bump message to change the customary **chore(deps): ** to **deps: ** as expected by release-please but release-please will only look for a message under a specific regular expression
/^deps: update dependency (.*) to (v[^\s]*)(\s\(#\d+\))?$/m;
and dependabot message carries the following format

deps: bump com.google.code.gson:gson from 2.10.1 to 2.11.0

The proposition here is to check the commit message agains 2 regex'es, 1 for renovate style and another for dependabot style.
Describe alternatives you've considered
can't think of any at the moment
Additional context
Add any other context or screenshots about the feature request here.

dependabot also produces this commit message patter:

build(deps): bump  from  to
build(deps-dev): bump  from  to

it would be great if release-please can create release PR for build(deps) changes but not build(deps-dev) changes


migrate to swift 3

results in iOS_swift3_migration branch

@dersim-davaod, @yaronyg, @drinkius  swift 3 code is here

there is a separate notification for @larryonoff :)

Thanks! are going to create PR ?

@larryonoff, I think it will have sense only after we officially declare that we support iOS 10. Or do you want this PR just not to forget about this changes?

@baydet you're right. not to forget and start reviewing.


👷 ci: Add dependabot config

Add dependabot config.
Automate gh-actions and go mod dependencies updates on a weekly-basis.
As mentioned in #7 and #57

@drpaneas You will have to "install" dependabot from Marketplace for this repo.

@drpaneas You will have to "install" dependabot from Marketplace for this repo.

done ;)


Handle problems in get study list from dicomweb server and study url problems #3541

#3541

Already done in OHIF


advance_drheader_for_bulkimport #8573

Description
This PR fixes DrHeader to also parse bulkimports
Test results
I have added another test that tests bulkimport results.

Sorry, I did not mention it before but now it has come to my eyes:

Is it necessary to copy-paste the whole part with iterations and create Findings? I suppose if can be used only at the end of the loop and decide if add find.unsaved_endpoints = [Endpoint.from_uri(url)] is necessary
if uses data[0].get("url"). What is endpoint will be used in the first finding but not in the second. Parsing would fail.

Hi @kiblik,
I don't know if I get right what you are asking, but I am explaining what I am interpreting:
DrHeader has two mods to scan targets: a) a single target or b) multiple (bulk) targets. This resolves in two different output formats. a) does not include endpoints in the finding results as it is clear which endpoint was scanned. b) does include an endpoint in each finding. These two scan results are captured through the if - else block:
if data != {} and data[0].get("url") is not None
Does this answer your question?
I could provide a comment in the code to the mods of DrHeader to make it more clear, but the parser will not fail unless DrHeader changes in future releases.

@cneill could you review the PR?

@manuel-sommer, now I see. I didn't realise that there is one for look in the first case and two of them in the second case.
I just noticed that lines 26-42 and 48-64 are almost the same and I wanted to avoid repeating the same code.
Can you imagine putting it to an extra function that will have one parameter (you will pass there item or finding) and prepare Finding? This function would be called instead of lines 26-42 and 48-64.

@kiblik could you retrigger the pipeline?

@kiblik could you retrigger the pipeline?

I'm not able to retrigger the pipeline (I do not have that kind of permission). But you can do it by closing and reopening PR.
Retrigger will not help you. There is an issue with the removed version of celery. I proposed fix but we have to wait until somebody from the community approves it and merges it. I already wrote to the community Slack to speed it up.

@manuel-sommer  Breaking changes in celery 5.3.2 and 5.3.3 broke our builds. I've merged 5.3.4 (which reverts the breaking changes) so please rebase to fix the issue celery caused that broke our tests.

Did I mess up the rebase somehow @mtesauro ?

@damiencarol please review

@cneill could you please review?


Reset slider

Hello
It's possible de reset slider when click on button type reset ?
Thanks

There is a reset event in the Web API (reference).
Combining the reset event with a programatic value change of the rangeslider.js API should be a possible solution.
Programatic value change example


Don't format disks before chef install

This fixes issue #384.
I believe the zap-disks script is what causes disks to require an xfsrepair after re-installing hosts.
xfsrepair is always a destructive operation, because XFS only requires repair after serious corruption, e.g. a missing superblock.  Routine problems, of the kind fixed by fsck, are handled by mount(2)

LGTM

LGTM.


[5.2] Urldecode email parameter and added email to compact function

The emailaddress in the resetemail is urlencoded, but in the view never decoded.
Also the email field was not passed to the compact() function when using the auth.reset view

@it-can did you actually have an issue with the e-mail address not being decoded properly or were you just anticipating?

I got a value of test%40test.com in my resetform, instead of<EMAIL_ADDRESS>

Aaah I see the problem now, it is double encoded... I used this in my mailtemplate:
$reset_url = route('password.resetlink', [$token, 'email' => urlencode($user->getEmailForPasswordReset())]);

but when I use
$reset_url = route('password.resetlink', [$token, 'email' =>$user->getEmailForPasswordReset()]);

it works correctly without the need to urldecode()


FullyConnected layer integration changes

Following changes have been made :

Integration of float32, 4-bit & 16-bit fully_connected kernels.
Integration of matmul kernels for float32, 4, 8, 16-bit batched fully_connected cases.
Data-type based registration for fully_connected operator.
Addition of compile flag to include / exclude HiFi floating point optimized fully_connected kernel.

BUG=none

@vp-cad - The formatting errors can be fixed with:
tensorflow/lite/micro/tools/ci_build/test_code_style.sh --fix_formatting


logfile prompt

I was running some test yesterday and I realised that it is quite easy to not start the logfile running. The button is to the lower right and non-descript. This was also true with the original logfile button and setup. I missed starting this logging on a couple of occassions.
It would be worthwhile to have a pop up window appear, particularly when a script file is running to advise the user if their have not started logging.

Potentially partially resolved by #517, as logfile button & setup are now in the significantly less cluttered left-hand side, but it could definitely be worth adding some form of indication for whether the logfile is being written to.


argument fn not work in mafSurvival() function

argument fn not work in mafSurvival() function
fn only exist in the argument part, so it can not save the picture as pdf

Hi,
Thanks for letting me know. Those arguments are not functional, and I have removed them.
You can save the plots as you would normally by calling pdf() before running mafSurvival().
Hope this helps.

Hi,
Thanks for letting me know. Those arguments are not functional, and I have removed them.
You can save the plots as you would normally by calling pdf() before running mafSurvival().
Hope this helps.


An unfinished sentence in types tutorial

This commit introduced the following sentence to "Numba types" documentation:

A function where type inference is unable to provide a specific type for a value (that is, any type other than the generic pyobject).

which clearly lacks a verb. Here is the full context:

It must be emphasized how important it is type inference in numba. A function where type inference is unable to provide a specific type for a value (that is, any type other than the generic pyobject). Any function that has a value fallback to pyobject will force the numba compiler to use the object mode. Object mode is way less efficient thant the nopython.

Edit: Also, the markdown links in CONTRIBUTING.md have some unwanted spaces which makes them misrender on GitHub.

Thanks for the report. The "Numba types" document to which you are referring is a number of years old and refers to v0.12, we just released a RC for 0.36 (docs are here for the latest released version, 0.35 and here for the cutting edge, 0.36rc1)! I'm fairly sure that tutorial does not render as part of the current documentation, however, I note there's a notebook of the same at numba/tutorials/Numba types.ipynb which does need updating.
Thanks for the note about https://github.com/numba/numba/blob/master/CONTRIBUTING.md, fixed in https://github.com/numba/numba/pull/2633

It is assumed that the above resolved the reported issue, if this is not the case please reopen the issue with new information. Many thanks.


timestamps are converted to utc on logging

Describe the bug
for example i have a from & to date columns with values of

from
to

2021-02-23 00:00:00
2021-02-27 00:00:00

but when logged they become

from
to

2021-02-22T22:00:00.000000Z
2021-02-27T22:00:00.000000Z

note the -2 hrs diff.
To Reproduce

set config.app.timezone to something else ex.EET
create a record
check the saved log

Expected behavior
data should be logged as it is without any changes.
Versions (please complete the following information)

PHP: PHP 8.0.2 (cli)
Database: 8.0.23
Laravel: 8.28.1
Package: 3.16.1

The value is still the same as the zulu offset is added. So if you say carbon to display & format it for a given timezone everything is fine.
I can recommend you to use https://github.com/jamesmills/laravel-timezone by @jamesmills to display your Datetimes.

but am not sure why the package changes the value in the first place ?, shouldnt it be a copy / paste of the original ?

We use the serializeDate() method on the model to ensure a string which we can save and the database understands.
https://github.com/spatie/laravel-activitylog/blob/ade270f291f4cb5883b3653919304a0b4e1cc284/src/Traits/DetectsChanges.php#L158-L162
Under the hood this method calls Carbon::toJSON() which again calls \Carbon\Traits\Converter::toISOString() and this methods drops timezone offset by default.
But you should always enforce a timezone when you need it instead of trusting Laravel or any package to properly keep your timezone. It makes it also easier to see that a given timezone is required there.

is there a way i could hook into the activity creating event and set/cast the dates ?

I've used this package in a project before and I've used the https://github.com/jamesmills/laravel-timezone to output the logged event date/time to the user in their timezone. I'm a strong believer in setting and storing everything in UTC.

@jamesmills this would be valid if u r saving the data in one way everywhere and displaying it in a unified  manner according to user prefs,
but when the data is saved in one way & logged in another, this creates wrong logs with changes not recognized  from the original action.
@Gummibeer
enforcing such a strategy on the user without warning is a bad decision, if i set a timezone globally for the whole app, it means i expect that every single date in the app will follow that, otherwise its considered a bug.

Ah, I get you.
Mon, 22 Feb 2021 22:00:00 +0000 Coordinated Universal Time
It is saving it as UTC as the ISO standard but you are asking why it's not saving it in the config.app.timezone Timezone. It looks like the laravel-activity package saves all data as UTC be default. I would say that's a safe way of doing things. I guess when it pulls it out you could argue it could look at the config.app.timezone value and output it as that. But you could just use the jamesmills/laravel-timezone package to output the date to the user. It will try use the users timezone and if that fails it will fallback to use the config.app.timezone (I think we added that recently).
Sorry if I'm not understanding or helping.

It would be a bug if we drop the timezone/zulu offset which would make it impossible to format the value in a wanted timezone. But as the timezone is appended it's only a different representation of the same datetime.
The data display representation is up to the user of this package and part of this is the timezone you want to display the date in.
The only solution I see I would be open to merge is to use toISOString(true) instead of serializeDate(). This should solve your issue.

for now here are a couple of solutions

save the date as expected

public static function logChanges(Model $model): array
{
  $changes = static::origLogChanges($model);

  foreach ($changes as $key => $val) {
      if ($model->isDateAttribute($key)) {
          $changes[$key] = (new Carbon($val))->setTimezone(config('app.timezone'))->toISOString(true);
      }
  }

  return $changes;
}

display the date as expected

protected function convertDate($item)
{
    if (strtotime($item)) {
        return (new Carbon($val))->setTimezone(config('app.timezone'))->format(...);
    }

    return $item;
}

Both aren't solutions I would accept in the package as it will only enforce another timezone instead of keeping the one that the carbon instance has.
That's why I would use the toISOString() which can keep the offset of the current instance.

the solutions would work as intended only if the all the dates in the app are saved/displayed according to app.timezone otherwise, you r correct using toISOString(true) would be the correct one.

i found another automated solution to get around saving in utc and displaying in different tz
// under any model

protected static function booted()
{
    static::retrieved(function ($model) {
        $casts = array_filter(array_keys($model->getCasts()), fn ($item) => $model->isDateCastable($item));
        $dates = array_merge($model->getDates(), $casts);
        $tz = 'EET'; // this could be a global config, cookie set vie middleware, etc...

        foreach ($dates as $key) {
            $model->{$key} = (new Carbon($model->{$key}))->setTimezone($tz);
        }
    });
}

Please would you PR a failing test descripting this issue.

Because this is a Laravel package, I think it should respect the Laravel timezone setting.
Perhaps it's "best practise" to save as UTC but I couldn't see anything on the website that suggests it disregards the config setting. And I think this can cause confusion for new-comers.

After digging a bit into I reject this feature request in favor of display formatting (packages). The persisted value is 100% valid and equals the assigned one.
This formatting is even better than the default DB datetime/timestamp column as they totally lose track of the timezone or require a second column.
I will accept a PR adding a note to the docs. But this change would be breaking (not so bad as we prepare v4) but also super hard to get consistent results as Laravel already does some timezone formatting (to the app timezone). In case we would implement such a feature I would want to do it in a more general way and persist the timezone of the assigned carbon instance independent of the app timezone.
As the user is able to switch the ISO string to whatever timezone wanted without having to guess the persisted timezone I will close this issue for the moment.
Regarding the last argument by @tyler36 it's another argument for not persisting the timezone of carbon object, even if it wasn't his intent. Every time you cast a carbon instance to JSON in Laravel it uses the ISO format without offset as that's the carbon default one. As we don't have any read/get casting logic in place the user is anyway responsible to get the wanted value/object instance - so the user also knows the best which timezone is wanted right now as that can change per app, user, view and so on.


Add images: import androidx.compose.foundation.Image

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-add-images?continue=https%3A%2F%2Fdeveloper.android.com%2Fcourses%2Fpathways%2Fandroid-basics-compose-unit-1-pathway-3%23codelab-https%3A%2F%2Fdeveloper.android.com%2Fcodelabs%2Fbasic-android-kotlin-compose-add-images#3
In which task and step of the codelab can this issue be found?
4. Add an Image composable
Describe the problem
Using sample code from the code-along video and the step 4. I'm receiving 4 errors when building the preview.
Sample Code:
@Composable
fun BirthdayGreetingWithImage(message: String, from: String){
    val image = painterResource(id = R.drawable.androidparty)
    Image(painter = image, contentDescription = null)
}

Errors:
-Cannot access '': it is package-private in 'Image'
-Cannot create an instance of an abstract class
-Cannot find a parameter with this name: painter
-Named arguments are not allowed for non-Kotlin functions
-Cannot find a parameter with this name: contentDescription
-Named arguments are not allowed for non-Kotlin functions
Steps to reproduce?

Go to...
Click on...
See error...

Versions
Android Studio version:
Android Studio Dolphin | 2021.3.1 Patch 1
API version of the emulator:
API3 3
Additional information
Include screenshots if they would be useful in clarifying the problem.

It seems like Android studio doesn't suggest importing import androidx.compose.foundation.Image . The tutorial also doesn't mention importing it.

Duplicate of #156
Please follow instruction in #156
Please let us know, if it does not work.


Update README.md

<EMAIL_ADDRESS>wasn't that helpful :)

Yeah sorry, I was testing GitHub pull requests and merging.


Porting to Python3

Hello,
I did support for Python3. I could test the compilation under versions 2.7.10 and 3.4.3 on a Raspberry Pi 2 with a DHT22 sensor.

Oups, forgot this file for compilation.

Spent a coupe of hours to port it to python 3 and got the more or less the same result as mala-zaba.
As I can see he basically changed the packing import statements in py files and the c-api object module initialization.
Please consider to merge this one!

https://github.com/adafruit/Adafruit_Python_DHT/commit/3e71e8c1b95e0e99cc002e3655f64d727a28ac92

Thanks so much for looking into the Python 3 port earlier!  This should be resolved now with a few recent pushes that added Python 3 support across the board.


mouse scroll on mac

it would be nice to be able to scroll through a buffer using my mouse.

I think this should be fixed. Can you pull the latest code and see if it works for you?

seriously, you implemented my feature request too quickly. It kinda sorta works now.
Unfortunately, window redraw seems to lag by quite a bit, so motion continues long after I've stopped scrolling.

It's been annoying me at work where I have a Mac, so I'd been meaning to look into it anyways.
I'll see if I have the same problems with the redraw/lag when I'm at work tomorrow and if there's anything obvious I can do about it while I'm physically at a Mac (other than trying to optimize the rendering code more..)

Okay, I'm definitely seeing the lag too. I think, other than the obvious fact that I need to optimize the rendering code, it might be that the shiny driver for Mac is sending the mouse wheel events at weird rates, because I'm also noticing things like it not sending any event if I scroll one click (or just in general if I scroll too slowly with the wheel), and the events are in the opposite direction of what the system preferences say it should be (golang/go#16020)
I'll try digging into it tonight and see if there's something wrong in my code or if I notice anything obviously with the driver (though that's unlikely since I don't really know objective C..)
(/cc @nigeltao FYI)

@crawshaw for mouse wheel weirdness on Mac shiny.
@driusan, are scroll events from the touch pad (instead of a mouse) OK?

@nigeltao Is there a event linter (testing program) for shiny? It might be easier and more direct to test on that. Something like go get -u github.com/goxjs/glfw/tests/events.
I tried de on OS X and the scrolling seems equally broken/laggy and not-smooth using both a mouse scroll wheel and a magic trackpad. But I can't be sure how much of that is due to shiny events, and how much due to de's logic on top.

@shurcooL that's basically what the shiny examples/basic program does, which is why I filed the upstream report based on the behaviour there instead of in de.
I'll try and see how things work with the trackpad tomorrow when I'm at my Mac, but it's harder to say definitively since there's no discrete "clicks" that should definitively cause/not cause an event with a trackpad

Ok, I tried examples/basic, and I can confirm that the scroll events from touch pad are abou equivalent as from mouse, not better. Events from the mouse scroll wheel are not great.
Scrolling down maps to button -1, and scrolling up maps to button -2. But there's no 1 to 1 mapping from scroll wheel to event. Instead, if you move the scroll wheel slowly, it takes about 10 scroll clicks before a single button event is generated. If you move it quickly, due to scrolling acceleration, you get many -1 button events all at once.

@nigeltao/@crawshaw Okay, a little more digging: the events on the trackpad are also screwed up. I added a note to golang/go#16020 about the trackpad and mouse system settings interacting in shiny, but as far as this issue goes: the trackpad seems far too sensitive, and the mouse either not sensitive enough or too sensitive depending on how fast you scroll the wheel.
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:912, Y:603, Button:-2, Modifiers:0x0, Direction:0x0}

Those are the events I got in basic from scrolling with 2 fingers at a relatively slow speed about 1-2mm on the trackpad.
I get no events if I scroll 1 click with a physical mouse wheel, as I said, and these are the events I get if I scroll three clicks relatively quickly:
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}
got mouse.Event{X:493, Y:538, Button:-2, Modifiers:0x0, Direction:0x0}

I can change the number of pixels that are scroll event moves from 50 pixels to 7 (a magic number that I thought I remembered seeing in cocoa.m, but can't find now..), but then a scroll event wouldn't scroll nearly enough under X11 or other drivers.

I think the only two real driver problems are golang/go#16152 and golang/go#16020.
The rest of the bugginess is on my end and/or I can work around with build tags.

The de side of this should be fixed now. As far as I know, all that's outstanding is golang/go#16152. If you notice any other problems, file a new ticket..


Newsletter appears to fail to extract body from very simple html page

Problem: extract content from this page
Expected result:
newspaper.html =

    <title>Test title</title>

Simplest.

newspaper.text = "Simplest."
Observed:
newspaper.html is correct, but newspaper.text is blank.

Newspaper has minimum length requirements for extracting  an article.text .
reference from the code:
 def is_valid_body(self):
    """If the article's body text is long enough to meet
    standard article requirements, keep the article
    """

Thanks. So working as intended I guess. Fair enough given how much noise there is on small pages.


Sync to www-covidcast release v10.0.0

Syncing covidcast_utils files to www-covidcast release v10.0.0.

This is an automated test PR for https://github.com/cmu-delphi/www-covidcast/pull/1216! We may or may not want to merge this - @melange396?

it doesnt matter too much either way.  we dont need to because theyre already present in #1155 where they are actually used.  on the other hand, we could merge them in now if you want to try to see what happens when the workflow is run but the files have not changed.

@krivard this "release version" is arbitrarily picked, since this is just a fully automated test PR. I can rename this PR/commit so there's no confusion about a 10.0.0 actually existing :)


Feat/remove vtk from scalismo

Removes all VTK dependent functionality from Scalismo. This is mainly IO and format conversion.
Upstream of this branch needs to be reset to main after the pending MRs are merged in. This branch contains the current version of the MRs.
All vtk dependent tests have been moved to scalismo-vtk and commented out in this MR.
Missing: The gaussianSmoothing has been commented out from GaussianGradientImagePreprocessor. We need to find another way to implement this in scalismo.
By removing the VTK dependency, a simple scalismo.jar app goes from +700MB to ~40MB.
This is the last part of removing the VTK dependency from Scalismo, https://github.com/unibas-gravis/scalismo/issues/415

Beside moving all VTK dependent functionality out of scalismo, we also move all active shape model code to a separate repository: https://github.com/unibas-gravis/scalismo-asm

ASM removed from the code and outcommented tests. I already rebased it to be on top of the release-1.0 branch.
So I would say that it can be merged in - it does include the decimator that is still under rewriting and with a bug, bug we have a separate MR open for that. We should just not make a RC before that is fixed and tested.


Please can you add the current days Gas m3 usage

Currently there is a Gas sensor for accumulative consumption in m3 for the previous period, however there is no corresponding entity for the current accumulative period, is it possible that could be created ?
The following sensor shows consumption in m3 for the previous period:-
sensor.octopus_energy_gas_xxx_yyy_previous_accumulative_consumption
Is it possible to create the corresponding sensor in m3 for the current period, i.e.:-
sensor.octopus_energy_gas_xxx_yyy_accumulative_consumption

Hello.
There is not currently a corresponding sensor because the Home Mini only reports in kwh. The two sensors exist for the previous consumption because originally the energy dashboard only accepted m3 data, but the APIs reported in either m3 or kwh depending on the smart meter. Therefore I reported both so that people got the actual reported value for their meter, and then a potentially estimated one for the energy dashboard.
If I was to add a sensor, it would be estimated like it is in certain scenarios for the previous consumption sensors. Out of curiosity, what is your use case for requiring this sensor?

Hi Dave.
Since I moved over to Octopus I noticed that the IHD doesn't show the actual cost of both Electric and Gas if you are on one of their intelligent rates, because the IHD doesn't know/use the correct rates, which makes the IHD a waste of time to be honest.
Using your integration allows me to pull actual usage and correct tariff rates from my Smart Meter to enable me to create a similar IHD display but with the correct costs calculated etc.
However I have noticed that on the Octopus website the Gas usage is calculated and displayed as m3, so I was hoping the current m3 Gas usage could be shown to allow me to compare whats displayed on the Octopus website.

This should now be available in the latest release (v10.0.0)

Thanks Dave, much appreciated.


ULTRA Use policy parameter from param.yaml inside baseline agent spec

Problem : Upon fixing the encoder issue #618 , we spotted that the encoder key with other social vehicle information was passed into the adapter. The information was hardcoded and was not linked to any of the policies' params.yaml. To retrieve the correct policy parameter and social vehicle information, we need to extract it from the params.yaml

Solution : Extract the social vehicle information from policy parameters which is retrieved from the params.yaml

Issue closed on behalf of PR #620


Add Include not-lastest-version: Part 1: client-side to grpc folders

Contributes to fixing #32886
1st of a few PR's.  This PR covers folders of content in alpha order from client-side to grpc.  148 files.
[!INCLUDE[](~/includes/not-latest-version.md)] was inserted with one blank line above and below it existing after the edit.
Only files that met all of the following conditions received the inserted text:

Is a .md file.
Has versioning, indicated by :::Moniker range inline or monikerRange in the metadata
Does not already have [!INCLUDE[](~/includes/not-latest-version.md)] in it.
Is not an include file.
Does not start with an H2 "##" before instead of an H1.
Is not a README.md file (A few of these are in sample folders but are not accessible from the TOC).

Internal previews
Toggle expand/collapse

📄 File
🔗 Preview link

aspnetcore/client-side/dotnet-interop.md
Run .NET from JavaScript

aspnetcore/client-side/spa-services.md
Use JavaScript Services to Create Single Page Applications in ASP.NET Core

aspnetcore/data/ef-rp/crud.md
Part 2, Razor Pages with EF Core in ASP.NET Core - CRUD

aspnetcore/data/ef-rp/intro.md
Razor Pages with Entity Framework Core in ASP.NET Core - Tutorial 1 of 8

aspnetcore/diagnostics/asp0000.md
aspnetcore/diagnostics/asp0000

aspnetcore/diagnostics/asp0001.md
ASP0001: Authorization middleware is incorrectly configured

aspnetcore/diagnostics/asp0003.md
"ASP0003: Do not use action results with route handlers"

aspnetcore/diagnostics/asp0004.md
ASP0004: Do not use action results with route handlers

aspnetcore/diagnostics/asp0005.md
aspnetcore/diagnostics/asp0005

aspnetcore/diagnostics/asp0006.md
ASP0006: Do not use non-literal sequence numbers

aspnetcore/diagnostics/asp0007.md
"ASP0007: Route parameter and argument optionality is mismatched"

aspnetcore/diagnostics/asp0008.md
ASP0008: Do not use ConfigureWebHost with WebApplicationBuilder.Host

aspnetcore/diagnostics/asp0009.md
aspnetcore/diagnostics/asp0009

aspnetcore/diagnostics/asp0010.md
ASP0010: Do not use UseStartup with WebApplicationBuilder.WebHost

aspnetcore/diagnostics/asp0011.md
"ASP0011: Suggest using builder.Logging over Host.ConfigureLogging or WebHost.ConfigureLogging"

aspnetcore/diagnostics/asp0012.md
ASP0012: Suggest using builder.Services over Host.ConfigureServices or WebHost.ConfigureServices

aspnetcore/diagnostics/asp0013.md
aspnetcore/diagnostics/asp0013

aspnetcore/diagnostics/asp0014.md
ASP0014: Suggest using top level route registrations

aspnetcore/diagnostics/asp0015.md
"ASP0015: Suggest using IHeaderDictionary properties"

aspnetcore/diagnostics/asp0016.md
ASP0016: Do not return a value from RequestDelegate

aspnetcore/diagnostics/asp0017.md
aspnetcore/diagnostics/asp0017

aspnetcore/diagnostics/asp0018.md
ASP0018: Unused route parameter

aspnetcore/diagnostics/asp0019.md
ASP0019: Suggest using IHeaderDictionary.Append or the indexer

aspnetcore/diagnostics/asp0020.md
"ASP0020: Complex types referenced by route parameters must be parsable"

aspnetcore/diagnostics/asp0021.md
ASP0021: The return type of the BindAsync method must be ValueTask<T>.

aspnetcore/diagnostics/asp0022.md
aspnetcore/diagnostics/asp0022

aspnetcore/diagnostics/asp0023.md
ASP0023: Route conflict detected between route handlers

aspnetcore/diagnostics/asp0024.md
"ASP0024: A route handler has multiple parameters with the [FromBody] attribute"

aspnetcore/diagnostics/asp0025.md
ASP0025: Use AddAuthorizationBuilder to register authorization services and construct policies.

aspnetcore/diagnostics/bl0001.md
aspnetcore/diagnostics/bl0001

[!NOTE]
This table shows preview links for the 30 files with the most changes. For preview links for other files in this PR, select OpenPublishing.Build Details within checks.

Closing and reopening for a fresh build.

@Rick-Anderson or @tdykstra , I am getting blocking warnings on the aspnetcore/includes/not-latest-version.md itself.  Am I inserting or using it in a way that it was not intended possibly? Or perhaps we are just getting new build check warnings we did not get before?

@guardrex, you have been using this not-latest-version include for blazor content successfully.  I don't know the history on it.  Was it intended to included only for very for specific versions of doc with specific ranges?  See the build errors on this PR.

@Rick-Anderson or @tdykstra , I am getting blocking build warnings on the aspnetcore/includes/not-latest-version.md itself. Am I inserting or using it in a way that it was not intended possibly? Or perhaps we are just getting new build check warnings on that include we did not get before?

I had the same error and @tdykstra showed me how to fix it. I don't remember the fix.

It can't be used in files that are versioned for the current release (or later). What I do is leave it in place commented out with a searchable comment for activation. For example ...
https://github.com/dotnet/AspNetCore.Docs/edit/main/aspnetcore/blazor/components/sections.md
When 9.0 comes out, and I search "UPDATE 9.0" in the Blazor node (which will return a bunch of little things that I need to do around the Blazor docs when I'm working 9.0 tasks), I activate them.
What you'll have to do is search out all files with either "monikerRange: '>= aspnetcore-8.0'" or "monikerRange: '>= aspnetcore-9.0" and either remove the INCLUDE links or comment them out as I have. Any that have it for docs versioned >=8.0 can be activated when 9.0 releases. Any that have it for docs versioned >=9.0, won't be able to activate it until 10.0 releases.

After discussing with TDykstra and including gaurdrex helpful info, it sounds like there are 3 conditions involved:
If the doc meta data at the top of the page has a monikerRange of:
monikerRange: '>= aspnetcore-8.0'
Then insert this just below the H1 (#):
<!-- UPDATE 9.0 Activate after release and INCLUDE is updated
[!INCLUDE[](~/includes/not-latest-version.md)]
-->

If the doc meta data at the top of the page has a monikerRange of:
:::moniker range=">= aspnetcore-9.0"
Then insert this just below the H1 (#)
[!INCLUDE[](~/includes/not-ga-yet.md)]

<!--
[!INCLUDE[](~/includes/not-latest-version.md)]
Uncomment this when 9.0 is the default value in the version selector and delete not-ga-yet.md
-->

If the doc meta data at the top of the page has a monikerRange that is anything <8.0:
Then insert this just below the H1  (#):
[!INCLUDE[](~/includes/not-latest-version.md)]

I will close this and do a much smaller number of files at a time until I am confident it all seems to work.

That all sounds right to me. The only piece that I'm not doing right now is the [!INCLUDE[](~/includes/not-ga-yet.md)] bit, but I don't have new 9.0+ Blazor docs coming in for this release. I'd use that in the future tho, but I'd always mark it in the comment with "UPDATE 9.0" so that I can search them out later to find them (as you showed in your first example). The "UPDATE {VERSION}" comments have been super helpful 🦸 in avoiding having to litter the repo with issues or keep a long list of things that I need to check and update later.


Enable Progressive Web App (PWA) for the site

A PWA or Progressive Web Application allows users to install the site as a desktop or android application. It will enhance user experience and drive organic traffic. It also allows users to access the site offline by pre-downloading assets such as files or images as cache memory.

Enabling Progressive Web Apps (PWAs) enhances a website by providing a native app-like experience with several key benefits:

Offline Access: Users can access content without an internet connection.
Fast Loading: PWAs load quickly, improving performance even on slow networks.
Home Screen Installation: Users can install PWAs on their devices without app store hassles.
Push Notifications: Engage users with timely notifications, even when the app isn’t open.
Responsive Design: PWAs work seamlessly across different devices and screen sizes.

ASSIGN AND ADD LEVEL 3 THANKYOU @param-code

A PWA or Progressive Web Application allows users to install the site as a desktop or android application. It will enhance user experience and drive organic traffic. It also allows users to access the site offline by pre-downloading assets such as files or images as cache memory.
 Enabling Progressive Web Apps (PWAs) enhances a website by providing a native app-like experience with several key benefits:

Offline Access: Users can access content without an internet connection.
Fast Loading: PWAs load quickly, improving performance even on slow networks.
Home Screen Installation: Users can install PWAs on their devices without app store hassles.
Push Notifications: Engage users with timely notifications, even when the app isn’t open.
Responsive Design: PWAs work seamlessly across different devices and screen sizes.

ASSIGN AND ADD LEVEL 3 THANKYOU @param-code

Okay.I am assigning you this @amiya-cyber .All the Best!!

hello @param-code I think this deserves atleast level 2 or level 3 bcoz i will be adding three new files to the project and in fact this is a unique feature

will see later.