Railway Track fault Detection

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Railway Track fault Detection
:red_circle: Aim : Create a model which will classify Defective and Non-Defective Railway Track
:red_circle: Dataset : https://www.kaggle.com/datasets/gpiosenka/railway-track-fault-detection-resized-224-x-224
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

Hi @abhisheks008 , can you assign me this issue please. I am learning Deep Learning and Neural nets. I am fluent in Python.
Full name : Chinmay Harkawat
GitHub Profile Link : https://github.com/janeka1122
Email ID<EMAIL_ADDRESS>Participant ID (if applicable) : None that I know of
Approach for this Project : Explore various algorithms and implement a Neural Net.
What is your participant role? SSOC (Social Summer of Code)

Issue assigned to you @janeka1122

Updates please @janeka1122

I have been unable to complete the issue, will take some more time.
I'am still very new to ML 😅

@janeka1122 updates please.

Full name : Kinshuk Goyal
GitHub Profile Link : https://github.com/Kinshuk2003
Email ID<EMAIL_ADDRESS>Participant ID (if applicable):
Approach for this Project : Python, keras and open cv
What is your participant role? (Mention the Open Source program) SWOC S3 Contributer
@abhisheks008 assign this issue to me

Issue assigned to you @Kinshuk2003. Go ahead.


Make sure PHP example can be run with Apache

Test case: Set up Apache server. User hit webserver asking to execute some PHP scripts. Apache invokes PHP (via a fastCGI service). The PHP script initiates a gRPC client, and tries to make connection to a gRPC server.

Tried to run some gRPC PHP examples with Apache / Nginx on Mac OS X and run into multiple problems:

Tested with Apache

Success: Ran some simple statements like $server = new Grpc\Server([]);

So that means at least the grpc.so extension is loaded properly

Failed: Anything that needs functions like startBatch()

The apache process httpd just hangs and needs to be killed

Failed: Anythat that needs constants like OP_SEND_INITIAL_METADATA

Strangely, just printing these constants works the first few times, and then the grpc.so extension mysteriously got unloaded by PHP and the httpd process eventually crashes

Tested with nginx and php-fpm

Success: Ran some simple statements like $server = new Grpc\Server([]);

So that means at least the grpc.so extension is loaded properly

Failed: similar failure with startBatch() and constants like OP_SEND_INITIAL_METADATA like above

At this point it feels like it doesn't matter whether Apache or nginx is the webserver. I focus on php-fpm as the FastCGI server.

Use cgi-fcgi to connect directly to php-fpm

Run php-fpm at port 9000
./homebrew/opt/php55/sbin/php-fpm --fpm-config ./homebrew/etc/php/5.5/php-fpm.conf

Run cgi-fcgi to connect directly to php-fpm running at port 9000
SCRIPT_FILENAME=grpc-common/php/greeter_client.php REQUEST_METHOD=GET cgi-fcgi -bind -connect localhost:9000

It hangs.
I did verify that running the greeter_client.php script directly on PHP CLI returns successfully
$ php grpc-common/php/greeter_client.php
Hello world

So I run a gdb session on the cgi-fcgi command, and got this trace:
$ gdb cgi-fcgi
$ set environment SCRIPT_FILENAME grpc-common/php/greeter_client.php
$ run -bind -connect localhost:9000

Program received signal SIGINT, Interrupt.
0x00007fff912193fa in select$DARWIN_EXTSN () from /usr/lib/system/libsystem_kernel.dylib
(gdb) bt
#0  0x00007fff912193fa in select$DARWIN_EXTSN () from /usr/lib/system/libsystem_kernel.dylib
#1  0x000000010000ddfc in OS_DoIo ()
   from /Users/stanleycheung/homebrew/Cellar/fcgi/2.4.0/lib/libfcgi.0.dylib
#2  0x0000000100001b9f in main ()

I may have found a workaround:
sleep(8); // that's 8 seconds
after instantiating a Channel, but before making any call

Same here. Got a whole lot of notices and constants disappearing.
I'm using PHP's (well, Symfony2's) built-in web server for now.
Notice: Use of undefined constant OP_SEND_INITIAL_METADATA - assumed 'OP_SEND_INITIAL_METADATA'.

It seems to be a lot more stable on Linux than on Mac. We are still working on this.

Closing this as the gRPC PHP extension is stable to be run behind either Apache or Nginx/PHP-FPM on Linux (Debian at least). Will log a separate issue for the Mac issue we were seeing.

I need to reopen this one. Our team's been trying to get the PHP extension to work reliably and consistently for the better part of last week – without any luck. Sometimes, after a fresh start of Apache it works for 1 or 2 calls and then it doesn't with the message in the log: Notice: Use of undefined constant OP_SEND_INITIAL_METADATA - assumed 'OP_SEND_INITIAL_METADATA'. I've been able to put together a Dockerfile for you to try out.
Steps to reproduce:

Clone repository here: https://github.com/alfatraining/docker-grpc-php-test.
Run make.
This compiles gRPC, the PHP extension, and runs the tests. This should take about 15 minutes (give or take). After that, it starts Apache2, the NodeJS example server and a tail -f /var/log/apache2/error.log.
Go to http://{insert-your-docker-host-ip-here}:8880/greet.php in your browser.

This will work for a few calls (sometimes just the first, sometimes 2 more) and then it doesn't. Blank page. Take a look at the log output of the tail:
[Tue Sep 29 14:05:41.518549 2015] [:error] [pid 22] [client <IP_ADDRESS>:52252] PHP Notice:  Use of undefined constant OP_SEND_INITIAL_METADATA - assumed 'OP_SEND_INITIAL_METADATA' in /var/www/grpc/examples/php/vendor/grpc/grpc/src/php/lib/Grpc/UnaryCall.php on line 54
[Tue Sep 29 14:05:41.518586 2015] [:error] [pid 22] [client <IP_ADDRESS>:52252] PHP Notice:  Use of undefined constant OP_RECV_INITIAL_METADATA - assumed 'OP_RECV_INITIAL_METADATA' in /var/www/grpc/examples/php/vendor/grpc/grpc/src/php/lib/Grpc/UnaryCall.php on line 55
[Tue Sep 29 14:05:41.518594 2015] [:error] [pid 22] [client <IP_ADDRESS>:52252] PHP Notice:  Use of undefined constant OP_SEND_MESSAGE - assumed 'OP_SEND_MESSAGE' in /var/www/grpc/examples/php/vendor/grpc/grpc/src/php/lib/Grpc/UnaryCall.php on line 56
[Tue Sep 29 14:05:41.518600 2015] [:error] [pid 22] [client <IP_ADDRESS>:52252] PHP Notice:  Use of undefined constant OP_SEND_CLOSE_FROM_CLIENT - assumed 'OP_SEND_CLOSE_FROM_CLIENT' in /var/www/grpc/examples/php/vendor/grpc/grpc/src/php/lib/Grpc/UnaryCall.php on line 57
[Tue Sep 29 14:05:41.518657 2015] [:error] [pid 22] [client <IP_ADDRESS>:52252] PHP Fatal error:  Uncaught exception 'InvalidArgumentException' with message 'batch keys must be integers' in /var/www/grpc/examples/php/vendor/grpc/grpc/src/php/lib/Grpc/UnaryCall.php:57\nStack trace:\n#0 /var/www/grpc/examples/php/vendor/grpc/grpc/src/php/lib/Grpc/UnaryCall.php(57): Grpc\\Call->startBatch(Array)\n#1 /var/www/grpc/examples/php/vendor/grpc/grpc/src/php/lib/Grpc/BaseStub.php(181): Grpc\\UnaryCall->start(Object(helloworld\\HelloRequest), Array, Array)\n#2 /var/www/helloworld.php(155): Grpc\\BaseStub->_simpleRequest('/helloworld.Gre...', Object(helloworld\\HelloRequest), '\\\\helloworld\\\\Hel...', Array, Array)\n#3 /var/www/html/greet.php(8): helloworld\\GreeterClient->SayHello(Object(helloworld\\HelloRequest))\n#4 {main}\n  thrown in /var/www/grpc/examples/php/vendor/grpc/grpc/src/php/lib/Grpc/UnaryCall.php on line 57

The container builds the extension on Debian off of the release-0_11 branch so it includes the fixes from version 0.11.0 and 0.11.1. To take a look into the running container, just open another terminal and run make attach.
Are we missing anything? We've also tried to build it on the tagged releases for 0.10, 0.11.0, 0.11.1 as well as straight up from master for the past several days and always hit this exact problem.

Working on this.

:dancers:

Update: Still working on this. There are some cases where this issue is reproducible but not others. There are several factors in play here: docker vs a straight up Debian VM, compile-from-source vs install via debian package, which release point of gRPC I am compiling from, Mac vs Linux, etc. I am still trying to isolate what works and what don't.

Update: Thanks to @bjori for submitting a PR to fix this. I am doing more testing and will merge accordingly. And then I will release the fix on PECL as well. Stay tuned!

Awesome work – thank you both! :+1:

@annismckenzie This issue should be fixed now. I put together a Dockerfile with an example:

git clone https://github.com/stanley-cheung/grpc-php-apache-testing.git
cd grpc-php-apache-testing/
docker build -t grpc-php-client grpc-php-client/
docker run -it --rm --name grpc-php-client-instance -p 9998:80 grpc-php-client
from another terminal: curl localhost:9998/math_client.php

The example should demo all 4 types of calls we support: unary, server streaming, client streaming and bidi-streaming.
Please give it a spin and see if that works for you! Thank you.

Apart from the small issue with the wrong libgrpc version (see my comment: https://github.com/stanley-cheung/grpc-php-apache-testing/commit/2a8addcb7bc20f6b88e51ddfc1db151c8ec383ff#commitcomment-13660113) this is working great. We've been running the fixed version in our staging environment since yesterday and it is working.
:dancers:
Thanks to everyone involved here! You may close this issue.


Test for CLA

Issue Number
Implementation description
@devonfw/devonfw-shop-floor

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Update sample to use constructor that takes a version

The no-argument version of the constructor is deprecated. Updated the sample to use the overload that takes the card version.

OPS Build status updates of commit 47e3f65:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/net-wpf/render-a-card.md
:white_check_mark:Succeeded

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


I don't know where the CROPSIM.CFG file accessed in the following program is located, or what format it is in. Can you provide a sample file?

I don't know where the CROPSIM.CFG file accessed in the following program is located, or what format it is in. Can you provide a sample file?
Plant/CROPSIM/CRP_RunInit.for，
Plant/CERES-Wheat_Barley/CER_Init.for，
Plant/CSYCA-Cassava/YCA_RunInit.f90，
Plant/CSCAS/CSCAS.for，
UtilitiesCSREADS.for，
Utilities/CSUTS.for

This file is needed only for the stand-alone CROPSIM model. If you are running DSSAT, you don't need it.

This file is needed only for the stand-alone CROPSIM model. If you are running DSSAT, you don't need it.

I need to modify the DSSAT and debug it, so I need this file. Is there a format description or sample file for the relevant file

I've spent a significant portion of my life modifying and debugging DSSAT. I've never seen or used this file.


Error: connect EConnrefused

I'm trying to use redis and redis-commander this way through docker-composer.
    redis:
        image: 'redis:latest'
        depends_on:
            - engine
    redisadmin:
        image: 'rediscommander/redis-commander:latest'
        environment:
            - 'REDIS_HOSTS=local:redis:6379'
        ports:
            - '8081:8081'

In the GUI nothing is connecting and in my logs I'm seeing this over and over again.
redisadmin_1   | setUpConnection Redis error Error: connect ECONNREFUSED <IP_ADDRESS>:6379
redisadmin_1   |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1191:14)

Looks like my environment variable needed updated.
redisadmin:
        image: rediscommander/redis-commander:latest
        environment:
            - REDIS_HOST=redis


Suggestion to add "title" to contributes/menus

When developing an extension which adds a lot of commands we prefix all commands with an identifier so that you easily can find all commands belonging to our extension when opening the command palette and searching for that prefix. (Also if we didn't prefix the command it wouldn't be obvious to the user that it belongs to the extension which we want)
However contributes/menus/"view/title" reuses the title from the command so that when you hover over a button it has the same prefix, which we don't really want since (in this case) the custom treeview we have is really obvious that it belongs to our extension.
Similarly we might want the hover to be more or less descriptive than the command title in general.
So if we could have an extra "title" or similar in contributes/menus/"view/title"-entries which could default to the command name that would be nice.
Mockup contributes (might contain errors) to hopefully help with showing what I mean:
{
  "contributes": {
    "commands": [
      {
        "command": "customList.doSomething",
        "title": "NameOfExtension do something",
        "icon": {
          "light": "media/iconBlack.svg",
          "dark": "media/iconWhite.svg"
        }
      }
    ],
    "menus": {
      "view/title": [
        {
          "command": "customList.doSomething",
          "when": "view == customList",
          "group": "navigation@1",
          "title": "Do something" // <--- suggested field to avoid hover showing "NameOfExtension do something"
        }
      ]
    },
    "views": {
      "custom-list": [
        {
          "id": "customList",
          "name": "",
          "icon": "media/listIcon.svg",
          "contextualTitle": "Custom"
        }
      ]
    }
  }
}

I can work around this by having two commands, with the same behavior, where the one assigned to the button has an "enablement" property with value "view == customList" causing it to not show up in the command palette.
Maybe that's the intended way to do it? Then we can close this.

I generally like this idea, but I'll leave it up to @jrieken.

When developing an extension which adds a lot of commands we prefix all commands with an identifier so that you easily can find all commands belonging to our extension when opening the command palette

Don't do that. Instead use the category-property. In short

title should be the normal title,
there is shortTitle for a more compact variant of that,
and category for the name of the scope/feature/extension.

The different UIs will then decide what of these bits and pieces to render, eg the command palette renders ": " but other menu use just title


Schussler et Al. implementation

Description
Implement the 2nd order scattering with specular tangent microfacet, eq 23
Description of the related problem
Smooth Shading Normals Feasibility study
Implement on a small low poly sphere first, see if we can treat the smooth shading normal as-if it came from a object space normalmap.
vec3 value = brdf_cos_eval(L,V);

const float deviation = dot(shadingNormal,geometricNormal);
if (deviation<THRESHOLD) // THRESHOLD<1.f
{
   vec3 tangentFacet = normalize(shadingNormal-deviation*geometricNormal);

   // implement rest of schussler but without overoptimization
}

Remember to implement pre dot(V,geometricNormal)>FLT_MIN and post dot(L,geometricNormal)>FLT_MIN geometrical feasibility checks.
See if it doesn't spoil everything compared to regular smooth shading.
Solution proposal
Optimized visible facet probability calculation
Asserting that the deviation is positive (no backfacing or tangent normals).
// deviation = clamp_dot(shadingNormal,geometricNormal);
// a_p = clamp_dot(dir,shadingNormal)/deviation
// a_t = clamp_dot(dir,tangentFacet)*sqrt(1.f-deviation*deviation)/deviation

// a_p/(a_p+a_t)
float shadingNormal_vpdf(in vec3 dir, in float deviation, in vec3 tangentFacet)
{
   const float cosTheta = clamp_dot(dir,shadingNormal);
   return cosTheta/(cosTheta+clamp_dot(dir,tangentFacet)*sqrt(1.f-deviation*deviation));
}

Is it possible to squeeze something more out of dot(dir,tangentFacet)*sqrt(1.f-deviation*deviation) ? YES
Before normalization, the length of tangentFacet is sin(deviationAngle) = sqrt(1.f-deviation*deviation)
float shadingNormal_vpdf(in float cXdotGeomN, in float clampedXdotShadingN, in float GeomNdotShadingN)
{
   assert(GeomNdotShadingN>=0.f);
   assert(XdotGeomN>0.f);
   return clampedXdotShadingN/(clampedXdotShadingN+max(XdotShadingN-GeomNdotShadingN*XdotGeomN,0.f));
}

Let the tangentFacet_vpdf = 1-shadingNormal_vpdf, there's nothing more optimal.
Optimized Masking Function (TODO triple check)
Same assertions as above
// <w_i,w_g>/(a_p+a_t)
float shadingNormal_masking(in float XdotGeomN, in float XdotShadingN, in float GeomNdotShadingN, enum facet)
{
   assert(GeomNdotShadingN>=0.f);
   assert(XdotGeomN>0.f);
   const float d = GeomNdotShadingN*XdotGeomN;
   if (XdotShadingN>d)
      return 1.f/(2.f*XdotShadingN/d-1.f);
   return facet==PERTURBED&&XdotShading>0.f ? 1.f:0.f;
}

Additional context
The 2nd order scattering Schussler BRDF is horribly expensive to evaluate.
Pay attention to Tangent Space in Anisotropic BxDFs
Tangent space needs to change when bump mapped (maybe construct tangent space after normal is perturbed).
Provide upgraded Microfacet Structs
Keep track of dot products of L,V and shading normal with geometrical normal.
Keep track of shading tangent space with reflected (around the schussler facet) V and L.
dot(X_refl,Y) = 2*dot(X,T)*dot(T,Y)-dot(X,Y)

Compute them only when there is enough deviation against geometrical normal and masking function says BRDF evaluation will have non-zero weight.
Make BxDF_cos functions capable of computing the triple evaluation at once
Certain computation can be shared, such as:

the V and L dependent factors which can be reused for masking function computation, and differential factors
some fresnel calculations

In the case of the Diffuse BRDF*cos, it only needs to be evaluated twice, not 3 times due to viewer invariance.
Figure out how to incorporate the Schussler model into BSDFs
What to do about transmission? Thankfully we can't have double refraction ;)
Material Compiler
Modify OPcode BUMP and its instruction heavily to compute new microfacet caches.
Implement triple choice in importance sampling (might be hard to make it work with the binary jump).
Maybe treat the microfacet scattering evaluations as sub-BxDFs, and associate bitmasks to scattering orders (for skipping evaluation of non-importance sampled BRDFs).
Pay attention to occupancy, no empty loop iterations, figure out how to skip to the next sub-BxDF (instruction stream fast forward loop before the instruction dispatch table?).
Investigate full-sum Quotient+PDF evaluation (less variance) vs stochastic sum (more variance, higher speed) in variants of pick sub BRDF only, pick one BRDF only.

Absolutely useless for interpolated normals, abandoning


Use useSelector instead of connect in several places.

Several instances of #4837 that are pretty straightforward.
There are more of these easy ones, and I almost did those here, but then I figured this was already a big enough chunk to review. 🙂

Thanks for the review!


issue with parameters passed by onChangeIndex

The API docs for onChangeIndex show it is called with function(index, fromIndex) but it doesn't seem to work properly for me. I am a bit of a noob so maybe I'm not understanding it but I did dig through the code to try to figure it out. Here's what I see:
this.props.onChangeIndex() is called in a number of different files but sometimes it is called with one parameter this.props.onChangeIndex(indexNew); and other times with two this.props.onChangeIndex(indexNew, indexLatest); . Am I correct in asserting the API will not always pass the fromIndex parameter? If so, is this maybe a bug because shouldn't onChangeIndex only fire when the index changes from something to something else?
Also I don't think those two parameters have the correct meaning when passed anyway.
In the handleTouchEnd function of both the index.native.antimated and SwipeableViews.js you have the variables:
indexNew, indexCurrent, and indexLatest
indexNew gets assigned
    if (Math.abs(this.vx) > this.props.threshold) {
      if (this.vx > 0) {
        indexNew = Math.floor(this.state.indexCurrent);
      } else {
        indexNew = Math.ceil(this.state.indexCurrent);
      }
    } else {
      // Some hysteresis with indexStart
      if (Math.abs(this.indexStart - this.state.indexCurrent) > 0.6) {
        indexNew = Math.round(this.state.indexCurrent);
      } else {
        indexNew = this.indexStart;
      }
    }

then sometime later this.setState is used to give indexCurrent and indexLatest the value of indexNew
    this.setState({
      indexCurrent: indexNew,
      indexLatest: indexNew,
      isDragging: false,
    },

and just a couple lines later in the setState callback indexNew is checked to see if it matches indexLatest
, () => {
      if (this.props.onSwitching) {
        this.props.onSwitching(indexNew, 'end');
      }

      if (this.props.onChangeIndex && indexNew !== indexLatest) {
        this.props.onChangeIndex(indexNew, indexLatest);
      }
    });

but how would they ever not be the same?
There is a good chance I just don't understand something about React or ES6 correctly.

@funkyeah You are right, the API isn't consistent. Can you have a look at https://github.com/oliviertassinari/react-swipeable-views/pull/58? It should improve this.

It looks like it should work to me. I'll be happy to give it a test when you want.
The only thing that looked a little fishy to me is the use of this.state.indexCurrent which often appears to be a duplication of this.state.indexLatest in https://github.com/oliviertassinari/react-swipeable-views/blob/standardize-onChangeIndex/src/SwipeableViews.js#L245
Although that is not always the case in other files. I guess it's just a little hard to understand what they are supposed to mean at all times... but probably still functioning correctly.

Well indexStart and indexCurrent are used for different purposes.

indexStart is for adding some hysteresis.
indexCurrent is for reflecting the swipe position at the next render.

You raised some good points. I could have added some comment to be more explicit. Are even better test them.

I wouldn't go that for. I would say my points are OK at best. I'm more just pointer to things that are hard for me to understand, which only means that they are hard for a total beginner to understand, not that anything is necessarily wrong.
Anyhoo, thanks for doing this project. I'm trying to use it in a react native app to setup gmail like swipe row items... basically the swipe to archive feature but instead swipe to mark as done. So the event API is what I'm depending on.


Fix memory leak of framework wrappers

Fixes #117

This is wonderful!   Thank you for taking the time to look into that bug @tishin


Create gsoc-2020-Vasyl-Teliman.md

Converted it to draft. I will refactor this document into a github gist link when the review is done.

CI failed due to a network error, I think.

@afd, I wonder if it would be better to put all the information in the report into the gist file and provide a link to it here. @paulthomson has argued that you might move this repo in the future so it might be better to have a stable link to the document.
If so, let me know when you've finished the review so I can copy it into the gist.


Encryption of User data

Closes #18

for now, only class User is encrypted
user data is encrypted using AES algorithm
key is stored in SharedPreferences

@sakshampruthi @sjain30 could you please look into it?


Dir Failed

I tried setting up everything from the README but I'm still getting this error for some reason. I tried changing the download directory in constants.js but same error.

A2C: Websocket opened. Bot ready.
download:https://raw.githubusercontent.com/out386/aria-telegram-mirror-bot/master/README.md gid:765a80751222be8d
Started 765a80751222be8d. Dir: 0c10a633-5b6d-404a-a4f0-74604c138a6b.
765a80751222be8d failed. Download aborted.
cleanup: Deleted 0c10a633-5b6d-404a-a4f0-74604c138a6b
download:https://raw.githubusercontent.com/out386/aria-telegram-mirror-bot/master/README.md gid:45ec985705c9ea33
Started 45ec985705c9ea33. Dir: f83ce242-a223-4979-a7e0-b4b62ebe30f9.
45ec985705c9ea33 failed. Download aborted.
cleanup: Deleted f83ce242-a223-4979-a7e0-b4b62ebe30f9

Make sure you aren't running out of space
Make sure that the bot can write to your download dir. Check directory permissions, and it should be owned by the user the bot is running under.

Thanks for replying so soon!
I figured out the issue dumb me: the download directory in constants.js was set up wrong. I corrected it and the bot started working!


ExtensionDeploymentStatus new Actions

Summary
Added new actions to page "Extensions Deployment Status"

Refresh: for refreshing the status of the deployment
Upload Extension: to re-upload an extension if the first try failed for some reason
Extension Management: to go back to the extension management page

Unfortunately it's not possible to test this Onprem and there does not seem to be a whole lot of test automation for this which I could re-use. Hopefully you can qualitity check this manually.
Work Item(s)
Fixes #977
Fixes AB#527490

Hi @JulianTillmann,
you've got a few easy to fix codecop violations. Could you look into those to get green ticks in the CI step? Then we'll process the PR 🙂


Add a Dockerfile

Based on https://github.com/ansible/ansible-hub-ui/blob/master/Dockerfile

Curious why is it needed to have a pulp-ui container running inside oci-env?
(As in, why not just run oci-env for pulp backend, and have the UI just proxy there?)
If you're copying the galaxy ui profile, I'm not sure anyone was using it, there may be skeletons there I don't know about :).
But, looks good as long as it still works :+1:  :)

Ah, makes sense :)
Looks like the Dockerfile should work, as long as it's run with a volume mounted in /pulp/app that points to pulp-ui/

Curious why is it needed to have a pulp-ui container running inside oci-env? (As in, why not just run oci-env for pulp backend, and have the UI just proxy there?)

The eventual goal is to have the UI also run in the same image of the Pulp backend, but I would like to get the node/npm depedencies inside the base Pulp image first. This is a temporary measure to help others on the Pulp team quickly setup the UI if they don't have node install on their system.

Honestly, I would prefer to not install node in the ci-container. It is still the base image for all the "production ready" containers we ship. And in production, you "just" want to serve some static files along with the API.

Honestly, I would prefer to not install node in the ci-container. It is still the base image for all the "production ready" containers we ship. And in production, you "just" want to serve some static files along with the API.

Yes, after the UI meeting I am in agreement that we just want the images to serve the static files. I'll make the changes to the oci-images CI to build the files and copy them over to the image.


Data table needs to be debounced

Because the table with the header selection boxes is completely reactive, every keystroke sets off a long computation. Debounce it

Closed by #12


Optimization (configuration, datasets, etc) and testing

After implementing fine-tuning via ray and locally with model+data parallelism, this should be tested.
@jieguangzhou to add comments and plans (distinguish small and large data)
@kartik4949 and @blythed to review.

[ ] Test on small fine-tuning dataset
[ ] Check that supplied metrics and correctly stored and decreasing
[ ] Check model check-pointing
[ ] Check user experience
[ ] ...

Related to: #1653


Reuse connected ConnectedField, ConnectedFields and ConnectedFieldArray

Redux connect() returns a new class. Currently, each ConnectedField, ConnectedFields and ConnectedFieldArray is connected to redux, thus creating many classes. This change connects ConnectedField, ConnectedFields and ConnectedFieldArray only once.
In a field array, if we would like to preserve state of our component, we need to use a key that identifies the element, instead of array index. However, doing so, Field, Fields and FieldArray detects that it is now bound to a new field name and discards the old connected class and connect again. React sees that the class is different, thus discards the old virtual DOM, along with the component and its state.
By using mapStateToProps(state, ownProps) and mapDispatchToProps(dispatch, ownProps), we can dynamically map according to the current ownProps.name or ownProps.names, thus ConnectedField, ConnectedFields and ConnectedFieldArray only needs to be connected once. React will see the same class and reuse the virtual DOM, preserving our component and its state.

Current coverage is 100% (diff: 100%)

Merging #1734 into master will not change coverage

@@           master   #1734   diff @@
=====================================
  Files          52      52
  Lines        1115    1135    +20
  Methods         0       0
  Messages        0       0
  Branches        0       0
=====================================
+ Hits         1115    1135    +20
  Misses          0       0
  Partials        0       0

Powered by Codecov. Last update 9186bd3...6f93372

Published in v6.0.3.


How to handle large SVG?

First of all, thank you all for your hard work in developing this library!
I have a use case where I'm rendering a large SVG (a line chart with may data points)  within a horizontal Scroll View, such that the x-axis is scrollable to view all the data points.
Obviously with many entries, the SVG becomes quite large and performance drops.
I am using a rectangular ClipPath, animated with the scrollOffset, such that it only shows what should be visible on-screen, while clipping the rest. This kind of works, but translating the clip-path results in a sub 60fps scroll experience.
What other ways would there be to clip the SVG based on the scroll position, other than an Animated ClipPath?
Thanks!

@noldidrita Did you find a solution to this?

@mrousavy Have a look at comment: https://github.com/react-native-svg/react-native-svg/issues/926#issuecomment-462052663 . The solution is to have the svg be at most the size of device view, and transform the content in response to touch.

Thanks @brookemitchell, but unfortunately @msand 's comment didn't help. I'm not sure why my vectors are so slow, I've created an issue for this (https://github.com/react-native-svg/react-native-svg/issues/1470) if you want to take a look at it.

+1

Try React.memo Worked for me.


Type Casting

Is there an easy way to go from, say, Point2<i32> to Point2<f32>. There doesn't seem a way to do this atm that doesn't involve more than a function call.
If there is no such way to do it, I'd be happy to implement a From to cast between types.

You should be able to use let float_point = nalgebra::convert(int_point).

It seems the reverse is actually not possible. How would this be achieved?

The reverse is possible but may fail (for example if a value being converted is NaN). So, instead of ::convert, you have to use nalgebra::try_convert which returns an Option<…>. If you don't care about special float values, you can use nalgebra::convert_unchecked which will always succeed and just performs the cast without checking for Inf/NaN. (convert_unchecked is unsafe because this kind of conversion  without checks can lead to crashes for other, more complicated types.)

I made an attempt to improve how this feature can be discovered in the API documentation by having the function documentations refer to each other for convert and try_convert. Let's hope this will inform future users better.
Closing, as the issue appears to be resolved otherwise.


Add browser pool to handle issues where browser disconnects and add config options for same

We when started using rendertron for our app for seo purposes, we were facing issues
1- where browser automatically disconnects after few hours. We added support for browser pool to maintain multiple browser in pool as per config.
2- rendertron was using same context to render all requests. So any cookie change in any request was being maintained for subsequent requests.
We used generic-pool to create the pool of browser and its maintenance. Have created three classed for creating pool, validating and maintaining a minimum number browser ready for use.
We also made change to support incognito context for different requests.

@himanshu0511 hey!
would you like to finish this pr, or do you want me to open a new one with the corrections suggested by @AVGP ?
I really want to help with releasing version 3. is there anything else i can do to make it happen sooner  @AVGP ?


noise

Hello,i want to know noise parameter which geted form sdk is contious or  dispersed？

Hello @derekhe89, what do you mean by 'noise parameter' ?

The noise parameter is the noise_variances and the bias_variances.

I want konw the contious noise_density and random_walk of gyroscope and accelerometer,but i don't know how to get that . Is the noise_variances is noise_density and the bias_variances is random_walk?@ icarpis

The ROS wrapper publish the IMU calibration info in order to calibrate the IMU (Accel/Gyro). Please take a look at this issue #256 .

Thank you for your answer. The issue you gave me just explain the scale、 cross axis and bias, but i want to know the contious noise_density and random_walk of gyroscope and accelerometer. @icarpis

These parameters could be found in this issue.
If you still have more questions about the ZR300 IMU sensor please consider to post a question in that issue.


Application examples?

Is rustus supposed to be exposed to the world or proxied by a "domain-specific" web service?
Did I understand well from this example:
https://github.com/s3rius/rustus/blob/320625059dd8ac362f29471952b596ad8348f911/docs/hooks.md?plain=1#L852-L855
That hooks could be used to authenticate file uploads?
I think it would be interesting as a narrative example to unroll a whole demo app that leverages rustus. Or give more context on why it was built?
Or for example, answer questions like "if I want to built a WeTransfer clone, what is the intended way to integrate rustus?"
If you're willing to give me a few pointers, I'd be glad to contribute something :)

HI! And thanks for you question.
Rustus is supposed to be opened to the world. To make it more secure, you can use CORS.
If you have no hooks configured, then everyone can upload anything.
But if you have file hooks or http hooks, then on pre-create hook you can easily abort uploads by either exiting with non-zero status code (if you use file hooks)  or return not 200 status code from your application (if you use http hooks) .
When upload is ready you can add post-finish hook to handle events when upload is complete.
I use rustus to upload renedered videos to one of my side-projects.
@router.post("/rustus_hooks")
async def rustus_hooks(
    hook: RustusHook,
    auth: AuthJWT = Depends(),
    hook_name: Optional[HookName] = Header(None),
) -> None:
    """
    Upload stream in database.

    :param hook: hook information.

    :param auth: service to validate authorization header.

    :param hook_name: hook name

    :raises HTTPException: if you dumb enough to simulate rustus.
    """
    auth.jwt_required()
    upload_id = hook.upload.id
    if hook_name == HookName.PRE_CREATE:
        logger.info("Stream upload started.")
        return
    elif hook_name == HookName.POST_TERMINATE:
        logger.info(f"Removing stream for upload_id={upload_id}")
        await Stream.filter(upload_id=hook.upload.id).delete()
    elif hook_name == HookName.POST_FINISH:
        logger.info(f"Stream upload_id={upload_id} successfully uploaded")
        user = await AdminTable.get(username=auth.get_jwt_subject())
        await Stream.create(
            upload_id=hook.upload.id,
            order=await Stream.all().count(),
            path=hook.upload.path,
            created_by=user,
        )
    else:
        raise HTTPException(
            status_code=status.HTTP_400_BAD_REQUEST,
            detail="Are you drunk?",
        )

That's the whole code to handle uploads. I use rustus with these parameters:
    RUSTUS_MAX_BODY_SIZE: "1000000"
    RUSTUS_DIR_STRUCTURE: "{year}/{month}/{day}"
    RUSTUS_TUS_EXTENSIONS: "getting,creation,termination"
    RUSTUS_HOOKS_HTTP_PROXY_HEADERS: "Authorization"
    RUSTUS_HOOKS_HTTP_URLS: "http://{my_service}/rustus_hooks"
    RUSTUS_HOOKS: "pre-create,post-terminate,post-finish"

I hope it helped you.

That definitely helps! Thank you :)

I'm really glad, you find this project useful.
If it works for you, please consider closing the issue.

Or maybe before closing it would be nice to add examples section in docs.

Yes I think it would be useful to show a few recipes/patterns in the docs.
I'm thinking one of:

minimal example with a tus client
authenticated transfer (the above example)
wetransfer-like (several files are added in something like a virtual folder)

Good set of cases. I will try to implement suggested examples and will put them in folder inside this repo.


FORCE_REDOWNLOAD does not work

Describe the bug
With GenerateMode.FORCE_REDOWNLOAD, the documentation says
+------------------------------------+-----------+---------+
|                                    | Downloads | Dataset |
+====================================+===========+=========+
| REUSE_DATASET_IF_EXISTS (default)| Reuse     | Reuse   |
+------------------------------------+-----------+---------+
| REUSE_CACHE_IF_EXISTS            | Reuse     | Fresh   |
+------------------------------------+-----------+---------+
| FORCE_REDOWNLOAD                 | Fresh     | Fresh   |
+------------------------------------+-----------+---------+
However, the old dataset is loaded even when FORCE_REDOWNLOAD is chosen.
Steps to reproduce the bug

import pandas as pd
from datasets import load_dataset, GenerateMode
pd.DataFrame(range(5), columns=['numbers']).to_csv('/tmp/test.tsv.gz', index=False)
ee = load_dataset('csv', data_files=['/tmp/test.tsv.gz'], delimiter='\t', split='train', download_mode=GenerateMode.FORCE_REDOWNLOAD)
print(ee)
pd.DataFrame(range(10), columns=['numerals']).to_csv('/tmp/test.tsv.gz', index=False)
ee = load_dataset('csv', data_files=['/tmp/test.tsv.gz'], delimiter='\t', split='train', download_mode=GenerateMode.FORCE_REDOWNLOAD)
print(ee)

Expected results
Dataset({
features: ['numbers'],
num_rows: 5
})
Dataset({
features: ['numerals'],
num_rows: 10
})
Actual results
Dataset({
features: ['numbers'],
num_rows: 5
})
Dataset({
features: ['numbers'],
num_rows: 5
})
Environment info

datasets version: 1.8.0
Platform: Linux-4.14.181-108.257.amzn1.x86_64-x86_64-with-glibc2.10
Python version: 3.7.10
PyArrow version: 3.0.0

Hi ! Thanks for reporting. The error seems to happen only if you use compressed files.
The second dataset is prepared in another dataset cache directory than the first - which is normal, since the source file is different. However, it doesn't uncompress the new data file because it finds the old uncompressed data in the extraction cache directory.
If we fix the extraction cache mechanism to uncompress a local file if it changed then it should fix the issue.
Currently the extraction cache mechanism only takes into account the path of the compressed file, which is an issue.


404 handler still logs in Episerver default EPiServerErrors.log

We have setup the 404handler in our solution. Unfortunately we are seeing a lot of messages like this in our EPiServerErrors.log file:
2017-03-24 07:25:00,806 [951] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
2017-03-24 07:25:04,821 [2118] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
2017-03-24 07:25:09,884 [2435] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
2017-03-24 07:25:30,915 [2161] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
2017-03-24 07:25:46,665 [2161] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
2017-03-24 07:26:34,103 [2118] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
2017-03-24 07:26:34,462 [4036] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
2017-03-24 07:26:38,134 [3965] ERROR EPiServer.Global: 1.2.5 Unhandled exception in ASP.NET
Our debugging have identified that these log lines corresponds to 404 requests being caught by the 404 handler but still being logged by Episerver. We have tried to register our own handler for UnhandledExceptions in Global.asax, and can get an output like this:
2017-03-24 07:25:04,821 [2118] ERROR UnhandledExceptions: Unhandled Exception
System.Web.HttpException (0x80004005): The controller for path '/favicon.ico' was not found or does not implement IController.
at System.Web.Mvc.DefaultControllerFactory.GetControllerInstance(RequestContext requestContext, Type controllerType)
at System.Web.Mvc.DefaultControllerFactory.CreateController(RequestContext requestContext, String controllerName)
at System.Web.Mvc.MvcHandler.ProcessRequestInit(HttpContextBase httpContext, IController& controller, IControllerFactory& factory)
at System.Web.Mvc.MvcHandler.BeginProcessRequest(HttpContextBase httpContext, AsyncCallback callback, Object state)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
In the Episerver documentation there is a listing of the Episerver.Global. It is probably a bit old, but I think the UnhandledException handling is still close to how it is today: http://world.episerver.com/documentation/class-library/?documentId=cms/7/e9e09ee4-16f6-ec1e-fc40-180b192c7f05
See this the method below.
Somehow the exception handled by the 404 handler still triggers the Global_Error eventlistener, but the Server.GetLastError() method returns null. This means that the logging line only logs the method, and since e=null, no exception is logged.
Question: Is this something you can handle in the 404handler, or do we need to involve Episerver to get them to fix their event handling?
private void Global_Error(object sender, EventArgs evt)
{
if (HttpContext.Current == null)
{
return;
}
        Exception e;
        try
        {
            //Get the previous exception
            e = Server.GetLastError();
        }
        catch
        {
            return;
        }

        if (e is UnauthorizedAccessException)
        {
            HandleAccessDenied();
        }

        _log.Error("1.2.5 Unhandled exception in ASP.NET", e);

        // Try to get the InconsistentDataException instance that caused the current exception
        InconsistentDataException inconsistent = e.InnerException as InconsistentDataException;
        if (inconsistent != null)
        {
            // The rare case where a delayed long string load fails to retrieve the correct data. Clear cache for
            // the relevant page to avoid that this error happens again for the same page.
            CacheManager.Remove("EPPageData:" + new PageReference(inconsistent.PageLink.ID, EPiServer.Configuration.Settings.Instance.Parent.SiteId).ToString());
        }

        if (!EnableGlobalErrorHandling)
        {
            return;
        }

        if (HttpContext.Current.Items.Contains("EPHandledUnhandledException"))
        {
            return;
        }

        try
        {
            // Clears the previous exception
            Server.ClearError();
            HttpContext.Current.Items.Add("EPHandledUnhandledException", true);
            //Clears all content output from the buffer stream
            Response.Clear();
            //Renders an error message to the user based on the exception
            ExceptionManager.RenderHttpRuntimeError(e);
            Response.End();
        }
        catch
        {
        }
    }

Thank you for your help.
Regards
Anders

Do you still have this issue?
This was a bug in Episerver which is fixed in the latest versions.


Error when module name starts with markdown delimiters

I tried to set the module name to "`My` first test module" then to "`My first test module" then to "*My first test module". Here are the errors I got:
ERROR: YAMLError: end of the stream or a document separator is expected at line 2, column 8:
    title: `My` first test module
           ^
ERROR: 500 (Internal Error): end of the stream or a document separator is expected at line 2, column 8:
    title: `My` first test module
           ^
ERROR: YAMLError: end of the stream or a document separator is expected at line 2, column 8:
    title: `My first test module
           ^
ERROR: 500 (Internal Error): end of the stream or a document separator is expected at line 2, column 8:
    title: `My first test module
           ^
ERROR: YAMLError: unidentified alias "My" at line 2, column 11:
    title: *My first test module
              ^

Granted, they are corner cases.

That should be fixed in master now. Thanks for the report.


Documentation Site

Hey so I was thinking, one thing this project is missing is a documentation site.
I don't know of any nextjs based static documentation generator type projects like docusaurus from facebook or docz with gatsby, but I could whip up a demo docz site which just takes the markdown pages that are already here / in the process of being written for v2, and display them nicely / makes them searchable, etc.
We could throw it up on now.sh and we'd be good to go.
Also js.org allows open source projects to grab subdomains for free, so I could get us next-auth.js.org to redirect to our docs page or the repo or whatever you want.
What do you think @iaincollins ? Might be nice to release a good looking docs page in tandem with v2 soon :)

I think this is a great idea! I completely agree I think would be helpful to have a site with solid documentation and example usage (especially for advanced configuration options).
If you can set up next-auth.js.org that would be great!

@iaincollins great! I've got a working example up here: https://next-auth-docs-1dzm2ljbf.now.sh/
I couldn't find a logo for the project anywhere, but if you have one you'd like me to use or prefer any specifics primarily colors for the project just let me know.
Currently this is all coming out of a subfolder (/docs) of a fork I made of next-auth/next-auth-2 about an hour ago ndom91/next-auth.
I can keep it separate, or if you want to me to make a PR to merge the docs subfolder into here I can do that too. Just let me know how you prefer to do it.

This looks fantastic, a PR would be great!
I really like how it extracts headings and the code block highlighting makes the docs easy to read.
I have no thoughts on branding / colours at the moment! (Agree I think it's helpful to have consistent branding, just don't have a view on it currently!)
cc @LoriKarikari who has been working on provider docs

Okay yeah no problem. I'll put together a PR then shortly. I'm assuming you want it to your v2 branch, right? Not the master?
Also how should we manage the now.sh hosting / deploying? It currently runs under my now.sh account and is linked to my fork of the repo. If the docs move into your primary repo, we have to relink the now.sh project.
I'm not sure the best way to go about this to be honest, but I think I need to have some sort of rights to this repo in order to link it inside my now.sh dashboard.
The other option would be that I completely delete my now.sh project and you can create a new one there. Important is just that you use the same project name so that we get the same ...now.sh url so that next-auth.js.org points to the correct place.
Thoughts?

Also, what's the name of this project? Is it NextAuth or next-auth? 😅 want to be consistent on the website and the documentation.

Oh also, currently the docs are "duplicated" because the markdown files are still in the root of the project, i.e. README.md, README-CLIENT.md, etc. I'll tighten up the normal README.md a bit in my PR so that Github still has a nice readme on the frontpage, with links to the docs page of course. The other documentation markdown files (README-CLIENT, AUTH, etc.) can just be deleted out of the root so that they're only located in the /docs subfolder then, right?

That sounds perfect!
I guess only doc we need in the root is the README.md, which also gets displayed on the NPM page and probably should make sense to have a quick summary, example usage, links to more docs and credits to contributors.

Also how should we manage the now.sh hosting / deploying? It currently runs under my now.sh account and is linked to my fork of the repo. If the docs move into your primary repo, we have to relink the now.sh project.
I'm not sure the best way to go about this to be honest, but I think I need to have some sort of rights to this repo in order to link it inside my now.sh dashboard.

Ooh, we could make a Team in now.sh maybe, so multiple folk can access? (I'm not sure if you can move existing URLs into a team, but I guess we could create a new one/redirect to another URL).

Yeah great, I'll make a draft of that README in my PR then and you can obviously adjust it then however you see fit.
Regarding the hosting - I just thought of something else, maybe its easier to host it out of github pages? They have docs for that specific setup here: https://v2.docusaurus.io/docs/deployment/#deploying-to-github-pages

Okay yeah no problem. I'll put together a PR then shortly. I'm assuming you want it to your v2 branch, right? Not the master?

If it's helpful and everyone is cool with that I am happy for us to merge the current v2 branch into master anytime now.

I just checked, teams in vercel / now.sh are not free at all unfortunately :/ $20 per seat with 14 day trial

Okay then what do you think about this?
I'll clean up the docs situation in the root folder and make a PR and see if I can find a github action template for deploying docusaurus. If that all looks good you could accept that and then merge into yuor master?

Okay PR is up: https://github.com/iaincollins/next-auth/pull/119
@LoriKarikari if you want to add any docs, simply put them in the /docs/docs/ folder and don't forget to add the page to the sidebar at /docs/sidebar.js. (I know its a bid odd with the docs subfolder for the docs subproject, and then another docs subfolder for the markdown content itself :/ )
The sidebar works like this:

The id, i.e. getting-started is just the filenames in relation to the /docs/docs folder. So if you create a new doc here, for example: /docs/docs/providers.md then the sidebar.js entry would just be:
'v2': [
  ...
  'providers',
],

Also, what's the name of this project? Is it NextAuth or next-auth? 😅 want to be consistent on the website and the documentation.

@LoriKarikari Thank you for raising that! That is a great question.
The NPM package has always been next-auth but I've tired (but sometimes failed) to use NextAuth as the name when referencing it in documentation.
To add to confusion, I see some guys with a mobile auth package registered the domain nextauth.com and renamed their product, which was previously called n-auth, to NextAuth.
They also grabbed the org name github.com/next-auth. To be clear though, they did this after I'd published NextAuth (this package), they just renamed their product with the same name.
This is a bit annoying and I'm not sure what to do about it. I am happy to keep calling this package NextAuth as not only did this package come first, but it doesn't look like they have any published open source software anyone is using (just the old n-auth package, which has one star).
However, I'm also open to renaming it! I don't think that should hold things up, but there is any consensus around changing the name I'm open to it.

@ndom91 I just pushed my docs before I saw this message lol. It's currently in a docs. Can change it if you want.

I would vote for keeping ./docs/* as just for Markdown docs, and creating another directory (e.g. /www?) for the website.
If it's not possible to handle this easily in config an okay for making a build step that does something like copies the docs into www/docs (e.g. in a build or dist directory).

@iaincollins ooh, I was too fast merging that. Sorry about that!

Yeah it seems they have to be in docs subdirectory.
You could just rename the first /docs folder www so that its /www/docs/content1.md, for example. That way we can skip a build step. The docs subfolder just wont be at the root of the project, I dont know how much of a problem that is for you guys.

Also just FYI, regarding the build step for building docusaurus, heres the docs from them and an example github action I found:

https://v2.docusaurus.io/docs/deployment/#deploying-to-github-pages
https://github.com/clay/docusaurus-github-action

@LoriKarikari  No worries. :-)

You could just rename the first /docs folder www so that its /www/docs/content1.md, for example. That way we can skip a build step. The docs subfolder just wont be at the root of the project, I dont know how much of a problem that is for you guys.

Oh cool, okay I might do that as I think it's slightly nicer.
I would love to have /docs at the root (as that's what GitHub Pages looks for it seems) but actually if there is a great website, maybe that doesn't matter so much.
Let me know if I should do anything with GitHub pages on the repo! (I will try and figure it out now. :)
I am going to copy current master in to v1 and then merge the v2 branch to be master, so we can all just work off that. :-)

So it's only the /www/docs folder then?

Okay I'll hold off on any further changes, etc. until the whole master -> v1 && v2 -> master is complete.
Until then I'll do some research about how to most easily get this into github pages.

Oh wait a seconddd, I think the Vercel team was not free because I already had one. That was completely unused though.
Anyway, I added another one and you guys can join that.
Tbh I think doing it over Vercel just fits a bit better. They take care of the  building and deployment previews, etc. all automatically (they have templates for docusaurus already built in too with their build commands, etc.). Not to mention this is a next based product, or at least began life as such ;)

@ndom91 Thanks, this is helpful! I am not sure the best way to do it but think this is important so appreciate you investigating! I'll add you as a contributor so you can make changes.
(As this is a personal repo and not an organisation one, I'm not sure if it will give you all the access you need for this, but will do that now and see how it goes! If you are missing access to anything after having contributor permissions just let me know and happy to make those changes!)

Okay great, thanks! I think contributor permissions should be enough

Damn it.. So without an Organisation there doesnt seem to be a way for me to do it :disappointed:
I tried the mirror variant, but it in fact does not update automatically. Netlify is the same deal - organisations only. I can send you the settings I used for now.sh if you're up for doing it yourself, it wasn't very difficult.

Let me know if thats the route you want to go. That way I will delete my project named next-auth-docs so that you can take that name and our js.org PR will still be valid ;)

Sucks that the org is taken 😢

Yeah :cry:
Oh well, I just deleted the now.sh project. If you create it with the name next-auth-docs it will be good to go and then we can still all collaborate inside this github project. The now.sh thing will update automatically once its setup once.

@iaincollins @LoriKarikari I merged our latest changes to the docs site into master, unfortunately it can't deploy to https://next-auth-docs.now.sh yet since the next-auth.js.org CNAME still isn't updated by those folks.
Until then though, here are the two latest preview URLs:

https://next-auth-docs-git-add-auth0.iaincollins.now.sh/
https://next-auth-docs-git-docs-update-1.iaincollins.now.sh/

And thats all for me for tonight. Thanks a lot guys and girls!

@ndom91 it's enough for me too haha. Night night!

The documentation site is up and running now.


Added option for Sidekiq macro that skips jobs that already queued.

We've started using Heroku to handle requests that go above the capacity of our infrastructure. We want to only have Hirefire scale when worker are waiting in the queue. I thought this option might be useful to others as well.

Hey Jarrett, hope all is well and thanks for the PR!
Looks good, though perhaps the terminology might be a bit confusing.
Rather than skip_queued, perhaps skip_working or skip_processing would be more accurate. What do you think?

@mrrooijen that seems fine to me. I was a little undecided on the name and just decided on that since it was the best I could think of. I'll change it to skip_working.

I'll probably cut a gem later today which will incorporate your changes. Waiting on another PR before I do so. I'll drop a message here once a new gem has been released. Thanks!

v0.9.0 has been released.


Feature Request: NTLM support for HTTP::Client

Right now HTTP::Client supports basic authentication, addition for NTLM (maybe even Kerberos?) could be really helpful to those working against Microsoft based products.

I think it could be done in a shard first, and if it's really necessary for a lot of people, add it to the stdlib but I doubt it a little.

@bew I really think that is we have basic_auth we should have NTLM support too, Ruby has it (I know it's not a good reason) and we can take most of the implementation details from there

Basic auth is a lot simpler than these other auth types and way more common. I doubt this will ever be in the stdlib.

@bararchy Are you sure Ruby has it built-in? I can only find gems about it.

My bad, I though Net::NTLM was in STD, apparently it was a gem.
http://www.rubydoc.info/gems/rubyntlm/0.5.0/Net/NTLM
So, I guess same logic should be in Crystal, I'll close the issue.


SAK-40212: web content > explain why pop-up behaviour changes for https vs http links

https://jira.sakaiproject.org/browse/SAK-40212
Due to mixed content rules in browsers, the behaviour of the "Open in new window?" option differs if the provided link is either https or http. Provide a brief explanation of this behaviour:
Note: Applies only to secure (https://) URLs. A non-secure (http://) URL will always open in a new window.

Travis build failure unrelated:
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.3:gulp (gulp build) on project rubrics-service: Failed to run task: 'gulp.js build' failed. (error code 1) -> [Help 1]

Thanks, @ottenhoff. Updated with your suggestion.


Fix account schema attribute "isMulti"

The incorrect account schema attribute "isMultiValued" has been corrected to the correct attribute name "isMulti".

Hey @Anneragh,
With the way that our SDKs are generated these files cannot be modified directly. I've made the changes in our API specs and we have given you the ambassador points for this change! Thank you for helping us make the SDKs better!


Add Sigstore claimant model

The Sigstore claimant model formally defines a set of claims made by Sigstore's two transparency logs. This was created in collaboration with the creators of the claimant model.
This also includes sequence diagrams to make it easier to understand how the various actors interact. These are a work in progress and generated by a tool in Trillian.

Summary

Release Note

Documentation

cc @bobcallaway @SantiagoTorres

@mhutchinson @bobcallaway for another review


Minor tidy-up in the make/framework.mk file

Changed some places in make/framework.mk where a target was referring to itself by name to use the $@ notation instead.

@litstrong: Any chance you or one of the owners of this project can review this pull request? 🙏 It's a non-functional change. Just a tiny bit of tidy-up.


Build tofnd cross platform

Allow building the tofnd binary plus containers cross platform the same way we have golang builds cross platform.

Pipeline is done.
PR : https://github.com/axelarnetwork/tofnd/pull/277

changes merged in


Where is MACHINE set?

Brief Issue Summary
We are building an entire embedded Linux operating system. A component supplier has provided a Yocto environment including a custom layer for their part. We are adding a couple of modules to their layer. It all works for our embedded OS. In order to develop our new code we are trying to get it to build inside VS-Code.
CMake Tools Log
The CMake/Build output panel shows:
[cmake] CMake Error at tools-public/packaging/packaging.cmake:7 (message):
[cmake]   MACHINE is not defined!
[cmake] Call Stack (most recent call first):
[cmake]   CMakeLists.txt:505 (include)
Platform and Versions

Operating System: Ubuntu 16.04
CMake Version: 3.18.6
VSCode Version: 1.55.2
CMake Tools Extension Version: 1.7.0
Compiler/Toolchain: Clang 9.0.0

Other Notes/Information
I expected to be able to set MACHINE in one of the .vscode/*.json configuration files but have not had any success yet.

A full build for an embedded machine would look like:
./run_configure.py
cd build
source setup-yocto
MACHINE= nice bitbake yocto-nsdk-ip-image-swu
I deleted the .build-pc directory and ran
./run_configure.py pc
The error did not appear. Up to 60% of the files compiled until other errors occurred.
I will try the cmake.configureXX settings if it fails again.

Does that script just define a bunch of variables, or does it also call into CMake?  If it sets up the environment for you and you only need to run it once, you could run it in your terminal before launching vscode, and then when you do launch vscode from that terminal, the environment will be inherited for configuration and build.
Another option is to create a "Kit" in your workspace and set the environmentSetupScript property to your python script.
If neither of those options work for you, then your scenario should be covered by #477 which we plan to get to soon.

run_configure.py configures the environment. setup-yocto fetches code from public repositories. bitbake calls code that uses cmake. My issue was when I was trying to work three levels below the root.

Mixing command line and vs-code builds caused problems. The project will not build using CLang so we have abandoned it.


Do you like to have native support of Allure Framework

Hi there! Do you like to have native support of Allure Framework? We would like to move Allure integration code to your repository, so you could maintain it at your will and e.g. add early support of your new features. We on our turn would like to move a little bit away from solving test framework specific issues and concentrate on general reporting problems to make Allure rock. What do you guys think?

What does it mean? Having your allure-testng-adaptor module here? Or are yoy thinking about something else?
I don't really like the idea more things here but why not having a dedicated repository under the @allure-framework or @testng-team organisation (and adding appropriate rights to be able to contribute easily)?
I'm ok to give you some help, but I've no idea what it means.

BTW, Allure already rocks! ;p

@juherr My understanding is that @baev would like to transfer the Allure-TestNG integration to TestNG, so they can focus on the core and leave external integrations to interested parties.
I don't have a problem with that, although obviously, such a transfer doesn't mean we'll be working actively on it, it will heavily depend on who wants to contribute.

Yes, it is what I understood too. So, I think @testng-team is the best place for it.

What does it mean? Having your allure-testng-adaptor module here? Or are yoy thinking about something else?

Yep, we would like to move Allure adaptor source code to your repository (I can send you the pull request with all the changes). It would also be great to see Allure as default TestNg report. Also it would be nice to support your test grouping (as far as I know usually TestNG users are using Suite -> Test -> Class -> Method grouping), save all parameters to the report and so on. Could you also briefly describe how do you see a perfect report? Would you like to have Allure as default one?

BTW, Allure already rocks! ;p

Thanks!

although obviously, such a transfer doesn't mean we'll be working actively on it, it will heavily depend on who wants to contribute.

The problem is that our team doesn't use the TestNG at all, so we don't have any valuable TestNG expertise. For now allure-testng-adaptor is supported mostly by the community as well.

I can send you the pull request with all the changes

Just tell me what is the related code.

It would also be great to see Allure as default TestNg report

It should be a user choice. I'd prefer to remove the current default html one :]

how do you see a perfect report?

No opinion, it depends un user needs. But IMO, something dynamic could be awesome. See http://stackoverflow.com/q/37746067/4234729

The problem is that our team doesn't use the TestNG at all

You should! ;)
BTW, it's just my opinion and @cbeust will have final words :)

@baev I created https://github.com/testng-team/allure-testng-adaptor (history kept) and gave you admin rigths on the repository.

It should be a user choice. I'd prefer to remove the current default html one :]

Where could we vote?

No need to vote: You already manage your dependencies yourself.
And when I say "remove", I mean "extracted in a dedicated dep".
But nothing is planned, I'm just sharing my minds.

Then it seems logical to add a chapter about this reporting option to TestNG documentation.

@RocketRaccoon Like http://testng.org/doc/documentation-main.html#testng-listeners and/or http://testng.org/doc/documentation-main.html#logging ?

@baev @cbeust @juherr the main question I'm a bit worried about is how you're going to perform allure-testng-adaptor integration testing? Technically adaptor is now located outside both projects, but it still contains corresponding testng / allure dependencies. Leaving it to community means that people must be aware of both projects' core updates. Otherwise, any PR to adaptor may completely break everything. This should have at least CI support for reports visualization.
The other question is: who is going to have a final word regarding dependencies / java version updates? E.g. Allure 2 is re-written on Java 8. Testng is still on Java 7. Adaptor has both dependencies. What would be a new version of allure-testng-adaptor? Or there will be the same unsuccessful discussion as in https://github.com/cbeust/testng/issues/864?

@juherr Yes, but dedicated to Allure features

@sskorol

how you're going to perform allure-testng-adaptor integration testing?

+1 It is something I planned to ask too. How could we test it? What is already available? ...

What would be a new version of allure-testng-adaptor?

About the Java dependency, it is easy to answer:

it is not planned to move TestNG core in java8
allure-testng-adaptor will have to follow the higher java version of its dependencies

@RocketRaccoon A link to https://github.com/allure-framework/allure-core/wiki/TestNG (or its future new place)?

@juherr At least for beginnig... We currently have testing framework based on TestNG with powered ReportNG, but moving reporting to Allure. I could provide some code examples of extended usage of TestNG Listeners and Allure, which could be useful for newcomers.

allure-testng-adaptor will have to follow the higher java version of its dependencies

@juherr correct. I just want to make sure that no one would then say: "hey, this project is a part of testng, so it should have the same java version". :)

@RocketRaccoon Depending on the size of the sample, feel free to create a dedicated repository. Then I can host it under @testng-team and provide you push rights on this repo.
@sskorol To be honnest, I think @allure-framework is a better place for allure-testng-adaptor. But it is not a problem to host it under @testng-team

Looking at it from different angle I'd conclude the following:

Allure team: hi TestNG team, do you want to support our adaptor, as we're not aware of your internals?
TestNG team: not really, but let's give it to our community! Someone may want to give it a shot, but if not - it's not our business.
Allure team: ok, pushing code... Done. Now it's yours.
TestNG team: ok, but it's not ours, it now belongs to the entire community!
:)

@sskorol calm down. Give me some time and I'll try to explain to you what is going on (kinda busy right now).

@baev ok, would be appreciated :)

@sskorol
The "problem" about testng team is: https://github.com/cbeust/testng/graphs/contributors?from=2015-06-28&to=2016-06-28&type=c or https://github.com/cbeust/testng-eclipse/graphs/contributors?from=2015-06-28&to=2016-06-28&type=c
As usual, it's a time issue and I'm not sure that only the free time of 3 persons is enough to support more.
I'm open to provide some help to allure because I like what they are doing, but the TestNG core will be always my priority :)
For the moment, I've just imported sources to understand the context and nothing is done.
BTW, you should considere to propose some help on both projects if you want a better support ;)

@juherr fyi, I'm already contributing to Allure, so I'm interested in keeping testng-adaptor alive. ;) But it doesn't really mean that I want to do it without any assistance. Both teams should cooperate together as only main committers know everything about projects' architecture, further plans, and potential pitfalls. And leaving it purely to community won't be an option at all. Anyway, I don't have a full picture about allure team intentions, so will just wait for some comments / details.

Sorry for the delay. Seems like I should start this discussion with the following explanation.
Allure consists of two big parts: report generation tool and a collection of adapters for different test frameworks. Adapters save test execution results for each test framework to a predefined format which is then used to generate a report.
So far as we have sufficient experience with JUnit and TestNG frameworks, respective adapters reside in main Allure repository and we spend more time improving them.
The rest of adapters are community-driven projects and live in separate repositories. They have different level of integration with Allure: some adapters correctly map test execution data to most of Allure features and some support only basic ones.
The first important problem I would like to talk about is the following. Very often test framework developers are not aware of existing Allure adapter or consider it an independent project. But unfortunately it’s a common case when we have no knowledge of concrete test framework or no time to fix created issues ourselves. We would like to fix this by better collaborating with test framework developers.
From the other side being compared with other approaches adapters are a big advantage of Allure. For example surefire.xml are not supporting all newest reporting trends and requirements. This is why we implemented a separate data storage format used to generate a report.
For the moment, our experience in communicating with real Allure users from different test frameworks we understood that the next data storage format should be adopted. For example current format sometimes does not correctly support test classification approaches widely used in some test frameworks. Also it would be great to use event-driven model for real-time reporting functionality.
The second problem I would discuss is Allure data storage format. It seems that we need to update it again to support new requirements. What we would like to do is to create an open data storage format for test frameworks being supported by the majority of existing frameworks and newcomers.
Having a common data format supported by the most important test frameworks we would concentrate on improving report generation part of Allure. We would like to propose you to participate in this work as the first framework supporting new format. We think your project is the best candidate for this purpose because you have a lot of loyal users and very flexible test grouping capabilities.
There is no need to move our code to your repository right now. All we need is consider the stages we need to complete before you be able to move the integration to your repository. Yep, personally I’d like to create a new module in TestNG repository. It would be much easier to test and support the integration in your repository, not in the separated one. But for now the most important thing is team collaboration on the way to perfect reporting tool.

We would like to fix this by better collaborating with test framework developers.

Feel free to ping me on testng related issues ;)

We would like to propose you to participate in this work as the first framework supporting new format.

What will be the expected effort? Writing a reporter is not a big one if we have a nice library that helps to generate the good format.

Feel free to ping me on testng related issues ;)

@juherr I just started my work on new TestNG adapter and have a few questions. Is there any place where we can discuss them (we can use this issue or create a new one, or use some kind of im like gitter)

@baev https://groups.google.com/forum/#!forum/testng-dev ?

@juherr I created 2 topics, both about the same problem but I guess the second is more clear one, so you can approve only the second one

@baev I'm not seeing them. Could you provide a link?

Nope, I cant see pending posts

@juherr - Is this discussion underway ? Just going through issues to see which of them can be closed.

@krmahadevan I don't know. It looks Allure still maintain the testng support with https://github.com/allure-framework/allure-java
@baev What is the current plan?

For now we decided to keep the integration in our repository.
At the moment the only issue is that there is no listener for data provider methods (see https://groups.google.com/forum/#!topic/testng-dev/WASvXfvq3_M )
BTW Thanks you guys for support

@baev Thanks. I've added an issue for the listener part #1490


Troubles with addon package - frontend port, unable to set devices in config

zigbee2mqtt add-on version:
<IP_ADDRESS>
Operating environment (HassOS, Virtual Machine, Device/platform running Home Assistant):
HA-supervised 2021.1.1 on RPI2
Description of problem:
I tried to find define a friendly_name for zigbee devices. Manuals say, that I have to place a block in section 'devices' into file configuration.yaml.
I'm a newbie with HA and searched, which one of config file it should be (for HA and z2m they have same name configuration.yaml). Pasting this section in HA config was faulty (no integration named 'devices') - I found, that config for z2m have such section. But my tries to paste block with friendly_name to this section was faulty too!
I found, that z2m has a frontend, where I can set friendly_name - but default port 8099 and the another one 8080, that i used in manuals - are not responding (404).
Netstat on rpi said, that 8099 and 8080 are not listening. But is listening port 8485, that by description is "Socat tcp-listen port" (which is disabled).
After configuration frontend to port 8485 - it becomes accessible.
It seems, that there are not enough ports proxied from z2m docker image to host and schema for config is to rigid and blocks to put a valid data.
Your entire configuration from the frontend (with sensitive fields redacted):
  "ports": {
    "8485/tcp": 8485
  },
  "ports_description": {
    "8485/tcp": "Socat tcp-listen port"
  },

"devices": "str?",

You should use most of the default settings. The frontend port is custom set to 8099 for easier usage using ingress. If you want to set friendly names you can use either the frontend or the file on the disk using some sort of file editor.
You can use terminal add-on or file editor add-on and navigate to /share/zigbee2mqtt/devices.yaml or /config/zigbee2mqtt/devices.yaml depending on your configuration and change what you need.


exception.hpp: warning C4265 given by Visual Studio

This has been reported before (https://svn.boost.org/trac10/ticket/13227), but I am not sure that tracker is still active. The problem is still relevant with boost 1.65.1 and 1.70.
Quoting:

MSVC falsely report a missing virtual destructor inside exception.hpp Would it be possible to add a "pragma warning (disable:4265)" in this file ? This will not happen with the default settings of Visual Studio : it happens when trying to raise the warning level (/we4265 : treat "misssing virtual destructor" as an error)

The above link has reproduction steps, in particular, https://github.com/ivsgroup/boost_warnings_minimal_demo

Sorry I had missed this. See https://github.com/boostorg/throw_exception/commit/43a57d518cf99fc693eebedefcbaa91074674f54

I know this is closed, but the warning / error doesn't appear to be a false report.  Instead of disabling the warning, shouldn't the destructor have been made virtual?

It is incorrect for this destructor to be virtual. The destructor is never called via a pointer to the base type.

As a general rule classes with virtual methods ought to have a virtual destructor which is the reason for the warning.  It certainly wouldn't hurt anything for the the destructor to be virtual.  There is nothing incorrect about a virtual, protected method.  It seems like it was more of a preference for someone to disable the warning.

It is a deliberate design decision. Marking a function virtual indicates dynamic polymorphism. In this design, calling the destructor polymorphically would be a logic error. In C++, this is communicated by declaring the destructor protected and non-virtual.


Feature/luna 212/embedding v3

Embedding v3 support
Node chagnes

added ability to select model (defaults to ada)
added ability to select dimensions

open ai function can pass those parameters now

@all-contributors please add @ShravanSunder for code


WIP | Feat/auto gen openapi docs

Added openAPI tab in request page to create openAPI documentation for the specific request.
I find this partial as the meaning for openAPI docs is to consolidate many requests. What do you think?

I agree that this is partial. This is good for now. We will extend this development to include multiple requests.


[BUG] Errors when opening file in Excel after saving a file with conditional formatting

🐛 Bug Report

Lib version: 3.9.0
Steps To Reproduce

const Excel = require("exceljs");
const fs = require("fs");

const inputFilePath = "input.xlsx";
const outputFilePath = "output.xlsx";

(async () => {
    const workbook = new Excel.Workbook();

    const data = await fs.promises.readFile(inputFilePath);

    await workbook.xlsx.load(data.buffer);

    // Write.
    await fs.promises.writeFile(outputFilePath, await workbook.xlsx.writeBuffer());
})().catch((e) => console.error(e));

input.xlsx
output.xlsx
Opening the output file with Excel results in the following:

<? version="1.0" encoding="UTF-8" standalone="yes"?>
<recoveryLog xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main">
  <logFileName>
    error043120_01.xml
  </logFileName>
  <summary>
    Errors were detected in file 'C:\Users\Rob\Documents\glen-tmp\output.xlsx'
  </summary>
  <removedParts summary="Following is a list of removed parts:">
    <removedPart>
      Removed Part: /xl/styles.xml part with XML error.  (Styles) Load error. Line 2, column 6585.
    </removedPart>
  </removedParts>
  <repairedRecords summary="Following is a list of repairs:">
    <repairedRecord>
      Repaired Records: Cell information from /xl/worksheets/sheet2.xml part
    </repairedRecord>
    <repairedRecord>
      Repaired Records: Column information from /xl/worksheets/sheet2.xml part
    </repairedRecord>
    <repairedRecord>
      Repaired Records: Conditional formatting from /xl/worksheets/sheet2.xml part
    </repairedRecord>
  </repairedRecords>
</recoveryLog>

Just opening and saving the file causes the file size to go from 33 KB to 14 KB. 😮
If I clear the conditional formatting in the input file, then I don't see the errors (although the file size still drops dramatically, which is a bit worrying).
The expected behaviour:

No errors when opening the file in Excel, and possibly more similar file size of input and output files.
Possible solution (optional, but very helpful):
n/a

Edit: Here's a smaller reproduction:
simple3-input.xlsx
simple3-output.xlsx

Have got the same issue. After a bit of investigation found that the rule value is broken.
So in the template:

But, once the doc is saved the following gets saved even if no changes have been made before that:

Hi,
I've been facing the same issue, it turns out the render in dxf-xform.js is rendering elements in the wrong order. Restoring the order to the one specified here http://www.datypic.com/sc/ooxml/e-ssml_dxf-1.html fixed the issue for me.

if you, like me, came here because of this bug and don't need conditional formatting, use this command on a worksheet:
worksheet.removeConditionalFormatting();

Fixed in  #1574


[Misc] Optimize Qwen2-VL LoRA test

I retrained a QWen-VL LoRA.  In my local environment using A800,   I tested the model on 100 image samples, the generation results were completely aligned with the transformers output.
BTW, add LoRA support for  vision modules and projecter modules

I assume this fixes the test?

I tested it on the A800 and it works without any issues. I used 100 samples for testing, and the generated results align perfectly with transformers. Regarding the previous LoRA, there might have been an issue during training. Although it could generate reasonable results, only about 30% of the outputs aligned correctly


[DOCS] Make the quick start less wordy and easier to understand

Why are the changes needed?

The current quick start is too wordy and not user-friendly.
In this PR, we simply the guide to let newcomers easier build a quick start deployment with Kyuubi and Spark only. The copied logs are removed the make the doc shorter.

How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[x] Add screenshots for manual tests if appropriate

[x] Run test locally before make a pull request

Thanks, merging to master


Tag a card

Is it possible to tag a card? Thanks!

hi @zhiboz!
Unfortunately, it's not possible to tag a card now on the latest version.
By the way, your feature sounds interesting, we will give it a think. 👍


Is validation check for integers too narrow?

I'm trying to incorporate UMAP into a pipeline which sets my n_component parameter to a numpy int64 at some point. This leads to a failed validation check (validate_parameters(), line 1309 of umap.py), since this is not an instance of a Python int.
I suggest either making the check more broad or just converting to an int?

Will be resolved in 0.4


Grey text doesn't appear, then appears after backspace-space

Easy to reproduce, happens often

Can you describe the issue here?

Grey text doesn't appear at all, but it gets saved in cache. If you hit Backspace, and then Space, you'll see quick completion coming from cache. Easy to reproduce -- happens a lot.

how do you know it is getting saved in cache?

but what makes you think that it is not just the original answer arriving slowly instead of a cached response?

Because originally you can wait as much as you want, the grey text will not appear.

Checked plugin version 0.0.2 from marketplace - problem is no longer reproducible.


opcode: add Futex{Wake,Wait,Waitv}

These opcodes are available since Linux 6.7, and are mentioned by #253. FutexWaitV expects a new struct futex_waitv which is available in linux-raw-sys. An opaque type is added to the main crate to avoid polling in the dependency.
See:

IORING_OP_FUTEX_{WAIT,WAKE}: https://github.com/torvalds/linux/commit/194bb58c6090e39bd7d9b9c888a079213628e1f6
IORING_OP_FUTEX_WAITV: https://github.com/torvalds/linux/commit/8f350194d5cfd7016d4cd44e433df0faa4d4a703

Exposed types::FutexWaitV and also fixed a typo in tests (waitv, not wakev).
I noticed that io-uring-test fails test_udp_recvmsg_multishot_trunc on my machine (io-uring-test/src/tests/net.rs:1549:25, assertion failed: msg.is_payload_truncated()), not sure if it's something kernel related (I'm on 6.9.0-rc2). But at least it seems unrelated.

Thank you!


Installing CumulusCI v 4 installs the latest version of urllib3 which seems to be incompatable with running ROBOT tests

Describe the bug
I am running a cci flow from a Github action and I started seeing the following error for every Robot test when running the Robot task.
Parent suite setup failed:
ValueError: Timeout value connect was <object object at 0x7f9212d244f0>, but it must be an int, float or None.
After some investigation I tracked it down to the urllib3 library. The latest version is 2.2.3 which is what is being installed with cumulusCI
Collecting urllib3<3,>=1.21.1 (from requests->cumulusci)
Downloading urllib3-2.2.3-py3-none-any.whl.metadata (6.5 kB)
If I add the step
  - name: Set urlib3 version
    run: |
      pip install urllib3==1.26.20
    shell: bash

after installing cumulus ci and before running the flow then it all works fine
Note that I am not using the standard cumulus Github actions. I had created my own which install the sf cli and cumulusci and then runs a version of the ci_feature flow.
I expect that this would be an issue in any installation that doesn't already have a version of urlib between 1.21.1 and 1.26.20
Reproduction steps

n. ...
Your CumulusCI and Python versions
CumulusCI version: 4.0.1
Python version: 3.13.0
Operating System
Ubuntu latest on a Github Action
Windows environment
No response
CumulusCI installation method
pip
Error Gist
No response
Additional information
No response

Thanks for the report. Looks like we pinned this in Snowfakery until recently. The issue is that we're pinning  robotframework-seleniumlibrary<6. We'll see whether we can remove that pin, and we'll restore the urllib3 pin if we can't.

We're also currently blocked due to this issue which hit us by surprise.

@Szandor72 The workaround is to make sure that you are using the correct version of that library, after you have installed cumulusci.
How are you experiencing this issue and are you still blocked?

We downgraded to cumulusci 3.87 for now because we don't want to be
responsible for managing CCI's internal package dependencies. We're
consumers not Pythonians.
On Mon, Nov 25, 2024, 3:11 PM liamcollerton-giveclarity <
@.***> wrote:

@Szandor72 https://github.com/Szandor72 The workaround is to make sure
that you are using the correct version of that library, after you have
installed cumulusci.
How are you experiencing this issue and are you still blocked?
—
Reply to this email directly, view it on GitHub
https://github.com/SFDO-Tooling/CumulusCI/issues/3849#issuecomment-2498126058,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAGS6TUDU3I4UDS4FIJOUL2CMVX3AVCNFSM6AAAAABSJ3NOTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIOJYGEZDMMBVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Szandor72 Sorry for the trouble caused by the recent changes. We made these updates to help with compliance on our end, but we didn't expect them to affect users as much as they have. It wasn't our intention to put you in a position where you have to manage our internal package dependencies—making things easier for ourselves while making it harder on our users is the opposite of what we want.

@Szandor72 Thank you for the kind words. We’ve been working on improving our test coverage and recently fixed some issues in our integration tests, which helped uncover these errors. That said, we should have caught it before release.


feat: add environment and commit_hash inputs

Fixes #15
Adds inputs:

environment (defaults to "preview")
commit_hash (not required)

Update deployment selection logic:

filter by commit_hash when provided
update environment selection to match input (instead of hardcoding to "preview")

Update tests

add a test to make sure we search through all deployment envs when environment is null
add a test to make sure we use commitHash when given

@ankushg what do you think about the changes?

Thanks @ankushg !


Bump Mesos to 396cda9cef532b9be980002d97e4aadf12ccec85.

High Level Description
This change contains file-based secrets and image pull secrets along with several bug fixes.
Related Issues
https://jira.mesosphere.com/browse/DCOS-10236 File-Based Secrets
https://jira.mesosphere.com/browse/CORE-810 Image pull secrets
Checklist for all PR's

[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
This PR relies upon Mesos test suite.
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): Mesos diff
[x] Test Results: ASF CI Results
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot bump-ee

LGTM!

@mesosphere-mergebot bump-ee

@mesosphere-mergebot label [Ready For Review]

@mesosphere-mergebot bump-ee

Holding until we fix the EE strict mode test failures

Closing in favor of https://github.com/dcos/dcos/pull/1653 with more recent master and fix for EE strict tests.