Replace deprecated registryAuth() methods in IT

Codecov Report

Merging #809 into master will decrease coverage by 0.22%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #809      +/-   ##
============================================
- Coverage     66.38%   66.15%   -0.23%
+ Complexity      722      719       -3
============================================
  Files           162      162
  Lines          3073     3070       -3
  Branches        347      347
============================================
- Hits           2040     2031       -9
- Misses          879      885       +6
  Partials        154      154

looks good except for lack of tests around the new impl of RegistryAuthSupplier

I didn't think FixedAuthRegistrySupplier needed tests since it's only in the test sources because it's only used for tests.

Oops, I overlooked that class probably because of the name. See https://github.com/spotify/docker-client/pull/818


tailwind class sorting prettier plugin

Would be nice to have. See: https://tailwindcss.com/blog/automatic-class-sorting-with-prettier

Looking forward to it!

Hi, i wrote some similar plugin - prettier-plugin-typewind, and it do this, but only from string class notation before class to be converted to object, so^ i think it could be some additional functional for this, nice plan =)


Add replay for GitLab.com API calls that result in 500 Internal Server Error

We get an error like this intermittently, and was hoping retry logic could be added around this request:
(X/Y) Processing project: path/to/project
Warning: Error occurred while processing project path/to/project, exception:
Request url='[https://gitlab.com/api/v4/projects/path%2Fto%2Fproject/protected_branches?name=main'](https://gitlab.com/api/v4/projects/path%2Fto%2Fproject/protected_branches?name=main%27), method=POST, json='{"allow_force_push": true, "merge_access_level": 40, "push_access_level": 40}' failed - expected code(s) [200, 201], got code 500 & body: '{"message":"500 Internal Server Error"}'

This particular example is for the protected_branches resource, but there might be others that could benefit from additional retry.
Perhaps for API requests that result in 500 errors, a small wait should be added between retries?

Is there a way to see when a retry is executed?  I think you have these 3 retries shared across all API calls for an entire gitlabform run, correct?  Since we have ~4000 projects, I can see those getting used up quickly over the 3.5 hours it currently takes to run.

We have 1 original request + 3 retries = 4 tries in total for each request, not for the entire run.
Also we have a retry of the whole section added in https://github.com/gitlabform/gitlabform/pull/497.
But the error you have shared here is a HTTP 500 in response to a POST and these are not retried as of now, see https://github.com/gitlabform/gitlabform/issues/492#issuecomment-1435657246 for more info why.
So we definitely can think of adding retries here too, just have to be smart about it as POSTs are not idempotent. Maybe we should cover this case too in https://github.com/gitlabform/gitlabform/blob/7d77a253f88422e954485aea3c61ecbd6b90a75f/gitlabform/processors/abstract_processor.py#L103-L125 ? 🤔

Is there a way to see when a retry is executed?

Yes, with a debug output. But I understand that it's not practical with your scale. To make the retries more exposed we would have to have a custom subclass of the standard Retry that would print more info with cli_ui, something like this:
original_total = 3

class VerboseRetry(Retry):
    def __init__(self, *args, **kwargs):
        super(VerboseRetry, self).__init__(*args, **kwargs)

    def increment(
            self,
            *args, **kwargs
    ):
        to_return = super(VerboseRetry, self).increment(*args, **kwargs)
        if not to_return.is_exhausted():
            cli_ui.info(f"Retry {original_total-to_return.total} of {original_total}...")
        return to_return

I'll think about that.

Just in case, for original issue reported
(X/Y) Processing project: path/to/project
Warning: Error occurred while processing project path/to/project, exception:
Request url='[https://gitlab.com/api/v4/projects/path%2Fto%2Fproject/protected_branches?name=main'](https://gitlab.com/api/v4/projects/path%2Fto%2Fproject/protected_branches?name=main%27), method=POST, json='{"allow_force_push": true, "merge_access_level": 40, "push_access_level": 40}' failed - expected code(s) [200, 201], got code 500 & body: '{"message":"500 Internal Server Error"}'

gitlab has https://gitlab.com/gitlab-org/gitlab/-/issues/463017

Hi @gdubicki and @amimas
Will you accept MR with changes for POST requests (retry) or it is not something you see as a feature for a product?

I would assume that having feature like retry per project for POST would be useful. For example:
By default no retries for POST requests per project
If gitlab form configuration has "project" -> retryPOST: N, then POST requests should be retried for 409, 500 and 502 error codes N times using default timeout between attempts.

After more thinking here... Maybe it will be better to consider retry in terms of project and not just POST request.
For example:

By default, no retries
If config has "project" -> "retry: N" and that "project" processing failed, it should be retried from the beginning.
Maybe we can consider retrying all failed project at the end of the job (when we have a summary on what failed).


Added the production dockerfile and OS requirements

The dockerfile in the root of the repo contains all tools required to develop on the repo. This initial attempt is probably missing a large number of necessary things (I've created it from the perspective that I've had with the repo) so feel free to comment and add more.
To use the image run docker build . -t "whatever tag you want" from the root of the repo and then docker run -it "whatever tag you want" -v ./:/caravel_user_project  and then you should be able to run the standard commands like make verify- etc...
Eventually I think it would be good to have each of the tools having their own dockerfiles that they push so there's already an image available for the right version and this repo pulls in those images using multi-stage builds, copying only the necessary files.
I think this would be a positive change because it guaruntees a consistent and reproducible environment for all users and developers, making issues occur more infrequently and making them easier to debug when they do pop up. This change does not affect users immediately since they do not have to use the docker container, but when it is mature enough (maybe in the next shuttle) it can be adopted more readily by users.
Happy to take criticism or comments and thank you for the consideration

Hey @AdamWRichardson . Thanks for you contribution. We are attempting to do something similar here. The implementation has certainly room for improvement but the goal is to have a one-for-all container that has all the tools required for caravel user project and more (you can find it in the repo under ./images/foss-asic-tools). @mkkassem can speak more about the motivation behind it, and of course we are open to comments and suggestions.

Hey @AdamWRichardson . Thanks for you contribution. We are attempting to do something similar here. The implementation has certainly room for improvement but the goal is to have a one-for-all container that has all the tools required for caravel user project and more (you can find it in the repo under ./images/foss-asic-tools). @mkkassem can speak more about the motivation behind it, and of course we are open to comments and suggestions.

Thanks for the information, this is definitely aligned with this pull request. For me there's advantages with having some dockerfiles in the separate relevant repos, for example modern IDEs can mount the git repo in a docker image created from a dockerfile and also it's easier to see which versions you need and how to configure the tools you need (versions, optional dependencies etc.,,)
As for the actual dockerfiles, if you can limit the number of RUN commands then this significantly reduces the size of the image as the final image is made up of layers which is just a snapshot prior to running RUN. See the official docs for other examples

Thank you everyone for your efforts on this. At this time, due to the age of this issue and other changes that have happened since, we have decided to close this PR without merging it. In some cases this also means there is now a better or other recommended approach, or possible the PR otherwise relates to a deprecated mode of use. Reviewed by @marwaneltoukhy @DavidRLindley @algofoogle.


Export null and notNull.

I find myself writing toNullable Nothing and toNullable $ Just something and it would be rad if I could use null and notNull something instead.

Found myself in the same situation.

@thomashoneyman this PR seems to be languishing. Any interest?

I’m out of town until Tuesday, and I can review then; from a glance this seems reasonable and I can merge then unless @paf31 has any objections.


Airmega 250 and 250S

I know they are not on the "confirmed" working list.
Is there any reason they shouldn't work? Looking at buying one.

I don't know what the 250S purifiers return by the API, but there is a good chance they work. I can't say for certain as no one has come to me and told me they are using the 250S with this integration. Also, note the 250 won't work as it doesn't have any WiFi capabilities.


feat(workflow): log the template used in case of an error

Without some info about the error is not possible to know where to look
Example without the log:
ERROR srv-f22: srv-f22_v1046.web (deploy): failed to create ReplicationController "srv-f22-v1046-web" in Namespace "srv-f22": 400 Bad Request
{'apiVersion': 'v1', 'metadata': {}, 'kind': 'Status', 'status': 'Failure', 'message': 'ReplicationController in version v1 cannot be handled as a ReplicationController: [pos 1053]: json: expect char \'"\' but got char \'6\'', 'code': 400, 'reason': 'BadRequest'}

Is this ready for review?

@helgi yes

Alright, I fixed the labels

@aledbf this is ready to merge. Thanks again!


Add "Adjustments" - recent plugin for Figma

Checklist

[x] I made something good today 💐.
[x] I put links in the correct format: [Tool](link) — description.
[x] My description starts with the lower-case letter and ends with the full stop.
[x] I put the tool in the alphabetical order.

Optional

[ ] I added the appropriate labels: free, open-source or mac.
[X] I put the tool only to one category.
[x] I followed Contribution Guidelines.

Added! Sorry for a huge delay from my side!


Bioluminescent plants like to go thru doors

Description
Dragging a plant allows it to go thru doors
Reproduction

Drag a bioluminescent plant
Push it into an airlock

Screenshots

Additional context

Discovered on salamander, with (i believe) the tickrate to be 30

lol, even how


chore(deps): update common-dev-assets digest to 2e77009

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
83ceca2 -> 2e77009

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 3.28.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Correct usage command, add TeamCity instructions

The Usage command was missing the 'run' argument required to make it work.
Also added some basic instructions for setting up the Build Step in TeamCity.

Thanks mate! :)


Correct issues with layout 11 for IDT92HD81B1C5 for Dell Latitude E6410

Minor adjustments to pin-config, fixed volume slider issues for internal speakers.

Thanks.


Mean

Submission Title
Mean of given Numbers
Submission Type
Maths_And_Stats
Submission Description
The mean is the average of the numbers. It is easy to calculate: add up all the numbers, then divide by how many numbers there are. In other words it is the sum divided by the count.
Folder Related To
Maths_And_Stats => Stats => filename.extension
Contributors

[x]  C++ -
[ ]  C -
[x]  Python -
[ ] Java -
[x] JavaScript -
[ ] TypeScript -
[ ] Golang -
[ ] Ruby -
[ ] php -
[ ] Swift -
[x] C# -

Can I do this with python/cpp ?

Can I work in python

or Java

I can do the C javascript C# part

Can I do this with python/cpp ?

Go with c++

in which language shall i Python or ?

i have done it please merge it in yours

I implemented this in c , c# and javascript
please do check  #169

I would like to work on this in PHP, please assign this to me.

Hi @ahampriyanshu , Assign me on this I can work on Java and C.

Hi @LUCIFER-dev-king  i already did the c part

Hi @LUCIFER-dev-king i already did the c part

Ok I'll do java part.

thanks @everyone :v:


retire macos-12 from CI

@scholarsmate I added macos-13 in to replace macos-12 as its x86 based, this way we keep that support. However, I do believe macos-14-large is x86 based but think -large and -xlarge runners cost money to use.

Thanks @shanedell, the changes look good to me.


Use lerna version instead of lerna publish

Update README with clear publishing flow

master currently uses npm publish.


Brave cxf

Hi @kristofa,
I've added CXF support. It supports both cxf jax-ws and jax-rs servers and clients.
Module depends on brave-http and contains cxf interceptors, README file and some tests.
Any hints what else is needed are welcome.

Michał Podsiedzik

Thanks for taking time to work on this, Michal, and welcome to Brave! Code-wise, I'd check for error conditions (ex a non-success http response), but the code looks pretty solid.
We do have an important question to ask before digging deep.. should we merge this feature to master?
It usually isn't a good idea to add new module with only the author interested (see rule of three). At least one of the regular contributors should be on board with maintaining this, if it is to go to master (as opposed to a separate repository). It ideally should have users besides the author.
Here are some hints for drumming up interest. You might find there are folks who would help use and support this:
CXF was mentioned last year by @fedor57, but hasn't ever been mentioned in zipkin's user group. CXF includes Apache HTrace support (which can export to zipkin), so folks using that only to get to zipkin might be interested. The authors of CXF might be interested. There was also a blog on CXF (using finagle) a couple years ago.. maybe the author would be interested.

Yes, I made some classes and was able to intercept CXF requests and responses. But had no energy or skills to make something reusable out of it. Now our project is suspended, here's what has left. You may be interested to look shortly at my code if it can be somewhat useful.
https://github.com/fedor57/brave/tree/fedor-brave-cxf

@fedor57
Hi, I'll definitely check it out.
@adriancole
I wasn't aware of CXF HTrace support. Maybe we should wait with merging until some other people could participate. Or leave it as it is, as an example hot to integrate CXF with Brave. In the meantime I'll try to add some more tests.

@reta you interested in this? I think you were behind the blog and also HTrace support. We're basically seeing if there are enough people who want to trace CXF into Zipkin (via brave) to warrant merging this.

Thanks for mentioning this PR, @adriancole! That's right, we have integration with HTrace (which also is fully compatible with Zipkin protocol) as part of CXF distribution. I think it won' hurt to have yet another option with OpenZipkin / Brave on the table so our users could pick the right one. Do you want me to play a little bit with this PR before merging?

yeah please do, Andriy! Let us know what you think

Hey @podsiedzik @adriancole !
I was fortunate to have some time and play with CXF integration. It is actually very nice, easy to get started and use, definitely good job here! There is one minor thing I would like to suggest just to make integration with traditional JAX-RS applications (which do not use factory bean) easier, is to have a CXF feature provided, very simple one:
import org.apache.cxf.Bus;
import org.apache.cxf.annotations.Provider;
import org.apache.cxf.annotations.Provider.Scope;
import org.apache.cxf.annotations.Provider.Type;
import org.apache.cxf.feature.AbstractFeature;
import org.apache.cxf.interceptor.InterceptorProvider;

import com.github.kristofa.brave.Brave;
import com.github.kristofa.brave.cxf.BraveServerInInterceptor;
import com.github.kristofa.brave.cxf.BraveServerOutInterceptor;
import com.github.kristofa.brave.http.SpanNameProvider;

@Provider(value = Type.Feature, scope = Scope.Server)
public class BraveFeature extends AbstractFeature {
    private final SpanNameProvider spanNameProvider;
    private final Brave brave;

    public BraveFeature(final Brave brave, final SpanNameProvider spanNameProvider) {
        this.brave = brave;
        this.spanNameProvider = spanNameProvider;
    }

    @Override
    protected void initializeProvider(InterceptorProvider interceptorProvider, Bus bus) {
        final BraveServerInInterceptor in = new BraveServerInInterceptor(brave.serverRequestInterceptor(), spanNameProvider);
        final BraveServerOutInterceptor out = new BraveServerOutInterceptor(brave.serverResponseInterceptor());
        interceptorProvider.getInInterceptors().add(in);
        interceptorProvider.getOutInterceptors().add(out);
    }
}

In this case it would be very easy to use Brave from JAX-RS application subclasses. Client-side feature would be good as well but not as beneficial as server one.
Another one is a bit more complex issue and in scope of this PR would be nice just to mention it so you guys could be aware (the proper fix may need some thoughts). JAX-RS has support of async API calls (both on the client and on the server). That means that request and response (along with filters and interceptors) are going to be processed in different threads. The effect of this for tracing is that the spans which were started but were never stopped (or closed). The reason is, similarly to HTrace, Brave implementation also uses thread locals to maintain current span. I don't think this should block this PR from merging, but something to address later on.
Answering on my behalf (but surely all CXF team), we would be more than happy to help you guys out and contribute as well in order to make the integration more robust and JAX-RSy. Please let me know what do you think guys :-)
Thanks, great one!
Best Regards,
Andriy Redko

eek.. looks like a merge happened. might want to rebase

Hi @reta,
I've read your comments regarding async support. I've changed approach a little bit.
I'm thinking about using cxf Message Exchange to pass Span state between request and response interceptors. Changes are already committed.
@adriancole
What do you think?

@podsiedzik  :+1:

FYI, I'm (finally) working this in. thanks for the efforts here and the patience!

out the door in 3.16


Issue #40- Remove episodes inner

-Added functionality for removing episodes from queue
-Left behind some minor remove from outside of queue, just so users can remove episodes that were queued before update
-Queue tag no longer applied on adding to queue
-Can now add episode to more than one queue
-Queuefragment refreshes on remove
-Remove is done via context menu to avoid clutter and enable future add ons, press and hold on episode to open context menu

Okay we now have conflicts since we merged my PR. We will fix them asap.

I tried to resolve conflicts on the web editor. I will now make sure that the app builds on my android studio, there seems to be problems.


[PE-D][Tester C] Copy Command

Describe the bug
After Copy, when I paste there is a semicolon at the back when its not suppose to be there.
Expected behavior
email should not have semicolon
Priority
p3
Screenshots/Video

Labels: severity.Low type.FunctionalityBug
original: headcube1/ped#7

This is not considered a functionality bug because the semicolon symbol is a delimiter ('separator') between email addresses, and will allow the full set of emails to be treated correctly by the email-sending platforms.

Perhaps this can be reflected better in the UG


Continue with Github

Hi again,
is there a way to remove the part which states "continue with Github" in the home page at login when all OAUTH methods have been disabled?
I would like to manage users internally only and I know that the Github button is useless because it only tells you to configure it, but more reasons to remove it completely if not enabled, right?
Thanks

Changed to show only during onboarding.
Will be in in the next release, probably later today.


Add self-hosted Kubernetes upgrade guide

Same as https://github.com/coreos/coreos-baremetal/blob/master/Documentation/bootkube-upgrades.md, but without bare-metal or QEMU/KVM mentions.

Actually, we should probably start a top level docs dir. Mind moving this into one?

Sure. docs or Documentation like our other projects?

Documentation sgtm


Invalid HTML select tag

Invalid HTML select tag
Page disorder

This issue needs more description, example and steps to reproduce etc

Closing due to age


Fix code alignment

Just my OCD :smiley:

Coverage remained the same at 55.3% when pulling f5369c5a4b281b316c0bc20afab8090d9446da88 on B3QL:master into cbdd554c3463e8b32d5344eafe2da71770f8f529 on OpenBazaar:master.


Fix initialisation of /partyinfo service

Normal 7 nodes example where node 1 is bootstrap node works as expected, however if each node has different peer node in the configuration, say node 1 has node 2 , node 2 has node 3 and so on, the partyinfo service of each node needs to initialise with the list of peers provided in the configuration file correctly. We are seeing behaviour where this initialisation is not working correctly if the sync poller fails to update the configured nodes during startup i.e., if node 1 is up before node 2 is up and it is not able to sync up with node 2. If this initialisation fails then it results in subsequent partyinfo sync up not working as expected i.e, node 1 will never be discovered by other nodes. To fix this we will inject the configured parties in 'partyinfo' service constructor to try indefintely and update the partyinfo service when 'addparty' API in invoked.

Fixed by #527

Fixed in 0.7.3 release


How to add other token/chain using this library?

Hi, I have question.
https://github.com/trustwallet/wallet-core/blob/master/samples/android/app/src/main/java/com/trust/walletcore/example/MainActivity.kt
I'd like to know how I can add Algorand transaction signing part here. Where is the documentation about this?
Thanks.

Take a look at the cpp test: https://github.com/trustwallet/wallet-core/blob/master/tests/Algorand/SignerTests.cpp#L90


Multilingual support

With an upcoming support of several languages in the interface of portals brought by AgroPortal, it naturally brings the question of doing it for the documentation as well.
It might not be as relevant for developers/maintainers than it is for users, but this idea is more concerning a future user documentation.

Relevant discussion about Documentation is there. https://github.com/ontoportal/ontoportal-project/discussions/1
I have reported your comment there. I believe we first need a documentaiton (User guide) before we translate it ;)


Add a limit on how much split view items can be displayed

I want to have a limit on how many split view items can be displayed on screen. Default should be 5, but customizable by the user.

Can you clarify what you mean by split view items?

I mean like this...

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Packagist integration broken

Is packagist integration setup well / migrated from the Legacy auto-update? It shows dev-master as a commit from January https://packagist.org/packages/webonyx/graphql-php#dev-master
Packagist possibly shows this message on package detail for @vladar

This package is using the legacy GitHub service and will stop being auto-updated in early 2019. Please set up the new GitHub Hook for Packagist so that it keeps working in the future.

Yeah, switched to the new packagist syncing method (using webhooks). Thanks!


New version: Alibaba.AlibabaCloudCLI version 3.0.152

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.4 schema?

Microsoft Reviewers: Open in CodeFlow

This package is expecting arguments:
Alibaba Cloud Command Line Interface Version 3.0.152

Usage:
  aliyun <product> <operation> [--parameter1 value1 --parameter2 value2 ...]

Commands:
  configure       configure credential and settings
  oss             Object Storage Service
  auto-completion enable auto completion

Flags:
...

@wingetbot waivers Add Validation-Installation-Error


[incubator/druid] Can I change druid.zk.paths.base and druid.discovery.curator.path?

I don't see a way to change both of those options in values.yaml documentation.
Is your feature request related to a problem? Please describe.
I cannot customize druid.zk.paths.base and druid.discovery.curator.path
Describe the solution you'd like
I'd like to be able to customize druid.zk.paths.base and druid.discovery.curator.path

@didip do you mean that you have an other zookeeper cluster and don't want use the default zookeeper chart？so that you want customize druid.zk.paths.base and druid.discovery.curator.path

https://github.com/helm/charts/blob/master/incubator/druid/values.yaml#L344 you should set zkHosts to your zookeeper cluster ip and port. And  set zookeeper.enabled with false

https://github.com/helm/charts/blob/master/incubator/druid/values.yaml#L15 you should set configVars.druid_zk_paths_base and configVars.druid_discovery_curator_path into install command.


Renderer Trigger Re-render

I have a custom renderer that has a button to launch a dialog that changes the value of the cell.  Is there a way to get the cell to re-render once the cell value has been changed?
I'm searching around for something RenderContext at the moment.

The widget returned by the renderer should be statefulWidget, and the widget should handle rendering according to the state.

I got around it by using StatefulBuilder


Inherit default style for popups

The current setup can cause style inconsistencies between popups and other windows/elements, particularly when using transparent backgrounds.
This change will resolve that issue (popups will inherit default colors for foreground and background).
Since this plugin doesn't utilize window-active-style or menu-style, there's no need for popup-style either.

Before:

After:

I'm sympathetic to personal taste with regards to what colors things should be. At the same time the entire point of this repo is to be opinionated about what colors things should be in tmux. So I'm hesitant to remove colors and just use defaults, especially when catppuccin has a style guide about what things like pop-ups should look like.

I'm sympathetic to personal taste with regards to what colors things should be. At the same time the entire point of this repo is to be opinionated about what colors things should be in tmux. So I'm hesitant to remove colors and just use defaults, especially when catppuccin has a style guide about what things like pop-ups should look like.

So how can I target the bg in my conf to use default?
Is there an option I'm missing somewhere?

Just set the tmux option after you load catppuccin


Rows in the ER section are not selectable but available through "More Shapes"

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'More Shapes'
Click on 'Entity Relation'
Notice the rows option.
Go to "Entity Relation" on side panel
Notice error.

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
draw.io version (In the Help->About menu of the draw.io editor):

draw.io version [e.g. 12.6.7]

Desktop (please complete the following information):

OS: Windows 10
Browser: NA
Version 13.2.4

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Some shapes are missing (some of them are marked yellow) in "More shapes" and when added to sidebar (diagrams.net online 13.3.1 and desktop 13.2.4 and 13.3.1)

.4.

Will be fixed in next release.


MFCMapi core library does not compile with VS 2022 17.10

Build errors:
core\smartview\block\blockT.h(39,34): error C2062: type 'WORD' unexpected
core\smartview\block\blockT.h(43,27): error C2062: type 'WORD' unexpected
core\smartview\block\blockT.h(44,32): error C2062: type 'WORD' unexpected
core\smartview\block\blockT.h(39,34): error C2062: type 'DWORD' unexpected
core\smartview\block\blockT.h(43,27): error C2062: type 'DWORD' unexpected
core\smartview\block\blockT.h(44,32): error C2062: type 'DWORD' unexpected
core\smartview\block\blockT.h(39,34): error C2062: type 'BYTE' unexpected
core\smartview\block\blockT.h(43,27): error C2062: type 'BYTE' unexpected
core\smartview\block\blockT.h(44,32): error C2062: type 'BYTE' unexpected

Works for me (tm).
Did you make sure to clone submodules?
git clone --recursive https://github.com/microsoft/mfcmapi.git

Just updated to 17.10 from 17.9 and now repro - sounds like a problem with VS, not the project, but I'll see what I can find

Thanks @stephenegriffin. Reported to VS Developer Community. They have reproduced it and are looking into it.
Here is the link:
https://developercommunity.visualstudio.com/t/Compiling-MFCMapi-after-upgrade-to-VS-20/10662946


Authentication

How do you handle authentication using this library? In most cases redis is protected by password for safety.
I would like to know how we handle authentication.

At present there's no specific support for this.  But individual applications can send an AUTH command explicitly when opening a connection.
This can be cumbersome depending on the nature of the work being done, so I'll leave this issue open and tag it as a feature request, as it would make sense to handle this as a convenience when opening (and re-opening) connections.

Thanks'! I'll keep my eyes on this.

Perhaps authentication could be done by passing a function as argument to connect/paired_connect.  This function will be called every time after connecting/reconnecting and before sending any other commands to server. In this function we can call AUTH, SELECT (change database number) and even upload lua scripts.

https://github.com/benashford/redis-async-rs/issues/49


Update project to use Gradle #4

Here you go! I also attached the (1.0.4) release artifacts in case you would like to publish them under https://github.com/devilgate/pertwee/releases.

pertwee-1.0.4.zip


Add new boolean property anchor_package_regex to resource apt_package resource

Description

Add new boolean property anchor_package_regex  to resource apt_package.
For apt-cache command the name of the package is searched as a regex due to which it tries to implicitly install all the packages whose name would contain the passed name string as a substring.
This causes issues for people which who not want this to happen. Hence we add this new property, which will be false by default for backward compatibility. Users can set it to true in their recipe if they want the package name to be exactly matched instead. (i.e anchored with ^...$)
Documentation pr https://github.com/chef/chef-web-docs/pull/4156
Related Issue

https://github.com/chef/chef/issues/12944
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.
[ ] All commits have been signed-off for the Developer Certificate of Origin.

Code is all great now - but the documentation was misleading, requested some changes.

What's wrong with it?

Code is all great now - but the documentation was misleading, requested some changes.

What's wrong with it?

@IanMadd Their suggestions
https://github.com/chef/chef/pull/13873#discussion_r1309270055
https://github.com/chef/chef/pull/13873#discussion_r1309272482

Had to add a last minute gem update and rebase to get the PR to pull in the correct versions of some things. The error in the unit test is known and will be forward-ported from chef-17.


Long exponential part causes an error

I noticed that there is no size check of exponential part. If I pass something like this:
1.33E+3333333333333333333333

It will cause "Allowed memory size exhausted" error.

That's true, the problem is related with the inner representation. We need to think a good way to decouple the inner representation from the Decimal object in order too allow numbers with really big exponents.
The problem is that php-bignumbers is designed to offer good precision, and it's not trivial to decide the point where jump from fixed point to floating point representation.
Do you have any suggestion?


[Task]: Add loading spinner until voting tx is confirmed

Task description
The voting flow popups miss a loading spinner until the tx is confirmed. After confirmation we show the success
like in staking.
Requirements
TBD
Acceptance criteria
TBD
Creation checklist

[X] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

#2412 merged

Reopening due to some reactivity issues on the spinner message:


The external network traffics are not being traced

Describe the bug
Hi, I want to identify the specific source that leads to the heavy traffics on my ingress workload. But in the  topology dashboard, i can't see the external IP  to my ingress workload, it seems that the  external network traffics are not being traced
How to reproduce?
Visit your ingress from outside the Kubernetes cluster
What did you expect to see?
External IP to ingress must be displayed
What did you see instead?
No node sends traffic to my ingress workload
Screenshots

What you saw is what we expect now. The metrics of kindling_topology_xxx are all generated from the data scraped from the client-side, and apparently, we can't get any data when the client is not monitored. That's why the dashboard doesn't display any source IP that is outside the cluster as a client.
If we want to display this information, we could use the data scraped from the server-side as the mimic of the one from the client-side. But the problem is that it could introduce many new unexpected issues since the data sometimes is not the one we want.
As explained above, I think this issue is not a bug but a "feature request". We'll talk about this feature later and now I prefer to remove the "bug" label.


Add a wiki: Picross Wiki

Link to origin wiki: https://picross.fandom.com
Link to destination (independent) wiki: https://picross.miraheze.org

Thank you for the submission! Added in v3.7.0 (now available for Chrome, release pending for Firefox).