Error, need to add one of ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION to AndroidManifest.xml

I'm getting this error:
"Missing location permission in AndroidManifest.xml. You need to add one of ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION. See readme for details."

However, I already added ACCESS_COARSE_LOCATION:
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="com.example.ranky">

    <!-- The INTERNET permission is required for development. Specifically,
         flutter needs it to communicate with the running application
         to allow setting breakpoints, to provide hot reload, etc.
    -->
    <uses-permission android:name="android.permission.INTERNET"/>

    <!-- The location permission is required for showing close contests to
         the user.
    -->
    <uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

...

I'm having the exact same issue. Any leads?


Make sure audio codec chip can not mess up other chips

Right now the serial data out is messing up the auto boot load mode of other things.

One possibility is to have and gate on output of codec with a enable line default low and controlled by UI cpu

@BrettRegnier - Can you provide more detail about what is going wrong right now

The pins that the wm8960 ADC is connect to can also be configured as USART3_RX, which when in bootloader mode all of the possible USART pins are configured into USART mode, and select the first configured USART bus as the communication line. Since the audio chip is always sending data unless it is reset then the bootloader will attempt to communicate using USART3 instead of USART1.
So, all we need to do is change which pin our i2s is connect to by swapping PC11 to PB4 (I2S_ADCDAT)

Did this happen on 10.1 ?

Yes! This is fixed in 10.1


Update node versions in Github actions config

Test on newer Node.js versions that support our updated dev dependencies
Update lint config for improved consistency between local dev and CI environments


Fix and update prettier config

This PR includes 2 fixes for prettier in pre-commit:

Bump prettier/plugin-xml version for v13
The plugin was not ignoring prettier-ignore blocks in xml files.
This feature was added in version 0.9.0: https://github.com/prettier/plugin-xml/blob/master/CHANGELOG.md#added-1
In the latest version (0.12.0), this is also fixed and no major changes in formatting are introduced.
See OCA/rma@d1b73c3
(This applies the same version that is already defined for v14 branches https://github.com/OCA/oca-addons-repo-template/blob/master/.pre-commit-config.yaml.jinja#L13)
Add missing prettier-xml dependency
After getting install errors like https://github.com/OCA/rma/runs/1733281591?check_suite_focus=true#step:4:104
looks like the prettier xml plugin depends on xml-tools/parser (see https://github.com/prettier/plugin-xml/blob/master/package.json#L22)
Adding that dependency explicitly fixes the issue.
See OCA/rma@a4b6ad8

Check the pull request in the rma repo for details.
@Tecnativa
TT27062
ping @Yajo

Closing this as the issue ended up being solved in a different way: the usage of xmlWhitespaceSensitivity: "strict" should fix most white space issues in .xml files, so no need to upgrade here.

Closing this as the issue ended up being solved in a different way: the usage of xmlWhitespaceSensitivity: "strict" should fix most white space issues in .xml files, so no need to upgrade here.


Change android and ios logo

Summary by CodeRabbit

New Features

Streamlined app icon assets for iOS, focusing on specific expected sizes for iPhone.
Simplified filenames for icons, enhancing organization and clarity.

Bug Fixes

Removed outdated icon sizes and scales, reducing potential confusion.

Refactor

Overhauled the structure of the icon asset definitions for improved efficiency.

lgtm @mdmohsin7 🚀


Merge MiniMessage into Adventure entry

MiniMessage is no longer a separate repository and has been merged into the main Adventure repository.
This should be reflected within the README.md

MiniMessage is no longer a separate repository and has been merged into the main Adventure repository.
This should be reflected within the README.md

@Andre601 https://github.com/LiteDevelopers/awesome-minecraft/pull/17
If you have any suggestions, feel free to write ^^


GitHub Actions

no more travis!

I want to make sure the build is green before we review, but currently, the build isn't running 🤔


hello word

Challenge Say Hello to HTML Elements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

<Hello word>Hello word</Hello word>

@ahmathamid
Thanks for reporting this. But your code is incorrect.
GitHub Issues are for reporting bugs on the website only.
Please use the Help chat room for getting challenge related help.
Happy Coding.


Coc-prettier doesn't recognize vue filetype

Auto formatting works with javascript and php but not vue.
I tried manually setting filetype:
:set filetype=vue
Any ideas why ?

It magically worked!
I'm not sure if it's because I added coc-vetur  plugin or the existence of eslint-plugin-vue in the project
anyway... leaving this here if it helps:
{
  "coc.preferences.formatOnType": true,
  "coc.preferences.formatOnSaveFiletypes": ["javascript", "php", "vue"],
  "prettier.eslintIntegration": true,
  "vetur.format.defaultFormatter.html": "prettier",
  "vetur.format.defaultFormatter.css": "prettier",
  "vetur.format.defaultFormatter.js": "prettier-eslint"
}

It's probably working because you have "pretier.eslintIntegration": true
However, the problem is that this setting is deprecated by Prettier (https://github.com/prettier/prettier-vscode/issues/999) and it also throws an error in typescript (https://github.com/neoclide/coc-prettier/issues/62)

This appears to be because of this:
https://github.com/neoclide/coc-prettier#prettierdisablelanguages-default-vue
I wonder why Vue was set at the default?

It's copied from prettier-vscode.


Django 1.9 support

Just took 1.9b1 for a spin, and immediately get this trying to start my app using SortedManyToManyField
File ".../sortedm2m/fields.py", line 8, in <module>
    from django.db.models.fields.related import add_lazy_relation, create_many_related_manager

Looks like create_many_related_manager has been removed, but I can't find explicit reference to this in the release notes.

create_many_related_manager was moved to django/db/models/fields/related_descriptors.py in https://github.com/django/django/commit/005c9fc45f99d03344fa9fae3dd984c2ab87f1ea

This fix https://github.com/shvechikov/django-sortedm2m/commit/8dff963483025aa9db08bd7b8f5ed53638406756 seems to work for me. Pheraphs you could cherry-pick it?

We already should have Django 1.9 in master with the merge of #65. @nemesisdesign is master working for you with Django 1.9?

@gregmuellegger sorry for not answering.. i'm drowning in github notifications here and I miss the good ones :-1:
Thanks for releasing Django 1.9 support :+1:


Can´t Forward to two grpc service using Yarp

Describe the bug
I created two grpc services in two different projects in asp.net core and one project as my gateaway using yarp.proxy, in addition the two projects contain each 1 grpc service name greeter... Now cannot forward request to each one because I cannot figure out how to configure yarp configuration for this case
``// The request message containing the user's name.
message HelloRequest {
string name = 1;
}
// The response message containing the greetings.
message HelloReply {
string message = 1;
}
Grpc service 2
syntax = "proto3";
option csharp_namespace = "GrpcService2";
package greet;
// The greeting service definition.
service Greeter {
// Sends a greeting
rpc SayHello (HelloRequest) returns (HelloReply);
}
// The request message containing the user's name.
message HelloRequest {
string name = 1;
}
// The response message containing the greetings.
message HelloReply {
string message = 1;
}
he´s how i´m calling the services
var channel1 = GrpcChannel.ForAddress("https://localhost:8000/greeter1/");
var client1 = new GrpcService1.Greeter.GreeterClient(channel1);
var request1 = new GrpcService1.HelloRequest { Name = "Jose Felix from service 1" };
var response1 = client1.SayHello(request1);
Console.WriteLine(response1.Message);
var channel2 = GrpcChannel.ForAddress("https://localhost:8000/service2");
var client2 = new GrpcService2.Greeter.GreeterClient(channel2);
var request2 = new GrpcService2.HelloRequest { Name = "Jose Felix from service 2" };
var response2 = client2.SayHello(request2);
Console.WriteLine(response2.Message);
To Reproduce

Further technical details

Yarp.proxy version 2.0.0
-Windows

{   "Logging": {     "LogLevel": {       "Default": "Information",       "Microsoft": "Warning",       "Microsoft.Hosting.Lifetime": "Information"     }   },   "AllowedHosts": "*",   "ReverseProxy": {     "Routes": {       "grpcservice1": {         "ClusterId": "grpcservice1",         "Match": {           "Path": "/greeter/{**catch-all}"         },         "Transforms": [           { "PathPattern": "/Greeter/{**catch-all}" }         ]       },       "grpcservice2": {         "ClusterId": "grpcservice2",         "Match": {           "Path": "service2/{**catch-all}"         },         "Transforms": [           { "PathPattern": "{**catch-all}" }         ]       }     },     "Clusters": {       "grpcservice1": {         "HttpRequest": {           "Version": "2",           "VersionPolicy": "RequestVersionExact"         },         "Destinations": {           "destination1": {             "Address": "https://localhost:8001"           }         }       },       "grpcservice2": {         "HttpRequest": {           "Version": "2",           "VersionPolicy": "RequestVersionExact"         },         "Destinations": {           "destination1": {             "Address": "https://localhost:8002"           }         }       }     }   } }

this the configuration i have tried so far but without success
{   "Logging": {     "LogLevel": {       "Default": "Information",       "Microsoft": "Warning",       "Microsoft.Hosting.Lifetime": "Information"     }   },   "AllowedHosts": "*",   "ReverseProxy": {     "Routes": {       "grpcservice1": {         "ClusterId": "grpcservice1",         "Match": {           "Path": "/greeter/{**catch-all}"         },         "Transforms": [           { "PathPattern": "/Greeter/{**catch-all}" }         ]       },       "grpcservice2": {         "ClusterId": "grpcservice2",         "Match": {           "Path": "service2/{**catch-all}"         },         "Transforms": [           { "PathPattern": "{**catch-all}" }         ]       }     },     "Clusters": {       "grpcservice1": {         "HttpRequest": {           "Version": "2",           "VersionPolicy": "RequestVersionExact"         },         "Destinations": {           "destination1": {             "Address": "https://localhost:8001"           }         }       },       "grpcservice2": {         "HttpRequest": {           "Version": "2",           "VersionPolicy": "RequestVersionExact"         },         "Destinations": {           "destination1": {             "Address": "https://localhost:8002"           }         }       }     }   } }

The main problem is that the service has the same name

Try this, I made some minor tweaks to your Match/Path fields to match your requests above.
{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft": "Warning",
      "Microsoft.Hosting.Lifetime": "Information"
    }
  },
  "AllowedHosts": "*",
  "ReverseProxy": {
    "Routes": {
      "grpcservice1": {
        "ClusterId": "grpcservice1",
        "Match": {
          "Path": "/greeter1/{**catch-all}"
        },
        "Transforms": [
          { "PathPattern": "/Greeter/{**catch-all}" }
        ]
      },
      "grpcservice2": {
        "ClusterId": "grpcservice2",
        "Match": {
          "Path": "/service2"
        },
        "Transforms": [
          { "PathPattern": "/" }
        ]
      }
    },
    "Clusters": {
      "grpcservice1": {
        "HttpRequest": {
          "Version": "2",
          "VersionPolicy": "RequestVersionExact"
        },
        "Destinations": {
          "destination1": {
            "Address": "https://localhost:8001"
          }
        }
      },
      "grpcservice2": {
        "HttpRequest": {
          "Version": "2",
          "VersionPolicy": "RequestVersionExact"
        },
        "Destinations": {
          "destination1": {
            "Address": "https://localhost:8002"
          }
        }
      }
    }
  }
}

I thanks for replying. I tried your suggestion but it didn't work. it is giving an error
Grpc.Core.RpcException   HResult=0x80131500   Message=Status(StatusCode="Unimplemented", Detail="Bad gRPC response. HTTP status code: 404")   Source=Grpc.Net.Client   StackTrace:    at Grpc.Net.Client.Internal.HttpClientCallInvoker.BlockingUnaryCall[TRequest,TResponse](Method2 method, String host, CallOptions options, TRequest request)
at Grpc.Core.Interceptors.InterceptingCallInvoker.b__3_0[TRequest,TResponse](TRequest req, ClientInterceptorContext2 ctx)    at Grpc.Core.ClientBase.ClientBaseConfiguration.ClientBaseConfigurationInterceptor.BlockingUnaryCall[TRequest,TResponse](TRequest request, ClientInterceptorContext2 context, BlockingUnaryCallContinuation2 continuation)    at Grpc.Core.Interceptors.InterceptingCallInvoker.BlockingUnaryCall[TRequest,TResponse](Method2 method, String host, CallOptions options, TRequest request)
at GrpcService1.Greeter.GreeterClient.SayHello(HelloRequest request, CallOptions options) in D:\GitHub\School\src\Services\Presentation\Wpf\YarpGrpcApp\GrpcClient\obj\Debug\net8.0\Service1\GreetGrpc.cs:line 119
at GrpcService1.Greeter.GreeterClient.SayHello(HelloRequest request, Metadata headers, Nullable1 deadline, CancellationToken cancellationToken) in D:\GitHub\School\src\Services\Presentation\Wpf\YarpGrpcApp\GrpcClient\obj\Debug\net8.0\Service1\GreetGrpc.cs:line 108    at Program.<Main>$(String[] args) in D:\GitHub\School\src\Services\Presentation\Wpf\YarpGrpcApp\GrpcClient\Program.cs:line 8

What was the request path for that one?

I made up a github repo and added my initial project so can have a better idea... help me...
https://github.com/jose8789/YarpGrpcTest.git

Your repo is empty.

Hi, I just saw that it is really empty. Sorry, but now try  this one
https://github.com/jose8789/testapp.git


fix: delete in binding.py now same as get/post

Currently you can not pass custom headers to delete, as they are overwritten with default self._auth_headers. Replaced that with all_headers as in get and put.

This change is required to leverage .delete using splunklib. Current work is blocked by this, as deletion is not possible without header authentication. Please have a look at this, or any other way we can expedite this.

Saw in another PR wanting to solve the same thing, to add a test case. Where would you suggest I do that? In which testing file is this functionality tested usually?


[iOS] Strip x86 libcore binaries on "archive"

x86_64 libcore binaries needed for the iPhone simulator where embedded when doing an archive to deploy on App Store, which was getting promptly rejected unless removed manually.
This should fix that ⓒ
Before

After

Type
Bugfix
Context

https://ledgerhq.atlassian.net/browse/LL-916
#263

Parts of the app affected / Test plan

Archive
Publish
???
Profit

w'll take this. building the app will see if there are any glitch but looks good to me.


First-class Elasticache support

Summary
Currently, users must use the custom connection target approach to connect to Elasticache instances. This involves manually setting up connectivity (at init time) and providing Basti with the target's IP and port (at connect time). Let's implement first-class support for Elasticache, just like for RDS. This includes:

Detecting Elasticache instances in the user's AWS account and presenting them as options in the connect and init commands
Elasticache instance initialization
Elasticache instance connection
Elasticache-related resources cleanup

does this issue have an ETA? I can start working on it now if relevant

@dollev36, I appreciate your willingness to contribute to the project 🙏
As far as I know, @yvashkiv has already started working on the implementation.
If you need to connect to an ElastiCache instance now, you can use the custom target approach. If you're interested in contributing to the project, I would appreciate it if you choose any other issue or create a new one ❤

@yvashkiv is there an ETA?

@dollev36 Probably it will be done by the end of this week.

Hi @dollev36 . Further research showed that it's hard to solve the problem of local connection for multi-node Redis or Memcached clusters as in this case, the client needs a connection to each of the nodes in the cluster (and it's only part of the problem). For now, I'll implement only Redis (Cluster Mode Disabled) and Memcached single-node clusters support.
Does this satisfy your use case?

Hey @dollev36 👋
Looks like it takes more time than expected to implement the enhancement. I just want to make sure your use case is covered with the custom target connection mode:

Initialize your Basti with basti init, select a custom target and your cluster's VPC
Allow connection from the bastion instance to your Elasticache cluster through the cluster's security group
Use custom target connection mode to connect to your target:basti connect --custom-target-vpc <you-cluster-vpc> \
  --custom-target-host <your-cluster-primary-endpoint> \
  --custom-target-port <your-cluster-port> \
  --local-port <local-port>

Hi @yvashkiv it sound like a good start but sadly it dosn't solve my case.
can you elaborate on the difficulties you are facing? I can continue from this point and implement the CME

Hey @BohdanPetryshyn , first, your project is super cool. You provide E2E experience which can really help AWS users. With regards to how I think it should work, I don't think users will want to use the --custom* command line but being able to choose the Redis node from the list of nodes they have access to. Similar to what you already do today with RDS.

Regarding sharded clusters.
Both Redis and Memcached leave request routing to the client. This means that the client has to maintain a connection to all the nodes in the cluster (at least all the primary nodes).
Moreover, the client uses the IP:port addresses received from the cluster to communicate with the nodes and follow possible redirects. When connecting through Basti (or any other port forwarding tool like SSH tunneling), the client should use different addresses - the ones exposed by Basti on the localhost. For example, the cluster has three primary nodes:

<IP_ADDRESS>:6379
<IP_ADDRESS>:6379
<IP_ADDRESS>:6379

Using Basti the actual addresses will be something like this:

<IP_ADDRESS>:6370
<IP_ADDRESS>:6371
<IP_ADDRESS>:6372

The client has to have a way to override the addresses. I managed to connect to a shared Redis cluster using the ioredis client for NodeJS and its Nat Mapping feature. However, this is not always possible. For example, the redis-cli client doesn't provide such functionality from what I know.
Possible solutions off the top of my head:

Implement connection to all the primary nodes but leave the rest to the user. Basti will make it possible to connect to shared clusters, however, this won't be the easiest thing to do in some cases.
Integrate some Redis/Memcached proxies like this one that would encapsulate routing and expose a single entry point. This might be too hard to implement and maintain especially considering that we need two proxies for Redis and Memcached.

I would be really glad to hear your thoughts on this!
cc @dollev36 @tomer-w @yvashkiv

I fully agree that if the goal is to allow cluster mode enabled clients to connect using basti than a proxy like mechanism is needed. For me, it was not the first goal of this support as I understand the complexity and don't have easy solution. What I do have in mind is administration support which will allow the customer to use Redis-cli type of tools to monitor and configure the cluster and for this reason it is enough to connect to a single node.
Will be glad if later we will come up with novel approach for the cluster connectivity issue but I don't see it as a blocker to start getting value of the Basti tool for ElastiCache.

Sounds good to me @tomer-w!
So the first iteration of Elasticache support could be:

For Redis Cluster Mode Disabled (CMD) - connect to the primary endpoint
For Redis CME - connect to the configuration endpoint
For Memcached - always connect to the configuration endpoint

The interactive mode CLI should be implemented in such a way as to make it clear to the user that only the configuration endpoint is available for shared clusters

I think that as the main usage is going to be configuration and monitoring you will want to be able to choose any node (primary or replica) for both CMD and CME.
It should be very similar to the ElastiCache console which you see list of all nodes (with some designation if this is primary or replica and which shard) and allow the user to choose the one he wants to work with.
This will be the same for both CME and CMD.
So, in the basti init phase you just choose a cluster and in the basti connect phase you can choose the specific node.

Thank you for your input, @tomer-w! I'll get back with some UX prototypes soon!

I would suggest an interactive mode layout like this:

The user can select a whole cluster or a particular node
If a Redis CME cluster is selected, the configuration endpoint is used
If a Redis CMD cluster is selected, the primary endpoint is used
If a Memcached cluster is selected, the configuration endpoint is used
The same approach will be implemented for RDS clusters and instances in the future

Hi, @dollev36 @tomer-w  @BohdanPetryshyn !
Sorry for the delay. I'm going to finish the implementation till the end of this week - beginning of the next week.

The issue has grown in scope significantly since @yvashkiv started working on it. We agreed with Yura that I'll finish the implementation instead.
Elasticache support should be released next week.

Hi Bohdan, thank you for taking it over from Yura and unblocking him. If you are busy, and no real work is yet done, maybe Dolev can take it, as he is available. Dolev and myself are working in AWS Elasticache service, and we think there is a real value we can provide to many AWS customers. So we are ready to take it over and contribute to your open-source project.

Hi @vovagring and @dollev36 👋
It would be great if you could handle this! As you guessed, there was not much progress made so far, so you can start from scratch.
This time, I'd suggest agreeing on an ETA from the beginning 😅
I would be happy to give you a quick intro to the project and share some thoughts on the future implementation!

Hi @BohdanPetryshyn ,
I'll be happy to handle this , and of course I'd love to have a chat with you for intro.

Could you please, message me on LinkedIn so that we can agree on the time?
https://www.linkedin.com/in/bpetryshyn/

@BohdanPetryshyn I'm sorry for the delay, iv'e missed the notification.
added you on LinkedIn

@BohdanPetryshyn ,
I appologize for the delay - I've started working on it, but due to personnal issues delaying me it will take about two to three weeks.

@dollev36, thanks for letting us know!

Hello, @dollev36 👋
I hope you're doing well! I recently gave this issue a higher priority as I think this functionality could be really helpful to many people. Please, let me know if you need any help! It would also be great if you could give an update on your progress and estimate.

Hi @BohdanPetryshyn
I'm doing all right, sorry for the delay, I estimate I will have a pr by the end of next week.

Sounds good, thank you for your reply! You're welcome to open a draft PR as soon as it makes sense to start receiving some feedback.

@dollev36 , @BohdanPetryshyn , thanks for getting this in. I am sure ElastiCache customers will benefit from this change. When are you going to release it?

Hi @tomer-w! I plan to add some docs and release the Redis support tomorrow. @dollev36 is going to start working on Memcached support soon.
Are there any channels available at AWS to let the ElastiCache customers know about the new solution?

This is what I had in mind as well. I think we can help with spreading the existence of this tool to our customers. This is why I want it to be released so I can start sharing it internally and discuss what we can do externally.

Cool! I'll let you know when the Redis support is released 🤝

Hey @tomer-w 👋
Elasticache Redis support was released with<EMAIL_ADDRESS>

With the release of<EMAIL_ADDRESS>we now support Elasticache Memcached natively 🥳
I'm going to add the CLI options and config file reference to README.md to improve Elasticache support visibility since RDS is used in all the usage examples.
Thank you for your contribution, @dollev36, @tomer-w and @yvashkiv 🤝
@tomer-w, I'd be happy to hear any feedback or feature requests from your internal discussion!

The reference doc was created and some minor README improvements were added in<EMAIL_ADDRESS>

At this point, I consider first-class Elasticache support fully implemented.
Please, feel free to open new issues for any bugs or feature requests if needed! Your feedback is highly appreciated!

Hi @tomer-w! I hope you're doing well!
Do you still plan on implementing this? Is there anything I can help with?

I think we can help with spreading the existence of this tool to our customers. This is why I want it to be released so I can start sharing it internally and discuss what we can do externally.

Hi @BohdanPetryshyn, I left Amazon, so I am no longer in the details of this. Please try @vovagring and @dollev36.


feat: add start/stop charge and charge limits to Hyundai USA

Hrm, maybe I shouldn't have bumped the version. Up to you.

Correct just do the api.  Version of the integration is managed by a ci in GitHub.

Reverted that version change, I did change the readme so that it reflects the change, however it looks like my editor replaced the html code with the actual symbols, so I can remove the readme change if you like.


Put token into log message if it exists when logging invalid metric type

Now with half the token and a hash for ties.


cannot access collection named "media"

Hi guys!
it seems a collection with "media" in its name is not accessible!
documentdb/lib/request.js line 53 is suspicious :)
var isMedia = ( requestOptions.path.indexOf("media") > -1 );
Bonus question: how do I name my media collections?

for the sake of my (and maybe someone else) sanity, just use letter case ... e.g.: "Media"

fixed in 1.12.2


invalid escape sequences

Your code presents some invalid escape sequences that are considered errors from python 11. Please check: https://docs.astral.sh/ruff/rules/invalid-escape-sequence/
A clear and concise description of the bug.
Steps To Reproduce
With CI workflow for analyzing the code, errors like:
E   SyntaxError: invalid escape sequence '?'
rises in the comment lines
Expected Behavior
A clear and concise description of what you expected to happen.
Environment

for all the OS
for python in range 3.9 to 3.12

I follow this repo too, I suspect you've had the same idea I did ;-)

@DeborahVolpe, could you please clarify where exactly and under what conditions are you seeing this error.
Invalid escape sequences currently (in Python 3.12), raise SyntaxWarning, not SyntaxError.

Thank you for your response. To be precise the first error occurring in this our CI test is the following:
"D:\a\mqt-qao\mqt-qao.nox\tests-3-11\Lib\site-packages\dwave\samplers\greedy\sampler.py", line 32 E       """Steepest descent sampler for binary quadratic models. E       ^^^ E   SyntaxError: invalid escape sequence '_'
Refferring to https://github.com/dwavesystems/dwave-samplers/blob/6b336abd0402519ce8de95952665b8f99cbd3e10/dwave/samplers/greedy/sampler.py#L52.
It is the _ character after the wikipedia link in the comment line. I think that it is not the only point in which a not-allowed character is employed.

@DeborahVolpe, that's a known issue we're fixing across our packages (converting such strings to raw strings), but what's not clear is why is this raised as SyntaxError in your setup, because this is only SyntaxWarning in Python 3.12+ (and only DeprecationWarning in Python 3.11). At some point, but not yet known when - perhaps as soon as Python 3.13, it will be converted to SyntaxError that you are seeing.
So I'm guessing you have a nox/test setup more stricter than Python default -- and converting warnings to errors.


Constrain AFIO leads to unsafe code when setting up EXTI

I'm working on a little hobby project on a blue pill with rtfm and this lib. I just added some PWM to the project which required calling constrain on AFIO.  A few lines after constraining, I want to do something like this:
p.device.AFIO.exticr3.write(|w| unsafe { w.exti11().bits(0x01) });

To enable EXTI11 on port B. Constrained AFIO does not have EXTICR3 available, so I tried it this way. However, AFIO has been moved so this line doesn't work and instead I need to do the unsafe { &*AFIO::ptr() } bit to get access to it.
I'm striving to minimize unsafe code. Is this a thing that will eventually be implemented on afio::Parts? Or is there a better way I can be doing this?

@freiguy1 This can be easily solved by adding exticr3 (and similar registers as well) to src/afio.rs like it is done with mapr in there. Would you like to take a stab at it and submit a PR?

Yes, that could be a great way to get my fifth Hacktoberfest pr as well :) I'll work on it

@therealprof Question:
MAPR struct looks like this currently:
pub struct MAPR {
    _0: (),
}

I'm confused why it needs the _0 field. It seems to build like this: pub struct MAPR; Maybe there's an inconspicuous reason why it's required.

That's to have a private field to forbid construction by the user.

@freiguy1 What @TeXitoi said.

PR is available: #113


Pub: 10.22,11.17,12.12,13.8, and more. [release]

postgres releases 10.22 11.17 12.12 13.8 14.5 for CVE-2022-2625 vulnerability.

Running this through


Indentation of "chained" calls

A common pattern for formatting "chained" calls is to place each new operation indented on a new line, for example:
router.route('/tables/:tableName/:id')
    .get(function (req, res, next) {
        return tables.read(req.params.tableName, req.query)
            .then(function (results) {
                res.send(JSON.stringify(results));
                next();
            });
    })
    .post(function (req, res, next) {
        // do some stuff
    })

However, NTVS formats the code without the additional indentation:
router.route('/tables/:tableName/:id')
    .get(function (req, res, next) {
    return tables.read(req.params.tableName, req.query)
            .then(function (results) {
        res.send(JSON.stringify(results));
        next();
    });
})
    .post(function (req, res, next) {
        // do some stuff
});

Great idea! I'll very optimistically assign it to the May milestone because I think there's a way to make this change without being too disruptive, and it you're right that this is super helpful from a code readability standpoint. Otherwise we'll take a look next time we're looking into formatter changes (we like to get those in early on in any release because the formatter is one of those areas that tends to break a bunch of other stuff when we touch it and we like having stabilization time.)

Fixed in NTVS 1.2 Alpha with ES6 Intellisense preview


Adding ToastController button handler

[x] 2.x
[x] feature request
Other information:
Hi everyone,
I was going to add button to toast for recovery options. I saw that there is an option to add button, however it calls dismiss function. It would be nice to have some different function to handle click event of toast button.
I don't know If I'm clear, here is use case; There is a button which is sending message. User mistakenly clicked button, there is a toast message which is saying your message successfully sent, and there would be cancel button.
Current behavior:
ToastController: Calling onDidDismiss when duration ends or button(showCloseButton:true) click

Expected behavior:
ToastController: Having different handler than dismiss to button.

I think something like this would be great!
Related code:
presentToast() {
  let toast = this.toastCtrl.create({
    message: 'User was added successfully',
    duration: 3000,
    position: 'top'
  });

  toast.onDidDismiss(() => {
    console.log('Dismissed toast');
  });

  toast.onButtonClick(() => {
    console.log('Button click');
  });

  toast.present();
}

With the current implementation we are differentiating as below
this._toast.onDidDismiss((data, role) => {
      console.log(data);
      this._onToastClose(role);
    });

if role == 'close' then the user clicked on button, else its dismiss based on timer.

Hello all! While this is an awesome feature request it is not something that we plan on doing anytime soon. Because of this I am going to move this to our internal feature tracking repo for now as it is just "collecting dust" here. Once we decide to implement this I will move it back. Thanks everyone for using Ionic!

This issue was moved to driftyco/ionic-feature-requests#84


A set of new functionality in RecoGym

This pull request contains a set of new notebooks and a lot of new functionality (please, follow the comments provided for each commit).
Feel free to exclude some notebooks which you think need some extra work.

@ihtiihti
evolute_agent.py -> evaluate_agent.py
and def evolute_agent( -> similar

I have fixes spelling errors


ML Extension - PREDICT sql script formatted for readability

Is your feature request related to a problem? Please describe.
The PREDICT function is not preformatted, making it hard to read.
Describe the solution or feature you'd like
SQL Keywords should be in capital.
Indentation to make it easier to read.
Here's an example:
expected_predict_format.txt
Describe alternatives you've considered
Formatting on my own. Or perhaps use one of sql formatter extension.
Additional context
n/a

@MsSQLGirl does this look correct?
DECLARE @model VARBINARY(max) = (
SELECT model
FROM [onnx].[dbo].[models3]
WHERE model_id = 3
);
WITH predict_input
AS (
SELECT TOP 1000
CAST([pi].[CRIM] AS FLOAT) AS CRIM,
CAST([pi].[ZN] AS FLOAT) AS ZN,
CAST([pi].[INDUS] AS FLOAT) AS INDUS,
CAST([pi].[CHAS] AS FLOAT) AS CHAS,
CAST([pi].[NOX] AS FLOAT) AS NOX,
CAST([pi].[RM] AS FLOAT) AS RM,
CAST([pi].[AGE] AS FLOAT) AS AGE,
CAST([pi].[DIS] AS FLOAT) AS DIS,
CAST([pi].[RAD] AS FLOAT) AS RAD,
CAST([pi].[TAX] AS FLOAT) AS TAX,
CAST([pi].[PTRATIO] AS FLOAT) AS PTRATIO,
CAST([pi].[B] AS FLOAT) AS B,
CAST([pi].[LSTAT] AS FLOAT) AS LSTAT
FROM [onnx].[dbo].[features] AS pi
)
SELECT
[predict_input].[CRIM],
[predict_input].[ZN],
[predict_input].[INDUS],
[predict_input].[CHAS],
[predict_input].[NOX],
[predict_input].[RM],
[predict_input].[AGE],
[predict_input].[DIS],
[predict_input].[RAD],
[predict_input].[TAX],
[predict_input].[PTRATIO],
[predict_input].[B],
[predict_input].[LSTAT],
[p].[variable1]
FROM PREDICT(MODEL = @model, DATA = predict_input, runtime=onnx)
WITH (
variable1 REAL
) AS p

Thanks @llali :)


Can't call a procedure with postgres_execute after retrieving an attached table in a transaction

What happens?
In a transaction, when calling a procedure (via postgres_execute) after retrieving from a table there is the following error:
duckdb.duckdb.Error: Failed to execute query "CALL test()": another command is already in progress

To Reproduce
Create procedure and table on postgres instance (db: postgresscanner):
create table log ( comment text );
create procedure test() language sql as $$ SELECT 'hello'; $$;

Launch the following python script:
import duckdb
con = duckdb.connect(database=':memory:')
tr = con.begin()
tr.execute("""ATTACH 'dbname=postgresscanner' AS s (TYPE postgres);""")
tr.sql("""SELECT * FROM s.public.log;""").fetchall()
tr.execute("CALL postgres_execute('s', 'CALL test()')")
tr.commit()

OS:
Archlinux
PostgreSQL Version:
16.2
DuckDB Version:
10.2
DuckDB Client:
Python
Full Name:
Christopher Meier
Affiliation:
HEIG-VD
Have you tried this on the latest main branch?

[ ] I agree

Have you tried the steps to reproduce? Do they include all relevant data and configuration? Does the issue you report still appear there?

[X] I agree

After further tests, any call to postgres_execute after a select in a transaction throws the same error:
import duckdb
con = duckdb.connect(database=':memory:', read_only=False)
tr = con.begin()
tr.execute("""ATTACH 'dbname=postgresscanner' AS s (TYPE postgres);""")
tr.sql("""SELECT * FROM s.public.log;""").fetchall()
tr.execute("CALL postgres_execute('s', 'SELECT 1;')")
# tr.execute("CALL postgres_execute('s', 'CALL test()')")
# tr.execute("CALL postgres_execute('s', 'CREATE TABLE log2(id INT)')")
tr.commit()

Throws duckdb.duckdb.Error: Failed to execute query "SELECT 1;": another command is already in progress

Thanks for the report! Could you try running SET pg_connection_cache  = false to see if that fixes the issue?

Same issue if I add
con = duckdb.connect(database=':memory:')
con.execute("""SET pg_connection_cache  = false""")

I am also seeing the another command is already in progress when trying to use transactions.
Use case: I have an attached postgres database with a queue table, I have multiple workers running at once reading/writing/updating/deleting from the queue. I would like to interface directly between postgres and duckdb without having to pop out to Python which is executing the duckdb commands.
My postgres table has been created with:
CREATE TABLE IF NOT EXISTS queues.entity_queue (
    id SERIAL PRIMARY KEY,
    entity_type TEXT NOT NULL,
    entity_id TEXT NOT NULL,
    processing BOOLEAN DEFAULT FALSE NOT NULL,
    locked_until TIMESTAMP WITH TIME ZONE DEFAULT NULL,
    enqueued_at TIMESTAMP WITH TIME ZONE DEFAULT CURRENT_TIMESTAMP
);

I attach the remote postgres instance with ATTACH as warehouse.
My overall query flow looks like:
USE warehouse;
BEGIN;

Open a transaction on the attached postgres database
        SELECT
            *
        FROM POSTGRES_QUERY('warehouse', $$
            SELECT
                DISTINCT entity_id
            FROM
                queues.entity_queue
            WHERE
                entity_type = '{entity_type}'
                AND (
                    (processing = FALSE AND ((locked_until < CURRENT_TIMESTAMP) OR locked_until IS NULL))
                    OR (processing = TRUE AND locked_until < CURRENT_TIMESTAMP)
                )
            LIMIT {num_entities}
            FOR UPDATE
        $$)

Fetch num_entities of an entity_type from the queue and mark with FOR UPDATE. We will pull out the entity_ids into a python list of strs for use in the next query
CALL POSTGRES_EXECUTE('warehouse', $$
    UPDATE queues.entity_queue
    SET
        processing = TRUE,
        locked_until = NOW() + INTERVAL '2 minutes'
    WHERE
        entity_id in ({','.join(queue_entity_ids)})
$$)

Use POSTGRES_EXECUTE to execute the command and get another command is already in progress errors with or without setting pg_connection_cache  = false. Attempting to do the update not within a POSTGRES_ function with or without pg_experimental_filter_pushdown set to True leads to the whole table attempting to be copied to duckdb afaict?
UPDATE warehouse.queues.entity_queue
    SET
        processing = TRUE,
        locked_until = NOW() + INTERVAL '2 minutes'
    WHERE
        entity_id in ({','.join(queue_entity_ids)})

COPY (SELECT "id", ctid FROM "queues"."entity_queue" WHERE ctid BETWEEN '(0,0)'::tid AND '(4294967295,0)'::tid) TO STDOUT (FORMAT binary);

I would be happy to hear I am approaching this the incorrect way, but the behavior seems like it should be supported/work

This should now be fixed in https://github.com/duckdb/postgres_scanner/pull/258 - essentially there is some odd internal state in libpq that is not entirely clear to me that leads to this error message - switching from PQsendQuery to PQexec fixes the issue.


Follow up feedback from new integration docs

As a follow up from https://github.com/dotnet/docs-aspire/pull/1648 there are a few items we should change on https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/integrations-overview page:

[x] Move "Available integrations" below "Cloud Native features" - Also the cloud native features section apply to the client integrations, that should be called out.

[x] Available integrations should be the bigger header and Azure and AWS integrations should be a smaller header size (these are all available integrations).

[x] The section about the Azure.Provisioning libraries doesn't seem like something we should call out on this page. When we make a doc about using the CDK, we can put it there.

[x] This note:

They extend the IServiceCollection interface allowing client-consuming projects, such as your web app or API, to use the connected resource. The official client integration NuGet packages

Our integrations extend IHostApplicationBuilder not IServiceCollection. This is because they use both IConfiguration and IServiceCollection.

Available integrations should be the bigger header and Azure and AWS integrations should be a smaller header size (these are all available integrations).

That's already the case, "Available integrations" is an h2 and the Azure and AWS headings are h3.

In the cloud-native features section, we should consider removing the orchestration paragraph completely, as it currently reads as though the app host provides orchestration in the cloud rather than being for dev time only.
We should consider removing "cloud-native" from the section altogether actually, and focus more on what is actually added, i.e. service discovery and service defaults.


Akka won't compile on JDK 9+, sun.misc.Unsafe problem

some previous history is at https://github.com/scala/community-builds/pull/749
in short, we're getting
[akka-actor] [error] /home/jenkins/workspace/scala-2.12.x-jdk10-integrate-community-build/target-0.9.12/project-builds/akka-actor-b454a7b577ffd7774882613b44b77d1f5836b1c1/akka-actor/src/main/scala/akka/util/Unsafe.java:14:29: object misc is not a member of package sun
[akka-actor] [error]     public static final sun.misc.Unsafe instance;
[akka-actor] [error]                             ^

note this is a scalac error message on a .java file
it happens on Jenkins and is also reproducible on MacOS on OracleJDK 9
but I have not been able to reproduce it outside of dbuild, even with ++2.12.7-bin-90c94cc

hmm maybe we need --add-modules=jdk.unsupported (though why it would work outside dbuild without that, idk)

close, it was -release 8. though I don't know why


is there something like Responsive column?

hello sir, i was working on my app that create a container that fill the whole window,
and i found ResponsiveRow to deal with the width changing, but after few days of searching in doc I still can't find a way to react the window height change

I don't think there is a responsive Column component. But you could probably put together something similar with a few simple lines of code, my approach would be to use a container to act as a html div and set different breakpoints for the height, as you scale down or up your main window, use the EventHandler page.on_resize  to call your function that will adjust the container's new height.

I don't think there is a responsive Column component. But you could probably put together something similar with a few simple lines of code, my approach would be to use a container to act as a html div and set different breakpoints for the height, as you scale down or up your main window, use the EventHandler page.on_resize to call your function that will adjust the container's new height.

thx for your advice, i made it with page.on_resize, but the event only trigger when i finished window resizing(left my LMB), unlike the instant width change with ResponsiveRow
Is there any way better? or its the limit, thx for your help still

There isn't.
@FeodorFitsner do you think it could be added?


add ivyrosefernsby

Add ivyrosefernsby as a contributor.

Hey there,
Thanks for your PR & contribution :wave:!
Don't forget to join follow me, join our organization, & follow our organization to stay updated with the latest developments 💻
Thank you, and have a good day ahead 😊


Small typo in README.md

The link was pointing to a reply instead of the tutorial itself

Gracias.


Funds might get stuck if on swap the routing contract does not use the full amount

If for any reason the routing contract does not use the full amount of the asset to swap for hats, the rest will stay in the contract, but not be accounted for in the balance still available to swap, this will make it stuck in the contract. Should we handle this case (considering that normally the swap contract is expected to use the full amount available) ?

it will not fail in case it can't swap everything?

it is not supposed to fail in case it can't swap everything?

That would depend on the routing contract not on us. So maybe, but maybe not...

then sounds to me that we should check

So you'd update the vars with amounts that were actually swapped instead of setting them to 0?

Well yes that's the solution. The question is if the added complexity is actually worth it.


Lone record is focused in continue reading

Type of installation
Portable (.zip)
Steps to reproduce

Open any file and close it.
Lone record is focused in continue reading when the 'Bookmark / History Search' option is enabled.

Also, when there are multiple records it does not happen.
But remove the records until only one record is present.
The lone record is focused again.

https://github.com/mienaiyami/yomikiru/assets/127277950/57d76b6a-419b-47e1-9a1d-3518bd2e6dd7
✔ Expected Behavior
For the lone record to not be focused.
❌ Actual Behavior
Lone record is focused.

I did fix this but forgot to check when bookmark/history search is enabled. Thanks for letting me know.


[BUG] v0.4.0 text submodule depend on features submodule

Hi,
I found v0.4.0 uses autogluon.features module in order to preprocess multimodal text-tabular data.
https://github.com/awslabs/autogluon/blob/0.4.0/text/src/autogluon/text/automm/data/preprocess_dataframe.py#L8
There is no dependency specified in setup.py in the text submodule.
This might cause errors if the user only did submodule installations.
For your reference:

@Qiaochu-Song i closed it since the fix has been merged. Thanks @Innixma !


Upgrade to support ESlint 6.x

@alansouzati Please review.

hey sorry @pgAdmin I took a break from open source. Would you like to own this project? Im going to review this, but moving forward it would be wise to transfer this repo to someone that is willing to maintain it.

@alansouzati I would be happy to maintain it

sure, im releasing the version and I will transfer the repo to you. also can i have your NPM username so that I can grant you access to publish to NPM?

I've just released 1.1.0

also, you might want to delete your fork, I tried transferring to you and I got an error because of that.

@alansouzati Deleted the fork. My npm username is pgadmin


Any way to connect to Databricks SQL

Is there a way to connect to a Databricks SQL instance, maybe through the Hive connector? If not, possible to add a new connection type for Databricks?

Hi @wt1309! It's the first time we get this specific request and we aren't aware if connecting to Databricks is possible. Could you please try it out with the Hive connection and share with us here if you encounter any errors? Then it would be more efficient to work around that. Thanks!
Here's our documentation: https://github.com/GoogleCloudPlatform/professional-services-data-validator/blob/develop/docs/connections.md#hive


Test run fails when Oracle.ManagedDataAccess is added

First of all I want to thank you for the amazing tool you've made!
I've got this issue in a project which targets full framework (4.6.1), where the test run writes out this error during execution:
C:\Users\user\.nuget\packages\coverlet.msbuild\2.3.0\build\netstandard2.0\coverlet.msbuild.targets(16,5): error : Invalid directory size. [C:\work\temp\demotest\demotest.csproj]
I've been able to isolate the problem, and it seems to only occur when I add a reference to the package Oracle.ManagedDataAccess. The issue is not present when targeting netstandard2.0/netcoreapp2.1 and using Oracle.ManagedDataAccess.Core, but since this package still is in beta we're not able to ship software relying on it, yet.
Steps to reproduce
Execute the following lines (was performed in wsl-terminal). I've truncated the classes to single lines to make it easier to copy-paste.
mkdir temp && cd temp
dotnet new classlib -n demo
dotnet new xunit -n demotest
dotnet add demotest/ reference demo/demo.csproj

sed -i 's\netcoreapp2.1\net461\' demotest/demotest.csproj
sed -i 's\netstandard2.0\net461\' demo/demo.csproj

dotnet add demotest/ package coverlet.msbuild

echo 'namespace demo { public class TestableClass { public static int Answer() { return 42; } } }' > demo/TestableClass.cs
echo 'using demo; using Xunit; namespace demotest { public class TestClass { [Fact] public void Test() { Assert.Equal(42, TestableClass.Answer()); } } }' > demotest/TestClass.cs

dotnet test demotest/ /p:collectcoverage=true
echo Return code $?

dotnet add demo/ package Oracle.ManagedDataAccess
dotnet test demotest/ /p:collectcoverage=true
echo Return code $?

Issue
The first test run is successfully executed, and returns exit code 0.
As you can see, the latter test run writes out the error message mentioned in the top after build, before proceeding (and successfully executing) with the test run, and returns exit code 1.

Hey @henrihs, at this time Coverlet only works with .NET Core and not the full framework. Bringing it to the full framework is definitely something I've thought about and so far there's been very little in the way of demand/ROI.
Opencover and AltCover might be alternatives to explore

Well there's nothing technically stopping Coverlet from working on .NET Framework, it's just not a scenario I've tested so there are definitely gonna be some kinks here and there.
However, since Oracle.ManagedDataAccess is a public package I'll try to reproduce this locally and come up with a solution

I've had a quick look at this, and

It looks to be purely cosmetic with coverage of the system under test being generated OK at the end of the day
The latest version of Oracle.ManageDataAccess.dll (which is of course copied to the output directory for a full framework build) fails to decompile in the latest ILSpy (it raises an exception reading the debug header with an invalid length) -- this may be related
As the Oracle package contains no .pdb files, AltCover doesn't even try to instrument that assembly, and raises no exception in an equivalent to the repro steps given above.

dotnet add demotest/ package altcover
dotnet test demotest/ /p:AltCover=true -v m

This should be resolved in last version where we skip to instrument dll without pdb or local sources(embedded or not).
Feel free to reopen if needed.


Felix_sprint 5 - intake + magical movement control

Yesterday I went to your university

the whole weekend I worked on my intake

Mr bro said the mounting part should not be just stuck into the plastic, but locked by a screw head. I'm working on it now

I should also make sure all the screws fit all holes

Yesterday I cleaned up the table and tested the intake, but we don't have any good gears for that so I'm making a new one

Redesigning the intake with only the parts we have

The intake is done+assembled

The intake is done, the holes are widened, the stings are connected and the intake is on the robot


Converted images to HTML tables.

Q
A

content fix?
no - yes?

New article?
no - yes?

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
Guidance
You can delete this section when you are submitting the pull request.

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch. Released documents are in live branch.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/design/accessibility.md
:white_check_mark:Succeeded

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


E999 syntax error for match statement

ruff throw a syntax error for code like this:
import sys

value: str = sys.argv[1]

match value:
    case "ruff":
        print("Rough?")
    case "awesome":
        print("Of course is it!")
    case _:
        print("what?")

$ ruff ruff_and_match.py
Found 1 error(s).
ruff_and_match.py:5:8: E999 SyntaxError: invalid syntax. Got unexpected token 'value'

versions

Python 3.10.6
ruff 0.0.108

config:
[tool.ruff]
line-length = 100
select=["E", "F", "W", "U", "N", "C", "B", "A", "T", "Q", "RUF", "M", "ANN"]
ignore=["F403", "F405", "B008", "A003"]

(and yes ruff is awesome ;-))

Yeah, ruff is using RustPython which doesn't support match yet.
Also see https://github.com/charliermarsh/ruff/issues/282 and https://github.com/charliermarsh/ruff/issues/54
There is a note in the README, but it's a bit hidden.

Ruff does not yet support a few Python 3.9 and 3.10 language features, including structural pattern matching and parenthesized context managers.

ok, sorry for the noise :grimacing:

No worries, just pointing it out. :) I think Charlie is working on alternatives to RustPython that could fix that.

Yeah, sadly those aren't supported yet. Another possibility is rewriting the RustPython parser to support that syntax! (It has to be rewritten anyway, CPython itself moved to a new parser to support those expressions which were "impossible" in the old parser.)

(For clarity: this is still open, but a dupe of #282.)

Fixed as of v0.0.250 which included match statement support.

Holy cow! 🎉 That's fantastic news, Charlie! Can't wait to replace all my elif chains with match statements now. 😄

🎸 🎸 🎸


Can the module run on Mac OS?

Thx.

It only supports Linux and there is no plan to extend to other OS.


Website

close #183

I am currently getting an error when running  sbt docs/ghpagesPushSite:
[info] Loading global plugins from /Users/julien/.sbt/0.13/plugins
[info] Loading project definition from /Users/julien/Project/Monocle/project
[info] Set current project to monocle (in build file:/Users/julien/Project/Monocle/)
[error] fatal: Not a git repository (or any of the parent directories): .git


chore: 🤖 Started setting up lerna, testers and linters

Basic lerna setup with a bunch of opinions just to get us started

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@beta dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@beta dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@beta dist-tag) :package::rocket:
GitHub release :package::rocket:

:tada: This PR is included in version<EMAIL_ADDRESS>:tada:
The release is available on:

npm package (@beta dist-tag) :package::rocket:
GitHub release :package::rocket:


feat(esl-image-utils): create esl-img-container mixin to provide imgcontainer functionality

Will be reopened when the final design will be discussed


🐾 Minor Update: Make the turtle sprite sit above 0 on the axis exercises

The turtle is at a random place in every axis exercise. Let's try to have it at one place, above/next to the 0 mark of the number line. This will help avoid confusion on the purpose of the turtle.

Proposed Solution

You may have to change the input that is given to the prop turtlePosition when AxisExercise is called within AxisParent.tsx.
Additionally, you may have to change the styling/position that is defined in AxisExercise.tsx that is in the code block that starts with pos === turtlePosition

[ ] :wave: I may be able to implement this update request

This is a :feet: Minor Update

#112 closes this issue


Fix LocalServerPort import path

The path should be org.springframework.boot.test.web.server.LocalServerPort instead of org.springframework.boot.web.server.LocalServerPort
See https://github.com/spring-projects/spring-boot/commit/48f8021d88ef0591d7b931b2a9bc6d4d48247d58

@onionpsy Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Bug has been fixed in the meantime https://github.com/spring-cloud/spring-cloud-commons/commit/c2a22346cde819971263c47b321a81a7908c4f40


refine all teh styles

What Changed

Tons of minor style changes (nudging padding, color changes, alignment, etc.)

Tickets/Issues

Add custom styles to wexplorer

Screencaps

:+1: LGTM


Minor changes to utils.

Added minimum/maxium times for the modes, added a overload to pass in the msh object instead of individual vectors. Squat now uses latest interface. Fixed bug that caused friction to be zero (wrong amount of arguments to getSpiritToeEvalutator).

LGTM, feel free to merge


[Bug]: Auth0 oauth integration strips out vital part of user ID

Package
@lucia-auth/oauth
Describe the bug
auth0 ids come in the form ${prefix}|${id}.
A simple ID might be for example auth0|64e4b9e0fbadcc044d320d37 which is an auth0 user signed in with the basic username & password option on auth0.
The prefix may differ however depending on (afaict) the authentication method, for example for google logins might have an id in the format google-oauth2|..., i've also seen waad for microsoft login.
The point is, that prefix is important and is part of the ID. Unfortunately the oauth integration provided by lucia for auth0 for some reason strips this prefix off. This seems to be done here https://github.com/lucia-auth/lucia/blob/ee7dd23ba446f6e4c37ee71e042af96eb99250d2/packages/oauth/src/providers/auth0.ts#L110
This means in the database the key is stored with the ID without the prefix, effectively making it useless (you couldn't query the auth0 api with it for example) and in theory it could collide with an id from another user if the prefix differed but the rest of the ID happened to be the same.
I'm sure this can be worked around given how flexible lucia is, but nevertheless this is somewhat unfortunate and surprising behaviour.

Edit: a slightly dirty workaround
const auth0Auth = await auth0Provider.validateCallback(code);
// @ts-expect-error providerUserId is private but we need to patch it due to https://github.com/lucia-auth/lucia/issues/1330
auth0Auth.providerUserId = auth0Auth.auth0User.sub;

Yeah this was a mistake but I unfortunately cannot change this without a major update. Were replacing the integration in v3 anyway so I’d recommend using its replacement to manually implement it: https://arctic.js.org/

Thanks for the recommendation, running into this trying to swap to arctic - https://github.com/pilcrowOnPaper/arctic/issues/29
I'll get a PR up to fix that

can I Work in this?

Closing this since it'll require a breaking change. I guess we can deprecate the Auth0 module but that's another issue


Adding Contributor Workflow to Documentation

I am a contributor to GSSOC'23, an open-source project. I would like add a contributor workflow to the documentation. Could you please assign this issue to me? @J0SAL

Hey @Jiggy9!
There are a few changes made to the project documentation, that I believe are similar to your issue.
If you think you can add something extra, do mention it in the description in a little more detail

Hey @J0SAL Thank you for your response! I noticed that there have been some changes made to the project documentation, but I would like to add a section on 'How to start contributing' that includes all the major basic steps. This section will cover everything from forking the repository, opening it on a local device, creating a new branch, making modifications, merging it into the master branch,  sending a pull request and wait till it is reviewed and merge.
I believe this section is crucial as it provides newcomers with a clear understanding of the contribution process. By following these steps, contributors can effectively participate in the project. Once I've added this section, you can review it and provide feedback on any missing or necessary information.

I believe those guidelines are already present here

Yes thank you I just noticed it.


[FLINK-20723][cassandra][tests] Retry on NoHostAvailableException

Beefs up the RetryRule to allow configuring retries per class, and subsequently sets up retries for the entire CassandraConnectorITCase.
To avoid inconsistent/unexpeced behaviors when combinding class-wide retries with expected exceptions, the latter are now properly handled by the retry rule (i.e., if they occur then we don't retry and just rethrow the exception).
The existing pattern of annotating single methods was not really viable for this case because various tests are inherited from a parent class, which we could only annotated by overriding each of them.
This seemed like annoying busy work, so I fixed the root issue instead.

We already tried that in the past to no avail.


Effects CropVisualEffect Enhancement Request

Thought others might benefit from this:
I have added a new enum to "CropVisualEffectType" (custom) in my code.
public enum CropVisualEffectType {     case blurDark     case dark     case light     case none     case custom(color: UIColor) }
modified "getEffect" to use it:
 static func getEffect(byType type: CropVisualEffectType) -> (UIVisualEffect?, UIColor) {         switch type {             case .blurDark: return (UIBlurEffect(style: .dark), .clear)             case .dark: return (nil, UIColor.black.withAlphaComponent(0.75))             case .light: return (nil, UIColor.black.withAlphaComponent(0.35))             case .none: return (nil, .black)             case .custom(color: let color): return(nil, color)         }     }
I also changed the "cropToolbar" modifier to public in "CropViewController"
This allows me to change the background, toolbar colors to match:
config.cropVisualEffectType = .custom(color: UIColor(named: "ThemeColor")!)  cropViewController.view.backgroundColor = UIColor(named: "ThemeColor")  cropViewController.cropToolbar.backgroundColor = UIColor(named: "ThemeColor")

@ejuden Would you mind submitting a PR for that so I can review the code?
Also, maybe you can add a ThemeColor property to Mantis.Config instead of making CropToolbar public.

I am not sure I created the PR correctly, looks like I have 4 separate patches for the same fix.
Edward
On Nov 12, 2020, 1:46 PM -0600, Yingtao Guo<EMAIL_ADDRESS>wrote:

@ejuden Would you mind submitting a PR for that so I can review the code?
Also, maybe you can add a ThemeColor property to Mantis.Config instead of making CropToolbar public.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ejuden Do you have a branch with the entire fix committed to it? If you push that branch to your github fork it is easy to make a single PR from that 👍

Ok, got a crash course on using PR in GitHub, never done that.  Thanks!
All done.
Edward
On Nov 12, 2020, 3:48 PM -0600, Apptek Studios<EMAIL_ADDRESS>wrote:

@ejuden Do you have a branch with the entire fix committed to it? If you push that branch to your github fork it is easy to make a single PR from that 👍
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

@ejuden Since you submitted the PR(https://github.com/guoyingtao/Mantis/pull/73) for this ticket. I just close this ticket and we can do more discussions in the PR.


Use data from external blob

This issue is for a: (mark with an x)
- [ ] bug report -> please search issues before submitting
- [] feature request
- [x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

I would like to use data from external blob what would be the best way to do it with current soluton ?
I don't want to download all files to local store them in data folder and then deploy them.
I want to connect to blov and have all file splited and analysed.

Take a look at this link:
https://github.com/Azure-Samples/azure-search-openai-demo/pull/35

Hi @adrianoaraujocoelho I did look at #35 but it is not working :(

did you download the code? What's the error?

@adrianoaraujocoelho Yes I did it fails to upload document most likely due to authorization issue

I have a sharepoint index set up in my cognitive search service in Azure. The index has data. I want to modify the code so that it can reference the sharepoint index instead of the default gptkbindex. Is there any way to do that?


maxNumberTenderers field name must be more explicit

Although its description is clear, tender.procurementTechnique.maxNumberTenderers suggests that it's not specific to framework agreements.

It seems that after this issue was opened, the field maximumNumberSelectedTenderers was moved under frameworkAgreement, which makes it clear.


WIP:Clarify how to use d4mac, d4win with Swarm mode

- What I did
Added new subtopics and notes to clarify how to use d4mac, d4win with swarm mode. Users are getting confused trying to follow the tutorial with d4mac and d4win.
- How to verify it
Test the suggested modes and scenarios.
Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>

@sfsmithcha @friism Here is the first pass on improving the docs around using d4mac, d4win with the new Swarm mode. I'll also add something in the d4mac, d4win docs tonight / tomorrow so that we can cross-link between the two docsets. This is a work-in-progress. Let me know what you think, and we'll iterate on it.

@friism @justincormack @sfsmithcha please take a look at revised version of these docs w/comments from you all incorporated. I'll start on adding relevant section to d4mac, d4win docs and link into Swarm tutorial from there. Let me know what you think.

@sfsmithcha @justincormack @friism if you guys think this is good to go, let me know and then merge?

other than final nit LGTM

@sfsmithcha I think this should do it in terms of your comments. If you think it's good-to-go, please merge (I don't have merge permissions). Then I'll write a relevant section in d4mac, d4win docs and link to this when this is published. Thanks!


Document design decisions: text-input

Text-input design is solid. The design decisions are captured through out this issue https://github.com/carbon-design-system/carbon/issues/2329#issuecomment-523153733 It would be amazing if we never have to have this conversation again because we forgot things, eg. dropdown cannot have helper text below field, etc etc. I know I myself have forgotten this multiple times and wondered why don't we place the helper text below to be less obtrusive?
What's the best way to document & present design decisions? FYI @janchild

Hey there! Going to close this one out due to inactivity. Feel free to comment and I can re-open!


Allow users to specify the remote batch_gahp script

This is required for Bosco 1.3 tarball usage with HTCondor 9.0.0 on
the CE
From here, my plan is to add some bits to the helm chart that will specify --rgahp-glite batch_gahp if the user specifies a Bosco 1.3 tarball

This change to remote_gahp is incomplete. When the gridmanager wants to start the condor_ft-gahp, another instance of the blahpd is started instead. I'm attaching an additional patch that fixes the problem.
(Seriously, GitHub? You don't like the .patch file extension?)
rg.patch.txt


Change Map dimensions

TODO:

Change Map Dimensions
Change Obstacle Sizes
Change In-obstacles function to check for collisions with the walls.

Add border color to bloated obstacle space


[🐞] Use Promise.allSettled for useTask$

Which component is affected?
Qwik Runtime
Describe the bug
It looks like Qwik is using Promise.all to wait for all useTask$ to resolve. This prevent all task to resolve if one of them rejects.
at Module.get (<PROJECT>\app\src\service\queries\utils.ts:33:9)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async qrl (<PROJECT>\node_modules\.pnpm\@builder.io+qwik@1.2.12_undici@5.22.0\dist-dev\tsc-out\packages\qwik\src\core\util\implicit_dollar.js:8248:24)
      at async AsyncFunction.useQuery_useTask_VW5jqtKnGPM (<PROJECT>\app\src\service\query.tsx:48:21)
      at async Promise.all (index 1)
      at async Promise.all (index 0)
      at async Promise.all (index 1)
      at async Promise.all (index 1)
      at async Promise.all (index 1)
      at async Promise.all (index 1)

I think this is happening here : https://github.com/BuilderIO/qwik/blob/main/packages/qwik/src/core/render/dom/notify-render.ts#L281
Reproduction
N/A
Steps to reproduce
No response
System Info
.

Additional Information
No response

AFAIK this is intentional, tasks should never reject

Maybe add a warning then in the console to explain that this is on purpose. It took me sometime to figure out what was going on.
Out of curiosity, why a task should not reject ?

Errors should be handled by the task function, so that expected errors can update the UI, and unexpected errors should break the application so that you can find what's wrong. Can you make a PR with a message that would have helped for you?

It seems like a dangerous way to force developers to handle error catching. Let's say a developer didn't handle error in one of his task, and some analytics API fails in production, then all tasks will fail, breaking the whole app while it might have been harmless.
Except if there is reason specific to Qwik, I think the expected (and safer) solution is to forward the error into the console, as it's managed in any JS runtime.

It's not showing the error in the console? That's a bug then. PR welcome :)

BTW https://github.com/BuilderIO/qwik/pull/1780#discussion_r998567387

The error is forwarded in the console, but if one reject all the other tasks won't resolve even if they could. So even if the app could have work, it won't because Promise.all didn't give it the possibility to.

Hmm, I suppose the Promise.all could wrap each task in a console logger and back to allSettled like before.

Did you read Manu's comment?

I did. If you only wait for Promise.allSettled you'll loose all errors, so in this case Promise.all() seems like a better option. But it comes at the price of rejecting promises that would have work. Sometime it's the expected behavior, but in the case of tasks I don't think it is.
Bad:
// Will never catch
await Promise.allSettled();

Better:
// Will over catch
await Promise.all();

Best:
// Will catch only what has rejected
const results = await Promise.allSettled();
for (const result of results) {
  if (result.status === 'rejected') console.error(result.reason);
}

I like the idea of adding an error handler to console.error the issue and moving on. Any chance we could get a PR for that?

I made the pr. merging it now


TCD-2331 Note clarifying ADB support

Description
Add a note to Appium > RDC doc stating that we don’t support ADB without the use of vUSB (and include link to  reference it back to https://docs.saucelabs.com/mobile-apps/features/virtual-usb/  ). vUSB + private devices is the only way to do “adb shell” commands. So the programmatic equivalent (mobile:shell scripts) is not supported at Sauce Labs. On Public or private devices. (source : Issue created in Slack from a message.)
Send to lakshmi, max, and wim for review approval.
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Documentation fix (typos, incorrect content, missing content, etc.)

Checklist

[ ] I have read the contributing document.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@aoleszyn Per my Slack message, please combine and re-write the two notes, and change to a regular note, not a caution note.

@lauramthomas I was discussing this case with @mdsauce and @wswebcreation. Since those are two separate limitations (ADP not being supported and ADP+vUSB) me and Wim agreed that they should be put in two different notes, separately. Also when i was discussing it with Max he mentioned that they are receiving questions about it and the warning should be placed somewhere in the beginning of doc.


Add custom cache-control header option

Closes #32
Essentially adds cache_control after each ttl, where the response headers are determined by
        if ttl:
            messageData["headers"]["Cache-Control"] = (
                f"max-age={ttl}" if status == "OK" else "no-cache"
            )
        elif cache_control:
            messageData["headers"]["Cache-Control"] = (
                cache_control if status == "OK" else "no-cache"
            )

so that cache_control is only used if bool(ttl) is False, which should keep backwards compatibility.

thanks for the PR @kylebarron,
I wonder if it would make sense to deprecate ttl and make cache-control the only way to set this.
If we do this, we will add a deprecation warning and later when we release a 6.0.0 version we will remove the ttl options

That's up to you. I don't have too strong a feeling either way.
Also you say lambda-proxy is adapted from aws/chalice; is this just a much simpler, smaller version of that?

yeah, Chalice does more things than lambda-proxy and require some libs while I wanted something really simple (at least that's how I felt when I started this project).
Most of the code here was inspired by earlier version of https://github.com/aws/chalice/blob/master/chalice/app.py

Makes sense. I can see why it would be helpful to have a small version tailored to your needs.

I added a deprecation warning for ttl

I can look up how to add a test for cache-control if you'd like.

thanks @kylebarron, I could have a look maybe tomorrow.

I can look up how to add a test for cache-control if you'd like.

Not sure to understand, you already added a test.
Maybe we could add a test to make sure the function warns for ttl

you already added a test.

😅 Oops, I forgot I did.


exported resources mocking

I wonder if it would be possible and if so where would one start, to try and mock, in some way the puppetdb api specificity for exported resources and possibly queries issued with dalen/puppet-puppetdbquery.
The scenario i have in mind is being able to use octocatalog-diff in CI pipeline which would preform the following steps

install puppet
download the current main/production/master branch in one dir
download the change branch/commit into another dir
run octocatalog-diff on the two branches to report on diffs.

This* mostly works unless a manifest needs to retrieve data from puppet i.e. exported_resources.  for the purposes of testing we generally dont care what the content of the exported resources are we just want need something stable to be available at run time so we can compile the catalogue consistently without error.  As such i wonder if there is currently a way, oir if you have considered implementing some way to mock the puppet api endpoint and fake the response to exported resources quires.
Im not sure how this might be implemented but it could be as simple as creating a yaml file with a bunch of valid resources to uses for puppetdb queries or dynamicly scan the puppet code base and generate exported resources on the fly based on some sane defaults.
*we currently uses a home grown tool to preform a similar function to octocatalog-diff however we also need to make changes to support puppet 6 and as such are considering switching to this tool.  in our current set up we just spin up an empty puppetdb instance and populate it with some junk data

That's a good set of questions, really...
So at GitHub, we run jobs on every PR that (basically) do the following:

ensure a representative set of catalogs compile (via octocatalog-diff)
run a bunch of rspec-puppet tests (and we use octofacts to use realistic facts in those tests)
run integration tests that build shared OS base images
run linters

We don't actually use the output of octocatalog-diff as a CI job unless you ask for it (as an alternative to running a puppet noop). Then, we kick off a CI job that does essentially what you describe (and there are options to do it against a single host, or multiple, etc).
I think we might have just retired some last vestiges of exported resources, but we do call out to puppetdb as part of those optional CI jobs to report on diffs. And more or less everything works fine - we don't have a general problem with the "stability" of the data in-between runs.
So I suspect I don't understand fully what use-case you're talking about? There may be some magic happening in our test setup to keep the stability that you're referencing - there's a lot of shell scripts and I stopped spelunking after awhile 😆.
Can you give me another example of what you're talking about? Maybe we didn't use exported resources in the same way that you do, so maybe I don't know what problems one might run into? 😆

That's a good set of questions, really...
So at GitHub, we run jobs on every PR that (basically) do the following:

ensure a representative set of catalogs compile (via octocatalog-diff)
run a bunch of rspec-puppet tests (and we use octofacts to use realistic facts in those tests)
run integration tests that build shared OS base images
run linters

We don't actually use the output of octocatalog-diff as a CI job unless you ask for it (as an alternative to running a puppet noop). Then, we kick off a CI job that does essentially what you describe (and there are options to do it against a single host, or multiple, etc).
I think we might have just retired some last vestiges of exported resources, but we do call out to puppetdb as part of those optional CI jobs to report on diffs. And more or less everything works fine - we don't have a general problem with the "stability" of the data in-between runs.
So I suspect I don't understand fully what use-case you're talking about? There may be some magic happening in our test setup to keep the stability that you're referencing - there's a lot of shell scripts and I stopped spelunking after awhile 😆.
Can you give me another example of what you're talking about? Maybe we didn't use exported resources in the same way that you do, so maybe I don't know what problems one might run into? 😆

Also - if you do decide to update your tool... the bulk of what needs to be done for puppet 6 support is here: https://github.com/github/octocatalog-diff/pull/226/files#diff-2f75d312af42343fc9eefc3b6295eb78cfad93005ca0c7ebfe77015e775d5e6bR61-R122 - the kicker, of course, is that you have to upgrade to at least Puppet 6.5.0. The rest of the PR is mostly test changes, and supporting another resource type that I think was introduced with Puppet 6. So the work to update your tool might be simpler with Puppet 6.5.0.
Of course we'd love for octocatalog-diff to work for what you need, though! 😄

Also - if you do decide to update your tool... the bulk of what needs to be done for puppet 6 support is here: https://github.com/github/octocatalog-diff/pull/226/files#diff-2f75d312af42343fc9eefc3b6295eb78cfad93005ca0c7ebfe77015e775d5e6bR61-R122 - the kicker, of course, is that you have to upgrade to at least Puppet 6.5.0. The rest of the PR is mostly test changes, and supporting another resource type that I think was introduced with Puppet 6. So the work to update your tool might be simpler with Puppet 6.5.0.
Of course we'd love for octocatalog-diff to work for what you need, though! 😄

Thanks for the response.  What we have sounds vary similar to what you have described.  including the fact that

our tool is also only run on demand, you can see examples via the Jenkins job.
we don't need puppetdb for facts as we use yaml files for the pcc run (rspec-puppet-facts for the rspec test)

however we do use exported resources as well as dalen/puppet-puppetdbquery query_* functions (which may be more of an issues then exported resources).
Currently the images that run theses jobs have a standalone puppet master configured with a local puppetdb instance.  the puppetdb instance is populated as CI jobs are scheduled i.e. the first job to run, runs against an empty puppetdb.  As such any catalogue compilations which require information from  puppetdb can fail or have nondeterministic affects leading to strange issues and hacky workarounds
We can fix our manifest so that the are resilient to puppet queries returning no data however this can have significant implications to the final compiled catalogue meaning not all code paths get tested.
As such it would be nice to have something like rspec-puppet-facts/octofacts.  but for exported resources or dummy resources which could be queried via dalen/puppet-puppetdbquery
I appreciate this is an edge case and writing it out makes me thing its more a problem with dalen/puppet-puppetdbquery and not exported_ resources.  Thus making it even more edge however the  machination of others who may have consiedred this are most welcome even if the bug is determined invalid/wont fix :)
As to further development, first thanks for the link, however for us moving to puppet 6.5 is probably some time away that said my current thinging is that when we do octocatalog-diff will be the preferred candidate to replace are internal tooling

Thanks for the response.  What we have sounds vary similar to what you have described.  including the fact that

our tool is also only run on demand, you can see examples via the Jenkins job.
we don't need puppetdb for facts as we use yaml files for the pcc run (rspec-puppet-facts for the rspec test)

however we do use exported resources as well as dalen/puppet-puppetdbquery query_* functions (which may be more of an issues then exported resources).
Currently the images that run theses jobs have a standalone puppet master configured with a local puppetdb instance.  the puppetdb instance is populated as CI jobs are scheduled i.e. the first job to run, runs against an empty puppetdb.  As such any catalogue compilations which require information from  puppetdb can fail or have nondeterministic affects leading to strange issues and hacky workarounds
We can fix our manifest so that the are resilient to puppet queries returning no data however this can have significant implications to the final compiled catalogue meaning not all code paths get tested.
As such it would be nice to have something like rspec-puppet-facts/octofacts.  but for exported resources or dummy resources which could be queried via dalen/puppet-puppetdbquery
I appreciate this is an edge case and writing it out makes me thing its more a problem with dalen/puppet-puppetdbquery and not exported_ resources.  Thus making it even more edge however the  machination of others who may have consiedred this are most welcome even if the bug is determined invalid/wont fix :)
As to further development, first thanks for the link, however for us moving to puppet 6.5 is probably some time away that said my current thinging is that when we do octocatalog-diff will be the preferred candidate to replace are internal tooling


chore(HACBS-2290): manual release-service update

The release-service update needs to run paired with an e2e-test change, so creating the update manually.

The e2e-tests PR that is paired with this is https://github.com/redhat-appstudio/e2e-tests/pull/634
The release-service PR that was paired with the e2e-tests PR is https://github.com/redhat-appstudio/release-service/pull/208

/lgtm


Bowtie2 mem error？  qsub ,  SGE

I'm working with an old version (Red hat 5.7) system computer cluster server without Internet-connection.
It took me a lot of time to install this atac_dnase_pipeline.
Anyway, the software invironment seems available now.
I have tried to submit analysis job using qsub.
It always terminated like this:
Specified adapter for rep1:00 (PE) : None
Task has finished (23 seconds).
Task failed:
        Program & line     : '***/modules/align_bowtie2.bds', line 148
        Task Name          : 'bowtie2_PE rep1'
        Task hint          : 'bowtie2    -X2000 --mm --local --threads 6 -x '
        Task resources     : 'cpus: 6   mem: -1.0 B     wall-timeout: 8640000'
        State              : 'ERROR'
        Dependency state   : 'ERROR'
        Retries available  : '1'

This is my script.
#!/bin/bash
#$ -S /bin/bash
#$ -q all.q
#$ -j yes
#$ -cwd
#$ -N ***
#$ -o ***
#$ -l h_vmem=15g
#$ -l ht=blade
source ***/.bashrc
source ***/.bash_profile
bds ***/atac.bds \
-species hg38 \
-nth 6 \
-mem_bwt2 12g \
-out_dir *** \
-fastq1_1 ***R1.fastq.gz \
-fastq1_2 ***R2.fastq.gz

I have tried : bds -s sge  -q all.q atac.bds ...   commad，just the same error.
And I'm sure someone has succeed using qsub.
So, what's the cause of this , the cluster didn't provide enough memory for the pipeline?
Thanks.

Please post a full log for more info. Can you give more memory #$ -l h_vmem=30g and try again? For the first command (local mode using qsub), -mem_bwt2 12g is useless so remove it.
BTW Your second command (sge mode, in this mode pipeline automatically qsub/qstat each sub-task) is wrong (bds -s sge -q all.q atac.bds ...). You need to run bds -s sge atac.bds -q all.q ... or bds atac.bds -system sge -q all.q ....

Hi,
I installed a standalone bowtie2 and tried this script with qsub :
#!/bin/bash
#$ -S /bin/bash
#$ -q all.q
#$ -j yes
#$ -cwd
#$ -N ***
#$ -o ***
#$ -l h_vmem=15g
#$ -l ht=blade
~/bowtie2 -X2000 --mm --local --threads 6
-x ***/GRCh38_no_alt_analysis_set_GCA_000001405.15.fasta \
-1 ***R1.fastq.gz \
-2 ***R2.fastq.gz

It worked well. Then I realized this might not be a memory issue.
I tested  commands after source activate bds_atac , found out bowtie2/perl couldn't run like this:
***/miniconda3/envs/bds_atac/bin
$ ./perl --version
./perl: /lib64/libc.so.6: version `GLIBC_2.11' not found (required by ./perl)

It seemed that the old version(red hat 5.7 , gcc4.1.2, glibc 2.5) system env wasn't available completely.
Then I linked it with a newly built gcc-4.9.2/glibc-2.19 lib:
***/patchelf --set-rpath \
***/glibc-2.19/lib:***/gcc-4.9.2/lib64:***gcc-4.9.2/lib:/usr/lib64:/usr/lib:/lib64:/lib:***/miniconda3/envs/bds_atac/lib \
--set-interpreter ***/glibc-2.19/lib/ld-2.19.so \
***/miniconda3/envs/bds_atac/bin/perl

My mentor had taught me that way to deal with a python lib compatible error.
It also worked on perl .
Then my previous bds script worked using qsub.
It's painful to have to use an old system. Hope it helps with other issues.


Tasks: reorder tasks in main page

Move multimodal and nlp up 🔝 @julien-c

closes https://github.com/huggingface-internal/moon-landing/issues/11505

waiting for an approval from code owners


[20.03] buildRustCrate fixes backports

Motivation for this change
This PR backports a bunch of changes that have been done to buildRustCrate since the branch-off. They are (mostly) just fixing bugs. Some of which are more annoying then others.
Since none of these break compatibility with older packages or users I do think they are still good to be included.
The PRs that are included in this:

#79299: buildRustCrate: remap the current build dir to / for (more) reproducible builds (bugfix)
#79816: buildRustCrate: remove superfluous dependency overrides (~10x eval speedup in some cases; bugfix)
#82155: buildRustCrate: Search for matching Cargo.toml in sub directories (feature/bugfix)
#82404: buildRustCrate: only link build deps into build script (bugfix)
#83481: buildRustCrate: fewer backslashes (syntax only change)
#83379: buildRustCrate: don't sort link flags  (bugfix for an issue introduced in #82404)
#83616: buildRustCrateTests: Fix link order test on darwin  (bugfix)
#83488:  buildRustCrate: Add "-r" to cp to make it work under Mac OS (bugfix)

Things done

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

[X] NixOS
[X] macOS

@GrahamcOfBorg build buildRustCrateTests

Dear @NixOS/nixos-release-managers,
Please consider this for inclusion into 20.03. This carries a bunch of bug fixes and other QoL improvements. Since we have a very low amount of actual buildRustCrate users in nixpkgs the impact is very minimal. There are a few rebuilds but no new failures.
It would be great to have this in 20.03 since it also improves the compatibility with Darwin.

20.03 hasn't been released, should be fine IMHO to merge if it doesn't cause immediate breakages.

Dear @NixOS/nixos-release-managers,
Please consider this for inclusion into 20.03. This carries a bunch of bug fixes and other QoL improvements. Since we have a very low amount of actual buildRustCrate users in nixpkgs the impact is very minimal. There are a few rebuilds but no new failures.
It would be great to have this in 20.03 since it also improves the compatibility with Darwin.

Soo polite :smile: It sounds good to me.


RangeError: Maximum call stack size exceeded

Environment Details

Pipeline

[x] Build
[ ] Release

Agent Type

[x] Hosted Agent
[ ] Self-hosted/private Agent

Agent OS

[x] Linux
[x] Mac
[ ] Windows

Agent Tool Versions

Mirror Git Repo Task version: 1.1.7

Description
This happens when "Source Repository - Personal Access Token" is empty.
There are 2 problems:

There is some weird error message
The task ended up as "succeeded" and it fails actually

Log Output
2018-12-13T05:40:39.0037948Z ##[section]Starting: Mirror Git Repository to somewhere
2018-12-13T05:40:39.0369605Z ==============================================================================
2018-12-13T05:40:39.0369763Z Task         : Mirror Git Repository
2018-12-13T05:40:39.0369824Z Description  : A straightforward utility to mirror one Git repository to another location
2018-12-13T05:40:39.0369880Z Version      : 1.1.7
2018-12-13T05:40:39.0369944Z Author       : Swellaby
2018-12-13T05:40:39.0370378Z Help         : [More Information](https://github.com/swellaby/vsts-mirror-git-repository)
2018-12-13T05:40:39.0370492Z ==============================================================================
2018-12-13T05:40:41.1745689Z [command]/usr/bin/git -c http.sslVerify=true clone --mirror<EMAIL_ADDRESS>2018-12-13T05:40:41.1746156Z Cloning into bare repository 'some-private-repo'...
2018-12-13T05:40:42.8078651Z fatal: could not read Password for<EMAIL_ADDRESS>No such device or address
2018-12-13T05:40:42.9111186Z path.js:78
2018-12-13T05:40:42.9112093Z function normalizeStringPosix(path, allowAboveRoot) {
2018-12-13T05:40:42.9112277Z                              ^
2018-12-13T05:40:42.9112598Z
2018-12-13T05:40:42.9113057Z RangeError: Maximum call stack size exceeded
2018-12-13T05:40:42.9113121Z     at normalizeStringPosix (path.js:78:30)
2018-12-13T05:40:42.9113229Z     at Object.normalize (path.js:1186:12)
2018-12-13T05:40:42.9113281Z     at Object.join (path.js:1221:18)
2018-12-13T05:40:42.9114667Z     at _ (/home/vsts/work/_tasks/mirror-git-repository-vsts-task_4e842f83-9438-4acb-994c-c8c31137dea9/1.1.7/git-mirror-task.js:1:15082)
2018-12-13T05:40:42.9115166Z     at S (/home/vsts/work/_tasks/mirror-git-repository-vsts-task_4e842f83-9438-4acb-994c-c8c31137dea9/1.1.7/git-mirror-task.js:1:14947)
2018-12-13T05:40:42.9115534Z     at _ (/home/vsts/work/_tasks/mirror-git-repository-vsts-task_4e842f83-9438-4acb-994c-c8c31137dea9/1.1.7/git-mirror-task.js:1:15078)
2018-12-13T05:40:42.9115971Z     at S (/home/vsts/work/_tasks/mirror-git-repository-vsts-task_4e842f83-9438-4acb-994c-c8c31137dea9/1.1.7/git-mirror-task.js:1:14947)
2018-12-13T05:40:42.9116321Z     at _ (/home/vsts/work/_tasks/mirror-git-repository-vsts-task_4e842f83-9438-4acb-994c-c8c31137dea9/1.1.7/git-mirror-task.js:1:15078)
2018-12-13T05:40:42.9116713Z     at S (/home/vsts/work/_tasks/mirror-git-repository-vsts-task_4e842f83-9438-4acb-994c-c8c31137dea9/1.1.7/git-mirror-task.js:1:14947)
2018-12-13T05:40:42.9117083Z     at _ (/home/vsts/work/_tasks/mirror-git-repository-vsts-task_4e842f83-9438-4acb-994c-c8c31137dea9/1.1.7/git-mirror-task.js:1:15078)
2018-12-13T05:40:42.9299089Z ##[section]Finishing: Mirror Git Repository to somewhere

Hi @Jamesits - it looks like your source repository is a GitHub repo at: https://github.com/Jamesits/some-private-repo. I don't see that anywhere as a public repo on your GH profile, and the repo name would indicate that it is a private repository, however, the output also indicates that you are not providing a PAT in the task configuration. Is that correct?

@calebcartwright Yes. I had some more tests: any error on repo URL or auth (didn't try other errors) would result in a RangeError: Maximum call stack size exceeded and the task would report a "succeeded" to the pipeline.

Thanks for letting us know. The task should result in a failed result in that condition so I've marked this as a bug.
However, for the use case described initially in this issue, you'll need to provide a PAT in order to access private repo, in any system.
I don't have a clue where the underlying call stack error is coming from 😄 but we'll look into it!

Well this is fascinating.. when I run the script locally, directly against the .js file emitted by the transpiler, the task executes as expected, and fails on the clone fail step. However, when doing the exact same thing but running the bundled file created by webpack, I can reproduce the reported error (max call stack size exceeded).
Is this a bundling issue?


Add LogSense images

It's a logsense.com integration.

There is a problem with contributed images: https://github.com/fluent/fluentd-kubernetes-daemonset/issues/293

This is no longer valid, I'm closing the PR.


Please tag 0.1.0

It’d be nice to only have to rely on tagged versions in https://github.com/FriendsOfSymfony/FOSHttpCache/pull/173/files.

#5 should be resolved first


Fix typings

Linting issue fix + moving type I missed when I was promoting stuff to stable (this was caught by the Definitely Typed PR so is fixed there already)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.005%) to 41.654%

Files with Coverage Reduction
New Missed Lines
%

extensions/sql-bindings/src/common/azureFunctionsUtils.ts
1
80.65%

Totals

Change from base Build<PHONE_NUMBER>:
0.005%

Covered Lines:
30347

Relevant Lines:
67449

💛  - Coveralls


linux : crash with bsfnullrenderapi.so

i build bsf with this  command:
cmake ../ -D RENDERER_MODULE=Null -D RENDER_API_MODULE=Null -D CMAKE_BUILD_TYPE=Debug -D AUDIO_MODULE=Null -D PHYSICS_MODULE=Null
i made a simple sample. when run ,it crashed. this is the crash log:
A fatal error occurred and the program has to terminate!

Error: InternalErrorException
Description: Could not load dynamic library libbsfNullRenderAPI.so. System Error: libbsfNullRenderAPI.so: undefined symbol: _ZTIN2bs2ct13RenderTextureE
In function: void bs::DynLib::load()

was this on linux? can you provide an example case to replicate?

@pgruenbacher  yes it was crashed on linux! By this way you can reproduce this bug!
`
#include "BsApplication.h"
namespace bs
{
UINT32 windowResWidth = 1280;
UINT32 windowResHeight = 720;
}
/** Main entry point into the application. */
#if BS_PLATFORM == BS_PLATFORM_WIN32
int CALLBACK WinMain(
In  HINSTANCE hInstance,
In  HINSTANCE hPrevInstance,
In  LPSTR lpCmdLine,
In  int nCmdShow
)
#else
int main()
#endif
{
using namespace bs;
// Initializes the application and creates a window with the specified properties
VideoMode videoMode(windowResWidth, windowResHeight);
Application::startUp(videoMode, "DebugWindow", false);

// Runs the main loop that does most of the work. This method will exit when user closes the main
// window or exits in some other way.
Application::instance().runMainLoop();

CppHttpLibServerConnector::shutDown();
// When done, clean up
Application::shutDown();

return 0;

}`


[WIP][SPARK-48797][SQL] Upgrade mariadb-java-client to 3.4.0

What changes were proposed in this pull request?

This PR aims to upgrade mariadb-java-client from 2.7 series to 3.4 series.
Why are the changes needed?

MariaDB Connector/J 3.4 supports Java 17/21 and it is the major updated version.
List of MariaDB Connector/J Releases: https://mariadb.com/kb/en/mariadb-connector-j-releases/
Upgrade from MariaDB Connector/J 2.7 to 3.4: https://mariadb.com/docs/server/connect/programming-languages/java/upgrade/
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Pass GA.
Was this patch authored or co-authored using generative AI tooling?

No.

@yaooqinn  Thank you for reminding me, I will close this pr.


[BUG] Additional space after comments

Describe the bug
A clear and concise description of what the bug is.
Spectrum theme render additional space after line with comments
To Reproduce
Code here
## Today tasks
%%Put the stuff here%%
- 7PM Week review

produces in default Obsidian

With spectrum theme

Expected behavior
A clear and concise description of what you expected to happen.
Spectrum theme will not render comments as empty line

Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS] MacOS BigSur
Obsidian Version: [e.g. 22] 0.11.5

Additional context
Add any other context about the problem here.

Oh wow, that is weird. 🤔
I will take a look into it, thanks for letting me know.

I looked into it, and I get the same break with default as well as with Spectrum. When using a comment, it creates an additional  element, which causes the empty line.

Hello👋 The same thing happens with line reference.

@DannyDies Very curious, have you tested it with the vanilla theme as well?

In default and other themes works fine. Disable all snippets too. Seems like a flexbox problem(other themes I've tested haven't it)

In my case, I disabled .markdown-preview-view.is-readable-line-width .markdown-preview-sizer. Then all stuff align to the left, so I disabled all css from 2 section(Text area) and all just fine for my issue. Flex features not important for me right now. But if you solve it another way, please, let me know.

Obsidian adds an empty div and p container when you have a reference.

a test note

is what it outputs when you write
a test note ^reference

But if you do not have a reference, then obsidian outputs this instead, which is how it should be:

a test note

@DannyDies I have discussed that issue with people on the Discord Server and made a bug report on the Forum, with version 0.12.9 this will be fixed.

Oh, it nice. Thanks for your efforts! Waiting 12.9.