Nodemailer Mail sender

Closes:

Title :  Nodemailer
Name: :  Dhairya gothi
Idenitfy yourself: :  GSSOC

Describe the add-ons or changes you've made 📃
How Has This Been Tested? ⚙

Screenshots 📷

Type of change ☑

What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Note to reviewers 📄

@Avdhesh-Varshney sir please merge PR

Properly follow the instructions. I'm not told to anyone again & again.

Done @Avdhesh-Varshney

@Avdhesh-Varshney please tell anything else i need to change ?

@Avdhesh-Varshney please merge PR 31 july is last date for contributing PR

done @Avdhesh-Varshney


feat: function to trigger open/close dialog

Tried to search for it but didn't find a way to close the dialog with a method or function. This is useful after processing data like - making a fetch request, mutation, or something that is awaitable, or can change dialog state from outside
In the example below, let's assume when the user clicks to "save changes", I want to handle some submit function as a result close dialog from that function.
... await updateData(data).then(res=>closeDialog()).catch(err=>setError(error))

Currently, the way I see is used after exporting Close from radix primitive. But this is a JSX element, cant be used as function to change dialog state
<DialogClose>Close<<DialogClose/>

There is 2nd way to close Dialog by creating a state and binding it to open={open} prop in the Dialog component. We can open or close Dialog by changing that state. But when do so, the "X" button and clicking outside of the dialog to close it stops working
Why we need that feature?
I think this will solve the issue we have in Note section which asserts that we have to encase the trigger button to Dialog itself. I take this as a big problem because if I have a Dialog component, it's not possible to trigger it from multiple places. If I need to have that dialog in multiple places I need to copy/paste the same dialog code which is a duplication issue.
Sample use case: I have "Newsletter dialog" and I need to trigger this dialog with the button in the navbar, footer, or inside the main content. Or if the user stays for 5 mins on the website, I want to trigger that newsletter dialog

If you want control the opening state by yourself, the open prop is the way to go, however, you also need to set the onOpenChange, so that the close button wiil able to trigger the onOpenChange event and change the state that you created.

I am using Next13.4 app router in which all the components and pages are RSC and SSR respectively by default. I am rendering the Dialog in the custom component lets say AddToCartDialog.tsx in  server component and want to close it programmatically something like handleCloseDialog().
I can't pass the prop state and setter function as React hooks do not work inside React Server Components. Is there clean way to do it? Or should I add a redundant client component wrapper for the dialogs?

@OsamaQureshi147 It seems like you need JS on client side to me tho, this is the time where you have to use client component instead.

@OsamaQureshi147 For a basic requirement, you can probably use the searchParams and do a condition like:
/some-page?productId=69&modal=true
export default function Page({
  searchParams,
}: {
  searchParams: { [key: string]: string | string[] | undefined }
}) {
  const { productId, modal } = searchParams

  return (

Some Page

      <YourDialog open={modal === "true"} productId={productId} />

  )
}

Other than that, client component.

@wobsoriano The problem is I don't think you can use this approach if you're trying to open a modal from a Navbar which typically lives in an application's root layout, without adding 'use client' to the root layout then causing the entire application to be client rendered. This would only work on non root layout pages.

@wobsoriano The problem is you can't use this approach if you're trying to open a modal from any components that generally live in an applications root layout such as a Navbar since search params are not available in that context, but I think it's good approach for subpages.
Source: https://nextjs.org/docs/app/api-reference/file-conventions/layout#layouts-do-not-receive-searchparams

Right @msbeeman, I guess you can still use useSearchParams in the layout.
@chungweileong94 this might be worth checking as well - Intercepting Routes
Example - https://nextjs-app-route-interception.vercel.app/

@OsamaQureshi147 For a basic requirement, you can probably use the searchParams and do a condition like:
/some-page?productId=69&modal=true
export default function Page({
  searchParams,
}: {
  searchParams: { [key: string]: string | string[] | undefined }
}) {
  const { productId, modal } = searchParams

  return (

Some Page

      <YourDialog open={modal === "true"} productId={productId} />

  )
}

Then use <Link href="/some-page" /> to dismiss the modal.
Other than that, client component.
Demo:
Screen.Recording.2023-09-29.at.4.14.55.PM.mov

How can I make a required fields in the modal?

If you want control the opening state by yourself, the open prop is the way to go, however, you also need to set the onOpenChange, so that the close button wiil able to trigger the onOpenChange event and change the state that you created.
Example:
const [open, setOpen] = useState(false);

return <Dialog open={open} onOpenChange={setOpen} />

Reference: https://www.radix-ui.com/docs/primitives/components/dialog#root

thanks, not so clear in the doc!

If you want control the opening state by yourself, the open prop is the way to go, however, you also need to set the onOpenChange, so that the close button wiil able to trigger the onOpenChange event and change the state that you created.
Example:
const [open, setOpen] = useState(false);

return <Dialog open={open} onOpenChange={setOpen} />

Reference: https://www.radix-ui.com/docs/primitives/components/dialog#root

Thank you very much, after searching and trying for couples of hours, I finally could reach it!

Might help some https://levelup.gitconnected.com/adapting-the-shadcn-ui-dialog-for-parallel-and-intercepting-routes-next-js-shorts-818d02f602d3

I'm actually trying a different approach (https://github.com/chungweileong94/nextjs-parallel-route-dialog) by using the NextJS parallel route to control the dialog open state. The thing that I focus in my code example is to preserve the dialog closing animation.

I'm actually trying a different approach (https://github.com/chungweileong94/nextjs-parallel-route-dialog) by using the NextJS parallel route to control the dialog open state. The thing that I focus in my code example is to preserve the dialog closing animation.

I also did the same and I got stuck at that bit. In the end I did something like this:
@edit/page.tsx:
export default async function Page() {
const prisma = new PrismaClient()
// fetch data

return (
<DialogContent props={}/>
}

@edit/dialog-content.tsx:
"use client"
export default function EditDialog({ params }: Props) {

  const router = useRouter()
  const [isOpen, setIsOpen] = useState(true)

  function handleClose(): void {
    setIsOpen(false) // let the closing animation start

    setTimeout(() => {
      router.push(`/suppliers/${params.id}/overview`)
    }, 90) // then push the URL (I'm not looking for a page update here, but you could handle an update with a reload or something.)
  }

<Dialog open={isOpen} onOpenChange={() => { handleClose() }}>
...
</Dialog>
}

It's mostly pseudocode from my real running code, but that should hopefully at least point you in the right direction.

This is how we can do, hope it helps
"use client";
// Imports here

export function AddProductModal() {
  const router = useRouter();
  const [open, setOpen] = useState(false);

  return (
    <Dialog open={open} onOpenChange={setOpen}>
      <DialogTrigger asChild>
        <Button
          className="bg-red-50 text-red-600"
        >
          Add Product
        </Button>
      </DialogTrigger>
      <DialogContent className="sm:max-w-[425px]">
         // ADD PRODUCT FORM HERE
        <DialogFooter>
          <Button
            onClick={() => {
              addProduct(data).then(() => setOpen(false));
              router.refresh();
            }}
            className="bg-red-50 text-red-600 hover:bg-red-100"
            type="submit"
          >
            Add
          </Button>
        </DialogFooter>
      </DialogContent>
    </Dialog>
  );
}

I wonder if there is some sort of race condition that is causing it to sometimes not work?

Well, it works fine to fit my use-case. But I don't expect the close animation to work in cases like hard navigation.
I do notice some limitation to the close animation, where the content of the dialog actually close instantly as soon as it triggers, but the animation is fast enough that you wouldn't notice it😬
You could try to use the browser history API with NextJS 14.1, to see if that helps, https://nextjs.org/blog/next-14-1#windowhistorypushstate-and-windowhistoryreplacestate, haven't try it myself personally.
But I will say if you really want to get the animation right, move things to client-side is the way to go.

You could try to use the browser history API with NextJS 14.1, to see if that helps, https://nextjs.org/blog/next-14-1#windowhistorypushstate-and-windowhistoryreplacestate, haven't try it myself personally.

I'll give this a go, I'll report back! I've already been messing around with the router.

But I will say if you really want to get the animation right, move things to client-side is the way to go.
I think I much rather not. To the point, I'm willing to sacrifice the exit animation. Although I personally think it's easily doable. I mean it's like 90% there anyway already. I just need to work out what causes it to sometimes not work.

Either way, my code and then the changes based on your reorganisation of the folder structure based on your example has been really useful. So has Ariakit's Dialog with App Router documentation. I'll let you know if I get further with the exit animations.

If you want control the opening state by yourself, the open prop is the way to go, however, you also need to set the onOpenChange, so that the close button wiil able to trigger the onOpenChange event and change the state that you created.
Example:
const [open, setOpen] = useState(false);

return <Dialog open={open} onOpenChange={setOpen} />

Reference: https://www.radix-ui.com/docs/primitives/components/dialog#root

bruh, i suck
i was try digging in wrong "dialogtrigger"
wasted 3 days because of this. open dialog

const [open, setOpen] = useState(false);

I am using Next13.4 app router in which all the components and pages are RSC and SSR respectively by default. I am rendering the Dialog in the custom component lets say AddToCartDialog.tsx in server component and want to close it programmatically something like handleCloseDialog(). I can't pass the prop state and setter function as React hooks do not work inside React Server Components. Is there clean way to do it? Or should I add a redundant client component wrapper for the dialogs?

what is did is {!form.formState.isValid ? (

Save changes

) : (

Save changes

)}

{!form.formState.isValid ? (               <Button type="submit" className="w-full">                 Save changes               </Button>             ) : (               <DialogClose asChild>                 <Button type="submit" className="w-full">                   Save changes                 </Button>               </DialogClose>             )}
this worked for me :)

`const [open, setOpen] = React.useState(false)
const { reset } = form;
const { isSubmitting, isSubmitSuccessful } = form.formState;
React.useEffect(() => {
isSubmitSuccessful && reset()
}, [isSubmitSuccessful, reset])
`
Dialog closing and form reset (react-hook-form) working properly with this. Didn't add anything like value={field.value} in the <Select onValueChange={field.onChange} defaultValue={field.value}> tag or anything in <SelectValue placeholder="Select priority" /> this tag.

Very useful!

This is how we can do, hope it helps
"use client";
// Imports here

export function AddProductModal() {
  const router = useRouter();
  const [open, setOpen] = useState(false);

  return (
    <Dialog open={open} onOpenChange={setOpen}>
      <DialogTrigger asChild>
        <Button
          className="bg-red-50 text-red-600"
        >
          Add Product
        </Button>
      </DialogTrigger>
      <DialogContent className="sm:max-w-[425px]">
         // ADD PRODUCT FORM HERE
        <DialogFooter>
          <Button
            onClick={() => {
              addProduct(data).then(() => setOpen(false));
              router.refresh();
            }}
            className="bg-red-50 text-red-600 hover:bg-red-100"
            type="submit"
          >
            Add
          </Button>
        </DialogFooter>
      </DialogContent>
    </Dialog>
  );
}

Does this only work on submit? I have been trying it in other parts of the code but it never works...

This  worked for me !!
"use client";
import React, { useEffect, useState } from "react";
import {
  Dialog,
  DialogClose,
  DialogContent,
  DialogDescription,
  DialogFooter,
  DialogHeader,
  DialogTitle,
  DialogTrigger,
} from "@/Components/ui/dialog";
import { Button } from "./ui/button";
import Image from "next/image";
import Search from "./Search";
import { usePathname } from "next/navigation";

function SearchDialog() {
  const [open, setOpen] = useState(false);
  const pathname = usePathname();
  useEffect(() => {
    setOpen(false);
  }, [pathname]);
  return (
    <Dialog open={open} onOpenChange={setOpen}>
      <DialogTrigger className="z-10 cursor-pointer" asChild>
        <Image src="/search.svg" width={24} height={24} alt="search" />
      </DialogTrigger>
      <DialogContent className="rounded-xl">
        <DialogHeader>
          <DialogTitle>Share link</DialogTitle>
          <DialogDescription>
            Anyone who has this link will be able to view this.
            <DialogClose asChild>
              <Search />
            </DialogClose>
          </DialogDescription>
        </DialogHeader>

        <DialogFooter className="sm:justify-start">
          <DialogClose asChild>
            <Button type="button" variant="outline">
              Close
            </Button>
          </DialogClose>
        </DialogFooter>
      </DialogContent>
    </Dialog>
  );
}

export default SearchDialog;import React, { useEffect, useState } from "react";
import {
  Dialog,
  DialogClose,
  DialogContent,
  DialogDescription,
  DialogFooter,
  DialogHeader,
  DialogTitle,
  DialogTrigger,
} from "@/Components/ui/dialog";
import { Button } from "./ui/button";
import Image from "next/image";
import Search from "./Search";
import { usePathname } from "next/navigation";

function SearchDialog() {
  const [open, setOpen] = useState(false);
  const pathname = usePathname();
  useEffect(() => {
    setOpen(false);
  }, [pathname]);
  return (
    <Dialog open={open} onOpenChange={setOpen}>
      <DialogTrigger className="z-10 cursor-pointer" asChild>
        <Image src="/search.svg" width={24} height={24} alt="search" />
      </DialogTrigger>
      <DialogContent className="rounded-xl">
        <DialogHeader>
          <DialogTitle>Share link</DialogTitle>
          <DialogDescription>
            Anyone who has this link will be able to view this.
            <DialogClose asChild>
              <Search />
            </DialogClose>
          </DialogDescription>
        </DialogHeader>

        <DialogFooter className="sm:justify-start">
          <DialogClose asChild>
            <Button type="button" variant="outline">
              Close
            </Button>
          </DialogClose>
        </DialogFooter>
      </DialogContent>
    </Dialog>
  );
}

export default SearchDialog;

@OsamaQureshi147 For a basic requirement, you can probably use the searchParams and do a condition like:
/some-page?productId=69&modal=true
export default function Page({
  searchParams,
}: {
  searchParams: { [key: string]: string | string[] | undefined }
}) {
  const { productId, modal } = searchParams

  return (

Some Page

      <YourDialog open={modal === "true"} productId={productId} />

  )
}

Then use <Link href="/some-page" /> to dismiss the modal.
Other than that, client component.
Demo:
Screen.Recording.2023-09-29.at.4.14.55.PM.mov

I had a slightly different requirement to be able to open a modal using the normal DialogTrigger but also from my navigation bar component which was in my root layout. I was able use this approach with some slight adjustments to get it to work.
Code is here in-case anyone is curious: https://github.com/pnavk/nextjs-rsc-modal-dialog-example

I found a better solution. Add modal={false} to  and then add this to the ModalTrigger:
<DialogTrigger
onClick={(e) => {
e.preventDefault();
setOpen(!open);
}}

And that's it.

this issue should be re-opened, I have tried the approach of having a state variable with the [open, setOpen],  when pressing cancel we need to reset the state to the state previous to opening the dialog,  this state is being shared across dialog instanciations somehow, even setting a key prop didn't help, the behaviour of the cancel button is not the same as the "X" close button defaulted by the Dialog component but still both actions are buggy
`'use client';
import { useState } from 'react';
import { Button } from '@/components/ui/button';
import {
Dialog,
DialogContent,
DialogDescription,
DialogFooter,
DialogHeader,
DialogTitle,
DialogTrigger
} from '@/components/ui/dialog';
import { Textarea } from '../ui/textarea';
type InputDialogConfig = {
triggerElement?: React.ReactNode;
title?: string;
description?: string;
deleteLabel?: string;
inputValue: string;
onSave: (value: string) => void;
onRemove?: () => void;
};
const CreateInputDialog = (config: InputDialogConfig) => {
const {
triggerElement = Edit,
title = 'Editing',
description = null,
deleteLabel = null,
inputValue = '',
onSave = () => {},
onRemove = () => {}
} = config;
const [input, setInput] = useState(inputValue);
const [open, setOpen] = useState(false);
return (

{triggerElement}

{title}
{description && {description}}

<Textarea
value={input}
onChange={(e) => setInput(e.target.value)}
className="col-span-4 h-[200px]"
/>

{deleteLabel && (
<Button
type="button"
variant="destructive"
className="absolute left-6"
onClick={(e) => {
e.stopPropagation();
onRemove();
setOpen(false);
}}
>
{deleteLabel}

)}
      <Button
        type="button"
        variant={'outline'}
        onClick={(e) => {
          e.stopPropagation();
          setInput(inputValue);
          setOpen(false);
        }}
      >
        Cancel
      </Button>

      <Button
        type="button"
        onClick={(e) => {
          e.stopPropagation();
          onSave(input);
          setOpen(false);
        }}
      >
        Save
      </Button>
    </DialogFooter>
  </DialogContent>
</Dialog>

);
};
export default CreateInputDialog;
`
please use this as an example and instantiate it twice on a higher order component, pass it a function to save, no need to test the delete as this has no possible issues, and after setting the two vars to different values and switching from one to other instanciation you will see the value being brought from one instantiation to another.
https://www.loom.com/share/2989c845f661479e9d6e1d7bd1072437?sid=fb91d584-3929-4796-8ebb-725114b9748a

@chungweileong94 will do, just finishing some refactoring that hopefully will fix it

Whoever came here looking for answers wraps the element that triggers close with <DailogClose />. It extends the close primitive under the hood and does the job perfectly
<DialogClose>
    <Button variant="outline">Cancel</Button>
</DialogClose>

I ended up using another  to wrap a  element to close the dialog while clicking the link.  Is this the same as using ?

I ended up using another <DialogTrigger> to wrap a <Link> element to close the dialog while clicking the link. Is this the same as using <DialogClose>?

No its not good to use <Dialogtrigger>  Twice, and shadcn doesnt even let to use it more than once

in remix this one works
  const actionData = useActionData<typeof loader>();

  useEffect(() => {
    if (actionData?.success) {
      setIsFormOpen(false);
    }
  }, [actionData?.success, setIsFormOpen]);

  <Dialog open={isFormOpen} onOpenChange={setIsFormOpen}>
...


autoRenewingAndroid missing in release 3.0.2

Version of react-native-iap
3.0.2
Version of react-native
0.59.10
Platforms you faced the error (IOS or Android or both?)
Android
Expected behavior
autoRenewingAndroid should be true if the user has not cancelled the subscription
Actual behavior
autoRenewingAndroid missing from Purchase item
Tested environment (Emulator? Real Device?)
Real Device
Steps to reproduce the behavior

Create a subscription in the Google Play Console
Request the subscription to be added for a user
Get the available purchases for a user
The purchase is in the list but the autoRenewingAndroid key is missing

Description
Hey guys I am trying to check if a User has a valid subscription in Android. I noticed in one of the Issues in there that it is mentioned that to verify a subscription is valid for Android one has to verify that the autoRenewingAndroid is set to true, which means the subscription is still valid?
It turns out that for 3.0.2 the key autoRenewingAndroid is missing and it looks as if it is a missing item.putBoolean in the RNIapModule.java (I am sending a PR soon as a proposed fix)
What concerns me is that I noticed in the Google Play documentation that a user can cancel the subscription that they have but the App should continue to provide the subscription until it reaches its end. Like if the user cancels a monthly subscription on the middle of the month, the app should still provide the premium services until the end of the month or previously agreed period.
I also fixed the missing autoRenewingAndroid here locally, but when I cancel a subscription in the app Subscriptions, I do not see this key changing to false, it is always set to true, is there something else that I am missing to validate Android Subscriptions?

I think your question is related to #275 #532. By using this solution, you may check if the user is subscribed.
I am not sure about your next question. autoRenewingAndroid always returning true should be some env problem in play store server.

I feel like releasing this in 3.0.3 though. I'll close this when this is ready.

Released 3.0.3 in #673


YAML formatting and capitalization fixes

This fixes some minor YAML formatting issues and ensures consistent capitalization of task names (except for handlers).

For me it's ok, just needs to solve the conflict.


Changing content 'right' default value to hide scrollbar.

Everybody hates these middle-aged browser scroll-bar. Sadly the first thing I noticed when I integrated this component in my app was that a scroll-bar popped on the right.
To fix it on a cross-browser level, we just need to change the 'right' default value of the content, the following way :
  content: {
    right: -15 // this value might need to be even lower in some browsers.
  }

Thank you!

You can just change the style of the content to overflow: auto or overflow: hidden. The docs tell you how to add different styles for the content or even a custom className to it.

The problem is that overflow:hidden is also disabling the scrolling which is not a desired behavior in most cases.

Ah, I see what you mean. But you'd like to be able to scroll without showing the scroll bar, is that it?
Either way, I wouldn't change the code for the component, it already allows you to customize the styling. If anything I'd only changge the overflow to auto so it doesn't appear when it's not needed.

The default style of overflow has been changed to auto in 3.0 just as @grsoares21 recommended.

Nice, thanks ;)


Directory structure may not work with nested user path globally

Describe the bug
When bootstrapping slidev at the parent folder of slides.md (or absolute path), it still uses the current directory to resolve directory structure (like public, setup and so on). I think it should use the dirname of slides.md to resolve directory structure.
https://github.com/slidevjs/slidev/blob/2acab57e93b069a35541a4598df37a6c576b1d28/packages/slidev/node/options.ts#L92-L101
A possible solution (I am not sure whether it will bring some break changes):
function getUserRoot(options: SlidevEntryOptions) {
  const { entry: rawEntry = 'slides.md', userRoot = process.cwd() } = options
  const fullEntry = path.resolve(userRoot, rawEntry)
  return { entry: path.basename(fullEntry), userRoot: path.dirname(fullEntry) }
}

To Reproduce
Steps to reproduce the behavior:

Create ./nest/slides.md
Create some client config ./nest/setup/xxx.ts
Run slidev ./nest/slides.md
Check that setup does not work

Desktop (please complete the following information):

OS: MacOS 12
Browser: Edge
Slidev version: 0.27.13

Make sense, do you mind to send a PR? Thanks


Add Navigation Page with Current Location and Map Integration

Pull Request Template for GSoC 2024
Related Issue
issue no is #178
Description of Changes
This PR introduces the navigation page with a map displaying the user's current location using OpenStreetMap (OSM) and Leaflet.js. The page allows users to input their starting location and destination. The current location is displayed using the Geolocation API, and basic layout enhancements were made. This is step 2 of the Making of navigation page.
Changes Made:
Integrated Leaflet.js with OpenStreetMap for map display.
Used the browser's Geolocation API to show the user's current location on the map.
(Please check relevant boxes by entering an "X" inside them)
Screenshots / Demo (if applicable)

Checklist for Contributor
use'X' in [ ] to check it .

[x] I have reviewed my code before submission.
[x] I have read and followed the project's Contribution Guidelines.
[x] I have tested the code thoroughly.
[x] I have attached related issue numbers, screenshots, or videos (if applicable).
[x] I have added comments to my code where necessary for clarity.
[x] I have checked the existing code base and my changes do not introduce any breaking changes.
[x] My PR addresses only one issue; I have created separate PRs for other issues.
[x] I have ensured that the PR does not include unrelated files.
[x] I am mindful of the project's coding standards and best practices.

Contribution Guidelines Reminder
Thank you for contributing to our project! Please ensure you follow the guidelines below:
Contribution Levels

Task Categories:

Basic Tasks: Primarily focused on small changes like minor bug fixes, documentation improvements, and unit testing. Labeled as Easy.
Intermediate Tasks: Moderate-level tasks that involve enhancing existing features, code refactoring, or performance improvements. Labeled as Medium.
Advanced Tasks: Complex tasks like building new features, significant refactoring, or critical bug fixes. Labeled as Hard.

Acknowledging Effort:

Exceptional contributions will be recognized with a higher contribution level if substantial effort and innovation are demonstrated.

Review Process

PRs will be reviewed by the maintainers, and feedback will be provided. Contributors should address feedback promptly and resubmit the PR if necessary.

Contributors are encouraged to participate in the review process of other PRs for community growth.

We appreciate your time and effort in improving this project and look forward to your valuable contributions!

@dhairyagothi  Merge this pr

good work @Raja-Abrar-Khan

Thanks @dhairyagothi  will move to step 3 and make it better


[AutoPR datafactory/resource-manager] [ADF v2]Add integration runtime sharing feature.

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3345

This PR has been merged into https://github.com/Azure/azure-sdk-for-java/pull/2136


tf.estimator.DNNClassifier TypeError: init() got an unexpected keyword argument 'batch_norm'

Hello ,
I've run into the following error and could not find any relevant post on stack overflow. I'm trying to create a DNN classifier using the tf.estimator.DNNClassifier. My  tf.GIT_VERSION is  v1.9.0-0-g25c197e023  and  tf.VERSION  is 1.9.0
Problem
TypeError: init() got an unexpected keyword argument 'batch_norm'
It doesn't seem like batch_norm is one of the params
Updating tensorflow to 1.10.0 causes another issue saying bitwise cannot be imported
Source code / logs
inspect.getargspec(tf.estimator.DNNClassifier).args
gives
<class 'list'>: ['self', 'hidden_units', 'feature_columns', 'model_dir', 'n_classes', 'weight_column', 'label_vocabulary', 'optimizer', 'activation_fn', 'dropout', 'input_layer_partitioner', 'config', 'warm_start_from', 'loss_reduction']
It has self as a param and the estimator.params dictionary is always None and doesn't give information about the values

Thank you for your post. We noticed you have not filled out the following field in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Thanks.
Have I written custom code
OS Platform and Distribution
TensorFlow installed from
TensorFlow version
Bazel version
CUDA/cuDNN version
GPU model and memory
Exact command to reproduce
Mobile device

Could you give a minimal example for reproducing the exception? Thanks.

You can try running this
inspect.getargspec(tf.estimator.DNNClassifier).args
which gives
<class 'list'>: ['self', 'hidden_units', 'feature_columns', 'model_dir', 'n_classes', 'weight_column', 'label_vocabulary', 'optimizer', 'activation_fn', 'dropout', 'input_layer_partitioner', 'config', 'warm_start_from', 'loss_reduction']
This is missing batch_norm

oh, my bad. So we need update document or support the argument, right?

Yup. I think the argument needs to be supported. It is defined and there is code which gets executed when this boolean value is True. It's not being read properly somewhere. I didn't debug where exactly. I can try that

cc @ispirmustafa

The batch_norm parameter was added in 1.10, which is why you get the error in 1.9. So I'm closing this issue.
As for the "bitwise cannot be imported" issue, can you file a new issue with the issue template filled out? Thank you.


Account for the new call opcode structure

Python 3.10 / 3.11 / 3.12 all have different call conventions
We need to unify them, most likely via a common bytecode representation,
which is conditionally transformed into the version bytecode

First part implemented - python 3.11 call structure is now partially transformed in the background


rerender

And using a commit hash instead of master.

Hi! This is the friendly conda-forge-admin automated user.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.


about add plugins

this is not a issue, just start to use this awesome vimrc and have some questions.

it's suggested to add self plugin under sources_non_forked/, what's the difference between sources_non_forked/ and sources_forked/
why not use submodule to manage plugins, do we always need a commit for some update

Non forked are those where I did not make any changes


[SPARK-30999][SQL] Don't cancel a QueryStageExec which failed before call doMaterialize

What changes were proposed in this pull request?

This PR proposes to not cancel a QueryStageExec which failed before calling doMaterialize.
Besides, this PR also includes 2 minor improvements:

fail fast when stage failed before calling doMaterialize

format Exception with Cause

Why are the changes needed?

For a stage which failed before materializing the lazy value (e.g. inputRDD), calling cancel on it could re-trigger the same failure again, e.g. executing child node again(see AdaptiveQueryExecSuite.SPARK-30291: AQE should catch the exceptions when doing materialize for example). And finally, the same failure will be counted 2 times, one is for materialize error and another is for cancel error.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Updated test.

Test build #119142 has started for PR 27752 at commit 692b751.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23884/
Test PASSed.

ping @cloud-fan @maryannxue @JkSelf  Please take a look.

Test build #119160 has started for PR 27752 at commit 0a52b62.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23903/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23914/
Test PASSed.

Test build #119172 has started for PR 27752 at commit 1dbb243.

Test build #119160 has finished for PR 27752 at commit 0a52b62.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119160/
Test PASSed.

Test build #119174 has started for PR 27752 at commit 13f8a1f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23916/
Test PASSed.

Test build #119172 has finished for PR 27752 at commit 1dbb243.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #119174 has finished for PR 27752 at commit 13f8a1f.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119174/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119172/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23936/
Test PASSed.

Test build #119196 has started for PR 27752 at commit d367526.

Test build #119196 has finished for PR 27752 at commit d367526.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119196/
Test PASSed.

Test build #119211 has started for PR 27752 at commit 46883a0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23952/
Test PASSed.

Test build #119211 has finished for PR 27752 at commit 46883a0.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119211/
Test FAILed.

retest this please

Test build #119219 has started for PR 27752 at commit 46883a0.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23958/
Test PASSed.

Test build #119219 has finished for PR 27752 at commit 46883a0.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119219/
Test PASSed.

Test build #119236 has started for PR 27752 at commit 654d9d3.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/23975/
Test PASSed.

Test build #119236 has finished for PR 27752 at commit 654d9d3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/119236/
Test PASSed.

Thanks! Merged to master/3.0

thanks all!


Apparent dealloc error after Swift 5/Xcode 10.3 upgrade

Hello,
I am taking over a project, and after making the upgrade to Xcode 10.3, Brightfutures is crashing every time. Any help offered would be appreciated. I am attaching the Stacktrace and screenshots of the code in question.

thread #25, queue = 'NSOperationQueue 0x600000c6caa0 (QOS: UNSPECIFIED)', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
frame #0: 0x000000010c942d68 libswiftCore.dylibswift_getAssociatedTypeWitnessSlowImpl(swift::MetadataRequest, swift::TargetWitnessTable<swift::InProcess>*, swift::TargetMetadata<swift::InProcess> const*, swift::TargetProtocolRequirement<swift::InProcess> const*, swift::TargetProtocolRequirement<swift::InProcess> const*) + 200   frame #1: 0x000000010c941308 libswiftCore.dylibswift_getAssociatedTypeWitness + 152
frame #2: 0x000000010a0164c9 Kit`MutableAsyncType<>.success(value=, self=) at :0

frame #3: 0x000000010a0174ab KitPromise.success(value=10745 bytes, self=0x0000600000c75ee0) at Promise.swift:49:16 frame #4: 0x0000000109fd5ea5 Kitclosure #1 in URLSessionRequestHandler.handleRequest(data=10745 bytes, response=0x0000600000c427e0, error=nil, promise=0x0000600000c75ee0) at URLSessionRequestHandler.swift:20:25
frame #5: 0x0000000109fd5fec Kitpartial apply for closure #1 in URLSessionRequestHandler.handleRequest(_:) at <compiler-generated>:0 frame #6: 0x0000000109fd6116 Kitthunk for @escaping @callee_guaranteed (@guaranteed Data?, @guaranteed NSURLResponse?, @guaranteed Error?) -> () at :0
frame #7: 0x00000001038d72b1 DAILYLOOK__InstrumentDataTaskWithRequestCompletionHandler_block_invoke.81 + 218 frame #8: 0x00000001038d72b1 DAILYLOOK__InstrumentDataTaskWithRequestCompletionHandler_block_invoke.81 + 218
frame #9: 0x000000010aa34178 CFNetwork__75-[__NSURLSessionLocal taskForClass:request:uploadFile:bodyData:completion:]_block_invoke + 19 frame #10: 0x000000010aa4ac56 CFNetwork__49-[__NSCFLocalSessionTask _task_onqueue_didFinish]_block_invoke + 172
frame #11: 0x0000000106d7f33e Foundation__NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7 frame #12: 0x0000000106d7f246 Foundation-[NSBlockOperation main] + 68
frame #13: 0x0000000106d7c120 Foundation-[__NSOperationInternal _start:] + 688 frame #14: 0x0000000106d81e87 Foundation__NSOQSchedule_f + 227
frame #15: 0x000000010d30cd7f libdispatch.dylib_dispatch_call_block_and_release + 12 frame #16: 0x000000010d30ddb5 libdispatch.dylib_dispatch_client_callout + 8
frame #17: 0x000000010d310c95 libdispatch.dylib_dispatch_continuation_pop + 552 frame #18: 0x000000010d31008f libdispatch.dylib_dispatch_async_redirect_invoke + 849
frame #19: 0x000000010d31e632 libdispatch.dylib_dispatch_root_queue_drain + 351 frame #20: 0x000000010d31efca libdispatch.dylib_dispatch_worker_thread2 + 130
frame #21: 0x000000010d6f66b3 libsystem_pthread.dylib_pthread_wqthread + 583 frame #22: 0x000000010d6f63fd libsystem_pthread.dylibstart_wqthread + 13

did you have a strong reference on the Future returned by handleRequest?

Sorry to hear you're encountering issues. I can't reproduce the issue myself, it would be helpful if you could provide a crashing test case in a PR if possible.
Could you also try rewriting the method to not use a Promise (as shown at https://github.com/Thomvis/BrightFutures#providing-futures) to see if the crash still happens?

I removed all Promises (there were several, nested). Once I switched to using only futures, the crashes stopped.

Glad to hear. Would still love to have a reproducing test case to get this issue fixed, so if you have any insights you can share please do :)

We're getting this exact same issue happening after the Swift 5/Xcode 11/BrightFutures 8.0.0 upgrade.
@adjustnox any luck on getting the reproducible project set up?
@Thomvis We tried converting the following block to Futures:
{
	private var computeFeedItemsTask:Future<[ContentItemVM], Never>?

	// FAILING METHOD
	private func computeFeedItems() -> Future<[ContentItemVM], Never> {
		...

		let existingComputation:Future<[ContentItemVM], Never> = computeFeedItemsTask ?? Future( value: [ContentItemVM]() )
		// FAILING LINE
		let existingComputationPart:String = (existingComputation.isCompleted) ? "finished" : "in progress...."

		...

		computeFeedItemsTask = existingComputation.map( computeFeedItemsQueue.context ){ _ /*(_:[FeedItemVM])*/ -> /*Future<*/[ContentItemVM]/*, NoError>*/ in
			...

			return feedItems

		}.onSuccess( DispatchQueue.main.context ){ (feedItems:[ContentItemVM]) in
			...
		}
	}
}

STACK TRACE:
#0	0x0000000112ebf94f in swift_getAssociatedTypeWitnessSlowImpl(swift::MetadataRequest, swift::TargetWitnessTable<swift::InProcess>*, swift::TargetMetadata<swift::InProcess> const*, swift::TargetProtocolRequirement<swift::InProcess> const*, swift::TargetProtocolRequirement<swift::InProcess> const*) ()

#2	0x000000010ee8edaf in AsyncType.isCompleted.getter ()

#3	0x000000010eb491f6 in FeedController.computeFeedItems() at /Users/marchy/Documents/Projects/Happ/Mobile-iOS/Code/Happ.Mobile/Controllers/FeedController.swift:2090

#4	0x000000010eb2c8f5 in FeedController.viewDidLoad() at /Users/marchy/Documents/Projects/Happ/Mobile-iOS/Code/Happ.Mobile/Controllers/FeedController.swift:936

by changing the .map{...} call above to computeFeedItemsTask = Future { complete in DispatchQueue.global().async { ... }} as suggested in the docs, but it actually doesn't even run that far, since existingComputation fails beforehand when trying to access existingComputation.isCompleted when set with its initial empty array value (Future( value: [ContentItemVM]() )).
Here's some outputs of the Future's state:
(lldb) po existingComputation
Async<Result<Array<ContentItemVM>, Never>>(Optional(Swift.Result<Swift.Array<Happ_Mobile.ContentItemVM>, Swift.Never>.success([])))

(lldb) po existingComputation.isCompleted
error: Execution was interrupted, reason: EXC_BAD_ACCESS (code=1, address=0x0).

(lldb) po existingComputation.result
▿ Optional<Result<Array<ContentItemVM>, Never>>
  ▿ some : Result<Array<ContentItemVM>, Never>
    - success : 0 elements

Seems pretty wild given the implementation of AsyncType::isCompleted seems to be simply:
public extension AsyncType {
    var isCompleted: Bool {
        return result != nil
    }
    ...
}

Hi @Thomvis @adjustnox did you guys have a chance to look into this by any chance?
This is preventing us from upgrading to Xcode 11 / Swift 5 / iOS 13.
Any insight would be much appreciated

It was a hold up for us as well, so we ended up replacing the promises with escaping closures :/
Can't offer any help, I'm afraid.

Sorry that this is still an issue. Still not sure what the root cause could be and why this is not reproducible in a new/simple project.
Can you think of any way in which your projects are similarly special? E.g. what is the install method (CocoaPods, Carthage, etc.)

Cocoapods for us.
I can say we had several nested promises, which we switched to futures as per earlier suggestions.


Invalid authenticator code

After inputting the authenticator code on the website, the website prompts as invalid. However when I try it with another mobile, it works.

Please check the time zone ( date and time settings) , this has to match the same zone you had when you added the token in the app .

Please re-open this issue if the problem still persists


Postgres 10 releae?

Hi,
I'm wondering if you are planning to release a version of this image based on the newly released PostgreSQL 10.
Thanks!

I am working on it here: https://github.com/appropriate/docker-postgis/pull/63

@tdamsma great, thanks!

Thanks @tdamsma and @md5


Remove Desktop install references

Signed-off-by: Usha Mandya<EMAIL_ADDRESS>Removed statements that mention that Docker Desktop includes Docker Machine.
Added a note to state that Docker Machine is no longer included in the Docker Desktop installer and included a link to Machine releases page on GitHub
Fixes https://github.com/docker/docker.github.io/issues/12243

@StefanScherer PTAL


Mismatch between role tags and supported platforms

Hi,
I just noticed your role tags and description only mention Debian systems, but RHEL and Fedora are mentioned in supported platforms.
A quick look at the source code suggests the description/tags are out of date; is that the case?

Redhat support was added by f-andrey. This might still work but was not tested lately.

Thanks for the reminder, I'll check it in the near future and try to fix it if something does not work, after the last commits

thanks guys!


Separate medications to take by headers like "Today, This Week, Next Week"

Hi @waseefakhtar, Please assign this to me, if this issue is still open

Hi @waseefakhtar, Please assign this to me, if this issue is still open

Hi @atharv028! It is open, so feel free to work on it. :)


i18n is not loading Intermittently

i18n is not loading Intermittently

Notice this on the front page occasionally now (always front page since that loads first), and then any Vue reactivity update seems to fix it. So the string re-rendering or loading another page etc.

Hadn't had this happen before, only things I can think of off the top of my head:

Using the global {{ $t('string.goes.here') }} instead of the composable that it used to use ?

import { useI18n } from 'vue-i18n';
const { t } = useI18n();

Just that the language jsons are bigger now and take longer to load causing a race condition?


1.1.1-alpha7: load_cert_pass() used with wrong param leading to "No filename or uri specified for loading certificate"

This was noticed by
openssl x509 -MD5 -fingerprint -noout -inform PEM
returning
No filename or uri specified for loading certificate
in OpenSSL 3.0.0-alpha7.
IMHO this is due to a refactoring resulting in calling load_cert_pass() with wrong params.
The declaration and implementation of load_cert_pass() in apps/include/apps.h and apps/lib/apps.c
X509 *load_cert_pass(const char *uri, int maybe_stdin,
const char *pass, const char *desc);
There is no format params and the second param maybe_stdin is an int signaling, whether data might be read from STDIN.
I found the following calling places, that use wrong params:
apps/ca.c:        x509 = load_cert_pass(certfile, certformat, passin, "CA certificate");
apps/ca.c:            revcert = load_cert_pass(infile, certformat, passin,
apps/ca.c:    if ((template_cert = load_cert_pass(infile, certformat, passin, "template certificate")) == NULL)
apps/s_client.c:        cert = load_cert_pass(cert_file, cert_format, pass, "client certificate");
apps/s_server.c:        s_cert = load_cert_pass(s_cert_file, s_cert_format, pass,
apps/s_server.c:            s_cert2 = load_cert_pass(s_cert_file2, s_cert_format, pass,
apps/s_server.c:        s_dcert = load_cert_pass(s_dcert_file, s_dcert_format, dpass,
apps/x509.c:        x = load_cert_pass(infile, FORMAT_UNDEF, passin, "certificate");
apps/x509.c:        xca = load_cert_pass(CAfile, CAformat, passin, "CA certificate");
I think most or all of them were introduced by 2a33470b4f23bcf1cd66bbf645c855142efa0ed9 (Merged from #12647). That commit switches from using load_cert() to load_cert_pass(). Note that in the same commit changes the original load_cert() from originally calling load_cert_pass() with maybe_stdin set to 1 to now calling it with a 0. So switching the callers back to using load_cert() will likely not fix the "No filename or uri specified for loading certificate" problem.
Also load_cert() drops the format param.

The format argument has become largely unnecessary, you can see more about that in the manual pages.  However, passing the format as argument for maybe_stdin is a clear omission, of course.  PR coming up!


Add changes according to ML-DSA draft standard

Hi, for a project of mine I was using your python implementation of Dilithium but I needed to move to ML-DSA. Therefore, I made a few changes based on the draft standard and also updated the KATs using the "standard" branch of the reference implementation.

Oh thanks! I'll look into this soon. I need to update both this and the kyber one (I have a full implementation not public on ML-KEM) but I was waiting for the final standard

Hey, are you still interested in working on this? I just finished cleaning up the Kyber/ML-KEM repo (https://github.com/GiacomoPope/kyber-py) and could do with cleaning this one up as well

My suggestion would be to make a directory called ml_dsa following the dilithium directory so we can support both for educational purposes. Are you happy to do this?

I have implemented this myself now following the above discussion so will close this PR


Channel webhooks events added

I want to merge this change because it adds new subscription base webhooks for channel create, update, delete, activate and deactivate events.
Docs PR here

Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations
[ ] Documentation needs to be updated

Pull Request Checklist

[ ] Privileged queries and mutations are guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migration files are up to date
[ ] The changes are tested
[ ] GraphQL schema and type definitions are up to date
[ ] Changes are mentioned in the changelog

Task linked: SALEOR-6482 Add channel webhook events


Woraround parallelize() issues and default to parallel matmul

Increases performance from ~190tok/s->~400tok/s on my machine. If you tune the number of threads self.rt = Runtime(nthreads) it gets up to ~500tok/s (best i found was 12 threads).
There are a few issues with parallelize that need to be worked around:

The single arg version of parallelize creates a new runtime for each invokation, which is slow.
The two arg version is much slower than the three arg version because querying the number of cores seems to be slow. Investigating this.

Wow! Looks cool. Thanks @itramble for you efforts.
Did you know what means rt.parallelism_level() ?
On my VM I set threads = 3 and I got best performance. I did silly assumption when nthreads = num_cores() // 2.. This expression leads to error /__w/modular/modular/Kernels/mojo/builtin/_startup.mojo:70:1: error: no viable expansions foun
I'm happy to merge this PR as is

Did you know what means rt.parallelism_level() ?

It returns the number of threads that the Runtime was constructed with (by default Runtime() creates a runtime with num_threads=num_cores()).

This expression leads to error /__w/modular/modular/Kernels/mojo/builtin/_startup.mojo:70:1: error: no viable expansions found

Hm this diff works for me:
diff --git a/llama2.mojo b/llama2.mojo
index fa4d4a4..6b24b57 100644
--- a/llama2.mojo
+++ b/llama2.mojo
@@ -282,7 +282,7 @@ struct RunState:
         self.key_cache.alloc_zero()
         self.value_cache = Matrix3(config.n_layers, config.seq_len, config.dim)
         self.value_cache.alloc_zero()
-        self.rt = Runtime()
+        self.rt = Runtime(num_cores() // 2)

 struct TransformerWeights:

End up with self.rt = Runtime(num_cores() // 2)
Before I tried via aliasing alias nthreads = num_cores() // 2 -- that's why it was failing.
So far best performance

Before I tried via aliasing alias nthreads = num_cores() // 2 -- that's why it was failing.

Ah you can only use alias for compile time values and num_cores() is a runtime value.


Incompatible with 2023.1.EAP

Describe the bug:
The plugin is incompatible with the 2023.1.EAP version of (at least) PHPstorm
Additional context:
Tried to enable the plugin regardless but I get a hard error on trying to generate something. It does seem to properly show the context menu in the project window.
Would be nice if the plugin could be a bit less version-dependent, I've had incompatibilities with EAP before (which I suppose could make sense sometimes).
As an in-between it might be nice if the nx command that would be running is displayed in the generate window, so that the plugin UI could still be used and the command could be copied to terminal.

I see the problem for the EAP, some api changed, I will try to provide a version that support EAP version.
You have a button that provide copy to clipboard of current command

Here a custom build compatible with latest EAP
Install plugin from disk > choose zip file
Nx Console Idea-0.56.0-EAP.zip

Here a custom build compatible with latest EAP Install plugin from disk > choose zip file
Nx Console Idea-0.56.0-EAP.zip

I tried this with 2023.1.3 and it seems not to be working as i does not find any templates to generate. the list of templates is just empty.


Ubuntu Make Problem

Hi,
I'm encountering a "make" problem on ubuntu server 13.04 (GNU/Linux 3.8.0-33-generic x86_64).
Everything seems to be fine until the make command. I was able to install imgmin successfully on a 12.04 LTS ubuntu server, but not on this new machine. I love this script it is fast and the ratio quality/weight is just wonderful I think.
Below, the output in terminal:
root@pop-front1:~/imgmin# make
make  all-recursive
make[1]: Entering directory /root/imgmin' Making all in src make[2]: Entering directory /root/imgmin/src'
gcc -W -Wall -Os  MagickWand-config --cflags --cppflags -o imgmin imgmin.c MagickWand-config --ldflags --libs
imgmin.c: In function ‘do_png’:
imgmin.c:389:9: warning: initialization discards ‘const’ qualifier from pointer target type [enabled by default]
imgmin.c:399:9: warning: initialization discards ‘const’ qualifier from pointer target type [enabled by default]
imgmin.c:406:9: warning: initialization discards ‘const’ qualifier from pointer target type [enabled by default]
imgmin.c:429:9: warning: initialization discards ‘const’ qualifier from pointer target type [enabled by default]
imgmin.c:368:32: warning: unused parameter ‘mw’ [-Wunused-parameter]
imgmin.c:369:50: warning: unused parameter ‘opt’ [-Wunused-parameter]
make -C apache2
make[3]: Entering directory /root/imgmin/src/apache2' if [ "apxs2" != "" ]; then \ 		apxs2 -I pwd/.. MagickWand-config --cppflags --ldflags --libs|xargs-Wc,-DIMGMIN_LIB -Wc,-W -Wc,-Wall -Wc,-Wno-unused-parameter -c mod_imgmin.c ../imgmin.c; \ 	fi Use of uninitialized value $includedir in concatenation (.) or string at (eval 9) line 1. apxs:Error: Unknown option: f. Usage: apxs -g [-S <var>=<val>] -n <modname>        apxs -q [-S <var>=<val>] <query> ...        apxs -c [-S <var>=<val>] [-o <dsofile>] [-D <name>[=<value>]]                [-I <incdir>] [-L <libdir>] [-l <libname>] [-Wc,<flags>]                [-Wl,<flags>] [-p] <files> ...        apxs -i [-S <var>=<val>] [-a] [-A] [-n <modname>] <dsofile> ...        apxs -e [-S <var>=<val>] [-a] [-A] [-n <modname>] <dsofile> ... make[3]: *** [mod_imgmin_la] Error 1 make[3]: Leaving directory/root/imgmin/src/apache2'
make[2]: *** [mod_imgmin] Error 2
make[2]: Leaving directory /root/imgmin/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory /root/imgmin'
make: *** [all] Error 2
Do you know what this could be ?
Thanks

I had the same issue and used @AerisG222's solution from #21 and it fixed the issue for me. I have created a PR (#54) with the change to 'src/apache2/Makefile.am'.

AerisG222's solution from #21 was added in ea2b77c to fix this problem, but on Arch Linux with ImageMagick libs 6.9.2-0, the output of:
MagickWand-config --cppflags --ldflags --libs | xargs

is

-fopenmp -DMAGICKCORE_HDRI_ENABLE=1 -DMAGICKCORE_QUANTUM_DEPTH=16 -fopenmp -DMAGICKCORE_HDRI_ENABLE=1 -DMAGICKCORE_QUANTUM_DEPTH=16 -I/usr/include/ImageMagick-6 -lMagickWand-6.Q16HDRI -lMagickCore-6.Q16HDRI -lMagickWand-6.Q16HDRI -lMagickCore-6.Q16HDRI

Since there are multiple instances of "-fopenmp ", to fix the problem, I add the "g" (global) flag on sed, like:
$(MAGICK_CONFIG) --cppflags --ldflags --libs|xargs|sed "s/-fopenmp\s//g"

I only need this fix on systems with Apache installed, as the Apache module doesn't get built without it.


Ignore nested components in no-multi-comp

I don’t think react/no-multi-comp should trigger on nested components or should have an option to disable it. A practical example:
import { FormattedMessage } from 'react-intl';

export function App() {
  return (
    <FormattedMessage
      values={{
        link:
          // The next line triggers react/no-multi-comp
          (text: string) => <a>{text}</a>,
      }}
    />
  );
}

I suggest to add an option ignoreNested which ignores any components that aren’t declared as part of the Program node body.

The issue there isn’t that it’s nested - it’s that it’s treated as a component despite being used in an object literal with a key name that can’t be a custom component name.
Our component detection should be improved here.

The issue there isn’t that it’s nested - it’s that it’s treated as a component despite being used in an object literal with a key name that can’t be a custom component name.

I like that explanation even better.


Update example project

Updated example project to 0.63.4
Updated project structure to build example project from inside example project it self
Removed GEM file setup, previously used to build and run example project
Other Clean ups not affecting the core library

Note: No changes affect the core library, it affects only the example project that to how we run it.
Check the section on how to run the example project, follow it and try running the project on iOS and android emulator.
I have tested it on both emulators.
This change should clean up the library and make it easier to upgrade to latest versions as it releases.

@ravirajn22 ❤
There are a lot of linting issues, maybe you can have a look 🙏

Fixed it

😻

@ravirajn22 Do we need react-native-maps added as a dependency to the example project?

No its setup like using react-native-maps directly from the folder


Please hear me out

Since issues are turned of for the PyPDF3 repository you own, and i could find no other way to contact you, please allow me to reach out to you here.
I've noticed that the excellent libraries PyPDF 1, 2, 3, and 4 are all suffering from lack of maintenance. PyPDF 1 and 2 have clearly been superseded and left behind, but it is unclear whether the community should rally behind PyPDF3 or PyPDF4, (or ideally combine efforts of PyPDF3 and 4) as both are not very actively developed, but not completely stagnant either. However since you have issues turned off, it seems like you are not looking for active collaboration on your fork of the library.
Now, since this is open source, you are of course not required to accept collaboration or give up your time to contribute to any open source library, but it would be helpful for the Python community if you made your position clear in the README.md of PyPDF3. What is the purpose of this repository to you? Is it just a repo you created to improve upon PyPDF2 for personal use and are you done with it now? Or do you want PyPDF3 to be(come) as generally useful and feature complete as possible and widely used by the community? Do you welcome collaboration, or do you encourage people to fork and supersede your library?
Currently, I don't know which library (PyPDF3 or PyPDF4) is more feature complete and bug free, nor do i know which should receive collaborative efforts, if any, or if another fork (PyPDF5?) should be attempted to revitalize the project. Forking yet another time is not my preferred course of action, as it increases fragmentation and confusion, but it may still be the best option depending on how you and the author of PyPDF4 feel about the respective prospects of your libraries. Another option could be transferring ownership of the repository and the PyPi package to someone else who is willing to further the development of the project in collaboration with the community.
I would like to hear your thoughts about this, and regardless of how you decide to lead your project, please make an attempt to communicate to the community your position (readme is probably the best place for that) so that we have clarity and can decide where to focus our efforts.
Regardless, thank you for your development of PyPDF3.

I'll get back to you on this later in the week, thanks for reaching out.


Users can create, read, update, and delete a profile in the database

User Stories

As a user, I can create my own profile that stores information about me

As a user, I can retrieve my profile data or another user's profile data

As a user, I can update my profile data

As a user, I can delete my profile

User model and routes have been created and tested.


[STREAMING] SPARK-4986 Wait for receivers to deregister and receiver job to terminate

Spark Streaming does not wait for all receivers to deregister and the receiver job to terminate before killing spark context which can cause data loss. This PR solves this by waiting for all receivers in ReceiverTracker stop function when using graceful shutdown.
This together with https://github.com/apache/spark/pull/3857 fixes SPARK-4986.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Jenkins, this is ok to test

Jenkins, test this please.

Test build #25037 has started for   PR 3868 at commit 8f0b636.

This patch merges cleanly.

Test build #25037 has finished for   PR 3868 at commit 8f0b636.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/25037/
Test PASSed.

Could you add an unit test that tests this functionality. Something like this is easy undergo regression silently.

@tdas yes I think I can, I will take a look at it. Thanks for the feedback.

As long as you're planning to do more work on this, I left a round of (kind of nitpicky) style comments (https://cwiki.apache.org/confluence/display/SPARK/Spark+Code+Style+Guide).

@JoshRosen Thank you for all the comments. I will update accordingly :).
Regarding the waitUntilDone function, yes I assume there must be something like this in Scala library already but I couldn't find it. Using ScalaTest's eventually seems to create a weird dependency. Any suggestions? Thanks.

Yeah, we can't / shouldn't use ScalaTest's eventually here; I was just noting the similarity.  Maybe there's a library that has something like this, but I don't know of one offhand (I checked Scalactic and it's not there).

I think I get the idea at a high-level what this patch is trying to do. The key change essentially is in the ReceiverLauncher - the stop is made to use the config spark.streaming.gracefulStopTimeout for tunability. However, this needs to be done carefully such that the behavior of the system is predictable.
The existing code is that if the timeout is set to 10 seconds, the context.stop will exit after 10 seconds. So that timeout applies across all the different waits (wait for receiver stop, wait for job generation, wait for job completion). This is makes it easy for a developer to understand what is going to happen if he/she sets the configuration to 60 seconds.
The current patch changes this to use the timeout at every level. The problem with that approach is that if the developer sets the timeout as 60 seconds, the system may take upto 60 * 3 = 180 seconds to stop gracefully. That's confusing.
So we need to wait intelligently such that max time the whole system waits is predictable and easy to understand. The current code already does that, but only partially as the receiver-stop-wait is fixed to 10 seconds and is not configurable. Maybe there is a better way of refactoring the code to achieve this, and the current patch is not the right way because of aforementioned reasons.
Here are two approaches.

if processAllReceivedData = true, then JobSchduler.stop() calls ReceiverTracker.stop() and JobGenerator.stop() with timeouts which will depend on the how much time has passed since JobScheduler.stop() was called. The overall timeout is the configurable parameter, and ReceiverTracker, ReceiverLauncher, and JobGenerator deal without whatever stop timeout has been given to them.

The whole sequence of stop()s is evaluated in a Future (with its own execution context, not the global one), and the configurable timeout is a timed wait on hte future. This may simplify code, but introduces another thread in the system. Probably okay to do so.

I suggest we try the second approach. What do you think, @cleaton @JoshRosen ?

@tdas Thank you for the input.
Yes, the main purpose of this patch is to make ReceiverTracker graceful by waiting for   ssc.sparkContext.runJob(tempRDD, ssc.sparkContext.clean(startReceiver)) to terminate and all receivers to de-register (possible redundant?). I borrowed the aproach used in JobGenerator and you are right I forgot to keep timeWhenStopStarted global.
The second approach sounds good to me. Would make it easier to follow the shutdown sequence if it is consolidated in one place.
And for unit test my idea is to create a dummy receiver implementation that blocks on shutdown while still producing a fixed number of records.
Do you think you or someone else working more closely with spark streaming should take over this patch? Seems it is about deciding which approach is best suited for spark in the long run. I can still try to provide a unit test for this though.

I am happy to review the code if you take a pass on implementing (2). I can jump in if things get too hairy.

OK sounds great. :+1:
I can prepare an implementation of (2). Bit busy now, but I think I can have something to review in a week.
Any specific unit test you can suggest for me to take a look at? The existing receiver tests? Thanks :)

@tdas I've added a unit test now covering slow receiver shutdown. What do you think about the approach now? Thanks

Jenkins, test this please.

This patch is definitely heading in the right direction. But as I was reading it, I realize that it affects the whole shutdown behavior of all the components pretty heavily. Since the whole purpose of this PR was to fix the bug that graceful shutdown was not waiting receivers to stop, I think it is better to split this attempt into two parts.

PR1 - Fixes the bugs with very surgical local changes. This probably should touch only ReceiverTracker. This is will be small enough to include in Spark 1.3 which is very soon.
PR2 - Refactors the code like this PR does and makes sure that the overall behavior is what is desired.

For PR2, I was thinking what is the desired behavior. This was not at all documented in the code, so I thought of first documenting this. Then verifying whether any PR satisfies the desired behavior will become easy. Here are what I think is the desired behavior.
Overall, ssc.stop(stopGracefully = false) should allow all the internal components enough time to stop immediately but cleanly so that the all resources of each component are cleared. If this requires taking some minimum amount of time, so be it. But each component is responsible for keep this time small. For ssc.stop(stopGracefully = true), the overall system should use whatever the configured timeout is. But here too each component should ensure that all resources are cleared when the stopping thread is interrupted after timeout. So overall the jobScheduler.stop(graceful = true) should do something like
if (graceful) {
	// call stop(graceful = true) on all components inside future, and wait for future with timeout
	// if timeout occurred (so graceful stop was not completed), call stop(graceful = false) on all components to clean all resources
} else {
	// call stop(graceful = false) on all components
}

Anyways, to summarize, it would great if you can submit a more surgical PR1 that affects only receiversTracker (and units to test for this), and then make this current PR refactor stuff to implement this behavior. I would love to have the surgical fix as part of Spark 1.3.

Thank you for the comments @tdas . I think the diff file for this PR has become a bit misleading. It looks like there is more change than there actually is. This is a summary of the PR in its current state.

Propagate the graceful shutdown information to receiverTracker / receiverExecutors stop function.

Add a Future to wrap the whole shutdown sequence.

The second part is because before  "spark.streaming.gracefulStopTimeout" was used to timeout the check for "jobScheduler.receiverTracker.hasUnallocatedBlocks" inside JobGenerator.scala . This is now removed from jobGenerator (only remove the timeout from the while loop) and instead use gracefulStopTimeout configuration to change the wrapping Future timeout.
Other than that I have not modified the original shutdown logic, it just shows up as removed and re-added in the diff file.
My purpose with this patch has always been achieve something like your PR1. But because of the "spark.streaming.gracefulStopTimeout" variable it is not so easy to add another place to gracefully wait without modifying other parts a little bit.

About the default timeout change from 10x batch duration to 100x batch duration. Don't you believe 10x is quite small when the batch duration is 1 second or less? 30 seconds might not be enough if a receiver is slow to shutdown for some reason.
I think the whole idea to have a "spark.streaming.gracefulStopTimeout" configuration option outside the code is a bit weird. I had no idea there was such option before I started looking into this code and I can not find it mention in the official documentation. I believe most developers are unaware of this timeout and just assumes graceful == "possibly wait forever and have to manually force kill if too slow" (at least this was my initial thought.)
Isn't it better to expose this timeout from the ssc.stop() function instead,  making it more visible for developers and giving them an option to actually wait forever if necessary?
When does the merge window for Spark 1.3 close?
Thanks

The merge window for features closes this weekend. However this is a bug fix so we can make it to early next week as well. But the change has to be surgical.

Default timeout - if batch sizes are less than 1 second, then i see your point. Ideally, the receivers should shutdown immediately, and stop receiving data, so only few batches should be generated and executed after the graceful shutdown command has been given. In practice that is probably a wrong assumption. However, this is also confusing if we wait for 100x batches. Most people run ~10s  batches, which means the system will wait for 1000 seconds. That's kind a confusing as well if the system is stuck for a while even with default configuration. So I guess the most desirable thing to do that balances both short and large batches is.

Default timeout max(10x batch size, 1 minute)

Log warning if there is a timeout.

Expose the timeout configuration

For 3, i donot want to add another configuration parameter to stop(), there are already a large combination of optional parameters in stop() and each addition gets harder to maintain in the Java and Python API. I want to just expose the SparkConf parameter.
Regarding this patch, I agree that the change is probably not much, but since this behavior of the code is not very tested, I am unsure of doing this so late in the release cycle for 1.3. So for this release, it would be great if we can do a surgical fix that solves the bug and expose the timeout. And have a separate PR that cleans this up with refactoring and proper tests testing all aspects of the behavior.

Thanks @tdas
I'll create a new minimal PR with only the receiver shutdown part and the unit test. The main problem is how to deal with the timeout then. The two most simple approaches I can think of is:

Propagate the time it took to shutdown the receivers and deduct it from the waiting time inside JobGenerator.scala

Directly deduct the time by setting the  "gracefulStopTimeout" conf parameter to the left over time after successfully stopping the receivers.

What do you think is the best approach for now?

@tdas I have a new branch here: https://github.com/cleaton/spark/compare/apache:branch-1.2...receiverstop
Still missing code to handle gracefulStopTimeout  but this diff should be much easier to read.

Yes, the branch looks good. Can you please submit that as a PR. There are a few minor comments that I want to make.

I will rebase to master tomorrow and submit it as a new PR for SPARK-4986. There is still the problem of how to handle the gracefulStopTimeout option, any thoughts about that?
Thanks

It is fine to not address the timeout in that PR. That PR is about correctness. With that PR, the system will not loose data when gracefully stopped. The time it may take to stop will be up to  { [time taken for all the receivers to stop] + [gracefulStopTime] }. Ideally it should just be [gracefulStopTimeout]. Addressing that requires quite a bit of refactoring, which should be the next PR.

@tdas I have created a new master branch PR. You can find it here: https://github.com/apache/spark/pull/4338

Thanks! @cleaton Could you close this PR, and then create a new PR with the new stuff. Also create a new JIRA saying something like "Make the gracefulStopTimeout more intuitive to use"  and the new PR  should have that name.


Unable to diff or sync a control plane with custom plugins since deck v1.27.0

I'm running the specified below config (names changed to more generic names), which I generated with deck dump on deck version 1.26.1.
running deck sync or deck diff with this config worked fine on 1.26.1 but on 1.27.0 I get the following error:
Error: building state: add defaults to plugin 'auth-plugin': retrieve schema for auth-plugin from Kong: HTTP status 404 (message: "no plugin-schema for 'auth-plugin'")

auth plugin is a custom lua plugin, for which support just was enabled in the konnect interface.
The plugin exists in the interface, and the schema file has been uploaded and is valid and the plugin runs correctly in the runtime instances.
If I dump the config with 1.27.0 it will only change the _konnect.runtime_group_name property to be named _konnect.control_plane_name and still refuses to sync or diff with the same error.
config I'm running:
_format_version: "3.0"
_konnect:
  runtime_group_name: Remote API # If I do `dump` with 1.27.0 this is the only line changed
services:
- connect_timeout: 60000
  enabled: true
  host: api.default.svc.cluster.local
  name: api
  port: 80
  protocol: http
  read_timeout: 60000
  retries: 5
  routes:
  - https_redirect_status_code: 426
    name: api
    path_handling: v0
    paths:
    - /
    plugins:
    - config:
        authorization_endpoint: http://auth-server.default.svc.cluster.local./auth
      enabled: true
      instance_name: auth-plugin
      name: auth-plugin
      protocols:
      - http
    preserve_host: false
    protocols:
    - http
    regex_priority: 0
    request_buffering: true
    response_buffering: true
    strip_path: true
  tags:
  - remote-api
  write_timeout: 60000

looks like it cannot find the schema of the plugin.
what does GET /plugins/schema/[plugin-name] return (http call on the management api), compared to GET /plugins/schema/key-auth.

Hi @EDeijl , would you mind trying with v1.27.1? We have pushed a few fixes yesterday.

Hi @EDeijl , would you mind trying with v1.27.1? We have pushed a few fixes yesterday.

This has fixed it! Thanks 👍


Dilar : Source request

Source name
Dilar
Source link
https://dilar.tube/
Source language
Arabic
Other details
No response
Acknowledgements

[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

uses GMANGA theme


Adds missing referrer mango account to PlacePerpOrder

Status
Type
⚠ Core Change
Issue

Ready
Hotfix
Yes
#60

Adds the missing referrer mango account public key to the PlacePerpOrder instruction

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 4 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 80.206%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
2163

Relevant Lines:
2666

💛  - Coveralls


feat: respect icm language settings

PR Type

[x] Feature
[x] Refactoring (no functional changes, no API changes)
What Is the Current Behavior?
The PWA ignores locale settings from the ICM, that are available in the configurations REST response.
What Is the New Behavior?
If retrieved, the PWA uses the ICM locale settings to set a default locale and filter available locales based on channel settings.
Does this PR Introduce a Breaking Change?

[ ] Yes
[x] No
Other Information
To have access t the configurations call results in the configurations store, the server-config store has to be moved from general to core.

wait for integration of #659

Hi Danilo, thanks for the PR! When you submitted this, we were in the middle of our own localization rework. You wrote some nice code, though and we used parts of it in #695 .
Thanks for your work but since this is fixed I'm closing the PR.


[v1.4.0] Updated Task's date attributes, updated UI to display information, bug fixes

Task changes

End date is no longer a mandatory field for adding tasks.
The end date will be the same as the start date if not specified by user.
The keyword today is now accepted as an input for start date or end date.
Program will automatically use the current system date if today is given as an input.

UI changes

Added new pane with tabs to show information of selected patient and records.
Tab that shows records will only be displayed when the user enters goto mode.
User can swap between tabs by clicking on the specific tab.

Model & Logic changes

Records can now be selected and the program now tracks which record is being selected.
Implemented to support the UI change of displaying record details.
taskadd and taskedit now checks if the program is in goto mode when the user tries to link a patient when adding or editing a task.
Attempting to link a patient when the program is in goto mode will prompt the user to exit goto mode first. (This is because the patient list must be shown when linking a patient to a task to ensure the user knows the index.)
help and exit are now supported in Task Calendar(TC) popup.
Using exit in TC mode will close(hide) the popup.

Bug fixes

Fixed bug where teeth image is not displayed when running the application from a jar file
Fixed bug where taskdone cannot be used in TC popup.
Fixed bug where alert box (the one that shows up when deleting a patient with any linked tasks) text is being truncated

Coverage increased (+0.1%) to 52.845% when pulling 30d89314ff4a95430f8a49049b6f73132311642b on cchj1995:master into 105f070ee2a5eb9ec6ddbd784f2c3b7014c12cc2 on CS2103-AY1819S2-W17-2:master.


mismatch in "installed" status between sidebar and main dashboard contents

really a minor inconvenience: after installing a few datasets, some of them appear as installed in the main dashboard, but not in the sidebar. In the screenshot below, look at "Cancer rates by US state", which I didn't install by clicking it (yet!):

This may be because of overlapping table names between datasets, or some tiny typos / mismatch in the code checking the installed status between those two parts of the UI. Perhaps you can just store a flag somewhere based on dataset ID (which you pass to InstallDS()) and make the installation status more explicit.

The shared snapshot is not stating any problem and status of sidebar and main dashboard is matching already.
Thanks

aaaaah, I was just looking at the colours and though green meant installed, which by sheer chance matched for the one in the line above that I looked at 😄
Thanks for the clarification!


IDEA - Pull from a feed

Love your project! I thought of using Python to call the block endpoind of an account but this is a lot more creative & easier for the end user.
My idea is to pull from a source like: https://blockout2024.org/ rather than static json file.

Thanks for the feedback!  The newest version of my instagram celebrity blocker is pulling from GitHub now.  I'll see what I can do about puling from other sources like blockout2024.org.


Can't run tests with es6 imports

Describe the bug
I'm using react-create-app for my application.
I've used npm run eject to get control over all the configuration files.
I'm trying to write unit-tests to some of my services in my application.
I'm importing modules inside the spec file using es6 import syntax as follows:
import LeverageLevelService from './index';

describe('leverage-level', () => {
    it('should pass case1', () => {
        ...
    });
});

I'm getting the following error while running npm test:
import LeverageLevelService from './index';
                                                                                ^^^^^^^^^^^^^^^^^^^^

    SyntaxError: Unexpected identifier

      at ScriptTransformer._transformAndBuildScript (node_modules/jest-runtime/build/script_transformer.js:403:17)

My jest is configured to run babel-jest to compiles the spec files since I've ejected from react-create-app and this is the default behavior. Here's my jest config taken from package.json:
"jest": {
    "collectCoverageFrom": [
      "src/**/*.{js,jsx,mjs}"
    ],
    "resolver": "jest-pnp-resolver",
    "setupFiles": [
      "react-app-polyfill/jsdom"
    ],
    "testMatch": [
      "<rootDir>/src/**/__tests__/**/*.{js,jsx,ts,tsx}",
      "<rootDir>/src/**/?(*.)(spec|test).{js,jsx,ts,tsx}"
    ],
    "testEnvironment": "jsdom",
    "testURL": "http://localhost",
    "transform": {
      "^.+\\.(js|jsx|ts|tsx)$": "<rootDir>/node_modules/babel-jest",
      "^.+\\.css$": "<rootDir>/config/jest/cssTransform.js",
      "^(?!.*\\.(js|jsx|ts|tsx|css|json)$)": "<rootDir>/config/jest/fileTransform.js"
    },
    "transformIgnorePatterns": [
      "[/\\\\]node_modules[/\\\\].+\\.(js|jsx|ts|tsx)$",
      "^.+\\.module\\.(css|sass|scss)$"
    ],
    "moduleNameMapper": {
      "^react-native$": "react-native-web",
      "^.+\\.module\\.(css|sass|scss)$": "identity-obj-proxy"
    },
    "moduleFileExtensions": [
      "web.js",
      "js",
      "web.ts",
      "ts",
      "web.tsx",
      "tsx",
      "json",
      "web.jsx",
      "jsx",
      "node"
    ],
    "watchPlugins": [
      "C:\\Users\\username\\WebstormProjects\\Project\\node_modules\\jest-watch-typeahead\\filename.js",
      "C:\\Users\\username\\WebstormProjects\\Project\\node_modules\\jest-watch-typeahead\\testname.js"
    ]
  },

As can be seen babel-jest is configured for any kind of extension file so it should work:
    "transform": {
      "^.+\\.(js|jsx|ts|tsx)$": "<rootDir>/node_modules/babel-jest",

Not sure what's going wrong in here, would appreciate if someone could pinpoint the problem.I wish to unit test some services in my react app.
My service is written with ES6 and when I run npm test it fails with:
import LeverageLevelService from './index';
             ^^^^^^^^^^^^^^^^^^^^
    SyntaxError: Unexpected identifier

I also tried adding "@babel/plugin-transform-modules-commonjs" to my babel plugins inside the webpack.dev.config file (I've used npm eject)
Did you try recovering your dependencies?
Yes
NPM version: 6.4.1
Environment
Environment Info:

  System:
    OS: Windows 10
    CPU: (8) x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
  Binaries:
    Node: 10.15.3 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.9.0 - C:\Users\<username>\WebstormProjects\WaltyFE\node_modules\.bin\npm.CMD
  Browsers:
    Edge: 42.17134.1.0
    Internet Explorer: 11.0.17134.1
  npmPackages:
    react: ^16.8.6 => 16.8.6
    react-dom: ^16.8.6 => 16.8.6
    react-scripts: Not Found
  npmGlobalPackages:
    create-react-app: Not Found

Steps to reproduce
1.create react app
2. run npm run eject
3. write a js file with ES6 features
4. create a spec file and import it
Expected behavior
Should've compiled without errors.
Actual behavior
Compiles with the specified error above.

Sorry, we aren't able to provide advice for any custom ejected configs.  Please try the jest issues or stackoverflow.
jest uses babel-jest and doesn't use webpack configs, you'll need an appropriate babelrc

Although I ejected I didn't really change anything config related.
So according to what you say I need a custom .babelrc file. How can I use a .babelrce with the default ejected configuration while solving this issue?

I'm saying that editing your webpack configs won't affect with your jest runs.
The default react app template works fine with jest after ejection.
If you want to customize your babel rules for jest, you'll need something like .babelrc or babel.confnig.js: https://jestjs.io/docs/en/getting-started#using-babel

I added babelrc: true to the options of babel-loader and added .babelrc file to the root of the project, copying the default configuration options from babel-loader and it seemed to work now, is that because babel-jest relies on .babelrc file and cannot read from the options in babel-loader inside the webpack config? If so how does jest works before ejecting, and do I need to do this everytime I eject a react-create-app for jest to work?

I'm glad it worked out for you.  I don't have any specific advise on what to do after ejecting.  As I stated https://github.com/facebook/create-react-app/tree/master/packages/babel-preset-react-app is used by default, you can continue to use it or use your own babel configs.


Develop and implement systematics mapping and linear deprojection functionality in  TXPipe.

This task is from the quarterly plan in the draft S17 IKC workplan.

30/NOV/23

working on the maps
now need implementing across the entire HSC field

20/DEC/23

@tmcornish reported

We've identified some places where the pipeline can be modified to suit our goals, and last week I submitted a pull request to the GitHub which has now been accepted. The next step is modifying how the pipeline conducts analysis of the density maps and accounts for systematics in Fourier space.

25/JAN/24

Tom currently writing an independent code first before tackling the implementation in TxPipe

08/FEB/24

independent code is now done
now looking to implement this in TxPipe, PR will be provided when this is done.

07/MAR/24

modifications in TxPipe enables required analysis
outstanding issue is outputs are different from external scripts so investigating further

14/MAY/24

will close when PR is finished

04/JUN/24

agreed to close


Path Strings/Strings contains a backslash () that is serialized and opened in i.e. VS Code is mistaken to be escape sequences

I don't understand the issue. Can you provide an example as well ?

It serializes my object into this: {"RecentProjects":["C:\dev\Beef\Steel\Examples\EditorDemo"]}. It should be double backslashes.

Oh okay I see. Will look into it.

Ok, I will make sure it is then 👍


Reference external default values files

Feature request to be able to reference an external value file for a chart. This concept is to be able to dry up repetitive base configurations across course.yml in different environments. These files could be layered, with deep merging preferring the latest item defined.
Example
charts:
  my-release-cert-manager:
    chart: cert-manager
    version: 0.6.0
    remote-default-values:
    - type: <type> # default to detect type if `type` key isn't defined
      source: <url> # utilized by the type implementation provider (with protocol)
      path: <path> # path to get/clone to a temp file locally

I'm envisioning supported values in the remote-default-values key would be:
remote-default-values:
- source: https://my.domain/
  path: /path/to/file
- type: git
  source: ssh://git@github.com:org/my-repo.git
  path: /path/to/default.yml
- type: git
  source: git@github.com:organiz/my-repo.git
  path: /my-default.yml
# Maybe if we're feeling fancy, use the AWS API to pull this object
- type: s3
  source: s3://my-bucket-of-defaults/
  path: /path/to/default/object.yml

Protocol detection would be based on git urls as well as protocol support for standard HTTP(s). If a protocol is tried and failed we should bubble up that error.
Thoughts and Considerations

Deep merging of values is handled with helm's default behavior (we don't deserialize the loaded remote yaml)
Helm command definition ordering priority of values

set-values
values
files (values files locally)
remote-default-values
remote chart values.yaml defaults

Not included in MVP

variable interpolation in the default templates

Seems awesome.  If we are going to support s3, we should simultaneously plan to support gcloud buckets.

Apparently this is already a feature in helm (for -f http://endpoint.com/file.yml). We can cross that one off the list for needed in the impl.


Can not edit or create new records in rails admin

I have a problem with crating and updating records with rails_admin. For update I get the 404 error, where POST actions is not found:
{"status":404,"error":"Not Found","exception":"#\u003cActionController::RoutingError: No route matches [POST] \"/admin/api_key/1/edit\"....
But if i look in the routes file, i see it's registered at PUT method.
For creating new record i get:
{"status":422,"error":"Unprocessable Entity","exception":"#\u003cActionController::InvalidAuthenticityToken: ActionController::InvalidAuthenticityToken\u003e","traces":{"Application Trace":[],"Framewor....
my config file:
RailsAdmin.config do |config|   config.actions do     dashboard                     # mandatory     index                         # mandatory     new     export     bulk_delete     show     edit     delete     show_in_app   end end
my route setting:
Rails.application.routes.draw do   mount RailsAdmin::Engine => '/admin', as: 'rails_admin'

I'm getting the same too, and I think this happened after I upgraded my gems

Yep, the problem is on 1.1.1; I reverted back to 1.1.0 and no errors encountered :)
But there's a need to find why its happening in the new version!

Not reproducible here, can you make the problem happen by using brand-new Rails app?

Just installed a fresh rails instance, and was able to replicate same issue. Rolling back to 1.1.0 resolved it for me also.
Using papertrail and devise if that helps any?

I just did fresh rails instance with papertrail and devise and I can create new record. I'm not able to reproducible.

I am having the same issue with 1.1.1 and going back to 1.1.0 solves the problem but as stated here, it's recommended to upgrade to 1.1.1 because 1.1.0 is known to have CSRF vulnerability.

I can also reproduce it with a fresh Rails app using --api.

Also reported here: https://github.com/rails/rails/issues/21948#issuecomment-307165595
I doubt it's Rails core issue, though, as it would have been fixed in newer versions otherwise.

The rails core issue seems to happens when you close the page and open again, so it might be unrelated.

I've considered it, of course, as well as the secondary calls (e.g. pjax) that may be recreating the token, and two users accessing the same site with the same admin_user.id.
I'll dig it deeper when I have time.

Fixed this by one or both of:

upgrading to Rails 5.1
implementing nginx real_ip module so that request.ip is always equal to request.remote_ip

I have rails 5.1.1 and no nginx.

@lesliev Dude, you totally are a day saver.
This solution works for both issues as advertised ! Thanks a lot.

Fixed by #3006.

I had this issue and adding config.middleware.use ::Rack::MethodOverride to the application.rb did not work for me.
This issue was present in my recently deployed production server (nginx+puma+rails), SSL enabled.
I fixed this by adding proxy_set_header X-Forwarded-Proto https; to the Nginx site configuration, like this:
location @puma {
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header Host $http_host;
  proxy_set_header X-Forwarded-Proto https;
  proxy_redirect off;

  proxy_pass http://puma;
}

This also solved getting "connection not secure" in Chrome even though my certificate was valid. It's not a rails_admin but it was showing there.
My settings
Rails API only.
Rails 5.2.3
rails_admin 1.42


bluetooth: controller: Revised ticker for improved conflict resolution

Changed ticker behavior to resolve conflicts in ticker_worker instead of
in ticker_job. This allows better real-time slot allocation, as well as
allowing callbacks even if ticker node doesn't get air-time (for audio
stream housekeeping). A priority property now also allows prioritizing
one ticker node over others.
Compatibility mode enables lagacy ticker behavior if needed.
Signed-off-by: Morten Priess<EMAIL_ADDRESS>

@cvinayak, any idea why Shippable fails?

CC @alexeRadu

The changes look good by inspection (minor change requested) and sanity run of scan_adv sample on nRF51 seems ok.

The changes look good by inspection (minor change requested) and sanity run of scan_adv sample on nRF51 seems ok.

. Is it possible for you to test scan_adv with nRF52 as well (=> new code exercised)? As far as I can see with nRF52, advertising is identical to using legacy ticker.

@cvinayak Ready!

As discussed on Tuesday 2019/08/06, this PR should correct the issue found in the previous PR #15787 (which was followed by the revert in #16885), by disabling the new functionality by default for the NRF51 with the new BT_TICKER_COMPATIBILITY_MODE.
If we were to find issues for NRF52 platforms, we could (in the worst case) change that default also for those.


Temporary fix build by disabling smoke test on gp tutorial

Discussion in #953. This seems to strangely and non-deterministically trigger on travis-ci. I am not able to replicate it locally yet.

Thanks for diagnosing this, Neeraj

@fritzo - I canceled the integration tests, and since the examples stage passes, we can merge this.

i recently learned cancelling unnecessary tests is frowned upon now, so i enabled the merging restrictions to require tests pass. i disabled it to merge this, but if they dont cost us anything, we should maybe always allow tests to run to completion. cc: @fritzo


chore(): updating to capacitor 4

Updating the code to go along the way with capacitor

Hello ! Have you an NPM package for this ? or a commit including the built code in order to try this with npm install ?
Thank you !

just pushed dist folder so this:
npm install chrum/capacitor-sms#capacitor-4-dist

should do the trick

wonderful, thank you !


theme colors support for Navbar color

Is your feature request related to a problem? Please describe.
Hi, in my app I have property from which navbar's color is changed. I want to use primary and success as my navbar color instead of hardcoded hax value how can I do that.
Describe the solution you'd like
Navbar color should also support theme colors like other components.
Describe alternatives you've considered
There's temporary I hard coded my color which is not dynamic and not good.

In the last update the support for the main colors was added
Thank you very much for the contribution


Application Service registration file options undocumented

Application Service registration files support rate_limited and protocols fields, however we don't specify this anyways in the Application Service Documentation.
Ideally we would have a table to break down and explain every possible AS registration file option and whether each is required or not.

Also the group_id for the users regex

Thanks, will note that one down too.

to clarify, it's this:
namespaces:
  users:
    - exclusive: true
      regex<EMAIL_ADDRESS>      group_id: '+discord:t2bot.io'

Neither. All the users that match the regex will be considered publicly joined to the group_id. They will not appear in a membership list though.
The intention is to have flair, but not a list of people to spam.

@turt2live Cool, alright.