How is this organization & package related to Vite's import.meta.env?

Hi Ernest,
First thank you for your effort & dedication for this project - I'm using it for containerizing our frontend and it works great 🙂
According to https://vitejs.dev/guide/env-and-mode.html:

Vite exposes env variables on the special import.meta.env object.

But I don't see this package being imported in Vite's package.json
How is this related? Does they really use your package or just the naming is confusing us to think they does?

Hello,
Thank you for using our project to containerize your frontend. I'm delighted to hear it's working well for you.
Regarding your question about Vite and the import-meta-env packages, it's important to clarify that the import-meta-env packages are designed to offer a framework-agnostic solution for developers working with JavaScript. They are not directly related to Vite and are not included in Vite's package.json.
Additionally, it's worth noting that import-meta-env supports various libraries and plugins like Babel, SWC, Webpack, Rollup, or RSPack, providing flexibility and compatibility with a range of tools.
I hope this explanation provides the clarity you were seeking. If you have any further questions or require additional information, please feel free to ask.

Thanks for clarifying! I would suggest to maybe rename the import.meta.env variable or write the disclaimer that your project is not related to Vite. I just find the usage of the same variable as in Vite being misleading & making an impression of being Vite-related implementation
Cheers


Missing unversioned deps in the normalized graph

I am trying to download logback-classic and getting the following error:
[main] ERROR MakeDeps - resolution and sha collection failed
java.lang.Exception: Missing unversioned deps in the normalized graph: ch.qos.logback:logback-classic
	at com.github.johnynek.bazel_deps.MakeDeps$$anonfun$resolve$2.apply(MakeDeps.scala:164)
	at com.github.johnynek.bazel_deps.MakeDeps$$anonfun$resolve$2.apply(MakeDeps.scala:131)
	at scala.util.Success.flatMap(Try.scala:231)
	at cats.instances.TryInstances$$anon$1.flatMap(try.scala:35)
	at cats.instances.TryInstances$$anon$1.flatMap(try.scala:14)
	at cats.FlatMap$Ops$class.flatMap(FlatMap.scala:21)
	at cats.FlatMap$ToFlatMapOps$$anon$2.flatMap(FlatMap.scala:21)
	at com.github.johnynek.bazel_deps.MakeDeps$.resolve(MakeDeps.scala:131)
	at com.github.johnynek.bazel_deps.MakeDeps$.runResolve(MakeDeps.scala:108)
	at com.github.johnynek.bazel_deps.MakeDeps$$anonfun$1.apply(MakeDeps.scala:37)
	at com.github.johnynek.bazel_deps.MakeDeps$$anonfun$1.apply(MakeDeps.scala:37)
	at scala.util.Success.flatMap(Try.scala:231)
	at com.github.johnynek.bazel_deps.MakeDeps$.apply(MakeDeps.scala:37)
	at com.github.johnynek.bazel_deps.ParseProject$.main(ParseProject.scala:17)
	at com.github.johnynek.bazel_deps.ParseProject.main(ParseProject.scala)

my dependencies.yaml looks something like this:
options:
  languages: [ "java" ]
  licenses: [ "notice" ]
  resolverType: "coursier"
  resolvers:
  - id: "mavencentral"
    type: "default"
    url: https://repo.maven.apache.org/maven2/
  thirdPartyDirectory: "third_party/jvm"
  buildHeader:
  - load("@io_bazel_rules_kotlin//kotlin:kotlin.bzl", "kt_jvm_import")
  - licenses(["notice"])

dependencies:

  ch.qos.logback:
    logback-classic:
      lang: kotlin
      vesion: "1.2.3"

I would have expected this to work - also I don't quite understand the error message. What does it mean?

Is that jar really Kotlin?
In any case could this be a version of #220 ?
Lastly that error is actually just an assertion we have that everything declared winds up in the final graph. You could remove the assertion and see if things were fine yet it was the assertion failing.

@Globegitter You spelt "version" incorrectly, that's why you're seeing that error. You've got vesion:
@johnynek I think this can be closed 👍

Thanks. This is a problem with parsing as yaml with our current parser: it just silently ignores unexpected keys which means it doesn’t always see typos.


LESS version

Would be great if you had a LESS version

I concur. This would be awesome if there was LESS support

:+1:

Hey guys!!! =)
Please, this is very relevant... take look at this.
https://www.npmjs.com/package/grunt-refactor

+1, Less is really easer to use maintain and compile.

+1  My team is eager to start using Materialize, but we are waiting for LESS version.

we need the LESS version, would be great.

+1... I think it would be really important. LESS is easer to work

+1 I LESS version would be great. Much easier.

Support for Less would be awesome!!

+1 LESS

LESS

LESS please

+1

+1

+1

+1

+1

+1

+1

Might give this a go myself.

+1 This would let people who use LESS to import Materialize directly into their code.

please allow less :(  - 99% of my css is less compiled

LESS would be less instead of S(ass)

+1 It would be awesome :)

:+1:

+1

As long as it doesn't replace SASS!
But it would mean more work to keep up to date both LESS and SASS to do the same job.

+1

+1

+1

:+1:

+1

LESS please!

LESS !

+1 LESS

:-1:  for LESS.

+1

Who can list compelling reasons why migrate on less?

Don't you think that there is a big enough crowd that prefer LESS? A lot of
people with Twitter Bootstrap background knows LESS better and I do think
that there is a whole lot of people with that background. With that said,
SASS is getting more and more dominant and even Bootstrap is letting go of
LESS in their Bootstrap 4 so, as of now, i cannot see any reason except
convenience for all the people that prefer LESS, but I don't know in what
approach you have towards your users.
2015-11-17 13:48 GMT+01:00 Valery Lyatevich<EMAIL_ADDRESS>
Who can list compelling reasons why migrate on less?
—
Reply to this email directly or view it on GitHub
https://github.com/Dogfalo/materialize/issues/313#issuecomment-157362547
.

+1

+1 Less

+1 for Less

+1 still wanted ;)

+1 for Less

+1

+1

+1

This would allow Materialize to work with Sails.js (which use Less) by default and would be awesome for fast development

+1

+1

++ !

+1

+1

+1

+1

+1

+1

+2 1 for ego

There are so many people left +1 comment here, that more than enough to develop a fork of MarerializeCSS with LESS, instead of asking core devs :smile:

I agree with @kmmbvnr that there are a "big enough crowd that prefer LESS" to do something about it, then someone ought to do something, right?
Also, that are arguably more reasons to keep SASS only than to have a LESS version, or even both of them. The popularity of something does not necessarily indicate any form of superiority. Because IDE vs SCSI, VHS vs Betamax, Blue-ray vs HD DVD, to name but a few, were popular, and yet not necessarily the best technological choices.
The module is published with a pre-built CSS file that can easily be merged with other CSS files, generated or not. I don't see a good reason to fiddle with the SASS anyway; extend the styles with your own custom selectors and styles!

This isn't something that we think would be a good use of our time, so we won't be maintaining a LESS version. If someone does make their own however, post it here to help people out 👍

totally understandable though, this lib wasn't built on Less.


[GLUTEN-2038][VL][FOLLOWUP] Fix and add test

The reason why E2EFilterTest .metadataFilter failed is that, it tests the filter pushdown using row group metadata but  after https://github.com/oap-project/velox/pull/326 it only has one row group. This prs change the max rows in one row group to 10 which is aligned with the test batch size, so that each batch can produce a row group.
Besides, this pr adds a new test to check we can combine small batches into a big row group.

cc @JkSelf @zhejiangxiaomai thank you

After this pr passed, I can make a new pr to fix format check.


Transitions

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
It seems like all the components should have exposed transitions props just like you exposing actions. You could have transition/option for combined in/out, as well as individual in/options and out/options.
What type of pull request would this be?
None
Any links to similar examples or other references we should review?
No response

@cycle4passion unfortunately Svelte transitions and Actions are not apt comparisons here.
Let's take the Avatar component for example, we accept the following props:
export let action: any = () => {};
export let actionParams = '';

action represents the actual action function to run
actionParams represent the object of optional settings (aka args) to said action

Then within the component we use the following to apply the action to the img element:
<img ... use:action={actionParams} />

This works great for Actions. However, if we take a look at even a minimal example of a Svelte transition we'll notice some key differences.
https://svelte.dev/tutorial/transition
<script>
	import { fade } from 'svelte/transition';
	let visible = true;
</script>

<label>
	<input type="checkbox" bind:checked={visible}>
	visible
</label>
{#if visible}
	<p transition:fade>Fades in and out</p>
{/if}

The good news is I tested the transition directive of transition:foo where foo was an empty object, and it did work as expected. So that's good, at least it's somewhat comparable there.
However, a key difference with Svelte Transitions is they require a wrapping{#if} statement around the element that contains the transition directive (ex: transition:foo). This means we would need a THIRD prop added that's a boolean value.
So what I'm saying, is that while there's some technical capabilities to do this. It's not going to be be a trivial lift to implement. And there's a bit of the elephant in the room here, in that there's nothing stopping you from implementing this using a wrapping element instead. It would work exactly the same for zero additional effort. Here's a quick trivial example:
<script>
	import { fade } from 'svelte/transition';
	let visible = true;
</script>

<label>
	<input type="checkbox" bind:checked={visible}>
	visible
</label>
{#if visible}
	<div transition:fade>
                <Avatar src="https://i.pravatar.cc/?img=48" width="w-32" />
        </div>
{/if}

My guess is that's not what you want though, that you want localized transitions within a portion of the component. And that complicates things ten fold. We then have to have a matching set of transition function, transition params, and boolean conditions PER portion of the component that's being transitions. All in all I just don't feel that's a reasonable ask.
What I might suggest instead, is let us know if there are particular components that you would like to see containing a built-in animation feature. For example, folks asked for Accordions to animate when open/closing AccordionItems. We'll gladly field requests like that. And honestly it may be a better approach since it benefits everyone.

Thank you for your very well thought out and considerate response. I have to agree with you. To further add to your argument, people would probably want transition   in: and out: options further increasing the params count. I agree that a wrapping conditional div is probably the best solution.

For sure, it could get real messy, real quick.

I guess the component I was thinking about and prompting my request was tabs.    This surely need transition support when tabpanels   change. I think this warrants the special special   use case as you did for accordion. For accordion a slide up/down is obvious.    For a tabpanel change either fade or     slide left/right (not natively supported by svelte transitions) would seem to the most obvious.

Great suggestion. Would you mind setting up a feature request for that? Obviously our focus right now is the v1.0 launch later this week, but I feel like this is something we could spend some time on in the near future. It's certainly something I'd like to see as well!


Remove PCmover Express reference

Lapilink's PCmover Express will cease to be free starting July 31st, 2021. It is currently not free for commercial use. Because these two facts conflict with USMT's free for commercial use solution, please remove the reference.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: cde8580a-bd82-ebd2-3767-f3ee662a904e
Version Independent ID: 94323219-e4ed-8761-723e-06be33c3b9cc
Content: User State Migration Tool (USMT) Overview (Windows 10) - Windows Deployment
Content Source: windows/deployment/usmt/usmt-overview.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

I will add a note that it is not free. The purpose of the article is not to provide only guidance that is free.


Different groups for notifications

Is your feature request related to a problem? Please describe.
When you use the app notifications a lot, is difficult to know when they are important (alarm for example) or informative only.
Describe the solution you'd like
Android let's divide the notifications in different groups, with different sounds, visibility, etc.. Let assign a group in the service as optional parameter when sending the notification.
Describe alternatives you've considered, if any
None.
Additional context
None.

Duplicate: https://github.com/home-assistant/home-assistant-android/issues/107


[BUG] simple C++ fmtlib example compiles does not execute

Describe the bug
A simple C++ example using fmtlib compiles but does not execute.
To Reproduce
Steps to reproduce the behavior:
#include <string>

#include <fmt/format.h>

int main() {
  const std::string s = fmt::format("The answer is {}.", 42);
  fmt::print("The answer is {}.", 42);
  return 0;
}

Pick the {fmt} in the library picker in both compile and execution panels.
Expected behavior
Program compiles and executes correctly.
Link
https://godbolt.org/z/PCoSdK
Screenshots

Desktop (please complete the following information):

OS: Win10, Ubuntu 16.04
Browser: Firefox
Version: 75.0

Additional context
N/A

We don't yet support linking with libraries for execution, I'm sorry. Duplicate of #1662


CB-10844 CM launched on Gateway in Flow Management Light/Heavy duty t…

…emplates. Changed 'gateway' node name to 'management', according to customer request.
See detailed description in the commit message.

@lajosrodek @doktoric should i also merge this change to some other branches or master will be enough?

@lajosrodek @doktoric should i also merge this change to some other branches or master will be enough?

@vbrodetskyi master (v2.38 at the moment) is sufficient if you are fine with having it only from CB 2.38 onwards. Otherwise, it would have to be pushed directly into some release branch and then rolled out as a Prod Hotfix. 😃
Holding back with merging until someone from CB can also approve.

@vbrodetskyi master (v2.38 at the moment) is sufficient if you are fine with having it only from CB 2.38 onwards. Otherwise, it would have to be pushed directly into some release branch and then rolled out as a Prod Hotfix. 😃
Holding back with merging until someone from CB can also approve.

@lajosrodek thank you for clarification, according to fix version in jira https://jira.cloudera.com/browse/CB-10844, it should be i 2.38, so looks like master branch should be enough.

@lajosrodek thank you for clarification, according to fix version in jira https://jira.cloudera.com/browse/CB-10844, it should be i 2.38, so looks like master branch should be enough.


FontAwesome5  edit Icon

[x] Review the documentation: https://github.com/oblador/react-native-vector-icons
[x] Search for existing issues (including closed issues): https://github.com/oblador/react-native-vector-icons/issues

MacOS- Mojave
React Native Expo
"react-native-vector-icons": "^6.6.0",

Im trying to add fontawesome5 edit icon

after I already apply the icon, you can see the difference.

Reproducible Demo
https://snack.expo.io/@mrvictoria/fontawesome5-icon
Let us know how to reproduce the issue. Include a code sample, share a project, or share an app that reproduces the issue using https://snack.expo.io/. Please follow the guidelines for providing a MCVE: https://stackoverflow.com/help/mcve

I was about to create a similar issue about the star icon:
Environment
Android 10
react-native-vector-icons: ^7.0.0
Description
In the directory FontAwesome5/star icon is a filled star:

But when I try to display it, I get an empty star:

Demo
https://snack.expo.io/@yairopro/f56ceb

Try adding solid as the prop. :)
<FontAwesome5 name={'edit'} size={40} solid/>

@mardikarifqi  Seems to work👌🏻


chore(deps): bump https://github.com/zeebe-io/zeebe-cluster-helm from 0.0.18 to 0.0.19

Update zeebe-io/zeebe-cluster-helm from 0.0.18 to 0.0.19
Command run was jx step create pr chart --name zeebe-cluster --version 0.0.19 --repo https://github.com/zeebe-io/zeebe-full-helm.git

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: salaboy
If they are not already assigned, you can assign the PR to them by writing /assign @salaboy in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@salaboy: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

serverless-jenkins
28aea4d0eef0ecacdc8f708cf56eee3cb45768e2
link
/test this

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Support manual rollback in interactive transactions

Problem
To rollback an interactive transaction, you have to throw an error. It would be awesome to have a manual rollback function (that potentially takes a data argument to pass back to the parent caller). Throwing errors makes code less predictable and weakly typed. We try to reserve throwing errors for unexpected errors, not for expected ones.
Suggested solution
When in a transaction block, be able to call rollback on the prisma client. One potential implementation:
await prisma.$transaction(
  async (prisma) => {
    // Code running in a transaction...
  prisma.rollback();
  // or with arbitrary data/error
  prisma.rollback(err);
  }
)

Alternatives
We don't really have an alternative here as we can't rollback without an error.
Additional context
Initially suggested here

Any update on this? i can't find this feature on official documentation.

any updates?

What does interactive code mean after a transaction commit or rollback command? In my opinion, the transaction end command should be equivalent to the function's end command.

While there is no built-in functionality for this, it can be implemented via client extension. Here is an example of the one that allows to roll back the transaction by returning rollback symbol:
class RollbackError extends Error {}
const rollback = Symbol()
const prisma = new PrismaClient()

const xprisma = prisma.$extends({
  client: {
    async $noThrowTransaction<T>(
      callback: (client: Prisma.TransactionClient) => Promise<T | typeof rollback>,
    ): Promise<T | undefined> {
      let result: T
      try {
        result = await prisma.$transaction(async (tx) => {
          const innerResult = await callback(tx)
          if (innerResult == rollback) {
            throw new RollbackError()
          }
          return innerResult
        })
      } catch (error) {
        if (error instanceof RollbackError) {
          return undefined
        }
        throw error
      }
    },
  },
})

// usage
const result = xprisma.$noThrowTransaction(async (tx) => {
  if (someCondition) {
    return rollback
  }
  return tx.user.findUniqueOrThrow()
})

But it also higlights a typesafety problem with this feature request: what should return value of $noThrowTransaction should be if it is using manual rollback? It can not be  return value of your callback since transaction is stopped before we got it. In by example it is undefined which creates it's own bundle of problems. It can also be some magic value, for example, the same rollback symbol. But that will poison the return types and you'll have to add if (result !=== rollback) condition every time before you can do anything with the return value.  Overall, it does not feel to me that for cases where we care about return value any of the proposed solutions substantially improves ergonomics over throwing errors. You are free to experiment with the extension I provided though - if it works for you then great, if it does not - feel free to adjust it in any way.

@pheetah because nobody built it yet. You are free to experiment with the extension I posted in my previous comment. In order for us to consider it as a built-in feature we need good answers to the questions I posted in the end of this comment and so far nobody attempted that.

Something like how sequelize does it: https://sequelize.org/docs/v6/other-topics/transactions/#unmanaged-transactions
// First, we start a transaction from your connection and save it into a variable
const t = await sequelize.transaction();

try {
  // Then, we do some calls passing this transaction as an option:

  const user = await User.create(
    {
      firstName: 'Bart',
      lastName: 'Simpson',
    },
    { transaction: t },
  );

  await user.addSibling(
    {
      firstName: 'Lisa',
      lastName: 'Simpson',
    },
    { transaction: t },
  );

  // If the execution reaches this line, no errors were thrown.
  // We commit the transaction.
  await t.commit();
} catch (error) {
  // If the execution reaches this line, an error was thrown.
  // We rollback the transaction.
  await t.rollback();
}

Any update about this?

https://github.com/prisma/prisma/issues/22309 This might help. Although we as team have moved to typeORM for better features.


Failed to refresh

On my MIUI Redmi note 4, with android 6.0 the widget refresh button do not work at all. Moreover, it not refresh automatically after an event has passed.

@hodbauer It's interesting, as for your observation, when is the Calendar Widget list updated?
The Calendar Widget is updated by external events, presumably sent by a Calendar application or a "Refresh" button,
and also automatically once in 6 hours (as I see in https://github.com/plusonelabs/calendar-widget/blob/master/app/calendar-widget/src/main/res/xml/calendar_appwidget_info.xml )

@yvolk The only case that I'm 100% sure about it, is when I'm scrolling to the bottom of the list, then it refresh the list, and I've got updated.
In any other case it's not for sure that i'll be updated.

See and follow up in #298


REQ-MCT-025 - List of future overpasses

The MCT shall display a chronological list of future overpasses for satellites of interest over user-specified ground station coordinates.

see #14
how will we test this? will create a new issue!


Change kubernetesVersion from v1.21 to v1.21.0

Fixes #27638

Signed CLA.

/assign @tengqm

Thanks @shannonxtreme .
/approve


python3Packages.tappy: refactor, add optional dependencies

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

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

That's a lot more rebuilds than I expected, retargeted to staging.

Fixed merge conflicts caused by https://github.com/NixOS/nixpkgs/pull/313628.


Handle slow UIs gracefully

Smooth scrolling, due to its nature, causes enormous amount of screen redraws. This is a problem when the redraw operation is particularly slow, f.ex. when running over a low-bandwidth SSH connection, or low-performance RPC pipelines, such as described in #17.
Minimal solution
As a bare minimum, the plugin should allow users to disable smooth scrolling on demand (f.ex. via dedicated variable or command), so that they can help themselves ad-hoc when the UI feels slow.
Optimal solution
Ideally, the plugin would detect as many slow-UI cases as possible, and automatically disable itself till the end of current editing session (or even better, adjust the animation frame rate dynamically to current conditions).

Detecting redraw speed and adjusting animation rate dynamically seems far outside the scope of what one would expect of a Vim plugin.
Probably a command to turn it on-off should suffice. You can always configure a hotkey for that command or use a separate refresh-rate-detection plugin to call that command.

I have tried to implement the minmal solution @psliwka mentioned in his post above
Please test #21 using the following config -
let g:smoothie_disabled = 1

and report bugs, if any

@psliwka We could use the ttyfast option to implement the optimal solution
You agree?

@psliwka We could use the ttyfast option to implement the optimal solution

Please correct me if I'm wrong, but ttyfast seems to be always on in current terminal world – almost all terminal emulators are xterm descendants or disguise themselves as such. Neovim devs even deprecated this option completely. Therefore, I doubt its value would carry any information useful for us.

Hm.... that's true...
But we could instruct the users to set this option when using a slow connection, because this option was meant for that...
:shrug:


Fixed output of Total test samples

Changed the variable name to display test_df, that was wrong before

Thanks for the PR. Please update all 3 files (py, ipynb, md).

Hi @apurvtaneja, thanks for the PR. Could you update the ipynb and md files, also? Let us know if you're still working on this. Otherwise we'll go ahead and close the request. Thanks!


[Popup] Light dismiss

I've been mulling over this proposal a bit. There have been a lot of interesting thoughts and reactions to it. (Thanks @tlouisse, @aardrian and others)
https://twitter.com/aardrian/status/1353060549102161921
https://twitter.com/aardrian/status/1353058391321530368
https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/442
I see the "light dismiss" behaviour as the most interesting part of this exploration. We currently have elements in a page that can have a show/hide or open/close state like <summary> and <details>. On the other side of the spectrum you can have a fully modal dialog.
The modal dialog has a lot of interesting aspects. You shouldn't be able to interact with the rest of the page which introduces a lot of caveats. A modal dialog is like a new page (but without the URL). It gives an entirely new context and removes you from the original context both visually, and non-visually.
It feels like the idea of a light dismiss tries to find a middle ground. It could be interesting for a proposal like this to explore the ideas behind modal behaviour (like defined with aria-modal).  Some elements are clearly not modal and some are completely modal, following the binary choices of aria-modal. What elements belong to the first group, which belong to the second, and which go into the category of the (semi-modal?) light dismiss. Likewise, what characteristics does it share with a modal dialog, and which doesn't it share?
A venn diagram of modal and non-modal behaviour could be made. And following, a venn diagram of (possible) elements. The current proposal is for an element, but the element is part of a system. When you want to improve a sytem by adding something, you need to consider the entire system.

There is another dimension to the venn diagram (or spectrum) from modal to non-modal behaviour, namely whether UI events are passed through when interacting with the area outside it - including the click-outside-to-dismiss.
In our web based design tool (https://github.com/concrete-utopia/utopia) we have three classes of controls that might be modelled with <popup /> or <dialog />:

A colour picker "popup" style control with swatches. It dismisses when clicking outside it. It  also needs to pass through that "click", as well as the hover events we use to draw hover outlines on other elements. Basically, the outside of the popup is transparent to all mouse events, including the click to dismiss.
An "uploading files" modal. Clicking outside it dismisses the modal, but neither the click outside nor the hover events should be passed through, but clicking outside does dismiss it.
A heavy "select" type of control. Here the click outside of it (to dismiss) should be passed through, but while the popup is visible, other events (e.g. hover) are not.

In practice we achieve this with a combination of React portals, fixed positioned elements with pointerEvents, global event handlers, and z-index contortions. In particular, we either have to draw a div to act as a click / hover catcher, or use global event handlers via JS. Because the click catchers need to have the right net z-index (behind the popup, in front of everything else), and cover an area contiguous to either the full screen or a part of it, we have to combine a number of techniques to achieve it (z-index, React portals, global event handlers, manually "positioning" the popup part).
There's obviously a number of ways to support it, but if the intention is for popup and dialog to cater for these use cases, having some control over what happens outside of the modal would be very welcome.

There is another dimension to the venn diagram (or spectrum) from modal to non-modal behaviour, namely whether UI events are passed through when interacting with the area outside it - including the click-outside-to-dismiss.
In our web based design tool (https://github.com/concrete-utopia/utopia) we have three classes of controls that might be modelled with <popup /> or <dialog />:

A colour picker "popup" style control with swatches. It dismisses when clicking outside it. It  also needs to pass through that "click", as well as the hover events we use to draw hover outlines on other elements. Basically, the outside of the popup is transparent to all mouse events, including the click to dismiss.
An "uploading files" modal. Clicking outside it dismisses the modal, but neither the click outside nor the hover events should be passed through, but clicking outside does dismiss it.
A heavy "select" type of control. Here the click outside of it (to dismiss) should be passed through, but while the popup is visible, other events (e.g. hover) are not.

In practice we achieve this with a combination of React portals, fixed positioned elements with pointerEvents, global event handlers, and z-index contortions. In particular, we either have to draw a div to act as a click / hover catcher, or use global event handlers via JS. Because the click catchers need to have the right net z-index (behind the popup, in front of everything else), and cover an area contiguous to either the full screen or a part of it, we have to combine a number of techniques to achieve it (z-index, React portals, global event handlers, manually "positioning" the popup part).
There's obviously a number of ways to support it, but if the intention is for popup and dialog to cater for these use cases, having some control over what happens outside of the modal would be very welcome.

Great examples @maltenuhn. I would like to add another example where light dismiss boundaries are not clear. The gif below shows what happens to the github dropdown when screensize is changed from 'desktop' to 'mobile':

Question arises: does the mobile screen still fit the 'light dismiss criterium'?
Since it has a backdrop, the only way to build this dropdown, would be with a <dialog>, since
popups don't have backdrops? See: https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/432

Great examples @maltenuhn. I would like to add another example where light dismiss boundaries are not clear. The gif below shows what happens to the github dropdown when screensize is changed from 'desktop' to 'mobile':

Question arises: does the mobile screen still fit the 'light dismiss criterium'?
Since it has a backdrop, the only way to build this dropdown, would be with a <dialog>, since
popups don't have backdrops? See: https://github.com/MicrosoftEdge/MSEdgeExplainers/issues/432

Thanks @erikkroes for opening this issue! Can you help me understand a little bit better what you'd hope the outcome of such an investigation would be? What would make your life easiest as a person who contributes to component libraries?

Let's try if I can say this in a short way, because I've been dreading a lengthy response 😄
We have a binary choice right now. Something is either modal, or not modal. I would be interested in more options to be defined, because this element sounds like neither (or both).
I think it would be interesting to have a spectrum of options with defined behaviors like aria-modal has.

Thanks folks for your feedback! I've been porting over issues to Open UI, where we are incubating the <popup> proposal. Closing this issue now, but please feel free to keep the discussion going on https://github.com/WICG/open-ui/issues/325.


Test in the meta.yaml that all installed python modules are available

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

I do not bump the build number or re-render as this only adds a test.

I do not bump the build number or re-render as this only adds a test.

This unfortunately means that the CI is not CI does build cleanly. Anyhow, it should be clean after https://github.com/conda-forge/bipedal-locomotion-framework-feedstock/pull/47 is merged.

Done in https://github.com/conda-forge/bipedal-locomotion-framework-feedstock/pull/50 .


File-scoped namespaces and other C#10 features support

https://docs.microsoft.com/en-us/dotnet/csharp/whats-new/csharp-10
Using some new C#10 features makes CodeNav disappear for now.

Grab the new release! 🚀

Now I use file-scoped namespaces everywhere ;)


How to initiate drag when finger begins to move from drag handle?

I could only imagine, shrinking the parent container so the handle reaches the father's edges faster. But if you could provide a demonstration in jsfiddle, we could fiddle around with it :)

@ChiefORZ I think getting this to work in a fiddle would be a major undertaking. Here is a Gist with my controller and template.
I noticed when I open example Codepen's using Sortable on my Android device they don't have the same drag behavior I'm seeing here. With them as soon as your finger moves on the drag handle the handle's parent follows immediately with no need to get to the edge of the parent first. There must be something I'm not configuring correctly.


Python2 installation issue with numdifftools

Probably not a astromodels issue, but with numdifftools:
$ python2 setup.py install --user

 Xspec is detected. Will compile the Xspec extension.

Found library XSFunctions in /home/user/bin/xspec/x86_64-unknown-linux-gnu-libc2.25/lib
Found library XSModel in /home/user/bin/xspec/x86_64-unknown-linux-gnu-libc2.25/lib
Found library XSUtil in /home/user/bin/xspec/x86_64-unknown-linux-gnu-libc2.25/lib
Found library XS in /home/user/bin/xspec/x86_64-unknown-linux-gnu-libc2.25/lib
Found library cfitsio in None
Found library CCfits_2.5 in /home/user/bin/xspec/x86_64-unknown-linux-gnu-libc2.25/lib
Found library wcs in None
Found library gfortran in None
running install
running bdist_egg
running egg_info
writing requirements to astromodels.egg-info/requires.txt
writing astromodels.egg-info/PKG-INFO
writing top-level names to astromodels.egg-info/top_level.txt
writing dependency_links to astromodels.egg-info/dependency_links.txt
package init file 'astromodels/tests/__init__.py' not found (or not a regular file)
reading manifest template 'MANIFEST.in'
writing manifest file 'astromodels.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
running build_ext
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/astromodels
creating build/bdist.linux-x86_64/egg/astromodels/xspec
creating build/bdist.linux-x86_64/egg/astromodels/xspec/include
creating build/bdist.linux-x86_64/egg/astromodels/xspec/include/sherpa
copying build/lib.linux-x86_64-2.7/astromodels/xspec/include/sherpa/fcmp.hh -> build/bdist.linux-x86_64/egg/astromodels/xspec/include/sherpa
copying build/lib.linux-x86_64-2.7/astromodels/xspec/include/sherpa/extension.hh -> build/bdist.linux-x86_64/egg/astromodels/xspec/include/sherpa
copying build/lib.linux-x86_64-2.7/astromodels/xspec/include/sherpa/constants.hh -> build/bdist.linux-x86_64/egg/astromodels/xspec/include/sherpa
creating build/bdist.linux-x86_64/egg/astromodels/xspec/include/sherpa/astro
copying build/lib.linux-x86_64-2.7/astromodels/xspec/include/sherpa/astro/xspec_extension.hh -> build/bdist.linux-x86_64/egg/astromodels/xspec/include/sherpa/astro
copying build/lib.linux-x86_64-2.7/astromodels/xspec/include/sherpa/array.hh -> build/bdist.linux-x86_64/egg/astromodels/xspec/include/sherpa
copying build/lib.linux-x86_64-2.7/astromodels/xspec/__init__.py -> build/bdist.linux-x86_64/egg/astromodels/xspec
copying build/lib.linux-x86_64-2.7/astromodels/xspec/factory.py -> build/bdist.linux-x86_64/egg/astromodels/xspec
copying build/lib.linux-x86_64-2.7/astromodels/xspec/xspec_settings.py -> build/bdist.linux-x86_64/egg/astromodels/xspec
copying build/lib.linux-x86_64-2.7/astromodels/xspec/_xspec.so -> build/bdist.linux-x86_64/egg/astromodels/xspec
copying build/lib.linux-x86_64-2.7/astromodels/xspec/README -> build/bdist.linux-x86_64/egg/astromodels/xspec
creating build/bdist.linux-x86_64/egg/astromodels/xspec/src
copying build/lib.linux-x86_64-2.7/astromodels/xspec/src/_xspec.cc -> build/bdist.linux-x86_64/egg/astromodels/xspec/src
copying build/lib.linux-x86_64-2.7/astromodels/xspec/LICENSE -> build/bdist.linux-x86_64/egg/astromodels/xspec
creating build/bdist.linux-x86_64/egg/astromodels/sources
copying build/lib.linux-x86_64-2.7/astromodels/sources/point_source.py -> build/bdist.linux-x86_64/egg/astromodels/sources
copying build/lib.linux-x86_64-2.7/astromodels/sources/__init__.py -> build/bdist.linux-x86_64/egg/astromodels/sources
copying build/lib.linux-x86_64-2.7/astromodels/sources/source.py -> build/bdist.linux-x86_64/egg/astromodels/sources
copying build/lib.linux-x86_64-2.7/astromodels/sources/extended_source.py -> build/bdist.linux-x86_64/egg/astromodels/sources
copying build/lib.linux-x86_64-2.7/astromodels/sources/particle_source.py -> build/bdist.linux-x86_64/egg/astromodels/sources
creating build/bdist.linux-x86_64/egg/astromodels/functions
copying build/lib.linux-x86_64-2.7/astromodels/functions/functions_3D.py -> build/bdist.linux-x86_64/egg/astromodels/functions
copying build/lib.linux-x86_64-2.7/astromodels/functions/functions_2D.py -> build/bdist.linux-x86_64/egg/astromodels/functions
copying build/lib.linux-x86_64-2.7/astromodels/functions/function.py -> build/bdist.linux-x86_64/egg/astromodels/functions
creating build/bdist.linux-x86_64/egg/astromodels/functions/dark_matter
copying build/lib.linux-x86_64-2.7/astromodels/functions/dark_matter/__init__.py -> build/bdist.linux-x86_64/egg/astromodels/functions/dark_matter
copying build/lib.linux-x86_64-2.7/astromodels/functions/dark_matter/dm_models.py -> build/bdist.linux-x86_64/egg/astromodels/functions/dark_matter
copying build/lib.linux-x86_64-2.7/astromodels/functions/__init__.py -> build/bdist.linux-x86_64/egg/astromodels/functions
copying build/lib.linux-x86_64-2.7/astromodels/functions/priors.py -> build/bdist.linux-x86_64/egg/astromodels/functions
copying build/lib.linux-x86_64-2.7/astromodels/functions/template_model.py -> build/bdist.linux-x86_64/egg/astromodels/functions
copying build/lib.linux-x86_64-2.7/astromodels/functions/functions.py -> build/bdist.linux-x86_64/egg/astromodels/functions
copying build/lib.linux-x86_64-2.7/astromodels/__init__.py -> build/bdist.linux-x86_64/egg/astromodels
creating build/bdist.linux-x86_64/egg/astromodels/data
creating build/bdist.linux-x86_64/egg/astromodels/data/dark_matter
copying build/lib.linux-x86_64-2.7/astromodels/data/dark_matter/gammamc_dif.dat -> build/bdist.linux-x86_64/egg/astromodels/data/dark_matter
copying build/lib.linux-x86_64-2.7/astromodels/data/dark_matter/dmSpecTab.npy -> build/bdist.linux-x86_64/egg/astromodels/data/dark_matter
creating build/bdist.linux-x86_64/egg/astromodels/data/tests
copying build/lib.linux-x86_64-2.7/astromodels/data/tests/test.yaml -> build/bdist.linux-x86_64/egg/astromodels/data/tests
copying build/lib.linux-x86_64-2.7/astromodels/data/tests/black_hole.yaml -> build/bdist.linux-x86_64/egg/astromodels/data/tests
copying build/lib.linux-x86_64-2.7/astromodels/data/tests/simple_source.yaml -> build/bdist.linux-x86_64/egg/astromodels/data/tests
copying build/lib.linux-x86_64-2.7/astromodels/version.py -> build/bdist.linux-x86_64/egg/astromodels
creating build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/configuration.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/angular_distance.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/vincenty.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/valid_variable.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/data_files.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/io.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/__init__.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/table.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/long_path_formatter.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/disk_usage.py -> build/bdist.linux-x86_64/egg/astromodels/utils
copying build/lib.linux-x86_64-2.7/astromodels/utils/pretty_list.py -> build/bdist.linux-x86_64/egg/astromodels/utils
creating build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/parameter_transformation.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/memoization.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/spectral_component.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/sky_direction.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/my_yaml.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/model_parser.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/node_ctype.so -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/units.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/tree.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/__init__.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/thread_safe_unit_format.py -> build/bdist.linux-x86_64/egg/astromodels/core
creating build/bdist.linux-x86_64/egg/astromodels/core/node_ctype
copying build/lib.linux-x86_64-2.7/astromodels/core/node_ctype/node_ctype.cxx -> build/bdist.linux-x86_64/egg/astromodels/core/node_ctype
copying build/lib.linux-x86_64-2.7/astromodels/core/serialization.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/polarization.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/parameter.py -> build/bdist.linux-x86_64/egg/astromodels/core
copying build/lib.linux-x86_64-2.7/astromodels/core/model.py -> build/bdist.linux-x86_64/egg/astromodels/core
creating build/bdist.linux-x86_64/egg/astromodels/tests
copying build/lib.linux-x86_64-2.7/astromodels/tests/test_functions.py -> build/bdist.linux-x86_64/egg/astromodels/tests
copying build/lib.linux-x86_64-2.7/astromodels/tests/test_tree.py -> build/bdist.linux-x86_64/egg/astromodels/tests
copying build/lib.linux-x86_64-2.7/astromodels/tests/test_memoizer.py -> build/bdist.linux-x86_64/egg/astromodels/tests
copying build/lib.linux-x86_64-2.7/astromodels/tests/test_load_xspec_models.py -> build/bdist.linux-x86_64/egg/astromodels/tests
copying build/lib.linux-x86_64-2.7/astromodels/tests/test_point_source.py -> build/bdist.linux-x86_64/egg/astromodels/tests
copying build/lib.linux-x86_64-2.7/astromodels/tests/test_parameter.py -> build/bdist.linux-x86_64/egg/astromodels/tests
copying build/lib.linux-x86_64-2.7/astromodels/tests/test_model.py -> build/bdist.linux-x86_64/egg/astromodels/tests
copying build/lib.linux-x86_64-2.7/astromodels/tests/test_template_model.py -> build/bdist.linux-x86_64/egg/astromodels/tests
byte-compiling build/bdist.linux-x86_64/egg/astromodels/xspec/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/xspec/factory.py to factory.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/xspec/xspec_settings.py to xspec_settings.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/sources/point_source.py to point_source.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/sources/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/sources/source.py to source.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/sources/extended_source.py to extended_source.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/sources/particle_source.py to particle_source.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/functions_3D.py to functions_3D.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/functions_2D.py to functions_2D.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/function.py to function.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/dark_matter/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/dark_matter/dm_models.py to dm_models.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/priors.py to priors.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/template_model.py to template_model.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/functions/functions.py to functions.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/version.py to version.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/configuration.py to configuration.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/angular_distance.py to angular_distance.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/vincenty.py to vincenty.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/valid_variable.py to valid_variable.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/data_files.py to data_files.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/io.py to io.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/table.py to table.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/long_path_formatter.py to long_path_formatter.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/disk_usage.py to disk_usage.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/utils/pretty_list.py to pretty_list.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/parameter_transformation.py to parameter_transformation.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/memoization.py to memoization.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/spectral_component.py to spectral_component.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/sky_direction.py to sky_direction.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/my_yaml.py to my_yaml.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/model_parser.py to model_parser.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/units.py to units.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/tree.py to tree.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/__init__.py to __init__.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/thread_safe_unit_format.py to thread_safe_unit_format.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/serialization.py to serialization.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/polarization.py to polarization.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/parameter.py to parameter.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/model.py to model.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/tests/test_functions.py to test_functions.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/tests/test_tree.py to test_tree.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/tests/test_memoizer.py to test_memoizer.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/tests/test_load_xspec_models.py to test_load_xspec_models.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/tests/test_point_source.py to test_point_source.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/tests/test_parameter.py to test_parameter.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/tests/test_model.py to test_model.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/tests/test_template_model.py to test_template_model.pyc
creating stub loader for astromodels/xspec/_xspec.so
creating stub loader for astromodels/core/node_ctype.so
byte-compiling build/bdist.linux-x86_64/egg/astromodels/xspec/_xspec.py to _xspec.pyc
byte-compiling build/bdist.linux-x86_64/egg/astromodels/core/node_ctype.py to node_ctype.pyc
installing package data to build/bdist.linux-x86_64/egg
running install_data
creating build/bdist.linux-x86_64/egg/astromodels/data/functions
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying astromodels.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying astromodels.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying astromodels.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying astromodels.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying astromodels.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
writing build/bdist.linux-x86_64/egg/EGG-INFO/native_libs.txt
zip_safe flag not set; analyzing archive contents...
creating 'dist/astromodels-0.5.1-py2.7-linux-x86_64.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing astromodels-0.5.1-py2.7-linux-x86_64.egg
Removing /mnt/data/daten/Master/home/.local/lib64/python2.7/site-packages/astromodels-0.5.1-py2.7-linux-x86_64.egg
Copying astromodels-0.5.1-py2.7-linux-x86_64.egg to /mnt/data/daten/Master/home/.local/lib64/python2.7/site-packages
astromodels 0.5.1 is already the active version in easy-install.pth

Installed /mnt/data/daten/Master/home/.local/lib64/python2.7/site-packages/astromodels-0.5.1-py2.7-linux-x86_64.egg
Processing dependencies for astromodels==0.5.1
Searching for numdifftools
Reading https://pypi.python.org/simple/numdifftools/
Downloading https://pypi.python.org/packages/70/25/1af07d513fc5fb60b80c4577971fdd3480f931291f783dde33de178b185f/numdifftools-0.9.20.tar.gz#md5=c0545b8d1d1b4cdd1d5dacd99ff42666
Best match: numdifftools 0.9.20
Processing numdifftools-0.9.20.tar.gz
Writing /tmp/easy_install-nJBrWo/numdifftools-0.9.20/setup.cfg
Running numdifftools-0.9.20/setup.py -q bdist_egg --dist-dir /tmp/easy_install-nJBrWo/numdifftools-0.9.20/egg-dist-tmp-X1wN3R
zip_safe flag not set; analyzing archive contents...

Installed /tmp/easy_install-nJBrWo/numdifftools-0.9.20/.eggs/pyscaffold-2.4.4-py2.7.egg
/usr/lib64/python2.7/site-packages/nose/plugins/manager.py:395: RuntimeWarning: Unable to load plugin answer-testing = yt.utilities.answer_testing.framework:AnswerTesting: super() argument 1 must be type, not None
  RuntimeWarning)
/usr/lib64/python2.7/site-packages/nose/plugins/manager.py:395: RuntimeWarning: Unable to load plugin tap = tap.plugin:TAP: (Pygments 2.2.0 (/usr/lib64/python2.7/site-packages), Requirement.parse('Pygments==2.0.1'))
  RuntimeWarning)
ERROR:root:Error parsing
Traceback (most recent call last):
  File "/usr/lib64/python2.7/site-packages/pbr/core.py", line 111, in pbr
    attrs = util.cfg_to_args(path, dist.script_args)
  File "/usr/lib64/python2.7/site-packages/pbr/util.py", line 267, in cfg_to_args
    wrap_commands(kwargs)
  File "/usr/lib64/python2.7/site-packages/pbr/util.py", line 569, in wrap_commands
    cmdclass = ep.resolve()
  File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 2428, in resolve
    module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib64/python2.7/site-packages/sphinx/setup_command.py", line 23, in <module>
    from sphinx.application import Sphinx
  File "/usr/lib64/python2.7/site-packages/sphinx/application.py", line 33, in <module>
    from sphinx.environment import BuildEnvironment
  File "/usr/lib64/python2.7/site-packages/sphinx/environment/__init__.py", line 45, in <module>
    from sphinx.util.websupport import is_commentable
  File "/usr/lib64/python2.7/site-packages/sphinx/util/websupport.py", line 11, in <module>
    from sphinxcontrib.websupport.utils import is_commentable  # NOQA
  File "/usr/lib64/python2.7/site-packages/sphinxcontrib/websupport/__init__.py", line 15, in <module>
    from sphinxcontrib.websupport.core import WebSupport  # NOQA
  File "/usr/lib64/python2.7/site-packages/sphinxcontrib/websupport/core.py", line 17, in <module>
    from jinja2 import Environment, FileSystemLoader
  File "/usr/lib64/python2.7/site-packages/jinja2/__init__.py", line 33, in <module>
    from jinja2.environment import Environment, Template
  File "/usr/lib64/python2.7/site-packages/jinja2/environment.py", line 15, in <module>
    from jinja2 import nodes
  File "/usr/lib64/python2.7/site-packages/jinja2/nodes.py", line 19, in <module>
    from jinja2.utils import Markup
  File "/usr/lib64/python2.7/site-packages/jinja2/utils.py", line 486, in <module>
    MutableMapping.register(LRUCache)
  File "/usr/lib/python-exec/python2.7/../../../lib64/python2.7/abc.py", line 109, in register
    if issubclass(subclass, cls):
  File "/usr/lib/python-exec/python2.7/../../../lib64/python2.7/abc.py", line 180, in __subclasscheck__
    if issubclass(subclass, scls):
  File "/usr/lib64/python2.7/site-packages/typing.py", line 1265, in __subclasscheck__
    return super(GenericMeta, self).__subclasscheck__(cls)
TypeError: super() argument 1 must be type, not None
error: Setup script exited with error in setup command: Error parsing /tmp/easy_install-nJBrWo/numdifftools-0.9.20/setup.cfg: TypeError: super() argument 1 must be type, not None

This was run on 33a71e1a6318e4191975e7ac228f0f9ac2d26524

Seems to be related: https://github.com/blue-yonder/pyscaffold/issues/136

Solved it by running
$ pip2 install . --user
and, before that, pip2 install pyscaffold==2.5.7 --user


Access or Roles requirement given to service account key for integration with DFCX #PermissionDenied #Roles

I got a service account key from my organization to make use of scrapi and automate some functionalities in DFCX like create bulk test cases and uploading intent with tp in bulk etc.
So the organization gave some access to that service account and when I use it to even read the agent using `get_agent()' it throws "PERMISSION DENIED" and basically says that my account doesn't have the right permission to perform this task without actually specifying which roles exactly.
I have less idea on what all roles/access the organization has given to the service account and I found no ways to find that unless I had access to IAM which I don't.
I would request to get clarity on what all roles does a service account need to perform basic functionalities like upload intents, create test cases etc.
I can see that in every example there is prerequisite to have "API admin role" assigned to the account but my organization can't provide me that access. So is that the issue or do we have some alternative roles that can compensate for it?
Please make use of this link https://cloud.google.com/dialogflow/cx/docs/concept/access-control
and state exact roles needed in a service account to perform basic functionalities in DFCX.

Hi @tima946 !
Authentication with Google APIs can be tricky at times, so I'll do my best to clarify a few scenarios below depending on how you are developing with the API.
Roles and Permissions
The IAM Roles required to make edits via the API contain the same underlying permissions that are granted to GCP principal accounts when editing via the UI/console. Depending on the tasks you want to accomplish via API, you will generally look to have 1 of these 3 roles granted:
TLDR: If you're planning on creating / updating resources, you need the Dialogflow API Admin role.

Dialogflow API Admin provides full read/write access via API. Note that if you are attempting to create new Intents, Pages, Flows, etc. using any create/update method, this is the only set of permissions that allows you to do so.
Dialogflow API Client provides the ability to hold a conversation with your agent. This essentially the same as using the "Simulator" in the UI/Console. This permission does not provide write access to Agent resources. You would only use this role if you're planning on testing out your agent by having a conversation via API. This could also be granted to any service account that was used for integration purposes. (i.e. Front End integration that needs to talk to the Dialogflow API back end.)
Dialogflow API Reader provides access to all GET methods from the API. If you're only planning on reading agent resources to see what they contain, this is the minimal permission needed to do so.

Authentication Without Service Account
It's possible to do things via the API without using a service account. However, you still need your principal GCP account to have the appropriate permissions to make changes via the API. This means you will need your IAM Administrator to assign one of the 3 Roles to your @yourcompany.com account OR you can have your IAM Administrator grant you a Basic GCP Role like "Editor". The easy way to know if you have the right access is this: If you can make edits and changes in the UI/Console with your principal account, you should be able to do the same via API using your principal account.
Google Colab Notebooks (.ipynb)
If you're using Google Colab notebooks for development, there's an easy way to test this out using the following code block.
# Install SCRAPI
!pip install dfcx-scrapi==1.5.1 --quiet

# Assign your GCP Project ID to a variable for us with the auth chain below
project_id = 'YOUR_GCP_PROJECT'

# this will launch an interactive prompt that allows you to auth with GCP in a browser
!gcloud auth application-default login --no-launch-browser

# this will set your active project to the `project_id` above
!gcloud auth application-default set-quota-project $project_id

# You can use SCRAPI now without passing in auth creds
# The Colab environment will grab them based on the above auth chain

from dfcx_scrapi.core.intents import Intents

i = Intents()
agent_id = 'your_agent_id'
intents_map = i.get_intents_map(agent_id)

Standard Python Environment (.py)
If you're working in an IDE like VS Code, you can perform the same auth chain above using gcloud commands. This will set an environment variable on your local machine that contains the authentication credentials that can be used with the API calls. Use the following code block from a local terminal (iTerm, VS Code Terminal, etc.) to set that up.
# Initialize gcloud if you haven't done this before
gcloud init

# Start the login process
gcloud auth login

# Check the auth list to see which user is currently logged in
gcloud auth list

# Set the GCP Project ID
gcloud config set project-id your_gcp_project_id

After doing the above auth chain, when you execute any .py script, it will attempt to use the environment credentials to pass to the API. You can test with this snippet of code in a .py file:
from dfcx_scrapi.core.intents import Intents

def get_intents_map(agent_id):
  i = Intents()
  intents_map = i.get_intents_map(agent_id)

  return intents_map

if __name__ == "__main__":
  agent_id = 'your_agent_id'
  intents_map = get_intents_map(agent_id)

  print(intents_map)

Summary
The key thing to remember is that no matter which method you choose to use from above, they will only work if either your Principal GCP Account or your Service Account has been granted the appropriate Roles / Permissions. If the default GCP Roles for Dialogflow are too broad, your IAM Administrator can choose to create a custom Role and assign individual permissions as needed.
Hope this helps.
I'll leave this Issue open for now to see if you have any other questions.

Closing issue based on previous answer.


Confidential signed

JIRA Link
Insert JIRA url here
Changelog / Description
Add description in points. Use bulleting/numbering to list the changes/features.
Checklist -

[ ] New Feature ?
[ ] Updated swagger annotation (if API structure is changed) ?
[ ] Unit Test (if possible) ?
[ ] Updated the Readme.md (if required) ?

When rebasing I had to resolve conflicts between SDK version + jenkins file + app module. This was after 100+ yubikey signatures.
Now the merge is blocked since the commits aren't the same :(

https://github.com/PolymeshAssociation/confidential-polymesh-rest-api/pull/5


No use to check OpBitCount result width

removed TODO

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

Fixes https://github.com/KhronosGroup/SPIRV-Tools/issues/843
(@jcaraban: If you write that "Fixes https://github.com/KhronosGroup/SPIRV-Tools/issues/843" in your commit message, then when the commit is merged it will close the issue.  That's usually what you want, i.e. when there is a one-to-one correspondence between issue and merge request.)


Unnecessary value assignment in BlinkyWebServerExample - WebServerTask.cs#113

Issue
There is maybe an unnecessary value assignment at the BlinkyWebServerExample.
Source
 public HttpServer(int serverPort, AppServiceConnection appServiceConnection)
 {
            listener = new StreamSocketListener();
            port = serverPort;
            appServiceConnection = appServiceConnection; //little bit confusing
            listener.ConnectionReceived += (s, e) => ProcessRequestAsync(e.Socket);
}

Links

Related file on Github
Related MSDN forum post

It is taking the variable passed in to the constructor and assigning to a private variable of the same name that's a class member.  It could be rewritten as
private AppServiceConnection appServiceConnection;

public HttpServer(int serverPort, AppServiceConnection randomVariable)
 {
        listener = new StreamSocketListener();
        port = serverPort;
        this.appServiceConnection = randomVariable;
        listener.ConnectionReceived += (s, e) => ProcessRequestAsync(e.Socket);
}

Ah, I see.
I would recommand that little refactoring. It would help beginners to understand the source without the question in mind "why does vs mark this yellow".

Agreed.  We have updated the sample to clarify this.  Thanks!

No problem. I'm glad I could help. :)


Bot api not making a request

When I made my rat, inserted bot id and chat id, also specified some parameters and collected.  After launching the bot, there was no reaction, I tried to restart it, but alas.  I think there is a problem with sending a request, there are no problems with the Internet connection
I am hope for your help

Hello! I can assume several reasons:

Incorrect input of botapi and chatid
You didn't write /start to the bot so that it could write back to you

You can create a test bot, create a build of your RAT, and send it to me. I'll try to find errors in the program.
Also, in order to speed up the search for errors , you can use x64dbg yourself to debug your build.

Thank for you answer, but alas, it's solutions not help for me.
Bot_id and chat_id was true, so I trying send requests to bot api across browser and it's worked.
In my opinion, problem in GetRequest function, she should return me std::string response, but when I make request, she return me null string ( . Possible it's problems this my OS - windows 7 ultimate. I will try make alternative solution for make request.
I did some code for a test, also I did a simple api with functions in your code (GetRequest and SendTextMessage), but they returned me null string:
`#include
#include
#include <Windows.h>
#include <WinInet.h>
#pragma comment(lib, "WinInet.lib")
class TeleBot {
public:
TeleBot(std::string botid, std::string chatid) {
this->bot_id = botid;
this->chat_id = chatid;
}
std::string GetRequest(const char* url, const char* useragent, const char* path, const char* ContentType) {
	InternetSetOption(0, 42, NULL, 0);

	HINTERNET hSocket = InternetOpenA(useragent, INTERNET_OPEN_TYPE_PRECONFIG, NULL, NULL, NULL);

	if (hSocket != NULL) {
		HINTERNET hConnection = InternetConnectA(hSocket, url, INTERNET_DEFAULT_HTTPS_PORT, NULL, NULL, INTERNET_SERVICE_HTTP, 0, 1);

		if (hConnection != NULL) {
			HINTERNET hRequest;

			if (path == "") hRequest = HttpOpenRequestA(hConnection, "GET", NULL, NULL, NULL, 0, INTERNET_FLAG_RELOAD | INTERNET_FLAG_SECURE, 1);
			else hRequest = HttpOpenRequestA(hConnection, "GET", path, NULL, NULL, 0, INTERNET_FLAG_RELOAD | INTERNET_FLAG_SECURE, 1);

			if (hRequest != NULL) {
				if (ContentType == "") HttpSendRequestA(hRequest, NULL, 0, NULL, 0);
				else HttpSendRequestA(hRequest, ContentType, sizeof(ContentType), NULL, NULL);

				std::string resultRss;
				BYTE _DATA_RECIEVED[1024];
				DWORD NO_BYTES_READ = 0;
				while (InternetReadFile(hRequest, _DATA_RECIEVED, 1024, &NO_BYTES_READ) && NO_BYTES_READ > 0) {
					resultRss.append((char*)_DATA_RECIEVED, NO_BYTES_READ);
				}

				return resultRss;
			}
			InternetCloseHandle(hRequest);
		}
		InternetCloseHandle(hConnection);
	}
	InternetCloseHandle(hSocket);

	return "";
}

std::string SendTextMessage(std::string message) {
	std::string path = "bot" + bot_id + "/sendMessage?text=" + message + "&chat_id=" + chat_id;

	std::string req = GetRequest("api.telegram.org", "User-Agent: Mozilla / 5.0\r\n", path.c_str(), "*/*");
	return req;
}

private:
std::string bot_id, chat_id;
};
int main() {
TeleBot bot("some bot_id", "some chat_id");
std::string conn = bot.SendTextMessage("test");
std::cout << conn << std::endl;
std::string test_req = bot.GetRequest("google.com", "User-Agent: Mozilla / 5.0\r\n", "", "*/*");
std::cout << test_req << std::endl;
return 0;

}`

Try checking whether the request is sent via HTTP Analyzer\Debugger. If it is sent, then check the result. If it is not sent , you will need to debug the program to get GetLastError().

Ok thank you, I'll try

Hello! I'm cheked requests in wireshark and I don't find request to telegram api
Example sreenshots:

Use HTTP Debugger.


Bumped marked version #14

Re: https://nodesecurity.io/advisories/marked_redos

Tests failed :(

Looks like it's that regex security fix in play, and update requires code changes.
Then I'm out of my waters here.

I looked more precise at failing test and understood that I can not update marked to 0.3.4 or later, because this update will break correct test, more details can be found in an issue.

Cool. Thanks.


bump up to mcloud 1.8 with Android 12 support

https://github.com/zebrunner/mcloud/pull/109

done

verified on prod


[Feature] Adding support to ItemsAdder

Pre-Request Checklist

[x] I have checked that I am on the latest version of Terra.
[x] I have searched github for similar features requests, including closed
ones, and found none.
[x] I believe this is within the scope of Terra.
[x] This feature request is for all of Terra, and isn't something that
should be implemented by a pack or addon.

Feature Description
Adding support for ItemsAdder ores into Terra Worlds

What Problem Does This Solve?
When I try to add custom ores into my world using terra generator/world, It realy annoys me that I have to either manually place the ores or have to use world edit to add the ores and even those solutions aren't that great/work well.

A Solution You'd Like
Being able to add itemsadder:<ore_name> to the world files so the ores would be automatically generated there like on other inferior generators

Alternative Solutions

Manually replacing, takes too much time and isn't efficient for an entire world
Using world edit to replaceall, to resource heavy and doesn't even work well/work at all sometimes

Additonal Context

This is something that would be added by an addon and not included within Terra itself.


Cannot read property 'getPooled' of null at Object.componentDidMount

I've been using react-konva fine in another project, however after creating a new project, installing react-konva and trying to render a <Stage>, the above error appears in the Chrome debugger. It traces back to var transaction = ReactUpdates.ReactReconcileTransaction.getPooled(); in react-konva.js, which then seems to trace to
var ReactUpdates = {
  /**
   * React references `ReactReconcileTransaction` using this property in order
   * to allow dependency injection.
   *
   * @internal
   */
  ReactReconcileTransaction: null,

  ...etc etc
};

Any ideas what the issue could be? (Obviously, react-konva is referencing a null property...but why? Or am I misreading the issue? I'm using react-konva v 1.1.4 and react-dom v 15.5.4

No idea why, but the trouble code was in my webpack.config.js
externals: {
    "react": "React",
    "react-dom": "ReactDOM",
    "canvas": "canvas"
},

All needed to be disabled


IViewService after login CurrentUser is null and IsAuthenticated = false

Hi,
Based on the sample provided, I have implemented in my solution the "CustomViewService" (IViewService), which load automatically login, logout etc.. that works perfectly!
However when I have created another Controller (to update user name for example), when I login and then go to that new page, the issue is that I'm losing any info regarding the login (IsAuthenticated = false) and even when I'm adding the [Authorize] above my controller I can't access the page..
And also, User.GetUserID() is giving error..
Could you please give some lead, maybe I'm missing something..
Thanks in advance

You need to check the authenticated user via the OWIN environment extensions exposed from IdSvr.


Open file upload images inline even when there's no file name with an extension.

Will need to check the mime type in the entities list for the URL.

The app already does this, do you have an example URL that's not working?

https://usercontent.irccloud-cdn.com/file/Csth0eik/


Fix numpy pinning

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Fixes https://github.com/MDAnalysis/mdanalysis/issues/3660
Remove numpy > 1.18.0 specification. This causes conda-smithy to remove the numpy pinning from the build, resulting in a build against the latest numpy ABI. After this change, conda-smith rerenders the build with the proper pinning.

Hi! This is the friendly automated conda-forge-linting service.
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.

Thanks for this PR, I'm not sure removing the 1.18.0 spec is the right way to go here, I'm planning to experiment on this further later today.

Thanks for this PR, I'm not sure removing the 1.18.0 spec is the right way to go here, I'm planning to experiment on this further later today.

Alright. The conda-forge gitter channel is a good resource for help sorting out pinning issues.

@conda-forge-admin, please rerender

@conda-forge-admin, please restart ci


HREDQS running in bidirectional mode raises error

HREDQS when running in bidirectional mode, raises the following error:
File "../lib/cair_seq2seq_hredqs_acg\neuroir\decoders\decoder.py", line 167, in _fix_enc_hidden
hidden = torch.cat([hidden[0:hidden.size(0):2],
same place as the issue# 10

This is due to the latest version of PyTorch. The solution is given below.
Set bidirection=False in this line.
self.decoder = Decoder(rnn_type=args.rnn_type,
                       input_size=self.embedder.output_size,
                       bidirection=args.bidirection, # this is wrong
                       nlayers=1,
                       nhid=args.nhid_decoder,
                       attn_type=args.attn_type,
                       dropout_rnn=args.dropout_rnn,
                       copy_attn=False,
                       reuse_copy_attn=False)

Thanks for the hint. I do your suggestion in https://github.com/wasiahmad/context_attentive_ir/blob/master/neuroir/hyparam.py#L125 and change the line to 'bidirection': False,


If a bot is connected to a skill, then export as a skill should be grayed out
If a bot has allowed callers configured then it is assumed to be a skill and Connect to a skill should be grayed out

We will not be addressing this at the moment.


openssl.exe has security vulnerability

This issue has been moved from a ticket on Developer Community.

Our corporate security PC has scanned my PC with the latest version of VC2019 on and reported that C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Extensions\Microsoft\Python\Miniconda\Miniconda3-x64\Library\bin\openssl.exe has a security vulnerability. I checked and it is version 1.1.1c. They say it should be upgraded to at lease 1.1.1l. Can you please arrange for this to be upgraded in a release?

Original Comments
(no comments)

Original Solutions
(no solutions)

Graham's released statement says we're not fixing old versions of the Python Interpreter, the users need to move up to a more recent version of VS. That being said, the MiniConda component isn't the same as the CPython interpreter, and this is a real security vulnerability, so we might have to fix it. Follow up with Graham for guidance.

Going to close this out as the VS2019 bundled miniconda is labeled as out-of-support so we are not providing full support on security updates.


CDS-82301 GitOps Agent HA

https://harness.atlassian.net/browse/CDS-82301
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[x ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

https://harness.atlassian.net/browse/CDS-82301

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


[Feature] Trigger new builds only upon commits to certain folders within repo

What App Center service does this feature apply to?
This is a feature for git/GitHub integration that would provide more flexibility in build-trigger configurations. I would consider it to be a standard CI feature but apparently App Center is still missing its implementation.
Describe the solution you'd like
When adding an integration to a repository, it should be possible to specify the updates in which folders within the repository should trigger a new build and which not. The configuration should be done in a form of a white-list/black-list (include/exclude) filled with comma-separated folder names. Wild-cards (*) should be available as well.
For every code commit to the build repository, the system would check if there is at least one file from a white-listed folder or at least one file that is not from a black-listed folder. If such a file found, the new build will be started; otherwise the code commit would be ignored as irrelevant to the binary.
Describe alternatives you've considered
Alternative solution would be to separate the code into two repositories--one for the build and one for auxiliary materials--but that introduces additional maintenance overhead. Current setup triggers a new build for every documentation update within the repo, which can potentially cause a queue of useless builds and slow down the development process.
Additional context

Thanks for the feature request! Path filters are something we use ourselves on a daily basis. We'll continue to track interest on this one.

I understand that the feature is quite clear and there is not much to discuss about it, but closing it due to inactivity sounds like a wrong call to me. I'd rather have it implemented. 😉

@vpavlushkov Thanks for reminding us about this. While this is currently not on our immediate roadmap, how important is a fully customizable path filter setting for the build configuration to you, rather than say - a pre-defined path filter based on the folder in your repository where we found your project?

@ranterle "importance" is a relative term. 😉
We can certainly survive without that feature as it only causes extra build time but no real harm. Even if App Center starts a build which is totally redundant, one can cancel it manually. Hence, I'd say it is "nice to have" feature. However, I am so used to have this feature in different CI servers that not having this basic feature is odd.
I would also presume the complexity of implementing this feature is pretty small. Why would not we add it to the queue, without adding it to a certain milestone? Then somebody could pick it up while being free between bigger tasks.

Agree, this can definitely be improved so we are better supporting mono repo scenarios etc.
In terms of putting this on the roadmap there is definitely multiple factors that we look for, effort required is one thing, but also customer interest in general and how the solution we can think of plays with other items on our roadmap and our existing feature set.
It'd be great to get more clarity on the feature set you all would like to see us support. To get a better understanding of this (of course, not making any promises about an ETA or exact feature set):

React with 🎉if you would be happy with a solution where we allow you to restrict builds to only be triggered when a commit is within the path of the project that we found in your repo,
React with 🚀 if you need an option to configure path filters matching certain patterns, i.e. using wildcards, per build configuration

We have iOS, Android, and documentation all in one repo. Kicking off multiple builds for a README.md seems wasteful and noisy. We could split the repo into 3, but that adds a bit more project-mgmt overhead.

Hi, on a similar note I've just opened an Issue here: https://github.com/microsoft/appcenter/issues/930
This issue makes me think about the situation from a different angle though. It would be amazing if I could specify that only changes to the android/* or ios/* for example would trigger a native build. If my JS changes I already have CI set up which triggers a codepush rollout.
Will be keen to track this one.

We have iOS, Android, and documentation all in one repo. Kicking off multiple builds for a README.md seems wasteful and noisy. We could split the repo into 3, but that adds a bit more project-mgmt overhead.

Agree with this. This is the norm with React Native projects especially and I know lots of orgs who are moving towards monorepos so this would be a huge win for users who fit those use-cases.

React with 🎉if you would be happy with a solution where we allow you to restrict builds to only be triggered when a commit is within the path of the project that we found in your repo,

About this, we have a Xamarin solution where we have an Android project, an iOS project and a Shared project. If any files in Shared change, I want both Android and iOS to be built. So it's much better if I can manually specify the paths to be watched for changes that trigger a build.

Would still love to see this in December 2020


Smallcaps doesn't work with non-English characters

Asciidoctor PDF seems to ignore non-English characters when transforming a string to small caps.
At first I thought it was just accents, but I decided to check with Greek characters as well just to see, and they don't get the expected small caps treatment either.

Here's the relevant text in my .adoc file:
== Compétences Δενδρων Έϊϋόύώ

And the theme file:
heading-h2:
  text-transform: smallcaps

Compare this to MS Word's treatment:

Suggestion:
Use built-in Unicode functions to find and transform lowercase characters to their uppercase counterparts.
I've not looked at the code, I haven't learned any Ruby, but I know that most programming languages have Unicode support.
Environment:
asciidoctor-pdf -v
Asciidoctor PDF 2.3.10 using Asciidoctor 2.0.20 [https://asciidoctor.org]
Runtime Environment (ruby 3.1.3p185 (2022-11-24 revision 1a6b16756e) [x64-mingw-ucrt]) (lc:IBM437 fs:UTF-8 in:UTF-8 ex:UTF-8)

I've done what I'm willing to do, and what is reasonably supported by the built-in fonts. See https://github.com/asciidoctor/asciidoctor-pdf/issues/1192#issuecomment-1116710989 If you would like to see the smallcaps mapping extended to include support for other character sets, it's something you will need to contribute (with tests).

Use built-in Unicode functions to find and transform lowercase characters to their uppercase counterparts.

It's not as simple as this. They're all uppercase characters, but from different parts of the Unicode plane. What you're looking for are smallcap uppercase counterparts, which is not something that Ruby's stdlib provides (and not well-defined in Unicode either).
Currently, Asciidoctor PDF maintains a mapping for a-z, and some of those characters were carefully chosen to increase the likeliness it is found in the font. It's just not a simple matter.
If you'd like to enhance Asciidoctor PDF's behavior to add additional mappings, you can do so by overriding the smallcaps_pcdata in an extended converter. For example:
class MyPDFConverter < (Asciidoctor::Converter.for 'pdf')
  register_for 'pdf'

  def smallcaps_pcdata string
    super.sub 'é', %(\u1d07\u0301)
  end
end

However, you need to use a font that supports the combining characters like the combining acute accent. The built-in fonts don't include those. However, I could perhaps add them at some point.
If you need more assistance or ideas, please ask in the project chat at https://chat.asciidoctor.org.

I'm not invested enough to learn Ruby and all the required libraries just to fix this.  I was curious, however, and had a peek and the code.  It looks like you're using small caps in the font.  I'm not sure how widely implemented that is across different fonts, but regardless, it seems that the available unicode codepoints for those small caps are also anglocentric.
I suspect a more universal implementation of small caps would be font-independant, but still use unicode features to determine and transform casing.
Roughly, I picture a solution to look like:

Iterate through the text that should be in smallcaps

If the character is a lowercase letter (c.is_lowercase() or something similar), then find it's uppercase counterpart (c.to_uppercase() or something similar), and render it with a with the current font style but at a reduced size (e.g. 1ex of the current font size).
If the character is a "combining diacritic mark" (a.k.a. accents), look ahead one character:

If that look ahead character is lowercase, render the current character (the accent) at a reduced size,
otherwise render the current character (the accent) at the normal size.

Otherwise, render it without further transformation.

In theory, this should transform any script that distinguishes between upper- and lower-case, account for diacritic marks (a.k.a. accents) that are separate from their letters, and leave characters that have no lowercase counterparts unchanged.  There may be some special cases I've not considered, but at least it's a start.
Again, I'm not really invested in this.  I just ended up removing smallcaps from the template I was using it in.
However, the current implementation of smallcaps is buggy, and in the interest of improving this project, I suggest leaving this issue open until someone comes in to fix it.  That may be you, maybe a future version of me that really wants this, maybe someone else entirely.

No, the current implementation is not buggy. It works exactly how it's designed to work and is thoroughly tested. (I'm happy to add a note to the documentation to make it clear which character ranges this transformation supports). Making an accusation that it's buggy is not they way to get what you want. It's true that the implementation of smallcaps in Asciidoctor PDF is ASCII-centric. And I've made the argument that it's because the smallcaps transformation is, itself, ASCII-centric. I know of no official mapping in Unicode outside of A-Z that actually describes how uppercase characters are mapped to x-height equivalents (small capitals). If there is one, you can point me to it. (Other software may provide bespoke behavior*, but that doesn't make what Asciidoctor PDF does incorrect).
Regardless, that still doesn't settle the fact that most fonts, including the bundled ones, don't provide glyphs of non-ASCII x-height uppercase characters (which typically require a second code point, as described above). So all the user would end up getting beyond the ASCII characters are missing glyph boxes anyway.

find it's uppercase counterpart (c.to_uppercase() or something similar), and render it with a with the current font style but at a reduced size (e.g. 1ex of the current font size).

This is bespoke behavior, not the smallcaps transformation. I've already explained how it is that you can add this bespoke behavior using an extended converter. (Alternately, you could apply a custom role in the AsciiDoc source itself to reduce the font size of select characters). If you're unwilling or unable to implement that bespoke behavior, that is not my responsibility as a maintainer.
Since I've explained that there's no other definition of smallcaps than the one used, I don't have any plans to pursue a change. And you, by your own admission, are not invested in this. Therefore, I will not keep this issue open. (I have, however, elaborated the documentation as promised, see https://docs.asciidoctor.org/pdf-converter/latest/theme/text/#transform).

I realized that it's possible to call .unicode_normalize :nfd to rewrite a string so all characters with diacritical marks are written using a combining character. If we then add those combining characters to the bundled fonts, then the smallcaps transformation will automatically start working for words that use characters with diacritical marks (since the ASCII letter to transform as been split out in the string). Given this is a breaking change, it will need to be made in Asciidoctor PDF 3. However, I'm still going to add the combining characters to the bundled fonts in 2.3.x.


no such table: udger_datacenter_range

How to create a table udger_ datacenter_ range

Hi yann-y, you're running the server, right? There you need a version of the udger database: https://udger.com/
It's not documented, so apologies for that. However, I think the rest should still work - just without data center information.

Hi,How to solve this problem？

You also need to have the honeypot component running, with a public IP address and wired up to the same database. The honeypot will save peers to hole punch in the database 👍


Mesh3D.edges_satisfying inconsistent

from docs.examples.ex21 import m

m.nodes_satisfying(lambda x: x[2] == 0.)
m.elements_satisfying(lambda x: x[2] == 0.)
m.facets_satisfying(lambda x: x[2] == 0.)

but
m.edges_satisfying(lambda x: x[2] == 0.)

raises
TypeError: <lambda>() takes 1 positional argument but 3 were given

This might have been a missed part of #51.


Add like/follow/unfollow counter to inherited from API methods

rewrite
bot.follow()
bot.like()
....
to count follows/likes/etc.

Done at <IP_ADDRESS>


ci(scorecards-analysis): 🧑⚕ add OSSF Scorecards analysis workflow

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1125

Relevant Lines:
1125

💛  - Coveralls


Make the service opt-in

I do not want this bot spamming my projects. I did not sign up for this. For some reason I cannot even block @dependabot.
This "service" needs to be opt-in and not on by default.
Please stop spamming my projects.

Agree. Disable by default.

Also getting spammed. I have Dependabot alerts and security updates disabled in https://github.com/settings/security_analysis and in the individual repository and I'm still getting messages. Really quite annoying.

Also getting spammed. I have Dependabot alerts and security updates disabled in https://github.com/settings/security_analysis and in the individual repository and I'm still getting messages. Really quite annoying.

It's absurd that Github allows this @dependabot user to spam across the platform without penalty. Absolutely ridiculous.
@nfin8x @feelepxyz any updates here?

It's absurd that Github allows this @dependabot user to spam across the platform without penalty. Absolutely ridiculous.
@nfin8x @feelepxyz any updates here?

??????????????

??????????????

After having disabled dependabot on all of my projects, I still get PRs from it. Guess I can only half solve this by adding the spamming emails to my spam folder..

Do you have a repo name where you've seen this behaviour after disabling?
For organisations you'll want to go the settings > Security & Analysis and Disable all under Dependabot security updates:

For personal repos you can disable all from the same page:

Hi,
Thanks for contacting me - that was quite unexpected! I have a repo called bucket-list where this is the case.
Best regards
Frederik Winther
Den 14. apr. 2021 kl. 15.51 skrev Philip Harrison @.***>:

Do you have a repo name where you've seen this behaviour after disabling?
For organisations you'll want to go the settings > Security & Analysis and Disable all under Dependabot security updates:
[Screenshot 2021-04-14 at 14 47 55]https://user-images.githubusercontent.com/20165/114721013-6b5a4080-9d30-11eb-90b5-eea74c4cc262.png
For personal repos you can disable all from the same page:
[Screenshot 2021-04-14 at 14 47 45]https://user-images.githubusercontent.com/20165/114721030-6dbc9a80-9d30-11eb-821f-bbe63395bc82.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/dependabot/dependabot-core/issues/2097#issuecomment-819534213, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEF3DZYHY5E7LEKUQIR23GTTIWMVVANCNFSM4OLVWDIQ.

@wintheer it looks like the config file is still in the repo, if you delete this you should be good to go: https://admin.github.com/wintheer/bucket-list/blob/master/.github/dependabot.yml (the UI only disables Dependabot Security Updates, that trigger in response to Dependabot Alerts, whereas the config file controls Version Updates which update dependencies to  the latest version on a schedule).

@feelepxyz, thank you so much. So after all it was my own mistake, doh!

I'm unclear if this ticket originated from a fork or from when we used to auto-enable security updates on new repos.
Since it was filed we've:

Changed the security updates to not enabled by default
Default disabled Dependabot for forks: https://github.com/dependabot/dependabot-core/issues/2804

So going forward, no repos should be default opted-in.
Repos that were already opted in will require manual disabling... we considered disabling them, but couldn't easily distinguish between those who did/didn't manually enable it from the beginning, so it was safer/more predictable for users if we left them untouched.
Note also that repos will be automatically opted in if you've selected the Automatically enable for new repositories option in your user or org settings. But that's essentially inheriting a manual opt-in.

I have very many repos. Is there a way to disable it across my account entirely?


Fix Kotlin idioms in MockResponse. Headers and Trailers should be vals.

Also track OkHttp 3.14.x in KotlinSourceCompatibilityTest. This shouldn't
have been updated to use new APIs.

Is this PR for 3.14.x branch or master? 👀

PR is for master, KotlinSourceCompatibilityTest works on 3.14.x APIs and today’s.


Example intg_xeon_nlb instantiation error.

Hey,
I've been trying to run the intg_xeon_nlb example shipped with the opae-sdk. During the 'make sim' command I came across three errors all of which were instantiation errors stating that the respective design units were not found.
I have attached a screenshot of my error.
Thank you.
https://user-images.githubusercontent.com/37444395/61383284-01e39e80-a8cc-11e9-8de8-bd63be02b28c.png

Sorry, I keep trying to get some of those ancient samples deleted. For reasons I don't completely understand they keep being resurrected.
I assume you are just looking for sample workloads to get started. Please use the tutorial at https://github.com/OPAE/intel-fpga-bbb/tree/master/samples.


Update command of Liquibase version > 4.20.0 not working with change log table name other than DATABASECHANGELOG

Search first

[X] I searched and no similar issues were found

Description
We operate multiple application in a single database. The database is upgraded using Liquibase with each application having it's own change log table.
Starting with Liquibase version > 4.20.0, the update command is no longer working with change log table name other than DATABASECHANGELOG.
The update command does ignore the parameter databaseChangeLogTableName or the environment variable LIQUIBASE_CHANGELOG_TABLENAME.
Steps To Reproduce

Apply database changes using Liquibase's update command with parameter databaseChangeLogTableName or environment variable LIQUIBASE_CHANGELOG_TABLENAME. Use Liquibase version 4.20.0
Upgrade Liquibase to a version > 4.20.0 (for example 4.21.1 or 4.23.0)
Run another update command with the new Liquibase version

After the upgrade of the Liquibase version, the parameter databaseChangeLogTableName is ignored, and the change log is verified against/written to the default change log table DATABASECHANGELOG.

Liquibase Version
4.21.1
Database Vendor & Version
PostgreSQL 14.5
Liquibase Integration
CLI
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

@bwonisch - I'm checking back to see if the information provided by @wwillard7800 addressed your issue. Please let us know when you get a chance. Thanks!


Adapts documentation for Pekko

There are still some more references/links to Lightbend/Akka that need to be re-worked.
We're also missing some sample projects:

https://github.com/akka/akka-sample-cluster-kubernetes-java
https://github.com/akka/akka-sample-cluster-kubernetes-dns-java

We might to incorporate them into https://github.com/apache/incubator-pekko-samples

With the 2 extra Akka repos: that code is not Business Software Licensed. If someone volunteers to produce Pekko equivalents, they could use their own non-Apache forks. Alternatively, we could create Pekko repos when a volunteer pops up.
For now, we could just document that those Akka-based samples are still useful for learning - that anything learned from them is still valid with Pekko (users just need to migrate their code to use Pekko libs instead).