Add arrow navigation to remaining popover menus

This enables arrow navigation for the series block sorting menus and the menus for adding block content.
Waiting for https://github.com/opencast/appkit/pull/3, which is needed in order for this to work.
Together they will close #753.

The view/order buttons of series blocks currently don't do anything when clicked or otherwise activated. I suppose the onClick handler just needs to be specified after the getItemProps or whatever.

Good catch, that fixes it.


Bracket pair highlighting issue for double brackets in markdown

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.78.2 (Universal)
OS Version: Darwin x64 22.5.0

Steps to Reproduce:

Create a markdown file with the following content:
[[test]]

The highlight is:

When setting editor.bracketPairColorization.enabled to false, then it will be correct.

I believe this is actually an issue with the markdown grammar's highlighting. Opened https://github.com/microsoft/vscode-markdown-tm-grammar/issues/146 to track this


WaveOut(Event).GetPosition() wraps around after a few hours

The implementation of GetPosition() for the WaveOut(Event) devices uses the waveOutGetPosition() with the TIME_BYTES setting.
The MMTIME struct only has a 32-bit DWORD to report the number of bytes.
This wraps around quite quickly. For example, at 48 kHz stereo playback, you will get a wraparound at 3 hours, 6 minutes and 25 seconds.
I had to create a workaround in my code to detect when the position wraps around, and then add 0x100000000L to the position myself, to compensate.
It would be nice if the WaveOut(Event) device implements the handling of wraparound internally.
Other implementations such as WASAPI and DirectSound do not have this problem.

I recommend using WasapiOut now. The WaveOut APIs are legacy windows APIs, and WasapiOut does everything that WaveOut can and more.

I actually moved away from WasapiOut because WaveOut has one nice advantage: it is hot-pluggable. You connect to a virtual device, and when Windows selects a new device, because a device is connected or disconnected, things just keep going.
With WasapiOut you connect to a physical device, and you manually need to detect whether your device is still available, and handle changes manually.
We have situations where systems may run 24/7, connected to displays with HDMI audio, where the displays may go in standby or turned off altogether sometimes.
With WasapiOut this always turned out to be somewhat haphazard. WaveOut was far more forgiving, and tended to 'just work', as Windows would take care of handling the devices.


react-map-gl 7 support

I'm currently int the process of updating react-map-gl to version 7 but get compilation errors (originating from react-map-gl-geocoder) saying:
Attempted import error: 'FlyToInterpolator' is not exported from 'react-map-gl' (imported as 'r').
And FlyToInterpolator seems to have been removed (https://visgl.github.io/react-map-gl/docs/upgrade-guide#upgrading-to-v70). Are there any plans of supporting version 7?

Sorry, no plans. It's possible that I'll do it at some point, but it probably won't be anytime soon. I usually suggest people just copy pasta the code and modify it for their needs especially since I don't really work on this project anymore. https://github.com/SamSamskies/react-map-gl-geocoder/blob/master/src/index.js

I understand. Well, thanks for the quick and informative answer. Appreciate it!

hi everyone, what is the solution here? Does downgrading just react-map-gl help or do I need to downgrade both react-map-gl and react-map-gl-geocoder? Many thanks much appreciated!

hi everyone, what is the solution here? Does downgrading just react-map-gl help or do I need to downgrade both react-map-gl and react-map-gl-geocoder? Many thanks much appreciated!

just React-Map-GL

Haven't tried it yet myself, but just noticed that the release notes say that you don't need a react wrapper for geocoder any more.
https://visgl.github.io/react-map-gl/docs/whats-new#react-map-gl-v70

Compatibility: first and third-party plugins! Directly use mapbox-gl-draw, mapbox-gl-geocoder, to name a few.

good advice @joelugh
Another option is to recreate the react-map-gl v7 geocoder example

Haven't tried it yet myself, but just noticed that the release notes say that you don't need a react wrapper for geocoder any more.
https://visgl.github.io/react-map-gl/docs/whats-new#react-map-gl-v70

Compatibility: first and third-party plugins! Directly use mapbox-gl-draw, mapbox-gl-geocoder, to name a few.

Hey @joelugh, did you end up trying this?

hi everyone, what is the solution here? Does downgrading just react-map-gl help or do I need to downgrade both react-map-gl and react-map-gl-geocoder? Many thanks much appreciated!

just React-Map-GL

Which version do you downgrade to?


Add cpu generation or cpu complete details

A benchmark could vary a lot from a cpu gen 1 and a cpu gen 10.
Example : an i7 - 930 (generation 1) desktop cpu is pretty slow in comparison to an i5 - 10210u (generation 10) mobile version. Same happen to Ryzen cpu's

@kikislater good tip - I will look at this.


RESTify Leonardo VIA URL

encode Leonardo state (enable/disable and the selected scenario) in the URL so you can share a link with specific use case configuration.
What do you say ?

Will start with a simple scenario export/import via url

cool, keep it rolling

:+1: :8ball: :8ball: :8ball:

Closing untill this becomes a priority


Fix TSLint warnings in msbot-connect-bot.ts

Related to #313
Proposed Changes
Fix the following warnings in the file msbot-connect-bot.ts:

typedef
no-any
interface-name
whitespace
no-empty
prefer-const
cyclomatic-complexity
one-line
curly
triple-equals
semicolon
newline-before-return
eofline

Testing
Travis will no longer report this issue.

Pull Request Test Coverage Report for Build 625

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.258%

Totals

Change from base Build 622:
0.0%

Covered Lines:
2836

Relevant Lines:
3526

💛  - Coveralls


add support for OpenSSL 1.1.x

that's all I have/need...!

[@zandbelt looking for discussion before actual code changes]
The more I go through the changes to cjose_set_alloc_funcs(), the less comfortable I am.
I wonder if it would be acceptable to separate out the "simple" alloc|realloc|dealloc functions from the file+line alloc|realloc|dealloc functions.  For example:
void cjose_set_alloc_funcs(cjose_alloc_fn_t, cjose_realloc_fn_t, cjose_dealloc_fn_t);
void cjose_set_alloc_ex_funcs(cjose_alloc3_fn_t, cjose_realloc3_fnt_t, cjose_dealloc3_fn_t);

Further, I'd be more inclined to define default implementations of cjose_(de|re|)alloc3_fn_t that can be passed to OpenSSL 1.1.x's CRYPTO_set_mem_functions(), even if this means real file/line values are lost (unless you call the _ex version).
To me, that eliminates the breaking change to cjose_set_alloc_funcs() while still supporting OpenSSL 1.1.x's allocators.

yes, that makes sense; I did not like the changes much myself either; stay tuned

I'm getting compiler errors, but have a branch with the fixes: https://github.com/linuxwolf/cjose/tree/openssl-1.1.x
But I am a little concerned about the dev experience of cjose_set_alloc_ex_funcs().  It feels really clunky, and I wonder if developers will get really turned off with this model.  It seems to me that it would make for a better experience to require the user to either set "basic" allocator/deallocator sets OR set "enhanced" allocator/deallocator sets, rather than both.
I'm going to put together a throwaway prototype to express what I mean.

Here is the changeset for a mutually exclusive cjose_get_alloc_funcs()/cjose_get_alloc_ex_funcs(): https://github.com/linuxwolf/cjose/commit/8b82d3085ee3e00c95eeb2bb4432472fc4290783
Let me know what you think @zandbelt

that looks better indeed


Add "Premium block blobs" in "Supported Azure Storage services"

Add "Premium block blobs" in "Supported Azure Storage services" table [https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy#supported-azure-storage-services] according to the other table "Supported storage account types" [https://learn.microsoft.com/en-us/azure/storage/common/storage-redundancy#supported-storage-account-types]

@jimmart-dev
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

emailed jimmart-dev

IM'd author

@lucabovo Hi Luca. Thanks for bringing this to our attention.  See this for a list of services:
https://learn.microsoft.com/en-us/azure/storage/common/storage-introduction#azure-storage-data-services
With that said, I noticed that "Page blobs" is listed in the storage services table under LRS, which is not a storage service either. I am opening a new PR to clean up and verify those tables.

#please-close


Nuget Package Broken?? (beta7-13983)

Hi, I'm trying to get EF7 running for the first time using VS2015 .Net (4.6) (also tried 4.5)
Following the Wicki Get Started Guide.
First this is when I do the "Add-Migration MyFirstMigration" step from the nugget console I get
"Exception has been thrown by the target of an invocation."
If I try and run the app I get the following exception from the DbContext constructor.
An unhandled exception of type 'System.TypeInitializationException' occurred in EntityFramework.Core.dll
Additional information: The type initializer for 'System.Collections.Immutable.ImmutableDictionary`2' threw an exception.
Is the Nuget package broken, of does it need some voodoo.
Thanks

Try to add this to your app.cofig:
<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
  <dependentAssembly>
    <assemblyIdentity name="System.Collections.Immutable" publicKeyToken="b03f5f7f11d50a3a"/>
    <bindingRedirect oldVersion="<IP_ADDRESS>" newVersion="<IP_ADDRESS>"/>
  </dependentAssembly>
  </assemblyBinding>
  </runtime>

Yes, use a binding redirect. Roslyn is compiled against 1.1.36, but the latest is 1.1.37.

Dupe of https://github.com/aspnet/EntityFramework/issues/2855


Switch shader on runtime: Compile directive in cginclude file appears to be ignored

When switching between the HoloToolkit shaders on runtime, for some shaders the materials "lose" their color, i.e. they are rendered in white, the default.
This apparently happens when using a shader that has the shader feature _USECOLOR_ON. (e.g. BlinnPhongConfigurable.shader)
Neither does material.SetFloat("_UseColor", 1); help, nor adjusting the shader to have the feature enabled by default.
So I commented out the according compile directives in the .cginc files:
//#if _USECOLOR_ON
float4 _Color;
//#endif

[...]

//#if _USECOLOR_ON
     c *= _Color;
//#endif

which helped me achieve what I wanted.
Still, there appears to be a problem when trying to access the _USECOLOR_ON keyword

@dbastienMS, any idea about this?

shader_feature doesn't compile all paths, just the used ones.  you can swap it out for multi_compile to get the behavior you want.  Ideally though you'd be using the fast configurable shader and not the earlier ones.  We need to blow them all away and move the samples over to fc.  Fast configurable is much lower per-pixel ALU ops for the same quality level.


Enhance title and author options

Proposal 1
Usage
<<title: subtitle: subsubtitle>> composers (arrangers) - lyricists (poets)

Syntax
titles_and_authors := titles S? authors S? NL

titles :=  '<<' S? title (':' S? subtitle (S? ':' S? subsubtitle S?)? )? S?>>
authors := composers? S? ( '(' arrangers ')' )? S? ( '-' S?  lyricists)

composers := author_list
arrangers := author_list
lyricists := author_list
author_list := author S? (',' author)*

title := words
subtitle := words
subsubtitle := words
author := words
words := [\w\s]+

Proposal 2
poets - lyricists <<title:subtitle:subsubtitle>> composers - arrangers

The proposal 1 is my first thought; however, I am in favor of proposal 2 due to its symmetric manner.

New syntax features are now moves to the musje-123-notation repository.


Use go-extpoints to establish an LndStart extension point

This is a proof of concept / example of using go-extpoints to add extension
points. In this case we add LndStart which is used to trigger behavior on
startup. The intention is to establish extension points wherever necessary to
attach behavior such as monitoring, etc, without having to add direct
dependencies to LND.

This is relative to #1355, as an alternative way of providing prometheus integration. In this way we could provide the necessary extension points to allow for an lnd-prometheus package to allow for integration.

wip: Fixing lints

Closing for further development.


make png save as parallel

Lightmap baker stops when we save image, but it should not.
So we have to run png save in parallel to prevent program stopping.

fixed issue in this commit : d740df19894b70019768dda0be53d2a3fe371301


Fix typo transitionDisposables

@niharu if the intent is to fix disposeables => disposables, maybe you check for more in our code? There seems to be more usages when I search.


ValueError: num_samples should be a positive integer value, but got num_samples=0

Hello, in root directory i did "git lfs pull", and my files in path "ckpt/backbone/"
decoder_epoch_20.pth has 162.5Mb
encoder_epoch_20.pth has 95Mb
When I run ./train.sh I have:
Loading weights for net_encoder @ ckpt/backbone/encoder_epoch_20.pth
Loading weights for net_decoder @ ckpt/backbone/decoder_epoch_20.pth
Traceback (most recent call last):
File "main.py", line 521, in
fire.Fire(LSDTrainer)
File "/home/user/anaconda3/envs/ppgnet/lib/python3.6/site-packages/fire/core.py", line 127, in Fire
component_trace = _Fire(component, args, context, name)
File "/home/user/anaconda3/envs/ppgnet/lib/python3.6/site-packages/fire/core.py", line 366, in _Fire
component, remaining_args)
File "/home/user/anaconda3/envs/ppgnet/lib/python3.6/site-packages/fire/core.py", line 542, in _CallCallable
result = fn(*varargs, **kwargs)
File "main.py", line 121, in init
pin_memory=True
File "/home/user/anaconda3/envs/ppgnet/lib/python3.6/site-packages/torch/utils/data/dataloader.py", line 176, in init
sampler = RandomSampler(dataset)
File "/home/user/anaconda3/envs/ppgnet/lib/python3.6/site-packages/torch/utils/data/sampler.py", line 66, in init
"value, but got num_samples={}".format(self.num_samples))
ValueError: num_samples should be a positive integer value, but got num_samples=0

It sounds like you didn't download and extract properly.  Did you download the dataset, then change the --data-root flag in the train.sh script to be where you downloaded the data?

I think @rayryeng is right. I added an assertion in the main.py script to provide more friendly error messages about this problem.


Testing Multiple SSH Supported Flist Deployments Progression

Is there an existing issue for this?

[X] I have searched the existing issues

which package/s did you face the problem with?
Dashboard
What happened?
Testing Images for VMs for supporting using multiple of ssh on vms
MicroVMs

[x] ubuntu 24.04
[x] ubuntu 22.04
[x] centos 08
[x] alpine 3
[x] Debian 12

Fullvms

[x] ubuntu 24.04
[x] ubuntu 22.04

Docs to be clear
Also making sure that every flist has its clear docs and env variables declared.

ubuntu 24.04
Tested image with multiple ssh and working fine

ubuntu 22.04
tested and working fine using multiple ssh

centos 08
tried multipe deployments but did not work with multiple ssh

same for alpine 3

Debian 12
worked fine with multiple ssh

@ramezsaeed @PeterNashaat shall we close this or there any more images to test ?

subsquid
worked fine with multiple ssh

https://github.com/threefoldtech/tf-images/issues/280
https://github.com/threefoldtech/tf-images/issues/231

Presearch
worked fine with multiple ssh

https://github.com/threefoldtech/tf-images/issues/280
https://github.com/threefoldtech/tf-images/issues/231

Presearch
worked fine with multiple ssh

https://github.com/threefoldtech/tf-images/issues/280
https://github.com/threefoldtech/tf-images/issues/231

Presearch
worked fine with multiple ssh

https://github.com/threefoldtech/tf-images/issues/280
https://github.com/threefoldtech/tf-images/issues/231

discourse also verified and tested

umbrel also verified


Simplify top level of the SMARTS repo

There are 35+ items at the top level of the SMARTS repo. Will be nice if we can reduce this down to somewhere between 10 and 20. It'll hopefully be easier for users to navigate the project and understand it structure.

A few proposals:

Move the ./cli/, ./zoo/ and ./envision/ folders into ./smarts/.

(./zoo/ will have to be appropriately combined with `./smarts/zoo/.)

Make a new ./etc folder and put the following in it:

setup/

install_deps.sh
requirements.txt
setup.py
test_pip_packages.sh

docker/

Dockerfile
Dockerfile.minimal

(the stuff in the ./extras/ folder)
(the stuff in the ./third_party folder)

Make a new bin/ folder and move the following into it:

header_test.sh
gen_header.sh

Move the stuff in the ./tools/ folder into ./examples/ and/or ./etc/.
Move the ./benchmark/ folder down from the top level to somewhere appropriate (not sure where, since I don't really know it's history or rationale).


Auth error again?

Is it just me and my code which isn't working or anyone else have problems with authentication?
Basic authentication test with code example on readme.md returns also errors.
--- Error finding meta_tag
Traceback (most recent call last):
devices = client.get_devices()
File "/usr/local/lib/python3.9/site-packages/pcomfortcloud/apiclient.py", line 38, in get_devices
self._get_groups()
File "/usr/local/lib/python3.9/site-packages/pcomfortcloud/apiclient.py", line 28, in _get_groups
self._groups = self._auth.execute_get(
File "/usr/local/lib/python3.9/site-packages/pcomfortcloud/session.py", line 59, in execute_get
return super().execute_get(url, function_description, expected_status_code)
File "/usr/local/lib/python3.9/site-packages/pcomfortcloud/authentication.py", line 389, in execute_get
check_response(response, function_description, expected_status_code)
File "/usr/local/lib/python3.9/site-packages/pcomfortcloud/authentication.py", line 25, in check_response
raise exceptions.ResponseError(
pcomfortcloud.exceptions.ResponseError: (get_groups: Expected status code 200, received: 401: {"code":"4100", "message": "Token expires"}
I haven't done any changes into my code and tried login from different locations to check if there's something with network. iOS app works fine. I can read that it says Token expires but isn't it suppose to renew if expired?

I also have the same behaviour.
The token expires but a new one is generated. It will work fine the next time.
It would be better if this error is intercepted and pcomfortcloud tries again transparently after a new token is created.

In my case it doesn't renew token. I call api every 30min, which has been interval in my case at least year now. At the moment I commented out that cronjob just to see if time would fix this 😬 I'm going to put it back "online" later and see what happens.

Hi. I am currently also not able to use bacause of "New version app has been published" issue:
Traceback (most recent call last):
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud.py", line 301, in
main()
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud.py", line 214, in main
session.start_session()
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud/apiclient.py", line 28, in start_session
super().start_session()
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud/session.py", line 303, in start_session
self._get_new_token()
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud/session.py", line 280, in _get_new_token
check_response(response, 'get_acc_client_id', 200)
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud/session.py", line 27, in check_response
f"{response.text}"
pcomfortcloud.exceptions.ResponseError: (get_acc_client_id: Expected status code 200, received: 401: {
"code":4106,
"message":"New version app has been published"

Still login issue here also. Not 403 but 401. I left script alone for couple days and just tried it with no luck :/

401 is Unauthorized.
You can try to login using the smartphone Comfort Cloud application to check your password is still valid. Maybe you have to accept new EULA, etc.

Hi. Not a problem with a password (still using the same) and using app on a daily basis, so login there is working, not new EULA, nothing. Right now getting this error:
pi@automation:~ $ python3.7  /home/pi/python-panasonic-comfort-cloud/pcomfortcloud.py<EMAIL_ADDRESS>XXX set --power On --temperature 18 -f Auto -m Cool -e Auto -y UpMid -x RightMid 1
--- Error finding meta_tag
Traceback (most recent call last):
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud.py", line 301, in
main()
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud.py", line 214, in main
session.start_session()
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud/apiclient.py", line 28, in start_session
super().start_session()
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud/session.py", line 301, in start_session
self._refresh_token()
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud/session.py", line 333, in _refresh_token
check_response(response, 'refresh_token', 200)
File "/home/pi/python-panasonic-comfort-cloud/pcomfortcloud/session.py", line 27, in check_response
f"{response.text}"
pcomfortcloud.exceptions.ResponseError: (refresh_token: Expected status code 200, received: 403: {"error":"invalid_grant","error_description":"Unknown or invalid refresh token."}

401 is Unauthorized.
You can try to login using the smartphone Comfort Cloud application to check your password is still valid. Maybe you have to accept new EULA, etc.

I'm using app with same password with out any issues. I think EULA isn't issue either in my case.

I can look into it, and I think we discussed a issue related to this earlier. Maybe there is an issue if the refresh token expires

Yeah, I solved this just by downloading whore repository from github again and it works great again.
What would be interesting to see why this came to this error from which the system cannot recover. It is still reproducible as I kept the original (now non-working) installation if needed for any test.

The meta tag thingy should be solved by #105 . I close this now until we get more information related to 401/403


Inquiry for token retrieval failure using first party application with MSALV1

Core Library
MSAL.js v1 (@azure/msal or msal)
Core Library Version
2.18.0
Wrapper Library
Not Applicable
Wrapper Library Version
n/a
Description
I am making a call to get token using my first party application for some new feature work, but an encountering a time out. Could someone please help me lookt into the logs to see whats going on?
request url:
Request URL: https://login.microsoftonline.com/3c79fde3-e9cf-4819-b103-e11991afbd37/oauth2/v2.0/authorize?response_type=id_token token&scope=https%3A%2F%2Fgraph.microsoft.com%2F.default openid profile&client_id=e29b5c86-b9ab-4a86-9a20-d10842007599&redirect_uri=https%3A%2F%2Ftesta190720221053-admin.sharepoint.com%2F_forms%2Fspfxsinglesignon.aspx&state=eyJpZCI6IjM1ZjRlYzYwLTM5YmYtNGJjMC1iZjNkLTYzZmIyZWNjNWQ4NCIsInRzIjoxNjU4NDI4MDI4LCJtZXRob2QiOiJzaWxlbnRJbnRlcmFjdGlvbiJ9&nonce=d6e4c30e-0a74-4a15-8b2c-901339c2111f&client_info=1&x-client-SKU=MSAL.JS&x-client-Ver=1.4.12&sid=08393b96-e3a2-4df5-b8e1-a96acb5eb10d&client-request-id=a89090bf-caaf-4fc3-8052-c1595e116ce9&prompt=none&response_mode=fragment
response headers:
x-ms-request-id: 083ec020-2080-434c-a2dc-6b4e37493c01
Thu, 21 Jul 2022 18:27:08 GMT
MSAL Configuration
No response
Relevant Code Snippets
No response
Identity Provider
No response
Source
Internal (Microsoft)

Resolved offline. App registration was not configured for implicit grant


The remote endpoint could not be called, or the response it returned was invalid.

I am new at developing with alexa. I followed to tutorial but when I get into the testing section it gives me an error:
The remote endpoint could not be called, or the response it returned was invalid.
Don't know what I did wrong - the arn is copied correctly.
I'm following the tutorial here: https://developer.amazon.com/alexa-skills-kit/tutorials/fact-skill-4
I am facing the issue in both N Virginia and Ireland regions

In Cloudwatch logs, this is the error I am getting:
{
"errorMessage": "No 'Unhandled' function defined for event: Unhandled",
"errorType": "Error",
"stackTrace": [
"AlexaRequestEmitter.EmitEvent (/var/task/node_modules/alexa-sdk/lib/alexa.js:194:15)",
"AlexaRequestEmitter.ValidateRequest (/var/task/node_modules/alexa-sdk/lib/alexa.js:160:23)",
"HandleLambdaEvent.i18n.use.init (/var/task/node_modules/alexa-sdk/lib/alexa.js:113:29)",
"/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:190:9",
"done (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:281:21)",
"/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:302:7",
"I18n.loadResources (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:238:7)",
"I18n.changeLanguage (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:301:10)",
"load (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:186:14)",
"I18n.init (/var/task/node_modules/alexa-sdk/node_modules/i18next/dist/commonjs/i18next.js:195:7)"
]
}

Same issue as this - https://github.com/alexa/skill-sample-nodejs-fact/issues/26


Add a new way to record patches

Pull Request Test Coverage Report for Build 1701

173 of 200 (86.5%)  changed or added relevant lines in 13 files are covered.
18 unchanged lines in 8 files lost coverage.
Overall coverage increased (+1.2%) to 49.604%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

repairnator/repairnator-core/src/main/java/fr/inria/spirals/repairnator/serializer/SerializerType.java
0
2
0.0%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/step/repair/AstorRepair.java
3
5
60.0%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/step/repair/AbstractRepairStep.java
27
29
93.1%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/inspectors/JobStatus.java
12
14
85.71%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/pipeline/Launcher.java
0
4
0.0%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/inspectors/RepairPatch.java
8
15
53.33%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/notifier/PatchNotifier.java
35
43
81.4%

Files with Coverage Reduction
New Missed Lines
%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/step/paths/ComputeTestDir.java
1
73.13%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/step/repair/NPERepair.java
1
81.03%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/testinformation/FailureLocation.java
1
94.87%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/testinformation/FailureType.java
1
56.52%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/git/GitHelper.java
1
45.73%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/inspectors/JobStatus.java
2
82.05%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/pipeline/Launcher.java
2
0.0%

repairnator/repairnator-pipeline/src/main/java/fr/inria/spirals/repairnator/process/nopol/NopolInformation.java
9
58.62%

Totals

Change from base Build 1694:
1.2%

Covered Lines:
2191

Relevant Lines:
4417

💛  - Coveralls


Remove version: TheDocumentFoundation.LibreOffice.LTS version <IP_ADDRESS>

EOL'd
Microsoft Reviewers: Open in CodeFlow

URL: https://download.documentfoundation.org/libreoffice/stable/7.6.5/win/x86_64/LibreOffice_7.6.5_Win_x86-64.msi
Response Error: The remote server returned an error: (404) Not Found.
(Automated message - build 911)


Add API to switch renderer types

Based on this thread: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!topic/cornerstone-platform/oA6YWHaiLjU
We should consider adding a simple API for this, rather than just deleting properties from the enabledElement.

Issue was meant to be on Cornerstone...


Ford Fulkerson in C++ and Python

Hello, I am Aditya Sinha. I am participating in GSSOC'21 I would like to add code for Ford-Fulkerson algorithm in C++ and Python

Hello @rudrakshi99 @plazzy99 @shreyanspoddar @anjul2000
Please assign me this issue.

I would like to contribute to the above problem in java as I am a participant of GSSOC'21. Kindly assign this to me.


Fix typographical error(s)

@EverythingMe, I've corrected a typographical error in the documentation of the openspace project. Specifically, I've changed beatiful to beautiful. You should be able to merge this pull request automatically. However, if this was intentional or if you enjoy living in linguistic squalor, please let me know and create an issue on my home repository.

:+1:


[resolves #254] Unable to load custom exception in load balancer

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/wildfly-camel-pullreq/193/
Test PASSed.


Support CH option in addIfLess and addIfGreater for ScoredSortedSet

RedissonScoredSortedSet addIfLess and addIfGreater methods don't support CH option.
Is that possible to add such support?
E.g. introduce new methods changeIfLess and changeIfGreater which will run ZADD command with both CH and XX options

Fixed! Thanks for report


translate is not a function :)

So I changed it to translator.translate

Nice catch ! Thx :+1:

Cheers!


Use context menu on DashContainer tab headers for adding views

Hoist P/R Checklist
Pull request authors: Review and check off the below. Items that do not apply can also be
checked off to indicate they have been considered. If unclear if a step is relevant, please leave
unchecked and note in comments.

[X] Caught up with develop branch as of last change.
[X] Added CHANGELOG entry, or determined not required.
[X] Reviewed for breaking changes, added breaking-change label + CHANGELOG if so.
[X] Updated doc comments / prop-types, or determined not required.
[X] Reviewed and tested on Mobile, or determined not required.
[X] Created Toolbox branch / PR, or determined not required.

If your change is still a WIP, please use the "Create draft pull request" option in the split
button below to indicate it is not ready yet for a final review.

Pull request reviewers: when merging this P/R, please consider using a squash commit to
collapse multiple intermediate commits into a single commit representing the overall feature
change. This helps keep the commit log clean and easy to scan across releases. PRs containing a
single commit should be rebased when possible.

I think this looks great, as discussed.  We can further tweak discoverability and customizability if needed, but definitely gives more functionality and scalability with less ink


fix: add jsdoc

:tada: This PR is included in version 0.5.4 :tada:
The release is available on:

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Add new protobuf parameters

Description

Linked issue

Closes #{issue_number}

Benefits

Checklist

[ ] I've read CONTRIBUTING.md
[ ] I've used the standard signed-off commit format (or will squash just before merging)
[ ] All applicable CI checks pass (or I promised to make them pass later)
[ ] (optional) I've written unit tests for the code changes
[ ] I replied to all comments after code review, marking all implemented changes with thumbs up

It is implementation of an internship project: https://wiki.hyperledger.org/display/INTERN/Iroha+1%3A+extend+queries+with+optional+arguments
@dominious1 Please add more description and make the PR as draft pull request for now.

Please remember about adding --signoff flag once you commit any new change. Example:
git commit --signoff --message "Test msg"

@dominious1 I think that the PR can be closed. So I'm closing its. If You have time and want to do its after completing: https://github.com/hyperledger/iroha/pull/4003 we can reopen:)


Retry resource group deletion as it not always delete resource group

Few resource was left behind even when deletion operation finished. The same command is called to remove the rest leftovers.
REF:
https://buildkite.com/redpanda/helm-charts/builds/470#018985aa-71a4-4331-8f8e-f62c1bb9c054

Trying to re-trigger Github action pipelines

discussed with @RafalKorepta and I force merged the PR without meeting the gh status checks requirements, as nothing was triggered/related to this PR


pgdg-centos95-9.5-3.noarch.rpm 404 Not Found

Hi, thank you for an excellent tool for weather services, i have smartmet 2 years ago, but on abril th repos updates and failure macgyver, postgresq and other tools inside the smartmet enviroment.
I try to make a new install, but the repo of postgresql  pgdg-centos95-9.5-3.noarch.rpm show me the error "404 Not found".
I looking for the pgdg-centos95-9.5-3 in others repos but i haven't found it.
Thanks in advanced, may be you have other solution.
rpm -Uvh https://download.postgresql.org/pub/repos/yum/9.5/redhat/rhel-
7-x86_64/pgdg-centos95-9.5-3.noarch.rpm
Retrieving https://download.postgresql.org/pub/repos/yum/9.5/redhat/rhel-7-x86_64/pgdg-centos95-9.5-3
.noarch.rpm
curl: (22) The requested URL returned error: 404 Not Found
error: skipping https://download.postgresql.org/pub/repos/yum/9.5/redhat/rhel-7-x86_64/pgdg-centos95-
9.5-3.noarch.rpm - transfer failed

Hello,
The PGDG packages have been renamed. You can find the latest CentOS 7 RPM from
https://yum.postgresql.org/repopackages.php
or directly from
https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm
The name should remain the same in subsequent versions. Also note that the repo-file now contains all PGDG versions from 9.4 to 12, plus a new repository called pgdg-common.
We are still transitioning to use the new repository system, but managed to build new versions using
yum-config-manager --disable "pgdg*"
yum-config-manager --enable pgdg-common pgdg95
yum-config-manager --setopt="pgdg*.exclude=postgis*,libpqxx*" --save
We expect to be able to build the packages using the PostGIS version packaged by PGDG in the near future, until then we're packaging our own RPMs using the version in EPEL.

Thank you for your answer, i installed https://download.postgresql.org/pub/repos/yum/10/redhat/rhel-7-x86_64/pgdg-redhat-r
epo-42.0-11.noarch.rpm.
And when continue with the smartmet installation show me this Error from smartmet-library-macgyver.
Error: Package: smartmet-library-macgyver-20.4.18-1.el7.fmi.x86_64 (smartmet-open)
Requires: libpqxx-4.0.so()(64bit)
Available: 1:libpqxx-4.0.1-1.el7.x86_64 (epel)
libpqxx-4.0.so()(64bit)
Installed: 1:libpqxx-5.0.1-2.rhel7.1.x86_64 (@pgdg11)
~libpqxx-5.0.so()(64bit)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
And if use "--skip-broken" does not install many libraries.

If you are using smartmet-open packages, the update path is now a bit more complicated since we've also moved on to Boost 1.69 from EPEL instead of using our own build.
In that case the upgrade path is something like
systemctl stop smartmet-server
rpm -e --nodeps libpqxx
rpm -e --nodeps libpqxx-debuginfo
yum erase 'pgdg-*'
# Replace with your own proxy if using one:
https_proxy=http://wwwcache.fmi.fi:8080 wget https://download.postgresql.org/pub/repos/yum/reporpms/EL-7-x86_64/pgdg-redhat-repo-latest.noarch.rpm
yum localinstall pgdg-redhat-repo-latest.noarch.rpm
rm -f pgdg-redhat-repo-latest.noarch.rpm
yum-config-manager --disable "pgdg*"
yum-config-manager --enable pgdg-common pgdg95
yum-config-manager --setopt="pgdg*.exclude=postgis*,libpqxx*" --save
# Replace with your own proxy if using one:
yum-config-manager --setopt="pgdg*.proxy=http://wwwcache.fmi.fi:8080" --save
yum update "*smartmet*"
yum erase 'boost*1.66*'
systemctl daemon-reload
systemctl start smartmet-server

We have used the above commands successfully both on our own ~10-20 servers as well as for external installations.

Thank you so much for your help.
The installation is successful.


prioritization fee cache: remove not required locks

The first part of #30
Problem
PrioritizationFeeCache needs to write lock cache for every new transaction.
Summary of Changes
Instead of using a shared cache for everything, we can use a map in the update thread and update the shared cache when slot is finalized.

Please fill out the PR description.

updated..

@fanatid , now that you have triage powers, CI will run automatically. And it's failing on this PR.

Codecov Report
Attention: Patch coverage is 99.05660% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 81.9%. Comparing base (a2579d4) to head (90d1281).
Report is 45 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff            @@
##           master     #272     +/-   ##
=========================================
- Coverage    81.9%    81.9%   -0.1%
=========================================
  Files         837      837
  Lines      226805   226780     -25
=========================================
- Hits       185846   185812     -34
- Misses      40959    40968      +9


on_mention() fails when there is a DM

Describe the bug
When the in_mention event is used, the Framwork fails after the routine is finished
To Reproduce
Start script
Send a DM to a bot with the on_mention() Event activ
Bot will anwser and then gonna fail
Failure log
Traceback (most recent call last):
  File "/home/misskey/ceilingfox-bot/ceilingfox-reply.py", line 57, in <module>
    asyncio.run(MyBot(prefix).start(uri, token))
  File "/usr/lib/python3.9/asyncio/runners.py", line 44, in run
    return loop.run_until_complete(main)
  File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in run_until_complete
    return future.result()
  File "/usr/local/lib/python3.9/dist-packages/mi/client.py", line 437, in start
    await self.connect(reconnect=reconnect, timeout=timeout)
  File "/usr/local/lib/python3.9/dist-packages/mi/client.py", line 398, in connect
    await self.ws.poll_event()
  File "/usr/local/lib/python3.9/dist-packages/mi/gateway.py", line 50, in poll_event
    await self.received_message(json.loads(msg.data))
  File "/usr/local/lib/python3.9/dist-packages/mi/gateway.py", line 45, in received_message
    self._misskey_parsers[str_lower(msg['type']).upper()](msg)
  File "/usr/local/lib/python3.9/dist-packages/mi/state.py", line 216, in parse_channel
    getattr(self, f'parse_{channel_type}')(base_msg['body'])
AttributeError: 'ConnectionState' object has no attribute 'parse_unread_specified_note'
Unclosed client session
client_session: <aiohttp.client.ClientSession object at 0x7f0b90630e20>
Unclosed connector
connections: ['[(<aiohttp.client_proto.ResponseHandler object at 0x7f0b9015a3a0>, 15199.94388424)]']
connector: <aiohttp.connector.TCPConnector object at 0x7f0b901886d0>

The problem is that the parse_unread_specified_note method does not exist, and we plan to fix this in v2.1.2.

this problem fixed in a5e7216fa7f8602ce003997a0fe77002f6e279ce
please wait release v2.1.2

Fixed


Incorrect Quote Padding

If I am using the list in quotes, the padding is incorrect.

Thanks for the feedback. Could you please show some demo Markdown code to reproduce this?

Sure, try this:

List item1.

This is a quote

List item 1 in quote
List item 2 in quote
List item 3 in quote

Thanks for the feedback. Could you please show some demo Markdown code to reproduce this?

Sure, try this:


Only update lastMessageText from pusher event from other users

cc @marcaaron
Details
This will do a better job of keeping the last comment text in the LHN in sync.

It adds updates the text when the optimistic comment is first added to Onyx
It only updates the text when the pusher event comes from the non-active chat participant

Fixed Issues

Fixes https://github.com/Expensify/Expensify/issues/157488
Tests
You need to have two chat clients running with two different accounts (use incognito or a different platform with a different user logged in)

Open a chat with both users
Make comments AS FAST AS YOU CAN by one user
Ensure the last message text is always up to date in the LHN
Make comments AS FAST AS YOU CAN by the other user
Ensure the last message text is always up to date in the LHN

Tested On

[x] Web
[ ] Mobile Web
[ ] Desktop
[ ] iOS
[ ] Android

Screenshots

Web

Mobile Web

Desktop

iOS

Android

Looks like tests didn't even start when GH Actions was down? I can't seem to manually retrigger them either, maybe you'll need to make a blank commit?

Works great! 🎉

Updated! Tests should run now, hopefully.

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


FIX#18 Changed the CI

The deployment of the package and doc where moved in the normal_ci (instead of pull_request_ci)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.2%) to 98.538%

Totals

Change from base Build<PHONE_NUMBER>:
1.2%

Covered Lines:
337

Relevant Lines:
342

💛  - Coveralls


P110.getEnergyUsage() no longer returns historical data

I think historical data is cleared by the firmware update, but should there be empty fields (or zeros) in the data returned?
Using the proposed change https://github.com/fishbigger/TapoP100/pull/77 and calling getEnergyUsage() I get two different results, depending on the firmware version.
For devices running the older firmware (v1.0.16 Build 220624 Rel.171733), I get 'result' which shows historical data populated as:
{'today_runtime': 1213, 'month_runtime': 42966, 'today_energy': 1414, 'month_energy': 56071, 'local_time': '2022-10-22 20:13:00', 'past24h': [72, 42, 167, 134, 54, 37, 72, 88, 37, 38, 85, 77, 40, 62, 98, 105, 65, 87, 62, 36, 88, 74, 46, 29], 'past30d': [1916, 1766, 1825, 1788, 2050, 2037, 1919, 2081, 1858, 1783, 2044, 1922, 1852, 1907, 1790, 1762, 1851, 1896, 2072, 2046, 1796, 1848, 1941, 1940, 1839, 1894, 1792, 1765, 1677, 1414], 'past1y': [0, 0, 0, 0, 0, 0, 0, 0, 0, 29890, 56387, 40689], 'past7d': [[75, 60, 65, 54, ....<snipped to save space>....]], 'current_power': 129899}, 'error_code': 0}
For devices running the newer firmware (v1.1.2 Build 220930 Rel.144500), I get 'result' populated with no historical data fields as:
'result': {'today_runtime': 165, 'month_runtime': 9314, 'today_energy': 33, 'month_energy': 1891, 'local_time': '2022-10-22 20:13:01', 'electricity_charge': [0, 0, 0], 'current_power': 12173}, 'error_code': 0}

I can confirm V1.1.2 is not returning the historical data when calling getEnergyUsage(). I get:
{'result': {'today_runtime': 78, 'month_runtime': 666, 'today_energy': 14, 'month_energy': 174, 'local_time': '2022-10-23 10:14:31', 'electricity_charge': [0, 0, 0], 'current_power': 12071}, 'error_code': 0}
It is worth noting that the Tapo app has moved from 'Energy Usage' and 'Runtime' to 'Energy Usage' and 'Power'. I will add that I have found the new feature to add price per unit buggy in the app.

Thanks to @tnmendes for comments his comment here
With some small change to the getEnergyUsage() method
{ "method": "get_energy_data", "params": { "end_timestamp":<PHONE_NUMBER>, "interval": 43200, "start_timestamp":<PHONE_NUMBER> } }
My testing shows that it works and working with an internal of 43200.
{'local_time': '2022-10-23 15:00:51', 'data': [315, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'start_timestamp':<PHONE_NUMBER>, 'end_timestamp':<PHONE_NUMBER>, 'interval': 43200}
But when I test with other internals like 3600 or 7200 I am getting {'error_code': -1001}

Glad to see the solution helped. So the Tapo app is used for intervals:
43200  = 1 month
1440 = 1 day
60 = 1 hour
But I'm detecting strange behavior in start_timestamp you need to set the correct value that is the first day of the month at zero hours to work. The tapo app is asking for the last 3 months so I am assuming that new firmware will just store 3 months of daily information information.

Yes as you said before minutes, I see now. I can get 7 days of hourly data, 90 days of daily data, and 12 months of monthly data.
It is returning all the data in one list none of the past7d from the older firmware.
I note that if requesting to start mid month via start_timestamp it in fact just returns from the start of the month. Like below (only got this plug two days ago hence the 21 zeros at the start)
'data': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 160, 537, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]
A strange thing is that when using looking at hourly data the plug seems to be a day ahead. By that I mean I can look at data for 24 Oct. I seem to have the correct location selected in the app. For example start datetime(2022, 10, 22) and end datetime(2022, 10, 25). Hence catching data for 22nd to end of 24th. I get:
'data': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 23, 29, 41, 20, 5, 0, 0, 15, 27, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 12, 12, 11, 33, 75, 41, 50, 64, 58, 33, 82, 75, 20, 0]

"A strange thing is that when using looking at hourly data the plug seems to be a day ahead."
It looks like it's the same on the Android APP... at the time of the screenshot, it was 9:15 AM, Oct 24th on my computer. The graph on the mobile app is showing data up to oct 24th 23:00-24:00 and it contains data! I am ot sure how we are meant to treat the data.

hoping this might help,
B

Generally speaking,
are we able to rollback the firmware version?
I have blocked requests to tplink servers with my pihole so hopefully I maintain a fixed version from now on.

The daily read is indeed off by one day (reading the data from Oct 25th 00:00 to Oct 26th 00:00 is giving my current day consumption (Oct 24).
The monthly read is also not intuitive. If I put the end/start date as for the daily read, the first index is the first day of October. If I put the time range from Oct 1st to Oct 31st, then this is what I get:
[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1561, 9059, 8366, 9350, 9943, 7758, 7284, 6865, 9349, 6953, 6498, 5901, 11572, 5680, 5855, 9431, 6924, 6134, 10837, 7471, 6608, 7289, 6859, 5560, 11716, 6858, 3274, 17125, 4754, 2861, 2257, 4640, 1601, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0]

1601 being today's entry, and it's off by 21 entries in the list 🤷 ?

It looks like some good detective work has taken place and there is a workaround at least for this. Is anyone able to share what needs tweaking and where to get my code running again and returning historical data?

I still can't map the data datetimes correctly, but I found an interesting function in the disassembled tapo app (I don't speak java, I'm a php dev), maybe this can help understanding how the exchange is made... I can see a reference to an interval of 5, which wasn't expected. Anyway, I think the app isn't displaying the correct datetimes either, and maybe it would be worth it to wait for another update before doing anything... not sure
/* renamed from: q */     public final void mo47832q() {         long j = (long) 1000;         Calendar instance = Calendar.getInstance(C5132x0.m15953d(this.f35770i));         C18563j.m60883e(instance, "it");         long currentTimeMillis = (System.currentTimeMillis() / j) * j;         instance.setTimeInMillis(currentTimeMillis);         instance.set(13, 0);         instance.set(12, (instance.get(12) / 5) * 5);         C18563j.m60883e(instance, "calendar");         long timeInMillis = instance.getTimeInMillis() / j;         long j2 = timeInMillis - 86400;         EnergyPowerDataResult value = mo47833r("day_power").getValue();         Long l = null;         mo47821B(timeInMillis, 5, value != null ? Long.valueOf(value.getEndTimestamp()) : null);         m40793x(new EnergyPowerDataParams(j2, timeInMillis, 5));         instance.set(12, 0);         instance.set(13, 0);         long timeInMillis2 = instance.getTimeInMillis() / j;         long j3 = timeInMillis2 - 604800;         EnergyPowerDataResult value2 = mo47833r("week_power").getValue();         if (value2 != null) {             l = Long.valueOf(value2.getEndTimestamp());         }         mo47821B(timeInMillis2, 60, l);         m40793x(new EnergyPowerDataParams(j3, timeInMillis2, 60));         instance.setTimeInMillis(currentTimeMillis);         instance.set(13, 0);         instance.set(12, 0);         instance.set(11, 0);         long timeInMillis3 = (instance.getTimeInMillis() / j) + ((long) 86400);         long j4 = timeInMillis3;         m40790p(new EnergyPowerDataParams(timeInMillis3 - ((long) 604800), j4, 60));         instance.set(13, 0);         instance.set(12, 0);         instance.set(11, 0);         instance.set(5, 1);         instance.add(2, -2);         m40790p(new EnergyPowerDataParams(instance.getTimeInMillis() / j, j4, 1440));         instance.setTimeInMillis(currentTimeMillis);         instance.set(13, 0);         instance.set(12, 0);         instance.set(11, 0);         instance.set(5, 1);         instance.add(2, 1);         instance.set(2, 0);         m40790p(new EnergyPowerDataParams(instance.getTimeInMillis() / j, instance.getTimeInMillis() / j, 43200));     }

@bobo3k The timestamps appear to be in unix format
Perhaps PyP110.py could be amended to add a copy of getEnergyUsage(), renamed as getEnergyData()
    def getEnergyData(self, startT, endT, intervalT):
        URL = f"http://{self.ipAddress}/app?token={self.token}"
        Payload = {
            "method": "get_energy_data",
            "params":{ "end_timestamp": startT, "interval": intervalT, "start_timestamp": endT},
            "requestTimeMils": int(round(time.time() * 1000)),
        }

Other folks on here would know a better way of doing this

@bacheshrew I know about the timestamps, but the problem is with the fact that the data returned is off compared to the timestamp... for example if you ask today's info from 2022-10-26 00:00 to 2022-10-27 00:00 it will show data from 27 to 28th... and we're not there yet. (look at the screenshot from the APP, it's faulty too). I'm pretty sure it's a bug they'll have to fix via a new firmware. My guess: we can only wait.

Thanks @bob3k. Let's wait and see.

Clearly, there are several issues with the dates of the firmware update.
I'm developing the app Watt for Smart Devices and the solution I have at the moment that matches android Tapo's app is:
startTime = 1st day of the month of the previous month at zero hours
EndDate= today with today's time
I think it is also necessary to pay attention to the GMT

Thanks all for your detective work on this. I feel it would be better to wait for a firmware update than to code in a temporary fix so I'm going to mark this as won't fix.
Let me know if there are any further comments on this :)

@fishbigger it seems that there is more than one issue raised in thread. I see two clear issues and there might be more.

P110.getEnergyUsage() no longer returns historical data - can be fixed adding a new method to PyP110.py using @bobo3k code.
The timeshift bug, where the plug is returning tomorrows data.

While I would agree that point (2) should be left for a Tapo bug fix. I am not sure that point (1) will be 'fixed' by Tapo, as it seems like that is the new way they are delivering the data.


Setting PartitionKey and RowKey arguments to null if not set when creating TableAttribute

This addresses issue #261 for C#.
The WebJobs SDK expects the partition key and row key arguments to be null if not set/used. Passing an empty string (which is what the current portal logic does when the metadata property is present) causes the binding failure that leads to this issue.

@mathewc this is the simple fix I mentioned earlier on #261

:ship:


Fix shader crash when using boolean type for vertex->fragment varyings

Currently, shader with declared boolean or boolean vector varying crashing with an error:
ERROR: 0:642: 'out' : cannot be bool

I've restrict using of them in that context (only fragment-to-light should be allowed now). Fixes crashing in three possible conditions:
varying flat bool test;

void vertex(){
	test = true; // Prints: "Varying with '%s' data type may be assigned only in 'fragment' function."
}

void fragment(){
}

varying flat bool test;

void vertex(){
}

void fragment(){
	if(test) // Prints: "Varying with 'bool' data type must be assigned in 'fragment' function first."
 	{
	}
}

varying flat bool test; // Prints nothing, but prevent shader crash in shader compiler.

void vertex(){
}

void fragment(){
}

@clayjohn Thanks, I've fixed and changed it a bit, now the error messages are more unified with a standard varying errors - check again.

@clayjohn And flat modifier is required with the boolean varying or not? - if not, I can remove it.

@clayjohn And flat modifier is required to be used with boolean varying or not? - if not, I can restrict usage of it.

Well, modifiers don't really do anything in the fragment to light varyings as the value is not interpolated (i.e. the value is passed as-is). So I guess we could give the user an error if they use it. But ignoring it would be fine too.


_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m  0s
the patch passed

+1 :green_heart:
compile
0m 28s
the patch passed

+1 :green_heart:
javac
0m 28s
the patch passed

+1 :green_heart:
shadedjars
6m 34s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 25s
hbase-client in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m  8s
hbase-client in the patch passed.

28m  6s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2353

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux ad9d6de8b59e 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 1e8db480b3

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/1/testReport/

Max. process+thread count
280 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 29s
Docker mode activated.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 53s
the patch passed

+1 :green_heart:
compile
0m 31s
the patch passed

+1 :green_heart:
javac
0m 31s
the patch passed

+1 :green_heart:
shadedjars
7m 30s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 26s
hbase-client in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
1m 20s
hbase-client in the patch passed.

30m 19s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/3/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2353

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux a799a7242279 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 8a6299bb38

Default Java
2020-01-14

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/3/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-client.txt

javadoc
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/3/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-client.txt

Test Results
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/3/testReport/

Max. process+thread count
215 (vs. ulimit of 12500)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/3/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 31s
Docker mode activated.

Planning to commit this in ~1 day unless there are any concerns.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 10s
the patch passed

+1 :green_heart:
compile
0m 30s
the patch passed

+1 :green_heart:
javac
0m 30s
the patch passed

+1 :green_heart:
shadedjars
6m 41s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 25s
hbase-client in the patch failed.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
7m 18s
master passed

+1 :green_heart:
checkstyle
1m 10s
master passed

+1 :green_heart:
spotbugs
2m 40s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
8m 41s
the patch passed

-0 :warning:
checkstyle
1m 23s
hbase-client: The patch generated 1 new + 51 unchanged - 0 fixed = 52 total (was 51)

+1 :green_heart:
whitespace
0m  2s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
22m 28s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
2m 32s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 26s
The patch does not generate ASF License warnings.

59m 45s

Subsystem
Report/Notes

Docker
Client=19.03.13 Server=19.03.13 base: https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2353

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle

uname
Linux 7defbc8e0586 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / ee02e673b7

checkstyle
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-client.txt

Max. process+thread count
84 (vs. ulimit of 30000)

modules
C: hbase-client U: hbase-client

Console output
https://ci-hadoop.apache.org/job/HBase/job/HBase-PreCommit-GitHub-PR/job/PR-2353/4/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


Update PHP to 8.1 to take advantage of new enum types

Now that PHP 8.1 has been officially released, it might be a good idea to update the projects minimum PHP version to 8.1 and take advantage of the new enum types.
I propose a new namespace App\Enums and to migrate all class constants within model policies to utilise specific enum cases. Here's an example for ArticlePolicy:
<?php

namespace App\Policies;

use App\Enums\ArticlePolicyAction;

final class ArticlePolicy
{
    const UPDATE = ArticlePolicyAction::UPDATE;
    const DELETE = ArticlePolicyAction::DELETE;
    const APPROVE = ArticlePolicyAction::APPROVE;
    const DISAPPROVE = ArticlePolicyAction::DISAPPROVE;
    const DECLINE = ArticlePolicyAction::DECLINE;
    const PINNED = ArticlePolicyAction::PINNED;

    ...
}

I have a proof-of-concept branch, and a draft PR but need a hand with a couple of tests that are failing when run via GitHub Actions, but run fine locally.

Thanks. I'll do this once Laravel 9 is out

Btw feel free to copy over the description here to the pr. No need to both create an issue and pr. Just the pr is fine. Thanks for your work!

@driesvints No problems - I got a tooltip when creating the PR that the contribution docs had changed and they said create a PR for an existing issue (something to the effect of an issue needing creating first, I think)

@joelbutcher thanks for letting me know that! I've updated that description a bit.


Missing require (require what you use)

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
Non-GitHub Verified Committers
There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.
Please sign the CLA here.

:+1:
@jkeiser You might want to fix up your gitconfig/supermarket settings to make sure curry bots knows you are are a cool dude.

@jkeiser I'm :+1:, but please do an amend to straighten out the commit's author's email addy and re push.

Hi. I am an automated pull request bot named Curry. There are commits in this pull request whose authors are not yet authorized to contribute to Chef Software, Inc. projects or are using a non-GitHub verified email address. To become authorized to contribute, you will need to sign the Contributor License Agreement (CLA) as an individual or on behalf of your company. You can read more on Chef's blog.
Non-GitHub Verified Committers
There are 1 commit author(s) whose commits are authored by a non-GitHub verified email address. Chef will have to manually verify that they are authorized to contribute.
Please sign the CLA here.

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.


How to remove coc?

How i can remove this?
let g:airline#extensions#coc#enabled = 0 is not helps.

Do you have coc installed?

Am 29.05.2019 um 19:01 schrieb zdm<EMAIL_ADDRESS>How i can remove this?
let g:airline#extensions#coc#enabled = 0 is not helps.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

no
On 29.05.2019 20:56, Christian Brabandt wrote:

Do you have coc installed?

Am 29.05.2019 um 19:01 schrieb zdm<EMAIL_ADDRESS>How i can remove this?
let g:airline#extensions#coc#enabled = 0 is not helps.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vim-airline/vim-airline/issues/1926?email_source=notifications&email_token=AAH2MSEFZKSRSM7R3KIVWL3PX27VVA5CNFSM4HQOZCJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWQEQKQ#issuecomment-497043498,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAH2MSD4PEIQMMPNTNXEMFTPX27VVANCNFSM4HQOZCJQ.

ah sorry, should be fixed now.


Chinese inteface

Hi.
I've installed fresh SRS and whole web interface is in Chinese. Is there any way to switch to English?
Previous issue #1180 has response but it's not understandable. Moreover if I try to open console on my host (http://ubuntu:1985/console) I get "Not found" page.
In issue #1184 it was suggested how to install console, which turned out to be separate project. I did that but it's Chinese as well and I've found no way to change language to English. I've checked ng_index.html file and it seems Chinese texts are hardcoded into it.
Additionally I'd say it's not a good practice to close issue before it's confirmed it's resolved.

DUP to #1184


[Docker RPM] containerd.io > 1.2.5 breaks docker run/start on RHEL 7

Description
Ever since containerd.io 1.2.6, I've been unable to launch or restart docker containers on RHEL 7.
Steps to reproduce the issue:

Install docker + containerd.io from https://download.docker.com/linux/centos/7/x86_64/stable/Packages/
docker run -ti ubuntu

Describe the results you received:
Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused "write /proc/self/attr/keycreate: permission denied"": unknown.
Describe the results you expected:
A working container.
Output of containerd --version:
containerd  1.2.10 b34a5c8af56e510852c35414db4c1f4fa6172339

Any other relevant information:
Downgrading to 1.2.5 makes everything work again.  Docker version doesn't seem to matter - everything from docker-ce-18.09.4-3.el7.x86_64 up to docker-ce-19.03.4-3.el7.x86_64 seems to work fine.

Seems issue of runc binary with containerd rpm (by Docker inc, not by us)?
What's the version of runc?

Make sure the container-selinux package is up to date.

@AkihiroSuda Apologies for the noise. I didn't look into the original provenance of the source but assumed that whatever was packaged in the containerd.io package was part of containerd.  Any ideas where I can submit this bug so that it will get looked at appropriately?  Their Open Source page (https://www.docker.com/community/open-source) just points here for containerd.
@cpuguy83 container-selinux fully updated.

@AkihiroSuda Here are the runc versions from those packages.  Non-working:
runc version 1.0.0-rc8+dev
commit: 3e425f80a8c931f88e6d94a8c831b9d5aa481657
spec: 1.0.1-dev

Working:
runc version 1.0.0-rc6+dev
commit: 2b18fe1d885ee5083ef9f0838fee39b62d653e30
spec: 1.0.1-dev

As far as I remember (reading https://github.com/opencontainers/selinux/pull/56 helps to refresh my memory) this is a combination of
1 a bug in RHEL7 kernel (which won't be fixed, see https://bugzilla.redhat.com/show_bug.cgi?id=1719067)
2 a mislabeled (runc?) binary
Maybe we should reopen the workaround PR (https://github.com/opencontainers/selinux/pull/56).
Let's at least check that SELinux labels are correct.

Next reason, the difference in behavior might come from the version of selinux-go package used, let's see.
$ rpm -q containerd.io; runc --version
containerd.io-1.2.5-3.1.el7.x86_64
runc version 1.0.0-rc6+dev
commit: 2b18fe1d885ee5083ef9f0838fee39b62d653e30
spec: 1.0.1-dev

$ rpm -q containerd.io; runc --version
containerd.io-1.2.6-3.3.el7.x86_64
runc version 1.0.0-rc8
commit: 425e105d5a03fabd737a126ad93d62a9eeede87f
spec: 1.0.1-dev

# check the old version first (seems like it's working)
$ cd ~/go/src/github.com/opencontainers/runc/
$ git checkout 2b18fe1d885ee5083ef9f0838fee39b62d653e30
$ grep selinux vendor.conf
github.com/opencontainers/selinux v1.0.0-rc1

# check the new (seemingly non-working) version
$ git checkout 425e105d5a03fabd737a126ad93d62a9eeede87f
$ grep selinux vendor.conf
github.com/opencontainers/selinux v1.2.2

Oops, there was a major bump. Let's see what's changed wrt keycreate:
$ git diff 2b18fe1d885ee5083ef9f0838fee39b62d653e30 425e105d5a03fabd737a126ad93d62a9eeede87f -- vendor/github.com/opencontainers/selinux/go-selinux/ | grep keycreate
+	err := writeCon("/proc/self/attr/keycreate", label)
+	return readCon("/proc/self/attr/keycreate")

OK here it is: there was no code writing that file before, thus the error.

Based on this analysis I am reopening https://github.com/opencontainers/selinux/pull/56

@paulgear if you have a system to experiment with, can you please do a small experiment?

Start on a non-working system (i.e. container start gives the write /proc/self/attr/keycreate: permission denied" error)
Downgrade containerd (yum downgrade containerd.io or so). Check that it fixes the issue.
Upgrade containerd again (without a reboot).

If I remember right, it was working for me after step 3. I wonder if you can get the same or different result (and if it's the same, how to explain it).

Hi @kolyshkin - thanks for checking this out.  In my case, I don't need any reboots to reproduce this behaviour.  Here's a session log:
$ docker run -ti --entrypoint /bin/bash python-base-image
docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused \"write /proc/self/attr/keycreate: permission denied\"": unknown.
ERRO[0000] error waiting for container: context canceled
$ rpm -q containerd.io
containerd.io-1.2.10-3.2.el7.x86_64
$ rpm -qil containerd.io | grep bin | xargs ls -lZ
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/containerd
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/containerd-shim
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/ctr
-rwxr-xr-x. root root system_u:object_r:container_runtime_exec_t:s0 /usr/bin/runc
# (downgraded containerd.io in another window as root)
$ rpm -q containerd.io
containerd.io-1.2.5-3.1.el7.x86_64
$ rpm -qil containerd.io | grep bin | xargs ls -lZ
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/containerd
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/containerd-shim
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/ctr
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/sbin/runc
$ docker run -ti --entrypoint /bin/bash python-base-image
root@087c512fc90c:/# uname -r
3.10.0-1062.12.1.el7.x86_64
root@087c512fc90c:/# exit
# (upgraded containerd.io in another window as root)
$ rpm -q containerd.io
containerd.io-1.2.10-3.2.el7.x86_64
$ rpm -qil containerd.io | grep bin | xargs ls -lZ
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/containerd
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/containerd-shim
-rwxr-xr-x. root root system_u:object_r:bin_t:s0       /usr/bin/ctr
-rwxr-xr-x. root root system_u:object_r:container_runtime_exec_t:s0 /usr/bin/runc
$ docker run -ti --entrypoint /bin/bash python-base-image
docker: Error response from daemon: OCI runtime create failed: container_linux.go:346: starting container process caused "process_linux.go:449: container init caused \"write /proc/self/attr/keycreate: permission denied\"": unknown.
ERRO[0000] error waiting for container: context canceled

The core problem was solved in a different repo/package; I assume those packages are now updated for the distro(s) in question and we can close any tracking here (as none of the investigation ending up requiring changes to containerd)


Moving the tier naming content from Learn to Contribute

TELCODOCS-1520: This PR moves the tier naming content from Learn to Contribute content type
Issue: https://issues.redhat.com/browse/TELCODOCS-1520:
Preview: http://373.docs-pr.validatedpatterns.io/contribute/about-pattern-tiers-types/

This is an automated message:
You can preview this docs PR at http://373.docs-pr.validatedpatterns.io
Note that they get generated every five minutes, so please wait a bit.

@danmacpherson Kindly review these changes for moving the tier naming content from Learn to Contribute. Again, the htmltest is failing but the changes implemented with this PR work fine locally.


feat(viewer_results): add ViewerResultsAllCPTs class (WIP)

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

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-3.0%) to 76.703%

Totals

Change from base Build<PHONE_NUMBER>8:
-3.0%

Covered Lines:
1610

Relevant Lines:
2099

💛  - Coveralls


update /api/delete to use POST method instead of DELETE

Related to issue 7895 and PR 8018

Hi @nguu0123 thanks for the first-time contribution, I appreciate that you thought of the SDKs when you saw the issue in the main repo. This isn't implemented in the main ollama repo, and I doubt it will be for some time if it does get picked up, having a POST to delete a model feels a bit confusing to me.
I'm going to mark this as a draft for now to keep things tidy.


Update paragraph.md

Add example on how to use paragraph style properties.
After long research to find out how to declare paragraph style properties, I conclude that the documentation miss this example.

Yes thanks for this actually came up before too.


Read text from multi line textbox

I run the parser and it's only read the first line of the textbox if the textboxt has more than one line.
And if the paragraph has more text style like this:
" Visual Studio Code is a lightweight but powerful source code editor which runs on your desktop and is available for Windows, macOS and Linux."
may be the color of the text, the font size too. I cant get all of this

Looks like there are a few questions here.  I'll get them separately. Here's the example I am using to Parse.

Multi-line Problem
Thanks, I hadn't realized this. The problem can be fixed in the paragraph parser
I naively just looked at the first element when extracting text, but after diseccting the actual Powerpoint Element, I see that each newline is a separate element of the array.
There is a raw element that is also a part of the PPTElement that actually has the parsed PPT XML that helps when debugging this uncaught stuff.

Might be smarter to iterate the array length and concatenate each element with a newline.
text: textElement["a:r"][0]["a:t"].toString() // problem is with the 0.

I'll see if I can push a new version soon or I'd encourage you to make a PR, now that you know the problem 😄
Preserving Color
I used red, and my color was preserved by the way. Colors are weird in Powerpoint, they can come from the theme or designs, try to explicitly assign one.
"textCharacterProperties": {
          "size": 1200, //ppt multipes fonts by 100 btw
          "fontAttributes": [
            0
          ],
          "font": "Helvetica", //this is the default, read the paragraph parser code, it'll teach you better
          "fillColor": "FF0000"
        }

In-line Bolding and Italics
I'm not sure how to handle the bolding and italics embedded in the text just yet, so that's probably not supported.
I'm still writing some docs, I haven't officially "published" this yet.  Not all elements are supported, you can see that list kind of here. Thanks for using this!

@tanphamanhh, should be fixed. Just published 1.0.6

I have an example PPTX that in one shape, it have more paragraphs. you can see the object model of pptx in here

I see in your PowerpointElement, in one shape it only have one paragraph

But, like the PPTX Object model image you see above, in one shape (PowerpointElement), it can have more than one paragraph.
Here is my pptx file's raw data:

That looks like a complex shape. At this point, I don't have plans to support that just yet. Feature requests can be tracked in Fider. I have added yours.
However, if this is something you really would like, I'd encourage you to make a PR to update the PPT Model and the parser to support paragraphs to return an array instead.


Receive email notification in my language

Bug Report
Problematic behavior
Even though my interface is in french I'm receiving notification emails in english.
Right the emails are sent in the language  setting  the sender using on the app. It should be the opposite.

I observed the same.
We need to store the language for the user.
With my PR from #333 we will have the same language in the backend that we have in the frontend, because of sharing the language cookie.
We just need to read that cookie on the backend when the user makes a request to it, and save the language stored in it to the user.
Then we always have up to date preferred language on the user entity
and when he is supposed to receive an invite, we can just use the target users last saved language

@lindenb1 and i would like to work on this issue next.
To do this, we would like to remove the current usage of the Content-Language Headers in both frontend and backend.
Instead we would add a Middleware that updates the language attribute of the requesting user.

after the user preferred language was determined (after LocaleMiddleware),
and after the requesting user has been determined (after AuthenticationMiddleware)

Then we would adapt the code that sends invitation emails, to associate the email-address with the receiving user, and use the stored preferred language for translation of the email.

associate the email-address with the receiving user,

@rvveber in the backend the email is sent to a user if we have one, so you will have access to user.language. If we have no user an invitation is sent to an email address but in this case we have no real way to determine a language... We could use the default instance language (settings.LANGUAGE_CODE) or the language of the requesting user like now? In the case of a governmental instance like us, the instance default language is paradoxically  our best bet!

You said:

With my PR from #333 we will have the same language in the backend that we have in the frontend, because of sharing the language cookie impress_language.
We just need to read that cookie on the backend when the user B makes any request to it, and if it changed, update the language attribute on the user enttity for user B.

But then you proposed:

Instead we would update language via the users API endpoint on language selection in the frontend.

Am I correct if I say this is in contradiction? If we update the field value on the user each time the cookie changes, we don't want to offer modifying via the frontend because it will be confusing?
I would expect the value to be set the first time I login, and then being editable in my settings via the frontend. This means that we can set it in the authentication backend and not via a middleware and the cookie?

I didn't see that we could add any email address!

@virgile-dev may not be obvious enough?

You said:

With my PR from #333 we will have the same language in the backend that we have in the frontend, because of sharing the language cookie impress_language.
We just need to read that cookie on the backend when the user B makes any request to it, and if it changed, update the language attribute on the user enttity for user B.

But then you proposed:

Instead we would update language via the users API endpoint on language selection in the frontend.

Am I correct if I say this is in contradiction? If we update the field value on the user each time the cookie changes, we don't want to offer modifying it via the frontend because it will be confusing?
I would expect the value to be set the first time I login, and then being editable in my settings via the frontend. This means that we can set it in the authentication backend and not via a middleware and the cookie?

The cookie determines the system language of django for the request as per LocaleMiddleware.
But it is not persistet on the user.
My original idea was to take that system language which is already correct for the user and persist it on his user entity. Because it would be a minimal solution.
But maybe doing it on each request is unnecessary stress, if it only happens on language switch anyways.

After external discussion with @sampaccoud we could agree on the process.
Currently the frontend detects its language in this order:

cookie
browser-lang

And stores the detected language in a cookie.
(Which then results in translation)
I will add a detection strategy after the cookie, that will get the users language attribute:

cookie
user.language
browser-lang

This way, when accessed from a new browser that has no cookie, or the cookie expired, we still get the users choosen language for the new cookie.
On language switch, i will update user.language asynchronously via API - then everything should be kept in sync, while still switching and loading instantly.
And of course finally, i will adapt to send the email in the users.language with fallback to djangos default language (settings.LANGUAGE_CODE).

Additional considerations:
@sampaccoud mentioned, that it would be better to have an account settings page, where to change user settings such as language.


App keep loading no error show (Bash on Windows)

Hi,
So I tried to setup my ruby environment on this new bash subsystem on Windows.
My app work right and all the gem was compatible.
Comes to mailcatcher installed from gem on this bash subsystem, no error shown on the installation.
No error shown also on the launch :
Starting MailCatcher ==> smtp://<IP_ADDRESS>:1025 ==> http://<IP_ADDRESS>:1080
but when I'm trying to load the page, it never stop loading until I quit the process by hand in the bash console.
So basically no error shown on console and on chrome console, the page never show but keep loading. (Sometimes when I stop the daemon the page stop loading and display some HTML code it apparently retrieve)
It would be nice to have mailcatcher working on the bash subsystem since it's the environment advised by many sources now. You might want to see this page to reproduce the bug maybe https://gorails.com/setup/windows/10
Thanks for your help,

Hi @koalabear974, I don't have a Windows system to get this running myself but if you want to contribute a patch it would be most welcome! Otherwise I'm afraid I'm unable to fix this and will close.


Two bug fixes

This commit fixes two bugs.  The first bug would prevent roles
which had been previously filtered from becoming unfiltered.  By
being too eager to save Dynamo operations we were updating only
roles with filters, which had the unfortunate side effect that
roles can't become unfiltered.
The other bug was attempting to use a exception details in an
error that wasn't triggered by an exception.

Coverage decreased (-0.3%) to 28.456% when pulling f515d3babadac89ae15cecb252ef4c560d0756cc on bug-fixes into b1dfe256dbdd86b0315745b00771e9ea0efb150d on master.

Coverage decreased (-0.3%) to 28.456% when pulling f515d3babadac89ae15cecb252ef4c560d0756cc on bug-fixes into b1dfe256dbdd86b0315745b00771e9ea0efb150d on master.


Configurator for macOS?

Hi @dekuNukem,
first time DPP user here. duckPad configurator 1.6.3 does not work with DPP. Is there no macOS (ARM if possible) equivalent to v2?
Tx, BF

@BabyFnord DuckyPad Pro software (v2) is currently only avalible for Windows. Me also waiting for the MacOS version.
https://github.com/dekuNukem/duckyPad-Pro/releases/tag/2.0.0

Thanks to pointers by @jbecker on Discord, I've assembled this reliably working method:
Install/Update Configurator
cd "$HOME"
git clone https://github.com/dekuNukem/duckyPad-Pro.git
mkdir duckyPad-Pro-VENV
python3 -m venv duckyPad-Pro-VENV
source duckyPad-Pro-VENV/bin/activate
pip install --upgrade pip
cd duckyPad-Pro/pc_software
python3 -m pip install -r requirements.txt
sudo python3 duckypad_config.py

Run Configurator
cd "$HOME"
source duckyPad-Pro-VENV/bin/activate
cd duckyPad-Pro/pc_software
sudo python3 duckypad_config.py

Of course you could install/run it anywhere else than $HOME, if you want to. Case closed, at least for me :)


Added stackoverflow link

Just want to stackoverflow's link like this

@MeiK2333 How is this?

thx :)


SpriteBatch problems

Hi!
I observed some problems using spriteBatch (using CANVAS on Phaser 2.4.4)
1- Sometimes the texture coordinates are not well calculated when using atlases for sprites/images.
The spriteBatch draws a bigger texture area (sometimes). It seems to me that it draws until the next power of two to the right and to bottom.
Example: if you have a texture atlas of 100x40 it seems to draw 128x64.
2- Sometimes the image position is not well calculated when using atlases for sprites/images with animations.
I have a head making nod that works perfectly when its alone but it jumps a bit when in a spriteBatch. It has anchor (0.5, 1) and a yoyo animation that rotates it.
3- The textures with negative scale are not well drawn.
I can fix that changing a line of code in the function: PIXI.SpriteBatch.prototype._renderCanvas
This line: if (child.rotation % (Math.PI * 2) === 0)
For this one: if (child.rotation % (Math.PI * 2) === 0 && child.scale.x >= 0 && child.scale.y >= 0)
But the image with negative scale is not well positioned and is a bit blurred (all it's ok when alone).
Thanks

Another one:
4- Seems that the hitAreas of the images/sprites in the spriteBatch do not work properly.
It seems that are scaled and in a first plane disallowing buttons that were in front.
These same hitAreas worked well out of the spriteBatch.

Closing due to several months of inactivity. A stand-alone running code example is needed to investigate this further.


Freeze and errors when saving project with thousands of files

Godot version:
master: 256bbd3561135c7886501a865be27cde3d26d47d
OS/device including version:
Ubuntu 18.04
Issue description:
When saving a scene in a project with thousands of files, the editor freezes in a loop.
Spamming: Object was deleted while awaiting a callback
And then:
TOTAL BYTES: 1048560
NULL count: 1
CALL : 8764
CALL _update_callback: 2
CALL _update_minimum_size: 1
ERROR: push_call: Message queue out of memory. Try increasing 'message_queue_size_kb' in project settings.
   At: core/message_queue.cpp:56.

Steps to reproduce:
Create a project with ~4400 scenes.
Save one of them. Boom!
NOTE: In the game I'm testing, I only have ~900 files, but it still freezes when saving, with similar error (though it seems following other code paths). In the demo project, I usually regain control over the editor in about 15/20 seconds. In my game I waited 45 seconds with no luck.
The only way I found to workaround this is by increasing the message_queue_size_kb.
(should we increase the default? Should the editor use it's own specific setting)
Minimal reproduction project:
manyfiles.tar.gz

Should be fixed by #24194.


Can not capture event async-load-nodes when there are more than three level.

When create a tree with more than three level, it can not capture event async-load-nodes.
Cause : vm.$emit only trigger an event on the current instance.

It is normal in the demo, and I will test the npm package later，thank you for your feedback.

i pulled source from git. and it is aslo not works.

Hi! Can you please show a better example of your code, or provide an example repo? It's not clear what you're doing from the code you've provided.

I'm sorry, I didn't notice this bug before. I misunderstood you, you can install<EMAIL_ADDRESS>this version has fixed it


Changed duckling extractor to return entity values as string

Signed-off-by: Davide<EMAIL_ADDRESS>Proposed changes:

let duckling return always string values, in order to allow entities extracted by it to be tested. With the actual rasa version in the following part of the test story, the entities cannot be tested correctly beacuse of the different types of the values:

* start_cooking: let's cook the [second]{"entity": "ordinal", "value": "2"} [one]{"entity": "number", "value": "1"}   <!-- predicted: start_cooking: let's cook the [second]{"entity": "ordinal", "value": 2} [one]{"entity": "number", "value": 1} -->

With the changes made, all the values are returned as a string and can be tested in the conversation_tests.md file, otherwise, they are reported as wrong predictions while testing.
Status (please check what you already did):

[x] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog (please check changelog for instructions)
[ ] reformat files using black (please check Readme for instructions)

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

Thanks for submitting a pull request 🚀 @tttthomasssss will take a look at it as soon as possible ✨

@tabergma, can you please review my pr?

@davidezanella Thanks for submitting the PR. The changes look good, but I am not quite sure if I understand the problem? During our evaluation we don't compare the actual values. So why is this needed? You mentioned something about an conversation_tests.md file. Do you have your own evaluation that is failing due to this?

@tabergma While developing my project with rasa, I've written some tests story for my assistant in the conversation_tests.md file. Originally, duckling returns integer values with the ordinal and cardinal categories but they fail the tests in the test story because the entities extracted must be string while the predicted ones are integers. So with my own tests, using duckling the assistant cannot be tested correctly because of these different data types.

@davidezanella Thanks for the quick response. Can you maybe convert the values into strings inside of your tests itself? I would hesitate to modify our code if it only affects your tests as the code is working and changing it would affect quite a lot of people.

@tabergma No, I cannot change the value into strings, I rewrite the example and try to explain it better.
* start_cooking: let's cook the [second]{"entity": "ordinal", "value": "2"} [one]{"entity": "number", "value": "1"}
<!-- predicted: start_cooking: let's cook the [second]{"entity": "ordinal", "value": 2} [one]{"entity": "number", "value": 1} -->

The first row is a test that I've written, the type of the value is a string because is the only type accepted by rasa and otherwise it will raise an exception.
The second row is the predicted entities and intent by my model and their value, since coming from duckling are of type integer. With the changes made in this pr the predicted values will be strings as well and the test succeeds.

Just to be sure, did you write the test on your own or are we talking about the end-to-end test?

I just wrote the not predicted part, which is a part of a story in the end-to-end format inside the tests/conversation_test.md file, that I tested using the rasa test command.

Ah ok, sorry about that. That was a misunderstanding on my side. So I just checked with a colleague and we both agree that we should not change the type of the duckling output.
If I understand the problem correctly, Rasa is reading all entity values of your conversation_test.md as strings. So something like
let's cook the [second]{"entity": "ordinal", "value": 2} [one]{"entity": "number", "value": 1}

becomes actually
let's cook the [second]{"entity": "ordinal", "value": "2"} [one]{"entity": "number", "value": "1"}

Is that correct? If that is the case, then I guess a better way of fixing this would be to update the reading process. What do you think?

Yes, what you said and the example you reported are correct. Actually, I didn't get  what you mean with the "reading process". Anyway, if you're aware of the impact of this change on the slots type and functionality, I've already tested it and it seems to work as before, so when accessing the ordinal and cardinal slots from an action their value is numeric as should be even if duckling now returns strings.

@davidezanella Thanks for the input. Before we merge this change, I would like to test it myself, just to be sure that it does not have any impact. Can you maybe share your assistant, so that I can use that for testing? Thanks.

Sure, I'm sending you an email with the code zipped

Thanks for sharing your code! That helped debugging the problem.
I think I found another way to fix this: We can convert the duckling values to string just for the evaluation itself. When evaluating the e2e stories the entity values coming from duckling are converted into strings. That should fix the issue you have. However, we don't modify the duckling extractor itself, so there should be no effect for other users relying on it.
The fix is currently on the branch e2e-testing (see https://github.com/RasaHQ/rasa/compare/e2e-testing). My suggestion: We close this PR and I will create a new PR with my changes referencing this one. How does that sound?

It sounds good, thanks!


Correct in S3AUnderFileSystem the owner id to username mapping

UNDERFS_GCS_OWNER_ID_TO_USERNAME_MAPPING -> UNDERFS_S3_OWNER_ID_TO_USERNAME_MAPPING

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/1937/
Test PASSed.


[Elasticsearch] pending_tasks metrics should include time_in_queue_millis

The current Elasticsearch integration collects counts of pending tasks but it does not collect the time_in_queue metric for the tasks.  This is a useful metric to show how long tasks are in the queue.  Please add time_in_queue_millis to the collected metrics.

+1

Hi @tsndqst,
Thanks for idea,

Hi @tsndqst,
Thank you for raising the issue, this is definitely something that should be return by the integration. I'm going to work on this as soon as I have some bandwidth.

The change will be available in the next agent release.
Closing the issue, fell free to reopen it if needed.


Add intersperse and intercalate to Sequential

Issue #39

Thanks, and well done ! it turn out trickier than expected.

I'll fix the issue with GHC 8.0 in a future commit


Failing test preventing PR build: ClusteredStateRepositoryReplicationTest.testClusteredStateRepositoryReplication

When running locally, I run across this failing test:
ClusteredStateRepositoryReplicationTest.testClusteredStateRepositoryReplication
When it fails, the build stops. I don't know why.
This prevent PR #1676 to build.
[Server thread isActive: active] INFO org.ehcache.clustered.server.EhcacheActiveEntity - Connecting PassthroughClientDescriptor{server=org.terracotta.passthrough.PassthroughServerProcess@2972c7e7, sender=org.terracotta.passthrough.PassthroughConnection@6c70440d, clientInstanceID=2}
[Server thread isActive: active] INFO org.ehcache.clustered.server.EhcacheStateServiceImpl - Configuring server-side clustered tier manager
[Server thread isActive: active] INFO org.ehcache.clustered.server.EhcacheActiveEntity - Disconnecting PassthroughClientDescriptor{server=org.terracotta.passthrough.PassthroughServerProcess@2972c7e7, sender=org.terracotta.passthrough.PassthroughConnection@6c70440d, clientInstanceID=2}
[Server thread isActive: active] INFO org.ehcache.clustered.server.EhcacheActiveEntity - Connecting PassthroughClientDescriptor{server=org.terracotta.passthrough.PassthroughServerProcess@2972c7e7, sender=org.terracotta.passthrough.PassthroughConnection@6c70440d, clientInstanceID=4}
[Server thread isActive: active] INFO org.ehcache.clustered.server.EhcacheActiveEntity - Adding Client PassthroughClientDescriptor{server=org.terracotta.passthrough.PassthroughServerProcess@2972c7e7, sender=org.terracotta.passthrough.PassthroughConnection@6c70440d, clientInstanceID=4} with client ID : 7617ad1a-deba-4202-a63d-ad93ff9aa661
FATAL EXCEPTION IN PASSTHROUGH THREAD:
java.lang.AssertionError: Unexpected exception
	at org.terracotta.passthrough.Assert.unexpected(Assert.java:28)
	at org.terracotta.passthrough.PassthroughServerProcess.reconnect(PassthroughServerProcess.java:784)
	at org.terracotta.passthrough.PassthroughServerMessageDecoder.decode(PassthroughServerMessageDecoder.java:307)
	at org.terracotta.passthrough.PassthroughServerMessageDecoder.decode(PassthroughServerMessageDecoder.java:37)
	at org.terracotta.passthrough.PassthroughMessageCodec.runRawDecoder(PassthroughMessageCodec.java:344)
	at org.terracotta.passthrough.PassthroughMessageCodec.decodeRawMessage(PassthroughMessageCodec.java:267)
	at org.terracotta.passthrough.PassthroughServerProcess.serverThreadHandleMessage(PassthroughServerProcess.java:497)
	at org.terracotta.passthrough.PassthroughServerProcess.runServerThread(PassthroughServerProcess.java:473)
	at org.terracotta.passthrough.PassthroughServerProcess.access$000(PassthroughServerProcess.java:78)
	at org.terracotta.passthrough.PassthroughServerProcess$2.run(PassthroughServerProcess.java:251)
	at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.Exception: Entity not found in reconnect
	... 10 more

FYI, this bug is created by https://github.com/Terracotta-OSS/tc-passthrough-testing/issues/58
As a workaround, I'll do a null-check after this like in Monitoring:
IMonitoringProducer monitoringProducer = services.getService(new BasicServiceConfiguration<>(IMonitoringProducer.class));
This will make PR #1676 pass.
But this won't resolve the issue: IMonitoringProducer should always be there: this is a platform-provided service.

Closing since the root cause is in a dependency


build(dep): bump sass to 1.34.1

removed rxjs and whatwg-fetch

Codecov Report

Merging #197 (92ccce0) into master (0f273cd) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #197   +/-   ##
=======================================
  Coverage   62.44%   62.44%
=======================================
  Files          58       58
  Lines        2868     2868
  Branches      595      595
=======================================
  Hits         1791     1791
  Misses        942      942
  Partials      135      135

Continue to review full report at Codecov.

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


chore: update dart_frog_gen version

Status
READY
Description
chore: update dart_frog_gen version

Type of Change

[ ] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[ ] 🧹 Code refactor
[ ] ✅ Build configuration change
[ ] 📝 Documentation
[x] 🗑 Chore

@renancaraujo do we still need this PR? Can we land it? Or close it in case we don't?