Remove unnecessary TYPE_CHECKING alias

The change was already proposed by @aqeelat in #1934 but it was not implemented.

Thanks @rafrafek!

The change looks good but unfortunately the aws lambda tests are failing (not because of your change), we'll need to fix this before we can merge this. @antonpirker maybe you have an idea what's wrong?

Created https://github.com/getsentry/sentry-python/issues/2487 to track progress on the aws lambda test suite issue.


support for windows terminal

Environment:

windows
neovim
windows terminal

If you have a trouble with coloration and are using Vim/Neovim with terminal:

[x] Does your Vim support full colors? (:set termguicolors)
[x] Does your terminal support full colors? (e.g. Terminal.app doesn't support it)

format required:
ex: Night Owl
{
"background": "#011627",
"black": "#011627",
"blue": "#82AAFF",
"brightBlack": "#969696",
"brightBlue": "#82AAFF",
"brightCyan": "#7FDBCA",
"brightGreen": "#22DA6E",
"brightPurple": "#C792EA",
"brightRed": "#EF5350",
"brightWhite": "#FFFFFF",
"brightYellow": "#FFEB95",
"cyan": "#21C7A8",
"foreground": "#D6DEEB",
"green": "#22DA6E",
"name": "Night Owl",
"purple": "#C792EA",
"red": "#EF5350",
"white": "#FFFFFF",
"yellow": "#ADDB67"
},

Could you explain that JSON? I'm not a Windows user.

Microsoft have released their Terminal for Windows not so long ago.
I'm guessing the issue creator requests the port of the colorscheme to the Windows Terminal? Well, he's in luck!
Basically, this JSON is how custom colorschemes are defined in settings.json of the Windows Terminal.
Here's the JSON for Iceberg (will move that to a gist shortly):
            "name" : "Iceberg",

            "cursorColor": "#c6c8d1",
            "selectionBackground": "#1e2132",

            "background" : "#161821",
            "foreground" : "#c6c8d1",

            "black" : "#1e2132",
            "blue" : "#84a0c6",
            "cyan" : "#89b8c2",
            "green" : "#b4be82",
            "purple" : "#a093c7",
            "red" : "#e27878",
            "white" : "#c6c8d1",
            "yellow" : "#e2a478",
            "brightBlack" : "#767676",
            "brightBlue" : "#91acd1",
            "brightCyan" : "#95c4ce",
            "brightGreen" : "#c0ca8e",
            "brightPurple" : "#ada0d3",
            "brightRed" : "#e98989",
            "brightWhite" : "#d2d4de",
            "brightYellow" : "#e9b189"

I have made this long ago, but couldn't be bothered to post it somewhere.

Thanks @gkeep
I was just looking for that
I think it will be cool if you pull request to add this json

OSS maintainers receive many issues every day. You can help us with more kind, detailed reports. @JDRanpariya


Changes to filter_bugs and export_bugs

@Nfsaavedra , is there anything missing in this PR?

@Nfsaavedra , is there anything missing in this PR?

@andre15silva I don't think so. You can merge.


Material Table & File List tweaks

@glassblowerscat This will probably conflict with your previews branch. Do you want me to wait until after it's merged?

@CarsonF Up to you. If you have lots of changes you want me to make on previews, I could just do the updates for this at the same time.

Haha 😬


1280x1024 aimbot problem

[settings]
welcome_notif = 1
size_of_window = 266
confidence_threshold = 0.55
nms_iou = 0.55
mouse_delay = 0.0001
pixel_increse = 5
status_overlay = 1
overlay_resolution_X = 10
overlay_resolution_Y = 10
promote = 0
When my friend running, my aimbot turns 90 degrees from him. He hasn't this problem. I have same settings as he. Is it my monitor resolution problem? And how to solve it?

It may be your monitor, The cheat is built for 1920x1080 We never planned to have it run on 1280x1024.
I can't give too much info on it other then you will just have to tweak the settings for yourself.
We will take this into consideration though and put this into our error-logs too add Multi-Resolution support with documentation on it, Sorry.

How long may we wait for custom resolution support?

How long may we wait for custom resolution support?

I cannot say as the development and updates have been a little slow lately, When we do update the project next we will do some testing, I am no longer interested in these kinds of projects anymore so the next update won't be for awhile.


Package Missing and LSFM not found

Hi,
I have successfully installed the menpo as instructed. However when I run the command C:>conda create -n lsfm -c menpo python=3.5 lsfm, it says:
Fetching package metadata .............
PackageNotFoundError: Package not found: '' Package missing in current win-64 ch
annels:

lsfm

However, when I run the command conda create -n lsfm python=3.5 -c menpo/lsfm The following happens:-
Fetching package metadata ....
WARNING: The remote server could not find the noarch directory for the
requested channel with url: https://conda.anaconda.org/menpo/lsfm
It is possible you have given conda an invalid channel. Please double-check
your conda configuration using conda config --show.
If the requested url is in fact a valid conda channel, please request that the
channel administrator create noarch/repodata.json and associated
noarch/repodata.json.bz2 files, even if noarch/repodata.json is empty.
$ mkdir noarch
$ echo '{}' > noarch/repodata.json
$ bzip2 -k noarch/repodata.json
.........
Solving package specifications: .
Package plan for installation in environment E:\Codes\External_Libs\LSFM\Minicon
da2\envs\lsfm:
The following NEW packages will be INSTALLED:
pip:            9.0.1-py35_1
python:         3.5.3-0
setuptools:     27.2.0-py35_1
vs2015_runtime: 14.0.25123-0
wheel:          0.29.0-py35_0

Proceed ([y]/n)? y
To activate this environment, use:

activate lsfm

To deactivate this environment, use:

deactivate lsfm

for power-users using bash, you must source

After activation it is unable to recognize lsfm as a command
(lsfm) C:>lsfm --help
'lsfm' is not recognized as an internal or external command,
operable program or batch file.
I will greatly appreciate some help on this.
Regards
Syed

Hi @SyedGilani,
Really sorry for this problem, we've been caught up a little with issues on our build system, working through this issue now, should have it rectified today

OK, the Linux build I have just verified is live, haven't got a win machine nearby to test but the issue should be resolved there also

Hi James
Thank you for fixing it. Which Menpo Version do you recommend? The 2.7 or
3.5?
Regards
Syed
On 3 May 2017 9:22 pm, "James Booth"<EMAIL_ADDRESS>wrote:

OK, the Linux build I have just verified is live, haven't got a win
machine nearby to test but the issue should be resolved there also
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/menpo/lsfm/issues/5#issuecomment-298908963, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AOyr8_OXt8ayoGZlxJnzQ5Xt5aS2QsN2ks5r2H-jgaJpZM4NIZX-
.

@SyedGilani lsfm actually requires 3.5.
I would recommend you run the original install command with a new environment name to get everything cleanly setup now, e.g.:
> conda create -n lsfmv1 -c menpo python=3.5 lsfm

Then to use this new env,
> source activate lsfmv1

And you should be good to go.

Closing as I believe this is now fully addressed.


Fixes signal instance deduplication check.

Deduplicating signal instances should only occur when those instances are associated with a case.

I think my preference would be to fix the check here:
https://github.com/Netflix/dispatch/blob/master/src/dispatch/signal/flows.py#L86
The assumption that a case exists if a signal has been filtered is wrong (e.g. they can be filtered in other ways like snoozing). There are likely other actions we will likely want to take if a case exists, by moving the conditional higher in the stack we make it clear that updating a message requires a case and provide a reasonable place to add other case-related actions in the future.


how to add utf-8 support via addHTML() with fromHTML() plugin?

I base on meteor js. and I use ongoworks:pdf package that using fromHTML() to generate PDF with meteor template.
But I don't understand how to integrate?
Please help me.

Hi there,
There's now a html2pdf example which much better supports generating documents from HTML.
Get the latest master and try:
npm install
npm start

Then visit localhost:8000/examples/html2pdf/showcase.html
Hope this works well for you :)
Many thanks,
James


New site: beta-invite.com

It seems to contain a doubly-rarred virus, I don't recommend touching the download button.

beta-invite.com

Implemented in #259 :) ty


Feature Request: return vertex ID on loadGraphML()

1 of 2 major issues I have before my little project can continue.
When loading a GraphML file into a pre-existing graph (I use Neo4j for example) it basically gets dumped on it's own as a separate sub-graph with no way to add an edge to it on import.
Say for example I want to give other users the ability to load their own GraphML files. My application can ask for the file and load it but unless the user also specified a vertex property or some other way of identifying the loaded graph then there is no other way to create a edge to place it in the correct location in my "main" graph. Worse, that none of these methods for identifying a vertex in the loaded GraphML file will be unique. A unique ID is required.
What I'm proposing is:
A) Allow a extra field in loadGraphML() for nominating a unique vertex ID provided by the GraphML file. This should then return the new ID generated for that vertex to allow an edge to be created.
For example: addEdge(g.loadGraphML('path/to/graphml.xml', ), g.v(1).out.filter(it.getProperty('label')=='BIN'), 'ATTACH')
B) Same as A) except the ID is specified with in the GraphML file itself. This might even be more flexible. For example you could specify more than 1 ID, etc. I don't know the structure it would take but something like:
C) Something similar or the same as loadGraphML().next() for finding the first loaded GraphML node. I must stress - and despite the conversations I've had on the Gremlin mailing list - I actually find this method extremely useful for structured data. This way the user doesn't have to specify a unique ID anywhere. In my mind this is far more important and useful than the first 2 options.
Thanks
Eddy

Could you customize loadGraphML to inject a unique node into the user-provided graph?

I've started looking at the code and I'm now wondering if this is really a feature request for Blueprints? Any suggestions?
Anyway, with my limited knowledge of Java/Groovy I was hoping someone could give me a little hint. As @i000 suggests whats the easiest way to override/customize both Gremlins GraphLoader and Blueprints GraphMLReader class methods?


Add an option to disable GUI

I don't use the frontend at all. Disabling it at compile time has some benefits:

Shorter build time
No need to install Qt5.

Tested with:
cmake -DDISABLE_FRONTEND=ON .

Bump. Is this PR still in consideration?

Ideally I'd rather specify which targets should be built (rather than having a custom variable to disable targets), but CMake seems to lack this basic functionality :disappointed:


Display undefined label for Neutral Action Ribbon

Describe the bug
Displays undefined  as no default label is provided unless user explicitly sets label from controls.
To Reproduce
Steps to reproduce the behavior:
Path: http://localhost:49345/?path=/story/components-action-ribbon--neutral

Run storybook
Navigate to Action Ribbons
Select Neutral
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots

Hi, @owilliams320 let me know if i can add a small PR for this :)


Inconsistent enum type merging

TypeScript Version<EMAIL_ADDRESS>(same with 3.2.4, 3.5.2, 3.5.3)

Search Terms: enum hover ternary union merging
enum subtype reduction
getUnionType
Code
enum SomeEnum {
  APPLE = 'APPLE',
  ORANGE = 'ORANGE',
  BANANA = 'BANANA'
}

function test(inputEnumMember: SomeEnum) {
  // Correctly gives `const a: SomeEnum`
  const a: SomeEnum.BANANA | SomeEnum = inputEnumMember;

  // Incorrectly gives `const b: SomeEnum.APPLE | SomeEnum`
  const b = Math.random() < 0.5 ? SomeEnum.APPLE : inputEnumMember;

  // Incorrectly gives `const c: SomeEnum.APPLE | SomeEnum` (really weird)
  const c = Math.random() < 0.5 ? SomeEnum.ORANGE : inputEnumMember;

  // Incorrectly gives `const d: SomeEnum.BANANA | SomeEnum`
  const d = Math.random() < 0.5 ? SomeEnum.BANANA : inputEnumMember;
}

Expected behavior:
All declared variables have the type SomeEnum or at least are consistently "wrong" (see const c as showing APPLE)
Playground Link:
https://www.typescriptlang.org/play/#code/KYOwrgtgBAyg9hYBRc0DeAoKUCCAFPAGSSgF4oByfIpCgGiygHkAlHAOQHETyLWPu9RgCEOYspVHsxFDAF8MGAGZgQAYwAuASzggoG4AGcNACi0gADmA0pIAWWAQARsABOALlgJkqAJRRMbAB6IKgAYThXV2BNABsATygAcy0ANyMoAAM1XWMoAENPeERbCEzGHJA8wq8S1AA6KXEAH1qfSAlzKxtUB2c3AG5FYNCASXVI6LjElPTDLMq8pyLvUvrqYihW4vayityNKCcJO3yNAAt613yQABMEE38AHigABnqAVigAfja1jZIni61lKfRcriGjBCUHGOSiMQ0CWSaQy2QOUDUKzqkHWBE221WqEyUBMAHdgFpXLdfPsqoc1CczpdrncHs83p8fn8GvwuICoMCevZHODISMYRN4dNkXMFujbljdo0xNIttzIOVsItDrdGRcrjd7hBHlAXu8vr8dmsmqqgZYQb0RYN5BggA
This is a really minor issue as it only applies to hover type information and the reported value while being weird isn't breaking anything.

This regressed between 3.0.1 -> 3.1.6.

Does this have observable effects other than quick info? I don't think it does?

I guess this should only have observable effects up to the extent that SomeEnum and SomeEnum.APPLE | SomeEnum.ORANGE | SomeEnum.BANANA are distinguishable.

Exactly when to perform subtype reduction is tricky business; there are some compromises we have to make in order for other scenarios to work. "Consistent" type display between different ways of generating observably-same types isn't something we can guarantee.


Updating requirements.txt file

Description
As i can see in the requirements.txt file added the python packages version specified are old.
I would like to update the requirements.txt file with the latest version number.
Have you read the Contributing Guidelines on Pull Requests?
yes.

I have assigned you the Issue @sameersrivastava13

Closing this issue for now, as there are no further updates to be done currently.


Add tests to Enhanced Cover Art Uploads

Couple of things to note:

Using pollyjs to record and replay HTTP interactions with the providers instead of actually doing network requests
Depends on #68

I suppose we could add a more integration test-like workflow to CI to run pollyjs in passthrough mode so we're actually performing the network requests rather than always replaying, so that we can find out whether there are any upstream changes that need to be accounted for. Such tests should definitely not be run on every commit in a PR, because, among other things, they may take quite a long time. Perhaps instead we could instead only run them on pushes to main (i.e. after a PR merge) before deployment, and/or on a cron schedule (perhaps once a week or so).
Drafting to check whether this works properly in CI.

I've been doing some thinking on how to best approach the core (non-provider) code refactoring to improve testability, so I'll just summarise so I don't forget:
The main challenge with testing the core code in its current state is that it's fairly heavily coupled to the UI. Since we're using JSX with nativejsx, that's near impossible to test. nativejsx does something completely different to the usual JSX implementations: In conventional JSX, JSX code is converted to a sort of object describing the DOM elements, which should later be fed into a render call, whereas nativejsx transforms the JSX code into DOM elements directly, eliminating the need for render calls. The problem with testing code containing JSX is that the JSX of course needs to be transpiled. There are babel plugins to do this, and we can use those before giving the code to jest, but those plugins use conventional JSX transformations, not the nativejsx ones. What we could do is write some helper functions similar to React.createElement to create DOM elements without the need to render them, but we'd still be heavily tied to the UI code. Instead, we should  refactor the core code to be UI-agnostic, i.e., all UI stuff into separate modules.
There are two options here:

Keep the ImageImporter class in index.ts, which then imports ui.tsx (or whatever UI module structure we go with), and have ImageImporter do the same thing it's currently doing: Set up the UI in its constructor, using functions now imported from ui.tsx.
Move ImageImporter into a separate module and remove all UI-related stuff from its implementation, and make index.ts do all the wiring of UI and implementation code. So index.ts imports ui.tsx and ImageImporter, and does setupPage(..., importer.addImages). ImageImporter can then be completely decoupled from any UI stuff and tested fully in isolation.

The problem with option 1 is that in order to test ImageImporter, we'd have to mock out ui.tsx, which won't be pretty, so I'd go with option 2.
I then foresee the following changes to make this work:

Setting up the paste box will likely remain more or less the same as what is happening now, since it's already using a callback anyway.
Setting up the buttons should not be done in setupPage anymore. We'll instead factor out the "detection" of providers and do the wiring in index.ts.
Filling in the upload form should be removed from ImageImporter, since that's UI stuff. ImageImporter.addImages should instead return the results (and probably renamed), index.ts should give those results to a UI function that fills the form.
StatusBanner has got to go, we'll replace it with a more robust logging setup where we can attach custom logging sinks to display messages.

W.r.t. that logging setup:

Homegrown implementation.
Would be a lib module.
Simple interface (debug, log, info, warn, error).
Attach custom logging sinks which can decide how to display the data. Examples include logging to console, logging to a UI element like a StatusBanner or a more advanced UI like the one used in the work codes script.
Possibly a singleton Logger instance exported from the lib. Since it's rolled up into the userscript, each script still gets its owner logger.

The ImageImporter could then probably just do logger.info('Added …'); instead of using the status banner, and index.ts would create and attach the status banner logging sink so it gets displayed on the page. We could possibly also use some constants that get replaced by babel to set a debug mode on or off depending on the build environment. Later on, we could replace the simple status banner with something akin to the message display used in the work codes script, so that we can display more than one message at a time and separate errors/warnings from informational messages (as suggested in #66).

Btw, the reason CI isn't running on these changes yet is because of the merge conflict. I'll resolve those conflicts once #68 is merged. Rest assured that all tests are passing (at least on my machine).

Since it's rather boring to see all tests pass, I am just making a few of them fail deliberately while I am reviewing locally 😁. I think I have already reviewed most parts of this PR too (as soon as you have pushed new commits) while I am still busy with #68, but it's hard to see the progress before the other one is merged (GitHub does not track the "reviewed" status of files across PRs which are containing the same commits). It won't take long now until I am done with the other one and you can rebase this PR.

FYI: Force-pushed to rebase onto latest main.

I'm going to stop for today. All of the UI stuff has been factored out, the image fetching logic has been split off into a separate module as well. There are still numerous things to do though, but I won't have much time in the coming days to work on this. Off the top of my head:

a-tisket seeder needs to go into a seeding directory, like we do for providers. We might add different seeders later (like VGMdb).
seeding should have a "main" file (seeding/base.ts or just seeding.ts), which has "encode" and "decode" functions for the seeder parameters. The whole addImageFromLocationHash should thus be removed, the decoding should take place in seeding "main" file. index.ts decodes the seeding params (if present), fetches as normal, and adds.
More work is needed on enqueuing URLs and filling types and comments. There's currently a bit of a hack in place to add types and comments from the location hash seeder, I'm not sure how we should handle that.
Everything needs to be tested, that's of course the main goal.

It should build fine in its current state. Not sure whether it runs fine though, haven't tested anything.

improve naming of image maximalisation

Only for the code, for commit messages we have Dunglish [irony off] 😁

Godverdomme 🤦 There's just some things I can't get rid off

We're getting closer to the end of this: All of the refactoring is done, and there's only one more module left to test. :)
E2E will be a separate PR.

I've pushed a couple of misc things that aren't directly related to testing, but would be nice to have in a next release. We should fix #79 before releasing though...


Switch all Dockerfiles to remoting 3.35

@oleg-nenashev In https://github.com/jenkinsci/docker-slave/pull/74 I missed to adjust the other Dockerfiles as well 😕
Sorry for that.

@oleg-nenashev @jeffret-b any thoughts on this? We (I) missed to update the other Dockerfiles with the new remoting version.

These missed versions and a serious of regressions last week shows that I
need a break before I can review PRs properly. Please proceed without me
for now, I am on vacation and need some time to recover
On Tue, Sep 24, 2019, 19:39 Alex Earl<EMAIL_ADDRESS>wrote:

@slide approved this pull request.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jenkinsci/docker-slave/pull/84?email_source=notifications&email_token=AAW4RIG6I4RFY2ZTCMIE6Q3QLJGD7A5CNFSM4IZLYKGKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCFYJZUY#pullrequestreview-292592851,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAW4RIAFEK7GXFKCMA6RBX3QLJGD7ANCNFSM4IZLYKGA
.

@oleg-nenashev thanks. Enjoy your vacation 😊

PS: who can release a new docker-slave version?

Once it's merged it should be auto built on dockerhub

Once it's merged it should be auto built on dockerhub

Ah, ok. Good to know.
But what I meant is a stable version like 3.35-3-alpine to reference in docker-jnlp-slave

I'm not sure how those tags get created.

I'm not sure how those tags get created.

@slide It seems Oleg switched to release-drafter 9 days ago. Before he created the tags manually.
I guess owners of the repo should see a new draft release?

As pull requests are merged, a draft release is kept up-to-date listing the changes, ready to publish when you’re ready


Webpack4 doesn't handle network paths

Bug report

What is the current behavior?
When output.path is a network path of the following format: \\hostname\directory\deep\tree webpack fails with the following message:
WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.output.path: The provided value "\\\\hostname\\directory\\deep\\tree" is not an absolute path!
   -> The output directory as **absolute path** (required).

If the current behavior is a bug, please provide the steps to reproduce.

Specify output.path as a network path.
Try to compile the application

What is the expected behavior?
Network path is accepted and webpack outputs files to the specified path.

Other relevant information:
webpack version:  4.41.2
Node.js version: 10.15.1
Operating System: Windows

Send a PR to schema-utils
Here is the relevant line: https://github.com/webpack/schema-utils/blob/6caaa59cf40af948ea3d9658f4c32bd79b6c37a5/src/keywords/absolutePath.js#L54

https://github.com/webpack/schema-utils/pull/85, but for webpack@4 we need fix it here https://github.com/webpack/webpack/blob/v4.41.5/schemas/ajv.absolutePath.js#L29

yep. fix master first, then old versions...

@sokra @evilebottnawi Looks like this has been addressed no?

Yes, thanks


Implement Nullable Type Functions and DefaultIfNil Utility

Title: Implement Nullable Type Functions and DefaultIfNil Utility
Description
This PR introduces a set of utility functions for handling nullable types and provides a generic utility function, DefaultIfNil, to handle nil values for various types in Go. Along with the implementation, comprehensive unit tests are added for each function to ensure their correctness.
Summary
Nullable Type Functions:
Added functions to handle nil checks and return default values for pointers of different types.
These functions will dereference the pointer if it’s not nil, or return the default value for the respective type otherwise.
NullableBool: Handles *bool.
NullableByteSlice: Handles *[]byte.
NullableComplex64: Handles *complex64.
NullableComplex128: Handles *complex128.
NullableFloat32: Handles *float32.
NullableFloat64: Handles *float64.
NullableInt: Handles *int.
NullableInt8: Handles *int8.
NullableInt16: Handles *int16.
NullableInt32: Handles *int32.
NullableInt64: Handles *int64.
NullableUint: Handles *uint.
NullableUint8: Handles *uint8.
NullableUint16: Handles *uint16.
NullableUint32: Handles *uint32.
NullableUint64: Handles *uint64.
NullableString: Handles *string.
NullableTime: Handles *time.Time.
DefaultIfNil Function:
Added a generic function DefaultIfNil to handle nil pointers of any type and return a default value if the pointer is nil.
This function uses Go generics (T) to allow usage with any data type.
Test Cases Added:
Comprehensive test cases were written for each function above.
For each function, we tested scenarios where the pointer is nil and where the pointer is not nil.
The tests ensure the correct default value is returned when the pointer is nil and that the pointer's value is returned when it is not nil.
For DefaultIfNil, we added tests to cover various types such as:
int, string, bool, float32, float64, and time.Time.
Why This Change?
Simplifies Code: These utilities simplify handling of nullable pointers in Go, reducing the need for repetitive nil checks throughout the codebase.
Improves Safety: The functions provide a safe way to work with pointers and nil values, ensuring that no nil dereference errors occur.
Generics Support: The DefaultIfNil function leverages Go's generics to handle multiple types, making it a reusable utility for different data types.
How to Test:
Unit Tests:
Run go test to execute the unit tests and verify that all functions are working as expected.
The tests cover both cases where the pointer is nil and where the pointer is not nil.
Example Usage:
You can use these functions for safely handling nullable types in your application. For example, when working with pointers to int, string, float64, etc., use NullableInt, NullableString, or DefaultIfNil to safely handle nil values.

Great! One QQ: Why we are not adding all code in one file? Most of the files seem to have only one function anyway.

I've been quite busy this week and couldn’t dedicate as much time to this task as I’d have liked. You’re absolutely right about the structure, but I’ve opted not to use a single file. Instead, I’ve organized similar functions into the same files for better clarity. Please review and share any suggestions for improvement.

That's totally ok. Whenever you get a chance you can complete this PR. It looks more structured now. Once you mark it as ready for review. I'll do the review.


BHBC-900: Tests + minor updates

Overview
Links to jira tickets
https://quartech.atlassian.net/browse/BHBC-900
This PR contains the following changes
Tests + minor updates.
This PR contains the following types of changes

[ ] New feature (change which adds functionality)
[ ] Enhancement (improvements to existing functionality)
[ ] Bug fix (change which fixes an issue)
[ ] Misc cleanup / Refactoring / Documentation
[ ] Version change

Checklist
A list of items that are good to consider when making any changes.
Note: this list is not exhaustive, and not all items are always applicable.
General

[ ] I have performed a self-review of my own code

Code

[ ] New files/classes/functions have appropriately descriptive names and comment blocks to describe their use/behaviour
[ ] I have avoided duplicating code when possible, moving re-usable pieces into functions
[ ] I have avoided hard-coding values where possible and moved any re-usable constants to a constants file
[ ] My code is as flat as possible (avoids deeply nested if/else blocks, promise chains, etc)
[ ] My code changes account for null/undefined values and handle errors appropriately
[ ] My code uses types/interfaces to help describe values/parameters/etc, help ensure type safety, and improve readability

Style

[ ] My code follows the established style conventions
[ ] My code uses native material-ui components/icons/conventions when possible

Documentation

[ ] I have commented my code sufficiently, such that an unfamiliar developer could understand my code
[ ] I have added/updated README's and related documentation, as needed

Tests

[ ] I have added/updated unit tests for any code I've added/updated
[ ] I have added/updated the Postman requests/tests to account for any API endpoints I've added/updated

Linting/Formatting

[ ] I have run the linter and fixed any issues, as needed
See the lint commands in package.json
[ ] I have run the formatter and fixed any issues, as needed
See the format commands in package.json

SonarCloud

[ ] I have addressed all SonarCloud Bugs, Vulnerabilities, Security Hotspots, and Code Smells

How Has This Been Tested?
Please describe the tests that you ran to verify your changes.
Screenshots
Please add any relevant UI screenshots, if applicable.

also can we add a test case for not applicable cases in the access request list component?

not a blocker, but would be nice if you could add the test case to auth-utils where array is empty


Add a refresh button on top left of popup to reload the extension - popup.html, popup.js

Pressing the refresh button will reload the extension, and re-fetch the data from the database.
A simple single line implementation.

solved in #110


Add Apache 2.0 license boilerplate

Let's add a canonical Apache 2.0 license to this project and make it public accessible

this repo is now public and has the license, closing this


Persistent Red colors

I am working with images containing a lot of grass and trees. Everything is green.
Visualizing the bounding boxes in green is not so practical.
I am looking for a way to persistently assign a color to those annotations (especially, I only have one class) without the need of launching a new view of manually changing the settings.
Is there something like this available in fiftyone?

Hi @nasserdr does this help you? You can assign custom colors to the dataset's app config that will be loaded every time.
https://docs.voxel51.com/user_guide/using_datasets.html#custom-color-scheme

Thanks, so it's Save as default' in the color settings.
Solved :)


Lay of the land / help / overview command

@kieferrm had an idea where we would use copilot to describe the current state & actions that can be taken to a screen reader user. Imagine what we do currently using the contextual help dialogs, but with more information.
In thinking about this, I wondered if we could have a command that would describe the current lay of the land / overview. For example, if a user is unsure where the focus has gone or if something is not working as expected, it might say "there are 2 editor groups open. The first has a bash terminal and the second has 4 typescript files. The extensions view is focused and contains 3 extensions that suggest reloading the window.". This would save time as otherwise, a user would have to navigate all over the workbench for this information.
@jooyoungseo, @rperez030 please let us know what you think of these ideas.
One thing we'd want to consider is should this content be read using Copilot voice or presented in an accessible view? I imagine the latter.

That sounds like a super powerful idea. My initial thought is that this should be part of the accessible view simply because not everyone will have access to Github copilot which is a paid product, but copilot would make much more sense because it would allow the user to ask more specific questions, for example, tell me more about the typescript files, or "how can I close that terminal?". If, on top of that, copilot could perform actions on the editor on behalf of the user... combine that with the speech feature, and we'll have powerful assistant that would help multiple user groups in a number of situations.

@meganrogge I would vote for Copilot voice instead of accessible view so that we can give a clear cue for users to distinguish the response from other text info in the accessible view.

@meganrogge I would vote for Copilot voice instead of accessible view so that we can give a clear cue for users to distinguish the response from other text info in the accessible view.

What about Braille users? Is copilot voice available to users who do not have access to GitHub copilot? Is it possible to interact with messages coming from copilot voice using the screen reader?
I personally haven't tried copilot voice.

That is a really great point @rperez030. I'm not certain, but would hope that Copilot Voice works with braille devices already. @bpasero do you know this?

braille support is really a screen reader feature. i don't know much about copilot voice. If it is supposed to be a voice only experience, it probably doesn't make sense that it works with Braille, but then all the features that are available through copilot voice should also be available through copilot chat.

@meganrogge can you clarify what you are asking me? Today the vscode-speech extension provides the capability of transcribing voice to text and fill it into the Copilot chat input boxes. We have not explored any further capabilities such as speaking text back to the user, though that is a feature that the underlying speech library is providing. Maybe check out https://learn.microsoft.com/en-us/azure/ai-services/speech-service/speech-sdk if that helps.

I was confused. I thought Copilot Voice allowed for text to be read to the user.
The link you shared looks like what I'd actually want to use, thanks.
So, a user would trigger the help command, we'd ask copilot to describe the lay of the land, and we'd use that library to read the response aloud. We'd have to see if the library integrates with braille. if it does not, I would guess we'd want to alert that text instead, so would need a setting as I do worry about how this would interplay with screen readers.

The ability to read out text is something currently not exposed from the library or the extension but I think could be added:

https://github.com/microsoft/node-speech
https://github.com/Microsoft/vscode-speech

On a teams call, @rperez030 used an NVDA extension to get this lay of the land:
"This image appears to be a screenshot of an online video conference call interface. There are four participants shown in the conference, each with a distinct video or profile image and name displayed.
Starting from the top left corner of the window, you can see a row of various icons and the duration of the current call, which is 03:35. Next to the call duration, there are options for engaging in the video conference call, such as Chat, People (highlighted with a number indicating there are 4 people in the call), Raise hand, React, View options, Notes, Whiteboard, Apps, and More options. There is a prominent Leave button in red, indicating the option to exit the call.
In the main area of the interface, there are four participants:

At the top left, there is a man named Roberto Perez, who is currently in a live video feed. He is wearing a polo shirt with horizontal stripes and headphones. He is in a room with a cream-colored wall and is visible from the chest up.

At the top right, there is a woman named Megan Rogge, also shown in a live video feed. She has curly hair and is wearing a plaid shirt. She is in a well-lit room with white doors and a window showing daylight in the background.

At the bottom left, there is a participant named Debra Shelton (Northwest Center), but instead of a live video feed, there is a profile picture displayed. The picture shows a person with a fair complexion and dark hair that covers part of their face, looking towards the camera with a light source in the background.

At the bottom right, there is a participant named Jen Agarwal, who is also represented by a profile picture instead of a live video. The image features a person with medium-dark skin and dark hair, looking to the side with a natural backdrop.

It's important to note that all names and any personal characteristics described here are derived from the visual content of the screenshot and do not violate the privacy rules set forth. The video conference interface itself bears a strong resemblance to Microsoft Teams or a similar application."

We now have this with the copilot vision extension. It will be enhanced when we merge it into vscode-copilot


Remove access rights text from create new scanned book page

I opened a PR in curation_concerns to make a partial for just the permissions note, to avoid having to copy and update a significant partial:
https://github.com/projecthydra-labs/curation_concerns/pull/409

projecthydra-labs/curation_concerns#409 is merged, but I wasn't able to get plum to use the current master branch without doing all the updates to CC/HW/PCDM that @tpendragon is going to do, so I'll wait.


gateway config doesn't work with ipv6 only network

Looks like chart doesn't work with ipv6 only network
Following environment variables, hardcoded bind to "<IP_ADDRESS>" which doesn't work with ipv6 only network

ZEEBE_GATEWAY_NETWORK_HOST
ZEEBE_GATEWAY_MONITORING_HOST

You can set the environment variables via the chart values, e.g.:
gateway:
  env:
    - name: ZEEBE_GATEWAY_NETWORK_HOST
      value: "::/0"

You can also do the same for the broker:
env:
  - name: ZEEBE_BROKER_NETWORK_HOST
    value: "::/0"

Please confirm if this works or not for you :+1:

@neermitt did you manage to try the suggested changes by @npepinpe ?

yes it did

It did not work for me.
which image version supports ipv6 for broker and gateway?
root@z-0-25-1-broker1-01:/usr/local/zeebe# zbctl status --address 240b:c0e0:202:5e2b:b424:2:0:81ea
Error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp: address tcp/c0e0: unknown port"
it is treating address colons as the colon before port


--testnet -> --network

proposed solution for #1808 as inspired by lighthouse

Can you do one last check to change all instances of testnet to network? I think your last design doc PR, just merged, may have included more.

yeah forgot to change the docs.  they are included in these changes now

Can you do one last check to change all instances of testnet to network? I think your last design doc PR, just merged, may have included more.

yeah forgot to change the docs.  they are included in these changes now


Unable to translate handler errors of the authentication exception org.apereo.cas.authentication.AuthenticationException: 0 errors, 0 successes. Returning UNKNOWN by default...>

CAS Output isn't showing the real error, instead I'm getting this stack trace
2017-02-02 17:48:38,152 DEBUG [org.apereo.cas.audit.spi.ThreadLocalPrincipalResolver] - <Resolving principal at audit point [execution(Authentication org.apereo.cas.authentication.AbstractAuthenticationManager.authenticate(AuthenticationTransaction))] with thrown exception [org.apereo.cas.authentication.AuthenticationException: 0 errors, 0 successes]>
2017-02-02 17:48:38,157 INFO [org.apereo.inspektr.audit.support.Slf4jLoggingAuditTrailManager] - <Audit trail record BEGIN
=============================================================
WHO: alvaro
WHAT: Supplied credentials: [alvaro]
ACTION: AUTHENTICATION_FAILED
APPLICATION: CAS
WHEN: Thu Feb 02 17:48:38 CET 2017
CLIENT IP ADDRESS: <IP_ADDRESS>
SERVER IP ADDRESS: <IP_ADDRESS>
=============================================================

>
2017-02-02 17:48:38,180 ERROR [org.apereo.cas.web.flow.AuthenticationExceptionHandler] - <Unable to translate handler errors of the authentication exception org.apereo.cas.authentication.AuthenticationException: 0 errors, 0 successes. Returning UNKNOWN by default...>

Steps to reproduce:

Downloaded MAVEN Overlay.
Added properties to cas.properties
run ./build.sh

Properties set:
cas.authn.mongo.mongoHostUri=mongodb://localhost:61954/cas
cas.authn.mongo.collectionName=users
cas.authn.mongo.attributes=attribute1,attribute2
cas.authn.mongo.username.attribute=username
cas.authn.mongo.password.attribute=password
I have enabled the debug mode on the log but nothing changes. Same error as before.
So I have to questions, how to change the error to be more "helpful" and why is not working ?

CAS server version: 5.0.2

You need to be following this doc:
https://apereo.github.io/cas/5.0.x/installation/MongoDb-Authentication.html
and then use the issue template provided.


In XCode7.3 compile error import by cathage

module file was created by an older version of the compiler; rebuild 'CocoaLumberjackSwift' and try again: /Users/zouliangming/Teambition-Universal/Carthage/Build/iOS/CocoaLumberjackSwift.framework/Modules/CocoaLumberjackSwift.swiftmodule/x86_64.swiftmodule

Just run carthage build and it should work fine

would this happen to fix:  dyld: Symbol not found: __TMPdCSs18_HeapBufferStorage
started getting this.

It doesn't work. Maybe it's a CocoaLumberjack bug.

carthage update --no-use-binaries

Thank you. @kdaniel123

If its solved then we should keep it closed. People will still find it.


Add more Opentracing detail to the app

This lets you see much more clearly which parts of the processing are taking time.
Unfortunately we have to add a thousand context.Context parameters, but that can't be helped - this is the Go way.
I used reflection to get the name of Map and Reduce objects, to avoid typing in specific span calls in each of them.
The overall result can look like this (using Jaeger):

Can you fix the conflicts? Otherwise LGTM


Unified  name styles for files and folders

This Pull Request unifies name styles as requested in #2 .

LGTM, thanks


I can't open a VP9 .ivf file ?

http://aomanalyzer.org/?
Hi, I can't open a VP9 .ivf file ? Is it normal ?
thanks

VP9 files are not supported, only the latest versions of AV1 .ivf files can be opened.

The latest version of the analyzer is now part of www.arewecompressedyet.com. For example:
https://arewecompressedyet.com/analyzer.html?maxFrames=4&decoder=https://arewecompressedyet.com/runs/ll4-cdef-strength08@2017-02-28T23:44:54.065Z/js/decoder.js&file=https://arewecompressedyet.com/runs/ll4-cdef-strength08@2017-02-28T23:44:54.065Z/objective-1-fast/Netflix_FoodMarket_1920x1080_60fps_8bit_420_60f.y4m-63.ivf

I ported the analyzer to vp9 as well, you should be able to load *.ivf files now.
http://aomanalyzer.org/awcy/analyzer.html?decoder=decoder-vp9.js&file=default-vp9.ivf
Instead of default-vp9.ivf, specify an URL where CORS is enabled.

Hi ,
Thanks a lot Michael.
I’ve just tried but it doesn’t work yet. The analyzer is just saying “Downloading Files” with the wheel turning.  Perhaps my vp9.ivf is not correct. Up to now I do not know how to enable CORS. I have to check. Is it possible to get vp9.ivf file ?
Thanks a lot
Patrick
From: Michael Bebenita<EMAIL_ADDRESS>Sent: Friday, March 03, 2017 10:27 AM
To: mbebenita/aomanalyzer
Cc: Patrick Dumenil; Author
Subject: Re: [mbebenita/aomanalyzer] I can't open a VP9 .ivf file ? (#9)
I ported the analyzer to vp9 as well, you should be able to load *.ivf files now.
http://aomanalyzer.org/awcy/analyzer.html?decoder=decoder-vp9.js&file=default-vp9.ivf
Instead of default-vp9.ivf, specify an URL where CORS is enabled.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mbebenita/aomanalyzer/issues/9#issuecomment-283906810, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AXU3SzsH5VQYpL7gWf9UP4hq4KU_uYalks5rh9zJgaJpZM4MPqTb.

One thing you can try is to set up a local server using:
pyhon -m SimpleHTTPServer

and then make the analyzer point to it
http://aomanalyzer.org/awcy/analyzer.html?decoder=decoder-vp9.js&file=localhost:8000/vp9.ivf

Can you share your .ivf file? I've only tested on my own files.

Hi Michael,
Here is my file attached. It is a UHD VP9. The stream can be played with ffmpeg.
Perhaps my ivf encaps is bad ?
Thanks a lot
Patrick
From: Michael Bebenita<EMAIL_ADDRESS>Sent: Friday, March 03, 2017 12:00 PM
To: mbebenita/aomanalyzer
Cc: Patrick Dumenil; Author
Subject: Re: [mbebenita/aomanalyzer] I can't open a VP9 .ivf file ? (#9)
Can you share your .ivf file? I've only tested on my own files.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/mbebenita/aomanalyzer/issues/9#issuecomment-283926320, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AXU3S5Bz0bMlhkD9GQ4U3XMP6L1JysoMks5rh_K7gaJpZM4MPqTb.

@dumenil you'll need to attach the file directly in this github issue, not by responding using email. I think the attachments are being dropped.

here is the vp9 ivf file
crowdrun_vp9.zip
I

crowdrun_vp9.zip

Ok , I have attached the file directly to the github.
From: Michael Bebenita<EMAIL_ADDRESS>Sent: Friday, March 03, 2017 5:28 PM
To: mbebenita/aomanalyzer
Cc: Patrick Dumenil; Mention
Subject: Re: [mbebenita/aomanalyzer] I can't open a VP9 .ivf file ? (#9)
@dumenilhttps://github.com/dumenil you'll need to attach the file directly in this github issue, not by responding using email. I think the attachments are being dropped.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mbebenita/aomanalyzer/issues/9#issuecomment-284000459, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AXU3S2xL9j0CbQizbr_hnu5xNqQ6RLwvks5riD-BgaJpZM4MPqTb.

This appears to work:
http://aomanalyzer.org/awcy/analyzer.html?decoder=decoder-vp9.js&file=crowdrun_vp9.ivf
I think it's just an issue with how you are specifying the URL to crowdrun_vp9.ivf. Another thing you can try is to use the analyzer in local mode.
http://aomanalyzer.org/awcy/analyzer.html?local=1
Then, drag both the decoder-vp9.js and crowdrun_vp9.ivf files (at the same time) on the first square, then click Analyzer. You can download the .js file from, http://aomanalyzer.org/awcy/decoder-vp9.js


App will be Crash with an InfoBar and Publishing as Single File Option

Describe the bug
If we have an InfoBar in MainWindow and publish it as a Single File (PublishSingleFile = true) App will not run and will crash.
i tested with visual studio debugger and i get
Exception thrown at 0x76C0F152 in App22.exe: Microsoft C++ exception: EEMessageException at memory location 0x0377EC8C.
Exception thrown at 0x76C0F152 (KernelBase.dll) in App22.exe: 0xE0434352 (parameters: 0x80131524, 0x00000000, 0x00000000, 0x00000000, 0x00AA0000).
Unhandled exception at 0x76C0F152 (KernelBase.dll) in App22.exe: 0xE0434352 (parameters: 0x80131524, 0x00000000, 0x00000000, 0x00000000, 0x00AA0000).

Steps to reproduce the bug
1.Create a New WinUI 3 Project
2.Change To Unpackaged Project
None
3. Add InfoBar on MainWindow
<Window
    x:Class="App1.MainWindow">
    <StackPanel>
        <InfoBar
                        Title="Up To Date"
                        IsClosable="False"
                        IsOpen="True"
                        Severity="Success" />
    </StackPanel>
</Window>

4.Publish Project as Single File (PublishSingleFile = true)
5.Run Published App
Expected behavior
App should run without any problems
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.0.3
Windows app type

[X] UWP
[X] Win32

Device form factor
Desktop
Windows version
Windows 11 (21H2): Build 22000
Additional context
Tested with WASDK 1.1.0-preview1, preview2 and preview 3
i reported this issue in wasdk repo but no one tracking this issue.
microsoft/microsoft-ui-xaml#7143

@RealTommyKlein Any ideas on what could be going on here?

@ghost1372 , any idea why this is closed? This is still an issue. Should we be focusing on any one specific issue of the duplicate/related issues instead?

@beeradmoore
i reopened this issue here
https://github.com/microsoft/microsoft-ui-xaml/issues/7143

Thanks. I have gone and subscribed to that one now.


Implement startup script(s) for dia-kafka-solr

A simple utility script should be provided to aid individuals tasked with initiating the dia-kafka-solr stack for the first time.
There are a number of places where this helps out so it will be worth the investment of time.

# Zookeeper
$ cd $KAFKA_HOME/bin
$ ./zookeeper-server-start.sh ../config/zookeeeper.properties

# Kafka
$ cd $KAFKA_HOME/bin
$ ./kafka-server-start.sh ../config/server.properties
$ ./kafka-topics.sh --create dia-updates --zookeeper localhost:2181 --partitions 1 --replication-factor 3

# ISATools Producer
$ mvn package
$ ... command line logic to initiate producer service

# LabKey Producer
$ mvn package
$ ... command line logic to initiate producer service

# Solr Server
$ cd $SOLR_HOME
$ java -jar start.jar

# Solr Consumer
$ mvn package
$ ... command line logic to initiate producer service

Some notes:

each component script should be tasked with initiating a Zookeeper server to the node upon which it resides. e.g. one on Labkey, ISATools and OODT nodes respectively.


MAKE SDK seems to be taking a long time/hanging?

This is more a question then an issue. I'm trying to use the mkbreak on my E400, using a Mac. First I had to install homebrew's coreutils and replace the "readlink" with "greadlink", and then when I executed the "doit.sh" it seems to hang after "adb wait-for-device". If I cancel it, the last executed line seems to be related to make:
^Cmake: *** [Settings.apk] Interrupt: 2
So, I guess this is the ${MAKE} SDK=${SDK} executing. Is this so? Does it really take a long time to run?

Nevermind. I forgot to enable USB debugging.


ID's are required in order to create the AtomFeed.

Just updated the ReadMe to include that ID's are required.

Will be closing


Fix typo in error message

Signed-off-by: Luiz Carvalho<EMAIL_ADDRESS>

It was caught during review, but I failed to actually make the change...


How to port application developed in web based composer to desktop application composer

Since I am facing the issue #3800 about telemetry, I am trying to port the application to desktop based composer. But, the file structure is totally different between web based composer and desktop based composer.
Desktop based composer is not recognizing the file structure of the web based composer.
Is there any tool or any other way to migrate the source to desktop based composer?

Hi @kshyambabu ,
Are you trying to migrate a bot you created in the web version of Composer to the desktop version of Composer?
The two versions might differ in where your "default bot location" is, that being the location on disk where Composer stores your bot assets, however, the structure of these bot assets remain the same between the versions.
How are you trying to migrate the bot assets? You should be able to just open up Composer desktop, select "Open" in the top command bar, and point it to one of your bot folders created in Composer web.

I just found another issue which relates to my problem here


What type of update are you requesting?
Something else not listed
Current Package Identifier
Rustlang.Rust.MSVC
Package Version
1.76.0
Please describe the changes you would like to see
Would it be possible to add rustfmt to that package? I installed Rustlang.Rust.MSVC and VSCode kept throwing
[Error - 1:29:25 PM] Request textDocument/formatting failed.
  Message: Failed to spawn "rustfmt" "--edition" "2021"
  Code: -32603

After uninstalling Rustlang.Rust.MSVC and installing Rustlang.Rustup it worked. But since I use winget, I didn't want another tool to manage packages.

The MSI installer doesn't contain rustfmt.
The pre-built binaries are provided in the repo releases but they can't be executed for some reasons.
See https://github.com/rust-lang/rustfmt/issues/3075


Update tests

Update tests so they work on CI and different versions of Julia.

This PR is ready for review @juliohm.

Fixes #18

Awesome work @eliascarv. Feel free to take a new issue from the list of open issues 👍🏽


pull request for e2e test at 01/21/2017 16:15:12

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


What is the name of your component?
OpenSearch-Py
What is the link to your GitHub repo?
https://github.com/opensearch-project/opensearch-py
Targeted release date
Jan 26, 2023
Where should we publish this component?
PyPi
What type of artifact(s) will be generated for this component?
.tar.gz
Have you completed the required reviews including security reviews, UX reviews?
Yes
Have you on-boarded automated security scanning for the GitHub repo associated with this component?
Yes
Additional context
No response

Opened this retroactively, this is complete in https://github.com/opensearch-project/opensearch-py/pull/240


Question: How do I enable SSL (https)

hello,
I added my ssl key and crt file to the config, but can't reach my gogs via https. Unfortunally I havn't find any documentation or support forum.
Help would be appreciated
greetings Lennart

How to redirect HTTP to HTTPS (SSL redirection) to avoid that small file download ?

I think you can use nginx and redirect the http to https.

i can still confirm this 7 byte thing in version 0.9.0

hosted on windows server 2008 R2 64 bit

i can still confirm this 7 byte thing in version 0.9.0 when configured to use https

I don't understand this sentence...

Sorry, all i wanted to tell is that the bug mentioned by @thinking-aloud still exists in v0.9.0.
After using gogs for a while we wanted to configure it to use https.

We created cert, configured the config file and restarted the service.
problem is now:

when accessing the webservice via http (not https) a file with 7 byte of crap are being served

https for the web service is working

@TilmannBach https://unknwon.io/setup-gogs-with-https/

I too have @thinking-aloud's bug. HTTPS works fine with a let's encrypt certificate. But when you try and connect using HTTP links a file names download with no extension is downloaded.

This issue occurs when gogs' interface is accessed through http://<domain>:3000, which returns the following output :
2016/10/16 10:12:57 http: TLS handshake error from <IP_ADDRESS>:51388: tls: first record
 does not look like a TLS handshake

Everything is fine when gogs is accessed through https://<domain>:3000

@inflation
Yes, you are right, we just need to use Nginx to set up https, instead of modify app.ini file. my  git site use this method.
This is my Nginx configure file:
server {
    listen 80;
    server_name git.huanglibo.com;

    location / {
        rewrite ^(.*)$  https://$host$1 permanent;
        proxy_pass http://localhost:3000;
    }
}

server {
  listen 443 ssl;
  ssl_certificate /etc/letsencrypt/live/git.huanglibo.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/git.huanglibo.com/privkey.pem;
  server_name git.huanglibo.com;

  location / {
        proxy_pass http://localhost:3000;
    }
}

the cert and key must be in gogs folder .and the path can't recognize '~' .

@Huang-Libo
location / {
        proxy_pass  http://gogs;
    }

http 改为 https

@khs1994 你这样写没有重定向功能.

@Huang-Libo
什么重定向，不太明白

我明白了
我不改 80 配置，改的是 443 配置
server {
  listen 443 ssl;
  ssl_certificate /etc/letsencrypt/live/git.huanglibo.com/fullchain.pem;
  ssl_certificate_key /etc/letsencrypt/live/git.huanglibo.com/privkey.pem;
  server_name git.huanglibo.com;

  location / {
        proxy_pass https://localhost:3000;
    }
}

@Huang-Libo 请问一下你这样做了以后clone的哪个地方会变成https么 如果可以是反向代理了以后自然就可以么还是在哪设置的
就是这里

download.txt
我把80作为gogs的端口，443给ss用，重定向到gogs，伪装一下。
直接访问https没问题，如果访问http就会下载这个文件，trace level的日志也没有相应的输出。
可以帮忙看看这个问题吗？虽然不影响使用但是有点恼人，谢谢。

@belligerent 不太明白

@Unknwon does this mean that you have to build your own? Isn't there an argument you can pass to ./gogs web [cert] [key] binary instead?

@belligerent I searched the entire x64 tar binary and couldn't find an app.ini file?


fix: discord link

smol bug

I abuse that redirect so can you update the redirect instead?

Oh wait this is cuz of Astro, will merge and flag to team

You can keep your redirect and use data-astro-reload to prevent the router from intercepting. https://docs.astro.build/en/guides/view-transitions/#preventing-client-side-navigation
Looking into what Astro should be doing here (obviously shouldn't get an error)

We fixed this in<EMAIL_ADDRESS>thanks for letting us know!


Adding German Translations

Adding in German Translations 1 at a time for the website. The goal (with time) is the get the website accessible for all German speakers.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

We are currently not accepting translations for Guide articles for German.
Note that if people submit translations of either the README.md or the CONTRIBUTING.md, we will accept those in any language. Contributors >should create files in the /docs folder.
Thank you.


Support iPhone’s ProMotion (120hz)

Now that iPhone Pro lineup supports variable refresh rates I’m wondering if it can be achieved with Flutter? How does the plist property impacts the performance overall?

Hi @miguelpruivo
There is an open issue with lots of activity,  closing as duplicate of https://github.com/flutter/flutter/issues/90675


chore(master): release 0.2.1

:robot: I have created a release beep boop
0.2.1 (2023-08-03)
Bug Fixes

add missing container config node attributes (6900303)

Miscellaneous Chores

deps: update everything (d65b4db)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/indykite/terraform-provider-indykite/releases/tag/v0.2.1 :sunflower:


Improve Docker image

Here I would gather some ideas to improve the docker image for Kalamar.
The current docker image will basically have the Mojolicious script as its entrypoint. This is pretty flexible, but could be improved by

Adding a command to enter the shell in the container
(This may be a Mojo command or a simple entrypoint switch script like here.)

Add HEALTHCHECK command

One improvement, that is not necessary related to docker, is the run-time integration of kalamar.conf.js. If we want to switch to docker for production deployment, it is necessary to support the configuration in runtime, so we do not have to rebuild the docker image just because we want to have, e.g., different annotations in the annotation helper.

I removed the first comment regarding shell. It's more common to use docker exec for this purpose - and because of the USER this already works fine in the current image.


Improve the topology grapher

This tool is great for productivity! It draws the Process + Store topology network.
This PR tunes the rendering, mainly to show Stores using the standard flowchart symbol for data stores. The trick is to construct a matplotlib Path and let draw_networkx_nodes(node_shape=s) pass it to ax.scatter(marker=s).
Labels are bigger and .. draws as ⬆.

Q: Is there a way to enter cross-library references in Sphinx? I'm unfamiliar with this tool.
Q: Should /doc/reference/api/ be git ignored and deleted from the repo?

Q: Is there a way to enter cross-library references in Sphinx? I'm unfamiliar with this tool.
Q: Should /doc/reference/api/ be git ignored and deleted from the repo?

@1fish2 yes, Sphinx supports cross-library references with intersphinx
I think we still need /doc/reference/api/ because while it's auto-generated, I don't think readthedocs will auto-generate those files for us. It's a command I added to Makefile

@1fish2 yes, Sphinx supports cross-library references with intersphinx
I think we still need /doc/reference/api/ because while it's auto-generated, I don't think readthedocs will auto-generate those files for us. It's a command I added to Makefile

@U8NWXD How does readthedocs get the generated files? Can someone manually run Sphinx before then (and thus omit all the auto-generated files from the repo)? If not, then I guess every PR should include manually running Sphinx and committing those changes.
Whichever way, just let me know the practice to use.

@U8NWXD How does readthedocs get the generated files? Can someone manually run Sphinx before then (and thus omit all the auto-generated files from the repo)? If not, then I guess every PR should include manually running Sphinx and committing those changes.
Whichever way, just let me know the practice to use.


Service Bus AMQP Cannot read property 'address' of undefined

Package Name: @azure/service-bus
Package Version: 1.1.9

Describe the bug
/app/node_modules/rhea-promise/dist/lib/link.js:62
return this.source.address;
^
TypeError: Cannot read property 'address' of undefined
at Receiver.get address [as address] (/app/node_modules/rhea-promise/dist/lib/link.js:62:28)
at Timeout.actionAfterTimeout [as _onTimeout] (/app/node_modules/@azure/amqp-common/dist/index.js:1240:47)
at listOnTimeout (internal/timers.js:549:17)
at processTimers (internal/timers.js:492:7)
similar issue for eventhub sdk: https://github.com/Azure/azure-sdk-for-js/issues/8584

@Connor-Wood - looking in history I found this was fixed @chradek in 1.1.8:
https://github.com/Azure/azure-sdk-for-js/pull/10046

Talking with @Connor-Wood more, there might be some more to chase here.

Hi @Connor-Wood , we've released @azure/service-bus 1.1.10 which now properly handles this condition.


[BUGFIX] Allow at-rules to be parsed in strict mode

The reverts the change to CSSList in
https://github.com/MyIntervals/PHP-CSS-Parser/commit/134f4e62fe8ab9f316425f3c0f480b3f4f52d804 and adds a comment that null is an expected return value when the end of the list (or block) is reached.
Fixes #352

The reverts the change to CSSList

Or at least it should.  I found it impossible to copy and paste the previous version of the code from the GitHub diff, so went hunting for a specific version that should have contained the code to restore.  Only it didn't.  So it was a bit painstaking to actually revert that change.  Any tips to speed up the process would be greatly appreciated.

Could not open input file: .\.phive\phpcs.phar
Can't fix this without knowing what the problems are.

Could not open input file: .\.phive\phpcs.phar
Can't fix this without knowing what the problems are.

OK, fixed, using info from logs.

Can't figure out how to remove the files I added that are no longer wanted.

Can't figure out how to remove the files I added that are no longer wanted.

Non-alphanumeric characters in filenames cause problems in OSs developed in the 1970s, that are still prevelant now.  So must be avoided.

I want to convert this from draft to live.  But can't find whatever I need to do to do so.  Nothing hapens when I click the 'Draft' button.

Change the status to “Ready for review” near the bottom of your pull request to remove the draft state

Nope.  Don't see it.

Change the status to “Ready for review” near the bottom of your pull request to remove the draft state

Nope. Don't see it.

Finally found it.  What an awful UI.  Thank you Microsoft.

Wondering it we should release an 8.5.1 with this fix, since it was a regression in 8.4.

Yeah, I think backporting it to 8.5.x makes sense. We probably need to change the native type declarations to PHPDoc annotations.
Would you be willing to create the backport PR?
And should we release 8.5.1 directly after merging it, or should we first collect some more fixes?

Yeah, I think backporting it to 8.5.x makes sense. We probably need to change the native type declarations to PHPDoc annotations.

Ah, yes, the 8.x branch supports older PHP versions which don't support native type declerations.

Would you be willing to create the backport PR?

I should hopefully be able to merge the commit to main to a PR branch off the 8.x.  Then revert the type hint changes.

And should we release 8.5.1 directly after merging it, or should we first collect some more fixes?

The other outstanding PRs awaiting review mostly don't look straightforward, and may require post-review changes, so may take some time to complete.
I was keen to resolve this issue as a priority since it was a regression.  The others aren't, AFAIAA, so it would be on a case-by-case basis whether they can be easily backported once completed on main.  So I'd suggest an 8.5.1 with this fix, and some time later when the outstanding PRs have been resolved one way or another, (probably) an 8.5.2 with a rollup of fixes from those.


Add E2E test for removing all text in edit deletes reply

Summary
Add test for removing all text in edit deletes reply
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/18720
Related Pull Requests
Screenshots
Release Note
NONE

Hello @shinnlok,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Thanks for participating in Hacktoberfest! You can claim your sticker set here: https://get.printfection.com/hacktober21/4144583267 @shinnlok


(Fix) Reserved tokens plus button is renamed to 'Submit'

Closes #486
Problem: Sometimes users forget to click "+" button to add reserved tokens because of think, that it will add another one destination address.
Solution: Rename "+" button to "submit". It is supported by community users https://gitter.im/poanetwork/ico-wizard?at=5af0880b6d98e53e045be068
@dennis00010011b please take a look. I guess this change should break e2e tests.

Pull Request Test Coverage Report for Build 2111

1 of 1 (100.0%) changed or added relevant line in 1 file are covered.
9 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.04%) to 23.155%

Files with Coverage Reduction
New Missed Lines
%

src/components/stepFour/utils.js
9
0.0%

Totals

Change from base Build 2094:
-0.04%

Covered Lines:
640

Relevant Lines:
2396

💛  - Coveralls

@vbaranov e2e changed  https://github.com/poanetwork/token-wizard-test-automation/tree/master
Please update submodule and try again


Paideia: add ability for users to delete their comments

[ ] let users delete their comments
[ ] let users delete their own discussion proposals

Should DAOs have admins or moderators that can delete?

API update is live now

Has a React memory leak error
Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.


Request to support another device: Smart Water Valve

Hello,
So, i have a couple of smart water valve (bluetooth), it has a simple switch so i am hoping that it would be an easy addition.
product category: sfkzq
Please let me know what you need or how i can help.  I have access to "Device Debug" from Tuya IoT and can send switch on/off from there.
Currently, after installed the custom component, Tuya BLE detects it but throws this error:
home-assistant  | 2023-05-09 19:34:51.035 ERROR (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] xx:xx:xx:xx:xx:xx: timeout receiving response, RSSI: None
home-assistant  | 2023-05-09 19:34:51.041 ERROR (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] xx:xx:xx:xx:xx:xx: Sending device info request failed
Many thanks!

Hi,
First of all, more info from log is required to resolve the error. It could be just an issue caused by the range of your BT adapter, but could be something else.
I need also, product_id and product_name, list of device's datapoints from "Device Debug" page (name and properties of each) and most important IDs of these datapoints. Here is described how to obtain IDs:
https://www.zigbee2mqtt.io/advanced/support-new-devices/03_find_tuya_data_points.html#_9-find-your-data-point

Hi,
Thanks so much for your prompt reply.
For the log, those are all pretty much everything, it repeats until it failed.  The device is in the same room as HA.
2023-05-09 21:04:14.722 ERROR (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] XX:XX:XX:XX:XX:XX: Sending device info request failed
2023-05-09 21:05:14.765 ERROR (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] XX:XX:XX:XX:XX:XX: timeout receiving response, RSSI: None
2023-05-09 21:05:14.771 ERROR (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] XX:XX:XX:XX:XX:XX: Sending device info request failed
2023-05-09 21:06:14.818 ERROR (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] XX:XX:XX:XX:XX:XX: timeout receiving response, RSSI: None
2023-05-09 21:06:14.825 ERROR (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] XX:XX:XX:XX:XX:XX: Sending device info request failed
2023-05-09 21:06:14.831 ERROR (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] XX:XX:XX:XX:XX:XX: Connecting, all attempts failed; RSSI: None
2023-05-09 21:06:14.837 ERROR (MainThread) [homeassistant.config_entries] Error setting up entry Smart Water Timer 2F1205 for tuya_ble
File "/config/custom_components/tuya_ble/init.py", line 44, in async_setup_entry
File "/config/custom_components/tuya_ble/tuya_ble/tuya_ble.py", line 272, in initialize
File "/config/custom_components/tuya_ble/tuya_ble/tuya_ble.py", line 312, in update
File "/config/custom_components/tuya_ble/tuya_ble/tuya_ble.py", line 843, in _send_packet
File "/config/custom_components/tuya_ble/tuya_ble/tuya_ble.py", line 588, in _ensure_connected
The Device ID from IoT Platform is: "eba6f3z6zfa2zjgj", while in the log, it says: "Smart Water Timer 2F1205", so I'm not sure which one is the Product ID.  Please let me know where I can find it if this is not correct.  The product name is probably "Smart Water Timer"
DataPoints:
1 - Valve Switch
7 - Battery Level
There are other non important dp such as Cycle Timer, Weather Delay, etc..., but i dont think we care at this point, do we?

i'm happy to report that with your pointers, i was able to copy/paste your codes to make it work for me, the switch and the battery.
however, i do see this in the log, presuming that the device get disconnected when sleep?
[custom_components.tuya_ble.tuya_ble.tuya_ble] {MACID}: Device unexpectedly disconnected; RSSI: -80

About first error. I still haven't decided what is the true reason of such disconnects. If one BT device is placed near to BT adapter, disconnects is quite seldom. More devices and longer range produces more disconnects.
A second error means that the device has sent a message which is not described in the documentation. Could you please collect more logging before this error?

So, i've enabled debug and knock on woods, haven't seen the disconnect error.
Here is my entire log after i started the integration over from scratch.  Looks like the error occured after DP 17, which is "Timer".  Although the next time when DP 17 is updated, there is no error.

18:25:22.469 DEBUG (MainThread) [custom_components.tuya_ble.cloud] Successful login for<EMAIL_ADDRESS>18:25:22.482 DEBUG (MainThread) [custom_components.tuya_ble.cloud] Retrieved: uuid: xxxxxxxxxxxxxxxx, local_key: xxxxxxxxxxxxxxxx, device_id: xxxxxxxxxxxxxxxx, category: sfkzq, product_id: nxquc5lb, device_name: Smart Water Timer, product_model: SOP10, product_name: Smart Water Timer
18:25:29.027 DEBUG (MainThread) [custom_components.tuya_ble.cloud] Retrieved: uuid: xxxxxxxxxxxxxxxx, local_key: xxxxxxxxxxxxxxxx, device_id: xxxxxxxxxxxxxxxx, category: sfkzq, product_id: nxquc5lb, device_name: Smart Water Timer, product_model: SOP10, product_name: Smart Water Timer
18:25:29.028 DEBUG (MainThread) [custom_components.tuya_ble.cloud] Retrieved: uuid: xxxxxxxxxxxxxxxx, local_key: xxxxxxxxxxxxxxxx, device_id: xxxxxxxxxxxxxxxx, category: sfkzq, product_id: nxquc5lb, device_name: Smart Water Timer, product_model: SOP10, product_name: Smart Water Timer
18:25:29.043 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Initializing
18:25:29.044 DEBUG (MainThread) [custom_components.tuya_ble.cloud] Retrieved: uuid: xxxxxxxxxxxxxxxx, local_key: xxxxxxxxxxxxxxxx, device_id: xxxxxxxxxxxxxxxx, category: sfkzq, product_id: nxquc5lb, device_name: Smart Water Timer, product_model: SOP10, product_name: Smart Water Timer
18:25:29.044 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Updating
18:25:29.058 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Connecting; RSSI: None
18:25:34.394 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Connected; RSSI: None
18:25:35.457 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending device info request
18:25:35.458 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #1 FUN_SENDER_DEVICE_INFO
18:25:35.761 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #1 FUN_SENDER_DEVICE_INFO, response to #1
18:25:35.761 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received expected response to #1, result: 0
18:25:35.763 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending pairing request
18:25:35.763 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #2 FUN_SENDER_PAIR
18:25:35.981 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #2 FUN_SENDER_PAIR, response to #2
18:25:35.982 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Device is already paired
18:25:35.983 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received expected response to #2, result: 0
18:25:35.986 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Successfully connected
18:25:35.987 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #3 FUN_SENDER_DEVICE_STATUS
18:25:35.991 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #3 FUN_RECEIVE_TIME1_REQ
18:25:35.993 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #4 FUN_RECEIVE_TIME1_REQ in response to #3
18:25:35.996 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.208 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #4 FUN_SENDER_DPS, response to #3
18:25:36.209 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received expected response to #3, result: 0
18:25:36.212 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Updating
18:25:36.212 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #5 FUN_SENDER_DEVICE_STATUS
18:25:36.287 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #5 FUN_RECEIVE_DP
18:25:36.288 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 1, type: DT_BOOL: value: False
18:25:36.289 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.292 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #6 FUN_RECEIVE_DP
18:25:36.293 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 12, type: DT_ENUM: value: 2
18:25:36.294 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.297 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #6 FUN_RECEIVE_DP in response to #5
18:25:36.300 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #7 FUN_RECEIVE_DP in response to #6
18:25:36.302 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.312 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #7 FUN_RECEIVE_DP
18:25:36.312 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 7, type: DT_VALUE: value: 49
18:25:36.313 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.315 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #8 FUN_RECEIVE_DP in response to #7
18:25:36.316 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.353 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #8 FUN_RECEIVE_DP
18:25:36.354 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 9, type: DT_VALUE: value: 139993
18:25:36.354 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.357 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #9 FUN_RECEIVE_DP in response to #8
18:25:36.359 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.428 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #9 FUN_RECEIVE_DP
18:25:36.428 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 10, type: DT_ENUM: value: 0
18:25:36.429 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.430 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #10 FUN_RECEIVE_DP in response to #9
18:25:36.507 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #10 FUN_RECEIVE_DP
18:25:36.508 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 12, type: DT_ENUM: value: 2
18:25:36.509 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.517 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #11 FUN_RECEIVE_DP
18:25:36.518 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 14, type: DT_BOOL: value: False
18:25:36.519 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.522 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #12 FUN_RECEIVE_DP
18:25:36.523 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 16, type: DT_RAW: value: b'\x00'
18:25:36.523 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.525 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #11 FUN_RECEIVE_DP in response to #10
18:25:36.529 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #12 FUN_RECEIVE_DP in response to #11
18:25:36.531 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.532 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #13 FUN_RECEIVE_DP in response to #12
18:25:36.534 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.589 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #13 FUN_RECEIVE_DP
18:25:36.591 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 17, type: DT_RAW: value: b'\x00\x00\x01h\x00\x1e\x7fd\x00\x00\x00\x00\x00\x00'
18:25:36.592 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.633 ERROR (MainThread) [root] A message handler raised an exception: 32789 is not a valid TuyaBLECode.
home-assistant  | Traceback (most recent call last):
home-assistant  |   File "src/dbus_fast/message_bus.py", line 811, in dbus_fast.message_bus.BaseMessageBus._process_message
home-assistant  |   File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/manager.py", line 874, in _parse_msg
home-assistant  |     on_value_changed(message.path, self_interface["Value"])
home-assistant  |   File "/usr/local/lib/python3.10/site-packages/bleak/backends/bluezdbus/client.py", line 172, in on_value_changed
home-assistant  |     callback(bytearray(value))
home-assistant  |   File "/config/custom_components/tuya_ble/tuya_ble/tuya_ble.py", line 1284, in _notification_handler
home-assistant  |     self._parse_input()
home-assistant  |   File "/config/custom_components/tuya_ble/tuya_ble/tuya_ble.py", line 1205, in _parse_input
home-assistant  |     code: TuyaBLECode = TuyaBLECode(_code)
home-assistant  |   File "/usr/local/lib/python3.10/enum.py", line 385, in call
home-assistant  |     return cls.new(cls, value)
home-assistant  |   File "/usr/local/lib/python3.10/enum.py", line 710, in new
home-assistant  |     raise ve_exc
home-assistant  | ValueError: 32789 is not a valid TuyaBLECode
home-assistant  |
18:25:36.642 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #15 FUN_SENDER_DPS, response to #5
18:25:36.643 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received expected response to #5, result: 0
18:25:36.644 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #16 FUN_RECEIVE_DP
18:25:36.645 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 1, type: DT_BOOL: value: False
18:25:36.645 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.646 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #17 FUN_RECEIVE_DP
18:25:36.646 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 12, type: DT_ENUM: value: 2
18:25:36.647 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.648 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #14 FUN_RECEIVE_DP in response to #13
18:25:36.649 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.649 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #15 FUN_RECEIVE_DP in response to #16
18:25:36.650 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.651 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #16 FUN_RECEIVE_DP in response to #17
18:25:36.655 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: None
18:25:36.659 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #18 FUN_RECEIVE_DP
18:25:36.659 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 7, type: DT_VALUE: value: 49
18:25:36.660 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.662 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #19 FUN_RECEIVE_DP
18:25:36.662 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 9, type: DT_VALUE: value: 139993
18:25:36.662 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.664 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #20 FUN_RECEIVE_DP
18:25:36.664 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 10, type: DT_ENUM: value: 0
18:25:36.665 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.780 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #17 FUN_RECEIVE_DP in response to #18
18:25:36.781 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: -68
18:25:36.782 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #18 FUN_RECEIVE_DP in response to #19
18:25:36.783 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: -68
18:25:36.783 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #19 FUN_RECEIVE_DP in response to #20
18:25:36.784 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: -68
18:25:36.825 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #21 FUN_RECEIVE_DP
18:25:36.826 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 12, type: DT_ENUM: value: 2
18:25:36.826 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.834 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #20 FUN_RECEIVE_DP in response to #21
18:25:36.835 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: -68
18:25:36.879 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #22 FUN_RECEIVE_DP
18:25:36.879 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 14, type: DT_BOOL: value: False
18:25:36.880 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.881 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #21 FUN_RECEIVE_DP in response to #22
18:25:36.881 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: -68
18:25:36.956 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #23 FUN_RECEIVE_DP
18:25:36.956 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 16, type: DT_RAW: value: b'\x00'
18:25:36.956 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.962 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received: #24 FUN_RECEIVE_DP
18:25:36.962 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Received datapoint update, id: 17, type: DT_RAW: value: b'\x00\x00\x01h\x00\x1e\x7fd\x00\x00\x00\x00\x00\x00'
18:25:36.962 DEBUG (MainThread) [custom_components.tuya_ble.devices] Manually updated tuya_ble data
18:25:36.969 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #22 FUN_RECEIVE_DP in response to #23
18:25:36.971 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Sending packet: #23 FUN_RECEIVE_DP in response to #24
18:25:36.972 DEBUG (MainThread) [custom_components.tuya_ble.tuya_ble.tuya_ble] [Mac-Addr]: Operation already in progress, waiting for it to complete; RSSI: -68

upgraded HA to 23.5.3 and esphome 2023.5.1 for proxy and the issue seems to go away for a couple of days already, so i will close the issue.  thanks so much for your help and your work.

@kaizday Could you share your code changes you did to integrate the Smart Water Valve. I have also one of them in use and would like to integrate it into my home assistant.

@kaizday Could you share your code changes you did to integrate the Smart Water Valve. I have also one of them in use and would like to integrate it into my home assistant.

Hello. What i did was to modify at least 2 files, devices.py (devices database) and the switch.py to add the valve switch. You can also modify sensor.py to read other values such as battery level.
devices.py - prepend to line 156
"sfkzq": TuyaBLECategoryInfo(
        products={
            "nxquc5lb":  # device product_id
            TuyaBLEProductInfo(
                name="Smart Water Timer",
            ),
        },
    ),

switch.py - prepend to mapping in line 78
"sfkzq": TuyaBLECategorySwitchMapping(
        products={
            "nxquc5lb":  # Smart Lock
            [
                TuyaBLESwitchMapping(
                    dp_id=1,
                    description=SwitchEntityDescription(
                        key="water_valve",
                    ),
                ),
            ]
        }
    ),

Good luck.


Fetch or pull packages throw the error: remote already exists!

What's wrong
Cannot update (fetch or pull) package updates. Even the straight-freeze-versions doesn't work. For example, running (straight-fetch-package "ess") return this message on *straight-process* buffer:
$ cd /home/karlo/.emacs.d.vanilla/straight/repos/ESS/
$ git remote add origin https\://github.com/emacs-ess/ESS.git

error: remote origin already exists.

[Return code: 3]

Directions to reproduce

Test Case
(straight-bug-report
  :pre-bootstrap
  (message "There is no problem in this step at all.")
  :post-bootstrap
  (message "Installation is ok!")
  (straight-use-package
   '(ess))
  (message "But fetching/pull process always throw the error: remote origin already exists.")
  (straight-fetch-package "ess")
  (message "Maybe the problem is some git config on my side?"))

Test run at: 2022-07-18 10:42:53
system-type: gnu/linux
straight-version: prerelease (HEAD -> master, origin/master, origin/HEAD) a90260ae 2022-07-18
emacs-version: GNU Emacs 29.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version 1.17.4) of 2022-03-17

Output
There is no problem in this step at all.
Bootstrapping straight.el...
Bootstrapping straight.el...done
Looking for gnu-elpa-mirror recipe → Cloning melpa...
Looking for gnu-elpa-mirror recipe → Cloning melpa...done
Looking for nongnu-elpa recipe → Cloning gnu-elpa-mirror...
Looking for nongnu-elpa recipe → Cloning gnu-elpa-mirror...done
Looking for emacsmirror-mirror recipe → Cloning nongnu-elpa...
Looking for emacsmirror-mirror recipe → Cloning nongnu-elpa...done
Looking for emacsmirror-mirror recipe → Cloning el-get...
Looking for emacsmirror-mirror recipe → Cloning el-get...done
Looking for straight recipe → Cloning emacsmirror-mirror...
Looking for straight recipe → Cloning emacsmirror-mirror...done
Building straight...
Building straight...done

Test run with version: prerelease (HEAD -> develop, origin/develop) ba36462 2022-06-22
Installation is ok!
Cloning ESS (for ess)...
Cloning ESS (for ess)...done
Building ess...
Building ess...done

But fetching/pull process always throw the error: remote origin already exists.
 I just find that using (straight-freeze-versions t) solve my problem.

Hum, that's an odd error you're getting, I do think that is a bug. However, when I tried, I got no error:

Test Case
(straight-bug-report
  :pre-bootstrap
  (message "There is no problem in this step at all.")
  :post-bootstrap
  (message "Installation is ok!")
  (straight-use-package
   '(ess))
  (message "But fetching/pull process always throw the error: remote origin already exists.")
  (straight-fetch-package "ess")
  (message "Maybe the problem is some git config on my side?"))

Test run at: 2022-08-06 12:01:19
system-type: gnu/linux
straight-version: prerelease (HEAD -> develop, origin/develop) b6dba13 2022-06-12
emacs-version: GNU Emacs 28.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.33, cairo version 1.16.0) of 2022-04-30

Output
There is no problem in this step at all.
Bootstrapping straight.el...
Bootstrapping straight.el...done
Looking for gnu-elpa-mirror recipe → Cloning melpa...
Looking for gnu-elpa-mirror recipe → Cloning melpa...done
Looking for nongnu-elpa recipe → Cloning gnu-elpa-mirror...
Looking for nongnu-elpa recipe → Cloning gnu-elpa-mirror...done
Looking for emacsmirror-mirror recipe → Cloning nongnu-elpa...
Looking for emacsmirror-mirror recipe → Cloning nongnu-elpa...done
Looking for emacsmirror-mirror recipe → Cloning el-get...
Looking for emacsmirror-mirror recipe → Cloning el-get...done
Looking for straight recipe → Cloning emacsmirror-mirror...
Looking for straight recipe → Cloning emacsmirror-mirror...done
Building straight...
Building straight...done

Test run with version: prerelease (HEAD -> develop, origin/develop) fed2153 2022-07-21
Installation is ok!
Cloning ESS (for ess)...
Cloning ESS (for ess)...done
Building ess...
Building ess...done

But fetching/pull process always throw the error: remote origin already exists.
Maybe the problem is some git config on my side?

Maybe there was a change in one of the upstream recipe repositories or packages that resolved the issue. One thing that might be nice is if straight-bug-report had a way to include/use a lockfile automatically to ensure reproducibility in a bug report.


New version: HCubature v1.4.0

Registering package: HCubature
Repository: https://github.com/stevengj/HCubature.jl
Created by: @stevengj
Version: v1.4.0
Commit: 0f079b380b37f1a9fa8da3eaae22c750dc711626
Reviewed by: @stevengj
Reference: https://github.com/stevengj/HCubature.jl/commit/0f079b380b37f1a9fa8da3eaae22c750dc711626#commitcomment-33942525

Closes #1385


Intial implementation of Synchrotron device

Fixes DAQ-4934
Instructions to reviewer on how to test:

Open up an iPython terminal on machine of the beamline network (e.g. a beamline workstation)
Along with the necessary imports for a Run engine and the Count plan, so the following import: from bluesky.run_engine import call_in_bluesky_event_loop, and run %autoawait call_in_bluesky_event_loop to cope with the current multi event loop problem described in https://github.com/bluesky/ophyd-async/issues/135.
Import the synchrotron .py file and creae an OASynchrotron device using the with DeviceCollector form
Run the Count plan on the device, apssing in lambda x,y: print(y) as the second parameter to the run engine to print out the emitted documents
Confirm that the full set of documents describing the readable signals of the device and their metadat are emitted and that no errors are reported

Checks for reviewer

[ ] Would the PR title make sense to a scientist on a set of release notes
[ ] If a new device has been added does it follow the standards

@stan-dot here's the initial implementation of the Synchrotron device, we're working on attaching units etc. more appropriately, but Synchrotron is Device, which is a tree of other Devices (ring_current, etc.), with leaves of signals (ring_current.current), and reading the Synchrotron reads all of the internal devices.

Will benefit from https://github.com/bluesky/ophyd-async/pull/137 being merged prior to moving to depend on ophyd_async main (or next release), as the Descriptor is about to get a lot richer.

Code looks good to me. I'm not 100% sure why the container build is upset, clearly it's due to unpinning the dependency but that should be fine. I think we merge anyway.

@DominicOram From discussion this morning I think we'd like to either fix or get rid of the container build, whichever is easier. Any objection to the latter? I don't think dodal in a container is ever used since it's a library

PR if we decide to remove the build: https://github.com/DiamondLightSource/dodal/pull/388

Yes, happy to remove it


Error when running the exe.

Hi there,
I am trying to understand the code, but when i tested it it throws an exception.

Ah, my code right now only works on files that are at least 16MB in size right now, I didn't think to handle when the file does not support the chunk sizes are much smaller. For now please make sure the measurements file is larger than that.

Thanks for the reply.
I tried it again with the large file that I have generated based from the java code.
And again it throws the Exception:

Note, in the file I have used the '\n' as the line feed.


Implement a TiDB datastore

Creating this issue to gauge interest

Personally, not using TiDB but would switch if postgres ever fails to scale for us.
MySQL differences:
https://docs.pingcap.com/tidb/stable/mysql-compatibility
https://docs.pingcap.com/tidb/stable/pessimistic-transaction
https://docs.pingcap.com/tidb/stable/security-compatibility-with-mysql

Is there a plan for supporting TiDB datastore?

I've spent some time looking into this and I'm not sure if it makes more sense targeting TiKV or TiDB.

@eastfisher are you still interested in a TiDB datastore?

TiKV, no doubt. Unlike TiDB, TiKV is a graduated cloud native foundation project, a guaranty of long term support and far less likely to move to an Affero style license.

@frew the most important requirement is to be able to serve strong consistent reads. This is needed to support zedtokens and address the new-enemy problem. Having Snapshot Reads and Change Stream support is definitely a plus, but it can also be layered on top of the database.
TiKV could be enough as long as you are able to support multiple read access patterns (to support different types of queries). I don't know how that works at the TiKV layer but I assume it's not different from what you'd do with Cassandra, where you have to either manually denormalize (or use materialized views). In that sense using the TiDB layer may be simpler.
Have you considered exploring modifications to the current MySQL datastore driver to support TiDB?