Clarify documentation for 3D Tiles styling

With the addition of vector tiles we added a lot of new styling properties to Cesium3DTileStyle but most of those are only applicable to vector tile point features. This could be clarified better in the documentation. Besides color and show which are used by all formats, each property should have a note about which tile formats they are applicable to.
vctr point feature properties: https://github.com/AnalyticalGraphicsInc/3d-tiles/tree/3d-tiles-next/Styling#vector-data
pointSize is used by both vctr point features and pnts.

@lilleyse I'll work on this update
just as a clarification regarding the documentation in the link you provided

all properties are available in point formats but only show and color are available for polygon/polyline formats, yes?
and all you want as a change is that each property now has a note stating that they're specifically only for point formats except for show and color, correct?

Yeah exactly.
The doc for verticalOrigin, for example, might look like:
        /**
         * Gets or sets the {@link StyleExpression} object used to evaluate the style's verticalOrigin property. Alternatively a string or object defining a number style can be used.
         * The getter will return the internal {@link Expression} or {@link ConditionsExpression}, which may differ from the value provided to the setter.
         *

         * The expression must return a VerticalOrigin.
         *

         *

         * This expression is only applicable to point features in a Vector tile.
         *

         ....


Add options to easily manage DB snapshots

Add invoke tasks to easily create DB snapshots and restore them.

El mar, 31 de ago de 2021 a las 08:50:56 AM, João Marques
@.***> escribió:

So, stopping it ensures all connections are closed before doing
anything. Is there a better way of ensuring this?

Yes, the only one issuing connections to db will be odoo, so just stop
odoo and it should be enough.

@Yajo I made some changes after your comments and also added a test. Can you check again please?


update read.me and dependencies

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


How to prevent failing to compile on CRA when eslint errors?

I installed the new react/CRA version (4). Right now when I have eslint errors the whole page blows and CRA fails to compile.
Sometimes I make some small test or debug something in the flow, and don't want CRA to fail the running only because of 1-2 intentional eslint errors.
Is there a possibility only to display the errors in the console, but not to fail to compile?
If it fails the npm run build it is okay.
Thanks and best regards

Add additional rules to your eslint configuration, it will overwrite error to warn. You have to specify it per rule.
rules: {
    "@typescript-eslint/no-unused-vars": ["warn"],
    ...

Hmm thanks, this is a kind of workaround, but I don't see it as real solution...

The issue with this workaround is that I extend multiple configs... I'd have to override a non-trivial number of rules.
In my case, the ideal would be to apply something like the now-deprecated eslint-loader's emitWarning: true during development. Even with Format on Save applied in my IDE, I am having to spend time fixing eslint errors for code that I am experimenting with and may never actually want to keep.
Only when I run a husky hook or in a pre-build step do I want to run a strict check with an NPM script like: "lint": "eslint --max-warnings 0 --ext .tsx,.ts ./src"

This is our exact issue as well. We updated from 3.4.3 and having the build fail for a stray unused import during development is almost hostile. There really should be an option to restore previous behavior.

This is our exact issue as well. We updated from 3.4.3 and having the build fail for a stray unused import during development is almost hostile. There really should be an option to restore previous behavior.

Couldn't agree more with this. Local development workflow now shot to pieces with this now

Burned by this since upgrading today, odd default for a development env.

This page has a comment which describes the desired behaviour from CRA < 4:
// We use eslint-loader so even warnings are very visible.
// This is why we prefer to use "WARNING" level for potential errors,
// and we try not to use "ERROR" level at all.
Was there a conscious decision to change this behaviour, or was it just left out of the new linting configuration during the migration away from eslint-loader?

This is a big stopper for me (and most likely for anyone else who extends CRA linting rules beyong it's default). Unless a solution is provied I'll have to revert to a pre 4.0 version.

Team, we are blocked by this as well. Do we have any more insight into what is going on here? What is the rational for failing the build on warnings? It would be good to know the background before we come up with next steps.
We have a large codebase that predates the introduction of eslint and a richer rule set. We keep warnings on to help with on-going clean up without failing builds.

Local development went from smooth to painful. Litteraly have to wait 10 sec for every change made because I added an extra space in my code somewhere and it doesn't compile. Can't debug properly. Rollbacking

Look at this issue : https://github.com/facebook/create-react-app/issues/9887
As they say, commenting out airbnb mentions in the extends array make things work again....

I don't even have airbnb in the extends array in my eslintrc config.
I have only have:

eslint:recommended
plugin:react/recommended
plugin:prettier/recommended

@NicoAdrian If you look at the eslint:recommended config, all rules are errors. You would need to override all of them locally - and all other errors in any other config - and turn them into warnings instead.

Linting errors didn't block me from compiling before 4.0.0, I don't plan to override settings

Having the same issue on my team - we want to enforce linting at commit/PR time, but not during active development. We would really like to ignore lint errors when running start but still keep those rules as errors in our lint config for use in a precommit hook or CI process.
I noticed under advanced configuration there is an option to compile despite having Typescript errors - TSC_COMPILE_ON_ERROR. Having a similar option for lint would be tremendous - something like LINT_COMPILE_ON_ERROR that we could set when this behavior is desired.

Used to work out the box, in the true style of CTA, now it doesn't.

This is completely unreasonable in my opinion as well. I think we also have no choice but to just roll back and wait for them to change it back.

This issue is a duplicate of: https://github.com/facebook/create-react-app/issues/9887

@pascalstr's workaround is a decent option. If you're not using typescript, add something like the following in .eslintrc.json:
{
  "rules": {
    "no-unused-vars": "warn",
    "react/prop-types": "warn"
  }
}

In my case, it's only these two that are showstoppers. It's sub-optimal and I agree with the comments above that refusing to compile in the development environment over an unused variable is pretty hostile. But you'll at least be able to compile and it's simpler than holding back indefinitely.

@webarnes but this will affect when you really want to lint your project, right? How can we configure a set of rules only for CRA that won't affect linting on CI for example?

You can write eslintrc in Javascript and export a different object in different environments. So you would have different rules in development vs. production. Again, just a stopgap. I think the real solution would be saner defaults in CRA but I also want to keep working.

Sorry you're running into this. It sounds like a duplicate of #9887. Let's consolidate the information over there if possible. Thanks!

SOLUTION

remove <React.StrictMode> from index.tsx.
in tsconfig.json add compilerOptions: { strict: false }

Sorry for being late but I think this can help others will have the same issue in the future
I only put this line ESLINT_NO_DEV_ERRORS=true in .env and worked as I expected

@niyodusengaclement Thanks, this do the job indeed!

I've done the same in my package.json, like so:
 "scripts": {
    "start": "ESLINT_NO_DEV_ERRORS='true' BROWSER=none PORT=8080 react-scripts start",
  },

And now I can run the app with npm start. However, we can't build it to send it to production. We have a lot on errors and warnings, and we do plan on fixing em. We are fixing our codebase from the ground up, and a lot remains to be cleaned, but the app is functional, and can be shipped. However, it's impossible right now, because of the build.
Looking at the node_modules/react-scripts/config/webpack.config.js file, I understand how the failOnError parameter is configured. It's at false only if it's in development AND we have the variable set. But temporaly, I want this parameter to be at true even while we create our production build. Is that possible? Can we overload part of the webpack.config.js file in our project?

 "scripts": {
    "start": "ESLINT_NO_DEV_ERRORS='true'  react-scripts start",
    "build": "DISABLE_ESLINT_PLUGIN='true' react-scripts build",
  },

Thanks, Ive been using Vite for a while and went back to CRA just to build a starter skeleton for projects that Vite can't handle and forgot how annoying that problem was and how it seems it still hasn't got a satisfactory fix yet! Your solution did the trick for now though.... thanks....

@PaulHaze I also switched to Vite, can you share what is possible at CRA, that can not be made with Vite? Just of curiosity...

@PaulHaze I also switched to Vite, can you share what is possible at CRA, that can not be made with Vite? Just out of curiosity...

Gosh I am probably the wrong person to ask. I'm still very much a beginner when it comes to programming. Especially compared to most people on here. My experience so far with Vite has been great though. Super fast, and feels a less bloated than CRA. Saying that I was working on one project with tailwind in Vite and the refresh was very slow and flickering on every save. For that one I went back to CRA and it worked fine. However since that project the issue hasn't returned and so far its playing nice with every tailwind build I've made with it.....

I fixed mine by adding ESLINT_NO_DEV_ERRORS=true and DISABLE_ESLINT_PLUGIN=true to .env, .env.development and env.production files

Install
https://github.com/bfanger/eslint-plugin-only-warn
Add only-warn to the plugins section of your .eslintrc configuration file:

{
  "plugins": ["only-warn"]
}

Failed to load plugin 'only-warn' declared in '.eslintrc.js': Cannot find module 'eslint-plugin-only-warn'


Tasmota doesn’t support resourcelinks

The beauty about updating is that something will brake.
I have updated to homebridge-hue v0.13.29 and Tasmota 10.0.0.
It looks like homebridge-hue tries to get the resourcelinks and since Tasmota doesn't support it, it cannot start.

[11/29/2021, 1:33:10 PM] [Hue] Philips hue: request 3: GET /resourcelinks
[11/29/2021, 1:33:10 PM] [Hue] Philips hue: request 3: timeout after 5 seconds
[11/29/2021, 1:33:10 PM] [Hue] Philips hue: timeout after 5 seconds - retrying in 15s

$ ph -H 192...13 get /

{
"lights": {
"234250913": {
"state": {
"on": true,
"alert": "none",
"effect": "none",
"reachable": true
},
"type": "Extended color light",
"name": "Snowflakes",
"modelid": "Generic",
"manufacturername": "Tasmota",
"uniqueid": "dc:::::2a:00:11-01"
}
},
"groups": {},
"schedules": {},
"config": {
"name": "Philips hue",
"mac": "DC:::::2A",
"dhcp": true,
"ipaddress": "192...13",
"netmask": "<IP_ADDRESS>",
"gateway": "192...1",
"proxyaddress": "none",
"proxyport": 0,
"bridgeid": "DC************2A",
"UTC": "2021-11-29T13:42:02",
"whitelist": {
"df662a": {
"last use date": "2021-11-29T13:42:02",
"create date": "2021-11-29T13:42:02",
"name": "Remote"
}
},
"swversion": "01041302",
"apiversion": "1.17.0",
"swupdate": {
"updatestate": 0,
"url": "",
"text": "",
"notify": false
},
"linkbutton": false,
"portalservices": false
}
}

At least the manufacturername is now "Tasmota". 👍

That’s a breaking change on the Tasmota side.  They used to return an empty object, see https://github.com/ebaauw/homebridge-hue/issues/512.

I increased the timeout but homebridge-hue still prevents Homebridge from starting.
I believe the root cause of this issue when Tasmota compressed more strings with UnishoxStrings: https://github.com/arendst/Tasmota/commit/0ed519184bb1c6afd050e0789bfe7a8e8cf2a7e9
It looks like resourcelinks is still supported but somehow it causes an error.

Best open an issue with Tasmota, then.

The last version of Tasmota to support resourcelinks is 9.2.0.
OTA update: http://ota.tasmota.com/tasmota/release-9.2.0/tasmota.bin
They have no plans to fix this issue so it's advised to stick with Tasmota 9.2.0.


Requests for UX tools?

Interested in developing some new tools for UX and want to get suggestions for improvements, enhancements, etc. in the UX space. Any particular needs as of right now?

I am recently looking for Open Source UX tools too.
Something with functionality of Adobe XD but working on Linux/Windows.


Write ServiceBusHubLifetimeManager

We need to implement a ServiceBusHubLifetimeManager. Some design questions:

Do we use multiple topics hashing the connection id to pick a particular topic?
Do we support partitioned topics?
Do we use volatile topics by default?

Previous implementation:
https://github.com/SignalR/SignalR/blob/b73cbabe69bc48c4cb8d768148e157712a264ce9/src/Microsoft.AspNet.SignalR.ServiceBus3/ServiceBusConnection.cs

Tracking servicebus work here.

I took a stab at this and the biggest blocker is the fact that the netstandard 2.0 client doesn't support any creation APIs. We can look at using the REST APIs to create the topics and subscriptions but it wouldn't work based solely on the connection string so it's more inconvenient.

This is blocked until we get new APIs

Is this something we expect will be ready for 2.1 RTM or do we not know yet?

@mjrousos yes, we no longe have any immediate plans to write a service bus backplane. We recommend redis as it's volatile nature is a much better fit for SignalR applications.


Notebook: copy / paste cell polish

Copy a cell
Cmd + V to paste a cell only works if the focus is inside the cell. It should work if you have the focus between the cells (still in the notebook)

Also

Cmd + C is a shortcut to copy a cell
However it has not effect since the editor copy line always ovewrites it

The issue should be gone now in Insiders.

I have seen in the default keyboard shortcuts that c should copy a cell (without cmd) and v should paste it, but this is not working. Is this supposed to work in the stable version?
Version: 1.48.2
Commit: a0479759d6e9ea56afa657e454193f72aef85bd0
Date: 2020-08-25T10:09:08.021Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.4.0

@cipri-tom no, we don't support native notebook yet in Stable.


Query result called twice

Minimal example:
export default Vue.extend({
    ...
    apollo: {
        me: {
            query: ME_QUERY,
            result(res) {
                console.log({ res });
            },
        },
    },
    created() {
        console.log('created');
    }
    mounted() {
        console.log('mounted');
    }
    ...
});

Outcome:

Query loads twice, before and after lifecycle hooks. Is this expected behaviour? Notice that the first result contains partial: false, and the second contains stale: false.
Expected outcome:
I only want result to be called once.

I have the same issue. It's definitely cache related. The Apollo Component only calls result once so this behavior is confusing.

Beware of using fetchPolicy: 'no-cache' because your query (which is a watchQuery) will no longer be reactive to cache changes.  This means updating the queried object elsewhere in your app will not be reflected in the query using 'no-cache', and you will need to manually refetch.  This largely defeats the purpose of using a watchQuery.
To get a single query result try using a fetchPolicy with 'cache-only' or 'network-only'.
For more info: https://www.apollographql.com/docs/react/api/apollo-client/#apolloclient-functions

Did someone find a solution?

fectchPolice: 'no-cache' works but loading will be always false,  network-only doesn't work.

Since the query sent by ApolloQuery may be periodically re-issued (look at pollInterval), it's conceptually necessary that you be prepared to process a progressive sequence of revisions/updates to the result object. The idea with the two callbacks you are seeing in your log is that you got an initial set of answers from the cache followed by a refined set of answers from the network-based query to the server. Subsequent re-fetch operations may produce further refinements. Basic use (as documented and intended) of ApolloQuery exploits the fact that the result object is reactive to get your application UI to update dynamically, but more sophisticated patterns may need your application to "wrap" that object in a fashion that deals with the ongoing updates. Re-run your test with a pollInterval parameter of 1000 and watch what happens.
Now that I'm thinking about it, my guess is that the res object itself is identically the same object getting passed up the event tree over and over again. What I suspect is changing here is the content of the res object, and the fired event serves to signal that a change has occurred. Reusing the res object seems necessary for the normal reactive behavior to work. You could check this by saving the res object reference whenever you receive the event and printing an === comparison between the last one and one you are receiving in the event handler.
If you get multiple events as I expect, then this isn't a bug. In fact, it's an essential and necessary behavior.

I am also experiencing this with queries (ie. result or error is called twice back to back).
const apolloClient = new ApolloClient({
  link,
  cache,
  connectToDevTools: !config.app.isProduction,
  defaultOptions: {
    query: {
      fetchPolicy: "cache-first",
    },
  },
});

apollo() {
  viewer() {
    return {
      query: ViewerQuery,
      fetchPolicy: "network-only",
      result(result) { console.log(result); },
      error(error) { console.log(error); }
    }
  }
}

This results in the result or error being logged twice

Hi everyone, there any update about this issue?
Thanks in advance

no update here?
I count the same issue

The same...Any results?

@nomadoda , did you solve this issue?

I don’t think so, I’m afraid

On 16 Nov 2020, at 19:07, Evgen<EMAIL_ADDRESS>wrote:
@nomadoda https://github.com/nomadoda , did you solve this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/vuejs/vue-apollo/issues/492#issuecomment-728231867, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGFS5SVPA7ACS5DQ65QYDZTSQFS7XANCNFSM4GREOJTQ.

So it turns out this is not a bug. It's an intentional behavior. I gave an less-than-correct explanation above, but here's what's happening:
The first callback happens using the cached data on the client. The intent is to give the UI whatever data is already known so that it can get started.
The second callback happens when the network query returns values, which may be different from what was already in the client-side cache. For most objects returned from the network there will be no change, but a few will have changed, some may be added, and others may be dropped. Which means that a new response is required for the client view to revise what it shows.
You can confirm this by overriding the query behavior. If you set the query to "cache only" or "network only", you should find that the callback only occurs once.
This bug should be closed as not-a-bug. The behavior is correct and intentional.

This is still ocurring for me even with network-only (see comment above for config).

Then my explanation is clearly wrong. But I would still guess that there is
something going on at the cache layer that is driving this.
If you change the applications's global fetch policy (the default) to
"Network only", do you still get two callbacks? And does the first callback
actually have any objects in it, or is it null?
On Fri, Nov 27, 2020 at 4:33 PM Kendall Roth<EMAIL_ADDRESS>wrote:

This is still ocurring for me even with network-only (see comment above
for config).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-apollo/issues/492#issuecomment-735018247,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEJX3CW6QIXIOCQ7AATJOBTSSBAL3ANCNFSM4GREOJTQ
.

So it turns out this is not a bug. It's an intentional behavior. I gave an less-than-correct explanation above, but here's what's happening:
The first callback happens using the cached data on the client. The intent is to give the UI whatever data is already known so that it can get started.
The second callback happens when the network query returns values, which may be different from what was already in the client-side cache. For most objects returned from the network there will be no change, but a few will have changed, some may be added, and others may be dropped. Which means that a new response is required for the client view to revise what it shows.
You can confirm this by overriding the query behavior. If you set the query to "cache only" or "network only", you should find that the callback only occurs once.
This bug should be closed as not-a-bug. The behavior is correct and intentional.

Let's imagine that it is correct, like you said.
But why in vue-apollo 2.1 it works without two responses? And it works correct. Was it mistake?

@MaevskiyE: That's a good question, and the answer is: I don't know.
Perhaps if you put a breakpoint in the callback using the browser debugger, you'll be able to see in the callstack where the calls are happening from.
I'd do it here, but right now I'm focused on a server-side problem that's a bit urgent.

@NataliaTepluhina , very nice! Thanx a lot!


Fix fatal crash on iOS due to incorrect arg names

Realized this when trying to run my app on iOS after upgrading to alarm to 4.0.0.

Thanks for the PR !

Added to 4.0.1


Special characters in team name

Hello,
First, thanks for sharing your great code with the community.
My issue: If I put some specific characters (like '_') in the team name, the generated tex won't compile with a "Miss inserted $" error. Solution could be to parse the team name for such specific characters and generate their latex counterparts ("_" in this case).
Thank you. Doms.

Hi Doms,
Thanks for pointing this out. As you can see here I replaced the _ in the annotation names with the escape character for latex, but forgot to do the same for the team name and version number.
Based on your suggestion and this link I updated the latex template to deal with special characters directly in latex without having to intercept them in python.
You can see the edits in this commit.
Should work now.


request: option to list notes by tag, instead of tags by notes

Pretty self-explanatory, I just want to be able to group my notes by the tags they have.
Could use this to improvise an index.
Thanks!
edit: this is regarding the file.tags  function (could maybe name the new one "tag.files"?)

This is technically doable using the query
TABLE tag, rows
FLATTEN file.tags AS tag
GROUP BY tag

The query essentially makes one row per (file, tag) pair, then groups by tag, giving all of the files that have that tag. It just looks really ugly. I will see if I can improve the list view to make a prettier version of this query.
I will also look at doing queries over tags as a more direct alternative that you sugggest - something like
TABLE name, files FROM tags("")

I think blacksmithgu's workaround is sufficient for now. What else would you have liked?


[Issue-2931] Update chainlist

Related issue(s)

#2931

🚀 Deployed on https://pr-2932--sw-web-runner.netlify.app


Add functionality for export to Universeum datalayer

PNG image with georeference to SWEREF 99 12 00 (EPSG:3007)
MP4 30fps with H264 compression
Bounding box (146087, 6395990) - (50018.2, 6401231.6)
Legend should be 2999x1049 with empty top 1/4

@dsjolie @orfeasel think we can do a mini version on Chalmers premises?

We have an ongoing InfraVis project for this, spanning till Fall 2023.


Tutorial on implicit differentiation

Title:
Implicit differentiation of variational quantum algorithms
Summary:
Implicit differentiation can be used to compute gradients of a function that
cannot be written down explicitly using simple elementary operations. In this
notebook we use the idea of implicit differentiation to compute gradients
through a variational quantum algorithm (VQA) that finds groundstate solutions to
a parameterized Hamiltonian H(a)
I need to

[ ] add a thumbnail link in implementations.rst.
[ ] Make a doodle explaining the concept instead of the exact figure used now
[ ] Add a doodle for the variational quantum circuit that helps in the understanding.
[x] Make some small changes to the plot to present the results a bit better.

Relevant references:
[1] Ahmed, S., Killoran, K., Carrasquilla Álvarez J. F. "Implicit differentiation
of variational quantum algorithms." arXiv preprint arXiv:2022.XXXX (2022).
[2] Blondel, Mathieu, et al. "Efficient and modular implicit
differentiation." arXiv preprint arXiv:2105.15183 (2021).
Possible Drawbacks:
The computing of these gradients on real hardware, or with shots=finite needs more investigation.
It is extremely slow with finite shots and in most cases not possible as JAXOpt wants to JIT all calculations
while computing implicit gradients. Nevertheless it works as it is for now.
Related GitHub Issues:

Hey @quantshah The bug has been fixed 😄 There are two things to take into account now to deploy the demo:

I think you are importing a library that is not in the requirements.txt (jaxopt) so it is not going to pass the tests (not sure). Could you add it with the version you are using?
Don't forget to add the item in demos_qml.rst. Don't worry about the thumbnail now. Put any image and we will modify it

@co9olguy Thank you for the very detailed review. I have now implemented all the changes and this is ready to be reviewed/merged from my side. @KetpuntoG is it possible to render the webpage again now?

@co9olguy Thank you for the very detailed review. I have now implemented all the changes and this is ready to be reviewed/merged from my side. @KetpuntoG is it possible to render the webpage again now?

Thanks for the work done this morning! As you can see, it already renders in this PR😊 I'm now going to give another revision to the demo

Thank you @KetpuntoG and @ikurecic for the edits. I have incorporated everything except those that require some input from @KetpuntoG. Feel free to edit and merge it as you see fit.

The following still needs to be done:

bio of the second author
lede
fixing the (newly changed) title/subtitle relations

I guess this is ready for merge?


[GroupBy][Bug]: Looping an aggregated variable same as a spread expression

Description
type Foo record {
    int id;
    string[] name;
};

function foo(Foo[] f) {
    string[] arr = ["a", "b"];
    foreach string item in [...arr] { //allowed
    }

    var r = from var {id, name} in f
        group by id
        from string a in [name] //@error incompatible types: expected 'string[]', found 'string'
        select id;

    io:println(r);
}

Steps to Reproduce
No response
Affected Version(s)
2201.7.0
OS, DB, other environment details and versions
No response
Related area
-> Compilation
Related issue(s) (optional)
No response
Suggested label(s) (optional)
No response
Suggested assignee(s) (optional)
No response

This is invalid. Hence closing


Allow setting custom parameters for each commands

As told in #29, this PR would allow one to set custom parameters for files.list.

@mrblur I am not familiar with TeamDrives support, but do we need to set supportsTeamDrives when requesting other commands (copy, create etc)?

@nao-pon To be honest I don't know yet, still waiting for service account to find out. Looking at docs, it does seems so. That's why I didn't request "Team Drives support", but only putting more control over parameters. At this time ;)
I don't see why Google would need supportsTeamDrives on copy or create as we would specify parent and we only need to have write support on that parent, but they do define supportsTeamDrives on other methods.
Perhaps there is more to do with received metadata and permissions as files on Team Drives does not have an owner.

@mrblur I changed getDefaultListItemsParameters() to applyDefaultParams($params, $cmdName) to make more genericlaize. Please check with new one.

:+1:
Shame on me for not coming up with solution of that kind :)

@nao-pon I have extended this PR with Team Drives support. Got my Service Account and finally was able to actually make API calls. The solution with defaultParams works nicely.
Changes:

I have added teamDriveId to fetch fields - it's easier that way. Changing fetch fields outside contructor would require more helper methods. However, I had to "hack" support of that field as normaliseObject would ignore it unless it's specified as additionalField.
I have added public enableTeamDriveSupport() which adds supportsTeamDrives parameter to defaults of all possible requests, a helper for people that would use corpora=[all|allTeamDrives,user] instead of single team drive.
I have added public setTeamDriveId($teamDriveId, $corpora = 'teamDrive') which configures root and files.list so Flysystems's listContents() works out of the box for single team drive.

I am not sure if adding all possible requests in enableTeamDriveSupport is needed, as Flysystem does not support file watchers, but that way the solution is complete in terms of changing all possible request parameters.

@mrblur I pushed to enable team drive by option setting. Please check whether the team drive can be used according to option setting.

@nao-pon Everything seems to be working fine. I have removed teamDriveId in latest commit as it wouldn't be populated anyway without putting it on fetchfields. It's also valuable only with corpora=allTeamDrives, to distinguish files between team drives and not neede otherwise.

@mrblur Thanks! 👍


Draft: Branch Prediction API

A code introducing branch prediction API. Still a draft PR as I am working through a compilation issue.
Please feel free to review and provide feedback.

@bdutro you might have some input...

Hi Arup, following up on our discussion last night. Could you help me understand how the API will provide configurability, and support speculative state updates?
For configurability, how do we pass in runtime parameters. Furthermore how can we enable reuse of predictor components.
A simple example could be that we have two different branch predictors, one is a bimodal table (similar to what you have implemented), the other is a global history predictor such as gshare (i.e. a branch history table that indexed through a hash of the global history and the PC).  Both predictors have different parameters, and you would likely want to swap them in and out but use the same BTB (and RAS/indirect predictor).
Like the Cache model allows users to change the address decoder, do we need similar methods for changing the components within the branch predictor i.e. the conditional branch predictor, the indirect target predictor, BTB and return address stack.
The other point is about supporting predictors which have internal speculative state. For example a global history predictor has the global history register which needs to be recovered following a flush. Similarly some predictors require meta data about the prediction to be available for the update, TAGE requires the provider table, and alternate prediction for example.
Finally we did speak about how to fit a block based BTB, like you've implemented, into a trace execution model. Branch predictors work in addresses, using trace is difficult because we have to pair instructions with their predictions based on their address. How do we handle malformed trace, or trace that has unexpected change of flow (i.e. interrupt/exception).

Knute mentioned looking at other simulators. I've used gem5, but I'm also aware of champsim.
gem5 o3 model
The branch predictor is an instance within the fetch unit. It contains the BTB, RAS, conditional and indirect target predictors. However the BTB, indirect target predictor and RAS are all objects within the branch unit, which can be swapped out, or disabled entirely.
Fetch
    ├── BranchPredictor
    │   ├── btb
    │   ├── ras
    │   ├── indirectBranchPred
    │   └── IndirectPredictor

As for the API you can read the documentation here for details but I'll summarize.
The interface with Fetch is just 3 methods: predict, squash(flush) and update.
Predict is called for each instruction fetched, the instruction itself is passed through the API. The predictor relies on a sequence number (seqNum) to map predictions to squashes/updates, as the updates/history is stored within the class.
The BTB/RAS/Indirect predictor objects can be swapped out in the build configuration as long as they're a subclass of the original implementation.
The conditional predictor on the other hand, must be a subclass of the branch predictor unit itself. Many leave the base predict, squash and update implementations, and instead override the methods referenced in those. Mainly the lookup*, updateHistories*, update (internal one), and squash.
*Both referenced by predict.
ChampSim
In ChampSim (looking at the ooo_cpu) it separates the BTB and BranchPredictor into two separate classes, though the BTB contains the RAS. The ooo_cpu does a prediction for each instruction fetched (as far as I can tell). It also validates the predictions against the trace, mispredictions stall the pipeline until their resolved.
Both the BTB and BranchPredictor take the PC to produce a prediction. The update methods take the PC, target, direction and branch type.
Going back to Olympia I think the makePrediction/doUpdate methods are fine, given how generic they are. But I do think more thought is needed on how to integrate these, providing parameterization and enable statistic collection.
It might be better to have separate objects for the conditional predictor, indirect target, BTB and RAS. With another API defined for each of them. And a simpleBranchPredictor implementation which orchestrates predictions, updates, flushes across those objects.

For configurability, how do we pass in runtime parameters. Furthermore how can we enable reuse of predictor components.
A simple example could be that we have two different branch predictors, one is a bimodal table (similar to what you have implemented), the other is a global history predictor such as gshare (i.e. a branch history table that indexed through a hash of the global history and the PC). Both predictors have different parameters, and you would likely want to swap them in and out but use the same BTB (and RAS/indirect predictor).

Addressing this part of question/comment: We can do this using ResourceFactories, which are used to configure the tree nodes. As an example, please see files core/CPUFactories.hpp. While sparta units such fetch, decode use a default factory, the unit execute uses a custom factory defined in core/Execute.cpp, which goes through the core extension yaml and creates execution units.
Extending that idea, we can do the following:

use a simple branch predictor or a more complex one (like specified in https://github.com/riscv-software-src/riscv-perf-model/issues/143) based on a command line parameter
for a more complex branch predictor with sub-predictors, select one of multiple available indirect predictor, based on parameters

Like the Cache model allows users to change the address decoder, do we need similar methods for changing the components within the branch predictor i.e. the conditional branch predictor, the indirect target predictor, BTB and return address stack.

IMO, the API should be generic enough to support simplest of the predictors, which may not have different sub-predictors as as long as API does not prevent or create undue burden on implementing more complicated predictors with sub-predictors.

The other point is about supporting predictors which have internal speculative state. For example a global history predictor has the global history register which needs to be recovered following a flush. Similarly some predictors require meta data about the prediction to be available for the update, TAGE requires the provider table, and alternate prediction for example.

Can we not use the updatePredictor method with appropriate input (sub-classed from DefaultUpdate or defined separately) to restore/change predictor states, as needed?

Finally we did speak about how to fit a block based BTB, like you've implemented, into a trace execution model. Branch predictors work in addresses, using trace is difficult because we have to pair instructions with their predictions based on their address. How do we handle malformed trace, or trace that has unexpected change of flow (i.e. interrupt/exception).

We do have to add proper mechanism to handle traces. I plan to address this later.

I think the makePrediction/doUpdate methods are fine, given how generic they are. But I do think more thought is needed on how to integrate these, providing parameterization and enable statistic collection.

I agree and issue #143 will give us the opportunity to work on these aspects.

It might be better to have separate objects for the conditional predictor, indirect target, BTB and RAS. With another API defined for each of them, and then a BranchPredict implementation which orchestrates predictions, updates, flushes across those objects.

I am happy to build on top of the currently proposed API, once reviewed and finalized, to create sub-predictor-specific APIs, if that's needed.
My suggestion would be that we work towards implementing #143 using the proposed branch prediction API and Sparta subunits to create, parameterize sub-predictors and combine them. As we work through it, we can discuss how can we keep interfaces generic enough to be APIs

On a different note do we need to discuss the directory structure going forward for when others implement their own predictors? Do we need a separate branchpred directory under core?

Please put everything in separate namespace

Have added branch prediction IF and SimplePredictor in the Olympia namespace, for now, in line with what we have currently for LSU, Dispatch etc. I will capture this request in a separate issue to create separate namespaces for different units of Olympia

On a different note do we need to discuss the directory structure going forward for when others implement their own predictors? Do we need a separate branchpred directory under core?

Let us address this in a new PR when we add other branch predictors.

Addressed review comments. Please take a look and approve, if looks good. I need at least one approval for merge.

As a reminder, if there is no further comment, please approve so that we can merge this.


Suppress MatchingDeclarationName for file containing only an extension property

I have a .kt file that only has a single extension property like this
val MyObject.myProperty = ...
I want to call this file something like MyObjectExtensions.kt, but Detekt won't let me do that due to a MatchingDeclarationName error. Supressing doesn't seem to work though, not directly on the property or via @file. How could I suppress this error here?

I just tried with this code and detekt doesn't show any warning:
@file:Suppress("MatchingDeclarationName")

val Any.myProperty = ' '

Could you provide a project/file to reproduce your issue?

Found the issue: We have two files with the same name and the same issue in two different modules of our project. Suppressing was successful but then nearly the same error showed up for the other file and we kept on trying. 🤦♂


Consider publishing non-minified files to npm or source maps

This would enable debugging the package when there's a problem.

I have evaluated publishing non-minified files to npm and I have reached the conclusion that the only possible errors that could propagate from this file would be passing an improper type to the TextDecoder.prototype.decode method. The TextEncoder throws no errors because it coerces its argument to a string on line 80. Of course, if you did (new TextEncoder).encode({toString:function throwFunc(){ throw Error("Troll") }}) then an error would propagate outwards. However, even in this esoteric hypothetical scenario, you would more likely be interested in which file the throwFunc originated from rather than which line of code in FastestSmallestTextEncoderDecoder propagated the error. Thus, I may be entirely wrong (if so, please explain it to me), but I do not see the need to include the source code at the cost of a longer file parsing time. Many NodeJS projects already take forever to startup as-is on non-SSD hard drives and I do not want to contribute any time to that long wait. Nevertheless, I have included a source map pointed to by the minified file should the need ever arise. If I am wrong and there is legitimate cause for increasing loaded files weight, then please explain it to me--I would be very very interested in hearing about it.
I really want to thank you for opening all of these Issues. It really means a lot to me. Thank you so much for being so helpful.

Devinus, much time has gone by and I am uncertain if and when you will respond. It is fine if you are too busy, but I shall temporarily close this issue in a week if there is no feedback about whether the source maps have fixed the problem.
~ Happy Coding.


Show type of symbol under cursor in the status bar

Isn't it too intrusive to use the status bar? It is a shared UI that can be used by anyone; the information displayed there may be overriden at any time.
Other options are:

Popup windows as per http://vfpt.uservoice.com/forums/247560-general/suggestions/6143128-show-type-annotation-on-expression

Tool windows similar to F# Interactive as per http://vfpt.uservoice.com/forums/247560-general/suggestions/5737085-add-a-pane-that-constantly-shows-the-tooltip-conte

These options require more work (and some XAML skills), but probably constitute a more useful feature.

An entire tool window is too large and would waste a lot of space:

I'd prefer an area inside the editor window, small and not sizable.

I'm going to show it in status bar. It seems VS does not use its left side. Will see how it's going.

Sure, go for it.
An alternative is to build our own status bar.
An example from Viasfora:
http://viasfora.com/images/feat/devmargin-buffergraph.png
https://github.com/tomasr/viasfora/blob/67b34291909ddf327c0c97363dd887a48ded15bb/Viasfora/Margins/DevMarginVisual.xaml

Addressed by #973. Closing.


Databricks Policies Assignments Failing ("out of scope")

Describe the bug
For new deployments via the portal experience, the databricks polices fail as the policy definitions as specified in policy assignment is "out of scope".
Steps to reproduce

Deploy ESLZ via the portal experience
Opt out of identity, connectivity configs to mimic Wingtip (have not tested with alternate options to know if this has any effect or not).

I have deployed two times with the same result.
Screenshots

The error is the same for the three policies:
{
   "status": "Failed",
   "error": {
       "code": "DeploymentFailed",
       "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/DeployOperations for usage details.",
       "details": [
           {
               "code": "BadRequest",
               "message": "{\r\n  \"error\": {\r\n    \"code\": \"InvalidCreatePolicyAssignmentRequest\",\r\n    \"message\": \"The policy definition specified in policy assignment 'Deny-DataB-Sku' is out of scope. Policy definitions should be specified only at or above the policy assignment scope. If the management groups hierarchy changed recently or if assigning a management group policy to new subscription, please allow up to 30 minutes for the hierarchy changes to apply and try again.\"\r\n  }\r\n}"
           }
       ]
   }
}

linking to #872

Confirming that re-running with same inputs fixed everything. Thank you for the guidance to resolve!


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter icons-smarthome for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.icons-smarthome
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E204] Version "0.0.1" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.

WARNINGS:

[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.noConfig" is deprecated for admin >= 5 at io-package.json. Please use property "adminUI.config":"none".
[ ] :eyes: [W520] Plugin "manual-review" missing at .releaseconfig.json. Please add.

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 06 Sep 2024 08:31:01 GMT

Issue outdated due to RECREATE request. Follow up issue #14 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


Install only compiled files

If you do cmake --DCMAKE_SKIP_INSTALL_ALL_DEPENDENCY=true
and then make tchsm_node
and then make install it should install the node. However it's failing....

#114 fixes this issue:
$ cmake -DENABLE_CRYPTOKI=OFF ..
$ make install


Distribution artifacts broken?

I'm trying to use Reactabular in a ClojureScript application (so I'm not using npm), and am trying to use the artifacts in dist in my HTML file like so:

That gives me:
TypeError: _ is undefined

... for this bit of code at the very beginning:
var _ = __webpack_require__(2);
var merge = _.merge;
            ^

Am I doing something wrong?

Reactabular depends on lodash/underscore.
One option to get rid of that requirement would be to bundle the dependencies. That would bloat the bundle a little but it would make it easier to consume.

Thanks for the quick turnaround!
So what exactly would I need to include along with reactabular.js?
I've added lodash.min.js, but the problem persists.

So what exactly would I need to include along with reactabular.js?

Good question. The dist build contains UMD wrapper so there are actually a couple of options. It looks like it seeks lodash through root["lodash"] (root points at window). I suppose that's the issue.
I could change the dist build to generate root["_"]. Maybe that would be nice here.
Can you try these adjustments? I have a feeling I might need to tweak React entry too while at it.

Thanks, that gets me further - to "React is undefined". Now I suppose I need to figure out how to convince ClojureScript to sqeeze React between Reactabular and my code?

Thanks, that gets me further - to "React is undefined". Now I suppose I need to figure out how to convince ClojureScript to sqeeze React between Reactabular and my code?

Likely yes. There's a declaration like root["react/addons"]. I expect we might need to have root["React"] or similar for Reactabular to find React through a global.
Let me know if this does the trick. Once we get this working I'll do these changes to the distribution version. It's far easier to consume Reactabular through npm but it's definitely nice if we have a sane dist bundle out there.

root["React"] indeed works, thanks! Now with that in place, how do I get at the binding for Table itself?

@mikesperber I think you should be able to see something through Reactabular global (the code performs exports["Reactabular"]).
I'll tweak root for the next version so you don't have to patch these by hand.

Ah, silly me. Didn't see that somehow. Thanks!

Same issue here. Using Underscore.js and global '_' reference getting replaced with lodash. Great component btw, simple to implement and powerful functionality out of the box. Unfortunately I will need to go with something else for now.

@mikesperber @kro12 I figured out a nice fix for this. Can you have a look at dev and give it a go? See esp. ./dist.

Yup, works. Thanks!

@mikesperber Great to hear! I published v0.7.0 with the change. I went for 0.7.0 to play it safe as I don't want to break someone's project in case there's some glitch in the dist.


[jnigen] Add doc about threading

Close #611

coverage: 88.81%. remained the same
when pulling abd411e0a11b3683c559cab1c84970c16d756b52 on threading-doc
into 4069de367751b4ee1ab50dcf1aeb41085c10edac on main.


When generating the dataset an Error occurs:  ValueError: operands could not be broadcast together with shapes (568,15) (0,15) (568,15)

data/ShanghaiTech/part_A/train_data\images\IMG_118.jpg
4%|▍         | 21/482 [00:02<00:45, 10.16it/s]
Traceback (most recent call last):
File "C:/Users/a/PycharmProjects/W-Net-Keras/generate_datasets.py", line 46, in
DM = gen_density_map_gaussian(k, gt, sigma=sigma)
File "C:\Users\a\PycharmProjects\W-Net-Keras\utils_gen.py", line 86, in gen_density_map_gaussian
] += gaussian_map
ValueError: operands could not be broadcast together with shapes (568,15) (0,15) (568,15)
The same problem occurs in your other code, SANet-Keras. I'm using Python 3.7.

    if (gaussian_map.shape[1] ==0)or(gaussian_map.shape[0]==0):
        continue

redefine below function
def gen_density_map_gaussian(im, points, sigma=4):
"""
func: generate the density map
"""
density_map = np.zeros(im.shape[:2], dtype=np.float32)
h, w = density_map.shape[:2]
num_gt = np.squeeze(points).shape[0]
if num_gt == 0:
return density_map
for p in points:
p = np.round(p).astype(int)
p[0], p[1] = min(h-1, p[1]), min(w-1, p[0])
gaussian_radius = sigma * 2 - 1
gaussian_map = np.multiply(
cv2.getGaussianKernel(int(gaussian_radius2+1), sigma),
cv2.getGaussianKernel(int(gaussian_radius2+1), sigma).T
)
x_left, x_right, y_up, y_down = 0, gaussian_map.shape[1], 0, gaussian_map.shape[0]
# cut the gaussian kernel
if p[1] < gaussian_radius:
x_left = gaussian_radius - p[1]
if p[0] < gaussian_radius:
y_up = gaussian_radius - p[0]
if p[1] + gaussian_radius >= w:
x_right = gaussian_map.shape[1] - (gaussian_radius + p[1] - w) - 1
if p[0] + gaussian_radius >= h:
y_down = gaussian_map.shape[0] - (gaussian_radius + p[0] - h) - 1
gaussian_map = gaussian_map[y_up:y_down, x_left:x_right]
if np.sum(gaussian_map):
gaussian_map = gaussian_map / np.sum(gaussian_map)
print('ljj checking here ',gaussian_map.shape,density_map.shape)
    if (gaussian_map.shape[1] ==0)or(gaussian_map.shape[0]==0):
        continue
    density_map[
        max(0, p[0]-gaussian_radius):min(h, p[0]+gaussian_radius+1),
        max(0, p[1]-gaussian_radius):min(w, p[1]+gaussian_radius+1)
    ] += gaussian_map
density_map = density_map / (np.sum(density_map / num_gt))
return density_map

Sorry for the late reply, I remember this problem was caused by the negative value axis in SH dataset. You should notice that there are two versions of SH dataset A and B, one link is to dropbox, another one is to Baidu Disk. I used the one from dropbox since there are negative ones in that from Baidu Disk which actually shouldn't exist.

but the dropbox sharing is cancelled ? can u update the baidu pan data；
for now  my results on the baidu pan
73.45434 118.59023 0.010220066 0.18018237 23.290236517822745 0.6487061596273813
with same configuration , seems not acceptable~
thanks in advance~

Thanks for your interest. The link was copied from an MCNN repository, and it's true that it doesn't work now. But I'm really busy with exams recently, and this W-Net is an uncomplete version, I remember that there're some points not clear in the original paper, and I spent time on other things at that time.
And it's very very similar to SFANet, the whole network architecture, and almost every hyperparameter and the  SFANet is earlier than W-Net on arXiv. If you need this network architecture for your research, I recommend this SFANet reproduction for you.
Good luck.


Crash with micro text editor after editing and saving files

What system are you running Yazi on?
Linux Wayland
What terminal are you running Yazi in?
foot version: 1.16.2
Yazi version
yazi 0.1.5 (82bab0f 2023-12-26)
Did you try the latest main branch to see if the problem has already been fixed?
Tried, but the problem is still present
Describe the bug
Opening a file with micro, editing a single character, saving and closing the file leads to:
Backtrace (most recent call first):

The application panicked (crashed).
  panic in a function that cannot unwind
in library/core/src/panicking.rs, line 136
thread: tokio-runtime-worker

This only seems to happen when files are at least 2 folders away from yazi's starting directory.
Expected Behavior
Yazi should not crash.
To Reproduce
See above.
Configuration
No response
Anything else?
No response

I can't reproduce it on my side. Could you record a gif and let me see your steps?

System
Linux Wayland
Terminal
foot 1.16.2
Yazi version
yazi 0.1.5 (82bab0f 2023-12-26)
Describe the bug
Not quite sure whether this is related; but the error message is identical:
As soon as I hover any file with a json or lock extension, yazi crashes with the error message above. So far I haven't found other extensions affected.
Thanks for your latest huge commit! Impressive.

I tried running the latest code on my macOS and Linux VM, but unfortunately, I still couldn't reproduce it.
When hovering over the json and lock files, they work fine, and I can edit them and preview the changes normally.
There's no information in the error message that could help pinpoint the issue. Could you please run Yazi in debug mode and set RUST_BACKTRACE=1, i.e. do a
export RUST_BACKTRACE=1
cargo run

In Yazi's source code directory.

Thank you. The yazi binary compiled with export RUST_BACKTRACE=1 does not crash any more. Yet, there is no preview for these file types (json, lock).
cargo run echoes quite a number of warnings. Would posting them help you?

So weird. I want to know how you built Yazi before and if there are any configuration files, please paste them here.

cargo run echoes quite a number of warnings. Would posting them help you?

That's unrelated; those are part of the plugin system that's still incomplete. I left them there to remind me to finish it. 🤣

Usually I compile yazi with
cargo build --release

Error happens without any user config files, too.
But this is my current yazi.toml:

[manager]
layout         = [ 0, 4, 3 ]
sort_by        = "natural"
sort_sensitive = false
sort_reverse   = false
sort_dir_first = true
linemode       = "none"
show_hidden    = false
show_symlink   = true

[preview]
tab_size   = 2
max_width  = 600
max_height = 900
cache_dir  = ""

[opener]
open = [
	{ exec = 'xdg-open "$@"', orphan = true, desc = "open", for = "unix" },
]
editTerm = [
	{ exec = '$TERMINAL $EDITOR "$@"', orphan = true, desc = "edit in new terminal", for = "unix" },
]
edit = [
	{ exec = '$EDITOR "$@"', block = true, desc = "edit", for = "unix" },
]

[open]
rules = [
	{ name = "*", use = [ "open", "editTerm", "edit" ] },
]

[tasks]
micro_workers = 5
macro_workers = 10
bizarre_retry = 5

[plugins]
preload = []

[log]
enabled = false

Thank you so much for investigating!

I think I've pinpointed the issue, which might be a bug in mlua. I'm not sure how to handle it yet, so I've decided to temporarily disable it.
I made a PR to fix it, https://github.com/sxyazi/yazi/pull/459, please give it a try and let me know if it works for you.

@sxyazi The latest PR does fix crashing on renaming/editing files, but yazi still crashes when hovering over certain file types - but I haven't figured out which types AND this behavior is not consistent across different HW (always Arch Linux with wayland)
Thank you for your time and work!

Same here. The PR fixes editing files with micro, but scrolling over text files with a preview causes the same crash.

Hi, I pushed a new commit. Please try it out again to see if it works. Hope it's effective :)

Hi, I pushed a new commit in that PR. Please try it out again to see if it works. Hope it's effective :)

Thanks a lot!
a005f20 solved this issue on my side.

Hi, I pushed a new commit in that PR. Please try it out again to see if it works. Hope it's effective :)

yazi built with that commit doesn't "show" any files here at all (only previews), unfortunately...

While that fixes the crash, some previews of text files, specifically .json files, are missing.

Okay, let's merge that PR first, and I'll keep this issue open to track any other potential issues.

As for .json preview, it's a breaking change - prior to Yazi v0.2.0, it would call jq first, and if that call failed (e.g., if the user hadn't installed it), it would fallback to Yazi's built-in code highlighting.
However, this behavior is inefficient for users who never installed jq but always use the built-in highlighting - it constantly creates processes to attempt whether jq is installed.
In Yazi v0.2.0, this fallback has been removed. When users don't really need jq, they can directly specify Yazi's built-in highlighting for the .json preview:
# yazi.toml
[plugin]
previewers = [
	# ...
	{ mime = "application/json", exec = "code.lua" },
]

Try to add this line to the previewers. For now, please copy the entire previewers. I will add new options before the release of Yazi v0.2.0 to allow users to selectively override certain previewers.

Hi, I pushed a new commit in that PR. Please try it out again to see if it works. Hope it's effective :)

yazi built with that commit doesn't "show" any files here at all (only previews), unfortunately... : (
EDIT: I used: linemode = "mtime" With: linemode = "none" files "reappeared"...

Should be fixed in https://github.com/sxyazi/yazi/commit/bfa5e0af0c5493d1420d68b3346be808177f496c, thanks for the report!

EDIT: I used: linemode = "mtime" With: linemode = "none" files "reappeared"...

Should be fixed in bfa5e0a, thanks for the report!

Yep, thanks a lot!

I think this issue has been resolved, so let me close it now.
BTW, in order to reduce the impact of v0.2.0 on user behavior, I've decided to reintroduce the fallback. 🤣
However, for users who never use jq, we now have an additional mechanism for selective opt-out - they can remove json.lua from the previewers, that's enough.


Add line break for warning for policy/asset/liability (Fix Issue #317)

As per title.

Codecov Report

Merging #319 (2f75bde) into master (06160a0) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #319   +/-   ##
=========================================
  Coverage     76.23%   76.23%
  Complexity      662      662
=========================================
  Files            98       98
  Lines          2260     2260
  Branches        187      187
=========================================
  Hits           1723     1723
  Misses          444      444
  Partials         93       93

Impacted Files
Coverage Δ

...in/java/donnafin/logic/commands/AppendCommand.java
78.46% <ø> (ø)

Continue to review full report at Codecov.

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


Unable to install wtf8 using npm

Not able to install wtf8 using npm. Are there any missing dependencies?
$ npm install -g wtf8
npm http GET http://registry.npmjs.org/wtf8
npm http 304 http://registry.npmjs.org/wtf8

><EMAIL_ADDRESS>preinstall /home/user/.nvm/v0.8.0/lib/node_modules/lib/node_modules/wtf8
> node-gyp configure build

make: Entering directory `/home/user/.nvm/v0.8.0/lib/node_modules/lib/node_modules/wtf8/build'
  CXX(target) Release/obj.target/wtf8/wtf8.o
In file included from ../wtf8.cc:1:0:
/home/user/.node-gyp/0.11.7/deps/v8/include/v8.h: In member function 'void v8::ReturnValue<T>::Set(uint32_t)':
/home/user/.node-gyp/0.11.7/deps/v8/include/v8.h:5928:31: warning: typedef 'I' locally defined but not used [-Wunused-local-typedefs]
   typedef internal::Internals I;
                               ^
../wtf8.cc: In function 'v8::Handle<v8::Value> {anonymous}::Decode(const v8::Arguments&)':
../wtf8.cc:37:41: warning: narrowing conversion of '((chr >> 10) | 55296u)' from 'uint32_t {aka unsigned int}' to 'uint16_t {aka short unsigned int}' inside { } is ill-formed in C++11 [-Wnarrowing]
         uint16_t surrogate[2] = {0xD800 | (chr >> 10), 0xDC00 | (chr & 0x3FF)};
                                         ^
../wtf8.cc:37:63: warning: narrowing conversion of '((chr & 1023u) | 56320u)' from 'uint32_t {aka unsigned int}' to 'uint16_t {aka short unsigned int}' inside { } is ill-formed in C++11 [-Wnarrowing]
         uint16_t surrogate[2] = {0xD800 | (chr >> 10), 0xDC00 | (chr & 0x3FF)};
                                                               ^
../wtf8.cc: In function 'v8::Handle<v8::Value> {anonymous}::Encode(const v8::Arguments&)':
../wtf8.cc:105:11: error: expected primary-expression before '&' token
     Buffer& slowBuffer = *Buffer::New(accumulator.size());
           ^
../wtf8.cc:105:13: error: 'slowBuffer' was not declared in this scope
     Buffer& slowBuffer = *Buffer::New(accumulator.size());
             ^
../wtf8.cc: In function 'void {anonymous}::RegisterModule(v8::Handle<v8::Object>)':
../wtf8.cc:113:74: warning: 'static v8::Local<v8::FunctionTemplate> v8::FunctionTemplate::New(v8::InvocationCallback, v8::Handle<v8::Value>, v8::Handle<v8::Signature>, int)' is deprecated (declared at /home/user/.node-gyp/0.11.7/deps/v8/include/v8.h:3354) [-Wdeprecated-declarations]
     target->Set(String::NewSymbol("decode"), FunctionTemplate::New(Decode)->GetFunction());
                                                                          ^
../wtf8.cc:114:74: warning: 'static v8::Local<v8::FunctionTemplate> v8::FunctionTemplate::New(v8::InvocationCallback, v8::Handle<v8::Value>, v8::Handle<v8::Signature>, int)' is deprecated (declared at /home/user/.node-gyp/0.11.7/deps/v8/include/v8.h:3354) [-Wdeprecated-declarations]
     target->Set(String::NewSymbol("encode"), FunctionTemplate::New(Encode)->GetFunction());
                                                                          ^
../wtf8.cc: In function 'v8::Handle<v8::Value> {anonymous}::Encode(const v8::Arguments&)':
../wtf8.cc:110:3: warning: control reaches end of non-void function [-Wreturn-type]
   }
   ^
make: *** [Release/obj.target/wtf8/wtf8.o] Error 1
make: Leaving directory `/home/user/.nvm/v0.8.0/lib/node_modules/lib/node_modules/wtf8/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/home/user/.nvm/v0.11.7/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:106:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:827:12)
gyp ERR! System Linux 3.11.0-15-generic
gyp ERR! command "node" "/home/user/.nvm/v0.11.7/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
gyp ERR! cwd /home/user/.nvm/v0.8.0/lib/node_modules/lib/node_modules/wtf8
gyp ERR! node -v v0.11.7
gyp ERR! node-gyp -v v0.10.9
gyp ERR! not ok
npm ERR! weird error 1
npm ERR! not ok code 0

Hey @lautis, would you accept a patch for wtf8 using rvagg/nan for native bindings ? Would solve this issue.

I would, although I definitely recommend using built-in Buffer in Node 0.10 or newer. These versions should be able to handle Unicode characters outside basic multilingual plane without any extra libraries.

Fixed in 0.2.0.


BT not validating card

Hello,
I've been trying to use this package, but when I am using getCardNonce() function, no matter what data I pass to it (it can be even nulls) it's always returning me a new card nonce. Is it expected behaviour? Shouldn't it return me any error that the card is invalid or something? It's happening on both android and ios. I am using sanbox testing token.

Maybe this will resolve your issue: https://github.com/kraffslol/react-native-braintree-xplat/pull/47

@edvinasbartkus it did, but only for iOS. It's still not working on Android. :(

Created PR fix for Android: #48

Should be fixed now with the contributions from @edvinasbartkus and yourself.

I updated to 3.2.0 and this did not cause it to start validating for either platform.


Automated testscript for metadata commands

Related Issues / Pull Requests
List all related issues and/or pull requests if there are any.
Description
Include a brief summary of the proposed changes.
What changes are proposed in this pull request?

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected; for instance,
examples in this repository need to be updated too).
[ ] This change requires a documentation update.

Checklist:

[ ] My code follows the style guidelines of this project (PEP-8 with Google-style docstrings).
[ ] My code modifies existing public API, or introduces new public API, and I updated or wrote docstrings that
uses Google-style formatting and any other formatting that is supported by mkdocs and plugins this project
uses.
[ ] I have commented my code.
[ ] My code requires documentation updates, and I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] New and existing unit tests pass locally with my changes.

Closing this PR as the changes in this one are added to a different branch and PR has been created with that branch


2.0 release notes and known limitations

@bdarnell, @nstewart, PTAL at these draft release notes for 2.0. As you'll see, I tried to summarize the most significant user-facing features (pretty much all from the roadmap). Please let me know if anything significant is missing, or if any language should be changed.
Of course, this leaves out a LOT of significant internal work and granular changes to the product, but I don't think we can list out everything here. Or if we want to, I'd need help.
This PR also documents 2.0 known limitations.
Fixes #2446.
Fixes #2566.

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/8422f5c1e8bbee80652c3bf5508967f74adce275/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/894a119be4f8ed7a423fedc63008017eb785a0ce/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5af5380b524eb469afc7a9bd359d1b8819e5c2d9/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9484b820566523062c9eca0b3d0ee4b9cb530b80/

Oh, and @nstewart, I need help with the intro sentence:

With the release of CockroachDB v2.0, we’ve...

For reference, here's what we had for v1.1:

With the release of CockroachDB v1.1.0, we’ve included support for faster migrations from other databases for developers, simplified cluster management for operators, and improved performance in real-world environments.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/709faec6a0813f5706a35c91209d6cc8708799c7/

We need to be sure to copy forward any of the backwards-incompatible changes from previous release notes. We have some in 0305 (sequences (only applies relative to previous alphas/betas) and zone constraints), 1026 (bytes/string casts), 1113 (NaN and drop user with grants), 0122 (removed settings and env vars).

Review status: 0 of 9 files reviewed at latest revision, all discussions resolved, some commit checks failed.

releases/v2.0.0.md, line 11 at r4 (raw file):

With the release of CockroachDB v2.0, we’ve...

- Read more about these changes in the [v2.0 blog post](https://www.cockroachlabs.com/blog/cockroachdb-1dot1/).

Don't forget to update this link.

Comments from Reviewable

Review status: 0 of 9 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

v2.0/known-limitations.md, line 17 at r4 (raw file):

The `--cache` and `--max-sql-memory` flags of the [`cockroach start`](start-a-node.html) command do not support non-integer values with a unit suffix, for example, `--cache=1.5GiB`.

As a workaround, use integer values or a percentage, for example, `--cache=1610612736B`.

A more compact and easier to understand suggested workaround would be --cache=1536MiB.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/fc8614da42299c15e82c20a5f97a06c2ec681daa/

Added backward-incompatible changes, @bdarnell. PTAL.

Review status: 0 of 16 files reviewed at latest revision, 2 unresolved discussions.

v2.0/known-limitations.md, line 17 at r4 (raw file):
Previously, petermattis (Peter Mattis) wrote…
A more compact and easier to understand suggested workaround would be --cache=1536MiB.

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b656a9392db480cfb714e82549a3f9336955526a/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/4e5a983d1f09106b899cdcde85e431e990c3562e/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/83ad96a3f2f52e97c061a018d10eb65233e7c5ad/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f1c190b9f31c3edcf90b7b36ac534d389dff5e1f/

@jseldess point in time backup/restore is a beta feature. I think @Amruta-Ranade is updating this cc @dianasaur323

yes, it is beta! just pinged @Amruta-Ranade about it. Also, @jseldess am I on deck to write the user contract for experimental vs beta? It would be great to have a docs person to work with so that I know where it lives and what best practices are? Do you mind letting me know who would be good to sync up with? Just need 15 minutes of their time and then I can go come up with a draft.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/5cc1ca86789907467887cbf02c551ae088571912/

releases/v2.0.0.md, line 11 at r4 (raw file):
Previously, bdarnell (Ben Darnell) wrote…
Don't forget to update this link.

Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/b0227b10370bf03e66ccf8b97b1e807ffbdad468/

@nstewart and @dianasaur323, added beta and experimental language where necessary.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/66eabbaaef4634ec18eafb5b9a84ec9a2b79b35d/

Thanks jesse!

The following callout must be inserted below the "Parameters" section in create-view.md:
{{site.data.alerts.callout_info}}It is not yet possible to use a common table expression
defined 1with WITH inside the selection query used to defined a
view. This is a known limitation that may be lifted in a future
version of CockroachDB.{{site.data.alerts.end}}

(you may want to insert a similar paragraph in the known limitation page)
The following callout must be inserted at the end of the "Syntax" sub-section of the "VALUES Clause" sub-section of selection-queries.md:
{{site.data.alerts.callout_info}}It is not yet possible to use a common table expression
defined with WITH outside of a VALUES
clause, inside a subquery inside the
VALUES clause. This limitation may be lifted in a
future version of CockroachDB.{{site.data.alerts.end}}

The following sub-section must be added at the end of the "Set Operations" sections in selection-queries.md:
### Using Set Operations With Common Table Expressions

Due to a current limitation in CockroachDB, a common table
expression (CTE) defined using `WITH` outside of a set expression
cannot be used in the right operand of a set operator. For example,
the following query is not yet recognized:

{% include copy-clipboard.html %}
~~~ sql
> WITH a AS (SELECT 1)
  SELECT * FROM users UNION SELECT * FROM a; -- "a" used on the
right, not yet supported.
~~~

For `UNION`, you can work around this limitation by swapping the
operands. For the other set operators, you can inline the definition
of the CTE inside the right operand.

This limitation may be lifted in a future version of CockroachDB.

Review status: 0 of 16 files reviewed at latest revision, 2 unresolved discussions, some commit checks failed.

Comments from Reviewable

I would also recommend adding a sub-section "LInks to known limitations" in the separate doc page common-table-expressions.md which cross references these things.

Review status: 0 of 16 files reviewed at latest revision, 2 unresolved discussions.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9bbf1c8013b52c28d89949a9df62bc80acf77bac/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/6ef6e63026ebe670e95fd43ac1897e5746530911/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f36204f0174a55e502a28a671e53d90b11fcec0b/

Thanks, @knz! Done.

Comments from Reviewable

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/641926760ea33462acf15d699a042537ba106ea8/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/c3bb9d2a104340c8b9035c3234fab7e0e3b013fd/


remove bvt issue tag

What type of PR is this?

[ ] API-change
[ ] BUG
[ ] Improvement
[ ] Documentation
[ ] Feature
[ ] Test and CI
[ ] Code Refactoring

Which issue(s) this PR fixes:
issue #
What this PR does / why we need it:

all

/test

refresh


Reach Rock Bottom (6a/6b Checkpoint) checks off after unlocking Reflection subchapter in 6b

omg haha this is such a silly bug. basically it's checking whether you have 4 checkpoints in 6a OR two checkpoints in 6b but the way it does this it will count a combination of partial progress toward both of them as the whole objective. very silly. it's fixed now. I'll put out a new version in the next few hours.


Make managing localStorage easier

It's possible to get localStorage into a weird state. I went from one deployment to another and I had state kicking around.

I haven't seen this so I'm going to close.


Output individual NLDI feature as json-ld representation.

Based on the outcome of #280 allow f=jsonld or the appropriate content type header to trigger the jsonld media type response. This would include the mainstem the feature is on and the @id of the feature is to be the existing url attribute of the feature.

Chatting with @EthanGrahn and mocked this up. @ksonda any feedback? Ideas?

I've used HY_Hydrolocation and schema:Place as types.
Source and sourceName are not in the graph - should they be?
comid is just an "in" association. Should schema topology be used or geoqparql?
we would need some logic to determine what gets put into the indirect position. Features that are tagged as hydrolocation would get a mainstem, features that have reachcode/measure would get the reachcode / measure.
we will not include schema:geo for the non--point indexed data that we have just recently implemented support for.

Thoughts?
{
	"@context": [
		{
			"schema": "https://schema.org/",
			"geo": "schema:geo",
			"hyf": "https://www.opengis.net/def/schema/hy_features/hyf/",
			"gsp": "http://www.opengis.net/ont/geosparql#",
			"name": "schema:name",
			"comid": {
				"@id": "schema:containedInPlace",
				"@type": "@id"
			},
			"mainstem": {
				"@id": "schema:url",
				"@type": "@id"
			}
		}
	],
	"@id": "http://www.waterqualitydata.us/provider/NWIS/USGS-WI/USGS-05430050/",
	"@type": [
		"https://www.opengis.net/def/schema/hy_features/hyf/HY_HydroLocation",
		"https://schema.org/Place"
	],
	"source": "WQP",
	"sourceName": "Water Quality Portal",
	"name": "BADFISH CREEK NEAR OREGON, WI",
	"comid": "https://geoconnex.us/nhdplusv2/comid/13296678",
	"hyf:referencedPosition": [
		{
			"hyf:HY_IndirectPosition": {
				"hyf:distanceExpression": {
					"hyf:HY_DistanceFromReferent": {
						"hyf:interpolative": "84.8194"
					}
				},
				"hyf:distanceDescription": {
					"hyf:HY_DistanceDescription": "upstream"
				},
				"hyf:linearElement": "https://labs.waterdata.usgs.gov/geoserver/wmadata/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=wmadata%3Anhdflowline_network&outputFormat=application%2Fjson&cql_filter=reachcode%20=%20%2712040104000071%27"
			}
		},
		{
			"hyf:HY_IndirectPosition": {
				"hyf:linearElement": {
					"@id": "https://geoconnex.us/ref/mainstems/2600464",
					"@type": "hyf:HY_Flowpath"
				}
			}
		}
	],
	"geo": {
		"schema:latitude": 42.9280563,
		"@type": "schema:GeoCoordinates",
		"schema:longitude": -89.329007
	},
	"gsp:hasGeometry": {
		"@type": "http://www.opengis.net/ont/sf#Point",
		"gsp:asWKT": {
			"@value": "POINT(-89.329007 42.9280563)",
			"@type": "http://www.opengis.net/ont/geosparql#wktLiteral"
		}
	}
}

We could remove mainstem from the context since we'll be putting it in the hyf:referencedPosition instead.

for comid, maybe schema:geoWithin if the comid identifier is eventually a semantic resource of type Place, or a catchment area?
Source and sourceName...
elsewhere we use the schema:provider concept, but we haven't thought about it rigorously. Maybe it could be something like
in context, "source": "schema:provider"
and then
"source": {
"@type": "schema:Organization",
"schema:url": "https://waterqualitydata.us",
"schema:name": "WQP",
"schema:description": "Water Quality Portal"
}

We could remove mainstem from the context since we'll be putting it in the hyf:referencedPosition instead.

agree you're not using mainstem as an alias anywhere. I guess if you wanted to you can do this
"hyf:HY_IndirectPosition": {
				"mainstem":  "https://geoconnex.us/ref/mainstems/2600464"
				}

and have this in the context
"mainstem": {
				"@id": "hyf:linearElement",
				"@type": "@id"
			}

and then over in refernce features we type all mainstems as hyf:HY_Flowpath

My understanding of the mainstem context that @ksonda suggested is that it makes it slightly simpler to write in the body.
e.g.
"hyf:HY_IndirectPosition": {
   "mainstem": "https://geoconnex.us/ref/mainstems/473915"
 }

vs
"hyf:HY_IndirectPosition": {
	"hyf:linearElement": {
		"@id": "https://geoconnex.us/ref/mainstems/2600464",
		"@type": "hyf:HY_Flowpath"
	}
}

I think just doing it:
"hyf:HY_IndirectPosition": {
   "hyf:linearElement": "https://geoconnex.us/ref/mainstems/473915"
 }

Seems fine?

You either need to specify an alias in the context with "@id": "hyf:linearElement" or do
"hyf:HY_IndirectPosition": {
   "hyf:linearElement": {"@id": "https://geoconnex.us/ref/mainstems/473915"}
 }

and now that I think about it, reachcode you might want to be
"hyf:linearElement": { "schema:url" (or "@id") : "https://geoconnex.us/nhdplusv2/reachcode/07090002008279"}

Ahhh --- we are honing in on two things. I was noting that there is another hyf:linearElement just below mainstem that's linking to the reach geometry. You were keying into the nuance about @id.
@EthanGrahn -- let's use the context to specify that hyf:linearElement is an @id and not use the mainstems json key in the body of the json-ld.

Not sure that I'm fully grasping what needs to be done. Something like this?
{
  "@context": [
    {
      "schema": "https://schema.org/",
      "geo": "schema:geo",
      "hyf": "https://www.opengis.net/def/schema/hy_features/hyf/",
      "gsp": "http://www.opengis.net/ont/geosparql#",
      "name": "schema:name",
      "comid": {
        "@id": "schema:containedInPlace",
        "@type": "@id"
      },
      "hyf:linearElement": {
        "@type": "@id"
      }
    }
  ],
  "@id": "https://waterdata.usgs.gov/monitoring-location/05430050",
  "@type": [
    "https://www.opengis.net/def/schema/hy_features/hyf/HY_HydroLocation",
    "https://schema.org/Place"
  ],
  "source": "nwissite",
  "sourceName": "NWIS Surface Water Sites",
  "name": "BADFISH CREEK NEAR OREGON, WI",
  "comid": "https://geoconnex.us/nhdplusv2/comid/13296678",
  "hyf:referencedPosition": [
    {
      "hyf:HY_IndirectPosition": {
        "hyf:linearElement": "https://geoconnex.us/ref/mainstems/473915"
      }
    },
    {
      "hyf:HY_IndirectPosition": {
        "hyf:distanceExpression": {
          "hyf:HY_DistanceFromReferent": {
            "hyf:interpolative": "64.4213"
          }
        },
        "hyf:distanceDescription": {
          "hyf:HY_DistanceDescription": "upstream"
        },
        "hyf:linearElement": "https://labs.waterdata.usgs.gov/geoserver/wmadata/ows?service=WFS&version=1.0.0&request=GetFeature&typeName=wmadata%3Anhdflowline_network&outputFormat=application%2Fjson&cql_filter=reachcode='07090002008279'"
      }
    }
  ],
  "geo": {
    "@type": "schema:GeoCoordinates",
    "schema:longitude": -89.329007,
    "schema:latitude": 42.92805628
  },
  "gsp:hasGeometry": {
    "@type": "http://www.opengis.net/ont/sf#Point",
    "gsp:asWKT": {
      "@value": "POINT(-89.329007 42.92805628)",
      "@type": "http://www.opengis.net/ont/geosparql#wktLiteral"
    }
  }
}

yeah you're right that works.
@dblodgett-usgs do you want the reachcode to be the geoconnex pid or the wfs call?
Incorporateing everything discussed so far, I think this
 {
 	"@context": [{
 		"schema": "https://schema.org/",
 		"geo": "schema:geo",
 		"hyf": "https://www.opengis.net/def/schema/hy_features/hyf/",
 		"gsp": "http://www.opengis.net/ont/geosparql#",
 		"name": "schema:name",
 		"comid": {
 			"@id": "schema:geoWithin",
 			"@type": "@id"
 		},
 		"hyf:linearElement": {
 			"@type": "@id"
 		},
 		"source": "schema:provider"
 	}],
 	"@id": "https://waterdata.usgs.gov/monitoring-location/05430050",
 	"@type": [
 		"https://www.opengis.net/def/schema/hy_features/hyf/HY_HydroLocation",
 		"https://schema.org/Place"
 	],
 	"source": {
 		"@type": "schema:Organization",
 		"schema:url": "https://waterqualitydata.us",
 		"schema:name": "WQP",
 		"schema:description": "Water Quality Portal"
 	},
 	"name": "BADFISH CREEK NEAR OREGON, WI",
 	"comid": "https://geoconnex.us/nhdplusv2/comid/13296678",
 	"hyf:referencedPosition": [{
 			"hyf:HY_IndirectPosition": {
 				"hyf:linearElement": "https://geoconnex.us/ref/mainstems/473915"
 			}
 		},
 		{
 			"hyf:HY_IndirectPosition": {
 				"hyf:distanceExpression": {
 					"hyf:HY_DistanceFromReferent": {
 						"hyf:interpolative": "64.4213"
 					}
 				},
 				"hyf:distanceDescription": {
 					"hyf:HY_DistanceDescription": "upstream"
 				},
 				"hyf:linearElement": "https://geoconnex.us/nhdplusv2/reachcode/07090002008279"
 			}
 		}
 	],
 	"geo": {
 		"@type": "schema:GeoCoordinates",
 		"schema:longitude": -89.329007,
 		"schema:latitude": 42.92805628
 	},
 	"gsp:hasGeometry": {
 		"@type": "http://www.opengis.net/ont/sf#Point",
 		"gsp:asWKT": {
 			"@value": "POINT(-89.329007 42.92805628)",
 			"@type": "http://www.opengis.net/ont/geosparql#wktLiteral"
 		}
 	}

 }

Yeah -- geoconnex pid.

ehh may have to rethink provider as source predicate
https://validator.schema.org/#url=https:%2F%2Freference.geoconnex.us%2Fcollections%2Fdams%2Fitems%2F1000195

some alternative candidates for schema:provider
https://schema.org/maintainer
https://schema.org/sourceOrganization
also maybe feature_data_source can be mapped to
https://schema.org/isBasedOn

Out of those two options, I would lean towards maintainer. @dblodgett-usgs what do you think?

I thought about it more, provider could maybe still be sued but the issue is a little deeper.
https://github.com/internetofwater/tracker/issues/5

One thing to note for the source schema:url is that we don't have info specifically for that. The best I could do is grab the base url from the @id. If it uses a subpath, that would make things trickier.

Should we drop the schema:Place type?  In this case, @id is literally a web resource that would be expected to have a schema:about that is a schema:Place.

dropping schema:Place also fixes the provider/maintainer issue

Mine is generally the same, but includes the mainstem alias.
{
  "@context": [
    {
      "schema": "https://schema.org/",
      "geo": "schema:geo",
      "hyf": "https://www.opengis.net/def/schema/hy_features/hyf/",
      "gsp": "http://www.opengis.net/ont/geosparql#",
      "name": "schema:name",
      "source": "schema:provider",
      "comid": {
        "@id": "schema:geoWithin",
        "@type": "@id"
      },
      "mainstem": {
        "@id": "hyf:linearElement",
        "@type": "@id"
      }
    }
  ],
  "@id": "http://www.waterqualitydata.us/provider/NWIS/USGS-WI/USGS-05430050/",
  "@type": "https://www.opengis.net/def/schema/hy_features/hyf/HY_HydroLocation",
  "source": {
    "@type": "schema:Organization",
    "schema:name": "WQP",
    "schema:description": "Water Quality Portal"
  },
  "name": "BADFISH CREEK NEAR OREGON, WI",
  "comid": "https://geoconnex.us/nhdplusv2/comid/13296678",
  "hyf:referencedPosition": [
    {
      "hyf:HY_IndirectPosition": {
        "mainstem": "https://geoconnex.us/ref/mainstems/473915"
      }
    },
    {
      "hyf:HY_IndirectPosition": {
        "hyf:distanceExpression": {
          "hyf:HY_DistanceFromReferent": {
            "hyf:interpolative": "64.4213"
          }
        },
        "hyf:distanceDescription": {
          "hyf:HY_DistanceDescription": "upstream"
        },
        "hyf:linearElement": "https://geoconnex.us/nhdplusv2/reachcode/07090002008279"
      }
    }
  ],
  "geo": {
    "@type": "schema:GeoCoordinates",
    "schema:longitude": -89.329007,
    "schema:latitude": 42.9280563
  },
  "gsp:hasGeometry": {
    "@type": "http://www.opengis.net/ont/sf#Point",
    "gsp:asWKT": {
      "@value": "POINT(-89.329007 42.9280563)",
      "@type": "http://www.opengis.net/ont/geosparql#wktLiteral"
    }
  }
}

So we still have a minor issue that @ksonda has me thinking about.
{
  "@id": "http://www.waterqualitydata.us/provider/NWIS/USGS-WI/USGS-05430050/",
  "@type":
  [
    "https://www.opengis.net/def/schema/hy_features/hyf/HY_HydroLocation",
    "https://schema.org/Place"
  ],
  "schema:provider":
  {
    "@type": "schema:Organization"
  }
}

Theoretically works, but many of the things we will have as @id in these documents will be identifiers for literal places -- not identifiers for web pages who's subject is a place as is the case here.
Would it be so bad to look at this as both cases are kind of a hybrid, where the @id is kind of always an identifier for the real place and an identifier for a real-world feature? If we do that, then saying that the @type is schema:Place is correct in both cases -- using indirect identification in one case and direct identification in the other.

I would recommend avoiding ambiguity on whether it might be one thing or another. We can't assume the end user will know which is which.

I tend to agree with @EthanGrahn , although we don't currently have a machine-readable way of disambiguating "real world thing" from "website about that thing" within the NLDI data model other than possibly the use of a geoconnex.us identifier...maybe the NWIS and WQP sites are currently a special case that IMHO could be changed eventually.
That said, @dblodgett-usgs proposal would work if we added "@type": "schema:CreativeWork" to everything, on the wishy-washy premise that the mere act of identifying a location is an act of creation, as is putting a streamgage there or making a website about it.
I prefer replacing the provider concept with subjectOf relationship like this
"schema:subjectOf": {
    "@type": "schema:CreativeWork",
    "schema:identifier": "WQP",
    "schema:name": "Water Quality Portal"
  }

or possibly even
"schema:isPartOf": {
    "@type": "schema:Dataset",
    "schema:identifier": "WQP",
    "schema:name": "Water Quality Portal",
    "schema:distribution": {
         "@type": "schema:DataDownload",
         "schema:contentUrl": "https://www.waterqualitydata.us/data/Station/search?mimeType=geojson&minactivities=1&counts=no",
         "schema:contentEncoding": "application/geo+json"
    }

I think both options are good. The second is better if we want to be pretty explicit as to what the nldi actually knows about the source. It knows that it retrieved GeoJSON data from that source uri. I'm also partial to not including the contentUrl.

if you don't want to do contentUrl I don't know if I see the value of the second option that much
(1) I'm part of a geojson dataset in a geojson format but you dont need to know the url from here
"schema:isPartOf": {
    "@type": "schema:Dataset",
    "schema:identifier": "WQP",
    "schema:name": "Water Quality Portal",
    "schema:distribution": {
         "@type": "schema:DataDownload",
         "schema:contentEncoding": "application/geo+json"
    }

vs
(2)
I'm part of a dataset with this name (and btw by "dataset" in this case i mean federated data system with a common api endpoint but im not giving you any link to it)
"schema:isPartOf": {
    "@type": "schema:Dataset",
    "schema:identifier": "WQP",
    "schema:name": "Water Quality Portal",

vs
(3) I am part of something called the WQP
"schema:subjectOf": {
    "@type": "schema:CreativeWork",
    "schema:identifier": "WQP",
    "schema:name": "Water Quality Portal",

(3) seems like the least-common denominator and to have the least amount of weird caveats

I agree. schema:Dataset doesn't make any sense without pointing to the dataset.

Agreed. I guess let's go with 3 and plan on adding a "source information" link to the crawler source table and use it here in the future?


Image with optical corrections

Hello,
I use this plugin and noticed the optical in-corrections in the image of "rotate".
Maybe you want to use my adjust image below.
Thx

Thank you - I've committed this to the repository.


Real Device Bug

I have successfully using this template to make APK, so impressive size is 13MB and startup just 3-4 seconds
But when Apps I minimize using Back button or else, then I open again both from Icon or from Home, then show me
"View already has a parent. View: Page (4) Parent: Frame (10), undefined"

Hi!
This is actually a known nativescript-vue bug. You may check its progress here: https://github.com/rigor789/nativescript-vue/issues/59


test fun

add test
update doc

Codecov Report

Merging #8 into master will increase coverage by 16.98%.
The diff coverage is 93.87%.

@@             Coverage Diff             @@
##           master       #8       +/-   ##
===========================================
+ Coverage   55.76%   72.75%   +16.98%
===========================================
  Files          10       10
  Lines         373      378        +5
  Branches       30       32        +2
===========================================
+ Hits          208      275       +67
+ Misses        164      101       -63
- Partials        1        2        +1

Impacted Files
Coverage Δ

tools/index.ts
100% <100%> (ø)
:arrow_up:

src/data-types/list.ts
56.41% <100%> (+5.19%)
:arrow_up:

src/data-types/string.ts
100% <100%> (+52%)
:arrow_up:

src/common/base.ts
96% <100%> (ø)
:arrow_up:

src/data-types/set.ts
52.77% <100%> (ø)
:arrow_up:

src/data-types/hash.ts
65.71% <100%> (+2.85%)
:arrow_up:

src/data-types/key.ts
100% <100%> (+42.85%)
:arrow_up:

src/common/protocol.ts
83.09% <62.5%> (+29.13%)
:arrow_up:

Continue to review full report at Codecov.

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


Bootstrap ActiveField checkbox ignores label option

The Bootstrap version of ActiveField checkbox function seems to ignore anything passed in on the label option and is always using the attribute label from the model.
use yii\bootstrap\ActiveForm;
$form = ActiveForm::begin();
echo $form->field($model, 'a_checkbox')->checkbox(['label' => 'This should display but does not.'])
ActiveForm::end();

I have worked around it using the following as suggested in some other issues, but I would imagine that others will probably have the same issue as Yii2 starts to be used more often.
echo $form->field($model, 'a_checkbox')->checkbox()->label('This should display and it does.')

Looking at some other related issues, I can't tell if this is intended behavior or not.  If it is the correct behavior, the docs should probably be updated to not inherit the non-Bootstrap ActiveField checkbox function description, as that makes it seem like passing in the label should work.

I confirm this issue.
@cebe  What is the expected behavior for radio/checkbox button with label option?

@pana1990 It should work, of course.
As a sidenote, there's a little difference between label() and passing label as option:

label() will create a full  tag (for checkboxes and radios: only if enclosedBylabel is false)
passing label option will use the raw string as label and not create a  tag

@mikehaertl @samdark radio and checkboxes of bootstrap extension have not same behavior that radio and checkbox of widgets
I think to it should be documented the methods. Currently it has inheritdoc.
what do you think about it?

@pana1990 right. I'll go over all the methods in ActiveField and add apropriate docs.

@pana1990 After some more thinking, I'm not really sure, if the method is so much different. What exactly are you missing?

when checkbox() or radio() function uses label method(), it has behavior different,
for example :
<?= $form->field($model, 'subject')->checkbox(['label' => 'TestOption'], true)->label('TestLabel') ?>
<?= $form->field($model, 'subject')->checkbox([], true)->label('TestLabel') ?>

it generated with yii\bootstrap\ActiveForm :

and with yii\widgets\ActiveForm :

@pana1990 I would say that the former is not really relevant use case (mixing label option with label() method). And the second rather looks like something that probably needs fixing in yii\widgets\ActiveField.

Sorry for "Hijacking", but I think my issue fits too. It seems there is no way to add HTML options to a label when using checkboxes with a custom template.
The following works in my scenario:
<?= $form->field($model, 'myAwesomeField')
                 ->label('Awesome Label', ['class' => 'awesome-label']);
                 ->checkbox(); // Works ?>

But since I'm controlling the labels via attributeLabels() I don't really want to do that. And I don't want to repeat the options again and again.
This - so I thought - should work too.
<?php
$form->fieldConfig['horizontalCheckboxTemplate'] =  "{beginWrapper}\n
\n\n{input}\n\n\n
\n{endWrapper}{label}\n
{hint}
\n
{error}
";
$form->fieldConfig['labelOptions'] = ['class' => 'awesome-label'];
?>
<?= $form->field($model, 'myAwesomeField')
                 ->checkbox(); // Does not work ?>

If I pass $enclosedByLabel as false for checkbox() it works, but my horizontalCheckboxTemplate is not used, instead template is used (of course now I've found out about it, by writing this post.)
So using "template" solves my problems. My only point is now, please document this kind of stuff. It really is frustrating. I basically have to read through core code to understand stuff like this, because it is not written anywhere, or maybe not easy to find.
Sorry again for hijacking. :)

@mikehaertl  you right, thanks for you comment

@fortex For now you can find many examples here: http://codemix.github.io/yii2-bs3activeform/index.html. This project was the predecessor of yii\bootstrap\ActiveForm and ActiveField, before it was merged into the official code base. So most of the examples are still valid.
I agree that something like this should be included in the Yii 2 documentation. I'm just not sure who's responsible.


Fix implement projection

The implement projection should be fixed now. The offset needed to be added in the odometer transformation frame.

[x] Test in simulation
[x] Add Pose3d -> Point3d function to rosys
[ ] Wait for new rosys release with https://github.com/zauberzeug/rosys/pull/185
[ ] Test on real robot

Since the new rosys version is now merged, we can test it this week


docs: remove interactive modal breaking gatsby build

Modal is breaking in gatsby, therefore preventing the doc site from being built. This needs to be updated in the modal component in the future.

Coverage decreased (-0.07%) to 88.422% when pulling a42f033a2f102d3123ddcb44676d096bf9c5ad9b on abutterworth/fix-docs-modal into b84d0584d867530ea76b17f08dc49a012cc122c9 on master.

:tada: This PR is included in version 4.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


build: switch to github actions instead of TravisCI

Codecov Report

Merging #512 into master will decrease coverage by 1.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #512      +/-   ##
==========================================
- Coverage   54.97%   53.46%   -1.51%
==========================================
  Files          96       97       +1
  Lines        3551     3675     +124
==========================================
+ Hits         1952     1965      +13
- Misses       1249     1362     +113
+ Partials      350      348       -2

Impacted Files
Coverage Δ

pkg/database/mysql.go
58.69% <0.00%> (-2.18%)
:arrow_down:

cmd/server/main.go
10.60% <0.00%> (ø)

pkg/upload/sftp.go
69.10% <0.00%> (+2.61%)
:arrow_up:

pkg/upload/filename_template.go
81.48% <0.00%> (+7.19%)
:arrow_up:

Continue to review full report at Codecov.

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


#113 don't use WriteFile for now

It seems that WriteFile was added in Go 1.16. Since otel-cli seems to have at least one user building with an older Go, this seems like a resonable change especially since most folks don't use the server part.

gonna hold off on this, #136 seems to force a Go upgrade anyways

Superceded by #138