Routes are not automatically updated through ConsulCatalogWatch

Hi Spring-Cloud-Consul-Team,
we use a minimal Spring-Cloud-Consul-based Zuul to forward requests to corresponding services. We noticed that it failed to update the routes as services come and go.
We use 1.0.2.RELEASE of spring-cloud-consul, but the problem persisted also with 1.1.1.RELEASE.
Our setup:
pom.xml
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-consul-discovery</artifactId>
</dependency>
<dependency>
    <groupId>org.springframework.cloud</groupId>
    <artifactId>spring-cloud-starter-zuul</artifactId>
</dependency>

Application.java
@EnableCircuitBreaker
@EnableDiscoveryClient
@EnableZuulProxy
@SpringBootApplication
public class Application {

    public static void main(String[] args) {
        SpringApplication.run(Application.class, args);
    }

}

Through debugging we noticed that no HeartbeatEvents are invoked as the @Scheduled-method of ConsulCatalogWatch is never called.
We could fix it by including our own configuration. Key was the @EnableScheduling annotation as mentioned in the javadoc for @Scheduled.
@Configuration
@EnableScheduling
public class CustomZuulConfiguration {

    @Autowired
    private ConsulClient consulClient;

    @Bean
    public ConsulCatalogWatch consulCatalogWatch(ConsulDiscoveryProperties discoveryProperties) {
        return new ConsulCatalogWatch(discoveryProperties, consulClient);
    }

}

Did we miss anything or is this a problem within spring-cloud-consul?
Thanks in advance.

Do you need to redefine the bean, or just add @EnableScheduling on an @Configuration class?

The bean must be redefined to get it working. It doesn't work to only add the @EnableScheduling annotation to the custom @Configuration. This fits to the javadoc description and examples of @EnableScheduling. In my understanding this annotation must be added to ConsulDiscoveryClientConfiguration.

Using a basic app from start.spring.io with zuul and consul discovery, the @Scheduled method on ConsulCatalogWatch executes for me using 1.1.1.RELEASE.
2016-11-28 14:06:33.666 TRACE 40260 --- [pool-2-thread-1] o.s.c.c.discovery.ConsulCatalogWatch     : Received services update from consul: {consul=[], consulzuul1=[]}, index: 1270
2016-11-28 14:07:07.982 TRACE 40260 --- [pool-2-thread-1] o.s.c.c.discovery.ConsulCatalogWatch     : Received services update from consul: {consul=[], consulzuul1=[]}, index: 1270

Can you please share a project that recreates the problem?

I could narrow it down to the following configuration setting: spring.cloud.config.discovery.enabled
If it is disabled I see the following line in the startup log:
2016-12-08 14:04:04.143  INFO 19655 --- [           main] s.a.ScheduledAnnotationBeanPostProcessor : No TaskScheduler/ScheduledExecutorService bean found for scheduled processing

Enabling it and the line is gone - and so is the invocation of the @Scheduled CatalogWatch.
Do you still need an example app?

If discovery is disabled the catalog watch shouldn't work.

I have a follow up question that relates to this one.
From my understanding the ConsulCatalogWatch should work with blocking queries, so that it would trigger a heartbeat on each change in the consul services catalog. Am I right? So catalogServicesWatchTimeout should make the call hang for a specified amount of time or until a change occurs. For me it does not react to any changes in the catalog.
Also why should the call be scheduled? In other implementations the blocking query is just executed in a while-true statement.

So how this should work ? I can only get updates from consul if I specifically create Bean like in CustomZuulConfiguration  class mentioned. Should it work without defining bean?


[BUG]: GCC High Error with Pagination Limitation Set to 10000

Describe the bug
In commercial, there seems to be no issue with the pagination limit being set above 5000 (the expected CDS connector limit) for pagination, but in GCC High, the Flows in the solution can't be saved because this exceeds the limit.
Is this expected? Is there a separate solution for GCC High to import that has pagination set to 5000?
To Reproduce
Import CoreComponents solution into GCC High environment.
Edit a Flow, and then try to save it. You will receive an error saying the pagination limit is too high. Maximum is 5000.

Hello. Are you installing with a trial license?

Hello we just confirmed that GCC supports the 10000 pagination so likely you are using a trial license which does not. Thank you for using CoE

Hi Jenefer,
Can you clarify if you confirmed for GCC or GCC High?
Best regards,
Robert Camp
Support Engineer
Microsoft Dynamics 365
Customer Services and Support
Manager: Kathy Swallow
Office: +1<PHONE_NUMBER> ext. 2200
rocamp<EMAIL_ADDRESS>Working hours: Monday-Friday 8AM-5PM CST
<EMAIL_ADDRESS>[Microsoft Logo]
From: Jenefer Monroe<EMAIL_ADDRESS>Sent: Thursday, February 25, 2021 2:12 PM
To: microsoft/powerapps-tools<EMAIL_ADDRESS>Cc: Robert Camp<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [microsoft/powerapps-tools] [BUG]: GCC High Error with Pagination Limitation Set to 10000 (#790)
Hello we just confirmed that GCC supports the 10000 pagination so likely you are using a trial license which does not. Thank you for using CoE

You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmicrosoft%2Fpowerapps-tools%2Fissues%2F790%23issuecomment-786170917&data=04|01|Robert.Camp%40microsoft.com|5150035c7fc2480a817608d8d9c9aa4c|72f988bf86f141af91ab2d7cd011db47|1|0|637498807567834755|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=AvV8lerVbqji68%2FEllQM%2FWMVQVPDUcXB6AJ5AJjgsvY%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAROLLHIAFJLPJATGKJF5QY3TA2VKPANCNFSM4YG3ZTQA&data=04|01|Robert.Camp%40microsoft.com|5150035c7fc2480a817608d8d9c9aa4c|72f988bf86f141af91ab2d7cd011db47|1|0|637498807567834755|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=b2MpbwF3xWUlnabLjdBBAzgNxSTkbc37AUWHACsz2rU%3D&reserved=0.

Apologies on my typo, yes we confirmed on GCC High today, but have been able to use these flows on both in the past.


Magic for loading from maven central

Magics for loading from maven central and probably other kind of package repository

Implemented magic %maven group_id:artifact_id:version which is able to load an artifact from a list of public maven repositories with all it's dependencies and add to the class path.


Templated config files

ability to add config files for use when deploying config.
Design to simulate Ansible template files.
Requirements

[ ] can be assigned to software

added 5m of time spent

marked this issue as related to #33


Inconsistency between generated Indvidual and Entity versions – number(ing) of sections

Quoting an e-mail we got discussing the issue:

It seems there is an inconsistency between the generated individual and entity contributor agreements. When selecting "Apache 2.0" as outbound license a paragraph is added to the individual, but not to the entity contributor agreement.
When selecting no commitment for an outbound license, the entity contributor agreement still contains a "4. License obligations by Us", though the numbering of the following paragraphs ignore this paragraph, i.e. there are two paragraphs numbered "4".

so the issue is that even with Outbound License(s) | Not Applicable there is still this section 4in the documents?
entity-contributor-license-agreement-1.1-2019-04-16-21_14_59.pdf
individual-contributor-license-agreement-1.1-2019-04-16-21_14_56.pdf

This is likely the same as #17 as when inserting both documents (and the hidden versions) into the document, IDs are doubled, but jQuery treats them according to spec when selecting by ID, which means only the first one gets selected and thus changed.

It seems there is an inconsistency between the generated individual and entity contributor agreements. When selecting "Apache 2.0" as outbound license a paragraph is added to the individual, but not to the entity contributor agreement.

was fixed in b5343a9ce8b1aa90bfe6f9af1c1c2a7aee7f5597 and b4e57abc0b9eb23fc66db9ec96f08c8befcb2e58

When selecting no commitment for an outbound license, the entity contributor agreement still contains a "4. License obligations by Us", though the numbering of the following paragraphs ignore this paragraph, i.e. there are two paragraphs numbered "4".

I think this was the same as #17 if I understand it correctly. As far a I can tell, there is now no Outbound section in either of the two agreements. Feel free to reopen/comment if I missed something.

I made a quick run and it looks OK, but I did stumble upon an issue where a chosen Documentation license was listed in the summary, but not in the CLA text itself.
Afterwards it even happened that the option to choose the Documentation license did not pop up.
@step21, could you try as well and see if we need to open a new ticket?

I couldn't really replicate this. Could you maybe specify exactly what you chose?

Unfortunately it worked OK the next time. It could have been when I tested it with the FLA default.

Or it might have been still in cache or something. Let me know if you notice it again.


Added resolution to IBM transcription

IBM transcription will now result in ComplexTextStims with TextStim elements that are either words or phrases (user provided argument to the converter). Previously, it partitioned word-by-word only.

Looks good, but can you modify the test for this Extractor to make sure it tests both settings of resolution?

test added 👍


feat: Added more hints on teleports for Lost City

an amulet of glory is pretty helpful for banking before going to entrana, maybe that could be added.


Fix typo

GitHub action -> GitHub Action

@changeworld : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@AlexandraKemperMS,
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.

@jborsecnik I am unable to leave a review but this looks good to me! Ready for sign off


Consider implementing Link prefetching for mobile

Originally posted by @benjaminsehl in https://github.com/Shopify/hydrogen/issues/804#issuecomment-1132068163
I really think it's important that developers have the option to enable this. There are a few ways we could do it though for sure. I can file a new ticket.
Intersection Observer is the strategy that Next.js uses: https://nextjs.org/docs/api-reference/next/link — which is pretty highly regarded in terms of performance.
Remix does "none/intent/render" which for now intent is just hover but they also say they plan on expanding that. They also add <link rel="prefetch"> to the head.
Perhaps a better solution here would be …

none
hover — hover 50ms
auto — hover 50ms, or present via intersection observer for 300ms? (arbitrary) … OR we could possibly do something like the link is fetched more aggressively for purchase path specific routes (collections, products, cart, checkout). We don't have a way to know for sure what routes are what today, but it's worth considering. This may overlap with the named routes idea @jplhomer
always — prefetch it when possible

I'm curious to see how other non-JSX frameworks approach this.

@benjaminsehl is this something you think we should jump into before GA?


sorting by snashot size not working

unable to sort by snapshot Size in snapshot information plugin.it is sorting by default by VM name even after sort-object  SizeGb  is provided.

Did you adapt plugin 02 Snapshot Information?
What did you change and where?
It should be sufficient to add a Sort-Object to the end of the line.
$VM | Get-Snapshot | Where-Object {$_.Created -lt (($Date).AddDays(-$SnapshotAge))} | Get-SnapshotSummary | Where-Object {$_.SnapName -notmatch $excludeName -and $_.Description -notmatch $excludeDesc -and $_.Creator -notmatch $excludeCreator} | Sort-Object -Property SizeGB


[FLINK-7241] Fix YARN high availability documentation

R: @rmetzger (or anyone really)

I would go a bit further in updating this:

The ZooKeeper root node has a default value of /flink (I think). You only need to set this when you want to organize your ZooKeeper node tree in a specific way.

The cluster-id docs should be changed to say that you do not need to set this manually in Yarn / Mesos mode and that it generates a new subtree per launch. You only need to set this if you want to manually recover an earlier HA job (which is different from re-launching the job from a savepoint or externalized checkpoint)

Thanks 👌 Will update

Merged


Document if CAxxxx rule is enabled by default or not

Currently the CAxxxx documentation doesn't include whether the rule is enabled by default or not.
As this changes between releases, the doc may mention the latest version or two.
Currently, we can just include .NET 5.0 only, and later on when .NET 6.0 is released, the doc should include both. Later when .NET 7.0 is released, drop .NET 5.0 and include only .NET 6.0 and .NET 7.0, etc.
If the default for rules change between minor versions, that would still be a problem.
cc: @mavasani @gewarren

related to #20560

Happy to help with the doc change if we agree upon a format/way to state changes depending on version.

@Evangelink Thanks for that offer! I've made a draft PR here. What do you think of adding the default severity to the table at the top of each rule's page?

I think that's perfect for the severity. Maybe we could have a sub-section in case of a version change (fake example, let's say it's Warning in .NET 5 and Info in .NET 6), I'd be in favor of showing both not only latest.
In term of seeing differences by version, I guess that in a perfect world, I'd like to be able to see what/how things changed so that when I am visiting this page for an older version I could see what was the severity at this point. Maybe rather than trying to make too complex things, we should just try to always specify which version adds or change something rather than considering the doc to be a view over the most recent state.
At first I was thinking about having some drop down to select the version and show the page as-is from this "release" but that would be putting a strong limit on how much we can change the UI so I don't like that.

I think that's perfect for the severity. Maybe we could have a sub-section in case of a version change (fake example, let's say it's Warning in .NET 5 and Info in .NET 6), I'd be in favor of showing both not only latest.

Yes if the severity is different in different versions, then we should probably have two rows in the table to differentiate it.

In an ideal world, we would be able to insert the Analyzer releases file into the docs repo and some tooling will extract and auto-populate the severity. This file should also contain the severity change history, rule removal history, etc. with different .NET releases, so has everything that @Evangelink requested above. I am not sure how feasible it is tooling wise to have this automated.


Support float64 for gauges

Requirement
We would like to emit gauge updates with floating numbers (e.g. probabilities)
Problem
The gauge interface in jaeger-lib only supports int64
https://github.com/jaegertracing/jaeger-lib/blob/78a0e7f3cd0c2ab3f747af150d98f534879f09f3/metrics/gauge.go#L18-L21
Implementations like tally, prom, go-kit, influx and expvar support float64 gauges, but jaeger-lib casts the int64 to a float64 value. Is there a reason for this?
https://github.com/jaegertracing/jaeger-lib/blob/78a0e7f3cd0c2ab3f747af150d98f534879f09f3/metrics/prometheus/factory.go#L230-L232
https://github.com/jaegertracing/jaeger-lib/blob/78a0e7f3cd0c2ab3f747af150d98f534879f09f3/metrics/tally/metrics.go#L49-L51
https://github.com/jaegertracing/jaeger-lib/blob/78a0e7f3cd0c2ab3f747af150d98f534879f09f3/metrics/go-kit/metrics.go#L49-L51
Proposal
Update Gauge to use float64 instead of int64 in jaeger-lib 3.0; alternatively jaeger-lib can declare new types GaugeV2, FactoryV2, etc  and create an adaptor.

+1, FactoryV2, FloatGauge
I suspect it's for historical reasons, the old statsd based m3 client didn't support floats.


Generate secrets for workspace

What does this PR do?
This is a draft PR that solves https://github.com/eclipse/che/issues/16647. The general idea is that only new keys will be added to the SecretStore on the cluster
What issues does this PR fix or reference?
https://github.com/devfile/devworkspace-operator/issues/434
Is it tested? How?

tested on crc

Closing this PR since we don't have a plan to finalize it.
Changes should be available in any case here if we later will prioritize https://github.com/devfile/devworkspace-operator/issues/434


[1.15] Build from source fails on Raspberry Pi

System information

OS Platform and Distribution: Archlinux
Mobile device: Raspberry Pi
TensorFlow installed from (source or binary): source
TensorFlow version: 1.15
Python version: 3.8
Installed using virtualenv? pip? conda?: the docker image you provide.
Bazel version (if compiling from source): the one you put in that image.
GCC/Compiler version (if compiling from source): the one you put in the image
CUDA/cuDNN version: No cuda
GPU model and memory: The computer on which Docker runs has 16gb of ram.

Builds fails while compiling. Build log has been attached. Instructions actually mention that one should checkout a known working version but it does not specify where I could discover which version actually builds on raspberry.
The one listed at this documentation page:
CI_DOCKER_EXTRA_PARAMS="-e CI_BUILD_PYTHON=python3 -e CROSSTOOL_PYTHON_INCLUDE_PATH=/usr/include/python3.4" \
tensorflow/tools/ci_build/ci_build.sh PI-PYTHON3 \
tensorflow/tools/ci_build/pi/build_raspberry_pi.sh

Any other info / logs
tensorflow-1.15-docker-raspberry-armhf-build.log.
Actually it just failed on another point, too.
Last part of the latter log:
peStorage; UniquerT = mlir::detail::TypeUniquer]'
external/local_config_mlir/lib/IR/Types.cpp:66:66:   required from here
external/local_config_mlir/include/mlir/Support/StorageUniquer.h:232:34: error: 'getKey' is not a member of 'mlir::detail::OpaqueTypeStorage'
     return ImplTy::getKey(args...);
                                  ^
external/local_config_mlir/include/mlir/Support/StorageUniquer.h: In instantiation of 'static typename std::enable_if<typename mlir::detail::detector<void, mlir::detail::has_impltype_hash_t, ImplTy, DerivedKey>::value_t:: value, llvm::hash_code>::type mlir::StorageUniquer::getHash(unsigned int, const DerivedKey&) [with ImplTy = mlir::detail::OpaqueTypeStorage; DerivedKey = std::pair<mlir::Identifier, llvm::StringRef>; typename std::enable_if<typename mlir::detail::detector<void, mlir::detail::has_impltype_hash_t, ImplTy, DerivedKey>::value_t:: value, llvm::hash_code>::type = llvm::hash_code]':
external/local_config_mlir/include/mlir/Support/StorageUniquer.h:141:59:   required from 'Storage* mlir::StorageUniquer::get(std::function<void(Storage*)>, unsigned int, Arg&&, Args&& ...) [with Storage = mlir::detail::OpaqueTypeStorage; Arg = mlir::Identifier&; Args = {llvm::StringRef&}]'
external/local_config_mlir/include/mlir/IR/TypeSupport.h:104:42:   required from 'static T mlir::detail::TypeUniquer::get(mlir::MLIRContext*, unsigned int, Args&& ...) [with T = mlir::OpaqueType; Args = {mlir::Identifier&, llvm::StringRef&}]'
external/local_config_mlir/include/mlir/IR/StorageUniquerSupport.h:67:64:   required from 'static ConcreteT mlir::detail::StorageUserBase<ConcreteT, BaseT, StorageT, UniquerT>::get(mlir::MLIRContext*, unsigned int, Args ...) [with Args = {mlir::Identifier, llvm::StringRef}; ConcreteT = mlir::OpaqueType; BaseT = mlir::Type; StorageT = mlir::detail::OpaqueTypeStorage; UniquerT = mlir::detail::TypeUniquer]'
external/local_config_mlir/lib/IR/Types.cpp:66:66:   required from here
external/local_config_mlir/include/mlir/Support/StorageUniquer.h:255:63: error: 'hashKey' is not a member of 'mlir::detail::OpaqueTypeStorage'
     return llvm::hash_combine(kind, ImplTy::hashKey(derivedKey));

EDIT 19/12/17: As a temporary workaround I installed PINTO0309's binaries.

Just hit this same issue building PI-PYTHON3, PI_ONE on a Ubuntu 18.04 host build machine.

I believe this issue has to do with the older cross compiler in the 1.15 Pi build (v4.9) which doesn't support all C++14 extensions.  I've worked around the issue by cherry-picking commit 20dfc83d and then building:
git clone https://github.com/tensorflow/tensorflow.git
cd tensorflow/
git checkout v1.15.0
git cherry-pick 20dfc83d

Thanks, @dougyfresh42
I've created PR for the cherry-pick.
https://github.com/tensorflow/tensorflow/pull/39441


PDF converter

Create a PDF conversion tool in html,css and javascript. (tool for converting files to PDF format)

Add navbar in your tool's html file. You can copy the navbar from index.html.
Add screenshot of your tool in, PR message and also in the folder of your tool
Before Making the PR Pull the latest changes that have been made to the repository

**Note: Please Don't Make Any Changes In index.html AND contributors.html **
**Note: Only make changes to the folder that you have created for your tool/utility **
Add the below mention section to your PR message
Title
Number of files/folder added
changes made
check the options that you have completed,
I have;

[ ] Read contibuting.md
[ ] Followed all the guidelines
[ ] Followed the directory Structure
[ ] updated readme.md
[ ] add your name in the footer of your tool.html file (if you created length conversion tool then add your name to length.html file you created)
[ ] provide below mentioned details if you want your name to be added in contributors.html
[ ] mail, twitter, github profile link.

obviously I would take this one ;)

I would love to work on this project

kindly let me know if I can work on it

@ke3peR007 it's already completed. But you can work on another issues always. ✌


doc: release: 3.6: Add note on sysbuild shield fix

Adds a note that the sysbuild shield fix has been applied

Needs rebase

@nordicjm please rebase


Added NETWORKQUALITY to environment and GameUserSettings.ini (default 3)

GameUserSettings.ini has an option for mNetworkQuality.
The games default value here is mNetworkQuality=0.
This refers to the ingame option "Network Quality" with the default value "normal".
I have added an environment variable to run.sh with the default value 3.
This equates to the ingame setting "Ultra"
Source
https://help.akliz.net/docs/common-satisfactory-errors
Unfortunately this option is not documented very well. The NetworkQuality setting is defined in Scalability.ini
TotalNetBandwidth=104857600
MaxDynamicBandwidth=104857600
MinDynamicBandwidth=10485760```
The bandwidth setting helps avoiding sync lags with conveyer belts.

Hey ChalyFlavour, thanks for the PR.
We already set NetworkQuality@3 in the image, see https://github.com/wolveix/satisfactory-server/issues/113#issuecomment-993358035 for more details. Do you have a use case where you actually need configurable network quality?

Closing this per @msladek's comment :) Please feel free to re-open if you have a valid use-case @ChalyFlavour

Hey ChalyFlavour, thanks for the PR.
We already set NetworkQuality@3 (and beyond) in the image, see #113 for more details. Do you have a use case where you actually need configurable network quality?

Hey Marc, thanks for the hint. As you’ve already guessed, I haven’t seen the #113 before committing a pull request.
I don’t have a use case for a configurable network quality as there shouldn’t be any reason to lower: we all should have enough bandwidth for Satisfactory.
However, I had some sync issues with conveyer belts and hyper tubes while CPU wasn’t the reason. So I messed around with Settings starting with network. Every time I changed the NetworkQuality to 3, my problems were solved while reverting to default brought back the lag.
I’m fine with using my fork, if you don’t want to have the configurable network setting in your image. I just thought, it won’t blow it up too much.
I have trouble adding a technical prove for this one. The average CPU usage on the dedicated server raised with setting 3 and my lags were gone. Some info from the devs would be of help. Maybe some servers code relays on the NetworkQuality setting instead of the bandwidth, dunno.

Hey @ChalyFlavour, that's certainly interesting to hear!
Your comment just prompted me to investigate this further. I noticed that we actually specify mNetworkQuality=0 in GameUserSettings.ini 🤦♂ So while we increase the bandwidth allocations for quality 3 (per @msladek's comment), we actually drop to quality 0 due to this mistake.
I'll push a fix to your repo, and merge this PR :) Thanks for bringing this to our attention!

Ah, darn it, didn’t notice the @3 in [NetworkQuality@3] myself. I was so fixed to the gamesettings that I missed that the Scalability didn’t match it.
Sorry, I’d have mentioned it in my first PR otherwise. The fallback to low quality totally explains the experience I had.
thanks for merging 🖖


MAXO:0035016 has a space at end of IRI

optical coherence tomography has IRI <http://purl.obolibrary.org/obo/MAXO_0035016 >. Similar to #542.

fixed


How to get access to ingress controller

What is the best way to get access to service in cluster through ingress-controller ? I used to use hostNetwork: true for ingress-controller in typical kubernetes bootstraped by kubeadm. Is it possible on rootless kubernetes ?
Another way is to expose nodeport of ingress-controller service
Now i'm using it by opening port with socat command
pid=$(cat $XDG_RUNTIME_DIR/usernetes/rootlesskit/child_pid)
socat -t -- TCP-LISTEN:30080,reuseaddr,fork EXEC:"nsenter -U -n -t $pid socat -t -- STDIN TCP4\:<IP_ADDRESS>\:30080"

I need more automated way. Maybe i have to create systemd service which execute  this command?
If i try to use rootlessctl i get the error.  How can I solve it?
 ./rootlessctl add-ports <IP_ADDRESS>:30080:30080/tcp
error: please specify --socket or set $ROOTLESSKIT_STATE_DIR

rootlessctl

Please try this
https://github.com/rootless-containers/usernetes/blob/master/rootlessctl.sh


queryBuilderClass:  parameter in .neon is not enough when several sub-class of querybuilder

first thanks for this awesome project and all the time you're putting into it, having DQL validation is just mind blowing.
related to #243 we have in our project several subclass of  Querybuilder (for some entities) in order to add helper method in a fluent way
like
use Doctrine\ORM\QueryBuilder;

class AdvancePaymentQueryBuilder extends QueryBuilder
{

    public function forCurrentPayPeriod(Company $company): self
    {
        $this
            ->andWhere('a.payPeriod = :payPeriod')
            ->setParameter('payPeriod', $company->getCurrentPayPeriod()->format('Y-m-d 00:00:00+00'))
        ;

        return $this;
    }
}

and phpstan-doctrine does not recognize them to validate DQL, and as we have several of them, and also we often use the base querybuilder ,  we can't simply use the queryBuilderClass property in phpstan.neon

If you remove the queryBuilderClass custom setting completely, what kind of errors are you experiencing in your codebase, along with some code samples? Thanks.

@ondrejmirtes  actually, i have nothing set right now, sorry if my previous message was ambigous,  I was saying that at first I thought it could have helped but not as it is limited to 1 class.
For error messages,  I don't have any, which is actually my problem,  as it that phpstan is ignoring DQL made with these sub-class, and so does not detect syntax error in the DQL that are normally caught when using the standard query builder.
I will put together a reproducing example tomorrow


Article props don't match model

The Article component props don't entirely match the model and graphql.   These inconsistencies need to be resolved.

We have added a post Boolean to Article and dropped the urlToImage.


CORE-16388 Removal of old 'InteropAliasProcessor' and redundant supporting classes

Changes

Delete interop alias processor.

@szymonsztuka This ended up being very simple, I can't see any other references to the deleted code, let me know if there is anything you think I have missed.


"You are browsing an outdated version of the documentation"

Display a warning on top of every doc page when the user is not seeing the most recent version of the documentation. Include a link to the most recent version.

@jitachi Do you have guidelines or a mockup to implement this? Thanks

we already have the yellow alert box, makes sense to use here.

I feel like the warning should be stronger.

like a red-ish color?
sure, maybe. the rest of the style of the alert box works as is though.

We'll see when we'll implement it when we'll have another version out


Remove deprecated az aks --docker-bridge-address option

The instructions for creating a private AKS cluster with az aks create specify a --docker-bridge-address option; however, with azure-cli 2.57.0 this option results in the warning:
Option '--docker-bridge-address' has been deprecated and will be removed in a future release.

This PR suggests removing mention of --docker-bridge-address in the documentation.
Related: https://github.com/Azure/AKS/issues/3534

@MGoedtel
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


export map option is not working

The "Export Map" option seems not to be working, is not exporting the map and in the network section of the dev tools, is not displaying any request when the "Export Map" option is selected.
It is happening with any map that you open in CARTO. (with one or more layers)

Basically, option is not doing anything :(.


build: custom-vet-check should respect make variable GO

With this change, the custom vet check respects the make variable GO which might point to a custom Go installation.
Otherwise, custom vetting fails because the default Go  installation is used.

/test

/test-runtime

/ci-verifier


React-native camera not working

Since React-native camera is deprecated (https://github.com/react-native-camera/react-native-camera). So now this library isn't working.
How can I make it run?

This library does not directly depend on react-native-camera. So this deprecation is not affecting it.

I am not able to run this project. If I try running your code I end up with multiple issues
In Android:

Firstly, I ran into cvc-complex-type.2.4.a: Invalid content was found starting with element 'base-extension'. One of '{codename, tag}' is expected. issues.
After resolving them I had compile issues

Are you rinning an example project in example folder?

yes

Sounds like you need to replase compile with implementation.
https://stackoverflow.com/questions/69044250/build-gradle-error-could-not-get-unknown-property-compile

Even after changing this, there were various issues. Currently, I am getting gradle issue. Even after I have added MavenCentral

Could not find com.android.tools.build:gradle:7.4.0.
Searched in the following locations:

https://jcenter.bintray.com/com/android/tools/build/gradle/7.4.0/gradle-7.4.0.pom
https://repo.maven.apache.org/maven2/com/android/tools/build/gradle/7.4.0/gradle-7.4.0.pom
Required by:
project :opencv
Add google Maven repository and sync project
Open File

It says in your error message to add google Maven repository. Have you tried that?


Hydro torus segfaults on GPU

<fluid>/mhd = False is unsupported for the torus problem right now. cuda-gdb suggests the issue is in ApplyFloors somewhere.

Fixed at some point.


Install procedure OSX/Mac and GenTL Producers

Could you please clarify how to install the GenTL producer in OSX? In the installation instructions you suggest to install mvIMPACT_Acquire from http://static.matrix-vision.com/mvIMPACT_Acquire/2.29.0/ but inside the directory there is not mvIMPACT_Acquire installer, only debug symbols files.
Another question is regarding the GenTL, you suggest to use Matrix Vision GenTL, will this work for any camera o will I need a specific GenTL file from the specific manufacturer? Thanks a lot for your work.

Hi. (1) MATRIX VISION does not support macOS. (2) Their GenTL Producer works with any GenICam compliant U3V or GEV camera as far as I know. I tend to suggest people to use their producer but please note that other manufacturers also produce their own excellent ones. You should know that this is also a valid option to use your camera manufacturer's GenTL Producer to keep your lifeline available. -Kazunari

Thanks a lot for your answer. Any recommendation for OSX? I've check JAI and Stemmer and none provide OSX producers (as far as I understand).

Let me list a few just for your information: Probably OMRON Sentech. Basler might support macOS for U3V, too. However, they would block other 3rd party cameras.

Thanks again, I am starting to realise that Max/OSX might not be the best option to work with this cameras anyway.

Hello I am having the same issue on Mac. Did you make it ?

@ducciopiovani Hi, thank you for being interested in Harvester. I am afraid but I am not a person who develops GenTL Producers. However, I could tell you more or less practical: The machine vision market should be smaller than you expect. It means just making an inquiry to those possible software manufacturers (or camera manufactures) of 10 or so then you could get an answer you would like to hear. Some of them might just avoid to publicly announce that they have macOS GenTL Producer. /Kazunari


Update Pages “about”

Automatically generated by Netlify CMS

👷 Deploy Preview for docbracing processing.

Name
Link

🔨 Latest commit
613d040c37f5468d7a08e9136b1358c8520c7196

🔍 Latest deploy log
https://app.netlify.com/sites/docbracing/deploys/650ec8437da35600083145ee


Cannot include two files with the same name

Hello everyone,
I am trying to publish my AsciiDoc to Confluence using your publisher tool. I received an error due to having an index.adoc in various directories:
Exception in thread "main" java.lang.IllegalStateException: Duplicate key index.adoc (attempted merging values /builds/pi-cloud/cicd/pipeline-templates/target/confluence/assets/72825d851c49074e43f78fd843dcfd132709287059941cbc019652e073d632e6/index.adoc and /builds/pi-cloud/cicd/pipeline-templates/target/confluence/assets/72825d851c49074e43f78fd843dcfd132709287059941cbc019652e073d632e6/index.adoc)
	at java.base/java.util.stream.Collectors.duplicateKeyException(Collectors.java:133)
	at java.base/java.util.stream.Collectors.lambda$uniqKeysMapAccumulator$1(Collectors.java:180)
	at java.base/java.util.stream.ReduceOps$3ReducingSink.accept(ReduceOps.java:169)
	at java.base/java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1655)
	at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484)
	at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
	at java.base/java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:913)
	at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
	at java.base/java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:578)
	at org.sahli.asciidoc.confluence.publisher.converter.AsciidocConfluenceConverter.toTargetAttachmentFileNameAndAttachmentPath(AsciidocConfluenceConverter.java:158)
	at org.sahli.asciidoc.confluence.publisher.converter.AsciidocConfluenceConverter.buildConfluencePageMetadata(AsciidocConfluenceConverter.java:128)
	at org.sahli.asciidoc.confluence.publisher.converter.AsciidocConfluenceConverter.lambda$buildPageTree$0(AsciidocConfluenceConverter.java:103)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at org.sahli.asciidoc.confluence.publisher.converter.AsciidocConfluenceConverter.buildPageTree(AsciidocConfluenceConverter.java:91)
	at org.sahli.asciidoc.confluence.publisher.converter.AsciidocConfluenceConverter.convert(AsciidocConfluenceConverter.java:78)
	at org.sahli.asciidoc.confluence.publisher.cli.AsciidocConfluencePublisherCommandLineClient.main(AsciidocConfluencePublisherCommandLineClient.java:100)

I briefly looked into AsciidocConfluenceConverter. You seem to flatten all attachments by there filename into one directory. Is it intended that there cannot be more than one file with the same filename?
Have a good day :)

Hi @maha-SOPTIM, thank you for reporting your issue. Could you please quickly outline your source directory layout (the relevant parts) to be sure to understand the situation correctly? Or if possible, describe the minimum layout that triggers the issue? Thank you!

Hi @cstettler, I am hosting my repo on a private GitLab-Instance where I put an index.adoc file in most sub-directories. I got a top-level index.adoc file which is linking to the described index.adoc files. Sadly, thay have to be named index.adoc to be shown by gitlab when viewing the directory (similar to README.md files).
This could be an example tree to reproduce it:
.
├── index.adoc # This links to docs-for-docker/index.adoc and docs-for-helm/index.adoc
├── docs-for-docker/
│   └── index.adoc
└── docs-for-helm/
    └── index.adoc

Hope that helps :)

Hi @maha-SOPTIM, thank you for your feedback. In your example, only the top-level index.adoc will be published since the Confluence Publisher requires a specific documentation source structure to derive the page hierarchy in Confluence (please see https://confluence-publisher.atlassian.net/wiki/spaces/CPD/overview, section Documentation Source Structure). Therefore, I am not able to reproduce your issue. Even when adding a docs-for-docker.adoc and docs-for-helm.adoc file (which leads to the two index.adoc files in the subfolder to be published) no error occurs.
What do you mean with "This links to docs-for-docker/index.adoc and docs-for-helm/index.adoc"? Is this a cross-page link, or maybe an include? It would be great if you could post a down-striped, anonymised example to reproduce and investigate the issue. Thank you for clarifying!

Ich just did not see the documentation of the page structure. This fixed my issue. Thank you very much!
Kind Regards


Removed switch/case construction

I added back the case statement for a couple reasons.

Metaprogramming is a more advanced topic that increases the complexity of this example code.
A switch statement is easy to understand and follow. It also has the benefit of explicitly listing the
valid options.
The metaprogramming approach produces unwieldy errors when a user supplies an invalid object name.

@nslocum So, but with switch/case construction it is not realization of factory:
see https://github.com/nslocum/design-patterns-in-ruby/issues/32


espressif: Update HAL library reference to include debug assert

Summary

espressif: Update HAL library reference to include debug assert

During the board bringup, the new HAL reference includes an assert to check if the critical section flags are being stored as expected.
Impact
Prevent losing the interrupt context between nested calls to enter/leave a critical section
Testing
Internal CI testing

@xiaoxiang781216 , any idea about the failing tests on CI? It seems unrelated to this PR...

@xiaoxiang781216 , any idea about the failing tests on CI? It seems unrelated to this PR...

i filed an issue
https://github.com/apache/nuttx/issues/13246


Compatibility issues with bagnon - Escape input ignored ?

Heya ! thanks for the addon, it looks cool, just a small list of issues I've found:

Autodelete and Shard manager do not seem to be compatible with Bagnon. The AutoDelete popup only shows if triggering a Bagnon's "clean items" function:

Even then, the AutoDelete function does not work, clicking the button does nothing:

Similarly, none of the functions of the shard manager seem to work.
-Esc does not work to close open menus. I don't know if it's by design, but I prefer to use esc to close menus, and the mod seems to be ignoring this unput completly.

Appreciate the feedback, previously this did work with Bagnon. Unfortunately this addon is no longer being actively maintained, I will mark the repo as archived and update the readme.


[cinder-csi-plugin] Cinder CSI plugin should not provision ROX or RWX volumes

/kind bug
What happened:
When creating a PVC with ROX or RWX access mode, the volume provisioned successfully, but when creating pods assigned to different nodes, it got attach failure.
What you expected to happen:
We should show out the unsupport message as cinder in-tree plugin does:
Warning ProvisioningFailed 7s (x3 over 14s) persistentvolume-controller Failed to provision volume with StorageClass "standard": invalid AccessModes [ReadWriteMany]: only AccessModes [ReadWriteOnce] are supported
How to reproduce it:

Install OSP cluster and cinder csi driver is installed.

Create PVC with ROX/RWX access mode, and create pod to consume it.

Check the pod and pvc statuses

Create another pod which assigned to another node

Volume provisioned successfully
$ oc get pvc -n wduan
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
mypvc02 Bound pvc-ae09e478-2b8e-4350-a83a-b789ff991d7d 1Gi RWX standard-csi 17m

$ oc get pvc -n wduan-01
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
mypvc03 Bound pvc-9404f88c-d437-493b-ba5e-3a2685cdc1c9 1Gi ROX standard-csi 14m

Attach failed when creating another pod assigned to another node
Warning FailedAttachVolume 12s attachdetach-controller AttachVolume.Attach failed for volume "pvc-ae09e478-2b8e-4350-a83a-b789ff991d7d" : rpc error: code = Internal desc = [ControllerPublishVolume] Attach Volume failed with error failed to attach ccc11e8b-cfff-40ac-92da-d7baed902b12 volume to fa6d2e8c-eb8f-4a57-a54a-5063f2b8bec7 compute: Bad request with: [POST https://rhos-d.infra.prod.upshift.rdu2.redhat.com:13774/v2.1/servers/fa6d2e8c-eb8f-4a57-a54a-5063f2b8bec7/os-volume_attachments], error message: {"badRequest": {"message": "Invalid input received: Invalid volume: Volume ccc11e8b-cfff-40ac-92da-d7baed902b12 status must be available or downloading (HTTP 400) (Request-ID: req-75c01a31-c877-4582-930e-35c5d8b64eaf)", "code": 400}}

@Fedosin which version of plugin you are using?

@Fedosin which version of plugin you are using?

@Fedosin I saw another node and another pod, to confirm, it's not caused by multiple nodes or pods
just ROX is not supported by CSI cinder so we want to reject that create action during creation stage because ROX is not supposed to be supported?

@Fedosin I saw another node and another pod, to confirm, it's not caused by multiple nodes or pods
just ROX is not supported by CSI cinder so we want to reject that create action during creation stage because ROX is not supposed to be supported?

This is our code https://github.com/openshift/cloud-provider-openstack
We are slightly behind the master (the rebase happened on Nov, 26), but I don't see what could fix the issue after that.

This is our code https://github.com/openshift/cloud-provider-openstack
We are slightly behind the master (the rebase happened on Nov, 26), but I don't see what could fix the issue after that.

@ramineni I think @Fedosin means he is using openshift master and encounter this issue
@Fedosin please help to confirm , if that's true, then this is something we need fix

@ramineni I think @Fedosin means he is using openshift master and encounter this issue
@Fedosin please help to confirm , if that's true, then this is something we need fix

@Fedosin Did you specify volume type is storage class as multiattach , and volume created in cinder have the property multiattach=True?

@Fedosin Did you specify volume type is storage class as multiattach , and volume created in cinder have the property multiattach=True?

Hi @ramineni, the issue occurs when asking for ROX or RWX access mode but the backend doesn't support multiattach. In this case, cinder CSI should not provision the volume but return an error because it won't be able to honor the required access mode.
See the following example:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: mydeploy03
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hello-cinder
  template:
    metadata:
      labels:
        app: hello-cinder
    spec:
      containers:
      - name: hello-openshift
        image: docker.io/aosqe/storage@sha256:a05b96d373be86f46e76817487027a7f5b8b5f87c0ac18a246b018df11529b40
        ports:
        - containerPort: 80
        volumeMounts:
        - name: local
          mountPath: /mnt/local
      volumes:
      - name: local
        persistentVolumeClaim:
          claimName: mydep-pvc03

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mydep-pvc03
spec:
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 1Gi
  storageClassName: standard-csi

The PV shows RWX access mode:
psi ❯ oc get pv -A
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                 STORAGECLASS   REASON   AGE
pvc-00cc5aec-a183-45fd-b222-9dcc219d26cb   1Gi        RWX            Delete           Bound    default/mydep-pvc03   standard-csi            37s

However, the volume doesn't support multi-attach:
psi ❯ openstack volume show dfab6c07-55ee-4804-a1f5-fdb61d647686
+------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field                        | Value                                                                                |
+------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| attachments                  | [{'id': 'dfab6c07-55ee-4804-a1f5-fdb61d647686', 'attachment_id': 'b1836bf2-8df4-4447-8889-9de3012603b5', 'volume_id': 'dfab6c07-55ee-4804-a1f5-fdb61d647686', 'server_id': 'a04d19e9-19d7-43aa-bc06-7ccf372534c5', 'host_name': 'compute-ci-d-036.localdomain', 'device': '/dev/vdb', 'attached_at': '2021-01-18T08:17:44.000000'}] |
| availability_zone            | nova                                                                                |
| bootable                     | false                                                                                |
| consistencygroup_id          | None                                                                                |
| created_at                   | 2021-01-18T08:17:41.000000                                                                                |
| description                  | Created by OpenStack Cinder CSI driver                                                                                |
| encrypted                    | False                                                                                |
| id                           | dfab6c07-55ee-4804-a1f5-fdb61d647686                                                                                |
| multiattach                  | False                                                                                |
| name                         | pvc-00cc5aec-a183-45fd-b222-9dcc219d26cb                                                                                |
| os-vol-tenant-attr:tenant_id | c73b7097d07c46f78eb4b4dcfbac5ca8                                                                                |
| properties                   | cinder.csi.openstack.org/cluster='kubernetes'                                                                                |
| replication_status           | None                                                                                |
| size                         | 1                                                                                |
| snapshot_id                  | None                                                                                |
| source_volid                 | None                                                                                |
| status                       | in-use                                                                                |
| type                         | tripleo                                                                                |
| updated_at                   | 2021-01-18T08:17:45.000000                                                                                |
| user_id                      | c58a5aa7bf2df7c49420a43898f9b1df39bff9ee0b7dc240a2aa975c910750a5                                                                                |
+------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Do you think it's enough to chesk the volume capabilities in CreateVolume() like @Fedosin did in https://github.com/kubernetes/cloud-provider-openstack/pull/1368/ ?

Hi @ramineni, the issue occurs when asking for ROX or RWX access mode but the backend doesn't support multiattach. In this case, cinder CSI should not provision the volume but return an error because it won't be able to honor the required access mode.
See the following example:
apiVersion: apps/v1
kind: Deployment
metadata:
  name: mydeploy03
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hello-cinder
  template:
    metadata:
      labels:
        app: hello-cinder
    spec:
      containers:
      - name: hello-openshift
        image: docker.io/aosqe/storage@sha256:a05b96d373be86f46e76817487027a7f5b8b5f87c0ac18a246b018df11529b40
        ports:
        - containerPort: 80
        volumeMounts:
        - name: local
          mountPath: /mnt/local
      volumes:
      - name: local
        persistentVolumeClaim:
          claimName: mydep-pvc03

---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mydep-pvc03
spec:
  accessModes:
  - ReadWriteMany
  resources:
    requests:
      storage: 1Gi
  storageClassName: standard-csi

The PV shows RWX access mode:
psi ❯ oc get pv -A
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                 STORAGECLASS   REASON   AGE
pvc-00cc5aec-a183-45fd-b222-9dcc219d26cb   1Gi        RWX            Delete           Bound    default/mydep-pvc03   standard-csi            37s

However, the volume doesn't support multi-attach:
psi ❯ openstack volume show dfab6c07-55ee-4804-a1f5-fdb61d647686
+------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Field                        | Value                                                                                |
+------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| attachments                  | [{'id': 'dfab6c07-55ee-4804-a1f5-fdb61d647686', 'attachment_id': 'b1836bf2-8df4-4447-8889-9de3012603b5', 'volume_id': 'dfab6c07-55ee-4804-a1f5-fdb61d647686', 'server_id': 'a04d19e9-19d7-43aa-bc06-7ccf372534c5', 'host_name': 'compute-ci-d-036.localdomain', 'device': '/dev/vdb', 'attached_at': '2021-01-18T08:17:44.000000'}] |
| availability_zone            | nova                                                                                |
| bootable                     | false                                                                                |
| consistencygroup_id          | None                                                                                |
| created_at                   | 2021-01-18T08:17:41.000000                                                                                |
| description                  | Created by OpenStack Cinder CSI driver                                                                                |
| encrypted                    | False                                                                                |
| id                           | dfab6c07-55ee-4804-a1f5-fdb61d647686                                                                                |
| multiattach                  | False                                                                                |
| name                         | pvc-00cc5aec-a183-45fd-b222-9dcc219d26cb                                                                                |
| os-vol-tenant-attr:tenant_id | c73b7097d07c46f78eb4b4dcfbac5ca8                                                                                |
| properties                   | cinder.csi.openstack.org/cluster='kubernetes'                                                                                |
| replication_status           | None                                                                                |
| size                         | 1                                                                                |
| snapshot_id                  | None                                                                                |
| source_volid                 | None                                                                                |
| status                       | in-use                                                                                |
| type                         | tripleo                                                                                |
| updated_at                   | 2021-01-18T08:17:45.000000                                                                                |
| user_id                      | c58a5aa7bf2df7c49420a43898f9b1df39bff9ee0b7dc240a2aa975c910750a5                                                                                |
+------------------------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Do you think it's enough to chesk the volume capabilities in CreateVolume() like @Fedosin did in https://github.com/kubernetes/cloud-provider-openstack/pull/1368/ ?

@mandre Thanks for the explanation. But PR #1368 blocks creation , irrespective of backend supports or not. If backend supports and user would like create a volume with volume type of multiattach , he should be able to use it.

@mandre Thanks for the explanation. But PR #1368 blocks creation , irrespective of backend supports or not. If backend supports and user would like create a volume with volume type of multiattach , he should be able to use it.

There seem to be multiple problems here:

the cinder CSI driver only reports the VolumeCapability_AccessMode_SINGLE_NODE_WRITER volume capability independently of what the backend really supports.
CreateVolume() doesn't check that the requested volume capabilities match the supported ones.

Is there a way for the cinder driver to discover what the backend really supports?
Just to make sure I understand correctly: #1368 fixes the second issue, but is not acceptable in its current form because, due to the first issue, this would prevent the Multi-Attach feature ?

There seem to be multiple problems here:

the cinder CSI driver only reports the VolumeCapability_AccessMode_SINGLE_NODE_WRITER volume capability independently of what the backend really supports.
CreateVolume() doesn't check that the requested volume capabilities match the supported ones.

Is there a way for the cinder driver to discover what the backend really supports?
Just to make sure I understand correctly: #1368 fixes the second issue, but is not acceptable in its current form because, due to the first issue, this would prevent the Multi-Attach feature ?

Just to make sure I understand correctly: #1368 fixes the second issue, but is not acceptable in its current form because, due to the first issue, this would prevent the Multi-Attach feature ?
@mandre right.

Just to make sure I understand correctly: #1368 fixes the second issue, but is not acceptable in its current form because, due to the first issue, this would prevent the Multi-Attach feature ?
@mandre right.

Is there a way to discover what capabilities the backend supports?

Is there a way to discover what capabilities the backend supports?

@mandre , right now, we only check volume.multiattach flag , to check volume is capable of multiattach or not. It requires admin to configure correct volume type while creating volume.

@mandre , right now, we only check volume.multiattach flag , to check volume is capable of multiattach or not. It requires admin to configure correct volume type while creating volume.

'multiattach' is an extra_spec on the volume type. We should be able to check that.

Incidentally, although the published api docs don't say so there's at least 1 code comment suggesting that volume.multiattach is deprecated:
https://opendev.org/openstack/cinder/src/commit/355681cd53fbb2f5fd2c4cecb55a83c5e0c27c2c/cinder/volume/flows/api/create_volume.py#L434-L436
I don't know how likely it is to go away in practise, but it seems prudent to use the extra_spec on the type rather than the field on the volume.

multi-attach is not by itself sufficient for safe RWX when using block storage like cinder.  You also need to make sure to set volumeMode = 'Block in your PVC', which was introduced as a beta feature in k8s 1.13 [1]  Not doing this setting or setting "Filesystem" gets you traditional behavior where ks expects to either find a filesystem or it will create an xfs or ext4 filesystem before making it available to applications.  These are node local file systems and it is not safe to mount them on multiple nodes in the cluster, even read only (read only mounts still write file system metadata).
So Cinder and other block based PVs with RWX is really for applications like some databases that work with raw block devices, read and write to block offsets rather than to posix filesystem paths, and that do their own coordination/write arbitration when there are multiple writers rather than relying on a filesystem for this function.
When you do multiple attaches of a Cinder block volume in OpenStack neither Cinder nor Nova builds a file system on the block volume so the traditional k8s behavior of imposing a node local filesystem is not an issue.  The owner of Nova guest VMs with multiple attaches to the same volume can make this mistake, but OpenStack itself will not put them in this predicament.
[1] https://kubernetes.io/blog/2019/03/07/raw-block-volume-support-to-beta/

For completeness, I wrote up what I believe should be the logic here: https://github.com/kubernetes/cloud-provider-openstack/pull/1368#issuecomment-818831513

I commented in #1368 that to my knowledge Cinder provides no way for a regular user (member with project scoped keystone role) to discover the multiattach extra spec in volume types.  IMO that is a deficiency that Cinder should address (PTG topic?  capabilities discovery has come up before in Cinder but to my knowledge was never resolved).  (FWIW, in Manila we distinguish between traditional, private extra-specs which have back end details that are not the business of regular users and public extra-specs, which can be used by regular users for capability discovery)

/remove-lifecycle stale

Cinder spec: https://specs.openstack.org/openstack/cinder-specs/specs/xena/expose-cinder-user-visible-extra-specs-spec.html
Cinder implementation (WIP): https://review.opendev.org/c/openstack/cinder/+/797170

/remove-lifecycle stale


Implemented login and signup for client side

This pull request solves issue #45  and is ready for review

#45
Add login and signup page on client side

Hey @rahul-2004-json, if you need any help let me know

I had some problem accessing the login page and signup page routes so I did it manually I don't know why default folder route functionality is not working in next js. I tried fixing in server also but didn't work.
I don't know where I am doing it wrong

I had some problem accessing the login page and signup page routes so I did it manually I don't know why default folder route functionality is not working in next js. I tried fixing in server also but didn't work. I don't know where I am doing it wrong Pls let me know about fix for accessing those pages.

Wait I will check it should work

Hey @rahul-2004-json, The issue is with folder structure.
Your current folder structure:

Folder structure should be like this:

It will looks like this after changing folder structure:

I had some problem accessing the login page and signup page routes so I did it manually I don't know why default folder route functionality is not working in next js. I tried fixing in server also but didn't work.
I don't know where I am doing it wrong

Thanks @abhijeetnishal for helping with route related problem ,I will implement the changes mentioned in pull request review.

Hey @rahul-2004-json, The issue is with folder structure.
Your current folder structure:
Folder structure should be like this:
It will looks like this after changing folder structure:
Try to make changes it will work and let me know if you need some help

I made changes as you suggested but don't know why I am not able to access that route .. my server is up and running

Hey @rahul-2004-json, just go to the route as mentioned in the output image

Hi @abhijeetnishal
I hope this message finds you well.
I wanted to inform you that due to my ongoing exams and my most of the time going into preparation, I am currently unable to contribute to the project. If you need to assign the particular issue I was working on to someone else to ensure the project's progress, please feel free to do so. I don't want the progress to be halted because of me.
The last pull request I made had changes which you told me to do , you can continue from there if feel it's right.
Thank you for your understanding.

Hey @rahul-2004-json, I guess you closed all the PR, could you create a PR and push the changes have you done till now. I will review

Best of luck for your exams.

Hey @rahul-2004-json, I guess you closed all the PR, could you create a PR and push the changes have you done till now. I will review

I made a pull request #101 . Please check !

Hey @rahul-2004-json, I guess you closed all the PR, could you create a PR and push the changes have you done till now. I will review

I made a pull request #101 . Please check !

Great I will review and merge to development branch so you become contributer of the project as I don't want your hard work wasted.

Hey @rahul-2004-json, I guess you closed all the PR, could you create a PR and push the changes have you done till now. I will review

I made a pull request #101 . Please check !

Great I will review and merge to development branch so you become contributer of the project as I don't want your hard work wasted.

Thank you soo much @abhijeetnishal for this kind gesture.
You were really patient, understanding and humble project owner I worked with ❤

No problem @rahul-2004-json, i understand.
Thanks for your kind words 😊
If you need any help in future, let me know. My discord id is - @abhijeetnishal


#2180 - Assessment Workflow Enqueuer Scheduler - Start Assessment-  E2E tests

Create a  few E2E tests for the new schedler.

Should queue an assessment when an active application has only the original assessment and it is in 'Submitted' state. (119 ms)
Should queue the oldest pending reassessment when an active application has one completed original assessment and multiple submitted reassessments queued. (145 ms)
Should not queue a 'Submitted' assessment if the another assessment has its status as 'Queued' (99 ms)
Should not queue a 'Submitted' assessment if the another assessment has its status as 'In progress' (101 ms)
Should not queue a 'Submitted' assessment if currentAssessment and currentProcessingAssessment are the same already. (96 ms)

Created a method to centralize the mock name creation and allow retrieve the mock to execute tests like toBeCalledWith.

startApplicationAssessmentQueueMock = app.get(
    getQueueProviderName(QueueNames.StartApplicationAssessment),
);

expect(startApplicationAssessmentQueueMock.add).toBeCalledWith(queueData);

Great work.  One clarification and one minor question.


create_if_not_exists with index doesn't work with concurrently

Environment

Elixir version (elixir -v): 1.6.1
Database and version (PostgreSQL 9.4, MongoDB 3.2, etc.): Postgres 10.1
Ecto version (mix deps): 2.2.8
Database adapter and version (mix deps): Postgrex 0.13.4
Operating system: MacOS High Sierra

Current behavior
I'm trying to add indexes conditionally to a very large table and have created the following migration:
defmodule PixelMetrics.Repo.Migrations.AddIndexesToForeignKeysOnActionsTable do
  use Ecto.Migration
  @disable_ddl_transaction true

  def change do
    create_if_not_exists(index("actions", [:app_id], concurrently: true))
  end
end

Running mix ecto.migrate throws because the migration is being run in a transaction, though @disable_ddl_transactionis set totrue`. Here's that stack trace:
[info] == Running PixelMetrics.Repo.Migrations.AddIndexesToForeignKeysOnActionsTable.change/0 forward
[info] create index if not exists actions_store_id_index
** (Postgrex.Error) ERROR 25001 (active_sql_transaction): CREATE INDEX CONCURRENTLY cannot run inside a transaction block
    (ecto) lib/ecto/adapters/sql.ex:200: Ecto.Adapters.SQL.query!/5
    (ecto) lib/ecto/adapters/postgres.ex:85: anonymous fn/4 in Ecto.Adapters.Postgres.execute_ddl/3
    (elixir) lib/enum.ex:1899: Enum."-reduce/3-lists^foldl/2-0-"/3
    (ecto) lib/ecto/adapters/postgres.ex:85: Ecto.Adapters.Postgres.execute_ddl/3
    (ecto) lib/ecto/migration/runner.ex:104: anonymous fn/2 in Ecto.Migration.Runner.flush/0
    (elixir) lib/enum.ex:1899: Enum."-reduce/3-lists^foldl/2-0-"/3
    (ecto) lib/ecto/migration/runner.ex:102: Ecto.Migration.Runner.flush/0
    (stdlib) timer.erl:181: :timer.tc/2
    (ecto) lib/ecto/migration/runner.ex:26: Ecto.Migration.Runner.run/6
    (ecto) lib/ecto/migrator.ex:128: Ecto.Migrator.attempt/6
    (ecto) lib/ecto/migrator.ex:73: anonymous fn/4 in Ecto.Migrator.do_up/4
    (ecto) lib/ecto/migrator.ex:261: anonymous fn/4 in Ecto.Migrator.migrate/4
    (elixir) lib/enum.ex:1294: Enum."-map/2-lists^map/1-0-"/2
    (ecto) lib/mix/tasks/ecto.migrate.ex:83: anonymous fn/4 in Mix.Tasks.Ecto.Migrate.run/2
    (elixir) lib/enum.ex:737: Enum."-each/2-lists^foreach/1-0-"/2
    (elixir) lib/enum.ex:737: Enum.each/2
    (mix) lib/mix/task.ex:314: Mix.Task.run_task/3
    (mix) lib/mix/cli.ex:80: Mix.CLI.run_task/2

Expected behavior
The migration runs outside a transaction. ;)

@matthewlehner could you please investigate? According to the test we were supposed to detect it just fine: https://github.com/elixir-ecto/ecto/blob/v2.2.8/lib/ecto/migrator.ex#L114-L123
So we are missing something somewhere.

In case you can't further pin it down, a minimal app that reproduces the issue would help us a lot, as most of the time fixing bugs is actually spent on reproducing them. :)

Here you go!
https://github.com/matthewlehner/concurrent_indexes
From my precursory trace through the logic, it looks like it does hit Ecto.Migrator.run_maybe_in_transaction/3 and runs fun.() under the true condition, not module.__migration__[:disable_ddl_transaction].
Beyond that, I got lost… Also, maybe don't rely on what I've said above, I'm not familiar enough with how macros result in this code to be super confident in my diagnosis and got to this point by adding IEx.pry() in the function.

Just dug in a bit more, and I think it's this?
https://github.com/elixir-ecto/ecto/blob/7d6dfe7dc43ae39ab5ccc3a42fd49682b7ccf418/lib/ecto/adapters/postgres/connection.ex#L645-L649

Good catch. This stack overflow post has more information about it: https://dba.stackexchange.com/questions/35616/create-index-if-it-does-not-exist
The proper statement that works with CONCURRENTLY is only available on Postgres 9.5 which is quite recent, so I don't feel like we should impose it onto users.
My suggestion is for you to run this particular command at the SQL level:
execute "CREATE INDEX CONCURRENTLY IF NOT EXISTS ...."

I am pretty sure this works now. The following (slightly doctored 😄) has shown to work locally using Postgres.
defmodule MyApp.Repo.Migrations.CreateFooNumbersGinIndexes do
  use Ecto.Migration
  @disable_ddl_transaction true
  @disable_migration_lock true

  def change do
    execute "CREATE EXTENSION IF NOT EXISTS pg_trgm", "DROP EXTENSION pg_trgm"

    create_if_not_exists index(:foos, ["foo_number gin_trgm_ops"],
                           name: "foos_foo_number_gin_trgm_idx",
                           concurrently: true,
                           using: :gin
                         )
  end
end


BUG: Recommended link(s) Careers & MyHR

As an employee searching for the digital Mat/Pat form on Careers & MyHR, I'd like one easy-to-access link to the digital form:

I've tweaked it to return on 'exact match' rather than Phrase

both look good


Release 2.6.2

This is a draft of changelog for the 2.6.2 release.
Here you can find all related translations changes: 2.6.1...master.

⚠ Do not merge this pull request manually ⚠
You should approve this pull request instead. After approving, I will automatically update it (release date needs to be adjusted), merge, and tag a new release. You can read more about the process on forum.

Show release notes preview
2.6.2

General changes:

Updated Flarum core translations.

All changes: 2.6.1...2.6.2.

Success! Now you can announce new release on forum:
## Version [`2.6.2`](https://github.com/flarum-lang/hebrew/releases/tag/2.6.2)

**General changes**:

* Updated Flarum core translations.

All changes: [2.6.1...2.6.2](https://github.com/flarum-lang/hebrew/compare/2.6.1...2.6.2).

In order to update run these commands:

```console
composer update flarum-lang/hebrew
php flarum cache:clear
```


Add a CHANGELOG

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 88.20%. Comparing base (eb3dd16) to head (3c6d5da).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #133   +/-   ##
=======================================
  Coverage   88.20%   88.20%
=======================================
  Files          11       11
  Lines         602      602
=======================================
  Hits          531      531
  Misses         71       71

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Open Graph meta initial test

In theory should make links from the site look like this on twitter and facebook, but due to the way the site is set up and it's async nature I'm not entirely sure. At the very least it won't break anything, but it needs to be live to really be tested.

Just for me to understand the code better, where is node.meta set or is that for the future when this proof of concept is working to add that into suitable a place? The render-function?

node.meta is from the node meta DB table,  In this case (for games) it contains cover images ( and opt-outs?)

Yeah, when you request a node from the server, I'm including a bunch of data, not just what's in the sh_node table.

Alright so it's part of the json from the server, but as far as I can see there's only meta.cover on game-nodes and profile-nodes.

Maybe make the default image something like the one at the bottom of this issue https://github.com/ludumdare/ludumdare/issues/380

Okay, lets try it. I'm not entirely sure it's going to work, but if it does hey.

Yeah, no effect. Metadata is set, but it's not tracked by Twitter.


Adds plugin mixin to "locate" items

This PR adds yet another plugin mixin class, this time to allow "location" of stock items / locations.
Ref: https://github.com/inventree/InvenTree/discussions/2678
Closes https://github.com/inventree/InvenTree/issues/2845
App Integration: https://github.com/inventree/inventree-app/pull/124
This would allow, as a first class feature, development of external plugins to identify / locate / retrieve stock items or locations.
For example, flashing an LED at the location, or retrieving the stock item from a robotic storage system.
This PR also allows native integration of this feature with the app!

Web Integration

App Integration

TODO

[ ] Add JSON field to StockLocation model for use by plugins
[ ] Documentation

What do you mean by a "position reference" here?

@matmair yeah, that makes total sense.
So, add a "reference" field to the StockLocation model? Could be a JSON field, perhaps?

@SchrodingersGat yes that would be good. Maybe referenced to the plugin slug.

@SchrodingersGat this will need some updates with the plugin refactor. Ping me if you want pointers / a PR

@matmair now that https://github.com/inventree/InvenTree/pull/2971 has merged I've got some conflicts to fix, working on that now.
Regarding the custom field for plugin access - I was thinking a "metadata" JSON field on the StockLocation model (which would not be used be internal application logic) could be provided solely for plugins to store custom data against a location. However, this would mean that each plugin would have to take care not to "clash" with whatever data it stores in that field.
Alternatively, we could have a new table which associates metadata between plugins and other tables, e.g. stock location. Then we'd want to expand this to other internal tables, such as the "part" table or "Company" table.
I can see this getting out of hand pretty quickly, and the simpler approach would be to have a single JSON field per location / per part / per customer / etc.
What are your thoughts on this one?

@SchrodingersGat I would recommend moving the new API endpoints and their tests to /plugin/api.py
The JSON field seems to be much simpler. If we provide a helper function to access the data that uses the plugin slug it might help with collisions.


Pull requests here won’t count toward Hacktoberfest.

Hi there,
Thanks for your interest in Hacktoberfest and helping others learn how to make their first contributions to open source!
That said, high-quality contributions are part of the the core values of Hacktoberfest, so we kindly ask that you do not create repositories which allow users to quickly gain a PR toward completing the challenge.
We encourage you to take a look at our list of Hacktoberfest issues for inspiration and ideas about making meaningful contributions to open source projects.
Due to this, we've added this repository to our list of excluded repositories and pull requests here will not count toward Hacktoberfest 2019.
Please note, you are welcome to keep running this repository as a learning tool for new contributors to open-source, but pull requests won’t count toward Hacktoberfest.
Happy Hacking,
The Hacktoberfest Team
Hacktoberfest is presented by DigitalOcean and DEV.

That's sad.  Building a dictionary could have been useful for future projects.

@veltaine The idea is good but implementation is bad. Just write a script for querying existing dictionaries such as WordNet instead, like https://pypi.org/project/PyDictionary/ already does.

To add to what @Isopach said: this repo is from last year's hacktoberfest. People should have continued contribution to an established repo at that point.


Prepend card title to action links inside of a Summary Card

It was raised in the recent DAC audit that pages with multiple Summary Cards had the potential to fail the Level A criterion Link Purpose (In Context) and the Level AAA criterion Link Purpose (Link Only), due to the repetition of links with identical labels—unless the implementor went out of their way to manually provide the required distinctions.
This PR modifies the Nunjucks template for Summary Lists so that, if a card title has been provided, the title is automatically prepended to any action links within the card. This is applied to both the card-level and individual row's action links.
This PR resolves #3673 add #3674.
Changes

Updated the component's internal _actionLink macro now takes a second, optional cardTitle parameter.
Updated instances of _actionLink to pass through the params.card.title object, if it exists.

Thoughts

This is currently hardcoding a content order (and a colon) that might not be preferable in all localisations. I'm hoping that, as two distinct pieces of information that are intended as separate phrases, this might be okay, but I'm not sure.
Piping params.card.title.html into a visually-hidden span feels a bit weird and like it may have adverse side effects depending on what HTML is provided, however we have no guarantee that params.card.title.text is set in all situations.

That certainly seems like a possibility that might work in practice (assuming the AT announces aria-describedby, though I'm not sure if doing that is compliant with the listed WCAG criteria, as the link text itself would not be unique and would appear identical in contexts like VoiceOver's links view.
CC @davidc-gds in case you have a view on this.

Hi @querkmachine from a information hierarchy standpoint, would it make sense to put the unique element (the action) first, and then the card title second?
We can take the 'Summary list as a summary card with actions plus summary list actions' PR preview example as a case study.
Right now it looks to be read out as:

"Undergraduate teaching assistant: Delete job history"
"Undergraduate teaching assistant: Withdraw job history"

I'm suggesting that since the unique element is the action name, we should reverse the order of the items, like so:

"Delete job history: Undergraduate teaching assistant"
"Withdraw job history: Undergraduate teaching assistant"

Thoughts , possibly from @claireashworth?

That certainly seems like a possibility that might work in practice (assuming the AT consistently announces aria-describedby), though I'm not sure if doing that is compliant with the listed WCAG criteria, as the link text itself would not be unique and would appear identical in contexts like VoiceOver's links view.
CC @davidc-gds in case you have a view on this.

I tested the ariadescribedby option in a few screen readers, and generally it looked like it worked for some and didn't for others. I think to be robust we can go ahead with the govuk-visually-hidden currently in use here.
I tested an aria-describedby version with the VoiceOver 'rotor' list of links, and it didn't show the describedby piece in the link label. I couldn't test the 'list of links' features in NVDA or JAWS quick enough, mainly because my computer doesn't have an insert key, and I couldn't troubleshoot how to open the list in the time I had.
So in conclusion:

this current govuk-visually-hidden method works in all 3 screen readers I tested
the aria-describedby was hit and miss, but we'd be fine using it as its totally valid use of that ARIA attribute

The only consistent downside for govuk-visually-hidden is that it always makes copy/pasting the content a real mess:
Copy/paste using govuk-visually-hidden:

Undergraduate teaching assistant
Undergraduate teaching assistant:Delete job history
Undergraduate teaching assistant:Withdraw job history
Name	Firstname Lastname
Undergraduate teaching assistant:EditnameUndergraduate teaching assistant:Deletename
Date of birth	13/08/1980	Undergraduate teaching assistant:Changedate of birth

Without using govuk-visually-hidden:

Undergraduate teaching assistant
Delete job history
Withdraw job history
Name	Firstname Lastname
Edit Delete
Date of birth	13/08/1980	Change

@davidc-gds Swapping the order makes sense to me.
The text-selection problem makes me wonder whether we want to set user-select: none on visually hidden text, but that's probably a topic for wider discussion.

Having the action first makes sense to me as well.

I've pushed changes to place the card title after the action name.
I've also added user-select: none to visually-hidden elements for the time being, so that it can be AT tested in situ.

@querkmachine I may be doing it wrong, but I can still copy/paste the hidden text, even with user-select: none applied to govuk-visually-hidden on the PR deployment.
I'm using cmd + c and cmd+ v on a Mac, on Chrome.

^ We found that David's macOS is configured is to paste with formatting by default, which seemingly always includes the visually-hidden text. This doesn't appear to be the default behaviour in macOS, needing to be configured in Settings → Keyboard → Keyboard Shortcuts... → App Shortcuts.
This does not happen in Firefox or Safari, so it seems to be a case of Chromium purposefully ignoring the CSS rule. As this is a configuration of the user's environment, we probably can't practically do anything about it.
Pasting without formatting omits the visually-hidden text as expected.


An API should be created

This will make the code more readable and give more freedom to developers.

client api modularized; documentation starts now


Improved UX of signing pages

Motivation and context

Added input animation
Removed additional prefix from inputs
Fixed register form autofill
Fixed some problems with autogenerated username
Fixed text aligns on buttons, headings
Decided to keep form button always active so user can press it, and see what fields have errors

How has this been tested?

Checklist

[ ] I submit my changes into the develop branch
[ ] I have added a description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[ ] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

/check

During running CI for this pr, ive encountered 2 unstable tests as reported here. They are not related, so we can merge I belive.


Inconsistent filtering behavior for keyword and data service

Steps to reproduce
Steps are captured in the attached bug video mp4.  For full steps, starting from launch of the website, refer to the associated test case video (in the attached zip).
Expected Behavior
Filtering on keyword and data service provides consistent numbers across filter dialog top area, bottom area, and map
Positive Test Case
Please include a publicly available URL to view the work.
Also, please provide step by step instructions on how to properly test this.

Go to _
link
_
Click on xxx and yyy
Note that [specific thing] happens, whereas in the past [other specific thing] happens.
Actual Behavior
Filtering on keyword and data service does not provide consistent numbers across filter dialog top area, bottom area, and map

port.zip


test: Adjust type tests to be compatible with React 18 typings

Ports https://github.com/DefinitelyTyped/DefinitelyTyped/pull/58289 to current typings as requested in https://github.com/DefinitelyTyped/DefinitelyTyped/pull/58289#pullrequestreview-855908766
Also deduped @types/react packages. Duplicate types packages is usually not supported. It also helped patching local typings.
yarn type-tests passes https://github.com/DefinitelyTyped/DefinitelyTyped/pull/56210 with these changes.

Neat. Thanks!


linux.stdenv: gcc_10 → gcc_11

Description of changes
Was able to build and boot into gnome 42 under kernel 5.17, seems like most packages already support gcc11 without changes; only 1 package gave issues and pinning it to a previous version was enough.
cat /proc/version                                                                                Thu 24 Mar 2022 09:42:13 PM CST
Linux version 5.17.0 (nixbld@localhost) (gcc (GCC) 11.2.0, GNU ld (GNU Binutils) 2.35.2) #1-NixOS SMP PREEMPT Sun Mar 20 20:14:17 UTC 2022

Currently running a home-manager switch but those are a ton more (~4500) over the system required packages (~2600)

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

/marvin opt-in
/status needs_reviewer

@ofborg eval

Oh, this was quite fast.  I'd expect that most of porting work would be C++ stuff.  I'll hope that it will go fine enough to go through the usual staging route, without a dedicated jobset.  It's not so new, so patches for anything important should be easy to find.

Yeah, I started my local build with GCC11 thinking there would be a ton of blockers and next day with only 1 patch I was already booted. (The home-manager switch was almost successful too, had to add 3 more patches)

Worth moving gfortran to 11 version as well?

Worth moving gfortran to 11 version as well?

Probably, but didn't test; it is not necessary afaik.

Taking a look, building lastest staging since binutils-2.38 got merged and seems like a linking/ld issue.

Was able to reproduce locally on current staging, investigating the cause and possible fixes.

@mweinelt, seems like the change of c++14 to c++17 by default changed abseil but not grpc so there was a link time issue. The following patch fixes the build on nixpkgs but will need to take a look at packages that depend on abseil.
diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index 16704f0ec64..f5fb9db5bae 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -17225,7 +17225,12 @@ with pkgs;

   grilo-plugins = callPackage ../development/libraries/grilo-plugins { };

-  grpc = callPackage ../development/libraries/grpc { };
+  grpc = callPackage ../development/libraries/grpc {
+    # grpc builds with c++14 so abseil must also be built that way
+    abseil-cpp = abseil-cpp.override {
+      cxxStandard = "14";
+    };
+  };

   gsettings-qt = libsForQt5.callPackage ../development/libraries/gsettings-qt { };

After this change we should also update https://github.com/NixOS/nixpkgs/blob/1d63f89caaf140ac33f1796dc0aaeb20f4ac4e55/pkgs/development/compilers/cudatoolkit/versions.toml#L43-L59. cc @NixOS/cuda-maintainers

This change broke dm-tree, jax, optax, https://github.com/NixOS/nixpkgs/issues/169134, https://github.com/NixOS/nixpkgs/issues/169148, flax, and certainly many many others. What is the plan for doing this migration? How should packages respond when this broke their build?
I suspect the total number of breakages to be in the hundreds.

There are several paths; currently doing as many fixes as possible but at the rate of 10 or so per day; if a specific gcc version is needed then an override of the stdenv would do. (stdenv = if stdenv.cc.isGNU then gcc10Stdenv else stdenv)

google-cloud-cpp seems to be related to a mismatch between abseil -std and google-cloud-cpp -std a similar override to abseil-cpp as that done on grpc should fix it. Currently working on a merge request.

google-cloud-cpp fix: https://github.com/NixOS/nixpkgs/pull/169220
Can't reproduce python3Packages.jaxlib build issue.

I would recommend either attempting a fix or if not possible opening an issue and notifying the maintainers.

I would recommend either attempting a fix or if not possible opening an issue and notifying the maintainers.

I am the maintainer :P

Probably better to open a separate issue to discuss possible solutions since what you point out (testing in staging-next before merging and block merging in case of breakage) might be lost / not reach other stakeholders on this merge request.

Yes, we're seeing a significant number of breakages every time staging/staging-next get merged. It consumes an enormous amount of maintainer time and energy for us to play "catch up" with these massive changes that break wide swaths of our package landscape.

That's "the same" everywhere.  Only for packages built on Hydra usually someone else is fixing the regressions.

This just doesn't seem like a sustainable long-term development model to me. As a maintainer it seems like I'm forced to either:

Constantly track all of the changes happening on master and recognize breakages before they make it into master. Maintainers have no infrastructure or support in doing this. My packages aren't in any hydra jobsets. How am I supposed to know when people break things before those changes end up in master?
Try to unbreak massive breakages after staging gets merged in and everything is messed up for reasons that maintainers don't understand or have context on. To make matters worse, there's 900 commits to sift through. So good luck sorting through the mess... This is a huge burden and leads to burnout.

Neither of these options are sustainable IMHO. We need a better system. Personally, I don't think people should be able to push PRs breaking other people's packages without a fallback option and a stated plan for completing a migration to the new version. Otherwise it's just chaos.

Quite many breakages do reach master all the time, even for packages built on Hydra, if we look at absolute numbers.  It's one of the reasons why stable releases exist, also in many other distros.  If you care about packages that don't get build on Hydra.nixos.org and/or OfBorg CI, I can't see how to significantly improve this for them without attacking the fact that they don't get build.  Without that noone will even know that there is a breakage.  (we're getting very off-topic on this thread)
In general, this gcc bump in particular had larger negative impact than I hoped, but that doesn't seem very related to the "system" questions.

In retrospective I was expecting a larger staging-next cycle of 2 weeks but it ended up being close to 3 days. (1 day when everything was building and only 2 days of fixes before it hit the main branch)
Even then I would have probably missed fixing breakages of packages / variants not built by hydra.

In particular, this gcc bump had larger negative impact than I hoped, but that doesn't seem very related to the "system" questions.

Agreed, we should take that discussion to a different thread somewhere. maybe discourse?

In retrospective I was expecting a larger staging-next cycle of 2 weeks but it ended up being close to 3 days. (1 day when everything was building and only 2 days of fixes before it hit the main branch)

Indeed and thank you for taking this on and addressing the failures so far, @fabianhjr! GCC bumps are not for the faint of heart, but they are important work. I don't fault you personally in this quagmire; I think the current development model, which I can only summarize as "branch aggressively and cross your fingers" is lacking for everyone involved. We need to think about designing a better system to give everyone more confidence in being able to make large changes more safely.

We do stabilization in separate branches and jobsets for some risky changes.

I started a discussion on Discourse for the broader conversation: https://discourse.nixos.org/t/nixpkgss-current-development-workflow-is-not-sustainable/18741.

rili broke, proposed fix: https://github.com/NixOS/nixpkgs/pull/169540

zkfuse broke, proposed fix: https://github.com/NixOS/nixpkgs/pull/169543


Possibly missing projects:cnrm-viewer for cnrm-controller-manager-logging

After deploying this package, embedded in landing-zone/logging/bigquery-export...
https://github.com/GoogleCloudPlatform/blueprints/blob/07c398d254970eb982361db78402b5d8259c878f/catalog/log-export/org/bigquery-export/Kptfile#L2-L6
One of the resources remained in an error state with this message:
[
  "logging",
  "bqlogexportdataset",
  "Update call failed: error fetching live state: error getting ID for resource: error getting value from reference: error resolving reference field: error getting referenced resource from API server: error getting referenced resource projects/logging-129082878300 with GroupVersionKind resourcemanager.cnrm.cloud.google.com/v1beta1, Kind=Project from API server: projects.resourcemanager.cnrm.cloud.google.com \"logging-129082878300\" is forbidden: User \"system:serviceaccount:cnrm-system:cnrm-controller-manager-logging\" cannot get resource \"projects\" in API group \"resourcemanager.cnrm.cloud.google.com\" in the namespace \"projects\""
]

I added this to landing-zone/namespaces/logging.yaml which seems to fix that
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata: # kpt-merge: projects/allow-resource-reference-from-logging
  name: allow-resource-reference-from-logging
  namespace: projects
roleRef:
  name: cnrm-viewer
  kind: ClusterRole
  apiGroup: rbac.authorization.k8s.io
subjects:
  - name: cnrm-controller-manager-logging
    namespace: cnrm-system
    kind: ServiceAccount

based on seeing the similar role binding being applied to the networking sa
https://github.com/GoogleCloudPlatform/blueprints/blob/07c398d254970eb982361db78402b5d8259c878f/catalog/landing-zone/namespaces/networking.yaml#L108-L120

Thanks for the report, you did indeed find the correct fix.


Add pod scenarios for custom app

Signed-off-by: mjulie<EMAIL_ADDRESS>

Can one of the admins verify this patch?

Can one of the admins verify this patch?

One small suggestion, you are kind of doing a double post action check. I would suggest picking just one.
The 2 different types can be seen in the first pod_scenario section here

the etcd scenario doesn't have a second item in the list and does the post action check in the yaml scenario file.

While the regex scenario has a python file in the list for that scenario. The regex scenario has varying number of pods so we use the python file to print the number of pods for that specific env. If you want to use a python file or bash script as the post action check, it will first run the script before the scenario to get the original number of pods before the pod killing and again after to make sure those numbers match.
Also, if you have a varying number of pods you can print just the number of pods as seen here and kraken will take care of the rest.

Please let me know if any of that doesn't make sense.

One small suggestion, you are kind of doing a double post action check. I would suggest picking just one.
The 2 different types can be seen in the first pod_scenario section here

the etcd scenario doesn't have a second item in the list and does the post action check in the yaml scenario file.

While the regex scenario has a python file in the list for that scenario. The regex scenario has varying number of pods so we use the python file to print the number of pods for that specific env. If you want to use a python file or bash script as the post action check, it will first run the script before the scenario to get the original number of pods before the pod killing and again after to make sure those numbers match.
Also, if you have a varying number of pods you can print just the number of pods as seen here and kraken will take care of the rest.

Please let me know if any of that doesn't make sense.

LGTM


Correction for raw affiliation Food and Healthy Living Group, Aeres University of Applied Sciences, Almere, Netherlands

Correction needed for raw affiliation Food and Healthy Living Group, Aeres University of Applied Sciences, Almere, Netherlands
raw_affiliation_name: Food and Healthy Living Group, Aeres University of Applied Sciences, Almere, Netherlands
new_rors: 03jnx2c74
previous_rors: 015d5s513
works_examples: W3196820251;W4293240524
contact: da852953b0a29c0d275b98504b9e89cc:ad194193e16c5ae0 @ aeres.nl

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


ValueError: Unknown CUDA arch (8.0) or GPU not supported

When I tried python3 setup.py build develop, an error occured as follow
ValueError: Unknown CUDA arch (8.0) or GPU not supported
I tried on both V100, CUDA 11.2 and 1060ti, CUDA 11.2, this error always exists.
What should I do?
Many thanks.

I use docker to build my environment, so I use pip install pytorch==1.4.0 torchvision==0.5.0, but I print torch.cuda.version, it is as follow:
'10.1'
Does this matter? Must I use conda to build environment?

no, conda is not a must. I conduct experiment on RTX 1080Ti and 2080. not sure whether it is gpu related problem or not.


make a contact us page implement contact us section in backend

we just have to make contact us page and add the page to existing Django app ,right??

yes but have to implement the backend also but you can done that in another PR first just make contact us page and link it in Django app must discuss with @7saikat7

sure
will do that

Hello
If this issue if still not resolved
I am interested on working of this

Hello If this issue if still not resolved I am interested on working of this

@prateekmohanty63 there is a bug in the contact us features i am creating a new issue for that comment on that i will assign you