devnet: bump local-celestia-devnet to v0.11.0-rc6

Overview
This PR updates the local-celestia-devnet version to v0.11.0-rc6.
While here, fix op-batcher dependencies and healthcheck.
Fixes #136
Checklist

[x] New and updated code has appropriate documentation
[x] New and updated code has new and/or updated testing
[x] Required CI checks are passing
[x] Visual proof for any user facing features like CLI or documentation updates
[x] Linked issues closed with keywords

utACK
Docs that need updating with new version

[ ] https://docs.celestia.org/developers/optimism-devnet/
[ ] https://docs.celestia.org/developers/optimism/ (mostly this caution flag)

@jcstein are these version updates in the docs variables yet? We can reapply what we did for app and node here. LMK how i can help.

would appreciate your help adding them if you can, possibly when version is updated
Could be in constants.js and updated manually, or in workflow somehow to use API to ping celestiaorg/optimism repo

but hitting this on arabica, but it is a local issue


save() for a 16bit Image does not preserve the 16 bit property.

julia> img
Gray Images.Image with:
  data: 256×256 Array{ColorTypes.Gray{FixedPointNumbers.UFixed{UInt16,16}},2}
  properties:
    colorspace: Gray
    spatialorder:  x y

julia> save("test.jpg", img)

julia> load("./test.jpg")
Gray Images.Image with:
  data: 256×256 Array{ColorTypes.Gray{FixedPointNumbers.UFixed{UInt8,8}},2}
  properties:
    colorspace: Gray
    spatialorder:  x y

http://blogs.adobe.com/jkost/2010/07/saving_16_bit_images_as_jpeg.html. Use PNG if you want 16-bit.
For future reference, Images.jl doesn't do any IO itself; any load/save issues might be better filed with the relevant package (e.g., ImageMagick.jl, QuartImageIO.jl, or whatever it is that's doing the saving), simply because any PR that closes that issue will be against the relevant package.

Ok :)


Highlight previous folder when going up a directory

Resolves #1763
(I haven't tested it much so there might be some bugs but very unlikely)

@d2dyno1 I found an issue,

Select an item in recycle bin
Naivagte to a different directory
Go back to recycle bin

@yaichenbaum fixed

Great work!


Druid Column Type does not get updated

Make sure these boxes are checked before submitting your issue - thank you!

[/] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[/] I have reproduced the issue with at least the latest released version of superset.
[/] I have checked the issue tracker for the same issue and I haven't found one similar.

Superset version
0.28.1
Expected results
When a column type in Druid (0.12.3) is changed (for example "String" -> "Long") and a "Refresh Metadata" is done, Superset gets the columns of the latest segment and updates all necessary Types (Column now has type "Long").
Actual results
Looking at the code, it does exactly as expected. In practice, the types in Superset stay the same (e.g. "String").
The Column type in Druid is now "Long" and displayed as "String" in Superset. This can be verified by metadata queries.
No Logs are shown in the process of refreshing metadata.
Steps to reproduce

Ingest Data into Druid with String Columns in Druid and point Superset to it
Change a column type in Druid and refresh metadata in Superset

Without Superset adapting the new data type, queries that sum up the values of a column cannot be done via Superset. If the column is given capability to "sum" in the datasource edit section, Superset tries to do a "StringSum" when running the query, which does not exist in Druid.

someone else could be resolving this issue?

If I remember correctly, the column type gets updated one week after it has been changed, as superset requests metadata for the last week of available druid data for every topic. So you either need to wait one week or re-add the datasource to superset.

OMG, well I'm learning superset and just right now I don´t know hos tu re-add the data source to superset, can you send me a link to do it, please.
And I appreciate your answer, have a nice day!

If I remember correctly, the column type gets updated one week after it has been changed, as superset requests metadata for the last week of available druid data for every topic. So you either need to wait one week or re-add the datasource to superset.

----Could you tell me, where can i find the code in superset to change that time, because i think is a lot of time to wait and see the change if i need to change column types frecuently its imposible to wait.
And thank you very much , your help was so helpfull. Best regards

Sorry to keep you waiting so long, here you go https://github.com/apache/incubator-superset/blob/e55fe43ca67a29518674a1a2137a3dbd4f166864/superset/connectors/druid/models.py#L647


Flatten transforms before generating OpenSCAD

The transform hierarchy is extra information that I don't care about when loading it in OpenSCAD, but it creates extra work every time OpenSCAD has to reload the model.
Calculating and applying the transform nodes ahead of time can potentially save a significant amount of time and space.

This is only viable for shapes that are unique. For Shape nodes that are reused (with DEF and USE), duplicating them to precalculate the transform would save some computation but would increase vertex/face count, and could increase space and memory usage.


Add the concept of an object-store UUID to identify it

E.g. to associate it with an existing DB, or to uniquely refer to it.
This could be generated during the init_container call and then stored in the repository config json

Also:

add a version of the repository (or of the library that wrote it)
during init, make sure the configuration makes sense and there are no unexpected values

@sphuber do we want this in AiiDA, so we know we are pointing to the right container? A bit like the UUID for RabbitMQ, or the same for the DB (I don't know if we have one implemented yet).
Also, should it be generated when creating the container, or should it be settable?

I don't think it is necessary. We don't have it now, after all, currently we also just have an absolute filepath in the profile pointing to the database. However, it might actually be a useful feature, and will allow us to perform some sanity checks. If we implement this, I would definitely lean to not allowing a user to determine the UUID, we just generate one. For the interface in the disk-objectstore you may want to allow passing in the filepath and the UUID of a container when initializing it and disk-objectstore will then perform the consistency check. I guess the construction of a container would return a UUID then, which we can store in AiiDA's database settings to make the connection when we create a container for a profile the first time


Replace current tools and partner images

What does this PR do?
This PR:

Replace current tools in tools page with those in https://newslab.withgoogle.com/training/tools
Remove partners page from nav bar and move them to "Awards Section" on both Index and certification pages.

Description of tasks performed

Modify the blue-section of the tools page

Add a sub-nav bar that contains tools, courses and Advanced learning to the tools page

Add Horizontal rule below the sub-nav bar

Add the first row of cards on Google tools selection

Add subsequent rows of cards on Google tools section

Add “follow us on social media” section to the front end page

Integrate the changes made in  front end to the course builder

Remove partners page from nav bar on index and certification page in front-end directory

Move partners page contents to index page in front-end directory

Move partners page content to certification page in front-end directory

Integrate the changes made on front-end directory into course builder

Update partners name accordingly

Ensure partner images and texts are uniform in size and height.


work in ios?

its not working in ios safari or webview any solution?

Older version of the library is used here. Please update to latest version.

will it work on safari with latest version?


Timesketch Import Fail

Hello and happy new year!
I seem to be having some issues with getting the import working for timesketch.

Some background of my configuration
System: Proxmox
OS: Ubuntu 20.04.06
Node-red: Setup via npm (bash <(curl -sL https://raw.githubusercontent.com/node-red/linux-installers/master/deb/update-nodejs-and-nodered). I tried the standard npm install but there were quite a few errors....
I also tried the docker version but couldnt work out how to give the Node-Red account access to the cases folder.
TimeSketch / Log2Timeline: Installed via the recommended tsplaso_docker_install.sh script
For the script there was an error for open search so I had to remove the following items.

These are the changes I made in Node Red
Triage Artefact Processor Flow
For the process variable should I leave it as localhost or put the IP that I use to access timesketch?
Also the kape output actually has the logs in /C/Windows/System32/winevt/logs. I see from slack it says its successful so I didnt amend the path.

For log2timeline I was not sure from the documentation what to change so I left it as is.

Hayabusa Process Flow
For Hayabusa I tried the latest version which now uses a wizard prior to starting and thought that might interfere with it starting so I downgraded and used the 2.5.1 version

Slack Notifications Flow
Slack notification is configured and works fine.
Thank you for your time and help!
Warm regards,
Marc

Try with rm ~/.timesketchrc ~/.timesketch.token

Still fails unfortunately...

Does the manual upload via the WebUI also fail? If it doesnt it must be a problem with the API.... i think. Im quite new to this.

Sorry for the delay. I am working an update of the workflow project. In the meantime please checkout if this gets resolved with the latest version of Timesketch and timesketch importer.


Mark peers not contributing signature shares as faulty

While writing the liveness proof for federated e-cash I noticed there is a situation in which f=n-t malicious members can prevent the federation from making progress on signing e-cash tokens.
Each HBBFT consensus round includes the proposals from n-fmembers, otherwise f members could block the consensus by delaying their contribution indefinitely. The other way around works too by just being early, then some other random honest member will be left out. If that's the case the dishonest member could simply never contribute signature shares and the federation would only ever get n-2f signature shares, which is less than the required t to combine to a signature.
There are two ways to fix this:

Requiring members to contribute signature shares the next round one is part of the consensus set and otherwise be banned (by not processing the peer's messages anymore). Unfortunately that would mean not being able to postpone signing if too little CPU resources are available (tx processing is more important, as soon as a tx is confirmed it can be accepted even without receiving e-cash tokens because that is guaranteed to happen eventually).
Requiring members to contribute a signature share after Δe epochs in the next round they are in the consensus set, otherwise they get excluded.

I think 1 would be more reasonable for now even though it requires some re-engineering afaik to make sure members always contribute in time. But premature optimization has bitten me way too often by now and 2 is just very comlex …

What about the other functions that require threshold sigs such as signing PSBTs for PegOuts?
Banning could be too dramatic if a peer goes down for a while how would they get unbanned?  Should this be tied to a punishment mechanism like fidelity bonds?
If the federation's membership drops should it try to recreate the public key at some point to lower the number of signing nodes required?

Banning could be too dramatic if a peer goes down for a while how would they get unbanned?

We'd only ban in case a peer makes a contribution but doesn't include an expected signature (same for e-cash tokens and PSBT signing), so you'd need to actively tamper with the code for that to happen. If they don't make a contribution at all that's ok.
The problem with making a contribution without including signatures is that only n-f contributions end up in the consensus set, so if f honest peers were excluded that way the remaining f  malicious ones could stop the federation from making progress.

Ah, I understand now.  Malicious peers can make HBBFT succeed while DoS attacking Minimint consensus.
There might be other similar attack vectors such as trying to lower the median block height during RoundConsensus

Taking a look at the code I'm thinking we introduce a new ConsensusItem::DropPeer that modules can write to the database if there is an problem that warrants dropping a peer.  Inside MinimintConsensus we can query for these items and pass them to the HBBFT thread where if detected it will drop that peer connection.


Remove libcontainer from containerd-shim

Libcontainer was only used for a single function, which in itself was just a tiny wrapper around golang.org/x/sys/unix; https://github.com/opencontainers/runc/blob/dbe44cbb1099eabfaa753322be2055a0a6e8fe2d/libcontainer/system/linux.go#L127-L130
// SetSubreaper sets the value i as the subreaper setting for the calling process
func SetSubreaper(i int) error {
	return unix.Prctl(unix.PR_SET_CHILD_SUBREAPER, uintptr(i), 0, 0, 0)
}

This patch replaces it with the implementation in our sys package

@AkihiroSuda ptal

LGTM excellent find!

The sys/reaper_linux.go defines SetSubreaper function. What about using the sys.SetSubreaper?

@fuweid good catch;  Let me use that one
Looking at that package, it looks like it's still defining a custom const for PR_SET_CHILD_SUBREAPER; I'll open a PR for that as well

@thaJeztah LGTM.

Updated, and replaced it with the one in sys
Doing a follow-up to fix that implementation (and doing some slight refactoring to move it into the sys/reaper package perhaps)

Codecov Report

Merging #4226 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #4226   +/-   ##
=======================================
  Coverage   38.34%   38.34%
=======================================
  Files          90       90
  Lines       12728    12728
=======================================
  Hits         4881     4881
  Misses       7181     7181
  Partials      666      666

Flag
Coverage Δ

#windows
38.34% <ø> (ø)

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 7d7104c...23aab35. Read the comment docs.

LGTM


issue with get_cmdclass

facing this issue - " AttributeError: module 'versioneer' has no attribute 'get_cmdclass' "
even after using the 0.19 version

If you're seeing that error, you probably have not installed versioneer into the project.
Have you run versioneer install before running setup.py?

yes I did a pip install versioneer

But not versioneer install? Please see the linked documentation.

i'll try this

Please reopen if this is still an issue.

Ok, this problem also arises in the following (I agree) bit weird situation:

has versioneer system-wide
patches the setup.py according to #193
running pip in a no-build-isolation mode.

The fix is quite easy (see my comment here: https://github.com/python-versioneer/python-versioneer/issues/193#issuecomment-958706634)
This should be the guideline for using versioneer I think.


x-input: correct the input type

Resolve #783
Please makes sure the items are checked before submitting your PR, thank you!

[x] Rebase before creating a PR to keep commit history clear.


component type error

BUG report
When

回滚volar到1.0.3版本等待解决吧

the same problem

Here is a reproduction repo
when open the App.vue file with vscode,
the component props error message would show like below

when the component has both <script setup> and <script> with export default defineComponent({}) existed

same error

回滚volar到1.0.3版本等待解决吧

回滚有效, 不过最近volar似乎不是很稳定.

+1

Same here, all my components components with inheritAttrs: false are throwing this error.

回滚volar到1.0.3版本等待解决吧

回滚有效, 不过最近volar似乎不是很稳定.

+1

In my case, these errors appear when calling methods defined via options API, e.g. this.myMethod(). I could workaround this in some cases by changing data() { ... to data: () =>. In this case, the type is correctly inferred. However, when I want to access the props in data and I need to change to data: (vm) => vm.myProp the inference is also broken.
Side note: The same errors appear also when building with vue-cli as soon as I switch from vue 2.7.10 to 2.7.11. As long as I stay on 2.7.10 this is only an IDE problem with Volar.

Was this really fixed? I'm getting:  not assignable to type ComponentProps when working with transition component

Same here: using Volar v1.0.9 (with takeover mode enabled, ofc) and this example.
It compiles and runs fine, it's just this error returned:
Type '{ width: string; }' is not assignable to type 'ComponentProps<string>'.
  Type '{ width: string; }' is not assignable to type 'string'.ts(2322)

Volar ts: 1.2.0

@johnsoncodehk this creates massive type errors in vue-tsc 1.3.10, somehow VS Code Volar 1.3.14 doesn't show the errors though. We can't basically use vue-tsc right now, as it emits too many unfounded errors, along the lines of
Argument of type '{ id: string; }' is not assignable to parameter of type '{ ref?: VNodeRef | undefined; key?: string | number | symbol | undefined; ref_for?: boolean | undefined; ref_key?: string | undefined; onVnodeBeforeMount?: VNodeMountHook | VNodeMountHook[] | undefined;


IRGen: Add missing bitcasts to emitNativeUnowned* operations.

Fixes rdar://problem/27664203.

@swift-ci Please test

@swiftix Does this look good for Swift 3?

CI config issue for mac OS failure.  Will re-run in a minute

@swift-ci test os x

@tkremenek Looks like there's still some kind of config issue with the second run.

@jckarter On it.

@swift-ci test os x

@jckarter LGTM. I'm testing it now on the original project mentioned in the radar, just for the case.

@jckarter I can confirm, it fixes the original problem reported in the radar. Thanks!

@swiftix Thanks! Does this test failure look familiar? It looks unrelated to this change.
******************** TEST 'Swift(macosx-x86_64) :: SILOptimizer/copyforward.sil' FAILED ********************
14:55:31 Script:
14:55:31 --
14:55:31 xcrun --toolchain default --sdk /Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk /Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-3.0-branch/buildbot_incremental/swift-macosx-x86_64/bin/sil-opt -target x86_64-apple-macosx10.9  -module-cache-path '/var/folders/_8/79jmzf2142z2xydc_01btlx00000gn/T/swift-testsuite-clang-module-cachehpXeuX' -enable-sil-verify-all /Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-3.0-branch/swift/test/SILOptimizer/copyforward.sil -copy-forwarding -enable-copyforwarding -enable-destroyhoisting | FileCheck /Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-3.0-branch/swift/test/SILOptimizer/copyforward.sil
14:55:31 --
14:55:31 Exit Code: 1
14:55:31
14:55:31 Command Output (stderr):
14:55:31 --
14:55:31
/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-3.0-branch/swift/test/SILOptimizer/copyforward.sil:257:10: error: expected string not found in input
14:55:31 //CHECK: copy_addr
14:55:31          ^
14:55:31 <stdin>:283:169: note: scanning from here
14:55:31 sil_scope 12 { loc "/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-3.0-branch/swift/test/SILOptimizer/copyforward.sil":260:13 parent @backward_takenoinit : $@convention(thin) <τ_0_0> () -> @out τ_0_0 }
14:55:31 <stdin>:283:173: note: possible intended match here
14:55:31 sil_scope 12 { loc "/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-3.0-branch/swift/test/SILOptimizer/copyforward.sil":260:13 parent @backward_takenoinit : $@convention(thin) <τ_0_0> () -> @out τ_0_0 }
14:55:31 <stdin>:294:2: error: CHECK-NOT: string occurred!
14:55:31  copy_addr [take] %1 to %0 : $*T, loc "/Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-3.0-branch/swift/test/SILOptimizer/copyforward.sil":266:3, scope 12 // id: %5
14:55:31  ^
14:55:31 /Users/buildnode/jenkins/workspace/swift-PR-osx/branch-swift-3.0-branch/swift/test/SILOptimizer/copyforward.sil:273:14: note: CHECK-NOT: pattern specified here
14:55:31 //CHECK-NOT: copy_addr
14:55:31              ^
14:55:31

@jckarter No, this test failure doesn't look familiar. I cannot remember seeing it.

The failure did not repro in master, and I don't think it can possibly be related to this patch, which only touches IRGen. Any ideas @eeckstein or @aschwaighofer ?

I don't see how this commit can possibly affect the outcome of the SIL optimizer.
(Other than unrelated non deterministic uninitialized memory bugs)

no idea either


Is there a way to get coverage reports reliably?

It looks like current coverage reports return by karma-coverage are weirdly minified and just have require('<the-test-file>'). So you can't really get coverage reports.

I haven't done much coverage testing myself. Before I dive deep into this, can you provide a sample repo where coverage reports work in another launcher (e.g. Firefox, Chrome) and don't work in karma-electron? It would save me a bunch of time

@twolfson I haven't used karma-coverage for browsers yet! But sure I can put a small sample repo.

Here is the sample repo i put up on github to see the issue do:
git clone git@github.com:cPhost/coverage-sample-repo.git
npm i
npm test

The coverage html will be generated in coverage directory.
The browser report would have correct report while electron one would be wrong.

Looking into this now

I've successfully reproduced the issue. It might be due to our lack of sourcemap support. Going to try messing with some settings to see how the coverage tool reacts

This test repo saved me a buuuunch of headaches, thanks =D

A little bit of progress, it looks like we set loadScriptsViaRequire: true. Unfortunately, that removes the would-be content from this file and apparently breaks coverage
However, the report still looks awful due to a lack of sourcemap telling it "hey, ignore this require section". I'm going to size up adding this in...

tl;dr - Going to take a bit of break. Will try again by the end of next weekend
Okay, I've spent about an hour on this and have a general idea of what needs to be done:

Warn users about lack of source map support when using loadScriptsViaRequire
Create/extend source map for other scenario

I have something that should work but I'm not iterating easily with it. I think I need to step back, reapproach source maps with a fresh set of eyes on a proof of concept (hard to know if what I'm doing is right with all these layers of coverage and Electron). Will prob be best to find a source map inspector/similar and use that as template for what we're doing
Should be as simple as creating a file with only a few characters offset on first line (e.g. void 0), then creating a source map for said file, then verifying its source map result is what we want
Going to take a bit of break. Will try again by the end of next weekend

Thanks for detailed updates on this (and working on the issue, appreciate it).
I think the use case for this is mostly going to be for a library's or npm packages for electron apps rather than electron apps themselves since it tedious to test the whole app and know what parts you missed.
I did need any sort of coverage needs for send-feedback webcomponent since I had an idea of whats going on and what needed to be tested before each release -> tests. But when working for some utilities like the utils repo on electron-elements it had some complex logic which I need to know it is well tested before each release and is a lot of manual testing to remember.
Once again thanks for working on it, and karma-electron provides a great and easy way to test electron app compared to something like spectrum.


Where's the doc about HTMI

The documentation links to https://github.com/kengz/aiva/tree/master/docs/HTMI.md but the link is broken same for Context Aware Knowledge Graph

Oops recently moved the doc to the main doc page. Forgot to update the link. Here's it for the mean time http://kengz.me/aiva/#human-turing-machine-interface

updated!


ADBDEV-4909-11: Remove redundant funcexpr check for NULL.

Remove redundant funcexpr check for NULL.
At this point, funcexpr is always not NULL, so I replaced funcexpr's redundant
NULL check with an assertion.

Can you add a brief comment why it can't be null?


Please also make similar app for n8n.io

Node-Red desktop is great app for quickly prototyping ideas and testing logic and APIs.
Please also look at https://n8n.io/ which offer many connectors to popular services out-of-the-box and can be used with Node-Red to consume these services.
It will be great to have a similar desktop version of n8n.io.

@ch3ckmat3 here it is https://docs.n8n.io/getting-started/installation/#desktop-app

Oh great! Thank you for the pointer.


UX Design - Customization to Threaded Comments in PDF Tron

Title of ticket: UX Design - Customization to Threaded Comments in PDF Tron
Description
Work through UX Design for Customizations with PDF to bring it up to the level our users need to track and protect users privacy and comments in new Redaction APP.
Dependencies

[ ] Confirmation of who needs access to what comments (IAO vs. Ministry - wont go any deeper then this)

DOD

[ ] Any changes to threaded comments as they exist now to better meet users needs
[ ] The organization of comments based off of users and there persona and what they need out of comments
[ ] Comments in relation to Peer Review
[ ] Comments in relation to harms between IAO and Ministry
[ ] Comments internal to IAO and with Analyst doing redaction
[ ] Comments between IAO and Ministry in relation to Sign Off
[ ] Ability to sort comments based off of user groups

Moving to ice box, as this customization is not a priority for MVP release of PDF Tron


No worries @Remi-Gau, this was just a draft PR. I am still trying to figure out the exact details so I am happy for non immediate feedback.

I wonder if I can keep editing the hack PR even though it has already been integrated into the website once?

yup if you edit the top message the CI will grab the new content and open a PR that I just have to merge.
Feel free to edit.


Refs #25778 -- Updated some links and references to HTTPS.

ticket-25778 has been open a while and had several PRs updating references, here’s another.

@adamchainz Thanks :+1:


Display client username and timestamp when a message is received

When a client sends a message to the server, it would be useful to display the username of the client and the timestamp of the message. This would make it easier to identify the sender and to track the timing of messages.
To implement this feature, the server will need to receive and store the client's username when they first connect. Then, when a message is received from that client, the server will need to retrieve the stored username and the current timestamp, and display them alongside the message.

Hi, I want to solve this issue, I want to start by asking the client to type a username that I will save and send to the server with every message.

of course, go ahead

@SparTiCoot make sure to checkout the latest updates on the repo, we've added Terminal UI for the app

Ok, I check. Thanks

@duckduckcodes
Should I work on the branch duckduckcodes-patch-1 or create a new one ?

ahh that's great, what you should do now, is make a pull request from your branch to the master branch, so i can review it and resolve conflicts, then i can merge

@duckduckcodes
When I run "git push origin feature/display-username-timestamp",
I encounter the following error:
"git push origin feature/display-username-timestamp
ERROR: Permission to duckduckcodes/updog.git denied to SparTiCoot.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists."

that's because you have to make a pull request, qo to your forked repo, and click on pull requests, and i should review it then merge it

Pull request submitted, I have explained everything in the comments and in the commits


why ply only

why does this only accept ply files? ideally we could support more than just vertex colors?

What format would you like support for? And, what do you mean by “more than just vertex colors” — are you talking about spherical harmonics?

Yeah SH would be nice

I've split Spherical Harmonics out to issue #10. Nobody said what formats you'd like support for; the top two I've seen around are Kevin Kwok's antimatter15 "splat" files, and PlayCanvas's "Compressed PLY" which is already requested in issue #7, so I'll go ahead and repurpose this issue for splat files in particular.

Implemented by commit 32c1669


file name saved under .c but changes to .c++ automatically

Issue Type: Bug
when i try to add a new file named 03_03.c it changes to c++ file type .....instead of c type.
VS Code version: Code 1.59.0 (379476f0e13988d90fab105c5c19e7abc8b1dea8, 2021-08-04T23:13:12.822Z)
OS version: Windows_NT x64 10.0.19042
Restricted Mode: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i3-1005G1 CPU @ 1.20GHz (4 x 1190)

GPU Status
2d_canvas: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onrasterization: enabledskia_renderer: enabled_onvideo_decode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
3.77GB (0.88GB free)

Process Argv
--crash-reporter-id 614bf1ab-e90b-41d5-a208-84c24c200bde

Screen Reader
no

VM
0%

Extensions (14)

Extension
Author (truncated)
Version

doxdocgen
csc
1.3.2

code-runner
for
0.11.5

vscode-pull-request-github
Git
0.29.2

better-cpp-syntax
jef
1.15.6

remote-containers
ms-
0.191.0

remote-ssh
ms-
0.65.7

remote-ssh-edit
ms-
0.65.7

remote-wsl
ms-
0.58.2

cmake-tools
ms-
1.7.3

cpptools
ms-
1.5.1

cpptools-extension-pack
ms-
1.0.0

vsliveshare
ms-
1.0.4673

vsliveshare-audio
ms-
0.1.91

cmake
twx
0.0.17

(1 theme extensions excluded)

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
pythonvspyt602:30300191
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
pythonvspyt639:30300192
pythontb:30283811
pythonvspyt551:30345470
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
pythonvsuse255:30340121
vscod805:30301674
pythonvspyt200:30340761
vscextlang:30333561
binariesv615:30325510
pythonvssor306:30344512
bridge0708:30335490
pygetstartedc2:30351386
vstre464cf:30350173
bridge0723:30351747

\gifPlease

\gifPlease

I can't repro this... I have a suspicion that it is caused by an extension.

Can you try extension bisect and see if there's a particular extension that's causing this?

I can't repro this... I have a suspicion that it is caused by an extension.

Can you try extension bisect and see if there's a particular extension that's causing this?

also share whats in your settings.

Its fixed now . Thanks for your time .


cli/workload/sync: MaxSyncTargetNameLength decreased by SyncerIDPrefix length

Summary
Fixes calculation of MaxSyncTargetNameLength. Currently MaxSyncTargetNameLength is 255, which is greater than DNS1123SubdomainMaxLength 253.

/retest

/retest


required checks for Bgee

the query is very slow even with two genes as input, any solution for improving?
add confidence_level_name

'confidence_level_name': 'high confidence level'

@dssib could you please check?

will check!

Thank you! The confidence level is being added by this PR: https://github.com/BioDataFuse/pyBiodatafuse/pull/120
@dssib is there a possibility to improve the efficiency of the query? for 4 genes it takes almost half an hour to get the output

yes, I have an idea - I think launching separate queries per gene will lead in much better performance, I will implement this during the next days

please check https://github.com/BioDataFuse/pyBiodatafuse/pull/124


Node not started on your end

Hello cat lover!
I think your node is not started on your side,
The seed is well typed in the net.cpp file: <IP_ADDRESS>  in hex code
But the connection is not going through, you've stopped it perhaps?
Thank you!

It should be up and running on the main network!
Try to add the node via the config:
addnode=<IP_ADDRESS>

Awesome thanks!


Error: The following formula cannot be installed from bottle and must be built from source.

Describe the bug
Following the README on installing the tool, I get the following error:
(base)  @094459  ~  brew install xcodeinstall
==> Downloading https://github.com/sebsto/xcodeinstall/archive/refs/tags/v0.1.ta
==> Downloading from https://codeload.github.com/sebsto/xcodeinstall/tar.gz/refs
                                                  #    #     #=O=#
==> Installing xcodeinstall from sebsto/macos
Error: The following formula cannot be installed from bottle and must be
built from source.
  xcodeinstall
Install the Command Line Tools:
  xcode-select --install

To Reproduce
Steps to reproduce the behavior:
brew install xcodeinstall

Screenshots
(base)  @094459  ~  brew install xcodeinstall
==> Downloading https://github.com/sebsto/xcodeinstall/archive/refs/tags/v0.1.ta
==> Downloading from https://codeload.github.com/sebsto/xcodeinstall/tar.gz/refs
                                                  #    #     #=O=#
==> Installing xcodeinstall from sebsto/macos
Error: The following formula cannot be installed from bottle and must be
built from source.
  xcodeinstall
Install the Command Line Tools:
  xcode-select --install

Desktop (please complete the following information):

OS: Monteray 12.5.1
xcodeinstall version 0.1

Thank you for reporting this. Do you have development tools installed on your machine ?
I should probably switch to distributing binaries instead of the source code.

Which development tools specifically? I have VSCode but I do not have Xcode installed.

OK, it might make sense to not have Xcode installed when using a tool to install it :-)
I just published v02 that install the binaries instead of compiling from source.
To install v0.2
brew upgrade
brew install xcodeinstall

If this works for you - I'll proceed and close this issue.

When I do that this time, I get the following:
==> Downloading https://github.com/sebsto/xcodeinstall/archive/refs/tags/v0.2.tar.gz
==> Downloading from https://codeload.github.com/sebsto/xcodeinstall/tar.gz/refs/tags/
                      #    #     #     #                                -=O=-
==> Installing xcodeinstall from sebsto/macos
Error: The following formula cannot be installed from bottle and must be
built from source.
  xcodeinstall
Install the Command Line Tools:
  xcode-select --install

Root cause found - the brew formulae only provides arm64 binaries.  It can not install on x86 machines at the moment
Going to follow up on this one : https://github.com/sebsto/xcodeinstall/issues/5


Release v2.14.0

New features

Handle safe-apps transactions with custom txGas value ( #1440 )
Make gasPriceOracle to be configurable for each network ( #1514 )
Add configuration to disable wallets that doesn't work in a specific network ( #1504 )
Add configuration for EWC and Volta networks compatibility ( #1253 )

Fixes

Token balance not updated after sending out all the balance for a token ( #1423 )
ERC721 Does not always appear ( #1509 )
Send ERC721 that uses a proxy contract ( #1508 )
Fix unexpected behaviour of collectibles list when safe has no collectibles ( #795 )
Collectibles groups aren't removed after sending last item ( #1503 )
Set network token in fiat value selector instead of hardcoded ETH ( #1498 )
Enabled modules aren't shown in advanced settings ( #1494 )
Update Sablier app to avoid stream errors in edge cases ( #1486 )
Update Aave app to latest version ( #1373 )
Fix safeTxGas estimation failing on non-Geth nodes ( #1515 )

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/xdai/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/xdai/app

A regression was run in the rinkeby network of this pr
For the other networks we checked mostly the connection, and signing of tx. We know and has been reported that.
Most wallets won't work on non-ethereum networks and those will be disabled
ENS names won't work on non-ethereum networks for now
The CryptoKitty token has an issue that is exclusive to that token. The other NFT's we were able to check are working fine.

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/xdai/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/rinkeby/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/xdai/app

Travis automatic deployment:
https://pr1537--safereact.review.gnosisdev.com/volta/app


[MB] Option to crawl for 3D version, regardless of quality set

Default crawling behavior would be filtering out 3D and only adding 720p quality. If one similarly would want to add 3D HSBS version in acceptable (1080p) quality to .crawljobs a separate option would be required.
e.g. crawl3d = true/false
would launch a separate logic that does not filter out 3d, but would instead look for 3D as well as 1080p (hsbs, even?) in the [MB] feed. Thus require 3d (or 3D) in a release title

With default settings (720p quality, filters) if [MB] is looking for the following line from Movies.txt:
Die Spam von Eggs Foojay Bar 2
Would automatically add these releases:
Die.Spam.von.Eggs.Foojay.Bar.2.2015.German.DTS.DL.720p.BluRay.x264-Group2
Die.Spam.von.Eggs.Foojay.Bar.2.2015.German.720p.BluRay.x264-Group1
And block any release with 3D or 1080p in its title (all rules applied)
The option described above should also add:
Die.Spam.von.Eggs.Foojay.Bar.2.3D.2015.German.DL.1080p.BluRay.x264-Group3D
And thus disregard any filter rule that disallows 3D, also disregarding the quality set (be it 480, 720, or 1080p)
Required would instead be .3D. somewhere in the title as well as 1080p for quality.


PEEK - Preview ANY (unknown) file in "text" view, just like Lister in total commander does.

Description of the new feature / enhancement
For the "unsupported" file extensions, the peek would show the file contents, just like the Lister does in total commander, instead of showing useless (to me at least) file details.
Scenario when this would be used?
For any "unsupported" file extension.
Supporting information
No response

/dup #26760


✨[feature Request]: Dark mode

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
The website does not have dark mode feature which add more attractiveness to the webite.
Use Case
The dark mode feature look cool and pleasant to some users
Benefits
No response
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24EXTD contributor
[X] I have starred the repository

Kindly assign me this issue. Would be glad to contribute! @Anjaliavv51

Assign this problem to me ASAP.

@ChampGupta go ahead.,

Thank you for assigning the project I will try to complete it by tomorrow.

@Anjaliavv51 could you please give guidelines for running the application in the local system ASAP so that I can fix the bug.

@Anjaliavv51 could you please give guidelines(command) for running the application in the local system ASAP so that I can fix the bug.

Use GitHub desktop for it


Code coverage support

Adds support - both for running tests with code coverage as well as importing a .coveragexml file from coverage.py.

Fixes #1020

Fixes #1113

Now fixes #1067 and #213

using System;

Header comment

Refers to: Python/Product/Analyzer/Intellisense/FileExtensionAttribute.cs:1 in d396cfb. [](commit_id = d396cfb35e36ac95c698f7643b6085a6499cd26a, deletion_comment = False)

namespace Microsoft.PythonTools.Analysis {

Header comment

Refers to: Python/Product/TestAdapter.Analysis/TestCaseInfo.cs:1 in d396cfb. [](commit_id = d396cfb35e36ac95c698f7643b6085a6499cd26a, deletion_comment = False)

namespace Microsoft.PythonTools.Analysis {

And fix the namespace

In reply to: 227834719 [](ancestors = 227834719)

Refers to: Python/Product/TestAdapter.Analysis/TestCaseInfo.cs:1 in d396cfb. [](commit_id = d396cfb35e36ac95c698f7643b6085a6499cd26a, deletion_comment = False)


Create sub-gist for equipment

Equipment is modeled generally as an Artifact in gist, but client engagements frequently call for more specific classes and properties. Examples from gist 12 include Actuator, Controller and Sensor. Example client classes have included HeatExchanger and FlowMeter. I suggest moving specific equipment-related classes and properties into a new sub-gist.
These equipment are not always (or even typically) connected to a network. They are not  necessarily IoT devices, although that possibility should be supported.
I see this sub-gist as useful for modeling concepts in manufacturing, logistics, materials handling, facilities and building management, and other domains that feature physical stuff that clanks, whirs and hums.

For the moment, I am moving the gist sensor concepts into a local repo in support of Issue #462

A sub-gist typically addresses either a horizontal or vertical market; we should think in those terms in order to figure out the right domain for the candidate sub-gist.


chore: Transaction component improvements

What changed? Why?

add prop that enables resetting of state after txn completion

Notes to reviewers
How has it been tested?

is the use case here that a user passes in calls or contracts then submits them, and wants to pass in more calls/contracts to the same button?  should it just reset state when calls/contracts changes?

Can you add a changeset


FEAT: Extension for Padding Class

Description
Added 3 types of Extension Method that deals with Padding for List types (Row, Column)
paddingDirectional method provides fine-grained control over directional spacing, allowing you to customize padding for the top, bottom, left, and right sides individually.
paddingSymmetric method simplifies the process of achieving uniform spacing by applying consistent vertical and horizontal padding to each widget in the list.
paddingAll method streamlines layout adjustments by uniformly applying the same padding value to all sides of each widget, ensuring a cohesive and polished design.

[x] ✨ Ran dartdoc
[x] 🛠 Added proper documentation
[x] ❌ No warnings or errors in the code
[x] ✅ If added a new extension, added in Readme and example too
[x] 🧪 If added a new extension, written proper test cases for it

Type of Change

[x] ✨ New feature (non-breaking change which adds functionality)
[ ] 🛠 Bug fix (non-breaking change which fixes an issue)
[ ] ❌ Breaking change (fix or feature that would cause existing functionality to change)
[x] 🧹 Code refactor
[ ] ✅ Build configuration change
[x] 📝 Documentation
[ ] 🗑 Chore

Hey, I added some new extension methods also wrote tests for them
@AbhishekDoshi26

@deepraj02 sorry for the delay, I was busy with the preps of Flutter Conf India.
I don't get the use-case of this extension. I mean, if I want to give padding to each element of my column/row, I will just give the padding to the column instead of giving to each element. As per your code that I understood, it is giving padding (only, symmetric and all) to the elements of List.
Can you explain the use-case of the same?

@deepraj02 can you update me on this?


Lambda host split

Coverage decreased (-0.3%) to 94.723% when pulling 3d8b0c946f4fb48b5777d285593667565ac5d95f on russell-lewis:lambda-host-split into 36fc01b8931976d640c50ec3d6cdc694376abf74 on Netflix:master.


tabs with icons not text not working

hi
when i have icons in my tablayout not just text , i can't see the icons ?

i will fix it

solved


fix: decrypt postgres password for use in connection string

Proposed changes
This addresses a bug introduced with #30 - the password is part of the connection string, but pulumi does not decrypt it for use in the string concatenation needed to build it. This has been fixed by using the Output.unsecret method.
Checklist
Before creating a PR, run through this checklist and mark each as complete.

[X] I have written my commit messages in the Conventional Commits format.
[X] I have read the CONTRIBUTING doc
[X] I have added tests (when possible) that prove my fix is effective or that my feature works
[X] I have checked that all unit tests pass after adding my changes
[X] I have updated necessary documentation
[X] I have rebased my branch onto master
[X] I will ensure my PR is targeting the master branch and pulling from my branch from my own fork

Running full test overnight.


Extensions do not work with RemoteFS

well, I'm having problems using the formatter or Intelephense of some language in my code using RemoteFS, I just can't, and below it shows an error of one of the extensions that I use outside of RemoteFS.

Describe the bug
PHP code intelligence for Visual Studio Code don't work via Remote File System for VS Code
To Reproduce
Open php file via Remote File System for VS Code
Screenshots

Platform and version
OS WIN10 and Intelephense version v1.6.3.

So, does it mean that it is not possible to have any extension power using RemoteFS ???
well, it's not just using PHP Intelephense that the problem occurs, it's with all my common ...

This is because while it does implement remote filesystems, it's done at an application level. To make this work properly with pre-existing extensions you'd have to do it at a much lower level, for example set up NFS at both client and server and mount the remote fs on the workstation. This would make the fs redirection visible to node and from there everything would be hunky dory.


Is probably pointless, but good to do, just to be sure.

Also, I removed some domains that are nonexistant (someone might start a service like Innapropriate Image Hosting at modshare.tk

Hi @Radical-from-Scratch thank you for the PR.
This repo is no longer maintained as s2forums has been integrated into Scratch's legacy codebase (referred to as scratchr2).


improving written protocol for 2022

@teixeirak,
Here is a couple things that would be good to address in the new protocole (feel free to disagree):

[ ]  protocol says If the status is “AU”, ... record crown position but the section describing how to rank crown position says Crown Position (dead trees only) --*> change to Crown Position (dead and unhealthy trees only)

[ ] the protocole does not say to measure the DBH when tree is dead--> add that in the list of things to do in this case + change section Diameter at breast height (DBH; mm) to Diameter at breast height (DBH; mm) (dead trees only)

[ ] filling DWR (dead with resprout) is not mentioned in the protocol. also, aren't we calling a tree AU if is has resprout? if yes, the name of the column should be changed to resprout (note that SS in EABF is "Stump sprouts")

[ ] In 2021, there is 3 types of crown positions:

Crown.position

Dead.crown.position

Crown.position...10.cm.DBH

you said here that Crown position <10 cm is the same as crown position. But they don't seem to match exactly (see bellow, number of cases with the different combinations of those 3 columns), and Crown.position actually seems to be Crown illumination (see figure 1 in protocole).
Also it is surprising that Crown.position...10.cm.DBH and Dead.crown.position, which seem to use the same system, don't always match (see when Crown.position...10.cm.DBH = S or NA).... I think crown position should only be asked once, whether the tree is dead or alive. And if you do want crown illumination, it should be called that.
, , Crown.position...10.cm.DBH = CD

              Dead.crown.position
Crown.position   CD    D    I   OG    S <NA>
          1       0    0    0    0    0    0
          2       0    0    0    0    0    1
          3       7    0    0    0    0    7
          4       1    0    0    0    0    2
          5       0    0    0    0    0    0
          <NA>    0    0    0    0    0    0

, , Crown.position...10.cm.DBH = D

              Dead.crown.position
Crown.position   CD    D    I   OG    S <NA>
          1       0    0    0    0    0    0
          2       0    0    0    0    0    0
          3       0    0    0    0    0    0
          4       0    1    0    0    0    2
          5       0    0    0    0    0    0
          <NA>    0    0    0    0    0    0

, , Crown.position...10.cm.DBH = I

              Dead.crown.position
Crown.position   CD    D    I   OG    S <NA>
          1       0    0    1    0    0    0
          2       0    0    5    0    0   40
          3       0    0    2    0    0    9
          4       0    0    0    0    0    0
          5       0    0    0    0    0    0
          <NA>    0    0    0    0    0    0

, , Crown.position...10.cm.DBH = OG

              Dead.crown.position
Crown.position   CD    D    I   OG    S <NA>
          1       0    0    0    0    0    0
          2       0    0    0    0    0    0
          3       0    0    0    1    0    0
          4       0    0    0    0    0    0
          5       0    0    0    0    0    0
          <NA>    0    0    0    0    0    0

, , Crown.position...10.cm.DBH = S

              Dead.crown.position
Crown.position   CD    D    I   OG    S <NA>
          1       0    0    2    0  103  252
          2       0    0    4    0    1   13
          3       3    0    0    0    0    2
          4       0    0    0    0    0    0
          5       0    0    0    0    0    0
          <NA>    0    0    0    0    0    1

, , Crown.position...10.cm.DBH = NA

              Dead.crown.position
Crown.position   CD    D    I   OG    S <NA>
          1       4    0    4    0  150 3079
          2       1    0   62    0    5 1847
          3      90    3    6    0    1 2192
          4       5   28    0    0    1  490
          5       0    0    0    0    0    2
          <NA>    1    0    1    0    2   34

-[ ]  need a figure number for Crown Assessment figure

other quick question:
@teixeirak , prior to 2021, only perc.crown was recorded. Does it correspond to 2021's percentage.of.crown.intact or percentage.of.crown.living ?
I find it a little redundant/confusing with crown.thinning (which is only for fraxinus)... but the protocole might be clear enough about the distinction - although I would rename the name of the figure for "Crown Assessment" (which need a figure number, see comment above) to something like "assessing percent crown intact and percent crown living" so there is no possible confusion.

crown.thinning is this:

So, crown.thinning is not the same as either percentage.of.crown.intact or percentage.of.crown.living , but it could be compared to percentage.of.crown.intact if that continuous variable were transformed into these categories.

Looking into this more. in 2017-2020, there are 3 columns that are on this same scale (1-5)...:

perc.corwn
DF
fraxinus.crown.thinning

perc.crown and DF are often not recorded together on the same tree (it is often one or the other that got recorded). When they are both recorded, they do not match.

(copying this message to this issue #57)

@teixeirak,  This file shows all the existing combinations of the three columns we are trying to make sense of.

perc.crown seems to be recorded mostly for dead trees (but a few A and AU trees got a record too), and for all species, including fraxinus
DF seems to be recorded mostly for AU trees (but some dead, and previously dead, and A trees got a record too), and for all species, including fraxinus
fraxinus.crown.thinning seems to be recorded for any status, mostly for fraxinus but a few other species got it too... (likely some carya but I have not checked).

perc.crown refers to percent crown (wood) intact (analagous to percentage.of.crown.intact):

DF refers to defoliation (analagous to percentage.of.crown.living)
fraxinus.crown.thinning refers to defoliation for Fraxinus + CHIVI (also affected by EAB). It should be recorded for all individuals. It uses the same scale as DF, so these should match if ever recorded for the same individual.

ok, thanks.
fraxinus.crown.thinning and DF do not always match when recorded on the same individual. But I'll ignore that for now.

to try to match 2021 and future censuses, I'll translate DF (percentage.of.crown.living) and prec.crown (percentage.of.crown.intact) to percentages, (taking average of 1-5 score).
okay?

to try to match 2021 and future censuses, I'll translate DF (percentage.of.crown.living) and prec.crown (percentage.of.crown.intact) to percentages, (taking average of 1-5 score).
okay?

That's modifying and potentially biasing the data, and I wouldn't be comfortable putting that into an analysis without explicitly stating that. In an analysis comparing them, it would be better too put the newer data into categorical classes (although we don't want to throw out the higher precision for other uses).
If it greatly facilitates working with the data, we could take the midpoint of each category and state in the  metadata that it is an average.

[ ] in 2021 there are quite a few notes saying "epicormic branches", but nothing is entered in epicormic.growth as that column is reserved for fraxinus. Maybe it would be worth opening that column to all speices, like it is the case for canaker... or wound or rotting trunk ?

to try to match 2021 and future censuses, I'll translate DF (percentage.of.crown.living) and prec.crown (percentage.of.crown.intact) to percentages, (taking average of 1-5 score).
okay?

That's modifying and potentially biasing the data, and I wouldn't be comfortable putting that into an analysis without explicitly stating that. In an analysis comparing them, it would be better too put the newer data into categorical classes (although we don't want to throw out the higher precision for other uses).
If it greatly facilitates working with the data, we could take the midpoint of each category and state in the metadata that it is an average.

I meant mid point. Ok, I'll put newer data into category,, changing name to be more explicit lie score.crown.intact, and keeping the percentage.of.crown.intact

you said here that Crown position <10 cm is the same as crown position.

@ValentineHerr , I made a mistake there (sorry!). These names are confusing. Crown Position is used in the FastField app to describe crown illumination index, and Dead Crown Position to describe what I've been calling crown position. So Crown position <10 cm is actually Dead crown position.

also, aren't we calling a tree AU if is has resprout? if yes, the name of the column should be changed to resprout (note that SS in EABF is "Stump sprouts")

Good question. I believe it counts as dead, although I think there might also be a special code for this. Leave as is for now.

So Crown position <10 cm is actually Dead crown position.

@teixeirak, what about Dead.crown.position then?
See this file (relevant rows in screenshot below) to see how the columns are currently interepreted.

@teixeirak, what about Dead.crown.position then?

That would be crown_position (same as Crown.position...10.cm.DBH)
And yikes... we have a crazy mix of variable names!

I think we can close this now.


Add /balances/:fiatCode endpoint

Related with https://github.com/5afe/safe-client-gateway-nest/issues/19 – I'd close it once I add more tests

Adds @nestjs/config – this dependency allows us to introduce an application level configuration which reads from the local environment
Adds an ExchangeService which depends on an external API to retrieve the fiat conversion prices (which is used by the /balances endpoint)
Introduce .env.sample – this file should be copied to .env if a local configuration should be changed. .env will be automatically read by configuration.ts

@hectorgomezv here I just adjusted the test that we had already in place. Since the payload is already increasing in size I'll have a look into Faker and ways to better associate the request with the response in the tests (possibly in a separate PR)

@hectorgomezv the idea of providing Fake data would be similar to this: https://github.com/5afe/safe-client-gateway-nest/blob/add-fake-data/src/services/transaction-service/entities/tests/balance.factory.ts

Related with #19 – I'd close it once this PR #31 is merged (it has more tests and includes Faker)

Adds @nestjs/config – this dependency allows us to introduce an application level configuration which reads from the local environment
Adds an ExchangeService which depends on an external API to retrieve the fiat conversion prices (which is used by the /balances endpoint)
Introduce .env.sample – this file should be copied to .env if a local configuration should be changed. .env will be automatically read by configuration.ts

@hectorgomezv here I just adjusted the test that we had already in place. Since the payload is already increasing in size I'll have a look into Faker and ways to better associate the request with the response in the tests (possibly in a separate PR)

Great, thanks! Yes, for faker we have this issue, I'll try to take it soon 🙂

Related with #19 – I'd close it once this PR #31 is merged (it has more tests and includes Faker)

Adds @nestjs/config – this dependency allows us to introduce an application level configuration which reads from the local environment
Adds an ExchangeService which depends on an external API to retrieve the fiat conversion prices (which is used by the /balances endpoint)
Introduce .env.sample – this file should be copied to .env if a local configuration should be changed. .env will be automatically read by configuration.ts

@hectorgomezv here I just adjusted the test that we had already in place. Since the payload is already increasing in size I'll have a look into Faker and ways to better associate the request with the response in the tests (possibly in a separate PR)

Great, thanks! Yes, for faker we have this issue, I'll try to take it soon 🙂

Maybe I can take that one since I introduced it in #31


version `GLIBC_2.33' not found (required by mbtiles)

I downloaded https://github.com/maplibre/martin/releases/latest/download/martin-x86_64-unknown-linux-gnu.tar.gz (https://maplibre.org/martin/installation.html), but can't run the programs. It seems my glibc is out of date. Interaction log with errors below.
Do I need to update, or is this expected?
I didn't find documentation about this. Upgrading glibc on my system will probably not be rainbow filled, but I'm will to try building with an adhoc glibc if that might fix it.
mbtiles validate gen/rye/points-stationary/naps.mbtiles
mbtiles: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by mbtiles)
mbtiles: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by mbtiles)
mbtiles: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by mbtiles)

mbtiles --version
mbtiles: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by mbtiles)
mbtiles: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by mbtiles)
mbtiles: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by mbtiles)

martin --version
martin: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by martin)
martin: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by martin)
martin: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by martin)
martin: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by martin)

uname -a
Linux ubp52 5.9.16-050916-generic #202012211331 SMP Mon Dec 21 14:11:13 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

interesting, could you try the MUSL version?

Sure what's that? :joy_cat:

One of the other download options on the release page

Oh, I see, the other Releases page  :)
Thanks, that worked, I'm off and validating mbtiles. :heavy_check_mark:
https://github.com/maplibre/martin/releases/download/v0.13.0/martin-x86_64-unknown-linux-musl.tar.gz

@whilei which other release page were you using before?  Should we update the docs somewhere?  Note that the installation instructions also mention musl.

I was using https://maplibre.org/martin/installation.html


Option to avoid automatic hyperlinking of URLs inside fenced code blocks would be useful

I ran into a problem where the following fenced code block:
```
$ curl -s 'https://api.github.com/users/dogsheep/repos'\
  | sqlite-utils memory - '
      select full_name, forks_count, stargazers_count
      from stdin order by stargazers_count desc limit 5
    ' -t
[...]
$ sqlite-utils memory species.csv creatures.csv '
  select * from creatures join species on creatures.species_id = species.id
'

Was being rendered with both https://api.github.com/users/dogsheep/repos and species.id (in the SQL query) as links. species.id isn't intended as a link, and the curl -s link became https://api.github.com/users/dogsheep/repos' - note the trailing ' character - which was a 404.

I came up with a workaround https://github.com/simonw/datasette.io/issues/66#issuecomment-864437178 where I used BeautifulSoup to strip any links that occurred inside a <pre> tag, but it would be great if there was an option for the fenced_code to disable auto-linking of content inside the rendered blocks.

This should definitely not be happening. What options are you passing to Python-Markdown?

First of all, Python-Markdown does not autolink any URLs. Autolinks must be wrapped in angle brackets. This suggests to me that a third party extension must be involved. As insufficient information has been provided to replicate the described behavior, I am closing this. Of course, if this is caused by a third party extension, the matter should be addressed by that extension.

My apologies: it turns out this was cased by the way I was using Bleach: https://bleach.readthedocs.io/en/latest/linkify.html#skipping-links-in-specified-tag-blocks-skip-tags


Update/Add AzTable PowerShell module

Tool information

Tool name: AzTable (PowerShell module)
Tool license: MIT
Add or update? Add
Desired version: latest (v2.0.3 at time of writing)
Approximate size: unknown
If this is an add request:

Brief description of tool: Set of cmdlets to add/retrieve/update entities on Azure Table Storage using PowerShell
URL for tool's homepage: https://www.powershellgallery.com/packages/AzTable/2.0.3
Provide a basic test case to validate the tool's functionality: New-AzStorageTable –Name $tableName –Context $ctx

Area for Triage:
Scripting and command line
Question, Bug, or Feature?:
Feature
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11.0
[x] Windows Server 2016 R2
[x] Windows Server 2019

Can this tool be installed during the build?
Yes. To the best of my understanding, all that needs to be done is adding an entry for AzTable in the images/win/toolsets/toolset-2019.json and images/win/toolsets/toolset-2016.json files under the powershellModules section. Is this correct?
Tool installation time in runtime
30 seconds maximum! PowerShell modules installed via PSGallery take a few seconds to install at most.
Are you willing to submit a PR?
Yes :)

Hi @vexingpos,
given the pretty small installation time we'd rather not to install this tool on the image. Please, continue installing it in runtime.
Note, that we do not provide the default Az module version, so you should set it by yourself.
I am closing this issue, feel free to create a new one in case if any other help is needed.
Thanks!