dbgenerated() doesnot support raw query anymore?

Bug description
I use this code while working on a project
token_amount     Decimal   @default(0) @db.Decimal(10, 2)  transaction_mode String?   @default(dbgenerated("\nCASE   WHEN (token_amount > (0)::numeric) THEN 'PLUS'::text  ELSE 'MINUS'::text\nEND")) @db.VarChar(5)
It seemed to be working fine then. (It was probably a year ago). But now when I try to setup the project in my new laptop, somehow the code throws an error saying.
db error: ERROR: cannot use column reference in DEFAULT expression
Is there any way I can use default value based on the column value?
How to reproduce

Ran migrate query

Expected behavior
Was expecting to run the migration successfully and all the tables created on the database.
Prisma information

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model user_transactions {
  id               Int       @id @default(autoincrement())
  user_id          Int?
  token_amount     Decimal   @default(0) @db.Decimal(10, 2)
  transaction_mode String?   @default(dbgenerated("\nCASE   WHEN (token_amount > (0)::numeric) THEN 'PLUS'::text  ELSE 'MINUS'::text\nEND")) @db.VarChar(5)

}

// Add your code using Prisma Client

Environment & setup

OS: macOS
Database: PostgreSQL
Node.js version: v18.16.0

Prisma Version
prisma                  : 4.8.1
@prisma/client          : 4.8.1
Current platform        : darwin-arm64
Query Engine (Node-API) : libquery-engine d6e67a83f971b175a593ccc12e15c4a757f93ffe (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/migration-engine-darwin-arm64)
Introspection Engine    : introspection-core d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/introspection-engine-darwin-arm64)
Format Binary           : prisma-fmt d6e67a83f971b175a593ccc12e15c4a757f93ffe (at node_modules/@prisma/engines/prisma-fmt-darwin-arm64)
Format Wasm             : @prisma/prisma-fmt-wasm 4.8.0-61.d6e67a83f971b175a593ccc12e15c4a757f93ffe
Default Engines Hash    : d6e67a83f971b175a593ccc12e15c4a757f93ffe
Studio                  : 0.479.0

Are you using the same Prisma version on your new laptop as in the old one or did you also update that?
How are you trying to setup your project on that new laptop - what Prisma command is giving you that error message?
How did you create your database on the old laptop - manually and then use db pull to create the Prisma schema, or did you really write that @default by hand and then use db push or migrate dev?
The error message you are getting comes from the database, not Prisma. Are you using the same database version as on your old laptop for testing?
What is the SQL statement that is generated based on this Prisma schema? (Use migrate dev to find out). Share it here please. Can you run that SQL manually against your database?


Update catalog_source.yaml

What type of PR is this?

Uncomment only one  /kind line, and delete the rest.
For example, > /kind bug would simply become: /kind bug

/kind cleanup

What does this PR do / why we need it:
Update image sha256 to use v0.0.15
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
How to test changes / Special notes to the reviewer:

 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.

@Aenima4six2 Thanks for the PR, Please sign the CLA if you havn't.
While the change looks good, argocd-operator is not yet updated in the community operators. @jomkz  is currently working on it. I think its good to merge the change once we have the community operator updated with new version

The image referenced by the SHAis out of date. I opened a new PR that contains the correct digest

#310 Has the correct SHA digest to use for v0.0.15


Added ability to have changes in hosting repository and bump versions.

Short description of the work completed

Can now have changes in a hosting repository branch and run tag-release --qa and it will keep those changes as well as allowing you to bump versions.

Steps to test (if not obvious)

Go into develop/master and run tag-release --qa
Should work as before.
Go into a branch in a hosting project that has changes and run tag-release --qa
Should now create a branch based on that branch to keep your changes and allow for the bumping of packages as before.
Go into a repository that doesn't have a develop branch and checkout a branch with no new changes and run tag-release --qa.
Should error out and advise the user.

For Reviewer Use Only

[ ] Code Reviewed
[ ] Tests Passed
[ ] Coverage Reviewed
[ ] Feature worked as expected
[ ] Added or updated flags to --help and README.md
[ ] Is the version upgrade path clear for this change? (breaking vs minor vs
patch)
[ ] Follow up work tracked in a card if needed

Hey, could you add a feature that allows you to keep the current branch name instead of having them pick a new one?


Large files in the final python package

🤓 Before submitting the issue

[X] I have visited the Troubleshooting section.
[X] I have searched among the existing issues.
[X] I am using a Python virtual environment.
[X] I am using the latest version of PyMAPDL and its dependencies (fully updated virtual environment). You can update them using pip install --upgrade --upgrade-strategy eager ansys-mapdl-core in your activated virtual environment.

🔍 Description of the bug
When I install the ansys-mapdl-core package, there are files in core/example/verif that are tens of megabytes in size (e.g. vm232-2.cdb)
🕵 Steps To Reproduce
Install the package and check the size of vm232-2.cdb in venv\Lib\site-packages\ansys\mapdl\core\examples\verif
💻 Which Operating System are you using?
Windows
🐍 Which Python version are you using?
3.11

@Gryfenfer97 ... you are right. Those files are considered complimentary of the vms. But it is true that most of them can be "rebuilt" from the *.dat files. I should check this first.
Then I think we can remove it so the size is smaller.

The files are still part of the package (and installed via the same wheel) - and hence the size of the pymapdl wheel is still larger than it ought to be. I'm reopening until that is addressed


How do you make a decision whether one device is authorized

I would like to ask you some questions.
1.How do you make a decision whether one device is authorized? We found that the license (free edition, for voice wake-up) worked well for a while, but it changed to invalid after the OS (Android) updating/upgrading. We had to apply for a new  license (free edition) to enable the voice wake-up function.

Can one device be authorized "permanently"? I mean if we can use some formal license method after buying formal edition, NOT free edition. Of course I know the device should connect to your service once a month.
So in the case we buy the formal edition, will the license be bound to e.g. the MAC address of Android device? Becoz the Android ID may change after updating or upgrading, while MAC address may be a fixed information for license

I'm looking forward to your prompt reply.

@hrjRai we use GitHub strictly for technical discussions. Please use the sales form for any commercial inquiries.
The Android is bound to your application and hence if you install/reinstall it will be counted as a new device. We do not plan to change this behaviour for free or enterprise users.


Gradle should allow pom.xml customization for Gradle Plugin Portal artifacts

Expected Behavior
There should be a way to ensure pom.xml files are identical at Gradle Plugin Portal and at Sonatype OSSRH.
Current Behavior
Gradle deploys a different pom to the portal, so the users of Gradle Dependency Verification identify an unexpected difference: https://github.com/burrunan/gradle-s3-build-cache/issues/8
Context
I deploy the plugin to both OSSRH and Portal (mainly for testing and signing reasons), and OSSRH mandates certain elements in the pom (license, etc).

TBH I think the plugin portal shouldn't do anything special and use the regular publishing mechanisms. We have no concrete plans now but we're seriously thinking about it.

@jjohannes  Could you be more specific about "do not change artefact/group via the plugin-publish specific mechanism"?
Facing the same issue now

@PFCJeong I mean that you use Gradle's core mechanism for setting "group" and "artifact" that is also used in other places.
For artifact: The subproject's name is the artifact. For this you need to make sure the subproject has the name you expect in the include("my-artifact") statment in settings.gradle. Or, if you publish the root project, use rootProject.name = "my-artifact" in settings.gradle..
For the group use the global project property group in the build.gradle file:
group = "my-group"

The generated pom is also missing the scmUrl even if it is set up in the pluginBundle extension, which stops some third party tools from associating repos (for the purposes of fetching changelogs) with the plugin.
https://github.com/renovatebot/renovate/discussions/12462#discussioncomment-1578161


buildSpritesheet gets an inferred any type

When building a spritesheet object as in this example no type information is found for buildSpritesheet, SpritesheetMetadata, or useInstancedSprite. This appears to be because release v8.11.2 ships without a /components/InstancedSprite/instancedSpriteUtils.d.ts file alongside the /components/InstancedSprite/instancedSpriteUtils.js file.

hey sorry types aren't working for you.
Could you give us a snippet of your code, did you add the .from<typeof meta> to your code?

Sure, the relevant file is
import { buildSpritesheet, type SpritesheetMetadata } from '@threlte/extras';

const meta = [
  {
    url: '/res/punyworld-overworld-tileset.png',
    type: 'rowColumn',
    width: 27,
    height: 38,
    animations: [
      {
        name: 'grass_0',
        frameRange: [0, 0],
      },
    ],
  },
] as const satisfies SpritesheetMetadata;

export const overworldTilesetAtlus = buildSpritesheet().from<typeof meta>(meta);

TS is trying to pull types from<EMAIL_ADDRESS>in particular this line:
export { useInstancedSprite, buildSpritesheet, type SpritesheetMetadata } from './components/InstancedSprite/instancedSpriteUtils';
But the referenced ./components/InstancedSprite/instancedSpriteUtils file has no type information. All the other exported values/types in<EMAIL_ADDRESS>are finding their type info just fine.

Hmm interesting 🤔 thank you for doing that quick double check with me. The team's looking into it further 👍


Jupyter issue

Type: Bug
Dear VS Code Team,
I hope this message finds you well. As a data engineer who heavily relies on Jupyter for data analysis and programming tasks, I have been experiencing some issues with the VS Code and Jupyter integration. I believe it's important to bring these problems to your attention, as they might be affecting many other users too.
The issue I'm facing is related to the colorization of variables and methods within Jupyter cells. Whenever I double-click 'DD' to delete a cell below, the variables in the cell above turn white, losing their colored formatting. Additionally, the auto-completion feature for variables and methods stops working, as if there is a disconnection between VS Code and Jupyter. The only way I have found to resolve this problem is to restart VS Code, which disrupts my workflow.
I am uncertain if this is a problem with your software, a bug in one of the plugins, or an issue with my configurations. However, I kindly request your assistance in identifying the root cause of this behavior and finding a solution.
Here are some additional details about my environment:
To help you investigate the issue, I would be happy to provide any logs, screenshots, or further information you may need.
My primary goal is to enhance the productivity and efficiency of my data analysis workflow in VS Code, and this issue has been hindering that significantly. I appreciate your prompt attention to this matter and look forward to hearing back from you with a resolution.
Thank you for your understanding and support.
 Losing the pylance functionality just by editing some lines of code is a hugh pain not only for data scientists like OP but for folks from other disciplines as well, I believe. It's a recurring issue and the very reason that makes me eagerly looking for alternatives.

https://github.com/microsoft/pylance-release/issues/4685#issuecomment-1674585559

thanks for the feedback, I think this is a duplicate of https://github.com/microsoft/pylance-release/issues/4685#issuecomment-1674585559

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!


The version of tvm of v0.6.1 is incorrect.

There is a problem that the internal version of tag 0.6.1 has not been rewritten.
It remains at 0.6.0.
I fixed this problem in my repository and confirmed the version.
Check this one.
https://github.com/LEA0317/incubator-tvm/releases/tag/v0.6.1

Thanks for reporting, cc @yzhliu

Thanks. I'll add one section to check&update version in the step-by-step release document.

closing for now as the release docs PR update has been merged and we won't act on it further for now. Thanks @LEA0317


Using without oh-my-zsh

So I've been using zsh-autosuggestions happily for a while now but tried removing oh-my-zsh as I'm not really using it much (only a couple of plugins).
But I can't seem to get zsh-autosuggestions to work without having oh-my-zsh also running which seems really odd to me.
I installed zsh-autosuggestions through pacman on Manjaro and have not installed it using oh-my-zsh.
To make it a little clearer here is my .zshrc before disabling oh-my-zsh
# Path to your oh-my-zsh installation.
export ZSH=/home/will/.oh-my-zsh

# oh-my-zsh-plugins
plugins=(git tmux gatsby)

source $ZSH/oh-my-zsh.sh
source /usr/share/zsh/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh

alias r="ranger"
alias x="exit"
alias nv="nvim"
alias rm="rm -i"
alias mv="mv -i"
alias zshconfig='nvim ~/.zshrc'
alias cl='clear'
alias ignorenode='attr -s com.dropbox.ignored -V 1 node_modules'

# powelevel10k theme
source /usr/share/zsh-theme-powerlevel10k/powerlevel10k.zsh-theme

# To customize prompt, run `p10k configure` or edit ~/.p10k.zsh.
[[ ! -f ~/.p10k.zsh ]] || source ~/.p10k.zsh
VISUAL=nvim; export VISUAL EDITOR=nvim; export EDITOR

# vi mode
bindkey -v

# bind jj to normal mode
bindkey jj vi-cmd-mode

# ssh aliases
if [ -r ~/Dropbox/.ssh.zsh ]; then
    source ~/Dropbox/.ssh.zsh
fi
export PATH="$HOME/.deno/bin:$PATH"

And with that config zsh-autosuggestions works as expected.
But if I comment out my oh-my-zsh stuff...
# Path to your oh-my-zsh installation.
# export ZSH=/home/will/.oh-my-zsh

# oh-my-zsh-plugins
# plugins=(git tmux gatsby)

# source $ZSH/oh-my-zsh.sh
source /usr/share/zsh/plugins/zsh-autosuggestions/zsh-autosuggestions.zsh

alias r="ranger"
alias x="exit"
alias nv="nvim"
alias rm="rm -i"
alias mv="mv -i"
alias zshconfig='nvim ~/.zshrc'
alias cl='clear'
alias ignorenode='attr -s com.dropbox.ignored -V 1 node_modules'

# powelevel10k theme
source /usr/share/zsh-theme-powerlevel10k/powerlevel10k.zsh-theme

# To customize prompt, run `p10k configure` or edit ~/.p10k.zsh.
[[ ! -f ~/.p10k.zsh ]] || source ~/.p10k.zsh
VISUAL=nvim; export VISUAL EDITOR=nvim; export EDITOR

# vi mode
bindkey -v

# bind jj to normal mode
bindkey jj vi-cmd-mode

# ssh aliases
if [ -r ~/Dropbox/.ssh.zsh ]; then
    source ~/Dropbox/.ssh.zsh
fi
export PATH="$HOME/.deno/bin:$PATH"

Then zsh-autosuggestions no longer works.
The path to my installation is correct, I can't work out why this could be.
Expected behavior
Should work without oh-my-zsh
Desktop
Manjaro linux
zsh 5.8 (x86_64-pc-linux-gnu)
Installed via pacman

zsh-autosuggestions displays suggestions based on command history. When you disable Oh My Zsh, you also disable history. Press Up to confirm. Once you fix history, zsh-autosuggestions will work.

Thanks for the reply, I had not realised oh-my-zsh was setting my history.
Adding
SAVEHIST=1000
HISTFILE=~/.zsh_history

to my .zhshrc does fix it.


[nrf noup] loader: remove cleanup for direct xip mode

Move ifdefs just to not add code for cleanup unusable slot when direct xip mode is enabled to avoid warnings.

fix provided also here #314


Skip adding empty list of items

Nothing breaking here - but it would show the warnings in the console for the components that this happened for and it's good to have for perf reasons anyways.

Pull Request Test Coverage Report for Build 516697774

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 43.249%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/browser/modelComponents/viewBase.ts
0
2
0.0%

Totals

Change from base Build 516588758:
-0.002%

Covered Lines:
24592

Relevant Lines:
52072

💛  - Coveralls

Pull Request Test Coverage Report for Build 516697774

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.002%) to 43.249%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/browser/modelComponents/viewBase.ts
0
2
0.0%

Totals

Change from base Build 516588758:
-0.002%

Covered Lines:
24592

Relevant Lines:
52072

💛  - Coveralls


Ability to push static DNS servers to containers?

Much like how the IP and GW are able to be defined, can the same be accomplished with DNS servers?
I am running pipework and a container on top of unRAID and use it to provide static IPs to my containers.  However, these containers also acquire their DNS servers from br0 (bridge on unRAID) which I have configured to use Google's DNS servers.
I would like a handful of my containers to use my VPN providers DNS servers instead otherwise I am vulnerable to DNS leaks.  My workaround for now is to have unRAID use my VPN providers DNS servers but I would prefer to not do this.

NM...can do this with the Docker run line.


Added support for HTML notifications with optional use of ngSanitize.

Potential solution for #12, #4, and #6.

nice


Add Nano Wallet v2.0.14

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.

Additionally, if adding a new cask:

[x] Named the cask according to the token reference.
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no open pull requests for the same cask.
[x] Checked the cask was not already refused in closed issues.
[x] Checked the cask is submitted to the correct repo.

Poking #42871, this may be related.

Named the cask according to the token reference.

https://github.com/caskroom/homebrew-cask/blob/master/Casks/nanowallet.rb


Long URLs move delete buttons out of view

Long URLs move delete buttons out of view.

Hi there.
I've addressed this in commit db3cd75 and it will be in the next release.
Thank you


Disable Publish button when there is no db connection

https://github.com/Microsoft/RTVS/commit/9e05ed87299dfaa57c9a50613c7883781b18055f


Create a formatUtils module and add the formatWeight function

I’m going forward with an implementation of the formatWeight util, a follow-up from this discussion
@tsevdos Can you assign me to this issue and link it to the roadmap project?

Please create a new formatUtils.ts module 😁
We need it for all the upcoming format utilities (https://github.com/tsevdos/elUtils/issues/42, https://github.com/tsevdos/elUtils/issues/43, https://github.com/tsevdos/elUtils/issues/44, etc. )

Closed with https://github.com/tsevdos/elUtils/pull/67


Add .gitignore to samples

@mbrandenburger @alexandrosfilios , please, can we have this also for the token-sdk? :)
Originally posted by @adecaro in https://github.com/hyperledger-labs/fabric-smart-client/issues/356#issuecomment-1206315966

Already exists

[X] https://github.com/hyperledger-labs/fabric-token-sdk/blob/main/samples/fungible/.gitignore
[X] https://github.com/hyperledger-labs/fabric-token-sdk/blob/main/samples/nft/.gitignore


Make opevpn configuration read-only

@agherzan @floion
Connects to #194

Related to #198

LGTM

Reverted CC @telphan @floion


Document how to disable Soft-RT (or document that it's impossible)

I'm struggling to figure out how to disable the "Soft Real-Time" feature after it have been previously enabled on Win10 LTSC 2021.
Can you please document how to disable the Soft-RT feature, or at least document that it's impossible?
Failed attempts on disabling Soft-RT
I've already tried the following:
$obj = Get-CimInstance -Namespace "root\cimv2\mdm\dmmap" -ClassName "MDM_WindowsIoT_SoftRealTimeProperties01"
$obj.SetRTCores = 0 # zero RT-cores to disable the feature
Set-CimInstance -CimInstance $obj
Set-CimInstance : A general error occurred that is not covered by a more specific error code.
+ Set-CimInstance -CimInstance $obj
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (MDM_WindowsIoT_...FT/WindowsIoT"):CimInstance) [Set-CimInstance], CimExce
   ption
    + FullyQualifiedErrorId : MI RESULT 1,Microsoft.Management.Infrastructure.CimCmdlets.SetCimInstanceCommand

.. and also attempted this:
$obj = Get-CimInstance -Namespace "root\cimv2\mdm\dmmap" -ClassName "MDM_WindowsIoT_SoftRealTimeProperties01"
Remove-CimInstance -InputObject $obj
Remove-CimInstance : The requested operation is not supported.
+ Remove-CimInstance -InputObject $obj
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotImplemented: (MDM_WindowsIoT_...FT/WindowsIoT"):CimInstance) [Remove-CimInstance], Ci
   mException
    + FullyQualifiedErrorId : MI RESULT 7,Microsoft.Management.Infrastructure.CimCmdlets.RemoveCimInstanceCommand

Gentle reminder.

According to https://github.com/amitxv/ReservedCpuSets it's possible to disable Soft-RT by deleting the HKLM\System\CurrentControlSet\Control\Session Manager\kernel\ReservedCpuSets registry key. I'm not found of tinkering with undocumented registry keys so it would be nice if this registry key could either be documented or a wrapper-API could be provided for the same process.


Stronger this typing?

Suggestion
The behavior of this in methods is one of the last features of JavaScript that is both unintuitive and not checked for by TypeScript. It is commonplace for both novice and experienced TypeScript programmers to accidentaly create a method (instead of an instance function) and then pass it as a callback. Currently, the only way to find out that one has made such a mistake is at runtime (yikes!).
I propose two small changes in the typechecking system which could be introduced as a strict rule (eg. strictThisArgument). Those changes would eliminate most of the mistakes that lead to unexpected values of this at runtime.
🔍 Search Terms
better this and bind, this.method is not a function, strict this, unbound method passed to map, filter, addEventListener compiles but fails at runtime, method as callback checking
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code — not if it's introduced as a strictness rule
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

⭐ Suggestion
Introduce a strict rule that will:

Automatically add the correct this signature to methods in a class
Make this in function signatures unknown by default – ie. () => void would be equivalent to (this: unknown) => void

📃 Motivating Example
Consider the following example:
class ConstantShift {
    additiveConstant = 42;

    addToNum(n: number) {
        return n + this.additiveConstant;
    }
}

function addToNumStrong(this: ConstantShift, n: number) {
    return n + this.additiveConstant;
}

const nums = [0, 1, 5, 27];
const shift = new ConstantShift();

nums.map(shift.addToNum); // compiles, doesn't work
nums.map(addToNumStrong); // compiles, doesn't work

nums.map(shift.addToNum.bind(shift)); // compiles and works
nums.map(addToNumStrong.bind(shift)); // compiles and works

Link to playground.
This example might look artificial, but in essence it's what every React developer does when they want their component to listen to some event. Passing methods as callbacks is a thing that happens quite often in the JS world.
How would this suggestion change this behavior? The first step would change the signature of the addToNum method to:
addToNum(this: ConstantShift, n: number): number

and the second step would make map accept (this: unknown, x: number) => number as the callback.
This would be enough to make TypeScript correctly recognize whether the code will work correctly at runtime, as can be seen in this playground.
💻 Use Cases
Eliminates mistakes when working with methods and callbacks, and ultimately increases productivity.

Duplicate of https://github.com/microsoft/TypeScript/issues/7968.
See https://github.com/microsoft/TypeScript/pull/6739 also for the explanation for removing --strictThisChecks flags.


Custom Controller Error 'DefaultController' is not a function

Hi,
implementing a custom controller.
angular.module('application').controller('SignInCtrl', SignInCtrl);
SignInCtrl.$inject = ['$scope', '$stateParams', '$state', '$controller'];

function SignInCtrl($scope, $stateParams, $state, $controller, $auth) {
  angular.extend(this, $controller('DefaultController', {
      $scope: $scope,
      $stateParams: $stateParams,
      $state: $state
  }));

  $scope.handleLoginBtnClick = function () {
      $auth.submitLogin($scope.loginForm)
          .then(function (resp) {
              console.log('Logged in');
          })
          .catch(function (resp) {
              // handle error response
          });
  };

}

When i call up the page the console output gives me:
Error: [ng:areq] Argument 'DefaultController' is not a function, got undefined
Edit:
It seems to have something to do with not using 'foundation.dynamicRouting'.
I followed https://github.com/zurb/foundation-apps/issues/501#issuecomment-76715381 because dynamic routing does not expose resolve functionality https://github.com/zurb/foundation-apps/issues/387 but i need this for using ng-token-auth https://github.com/lynndylanhurley/ng-token-auth

@NicoBleh If you do not want / need to use the foundation.dynamicRouting module, there is not need at all to extend the DefaultController which is part of the above mentioned module. So simply delete the angular.extend(...) rows and everything should work fine.
BTW: you forgot to include $auth as last element in the $inject array.

@gjungb thanks i really forgot to inject $auth. I deleted the extend rows and moved on.
The main problem was that
$scope.handleLoginBtnClick = function () {
...
}

was not handled. So i guessed that it had something to do with not extending the SignIn controller with the DefaultController.
I turns out that it has to be done like that:
$scope.$on('auth:login-success'), function (ev, user) {
...
 :)


SDFGI doesn't update Mesh instances correctly in the editor

Godot version
4.0.1
System information
Windows 11, Vulkan, whatever graphics is included in intel i5-8265U
Issue description
The SDFGI cascades aren't updating correctly when properties of Mesh instances are updated, i.e visibility, position etc. See video:
https://user-images.githubusercontent.com/11806563/227746411-15c2141c-78f7-496e-b71b-e7c3adedd24f.mp4
The user is looking into a mirror material at other objects
Steps to reproduce

Open godot 4.0
Move temp.tres from scene.zip to project folder
Open scene in editor
Position camera looking into the reflective node with the other nodes behind the camera.
View bug as in video.
Cry.
Fix bug.
Live a long and prosperous life.

Minimal reproduction project
scene.zip

SDFGI doesn't support dynamic objects yet. This would need to be added, and you'd have to make objects dynamic for it to work on those objects.
For static objects in the editor, the SDFGI data could be invalidated when a change is made in the editor after a certain amount of time with no changes has passed (debouncing). This would require https://github.com/godotengine/godot/issues/39961 to be implemented first.

An alternative is to just have a button to update the data or do an update on scene save.

SDFGI doesn't support dynamic objects yet. This would need to be added, and you'd have to make objects dynamic for it to work on those objects.

Thanks for your explaining. Is there currently a plan on this, for example, planned for 4.x?


Firestore Fatal Error on reading query snapshot document changes

Xcode version: 10.1
Firebase SDK version: 5.15.0
Firebase Component: Firestore
Component version: 0.16.1

I am trying to loop through an array of document changes retrieved from a QuerySnapshot. When attempting to access an element from the [DocumentChange] array or loop through them (ie. snapshot.documentChanges.forEach) this fatal error occurs: "NSArray element failed to match the Swift Array Element type".
This code can be used to recreate the error which occurs on line: snapshot.documentChanges.forEach
        let query: Query
        private var profileListener: ListenerRegistration?

        self.profileListener = query.addSnapshotListener
        {
            (querySnapshot: QuerySnapshot?, error: Error?) in

            guard let snapshot = querySnapshot else
            {
                print("Error fetching snapshots: \(error?.localizedDescription ?? "")")
                return
            }

            snapshot.documentChanges.forEach
            {
                (diff: DocumentChange) in

                let document = diff.document
            }
        }

I can't reproduce the underlying issue, and without more information on this there's really nothing I can do. @morganchen12 or @Thomas-Cartotto if you're able to reproduce this please let us know and we'll reopen and investigate further.


Ignoring Meross native hk devices

What issue do you have? Please be as thorough and explicit as possible.
The only way I can get the Meross plugin to ignore native hk devices is to not insert cloud credentials and add devices individually into the plugin with name, uuid, ip address, etc.
Is this expected behavior ?
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge UI-X

Which version of Homebridge/HOOBS do you have?
V1.6.0

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Windows 11 Pro in a Hyper-V machine
Node.js v18.13.0

Which version of this plugin (homebridge-meross) do you have? Has the issue started since upgrading from a previous version?
V8.5.1-beta.3, first install

Which Meross devices do you have that are causing issues? Please include product models if applicable.
HomeKit native MSS110, MSS510XR maybe others
Total of 14 out of 39, all at least 1 year old, no new models, the non-native hk devices that I’m adding are MSS110

Please paste any relevant logs below.

Hi,
Please can you provide a list of unique models that are homekit native along with their hardware versions?
I ignore these devices on a case by case basis from user feedback as obviously i cannot own every model!

Native HomeKit
MSS110     4.0.0
MSS110     7.0.0
MSL120D     4.0.0
MSL120DR   4.0.0
MSS510X     4.0.0
MSS510XR   4.0.0
MSS550X     4.0.0
MSS560X     4.0.0
MSS570X     4.0.0
MSS620       7.0.0
Non-native
MSS110     2.0.0

Ah, are you aware there is an option in the configuration to hide native homekit devices?
If you enable this, most of these models would get removed.
In the new beta version I have just added the rest, so if you update to the beta and enable this option, all these models will be hidden from Homebridge.

Yes, I had that option enabled and yet 14 of my 40 or so Meross devices were doubled

These may have been the models that weren’t added to my list, they are updated in the beta version now.

Thanks for updating, installed the latest beta and all is good.

The list I gave you is all my Meross devices, not the ones that were doubled. Couldn’t remember which ones specifically weren’t recognized as HomeKit native.

The only ones i had missing were the MSS110 (v4) and MSS510XR 👍🏻

Thank you

Thanks for your support 🙂


Added titles and also fixed a spelling mistake

A cool project, I'd like to help. I added an option to filter the assignments titles so that users (if there are any more) can have them in a list. I have a lot of time on my hands, I could help develop this if there are any more endpoints. If you have a list of any other endpoints, I could add methods for them.

Also, I am going to hold off on this commit for now because I would rather make another model for assignments and classes and stuff like that. If you want to make that that would be great.

Hey, yeah, my high school uses oncourse and I spend a lot of time on the command-line, so I was wondering if anyone found the API for it and I found this. It's really nice work. I'd love to add to it and make more models. Just wondering if there are any more endpoints, or only the ones here. BTW, I was looking through the commit history and found your oncourse ID and password. I think you can remove that commit from the history in Github.
It's crazy, the open-source community really has stuff for everything.
Can I add you on discord?

Ya, you can add me on discord, I would like to talk about it more there! Wolfhound905#1234


Updates and refactorings

Takes care of #10.

Sure, will do!
On 7 Nov 2019 10:05, Robert Forkel<EMAIL_ADDRESS>wrote:
@xrotwang commented on this pull request.

In cldf/cldf-metadata.jsonhttps://github.com/lexibank/halenepal/pull/11#discussion_r343539518:

@@ -11,37 +11,37 @@
"dc:related": null,
"dc:source": "sources.bib",
"dc:title": "Wordlists in Selected Languages of Nepal",

"dcat:accessURL": "https://github.com/lexibank/halenepal",

"dcat:accessURL": "git@github.com:lexibank/halenepal",

@chrzykihttps://github.com/chrzyki I admit that using the git remote URL as access URL is somewhat misuse - but since we do, could you switch to cloning via https?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/lexibank/halenepal/pull/11?email_source=notifications&email_token=ABDYZC6O6K5QKVYK4PMJN33QSPK4ZA5CNFSM4JKC6P62YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCKVO3EY#pullrequestreview-313191827, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABDYZC3LAMEDIFM4PLWQVS3QSPK4ZANCNFSM4JKC6P6Q.

I'm opening an issue for the refactorings you mentioned @LinguList but merging for now to get a first figure of the updated CLICS stats.


Numeric Conversion documentation link goes to wrong URL

It goes to https://www.boost.org/doc/libs/1_82_0/libs/numeric-conversion/ which is 404
It should go to https://www.boost.org/doc/libs/1_82_0/libs/numeric/conversion

Yep that's one of the "special cases" libraries. We really should try to normalize that if possible.

This seems like it may have been resolved?!
Image

appears to be working fine.


Makefile.coq: Operation not permitted during esy setup

Hi, I am trying to get the formalisation compiled on macOS 10.15.7, but after running for some time, esy aborts when compiling coq-stdpp. This is the error I get:
info esy 0.6.10 (using package.json)
info building @opam/coq-stdpp@git:https://gitlab.mpi-sws.org/iris/stdpp.git#6eb05dfc40feef58063bb537fb742eb16bbf86d1@751b68c1
info building coq-flocq@git:https://gitlab.inria.fr/flocq/flocq.git#a9be51660cd865d323b0b3bbb9faa793856ea0de@c6503a40
info building coq-itree@github:Mbodin/InteractionTrees#238cbdd6dce3d3f3f9431f1d0c6117ba42674007@d41d8cd9
error: build failed with exit code: 1
  build log:
    # esy-build-package: building: @opam/coq-stdpp@git:https://gitlab.mpi-sws.org/iris/stdpp.git#6eb05dfc40feef58063bb537fb742eb16bbf86d1
    # esy-build-package: pwd: /Users/matija/.esy/source/i/opam__s__coq_stdpp__ed9c85ce
    # esy-build-package: running: '/Users/matija/.esy/3_________________________________________________________________/i/opam__s__coq-opam__c__8.10.1-9e5ff3df/bin/coq_makefile' '-f' '_CoqProject' '-o' 'Makefile.coq' 'DESTDIR' '=' '/Users/matija/.esy/3_________________________________________________________________/s/opam__s__coq_stdpp-d0db58e0' 'COQMF_WINDRIVE' '=' '/Users/matija/.esy/3_________________________________________________________________/i/opam__s__coq-opam__c__8.10.1-9e5ff3df/lib/coq'
    Fatal error: exception Sys_error("Makefile.coq: Operation not permitted")
    error: command failed: '/Users/matija/.esy/3_________________________________________________________________/i/opam__s__coq-opam__c__8.10.1-9e5ff3df/bin/coq_makefile' '-f' '_CoqProject' '-o' 'Makefile.coq' 'DESTDIR' '=' '/Users/matija/.esy/3_________________________________________________________________/s/opam__s__coq_stdpp-d0db58e0' 'COQMF_WINDRIVE' '=' '/Users/matija/.esy/3_________________________________________________________________/i/opam__s__coq-opam__c__8.10.1-9e5ff3df/lib/coq' (exited with 2)
    esy-build-package: exiting with errors above...

  building @opam/coq-stdpp@git:https://gitlab.mpi-sws.org/iris/stdpp.git#6eb05dfc40feef58063bb537fb742eb16bbf86d1
esy: exiting due to errors above

Any ideas what I can do? Thanks in advance!

Hi! Thanks for the report.
I’ve never had this issue before ☹ I will investigate next week and try to understand what could have yield this error message.

I’m sorry, I’m afraid that I don’t understand what could have cause this issue.
We based ourselves on esy as our dependencies are quite sensitive on version numbers (and esy enables to point to a particular commit hash, which I find convenient, but it’s subjective), and some of these were difficult to compile, even through opam. I can try making an opam package, but it will take me some time. Sorry about that.
We recently started a branch called 8.13 to run on a more recent version of Coq and our dependencies. It does not compile yet, but the dependencies should. Can you try on this branch just to see whether the error message is the same?
Thanks in advance!

Thanks for your effort! I tried compiling the 8.13 branch and I get the same error as above, except the info building on top points to slightly different libraries.
info esy 0.6.10 (using package.json)
info building coq-flocq@git:https://gitlab.inria.fr/flocq/flocq.git#c9353b99debd7b8533c2558b8523d3946831f000@2da84757
info building coq-mathcomp-ssreflect@github:math-comp/math-comp#6bff567e84b01c1b3502985ec936b9e74ea252b4@1c5796f8
info building coq-paco@github:Mbodin/paco#40cea8feac992e4b69266516ed70f0916366d622@d41d8cd9
info building @opam/coq-stdpp@git:https://gitlab.mpi-sws.org/iris/stdpp.git#13df68219bf461b6363b8c03703290245690628d@e49e485d
error: build failed with exit code: 1
  build log:
    # esy-build-package: building: @opam/coq-stdpp@git:https://gitlab.mpi-sws.org/iris/stdpp.git#13df68219bf461b6363b8c03703290245690628d
    # esy-build-package: pwd: /Users/matija/.esy/source/i/opam__s__coq_stdpp__6309a4d1
    # esy-build-package: running: '/Users/matija/.esy/3_________________________________________________________________/i/opam__s__coq-opam__c__8.13.2-12a14a60/bin/coq_makefile' '-f' '_CoqProject' '-o' 'Makefile.coq' 'DESTDIR' '=' '/Users/matija/.esy/3_________________________________________________________________/s/opam__s__coq_stdpp-d939b084' 'COQMF_WINDRIVE' '=' '/Users/matija/.esy/3_________________________________________________________________/i/opam__s__coq-opam__c__8.13.2-12a14a60/lib/coq'
    Fatal error: exception Sys_error("Makefile.coq: Operation not permitted")
    error: command failed: '/Users/matija/.esy/3_________________________________________________________________/i/opam__s__coq-opam__c__8.13.2-12a14a60/bin/coq_makefile' '-f' '_CoqProject' '-o' 'Makefile.coq' 'DESTDIR' '=' '/Users/matija/.esy/3_________________________________________________________________/s/opam__s__coq_stdpp-d939b084' 'COQMF_WINDRIVE' '=' '/Users/matija/.esy/3_________________________________________________________________/i/opam__s__coq-opam__c__8.13.2-12a14a60/lib/coq' (exited with 2)
    esy-build-package: exiting with errors above...

  building @opam/coq-stdpp@git:https://gitlab.mpi-sws.org/iris/stdpp.git#13df68219bf461b6363b8c03703290245690628d
esy: exiting due to errors above

I guess this may be an issue with stdpp, so I'll try and look there next.

I just realised that I didn’t add the "buildsInSource": true tag for coq-stdpp in the file package.json. That might be the issue. (And it makes me think about why it was even accepted on my system ☹) Sorry about that.
Can you check again with the last version of the main branch? Thanks in advance!

Sorry, I was away on the vacation. I've tried again and now I get the following error:
debug checkStaleness /Users/matija/Documents/webassembly/WasmCert-Coq/_esy/default/installation.json: false
debug checkStaleness /Users/matija/Documents/webassembly/WasmCert-Coq/esy.lock/index.json: false
debug checkStaleness /Users/matija/Documents/webassembly/WasmCert-Coq/package.json: false
debug checkStaleness /Users/matija/.esy/source/i/compcert__3245df9a/package.json: false
debug checkStaleness /Users/matija/.esy/source/i/coq_itree__ed7d071c/package.json: false
debug checkStaleness /Users/matija/.esy/source/i/coq_paco__139799f8/package.json: false
debug checkStaleness /Users/matija/.esy/source/i/esy_m4__779f59f5/package.json: false
debug checkStaleness /Users/matija/.esy/source/i/esy_ocaml__s__substs__0.0.1__19de1ee1/package.json: false
debug checkStaleness /Users/matija/.esy/source/i/ocaml__4.8.1000__fac38140/package.json: false
debug checkStaleness /Users/matija/.esy/source/i/parseque__0a0b6bb7/package.json: false
debug checkStaleness /Users/matija/.esy/source/i/strong_induction__53ca3d1f/package.json: false
debug checkStaleness /Users/matija/Documents/webassembly/WasmCert-Coq/package.json: false
debug using cache
debug reading project cache: 23.756981ms
info esy 0.6.10 (using package.json)
debug PkgArg root resolves to wasm_coq@link-dev:./package.json
info running:
             esy build-dependencies \
             --all \
             wasm_coq@link-dev:./package.json
debug ['getconf' '_NPROCESSORS_ONLN']
debug buildDependencies ~concurrency:4
debug build: 2.235889ms
info running:
             esy build-package (disable-sandbox: false)\
             wasm_coq@link-dev:./package.json
debug build wasm_coq@link-dev:./package.json
make: error: couldn't create cache file '/var/folders/zz/zyxvpxvq6csfxvn_n0000000000000/T/xcrun_db-RhxAO1Bx' (errno=Operation not permitted)
mkdir -p .vscode
mkdir: .vscode: Operation not permitted
make: *** [.vscode/settings.json] Error 1
error: command failed: 'make' (exited with 2)
esy-build-package: exiting with errors above...
debug build wasm_coq@link-dev:./package.json: 70.415020ms
error: build failed with exit code: 1

esy: exiting due to errors above

Running esy ls-builds gives me the following output:
<EMAIL_ADDRESS>[build pending]
├── @opam/cmdliner@opam:1.0.4 [built]
├── @opam/coq@opam:8.10.1 [built]
├── @opam/coq-stdpp@git:https://gitlab.mpi-sws.org/iris/stdpp.git#6eb05dfc40feef58063bb537fb742eb16bbf86d1 [built]
├── @opam/dune@opam:2.4.0 [built]
├── @opam/linenoise@opam:1.3.1 [built]
├── @opam/mdx@opam:1.9.0 [built]
├── @opam/ocamlfind@opam:1.8.1 [built]
├── @opam/odoc@opam:1.5.2 [built]
├──<EMAIL_ADDRESS>[built]
├── coq-ext-lib@github:coq-community/coq-ext-lib#ddeab06b09115f66db54b2997df390cd7599eec6 [built]
├── coq-flocq@git:https://gitlab.inria.fr/flocq/flocq.git#a9be51660cd865d323b0b3bbb9faa793856ea0de [built]
├── coq-iris@git:https://gitlab.mpi-sws.org/iris/iris.git#69dfcc7191e4cd1954fd6a00e192ad0ebb0697b9 [built]
├──<EMAIL_ADDRESS>[built]
├── coq-mathcomp-ssreflect@github:math-comp/math-comp#ab54764c15886289107ec43b94bc355ada662c4c [built]
├──<EMAIL_ADDRESS>[built]
├──<EMAIL_ADDRESS>[built]
├──<EMAIL_ADDRESS>[built]
└──<EMAIL_ADDRESS>[built]

Let me know if you need any additional information.

Thanks a lot!
The good news is that all the dependencies have been compiled. The permission error seems to be because I told esy that the compilation would be in the _build folder, which is almost the case, apart from the part creating the settings for vscode. It’s frustrating that somehow the permissions are not the same in our respective configurations (and I would argue that your settings are better than mine, as they check more things). I’m disabling the generation of the .vscode folder for now and pushing into the main branch.
I’m sorry about this: I was expected this tool to provide more reproducibility.

Yes, it now builds successfully (almost)! I had to comment out ln -f -s ./_build/install/default/bin/wasm_interpreter ./wasm_interpreter in the Makefile in order to avoid a similar issue to the one above. Running ./wasm_interpreter tests/const.wasm hello 10 --vi ends up with a crash (see the following output) though, but I think this is a different issue, so feel free to close this one. Thanks for all your help!
parsing OK
instantiation OK
interpreting OK
step 0:

invoke
0with values (empty)

step 1:
normal
  local 1
  with values (empty)
    block i32
        i32.const 42
    end
  end local
with values (empty)
and store unchanged
step 2:
normal
  local 1
  with values (empty)
    label 1
    label_cont
      i32.const 42
    end label
  end local
with values (empty)
and store unchanged
step 3:
crash
with values (empty)
and store unchanged
crash%

This latter bug looks like it might be related to #5 .


Please invite me to the GitHub Community Organization

Name
Sai Adarsh S
Discord Username (if applicable)
ad6rsh#7823
Additional Context
Open Source. Communities. Contributions. Issue fixes

Check your email or organisation page
Thank you for contribution 🙂
Please contribute in Unique-Github-Profiles


GLTF2 Failure to import

Godot version:
0c3335d / Custom branch
OS/device including version:
Windows 10
Issue description:
"Make sure all parents of a multi-rooted skin are the SAME" failure to import.
Steps to reproduce:
Export via Maya2GLTF. Ping me if you need to create it.
Minimal reproduction project:
Causes "Make sure all parents of a multi-rooted skin are the SAME".
aquarius-astellia-maya2gltf.zip
https://sketchfab.com/3d-models/aquarius-astellia-622bde32272d4545b89cc09113ca7439

Should be fixed with that PR ^

Worked, can close after pr is merged.


Service Page - Show custom field attached to Service on side panel

Service Page - Custom Field / Files attached on service page, just show, no alteration changes on custom fields / files
Only showing Custom Fields / files attached no changes to fields / file allowed here, only preview mode,
agreed by @vinpahilwani

changing custom fields / files will require lot of api changes/role changes
so not created initially , only preview mode required


Allow returning CompletableFuture's from datafetchers

When returning CompletableFutures from datafetchers we sometimes encounter an error in the lines of Unknown value 'java.util.concurrent.CompletableFuture@e77cd7a[Completed normally]'.
By converting the future to a mono it should be handled properly.
This is probably not a complete solution, and maybe the returned CompletableFuture should be handled somewhere different, but this at least seems to solve the issue.

Generally, we mean to let CompletableFuture pass through, with no additional processing needed, since GraphQL Java anyway expects asynchronous values to be of that type. The way support Reactor types is to turn Mono into a future in ContextDataFetcherDecorator. So now with this change we would turn the future to Mono, only to turn it back to a future again before it gets to GraphQL Java.
Can you provide more details on the original problem, what do you observe and what happens exactly? Is it an error log message, or an error in the response, what component creates that "Unknown value" error message, etc

Can you provide more details on the original problem, what do you observe and what happens exactly?

I can't verify it myself right now, but I believe that if you run the test without the implementation changes you should be able to observe the problem yourself.

But the issue we were experiencing was along the lines of that a resolver function with a signature like fun name(user: User): String, with a parent type like fun user(): CompleteableFuture<User> was failing on the fact that it couldn't find a method on the controller that accepted a CompleteableFuture<User>.
For all those cases we added toMono(), because a signature like fun user(): Mono<User> works allright, but I would expect that to work for CompleteableFutures as well.

I did look into it again, and I now remember what was going wrong; the returned CompleteableFuture is wrapped in a Mono when one of the parameters is a Mono (which is the case when for example there's a Principal argument defined in the resolver method).
This mono is then unwrapped somewhere, but then it's still a CompleteableFuture, and thus no matching resolver method can be found.


Update the interface for declaring Python download preferences

The loose consensus is that "fetch" doesn't have much meaning and that a boolean flag makes more sense from the command line.

Adds --allow-python-downloads and --no-python-downloads to the CLI to quickly enable or disable downloads
Deprecates --python-fetch in favor of the options from (1)
Removes  python-fetch in favor of a python-downloads setting
Adds a never variant to the enum, allowing even explicit installs to be disabled via the configuration file

Notably I did not deprecate the python-fetch setting, just removed it. I'm not sure what the pattern is to deprecate a setting yet.

I'm a little uncertain of the "never" value, but I do think it has some utility to require explicit opt-in from the CLI to install versions.

Whoops I checked in my pyproject.toml change, and look, it works https://github.com/astral-sh/uv/actions/runs/10310109626/job/28541254932?pr=5936

Thanks. Am I right that --python-downloads isn't exposed on the command line? So those settings are only available in a configuration file?
I'm wondering it it should be --download-python and --no-download-python to match settings like --compile-bytecode. Are we consistent with that pattern?

I leaned away from --download-python because it won't force Python to be downloaded, it just allows it if it would be, e.g. --python-preference only-system --download-python would still never download Python.

Am I right that --python-downloads isn't exposed on the command line? So those settings are only available in a configuration file?

Yes, only a boolean option is available from the command line and the "manual" value is only accessible via the configuration file. I find that a little peculiar, but don't think it'll be problematic in practice.


Inaccurate end time calculation of mobile phone

When I use the phone，the end time show Infinity：NaN：NaN，please help me,thank you

My Apple phone is also equipped with this problem. Is there a solution? @a291755596


Notification schedule

Scheduling notification using job dispatcher sometimes is getting destroyed by the system. Needs to update the recurring settings or switch to alarm receiver.

Will be replaced by JobScheduler


Set rails dependency down to ~> 5.2.0

As I could not find any errors with rails 5.2 I suggest downgrading the minimum required version.
Fixes #4

Let's see, what the specs do.

Hey @henkesn.
Sorry to reply so late.
I tried to downgrade as you propose (also updating spec/dummy/config/application.rb) but some tests fails.
     Failure/Error: ActiveStorage::Blob.create_and_upload! io: StringIO.new(data), filename: filename, content_type: content_type, identify: identify, record: record # rubocop:disable Layout/LineLength

     NoMethodError:
       undefined method `create_and_upload!' for #<Class:0x00007fc80757f0e0>
       Did you mean?  create_after_upload!

@blocknotes never mind. We had in running for some time in production with rails 5.2 without issues. During migration I noticed that the way I set it for rails 5 was wrong anyway as it won't accept rails 6 anymore. It would be better to use a version constraint like '>= 5.2.0', '< 7'.
But as already said, we have already migrated which probably makes it hard to maintain for 5.2.
I'd just leave it like it is and close this PR.


Remove IShaderConstantSetCallback from the engine

In vulkan we can no longer "set" uniforms, only UBOs for dynamic or large data and push_constants for small and static data.
Everything must be in the command buffer or data buffer, nothing can be set dynamically so there is no reason to have a shader callback.
So remove this API as soon as the new material system is complete.
For OpenGL a special functional (or a vector of pair<uniformName,offset>) to map the 128 bytes of vulkan push_constants to some uniforms (no opaque types!) is required.

Requires a graphics pipeline object.

Idea have two systems working in parallel, one with normal shader programs and another with separate shader pipelines.
By GL spec: pipeline if bound will be used, otherwise shader program object that's bound.
So don't even have to code state tracking which takes into account the interplay between programs and shader pipelines, if SMaterial has a nullptr pipeline then unbind pipeline if there was any bound.

Depends on #102

https://repository.genmymodel.com/devshgraphicsprogramming/VulkanShaders
https://repository.genmymodel.com/devshgraphicsprogramming/VulkanPipelineLayout

Latest musings
https://github.com/buildaworldnet/IrrlichtBAW/issues/102#issuecomment-460566609

@Crisspl read the first post


Update control_of_documents.md

typo's and improved readability

not sure whether I did something wrong with adding these changes-

Added my changes in the full_reveiw, this pull request can be deleted


sp-wasm-interface: remove useless wasmi impl

Since the wasmi backend has been removed from sc-executor, so I don't think it's necessary to keep the wasmi_impl part in sp-wasm-interface

@koute PTAL

bot rebase

bot merge


Add support for external references

I have several use-cases where a resource has a reference to a resource managed by another server.  I can get the reference to work by defining a dummy resource, but it would be nice if there were built in support for this.  Maybe something like:
owner: jsonApi.Joi.one('users').external()

That sound like a very reasonable extension @BryanHunt. We'll be happy to merge support for it if you submit a PR.


CLI command to transform contract code to hex with imports replaced

Issue To Be Solved
I'm working on contract to aid in delegated contract updates, and this includes storing contract code in onchain resources. The easiest way to pass around contract code is as a hex string and convert it to a byte array in the transaction. However, hexifying the .cdc file contents with non-native utils means I need to explicitly state the import addresses.
It would be really helpful if I could tap into Flow CLI's import syntax replacement to handle this for me.
Suggest A Solution
Add a flow command that takes a contract file location and returns the code as a hex string, something like
flow hexify ./contracts/Foo.cdc --network emulator # returns 70756...0a7d

Where the CLI replaces import addresses in Foo according to the aliases set for the specified network and returns the resulting contract code as hex.
Context
Mentioned above

I would suggest having this command a bit differently, since this seems a bit of a special use case at least for now I would avoid adding it to the top level since we are trying to have as few as possible to keep it concise and readable. I think since everything that has to do with using flow.json to resolve the code is in the project domain it would be a nice fit to put it there. Furthermore, the output encoding could be achieved using the already existing output flags --output which was made just for the purpose like these (It's more of a helper flag tbh because in true nature of CLIs you should pipe the output in a command that converts the input to hex but that's another convo 😄).
My suggestion is:
Have the command as:
flow project build {optional name of contract}

That would build all the contracts or just the one specified. You can then leverage the ouput flag and save flag if you want to save to file. So the whole command would be:
flow project build Foo --output hex

Would that work for you?
I'm just changing proposal to keep things consistent with other commands.

That all makes sense! Agree that it's better to put the feature behind a flag instead of a top-level command.

I have this code in overflow.


UserWarning: Implicit dimension choice for softmax has been deprecated.

I understand that this repository is still a work in progress, but I just wanted to point this out.
onmt/modules/copy_generator.py:93: UserWarning: Implicit dimension choice for softmax has been deprecated. Change the call to include dim=X as an argument.
  prob = F.softmax(logits)

Thanks for pointing this out.
Solved in: https://github.com/Ubiqus/OpenNMT-py/commit/04c67bd7eb920b1174655e3f963fb19a424773bc .


Changing the CSS Cursor for chart elements

In a bar series, some of my bars are clickable and some are not. I wish to change the default cursor for clickable bars to a pointer.
I can do this using a CSS attribute selector to find elements with the fill color I've set for bars that have a dataPointSelection event that will result in a visual change like so,
path[fill='rgba(0,123,255,0.85)'] {
  cursor: pointer;
}

The hack works for now, but is there a more reliable way to do this?

You can set the cursor to pointer with:
    chart: {
      ...
      events: {
        dataPointMouseEnter: function(event) {
          event.path[0].style.cursor = "pointer";
        }
      }
    }

And inside the dataPointMouseEnter function you can define a condition for when the cursor would be changed.

Hey! It doesn't seem like this is working as of @3.33.2, has this been changed in a release after this has been answered or is there something different for react apexcharts? Thanks so much!

Hey! It doesn't seem like this is working as of @3.33.2, has this been changed in a release after this has been answered or is there something different for react apexcharts? Thanks so much!

Try this:
events: {         dataPointMouseEnter: function(event) {           event.fromElement.style.cursor = "pointer";         }       }
Worked for me.

@edward-hunt thanks for the help really . but I found using scrElement like this event.srcElement.style.cursor = 'pointer' more accurate

This worked for me
chart: {
      events: {
        dataPointMouseEnter: function (event) {
          event.target.style.cursor = 'pointer'
        },
      },
    },


Allowing downloading of the Manim docs

Pretty much what the title says, it would be nice to have a downloadable version of the docs (doesn't need to have the animations in the doc but maybe a link or the video file, (all of them can be downloaded along with the docs).
Not a huge feature but would be massive for learning offline!

Oh alright fair enough, thanks a ton!


(fix) Correct the removal of a position

Before submitting this PR, please make sure:

[x] Your code builds clean without any errors or warnings
[x] You are using approved title ("feat/", "fix/", "docs/", "refactor/")

A description of the changes proposed in the pull request:
The connector attempted to delete a key in an non-existent attribute of the class. Partially addressing hummingbot #6032
Tests performed by the developer:
Ran testsuite
Tips for QA testing:

New proposal by another submitter includes tests