Rails_Admin, Sorcery + CanCanCan

Hello, When I use Sorcery with CanCanCan gem I had a had a mistake "You are not authorized", but my user had all abilities to manage all, for a few days. To fix this error I add config.current_user_method(&:current_user), like in Devise gem... So I think you should add this in Wiki

Can you update https://github.com/sferik/rails_admin/wiki/Sorcery if needed?
Thanks.


Multiline textfield does not support text color change

I have noticed that when I use a multiline textfield that I cannot change the color of the text. If I use the same textfield, but remove the properties for the row and multiline the text color changes correctly. Please let me know if there is a fix for this as it breaks the style of the recent thing I was working on. I have posted an open issue on stackoverflow here: https://stackoverflow.com/questions/44440163/material-ui-doesnt-support-colored-text-on-multiline-textfield-react where you can see the issue in more depth. I believe that on an earlier version of material-ui someone else opened the issue and it was closed as resolved, but at least on this version (v0.18.2) this is still broken.

We have been porting the component on the next branch. We reimplemented it from the ground-up. While we haven't tested it, I think that the issue is most likely fixed on that branch. Hence, I'm closing it.


New package: 1ICB.V.BPMN-RPAStudio version 27.0.0

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@SpecterShell - seems you're the latest contributor to  1IC.BPMN-RPAStudio
Do you know if this is a separate package? Can you review this one?

Should be the same package. The 1ICB.V from 1ICB.V.BPMN-RPAStudio is the full name of the publisher.
The manifests for this MSI installer was available here before it was removed in https://github.com/microsoft/winget-pkgs/pull/133698/files

URL: https://1ic.nl/BPMN_RPA/BPMN-RPA Studio.msi
Status Code: 200
(Automated message - build 788)


Issue with wrong redirect_uri for SSO

We were using amundsen frontend with flaskoidc with okta as auth layer wrapper.
This is our Architecture (Mounted on Azure):
Browser(Client) --(HTTPS)--> Azure AppGateway ----(HTTPS)--> Nginx Ingress Controller --(HTTP, port:5000)--> Amundsen-Frontend-Service
In our case is very similar to issue #594 because flask_oidc was detecting the wrong redirect_uri
(Identity Provider: Unknown Error Code: invalid_request
Description: The 'redirect_uri' parameter [http://subdomain.domain.com/oidc_callback] must be an absolute URI whitelisted in the client app settings: https://dev-xxxxxxxx-admin.okta.com/admin/app/oidc_client/instance/xxxxxxxxxxxxxxxxx#tab-general )
URL Whitelisted: https://subdomain.domain.com/oidc_callback
Also when we hardcode it (adding https) starting show an Internal Server Error 500 on the amundsen application.
Expected Behavior
redirect uri comes correctly on "Location" header with "https" scheme
Current Behavior
redirect_uri comes incorrectly on "Location" header with http. If we hardcoded it(force to use https), shows an Internal Server Error 500
Possible Solution
N/A
Steps to Reproduce
Deploy App on K8s and expose the service.
Screenshots
Context
Unable to use SSO for Amundsen app
Your Environment

Amunsen version used:

dockerimages :
amundsendev/amundsen-search:2.0.0
amundsendev/amundsen-metadata:2.0.0
amundsendev/amundsen-frontend-oidc:2.2.0
Deployment: k8s behind Nginx ingress and AzureAppGw:
Browser(Client) --(HTTPS)--> Azure AppGateway ----(HTTPS)--> Nginx Ingress Controller --(HTTP, port:5000)--> Amundsen-Frontend-Service

Hi team, I close this issue, we found that flaskoidc has an error on the config file. Right now is working with Okta.

@dalbaradoey How did you fix this? We're experiencing issues with creating a user profile with Okta through the get_user_details method which we passed in through the metadata config.


Remove dependacies to system service (on messaging & crm)

There are two dependencies open:

User,
Rules

I'm fine with keeping those, as they are now limited in scope due to #99 stage 1 implementation. The surface of system/service is now significantly reduced.


Refactor: Make library web3/ethers agnostic and require a EIP1193 provider

This PR:

refactors the library to be web3/ethers agnostic by requiring a provider implementing EIP-1193 interface

Notable changes:

It doesn't checksum the returned address anymore. We could implement checksumming, but usually, the libraries for web3 interaction, such as ethers or web3 implement them already so the library consumer could reuse them

Blockers:

https://github.com/ethers-io/ethers.js/pull/3166

@jfschwarz done. web3.js is a little trickier


INTF Change abap language version description

well, the JSONs are auto generated, so the change should be done in https://github.com/SAP/abap-file-formats/blob/main/file-formats/zif_aff_types_v1.intf.abap#L14 ?
if/when we get the automation running, it should be able to catch and add a warning in the PR if files are not in sync


Port all components to v0.5.0

All components inside the components/ folder in Tafel should be brought up to date, and moved to the new package structure, along with its unit tests.
The list below is incomplete, so please edit this comment w/ additional components.

[x] Banner
[x] Board
[x] EmptyMessage
[x] Button
[x] Card
[x] Loading
[x] Support Button
[x] Floating Button
[x] Toggle Button
[x] Badge
[x] Drawer
[x] Form

[x] Input (text, radio, textarea)
[x] Select (use react-select v2)
[x] Form Container

[x] Dropdown

[x] Dropdown Item
[x] Dropdown menu
[x] Dropdown Selector
[x] Dropdown Toggle

[x] Layout (Sidebar, Wrapper, Content)
[x] Modal
[x] Pagination
[x] Split Button
[x] Tooltip

This is all finished, so we can close this. We'll tackle InputSelect in a future release.


How can I use the methods like clearInput?

I am a new user and trying to clear the input value after selecting result. I am trying these codes
`
    <button type="button" class="btn btn-success ml-2 width-xs"  @click="add"><i class="las la-check-double"></i></button>
</div>

`
Can anyone help me to understand the usease of the methods, please?

I fixed it. It wasn't running because I tried it on version 1.0.5. I updated the version and it is now working fine!


Preventing state reload on URL change

I currently use the following code to prevent my route, and therefore controller, being reloaded when I update the $location:
angular.module('Shared').service('location', function($location, $route, $rootScope) {
  $location.skipReload = function () {
    var lastRoute = $route.current;
    var un = $rootScope.$on('$locationChangeSuccess', function () {
        $route.current = lastRoute;
        un();
    });
    return $location;
  };
  return $location;
});

along with:
location.skipReload().path("/newpath").replace();

Can I achieve the same behaviour with ui-router?
I tried simply replacing $route above with $state but this still resulted in a state change. My use case is I only have 'new' and 'edit' states which are exactly the same, when a user saves within the 'new' state I want to update the URL to include the saved id but not reload the view.

@intellix Did you ever find anything out about this issue? I for the life of me can't figure out a way around this.

@roryf, your decorator worked perfectly for me. So far it was the cleanest solution I could find, thank you!

@roryf thanks for the decorator. This is fixed version that uses $delegate:
locationDecorator = ($delegate, $rootScope) ->
  skipping = false

  $rootScope.$on '$locationChangeSuccess', (event) ->
    if skipping
      event.preventDefault()
      skipping = false

  $delegate.skipReload = ->
    skipping = true
    return this

  return $delegate

mod.config ($provide) ->
  $provide.decorator('$location', locationDecorator)

@roryf, thanks for your decorator solution! I can confirm it works with ui-router 0.2.13 and angular 1.2.14.

This seems to be a poorly documented option of the $state.go() function. Setting the notify options to false seems to keep everything from refreshing.
//change state without refreshing everything
$state.go('my-state', { id: myId }, { notify: false });

@heygrady That worked for me

@heygrady Thanks for the tip, worked great!

For some reasons, it didn't work for me.
But after tries and errors, accidentally I found a simple solution that works for me.
$state.params.id = id;  //updating the $state.params prevents reloading the state
$location.path('/folders/' + id);
I hope it helps someone.
Note: I'm using angularjs 1.2.7 and ui-router 0.0.1.
I do also have a custom global $stateChangeStart handler somewhere else but most likely not related to this solution (it is for doing some validation whether the target state is allowed or not).

This will allow what you're after. You can disable the notify on a link so the URL changes but doesn't reload your controller: https://github.com/angular-ui/ui-router/issues/1875

Hello, @nateabele
It seems your code break the replace function
  $location.path('http://...').replace();

Am I wrong ?

@roryf legend mate! Worked on angular 1.3.16 & angular-ui-router 0.2.15.

@jeremieca Show me.

@nateabele Thanks, it solved. I made a mistake :) Sorry.

@roryf
This decorator raises Circular Dependency (maybe only in latest angular)
https://github.com/angular-ui/ui-router/issues/427#issuecomment-24518433
Inside of decoration function must be used $delegate argument instead of $location:
angular.module('Shared', []).config(['$provide', function($provide) {
    $provide.decorator('$location', locationDecorator);
    function locationDecorator($delegate, $rootScope) {
        var skipping = false;

        $rootScope.$on('$locationChangeSuccess', function(event) {
            if (skipping) {
                event.preventDefault();
                skipping = false;
            }
        });

        $delegate.skipReload = function() {
            skipping = true;
            return this;
        };

        return $delegate;
    }
}]);

Though event.preventDefault(); didn't worked for me. The very first solution was better.
Created lib from that: https://github.com/anglibs/angular-location-update

@garmoshka-mo Great solution! It works like a charm. Back & forward buttons also work as expected. I'm using it in my production project.
@andremendonca Use $location.path() or $location.search() instead of $state.go() to change the URL without state reloading.

@roryf @garmoshka-mo location.skipReload().search(yourParams) won't update $stateParams. Must be manually updated by angular.extend($stateParams, yourParams) afterwards.


System plugin master, sprint2009 and sprint2010 changes to stable2

Bringing in System plugin changes from master, sprint2009 and sprint2010 branches to stable2.

RDKTV-231, RDKTV-230: setCachedValue, removeCacheKey
DELIA-43557: getDownloadedFirmwareInfo
DELIA-43983: setPowerState, getFirmwareDownloadPercent, setCachedValue, getCachedValue, added KEY checks in APIs, getfirmwareupdateinfo
DELIA-43902: system plugin fix onFirmwareUpdateStateChange event
DELIA-43902: getStbVersionString
XIONE-1468: getPreviousRebootReason fails on Realtek devices (#431)

Signed-off-by: Arun Madhavan<EMAIL_ADDRESS>

Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 6 files pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/483/rdkcentral/rdkservices

Commit: d789ac9a8fbfee3ed74d981b30bdf533217dc6ce

Report detail: gist


webzop\notifications\widgets\WebNotifications class not found

webzop\notifications\widgets\WebNotifications widget class does not exist in widget folder.

Use
php7.3 composer.phar require "webzop/yii2-notifications" "dev-master" -w

to install dev-master version


NGLParserMTL enumerateLinesUsingBlock EXC_BAD_ACCESS

Hi,
I have an EXC_BAD_ACCESS error into the file NGLParserMTL.m at the line 400 :+1:
[source enumerateLinesUsingBlock:^(NSString *line, BOOL *stop) {
		 [self processLine:line];
}];

The NSString source is not null an contains the MTL file data...
Thank you for your reply.

I've fixed a bunch of 64bit and threading issues on my fork.
https://github.com/conquermobile/NinevehGL
Submitting a pull request.


FoundryVTT logo reappearing with some themes / Minimal UI

This is because both use visibility since the recent updates.

Should be fixed with v1.3.0


Could not decode file, replacing by FALSE value: *.9.spi with latest apktool

Hi iBotPeaches!
Information

Apktool Version (apktool -version) - 2.2.2
Operating System (Mac, Linux, Windows) - Windows
APK From? (Playstore, ROM, Other) - Samsung ROM

Affected: apktool https://github.com/iBotPeaches/Apktool/commit/c659df9dce1d92e6175e73ff8515057f8368c27a and above (including 2.2.2)
Not affected: apktool https://github.com/iBotPeaches/Apktool/commit/e407fe839b49551fb06d03fe478f1496018ae24f
Steps to Reproduce

apktool if framework-res.apk
apktool if twframework-res.apk
apktool d SecSettings.apk

I: Using Apktool 2.2.2 on SecSettings.apk
I: Loading resource table...
I: Decoding AndroidManifest.xml with resources...
I: Loading resource table from file: bin\framework\1.apk
I: Regular manifest package...
I: Decoding file-resources...

I: Baksmaling classes.dex...
I: Copying assets and libs...
I: Copying unknown files...
I: Copying original files...

APK and frameworks here https://yadi.sk/d/TJBdGAge3AbeP9
Thanks!

Theres no excuse for this. I never downloaded this application and the bug report is almost 3 months old. I apologize for the massive delay. I'm trying to clean up old tickets (forgotten tickets) and if you happen to have the application again, I'll try immediately to triage and tag.


Readme

Summary of your changes
Description

Checklist

[x] My change follows the Contributing Guidelines
[x] I have added only one new link to the list.
[x] I have checked that the link that I added does NOT exist in the project already.
[x] I have sorted the link alphabetically under the related section.

The project contributors will be shown in the readme section


Flickering of images in FlatList at start of transition

I've been having some issues with images flickering at the start of the transition navigation. I have a transitions with one large shared image, 5 small ones, and some text, and the images occasionally flicker. I'm not sure if its a performance issue or an issue with opacity/styling or even the transition calculations.
I put together a snack on Expo with a somewhat similar structure to what I have in the app: https://snack.expo.io/@kennygoff/fluidtransition-test
Here is a GIF of the issue in action on device: https://gph.is/2NHoobv
In the GIF, it completely messes up the transition, which is pretty rare. The second open, where the main image and one of the smaller images flicker invisible is what happens often for me. It's not consistent, but clicking open and close on items for about a minute will get it to happen normally.
Happens on iOS and Android, both simulator and device.
Possibly related:

https://github.com/fram-x/FluidTransitions/issues/80
https://github.com/fram-x/FluidTransitions/issues/79

Hi @kennygoff! Thanks for submitting an issue with a test project! When opening the snack on my iPhone I didn't notice any flickering at all (the GIF you sent didn't look good, I admit that).
Would it be possible for you to upgrade to the latest version of the package (as of today this will be 0.2.71) and see if the release build flickers (We've noticed that sometimes the debug environment slows the executing down a bit, causing some flicker to occasionally occur).

Thanks @chrfalch! I tested running using 0.2.71 on device in release mode and the issue still occurs. I did realize my Expo Snack which was a fork of someone else's was running 0.2.0 whereas my app was running 0.2.6. I will try to update the Snack to the latest version when I get a chance and get back to you.

@chrfalch I've updated the snack (same link) to 0.2.6 to reflect what's in my app, but I wasn't able to get the latest version of the library running on Expo Snack. Changing the version to 0.2.71 or 0.2.72 in the package.json of the snack fails to install.

@chrfalch @kennygoff  I've run into a similar issue. If you slow down the transition you are much more likely to see the issue.
https://snack.expo.io/@nlbgt256/fluidtransition-test
I've noticed it much more using the back button but it certainly happens from time to time going from the list to the detail page.

Hi @nlbgt, I'm aware of the small "flicker"-issue when running the transition in slo-mo; would you please test to see if this is an issue on a real device with full-speed as well?


Bugfix: metric system f_to_c define

This commit fixes the ability to use the metric system with decimals as proposed in issue #3

:+1: Thank you!


updated robots.txt Non latest documentation fixes#1960

Summary of Changes:

Updated robots.txt file to ensure that only the latest version of the Taipy documentation is indexed by search engines.
Allow search engines to index the latest version: /en/latest/
Disallow search engines from indexing all other versions: /en/*/
Sitemap reference added: https://docs.taipy.io/sitemap.xml
fixes #1960

Purpose of These Changes:

Prevent older documentation versions from appearing in search results when users search for Taipy documentation (e.g., currently, the /en/release-3.0/ version is showing instead of the latest).
Ensure that search engines prioritize the latest version (/en/latest/) of the documentation.

Next Steps (For Maintainers):

After merging this PR, it would be helpful to resubmit the robots.txt file and the sitemap via Google Search Console to expedite the reindexing process.
Consider using the URL removal tool in Google Search Console to request removal of outdated versions from search results to further improve the discoverability of the latest documentation.

Testing:

The changes have been tested locally by inspecting the robots.txt file and verifying the presence of the canonical tags in the HTML headers of older versions.

Please review the changes, and let me know if any adjustments are needed. I’m happy to assist with further improvements!

In a robots.txt file, the * wildcard is used in the Disallow line to block a range of URLs matching a pattern, such as Disallow: /en/release-/, which prevents access to all release versions of the documentation except the latest. On the other hand, the Allow line often doesn’t need a wildcard, as it generally applies to all URLs under a specified path by default. For instance, Allow: /en/ would allow access to all pages starting with /en/, including the latest version, without needing a wildcard. Your proposed configuration of using Allow: /en/ and Disallow: /en/release-*/ is valid, allowing access to all documentation under /en/ while blocking specific release versions, except those under /en/latest/.

In a robots.txt file, the * wildcard is used in the Disallow line to block a range of URLs matching a pattern, such as Disallow: /en/release-*/, which prevents access to all release versions of the documentation except the latest. On the other hand, the Allow line often doesn’t need a wildcard, as it generally applies to all URLs under a specified path by default. For instance, Allow: /en/ would allow access to all pages starting with /en/, including the latest version, without needing a wildcard. Your proposed configuration of using Allow: /en/* and Disallow: /en/release-*/ is valid, allowing access to all documentation under /en/ while blocking specific release versions, except those under /en/latest/.


Remove ES Module build with a source change

Right now the source is already a well organized set of ES Modules, thank you!
But there is one non-standard right now and its that its omitting the .js extension when importing. This is added back during the build and the files are published under the es/ folder.
We can see this in action by looking at<EMAIL_ADDRESS>import identity from "./identity.js";
import uniqBy from "./uniqBy.js";
/**
 * Returns a new list containing only one copy of each element in the original
 * list. [`R.equals`](#equals) is used to determine equality.
 *
 * @func
 * @memberOf R
 * @since v0.1.0
 * @category List
 * @sig [a] -> [a]
 * @param {Array} list The array to consider.
 * @return {Array} The list of unique items.
 * @example
 *
 *      R.uniq([1, 1, 2, 1]); //=> [1, 2]
 *      R.uniq([1, '1']);     //=> [1, '1']
 *      R.uniq([[42], [42]]); //=> [[42]]
 */

var uniq =
/*#__PURE__*/
uniqBy(identity);
export default uniq;

Here's where we can do better. If all we did was add .js to all the imports, then we don't even need a build step. The tagged source from github is already usable. We can see https://raw.githubusercontent.com/ramda/ramda/v0.27.0/source/uniq.js is almost there
import identity from './identity';
import uniqBy from './uniqBy';

/**
 * Returns a new list containing only one copy of each element in the original
 * list. [`R.equals`](#equals) is used to determine equality.
 *
 * @func
 * @memberOf R
 * @since v0.1.0
 * @category List
 * @sig [a] -> [a]
 * @param {Array} list The array to consider.
 * @return {Array} The list of unique items.
 * @example
 *
 *      R.uniq([1, 1, 2, 1]); //=> [1, 2]
 *      R.uniq([1, '1']);     //=> [1, '1']
 *      R.uniq([[42], [42]]); //=> [[42]]
 */
var uniq = uniqBy(identity);
export default uniq;

Btw, I noticed this when trying to use Ramda in https://github.com/denoland/deno

Although we would have to run it by people who better understand the various module builds, we would certainly welcome a PR on this.

It would certainly be great to ensure Ramda works nicely with Deno.  Then it can be added to Deno's third-party modules list, as lodash is.

My go-to person for this is @Andarist.  Any thoughts?

Well, there is no much harm in including those extensions there, BUT why you (@Pyrolistical) would like to consume those files using source files? Distributed es directory is pretty much equivalent and it already contains those extensions. While Ramda is not really using much of a build step this might change in the future (probably not though). Having a distinction between source and distributed files give maintainers freedom to structure source files however they want, including using custom Babel plugins, TS, or whatever else.

It would certainly be great to ensure Ramda works nicely with Deno. Then it can be added to Deno's third-party modules list, as lodash is.

This is an interesting argument - but from what I understand this requires no build step which is somewhat a bummer as mentioned by me above. Shouldn't be much of a problem for Ramda, but it doesn't seem like a good strategy for the entire ecosystem. For instance, any React-based library has to compile their source files and committing both sources and distributed files is also not ideal.

I'm "the build guy" as well, but dislike having any build at all. I really dislike the how built artifacts are pushed up to package managers like npm. We've seen the security implications of this again  and again.
This is why I want to use Ramda's source directly via commit hash https://raw.githubusercontent.com/ramda/ramda/f494250c0aed9ecc096cc5b5b7823661edc14de2/source/uniq.js
Then at least I know in order for a malicious actor to inject code, it would require them over $10,000 USD to find a sha1 collision.
The way I think about it is, Ramda isn't something fancy like JSX in React, its just plain modern JS. If you wish you add a build to output a Babel tree shakable version, that is fine. Call it as such but not es.

my view is that there would still be value in giving people ability to import modules directly,
this is also where javascript is heading...
However,
I totally agree with having src/dist separation,
this is essential for maintenance (build optimisations, bundle optimisations, metrics, etc.)

I think es consumption should be done via package.json#module

Yes, your argument makes sense in npm universe, but I'm not in that. I'm thinking about pure ES Module standard and things like Deno that consume it directly.

Hmm, also ran into a related issue when trying to use the es build. Ramda uses variable names which are keywords in TypeScript.
For example type is a keyword isn't allowed here https://github.com/ramda/ramda/blob/03817fe578048652b9532ae71fd1f1705da4de60/source/internal/_equals.js#L7
This problem is very tricky. Ramda has TypeScript type, but doesn't really have first class support as raised here https://github.com/ramda/ramda/issues/2976
On one hand its honestly not that hard to fix a bunch of minor code changes such that it is compatible with TypeScript, on the other hand Ramda never signed up for this.

That does become tricky.  While Ramda would like to play nicely with things like Typescript, it's never been a major goal.  And while renaming type to something that doesn't conflict is easy enough, how do we make the call of when to do so?  If only a slight change would make Ramda compatible with CoffeeScript, should we do it?  If Ramda could be used in Elm applications with only these two tiny tweaks, is it worth it?  If Ramda could be used inside R, if only we'd rename our usual export variable, should we?

I find this issue very surprising,
typescript should be "smart" enough to figure out whether the type word is being used as variable and not as a type.
This is absolutely fine in all my projects,
I have just checked it.
Can you provide more info to reproduce the issue?

Yes, your argument makes sense in npm universe, but I'm not in that. I'm thinking about pure ES Module standard and things like Deno that consume it directly.

Won't Deno provide any means to consume things differently? I find it hard to believe that they would give up on npm ecosystem in which many packages are packaged before publishing. It's somewhat quirky to me to treat github as a package repository like that. It was not really meant to be one so assuming it can serve as such is somewhat a stretch - or rather, to expect everybody treat it as such at this point in time.
Im kinda playing devil's advocate here though as I maintain multiple packages, but nearly all of them are built from source codes. I would like to support Deno if possible but I'm currently not sure what's the best way to do that.

I find it hard to believe that they would give up on npm ecosystem in which many packages are packaged before publishing

Mr. Node doesn't like npm.
https://deno.land/v1#compatibility
"Unfortunately, many users will find a frustrating lack of compatibility with existing JavaScript tooling. Deno is not compatible, in general, with Node (NPM) packages."
Some rationale (from the same source):-
"Furthermore the [Node] mechanism for linking to external libraries is fundamentally centralized through the NPM repository, which is not inline with the ideals of the web."

Hey guys; since this conversation seems to have died down, I created a PR to resolve the issue reported. My feeling is that using the source directly through ES module is the direction the community is taking (Browser import, Deno import). I see people starting to create "experimental" FS modules inspired by Ramda for Deno; I know there is a strong community here and a lot of work went into this, I really want to register Ramda as a Deno third-party ASAP 😄

I'm all for a PR.  It gets really difficult to discuss such things in the abstract.

For those who are interested: I submitted Ramda as Deno third-party. denoland/deno_website2#1174

@sebastienfilion my types are still a mess with that, how do you handle the types?
I tried getting the ramda.d.ts from definitelytyped but it depends on more stuff still.

@sebastienfilion my types are still a mess with that, how do you handle the types?
I tried getting the ramda.d.ts from definitelytyped but it depends on more stuff still.

There's no implementation of type in Ramda... I don't think it's a good idea to try to force types. Is there an alternative?

What do you mean force types? You mean you'd discourage @types/ramda? In that case there's only waiting for Ramda to support typescript #2976 , and otherwise a short list of typescript supporting fp libs but Ramda is great for people just getting into FP.

What do you mean force types?

I meant that I don't think that Ramda should be rewritten in TypeScript. In my opinion, the approach of DefinitelyTyped is better.
I think that the issue you're having with DefinitelyTyped is that the import statements omit the extension of the files; standard ESM requires a valid URL path -- which is how Deno implements ESM.
// https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/ramda/es/map.d.ts
import { map } from '../index';
export default map;

@sebastienfilion right, so then my question is how do I get definitelytyped types with a Deno import? But I think I found my answer, right now that's not possible. Over here they explain how some d.ts files expect to import others node style, which the ramda one does, which doesn't work for Deno. But that's an issue I can take up with people over on DefinitelyTyped.
If anyone has other suggestions for how to get Ramda types with Deno, I'm all ears.

I've just wanted to chime in here again after thinking about this problem in a different repository. I believe that the best thing would be to keep build artifacts ignored on the branches but they could be added to git on a detached HEAD, just before tagging that detached HEAD. It would kinda let library authors have cake and eat it too. That way anyone could use dist files directly from the tagged commits and we wouldn't have to worry about people using source files directly as they very often are not for public consumption.

@Andarist: I like your thinking.  I have no real idea what other implications this would have, and would have to think about it and play around a bit.  (Unfortunately my main computer died and until the new year, I'm probably stuck coding on a tablet, so I don't expect to do too much myself for the next six weeks or so.)

I don't think there would be a lot of implications - can't quite see any dangers from any side. Just tags would be created for commits that wouldn't exist in the main trunk of the git history but this doesn't seem to be inherently bad, those are not that uncommon situations.


Updated binding to work with Odin version 0.12.0

Modified binding to utilize default stub functions in the event that late-binding fails
Adjusted late-binding implementation
Modified init to bind functions only when found in the loaded XInput version
Added xinput package declaration
Removed unnecessary imports
Altered naming conventions to use the Windows standard (due to GingerBill's intentions to rewrite core:sys/win32 to utilize the Windows naming conventions)
Added ERROR_EMPTY for XInputGetKeystroke API

Altered naming conventions to use the Windows standard (due to GingerBill's intentions to rewrite core:sys/win32 to utilize the Windows naming conventions) I do not agree with this and do not want this in here.

You also removed the that the user passes in the functions to load proc addresses and the library, I did that so the user could implement logging around things if they wanted, you have no way to do that now

You also removed the that the user passes in the functions to load proc addresses and the library, I did that so the user could implement logging around things if they wanted, you have no way to do that now

That's definitely fair - had not been able to determine your intentions for it when I was making updates. I certainly see the value in that.
I'll maintain the fork with the alternate naming convention for now, but I'd be happy to submit a PR containing only the changes required for the wrapper to work with the current compiler version if you'd like.

If you're willing to do that, that would be swell

Closing this PR in favor of opening another with a new branch containing the changes requested above.


Can't see the images on "talk" section

Hi!
Thank you for this wonderful platform!
I'm working on my own blog and I think that something I did make the small images on the talk section disappear.
I used some of the default examples and it looks like this:

Link for my code:
https://github.com/uriahf/rtichoke_hugo/tree/main/content/talk
This is the link for the rendered section:
https://rtichoke-blog.netlify.app/talk

It seems like you're missing the section config page (_index.md) for that section.

 It's fixed now :)


Set logger to discard by default and use value in the config file

Hello,
When the log and debug option are set to false. Event Override TS continue to log on stderr.
Fix the init of the event_override.
Regards.

Thanks for catching this!


YarnSpinnerConsole won't load under Linux MonodDevelop

When loading YarnSpinner.sln into the MonoDevelop FlatPak, we get

Error while trying to load the project '/path/to/YarnSpinner/YarnSpinnerConsole/YarnSpinnerConsole.csproj': Object reference not set to an instance of an object

And nothing can be done on the YarnSpinnerConsole.
No real indication as to what's causing the problem right now.

Seems this is only a problem on the master branch, development seems fine. Given #78 is suggesting a merge from development to master, it's probably best to wait for that process to complete before addressing this.

Unfortunately the Console got a bit behind the core of the project.
We are working on updating the console but that will require a hefty rewrite of the Console so it won’t happen until after 1.1 release.
I am closing this now but if you have any other issues with the console please mention them in issue #175 to keep it all in one place.


DB engine function as (SELECT) column name

Hello there
I'm evaluating the possibility of using goqu to build queries for clickhouse, I know it's not officially supported but I decided to ask anyway
I know goqu implements common functions like goqu.SUM("duration").As("total_time")
But I was wondering if it's possible to set custom functions as I'm showing in the snipped below with a clickhouse function called formatDateTime.
SELECT
     formatDateTime(time, '%Y-%m-%d', 'US/General') AS day,
     sum(duration) AS total_time
FROM sometable

Dialect

[ ] postgres
[ ] mysql
[ ] sqlite3
[x] clickhouse

goqu.Func("formatDateTime", goqu.L("time"), "%Y-%m-%d", "US/General").As(day)


Feature/job ad building

I want to merge this change because...

Screenshots

Pull Request Checklist

[ ] All visible strings are translated with proper context.
[ ] All data-formatting is locale-aware (dates, numbers, and so on).
[ ] The changes are tested.
[ ] The code is documented (docstrings, project documentation).
[ ] Changes are mentioned in the changelog.

Test Environment Config

API_URI=https://qa.staging.saleor.cloud/graphql/

@E1379 I've changed all the text to be able to translated. Can you please take a look again?


Customization for textFormField is very limited

Customization for textFormField is very limited like what if I don't want cursor or I want to resize cursor height width or color. Also There should be a initState function which returns default country's code if not selected

It's not an official way but you can change the colour of the cursor by editing intl_phone_field.dart plugin file after that cold restart the app, that worked for me.


X axis tick culling on 0.1.29

Hi Masayuki,
I have some problem with x axis tick culling on your latest version. Previously, culling make equal tick space but the new version is not. Part of my code related to culling had shown below. Do you have any idea what I need to made change to get the same result when I had run with previous version?
Thanks,
Panuwat

x: {
type : 'timeseries',
tick : {
format : "%Y",
culling: {max: 6	}
},

@jmnunezizu Mind creating a Plunker demonstrating the issue? It's a lot easier to help with one. :smile:
Alternately, this might be a good question for the Google Group, where it will probably get more attention than a closed issue. :+1: Thanks!


Added support for Build Name Updater plugin

I have added support for plugin: buildnameupdater
Also written a test case as well.

This is great. Thanks!
Would you mind rebasing this onto the latest master and squashing it down into one commit?

This is great. Thanks!
Would you mind rebasing this onto the latest master and squashing it down into one commit?

Done!

I've pushed v1.9.0 to PyPI with this change.


Update README.md

Removed AWS as AMI is not available
NOTE: Please read the CONTRIBUTING.md guidelines before submitting your patch,
and ensure you followed them all:
https://github.com/Kong/kong/blob/master/CONTRIBUTING.md#contributing
Summary
Removed AWS AMI link as it is outdates
Full changelog
Removed link to AWS  from deployment kist
Issues resolved

 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.

Hi @svenwal, checking in for updates here, will you address the review? Thanks


Replace LALRPOP parser with hand-written parser

(Supersedes #9152, authored by @LaBatata101)
Summary
This PR replaces the current parser generated from LALRPOP to a hand-written recursive descent parser.
It also updates the grammar for PEP 646 so that the parser outputs the correct AST. For example, in data[*x], the index expression is now a tuple with a single starred expression instead of just a starred expression.
Beyond the performance improvements, the parser is also error resilient and can provide better error messages. The behavior as seen by any downstream tools isn't changed. That is, the linter and formatter can still assume that the parser will stop at the first syntax error. This will be updated in the following months.
For more details about the change here, refer to the PR corresponding to the individual commits and the release blog post.
Test Plan
Write lots and lots of tests for both valid and invalid syntax and verify the output.
Acknowledgements

@MichaReiser for reviewing 100+ parser PRs and continuously providing guidance throughout the project
@LaBatata101 for initiating the transition to a hand-written parser in #9152
@addisoncrump for implementing the fuzzer which helped catch a lot of bugs

Ship It! ;)

One obligatory comment :P Excellent work. Looking forward to my next git pull

:rocket: Let me know if I can help with further testing.


SO_BROADCAST setsockopt for UDP socket

Hi,
Any possibility of adding a setBroadcast function to enable/disable the SO_BROADCAST socket option (required for UDP sockets to send broadcast messages) ? The code looks something like this:
    /// Set SO_BROADCAST sockopt
    pub fn setBroadcast(self: *Self, enable: bool) !void {
        const val: u32 = if (enable)  1 else 0;
        if (is_windows) {
            try windows.setsockopt(self.internal, std.os.SOL.SOCKET, std.os.SO.BROADCAST, std.mem.asBytes(&val));
        } else {
            try std.os.setsockopt(self.internal, std.os.SOL.SOCKET, std.os.SO.BROADCAST, std.mem.asBytes(&val));
        }
    }

(I can do a pull request if you like but it seemed like such a small thing)

Hm. I left broadcasts out on purpose, as new software shouldnt use them, as they are not compatible to IPv6.
But i could see some use cases, what are yours?
Feel free to make a PR tho, if you have a use case for it. But please make a comment about the missing support for IPv6 and maybe assert an IPv4 socket

Thought there might be a reason :-). This particular use case is adding a zig language binding to an interface to some legacy hardware that uses UDP broadcast for device discovery.
I'll work up your suggestions and submit a PR - thanks!

Cool! Thanks!


General Code Improvements

Using Intellij automated tools refactored some of the code. No behavior was changed (ie, no streams)

Replace tabs with spaces
Remove redundant type operations
Prefer Optional.empty to Optional.ofNullable(null)
Prefer try-with-resources
Prefer lambdas to anonymous classes
Simplify if conditionals
Optimize imports

The build on Travis CI fails with (https://travis-ci.org/dropwizard/dropwizard/builds/133273498#L4421-L4423):

[ERROR] /home/travis/build/dropwizard/dropwizard/dropwizard-views/src/main/java/io/dropwizard/views/ViewBundle.java:[112,48] incompatible types: inferred type does not conform to upper bound(s)
[ERROR] inferred: java.util.Map<? extends java.lang.Object,? extends java.lang.Object>
[ERROR] upper bound(s): java.util.Map<java.lang.String,java.lang.String>,java.lang.Object

Additionally, the `*WhenPresentButNull` tests in `GuavaOptionalValidatedValueUnwrapperTest` and `OptionalValidatedValueUnwrapperTest` are now identical to the `*WhenAbsent`/`*WhenEmpty` tests and should be removed (they were testing `Optional` to do the right thing with `null` values instead of the value unwrapper anyway).

Very bizarre that the build fails on Travis, it passes on my machine. May have to do with the jdk version (I'm using jdk1.8.0_66). If it fails again on Travis I'll remove the trouble commits

Yeah looks the old version of the JDK on travis is giving some headaches:
https://github.com/travis-ci/travis-ci/issues/3259
https://github.com/travis-ci/travis-ci/issues/4042

This workaround may help https://github.com/openzipkin/brave/commit/0efe6cc5327fe8e5441b898e15d0731463ed6f12

Coverage decreased (-0.009%) to 81.143% when pulling 284e00dbc93b9aee510301fc4f44069228e2b436 on nickbabcock:gen-code-improvs into 76d9580b221f698ae0b0bd44919be1edd1926425 on dropwizard:master.

Coverage decreased (-0.009%) to 81.143% when pulling abd97be96f2ae23c70775719b7eb2ee8ad747ff4 on nickbabcock:gen-code-improvs into 76d9580b221f698ae0b0bd44919be1edd1926425 on dropwizard:master.

@nickbabcock I wouldn't invest too much time into making a more recent JDK usable in Travis CI and revert the offending commit instead.

LGTM. 👍


Build out team

Build out team
User Story
AS A manager
I WANT to generate a webpage that displays my team's basic info
SO THAT I have quick access to their emails and GitHub profiles
Acceptance Criteria
GIVEN a command-line application that accepts user input
WHEN I enter the team manager’s name, employee ID, email address, and office number
THEN I am presented with a menu with the option to add an engineer or an intern or to finish building my team

This has been completed


Question regarding tradeoff between grouped and flat distribution in vespa.

Hi Vespa Team,
We were evaluating the tradeoffs between Grouped vs Flat distribution in vespa and wanted to confirm out analysis with.
For grouped config, our cluster has 3 groups with 6 content node in each group. The redundancy and searchable copy count is 3.
For flat distribution, our cluster redundancy and searchable copy is both set to 3.
Question regarding Concurrency :
Vespa will create a fixed amount of threads(per search thread setting) for serving any search queries. In a flat distribution the search query will be dispatched to every content node hence the number of threads remaining to serve a new request will be lower than the number of threads available to serve new requests in group distribution since query will be dispatched to a single group and more number of threads available to handle new requests.
Is this analysis correct?
Question regarding Resiliency :
One node down -> When only one node is down in vespa cluster, request will not be dispatched to the group since all docs are not yet available in that group hence we will serve less concurrent requests since none of the nodes in a group are serving requests.
When compared against flat distribution the unhealthy node will be the only one not serving any request.
Is our understanding how vespa will handle this scenario correct?
Question regarding Resiliency :
Multiple node down -> Let us consider a scenario where we have atleast one node down each of the groups. None of the nodes are sharing the same bucket i.e there is atleast one copy of a document on a healthy node.
Can we say that since in group it will send the request to a particular group we will always see lower coverage whereas in a flat distribution since request will be sent to each healthy node which will have searchable copy for the docs the coverage will be 100% in this case.

Hi,
Thanks for a lot of great questions. Please review a document written for Vespa Cloud that addresses some of your questions at https://cloud.vespa.ai/en/topology - then see if there are any open questions after reviewing it.
Note that Vespa Cloud's redundancy config is a little different, but the basic concepts apply

@bratseth But isn't the work load per node lesser in flat distribution as the data sets will be spread out in more number of nodes and hence fewer data is served per node (since only one active copy of data is used during search)? Even if DQW is significant in comparison to SQW, does group distribution result in higher throughput or similar throughput to flat?

In a flat distribution the search query will be dispatched to every content node hence the number of threads remaining to serve a new request will be lower than the number of threads available to serve new requests in group distribution


Adsk Contrib - CDL rework for description.

CDL in OCIO V1 was handling only 1 descritpion. The first description in the SOPNode.
Extending CDL description support using the FormatMetadata.
Legacy get/setDescription on CDLTransform is kept for backward compatibility but using setDescription will clear all other formatMetadata.

Following the two-weeks rule, here is a friendly reminder that the branch could be merged somewhere next week unless there are some objections.


Docs - change docker and docker-compose req version

The Problem/Issue/Bug:
With ddev in version 1.20.0, you need Docker 18.06. With ddev in version 1.20.0, file docker-compose.yaml require version: '3.6', but that property is only available from docker-compose in version 1.20, which supports Docker in version 18.02 or higher. Version 1.22.0 of docker-compose supports Docker 18.06 or higher, which is also required for ddev to run, so I propose to change docs to require Docker in version 18.06 or above, and docker-compose in version 1.22.0 or above.
How this PR Solves The Problem:
Manual Testing Instructions:
Automated Testing Overview:
Related Issue Link(s):
Release/Deployment notes:

 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.

@rfay are you sure about this docker compose version? From what I see, version 3.6 of docker-compose
(currently supported in ddev 1.20) file is introduced in docker compose 1.20
https://github.com/docker/compose/blob/master/CHANGELOG.md#1200-2018-03-20

Thanks for paying close attention! In https://docs.docker.com/compose/compose-file/ they say that 3.6 was introduced in docker engine release 18.02.0.
But... your link wins! Our docker-compose requirement was wrong, and needs to be updated in version.go.  You want to push it or should I?

Updated to current upstream master with distasteful web ui merge :) Couldn't push rebase into the fork.


Documented path for NuGetDefaults.Config on Windows seems incorrect

This page states that on Windows the location for a NuGetDefaults.Config is %ProgramFiles(x86)%\NuGet\Config.
It seems that newer NuGet versions resp. at least dotnet restore expect the NuGetDefaults.Config to be located under %ProgramFiles(x86)%\NuGet.
The relevant source code in PackageSourceProvider.cs also indicates that the documentation is incorrect.
I haven't challenged other places mentioning the Config subdirectory, such as the User and Computer location for the NuGet config. It may be worth to challenge these as well.
Can you please have a look and if confirmed fix the docs?

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

ID: 370d9d91-9f35-79aa-3ace-7b77436e988f
Version Independent ID: 3da4591a-3d3d-c07a-6672-97964de13b14
Content: Common NuGet configurations
Content Source: docs/consume-packages/configuring-nuget-behavior.md
Product: nuget
GitHub Login: @JonDouglas
Microsoft Alias: jodou

@heng-liu Can you confirm?

Hi @JonDouglas , yes, NuGet tries to get settings from NuGetDefaults.config at https://github.com/NuGet/NuGet.Client/blob/dev/src/NuGet.Core/NuGet.Configuration/Settings/ConfigurationDefaults.cs#L33-L44
The directory and configFile are specified at
https://github.com/NuGet/NuGet.Client/blob/dev/src/NuGet.Core/NuGet.Configuration/Settings/ConfigurationDefaults.cs#L21-L22
On Windows, the MachineWideSettingsBaseDirectory  is %ProgramFiles(x86)%\NuGet, not %ProgramFiles(x86)%\NuGet\Config.

On Windows, the MachineWideSettingsBaseDirectory  is %ProgramFiles(x86)%\NuGet, not %ProgramFiles(x86)%\NuGet\Config.

That is correct, but that's not how machine wide settings are calculated.
I am not really sure about the history of it all, but
https://github.com/NuGet/NuGet.Client/blob/a5baa60cfd7560904a264cae1c21eff3498be177/src/NuGet.Core/NuGet.Common/PathUtil/NuGetEnvironment.cs#L44-L47 NuGet\Config is what the machine wide settings are loaded as (we have features that rely on that), but the other one just checks NuGetDefaults.config which is not something heavily used anymore.

@heng-liu @nkolev92 Is this issue good to be closed? I see a PR was merged with a fix.

looks like it, yes.


Crashes when after models load

I'm on Intel Core. Have tried dl by homebrew or dmg. Both crash after installing any of the models for the first time. I go back in to the app and record but no transcription is produced. When I try with huggingface I get an error that model can't be 'none'.
I deleted and did a reinstall of buzz, but the models i tried previously won't automatically download the next time. I try some other models not previously used but same thing happens and it crashes after downloading.
Looks like a great app and would love to use for medical admin.

the audio file to text transcription works though

I also get this error when attempting to re-install using 'brew install --cask buzz'
(base) iMac:journal jamesballantyne$ brew install --cask buzz
Warning: Cask 'buzz' is unavailable: No Cask with this name exists.
==> Searching for similarly named casks...
Error: No casks found for buzz.

I also get this error when attempting to re-install using 'brew install --cask buzz'
(base) iMac:journal jballant$ brew install --cask buzz
Warning: Cask 'buzz' is unavailable: No Cask with this name exists.
==> Searching for similarly named casks...
Error: No casks found for buzz.

Hi, could you please share the contents of the logs at /Users/[username]/Library/Logs/Buzz/logs.txt? Are there any logs that might be of interest?

Also having the issue! Here's what was in that pathway.
logs.txt
In addition, if it's helpful, here's apple's crash log:
Buzz Crash.txt

I have the same issue


Getting SyntaxError: Unexpected identifier

When I execute node home-connect.js I get a syntax error:
/home/pi/bsh-api/index.js:182
async _executeCall(api, params, body) {
^^^^^^^^^^^^
SyntaxError: Unexpected identifier
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (/home/pi/bsh-api/test/home-connect.js:3:13)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)

node --version?

Well, I checked this. It is 4.4.5 which is quite old.
A try on another machine delivered (version = v8.9.1):
https://developer.home-connect.com/security/oauth/authorize?client_id=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX&redirect_uri=https://apiclient.home-connect.com/o2c.html&response_type=code&scope=IdentifyAppliance Monitor *-Control Settings&state=xxxxxx-xxxxx-xxxxxx-xxxxx-xxxxxxxx
error=invalid_scope&error_description=given+scope+doesn't+match+requested+scope
Are there any parameters I have to consider when I execute "node home-connect.js"?

For the first issue, you need at least node v8 for async/await.
For the second issue: the test is by default set up for an 'Advanced Account'. You probably have a 'Basic' account, i.e. you won't be able to get the authorization scope you requested (no permission for '-Control' and '-Settings'). See https://developer.home-connect.com/?q=docs/api/authorization/scope

I checked it with node version v9.1.0 and it's working fine now.


FIX: Fix OSX

This will hopefully fix our OSX timeouts.

Codecov Report

Merging #223 into master will increase coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #223      +/-   ##
==========================================
+ Coverage   74.16%   74.25%   +0.08%
==========================================
  Files           7        7
  Lines        2435     2435
  Branches      485      485
==========================================
+ Hits         1806     1808       +2
+ Misses        455      454       -1
+ Partials      174      173       -1

Indeed it did!

So weird to see a green merge button for pysurfer :)

Hopefully it will stay that way for longer than a week or two this time :)


Develop Diffusive-Reservoir integration

@jdmattern-noaa, @mehdire61 -- these first three items are what we discussed today on the call (we identified only two, explicitly, but the first is implicitly required to achieve the second two.)
Create a new parallel option in compute.py, mimicking the by-subnetwork-jit
Essentially, these lines provide a template for a new option which could be named by-subnetwork-diffusive. For the moment, there will be only one option for subnetwork splitting (that is, on the reservoirs) but we can explore the idea of having another piece of logic that allows additional subnetwork splitting schemes.
Add a function for subnetwork development by reservoirs; add to new parallel option
@awlostowski-noaa, will you please add a reference to the prototype code you developed?
The new function would replace this call in the new parallel option.
Add logic for switching compute kernels depending on content of subnetwork
Some additional logic, ultimately affecting compute_func as used in this call, will be needed to make sure reservoir subnetworks (which will really just be single segments) are sent to the compute kernel for reservoirs while routing subnetworks are sent to the diffusive routing kernel. Eventually, this switching capability could provide the basis for a totally heterogenous routing strategy (assuming we can find a way to satisfy the physics requirements in the subnetwork
@kumdonoaa @awlostowski-noaa -- this piece is where we may need to do some work on the diffusive kernel
Add handling of upstream inputs for diffusive simulation to support reservoir+diffusive integration
Somewhere as part of this call, we need to add code to prepare a dataset of upstream inflows that will be coming as part of the integration with subnetwork-based reservoir modeling. The MC algorithm does this by adding the flows to the flowveldepth array; some other method may be more appropriate for the diffusive algorithm.

Here is the subnetwork creation prototype https://github.com/awlostowski-noaa/t-route/blob/break-nets-at-reservoirs/notebooks/break-networks-at-reservoirs.ipynb

Follow-on work possibilities:

[ ] expand from Croton to Florence for testing
[ ] Evaluate performance of splitting algorithm on large-scale domain (i.e., CONUS)
[ ] Complete merge with 'buttoned-up' test case
[ ] scope (and possibly begin) follow-on effort with more sophisticated splitting scheme
Ideas:

determine need (does reservoir-only satisfy the operational requirement? can we be strategic about clustering to satisfy the parallel execution need?)
document split network statistics (make tools to do this and report on it as part of the nhd_network script/network package) (how many networks are we seeing? What are their sizes and size distributions? What are the topological relationships, i.e., what's the longest path?)
build simple 'overlap' test (for first proposed method, we see the idea of an 'overlap' zone; the mechanics and logic of handling such a zone need to be added to the code. It could be useful to generalize this capability to be functional not only in the diffusive subnetwork parallel mode.)
Build a markdown writeup explaining the proposed method
build and evaluate network size from 'overlap' splitting schemes
build and evaluate tests results generated from applying other splitting schemes

Here is an example of how we would extract the upstream flow values from the upstream_results dictionary:
    for upstream_tw_id in upstream_results:
        tmp = upstream_results[upstream_tw_id]
        fill_index = tmp["position_index"]
        fill_index_mask[fill_index] = False
        for idx, val in enumerate(tmp["results"], qvd_ts_w):
            flowveldepth[fill_index, idx] = val

Need to change the dimensions ubcd_g in Fortran code to allow finer time resolution of reservoir outflow data

Closed by #347


Test lifecycle option in main container

Signed-off-by: Eric Totten<EMAIL_ADDRESS>Signed-off-by: Eric Totten<EMAIL_ADDRESS>Signed-off-by: AliceProxy<EMAIL_ADDRESS>Description
A few sentences describing the overall goals of the pull request's commits.
Just want to run CI on a community PR real quick then I'll close this. For some reason the CI on that PR appears to have gotten stuck and I have no option to restart/approve it so here we are.

Looks good except I don't remember how the ci tests work -- do they just vet that the chart can install, or what?

Yep and they lint the chart after using the values from the test yaml as well before the install.

Thanks @AliceProxy! I'm going to forcibly land this.


Disable Salt's Job Cache

Salt's job cache is buggy, causing random failures to lookup mine data, which
in turn causes our deployments to fail.
Fixes bsc#1054256

Should this change also include the Velum logic for cleaning up old jobs? (include as depend on other Velum PR)

This change can't, as that logic needs to go to the velum repo :)
However, I'd like to merge this anyway, prior to getting the cleanup implemented, so we can continue to validate larger clusters without hacking this in :)

Yup, I meant "include" as a reference to other PR, but fine by me.
LGTM.


Switch to mdanalysis-sphinx-theme

Explicitly add html_logo and html_favicon paths to placeholders so people know what to edit.
I think we can use the github host account (== MDAnalysis) to determine if mda_official is True or not.

If mda_official is True, we should include something in the license by default: https://github.com/MDAnalysis/mdanalysis-sphinx-theme/issues/44

Oof that does get really annoying to include license bits modularly - could we just ship the logo license along every time we do a copy instead?


Catching order

Short Description
Currently it seems that the bot catches visible pokemons in no particular order. If there are Pidgey, Spearow, Rattata and Snorlax at the starting location, then most likely the bot will not try catching Snorlax first, even though it is VIP and will disappear in 30 seconds. This actually happened to me several times.
Possible solution
It would be very helpful to have an option to catch the available pokemons in some particular order. Possible orders:

by time to expire (expiring soon first),
by rarity (lower spawn rate first),
by a user metric (each pokemon type is assigned a user priority, e.g. I want to catch Growlithe before Drowzee, so Growlithe should have higher priority),
by CP/NCP/IV (strongest first).

It may be reasonable to apply the next ordering if the previous ordering resulted in the same ranking. E.g. if both visible pokemons expire in 30-60 sec, then treat their time rank equal and check the rarity rank to decide which one to catch first.
How it would help others
This feature would allow the bot to catch better pokemons more often at the starting location and when teleporting/sniping.
It would also be more human-like behavior (except for the time ranking), since humans catch better pokemons first.

I like this feature, but if we want to do this more human-like behaviour, we can't use all the catching order, I mean:

by time to expire (expiring soon first),

or

by CP/NCP/IV (strongest first).

You can't get that information using the information provided by Pokemon Go app, so maybe

by rarity (lower spawn rate first),

or

by a user metric (each pokemon type is assigned a user priority, e.g. I want to catch Growlithe before Drowzee, so Growlithe should have higher priority),

These two catching order are more human-like behaviour and with the information provided using Pokemon Go app

Could use the same order provided by MoveToMapPokemon, eg. pokemon with a higher threshold should be caught first.
Might need to separate thresholds from MoveToMapPokemon to achieve.

Suggest move "catch" out of MoveToMapPokemon task, and add new "priority" global config item to replace it. That way it could be shared by different tasks.
Alternatively, could just prioritize "vips" then let the rest sort themselves out.


Map JS name to python name for Vue component attributes

Should simplify setting the LMap max and min zoom parameters (i.e., set maximum and minimum zoom level beyond which no new tiles are served)
(And accidentally deleted the paddingBottomRight param; added it back though!)

Thanks @cardinalgeo but I was thinking for consistency to do that for all the params. Doing it for only those 2 would make things worse than before.  We should either embrace the current camelCase that is working and functional or fix all of it to follow Python snake_case approach. Hope that make sense, and sorry if I was not clear initially.

Roger that — I had seen a few cases of the JS-to-Python mapping elsewhere in that file, so it seemed adding a few more wouldn't be unreasonable haha. But I'll give this a go again early this week and let you know if I run into issues!

Hi @jourdain, I've made additional changes aligned with your request — hopefully that does the trick! One question though. Should I touch the camelCase in line "update_latLng" found on line 299 (here? I don't see any indication in the Vue Leaflet documentation that lat-lng is something distinct from latLng, and so I don't quite understand why lines 298 and 299 are not collapsed into one!

Looks great and you are right, there is no difference between 299-300. One can be removed.

Do you want to fix that line or should I just merge your work?

You need to run black but it might be good to run the rest of the pre-commit hooks like describe here. Actually we should add that file in that current repo.

Thanks for your contribution and that new 1.1.0 release!

Thanks for the suggestions, and glad I could help!


Relative destination

Hello!
I've had this problem with stylus url resolving: https://github.com/stylus/stylus/issues/1933
And figured out your plugin processes all css files to one folder specified in dest.
But when my src is like  src/component/*/in.styl and i want to generate each .css at src/component/*/css/out.css, i should use rename to move my files.
So I made an improvement – now param relativeDest can be passed and then all .css files will be generated relatively to dest.
For example
  task: {
        files: [{
          expand: true,
          relativeDest: '/out',
          src: ['test/in.styl'],
          dest: 'tmp',
          ext: '.css'
        },

will generate tmp/test/out/in.css and, the most important, will provide this path to stylus to let it resolve urls correctly

hello, is anyone here?

@tkellen @shama @ctalkington @vladikoff, patiently waiting for your review)

Thank you for the PR! I think this use case is already sufficiently handled by rename though. Unless there is a use case I'm missing here?
Also we reserve configuration at that scope to Grunt supplied options. Any additional configuration for a plugin should be specified in opitons instead.

rename option can't help because it generates .css file near .styl and THEN moves it to another folder, and all resources paths are resolved relatively to it's first location. So when file is moved, all resources paths point to not existing files.
Talking about position of relativeDest param – I get your point, this will be changed.

So what would you say now, @shama?

Added some notes. Could you also add this option to the docs: https://github.com/gruntjs/grunt-contrib-stylus/blob/master/docs/stylus-options.md? Thanks!

@shama, check now please, is everythink ok?

I also noticed that grunt-contrib-stylus doesn't resolve urls from imported .css files (option "include css")
This happens because of https://github.com/stylus/stylus/issues/1957
It can be fixed by additional .set() or updating stylus to 0.52.0, so I've done this within this issue

Thanks a bunch for this @cakeinpanic! :sparkles: :+1: :sparkles:
I'm going to do some other maintenance and then publish a new release.


Implement FlutterTizenEngine spawn

This is a implementation for multi-engine scenarios. This implementation allows to reduce the memory we need to use multiple engines.

Implement FlutterTizenEngineGroup
Change the type of EmbedderEngine's thread_host_ from std::unique_ptr<EmbedderThreadHost> to std::shared_ptr<EmbedderThreadHost>
Add SpawnEmbedderEngine api at embedder_engine
Add FlutterEngineSpawn api at embedder
Add SpawnEngine api at FlutterTizenEngine

The table below shows the result of using gallery with emulator(device Tizen T-samsung-6.5-x86).

Instances
Standard
Spawn

1
143 MiB
143 MiB

2
252 MiB
154 MiB

5
625 MiB
181 MiB

Whenever an instance is added, add about 120 MiB memory in the Standard and add about 10 MiB memory when using Spawn.
contribute to https://github.com/flutter-tizen/flutter-tizen/issues/351
Signed-off-by: swan.seo<EMAIL_ADDRESS>

@Swanseo0
I think there was a crash while testing on CI. Are you checking this out?

After modifying this, I will reopen it in flutter-tizen/engine and flutter-tizen/embedder.


UnexpecTEDIntentPolicy final merge

Proposed changes:
This PR introduces a new policy called UnexpecTEDIntentPolicy and accompanying functionality for different rasa commands like rasa train, rasa test, etc.
Note: The whole feature development was broken down into smaller PRs which were independently reviewed. No code was directly committed to this branch without being peer reviewed as part of a PR.
To get a better understanding of the feature implementation, please head over to the implementation document.
All the smaller PRs are listed below -
Completed PRs
Research:

Implement a new tracker featurizer IntentMaxHistoryTrackerFeaturizer
Implement a new loss function MultiLabelDotProductLoss
Implement the policy IntentTEDPolicy
Add a tolerance parameter to policy
Add severity to policy's output metadata and make use of ranking_length
Fix logic to ensure predictions are skipped when needed.
Experimental label and more integration tests

Engineering:

Add a new default action_unlikely_intent action
Add IntentTEDPolicy to default configuration
Adapt rasa interactive
Support for rasa test https://github.com/RasaHQ/rasa/pull/8843 and https://github.com/RasaHQ/rasa/pull/8949
Update rasa data validate to warn if action_unlikely_intent is present in story training data.

Ongoing PRs

Docs for feature (changelog, migration guide will be part of this)
Sort warnings from rasa test by severity

Note: The introduction of a new default action will make the overall release breaking backwards compatibility of models.
This has been communicated in the changelog and migration guide + MINIMUM_COMPATIBLE_VERSION has been increased in rasa/constants.py.
Status (please check what you already did):

[x] added some tests for the functionality
[x] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

This one needs to also be merged: https://github.com/RasaHQ/rasa/pull/8969

@alwx I've already included that in the description of the PR along with other ongoing PRs.

@dakshvar22 I've resolved all my comments, and also updated this PR: https://github.com/RasaHQ/rasa/pull/8969
It's also seems like I'll be busy tomorrow so not sure if I will have a chance to take another look at this PR until Monday.

Hey @dakshvar22 just a quick note from me. I was investigating some of the recent flaky tests and found that our core-memory leak test tends to time out (10m) for intent ted every now and then like in this case https://github.com/RasaHQ/rasa/runs/2895478026
here's the code of the test:
https://github.com/RasaHQ/rasa/blob/08bb8d2129d4d323d1764370e3abf2598f587797/tests/test_memory_leak.py#L150-L171
I think it is because A) now intent ted policy is in the default config which increases test time here. I guess, either use the traditional config for this test, or reduce the number of epochs that the test trains for. Probably 100 epochs should be fine anyway to achieve the goal of this test.

We should keep the policy in the config but yes we can reduce the number of epochs for the test. 100 seems fine to spot something weird.

@dakshvar22 might be a good idea to also increase the memory allowance to 1.8 / 2GB or so, given that we have another policy inside

@dakshvar22 I just tried rasa interactive trained on the latest version of rasa-demo (main) and something's looking weird. I'm on commit 76b678259f5d0ac39f3954f37475961b5aa881dc of this PR (from today's morning) so possibly some relevant changes happened since, but I'd have to re-train the model to check this.
What I'm seeing: I managed to get to an unlikely intent (as shown by debug logs from rasa interactive) but action_unlikely_intent doesn't get predicted (instead, a normal next action is taken). When I write a test story that includes action_unlikely_intent in the expected place, rasa test core makes a mistake (doesn't predict action_unlikely_intent -- the same way as in rasa interactive). Fyi this is the story file:
- story: some name
  steps:
  - intent: canthelp
  - action: utter_canthelp
  - intent: affirm
  - action: utter_starter_pack_info
  - intent: switch
  - action: action_unlikely_intent  # predicted: utter_ask_which_tool
  - action: action_listen  # predicted: utter_ask_which_tool

and the config I used for training (together with --augmentation 5) is:
language: en
pipeline:
- name: WhitespaceTokenizer
  token_pattern: (?u)\b\w+\b
- name: RegexFeaturizer
- name: LexicalSyntacticFeaturizer
- name: CountVectorsFeaturizer
  OOV_token: oov
- name: CountVectorsFeaturizer
  analyzer: char_wb
  min_ngram: 1
  max_ngram: 4
- name: DIETClassifier
  epochs: 70
  ranking_length: 5
- name: DucklingEntityExtractor
  url: http://localhost:8000
  dimensions:
  - email
  - number
  - amount-of-money
- name: EntitySynonymMapper
- name: ResponseSelector
  retrieval_intent: out_of_scope
  scale_loss: false
  epochs: 50
- name: ResponseSelector
  retrieval_intent: faq
  scale_loss: false
  epochs: 50
- name: ResponseSelector
  retrieval_intent: chitchat
  scale_loss: false
  epochs: 50
- name: FallbackClassifier
  threshold: 0.7
policies:
- name: RulePolicy
  core_fallback_threshold: 0.3
  core_fallback_action_name: "action_default_fallback"
  enable_fallback_prediction: True
- max_history: 6
  name: AugmentedMemoizationPolicy
- name: TEDPolicy
  max_history: 10
  epochs: 50
  batch_size:
  - 32
  - 64
- name: UnexpecTEDIntentPolicy
  epochs: 50
  max_history: 10

Turns out my comment above was a false alarm (good for us!). While there are debug log messages saying the intent was unlikely, there's a memorised story (in AugMemoPolicy) which kicks in and overrides the prediction of action_unlikely_event. So, all is good, I just got confused by log messages from within UnexpecTEDIntentPolicy 🙂

@wochinge @samsucik All the comments that you folks made have been addressed / replied to either in this PR or https://github.com/RasaHQ/rasa/pull/9005 . Could you folks please take another look?

Gitleaks still complains about the commits that push secrets to rasa/data/test_moodbot/credentials.yml . Is it intentional to keep those secrets in the code?  If yes, one thing that we can do is to tell gitleaks ignore this file.

@HotThoughts it's just a fake config and no real credentials

#9108 😊


Store country code in Vessel Information page

Hey there! I am happy to contribute to your repository as part of Hacktoberfest 2020
This PR Closes #332
Some rationale behind my changes:
• I renamed image variable to code in CountryPickerData because it is quite because previous name is quite ambiguous and misleading per se. So now variable code basically describes what kind of value it holds (short country code). image variable was used only once when magically retrieving country emoji, and even in that context it makes more sense to write function like flag(for countryCode: String)
• This change basically enabled me to retrieve $0.code directly and assign it to vessel.nationality in binding closure without introducing ambiguity (it'd be less obvious if it was self.vessel.nationality = $0.image, but it'd have worked the same way it does now).
• Also I fixed name of the CountryPickerView.swift file.

Hi @nugmanoff - Thanks so much for this PR! We appreciate that you gave your rationale for the things we might say "why did they do that?"
Our team will fully review this by this time on Monday (three business days). Until then, please feel free to work on another issue.

 Review PRs

@am-MongoDB thanks for pointing that one out, I missed that! Can you please check the updated revision?

@am-MongoDB  I tried to clean up the PR, but unfortunately I wasn't able to do that. I have no idea how to do it in this context, can you please give me some ideas on how to remove this unneeded commits from the PR?

@nugmanoff I'm not a git-guru and so I always keep it simple.
If you can't get your current fork into line, then:
[ ] Take a copy of the files you've changed
[ ] Create a clean fork
[ ] Reapply your changes
[ ] Create a new PR, include #fixes #332 and a  reference your original PR in the description
Andrew.

@am-MongoDB thanks! but I think I've already fixed the issues

Thanks @nugmanoff PR merged - thanks!


Disable custom_target::custom_bin_target on windows-gnu

The custom_target::custom_bin_target test has been crashing frequently in CI on the x86_64-pc-windows-gnu target since the last LLVM 17 update. This disables the test to reduce the disruption in CI. The issue is being tracked in https://github.com/rust-lang/rust/issues/115985.

Looks good!
@bors r+

:pushpin: Commit 704a5d32b5f6ba322de8c5a6bfbd4b3d4d9fd8ea has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 704a5d32b5f6ba322de8c5a6bfbd4b3d4d9fd8ea with merge 1f94bf2db8c816363792d623e4c178e80181ba42...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 1f94bf2db8c816363792d623e4c178e80181ba42 to master...


Add libraries to the "Use" section.

One can explore the dependencies for a repository in the dependency graph.

dependencies are definitely worth mentioning, all software is based on them.
I only have a problem with the sheer number, e.g. digiwf has 250 pages of dependencies, even if I add them automatically I can only display the static data, which has no added value for me.
We always try to put all the software we list in relation to us, where do we use it, why this particular software. I couldn't do that with 250 dependencies per repo.
But we should make dependencies more prominent, can you think of anything?

I expect a lot of dependencies to overlap among different projects but I agree that the number will be higher from what can be meaningfully displayed.
For displaying one could reduce this to direct dependencies (instead of including transitive ones).
Also one hint that static generated pages can contain javascript (e.g. a static json file with the data and a javascript list to populate based on this data including search and pagination.
Another thing I find very useful is the overview at "back your stack": https://backyourstack.com/it-at-m
This lists all dependency projects looking for funding at Open Collective. Especially low level libraries are very important for performance and security but often receive very little funding for the poor visibility.

https://backyourstack.com/it-at-m was new for me, thx. I will definitely look into this


_.template function does not accept inline data variable.

As title suggests _.template function does not accept inline data variable. It was working fine previously. But since I tried version 1.8 as it supports _.findkey but it stopped working with inline Data variables for the _.template function.

We removed the data from _.template, you now have to invoke the returned function.
_.template(templateString)(data);
_.template(templateString, options)(data);

Hello jridgewell,
Thanks for your response and clarification. I am aware of this change. But what about those apps which are previously using data variable inline with _.template function. They will stop working something that happened with my app. It has so many template calls and will require to revise all of them. So all existing apps that are using data variable inline does not support the latest version of underscore.js
I think there should have been a way for backward compatibility as this is a great framework and is being used in many modern apps and should be taken care of the backward compatibility while disclosing new versions. Currently it's giving impression of immature framework.


when I install axios, create-react-scripts not working!

I working with create-react-app v2.
When I install axios, it's not working anymore!
I think this bug removed after final release of v2.
Regards.

Please fill out issue template.

still not working

Just saying something is not working won't help you to get a proper solution, we need to know your environment, terminal output, etc.
This link https://meta.stackexchange.com/help/how-to-ask is for stack overflow, but i think it applies in any place that you seek for help.
I'm excited for a chance of contributing when i see a notification of a new issue in CRA, but if there are not enough info, it's just a waste of my time (or anyone that subscribe to CRA issue time).
please keep this in mind when you open a new issue or commenting, thanks 🙂

My problem solved!
There is only one rule you have to do. You have to use only one of the package managers. NPM or Yarn.
If you use both, your app will crash!
If you already use them both and your app is crashed, you can delete node_modules folder and run yarn add or npm install command and that's it.
Have fun with you project 👍


v2.4.1 Multi-column imputation

@JuliaRegistrator register()

Registration pull request created: JuliaRegistries/General/5920
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v2.4.1 -m "<description of version>" 73cfaeb06fabe3348061310c8e875be837ca4b89
git push origin v2.4.1

@JuliaRegistrator register()

Registration pull request updated: JuliaRegistries/General/5920
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v2.4.1 -m "<description of version>" 67af04e76742ccf396e338371730e5a62542d1d5
git push origin v2.4.1


Add FFT response Error

We need to output an error if FFT is requested on a sensor but the full FFT response is not received back from the sensor.  For instance if a few packets are received back but some are lost resulting in bad data.  Right now there is no way to know that this failed.  It is important to know as it can lead to FFT requests being sent to sensors on every cycle leading to depletion of the batteries.  Knowing that the FFT response is failing will notify the user of poor wireless connectivity which can be addressed through moving the sensor, adding repeaters, etc.

I vote for this feature as well!


Meta [Gemfile, Gemspec, Travis]

Made some changes to the meta project. Added travis and Gemfile and also moved out the gemspec to its own file.

@hartsock Hello, is there any chance that you might get back to the maintenance of this project? This PR is the basis that would enable more contributions
cc @tianhao64 in case you would like to help the ruby community along the python one :smile:

@MichaelPereira
Hey, I'm actually heads down on another project right now and just don't have the bandwidth to spare here. @tianhao64 How is your bandwidth? Any folks scheduled for Ruby contributions & community care?

I have a couple of these kinds of changes to look at.

@dekz This looks good. There are a few issues merging your PR due to changes in the Rakefile and the existence of a Gemfile now. Would you like to resolves the conflicts for this or would you rather me just close this and redo this? I have no problems handling this myself, but I want to make sure you get credit for doing this.


Fix benchmarking macro for pallet with instance and where clause

Breaking change
The macros frame_benchmarking::benchmark, frame_benchmarking::benchmark_instance, frame_benchmarking::benchmark_instance_pallet, now generate the test function as method on the Pallet struct instead of a regular function.
So to write test instead of writing benchmark test like:
#[test]
fn test_benchmarks() {
  new_test_ext().execute_with(|| {
    assert_ok!(test_benchmark_dummy::<Test>());
  }
}

you must write:
#[test]
fn test_benchmarks() {
  new_test_ext().execute_with(|| {
    assert_ok!(Pallet::<Test>::test_benchmark_dummy());
  }
}

But best is to use the test macro impl_benchmark_test_suite.
Description
Currently the benchmark macro doesn't fully support where clause for pallet with instances.
This should fix it.
You can read the first commit to see a minimal diff, the second commit is for formatting correctly.
I need to implement test as there seem to be no test for the benchmark macro ? cc @shawntabrizi
cc @kianenigma

test added

bot merge


Add support for strut styles

https://docs.flutter.io/flutter/dart-ui/StrutStyle-class.html

New URL: https://api.flutter.dev/flutter/dart-ui/StrutStyle-class.html

AFAIK this is supported.


bug: entry.js generation does not reference import paths correctly on Windows.

Describe the Bug
When running svelte-kit build with the adapter enabled, the build fails after the vite transformation. I am on Windows 10.
Here's an snippet of the output.
`> Using svelte-adapter-firebase
X [ERROR] Could not resolve "../H:directoryto.svelte-kit/output/server/index.js"
.svelte-kit/firebase/entry.js:1:21:
  1 │ import {Server} from '../H:\directory\to/output/server/index.js';
    ╵                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

X [ERROR] Could not resolve "../H:directoryto.svelte-kit/output/server/manifest.js"
.svelte-kit/firebase/entry.js:2:23:
  2 │ import {manifest} from '../H:\directory\to/output/server/manifest.js';
    ╵                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Build failed with 2 errors:
.svelte-kit/firebase/entry.js:1:21: ERROR: Could not resolve "../H:directoryto.svelte-kit/output/server/index.js"
.svelte-kit/firebase/entry.js:2:23: ERROR: Could not resolve "../H:directoryto.svelte-kit/output/server/manifest.js"
`

And in the entry.js file in .svelte-kit/firebase. the first two lines for the imports for Server and manifest the paths are incorrectly formed.
Steps to Reproduce

Run npm run build on project
Notice that after vite transform is finished, the build fails.

Expected Behaviour
When building the project with the firebase adapter, the build completes.
svelte-adapter-firebase version
0.14.0
sveltejs/kit version
1.0.0-next.334

Apologies for this, I don't have a Windows machine to test on. What's the best way to reach out to you to test a new build?
That looks like an issue with
const relativePath = path.posix.relative(dirs.tmp, builder.getServerDirectory());
from index.js
Or, more specifically, from dirs.tmp from line 37
tmp: path.join('.svelte-kit', 'firebase'),

@Nushio Discord is probably easiest. My discord username is my Github username with #6301

In future I want to run the e2e test suite on Windows inside GitHub Actions. I believe this is possible now.


Failed building wheel for ffpyplayer

Software Versions

Python:
OS: Rasp Pi OS Lite + KDE Plasma
Kivy:
Kivy installation method: pip - virtual env

Describe the bug
See error below. Looks like a problem with sdl.h.
`python -m pip install "kivy[full]"
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: kivy[full] in ./.env/lib/python3.11/site-packages (2.3.0)
Requirement already satisfied: Kivy-Garden>=0.1.4 in ./.env/lib/python3.11/site-packages (from kivy[full]) (0.1.5)
Requirement already satisfied: docutils in ./.env/lib/python3.11/site-packages (from kivy[full]) (0.20.1)
Requirement already satisfied: pygments in ./.env/lib/python3.11/site-packages (from kivy[full]) (2.17.2)
Requirement already satisfied: pillow<11,>=9.5.0 in ./.env/lib/python3.11/site-packages (from kivy[full]) (10.2.0)
Collecting ffpyplayer (from kivy[full])
Using cached ffpyplayer-4.5.1.tar.gz (88 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Preparing metadata (pyproject.toml) ... done
Requirement already satisfied: requests in ./.env/lib/python3.11/site-packages (from Kivy-Garden>=0.1.4->kivy[full]) (2.31.0)
Requirement already satisfied: charset-normalizer<4,>=2 in ./.env/lib/python3.11/site-packages (from requests->Kivy-Garden>=0.1.4->kivy[full]) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in ./.env/lib/python3.11/site-packages (from requests->Kivy-Garden>=0.1.4->kivy[full]) (3.6)
Requirement already satisfied: urllib3<3,>=1.21.1 in ./.env/lib/python3.11/site-packages (from requests->Kivy-Garden>=0.1.4->kivy[full]) (2.2.1)
Requirement already satisfied: certifi>=2017.4.17 in ./.env/lib/python3.11/site-packages (from requests->Kivy-Garden>=0.1.4->kivy[full]) (2024.2.2)
Building wheels for collected packages: ffpyplayer
Building wheel for ffpyplayer (pyproject.toml) ... error
error: subprocess-exited-with-error
× Building wheel for ffpyplayer (pyproject.toml) did not run successfully.
│ exit code: 1
╰─> [89 lines of output]
Source/build path: /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579
FFMPEG_ROOT: "None"
WARNING: A problem occured while running pkg-config --libs --cflags libavcodec libavdevice libavfilter libavformat libavutil libswscale libswresample libpostproc (code 1)
  b"Package libavcodec was not found in the pkg-config search path.\nPerhaps you should add the directory containing `libavcodec.pc'\nto the PKG_CONFIG_PATH environment variable\nPackage 'libavcodec', required by 'virtual:world', not found\nPackage 'libavdevice', required by 'virtual:world', not found\nPackage 'libavfilter', required by 'virtual:world', not found\nPackage 'libavformat', required by 'virtual:world', not found\nPackage 'libavutil', required by 'virtual:world', not found\nPackage 'libswscale', required by 'virtual:world', not found\nPackage 'libswresample', required by 'virtual:world', not found\nPackage 'libpostproc', required by 'virtual:world', not found\n"

  SDL_ROOT: "None"
  WARNING: A problem occured while running pkg-config --libs --cflags sdl2 (code 1)

  b"Package sdl2 was not found in the pkg-config search path.\nPerhaps you should add the directory containing `sdl2.pc'\nto the PKG_CONFIG_PATH environment variable\nPackage 'sdl2', required by 'virtual:world', not found\n"

  Generating ffconfig.h
  Generating ffconfig.pxi
  Include directories: ['/tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer', '/tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/includes']
  Library directories: []
  running bdist_wheel
  running build
  running build_py
  creating build
  creating build/lib.linux-aarch64-cpython-311
  creating build/lib.linux-aarch64-cpython-311/ffpyplayer
  copying ffpyplayer/__init__.py -> build/lib.linux-aarch64-cpython-311/ffpyplayer
  creating build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/__init__.py -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  creating build/lib.linux-aarch64-cpython-311/ffpyplayer/tests
  copying ffpyplayer/tests/__init__.py -> build/lib.linux-aarch64-cpython-311/ffpyplayer/tests
  copying ffpyplayer/tests/test_write.py -> build/lib.linux-aarch64-cpython-311/ffpyplayer/tests
  copying ffpyplayer/tests/common.py -> build/lib.linux-aarch64-cpython-311/ffpyplayer/tests
  copying ffpyplayer/tests/test_pic.py -> build/lib.linux-aarch64-cpython-311/ffpyplayer/tests
  copying ffpyplayer/tests/test_play.py -> build/lib.linux-aarch64-cpython-311/ffpyplayer/tests
  copying ffpyplayer/player/frame_queue.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/core.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/decoder.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/queue.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/clock.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/player.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  creating build/lib.linux-aarch64-cpython-311/ffpyplayer/clib
  copying ffpyplayer/clib/misc.h -> build/lib.linux-aarch64-cpython-311/ffpyplayer/clib
  creating build/lib.linux-aarch64-cpython-311/ffpyplayer/includes
  copying ffpyplayer/includes/ffmpeg.pxi -> build/lib.linux-aarch64-cpython-311/ffpyplayer/includes
  copying ffpyplayer/includes/ff_consts.pxi -> build/lib.linux-aarch64-cpython-311/ffpyplayer/includes
  copying ffpyplayer/includes/sdl.pxi -> build/lib.linux-aarch64-cpython-311/ffpyplayer/includes
  copying ffpyplayer/includes/inline_funcs.pxi -> build/lib.linux-aarch64-cpython-311/ffpyplayer/includes
  copying ffpyplayer/includes/ffconfig.pxi -> build/lib.linux-aarch64-cpython-311/ffpyplayer/includes
  copying ffpyplayer/includes/ffconfig.h -> build/lib.linux-aarch64-cpython-311/ffpyplayer/includes
  copying ffpyplayer/writer.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer
  copying ffpyplayer/pic.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer
  copying ffpyplayer/threading.pxd -> build/lib.linux-aarch64-cpython-311/ffpyplayer
  copying ffpyplayer/player/decoder.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/player.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/clock.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/core.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/frame_queue.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/player/queue.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer/player
  copying ffpyplayer/clib/misc.c -> build/lib.linux-aarch64-cpython-311/ffpyplayer/clib
  copying ffpyplayer/writer.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer
  copying ffpyplayer/pic.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer
  copying ffpyplayer/threading.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer
  copying ffpyplayer/tools.pyx -> build/lib.linux-aarch64-cpython-311/ffpyplayer
  running build_ext
  Build path changed to: /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579
  Using compiler "unix"
  Using compiler args: ['-O3', '-fno-strict-aliasing', '-Wno-error']
  Using linker args: []
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/pic.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/pic.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/threading.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/threading.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/tools.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/tools.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/writer.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/writer.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/clock.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/clock.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/core.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/core.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/decoder.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/decoder.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/frame_queue.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/frame_queue.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/player.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/player.c
  cythoning /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/queue.pyx to /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/player/queue.c
  building 'ffpyplayer.pic' extension
  creating build/temp.linux-aarch64-cpython-311
  creating build/temp.linux-aarch64-cpython-311/tmp
  creating build/temp.linux-aarch64-cpython-311/tmp/pip-install-blnokkro
  creating build/temp.linux-aarch64-cpython-311/tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579
  creating build/temp.linux-aarch64-cpython-311/tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer
  creating build/temp.linux-aarch64-cpython-311/tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/clib
  aarch64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g -fwrapv -O2 -fPIC -I/tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer -I/tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/includes -I/home/redrobin/.env/include -I/usr/include/python3.11 -c /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/clib/misc.c -o build/temp.linux-aarch64-cpython-311/tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/clib/misc.o -O3 -fno-strict-aliasing -Wno-error
  In file included from /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/clib/misc.h:5,
                   from /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/clib/misc.c:2:
  /tmp/pip-install-blnokkro/ffpyplayer_f93d1d5951c54425bca7837f425bc579/ffpyplayer/clib/../includes/ffconfig.h:5:10: fatal error: SDL_version.h: No such file or directory
      5 | #include "SDL_version.h"
        |          ^~~~~~~~~~~~~~~
  compilation terminated.
  error: command '/usr/bin/aarch64-linux-gnu-gcc' failed with exit code 1
  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for ffpyplayer
Failed to build ffpyplayer
ERROR: Could not build wheels for ffpyplayer, which is required to install pyproject.toml-based projects
`
Additional context
I installed Kivy base first with no issues. Then tried to install full but got the ffpyplayer error.
Since I'm using KDE plasma as my DE on top of Rasp Pi OS Lite, I'm not sure if I need to run the extra command for additional depenencies. I tried it just in case, but got the following result:
apt-get install libgl1-mesa-glx libgles2-mesa libegl1-mesa libmtdev1 E: Could not open lock file /var/lib/dpkg/lock-frontend - open (13: Permission denied) E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), are you root?
(I am the only user.)

I've the same issue at full installation.

Hi @ElectroDrome and @CodeRabbit957 !
This does not look like an issue with Kivy, but with https://github.com/matham/ffpyplayer install as a pre-built artifact does not exists for your specific architecture.
However, feel free to reach out on our support channels, where someone certainly will try to help you.


DragonEgg is affected by gravity too

Hi,
DragonEggs are affected by gravity but are not assignable from FallingBlock class.
That's weird but maybe it property GravityAffected must be added, isn't it ?
https://github.com/SpongePowered/SpongeCommon/blob/6ffd99fdb7ac0c0f47586230e3bc7183dbd9eb63/src/main/java/org/spongepowered/common/data/property/store/block/GravityAffectedPropertyStore.java#L48

Closed in latest SpongeCommon. The next time we do a SpongeForge or SpongeVanilla build this will be included. Thanks!