Make it easier to create templates and glee projects

Reason/Context
We have had talks before about making it easier to create new generator templates through something like npx create-asyncapi-template. However, I think that our CLI could fulfill that role to offer a better user experience for developers, to easily bootstrap new templates or glee projects.
Notice: Glee already use npx for setup
What do you think, does it fit the CLI use-case?

imho yes, AsyncAPI CLI should be a single place where we integrate all AsyncAPI tools to make work from the terminal a pleasure. So folks install just one tool to use all the others. One 💍 to rule them all 🤓
it is just a matter of coming up with proper command names and good DX

Hey, this sounds amazing!! 🤩
Would like to work on this.

Would bootstrap make sense? 🤔
asyncapi bootstrap glee --output ./output-dir
asyncapi bootstrap glee mqtt --output ./output-dir

asyncapi bootstrap template --output ./output-dir
//Incase you want to copy an existing template
asyncapi bootstrap template @asyncapi/java-cloud-stream --output ./output-dir

I think scaffold is more accurate technical word that would explain what is done, not sure bootstrap is correct 🤔
can you provide some more explanation of what each command would actually generate?

Yes @derberg , scaffold sounds less confusing than bootstrap.
So I was thinking to start it with, something like support of Async API for NextJS API Directory.
Objective:
The user can create NextJS Serverside Asynchronous APIs from the AsyncAPI spec file.
Assuming, AsyncAPI and NextJS are installed globally.
Steps

User should be able to run ->
asyncapi scaffold nextjs --output <NextJS_API_Directory>

This builds a directory with particular endpoints as separate filenames (That's how NextJS function), and a NextJS friendly code.
The --typescript flag will help to choose the language.

Your suggestions: @jonaslagoni

What about new? We already have it and would be just a matter of extending it:
asyncapi new --> New AsyncAPI file, as it is now.
asyncapi new file --> Same as above.
asyncapi new project --> New Glee project
asyncapi new glee --> New Glee project
asyncapi new generator --> New Generator template (or generator if we end up calling them like this)
asyncapi new generator --clone @asyncapi/java-cloud-stream --> In case you want to clone an existing one

new sounds more relevant to the scope ✌ .
We can add a code generator  for different frameworks too
For example:->  NextJS, which requires customization to NextJS Formatted Code and Directories for APIs.

new sounds good to me, simple.

Same here 🎉

Hey guys! 👋 @jonaslagoni @derberg @imabp @fmvilas
I've been having a look and investigating a bit on this issue and I'd like to start working on it to keep on contributing to the CLI repo. If no objections from your side, I'll take it up and get back to you with a proposal as soon as I have some working code 💪 Cheers!

No objections from my side 👍 🚀

Hey guys! 👋 @jonaslagoni @derberg @imabp @fmvilas I've been having a look and investigating a bit on this issue and I'd like to start working on it to keep on contributing to the CLI repo. If no objections from your side, I'll take it up and get back to you with a proposal as soon as I have some working code 💪 Cheers!

Awesome @peter-rr!
Not sure how you want to do it, but as a suggestion, don't try to jam everything into one PR :) Start small with one of the commands like asyncapi new glee, and make a PR and gradually add features 🙂

I'm happy to be a mentor for this issue in the Mentorship program.

@fmvilas As I said I'd be happy to contribute on this issue 💪 So I'd like to do it as part of the Mentorship program if selected :) Cheers!!

Still relevant, don't close it :)

Hey folks! I'm about to start working in this issue and I think it would be more convenient if we split it into two different issues:

Create glee projects
Create templates

My idea is to focus on creation of glee projects for now, so the the other issue about creation of templates would be available to be picked by anybody else. @Souvikns I know you were interested recently in working on this issue, so I was thinking maybe you'd like to pick the second issue I've proposed (Create templates). If that's the case, feel free to create a new issue for that purpose 😉 What do you think, guys?

It's always a good idea to split things in smaller chunks 👍

By the way, in order to implement the creation of glee projects, I was considering the option of using the create-glee-app command inside the code, but not sure whether that's something out of the scope for this issue or then the main goal should be to bootstrap the glee project manually without making use of that command at all 🤔
Besides, I don't know what is planned for this repository in the future, so I doubt if I should rely on it or it might be better to avoid using it. Any ideas or suggestions on this?

Please completely avoid using create-glee-app. It will be deprecated in favor of this command.

Yeah @peter-rr I would love to help. What would be a good idea

to use examples in glee as templates so that CLI can pull them during build something we are currently doing https://github.com/asyncapi/cli/blob/master/scripts/fetch-asyncapi-example.js
Or have a separate templates folder in glee for specific templates.

I'm not really sure about what should be the strategy in terms of templates organization 🤔 Maybe @fmvilas or @jonaslagoni have some suggestions about it 💭

As for Glee, I think it makes sense to be able to fetch a Glee example somehow. As we're doing right now in create-glee-app with the -e, --example option: https://github.com/asyncapi/create-glee-app#options. Take into account that creating a Glee project is not just a matter of picking an AsyncAPI to start with but also some example code in the functions.

So you dont just want the bare configuration for a Glee project to be setup alongside the AsyncAPI document, you actually want it to implement business logic @fmvilas? 🧐

No no, just be able to "clone" an example from the examples folder in Glee or a [Git|Gitub] URL. Just what we have right now with create-glee-app. Also a cool feature of create-next-app.


Can Habitat handle multi-agent scenarios?

My purpose:
My purpose is to deal with the scene where multiple robots work together (such as multi-agent navigation, moving objects together, etc.), which requires:
Each robot can see other robots and other dynamic obstacles (such as randomly walking humans).
Each robot can detect whether it collides with other robots.
Robots can communicate with each other (the communication message can be their own observations or positions, etc.).
Each robot can execute its own policy simultaneously in a distributed manner.
Can Habitat add multiple robots in a single common environment?
Thanks a lot!!!

Closed at this issue


Swarm over ssl not working?

I am having trouble getting swarm working and I'm wondering if I'm doing something obviously wrong.
My error message is:

Error response from daemon: No healthy node available in the cluster

My steps to reproduce are:

Use docker-machine RC1 to create a docker host on digitalocean (docker-1)

as machine ssh docker-1:
swarm join --addr xx.yy.zz.252:2376 --discovery token://<token>

as machine ssh docker-1 (same host as step 2):
swarm manage --tlsverify --tlscacert=/etc/docker/ca.pem --tlskey=/etc/docker/server-key.pem --tlscert=/etc/docker/server.pem -H tcp://xx.yy.zz.252:10000 --discovery token://<token>

Now from the host that I did the initial machine create docker-1 on:
docker ps
docker --tls --tlscacert=/home/pdericson/.docker/machines/docker-1/ca.pem --tlscert=/home/pdericson/.docker/machines/docker-1/cert.pem --tlskey=/home/pdericson/.docker/machines/docker-1/key.pem -H tcp://xx.yy.zz.252:10000 ps

OK:
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES

docker run
docker --tls --tlscacert=/home/pdericson/.docker/machines/docker-1/ca.pem --tlscert=/home/pdericson/.docker/machines/docker-1/cert.pem --tlskey=/home/pdericson/.docker/machines/docker-1/key.pem -H tcp://xx.yy.zz.252:10000 run ubuntu:trusty /bin/bash

NG:
FATA[0001] Error response from daemon: No healthy node available in the cluster

Notes:

swarm manage is reporting
Get https://xx.yy.zz.252:2376/v1.15/info: remote error: handshake failure

Any ideas?  I think it's interesting that I'm able to do a "docker ps" against xx.yy.zz.252:10000 - that makes me think I'm almost there, just not sure if I'm doing something obviously wrong so wanted to check here before I dig any deeper.
Cheers

As far as i understand it, swarm's TLS support requires all host's certificates to be signed using the same ca.cert, which is not how boot2docker (and i'm not sure about the DO machine implementation) works.

Yes, the way docker-machine is creating certs (up to and including the RC) is not compatible with what swarm needs (for --tlsverify)
docker-machine master has changed how it generates TLS certs so that you can (more) easily add any machine created by docker-machine to a swarm cluster (assuming swarmd was started with a keypair signed by that CA as well)
On the docker-machine RC, each new machine gets a new CA key pair, a new server key pair, and a new client key pair. This is problematic because when doing tls verification (of either client and/or server), the keys you are using need to be signed by the same CA.
On docker-machine master, only 1 CA and client key pair are created (for all machines), and each machine gets its own server key pair signed by the 1 CA.
Still some work to do on the machine side to make this more seamless, but it's coming along!

Yes, what @cpuguy83 said.
@pdericson There should be a few self explaining messages in the swarm logs about not being able to communicate with the nodes.
Can you confirm?

Hmmm
Using docker-machine built from c209704
machine create -d digitalocean docker-1
machine ssh docker-1
root@docker-1:~# swarm join --addr ...:2376 --discovery token://...

machine ssh docker-1
root@docker-1:~# swarm manage --tlsverify --tlscacert=/etc/docker/ca.pem --tlskey=/etc/docker/server-key.pem --tlscert=/etc/docker/server.pem -H tcp://...:1000
0 --discovery token://...

Really appreciate the help everyone

/cc @ehazlett

This is because currently machine does not generate the proper extended usage in the certificate.  I have a branch "swarm" on my fork that does this and will be merged soon.

Thanks @ehazlett. I'm closing this down since it's not swarm related.
@pdericson: Please re-open if the problem is not fixed once @ehazlett's branch gets merged into machine.

yw
On Wed, Jan 28, 2015 at 12:38 AM, Andrea Luzzardi<EMAIL_ADDRESS>wrote:

Closed #311 https://github.com/docker/swarm/issues/311.
—
Reply to this email directly or view it on GitHub
https://github.com/docker/swarm/issues/311#event-225865433.

Working in https://github.com/ehazlett/machine/tree/swarm :)  thanks


yolo make file and missing files in host directory

The Makefile in the ./yolo directory is looking for some host files.
These files:
HOST_SRCS = ./host/main_yolo_3.8.cpp ../common/ocl_util.cpp ../common/timer.cpp ./host/utility/region.cpp ./host/utility/box.cpp ./host/utility/showboxes.cpp

But they do not exist in the yolo directory. I did find the ./host directory in ./project, but the files listed above are not present their either.

I did a little more digging and it looks like you added all of that logic on the latest commit.
The main project is located in the 'project' directory, so the yolo was and is just a reference at this point.
It would be great if you could share enough to make it a complete project.

We will make a update in the following weeks.  Thx for the reminds.


Task #119 signature help implementation revamp

Purpose

Resolves #119

Goals

Introduce node visitor based signature resolving implementation

Approach

Add the node visitor to traverse the BlangPackage to identify the scope and extract the function information

Closing the PR since this has been merged in the latest repo


Add message throttling to the reporter example

r? @vinipsmaker
(maidsafe_highfive has picked a reviewer for you, use r? to override)

This should fix https://github.com/maidsafe/crust/issues/364.


Add error handlers for developers to handle internal errors in clients

Motivation
When some internal errors occur (in fact, they're usually errors caused by the custom callbacks provided by developers), there is no way for developers to know the errors have occurred. e.g.
    constructor(turmsClient: TurmsClient) {
        this._turmsClient = turmsClient;
        this._turmsClient.driver
            .addNotificationListener(notification => {
                const isBusinessNotification = notification.relayedRequest
                    && !notification.relayedRequest.createMessageRequest
                    && !notification.closeStatus;
                if (isBusinessNotification) {
                    // If "listener(notification.relayedRequest)" throws, developers cannot know it.
                    this._notificationListeners.forEach(listener => listener(notification.relayedRequest));
                }
            });
    }

so we should provide developers with error handlers for these cases.


Resources: limits/requests should be ignored for initContainers

Currently, polaris reports a warning of cpu/memory limits and requests missing on initContainers but per https://kubernetes.io/docs/concepts/workloads/pods/init-containers/#resources I don't think that setting limits/requests on initContainers is standard / best practice?
Correct me if wrong!

Hey @alexcurtin, this is a great find, thanks! Although these can be useful in some cases, I think those are quite rare, so we're disabling these checks for init containers by default. I've opened a PR for that referenced above, we should get this out in our next release.

Fixed in 0.1.5. Thanks for the report!


updated version to 4.3 rc

Coverage remained the same at 75.337% when pulling a879e4016298f97baaada09f29f9051894ac7493 on Hadis-Fard:dev into a97a2f58800ba6709a2c8a6f1cdae75765ce27d1 on Microsoft:dev.


Validation on $element before Duplicate

Check if  is canCreate before duplicate element. This will resolve https://github.com/dnadesign/silverstripe-elemental/issues/857

@Jianbinzhu I've picked up this issue in a new PR to try and get this one over the line.  There's some additional UX changes that need to be made, though we can take care of those for you.
I've put you down as as a co-author in the git commit message


Shut down HTTP server at upgrade to avoid immortal thread

@jsingle Turns out exec and threads play about as well together as fork and threads do. During upgrade flow, we need to make sure to shut down the HTTP server, or we lose track of it completely (and it never dies) once we exec to the new binary.

Is this better than having the thread variable accessible and stopping the server that way?


firestore-clear CLI is not working

Expected behavior
To delete my entire DB information
Actual behavior
Error:
'firestore-clear' is not recognized as an internal or external command, operable program or batch file.
Steps to reproduce the behavior
Just execute the command.
firestore-import works perfectly
firestore-export works perfectly.

@amerbazerbachi Thanks for catching this


X.L.MagicFocus: always use focused as master

Description
Instead of searching for the currently focused window across workspaces,
make it so there is never any window above focus on the Stack that is
given to the modified layout.
Closes #657.
Checklist

[x] I've read CONTRIBUTING.md

[x] I've considered how to best test these changes (property, unit,
manually, ...) and concluded: manually

[x] I updated the CHANGES.md file

Thanks!


Separate Optimization workflow

NOTE: hooking up the new workflow and widgets into the main ATMOSPEC workflow an app is a task for another PR.
TODO:

[ ] Solve #117
[ ] Do not submit OrcaBaseWorkChain, subclass it and submit the OrcaCalculation CalcJob directly
[ ] Attach energies and boltzmann weights to TrajectoryData
[x] Add Code and Resources widgets as inputs
[x] Tests: Tests status of all steps throughout
[x] Test buttons enabled / disabled
[x] Robustness of steps, input parameter from UI handling per QeApp

Closes #103

Remaining TODO items will be implemented in follow up PRs, this one is an MVP.


AuthenticationPrincipal is not null when Authorization header is absent

When making 2 successive calls, one with Authorization Header and the second without one (but both with header Cache-Control = private, max-age=0, no-cache), the Second call still have the AuthenticationPrincipal ClientDetail param set in the controller.
For what i understand from http://docs.spring.io/spring-security/site/docs/3.2.0.CI-SNAPSHOT/reference/html/headers.html, If i'm not specifying any headers then Cache-Control is enabled for responses and spring does not cache the request.
The weirdest part that HttpServletRequest.getHeaderNames() does not contain the Authorization header for the second call but i'm still authenticated.
Is it normal behavior? if so how can i change this kind of behavior? I'm Using Spring-boot
Totally unrelated question: when debugging my app, i've put break point at OAuth2AuthenticationProcessingFilter.doFilter() and every second (or less) there is a call with empty body of type FirewalledRequest[ org.apache.catalina.connector.RequestFacade@e6d141d]
Is it normal?

I can't say I've ever had that experience. Maybe if you could publish a simple minimal project that reproduces it we could take a closer look. No server should cache requests that are authenticated, so I doubt if that is the issue (unless you are running through some funky proxy).
The other question about the OAuth2AuthenticationProcessingFilter breakpoint only makes sense if there is a process in your environment pinging your app. It happens, but it's nothing to do with Spring. Check your OS and anti-virus settings, and ask your sysadmin (if you have one) what he is doing to spy on you.

Thanks for your answer. well i've made an example project but surprise surprise..it's working as expected. the configuration are exact and i've even used the same custom token store.
I did however compare between the security logs of both the projects and found diffs between them:
(both calls are the first call with Authorization header, i only show log lines that are in the bad request and not in the good request)
In the not working correctly server:
DEBUG org.springframework.security.web.FilterChainProxy - /greeting at position 2 of 10 in additional filter chain; firing Filter: 'SecurityContextPersistenceFilter'
(*not in good request*) DEBUG org.springframework.security.web.context.HttpSessionSecurityContextRepository - HttpSession returned null object for SPRING_SECURITY_CONTEXT
 (*not in good request*) DEBUG org.springframework.security.web.context.HttpSessionSecurityContextRepository - No SecurityContext was available from the HttpSession: org.apache.catalina.session.StandardSessionFacade@5f5df6dc. A new one will be created.

and:
DEBUG org.springframework.security.web.FilterChainProxy - /greeting at position 6 of 10 in additional filter chain; firing Filter: 'RequestCacheAwareFilter'
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - pathInfo: both null (property equals)
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - queryString: both null (property equals)
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - requestURI: arg1=/greeting; arg2=/greeting (property equals)
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - serverPort: arg1=8080; arg2=8080 (property equals)
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - requestURL: arg1=http://<IP_ADDRESS>:8080/greeting; arg2=http://<IP_ADDRESS>:8080/greeting (property equals)
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - scheme: arg1=http; arg2=http (property equals)
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - serverName: arg1=<IP_ADDRESS>; arg2=<IP_ADDRESS> (property equals)
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - contextPath: arg1=; arg2= (property equals)
DEBUG org.springframework.security.web.savedrequest.DefaultSavedRequest - servletPath: arg1=/greeting; arg2=/greeting (property equals)
DEBUG org.springframework.security.web.savedrequest.HttpSessionRequestCache - Removing DefaultSavedRequest from session if present

Also in the bad request AnonymousAuthenticationFilter is not present
SessionManagementFilter:
(not in good request, only in bad one)DEBUG org.springframework.security.web.context.HttpSessionSecurityContextRepository - SecurityContext stored to HttpSession: 'org.springframework.security.core.context.SecurityContextImpl@49bfd88: Authentication: org.springframework.security.oauth2.provider.OAuth2Authentication@49bfd88: Principal: com.questter.boshi.services.users.CustomUserDetailsService$UserRepositoryUserDetails@1db6f98c; Credentials: [PROTECTED]; Authenticated: true; Details: remoteAddress=<IP_ADDRESS>, sessionId=<SESSION>, tokenValue=<TOKEN>; Granted Authorities: ROLE_USER'

DEBUG org.springframework.security.web.context.HttpSessionSecurityContextRepository - SecurityContext stored to HttpSession: 'org.springframework.security.core.context.SecurityContextImpl@49bfd88: Authentication: org.springframework.security.oauth2.provider.OAuth2Authentication@49bfd88: Principal: com.questter.boshi.services.users.CustomUserDetailsService$UserRepositoryUserDetails@1db6f98c; Credentials: [PROTECTED]; Authenticated: true; Details: remoteAddress=<IP_ADDRESS>, sessionId=<SESSION>, tokenValue=<TOKEN>; Granted Authorities: ROLE_USER'
DEBUG org.springframework.security.web.context.HttpSessionSecurityContextRepository - SecurityContext stored to HttpSession: 'org.springframework.security.core.context.SecurityContextImpl@49bfd88: Authentication: org.springframework.security.oauth2.provider.OAuth2Authentication@49bfd88: Principal: com.questter.boshi.services.users.CustomUserDetailsService$UserRepositoryUserDetails@1db6f98c; Credentials: [PROTECTED]; Authenticated: true; Details: remoteAddress=<IP_ADDRESS>, sessionId=<SESSION>, tokenValue=<TOKEN>; Granted Authorities: ROLE_USER'
DEBUG org.springframework.security.web.context.HttpSessionSecurityContextRepository - SecurityContext stored to HttpSession: 'org.springframework.security.core.context.SecurityContextImpl@49bfd88: Authentication: org.springframework.security.oauth2.provider.OAuth2Authentication@49bfd88: Principal: com.questter.boshi.services.users.CustomUserDetailsService$UserRepositoryUserDetails@1db6f98c; Credentials: [PROTECTED]; Authenticated: true; Details: remoteAddress=<IP_ADDRESS>, sessionId=<SESSION>, tokenValue=<TOKEN>; Granted Authorities: ROLE_USER'

That's not really a full set of cards to read, but I'd say from the little you've given that your "bad" server has a different filter configuration, and probably the difference is to do with session creation (and hence it is sending a cookie back to the client whereas the "good" one is not). Probably your client is also sending a cookie with the second request (the one that you were surprised to see a non-null authentication).

I'm using postman client to send the request. there are no cookies, and the request is the same for both servers. The configuration is exact for both servers (i've just duplicated the configuration files for the sample project) but giving different results...can i post something more that will enable help us figure the problem? this is the sample project..https://github.com/roybrener/sample. also should i disable the SessionManagementFilter?

Your project doesn't compile for me. Is there a missing "Schema" class?

Yeah sorry about that...added import static com.ex.server.oauth.OAuth2Conf.*; to MongoOauth2AccessTokenDao

I can run the app now, and I can see the expected 401 responses from your REST resources but I don't know how to login or obtain an access token. I must say I do find it weird that you have a combined UserDetailsService and ClientDetailsService (they are clearly not the same thing), but that's probably irrelevant. I also think you'd be well advised to switch CSRF protection back on for your UI resources (if there ever are any - there seem to be none at the moment).

Thanks dave for your answer. currently there is no ui resources so no need for csrf. i will switch it back on in the near future. currently there is 1 user. my auth request is:

Also did you mean that by combining those 2 services what i'm basically doing is returning ClientDetails on loadUserByUsername? it's dirty solution that i will handle when all my configuration problems will go away.

OK, that gets me a token. I can't reproduce the problem though with curl. I suggest you try with a command line tool as well.

yeah, as i've wrote before...this is the sample app that is working as expected. the configuration is the though...just wanted to know if there is something in the configuration that i should change in order to disable caching.

Well since it all seems to work, and the things that looked odd (as mentioned) don't seem relevant, I think we are stuck. I really strongly advise you to test it on the command line, not using packaged software that you don't control.

Closing this as questions are better suited on Stack Overflow. We prefer to use GitHub issues for bugs and enhancements.


[Website]Lift timeout restriction on CI configuration

Description
This pull request works together with the previous pull quest #1252 . #1252 works on the python script part and this pull request works on the Jenkins CI part.
They work together to solve the problem from #1230
Checklist
Essentials

[x] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

cc @dmlc/gluon-nlp-team

Error log is below:
[2020-07-05T16:35:45.739Z] intersphinx inventory has moved: https://beta.mxnet.io/objects.inv -> https://mxnet.apache.org/

@szha It seems that an inventory on mxnet.io is not redirecting correctly? Which team is in charge of this part of work?
Thanks!

I think the beta.mxnet.io is deprecated and we should find the alternative on mxnet.apache.org

Fixed in #1256

Job PR-1255/4 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-1255/4/index.html


Cognitive Services 2023-10-01-preview

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[x] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[x] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

        "$ref": "../../../../../common-types/resource-management/v2/types.json#/parameters/ResourceGroupNameParameter"

please always use the latest common type version. Current is v5.

Refers to: specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/preview/2023-10-01-preview/cognitiveservices.json:1375 in 1dce978. [](commit_id = 1dce978eecbd4302099c269c7fd604b0700c8aa9, deletion_comment = False)

"deploymentNameParameter": {

since it's referenced in the newly added operation, please add pattern to fix the lint-diff ResourceNameRestriction error:
https://github.com/Azure/azure-rest-api-specs/pull/26054/checks?check_run_id=17481379278

Refers to: specification/cognitiveservices/resource-manager/Microsoft.CognitiveServices/preview/2023-10-01-preview/cognitiveservices.json:5327 in 1dce978. [](commit_id = 1dce978eecbd4302099c269c7fd604b0700c8aa9, deletion_comment = False)

Hi @ms-zhenhua, about "deploymentNameParameter", it's not a newly added parameter, if I add "pattern", will cause breaking change. And it seems like changing the common type version to v5 also cause some breaking change. Will these pass the breaking change review?

Hi @tianxin-ms, since it will cause breaking change, please revert your changes and  follow Swagger-Suppression-Process to suppress ResourceNameRestriction in https://github.com/Azure/azure-rest-api-specs/pull/26054/checks?check_run_id=17481379278.  Thanks.

Hi @ms-zhenhua, @rkmanda, can you please help review this PR and I reverted the changes that cause breaking-change, added suppressions to readme file, who will help with Suppression Review?

Hi @tianxin-ms please also suppress ResourceNameRestriction in https://github.com/Azure/azure-rest-api-specs/pull/26054/checks?check_run_id=17588226340 with the breaking change reason.

Hi @ms-zhenhua, thank you for the review, suppressions were updated, please help review again. Thank you!

/pr RequestMerge


recommended nix-channel or nixpkgs version?

I'm trying it out with latest nixpkgs-unstable on OS X 10.11.6, and running nix-shell in the hseverywhere directory leads to building GHC 7.8.4... kind of crazy, isn't it?
Do you think specifying a particular version of ghc and/or ghcjs (in default.nix) can fix this problem?
Before I did the nix-channel --update, I ran into some broken dependency issue in building ghcjs. So I thought maybe I should update the channel, and now this...

well, even the latest wouldn't work. Still fails at haddock:
Configuring haddock-2.17.2...
Setup: At least the following dependencies are missing:
haddock-api ==2.17.*
builder for ‘/nix/store/88plc2m43y6b31bgxpz2628rdhnk5m3f-haddock-2.17.2.drv’ failed with exit code 1

Looks like I'm hit by this: https://github.com/NixOS/nixpkgs/issues/17176

Hi,
I have no idea about the stability of different nix-channels/branches or ghc/ghcjs in them...
... except that everything seems to break every now and then at least in nixpkgs master. That's why I wanted to make this project always use an explicitly specified state (in nix-revision.txt), so that it doesn't break even if you meddle with your global Nix installation.
Unfortunately I seem to have forgot to "purify" the basic shell (whoops), so running "nix-shell" used your global Nix installation. Please use "./shell.sh" to start the shell in the same revision all other scripts use. If you want to try different revision just set it in nix-revision.txt and try out the different script to see if it works.
Does this solve your problem, even though it doesn't directly answer your question about recommended channel/revision?

Thanks! I'm trying it out...

Yes, it worked! Thanks a bunch! This is a very cool project, keep it coming!


slicer3d: init at 5.6.2

Adds slicer 3d package. This is a qt5 package, so this isn't placed in by-name. Also, this isn't a source build due to the the source build seemingly requiring git clones that aren't able to be disabled with a cmake variable as far as I can tell.
I've tested and used the main executable, but not any of the other ones since there are many of them.
There is a darwin version but I don't have use macos so I didn't add support for that here.
@bcdarwin this might be of interest to you to review if you'd like.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release 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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@bcdarwin All comments addressed.
I did, however, realize I made a mistake: they use a modified version of the bsd licence. What should I do to reference it correctly?
https://github.com/Slicer/Slicer/blob/main/License.txt

@bcdarwin All comments addressed. I did, however, realize I made a mistake: they use a modified version of the bsd licence. What should I do to reference it correctly? https://github.com/Slicer/Slicer/blob/main/License.txt

Use licenses.free and leave a comment and/or link to source file.

@bcdarwin I can't seem to reply to the last comment about hwloc for whatever reason, so this is a reply to that:
I have only really used slicer to open and browse images, so I don't think i did anything that would use hwlo(I.e. network stuff?). With that in mind, I haven't had any crashes due to it.
I spent a decent amount of time when i first made this for myself earlier in the year, and couldn't, but if it's something that would block a good amount of features I can give it another shot.

Every review comment was implemented aside from retrying an old version of hwloc.

does this need a rebase ?

Rebased. Only needed change in the maintainers file due to a conflict there.

@pluiedev All review comments should be addressed.

As far as I can tell, it will be a pretty monumental task to build from source since there are a very large amount of remote git repos that they pull in while building that, at least when I checked a few months ago, weren't easily able to be disabled.
The best way to do it would probably be to just upstream improvements to their build system from what I can tell.


cmake: check sdk_version format

I encountered situation when after zephyr-sdk had been installed west build was unable to work despite I had done everything properly (at the firs glance)
It takes me extended amount of time to realize that sdk_version string was empty and this must had been the result of corrupted installation (I probably must had missed a message about failure).
The version should had 0.0.0 format.
Patch add check for this and descriptive failure message.
Objective is to help the user to recognize the installation failure.
Signed-off-by: Andrzej Puzdrowski<EMAIL_ADDRESS>

@carlescufi pleas revisit


Need help in creating workspace with backpack and all others

i need to create a workspace as appinventor ,so i have coded as below
1).injected a workspace then
2).made as below for backpack
`var opts={
collapse : true,
disable : true,
trashcan : true,
comments:true,

css : true,
rtl : false,
scrollbars : true,
sounds : true,
setMetrics:{
	absoluteLeft:100,
	absoluteTop:10,
	contentHeight:100,
	contentTop:10,
	contentLeft:10,
	contentWidth:10,
	flyoutHeight:undefined,
	flyoutWidth:undefined,
	svgHeight:undefined,
	svgWidth:undefined,
	toolboxHeight:undefined,
	toolboxPosition:undefined,
	toolboxWidth:undefined,
	viewHeight:10,
	viewLeft:100,
	viewTop:10,
	viewWidth:100
}

}
Blockly.Backpack(Blockly.getMainWorkspace(),opts);`
i got error as below for everythin i do like in case of backpack,show warnings/error, toolbox
;
can anyone fix it please
Regards surya,
Thanks in advance

Actually what is this bind error and how to solve it..

how to create block workspace as app inventor not the design part need only blocks using javascript need a guide throw it

@NeilFraser
can u help me with that please

I think we should continue this discussion on the forum as it doesn't actually pertain to the App Inventor sources.


net/http: add http.ListenAndServe to ServeMux.Handle example

What version of Go are you using (go version)?

$ go version
go version go1.14.4 darwin/amd64

Does this issue reproduce with the latest release?
In current package documentation at https://golang.org/pkg/net/http/#example_ServeMux_Handle
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GOARCH="amd64"
GOOS="darwin"

What did you expect to see?
Expected example to initiate http.ListenAndServe or equivalent with new ServeMux

package main

import (
	"fmt"
	"log"
	"net/http"
)

type apiHandler struct{}

func (apiHandler) ServeHTTP(http.ResponseWriter, *http.Request) {}

func main() {
	mux := http.NewServeMux()
	mux.Handle("/api/", apiHandler{})
	mux.HandleFunc("/", func(w http.ResponseWriter, req *http.Request) {
		// The "/" pattern matches everything, so we need to check
		// that we're at the root here.
		if req.URL.Path != "/" {
			http.NotFound(w, req)
			return
		}
		fmt.Fprintf(w, "Welcome to the home page!")
	})
	log.Fatal(http.ListenAndServe(":8080", mux))
}

What did you see instead?
The example immediately exits without serving

package main

import (
	"fmt"
	"net/http"
)

type apiHandler struct{}

func (apiHandler) ServeHTTP(http.ResponseWriter, *http.Request) {}

func main() {
	mux := http.NewServeMux()
	mux.Handle("/api/", apiHandler{})
	mux.HandleFunc("/", func(w http.ResponseWriter, req *http.Request) {
		// The "/" pattern matches everything, so we need to check
		// that we're at the root here.
		if req.URL.Path != "/" {
			http.NotFound(w, req)
			return
		}
		fmt.Fprintf(w, "Welcome to the home page!")
	})
}

I'd be happy to work on this for my first contribution if accepted

Thanks for reporting. I agree the example, as displayed at https://golang.org/pkg/net/http/#example_ServeMux_Handle, can feel like it's missing some code to start the server.
However, the example as written in code (see here), and displayed on<EMAIL_ADDRESS>at this time seems a lot more reasonable to omit starting up a server, since it's meant to show how to use the ServeMux.Handle method:
mux := http.NewServeMux()
mux.Handle("/api/", apiHandler{})
mux.HandleFunc("/", func(w http.ResponseWriter, req *http.Request) {
	// The "/" pattern matches everything, so we need to check
	// that we're at the root here.
	if req.URL.Path != "/" {
		http.NotFound(w, req)
		return
	}
	fmt.Fprintf(w, "Welcome to the home page!")
})

So, we should decide whether to do given it's displayed differently on those websites, and take it into account if examples are displayed differently in the future.
Given that the example doesn't have an // Output: comment, it doesn't seem like it should be displayed as a complete program, so the current pkg.go.dev (and godoc.org, see https://godoc.org/net/http#example-ServeMux-Handle) version seems better.
/cc @julieqiu @jba @shaqque


Fix bug where menu wouldn't open on the first click after a page reload

…ad and remove node click event listener so that window click event listener takes care of click events
Before submitting the PR:

[X] Does your PR reference an issue? If not, please chat to the team on Discord or GitHub before submission.
[X] Did you update and run tests before submission using npm run test?
[X] Does your branch follow our naming convention? If not, please amend the branch name using branch -m new-branch-name
[ ] Did you update documentation related to your new feature or changes?

What does your PR address?
This would Close #685, where the menu wouldn't open on the first click after a page reload.
Please briefly describe your changes here.
The problem was because onToggleClick was checking if the elemMenu.style.display === 'none' but this only gets set when the menu is closed, so when a click is made anywhere on the page but the menu button. I changed the if statement to fix this.
I also made another update and removed the node click event listener, since we already have a window click event listener, and having both of them was a bit confusing.
Tips

Tap "convert to draft" to indicate this is work in progress.
Link to an issue using the verbiage Fixes #XX
Linked issues will auto-close when the PR is merged.

This is great Benny, this feels much better to use in practice. Thank you for this!


[BSO] Improved Zippy

Description:

Changed zippy to account for multiple clues on the same trip, so people don't do 1 clue at time.

Changes:

It is a small nerf for lower clues and a huge buff for higher clues.

It takes into consideration if the user is maxing a trip (doing the maximum number of clues it can). If that is true, Zippy will give a chance do double it's rewards and improve the odds of receiving mystery boxes by 30%.

Users that have the collection log completed will have a 1 in 10 chance to receive double Zippy loot! Users that does not still have a 1 in 50.

Mystery boxes still have similar odds of dropping form Zippy if doing max trips or 30% lower if doing partial trips.

Zippy have been balanced to accept any amount of clues for the trip. The higher, the better the results in the long run.

Zippy no longer drops caskets above its trip clue tier. Any roll above it's trip clue tier will default to it's clue tier. So, if user is doing medium clues and the possibleReward rolls on a master casket, it'll default to a medium. Doing master is the only way to receive extra masters.

[X] I have tested all my changes thoroughly.

Here is the average new drop-rate for Zippy:
// Weight based on trips without any bonuses
// 1/500 becomes 1/100 if CL is complete
// rolls: number of zippy possible rewards / avg: average number or rolls per trip
// rolls/box: average number of rolls for a box to be rewarded
// a clue can't give a casket above its tier. So a medium can't give hard caskets.

Beginner: 1, // Roll: 13 to 13 | Avg: 13 | 1/10: 26 | 1/500: 52 | Rolls/Box[MaxTrip]: 1/27[18]
Easy: 2, //     Roll: 9  to 18 | Avg: 13 | 1/10: 26 | 1/500: 52 | Rolls/Box[MaxTrip]: 1/24[16]
Medium: 2, //   Roll: 6  to 12 | Avg: 9  | 1/10: 18 | 1/500: 36 | Rolls/Box[MaxTrip]: 1/24[16]
Hard: 3, //     Roll: 4  to 12 | Avg: 8  | 1/10: 16 | 1/500: 32 | Rolls/Box[MaxTrip]: 1/21[14]
Elite: 5, //    Roll: 3  to 15 | Avg: 9  | 1/10: 18 | 1/500: 36 | Rolls/Box[MaxTrip]: 1/15[10]
Master: 7 //    Roll: 3  to 21 | Avg: 12 | 1/10: 24 | 1/500: 48 | Rolls/Box[MaxTrip]: 1/9[6]```

Did my own simple and easy buff of zippy which I think is good enough.


Win10 + WSL2 + Ubuntu 20.04 + miniconda ：CUDA SETUP: CUDA detection failed!

System Info
Win10 + WSL2 + miniconda + Ubuntu 20.04
Reproduction
I am using Ubuntu 20.04 in WSL2, Win10, miniConda
I installed bitsandbytes by conda install conda-forge::bitsandbytes
The conda env config vars list is:
BNB_CUDA_VERSION = 124
LD_LIBRARY_PATH = /usr/local/cuda-12.4

I set the LD_LIBRARY_PATH, bitsandbytes didn't use the toolkit I installed.
I installed multi version cudatoolkit by the fellowing command:
wget https://developer.download.nvidia.com/compute/cuda/repos/wsl-ubuntu/x86_64/cuda-wsl-ubuntu.pin
sudo mv cuda-wsl-ubuntu.pin /etc/apt/preferences.d/cuda-repository-pin-600
wget https://developer.download.nvidia.com/compute/cuda/12.4.0/local_installers/cuda-repo-wsl-ubuntu-12-4-local_12.4.0-1_amd64.deb
sudo dpkg -i cuda-repo-wsl-ubuntu-12-4-local_12.4.0-1_amd64.deb
sudo cp /var/cuda-repo-wsl-ubuntu-12-4-local/cuda-*-keyring.gpg /usr/share/keyrings/
sudo apt-get update
sudo apt-get -y install cuda-toolkit-12-4

wget https://developer.download.nvidia.com/compute/cuda/12.2.0/local_installers/cuda-repo-wsl-ubuntu-12-2-local_12.2.0-1_amd64.deb
sudo dpkg -i cuda-repo-wsl-ubuntu-12-2-local_12.2.0-1_amd64.deb
sudo cp /var/cuda-repo-wsl-ubuntu-12-2-local/cuda-*-keyring.gpg /usr/share/keyrings/
sudo apt-get update
sudo apt-get -y install cuda-toolkit-12-2

wget https://developer.download.nvidia.com/compute/cuda/12.1.0/local_installers/cuda-repo-wsl-ubuntu-12-1-local_12.1.0-1_amd64.deb
sudo dpkg -i cuda-repo-wsl-ubuntu-12-1-local_12.4.0-1_amd64.deb
sudo cp /var/cuda-repo-wsl-ubuntu-12-1-local/cuda-*-keyring.gpg /usr/share/keyrings/
sudo apt-get update
sudo apt-get -y install cuda-toolkit-12-1

wget https://developer.download.nvidia.com/compute/cuda/11.8.0/local_installers/cuda-repo-wsl-ubuntu-11-8-local_11.8.0-1_amd64.deb
sudo dpkg -i cuda-repo-wsl-ubuntu-11-8-local_11.8.0-1_amd64.deb
sudo cp /var/cuda-repo-wsl-ubuntu-11-8-local/cuda-*-keyring.gpg /usr/share/keyrings/
sudo apt-get update
sudo apt-get -y install cuda-toolkit-11-8

The output of python -m bitsandbytesis blow:
/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/cuda_setup/main.py:122: UserWarning:

================================================================================
WARNING: Manual override via BNB_CUDA_VERSION env variable detected!
BNB_CUDA_VERSION=XXX can be used to load a bitsandbytes version that is different from the PyTorch CUDA version.
If this was unintended set the BNB_CUDA_VERSION variable to an empty string: export BNB_CUDA_VERSION=
If you use the manual override make sure the right libcudart.so is in your LD_LIBRARY_PATH
For example by adding the following to your .bashrc: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:<path_to_cuda_dir/lib64
Loading: libbitsandbytes_cuda124.so
================================================================================

  warn(
False

===================================BUG REPORT===================================
/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/cuda_setup/main.py:183: UserWarning: Welcome to bitsandbytes. For bug reports, please run

python -m bitsandbytes

  warn(msg)
================================================================================
/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/cuda_setup/main.py:183: UserWarning: /home/donadjohn/miniconda3/envs/hg1 did not contain ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0', 'libcudart.so.12.1', 'libcudart.so.12.2'] as expected! Searching further paths...
  warn(msg)
/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/cuda_setup/main.py:183: UserWarning: Found duplicate ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0', 'libcudart.so.12.1', 'libcudart.so.12.2'] files: {PosixPath('/usr/local/cuda/lib64/libcudart.so'), PosixPath('/usr/local/cuda/lib64/libcudart.so.12.0')}.. We select the PyTorch default libcudart.so, which is {torch.version.cuda},but this might mismatch with the CUDA version that is needed for bitsandbytes.To override this behavior set the BNB_CUDA_VERSION=<version string, e.g. 122> environmental variableFor example, if you want to use the CUDA version 122BNB_CUDA_VERSION=122 python ...OR set the environmental variable in your .bashrc: export BNB_CUDA_VERSION=122In the case of a manual override, make sure you set the LD_LIBRARY_PATH, e.g.export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-12.2
  warn(msg)
/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/cuda_setup/main.py:183: UserWarning: /usr/local/cuda/lib64: did not contain ['libcudart.so', 'libcudart.so.11.0', 'libcudart.so.12.0', 'libcudart.so.12.1', 'libcudart.so.12.2'] as expected! Searching further paths...
  warn(msg)
The following directories listed in your path were found to be non-existent: {PosixPath('/home/donadjohn/installed_softwares/jdk-11.0.13/jre')}
The following directories listed in your path were found to be non-existent: {PosixPath('//<IP_ADDRESS>'), PosixPath('2080'), PosixPath('http')}
The following directories listed in your path were found to be non-existent: {PosixPath('//<IP_ADDRESS>'), PosixPath('2080'), PosixPath('http')}
The following directories listed in your path were found to be non-existent: {PosixPath('/home/donadjohn/installed_softwares/jdk-11.0.13/jre/lib')}
CUDA_SETUP: WARNING! libcudart.so not found in any environmental path. Searching in backup paths...
DEBUG: Possible options found for libcudart.so: {PosixPath('/usr/local/cuda/lib64/libcudart.so'), PosixPath('/usr/local/cuda/lib64/libcudart.so.12.0')}
CUDA SETUP: PyTorch settings found: CUDA_VERSION=121, Highest Compute Capability: 8.9.
CUDA SETUP: To manually override the PyTorch CUDA version please see:https://github.com/TimDettmers/bitsandbytes/blob/main/how_to_use_nonpytorch_cuda.md
CUDA SETUP: Required library version not found: libbitsandbytes_cuda121.so. Maybe you need to compile it from source?
CUDA SETUP: Defaulting to libbitsandbytes_cpu.so...

================================================ERROR=====================================
CUDA SETUP: CUDA detection failed! Possible reasons:
1. You need to manually override the PyTorch CUDA version. Please see: "https://github.com/TimDettmers/bitsandbytes/blob/main/how_to_use_nonpytorch_cuda.md
2. CUDA driver not installed
3. CUDA not installed
4. You have multiple conflicting CUDA libraries
5. Required library not pre-compiled for this bitsandbytes release!
CUDA SETUP: If you compiled from source, try again with `make CUDA_VERSION=DETECTED_CUDA_VERSION` for example, `make CUDA_VERSION=118`.
CUDA SETUP: The CUDA version for the compile might depend on your conda install. Inspect CUDA version via `conda list | grep cuda`.
================================================================================

CUDA SETUP: Something unexpected happened. Please compile from source:
git clone https://github.com/TimDettmers/bitsandbytes.git
cd bitsandbytes
CUDA_VERSION=121 make cuda12x
python setup.py install
CUDA SETUP: Setup Failed!
Traceback (most recent call last):
  File "<frozen runpy>", line 189, in _run_module_as_main
  File "<frozen runpy>", line 148, in _get_module_details
  File "<frozen runpy>", line 112, in _get_module_details
  File "/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/__init__.py", line 6, in <module>
    from . import cuda_setup, research, utils
  File "/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/research/__init__.py", line 2, in <module>
    from .autograd._functions import (
  File "/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/research/autograd/_functions.py", line 8, in <module>
    from bitsandbytes.autograd._functions import GlobalOutlierPooler, MatmulLtState
  File "/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/autograd/__init__.py", line 1, in <module>
    from ._functions import get_inverse_transform_indices, undo_layout
  File "/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/autograd/_functions.py", line 10, in <module>
    import bitsandbytes.functional as F
  File "/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/functional.py", line 17, in <module>
    from .cextension import COMPILED_WITH_CUDA, lib
  File "/home/donadjohn/miniconda3/envs/hg1/lib/python3.11/site-packages/bitsandbytes/cextension.py", line 17, in <module>
    raise RuntimeError('''
RuntimeError:
        CUDA Setup failed despite GPU being available. Please run the following command to get more information:

        python -m bitsandbytes

        Inspect the output of the command and see if you can locate CUDA libraries. You might need to add them
        to your LD_LIBRARY_PATH. If you suspect a bug, please take the information from python -m bitsandbytes
        and open an issue at: https://github.com/TimDettmers/bitsandbytes/issues

Expected behavior
Anyone encountered this?

I solved this problem, the bitsandbytes.0.43.0 from conda-forge is not work for me,
I downgraded to 0.42.0, by conda install bitsandbytes=0.42.0,  it works now!
The total steps to recover is below:
//create new conda env
conda create -n py312 python=3.12

conda install conda-forge::transformers conda-forge::accelerate conda-forge::bitsandbytes=0.42

python -m bitsandbytes

it should work now, the python -m bitsandbytes output is below:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++ BUG REPORT INFORMATION ++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

++++++++++++++++++ /usr/local CUDA PATHS +++++++++++++++++++
/usr/local/cuda-11.8/targets/x86_64-linux/lib/stubs/libcuda.so
/usr/local/cuda-11.8/targets/x86_64-linux/lib/libcudart.so
/usr/local/cuda-12.4/targets/x86_64-linux/lib/stubs/libcuda.so
/usr/local/cuda-12.4/targets/x86_64-linux/lib/libcudart.so
/usr/local/cuda-12.2/targets/x86_64-linux/lib/stubs/libcuda.so
/usr/local/cuda-12.2/targets/x86_64-linux/lib/libcudart.so

+++++++++++++++ WORKING DIRECTORY CUDA PATHS +++++++++++++++
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda110.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda110_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda111.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda111_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda114.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda114_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda115.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda115_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda117.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda117_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda118.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda118_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda120.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda120_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda121.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda121_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda122.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda122_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda123.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/bitsandbytes/libbitsandbytes_cuda123_nocublaslt.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/torch/lib/libc10_cuda.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/torch/lib/libtorch_cuda.so
/mnt/d/workspace/myenv/lib/python3.8/site-packages/torch/lib/libtorch_cuda_linalg.so

++++++++++++++++++ LD_LIBRARY CUDA PATHS +++++++++++++++++++

++++++++++++++++++++++++++ OTHER +++++++++++++++++++++++++++
COMPILED_WITH_CUDA = True
COMPUTE_CAPABILITIES_PER_GPU = ['8.9']
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++++++++++++++++++++ DEBUG INFO END ++++++++++++++++++++++
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Running a quick check that:
    + library is importable
    + CUDA function is callable

WARNING: Please be sure to sanitize sensible info from any such env vars!

SUCCESS!
Installation was successful!

eh,
The fellowing code is still now working, but in venv it works, same code, same lib version, I am giving up, I am swiching to venv from conda:

>>> from transformers import AutoModelForCausalLM
>>>
>>> model = AutoModelForCausalLM.from_pretrained(
...     "mistralai/Mistral-7B-v0.1", device_map="auto", load_in_4bit=True
... )
The `load_in_4bit` and `load_in_8bit` arguments are deprecated and will be removed in the future versions. Please, pass a `BitsAndBytesConfig` object in `quantization_config` argument instead.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/donadjohn/miniconda3/envs/py312/lib/python3.11/site-packages/transformers/models/auto/auto_factory.py", line 563, in from_pretrained
    return model_class.from_pretrained(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/donadjohn/miniconda3/envs/py312/lib/python3.11/site-packages/transformers/modeling_utils.py", line 3049, in from_pretrained
    hf_quantizer.validate_environment(
  File "/home/donadjohn/miniconda3/envs/py312/lib/python3.11/site-packages/transformers/quantizers/quantizer_bnb_4bit.py", line 62, in validate_environment
    raise ImportError(
ImportError: Using `bitsandbytes` 8-bit quantization requires Accelerate: `pip install accelerate` and the latest version of bitsandbytes: `pip install -i https://pypi.org/simple/ bitsandbytes`

OK, I downgraded python to 3.8, it works again,
I'm impressed.

I had the same issue that you using an Ubuntu 22.04 machine and a conda venv. On my end, I believe that the problem was due to dependency conflicts between cuda, pytorch and bitsandbytes.
I decided to reinstall everything on a new venv using python 3.11 :
conda create -y -n myenv python=3.11
pip3 install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu118
pip install transformers
pip install bitsandbytes

I installed the 0.43.0 version for bitsandbytes
According to the bitsandbytes documentation on HuggingFace: https://huggingface.co/docs/bitsandbytes/main/en/installation
I then followed this code snippet and changed the version to my version (118) :
wget https://raw.githubusercontent.com/TimDettmers/bitsandbytes/main/install_cuda.sh
# Syntax cuda_install CUDA_VERSION INSTALL_PREFIX EXPORT_TO_BASH
#   CUDA_VERSION in {110, 111, 112, 113, 114, 115, 116, 117, 118, 120, 121, 122, 123, 124}
#   EXPORT_TO_BASH in {0, 1} with 0=False and 1=True

# For example, the following installs CUDA 11.7 to ~/local/cuda-11.7 and exports the path to your .bashrc

bash install_cuda.sh 117 ~/local 1

After running this my code was compiling without any issues


Not possible to add liquidity after upgrade to 2.3.0 and coin swap on DEX

What happened:
After updating to 2.3.0 and waiting for full sync I made a DFI => BTC change on the DEX.
Wanted to add Liquidity to the BTC Pool, but received the error in the added screenshot.

What you expected to happen:
I expected the App to add the amount of BTC / DFI.
How to reproduce it (as minimally and precisely as possible):
Close the error and retry to to add Liquidity.
What are your environment parameters?

DeFi App Version: 2.3.0
Operating System (OS): macOS Big Sur 11.2.1

app_logs.zip

Hi @Brownie89 , thanks for your feedback, the error Please wait for your transaction to be reflected in the next block before proceeding with a new transaction occurred because you may have too many transactions stuck in the same block. The solution for this would be to leave your app running for about 1–2 hours and let the app process your pending transactions. Type the following to check pending transactions via CLI: listtransactions

/triage accepted

Waiting for the error to solve itself was my first idea, but this didn't help.
After waiting a couple of hours I tried to swap a little amount of ETH on the DEX, this worked, but I still wasn't able to add BTC Liquidity.
Then I added some ETH to LM successfully, this may have changed something in the background, because after this step I was also able to add BTC.
All this should be visible in the appended log-files.

Today I was able to reproduce the error with the same steps already mentioned.
Changed DFI to BTC on DEX, tried to add it to LM and got the error. Waited for over 12 hours and retried with same error.
Added ETH to LM was successfully and afterwards I was able to add BTC to LM.

Hi @Brownie89 , thanks for elaborating, please give us time to investigate this.

I had the same issue. I solved it also by using the ETH-DFI first then the other pools worked fine but when I try to add first to BTC-DFI or USDT-DFI I'll get the same error.

Hi @Amino159 , thanks for your feedback, can you send your app logs please?

Of course. You'll find it attached.
app_logs.zip

Hi @Amino159 , thank you, please give us time to investigate this.

Hi @Amino159 , may I know what your output of the following:
getbalance — utxoDFI
gettokenbalances — accountDFI
The sum of utxoDFI & accountDFI would be your total DFI tokens.

getbalance
1.52960166
gettokenbalances
[
"3.03015864@0",

Hi @Amino159 , can you send 1 DFI to your address that holds the 1.52 DFI. You can check which address holds those DFI via CLI:
listaccounts {} false false true

@izzycsy When I check via the CLI I see serveral adresses but none of them is holding exactly the 1.52 DFI
But getbalance still same result as before.

@Amino159 does the DFI add up in your addresses? 1.52960166 + 3.03015864 = 4.5597603
DFI exist in 2 forms; utxoDFI and accountDFI. utxoDFI is used to pay for transactions fees while rewards received are in accountDFI. You can freely convert between the 2 anytime — at a 1:1 ratio. What you'll have to do is convert accountDFI to utxoDFI, the simplest way is to send DFI from your receive address B to your receive address A, the app will automatically convert for you.
Any function you use in the app charges a utxoDFI fee. It could be you've insufficient utxoDFI. Either that, or there's too many transactions going on in the same block, hence you'll have to wait for the next block to try again.

Hi @Brownie89 @Amino159 , update v2.3.2 is out, this is a mandatory update.
Please read through the release notes before updating.
Do give a thumbs up to this comment if your issue has been resolved, otherwise, please send new information (include screenshots) and app logs. Thank you.

I just had exactly the same problem with version 2.3.2. See logs for details.
Thanks!
defilogs.zip
Env:
DeFi Wallet Version: 2.3.2
Operating System (OS): macOS Big Sur 11.2.3

Having the same issue as above post installing 2.3.2
I'm able to make exchanges on DEX - however I cannot add to liquidity pool.
each time gives the above error.
"Please wait for your transaction to be reflected in the next block before proceeding with a new transaction."
DeFi Wallet Version: 2.3.2
Operating System (OS): macOS Big Sur 11.2.3

Hi @lraphael @mrowean , it’s likely that you've insufficient utxoDFI balance (min. 1 DFI) — which is required to perform swap and all other functions. DFI exist in 2 forms; utxoDFI and accountDFI. utxoDFI is used to pay for transactions fees while rewards received from liquidity mining (for example) are in accountDFI.
You can freely convert between the 2 anytime — at a 1:1 ratio. To convert accountDFI to utxoDFI, the simplest way would via be DeFi Wallet app. Go to send DFI > paste in your address (send to yourself), the app will convert for you.

Hi @Brownie89 @lraphael @mrowean , v2.3.3 is out. Please read through the release notes before updating. If you have not sync to 100%, there was a node issue on 05/04/2021 that may have cause the network error, everything is back online now, you may try the following:
Option 1 — Reset & Reindex (sync from 0%)

Settings > Reset & Reindex

Option 2 — Snapshot (sync from 90%+)

Settings > Reset & Reindex
Wait for app to start syncing
Ensure you’ve at least 27GB of extra space
Click on i located at bottom-left corner of app screen
Download Snapshot

If your issue persist, we can further discuss on the problem here v2.3.2 Unable to add liquidity. We would like to keep same issues in one thread. Thank you for your patience.


Active/Active failure tests have trouble working with kc-failover.sh script

Describe the bug
Cluster failure script within kc-failover.sh works functionally with some exceptions and manual interventions.
The cluster objects for both Keycloak and external Infinispan get deleted, however the command FAILOVER_MODE=CLUSTER_FAIL DOMAIN=a0ebba97687f87f44.dualstack.awsglobalaccelerator.com ./kc-failover.sh fails to complete the lifecycle as it gets stuck on the activeClusterDown function execution, details in DEBUG Log1.
However, the cluster is set in the desired state, and all the pods are deleted from Keycloak and Infinispan.
DEBUG Log1:
+ activeClusterDown a0ebba97687f87f44.dualstack.awsglobalaccelerator.com
+ DOMAIN=a0ebba97687f87f44.dualstack.awsglobalaccelerator.com
++ dig +short client.a0ebba97687f87f44.dualstack.awsglobalaccelerator.com
++ sort
+ CLIENT_IPS=
++ dig +short primary.a0ebba97687f87f44.dualstack.awsglobalaccelerator.com
++ sort
+ PRIMARY_IPS=
++ dig +short backup.a0ebba97687f87f44.dualstack.awsglobalaccelerator.com
++ sort
+ BACKUP_IPS=
+ [[ '' == '' ]]
+ [[ '' != '' ]]
+ return
+ sleep 0.1

And coming to the recovery command RECOVERY_MODE=ACTIVE DOMAIN=a0ebba97687f87f44.dualstack.awsglobalaccelerator.com ./kc-failover.sh the recovery function exists prematurely unable to find statefulsets.apps "infinispan" not found. And as well sometimes there seems to be a race condition between the Keycloak and Infinispan operators, causing a lag between when the Infinispan pods come up and when the Keycloak pods come up, which results in a work cache not available on start-up message from Keycloak, but it resolves eventually on its own when all the needed pods come up.
DEBUG Log2:
INFO:2024-08-16-13:26:50-EDT Running Recovery scenario - ACTIVE
+ cat
+ kubectl -n runner-keycloak apply -f -
route.route.openshift.io/aws-health-route unchanged
+ kubectl -n openshift-operators scale --replicas=1 deployment/infinispan-operator-controller-manager
deployment.apps/infinispan-operator-controller-manager scaled
+ kubectl -n runner-keycloak scale --replicas=1 deployment/keycloak-operator
deployment.apps/keycloak-operator scaled
+ kubectl -n runner-keycloak rollout status --watch --timeout=600s statefulset/infinispan
Error from server (NotFound): statefulsets.apps "infinispan" not found

Full log:
> FAILOVER_MODE=CLUSTER_FAIL DOMAIN=a0ebba97687f87f44.dualstack.awsglobalaccelerator.com ./kc-failover.sh
INFO:2024-08-16-11:24:13-EDT Entering Failover mode, with an initial delay of 60 seconds
INFO:2024-08-16-11:25:13-EDT Running Failover scenario - CLUSTER_FAIL
deployment.apps/infinispan-operator-controller-manager scaled
deployment "infinispan-operator-controller-manager" successfully rolled out
deployment.apps/keycloak-operator scaled
deployment "keycloak-operator" successfully rolled out
Warning: Immediate deletion does not wait for confirmation that the running resource has been terminated. The resource may continue to run on the cluster indefinitely.
pod "infinispan-0" force deleted
pod "infinispan-1" force deleted
pod "infinispan-2" force deleted
pod "infinispan-router-766c85c469-gf5cf" force deleted
pod "keycloak-0" force deleted
pod "keycloak-1" force deleted
pod "keycloak-2" force deleted
pod "keycloak-operator-5f94d75864-f5tqk" force deleted
pod "keycloak-with-aws-jdbc-wrapper-1-build" force deleted
statefulset.apps "infinispan" deleted
statefulset.apps "keycloak" deleted
^C
> RECOVERY_MODE=ACTIVE DOMAIN=a0ebba97687f87f44.dualstack.awsglobalaccelerator.com ./kc-failover.sh
INFO:2024-08-16-11:30:20-EDT Running Recovery scenario - ACTIVE
route.route.openshift.io/aws-health-route created
deployment.apps/infinispan-operator-controller-manager scaled
deployment.apps/keycloak-operator scaled
Error from server (NotFound): statefulsets.apps "infinispan" not found

Version
keycloak-benchmark latest main
Expected behavior
No response
Actual behavior
No response
How to Reproduce?
run the below commands using the kc-failover.sh script.
Failure test:
FAILOVER_MODE=GOSSIP_ROUTER_FAIL DOMAIN=XXXXXXXXXXX.dualstack.awsglobalaccelerator.com ./kc-failover.sh

Recovery test:
RECOVERY_MODE=ACTIVE DOMAIN=XXXXXXXXXXX.dualstack.awsglobalaccelerator.com ./kc-failover.sh

Anything else?
No response

this is being tracked under - #965

Tested and worked as expected.


Adds IDs to step arguments (DocString and DataTable)

Summary
Original PR: https://github.com/cucumber/cucumber/pull/847
So the idea is to add an id field to DocString and DataTable and reference them from their pickle equivalent.
Details

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
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 not work as expected).

Checklist:

[x] The change has been ported to Java.
[x] The change has been ported to Ruby.
[x] The change has been ported to JavaScript.
[x] The change has been ported to Go.
[ ] The change has been ported to .NET.
[ ] I've added tests for my code.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

@aslakhellesoy - pasting answer to your question in the previous PR

When is this needed?

It is used in cucumber-ruby-core compiler#create_multiline_arg
Both Test::DataTable and Test::DocString need Location when created. This may be dropped later on I guess, but for now I'll try to be as compliant as possible with the existing when moving cucumber-ruby to gherkin 9+

Both Test::DataTable and Test::DocString need Location when created

Ok, I see that. But is that location ever accessed/used anywhere? If not, wouldn't it be simpler to just pass in a dummy location, or better - remove it entirely?
I'd like to avoid adding more code that isn't used if possible.

it's indeed not that useful, I won't set them anymore in cucumber-ruby.


How can I delete all tags and taggings, where tags are only used once?

Since we use tags only to group objects, objects with one tag dont make sense but I can not find out how to solve that problem either over the console or else.

tag.destroy will delete the taggings as well right?


Import Text From Doc or txt file📄

Adding functionality to add text imported from the .txt format or .doc format

I wan’t to work on this

I wan’t to work on this

Hey @vidhi-mody sorry to say this. My University exams just got announced. So I couldn't proceed with the issue. Please unassign and give it to anyone who needs. Sorry Again!

Hey @vidhi-mody sorry to say this. My University exams just got announced. So I couldn't proceed with the issue. Please unassign and give it to anyone who needs. Sorry Again!

/polls "yes" "no" "why"

/polls "yes" "no" "why"

/polls Option1 'Option 2' "Option 3"
Automatically replace with the following markdown =>

/polls Option1 'Option 2' "Option 3"
Automatically replace with the following markdown =>


Add checkout-submodules parameter

I would love to use this action in one of my projects but I need support for automatically cloning submodules on checkout.

In the meantime, I've developed a workaround in the form of a Maven plugin: https://github.com/seart-group/git-submodule-maven-plugin. I've tested it on one of my other projects and found that it works quite well.


Stopping flings on iOS should not count as a touch

(A video would make this easy to understand, but it's not easy for me to capture one at this second.)
To repro:

Open Flutter Gallery on iOS
Fling scroll on the home page.

Lift your finger after stopping.  Notice that it counted your "stop scroll" as an action and activated the list item below your finger and took you to whatever demo you happened to be over.

Compare this behavior with how flings of other scrolling lists work on iOS (such as Settings), notice that Flutter's behavior is incorrect.
It's possible our behavior here is wrong on Android too, but I haven't confirmed yet.
Thanks to @goderbauer for bringing this to my attention.

We just tested, Android doesn't count these as touches either.  @Hixie said he'd take a look.

Got reverted due to blocking touches even after you stopped scrolling sometimes.  Eventually touches would work again, but sometimes took several seconds.  I was testing on iOS.


Flatten binary tree to linked list in c++

I want to con

hey @ritikbanger  i want to contribute to this issue...
please allow me...

Hello @ritikbanger,

Hello,
I want to Contribute to this code.

I am also a contributer...ony @ritikbanger  has right to assign...

Hello, Can you please assign this issue to me?
Thanks in advance :)

Hello, Can you please assign this issue to me?


Support libraw options

Phase 1
Dcraw reconstruction options

[ ] deadpixels str -- Filename to read bad pixels from insetad of .badpixels.
[ ] darkframe str -- Filename to read a darkframe from.
[ ] darkness int -- Darkness level.
[ ] saturation int -- Saturation.
[ ] noise_threshold int -- Wavelet noise reduction (generally ~100–1000).
[ ] color_correction tuple (red_mag float, blue_mag float) -- Scale the red and blue layers to fix chromatic aberration (defaults to (0.999, 1.001)).
[ ] highlights int -- Clip or blend highlights.

CLIP = 0 = 0 (default)  -- Clip all highlights to white.
IGNORE = 1 -- Leave highlights unclipped in various shades of pink.
BLEND = 2 -- Blend clipped and unclipped values for a gradual fade to white.
3+ -- Reconstruct highlights with various levels of aggressiveness.
RECONSTRUCT = 5 -- A good compromise.

Dcraw color options

[ ] white_balance (Enum, or tuple)

CAMERA (default) -- Use the camera's white balance if specified. Otherwise fallback to...
AVERAGE -- Calculate the white balance by averaging the entire image.
AREA -- Calculate based on a neutral area (expects a (left, top, width, height) iterable).
CUSTOM -- Also expect an array of 4 multipliers.
Need to decide on an API for setting custom/area WB. A WB class, or a setter method, or a second option for each?

[ ] color_space (Enum) -- Select the output color space.

RAW = 0
SRGB = 1 (default)
ADOBE = 2
WIDE_GAMUT = 3
KODAK = 4
XYZ = 5

Phase 2

[ ] Use color matrix from camera metadata (see man dcraw under Color Options)
profile string or const EMBEDDED -- Use the ICC color profile from a file or the embedded one (See #26)

Libraw only / rawkit only options

TODO: Add libraw things or anything we want to do ourselves here.

We can handle white balance like this with class methods and a WhiteBalance object.
from rawkit.color import WhiteBalance
{
	'white_balamce': WhiteBalance.camera
}

{
	'white_balamce': WhiteBalance.greybox(,,,)
}

{
	'white_balamce': WhiteBalance.auto
}

{
	'white_balamce': WhiteBalance.manual(,,,)
}

We also need to support setting the bit depth of output. It can only ever be 8 or 16, so it can probably just be a constant.

What happens if we just construct a WhiteBalance object, eg:
{
  'white_balance': WhiteBalance()
}

It seems reasonable to me that that should be the same as .camera by default, or possibly also be able to take init arguments to make it a manual one. Or we could just throw a TypeError or something.

We may also want to normalize some of these options; they're all different scales and units which aren't documented anywhere that I can find (I'm having to set things by a mix of educated guessing and trial and error to test the options as I add them).

Unexpected problem with the current approach to options which I should have thought of: It's hard to document them w/o adding a bunch of verbose placeholder methods (which I suppose is fine as we'll be doing that for a lot of options to normalize or validate them anyways).
Also, I sort of miss being able to set options with a literal (eg. options = { 'some': 'stuff', 'some_other': 'stuff' }) like you got with a dict.


Changes to AArch64 nofp variant

Make the variants strictly aligned
Create new variant for big endian
Create new variant for exceptions and RTTI

LGTM. I guess that the -mno-unaligned-access isn't present in multilib.json as we don't need to select a variant based on it.

It's not present in order to select these new variants with or without -mno-unaligned-access in the command-line.


Drop Python-3.8 support on 2024-10

EOL
Python 3.8: Oct 2024 https://endoflife.date/python

update old syntax compat code
update tox and github CI
update pyproject.yml
update document
bump version X.y.z for imcompatible update

done by #163


Sync eng/common directory with azure-sdk-tools for PR 6518

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/6518  See eng/common workflow

Unrelated to this code change. windows2022 always seems to have issues.

/check-enforcer override


mutable & const correctness

@GlynLeine please make sure that your code correctly qualifies const & mutable
ecsregistry.cpp
In file included from ecs/ecsregistry.cpp:1:
In file included from ../core/ecs/ecsregistry.hpp:7:
In file included from ../core/ecs/component_container.hpp:5:
../core/containers/atomic_sparse_map.hpp:71:27: error: no matching constructor for initialization of 'async::readonly_guard'
                { async::readonly_guard lock(m_container_lock); return m_dense_value.cbegin(); }
                                        ^    ~~~~~~~~~~~~~~~~
../core/async/readonly_rw_spinlock.hpp:67:3: note: candidate constructor not viable: 1st argument ('const async::readonly_rw_spinlock') would lose const qualifier
                readonly_guard(readonly_rw_spinlock& lock) : lock(lock)
                ^
../core/async/readonly_rw_spinlock.hpp:96:3: note: candidate constructor not viable: no known conversion from 'const async::readonly_rw_spinlock' to 'const args::core::async::readonly_guard' for 1st argument
                readonly_guard(const readonly_guard&) = delete;
                ^

this is directly from develop/core
as you can see the right constructor is discared because it does not qualify const correctly, m_container_lock needs to be mutable in this context

I'll do it immediately when i get home, prolly 1 hour max from now.

i see you already fixed it


Is there any way to add icon before each list item?

Would to put an icon before each item list, wondering if it is achievable with this lib.

Hey, you can use the renderRow prop to pass in your own row component.
Here is an example:
    <GooglePlacesAutocomplete
      query={{
        key: GOOGLE_PLACES_API_KEY,
        language: 'en', // language of the results
        }}
        renderRow={results => (
         <>
          <Image source={require('./assets/red_place.png')} style={{ width: 15, height: 25 }} />
          <Text>{results.description}</Text>
        </>
        )}
      onPress={(data, details = null) => console.log(data)}
      onFail={error => alert(error)}
    />


When DAGCircuit.qasm() got replaced by QuantumCircuit.qasm() some features got lost

After  https://github.com/Qiskit/qiskit-terra/pull/1781, DAGCircuit does not support qasm method and it was replaced by the method in QuantumCircuit. However, many parameters were supported before (see: https://github.com/Qiskit/qiskit-terra/pull/1781/files#diff-d2039341ad623e4c82f0beeec0ad1f87L772) that are not supported now.
        Return a string containing QASM for this circuit.
        Args:
            qeflag (bool): if True, add a line to include "qelib1.inc"
                and only generate gate code for gates not in qelib1.
            eval_symbols (bool): if True, evaluate all symbolic
                expressions to their floating point representation.
            no_decls (bool): if True, only print the instructions.
            aliases (dict): if not None, aliases contains a dict mapping
                the current qubits in the circuit to new qubit names.
                We will deduce the register names and sizes from aliases.

Yeah but are those parameters needed? They were not used anywhere in the code.

https://github.com/Qiskit/qiskit-terra/issues/1747

Yeah I don't think we want to control qasm printing at that level. It should not be a smart function in my opinion. I did notice that one place where the aliases got used, but really no where else, and none of the other parameters were used either.

Related, other possible use in #875

I'm closing this as wont fix. Thanks!


CIP-0059 | Add "Valentine" HF

I find this table very useful both for myself and for pointing others to it.

thank you @amesgen! I made one small comment, but everything else is perfect!


SwiftPM Firestore: SSL symbol collision

The Swift Package Manager implementation of the Firestore BoringSSL dependency does not do symbol renaming like its CocoaPods implementation. This may cause potential symbol collision issues for apps that link another SSL implementation.
Please thumbs-up this issue to help us prioritize if it impacts your app.

For grpc-swift, see #7508 and https://github.com/apple/swift-nio-ssl/pull/269

Some additional detail notes from a conversation with @wilhuff:
Specifically there is still a potential symbol collision with OpenSSL.
Unlike the CocoaPods version of BoringSSL, the SPM version does not do symbol renaming.
For SPM, we'd likely need to do a source transformation to rename, since SPM does not support preprocessing like podspecs do.
Alternatively, we could switch the SPM version to depend on swift-nio-ssl instead but that would be inconsistent with the CocoaPods distribution.
Even more ideal would be for gRPC and gRPC-Swift to agree upon the same BoringSSL implementation and then Firebase use the same for both CocoaPods and SPM

Xcode 13.3 introduces build tool plugins, which might make it more feasible for the BoringSSL Package.swift to do a renaming similar to do what is done with CocoaPods. See https://developer.apple.com/documentation/xcode-release-notes/xcode-13_3-release-notes.
cc: @wu-hui @dennycd

We have duplicated symbols because of another project which uses another version of BoringSSL. It's needed to scope your version for your use cases.

Hello @paulb777
Is there any chance to assign a higher priority to this issue? We're currently in the process of migrating our codebase from cocoa pods to spm and we're currently experiencing this issue, just as described in this swift forums thread - the symbol collision is between openssl included by another dependency and boringssl from firebase.

Thanks for the upvotes. I've had conversations with the gRPC team about this and hopeful to get it on the roadmap for the first quarter of 2023

We're starting to look into this issue. But would it be possible for us to get example project with the above mentioned collision? So that we could use it to verify that our fix works. Thanks!
@paulb777 FYI :)

Xcode 13.3 introduces build tool plugins

We are still using Xcode 11.3 unfortunately. The upgrade to Monterey (with Xcode 13.4) is in-progress I however have no idea when it'll happen.

@sampajano @paulb777  do you have a fix?
Maybe you could provide a (unstable) branch which we could use together with swift package manager. Then we could give you some feedback :)

This was fixed in Firebase 10.8.0 when we fixed to a binary distribution built from the CocoaPods distribution with symbol renaming.

Works but now the dsym upload to crashlytics doesnt work anymore.
We have no crashlogs @paulb777


weird text problem and others

hi again so theres a problem where when i play freehl this weird text pops up on the screen and also there may be some missing textures cause i saw one while in the train, and also some sfx doesnt work like the train moving

if you're running fte on macOS or HellOS, you're likely running a pre-CSQC/SSQC 2023 rework

if you're running fte on macOS or HellOS, you're likely running a pre-CSQC/SSQC 2023 rework

can u elaborate idrk what csqc or the other thing means lol


[ENHANCEMENT] Optimize Horizontal rules

Change the thickness from 1px to 3px
Change the margin form 1rem to 2rem
Not change the color

Check https://66a7ca34.hugodoit.pages.dev/markdown-tests/#horizontal-rules for difference. There is not much difference because I find it is really ugly with a higher contrast color, so the color remains unchanged. The extra thickness and margin should make it look better than before.


Once the layer is created, the parent should be modificable

SC-TEI-45

Changing the parent if the layer already have entities created can produce some problems. We can allow the modification only for layers with no entities associated

This feature was already added - layers hierarchy can be changed, but it is only allowed if there are no entities created in order to avoid inconsistence in data


v3 error

I get the following error in console since v3:
using: nuxt3
Uncaught SyntaxError: The requested module '/_nuxt/node_modules/@dargmuesli/nuxt-cookie-control/dist/runtime/methods.mjs?v=f94e13d6' does not provide an export named 'getCookie' (at CookieControl.vue:167:1)

Thank you for the bug report! :pray: It would be great if you could recreate the issue using this new form. A minimal reproduction would allow me to help quick :raising_hand:

Closing due to inactivity. Can be reopened anytime.


"Action required: Greenkeeper could not be activated" impossible to execute

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github.

The repository in question is part of an organization, and the organization has whitelisted all repositories for greenkeeper. Therefore I cannot remove/add the repository -- and I'm a bit too scared to disable the whitelist just to try whether that triggers anything.
Note that the underlying issue is that greenkeeper found the new repository, and then started on it before the CI was in place.
(https://github.com/Collaborne/intl-chrome-i18n/issues/2)

Thanks Andreas, I’ll have a look today!

Hi @ankon, I’ve reset the single repository and I think things worked out this time, can you confirm?

@gr2m yes, this time things worked out, and the "Action required" issue was closed, and the the initial PR was submitted successfully.
In the grander scheme of things though: would it be "ok" if I temporarily enabled the whitelist in the settings, save, and then disable it again? We do have a couple of projects in this state actually :)

@ankon We're working on something that allows you to reset repos within the accounts app, right now it's only accessible to us :)
We don't recommend using the "enable all" approach, as this doesn't allow you a more fine grained control over which repos Greenkeeper should be enabled for and what repo is ready to use it (read: CI is ready to run, package.json exists).
In your case, if you disable the "enable all", we'll delete all our knowledge of your repos from our database. If you then add a new repo via the whitelist, it will run through the regular initial process (create initial branch -> wait for commit status from CI -> create initial PR).
If you have other repos that you need us to reset, don't hesitate to just post them here, for us it's just a command away :)

Thanks for the offer to press buttons for me :)
Here's another one:
https://github.com/Collaborne/eslint-config-collaborne/issues/1

done 👍

https://github.com/Collaborne/incremental-json-parser/issues/1 appeared before I had Travis enabled, branch is deleted.
/me is wondering whether it would work to just create a PR manually from the branch and/or just add the badge to the right place to enable things :)

Ok, I this isn't workable for us: every single new repository ends up with the 'Action required', and every time I either have to kill the ticket (non-OSS project, but we're not using greenkeeper.io with a paid subscription due to the pricing model), or delete the branch and ticket, link it to here (if I don't forget) and hope it eventually figures things out.
So, I've now enabled the whitelist, and will just go through all our OSS repos again to enable them when I have the time for that.

Even when I enable whitelist repos, I needed to add/remove my repo 2 times to make Greenkeeper to create a pull request. I merged the initial pull request 2 hours ago, but Greenkeeper is still disabled for my repo now. Could you please have a look at it? @gr2m
https://github.com/Tiendq/youtube-embed-video
Thanks,

@Tiendq I enabled it. If you encounter any more problems write a short mail to<EMAIL_ADDRESS>🌴 📫

@Realtin I just checked README file, it's enabled now. Thanks.

closing this in favour of https://github.com/greenkeeperio/greenkeeper/issues/355


[IMPROVEMENT] transfer backup CR ownership when IM is down

Is your improvement request related to a feature? Please describe
Discussion thread starts here.
Describe the solution you'd like
As discussed in the PR review session, we've reached a consensus to deal with the bad IM with ownership transfer.
Describe alternatives you've considered
https://github.com/longhorn/longhorn-manager/pull/1338#issuecomment-1141913378
Additional context
https://github.com/longhorn/longhorn/issues/3546

Close in favor of https://github.com/longhorn/longhorn/issues/4076.


Custom Configuration

With our current configuration it needs a bit of digging before someone who is not familiar with Vagrant is able to modify basic settings.
To make it easier to customize the configuration without having to understand how a Vagrantfile works, I would suggest to collect the following options in one place to make editing easier:

VM hostname
VM IP address
VM memory
Host directory that is mounted into /home/vagrant/code/Ghost

A short explanation what these values are used for would also help.
I see 2 options to make that work:

add variables with comments at the beginning of our Vagrantfile
add the option to use a separate config file (config.yaml) for these values

The values that are used in our current configuration seem to be sensible default values and should stay the same if the user doesn't change them manually.
Thoughts?

I would be in favour of using a separate config file. This would prevent the need to modify the Vagrantfile directly (which is under version control). I would say that the config.yml should be git ignored by default. The Vagrantfile will then source this in if it is present in the root directory. If a config.yml file is not present in the root directory, then one is generated automatically with the current sensible defaults.

Yeah, adding the config to the Vagrantfile is probably not the best idea when it comes to version control :+1:.
Maybe have a config.yml.example that is cloned if no config.yml exists?