[STORM-2773]If a drpcserver node in cluster is down,drpc cluster won't work if we don't modify the drpc.server configuration and restart the cluster

https://issues.apache.org/jira/browse/STORM-2773
There is a cluster which includes three nodes named storm1,storm2,storm3.And there is a drpcserver in every node,a worker which has been started on strom1.When strom1 was down with hardware failure,my drpc topology won't work,when I send request from drpcclient.
As storm1 was down,so the worker will be restarted on another node,but it can't Initialize successfully because the call method of Adder will throw a RuntimeException,when drpcspout try to connect to storm1,so the worker will restart again.
In conclusion,If a drpcserver node in cluster is down,drpc cluster won't work until we modify the drpc.server configuration and restart the cluster,but in production,it's difficult to restart whole cluster.
So I think we should catch the RuntimeException and log it,and the drpc topology will work normally.

You are also going to need to fix the checkstyle errors.

@revans2
I have fix the checkstyle errors and log the exception.Could you help me review this PR again?

Actually I have dug deeper, and I think we want to do this differently, although it will be just as simple of a change.
Currently a ConnectException is thrown deep down that end up being wrapped and bubbles up to be a RuntimeException which you are catching and simply not adding that client to the list of clients.  The issue I am concerned about is what happens if the node is temporarily down and will come back up.  Before this would cause the worker to restart until it was back up (not ideal but would work).  With this patch we will end up never having the spout connect to that drpc server.
I think the proper fix is actually here
https://github.com/liu-zhaokun/storm/blob/d92f1a9c8d7442d4959fec57813fc5de42b179a9/storm-client/src/jvm/org/apache/storm/drpc/DRPCInvocationsClient.java#L44
If instead of letting the Exception bubble up and be handled by the Spout we instead will catch/log it and set the AtomicReference to null.  This will allow the spout to do its reconnect logic periodically to try and recover, but will still keep the spout up and running if a node is completely removed.
Longer term it might be interesting to try and replace the config with a location in zookeeper where the DRPC servers can register, so we can add/remove DRPC servers as needed and the system automatically adjusts.

In the long term, it's difficult for us to improve drpc. But would you like to help merge this PR?

@liu-zhaokun I'm not sure you understood my comment from before.  This current code has a bug in it.  If a DRPC server is down when the spout comes up, even temporarily down, it will never try and connect again.  This is not acceptable.  We need it to keep trying periodically.  I think we can fix it by making the change at
https://github.com/liu-zhaokun/storm/blob/d92f1a9c8d7442d4959fec57813fc5de42b179a9/storm-client/src/jvm/org/apache/storm/drpc/DRPCInvocationsClient.java#L44
instead.

@revans2
I try to fix this bug follow your advice,but I found the original bug occurred in line 41 https://github.com/liu-zhaokun/storm/blob/d92f1a9c8d7442d4959fec57813fc5de42b179a9/storm-client/src/jvm/org/apache/storm/drpc/DRPCInvocationsClient.java#L41 drpcinvocationclient wan't to establish connection with the thrift server.And I am not sure we should fix this bug in line 41.Could you give me some suggestion?Thanks.

@liu-zhaokun You are correct I had forgotten the ThriftClient establishes the connection then initializes the _protocol member and then finally the Client itself is created which will read from the protocol.
The solution is that we need a way to not call reconnect from the constructor of ThriftClient.  We have that in a few cases for testing/local mode
https://github.com/liu-zhaokun/storm/blob/d92f1a9c8d7442d4959fec57813fc5de42b179a9/storm-client/src/jvm/org/apache/storm/security/auth/ThriftClient.java#L73-L75
But I think we want another parameter to the constructor to say don't do this, so we can try and connect ourselves and if it fails we can ignore it and go on.

@revans2
Do you mean there no need to reconnect when I create a DRPCInvocationClient instance?

Currently ThriftClient will connect to the server itself in the constructor.  What we want to do is to optionally not do that, and instead let the DRPCInvocationsClient do it in a location where it can catch the exception and ignore it, because we know it is going to try again to reconnect later.

Hi,@revans2,I'm not sure whether the ci's failure related to me.And I have add a retry to DRPCInvaction,could you help me to review it?

@HeartSaVioR
Hi,are you available to help me review this PR?

@HeartSaVioR  @revans2
Hi,are you available to help me review this PR?

@revans2
Hi,revans! I guess you  forgot this PR after a long time.I just want to know if this PR is available because I used to work hard to make it. Even if you think it is not good enough, I hope you can reply to me rather than ignore it.


luv test error

When I compile luv in debug mode using vs2015 and run test, an error window was propmoted, the message is
"
Debug Error!
File: e:\github\luv\src\fs.c
Line:366
Runtime check failure #3 - the variable 'buf' is being used without being initialized.
"
I check the code, it seems that it is an error.

When you get this runtime error are you passing a single string to write or a list of strings?

I just use lua tests\run.lua to do official test.
the output is like below when error occur
"
ok 13 fs - read a file sync
{ fd = 3 }
{
stat = {
nlink = 1,
ino = 158118,
mtime = table: 0061A860,
gid = 0,
mode = 33206,
size = 5867,
dev =<PHONE_NUMBER>,
gen = 0,
rdev = 0,
atime = table: 0061A3B0,
blksize = 2048,
uid = 0,
type = "file",
flags = 0,
ctime = table: 0061A630,
birthtime = table: 0061A608,
blocks = 16
}
}
{ chunk = 5867 }
ok 14 fs - read a file async
"
it seems this code
"
uv.fs_write(fd, {"with\n", "more\n", "lines\n"}, -1)
"
cause this problem

Yep, that's what I thought.  Try with this patch and it should fix it https://github.com/luvit/luv/commit/118f4b4270f3e6d73fe5ee54fff9b2b9f8e19d97


Automated AppVeyor tests extras bucket

@lukesampson I added more tests to this bucket because it was really messy. 😐 https://github.com/lukesampson/scoop-extras/commit/da5dd74b1ec4a0adaf371b66d8d861c7c5abc829
I wanted to ask if you could setup appveyor to run automated tests on this repo? :smile:

Thanks! I've added an AppVeyor project here. Is anything else needed?

Maybe for the versions bucket. I also added those test there.

I can't work out how to add scoopinstaller/versions repo to AppVeyor — I only see my GitHub user repos.

Hm, maybe you have to log in with the organization account?

@deevus are you able to add AppVeyor projects for scoopinstaller GitHub org, since you set it up?

@lukesampson I don't appear to have access. Looks like they're set up under
your account. I think you'll need to invite me to the team?
On Mon, May 8, 2017 at 7:22 PM Luke Sampson<EMAIL_ADDRESS>wrote:

@deevus https://github.com/deevus are you able to add AppVeyor projects
for scoopinstaller GitHub org, since you set it up?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lukesampson/scoop-extras/issues/398#issuecomment-299816953,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA0QguweRmfXw50cTnsb1Orfa_qx4IgOks5r3t69gaJpZM4NTOP3
.

If I authorise GitHub and allow access to scoopinstaller I can see them to create projects, though

Ah okay thanks. I can see scoopinstaller repos now, not sure how you did that @deevus but thanks. https://ci.appveyor.com/project/lukesampson/versions is set up now @r15ch13.

Thanks 👍


add project page for BAZ

Created project page for Bernd Alois Zimmermann Complete Edition. Cleanup of projects on the wiki.

Thank you both for the additon of the BAZ project.
@bwbohl Could you please have a look at the project's members and update if needed?

The contributors list is not complete and depending on the goals not up to date. Should all project contributors be listed also past employees.
Also I'm not sure about the correct english terminology of the individual contributors; research associate vs. assistant and what about undergraduate or student assistants?
The text seems to be a translation of a text from the project website, which is copyrighted. The image is copyrighted, too…
I will check on this with the project lead.

Sidenote: would prefer to rename page to baz-ga instead of baz as this is the official abbreviation of the project.

@bwbohl if you want to update the text for that page please go ahead. I was trying to use the project descriptions that I found on the project sites, but since you are closer to the project it would be great if you can provide the description.


Case sensitive router

The routing is case sensitive and I am not quite sure if it's intended to be like this and url's should not be case sensitive.
I have this route:
{ route: "fertigung/waage/:id", moduleId: "fertigung/waage", name: "waage", title: "Waage", nav: false, settings: { hasSubMenu: false, isSubMenu: true, parent: 'Fertigung' }

and I have a link dependent on that route:
 Waage
As you can see I have written "Waage" with a capital "W" in the html link, which results to a redirect to the default route. Shouldn't the route itself be case insensitive?

@bryanrsmith I'm thinking that our pattern matching should be case-insensitive but that when we pass the parsed parameters on to the activate method, they should retain their original casing. What do you think?

I agree.

If this is changed I would like to have an option for the router to remain case sensitive.

I would also be interested in the router being case insensitive.

I have a strange behaivor with the router tests.
I have add after it('should navigate to named routes', this test:
it('should navigate to case sensitive routes', (done) => {
  const options = {};
  spyOn(history, 'navigate');

  router.configure(config => {
      config.map({ name: 'test', route: 'Test/Test', moduleId: './test' });
    })
    .then(() => {
      router.navigate('/Test/Test', options);
      expect(history.navigate).toHaveBeenCalledWith('#/Test/Test', options);
      history.navigate.calls.reset();

      router.navigate('/test/Test', options);
      expect(history.navigate).toHaveBeenCalledWith('#/test/test', options);
      history.navigate.calls.reset();

      done();
    });
});

And the new test passed ... Should this fail?

I'd love to see some movement on this feature.

I would like to help to implement it but have no experience with tests. Anybody can tell me how to test it in order to try implement it?

Take a look at some of the existing tests in the repo and see how they are put together. If you have questions, I'm sure @bryanrsmith can help you out.

Yes, I have looked to the rest of the test, and I have copied the should navigate to absolute paths test, I have wrote the avobe test and I think it works.
The problem is that it should fail but passed ... I don't understand :D. If I write the test with other route, for example:
it('should navigate to case sensitive routes', (done) => {
  const options = {};
  spyOn(history, 'navigate');

  router.configure(config => {
	  config.map({ name: 'test', route: 'Test/Test', moduleId: './test' });
	})
	.then(() => {
	  router.navigate('/Test/Test222222', options);
	  expect(history.navigate).toHaveBeenCalledWith('#/Test/Test', options);
	  history.navigate.calls.reset();

	  router.navigate('/test/Test22222222', options);
	  expect(history.navigate).toHaveBeenCalledWith('#/test/test', options);
	  history.navigate.calls.reset();

	  done();
	});
});

Both fails, the problem is when I try to test the case sentive route navigate its works ... like if the router is case insensitive ... I don't get it to fail with case sensitive routes ...

I'm thinking ... sould be this issue related to "route-recognizer"??
I think yes.

I have created a pull request on "route-recognizer" to be case insensitvie: https://github.com/aurelia/route-recognizer/pull/20
If this pull request is accepted will be easy to enable it by each route.

@bryanrsmith or @jedd-ahyoung Can you review the PR?

@EisenbergEffect Left a few comments for minor issues.
I'm not sure about the API, though. It looks like we're adding an API for specifying whether or not the router is case sensitive, and then letting you specify an override on each individual route. IMO we should just make the router case insensitive by default, and let routes specify otherwise. I think that would be a less surprising default, and putting the only API on the route config means I don't have to look elsewhere to figure out how a particular route will behave.

@bryanrsmith I'm agree with your comments on the PR.
I'm agree about API notes too, if @EisenbergEffect is agree too I can make the changes.
@EisenbergEffect are you agree?

@tolemac Yes, I agree. Let's proceed 😄
Also, I noticed that you haven't yet signed our CLA. We would appreciate it if you would consider doing that for us. Before signing, please take a few minutes to read our contributing guidelines. These guidelines will help get you up to speed on how our community likes to operate and how the pull request process works. Once you have read that, assuming you are in agreement, simply sign our online CLA.
Please CC myself and @bryanrsmith when you have signed the CLA and made the change that bryan recommends.

@EisenbergEffect and @bryanrsmith my apologies, I didn't read the contributing guidelines. Well, I have read it now, and I have cancel the pull request and I have done other following the guidelines.
I have signed the CLA too.
Here is the new pull request: https://github.com/aurelia/route-recognizer/pull/21

Well, the changes on route-recognizer aren't enougth to close this issue.
We need to make changes on the router too. I think to add "caseSensitive" property to the RouteConfig interface. Then, on Router.addRouter method pass this property to route recognizer:
let state = this._recognizer.add({path: path, handler: config, caseSensitive: config.caseSensitive});

I'm trying to write a spec to test the router to navigate to case sensitive routes.

@bryanrsmith, @EisenbergEffect I just finished the changes on the router. I have replace the route-recognizer module by the new and it works.
How to do it? have I to wait to you accept the route-recognizer and then make the pull request to the router??

@bryanrsmith Can you review?
@tolemac Go ahead and add a PR the second set of changes to the router.

Done.


coveralls is no longer working

Probably related to the latest changes in travis-cargo.

Which change in travis-cargo?

Not sure, just noticed that the failure seems to be caused by the incorrect args being passed to kcov.

Might be related to https://github.com/huonw/travis-cargo/issues/54

Opened huonw/travis-cargo#55.

I just read about grcov in the unstable book. I wonder if that could help us here.


Update todoist

I've done a bit more digging, and discovered that they don't offer direct downloads anymore for their latest versions (6.1.1 at the moment). I propose that this cask simply be removed.


Explicitly use iloc for row indexing within read_sql_table()

When I was attempting to read from my database, I was getting repeated mysterious 'KeyError': 0.0. After digging around, it seems that for some reason the line of code head[:0] was attempting label-based indexing instead of row-based indexing.
The expected behaviour of that line is to return an empty dataframe that we can derive the metadata from; by explicitly using head.iloc[:0] we can guarantee that behaviour.
I have not been able to explain why my returned dataframe behaves strangely in this way; I have not been able to recreate it when I create a dataframe outside of this dask data pull, but this seems like a zero-loss change to make as the desired behaviour is always that of .iloc[:0].

[x] Tests added / passed
[x] Passes black dask / flake8 dask

@KrishanBhasin thanks for the PR.  This looks good to me but I am curious what version of Pandas you were using.  Can you post the version ?

Yeah, this seems harmless, but it'd be nice to know why it was failing in
the first place. I haven't been able to come up with anything.
On Thu, Oct 17, 2019 at 1:17 PM Benjamin Zaitlen<EMAIL_ADDRESS>wrote:

@KrishanBhasin https://github.com/KrishanBhasin thanks for the PR. This
looks good to me but I am curious what version of Pandas you were using.
Can you post the version ?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/pull/5500?email_source=notifications&email_token=AAKAOIT7JTKYJHFE5WZY4SLQPCT4JA5CNFSM4JB3TKDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBRBKWY#issuecomment-543298907,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAOIVQZCF6NFRMX2S5NYLQPCT4JANCNFSM4JB3TKDA
.

$ pip freeze | grep pandas
 pandas==0.24.2

Yeah it was really weird. When @permanentfoot2 and I used pd.DataFrame.from_dict() to make some dataframes, no matter how we manipulated the them we couldn't get them to throw the error.
I pickled the dataframe out of my debugging session and had a quick play with it and didn't find much too weird with it.
I figured there was too much point diving that deep because switching to .iloc[] seemed like an easy fix.

It throws the same error on pandas==0.25.1
Looks like it may be an incident of this bug?
H/T @PermanentFoot2

We dug down a bit more to find that df[:0] errors if the index has type Float64Index and is not monotonic - we raised a pandas issue here.
Reproducible example:
>>> df = pd.DataFrame({'a': [3.0, 1.0, 2.0], 'b':[5, 6, 7]}).set_index('a')
>>> df[:0]

KeyError: 0.0

Any reason not to merge this in ?

Any reason not to merge this in ?

Not from me - my comment above was just for curiosity

We'd love to see it merged!
I'm installing & running from my fork to get around this issue at the moment.

Thanks @KrishanBhasin.

Thanks @KrishanBhasin !  Merging now

Thanks for merging! And thanks to @PermanentFoot2 too!


https://github.com/facebook/facebook-android-sdk/commit/c83e8b4558a85646390e85bc559a1f86ef73024d

https://github.com/facebook/facebook-android-sdk/commit/c83e8b4558a85646390e85bc559a1f86ef73024d

https://github.com/facebook/facebook-android-sdk/commit/c83e8b4558a85646390e85bc559a1f86ef73024d

are you ok?


Define API-Spec with Swagger

Based on db-diagram on: https://dbdiagram.io/d/62660b3a1072ae0b6ade54ac and business process explained in https://docs.google.com/presentation/d/1nHWAZBuamOwS5tzknU4GUIkwcBwJPjSXjFaP4Ohaz08/edit#slide=id.g125f8848f67_0_18, create an api-spec with swagger.
With these rules:

All of doctor can access and modify all of medical-record related features, but no master data;
Admins can only access read-only the MR's and modify the master data;
The login access must be placed on different routes, though it's will be returned the same content.

Finished with #17.


[Bug]: No colour one some hours in energy graph

Contact Details
<EMAIL_ADDRESS>VRM portal ID
d41243cd7f0b
Country / region
Sweden - SE3 (se-3)
B max
20
TB max
5
FB max
9
TG max
2
FG max
11
Battery costs
0.0001
Buy price
(p+0.027692+0.041281)*1.25
Sell price
(p-0.02527+0.00)*1.25
feed-in possible
yes
feed-in control
yes
Version
0.1.6
What happened?
I got some hours that are white in the energy graph, see below

There is a white unlabeled section in the popup legend and only forecasts for PC yield and consumption is shown during some hours. The white section seems to equal the consumption forecast in the graph.
/Kaj
Relevant log output
No response
Screenshots
![DESCRIPTION](LINK.png)

Looking at the Overviwe graph the system SoC is flat during most of the same time

And the Dynamic ESS schedule is locked to 63%

The white value is essentially the part below both of the lines (consumption and pv yield). The part between should be filled as well, but when price is below zero, things become special. We are looking into improving the graph in such cases.


Definition object does not support primitives type schema object fully (e.g. string minLength)

According to this (https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#definitionsObject), i should be abel to specify a primitive type.
For example, if I want to share the following string type (with validation on maxLength) within a few different operation params, I have to repetitively declare them inline instead of using one "Definition".
"shortName": {
        "type": "string",
        "maxLength": 25
}

It's supported when using JSR303.

@danieljsun - have you tried it?

Closing this one due to lack of activity. Please reopen if needed.


get balance

when i conneted the wallet and use the addree to receive tokens ,how can i see my token banlance,i did not find the api method in the reference

@Antorny-Leung To see your token balance after connecting your wallet, you typically need to use the wallet's interface or a blockchain explorer that supports the tokens you're dealing with.


Bug: REPL does not load when clicking on a repl from repl list

REPL does not load when clicking on a repl from repl list(on apps).
It just shows progress bar progressing
https://svelte.dev/apps

I believe this is fixed along with the site migration.


Make MPs usable for Snapshot governance

Currently staked SNT is an ERC20 token (or not?) - however, I am not sure it is implemented correctly as the functions changing balances do not utilize the ERC20 functions.
However, a more necessary feature is to make MPs work with governance solutions (Snapshot rankings is the short-term target). Therefore, we need to provide public read functions to access balances - whether this is using ERC20 or not depends on the additional complexity.
We might consider using ERC20Votes.sol for futureproofing if proper decentralized governance were a long-term target. However, in such a case the contract can be. updated.

I'm flagging this with low priority for as we need to discuss what governance exactly will entail but for now I think we should focus on getting the staking functionality right first.

The governance is a separate process that currently uses Snapshot for voting on NIPs posted on discourse. Not sure how this will evolve, however, having at least ERC20 read functionality for MP balance would suffice for now.

It would be possible to include balanceOf functions in the StakeManager, which would return whatever we want. transfer would not be implemented.

Added label of feature, as it would be a feature, and refactor, as it would probably need refactor (in case we need to inherit Votes.sol from OpenZeppelin)

We'll likely need Snapshot compatibility in the foreseeable future. Votes.sol would be futureproofing that can, however, be addressed by migration to a new contract if necessary.

Unassigning @3esmit for now as this is not actually being worked on atm.

MP will not be part of governance. If at all, it's going to be XP * SNT.
This stuff is not actually something we're working on atm moment and it seems unclear if we will be going down that path.
Closing this issue for now and will revisit once this is more relevant.


Changes to tests

During my runs on my server I found a few situations, which I think are not tests the specification correctly. Please review these

Going to close this because I think there are more things to change in this code than what's been put in here.


Plugin error when starting CLN

Running CLN v22.11rc1 and rust-teos at 832dd71ae5b8b7875f892d12851379349812b0cd
Printed to console when starting lightningd:
Error: Got unexpected message Err(invalid type: string "cln:getmanifest#13", expected usize) from lightningd

CLN logs:
2022-11-13T01:15:07.362Z INFO    plugin-watchtower-client: Killing plugin: exited before replying to getmanifest

Yep, I'm aware of this.
Looks like this is due to the last release of CoreLN using the latest version of cln-plugin (the Rust interface for plugins) while this was publicly released yesterday, so our plugin os not.
This should be solved once we patch the watchtower-plugin to match the introduced changes.
Quoting @cdecker from CoreLN Discord:

sr_gi: Has something recently changed in how plugins interact with lightningd? I've upgraded from v<IP_ADDRESS> to v0.12.1 and suddenly I'm getting:

Error: Got unexpected message Err(invalid type: string "cln:getmanifest#14", expected usize) from lightningd

2022-11-04T13:51:02.113Z INFO    plugin-watchtower-client: Killing plugin: exited before replying to getmanifest

cdecker: That the rust cln-plugin library. I think it most likely is the switch from numeric-only call IDs to serde_json::Value. So using the version in the repo will fix that. Also I'll publish the latest version to crates.io once I get home.


Fatal Error after upgrading to nuxt 2.10.2

After upgrading from nuxt 2.10.1 to 2.10.2 our build fails with the following error:
ERROR in ./node_modules/vuetify/src/components/VBadge/VBadge.sass (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-1-1!./node_modules/postcss-loader/src??ref--6-oneOf-1-2!./node_modules/sass-loader/dist/cjs.js??ref--6-oneOf-1-3!./node_modules/vuetify/src/components/VBadge/VBadge.sass)
Module build failed (from ./node_modules/css-loader/dist/cjs.js):
ValidationError: CSS Loader Invalid Options

options should NOT have additional properties

    at validateOptions (/…/node_modules/schema-utils/src/validateOptions.js:32:11)
    at Object.loader (/…/node_modules/css-loader/dist/index.js:44:28)

After hours of investigation I found out that removing this module let work the build again. But removing this module also means removing global sass variables and mixins etc. So could not be a  solution.
The error comes from css-loader and maybe it depends on a breaking change of handling loader-options
I compared the versions of css-loader and it seems that this could be the cause:
yarn why css-loader with 2.10.1:
$ yarn why css-loader
yarn why v1.19.1
[1/4] 🤔  Why do we have the module "css-loader"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Reasons this module exists
   - "vuepress#@vuepress#core" depends on it
   - Hoisted from "vuepress#@vuepress#core#css-loader"
info Disk size without dependencies: "328KB"
info Disk size with unique dependencies: "2.43MB"
info Disk size with transitive dependencies: "6.63MB"
info Number of shared dependencies: 32
=> Found "<EMAIL_ADDRESS>info This module exists because "@storybook#vue#@storybook#core" depends on it.
info Disk size without dependencies: "144KB"
info Disk size with unique dependencies: "2.29MB"
info Disk size with transitive dependencies: "6.45MB"
info Number of shared dependencies: 32
=> Found "<EMAIL_ADDRESS>info This module exists because "nuxt#@nuxt#webpack" depends on it.
✨  Done in 1.23s.

and after upgrading to 2.10.2
$ yarn why css-loader
yarn why v1.19.1
[1/4] 🤔  Why do we have the module "css-loader"...?
[2/4] 🚚  Initialising dependency graph...
[3/4] 🔍  Finding dependency...
[4/4] 🚡  Calculating file sizes...
=> Found<EMAIL_ADDRESS>info Has been hoisted to "css-loader"
info Reasons this module exists
   - Hoisted from "@storybook#vue#@storybook#core#css-loader"
   - Hoisted from "nuxt#@nuxt#webpack#css-loader"
info Disk size without dependencies: "124KB"
info Disk size with unique dependencies: "2.21MB"
info Disk size with transitive dependencies: "6.37MB"
info Number of shared dependencies: 32
=> Found "<EMAIL_ADDRESS>info This module exists because "vuepress#@vuepress#core" depends on it.
✨  Done in 1.00s.

I'm at a loss and need some tips.

The solution depends on a version mismatch of core-js. Nuxt uses per default version 2 and Storybook version 3. So to solve the issue I have to follow this note from @nuxt/babel-preset-app:

Note: Since core-js@2 and core-js@3 are both supported from Babel 7.4.0, we recommend directly adding core-js and setting the version via the corejs option.

I get a working environment again with Nuxt 2.11.0 using this update on my nuxt.config.js:
yarn add --dev core-js@3 @babel/runtime-corejs3

export default {
  …
  build: {
    babel: {
      presets() {
        return [
          [
            '@nuxt/babel-preset-app',
            {
              corejs: { version: 3 }
            }
          ]
        ]
      }
    }
  }
}


Upsight.com

Lawsuit Alleges Disney Illegally Tracks Children Via Apps

from https://android.izzysoft.de/help?topic=modwarnings#upsight
We should block the whole domain (Upsight.com)

Beer @beerisgood we aren't in the business of 'disappearing' companies from the internet.  So we aren't going to block the home domain unless they use that to deliver adware or scumware.
The references provided by the link above are from 2017.
This is a very stale trail, without specific actionable domains.
Closing.


1.0 Quick Start with Google Kubernetes Engine:  Istio GKE Deployment Manager fails

Describe the bug
The 1.0 GKE Quick Start works up to this point:  https://preliminary.istio.io/docs/setup/kubernetes/quick-start-gke-dm/#launch-deployment-manager
When I try to open the 'Istio GKE Deployment Manager' I get a blank page
Expected behavior
Something useful should be generated
Steps to reproduce the bug
Start from the top of https://preliminary.istio.io/docs/setup/kubernetes/quick-start-gke-dm and work your way down to opening the 'Istio GKE Deployment Manager'
Version
$ istioctl version
Version: master-20180709-09-15
GitRevision: 7bba996125b321cbe694e057e1e8f0dfc4386593
User: root@1be68a119004
Hub: gcr.io/istio-release
GolangVersion: go1.10.1
BuildStatus: Clean

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"dd5e1a2978fd0b97d9b78e1564398aeea7e7fe92", GitTreeState:"clean", BuildDate:"2018-04-19T00:05:56Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10+", GitVersion:"v1.10.5-gke.0", GitCommit:"f4c74e18e57148052c59cc0467bb7e99dcc46399", GitTreeState:"clean", BuildDate:"2018-06-21T14:11:26Z", GoVersion:"go1.9.3b4", Compiler:"gc", Platform:"linux/amd64"}

Is Istio Auth enabled or not?
No
Environment
GKE

We need to update this file once the 1.0 release is created
https://github.com/istio/istio/blob/master/install/gcp/deployment_manager/istio-cluster.jinja#L107

cc @salrashid123

For me the deployment manager starts, but fails with this error. I think because the debian8 images are not longer available, so the DM template needs to be updated AFAICT.
"ResourceType":"compute.v1.instance","ResourceErrorCode":"404","ResourceErrorMessage":{"code":404,"errors":[{"domain":"global","message":"The resource 'projects/debian-cloud/global/images/family/debian-8' was not found","reason":"notFound"}],"message":"The resource 'projects/debian-cloud/global/images/family/debian-8' was not found","statusMessage":"Not Found","requestPath":"https://www.googleapis.com/compute/v1/projects/REDACTED/zones/us-central1-a/instances","httpMethod":"POST"}}

Reopen for tracking 1.0 merge.


[Core][MachO] Implement endianess check (& then integrate it into MachO & Fat related plugins)

Implement endianess check (& then integrate it into MachO & Fat related plugins)

Implement endianess check - this has been done by @xTachyon.
Fat plugin has been unified with MachO.
Endianess integration check via new functions needs to be added into MachO plugin.


xfreerdp: error exit during start of click/drag in Excel (reproducible)

Describe the bug
Error exit of xfreerdp during normal use.
To Reproduce

Initiate a click drag of a column name in the pivot table configuration dialog in Excel.
xfreerdp exits.

Expected behavior
xfreerdp does not exit.
Screenshots
N/A
Application details

Version of FreeRDP 2.0.0
Command line used xfreerdp /v:$host -sec-nla -encryption /w:3840 /h:2160 /log-level:trace /scale-device:140 /scale:140 /scale-desktop:175 /gfx:RFX /audio-mode:1 /bitmap-cache /heartbeat /dynamic-resolution
output of /buildconfig

This is FreeRDP version 2.0.0 (2.0.0)
Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CAIRO=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_TSMF_AVAILABLE=0 WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=ON WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=TRUE WITH_FFMPEG=TRUE WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_GSTREAMER_0_10=ON WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENCL=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=ON WITH_PAM=ON WITH_PCSC=ON WITH_PROFILER=OFF WITH_PROXY=ON WITH_PROXY_MODULES=OFF WITH_PULSE=ON WITH_SAMPLE=OFF WITH_SANITIZE_ADDRESS=OFF WITH_SANITIZE_ADDRESS_AVAILABLE=1 WITH_SANITIZE_MEMORY=OFF WITH_SANITIZE_MEMORY_AVAILABLE=1 WITH_SANITIZE_THREAD=OFF WITH_SANITIZE_THREAD_AVAILABLE=1 WITH_SERVER=ON WITH_SERVER_CHANNELS=ON WITH_SERVER_INTERFACE=ON WITH_SHADOW=ON WITH_SMARTCARD_INSPECT=OFF WITH_SOXR=OFF WITH_SSE2=ON WITH_SWSCALE=OFF WITH_THIRD_PARTY=OFF WITH_VAAPI=ON WITH_VALGRIND_MEMCHECK=OFF WITH_VALGRIND_MEMCHECK_AVAILABLE=1 WITH_WAYLAND=OFF WITH_WINPR_TOOLS=ON WITH_X11=ON WITH_X264=OFF WITH_XCURSOR=ON WITH_XDAMAGE=ON WITH_XEXT=ON WITH_XFIXES=ON WITH_XI=ON WITH_XINERAMA=ON WITH_XKBFILE=ON WITH_XRANDR=ON WITH_XRENDER=ON WITH_XSHM=ON WITH_XTEST=ON WITH_XV=ON WITH_ZLIB=ON
Build type:          RelWithDebInfo
CFLAGS:               -fPIC -Wall -Wno-unused-result -Wno-unused-but-set-variable -Wno-deprecated-declarations -fvisibility=hidden -Wimplicit-function-declaration -Wredundant-decls -g
Compiler:            GNU, 9.2.1
Target architecture: x64

OS version connecting to: Windows 10 1910
If available the log output from a run with /log-level:trace

[14:25:34:995] [29504:29507] [DEBUG][com.freerdp.core.heartbeat] - received Heartbeat PDU -> period=1, count1=8, count2=8
[14:25:34:995] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:995] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:009] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:009] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:029] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:029] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:069] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:069] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:089] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:089] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:109] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:109] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:129] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:129] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:149] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:150] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:169] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:169] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:189] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:189] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:209] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:209] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:229] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:229] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:249] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:249] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:269] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:269] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:289] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:289] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:309] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:309] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:329] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:329] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:34:349] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:34:349] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:369] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:369] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:389] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:389] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:409] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:409] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:429] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:429] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:449] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:449] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:469] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:469] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:489] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:489] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:509] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:509] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:529] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:529] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:549] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:549] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:569] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:569] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:589] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:589] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:609] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:609] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:629] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:629] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:649] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:649] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:669] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:669] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:689] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:689] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:709] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:709] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:729] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:729] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:749] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:749] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:769] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:769] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:789] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:789] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:809] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:809] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:829] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:829] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:849] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:849] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:869] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:869] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:889] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:889] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:890] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:890] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:890] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:890] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:909] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:909] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:929] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:929] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:949] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:949] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:969] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:969] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:989] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:989] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:009] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:009] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:017] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:018] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:018] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:018] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:021] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:021] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:021] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:021] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:025] [29504:29507] [DEBUG][com.freerdp.core.heartbeat] - received Heartbeat PDU -> period=1, count1=8, count2=8
[14:25:35:025] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:025] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:029] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:029] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:033] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:033] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:033] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:033] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:037] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:037] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:037] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:037] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:039] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_Pointer_Set
[14:25:35:039] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_Pointer_Set
[14:25:35:039] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_process_x_events
[14:25:35:039] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_process_x_events
[14:25:35:041] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_Pointer_New
[14:25:35:041] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_Pointer_New
[14:25:35:041] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_Pointer_Free
[14:25:35:041] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_Pointer_Free
[14:25:35:041] [29504:29507] [ERROR][com.freerdp.core.fastpath] - Fastpath update UNKNOWN [c] failed, status 0
[14:25:35:041] [29504:29507] [ERROR][com.freerdp.core.fastpath] - fastpath_recv_update_data: fastpath_recv_update() - -1
[14:25:35:041] [29504:29507] [ERROR][com.freerdp.core.fastpath] - fastpath_recv_update_data() fail
[14:25:35:041] [29504:29507] [ERROR][com.freerdp.core.transport] - transport_check_fds: transport->ReceiveCallback() - -3
[14:25:35:041] [29504:29507] [ERROR][com.freerdp.core] - freerdp_check_fds() failed - 0
[14:25:35:041] [29504:29507] [ERROR][com.freerdp.client.x11] - Failed to check FreeRDP file descriptor
[14:25:35:041] [29504:29507] [DEBUG][com.freerdp.core.rdp] - rdp_recv_callback: CONNECTION_STATE_ACTIVE - rdp_recv_pdu() - -3
[14:25:35:041] [29504:29507] [DEBUG][com.freerdp.core.rdp] - transport_check_fds() - -1
[14:25:35:041] [29504:29507] [DEBUG][com.freerdp.core] - rdp_check_fds() - -1
[14:25:35:041] [29504:29507] [INFO][com.freerdp.client.common] - Network disconnect!
[14:25:35:043] [29504:29560] [DEBUG][com.freerdp.channels.drdynvc.client] - close_channel_iface: id=7
[14:25:35:043] [29504:29560] [DEBUG][com.freerdp.channels.drdynvc.client] - close_channel_iface: id=15
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_lock_x11_:	[1] from xf_Pointer_Free
[14:25:35:049] [29504:29507] [TRACE][com.freerdp.client.x11] - xf_unlock_x11_:	[0] from xf_Pointer_Free

Desktop (please complete the following information):

OS: Ubuntu
Version 19.10

Additional context
gfx:AVC444 also fails.
I can reproduce the crash with version 2.0.0. However a build I made previously with 2.0.0-rc4 works fine launching with the same configuration.
2.0.0-rc4-1090-g71feb974a
git: 71feb974ac9854a6df390ed17715080f12dd1ad0

The problem is here https://github.com/FreeRDP/FreeRDP/blob/2.0.0/libfreerdp/codec/color.c#L338
(gdb) info args
pDstData = 0x7fffe8662890 ""
DstFormat = 537168008
nDstStep = 400
nXDst = 0
nYDst = 0
nWidth = 100
nHeight = 63
xorMask = 0x0
xorMaskLength = 0
andMask = 0x7fffe8658e70 "\324I"
andMaskLength = 882
xorBpp = 24
palette = 0x7fffe8352dc8
(gdb) bt
#0  0x000055555564c7fb in freerdp_image_copy_from_pointer_data
    (pDstData=0x7fffe8662890 "", DstFormat=537168008, nDstStep=400, nXDst=0, nYDst=0, nWidth=100, nHeight=63, xorMask=0x0, xorMaskLength=0, andMask=0x7fffe8658e70 "\324I", andMaskLength=882, xorBpp=24, palette=0x7fffe8352dc8)
    at libfreerdp/codec/color.c:338
#1  0x00005555555b47fd in xf_Pointer_New (context=0x555555a06ab0, pointer=0x7fffe8658b60) at client/X11/xf_graphics.c:263
#2  0x00005555556b27ad in update_pointer_large (context=0x555555a06ab0, pointer_large=0x7fffe8387a20) at libfreerdp/cache/pointer.c:186
#3  0x0000555555619425 in fastpath_recv_update (fastpath=0x555555a22f10, updateCode=12 '\f', s=0x555555a26f90) at libfreerdp/core/fastpath.c:479
#4  0x0000555555619cc6 in fastpath_recv_update_data (fastpath=0x555555a22f10, s=0x7fffe83603c0) at libfreerdp/core/fastpath.c:628
#5  0x0000555555619e22 in fastpath_recv_updates (fastpath=0x555555a22f10, s=0x7fffe83603c0) at libfreerdp/core/fastpath.c:659
#6  0x0000555555612d8c in rdp_recv_fastpath_pdu (rdp=0x555555a0bf20, s=0x7fffe83603c0) at libfreerdp/core/rdp.c:1461
#7  0x0000555555612df2 in rdp_recv_pdu (rdp=0x555555a0bf20, s=0x7fffe83603c0) at libfreerdp/core/rdp.c:1469
#8  0x0000555555613926 in rdp_recv_callback (transport=0x555555a183c0, s=0x7fffe83603c0, extra=0x555555a0bf20) at libfreerdp/core/rdp.c:1646
#9  0x000055555561f196 in transport_check_fds (transport=0x555555a183c0) at libfreerdp/core/transport.c:1061
#10 0x0000555555613c42 in rdp_check_fds (rdp=0x555555a0bf20) at libfreerdp/core/rdp.c:1706
#11 0x00005555556021b3 in freerdp_check_fds (instance=0x555555a067d0) at libfreerdp/core/freerdp.c:333
#12 0x000055555560242d in freerdp_check_event_handles (context=0x555555a06ab0) at libfreerdp/core/freerdp.c:381
#13 0x00005555555bfe04 in xf_client_thread (param=0x555555a067d0) at client/X11/xf_client.c:1620
#14 0x00005555557f6ae6 in thread_launcher (arg=0x555555a4e7d0) at winpr/libwinpr/thread/thread.c:327
#15 0x00007ffff5f4d669 in start_thread (arg=<optimized out>) at pthread_create.c:479
#16 0x00007ffff5b08323 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb)

@wpbrown sorry, you just found the position it is breaking after the fact.
Could you check if fastpath_recv_update_data or update_pointer_large are failing?

Looks like the assumption of color pointers always having a xorMask is wrong. need to investigate.

@akallabeth Tested your PR, it's working fine with that. Thank you.


feat(#69): Skip integration tests for RuleAllTestsHaveProductionClass check

Add isIntegrationTest check for test characteristics and skip all integration tests in RuleAllTestsHaveProductionClass check.
History:

feat(#69): Add tests for integration tests
feat(#69): Ignore integration tests for RuleAllTestsHaveProductionClass
feat(#69): append all-have-production-class integration test with a new it case which should be ignored
feat(#69): Add resources for the future unit tests
feat(#69): implement isIntegrationTest method for BytecodeTestClassCharacteristics
feat(#69): implement isIntegrationTest method for CharacteristicsJavaParser
feat(#69): fix all qulice suggestions

Closes: #69

PR-Codex overview
Focus of this PR:
This PR focuses on adding support for identifying and categorizing integration tests in the codebase.
Detailed summary:

Added isIntegrationTest() method to TestClassCharacteristics interface.
Implemented isIntegrationTest() method in JavaParserClass and CharacteristicsJavaParser classes.
Added test cases to verify the behavior of isIntegrationTest() method.
Added a new IntegrationTest class to test integration test characteristics.
Updated BytecodeTestClassCharacteristicsTest to include tests for integration tests.
Added a new IntegrationTest class in the src/it/all-have-production-class directory.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)

@rultor release, tag is 1.0.0, title is 1.0.0

@rultor release, tag is 1.0.0, title is 1.0.0

@volodya-lombrozo OK, I will release it now. Please check the progress here


HARDWARE_ERROR - TIMEOUT ON LOGICAL UNIT error with CDs

Version
20231201 via Media Preservation Frontend version 3.0.2 net 8.0 win x64 on windows 10
Describe the bug
I’m getting HARDWARE_ERROR - TIMEOUT ON LOGICAL UNIT error with the most recent version of DIC. I tested previous disks I successfully dumped, and the error also appears with them. This issue isn’t present with the 20230909 version. I managed to dump the disk with that version with no errors. This issue only appears with CDs, DVDs work with no problems.
Drive Info
BW-16D1HT with RipSharks firmware 3.10
Screenshots
Check if subchannel pack mode is supported
LBA[000000, 0000000]: [F:ReadCDForCheckingSubPack][L:1235]
	Opcode: 0xbe
	ScsiStatus: 0x02 = CHECK_CONDITION
	SenseData Key-Asc-Ascq: 04-3e-02 = HARDWARE_ERROR - TIMEOUT ON LOGICAL UNIT
lpCmd: be, 00, 00, 00, 00, 00, 00, 00, 01, f8, 04, 00
dwBufSize: 2448
[WARNING] This drive does not support subchannel pack mode

Disc title
Casio Utilities CD - fx-9860G
Disc ringcode
Mastering Code: CDCSOG497A01A	C12072601
Mould SID Code: IFPI T116
Log file
fx-9860G.zip

Fixed: fail to dump when LG/ASUS drive is used.
DiscImageCreator_test.zip

This issue isn’t present with the 20230909 version.

Yes. I added at 20231201.

I found a bug with the test version. While trying to dump Virtua Fighter 2 after reaching “Checking SubRtoW (Track)  1/24” I get an “HARDWARE_ERROR - TIMEOUT ON LOGICAL UNIT” error and then I got continuously “MEDIUM_ERROR - L-EC UNCORRECTABLE ERROR” errors. This doesn’t happen with the 20230909 version, just like the bug I reported initially on this thread.
Drive Info
BW-16D1HT with RipSharks firmware 3.10
Screenshots
LBA[000000, 0000000]: [F:ReadCDForCheckingSubPack][L:1236]
	Opcode: 0xbe
	ScsiStatus: 0x02 = CHECK_CONDITION
	SenseData Key-Asc-Ascq: 04-3e-02 = HARDWARE_ERROR - TIMEOUT ON LOGICAL UNIT
lpCmd: be, 00, 00, 00, 00, 00, 00, 00, 01, f8, 04, 00
dwBufSize: 2448

LBA[144194, 0x23342]: [F:ReadCDForCheckingSubRtoW][L:1283]
	Opcode: 0xbe
	ScsiStatus: 0x02 = CHECK_CONDITION
	SenseData Key-Asc-Ascq: 03-11-05 = MEDIUM_ERROR - L-EC UNCORRECTABLE ERROR
lpCmd: be, 00, 00, 02, 33, 42, 00, 00, 01, f8, 01, 00
dwBufSize: 2448

Disc title
Virtua Fighter 2, XPLOSIV version
Disc ringcode
Mastering Code: (kdg-NL) 01 EI 1305
Mastering SID Code: IFPI L371
Mould SID Code: IFPI 5599
Log file
SEGA_VF2.zip
The log files might be incomplete because I closed the cmd window before it finished on its own. The “MEDIUM_ERROR - L-EC UNCORRECTABLE ERROR” errors seemed to be endless.

DiscImageCreator_test.zip
changed: pack mode supported drive only checks SubRtoW.
fixed: fail to dump when mixed mode disc is dumped by LG/ASUS drive. (http://forum.redump.org/post/113592/#p113592)

DiscImageCreator_test.zip
fixed: error occurs when checks adr by LG/ASUS drive. (http://forum.redump.org/post/113615/#p113615)


'error' event handler in 0.10

I've been using handlers like these in 0.9:
ws.on('message', fn1)
ws.on('close', fn2)
ws.on('error', fn3)

Since 0.10, there's an exception thrown when attempting to register the 'error' event in above fashion:
Registering more than one listener to a WebSocket is not supported.

Is this intentional and if so, how would one access client-side errors in 0.10?

Oh, and I also have a wss.on('error', fn4), maybe the check is confusing these two handlers?

If you try the nodejs/client.js and add an error handler it works. Try and enter an invalid address and it will call the error handler. Can you try and do some debug prints and see what happens?

The removeListener is probably not implementing the 'error' string though. Are you relying on that?

Working on a minimal example now, sec.

No example yet, but I noticed that the node process starts saturating one CPU core on the first request, no matter if I try to attach that error handler or not. I'm attaching multiple websocket servers to a mix of http/https servers, will test further with less servers.

Sounds like something strange, will check this out tomorrow.

Minimal example for the error handler issue:
"use strict";

var server = require("http").createServer(function(_, res) {
  res.end(`<!DOCTYPE html><head></head><body></body>`);
});

server.listen(9000, "<IP_ADDRESS>", function() {
  var Wss = require("uws").Server;
  var wss = new Wss({server: server});
  wss.on("connection", function(ws) {
    console.log("ws connection");
    ws.on("message", console.log.bind(null, "message"));
    ws.on("close", console.log.bind(null, "close"));
    ws.on("error", console.log.bind(null, "error"));
  });
  wss.on("error", console.log.bind("wss error"));
});

Couldn't reproduce the CPU hang with it, but that one appears with just one server at least.

Ah okay I see. You are registering an 'error' to a server socket. Yeah that won't work, the server websockets do not have any error. This should be fixed so that it is ignored just like before.

This should be fixed in v0.10.3


Findbugs warning for floating point comparison in mergeFrom

Findbugs complains that for a class like this:
@FreeBuilder
public abstract class Wheel {
    abstract double diameter();
    public static class Builder extends Wheel_Builder {}
}

The generated java code contains floating point comparisons for equality:
public Wheel.Builder mergeFrom(Wheel value) {
    Wheel_Builder _defaults = new Wheel.Builder();
    if (_defaults._unsetProperties.contains(Wheel_Builder.Property.DIAMETER)
        || value.diameter() != _defaults.diameter()) {
      diameter(value.diameter());
    }
    return (Wheel.Builder) this;
  }

Note that both autoValue and Immutable use this code pattern:
// autoValue
 return (Double.doubleToLongBits(this.diameter) == Double.doubleToLongBits(that.diameter()));
// Immutables
  private boolean equalTo(ImmutableWheel another) {
    return Double.doubleToLongBits(diameter) == Double.doubleToLongBits(another.diameter);
  }

Same for float, I guess.
Also see http://stackoverflow.com/questions/3832592/test-for-floating-point-equality-fe-floating-point-equality

Note that the equals comparison:
´´´
@Override
public boolean equals(Object obj) {
if (!(obj instanceof Wheel_Builder.Value)) {
return false;
}
Wheel_Builder.Value other = (Wheel_Builder.Value) obj;
return Objects.equals(diameter, other.diameter);
}
´´´
using Objects.equals() might be suspect to the same vulnerabilities.

This was an intentional choice when first made, to treat all NaNs as equals. However, Objects.equals defers to Double.equals which uses doubleToLongBits, so we regressed on that decision anyway.

Lies! Lies! It's just a bug. It'll be exciting trying to write a unit test for this 😄

Hmmm, doubleToLongBits actually makes all NaNs use the same bit pattern anyway. Not even sure I can write a unit test for this.

I've remembered the way equality treats NaN backwards. Primitive equality comparison always treats NaNs as not matching. Unit testing should be easy then.

I'm going to go ahead and delete all my comments, whistle nonchalantly, and pretend this never happened.

Good spot, thanks! Object.equals does the right thing, fortunately.


All files

Images strings should be localized
77 files in the AZ-204-DevelopingSolutionsforMicrosoftAzure.fr-fr-OLPRODLOC  02_Target\AZ-204-DevelopingSolutionsforMicrosoftAzure.fr-fr-OLPRODLOC\Instructions\Labs\media folder from 10_create_sb_namespace.png until Lab12-Diagram.png (77 files)

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

The image locfile show blocked status, I re-set prehandoff status, waiting for check in to locrepo. ICMS QUERY


Transpile to ES5 before publishing the package

Maybe the solution is a npm script prepublish running npm run build that uses babel-cli and also change the package.json main field to the transpiled code. wdyt?

sorry, I just read the README.md 🤦♂ :
Note: v3+ targets ES6, and is therefore incompatible with the master branch of uglifyjs. You can either:

use babili, which supports ES6
use the harmony branch of uglifyjs
stick with the 2.x.x branch

and https://github.com/ericnorris/striptags/issues/27#issuecomment-280038900


blog series on how to make sundial

i have this demo sundial http://jeromeetienne.github.com/demo.sundial/

it looks good, but it isnt complete

what about a blog on how to do it

all around light and time

a step by step and you end up with something nice on screen

people would love that

people would learn tquery along the way

present it like that

you got this old incomplete demo
never released because incomplete
but it looks quite good on screen.
so i dont want to drop it. i want make something with this stuff.
So here we go
i will write a serie about making this sundial in tquery
and we complete this demo together :)

think about the steps

how to make each part of the demo

make plugins along the way

winwin situation:

i complete the demo
i improve tquery code
i document tquery
people learns and can use 3D


cmdAdd results provide results for last delegate

As far as I can tell, the returned "result" field for cmdAdd is the result from the last delegate which was added.  I wonder if it'd make sense to embed the other results as well in this reply.  Callers who know to look for these fields would be able to observe the network details for each CNI plugin individually.  Callers who don't know to look for these fields, assuming golfing JSON unmarshaling is used, would not be impacted.
Similar idea to what @mcastelino was suggesting at https://github.com/intel/vhost-user-net-plugin/issues/2
What do you think?

Let have an internal discussion on this.


Is 3D supported?

All examples are written for 2D. Trying with own 3D data was not working.
Could it be, that 3D geometries are not fully supported?

Could you give us some more details? Which operations are you trying with 3D data?

select esri.ST_PolyFromWKB(esri.ST_AsBinary(esri.ST_GeomFromText('polygon ((0 0, 10 0, 0 10, 0 0))')));  -- 2d works --> returns a bytestring
select esri.ST_PolyFromWKB(esri.ST_AsBinary(esri.ST_GeomFromText('polygon ((0 0 1, 10 0 2, 0 10 3, 0 0 4))')))  -- 3d doesn't work --> returns NULL

@git-aybo Does this work?
select esri.ST_GeomFromText('polygon z ((0 0 1, 10 0 2, 0 10 3, 0 0 4))')

It works now fine, also with m and zm. Thank you for the quick solution .


Is there any way to make custom response?

Hello! Thanks for awesome package.
I want to make custom response
ASIS
{
  "validation_error": {
    "query_params": [
      {
        "loc": ["age"],
        "msg": "value is not a valid integer",
        "type": "type_error.integer"
      }
    ]
  }
}

TOBE(or some other fomat, maybe)
{"error" : "validation_error",
"desc" : "some_my_custome_message"}

Thanks for reading this.

+1
I don't see any way to do this  in the current verison

So, I have been thinking about this one and wanted to throw out an idea. There already exists the FLASK_PYDANTIC_VALIDATION_ERROR_STATUS_CODE configuration value that lets you change what the status code is. What if we added another configuration value like FLASK_PYDANTIC_VALIDATION_ERROR_EXCEPTION that, if set to true, would just raise an exception (to be defined) containing the fields that are in the current json error response. If the user set that config value, it is their responsibility to set the flask exception handler for that exception type, then they can return whatever type of response they want.


Interference with Developer Console and Handlebars.js Functionality

Issue Summary:
When the System Sculpt AI plugin is enabled in Obsidian, it interferes with the Developer console. Specifically, it stops console.log messages from other plugins and prevents the use of variables when getting or setting with Handlebars.js.
Steps to Reproduce:

Enable the System Sculpt AI plugin in Obsidian.
Attempt to log messages using console.log from another plugin.
Try to use variables with Handlebars.js for getting or setting values.

Expected Behavior:

console.log messages from other plugins should be visible in the Developer console.
Variables should be usable with Handlebars.js without any issues.

Actual Behavior:

console.log messages from other plugins do not appear in the Developer console.
Variables cannot be used effectively with Handlebars.js, disrupting functionality.

Environment:
Obsidian version: v1.6.5
System Sculpt AI plugin version: 0.4.7
Operating System: Ubuntu 22.04
Additional Information:
Disabling the System Sculpt AI plugin resolves the issue, indicating a conflict between the plugin and the Developer console/Handlebars.js functionality.

Great catch; one of the blindspots since I always have dev mode enabled. I'll have this fixed in the next update :)

Fixed in update later today.


Rework multiple choice quizzes

Description
Rework the multiple choices to make them more appealing than simple checkboxes.
Acceptance Criteria

[ ] multiple choice quizzes have been reworked

@LG1401 What should MC quizzes have, instead of the checkboxes?


Support repeat function

Changelog category (leave one):
Support repeat function , as described in issue: https://github.com/Kyligence/ClickHouse/issues/297
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
...

Information about CI checks: https://clickhouse.tech/docs/en/development/continuous-integration/

Can one of the admins verify this patch?

Can one of the admins verify this patch?

test this please

test this please with 975

test this please with 975

test this please with 975

test this please with 975


Update styleguide links in CONTRIBUTING.md

Files were added into directory engineering/

@SimonHFrost Good catch - thanks! :+1:

Thanks for the PR @SimonHFrost !


Add API method to check, whether a query structure is selected

Solution
Add ketcher API method isQueryStructureSelected. Returns true if selected structure has query properties and false otherwise.

Tested.


allow glsify(path.join(

glsify(path.join(__dirname, 'shader.frag'))

fails at the moment
I added path to staticModule like brfs does it.

Pushed as 5.1.0, thanks!

Ooh, this is cool!


Drag-drop or copy-pasted images break the editor

Hi @JiHong88,
I have found a couple of issues with images.
First is that any images that are either copy-pasted or dragged and dropped into the editor appear to break all the standard image functionality. I.e. none of the resize works or any other image features.  To replicate just find any online content that contains an image, copy it and paste it into the editor. You'll find attempting to resize to say 25% wont work.
Second is that you dont seem to be able to place the cursor at the beginning of the image and move it down. When an image is inserted as the first thing into the editor an empty pararaph is created on top of the image (I suspect as a way to allow the cursor to be placed above the image for new lines) which cannot be removed (unless you direct edit HTML).  However, it would be far better to remove the auto addition of the paragraph and allow the user to place the cursor at the start of the image where pressing enter would move the image down (create paragraphs above).
Regards,
Derrick

Hi @DeZZar
Thank you very much for your feedback.
Fixed in v2.15.3
Thank you.


Query returns null on similar type with different request variables

Discussed in https://github.com/FormidableLabs/urql/discussions/2767

Originally posted by Svarto October 27, 2022
Hi all, apologies if I am using the wrong terminology, I hope I can explain this as it is a headscratcher which I would really appreciate anyone's help untangling.
TLDR: When pulling one Query with a smaller subset of data, when navigating to another screen with a different Query that pulls the some data typename but with a different subset of requested data - the query returns data: null with no error and in Urql Devtools I get "undefined" for that typename.
Longer explanation:
I have Query 1 (see below for query), that is a infinite list with date as the cursor. When I pull this on a page all is fine. However, when I scroll down and pull the next data (i.e. update the cursor with the last items "created_at" number to move the cursor down the list) I get the data for Query 1, but if I navigate to another page with Query 2 (see below for query) it returns data: null. This happens even when I can confirm that the cursor argument for Query 2 is updated, so it is not the same as Query 1.
I receive no error, stale is false, and I just get back data: null. If I try to refresh the query by updating the cursor for Query 2 to new Date() (i.e. update it to NOW), then the same thing happens. See below for screenshot from Urql Devtools (note that the date format is different from React Native new Date(), which ends with Z, compared to the created_at, i.e. when the cursor is moved down the list to fetch a next batch of items, which ends with 00-00. Not sure if that is relevant):

Query 1:
// Used in collection bottom sheet
export const GET_OWN_RECIPES_WITH_COLLECTIONS = gql`
  query GetAllUserRecipes(
    $user_id: uuid!
    $cursorArgument: timestamptz
    $collection_id: Int
  ) {
    recipe(
      order_by: { created_at: desc }
      limit: 15
      where: {
        created_at: { _lt: $cursorArgument }
        user_id: { _eq: $user_id }
      }
    ) {
      dishtype
      created_at
      id
      user_id
      title
      draft
      images {
        id
        image_id
        user_id
      }
      collections_recipes(where: { collections_id: { _eq: $collection_id } }) {
        collections_id
        type
        recipe_id
      }
    }
  }
`;

Query 2:
// Used in my recipe feed
export const GET_USER_RECIPES = gql`
  query GetAllUserRecipes(
    $user_id: uuid!
    $cursorArgument: timestamptz
    $current_user: uuid
  ) {
    recipe(
      order_by: { created_at: desc }
      limit: 15
      where: {
        created_at: { _lt: $cursorArgument }
        user_id: { _eq: $user_id }
      }
    ) {
      dishtype
      created_at
      id
      user_id
      title
      draft
      images {
        image_id
        id
        user_id
      }
      recipe_likes_aggregate {
        aggregate {
          count
        }
      }
      recipe_likes(where: { user_id: { _eq: $current_user } }) {
        recipe_id
        user_id
      }
      cooked_recipes(where: { user_id: { _eq: $current_user } }) {
        id
      }
      cooked_recipes_aggregate {
        aggregate {
          count
        }
      }
    }
  }
`;

Happy to give more information, I am really scratching my head what is going wrong here...thanks for any help!!

Hey for issues we require reproductions 😅

Hey for issues we require reproductions 😅

🙃 Very fair! I'll close it for now until I have time to create a reproduction!


Health check and scheduler stuck initializing

Rancher Version:
1.2.1
Docker Version:
1.12.3
OS and where are the hosts located? (cloud, bare metal, etc):
Ubuntu 14.04 aws
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
3 node ha with external db
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Install 1.2.1 add hosts
Results:
Scheduler and health check stuck initializing
Expected:
Started
Healthcheck logs
12/19/2016 2:10:21 PMtime="2016-12-19T19:10:21Z" level=info msg="Starting haproxy listener"
12/19/2016 2:10:22 PMtime="2016-12-19T19:10:22Z" level=info msg="healthCheck -- starting haproxy\n * Starting haproxy haproxy\n   ...done.\n"
12/19/2016 2:10:22 PMtime="2016-12-19T19:10:22Z" level=info msg="Scheduling apply config"
12/19/2016 2:10:22 PMtime="2016-12-19T19:10:22Z" level=info msg="healthCheck -- reloading haproxy config with the new config changes\n[WARNING] 353/191022 (32) : config : 'option forwardfor' ignored for proxy 'web' as it requires HTTP mode.\n"
12/19/2016 2:10:27 PMtime="2016-12-19T19:10:27Z" level=info msg="Scheduling apply config"
12/19/2016 2:10:27 PMtime="2016-12-19T19:10:27Z" level=info msg="healthCheck -- no changes in haproxy config\n"
12
scheduler logs
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Listening for health checks on <IP_ADDRESS>:80/healthcheck"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Connecting to cattle event stream."
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Subscribing to metadata changes."
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Adding resource pool [storageSize] with total 74347999 and used 0 for host 28a04038-6ef8-4b3f-a084-8c7a39e31bd3"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 24 for host 28a04038-6ef8-4b3f-a084-8c7a39e31bd3"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Adding resource pool [cpuReservation] with total 4000 and used 0 for host 28a04038-6ef8-4b3f-a084-8c7a39e31bd3"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER>4 and used 0 for host 28a04038-6ef8-4b3f-a084-8c7a39e31bd3"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER>4 and used 0 for host 73d68cf1-7f80-4dc8-81e7-2bc51b403f33"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Adding resource pool [storageSize] with total 74445799 and used 0 for host 73d68cf1-7f80-4dc8-81e7-2bc51b403f33"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 22 for host 73d68cf1-7f80-4dc8-81e7-2bc51b403f33"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Adding resource pool [cpuReservation] with total 4000 and used 0 for host 73d68cf1-7f80-4dc8-81e7-2bc51b403f33"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Initializing event router" workerCount=100
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Connection established"
12/19/2016 2:10:46 PMtime="2016-12-19T19:10:46Z" level=info msg="Starting websocket pings"

Looks like you have the same issue as me: https://github.com/rancher/rancher/issues/7130

Looks like a few of us are experiencing the same issue with the health check, scheduler and load balancer getting stuck in 'initializing' status, which at least is a small crumb of comfort that it is likely to be a common cause/effect rather than necessarily something very site specific (still might be of course).
Hopefully Rancher will be able to provide some solid advice ASAP as for us it is a total blocker for using v1.2 (we don't see this for v1.1.4)
Fraser.

Adding a few more details.
I stood up a simple Rancher cluster (1 server + 2 nodes) with a local Db, just for testing.
It comes up almost ok, apart from three things ...

  The scheduler container doesn’t start, it’s just stuck initializing. The logs show this :-

18/12/2016 22:31:34time="2016-12-18T22:31:33Z" level=info msg="Listening for health checks on <IP_ADDRESS>:80/healthcheck"
18/12/2016 22:31:34time="2016-12-18T22:31:33Z" level=info msg="Connecting to cattle event stream."
18/12/2016 22:31:34time="2016-12-18T22:31:33Z" level=info msg="Subscribing to metadata changes."
18/12/2016 22:31:34time="2016-12-18T22:31:34Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 9 for host e5f1c264-f1ca-4ace-bc3e-927459bd9add"
18/12/2016 22:31:34time="2016-12-18T22:31:34Z" level=info msg="Adding resource pool [cpuReservation] with total 2000 and used 0 for host e5f1c264-f1ca-4ace-bc3e-927459bd9add"
18/12/2016 22:31:34time="2016-12-18T22:31:34Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host e5f1c264-f1ca-4ace-bc3e-927459bd9add"
18/12/2016 22:31:34time="2016-12-18T22:31:34Z" level=info msg="Adding resource pool [storageSize] with total 5818134 and used 0 for host e5f1c264-f1ca-4ace-bc3e-927459bd9add"
18/12/2016 22:31:34time="2016-12-18T22:31:34Z" level=info msg="Initializing event router" workerCount=100
18/12/2016 22:31:34time="2016-12-18T22:31:34Z" level=info msg="Connection established"
18/12/2016 22:31:34time="2016-12-18T22:31:34Z" level=info msg="Starting websocket pings"
18/12/2016 22:49:59time="2016-12-18T22:49:59Z" level=info msg="Adding resource pool [instanceReservation] with total 1000000 and used 4 for host 0cdada1a-1e59-4889-9939-3a2d2329839f"
18/12/2016 22:49:59time="2016-12-18T22:49:59Z" level=info msg="Adding resource pool [cpuReservation] with total 2000 and used 0 for host 0cdada1a-1e59-4889-9939-3a2d2329839f"
18/12/2016 22:49:59time="2016-12-18T22:49:59Z" level=info msg="Adding resource pool [memoryReservation] with total<PHONE_NUMBER> and used 0 for host 0cdada1a-1e59-4889-9939-3a2d2329839f"
18/12/2016 22:49:59time="2016-12-18T22:49:59Z" level=info msg="Adding resource pool [storageSize] with total 5817597 and used 0 for host 0cdada1a-1e59-4889-9939-3a2d2329839f"

  I created a global scope load-balancer (linked to an nginx service (port 80:80) that came up no problem – pulled from ECR) but it is also stuck initializing’. Log shows this :-

18/12/2016 22:39:13time="2016-12-18T22:39:13Z" level=info msg="KUBERNETES_URL is not set, skipping init of kubernetes controller"
18/12/2016 22:39:13time="2016-12-18T22:39:13Z" level=info msg="Starting Rancher LB service"
18/12/2016 22:39:13time="2016-12-18T22:39:13Z" level=info msg="LB controller: rancher"
18/12/2016 22:39:13time="2016-12-18T22:39:13Z" level=info msg="LB provider: haproxy"
18/12/2016 22:39:13time="2016-12-18T22:39:13Z" level=info msg="starting rancher controller"
18/12/2016 22:39:13time="2016-12-18T22:39:13Z" level=info msg="Healthcheck handler is listening on :10241"
18/12/2016 22:39:16time="2016-12-18T22:39:16Z" level=info msg=" -- starting haproxy\n[ALERT] 352/223916 (27) : Starting frontend GLOBAL: cannot bind UNIX socket [/run/haproxy/admin.sock]\n"
18/12/2016 22:39:16time="2016-12-18T22:39:16Z" level=info msg=" -- reloading haproxy config with the new config changes\n[WARNING] 352/223916 (38) : config : 'option forwardfor' ignored for proxy 'default' as it requires HTTP mode.\n"

  On the first host, the health-check container is running fine, but the one on the second is stuck initializing. The logs show this :-

18/12/2016 22:50:24time="2016-12-18T22:50:23Z" level=info msg="Starting haproxy listener"
18/12/2016 22:50:28time="2016-12-18T22:50:28Z" level=info msg="healthCheck -- starting haproxy\n * Starting haproxy haproxy\n   ...done.\n"
18/12/2016 22:50:28time="2016-12-18T22:50:28Z" level=info msg="Scheduling apply config"
18/12/2016 22:50:28time="2016-12-18T22:50:28Z" level=info msg="healthCheck -- reloading haproxy config with the new config changes\n[WARNING] 352/225028 (31) : config : 'option forwardfor' ignored for proxy 'web' as it requires HTTP mode.\n"
18/12/2016 22:50:38time="2016-12-18T22:50:38Z" level=info msg="Scheduling apply config"
18/12/2016 22:50:38time="2016-12-18T22:50:38Z" level=info msg="healthCheck -- no changes in haproxy config\n"
18/12/2016 22:51:52time="2016-12-18T22:51:52Z" level=info msg="Starting haproxy listener"
18/12/2016 22:51:52time="2016-12-18T22:51:52Z" level=info msg="healthCheck -- starting haproxy\n[WARNING] 352/225152 (16) : config : 'option forwardfor' ignored for proxy 'web' as it requires HTTP mode.\n"
18/12/2016 22:51:52time="2016-12-18T22:51:52Z" level=info msg="Scheduling apply config"
18/12/2016 22:51:52time="2016-12-18T22:51:52Z" level=info msg="healthCheck -- no changes in haproxy config\n"

I can ping between the ip-sec containers on separate hosts (in both directions), but NOT between an ipsec container and any other container nor between any other two containers (not ipsec).
Here’s a picture :-

More details
I created a new group of nodes (1 server + 2 nodes) this time using docker 1.10.3 in case using 1.12.x was a problem.
No change, health-check and scheduler containers still stuck in 'initializing' state.
OS: RHEL 7.3
Platform: AWS
Rancher Version: 1.2.1
Docker Version : tried 1.12.3 and 1.10.3 (same behavior)
Docker Compose version: 1.9.0 (also 1.8.1 on the docker 1.10.3 hosts).

Rancher have confirmed a problem with networking that should be fixed in v1.2.2 (expected in the next few days).

I have fixed our problem, it was two fold:

you must use an ALB with aws installations, do NOT use an ELB
when you register your hosts you need to set the cattle_agent_ip to the private ip of the ec2 instance, don't let it auto-discover as it uses the public ip instead.

@leodotcloud @ibuildthecloud

We already use an ALB and none of our instances have a public IP.

I had this problem at one point when I registered the first two agents in quick succession.  Removing one of the agents and re-adding it seemed to fix that problem.

Hi I'm having an issue like this...I have a rancher-server on a local server. What I'm trying to do is add my AWS host with his public IP but they can reach my local server only by VPN connection. (When I execute the command generated by the UI of Rancher to add a host the detected cattle agent IP is his IP of the VPN even when use the public IP of the host for cattle agent IP).
Every host has a OpenVPN client that is running on background providing a tun0 interface, I have a VPN server on AWS that allows connection between clients and redirect all the traffic through the VPN. Also my local server is connected to that VPN.
The AWS hosts get added but when the second host is added the health check stays on initializing and there is no connection between hosts. Any idea of what is happening? What I'm doing is wrong?

@ElPsyCongro maybe you have to open udp ports 500 and 4500 for hosts inter-communication?
http://rancher.com/docs/rancher/v1.6/en/hosts/custom/#security-groupsfirewalls

@ElPsyCongro Can you open a new issue if you are experiencing problems? Along with all the used versions etc we can investigate.

@iamfreee All my hosts have the UDP port 500 and 4500 open on the inbound rules in AWS. There is no communication between health check containers and there should be able to ping from the Shell to the IP of the other container.

@superseb Yes I will, but the thing is that I don't know if what I'm trying to do is correct or it should work.
Remember that I'm using an OpenVPN client connection on the local server in order to be reachable from anyone that has a OpenVPN client configuration to the OpenVPN server hosted on AWS. So my hosts has an OpenVPN client config and they are connected to the VPN but as I said the connection between my hosts in Rancher doesn't happen.

Ran into this issue again today, this time, none of the tips helped me. I explicitly had to tell the agent to use the IPv4 address as CATTLE_AGENT_IP. I double checked the UDP ports being open for the IPv6 which is being used by Rancher by default, but couldn't get it to work. Anyway, maybe that helps somebody else.


Unable to login, as it requires to pass email check even if it's disabled

Fixed the issue in the patch


Web demo: Bug when labeling with radio buttons

From @SyRenity in this mailing list thread:

Install the latest docker version:
docker pull bamos/openface

Launch the docker as bash (regular launch didn't work for me, complaining it can't find th):
docker run -t -i -p 8000:8000 -p 9000:9000 bamos/openface /bin/bash

Click train to start training

Stop training after 7-10 images

Add a name

Click in trained faces list on the added name radio button to assign name to face

Demo crashes with:
2016-01-21 20:51:46+0000 [-] /usr/local/lib/python2.7/dist-packages/sklearn/cross_validation.py:417: exceptions.Warning: The least populated class in y has only 1 members, which is too few. The minimum number of labels for any class cannot be less than n_folds=5.
2016-01-21 20:51:46+0000 [OpenFaceServerProtocol,0,<IP_ADDRESS>] Unhandled Error

exceptions.ValueError: The number of classes has to be greater than one; got 1

By the way, if I follow the demo youtube video usage flow (first creating a name then training), it works fine.

I'm also facing the same issue ....
Any hints on how to solve ?

@bamos any ideas ?

I got this problem as well

Hello ,
This is because SVM by default is multiclase and as the error says you are trying to train only one class.
See official documentation. http://scikit-learn.org/stable/modules/generated/sklearn.svm.SVC.html
In a nutshell you try to train a model with only one person.
If for some reason, so you need, I can think of a dirty trick.
Creates 2 folders one with data of the person to identify and another with data that you will call unknown.
I apologize for my English, I do not speak it natively.


tree mortality: code some basic summary charts

@alyssaterrell , @ValentineHerr ,
It would be helpful to write scripts to make some charts summarizing results of the mortality census, similar to the ones we used to produce: mortality rate and biomass mortality for each census-- total and by genera, and some additional ones breaking up by genera for Fraxinus and Quercus.  It would also be nice to include an update of the one in the Shenandoah paper.
The main purpose is to keep us up to date with the results of the census/ allow us to pick out any interesting new patterns. It's also handy to have nice graphs ready for presentations, tours, etc.
This is not particularly urgent, but if its ready tomorrow I'd use them for the VNPS tour (replacing some ugly ones I threw together quickly).

Working on reproducing this now:

@teixeirak,
For mortality rates, If I subset for species and censuses that started with > 100 individuals I have a similar results but if I subset for species that always had N>100 to start with (at each census), Ulru disappears ( Ulru went below 100 individuals at the end of 15-16 census and that is why we don't see anything for those years in the plot above).
Any preference on how to handle that ?

@teixeirak, to clarify,
Two options:
A - we ignore mortality rates for one census because there was not n >100 a the beginning of that census,  but we still plot the other censuses for that species. It would look like this:

B- We ignore the species all together is one of the census did not have n>100. It would look like this:

@teixeirak,
For mortality rates, If I subset for species and censuses that started with > 100 individuals I have a similar results but if I subset for species that always had N>100 to start with (at each census), Ulru disappears ( Ulru went below 100 individuals at the end of 15-16 census and that is why we don't see anything for those years in the plot above).
Any preference on how to handle that ?

Let's include ULRU (species with ≥100 individuals at start)

Let's go with option A

The plots look very nice, by the way. Thank you!

Ok I'll push them.
working on updating Shenandoah results now.

Let's put the Shenandoah results in this repo, not the Shen repo. I'm not currently planning to update the figure/ stats in that paper.

Hmm... That could get tricky....
What figures would you like here? I believe this is the only one that does not use Shenandoah data:

That's the only one I had in mind

Ok, I'll try to script it here again so that the two repos do not depend on each other.

@teixeirak, it would actually be hard/take a lot of time without updating the Shenandoah repo... I'll try to work there, on a separate branch.

It's not that important. You can just drop that one. The point was just to make some quick figures to visualize some results from the census. Since we don't have any specific use in mind right now, its not worth extra effort for this one.

ok

In the end the script ran over lunch time and here is the figure:

NOTE: Cercis went below 100 individuals after 2018.

Thanks! Which is the taxa that got up to ~7% mort rate in 2019?

Carpinus

Thanks!
@alyssaterrell , (@gonzalezeb) , any idea what's getting Carpinus?

It seems that nothing in particular gets them. Canker but not a particular pest or pathogen known.
https://edis.ifas.ufl.edu/st120
Sent from my iPhone
On Sep 27, 2019, at 8:22 PM, Kristina Anderson-Teixeira <notifications<EMAIL_ADDRESS>wrote:
CAUTION:This email originated outside the Institution. Unless you recognize the sender and know the content is safe, do not follow guidance, click links, or open attachments.
Thanks!
@alyssaterrellhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Falyssaterrell&data=02|01|gonzalezeb%40si.edu|a498d376794a451d588508d74377ae9d|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637052053618945035&sdata=Hmswhblb2GYRNH%2F01hLQGIskbQRDN571xx3AM%2F%2FFzJ4%3D&reserved=0 , (@gonzalezebhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fgonzalezeb&data=02|01|gonzalezeb%40si.edu|a498d376794a451d588508d74377ae9d|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637052053618955024&sdata=vGuZfUetCF3%2FxaW5OS4KVNHFxNFoqiMe5iasla26gqg%3D&reserved=0) , any idea what's getting Carpinus?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSCBI-ForestGEO%2FSCBI-ForestGEO-Data%2Fissues%2F18%3Femail_source%3Dnotifications%26email_token%3DAGNAWNGVLGNK3JLRMJPQX33QLZFO7A5CNFSM4I3EYHXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7ZXB6A%23issuecomment-536047864&data=02|01|gonzalezeb%40si.edu|a498d376794a451d588508d74377ae9d|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637052053618955024&sdata=bGvmHZGjkzKEuCyi%2FEoAygabxLwZVgGwEPLR0Rzo9eg%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAGNAWND4E63D4N635SNTMJTQLZFO7ANCNFSM4I3EYHXA&data=02|01|gonzalezeb%40si.edu|a498d376794a451d588508d74377ae9d|989b5e2a14e44efe93b78cdd5fc5d11c|0|0|637052053618955024&sdata=lr00Ux%2FPXE%2BoHbH3l9A6R2z6IbwwzSzw8ATg0b418PE%3D&reserved=0.


lint code

Describe the PR
[x] Lint code
[x] Refactor annotations, struct tags to constant
Relation issue
NONE
Additional context
I will like to do more refactor but I'm afraid the review will never be done or it will require too much time.

@easonlin404 looks like Travis is getting stuck for some reason ...


Clarify testing expectations

Question asked about when testing JULES with the UM which groups are required - is it developer or just jules. This could be made clearer in the docs.
I would suggest in the Testing JULES page to add details of testing expectations and a link to the working with multi repositories page for the instructions. Probably the same for UKCA.

I think the testing expectations for KGO changes for all repos could do with being made more obvious


Make ignore main optional

Addresses https://github.com/PanagiotisPtr/cov-diff/issues/10

That integration test fail is OK. It's just failing to publish the comment - the build passed. The github action for publishing comments doesn't work on PRs from forks: https://github.com/mshick/add-pr-comment#proxy-for-fork-based-prs
Let me know if you're happy with the PR and I'll merge

Apologies, I have been sick. I addressed the comment and I think it would be ready to merge.
Thanks again!

No worries, thanks for the contribution. Looks good. I'll merge it in and if there's anything I'll push a subsequent fix (should be ok though)


Why, these two colors are not the same

You need to go to the setting of the material theme builder and check the color match option so the primary color directly set to actual value

您需要转到材质主题构建器的设置并选中颜色匹配选项，以便原色直接设置为实际值
Is this it?
Can you elaborate on that?
I don't know much about the design side.

I think you are confusing the "primary color" with the "primary color role".
When you select a primary color (in this case #673AB7) you get a tonal palette, and then one of those colors (in this case P-40, whose value is #6750a4) is used for the "primary color role".
Also, as @deweyferdinand said, if you need to more precisely choose your colors you can check the "Color match" option.

@ElianFabian is P-40 supposed to be the same color as Primary40? They seem to be different (same with S-40 vs. Secondary40, etc.)

@ElianFabian is P-40 supposed to be the same color as Primary40? They seem to be different (same with S-40 vs. Secondary40, etc.)

I used a color picker and they have the exact same hex number, you can do the same to check it.

let say we'd like to keep the color we give as the default for the p-40, does this require a new issue #featureRequest or is it a bug?