Directive requiring can't find camelCased directive with a data prefix

This is either a configuration issue or a parsing issue. I keep getting these errors:
https://docs.angularjs.org/error/$compile/ctreq?p0=superhero&p1=strength
https://docs.angularjs.org/error/$compile/ctreq?p0=super-hero&p1=invis
The code is in the plnkr below.  http://plnkr.co/edit/Ofq6OXE1tTTIIKMCZic6
I would expect the consistent camelCasing to work, but that doesnt see to be the case here.

I'm not sure I understand the problem... In your invis directive you've got require: "^super-hero", while you should have require: "^superHero", - the same way you've got it in the strength directive.
What do you mean exactly by:

I would expect the consistent camelCasing to work

@pkozlowski-opensource I updated the plunkr, so I found out that the bug only happens when you add data as a prefix to the directive. Basically, if my directive was named dataHero then I would expect the element <data-hero></data-hero> to work, and it does. However, when I require it with ^dataHero then it is unable to find the correct controller. The easier fix here is to just not use data as a prefix, but I thought I would report it anyway.

@moneytree-doug
data is a just decorator which is skipped in directive search, you add data- in html just to pass validations.
So, if your directive is named TotoLulu, you can use it with:
<toto-lulu> or <data-toto-lulu>
and to require it you use its name: require: totoLulu
But don't name your directive dataTotoLulu, even if it could work in some use cases, it is highly confusing with the general use of 'data-' in directive name, and avoiding confusion in your code is always a good idea ;-)

@frfancha I agree completely, but having data prefixed in the element is different from prefixing data to an attribute. But the better error here would be to say not use a data prefix instead of saying the controller cannot be found

having data prefixed in the element is different from prefixing data to an attribute

I don't see why, actually.

@moneytree-doug the data prefix has special meaning in AngularJS directives (as described in the "Matching Directives" section of https://docs.angularjs.org/guide/directive) and this prefix is stripped from directive names. So yes, you shouldn't be really naming your directives with the data prefix.
As to:

having data prefixed in the element is different from prefixing data to an attribute

this is debatable - I'm not sure what spec are saying about data prefix on the element names. Would be great if anyone could do a bit of searching / reading on the topic.
I'm going to keep it open for a while as I'm not sure what is the best course of action here: either trying to "fix" this or just update docs....

BTW, (not that I recommend this, but) you can still use an element directive starting with data, by prefixing all occurences with data- or x-, e.g.:
<x-data-hero>...</x-data-hero>
or
<data-data-hero>...</data-data-hero>

I would rather just have Angular restrict a data prefix for a directive name than telling me that it cannot find the correct controller. It just basically diverts my attention to away from the correct thing, and I end up spending a few hours figuring out if its configured properly and having to debug Angular itself to figure out the issue.

@moneytree-doug actually you are onto something - it is true that we could throw when a directive is named starting with one of the "restricted" prefixes.
@petebacondarwin WDYT?

...but they are not "restricted" :(

@gkalpak sure, but as you've said, you wouldn't recommend people to use they directives like <x-x-mydirective>, <data-data-mydirective> or <x-data-mydirective>, right?
Maybe the right thing to do here would be to have this warning in ng-hint?

I am just saying that they are not "restricted" directives (right now)as there is a way to use them without problem.
So, although I wouldn't be opposed to making them restricted (and throwing an error), it would be a breaking change. (Not that I have anything against breaking changes; just pointing it out :))
--
In any case, if we decide to "keep" them, raising awareness on the directive normalization process would be nice. There is only a short mention in the $compile docs (L530); and of course in the developer guide, although I am not sure how many people actually read the guide.
:+1: for ngHint wanring !


remove open_share_price argument from close short action creation

agent.create_agent_action has a new parameter open_share_price, which is only used if the action is CLOSE_SHORT. The parameter is also an attribute of MarketAction. This is not a great pattern, because users have to know when this argument is used or not and most of the time it is not. It's also not documented in the class docs, which is a separate issue.
One possible alternative solution is to switch units into base, so that the share price is baked into the unit. We possibly also pass the market state into create_agent_action, although I don't love that either because it's still unclear which market state attributes are used.

addressed by #208

addressed by #207


Bump bicep types version

This PR bumps the version of Azure.Bicep.Types used to 0.2.2. Because this version adds a Flags and a ReadOnlyScopes property to serialized resources, I've added the plumbing for that to the included plugin and rerun the type generator. (The type generator was run in a separate commit and should be easy to filter out when reviewing.
I don't know if/how K8s declares readonly resources, so the type detection logic is unchanged. Each resource type will now have a "Flags":0 property (indicating that it is read/write), but the generated files should be otherwise unchanged.

Mooted by https://github.com/Azure/bicep-types-k8s/commit/dc544ffbef9b86a8e0e29d12b8356b1948ff8e9e


svlint: init at 0.4.7

Motivation for this change
Add a SystemVerilog linter to Nix.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

/marvin opt-in
/status needs_reviewer

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/291

going to wait for ofborg to finish


Mm-38333 display users within a channel

Summary
Added users within a group to list view in add members
Ticket Link
https://mattermost.atlassian.net/browse/MM-38333
Related Pull Requests
NA
Release Note
NONE

@mkraft Unsure who to add as QA because Malik is on PTO

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @aspleenic

Hi @hamzaMM, are you keen on finishing this PR?

/update-branch

Error trying to update the PR.
Please do it manually.

@BenCookie95 can you please fix the conflict ?

Awesome, lets get this merged! @BenCookie95 can you help and merge when possible?


Get the most customized insights into all organizations on GitHub！

Hi developers,
Good news! We are planning a new feature to OSS Insight to provide you with interesting, inspiring, and customized insights into all the companies and organizations on GitHub. The source data is the public information of those companies and organizations they display on GitHub.
To provide better user experience and let you get the most useful and customized insights, we’d like to invite all of you to join and share with us your ideas.

What do you expect from this feature?
What kind of insights do you want to know the most?
What problems/issues do you expect to solve with this feature?
What goals do you want to achieve with this feature?

Feel free to leave your ideas or suggestions here, and look forward to your responses. 😄

It's excactly what I want! Actually I've been thinking about how to find some interesting companies or organizations for some time. What I'm looking for is something like this:

How many companies/organizations are there on Github? Where are they located?
Trending companies/organizations by languages/countries/topics/businesses?
What technologies/repos are companies/organizations built with?

It's excactly what I want! Actually I've been thinking about how to find some interesting companies or organizations for some time. What I'm looking for is something like this:

How many companies/organizations are there on Github? Where are they located?
Trending companies/organizations by languages/countries/topics/businesses?
What technologies/repos are companies/organizations built with?

Hi @bitgorust, thanks to share your ideas with us! We will consider it and let you know if there are any progress about this feature.


Capistrano breaks when new deploy started before previous finished

I was doing cap staging deploy and before it was finished I saw that other team member tried to do same thing as well. Both deploy finished successfully.
After second deploy was finished I saw that there's exception into the unicorn.god.log (used by God gem to log unicorn start/restart/stop errors).
/usr/local/rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.4/lib/bundler/definition.rb:22:in `build': /home/deployer/apps/xxxxxxxxxxxx/releases/20150428140210/Gemfile not found (Bundler::GemfileNotFound)

As you see, I'm using God for managing server processes with touching file in tmp folder for restarting the Unicorn server.
My Capistrano version is 3.3.5
Is there any clear way to handle this scenario?

Communication! There are some solutions which may or may not be appropriate for your team, but lock-files have a habit of going stale. You might also consider using a service like the one we're building to collaborate on your deployments at https://www.harrow.io/ (Official web based Capistrano (and more) service) launching in a few weeks.

I agree; I think this is better solved by an external plugin (or communication) and not by Capistrano itself. Closing as "won't fix".


Update graphics and one social post

Description
Updates the graphics on the action page and replaces the most time-sensitive of the social media posts.
We received some feedback on the graphics library not being very noticeable on the site (the person said the current link made them think it would just link to the graphics carousel itself), so I added a button linking to that. Open to other ideas though, since I'm not sure it fits very well.
Type of change

[ ] Updated content (New CTA, updated wording, etc.)

Misc Notes
Preview site: https://dftba-shalom.github.io/tbfightersdotorg/action.html

I can't figure out how to fix the button for mobile :(. If anyone is able to help with that it would be very appreciated!

I can't figure out how to fix the button for mobile :(. If anyone is able to help with that it would be very appreciated!

I can help tonight


Enhancement - Performance Optimisation - Style Node and Edges

Enhancement
Root Cause

Current behaviour

Perform looping on all the node and edges to modify the style objects, results in cascading update ("update inside an update") and calling lifecycle methods in Graphin componentDidUpdate.
Perform styleNode and styleEdge manually perform Object.assign on every single style metadata.
Every single style changes causing React to repeat it's cycle: reconcile the react tree, commit DOM changes and recall the hooks, results in wasteful re-render.
With the data structure changes on #184 , looping collection are more expensive compare to array of object due to transform objects into array with Object.values or Object.entries.

Describe the solution you'd like

using updateItem to perform styling during data importation, node styling and edge styling.
reduce re-render on React components and prevent dispatch onto redux state on every single style change

References

Graphin perform setState in componentDidMount results in Cascading Update

Proceed to close this issue as we feel that styling the nodes and edges do not affect the user experience heavily compare to other enhancements stated in #180


Duplicate styles injected when using Astro integration

UnoCSS version
0.51.4
Describe the bug
When using the UnoCSS Astro integration, two different sets of the same UnoCSS styles are injected into the <head>, one with the attribute data-astro-dev-id="{path/to}/__uno.css" and another with the attribute data-vite-dev-id="/__uno.css"
Reproduction
https://stackblitz.com/edit/github-u8fq8k?file=src/pages/index.astro
System Info
macOS 13.3.1, Chrome 112.0.5615.121, Astro 2.3.0
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This problem still exists.
https://stackblitz.com/edit/github-u8fq8k-s1lqwe?file=package.json


Script fixes

codebase-check.sh

rc exit code was mistakenly being overwritten

rotate-secrets.sh

Add oc version check
Add absolute path for repo*.txt
Add token rotation for framework Actions

/override "Framework KinD / Tests (latest, false, hosted)"

/override "E2E / Framework KinD / Tests (latest, false, hosted)"


[ENH] Introduce alternative clique finding methods

Reference Issues/PRs
#451
dependent on #452
What does this implement/fix? Explain your changes.
This will allow CD cliques to be formed using pairwise test results, either with Bonferroni adjustment or Holm correction. I am also tidying up the CD drawer.
One thing with the post hoc nemenyi test: the qalpha values are hard coded for three alpha levels and set by n_estimators only (not number of problems/rows). I assume these are for very large n, but there seem to be methods that set it by both n_estimators (columns) and n_problems (rows). I will investigate further

Small question, its better to use the Friedman test from scipy isn't it ? As done in here for instance. Not sure if you agree, but it would reduce the amount of code. Correct me if this is a version that is different than the one you are using in the cdd code.

yes definitely, this may not be the version going in, frankly doesnt look very good. We should also use the proper qstat values for the posthoc test, rather these hard coded values which I think are for very large n only and a weird legacy of the original matlab code :)

made redundant by #582


javaslang++

Current coverage is 99.55%

Merging #40 into master will decrease coverage by -0.45% as of 51ad9f0

@@            master     #40   diff @@
======================================
  Files           22      22
  Stmts          227     227
  Branches        49      49
  Methods          0       0
======================================
- Hit            227     226     -1
- Partial          0       1     +1
  Missed           0       0

Review entire Coverage Diff as of 51ad9f0

Powered by Codecov. Updated on successful CI builds.


surah HeaderView integration with SurahView

https://github.com/islamversity/Reyan/projects/1#card-46265520

@rezaiyan
I created a new issue for your comments regarding ui improvements
https://github.com/islamversity/Reyan/issues/55


v2.0.13

Closes #321
Closes #325
Closes #327

Codecov Report

Merging #330 (b6cf4c4) into main (7ed82f7) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main      #330   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           71        72    +1
  Lines         6134      6222   +88
  Branches      1707      1733   +26
=========================================
+ Hits          6134      6222   +88

Flag
Coverage Δ

unittests
100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/classes/api/index.ts
100.00% <100.00%> (ø)

src/classes/applications/main-app.ts
100.00% <100.00%> (ø)

src/classes/applications/migration-app.ts
100.00% <100.00%> (ø)

src/classes/calendar/calendar-manager.ts
100.00% <100.00%> (ø)

src/classes/calendar/index.ts
100.00% <100.00%> (ø)

src/classes/migrations/v1-to-v2.ts
100.00% <100.00%> (ø)

src/classes/notes/note-manager.ts
100.00% <100.00%> (ø)

src/classes/notes/note-sheet.ts
100.00% <100.00%> (ø)

src/classes/notes/note-stub.ts
100.00% <100.00%> (ø)

src/classes/notes/note-trigger.ts
100.00% <100.00%> (ø)

... and 4 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7ed82f7...b6cf4c4. Read the comment docs.


Documentation for interfaces

Spectaql doesn't seem to generate output for interface types or queries that return them. In other words, I see my types that are declared as type or input but not interface, and queries that return interface types don't show up at all. I don't see any mention of interfaces in the documentation, so maybe they're not currently supported? What would be required to include these in the documentation?

Fix coming...

Fixed in 0.8.0

I am currently using version 1.2.1 and the interfaces are not generated. Back in version 0.9.2 it is wroking correctly. Can you please fix it as before? The documentation then have not working links to the interfaces and people complain about not working links. Either remove it from docs or fix the links and generation of interfaces. Thank you in advance


python310Packages.grpc-interceptor: 0.15.1 -> 0.15.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.grpc-interceptor is: Simplified gRPC interceptors
meta.homepage for python310Packages.grpc-interceptor is: https://github.com/d5h-foss/grpc-interceptor
meta.changelog for python310Packages.grpc-interceptor is: https://github.com/d5h-foss/grpc-interceptor/releases/tag/v0.15.2
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.15.2 with grep in /nix/store/9ba3n5s6pjkbqrrk6ngnvbsmk07cyj74-python3.10-grpc-interceptor-0.15.2
found 0.15.2 in filename of file in /nix/store/9ba3n5s6pjkbqrrk6ngnvbsmk07cyj74-python3.10-grpc-interceptor-0.15.2

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.grpc-interceptor
python311Packages.grpc-interceptor

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/9ba3n5s6pjkbqrrk6ngnvbsmk07cyj74-python3.10-grpc-interceptor-0.15.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.grpc-interceptor https://github.com/r-ryantm/nixpkgs/archive/d2b4da5b625aaea93bcd1db2ebf5fb927228a197.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/9ba3n5s6pjkbqrrk6ngnvbsmk07cyj74-python3.10-grpc-interceptor-0.15.2
ls -la /nix/store/9ba3n5s6pjkbqrrk6ngnvbsmk07cyj74-python3.10-grpc-interceptor-0.15.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.grpc-interceptor
python311Packages.grpc-interceptor

Maintainer pings
cc @tomaskala for testing.

Result of nixpkgs-review pr 242878 run on aarch64-darwin 1

4 packages built:

python310Packages.grpc-interceptor
python310Packages.grpc-interceptor.dist
python311Packages.grpc-interceptor
python311Packages.grpc-interceptor.dist


Password reset flow

When we implement this flow server side we'll want to restrict access to /reset based on the presence of a (valid?) ?token=x key.

This page can be public. The form can POST the token from the url and the new password together. Then the API endpoint can validate the token.

@zpnk I don't mind the duplication for now, but should we figure out a way to share the common components between these two pages?


Re-Activate vsphere tests

What this PR does / why we need it:
Re-enables the vsphere e2e tests :)
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes kubermatic/kubermatic#3398
Special notes for your reviewer:
none

/retest

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/test pull-machine-controller-e2e-vsphere

/assign @mrIncompetent


WIP: Windows builds

Let's try

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.
I do have some suggestions for making it better though...
For recipe:

Recipes should usually depend on matplotlib-base as opposed to matplotlib so that runtime environments do not require large packages like qt.

@jaimergp, this doesn't find curand.lib, even though cudatoolkit is installed, and it should be coming from there AFAICT. Any hints?

cudatoolkit only distributes the DLL, afaik. See here.
The lib files must be provided by the build-time installation. So they should be in %CUDA_HOME% (system location).

I thought CMake would set LIB correctly, but maybe we need to add %CUDA_HOME%\xxx to LIB (I don't know where exactly the lib files are in the CUDA tree, but you get the point)?

Thanks for the quick reponse! With LIB you mean something like CMAKE_LIBRARY_PATH? I found something perhaps relevant paths in the nvcc activation
if not exist "%CUDA_PATH%\lib\x64\cuda.lib" (

and openmm-feedstock
CMAKE_FLAGS+=" -DCMAKE_LIBRARY_PATH=${CUDA_HOME}/lib64/stubs"

Let's try!

BTW, I just noticed that %CMAKE_ARGS% seems to be empty on windows...

glog does ship the CMake files needed for the auto-discovery, so no clue what's going on... Maybe make sure the search path for CMake modules is correctly set up. Docs.

glog does ship the CMake files needed for the auto-discovery, so no clue what's going on... Maybe make sure the search path for CMake modules is correctly set up. Docs.

Thanks a lot. It looks like the glog files do not comply with the paths that CMake searches on windows, i.e.
Library/lib/cmake/glog/glog-config.cmake

is not in
<prefix>/
<prefix>/(cmake|CMake)/
<prefix>/<name>*/
<prefix>/<name>*/(cmake|CMake)/
<prefix>/<name>*/(lib/<arch>|lib*|share)/cmake/<name>*/
<prefix>/<name>*/(lib/<arch>|lib*|share)/<name>*/
<prefix>/<name>*/(lib/<arch>|lib*|share)/<name>*/(cmake|CMake)/

It seems to me something is off with the glog cmake files. CMake docs for CMAKE_PREFIX_PATH say:

Semicolon-separated list of directories specifying installation prefixes to be searched by the find_package(), find_program(), find_library(), find_file(), and find_path() commands.

And I'm definitely pointing right at the files with
-DCMAKE_PREFIX_PATH=%LIBRARY_LIB:\=/%/cmake;%LIBRARY_LIB:\=/%/cmake/glog;%LIBRARY_LIB:\=/%/cmake/gflags ^

No ideas anymore...

Maybe you need to quote the full path expression?
-DCMAKE_PREFIX_PATH="%LIBRARY_LIB:\=/%/cmake;%LIBRARY_LIB:\=/%/cmake/glog;%LIBRARY_LIB:\=/%/cmake/gflags" ^

Maybe you need to quote the full path expression?

Thanks for the tip, but no dice, unfortunately.


Cron jobs don't kick off at the expected time

I am having an issue trying to figure out the Cron job's scheduled time. My Crawlab is sitting on a digital ocean droplet and hosted in Amsterdam which is on GMT+2 (same as my timezone). When I schedule the Cron at * 16 * * * expecting it to kick off at 16:00 in the afternoon it runs at 08:30 in the morning, I have attempted to kick it off this morning by moving the cron job time every hour and it just doesn't kick off, yet it moves the cron info after the time passes till tomorrow - for example, I attempted to kick it off this morning at 11:00 am, 11:00 came and went and the cron info moved till tomorrow but no task kicked off.
My question is - is the cron info based on your server's time or what would the cron job timezone be so I can adjust accordingly? I am running crawlab v0.6.0

Hi @DevinSmith69,
I think the cron time is based on your local server time zone and please check your host server's tz config and make sure it aligns with your current time zone.

For those using docker/docker compose, set the TZ environment variable to fix this. The documentation could benefit from adding this info. I assume it is set to the developers point of origin.

Ahhh, thank you @oyhel - think that is my issue - will check it out


Fix off by one in binary_all

This fixes #4 and adds a test that would have caught it.

Looks like you are right. Thanks!


Theme Transition

Changing the theme from bluish to greenish
Use sea green as the color..See code for hex
Must change text colors which are bluish

resolved


not all volume mounts are readonly

We want the language here to allow for distributions to support volume mounts that support write operations (ie. emptyDir)
Thus we moved the requirements to the volume's source

cc @knative/trademark-committee

/LGTM

+1

/LGTM

/approved


mysql: type "time" unsupported Scan error

Your issue may already be reported! Please search on the issue track before creating one.
What version of Go are you using (go version)?
1.13
Which database and its version are you using?
mysql 5.7
Please provide a complete runnable program to reproduce your issue. IMPORTANT
package main

import (
	"github.com/jinzhu/gorm"
	_ "github.com/jinzhu/gorm/dialects/mssql"
)

var db *gorm.DB

func init() {
	var err error
	db, err = gorm.Open("mysql", "gorm:gorm@tcp(localhost:9910)/gorm?charset=utf8&parseTime=True")
	if err != nil {
		panic(err)
	}
	db.LogMode(true)
}

type Demo{
  Time time.Time `gorm:"type:time"` // mysql dataType is time
}

func main() {
        d:=Demo{}
	db.First(&d) // panic ,  unsupported Scan error, storing driver.Value type []uint8 into type *time.Time
}

你好，问题解决了吗，我也碰到了这种

@wuyouxin 没有从根本上解决，hacking方法如下：
type Demo{
  Time string  `gorm:"type:time"` // time.Time => string
}

mark

mark