fix: overlay error in dev mode [HDH-210]

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[x] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[x] Tested Locally
[ ] Optional Screen Shoot.

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


Combine more expressions

This PR allows more expressions to be combined with function calls, but not with match arms because I am not sure how combining interacts with wrap_match_arms option.
If it is prefered to wait before implementing, I am happy to close this without merging.

Thank you for your comment!
I have no problem putting the control flow expressions behind an option.
I have a question, after #1520 (#525) rustfmt allows match expression to overflow like closure by default.
Should we disallow this exception in favour of discussion in https://github.com/rust-lang-nursery/fmt-rfcs/issues/61, or keep the current behaviour?

Should we disallow this exception in favour of discussion in rust-lang-nursery/fmt-rfcs#61, or keep the current behaviour?

I would keep the current behaviour for now

Added an option for combining control expressions and refactoring/bug fixes to avoid regressions.

Thank you for you feedback!
I would like to improve it, probabaly we should disallow combining method chain if it goes multi line.

Added commits and rebased to resolve conficts.

I think we should perhaps default combine_control_expr to false (and add it as true to rfc-rustfmt.toml)

I added commits to reflect the feedbacks.

Thanks for all the changes!


Fixed performance counters related to AGAS cache timings

This fixes #1646

@parsa Could you verify whether this patch fixes your problem, please?


Instances of objects held by other object running in threads causes untidy shutdown issues

The order of shut down and release of objects needs to be sorted out. When shutting down, on some architectures there are error messages relating to access after free and segmentation faults. On RPi4 there is an xserver error relating to uncontrolled shutdown of threaded processes.

see 7afcee17a17ea7ab6aec4810ea979c6b87175d89 Seems better with flags set after loops ended and blocking until that's happened. Also shutdown viewer loop last of all.
There is no mechanism to stop the http loop if the keyboard is used to stop - and the other way round. Maybe there should be a comment in the configuration.yaml or in the docs warning this.


How to shared filesystems with -v

Hi
Does provided such feature in docker cli -v /tmp:/tmp ?
ContainerConfig.builder().volumes("")  seems doesn't work as i want to.

my fault,
the config in HostConfig.


reduce calling exec

There are some calls to exec to hit kubectl instead, we should be leveraging the k8s python client.

Fixed by #54.  There are still a few calls to CLI kubectl, but none in loops or performance sensitive spots.   They are primarily information gathering.


[Docs] Broken image link in README

Current State

Desired State
Link should be updated with new image location.

Contributor Guides and Resources

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma
🙋🏾🙋🏼 Questions: Layer5 Discussion Forum and Layer5 Community Slack

Can I try to work on this ?

Thanks, @rohannair11

how do I view the changes locally ?

@rohannair11 follow the steps:-
1.)fork the repo
2.)In your forked repo scroll down to readme

3.)In the top-right of readme there is edit button click it
4.)Edit the code and the check the changes with the preview button

yeah i'm following the same steps, but I what image should I fix the broken text with?

hey I opened a pr on my forked branch I guess, how should I make this PR show up on the main repo?

I think you are not commiting the changes...scroll down and commit the changes.

@KrishAryan

It shows that the PR has been merged but that's probably to my fork instead of the main repo

I think you made a new branch and merged the changes in your own branch. Merging should be from your fork to the main repo of  meshery-operator

I think it would be better to ask for help in a slack thread since you can get help from many people there.

@rohannair11 I realized that we are in different time zone, but if you post in the Slack thread, we will be able to help out to get your PR in. You have the PR merged with your forked repository.

if this issue is live I want to contribute to it. @leecalcote can you assign me, please?

@KrishAryan does this issue still exist? 🤔

I think this issue is solved as there are no broken images right now

Fixed per PR https://github.com/meshery/meshery-operator/pull/373


Terminal crashes while opening new tab when using Ubuntu as a default profile

Environment
Windows build number: 10.0.19041.208
Windows Terminal version (if applicable): 0.11.1251.0

I haven't modified terminal configuration except setting Ubuntu as a default profile.
When I open a new tab it crashes randomly, so if I just spam add new tabs it eventually happens.
I reverted default profile to PowerShell and it seems to only happen for ubuntu. Unfortunately feedback hub doesn't recognize it as a crash so I don't have a diagnostic data.
Here is the screen recording: https://streamable.com/lmooag
Steps to reproduce
open new tabs repetitively
Expected behavior
not crash
Actual behavior
crash

After further investigation, it seems to be zsh (or oh-my-zsh) specific issue. doesn't happen when using bash

Since this seemed to be an issue with your own zsh install, I'll close this issue up. Thanks for following up!


Created tests for WriteMessage method of MessageReaderWriter

Hi David,
I was looking to pick a learning exercise and decided to start to write some tests for this library, also as an opportunity to understand the implementation.
I'm opening a PR. in case you are interested in this.
Thank you,
Alessio

Looks great!


No issue - Only contact information

hello
Is there any forum/chat/fb to contact with you mytherin? You are PL?

You can contact me on reddit. You can also try finding me online on Tibia but I don't play too much; usually for an hour or so in the evenings anywhere between 21:00-23:00 CEST. I'm not Polish, I'm Dutch.


accept-whitelist instead of accept_whitelist in config is causing error

I did a composer update and an error occured after that:
Fatal error: Uncaught exception 'Zend\Stdlib\Exception\BadMethodCallException' with message 'The option "accept-whitelist" does not have a callable "setAccept-whitelist" ("setaccept-whitelist") setter method which must be defined' in /var/www/engine/canarium-appmaster/forms/vendor/zendframework/zendframework/library/Zend/ServiceManager/ServiceManager.php on line 946
( ! ) Zend\Stdlib\Exception\BadMethodCallException: The option "accept-whitelist" does not have a callable "setAccept-whitelist" ("setaccept-whitelist") setter method which must be defined in /var/www/engine/canarium-appmaster/forms/vendor/zendframework/zendframework/library/Zend/Stdlib/AbstractOptions.php on line 110

I checked the source and it seems that the accept-whitelist is causing it in config/admin.config.php. The zf-content-negotiation is expecting an underscore as a separator so changing it to accept_whitelist solves the problem.
Maybe a recent update on dependent packages is also causing this since it was working fine before the update.
Thanks

zf-content-negotiation versions 1.0.9 and 1.1.1 now allow the dash-separated configuration keys. One thing to note: prior to the change that introduces the above exception, dash-separated keys were silently ignored. The patch in zf-content-negotiation now recognizes them. The appropriate fix is for this module to use correct keys, however.

@weierophinney they get overridden by each other though, so the problem still exists, no matter how they are seperated.
This needs a merge now.


4.3.1 version is incompatible with flutter 3.16

It's basically the same as in https://github.com/daegalus/dart-uuid/issues/101, but with flutter 3.16:

Because every version of flutter_test from sdk depends on meta 1.10.0 and uuid >=4.3.0 depends on meta ^1.11.0, flutter_test from sdk is incompatible with uuid >=4.3.0.
So, because app depends on both uuid 4.3.1 and flutter_test from sdk, version solving failed.

So do we have to wait for a next version of Flutter SDK?

Sorry for the delay, busy with newborn still.
I can rollback the meta version to fix this, my apologies, I was hasty to bump the version all the way.

4.3.2 should fix this. please reopen if it doesnt


Spring Data Spanner - "findXByYLike" doesn't seem to work

@RepositoryRestResource
public interface EventRestRepository extends SpannerRepository<Event, Long> {
	public List<Event> findEventsByNameLike(String name);
}

When I call this via REST API, e.g.,
curl http://localhost:8080/events/search/findEventsByNameLike?name=Java
{"timestamp":"2018-06-27T21:00:33.142+0000","status":500,"error":"Internal Server Error","message":"INVALID_ARGUMENT: Syntax error: Illegal input character \"%\" [at 1:39]\nSELECT * FROM event WHERE ( name LIKE %@tag0 );\n                                      ^","path":"/events/search/findEventsByNameLike"}

@ChengyuanZhao Is this a bug, or we just never added support for "LIKE" queries?


Printing special characters

I have problems with special characters like ä, ö, ü. Also replacing the special characters with UTF-8 hex code was no solution. Do you have a tip for me?

Are you able to print those characters successfully using another application or their design tool?
What is printed in place of the character with a diacritical mark?
'^FT78,76^A0N,28,28^FH\^FDIch hänge das Poster an die Wand.^FS' | Out-ZebraPrinter -IpAddress <IP_ADDRESS> -Port 9100

Maybe change the encoding?  Write Unicode String In a File Using StreamWriter doesn't Work.
Change this line: https://github.com/craibuc/PsZebra/blob/d465d6944f3430a146581072c3aeca4739eeff0f/PsZebra/Public/Out-ZebraPrinter.ps1#L43
to this:
 $writer = [System.IO.StreamWriter]::new($client.GetStream(), $false, [Encoding]::UTF8)

Try toggling the last value between [Encoding]::Default and [Encoding]::UTF8.
If this works, we can add an $Encoding parameter to the function to allow it to be explicitly specified.

It was easier in the west and ultimately my fault. I hope I didn't take too much of your time.
Adding the "Encoding" parameter caused the printer not to respond.
Adding the CI28 parameter at the beginning of the ZPL code solved my problem.
Here is the working ZPL code (relevant detail row 2):
^XA
^CI28
^FT78,76^A0N,28,28^FH\^FDIch hänge das Poster an die Wand.^FS
^XZ

See the attached printed results or check Labelary

^CI = Change International Font/Encoding
28 = Unicode (UTF-8 encoding) - Unicode Character Set


Port of Hamurabi to Java (WIP)

Works for me, incremental progress ftw

Thanks, Jeff.
Up until now bugs fixes aside I've added a completed game in a single commit, but with the bigger games I think its best to upload when its in a semi workable state to show others a version is in the works. Initially at least, with so many games to choose from, its probably worth while to get all other games ported before looking at duplicate versions in the same language.
I'll make sure I finish a game before moving onto another, and will aim to have any one game finished in a few days.
I'm really enjoying converting all these games :)
Cheers


Affiliation of Frank

Coverage remained the same at 39.018% when pulling b9699dff117532c9d3e4092ddc7a8422e3213cc5 on feature/affiliation-frank into e606442f520f41b2d78d7d6672fd352a90e41b57 on develop.


Map HTML tags to custom composables

In the past in React, I've used https://github.com/remarkjs/react-markdown to render url tags with custom react components. For example a github link can be rendered as card with the projects open graph data.
I'd be nice if we had a way to intercept the HTML tags being rendered, read metadata from within it and substitute in our own custom composable.

Any update on this issues ?


Add support for all TeX fonts, by @cobordism

Allow custom Tex configuration per TexMobject,
Supply Tex configurations for all* Tex fonts,
Fixes to SVG import to allow InkScape saved files

List of Changes

Allow custom Tex configuration per TexMobject,
Supply Tex configurations for all* Tex fonts,
Fixes to SVG import to allow InkScape saved files

Motivation

@cobordism could you please state why you feel these changes are needed in a comment? i'll copy them in here.
Explanation for Changes

@cobordism could you please state why you feel your changes solve aforementioned problems? i'll copy them in here.
Testing Status
Same here.
Acknowledgement

[x] I have read the Contributing Guidelines

The most important change is that you can specify a tex template when you create a TexMobject.
Thus you can mix TexMobject("text1", template=template1) with TexMobject("text2", template=template2) in the same scene.
The second important change is that the tex template gets latex command and output format -- so I can specify that a particular template should be compiled with lualatex with a pdf output. Technically this means that the use-ctex flag is no longer needed, but I left it all in in the interests of backward compatibility.
The inkskape svg fix is a small fix and will be subsumed in the future in the revamp of the svg system.
The final piece is a collection of TeX fonts with maths support -- see here for details" http://jf.burnol.free.fr/showcase.html
These fonts needed the above changes to the latex compilation system. I have included all of the font configs from there, but some are commented out if they did not work on my machine... I suppose we can deal with them later if we wish. All this font stuff is entirely contained in the two files tex_font_template.tex and tex_font_templates.py  and can be removed, keeping my other changes.

@PhilippImhof You might want to take a look about how the integration of the font configs might be tidied up.
It all works now, but I'm sure it can be done cleaner - I'm very new at this.
I particular, I didn't use any of your tex_preamble_text or generate_usepackage constructions, nor any of the new templating system.
The issue I had was that font configs need more than just some \usepackage commands, and that some of them live strictly before the \begin{document} tag while others live both before and after; and of course that I need to be able to specify both the compiler and the output format.
[Side note, I think the functions get_text_for_tex_mode (and related functions) in TexTemplate(TexTemplateFromFile) are redundant, because they are identical to, and get inherited from, TexTemplateFromFile.]
@PhilippImhof perhaps you can think of a way to use these functions reimplemented in some kind of TexFontTemplate(TexTemplateFromFile) to better integrate the font configurations into your template engine? just a thought.

alternative suggestion: keep all the changes to the tex-to-svg pipeline and the templates, but move the font specific files into an example scene.

I agree with the causes. It is indeed useful to be able to specify the compiler, the font etc. This should be made entirely customizable.

There are changes requested on this PR, is there any progress on that front?
We also need another review, perhaps @yoshiask or @kilacoda ?

Hi,
I have finally found time to look at this again.
There are two parts to this.

Add support for alternative TeX compilers and allow you to choose a tex compiler (and template) on a per ~TexMobject~ MathTex basis.

Add the LaTeX configurations for all the latex math fonts.

For point 1. I have collected the changes here: https://github.com/cobordism/manim/tree/more-tex-options (Hey look! I even have a github account now because we can't issue merge requests from gitlab)
For point 2. I'll do that next.

Is this PR gonna require extra latex packages? Pretty much I have come with a custom LaTeX package for manim based of TexLive. Now, if this requires new Packages please inform me. For now the list of packages installed are https://github.com/yihui/tinytex/blob/master/tools/pkgs-custom.txt and  standalone preview doublestroke ms setspace rsfs relsize ragged2e fundus-calligra microtype wasysym physics dvisvgm jknapltx wasy cm-super babel-english. If that contains everything than no worries. If not tell me what should be added.

@naveen521kk I would say that people who want to use custom fonts or different TeX engines will definitely need the corresponding font files, packages and tools installed. However, IMHO this does not have to be part of your lightweight TeX bundle for manim. I think it is safe to assume that those people already have a regular LaTeX installation on their systems.

Pretty much I can assue that people use tlmgr to install missing latex packages. Maybe I will soon document it once that's ready.

Ok. Here is what I have done now.
I had added all the necessary hooks to allow anyone to chose custom tex templates (and compilers, outputs) on a per TextMobject basis.
I have taken all the special stuff I did with fonts and kept it in an example only at example_scenes/advanced_tex_fonts.py.
That should give any interested party enough information to start playing around with this without needing to add a lot of complex LaTeX config to the manim itself.
I have pushed the code to my new github repo. I will reissue the PR from there.

Does #457 mean we can close this one now?

yes sure. go ahead. close it.


Add Delay to privacy tests

Task/Issue URL: https://app.asana.com/0/488551667048375/1205316272499589/f
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3497   👈

This comment was auto-generated by Graphite.


Files created by the build are owned by root, not "runner"

Bug description
After building using the unity-builder github actions, the output files are owned by root.root instead of runner.docker like the files in git.
How to reproduce
Build.
Expected behavior
Files can be modified by the github actions
Additional details
The root cause here is that my build doesn't build to build/${{ targetPlatform }}/${{ targetPlatform}}.$EXTENSION, but somewhere else, and so I want to move the output around afterwards in the github workflow rather than in the build function, but I can't because of permissions. But it seems like, in general, this would be a better practice to run chown within the docker before finishing.

This is a tricky one. chown to whom?
Docker images are not exclusively used on GitHub, but also on Gitlab, CircleCI, Travis, Jenkins, Azure pipelines, Bamboo, and more.

Good point. I probably should have opened this on the GH action. We can get the name, though, by passing in the result of $(whoami) or $(id).
From the workflow, while we have permissions to delete the files, a chown (or for that matter, chmod, which is what I really need) failed with "permission denied".

Does this issue also happen in other CI tools (as mentioned these images are also used on GitLab, CircleCI, etc...) ?

Basically: If this issue only affects GitHub Actions self-hosted runners, maybe a simple chown-files action would be sufficient to fix the problem.
But if other tools are also affected, then the fix has to happen here, and it has to not just be #141, but also be compatible with #165

Okay, I had a little problem re-implementing #141, the license activation step was tripping up because the runner user's $HOME wasn't set correctly.
Setting it manually to "/github/home" solves this issue: https://github.com/game-ci/unity-builder/compare/main...Bradshaw:fix-root-files-and-android
I'm now taking a look at the sdkmanager issue, and will try to solve it in a way that doesn't require running as root


BlueotoothHCI dont compile in linux.

Hi Jeija. When I execute npm install, I have a compilation error in BluetoothHciSocket.
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/node-gyp/lib/build.js:190:23)
gyp ERR! stack     at ChildProcess.emit (events.js:193:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:255:12)
gyp ERR! System Linux 5.2.1-arch1-1-ARCH
gyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/neocop/src/bluefluff/fluffd/node_modules/bluetooth-hci-socket
gyp ERR! node -v v11.15.0
gyp ERR! node-gyp -v v5.0.2
gyp ERR! not ok
I'm using archlinux x86_64. Thank you

This problem is related to https://github.com/noble/node-bluetooth-hci-socket/issues/84, it's not bluefluff's fault. As a workaround, you can install the LTS version of nodejs (pacman -S nodejs-lts-carbon on Archlinux). Please let me know if this helps / close the issue if it does.

Ok Jeija, Problem solved. Now I can open the html interface and I can see the options at the left.
Thank you for your work.  :)


Fix memory

Some other changes to improve memory management.

Resetting the cursor before initializing it is not really necessary.


add podman to readme

Description
Add steps to run edge-api using podman and fix problem on fdo once we dont want compile it locally
Type of change
What is it?

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Documentation update
[ ] Tests update

Codecov Report

Merging #412 (bf808de) into main (01a3f41) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #412   +/-   ##
=======================================
  Coverage   30.71%   30.71%
=======================================
  Files          32       32
  Lines        3194     3194
=======================================
  Hits          981      981
  Misses       2109     2109
  Partials      104      104

Continue to review full report at Codecov.

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

Thanks @acosferreira 🙏🏽

I just now figured what you were trying to do, so running podman run --rm -ti -p 3000:3000 quay.io/cloudservices/edge-api:qa will solve all of your problems without anything else needed.
The :libfdo-data can be used for testing locally 😄


IsConnectable Issue

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[ ] iOS
[x] Android
[ ] UWP
[ ] .NET Standard

Feature Library

[ ] Core
[x] BluetoothLE
[ ] Locations
[ ] HTTP Transfers
[ ] Notifications
[ ] Sensors

Version of OS(s) listed above with issue
Version of Library
<IP_ADDRESS>
Expected Behavior
Not to crash
Actual Behavior
Crash
I checked Bluetooth LE in Shiny and figured out that if you try to use IsConnectable property you have a crash on Android 7-. So, it would be better if the library can handle it.
Also, users need to spend time to realize the root cause. I Found a comment in the source code that this property supported only in Android 8+
https://github.com/shinyorg/shiny/blob/1d8d4f97b961a6e5b42105df7678adf6ea95f747/src/Shiny.BluetoothLE/Central/Platforms/Android/AdvertisementData.cs
It would be better to have the description in order to be able to see that this property supported only for several android versions.

Thanks for the help


It doesn't work

I have tried to install following "How to install the Awesome version"
But it doesn't change anything.
What is the matter?
Thx!

I have the same problem.


Microsoft.Azure.Documents.ServiceUnavailableException is internal to Microsoft.Azure.Cosmos.Direct

Is your feature request related to a problem? Please describe.
We have the need to track when Microsoft.Azure.Documents.ServiceUnavailableException exceptions are thrown by the Cosmos DB SDK. Unfortunately it and its parent class, Microsoft.Azure.Documents.DocumentClientException, are internal to the Microsoft.Azure.Cosmos.Direct assembly. Furthermore, we really want to track the sub status code on the ServiceUnavailableException but the sub status code is a field on DocumentClientException and the Microsoft.Azure.Documents.SubStatusCodes enumeration is also internal to the Microsoft.Azure.Cosmos.Direct assembly.
Describe the solution you'd like
Is it possible to make ServiceUnavailableException, DocumentClientException, and SubStatusCodes public types while also making the sub status code on DocumentClientException a public property?
Describe alternatives you've considered
To get around this, we have to catch a plain Exception then use reflection to identify the exception as a ServiceUnavailableException then get its sub status code.
try
{
    // ...
}
catch (Exception ex)
{
    var cosmosDirectAssembly = Assembly.Load("Microsoft.Azure.Cosmos.Direct");
    var typeOfServiceUnavailableException = cosmosDirectAssembly.GetType("Microsoft.Azure.Documents.ServiceUnavailableException", false);
    var typeOfCosmosSubStatusCodes = cosmosDirectAssembly.GetType("Microsoft.Azure.Documents.SubStatusCodes", false);
    var typeOfNullableCosmosSubStatusCodes = typeof(Nullable<>).MakeGenericType(typeOfCosmosSubStatusCodes);
    var typeOfDocumentClientException = cosmosDirectAssembly.GetType("Microsoft.Azure.Documents.DocumentClientException", false);
    var serviceUnavailableExceptionSubStatusCode = typeOfDocumentClientException
                    .GetFields(BindingFlags.Instance | BindingFlags.Public | BindingFlags.NonPublic)
                    .FirstOrDefault(p => p.FieldType == typeOfNullableCosmosSubStatusCodes);

    if (ex.GetType() == typeOfServiceUnavailableException)
    {
        var subStatusCode = serviceUnavailableExceptionSubStatusCode.GetValue(ex);
        // Log the substatus code
    }
}

Microsoft.Azure.Documents.ServiceUnavailableException is not thrown by the SDK.
They are all CosmosException.
Please see: https://github.com/Azure/azure-cosmos-dotnet-v3/blob/master/Exceptions.md#typed-apis
If you have evidence of a Microsoft.Azure.Documents.ServiceUnavailableException being thrown to the application, please reopen this Issue with the full stack trace and exception's ToString()

@ealsur

ServiceUnavailableException and other DocumentClientException derived exceptions might not be thrown directly by the SDK, but they are included as inner exceptions of CosmosException - for example GoneException. IMHO it's inconsistent to have an internal-typed inner exception of a publicly-typed thrown one.
CosmosException contains a public SubStatusCode property, whose value would be some Microsoft.Azure.Documents.SubStatusCodes which is internal. So again, the same inconsistency where you expose internal-typed information in a publicly-typed exception.

The stack trace below demonstrates both points above:

Microsoft.Azure.Cosmos.CosmosException : Response status code does not indicate success: ServiceUnavailable (503); Substatus: 0; ActivityId: xxxxx-xxxx-xxxx-xxxx-xxxxxxx; Reason: (Service is currently unavailable. More info: https://aka.ms/cosmosdb-tsg-service-unavailable
ActivityId: xxxxx-xxxx-xxxx-xxxx-xxxxxxx, Microsoft.Azure.Cosmos.Tracing.TraceData.ClientSideRequestStatisticsTraceDatum, Linux/2.0 cosmos-netstandard-sdk/3.22.2);
---> Microsoft.Azure.Documents.GoneException: The requested resource is no longer available at the server.
ActivityId: xxxxx-xxxx-xxxx-xxxx-xxxxxxx, Linux/2.0 cosmos-netstandard-sdk/3.22.2
at Microsoft.Azure.Documents.TimeoutHelper.ThrowGoneIfElapsed()
at Microsoft.Azure.Documents.StoreReader.ReadMultipleReplicasInternalAsync(DocumentServiceRequest entity, Boolean includePrimary, Int32 replicaCountToRead, Boolean requiresValidLsn, Boolean useSessionToken, ReadMode readMode, Boolean checkMinLSN, Boolean forceReadAll)
at Microsoft.Azure.Documents.StoreReader.ReadMultipleReplicaAsync(DocumentServiceRequest entity, Boolean includePrimary, Int32 replicaCountToRead, Boolean requiresValidLsn, Boolean useSessionToken, ReadMode readMode, Boolean checkMinLSN, Boolean forceReadAll)
at Microsoft.Azure.Documents.QuorumReader.ReadQuorumAsync(DocumentServiceRequest entity, Int32 readQuorum, Boolean includePrimary, ReadMode readMode)
at Microsoft.Azure.Documents.QuorumReader.ReadStrongAsync(DocumentServiceRequest entity, Int32 readQuorumValue, ReadMode readMode)
at Microsoft.Azure.Documents.ReplicatedResourceClient.<>c__DisplayClass31_0.<b__0>d.MoveNext()
--- End of stack trace from previous location ---
at Microsoft.Azure.Documents.RequestRetryUtility.ProcessRequestAsync[TRequest,IRetriableResponse](Func1 executeAsync, Func1 prepareRequest, IRequestRetryPolicy2 policy, CancellationToken cancellationToken, Func1 inBackoffAlternateCallbackMethod, Nullable1 minBackoffForInBackoffCallback)    --- End of inner exception stack trace ---    at Microsoft.Azure.Documents.ShouldRetryResult.ThrowIfDoneTrying(ExceptionDispatchInfo capturedException)    at Microsoft.Azure.Documents.RequestRetryUtility.ProcessRequestAsync[TRequest,IRetriableResponse](Func1 executeAsync, Func1 prepareRequest, IRequestRetryPolicy2 policy, CancellationToken cancellationToken, Func1 inBackoffAlternateCallbackMethod, Nullable1 minBackoffForInBackoffCallback)
at Microsoft.Azure.Documents.StoreClient.ProcessMessageAsync(DocumentServiceRequest request, CancellationToken cancellationToken, IRetryPolicy retryPolicy, Func`2 prepareRequestAsyncDelegate)
at Microsoft.Azure.Cosmos.Handlers.TransportHandler.ProcessMessageAsync(RequestMessage request, CancellationToken cancellationToken)
at Microsoft.Azure.Cosmos.Handlers.TransportHandler.SendAsync(RequestMessage request, CancellationToken cancellationToken)

@ohads-MSFT  I don't understand the intent of your comment.
The OP asked how to detect the ServiceUnavailable error, to which the answer is, in V3 SDK, there is no specific exception, just catch the CosmosException and match the StatusCode. That completes the requirement. There is no need to dig into the InnerExceptions to achieve this.

Sure, there might be other internal exceptions but what is the problem with that? If your intent is to detect a Service Unavailable exception, you simply use the CosmosException and get the Status 503. Which exactly is your use case that you require identifying the Inner Exceptions?
The CosmosException exposes the headers returned in the service response through the Headers property. If you want to read the substatus, you can use Headers["x-ms-substatus"]. Which is the use case where you need the substatus to programmatically action on the error?

@ealsur

I don't have a specific use case in mind, but for example it might be interesting to check GoneException::LocalIp or one of the DocumentClientException properties that aren't exposed on the CosmosException (e.g. StatusDescription).
Getting the substatus is not the issue, indeed I have it under the public CosmosException::SubStatusCode. As you mentioned, the issue is acting upon it programmatically, namely comparing the substatus to some known values in the currently internal enum SubStatusCodes. I imagine there might be various use cases, but if I were to speak to ours, it's for detecting client-side issues specifically (e.g. TimeoutGenerated410). For example, we might to translate these into other HTTP responses back to the original caller (e.g. 429).

If there are any properties that you require access, please let us know and we'll help understand how you can access them. Why do you need to check for GoneExceptions? It is an internal type and was not even public on V2 SDK (so it is not a migration gap), giving access just for the sake of access?
If the intent is to propagate to the original caller, then you can simply propagate all Headers, that should be the correct thing, because you don't know which header the caller is interested on. Maybe the caller wants to know the Session Token. So in that scenario, just iterate over the Headers and add them to the response, for example: https://github.com/ealsur/ondotnet-cosmosdb/blob/master/src/episode1/streams/Controllers/ItemsController.cs#L40-L57. For 503 troubleshooting, there is nothing you can programmatically do based on the substatus. If its 20001 or 20002, there is no code you can change to act on it, in both cases, you are experiencing connectivity issues, the recommendation for both is the same for your application: https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/conceptual-resilient-sdk-applications#timeouts-and-connectivity-related-failures-http-408503. Now, if the volume of these 503s exceeds the expectations yes, the Substatus and the entire Diagnostics help root causing, but fixing the issue is not something the application, from code, can do, it's someone who is diagnosing the details that needs to act on it.

I want to reiterate, if the use case is there, we will help either making the information accessible through public methods or properties if it's not or helping with how you can obtain it from the current public methods. But there should be a use case for it, there should be value in exposing that.
Everything described in this thread so far is achievable through the current public surface API.


Fix token weaver not reading tokens from single token studio JSON file

fixes #9

You can ignore files under dist/ when reviewing. They are generated distribution files and we have CI check to verify that we have up-to-date dist files


Report half-blank - CommitmentDiscounts.pbix - FinOps hubs 0.2.1-rc2

🐛 Problem
TODO: After redeploying FinOps hubs 0.2.1-rc2 from HERE.
Then downloading the new CommitmentDiscounts.pbix from HERE
I am left with a half-blank report. Only Purchases and Hybrid Benefit have data present. Other tags don't have the subscriptions/services etc.
👣 Repro steps
1: Open CommitmentDiscounts.pbix
2. Enter transform data.
3. Open CM connector: scope (must enter scope here even though I use hub)
4. CM connector: number of months - set to 2.
5. FinOps Hubs - Storage URL - update to my deployment hub output URL.
6. Update Rangestart and range end to 01/12/23 - 31/01/2024
7. CLOSE AND APPLY
All queries loading successfully. No error presented.
Click Commitments, loading icons turn, no data presented. (BLANK)
Cannot select date range in the Commitment tab.
All other tabs up to Purchases are blank.
In purchases I can only select current month. All other days are unselectable.

Go back to Commitments tab, only FROM date is now present. However I can now select any date (even back before my exports are present). This doesn't change the blank data however.
ℹ Additional context
If I enter the CostDetails query - I do get data here. A lot of nulls but important items like effective cost, usage quantity are populated.

RecommendationsSingle - blank
RecommendationsShared - blank
InstantSizeFlexibility - populated ok

For reference, the CostSummary.pbix report looks ok (I feel some months look wrong, but cannot confirm yet).
Commitments Tab doesn't look great however;

@psilantropy I was just coming here to file a bug that was reported where the table is empty. There's a PricingCategory filter in the Commitment discounts report that was set wrong. The fix is easy. Just edit the filter to filter on Commitment-Based instead of Commitment Discount.
You'll need to apply it to the following pages:

Commitments
Savings
Chargeback
Prices

I'm about to submit a PR. I'll associate it with this issue for now but please let me know if that's the issue you're running into.

@allcontributors please add @psilantropy for bug

@all-contributors please add @psilantropy for bug

I'm about to submit a PR. I'll associate it with this issue for now but please let me know if that's the issue you're running into.

Sorry was away a few days. Yes that was exactly the issue and your filter change results in data now. Thank you :).
However, now I see the commitments data - Savings plan data results in an incorrect savings calculation.

This is the same result I get from the Azure Savings Dashboard. So maybe I have something strange going on here.
This issue is in any tab that includes Savings Plan.


Generic formatter Keccak-ECDSA using FFMul

Explain your changes:

This PR updates the converter from https://github.com/MinaProtocol/mina/pull/13819 to be more generic in the type of inputs it accepts. Now, it is not tailored for 256-bit inputs and 256-bit outputs only, but arbitrary lengths.

Explain how you tested your changes:

Now the negative test for larger inputs works, because it reduces arbitrary lengths.

Closes https://github.com/MinaProtocol/mina/issues/13912

Parent PR has been closed, closing this one too.


Delete .validation

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@ChuckFerring @palenshus

https://github.com/microsoft/winget-pkgs/tree/master/manifests/a/AcFun already exists. So, https://github.com/microsoft/winget-pkgs/tree/master/manifests/a/acfun/acfunlive needs to be deleted.


[Bug]: @shopify/app >= 3.55 includes vulnerable version of lodash.set

Please confirm that you have:

[X] Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
[X] Reproduced the issue in the latest CLI version.

In which of these areas are you experiencing a problem?
App
Expected behavior
npm audit should show 0 vulnerabilities
Actual behavior
npm audit shows 5 high severity vulnerabilities if you install v3.55 or higher
Verbose output
# npm audit report

lodash.set  *
Severity: high
Prototype Pollution in lodash - https://github.com/advisories/GHSA-p6mc-m468-83gw
fix available via `npm audit fix`
node_modules/lodash.set
  @shopify/theme-check-common  *
  Depends on vulnerable versions of lodash.set
  node_modules/@shopify/theme-check-common
    @shopify/theme-check-docs-updater  *
    Depends on vulnerable versions of @shopify/theme-check-common
    node_modules/@shopify/theme-check-docs-updater
      @shopify/theme-check-node  *
      Depends on vulnerable versions of @shopify/theme-check-common
      Depends on vulnerable versions of @shopify/theme-check-docs-updater
      node_modules/@shopify/theme-check-node
        @shopify/app  <=0.0.0-nightly-20240207151516 || >=3.55.0
        Depends on vulnerable versions of @shopify/theme-check-node
        node_modules/@shopify/app

### Reproduction steps

1. Use `"@shopify/app": "^3:` in your `dependencies`
2. npm update
3. You will recieve the error and cannot fix it with `nppm audit fix`
5. Change to `"@shopify/app": "3.54"` in your `dependencies`
6. npm update
7. You will no longer receive the error

### Operating System

All

### Shopify CLI version (check your project's `package.json` if you're not sure)

3.55

### Shell

zsh

### Node version (run `node -v` if you're not sure)

v21

### What language and version are you using in your application?

All

I believe https://github.com/Shopify/cli/pull/3405 fixes this and will be included in the next CLI release.


how to use --enable-shared ?

I've tried to fork this repository and add --enable-shared to this line
https://github.com/heroku/heroku-buildpack-python/blob/main/builds/runtimes/python3#L26
./configure --prefix=$OUT_PREFIX --with-ensurepip=no --enable-shared
make
make install

but it not works my heroku builded without using the python that have enable-shared
even I think heroku build the python without using my buildpacks at all
any guidance how to use python3 that compiled using --enable-shared ?

@buncis Hi! The scripts under builds/ in this repository are not run when each app is built using the buildpack, but separately when releasing new Python versions to S3. You will need to run the compile scripts uploading to your own S3 bucket (build docs), then use BUILDPACK_S3_BASE_URL to point at that bucket (after mirroring the other contents eg pip wheels). BUILDPACK_S3_BASE_URL cannot be set as an app env var, and will need to be set via an earlier buildpack's export script (or just fork the buildpack).

@edmorley thanks for the quick response
I see, so the correct way to enable-shared is just like this fork right ?
https://github.com/ReforgeHQ/heroku-buildpack-python/commit/813825b1d886aa78f70070cedcae3aeb1ea8fe46
I've tried that way too, I fork that fork and change the line to my desired python version but somehow its not working and I forced to use heroku-18 stack for that fork
ok please bear with me
so what I need to do is
[ ] compile the python myself with --enable-shared configuration
[ ] upload the compile result to amazon s3
[ ] fork this heroku-buildpack-python and change the BUILDPACK_S3_BASE_URL to my own s3

so what I need to do is

Yeah that's one approach.
Another would be to just compile during the build, and store the result in the cache, so you don't need to mess about with S3.
Example at:
https://github.com/heroku/heroku-buildpack-python/issues/488#issuecomment-659579578
(Though note this is all unsupported and you'll unfortunately mostly need to figure this out yourself)

I think I will follow that #488 approach since its almost have same use case and simpler
but I don't know where to put the post_compile scripts
did this is the correct file ?
https://github.com/heroku/heroku-buildpack-python/blob/f3abce6ac660a009c7ffac95d5b86d231555c28a/bin/steps/hooks/post_compile
yeah If I could pass this
I think I will make a wiki/tutorial post @https://github.com/mrkn/pycall.rb since some people have same trouble as me

I manage to solved it by using approach mentioned in https://github.com/heroku/heroku-buildpack-python/issues/488#issuecomment-659579578
my post_compile scripts
set -e
buildpack_url=https://github.com/heroku/heroku-buildpack-python
buildpack_vsn=v197

# rebuild python if it's missing enable-shared
if  ! python3 -msysconfig | grep enable-shared \
    > /dev/null; then
  PYTHON_VERSION="$(< runtime.txt)"
  git clone -b "$buildpack_vsn" "$buildpack_url" _buildpack
  export WORKSPACE_DIR="$PWD/_buildpack/builds"
  rm -f .heroku/python/bin/python   # prevent failing ln after build
  sed -i 's!figure --pre!figure --enable-shared --pre!' \
    "$WORKSPACE_DIR"/runtimes/python3
  "$WORKSPACE_DIR/runtimes/$PYTHON_VERSION" /app/.heroku/python/
  rm -fr _buildpack
fi

latest build log and quick check
remote: Verifying deploy... done.
To https://git.heroku.com/xxxx.git
   7349abb..2a3c3cf  master -> master
~/xxxx (master) $ heroku run bash
 ›   Warning: heroku update available from 7.56.0 to 7.56.1.
Running bash on ⬢ xxxxx... up, run.8039 (Free)
~ $ python
Python 3.8.10 (default, Jul 30 2021, 07:53:46)
[GCC 7.5.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sysconfig
>>> sysconfig.get_config_vars('Py_ENABLE_SHARED')
[1]
>>> exit()
```

As of #1320 the Python binary build scripts now use --enable-shared for Python 3.10+.
Existing binaries are not being recompiled, so this will only take effect for future Python releases (ie: the future Python 3.10.5+) or for new stacks (ie: for Heroku-22's 3.10.*, once Heroku-22 is released).


Getting an Uncaught ReferenceError: Tooltip is not defined in the javascript console

My setup :

OmniDB 3.0.2b running under Ubuntu Server 20.04.1
Apache setup as a reverse proxy to access omnidb (which is running under <IP_ADDRESS>:8000/omnidb) through the /omnidb route

What I do :

Start a PostgreSQL connection
Right click on any item that supports edition or creation (such as a database, a schema, a table...)
Click CREATE ... or ALTER ... button

What happens:

I get an Uncaught ReferenceError: Tooltip is not defined in the javascript console, with a long error dump (I can send it if needed)

Extra information :
The first time this error happened, it told me "Webserver was shutdown" (and didn't complete the query), so obviously restarted the server, after checking the console and seeing that error dump.
After I restarted the process, strangely, it had removed the CUSTOM_PATH = 'omnidb' line from my config file, to replace it with CUSTOM_PATH = ''
Later instances didn't change that line.
I really don't know what to make of that error

Hi @Faholan ,
I just tried to reproduce the bug you reported without success.

v3.0.2b
Debian 10
Chrome and Firefox

Will try again later tonight with extra scenarios to reproduce that behaviour.
When that happens, does it break the interface as well / prevent the creation of the new tab that should result from the context  or is it just the tooltip error on the dev console?
If you want you can send the error to me so I can have a look there as well.
<EMAIL_ADDRESS>Best regards

Hi @Faholan ,
I just tried to reproduce the bug you reported without success.

v3.0.2b
Debian 10
Chrome and Firefox

Will try again later tonight with extra scenarios to reproduce that behaviour.
When that happens, does it break the interface as well / prevent the creation of the new tab that should result from the context  or is it just the tooltip error on the dev console?
If you want you can send the error to me so I can have a look there as well.
<EMAIL_ADDRESS>Best regards

This bug doesn't prevent the creation / edition, so I guess it must not be that important. I was more worried about any issue I wouldn't be seeing, because I don't know what that prevents omnidb from doing.
I also tried to reproduce it with another instance of OmniDB, same message. Maybe it's just my browser that's bugged ?
But yes, as far as I know, this doesn't prevent me from doing anything, and it only seems to appear in the console.

This bug doesn't prevent the creation / edition, so I guess it must not be that important. I was more worried about any issue I wouldn't be seeing, because I don't know what that prevents omnidb from doing.
I also tried to reproduce it with another instance of OmniDB, same message. Maybe it's just my browser that's bugged ?
But yes, as far as I know, this doesn't prevent me from doing anything, and it only seems to appear in the console.


wstring (utf16) -> string (utf8) transition (community feedback requested)

As mentioned in e.g. #334, I intend to replace the usage of std::wstring in the Result struct with utf8 encoded std::string for better interoperability with non-windows systems. The question is: how to go about doing that with minimally annoying users of the library? I currently see these options:

introduce a preprocessor macro ZX_USE_UTF8 that client code can define before including ReadBarcode.h that would switch the return type of Result::text() to std::string. The absence of this macro could trigger a deprecation compiler warning. In a second phase I could then default to using utf8 but introduce a ZX_USE_UTF16 macro that switches back to std::wstring to allow a 1-line fix or even a build environment setting to go back to the old ways.

introduce 2 new Result properties: std::string utf8() and std::wstring utf16(), the latter being an alias for the current text(). This would not introduce a breaking change and lend itself to keep both variants indefinitively. If feels like less hassle but also a bit unusual and over the top. It is also no solution for the std::wstring ecLevel(), which will simply be an ASCII std::string. :-/

This question is also related to #333.
Any feedback on preferences or even other alternatives welcome.

It seems either no-one has read this post or no-one cares. Would anyone object if I skipped all the transition effort and simply changed the return type of text, thereby breaking all of your code? :-P

Thanks for your comment. I think content is not a good name as it does not convey a distinction to bytes. Both are representation of the content of the symbol. In fact I think the meaning 'human readable interpretation' is exactly what would be most helpful for most of the users. It is also at the core of the whole binary content discussion. And with that in mind I was already looking into bringing the GS1 "(ai)data" format from DataBar to generally all GS1 codes and ideally remove that internal transformation from the bytes channel where it certainly doesn't belong - except if that was actually specified in the DataBar spec, which I did not check, yet, but seemed unlikely.
As an alternative to simply doing that translation to all GS1 codes, one could argue to introduce a DecodeHints flag to enable it or to supply a separate helper function that can be used to make that transformation.

Any feedback on preferences or even other alternatives welcome.

From the KDE consumer point-of-view where we have to support multiple ZXing versions provided by Linux distributors for some time usually: The second option seems a bit easier and slightly more predictable, but since we have to wrap the usage in version check ifdefs for some time anyway the difference isn't all that big either.

Re GS1 it is defined that way in the GS1 General Specifications, i.e. the data is the AIs followed by their data fields, with <GS> separators inserted where required. It is not the "(ai)data" form, which is the Human Readable Interpretation, which is intended to be printed with the barcode in case manual entry is required. (There is another form, what they unhelpfully call "Non-HRI Text", which is an expanded version of HRT with the AIs labeled - see GS1 General Specifications 22.0 (2022), Section 4.15.)
On the general point, I haven't followed the text/binary discussion closely but my general impression is that it's a wrong-headed distinction. There's the byte stream - what is now named bytes() (good name). There is the bytes interpreted according to the character encodings (specified or otherwise) - what is now named text() (bad name). There should also be a separate API returning the GS1 HRI, which would return the "(ai)data" format, named hri() or something. It would also be nice to supply an API returning the GS1 "Non-HRI Text" form.

Re HRI form it could also deal with e.g. ISBN formats (with dashes inserted), and other non-GS1 formatting.

It seems non-controversial that bytes or actually bytesECI is or rather should be the basic ISO conform 'content' of the symbol. (By the way: I'm ok with the term bytesECI but am open for creative alternatives). Then we have conceptually two more views:

utf8 version (of bytes)
HRI version (of utf8 version of bytes)

I'm questioning how pronounced these two variants need to be represented in the API?

just provide the HRI version
provide a hint to switch between the two
provide two separate 'channels'

The choice of name(s) is dependent on which of these end up being used. Since we currently have 1) and no-one was asking for more, I did not feel the need to provide even more channels than the 4 we have right now. But since I don't want to break the API anytime soon again, I'd rather end up with something lasting, i.e. capable enough.
I'd like to hear from people actually using this in production code/apps what their use cases are with respect to the different 'types' of content. @markusfisch @vkrause @huycn (if I should stop mentioning individuals in these kind of potentially annoying "say something" pokes, please let me know ;)).

@vkrause thanks. What is your stance on the utf8 vs. HRI question? How do those two fit into your landscape? Do have a use for both, if not, which one then?

Update on my current plan regarding the successor of text: introduce std::string utf8() and std::string hri() (the full name humanReadableInterpretation() is just too ugly for my taste).
That leaves the question how to deal with the remaining std::wstring ecLevel()?

introduce eccLevel
introduce errorCorrectionLevel
simply replace the return type, introducing an API braking change without deprecation warning
do the whole macro dance describe above (I don't see that coming)

A google search shows actually 4x the results for eccLevel compared to ecLevel but the QRCode spec uses the term "error correction level" not "error correction capacity level".
I assume very few people are making use of this member anyway so maybe option 3 is practical. As usual: comments welcome.

Am 18.06.2022 um 16:32 schrieb axxel:

Update on my current plan regarding the successor of |text|: introduce
|std::string utf8()| and |std::string hri()| (the full name
|humanReadableInterpretation()| is just too ugly for my taste).
That leaves the question how to deal with the remaining |std::wstring
ecLevel()|?

introduce |eccLevel|
introduce |errorCorrectionLevel|
simply replace the return type, introducing an API braking change
without deprecation warning
do the whole macro dance describe above (I don't see that coming)

A google search shows actually 4x the results for |eccLevel| compared to
|ecLevel| but the QRCode spec uses the term "error correction level" not
"error correction capacity level".

My personal perception is, that "ECC" means "Error correction Code" and
is a well established term. But I am in Data Matrix, not in QR.
Maybe, the QR code spec may be enhanced here.
THanks,
Harald

Maybe, the QR code spec may be enhanced here.

I don't see any issue with the terms used there. Both QR and DM spec use the term "error correction level" (so neither "error correction capacity level" nor "error correction code level") hence, I would not have chosen eccLevel when starting from scratch but ecLevel (or the long form). This led me to double check my google search and it turns out, I failed at using google!?! I also gave the github search a go and both agree that ecLevel is by far the more popular term (no wonder, as it is more accurate).
So this leaves option 2 and 3 on the table. I vote for 3 (just switch the return type). Those who agree, please leave a thumbs up, the others a thumbs down.

Sorry people but I have to admit that I am turning in circles here. When making up my mind about the name utf8 I was too narrowly focused on the c++ Result class and the distinction between bytes and the "utf8 version" thereof and since it seemed an easy way out of the deprecation issues, I liked the idea (better than any other I had/heard that far). Now properly taking the wrappers into account, it is obvious to me that utf8 does not make any sens there at all. We still need a name for that as well and if that stays text (which it could without disruption as there is no type transition required) then there is a strong argument to use it on the c++ side as well, if only for consistency.
The only other meaningful alternative I could come up with is str or string (see e.g. the python type). I agree with @gitlost that the term text semi-implies 'human readable', which this blob of data will not strictly be. It feels like string carries that meaning less so but therefore focuses more on the 'data type' instead of the 'content type' which is unfortunate. The problem would be solved if we did not need this channel at all and only provided bytes and text where the latter would mean the HRI. I have the gut-feeling that those 2 variants are the most helpful anyway: Those who need the 'raw' or the 'standard' data will go for bytes and those who end up displaying a string on screen will be better served with the HRI (maybe with some escaping of non-graphical characters like the -escape option of ZXingReader for anything non-text).
I could still let there be the current utf8 property but it will serve a yet to be found use case and not be exposed in any of the wrappers (until demand is expressed).
Notes:

the term utf8ECI does not have this problem as it does explicitly contain exactly that (utf8 encoded bytes according to the ECI protocol)
text is an established name and is also used by at least one commercial SDK
if it was not for the type transition issue, I would not have considered changing it

I read the relative silence from you guys on this matter as a sign that it is just not that important to you how this one function is called, which I understand completely...

To make some progress here, I decided to go the original #define ZX_USE_UTF8 route and keep text and only switch the return type. To make that an ABI compatible, client side switch, text is inline and either calls utf8 or utf16. Whether those two stay after the completed transition will be decided later. Same goes for the question of whether text will return a HRI version of utf8 or if a new hri will be added for that.
This should be close to release 1.4 now to get the deprecation warnings out and about. Please merge and test your code and let me know if something broke. Thanks.
Before releasing, I'll make sure the android, python and Qt wrappers will have access to the contentType and both bytes and text.

@gitlost @oehhar I'm about to push a new API that translates GS1 strings to their HRI version (extracting it from the DataBar code base). I'm not happy with the naming ideas I came up so far. The main issue being that I don't know how these strings are called within the GS1 System. I glanced at the spec but could not find a proper term. My current ideas:

HRIFromGS1
HRIFromGS1AIs
HRIFromGS1System
HRIFromGS1String

Any better ideas?

I prefer HRIFromGS1. No better idea.
Harald

Thanks for your quick feedback. It is a freestanding global function that is meant to be later used in Result::text() or Result::hri(). See 24b737365358bdb0e404e65cb70d0071362159f7.

@gitlost Reimplementing the DataBarExpanded bit stream decoder to get rid of both DecodeStatus usage and the hard-coded HRI stuff going on there, I came across two issues:

rssexpanded-3/13.png contains the 'raw' substring<PHONE_NUMBER>888888888888888888888888888888888888888888888888. 3922 has a max length of 15 according to the spec. My new HRIFromGS1 fails then decode this. My interpretation: this is an invalid symbol.
There are a bunch of samples that contain the 422 field which is fixed size 3 but then have a FNC1 follow it. Again invalid according to my understanding.

Comments?

Re 1. yes this is invalid GS1. How to treat this? - not sure.
Re 2. there's only a set number of AIs which are considered "predefined length", the first 2 digits of which are listed in GS1 General Specifications v22.0 Figure 7.8.5-2, and "42" is not one of them, so "422" should be terminated by an FNC1, even though it has a fixed length. (I think the idea is that the "predefined length" AIs will never be added to the future, i.e. are set in stone.)
Note also Section <IP_ADDRESS>: "Notwithstanding the above, the processing routine SHALL tolerate a single separator character
immediately following any element string, whether necessary or not..."
(The handiest and best overview I think of AIs is given by BWIPP's gs1-format-spec.txt - generating the aiInfos table in "GS1.cpp" automatically from this is on my to-do list (eye-balled it the last time)).

Thanks a lot. Very help feedback. I fixed 2 and HRIFromGS1 does indeed currently return an empty string. This means a couple blackbox tests currently fail until I change them to test for proper bytes() content instead of HRIFromGS1(). Will do that before release 2.0. Which will be a breaking change for some. Nothing to be done about that, I'm afraid....

To be a bit more flexible for the future and allow for even more 'rendering' options without introducing ever more 'channels' I'd like to mention the possibility to parameterize text( TextMode mode = TextMode::HRI ). With modes like

Utf8 - simply return what utf8() currently does
HRI - human readable interpretation
Hex - ToHex(bytes)
Base64 - maybe?
EscapeNonPrintable - what ZXingReader -escape currently does
Utf8ECI - replace utf8ECI()?

This does not translate too well into the wrappers though as it is way easier to return a POD struct with some ready made strings than to pass an object that can sill call into c++ code. So there we'd have the 'channels' either way, I think. Hm, we could also have both, of course...
I'll implement this in the backend (Content) where it makes sens either way and also see if there is any feedback from others about this idea and then decide.
Looks like my plan to release 1.4 today has to be postponed again until I made up my mind about this.

I decided to postpone the decision but get 1.4 out anyway. I realized that there is another related issue and that is the fallback character set that can currently be specified via DecodeHints::setCharacterSet. That has the same property as the outlined TextMode in the sense that it actually does not really belong in the DecodeHints because it is only needed during the bytes -> text transition and could therefore actually be a parameter of text() as well. In fact it could very well be that the user might want to specify a different character set for different symbols/results from the same ReadBarcodes() call (especially if they are of different symbologies). That might be very rare, though and it is convenient from the wrappers perspective to handle it like it is handled now (even though that is more for historic reasons).
Bottom line: if specifying the character set via DecodeHints stays, then specifying a TextMode via the same route would be consistent and pragmatic for the wrappers. While at the same time we could provide a more capable Result::text(TextMode mode = HRI, std::string fallbackCharset = {}) function that would then override anything provided via DecodeHints beforehand.
All not very 'clean' I admit. Better ideas someone?

The polls are in: no better ideas have been presented. ;). I went ahead and tuned the constants a little:
enum class TextMode : unsigned char // see above
{
	Raw,     ///< bytes() transcoded to unicode/utf8 based on ECI info or guessed based on content
	ECI,     ///< standard content following the ECI protocol with every character set ECI segment transcoded to unicode/utf8
	HRI,     ///< Human Readable Interpretation (dependent on the ContentType)
	Hex,     ///< bytes() transcoded to ASCII string of HEX values
	Escaped, ///< Use the TextUtfEncoding::EscapeNonGraphical() function (e.g. ASCII 29 will be transcoded to "<GS>")
};

I decided to remove the mentioning of 'utf8' as that does not make sense for the wrappers where strings may be encoded in another way depending on the platform. What I'm still struggling somewhat are two questions:

Better term for Raw? Maybe Plain or Unicode? (Decided against Default and Standard)
What should the default setting for this be? I'd argue HRI, because users who don't know much about the subject likely just want to display a string somewhere and will not find/look for the textMode setting. But this would be a potentially surprising/breaking change for a couple of users. It would also require changes to the test, as a whole bunch would then fail.

I went for the term Plain and used it as the default (for now). feedback welcome.

Let's see if the default mode change to HRI will 'provoke' some feedback ;).

Sorry if I have delayed closing this 🙈 And sorry for not giving feedback earlier. I didn't really understand the scope of this change.

@markusfisch You did not delay anything here. Your recent commit merely reminded me that this was still open and that now might be a reasonable time to call it done.


Fix potential null reference callback invokation in script/clean

A bug was introduced in https://github.com/atom/atom/commit/76f9f43e6aec3d53b1b23b893648eac238090a60, which boiled down to not checking whether the (seemingly) optional callback in ChildProcess.safeExec is defined before invokation.
I wasn't sure whether we wanted to add a condition on the else statement, or set callback to a noop function. I opted for the formed, but I'm open to suggestions.
/cc @thedaniel @abe33 @damieng

Fixes #11328

Looks good to me, thanks for spotting this.


Changed to terragrunt in README

Signed-off-by: Rich Ehrhardt<EMAIL_ADDRESS>

The changes on this pull request are included in the standard BOM additions.


Add py.typed marker to work with PEP 561

The project currently lacks a py.typed marker file, which is required to declare the project as PEP 561 compliant. This file is essential for proper type checking and type hinting support when the project is used as a dependency in other Python packages.
An empty py.typed marker file could be added to the project's root directory, along with one line change in setup.py. This shall enable type checkers and IDEs to recognize the project as a valid type hint provider.

You're right, thanks. I'll add it soon.

The new release (0.11.0) have py.typed included.


Clarify language support quality status

The README.md says tesseract "supports over 100 languages out of the box". But - which languages? And what quality is the support for different languages known to be, out of the box?
It would be helpful if a separate file (or wiki page) would detail, to the extent possible, this information.

See https://tesseract-ocr.github.io/tessdoc/Data-Files-in-different-versions.html. All work on Tesseract is currently done by volunteers, so you are invited to find the answer to your questions and document them.


Cannot view what is selected when disabled

I've noticed a UX issue when you set the select-picker to disabled. In this case, the button for the select-picker is disabled, so you cannot open the select-picker "drop-down". Therefore, you can't see what is selected specifically, just "n Items Selected". Could it be changed so that you can click the select-picker button but not edit what is selected?

Technically it can be done. I'll mark this as a feature.
Anyone wana take up the challenge?

Fixed in 2.3.0


Support for Basis/KTX2 supercompressed textures?

Heya, love your work (I'm coming from the Pixi AssetPack compressed-textures PR here)
Any thought as to possible support for supercompressed Basis Textures? (re: @pixi/basis) Keen to know if these are especially challenging

Check this out: https://github.com/ddenisyuk/gpu-tex-enc/tree/main/packages/%40gpu-tex-enc/basis
v1.2.4 available in npm

You are a legend, thanks @ddenisyuk! I've got a couple custom plugins for assetpack so I'll be on the current "legacy" version for the foreseeable future anyway 😎


Add beanstalkd scaler

Adds a new scaler for beanstalkd queues (https://github.com/beanstalkd/beanstalkd). It scales based on the total job count of reserved and ready jobs by default, with the option to add delayed jobs as well.
Both unit tests and integration tests have been added.
Checklist

[x] When introducing a new scaler, I agree with the scaling governance policy
[x] I have verified that my change is according to the deprecations & breaking changes policy
[x] Tests have been added
[x] Changelog has been updated and is aligned with our changelog requirements
[x] A PR is opened to update the documentation on (repo) (#1454)
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Relates to #5901

Relates to #1454

/run-e2e beanstalkd

/run-e2e beanstalkd

/run-e2e beanstalkd


Show component version in DOM

Is your feature request related to a problem? Please describe.
Users of our elements find it difficult to know what version of an element is appearing in the UI. It would be helpful if the element showcased the version by inspecting the DOM.
Describe the solution you'd like
See this commit for inspiration https://github.com/AlaskaAirlines/auro-button/commit/9f3fbdf52152b4db1a1e59b10d637e13e0bd71c3#diff-d4dd6eae5a93186ddce0997857009fd364d8e3f6ed07792ccb2f37960049e989R6
Additional context
An issue that was not solved is that this solution is always a release behind the CDN versions. The feature linked needs to be updated to fetch the next version prior to bundled generation.

I feel that this is no longer needed. The strategy of giving the devs the proper loading sequence has addressed many issues that we were having around this.


modified the query to get the answers as expected from the question

existing query was not generating the correct date for filtering in where condition

Thank you for your contribution!


Chime active speaker name not detected correctly sometimes

Describe the bug
Chime active speaker name not detected and recored correctly sometimes
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Chime active speaker name should be detected correctly and recored
Screenshots

If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Fixed in #19


Error running command mpremote.refreshSerialPorts

Error running command mpremote.refreshSerialPorts: command 'mpremote.refreshSerialPorts' not found. This is likely caused by the extension that contributes mpremote.refreshSerialPorts.
Python 3.11.0
mpremote 1.20.0

What version of the extension are you using? I'm not able to reproduce this and I'm using v1.20.16 of the extension.

Unable to reproduce.


Can't run Google Maps 6 in the simulator in the M1

Environment details

Google Maps 6.0.1
Xcode 13.2.1
iOS 13.6
macOS 12.1
Swift project
Cocoapods 1.11.2

Steps to reproduce

Use the project attached in an M1 mac googlemapstest.zip
pod install
Build it for the simulator
It can't build error building for iOS Simulator, but linking in object file built for iOS, file '/Path/Pods/GooglePlaces/Frameworks/GooglePlaces.framework/GooglePlaces' for architecture arm64

CocoaPods is not yet supported. If you are on an M1 machine, you will need to use the XCFramework version of the SDK. See: https://developers.google.com/maps/documentation/ios-sdk/config#install-the-xcframework
If you'd like support for CocoaPods, please see the public issue tracker for any existing issues on this topic (feel free to open one if none).

CocoaPods is not yet supported. If you are on an M1 machine, you will need to use the XCFramework version
of the SDK. See: https://developers.google.com/maps/documentation/ios-sdk/config#install-the-xcframework

There is also the simple solution of adding the GoogleMapUtils dependency using Swift Package Manager. You can do this using with Cocopods to install the GoogleMaps dependency.
Or full SwiftPM for GoogleMaps dependency using a package.swift file created by a third-party
e.g. https://github.com/YAtechnologies/GoogleMaps-SP
I'm not sure why Google haven't done this yet!


gtk3: 3.24.27 -> 3.24.30

Motivation for this change
Version bump. I don't see anything of concern in the changelogs.
https://ftp.fau.de/gnome/sources/gtk+/3.24/gtk+-3.24.28.news
https://ftp.fau.de/gnome/sources/gtk+/3.24/gtk+-3.24.29.news
https://ftp.fau.de/gnome/sources/gtk+/3.24/gtk+-3.24.30.news
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Remove the Google Cloud Print backend, since the service was shut down

Maybe we can remove librest dependency now?

Weird, we do not depend on librest here. Perhaps that was not enabled.

What about json-glib? https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3729

Result of nixpkgs-review pr 129896 at 0be86875 run on x86_64-linux 1

44 packages marked as broken and skipped:

adoptopenjdk-hotspot-bin-13
adoptopenjdk-hotspot-bin-14
adoptopenjdk-jre-hotspot-bin-13
adoptopenjdk-jre-hotspot-bin-14
adoptopenjdk-jre-openj9-bin-13
adoptopenjdk-jre-openj9-bin-14
adoptopenjdk-openj9-bin-13
adoptopenjdk-openj9-bin-14
cassandra_2_1
cassandra_2_2
electron_3
electron_4
electron_5
epsxe
gnuradio3_7Packages.ais
gnuradio3_7Packages.gsm
gnuradio3_7Packages.limesdr
gnuradio3_7Packages.osmosdr
googleearth-pro
hadoop
hadoop_2_7
hadoop_2_8
hadoop_2_9
impressive
invoice2data
jboss
keyfinder
linuxPackages_hardkernel_4_14.akvcam
linuxPackages_hardkernel_4_14.virtualbox
linuxPackages_hardkernel_latest.akvcam
linuxPackages_hardkernel_latest.virtualbox
obinskit
odpdown
opentsdb
pcsxr
pdfdiff
pig
spark
termplay
tvheadend
twinkle
unicap
vdrPlugins.xineliboutput
xpdf

4235 packages skipped due to time constraints:

AusweisApp2
DisnixWebService
MIDIVisualizer
OSCAR
R
Sylk
_1password-gui
abcl
abiword
adapta-gtk-theme
...

31 packages built successfully:

adoptopenjdk-bin (adoptopenjdk-hotspot-bin-11 ,openjdk11-bootstrap)
openjdk16-bootstrap (adoptopenjdk-hotspot-bin-15)
openjdk8-bootstrap (adoptopenjdk-hotspot-bin-8)
cinnamon.bulky
enpass
fsearch
gnome.gnome-session-ctl
gtk3 (gnome.gtk ,gtk3-x11)
gnome.zenity
gssdp
gupnp
gupnp-igd
libappindicator (libappindicator-gtk3)
libcanberra-gtk3
libdbusmenu-gtk3
libindicator (libindicator-gtk3)
libnice
libwnck
openconnect (openconnect_gnutls)
pantheon.elementary-icon-theme
songrec
stoken
sublime3 (sublime3Packages.sublime3)
sublime3-dev (sublime3Packages.sublime3-dev)
sublime4
sublime4-dev
tuna
vimPlugins.vCoolor-vim
wrapGAppsHook
xfce.xfce4-dev-tools (xfce.xfce4_dev_tools)
xsnow

4 suggestions:

warning: unused-argument
Unused argument: gmp.
Near pkgs/development/libraries/gtk/3.x.nix:31:3:
   |
31 | , gmp
   |   ^

warning: unused-argument
Unused argument: x11Support.
Near pkgs/development/libraries/gtk/3.x.nix:37:3:
   |
37 | , x11Support ? stdenv.isLinux
   |   ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/libraries/gtk/3.x.nix:79:5:
   |
79 |     ./patches/3.0-immodules.cache.patch
   |     ^

warning: missing-patch-comment
Consider adding a comment explaining the purpose of this patch on the line preceeding.
Near pkgs/development/libraries/gtk/3.x.nix:81:5:
   |
81 |     (fetchpatch {
   |     ^

What about json-glib? https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3729

Good catch, thanks! At a glance it seems fine.

According to the bot gmp and x11support are unused arguments. Good to remove them too.

Thanks.


[Event Reqeust] codeunit 5644 "FA Reclass. Jnl.-Transfer" -    local procedure "Code"()

Describe the request
local procedure "Code"()
var
    IsHandled: Boolean;
begin
    IsHandled := false;
    OnBeforeCode(FAReclassJnlLine, IsHandled); //CustPub;
    if IsHandled then
        exit;

    with FAReclassJnlLine do begin
        FAReclassJnlTempl.Get("Journal Template Name");

[IntegrationEvent(false, false)]
local procedure OnBeforeCode(var FAReclassJnlLine: Record "FA Reclass. Journal Line"; var IsHandled: Boolean) //CustPub
begin
end;

Additional context
Publisher request marked with //CustPub tag.Internal work item: AB#494057

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 14667.


Feedback on chapter 3 - RISC-V N-Trace (Nexus-based Trace) Specification

This issue summarizes the feedback and comments from AR on Chapter 3.

The specification states that 38 bytes is the maximum message size. It was
not apparent that the protocol itself has such a limit on the maximum message
size. The last row of the comparison table should be updated to state
"In this version of the specification is 38 bytes (sum  of all field lengths)"
instead of "38 bytes (worst sum of all fields" - which would imply a
inflexible upper bound fixed at 38 bytes. Same comment about the following
sentence - "Max message size (38 bytes) " should be reworded as
"The maximum message size of 38 bytes in this version of the specification is
to transmit the IndirectBranchHistSync message which includes TCODE/ SRC/
SYNC/ B-TYPE (5 bytes total), I-CNT(30 bits, 5 bytes), F-ADDR(63 bits, 11 bytes),
HIST(32 bits, 6 bytes), and TSTAMP(64 bits, 11 bytes).
Did not include "worst" as assumption was that it just means maximum size. If
there is a different meaning please clarify.

Reword "Particular hardware ...."
"While implementations may have a shorter maximum message size (e.g, due to I-CNT
being smaller), they must assure that the internal FIFOs are designed to hold at
least two maximum sized messages that the implementation can produce."
This does not make assumptions about the implementation being hardware or
firmware or a combination of both.

Reword "Decoding software..." for better clarity
"While decoding software may be designed to avoid dynamic memory allocation, it
must nonetheless be robust enough to handle messages of any size. This is to
account for scenarios where trace memory could be corrupted, such as a trace
consisting entirely of zeros, which could be interpreted as an unusually long
variable-length field."
Or alternatively error out.

Section 3.1, "on LSB part of each byte" -> "located in the least signficant
bits of each byte"

Section 3.1 Second sub-bullet of second bullet should be split into two. The
sub-bullet should only describe the non-last bytes of a variable length field.
A separate main bullet created for fixed-length fields.
The statement "initial parts of longer variable" may be misread to imply that
the rule applies to only some initial bytes. Its better to write it as "The
non-last bytes of a variable-length field are indicated by MSEO[1:0]=00"

Section 3.1 "The last byte of a variable-length.." - should be written to
"The last byte of a variable-length field, that is not the last byte of a
message,  is indicated by MSEO[1:0]=01". Else it contradicts a bit with the
later bullets. Similar wording can be used for the fixed-length fields rule.

Section 3.1 - "The last byte of a message..." - there is a stray ** in the
text.

Table 5 - these transitions are not factoring in the Last byte of variable-length
field also being last byte of message i.e. 00-11 (or 01) should be a end of
variable length message.

Table 5 - Since the last byte of variable length message must be 11 if it is
also last byte of message, the 01-11-(more 11s) transition is not allowed for
End of message. Should it not just say "00-11-(more 11s)"

Table 5 - Idle is stated as 11s. It should be 11-11s?

Tabel 5 - message transmission can also see 00-01-00 and not just 00s

Section 3.1 - is there a unstated rule that first field of message cannot be a
6-bit variable-length field? If that is allowed then Start of message could
also be 11s->00(or 01)? If it is disallowed then should state that rule.

Since the N-trace reproduces/copies parts of the IEEE-ISTO 5001-2012 - like
section 3.1 - the N-trace specifcation should include copyright notice and
the rules in the copyright are followed. Either please remove the
reproductions or ensure that the document is compliant with the IEEE
copyright rules.

Section 3.3 - "Idle state must be...all MSEO..." -> "...all 1s MSEO..."

Section 3.3 -> do not split "The following 4 example sequences:" and "are
all valid"

The message transmission protocol of N-trace is different than that of Nexus
Adding a diagram along the lines of Figure 5-2 of Nexust specification is
good to highlight the divergence.

"LSB bits" is redundant.  Better to just say "least significant bits"

"N-trace messages transmission protocol..." -> "N-trace message transmission
protocol..." ->

What does "each LSB first" mean?

Table 5 - This table is confusing.  I guess it is only listing the MSEO bits
of each byte.  Term "Message transmission" should be clarified.

Section 3.2 : ALWAYS -> always

Section 3.3 - All of this seems implicit from prior rules.  Maybe just state
the first bullet as a sentence in an earlier section, and remove this section?

Section 3.4 - Should this entire section be non-normative?

Table 6 - ICNT[10]=0x7D - Re-phrase the description.

Table 6 - Rephrase "Here we could have TSTAMP..."

I am closing all N-Trace PDF related issues with same comments as all issues were handled via comments/discussions in SINGLE Google Docs. Relevant links are as follows:
Notes to N-Trace PDF:   https://docs.google.com/document/d/1h__c0Kc7TQAWMh5bw9cNC9bl_IGqyY_ylPV14uc2xj0
N-Trace PDF rc20:       https://github.com/riscv-non-isa/tg-nexus-trace/commit/221f6b1cef94c5f503554e0cb0deb4046dd49686
N-Trace for ARC review: https://github.com/riscv-non-isa/tg-nexus-trace/commit/1de77dcff1a75197232f72b8fe6863892da0cc74


Settings.current

@matthewford @jaleszek @RuslanHamidullin
We use Settings.current to get current settings for the application.
  def self.for_year(year)
    where(year: year).first_or_create
  end

  def self.current
    for_year(Date.current.year)
  end

The problem is that applications are being processed for a period that covers two years so we can not just use Date.current.year. Otherwise all settings that've been set up now won't be used after 01.01.2016.
We need to think of the way of detecting what award year is it.
@matthewford @jaleszek @RuslanHamidullin

Can we not set the year when the user creates the application?

@dreamfall @jaleszek @matthewford
maybe we should use calculated year instead of
Date.current.year

Award year is starts at 21 April.
now = Time.now
21_april_this_year = DateTime.new(now.year, 4, 21)

if now >=  21_april_this_year
  Date.current.year + 1
else
  Date.current.year
end

So, before 21 april - will be current year (2015)
After 21 april - will be next year 2016

@RuslanHamidullin I thought about that but we need to be sure that there will be no notifications after the 21st of April for previous awards.

@dreamfall @RuslanHamidullin can close this now right, with the refactoring of the years?

@matthewford I guess no. We should leave it until we do the switch between award years in admin area (in the menu).


Add support for managed entity count

Add support for storing and managing entity counts based on the specification provided.
DynamoDB does not have a way to retrieve a count of a given entity, but similar results can be achieved by maintaining a count property as a separate item in the table, there are many strategies to do this, like:
Tasks

[ ] entity decorator to support specifying managedCount as an option
[ ] when managedCount is enabled, auto-generate new managed count record
[ ] when modifying creating/deleting item with managed count enabled, also update managed count record to reflect correct values
[ ] add test coverage
[ ] document API and add section demoing the use case of managed count in recipes section

Before this can be implemented, we will need a reliable way to get a count of entities in case it was enabled on already deployed entities. For now, tho, adding a simple count operation on the entity manager will resolve the issue, which is being tracked #119


Update README.md

Adding my name to the README.md
Related issue

What changes does this PR do?
Screenshots (If any)
Questions

This PR seems to be a duplicate of #2488


Update to arrow 38

Which issue does this PR close?

Closes #.
Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

🤔  there appear to be more changes needed to tests in other modules


Improve compatibility of state space representation using LaTeX

It is not work with KaTex renderer
Maths in notebooks are rendered using KaTex in vscode. This result in:

With these changes:

It is algo working in Jupyter Lab.

Hi @gonmolina, thank you for your contribution!
The change looks reasonable to me. Could you please adjust the tests accordingly?
For example here:
https://github.com/python-control/python-control/blob/9c0ab033805e52d8c30a4aa7eb52859f11c642db/control/tests/statesp_test.py#L1014-L1031
I see the TransferFunction LaTeX representation already has $$.

Coverage remained the same at 94.766% when pulling 112af1a7392d1559bc66077313dcc7ed75af1d79 on gonmolina:repr-latex-statesp into 9c0ab033805e52d8c30a4aa7eb52859f11c642db on python-control:main.

Excellent! Thank you!


Getting an indexed color from TSkPaint.Shader.MakeGradientLinear

I have this code
RainbowColors := [$FFe81416, $FFffa500, $FFFAEB36, $FF79C314, $FF487DE7, $FF4B369D, $FF70369D];
RainbowPoints := [0.0, 0.167, 0.334, 0.501, 0.668, 0.835, 1.0];
var Paint : ISkPaint;
Paint := TSkPaint.Create;
Paint.Style := TSkPaintStyle.Fill;
Paint.AntiAlias := True;
Paint.Shader := TSkShader.MakeGradientLinear( TPointF.Create( 0, 0 ), TPointF.Create( 0, SkPaintBox1.Width ), RainbowColors, RainbowPoints, TSkTileMode.Clamp );

How do I get the indexed color of the gradient? I've looked at TSkShader, TKSPaint, and TSkCanvas, but, I can't find any method to a get the gradient array;

There are no way. You will need to create your own logic for this, saving the colors used to create it, etc...


Counter iOS Compose UI frontend

For maximum WTF.

Somewhat undermines the point of Redwood so let's not.


⚠ Bofrost.fr has degraded performance

In 4a91420, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1634 ms

Resolved: Bofrost.fr performance has improved in 0cc9bd3 after 6 minutes.


INFO、warning、error日志 需要区分开，不同的日志写在不同的文件夹里面，目前有的ERROR日志写了三份

Is this a regression?
Yes
Description

Please provide a link to a minimal reproduction of the bug
No response
Screenshots or videos
No response
Please provide the version you discovered this bug in (check about page for version information)
No response
Anything else?
No response

xuhaoliang


Skip dep check

PR Description
Fixed Issue(s)

Documentation

[ ] I thought about documentation and added the doc-change-required label to this PR if updates are required.

Changelog

[ ] I thought about adding a changelog entry, and added one if I deemed necessary.

Was able to release without needing these temporary hacks


The https://api.weather.gov/points/... response recently changed 2 properties : updateTie & Icon

The response to the https://api.weather.gov/points/... recently changed 2 properties : updateTie & Icon.
The Icon property changed from a complete Url to a string that no longer a complete Url, it no longer has a website.
The updateTime property changed from a DateTime object to a Date Time string.
So now the NationalWeatherServiceLibrary library no longer works.
Am I observing this correctly?

Yes. You are correct. I have updated the library with those changes.


Can the table fit to the specified view without expanding to scroll in view?

I need to create a table but i dont need the table to be scrollable in the view, but i need that the table fits the specified width, height ?

Also can you suggest me on how to display this type of json ?
https://pastebin.com/JHzGiUUL

Hi @aldocano,
for the width it is the default behavior to be not scrollable. If you want to have the height fixed, you can use either a fixed height value (e.g. 200dp) or a relative height (like MATCH_PARENT). If the content is bigger than the parent, the table will  make the content scrollable.
Best regards,
Ingo

Regarding your question about showing the sent json data inside the table:
Of cause it is possible to show it in the table. You can also add some custom styling to it. But I don't think it makes sense to clarify this here, as it is a very project specific question.
If you need support please give me some information about how I should get in direct contact with you.


Replaced the spinner on the NetworkPaginator

Same as the Pull to refresh controller

@aleffert pl review

:+1:


Change action anchor to "last"

generating constructors and other stuff is used far more often, so this plugin should not be on the first position

you are right.

fix it，You can upgrade the plugin


Update tmpdir and tmpfile context manager docstrings (#7800)

[x] Closes #7800
[x] Passes pre-commit run --all-files

@jrbourbeau Thanks for reviewing! I agree with your suggestions and believe now it looks better.


Create NameLayer Bungee Plugin

Jus to set a users display name from bunge.

so how does this work? does this fix the currently reported issues with namlayer tab auto complete not working?

No you just need to update mercury for that.


Better defaults for publicEntrypoints and appReexports?

Problem
The current config for publicEntrypoints and appReexports is only working for component ootb. I don't think much thought actually went into this, more likely this had its origins in some other sample config file.
I think this can cause some problems:

people might not be aware, and wonder why things are not working when they add e.g. a modifier instead
once we have ember g also working within v2 addons, this won't work ootb without touching the rollup config (manually, or by some AST transform, which can be brittle)
it complicates things in migration tools

Possible Solutions
appReexports
We could add entries for all the things that were subject to DI resolution in classic Ember:

components
helpers
modifiers
services
(theoretically in could be routes and controller also? But that's a weird case for addons we don't want to support by default I think!?)
(instance-)initializers?

publicEntrypoints
Make everything an entrypoint by default (like **/*). People can still customize if they want...
Or somewhat similar to appReexports, we could make entrypoints for  all the conventional paths that ember g would create files in (not just DI!), like

components
helpers
modifiers
services
utils
(instance-)initializers?

These are good points.
Adding to the discussion: I don't think it would be good to automatically add a component to appReexports, publicEntrypoints, or package.json exports just because an addon author runs ember g component. Not all components in an addon are necessarily intended to be public.
If we don't want to have to change the config often, we could define a filesystem convention instead. Like src/components is for public ones and internal ones go somewhere else. But that imposes some awkward limitations on how you organize your code. The natural place to put an internal component that's shared by two public components is probably right "beside" them.
Just making everything public is probably a bad habit. It leaks your internals making them harder to change later, and in large enough addons it will actually impose build costs on apps, because the more public entry points there are, the less rollup can do at addon-build time to reduce the number of files.
I think the ideal defaults here are probably different for converted addons vs new addons. Converted ones may indeed want to very loose config that simulates the older behaviors. Whereas a green-field addon could have a cleaner config that doesn't leak all its internals.

I have received some concerns for topics like v2 addons that we are now moving to "configuration over convention", so I think we need to be careful here when evaluating the tradeoffs...

Like src/components is for public ones and internal ones go somewhere else.

Yeah, I have been using something like that in ember-headless-form: all of the private stuff went into /src/-private. See suggestion #3 below...

But that imposes some awkward limitations on how you organize your code.

Right. But I think not doing this could would mean you need to maintain a very elaborate (error prone) config, when you want to selectively make things public vs. private. In the worst case you might even list files explicitly without using glob patterns. And this would indeed fuel the argument of "are we doing configuration over convention now".
Thinking of possible solutions, each with their own tradeoffs...
1. All public by default
// rollup.config.mjs

addon.publicEntrypoints([
  '**/*.js',
]),

// we can be more restrictive with appReexports, to only cover things that actually are resolved by DI lookups
addon.appReexports([
  'components/**/*.js',
  'helpers/**/*.js',
  'modifiers/**/*.js',
  'services/**/*.js',
]),

Pros:

adding new code (e.g. via blueprints) always works

Cons:

everything is public by default
no rollup optimization
users would have to opt-in to more strict settings

2. strict by default
// rollup.config.mjs

addon.publicEntrypoints([
  // index is the only public entrypoint, plus...
  'index.js',
  // all things reexported also need to be importable
  'components/*.js',
  'helpers/*.js',
  'modifiers/*.js',
  'services/*.js',
]),

addon.appReexports([
  // note: we are only exposing top-level components etc. here, no nested ones,
  // assuming the former will always be public, while the latter may be private
  'components/*.js',
  'helpers/*.js',
  'modifiers/*.js',
  'services/*.js',
]),

Pros:

only a minimal set of modules is public by default

Cons:

only top-level components are public be default (components/foo/bar.js is not). This might trip people up!
adding more public modules requires config changes

3. dedicated private folder
// rollup.config.mjs

addon.publicEntrypoints([
  // we expose anything that is not in our conventional private folder
  '!(-private)/**/*.js',
]),

addon.appReexports([
  'components/**/*.js',
  'helpers/**/*.js',
  'modifiers/**/*.js',
  'services/**/*.js',
]),

// package.json

// now we can easily provide an exports "rule" to deny anything in -private
"exports": {
  // existing default setup here
  "./-private/*": null
},

Pros:

adding new code (e.g. via blueprints) always works
public vs. private is now convention based, rather than having to tweak configs

Cons:

internally used private components (etc.) are not colocated
blueprints would need to support a custom location, or explicitly support --private

Any other alternatives come to mind?

I think the ideal defaults here are probably different for converted addons vs new addons. Converted ones may indeed want to very loose config that simulates the older behaviors. Whereas a green-field addon could have a cleaner config that doesn't leak all its internals.

Agree!


Where is the v0.21.1

Describe the bug
see the screenshot
Steps to reproduce
nothing
The version of Memos you're using
0.21.0
Screenshots or additional context

Please ignore this inbox, the latest is 0.21.0 for now.


Response in the request language in get_app_details

When requesting get_app_details with the country selection parameter, a response was received in the language of the selected country (description, name...).
Or is it impossible, since Steam does not store such data?

Hey sorry for the late response. Been busy with work and going to make more of an effort to answer. It looks like they do not have that data from what I can tell. I think it might js on the browser that might update the language. Not sure


feature: add configurable master instance settings

This PR makes the following changes:

add custom master configuration/slave only spot

Fully tested on our production environment
Fixes #82.

@nchammas can this be merged in some form? it would be nice to have this feature - depending on the application, the master doesn't really need to be very beefy, but having bigger slaves can be better for performance (to a certain extent)

My apologies to both @luhhujbb and @devyn about leaving this PR hanging. I won't have the capacity in the foreseeable future to review and shepherd this PR through to completion.
I would consider running a fork of Flintrock to get this feature. The instructions in the README should help you build your own version. If you have trouble doing that, please reach out and I will try to help.


Adding bias detection form

Please test here

Bias Detection

Can you please make the default into a form and hide the code?
I also like what you did with the forms, can you please the description just so others know that it's comma-separated?