Error in CTM

I am working on a topic modelling project and want to use the Tomotopy implementation of CTM. So far I have succesfully implemented LDA and Pachinko in the same pipeline as CTM but for CTM I am getting the following error. I am uncertain of why this error arises or how to resolve this. We have tried changing the number of topics, the values for eta and introduced 'model.num_beta_sample=5'. I have around 4620 documents for training. Please find the relevant bit of the code below the error.

`def train_CTM(documents, k, min_cf=0, rm_top=0, eta=0.01, model_burn_in=100, #smoothing_alpha=0.1,
train_updates = 1000, train_iter = 10):
# instantiate
model = tp.CTModel(tw=tp.TermWeight.ONE, min_cf=min_cf, rm_top=rm_top, k=k, #smoothing_alpha = smoothing_alpha,
                  eta = eta)

model.num_beta_sample = 5

# add documents to model
for doc in documents: model.add_doc(doc)

# training**
model.burn_in = model_burn_in
# initialising
model.train(iter=0)
print('Num docs:', len(model.docs), ', Vocab size:', len(model.used_vocabs), ', Num words:', model.num_words)
print('Removed top words:', model.removed_top_words)
print('Training...')
# actual training
for i in range(0, train_updates, train_iter):
    model.train(train_iter)
    if i%100==0:print('Iteration: {}'.format(i))
return model

def CTM_search(train_docs, test_docs):
""" Wrapper function for CTM grid search """
print("Starting CTM grid search ...")
w = get_num_tokens(train_docs)

# The GRID
ks = [50, 100, 150, 200, 300]
etas = [1/w, 10/w, 0.1/w]

grid_results = pd.DataFrame(columns=["K","eta","perplexity"])

start = time.time()

for k in ks:
    startk = time.time()
    for eta in etas:
        print(" ------------------------------------------- ")
        print("| K = " + str(k) + "\t| eta=" + str(eta))
        try:
            model= train_CTM(train_docs, k,
                            eta=eta,
                            model_burn_in=MODEL_BURN_IN,
                            train_updates = TRAIN_UPDATES,
                            train_iter = TRAIN_ITERS)
        except Exception as e:
            print("The following error occurred:")
            print(e)
            print("The grid search will skip the current values.")
            grid_results = grid_results.append({"K":k, "eta":eta,"perplexity":np.nan},
                                            ignore_index=True)
            continue

        ll = get_test_LL(test_docs, model)
        pp = compute_test_pp(ll, test_docs)
        grid_results = grid_results.append({"K":k, "eta":eta,"perplexity":pp},
                                            ignore_index=True)
        print("Test perplexity = "+str(pp))

    endk = time.time()
    print("Time elapsed for k="+str(k)+" : " + str(round(endk - startk, 1)) + " s")

end = time.time()
print("Time elapsed: " + str(round(end - start, 1)) + " s")

return grid_results`

Would you have any indication of where this may originate from or how to fix it?
Many thanks in advance for any insight you can provide.

Is there any news on this one?

Is there any news on this one?

Thank @danielgarel for reporting the bug and @GiuliaLanzillotta for reminding it.
Umm... it seems there are some potential bugs in the implementation of Truncated Multivariate Normal distribution.
https://github.com/bab2min/tomotopy/blob/e95b656c46c0d486c09f64a7d7718ce0195ed326/src/Utils/TruncMultiNormal.hpp#L10-L69
Normally, truncation domain [A, B] satisfies A <= B, but sometimes it seems to be broken.
I'll test it with another implementation of Truncated Multivariate Normal function.

Thank @danielgarel for reporting the bug and @GiuliaLanzillotta for reminding it.
Umm... it seems there are some potential bugs in the implementation of Truncated Multivariate Normal distribution.
https://github.com/bab2min/tomotopy/blob/e95b656c46c0d486c09f64a7d7718ce0195ed326/src/Utils/TruncMultiNormal.hpp#L10-L69
Normally, truncation domain [A, B] satisfies A <= B, but sometimes it seems to be broken.
I'll test it with another implementation of Truncated Multivariate Normal function.

@danielgarel, @GiuliaLanzillotta
The problem was determined to be due to numerical instability of Truncated Multivariate Normal implementation. I have released version 0.10.2 that solved the problem.
https://github.com/bab2min/tomotopy/blob/77fcff050351facdcc17b86910d437f49554f094/src/Utils/TruncMultiNormal.hpp#L10-L67
https://github.com/bab2min/tomotopy/blob/77fcff050351facdcc17b86910d437f49554f094/src/TopicModel/CTModel.hpp#L57-L114


setting the base ID

When generating the proxy table, there is no way to set the base id to be used for the field IDs of the proxy table. They are numbered independently on the ID entered for the new proxy table.

CC: @onbuyuka
Let me try to understand you better @Kine. Suppose the dataverse table has 3 fields and you provided invoking the proxy table generator with baseID 50000, then you expect that the 3 fields have IDs : 50001, 50002 and 50003, instead of 1, 2 and 3? Why do you see this as a limitation?

Got it! Thanks @kine. Field IDs can be named 1, 2, 3 etc... they would still compile in the PTE (for example, see this PTE table). Therefore the renumbering of field ids to the partner object IDs appear to be an optional step to deploy the app. Thanks for the suggestion- however the workaround seems to be clear and easy, and one- time for each table.

Yes and no.
Yes, it is not problem, when the table is created as a product of the run.
No, if TableExtension is created, because in this case, the IDs must be in the partner range. And one time renumber is not so good, when you need to update the TableExtension again when some change was done on the Dataverse side.
But yes, I can fix it manually, but every time I run it to refresh the schema, I need to renumber them again.


Feature Python Virtual Environment Support

Description

Add support for python virtual environments in Lean, allowing overriding of base libraries with py venv directory config value ("python-venv") for local use or job packet var ("sPythonVirtualEnvironment") for cloud.

Refactor AddPythonPaths to prepend to path to use for this solution
Add static ActivatePythonVirtualEnvironment to prepend the virtual environment libraries to PythonPath, so that they are used.

Add "venv" virtual environment to foundation image, acts a shell install that gets mounted on later.

Add Jupyter Kernel for this venv to allow switching to this set of libraries

Related Issue

Closes #3189
Closes #4857
Closes #3950
Closes https://github.com/QuantConnect/Lean/issues/6291
Motivation and Context

Requires Documentation Change

How Has This Been Tested?

Regressions and unit tests ✅
Image testing successful using new foundation image with venv config value. ✅
Cloud testing ✅
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which improves implementation)
[ ] Performance (non-breaking change which improves performance. Please add associated performance test and results)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Non-functional change (xml comments/documentation/etc)

Checklist:

[x] My code follows the code style of this project.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

We can review pending libraries that were blocked because of backwards compatibility/breaking changes, can see a few at https://github.com/QuantConnect/Lean/pull/5536

Rebased and ready 👍🏽

Partially replaced by https://github.com/QuantConnect/Lean/pull/6556


Error due to wrong file type is incorrectly classified as "got XML response"

https://github.com/ClarityMoe/Sagiri/blob/master/lib/Handler.js#L171-L176
If user uploaded something that is not an image, the API will return HTML:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>Sauce Found?</title>
<link rel="stylesheet" href="css/saucenao-new.css" media="screen" type="text/css" />

You need an Image! ...GO BACK TO START...

If an image was provided, it may not be loading properly, or may not be in an acceptable format... The image must be: gif, jpg, png, bmp, svg, or webp...
 Try another, or convert your image first.

Detected Type 1: application/pdf
Detected Type 2: application/pdf

Which is incorrectly handled as "got XML response".

@Voileexperiments intended handling but the error message was wrong. Correcting it rn


fix allows_any for local versions

Fixes https://github.com/python-poetry/poetry/issues/2543
similar to #395

Would be lovely to see a release of this <3

me too :smiley:


sgx.nonpie_binary option causes failure in Gramine but passes in GSC

Description of the problem
Gramine has deprecated the sgx.nonpie_binary manifest option and introduced a manifest check tool that flags any unsupported entries in the manifest file.
https://github.com/gramineproject/gramine/commit/970b62f253ad77f0da4fa03006433f1992083353
https://github.com/gramineproject/gramine/commit/f1258cc003a649e2b0c5b805b739160cbd72cfcf
Steps to reproduce

We updated the helloworld example to include the sgx.nonpie_binary option in the manifest file. When running the make SGX=1 command, build fails:
$ make SGX=1
cc -Wall -Wextra -O3   -c -o helloworld.o helloworld.c
cc   helloworld.o   -o helloworld
gramine-manifest \
        -Dlog_level=error \
        helloworld.manifest.template helloworld.manifest
WARNING: error in manifest (after rendering): extra keys not allowed @ data['sgx']['nonpie_binary']
gramine-manifest-check helloworld.manifest
error in manifest: extra keys not allowed @ data['sgx']['nonpie_binary']
make: *** [Makefile:26: helloworld.manifest] Error 1

As expected, the make command fails during the gramine-manifest-check step with the error extra keys not allowed. However, this check is not integrated into GSC (Gramine Shielded Containers), which uses a different logic for generating the manifest file.
When we add sgx.nonpie_binary=true to the GSC test and build the workload, the build completes successfully without any errors and workload is running successfully.
GSC Log attached
gsc_nopie.log
Expected results
gramine-manifest-check tool should be integrated into gsc
Actual results
GSC build completes successfully without throwing any errors

As expected, the make command fails during the gramine-manifest-check step with the error extra keys not allowed. However, this check is not integrated into GSC (Gramine Shielded Containers), which uses a different logic for generating the manifest file.

True.
I think the fix would be to add the following line somewhere around here: https://github.com/gramineproject/gsc/blob/e57a501fe2e54692742876ac1cc3b81cfa24af86/templates/Dockerfile.common.sign.template#L12
+RUN {% block path %}{% endblock %} gramine-manifest-check /gramine/app_files/entrypoint.manifest

Any volunteers for this change?


Gitlab - Post Reconfigure Update

Latest Gitlab-CE image has the application setting attributes updated.
On legend/installers/aws-docker/install/run-gitlab.sh
Post Install reconfigure should update from ApplicationSetting.last.update_attributes(signup_enabled: false)
to
ApplicationSetting.last.update(signup_enabled: false)

This issue is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.

This issue was closed because it has been inactive for 35 days. Please re-open if this issue is still relevant.


Document the Alex |Andre |Gilberto |Shize algorithm

Overview
Participants in the Data Science Bowl produced several algorithms that we would like to incorporate. To help facilitate this effort, we also want to add documentation so that contributors can make an educated decision when selecting an algorithm to incorporate.
Expected Behavior
This documentation should enable people to:

view the library dependencies and license
understand its pros/cons
evaluate its performance/accuracy
identify which areas of the codebase to target for improvement

Design doc reference: Detect and select
Algorithm info

key
value

team
Alex |Andre |Gilberto |Shize

rank
8

repo
https://github.com/astoc/kaggle_dsb2017

trained models
https://github.com/astoc/kaggle_dsb2017/tree/master/code/Andre/nodule_identifiers

converted branch

ML engine
Keras

engine-version
1.2.2

ML backend
Theano

backend-version

training method

architecture

algorithm

OS

OS version

Python version

CUDA version

cuDNN version

notes

Technical details

This feature should be implemented as a new markdown file in the docs folder

Acceptance criteria

[ ] effective documentation for the above

NOTE: All PRs must follow the standard PR checklist.

I'm reading through this one right now. Please correct me if I'm wrong, but it seems like the competition target variable was to predict the probability of the patient having cancer as a whole as opposed to the probability of each individual nodule within the lungs?
It looks like most of these go through the same z-slice normalization, lung segmentation, and nodule detection/isolation steps. But then it's the final feature generation steps that might need to be refactored quite a bit to tackle the new problem statement of predicting the probability of each nodule being cancerous. Is that a fair statement?
A feature such as total_number_of_nodules (I made that up as an example) aggregated at the patient level might still be important at the nodule level, but it does seem to imply that the goal was slightly different.

Answer posted here.

@tjvananne Did @reubano's link answer your question? :)

@lamby same here - is something preventing this issue from getting closed? :)


Pl330 fixes

This patch set series contains fixes related to pl330 driver.

Hi @kgugala,
"boards: arm: Enable pl330 in bcm958402m2_m7" patch enables compilation of DMA_PL330 and tested on bcm958402m2_m7 board using "tests/drivers/dma/chan_blen_transfer" application.

@galak :  At the time of pushing this change it was not tested on bcm958402m2_a72. Now its tested, I will enable DMA/DMA_PL330 in bcm958402m2_a72 as well and push.


Don't change example code after run

After running a first example, if I choose another example, the code textfield does not change.
Firefox 83.0 (Linux 64 bits)

I'll take a look. I've only used Chrome so far and this works fine there. To be clear, I did this:

go to a fresh playground (contains hello world code)
choose an example
click Run button
choose a different example

Now It's working with Firefox. Tested in Chromium and works too.
I didn't change anything. Did you?

Nope. It's possible it's related to the funky way I have my dev instance deployed. I noticed that at one point it didn't respond until I foregrounded the emacs I have it running in. :-)
Going to close this for now since I can't reproduce it on Safari or Firefox on Mac either.

Wait, was this a problem with the dev instance or play.opendylan.org?

dev instance

ok, closing. thanks.


Can't create LinuxFunctionApp

What happened?
I'm trying to create a LinuxFunctionApp following the example provided by the documentation.
var exampleLinuxFunctionApp = new Azure.AppService.LinuxFunctionApp("exampleLinuxFunctionApp", new()
    {
        ResourceGroupName = exampleResourceGroup.Name,
        Location = exampleResourceGroup.Location,
        StorageAccountName = exampleAccount.Name,
        StorageAccountAccessKey = exampleAccount.PrimaryAccessKey,
        ServicePlanId = exampleServicePlan.Id,
        SiteConfig = null,
    });

Expected Behavior
The function app is created as expected.
Steps to reproduce
Follow the example provided by the documentation page.
https://www.pulumi.com/registry/packages/azure/api-docs/appservice/linuxfunctionapp/#example-usage
You will get the error:
error: Running program '[...]' failed with an unhandled exception:
System.ArgumentNullException: [Input] Pulumi.Azure.AppService.LinuxFunctionAppArgs.SiteConfig is required but was not given a value (Parameter 'SiteConfig')
at async Task<ImmutableDictionary<string, object>> Pulumi.InputArgs.ToDictionaryAsync()
at async Task Pulumi.Deployment.PrepareResourceAsync(string label, Resource res, bool custom, bool remote, ResourceArgs args, ResourceOptions options)
at async Task<(string urn, string id, Struct data, ImmutableDictionary<string, ImmutableHashSet> dependencies)> Pulumi.Deployment.RegisterResourceAsync(Resource resource, bool remote, Func<string, Resource> newDependency, ResourceArgs args, ResourceOptions options)
at async Task<(string urn, string id, Struct data, ImmutableDictionary<string, ImmutableHashSet> dependencies)> Pulumi.Deployment.ReadOrRegisterResourceAsync(Resource resource, bool remote, Func<string, Resource> newDependency, ResourceArgs args, ResourceOptions options)
at async Task Pulumi.Deployment.CompleteResourceAsync(Resource resource, bool remote, Func<string, Resource> newDependency, ResourceArgs args, ResourceOptions options, ImmutableDictionary<string, IOutputCompletionSource> completionSources)
Output of pulumi about
CLI
Version      3.55.0
Go Version   go1.20
Go Compiler  gc
Plugins
NAME    VERSION
dotnet  unknown
Host
OS       darwin
Version  13.1
Arch     arm64
This project is written in dotnet: executable='/usr/local/share/dotnet/dotnet' version='7.0.102'
[...]
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@FernandoMorais Thanks for checking out the documentation for this resource and reporting your issues using it.
I've checked the documentation in the link provided (https://www.pulumi.com/registry/packages/azure/api-docs/appservice/linuxfunctionapp/#example-usage), and I see that siteConfig is defined as siteConfig: {}. In your snippet provided, you have null instead of {} for the siteConfig field. This is a required field, so it cannot be set as null.
Please update your code to set this field so that this resource can be provision.
Since our documentation and examples does have this field set, I'll mark this as closed. But please feel free to re-open if you still need assistance.

@rquitales
Got you, the documentation must show the snippet you described for C# (and Go).

Anyways it works setting SiteConfig. Thanks!


Cannot run symplify tests

composer install
composer complete-check

PHP Fatal error:  Uncaught Error: Class 'Symfony\Component\DependencyInjection\Loader\GlobFileLoader' not found in /home/tousek/Projects/symplify/symplify/packages/EasyCodingStandard/src/DependencyInjection/EasyCodingStandardKernel.php:95

Any ideas?

Yeah, looks like composer.lock is outdated - it installed symfony/dependency-injection v3.4.0 instead of 4.0.x.
After composer update I can run tests. However two tests are failing with following error:
1) Symplify\Statie\Tests\Console\Command\GenerateCommandTest::test
OutOfBoundsException: Required package "symplify/statie" is not installed: cannot detect its version

Might be related: https://github.com/Symplify/Symplify/pull/589/files

Still same failure even after removing "symplify/statie": "self.version",.

That is needed for the version feature.
Still can't reproduce:
git clone git@github.com:Symplify/Symplify.git symplify-test --depth 1
cd symplify-test
composer update
composer complete-check

Random idea: I'd try updating the composer

Any updated on this?

Looks like composer self-update helped. I've found another (unrelated) problem though so I'll close this and create a new issue.


Build Scaladoc

It would be nice to build Doodle Scaladoc.

Yes, indeed!
BTW, when building a triangle, what do represent the two parameters?
Obviously (correct me if I'm wrong), the triangle looks isosceles, and the first parameter defines the size of the horizontal basis. What does represent h ? Is it the size of the two other sides of the triangle, or rather the height of the triangle ?
Another question is: what's the unit used for these parameters ? Are they pixels, or something else?
Thanks

Triangle is represented by width and height. Units are (usually) pixels but there isn't a strict interpretation for them.

https://www.creativescala.org/doodle/ links to the ScalaDoc


2 Players can hold each other in order to fly

When fixing this, keep in mind that the problem will probably still occur in groups larger than 2 if the players form a "ring" of holders

Fixed and added to config(hopefully correctly)


Link container build to anchore.io for automated security tests

In order to ensure there are no known vulnerabilities within the Docker image installed software each image build should be hooked up to https://anchore.io/ and auto-scanned on build and prior push to docker hub.

Currently testing this feature for PHP 5.4

https://anchore.io/preview/dockerhub/devilbox%2Fphp-fpm%3A5.4-base
https://anchore.io/preview/dockerhub/devilbox%2Fphp-fpm%3A5.4-mods
https://anchore.io/preview/dockerhub/devilbox%2Fphp-fpm%3A5.4-prod
https://anchore.io/preview/dockerhub/devilbox%2Fphp-fpm%3A5.4-work

All PHP Container are now added to https://anchore.io for public security review


FEAT: Add CLIs in TRL !

cc @lvwerra

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


fix: prevent layout shifts in header

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


pycharm warning of Unresolved reference

Hi, I really like this project! It's mind blowing for me!!
I have a question. When coding in pycharm using TensorType with a string dimension name, I got a warning about unresolved reference

I am not sure if this is a limitation of pycharm. I am using pycharm 2021.1.1, python 3.7.10 and torchtyping 0.1.4.
Thanks!

This is because strings in types are often used to denote forward references, e.g.
def f(x: "A"): ...

class A: ...

As a result PyCharm is looking for an object called batch somewhere, and is complaining that it can't find it.
This is essentially a limitation of PyCharm -- it's assuming strings are being used in a way that they're only sometimes used.
One option is to disable the warning, via whatever mechanism PyCharm offers for that. It's been a while since I've used PyCharm but I think you should be able to disable the warning locally, or for the whole file, or globally.
The other option is just to put batch = None anywhere in the file to fool PyCharm into thinking that something called batch exists.

Hi, is there any workarounds that does not require disabling linting or creating weird variables? thanks!


const "ERROR" gets lowercased to "Error"

Bug report
PHP CS Fixer version: v3.7.0
PHP Version: 8.0.16
Config: 'class_reference_name_casing' => true
<?php

const ERROR = 'error';
const INFO = 'info';

function foo(string $bar): void
{
    echo $bar;
}

foo(ERROR);
foo(INFO);

The rule class_reference_name_casing changes foo(ERROR) to foo(Error).
foo(INFO) is not changed.
Before v3.6.0 foo(ERROR) was not changed as well.

thanks for reporting, proposed fix is here https://github.com/FriendsOfPHP/PHP-CS-Fixer/pull/6331

Wow, that was fast!
I can confirm that the PR solves the issue in my project.


Only as a overlay

Hello
is it possible to use the particles only as an overlay?
I am using “OWL CAROUSEL” and I would like to put “Particles” over it to make them visable but I don’t want to lose the carousel controles.
any idea on that

Heya @Tasslhof,
You can set the particles container div to a higher z-index and then set it's pointer-events: none to make sure mouse clicks go through it.
Cheers!

Yes I was successfully in doing this :)
I had a CAROUSEL under the particle js div

<canvas></canvas>

My CSS Code on the canvas
position: aboslute;
z-index: 100
pointer-events: none;
top: 0px;


Formtastic Custom Input Gem

Would it be possible to author a gem that just included overrides the original input types but still relies on the original formtastic gem or any of its variants?

Yes, in theory. If you make an engine gem that has formtastic as a dependency, you'll be able to have an app/inputs/ directory inside the gem. In theory, that will work, but I've never tried it.


Make printing press work with any black dye

Addresses https://github.com/Nuchaz/BiblioCraft/issues/559
If this is released, Sevtech can re-enable the printing press, assuming they're open to PRs.

Tested on my server. PR does not contain buildscript changes necessary to run in 2024 with semi-modern FG.

I am going to take a look at this and maybe we can get this pushed, this looks like like a good thing.


Include cluster diagram

Could be useful to include a slide showing this diagram which is currently on our HowTo website.

Closing, because this is now included in the larger issue #10


Update Updates “releases”

Automatically generated by Netlify CMS

Deploy preview for cms-demo ready!
Built with commit 2c76819a57932cb9fbe3bba1d29837433d8c0538
https://deploy-preview-1374--cms-demo.netlify.com

Deploy preview for netlify-cms-www ready!
Built with commit 2c76819a57932cb9fbe3bba1d29837433d8c0538
https://deploy-preview-1374--netlify-cms-www.netlify.com


Metric value level

Codecov Report

Merging #15 (c605a0f) into main (7d7928f) will decrease coverage by 20.43%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main      #15       +/-   ##
===========================================
- Coverage   89.18%   68.75%   -20.44%
===========================================
  Files          13       14        +1
  Lines          74       96       +22
===========================================
  Hits           66       66
- Misses          8       30       +22

Impacted Files
Coverage Δ

lib/src/models/metric_value_level.dart
0.00% <0.00%> (ø)

lib/src/models/severity.dart
57.14% <ø> (ø)

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 7d7928f...c605a0f. Read the comment docs.

Codecov Report

Merging #15 (c605a0f) into main (7d7928f) will decrease coverage by 20.43%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             main      #15       +/-   ##
===========================================
- Coverage   89.18%   68.75%   -20.44%
===========================================
  Files          13       14        +1
  Lines          74       96       +22
===========================================
  Hits           66       66
- Misses          8       30       +22

Impacted Files
Coverage Δ

lib/src/models/metric_value_level.dart
0.00% <0.00%> (ø)

lib/src/models/severity.dart
57.14% <ø> (ø)

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 7d7928f...c605a0f. Read the comment docs.


Lower contrast of buttons

I think the buttons would look a lot better, when bit lighter/lower contrast.

@iDuuck I totally agree with you, the buttons would look better with lower contrast. But I really don't think lightening the buttons would be a good choice. It hurts accessibility immensely, and makes the app harder to use even for people with perfect vision, because icon differentiation is harder (especially in extreme light conditions). I would highly encourage @noahbuscher and @ColeTownsend not to do this. 😁

@lachlanjc up to @noahbuscher but I think the contrast is pretty low in general

@ColeTownsend yeah, so we shouldn't lower it :smile:

Yes - contrast is already pushing the limits and while I'd agree that lightening the buttons may look nicer, accessibility and readability will be sacrificed. Closing for now. :blush:

But the overall contrast on the input for example uis very low, too.. So it
wouldn't hurt. Only if the rest of the theme would also be made darker it
would make sense to say that it would hurt accessibility.
On Sun 20 Dec 2015 at 08:22 Noah Buscher<EMAIL_ADDRESS>wrote:

Yes - contrast is already pushing the limits and while I'd agree that
lightening the buttons may look nicer, accessibility and readability will
be sacrificed. Closing for now. [image: :blush:]
—
Reply to this email directly or view it on GitHub
https://github.com/noahbuscher/N1-Taiga/issues/18#issuecomment-166077123
.


Jwilaby/babel builds

Pull Request Test Coverage Report for Build 717

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
23 unchanged lines in 5 files lost coverage.
Overall coverage increased (+32.2%) to 81.511%

Files with Coverage Reduction
New Missed Lines
%

packages/app/client/src/data/action/azureAuthActions.ts
1
83.33%

packages/app/client/src/data/sagas/navBarSagas.ts
1
66.67%

testSetup.js
3
53.33%

packages/app/client/src/data/action/notificationActions.ts
5
12.5%

packages/app/client/src/data/action/editorActions.ts
13
7.14%

Totals

Change from base Build 670:
32.2%

Covered Lines:
323

Relevant Lines:
376

💛  - Coveralls


[cockroachdb] Adds 24.2 and new policy

The policy has changed a lot since the last few releases, this PR reflects the same.

And more changes the next day: https://www.cockroachlabs.com/enterprise-license-update/


Trajectory parameter error message update.

Summary
Summary of PR.
Related Issues

Resolves #

Backwards incompatibilities
None
New Dependencies
None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

147 of 175 (84.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.07%) to 95.631%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

dymos/trajectory/trajectory.py
16
20
80.0%

dymos/trajectory/test/test_trajectory_parameters.py
119
143
83.22%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
28588

Relevant Lines:
29894

💛  - Coveralls


Could not load image asset '/metagui/themes/frackin/v2/...

Hi, I often see those errors popping up in the log:

[13:05:50.834] [Error] Could not load image asset '/metagui/themes/frackin/v2/frame.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/frame.png'
[13:05:50.837] [Error] Could not load image asset '/metagui/themes/frackin/v2/panel.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/panel.png'
[13:05:50.840] [Error] Could not load image asset '/metagui/themes/frackin/v2/button.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/button.png'
[13:05:50.842] [Error] Could not load image asset '/metagui/themes/frackin/v2/scrollBar.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/scrollBar.png'
[13:05:50.844] [Error] Could not load image asset '/metagui/themes/frackin/v2/textBox.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/textBox.png'
[13:05:50.847] [Error] Could not load image asset '/metagui/themes/frackin/v2/tabPanel.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/tabPanel.png'
[13:05:50.849] [Error] Could not load image asset '/metagui/themes/frackin/v2/tab.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/tab.png'
[13:05:50.851] [Error] Could not load image asset '/metagui/themes/frackin/v2/checkBox.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/checkBox.png'
[13:05:50.853] [Error] Could not load image asset '/metagui/themes/frackin/v2/radioButton.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/radioButton.png'
[13:05:50.856] [Error] Could not load image asset '/metagui/themes/frackin/v2/itemSlot.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/itemSlot.png'
[13:05:50.858] [Error] Could not load image asset '/metagui/themes/frackin/v2/itemRarity.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/itemRarity.png'
[13:05:50.858] [Error] Could not load image asset '/metagui/themes/frackin/itemRarity.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/itemRarity.png'
[13:05:50.867] [Error] Could not load image asset '/metagui/themes/frackin/v2/windowBg.png', using placeholder default.
(AssetException) No such asset '/metagui/themes/frackin/v2/windowBg.png'

starbound.log
I don't think those are problematic errors, as there exists fallbacks. I suppose the errors come, because this theme doesn't haven't any specific files for elements under /metagui/themes/frackin/v2/. Anyways, just wanted to let you know :-)

Expected behavior. Currently have no way to check for an image's existence without causing an error message.


Composite resource phase-2

Pull Request Checklist:

[x] Positive Test Case Written by Dev

[x] Automated Testing

[ ] Sufficient User and Developer Documentation

[x] Passing Jenkins Build

[ ] Peer Code review and approval

Positive Test Case

Creating a Generic Aggregation:
Upload any file to a composite resource. In resource edit mode right click on the file and select option 'Set Generic Aggregation'. An aggregation gets created. Select the file and then select the Aggregation Metadata tab to see aggregation specific metadata. At this point the aggregation should have only the title metadata The aggregation title should be the same as the name of the file.

Editing Generic Aggregation Metadata: In resource edit mode, select a file that is part of a generic aggregation and then select Aggregation Metadata tab. You should be able to edit the following metadata:

title
keywords
temporal coverage
spatial coverage
key/value metadata

Creating Reference Timeseries Aggregation:
Upload a json file (file name must end with .json.refts) containing valid reference timeseries data. In resource edit mode right click on the json file and select the option 'Set Reference Timeseries Aggregation'. You should see a new aggregation has been created. Select the json file and then select Aggregation Metadata tab to see the extracted metadata. Note: You should not be able to edit any of the extracted metadata for this aggregation.

Creating Multidimensional Aggregation:

Creating aggregation by selecting netcdf file: Upload a valid netcdf file. In resource edit mode, right click on the netcdf file and then select the option 'Set Multidimensional Aggregation'. You should see a new aggregation has been created (Multidimensional Aggregation icon should appear). If the netcdf file was not in a folder when you selected the file to create the aggregation, a new folder should have been created (folder name same as the netcdf file name). Select the aggregation and then select Aggregation Metadata tab to see the extracted metadata. Note: Not all aggregation level metadata can be edited. However, if you edit any aggregation level metadata, you should see an option to update the netcdf file. Selecting the option to update the netcdf file will write the edited metadata to the netcdf file.
Creating aggregation by selecting a folder that contains a netcdf file: Create a folder and then upload a netcdf file to that folder. In resource edit mode, right click on the folder and select the option 'Set Multidimentional Aggregation'. A new aggregation should be created and no new folder should be created.
View aggregation content files: Double click on the aggregation (icon) to see the files that are part of this aggregation. You should find a new txt file in addition to the original netcdf file.

Creating Geographic Feature Aggregation:

Creating aggregation by selecting a file with extension  '.shp' file: Upload all the files that are part of the shape file. In resource edit mode, right click on the file with extension '.shp' and then select the option 'Set Geographic Feature Aggregation'. You should see a new aggregation has been created (Geographic Feature Aggregation icon should appear). If the .shp file was not in a folder when you selected the file to create the aggregation a new folder should have been created (folder name same as the .shp file name). Select the aggregation and then select Aggregation Metadata tab to see the extracted metadata. Note: Not all aggregation level metadata can be edited.
Creating aggregation by selecting a folder that contains all files that are part a shape file: Create a folder and then upload all files that are part of a shape file. In resource edit mode, right click on the folder and select the option 'Set Geographic Feature Aggregation'. A new aggregation should be created and no new folder should be created.
Creating aggregation by selecting a zip file that contains all the files that are part of a shape file. Upload a zip file. In resource edit mode, right click on the zip file and then select the option 'Set Geographic Feature Aggregation'. A new aggregation should be created. The original zip file will be deleted. If the zip file when selected for creating the aggregation was not in a folder a new folder should be created. If a new folder gets created the name of the folder is same as the name of the zip file.
View aggregation content files: Double click on the aggregation (icon) to see the files that are part of this aggregation.

Creating Geographic Raster Aggregation:

Creating aggregation by selecting a tif file: Upload a tif file. In resource edit mode, right click on the tif file and then select the option 'Set Geographic Raster Aggregation'. You should see a new aggregation has been created (Geographic Raster Aggregation icon should appear). If the  tif file was not in a folder when you selected the file to create the aggregation a new folder should have been created (folder name same as the tif file name). Select the aggregation and then select Aggregation Metadata tab to see the extracted metadata. Note: Not all aggregation level metadata can be edited. If you open the aggregation folder you should see a new vrt file.
Creating aggregation by selecting a folder that contains a single tif file: Create a folder and then upload a tif file to that folder. In resource edit mode, right click on the folder and select the option 'Set Geographic Raster Aggregation'. A new aggregation should be created and no new folder should be created. If you open the aggregation folder you should see a new vrt file.

Creating aggregation by selecting a folder that contains multiple tif files and a vrt file: Create a folder and then upload tif files and a vrt file that are part of raster dataset to that folder. In resource edit mode, right click on the folder and select the option 'Set Geographic Raster Aggregation'. A new aggregation should be created and no new folder should be created.
Creating aggregation by selecting a zip file that contains multiple tif files and one vrt file. Upload a zip file. In resource edit mode, right click on the zip file and then select the option 'Set Geographic Raster Aggregation'. A new aggregation should be created. The original zip file will be deleted. If the zip file when selected for creating the aggregation was not in a folder a new folder should be created.
View aggregation content files: Double click on the aggregation (icon) to see the files that are part of this aggregation.

Creating Timeseries Aggregation:

Creating aggregation by selecting a SQLite file: Upload a ODM2 SQLite file. In resource edit mode, right click on the SQLite file and then select the option 'Set Timeseries Aggregation'. You should see a new aggregation has been created (Timeseries Aggregation icon should appear). If the SQLite file was not in a folder when you selected the file to create the aggregation, a new folder should have been created (folder name same as the SQLite file name). Select the aggregation and then select Aggregation Metadata tab to see the extracted metadata. If you edit any aggregation level metadata, you should see an option to update the SQLite file. If you select the option to update the SQLite file, edited aggregation level metadata will be written to the SQLite file.

Creating aggregation by selecting a folder that contains a SQLite file: Create a folder and then upload a ODM2 SQLite file to that folder. In resource edit mode, right click on the folder and select the option 'Set Timeseries Aggregation'. A new aggregation should be created and no new folder should be created.

Creating aggregation by selecting a CSV file: Upload a CSV file containing timeseries data. In resource edit mode, right click on the CSV file and then select the option 'Set Timeseries Aggregation'. You should see a new aggregation has been created (Timeseries Aggregation icon should appear). If the CSV file was not in a folder when you selected the file to create the aggregation a new folder should have been created (folder name same as the CSV file name). Select the aggregation and then select Aggregation Metadata tab to see the extracted temporal coverage metadata. Once you edit all the aggregation level metadata to generate sufficient data for ODM2 SQLite file, you should see an option to update the SQLite file.

Creating aggregation by selecting a folder that contains a timeseries CSV file: Create a folder and then upload a timeseries CSV file to that folder. In resource edit mode, right click on the folder and select the option 'Set Timeseries Aggregation'. A new aggregation should be created and no new folder should be created.

View aggregation content files: Double click on the aggregation (icon) to see the files that are part of this aggregation. If this aggregation was created from a CSV file then you should see that CSV file as well as a new SQLite file. Otherwise, you should only see one SQLite file.

Remove Aggregation: To remove a single file aggregation (generic or reference timeseries), in resource edit mode, right click on the file and then select the option 'Remove Aggregation'. For multi-file aggregation (raster, geofeature, timeseries. multidimentional), right click on the folder(aggregation icon) and then select the option 'Remove Aggregation'. When an aggregation gets removed the aggregation metadata gets deleted, but the contents files stays.

Renaming an aggregation: In case of single file aggregation (generic and reference timeseries) you can rename the aggregation content file. In case of multi-file aggregation (raster, geofeature, timeseries. multidimentional) , you can rename the folder that represents the aggregation.

Moving an aggregation: In case of single file aggregation (generic or reference timeseries), you can move the file that is part of the aggregation to a different folder. In case of multi-file aggregation (raster, geofeature, timeseries. multidimentional), you can move the folder (folder shown as the aggregation type icon) to a different folder. In both cases the target folder must not represent a multi-file aggregation.

Updating resource coverage from coverage data in contained aggregations: If any of the contained aggregations has spatial coverage data, then in resource edit mode, you should see the button 'Set spatial coverage from content files'. Selecting this button will set the resource spatial coverage that includes all the spatial coverages of the contained aggregations. The same applies to temporal coverage. You should see a button 'Set temporal coverage from content files' if any of the aggregations has temporal coverage data.

Dwnloading a folder that contains one or more aggregations: Create an aggregation (see above how to create a specific type of aggregation) so that the aggregation content file(s) are in a folder. Right click on the folder that contains the aggregation that you created and select the option 'Download'. In the downloaded zip file in addition to the content files, you should find two additional xml files. The xml file that has file name ending with '_meta.xml' contains aggregation level metadata. The other xml file that has name ending with '_resmap.xml' is the aggregation level resouremap document.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

I have finished my review of the composite resource.

I walked through the system on park and it looks pretty good. Two things - one minor and one potentially major.

The icon alignment looks a little goofy. No big deal but a little jarring. We should resolve to a consistent size and margin/padding.

The second thing is that the system seems really picky when it comes to extra files in an aggregation. It's ok, and justifiable - shapefiles for instance need a specific number of specifically typed files in order to work, but I'd say we need either A. more graceful ways to handle stray files in an aggregation or B. better error messaging to the user such as "The file readme.html does not belong in a shapefile aggregation" as opposed to "could not create aggregation." Something actionable the user can do.

Apologies if any of this is already covered in the other reviews. Other than that, great work!

I have the icon alignment fix in the auto-aggregate work.  Getting close to having it ready for review.
Scott

From: Mark Robert Henderson<EMAIL_ADDRESS>Sent: Tuesday, May 15, 2018 7:51:26 PM
To: hydroshare/hydroshare
Cc: Scott Black; Mention
Subject: Re: [hydroshare/hydroshare] Composite resource phase-2 (#2719)
I walked through the system on park and it looks pretty good. Two things - one minor and one potentially major.

The icon alignment looks a little goofy. No big deal but a little jarring. We should resolve to a consistent size and margin/padding.

[image]https://user-images.githubusercontent.com/106148/40092146-cea75388-5889-11e8-9e13-7bb8c461c42d.png

The second thing is that the system seems really picky when it comes to extra files in an aggregation. It's ok, and justifiable - shapefiles for instance need a specific number of specifically typed files in order to work, but I'd say we need either A. more graceful ways to handle stray files in an aggregation or B. better error messaging to the user such as "The file readme.html does not belong in a shapefile aggregation" as opposed to "could not create aggregation." Something actionable the user can do.

Apologies if any of this is already covered in the other reviews. Other than that, great work!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/hydroshare/hydroshare/pull/2719#issuecomment-389369166, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AiKTZplwjc2RjypW_fqlnc240PX5fL6wks5ty4YegaJpZM4Te3lB.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Some unit tests are failing after I updated this branch with develop. Will fix those unit tests tonight and then deploy to park.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

Build finished.

I've deployed the updated branch to https://dev-hs-6.hydroshare.org/
I ran the following management commands:

remove_auto_generated_generic_metadata
fix_irods_user_paths (not sure if this one was necessary)
regenerate_xml_files_composite_resource (Ran for awhile and then errored out with this error.  django_irods.icommands.SessionException: (SessionException(...), 'Error processing IRODS request: 3. stderr follows:\n\nERROR: mkdirUtil: mkColl of /hydroshareuserZone/home/cuahsi6UserProxy/9e1b23607ac240588ba50d6b5b9a49b5/data error. status = -818000 CAT_NO_ACCESS_PERMISSION\n'))

Did I miss any commands?  And does something need to be done for the regenerate command error?

Any objections to merging develop into this branch?  Looks like it fell behind.

@sblack-usu No objections, in fact that would be very helpful!


Charts interfere with each other

When showing a couple of the default bar charts on a page, the self._destroy method applied to the first chart manages to affect the data for the second chart (causing the bars in the second chart to disappear), as the _mainStorage ends up with only the bar data belonging to the second chart.
As a quick hack, I've commented out the destroy method to stop this causing a problem for me (at line 740):
if (self._vis) {
// _mainStorage is getting polluted with the data from another chart.
// This causes the other chart to lose its bars when the first chart is redrawn.
// Ignoring this destroy call is the easiest hack to stop this happening.
//      self._destroy(self._vis, self._mainStorage);
}

I've encountered a similar issue to this, which was difficult to trace due to our use of Knockout bindings, components, and modules.
What I realised after much debugging was that both the class names within the data object AND the class names (and obviously IDs) of the HTML figure element must both be unique on the page:  we got around this by setting up KO computed observables for the class and ID names which were made unique on a given page of our application by suffixing with a unique identifier - we then bound these values using Knockout to he figure element e.g.
<figure data-bind="css:outboundClass, attr: {'id': outboundId }"></figure>
I'm posting here in case what I found helps anyone else who finds this post due to similar issues.


No image displaying

Hello,
When I run the code:
params = [{
	'size': '600x300',
	'location': '35.124762,-89.990795',
	'heading': '151.78',
	'pitch': '-0.76',
	'key': 'KEY NOT SHARED HERE'
}]

results = google_streetview.api.results(params)
results.preview()

It does not display an image. I am running this code in Google Colab. Here is what I get instead:
[0] DcLKdIVOjVWy1jDDui2kDA
===========================
date: 2019-06
location:
  lat: 35.12474824026881
  lng: -89.99079815233901
pano_id: DcLKdIVOjVWy1jDDui2kDA
status: OK

How do I get the image from google street view to appear?

Hi @gndumbri
The code results.preview() is for previewing the API search results and does not actually download the images. This is good for checking if your code is working.
To download the actual images, use:
# Download images to directory 'downloads'
results.download_links('downloads')

More information here.
After you download the images to the downloads folder, you can then load and display them in your notebook:
from IPython.display import Image

# Replace <PATH> with path to your downloaded streetview image
Image(filename='<PATH>/streetview_image.png')


Distinguishing exterior rings from holes

How can I distinguish exterior rings from holes in the results?
As an idea, the library could use a GeoJson alike format of polygons+multipolygons inputs/outputs to handle this case.

The algorithm doesn't actually output polygons with holes.  This isn't intentional, but a nice side-effect of the chaining process.
If you look at the demo here:
https://rawgit.com/voidqk/polybooljs/master/dist/demo.html
In the first demo ("1. Assorted Polygons"), it looks like the output has holes in it -- but if you step through the animation towards the end, where the segments are being chained together and turning green, you'll notice that the final result doesn't actually have any holes.

This screenshot is one step before the final result (i.e., hit the "Prev" button twice under "Animation:").
The "hole" is made by two polygons that touch at similar points, but it isn't an actual hole in a single polygon.
As far as GeoJson goes, I'm not sure what that is, or how it will help.  Maybe you could explain that further.

Hi, thanks for replying.
Basically my final idea is to pass the resulting polygon to render it to screen. At first I thought of using a non-zero filling rule, but that requires results with certain constraints, namely:

External shell polygons to have a counter-clockwise winding
Holes  to have a clockwise winding.

After a bit more thought I think I could simply use a even-odd filling rule, which doesn't take into account the polygon winding, is this right?
--
As for GeoJson (https://en.wikipedia.org/wiki/GeoJSON) it is some sort of semi-standard way to serialize geometric figures (points, lines, etc). That page on wikipedia have nice examples on the format of each one, but basically I'd say that the input and output of this lib are basically either Polygons or Multipolygons, only that the current output format doesn't allow distinguishing outer shells from holes inside those outer shells, making the conversion costly.
You may see here for a related discussion on a similar library: https://github.com/w8r/martinez/issues/5

Ah, now I see what you mean when you talk about holes!
You can see how I perform a fill on the demo page:
function drawRegions(regions, offset){
	regions.forEach(function(region, i){
		if (region.length <= 0)
			return;
		ctx.moveTo(scaleX(region[0][0]), scaleY(region[0][1]) + offset);
		for (var i = 1; i < region.length; i++)
			ctx.lineTo(scaleX(region[i][0]), scaleY(region[i][1]) + offset);
		ctx.closePath();
	});
}

function polyStroke(result, offset){
	ctx.beginPath();
	drawRegions(result.regions, offset);
	ctx.stroke();
}

function polyFill(result, rect1, rect2, offset){
	ctx.beginPath();
	if (result.inverted){
		ctx.moveTo(rect1[0], rect1[1] + offset);
		ctx.lineTo(rect1[0], rect2[1] + offset);
		ctx.lineTo(rect2[0], rect2[1] + offset);
		ctx.lineTo(rect2[0], rect1[1] + offset);
		ctx.closePath();
	}
	drawRegions(result.regions, offset);
	ctx.fill('evenodd');
}

Clockwise and counter-clockwise don't matter -- only the fact that it's an even/odd rule.
--
As for the GeoJSON Polygon, here is the spec:
https://tools.ietf.org/html/rfc7946#section-3.1.6
If I'm understanding this correctly, then a polybooljs polygon should be able to be converted to a GeoJSON Polygon (and vice-versa)... it would simply be a matter of embedding the inverted flag into the winding of the result.
So in theory, that should be possible.  Off the top of my head, I don't know exactly how to do that though.  You would have to find the outer-most polygon, and change it's winding to match the inverted flag, and then alternate windings for polygons inside it..?
I would be open to including utility functions in polybooljs to perform these conversions.  But I'm too busy to research and write them myself at the moment.

Also, I just thought of this: GeoJSON must enforce a coordinate system (is positive Y up or down?), in order to define winding.  Polybooljs doesn't care about the direction of positive Y.

GeoJSON support was just pushed for v1.2.0, let me know what you think in Issue #7.


VTOL: FW flight very strange lock down in Loiter.

Hi guys,
We've had a very strange case in witch once we've transitioned, we put the plane in Loiter manually, and from then on the VTOL just stopped responding. It disconnected from QGC and started Loiter but with Cruise speed, and not min airspeed. We switched off the RC to make it failsafe to no avail. It just continued circling. We tried everithing possible but nothing happened. At some point the batteries just started to die and the plane just landed very nice in Loiter. I must say the TECS just did a brilliant work.
We could not find the reason, because the LOG file just stopped recording very soon in to the flight. And the other logs are very ordinary.
http://logs.uaventure.com/view/dAEJ87t6rCy5qw7MqmAKkC
This is from the messages log:
2016_11_02_14_45_12: ARMED by RC
2016_11_02_14_45_13: [blackbox] /fs/microsd/log/2016-11-02
2016_11_02_14_45_13: [blackbox] recording: 14_45_11.px4log
2016_11_02_14_45_18: Takeoff detected
nothing more.
And here is the PreFlight log again normal log.
preflight_perf14_45_11.txt
It was on PixFalcon with the digital airspeed.
The plane was holding the loiter brilliantly all the time, so the GPS must have been working. The TECS were brilliant. Just it did not respond to our RC nor the our Telemetry connection. The telemetry was having a green light which mean there was a connection between the telemetry modules, but there was no obvious traffic.
Version 1.5RC1

This is a situation in which it would be nice to have MANUAL mode available.

@tubeme have you seen this behavior again?

@sanderux No never again. Sorry for the delay.

Unfortunately, this was probably a hard fault. Newer PX4 has hard fault logging if it happens again.


Components Don't Compile with strictNullChecks set to true in tsconfig.json

Ionic version:  (check one with "x")
[ ] 1.x
[x] 2.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Alert Component fails to compile on ionic build android when switching strictNullChecks to true in tsconfig.json
Expected behavior:

All Components compile correctly with strictNullChecks set to true.
Steps to reproduce:
Change your tsconfig.json to have strictNullChecks to true and then try to run an ionic build
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
--------------------------------
--------------------------------
Your system information:

Cordova CLI: 6.4.0
Ionic Framework Version: 2.0.0-rc.1
Ionic CLI Version: 2.1.4
Ionic App Lib Version: 2.1.2
Ionic App Scripts Version: 0.0.37
OS:
Node Version: v6.9.1
--------------------------------

I'm interested in seeing this addressed as well, particularly since there's no workaround that I know of (TypeScript doesn't support one-off exceptions to the strictNullChecks rule)

Yea, my work around has been to comment out strickNullChecks in my tsconfig when doing builds or pushing to my CI system. That way I at least get strict checking during dev. But this is flaky and people forget to do this so missing checks get added in on occasion. I would really love to see this addressed.

We will keep the progress of this feature here: https://github.com/driftyco/ionic/issues/10646
Thanks!


Add harfbuzz

HarfBuzz is a cross-platform opentype text shaping library which is popular among opensource projects and it would be nice if be added to vcpkg.
Repo: https://github.com/behdad/harfbuzz
Releases: https://www.freedesktop.org/software/harfbuzz/release/

I agree.

Fixed on #132 by @vlj :)


Typed Array missing one or more of type definitions for TypedArrays.prototype functions

⚙ Compilation target
ESNext
⚙ Library
typescript
Missing / Incorrect Definition
TypedArray.prototype.at
Sample Code
// Note Uint8Array is one of many classes that extends the TypedArray
const buffer = new Uint8Array();
buffer.at(0);

Documentation Link
MDN

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray#exceptions

TypedArray Spec

https://tc39.es/ecma262/multipage/indexed-collections.html#sec-%typedarray%.prototype.at

Works for me if lib is at least es2022: Playground

Hmmm..... Thought I had my compilerOptions.target set to es2022, not es2017
I think that was the actual issue.

@rcampbel For the record, the actual thing that controls it is lib - it’s just if you don’t have lib set explicitly then it’s inferred from target


Simulate dispatch latency during unit tests

The assertion for dispatch latency metrics is flaky since the
sender is a mock that doesn't do anything.
This ends up producing a dispatch latency of 0.
Signed-off-by: Pierangelo Di Pilato<EMAIL_ADDRESS>
Proposed Changes

Simulate dispatch latency during unit tests

/test pull-knative-sandbox-eventing-kafka-broker-channel-integration-tests-ssl
/test pull-knative-sandbox-eventing-kafka-broker-channel-integration-tests-sasl-ssl

/assign @aliok @matzew

/cherry-pick release-1.2

/cherry-pick release-1.1


hotfix/myNextClass

I have yet to rename the folder to MyNextClass instead of My Next Class and add view and controller folders. I also still have to organize the code and add #pragma marks. I hope that waiting to do those things makes it easier to see my changes to the code

This change is

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

byuSuite/Apps/My Next Class/MyNextClassViewController.m, line 425 at r1 ([raw file](https://github.com/byu-oit-appdev/ios-byusuite/blob/6ef1ed9f33b43f58132fdb63acc045afb98f0c92/byuSuite/Apps/My Next Class/MyNextClassViewController.m#L425)):

-(void)loadBuilding {
    [CampusLocationsClient loadCampusBuildingsWithCallback:^(NSArray<CampusBuilding *> *campusBuildings, ByuError *error) {

Do we ever reload? If so, we should start the spinner animating before this line as well

byuSuite/Apps/My Next Class/MyNextClassViewController.m, line 446 at r1 ([raw file](https://github.com/byu-oit-appdev/ios-byusuite/blob/6ef1ed9f33b43f58132fdb63acc045afb98f0c92/byuSuite/Apps/My Next Class/MyNextClassViewController.m#L446)):

            [self.map addAnnotation:self.building];
            self.mapLoaded = YES;

We might be able to replace this with a simple check to see if the map is not null

Comments from Reviewable

Review status: all files reviewed at latest revision, 2 unresolved discussions.

byuSuite/Apps/My Next Class/MyNextClassViewController.m, line 425 at r1 ([raw file](https://github.com/byu-oit-appdev/ios-byusuite/blob/6ef1ed9f33b43f58132fdb63acc045afb98f0c92/byuSuite/Apps/My Next Class/MyNextClassViewController.m#L425)):
Previously, romrell4 (Eric Romrell) wrote…
> Do we ever reload? If so, we should start the spinner animating before this line as well

done

byuSuite/Apps/My Next Class/MyNextClassViewController.m, line 446 at r1 ([raw file](https://github.com/byu-oit-appdev/ios-byusuite/blob/6ef1ed9f33b43f58132fdb63acc045afb98f0c92/byuSuite/Apps/My Next Class/MyNextClassViewController.m#L446)):
Previously, romrell4 (Eric Romrell) wrote…
> We might be able to replace this with a simple check to see if the map is not null

In the old code in refreshVeiw(), mapLoaded was set to YES after the request was initiated to get all buildings (which would then add a building annotation to the map upon a successful request). It seems as if the mapLoaded is to help with the timing of requesting the buildings with the other requests. Requesting the building info isn't initiated until the current semester is loaded and the student's schedule is loaded. Let me know when you have a sec and we can look at together

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion, all commit checks successful.

a discussion (no related file):
Format code

Comments from Reviewable

Review status: 5 of 6 files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, romrell4 (Eric Romrell) wrote…
> Format code

done

Comments from Reviewable

ok

Review status: 5 of 6 files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Reviewed 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, nateyj (Nathan Johnson) wrote…
> done

Remove spaces from group and directory

Comments from Reviewable

Reviewed 7 of 7 files at r4.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

a discussion (no related file):
Previously, romrell4 (Eric Romrell) wrote…
> Remove spaces from group and directory

done

Comments from Reviewable


add a gif of home page in read me

Issue Type:

[ ] Bug Report
[x] Feature Request
[ ] Documentaion

add a gif in read me like this repo
https://github.com/arpit456jain/Cool-Front-End_Templates

Can i work on this issue

Go ahead @priyakumari02


Improving eBPF support checks

Overview

so instead of checking <5.4 we check <4.4 with BTF?

We are checking for BTF which is mandatory for our sensor and ig.
Regarding the kernel version, checking 5.4 is because since 5.4 there is BTF/CO-RE but some kernels "lies" with their version so it's not valuable to check it.
Since kernel 4.4 there is eBPF so we can check that just in case but again, it's not too much valuable but it's more for us to have more debugging information, this is why we don't exist on the error but log it.
What do you think? @matthyx

Fine go ahead


assetfinder: init at v0.1.1

Description of changes
assetfinder - A lightweight tool to find domains and subdomains related to a given domain
See:

https://repology.org/project/assetfinder/information
https://github.com/tomnomnom/assetfinder/

Note: Despite being an old tool that is not in active development anymore, it is still used in certain cases for subdomain/domain discovery.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

Description of changes
assetfinder - A lightweight tool to find domains and subdomains related to a given domain
See:
* https://repology.org/project/assetfinder/information

* https://github.com/tomnomnom/assetfinder/

Note: Despite being an old tool that is not in active development anymore, it is still used in certain cases for subdomain/domain discovery.
Things done
* Built on platform(s)

  * [x]  x86_64-linux
  * [ ]  aarch64-linux
  * [ ]  x86_64-darwin
  * [ ]  aarch64-darwin

* For non-Linux: Is sandboxing enabled in `nix.conf`? (See [Nix manual](https://nixos.org/manual/nix/stable/command-ref/conf-file.html))

  * [ ]  `sandbox = relaxed`
  * [ ]  `sandbox = true`

* [x]  Tested, as applicable:

  * [NixOS test(s)](https://nixos.org/manual/nixos/unstable/index.html#sec-nixos-tests) (look inside [nixos/tests](https://github.com/NixOS/nixpkgs/blob/master/nixos/tests))
  * and/or [package tests](https://nixos.org/manual/nixpkgs/unstable/#sec-package-tests)
  * or, for functions and "core" functionality, tests in [lib/tests](https://github.com/NixOS/nixpkgs/blob/master/lib/tests) or [pkgs/test](https://github.com/NixOS/nixpkgs/blob/master/pkgs/test)
  * made sure NixOS tests are [linked](https://nixos.org/manual/nixpkgs/unstable/#ssec-nixos-tests-linking) to the relevant packages

* [x]  Tested compilation of all packages that depend on this change using `nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"`. Note: all changes have to be committed, also see [nixpkgs-review usage](https://github.com/Mic92/nixpkgs-review#usage)

* [x]  Tested basic functionality of all binary files (usually in `./result/bin/`)

* [24.05 Release Notes](https://github.com/NixOS/nixpkgs/blob/master/nixos/doc/manual/release-notes/rl-2405.section.md) (or backporting [23.05](https://github.com/NixOS/nixpkgs/blob/master/nixos/doc/manual/release-notes/rl-2305.section.md) and [23.11](https://github.com/NixOS/nixpkgs/blob/master/nixos/doc/manual/release-notes/rl-2311.section.md) Release notes)

  * [ ]  (Package updates) Added a release notes entry if the change is major or breaking
  * [ ]  (Module updates) Added a release notes entry if the change is significant
  * [ ]  (Module addition) Added a release notes entry if adding a new NixOS module

* [x]  Fits [CONTRIBUTING.md](https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md).

Add a 👍 reaction to pull requests you find important.

Related to https://github.com/NixOS/nixpkgs/issues/81418

Result of nixpkgs-review pr 279165 run on x86_64-linux 1

1 package built:

assetfinder

assetfinder was not maintained in the last 4 years. I highly doubt that the development will continue.

It still can be useful in certain cases, despite it being an abandon-ware, I also made sure it worked as intended. The versioning has been fixed, thank you for the review.

Result of nixpkgs-review pr 279165 run on x86_64-linux 1

1 package built:

assetfinder


does wss support cdn forwarding

The wss client of another library I am using cannot be accessed once cdn(cloudflare) is turned on. I want to know whether this library supports cdn

Cloudflare requires passing a couple of headers I think? Beast can certainly do that.
Can you detail cloudflare's requirements here?

I see that grpc has request header requirements, but the weboscket requirements are not found. I access the cloudflare-protected website via browser f12 and I don’t find anything special. I need to continue to search for information.
https://support.cloudflare.com/hc/en-us/articles/360050483011-Understanding-Cloudflare-gRPC-support
https://support.cloudflare.com/hc/en-us/articles/200169466-Using-Cloudflare-with-WebSockets

give up the use of cdn forwarding to solve this problem.


Add option for portrait background image

I have a hopefully simple request regarding portraits that others may find useful as well. It would be handy to be able to have a configurable background image that can go behind a character portrait. This way, I could have a consistent frame that the portrait can appear in without necessarily having to manually apply it to every portrait, or to have the option of customizable frames. Could also be used if you wanted to have something like a different background behind the character for different areas, for example.
Examples:

For the final result of:

One thing to consider with this would be how to handle scale/offsets, but if the image sizes were always consistent you could have a global offset for backgrounds and a corresponding global offset for the portraits, maybe with the option to still have an override on a per portrait basis.
Not an urgent request, but hopefully an idea that has some value! It's definitely a useful plugin. :)

This should be doable already by using custom portrait scenes.

With the new system in 2.0 you should be able to do this kind of layouts easily


a01_FastText

Hi,
In data_util_zhihu.py:
def create_voabulary(simple=None,word2vec_model_path='zhihu-word2vec-title-desc.bin-100',name_scope='')
but your data is zhihu-word2vec-title-desc.bin-100.txt, should I add the .txt to the path, but if I do this, it will have other errors

rename the txt file: zhihu-word2vec-title-desc.bin-100


xfontsel: 1.0.5 -> 1.0.6

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
Warning: no binary found that responded to help or version flags. (This warning appears even if the package isn't expected to have binaries.)
found 1.0.6 with grep in /nix/store/adg669da0gmhxmlgh7y2w5c7nw3w10gi-xfontsel-1.0.6

cc @viric for review

@GrahamcOfBorg eval

@GrahamcOfBorg build xfontsel

Success on x86_64-darwin (full log)
Attempted: xfontsel
Partial log (click to expand)
 /nix/store/s28xb9v7xf6axvf4a3av2mnczws2hsdg-coreutils-8.29/bin/mkdir -p '/nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6/share/X11/app-defaults'
 /nix/store/s28xb9v7xf6axvf4a3av2mnczws2hsdg-coreutils-8.29/bin/install -c -m 644 app-defaults/XFontSel '/nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6/share/X11/app-defaults'
make[2]: Leaving directory '/private/tmp/nix-build-xfontsel-1.0.6.drv-0/xfontsel-1.0.6'
make[1]: Leaving directory '/private/tmp/nix-build-xfontsel-1.0.6.drv-0/xfontsel-1.0.6'
post-installation fixup
gzipping man pages under /nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6/share/man/
strip is /nix/store/vb6mgjqgd9h11nbv60fvrp1ls9nxck2y-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6/bin
patching script interpreter paths in /nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6
/nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6

Success on x86_64-linux (full log)
Attempted: xfontsel
Partial log (click to expand)
make[1]: Leaving directory '/build/xfontsel-1.0.6'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6
shrinking /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6/bin/.xfontsel-wrapped
gzipping man pages under /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6/bin
patching script interpreter paths in /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6
checking for references to /build in /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6...
/nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6

Success on aarch64-linux (full log)
Attempted: xfontsel
Partial log (click to expand)
make[1]: Leaving directory '/build/xfontsel-1.0.6'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/673i7hnnc6kprrjalvxc16jj98qsrs2m-xfontsel-1.0.6
shrinking /nix/store/673i7hnnc6kprrjalvxc16jj98qsrs2m-xfontsel-1.0.6/bin/.xfontsel-wrapped
gzipping man pages under /nix/store/673i7hnnc6kprrjalvxc16jj98qsrs2m-xfontsel-1.0.6/share/man/
strip is /nix/store/3zq400fri5dv7d30lpxlqm2v9y1iis6j-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/673i7hnnc6kprrjalvxc16jj98qsrs2m-xfontsel-1.0.6/bin
patching script interpreter paths in /nix/store/673i7hnnc6kprrjalvxc16jj98qsrs2m-xfontsel-1.0.6
checking for references to /build in /nix/store/673i7hnnc6kprrjalvxc16jj98qsrs2m-xfontsel-1.0.6...
/nix/store/673i7hnnc6kprrjalvxc16jj98qsrs2m-xfontsel-1.0.6

Success on aarch64-linux (full log)
Attempted: xfontsel
Partial log (click to expand)
/nix/store/673i7hnnc6kprrjalvxc16jj98qsrs2m-xfontsel-1.0.6

Success on x86_64-linux (full log)
Attempted: xfontsel
Partial log (click to expand)
make[2]: Leaving directory '/tmp/nix-build-xfontsel-1.0.6.drv-0/xfontsel-1.0.6'
make[1]: Leaving directory '/tmp/nix-build-xfontsel-1.0.6.drv-0/xfontsel-1.0.6'
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6
shrinking /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6/bin/.xfontsel-wrapped
gzipping man pages under /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6/share/man/
strip is /nix/store/fzcs0fn6bb04m82frhlb78nc03ny3w55-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6/bin
patching script interpreter paths in /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6
checking for references to /tmp/nix-build-xfontsel-1.0.6.drv-0 in /nix/store/96zhy1sv3x7cmx05rvjj1ciyf6q4k9bk-xfontsel-1.0.6...

Success on x86_64-darwin (full log)
Attempted: xfontsel
Partial log (click to expand)
 /nix/store/s28xb9v7xf6axvf4a3av2mnczws2hsdg-coreutils-8.29/bin/mkdir -p '/nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6/share/X11/app-defaults'
 /nix/store/s28xb9v7xf6axvf4a3av2mnczws2hsdg-coreutils-8.29/bin/install -c -m 644 app-defaults/XFontSel '/nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6/share/X11/app-defaults'
make[2]: Leaving directory '/private/tmp/nix-build-xfontsel-1.0.6.drv-0/xfontsel-1.0.6'
make[1]: Leaving directory '/private/tmp/nix-build-xfontsel-1.0.6.drv-0/xfontsel-1.0.6'
post-installation fixup
gzipping man pages under /nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6/share/man/
strip is /nix/store/vb6mgjqgd9h11nbv60fvrp1ls9nxck2y-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6/bin
patching script interpreter paths in /nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6
/nix/store/h92vxr8ycnzwbcl6s1b8az5srw431d0d-xfontsel-1.0.6


pull request for e2e test at 01/20/2017 08:26:14

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


fix(ui): Added bootstrap style validation on Position page on Career Site

Closes #22.

[x] I have reviewed my code in "Files changed" tab.
[x] I have re-read the issue and this PR fully resolves it.

@delavaler Would we like to add related error display here also from the backend (for errors related to the relevant fields)?

@delavaler Would we like to add related error display here also from the backend (for errors related to the relevant fields)?

Yes, would be good to show errors related to fields with bootstrap style near these inputs.

@Lyams  maybe I wasn't clear enough, but I expect to create all style related changes from the update to tabler branch, since tabler has own styles, for input validations as well

wrong parent branch. Create PR with right parent(main) branch https://github.com/freeats/freeats/pull/137


insufficient permissions

TF50309: The following account does not have sufficient permissions to complete the operation: Ian Hay. The following permissions are needed to perform this operation: Create new projects.
This is supposed to be a test environment, why do I not have access?
AB#3683

Hello @ianhaymaxgeo Thank you for reaching us.
Hope this thread might help you #319
Thanks


IO Error: Cannot open file

In my environment, gadwall always fails like:
C:\temp>python -m gadwall duck.db
Traceback (most recent call last):
  File "C:\Program Files\Python39\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Program Files\Python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Program Files\Python39\lib\site-packages\gadwall.py", line 75, in <module>
    main()
  File "C:\Program Files\Python39\lib\site-packages\gadwall.py", line 68, in main
    cmd = Gadwall(args.filename.name)
  File "C:\Program Files\Python39\lib\site-packages\gadwall.py", line 22, in __init__
    self.conn = duckdb.connect(file_name)
RuntimeError: IO Error: Cannot open file "duck.db": The process cannot access the file because it is used by another process.

(Sorry, the last sentence may be wrong: it was in German, i translated it myself as i do not know how to force it to English)
I could fix this by two changes: I changed
    parser.add_argument('filename', type=FileType('r'))
    args = parser.parse_args()

    cmd = Gadwall(args.filename.name)

to
    parser.add_argument('filename')
    args = parser.parse_args()

    cmd = Gadwall(args.filename)

In fact, i wonder how the original code could work. But i did not find documentation of what argparse "returns" in case of type=FileType().
My environment:
Windows 10 21H2 (Build 19044.1586), 64bit
Python 3.9.6, 64bit
argparse-1.4.0
duckdb-0.3.2
gadwall-0.1.0
Kind regards,
Arnold

Thanks @a-schommer for reporting. args.filename.name is a str just like your fix.
Can you try something else? Add args.filename.close() before cmd = ...? and LMK if this works for you?

Add args.filename.close() before cmd = ...? and LMK if this works for you?

Yes, that works, too.
I sense this is better than my approach above because argparse still can check the file.


Fix #36047 - No deselect on already selected row when selection mode set to SELECT_ROW

Fixes #36047
I checked and it worked, it no longer de-selects an already selected row if the SELECT_MODE is set to SELECT_ROW.
How can I test this? I manually tested this but I think there are some edge cases or something.

PRs should be made against the master branch.
Please squash commits together and amend the commit log to be meaningful, "Fix" isn't. See https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md#format-your-commit-logs-with-readability-in-mind

PRs should be made against the master branch.
Please squash commits together and amend the commit log to be meaningful, "Fix" isn't. See https://github.com/godotengine/godot/blob/master/CONTRIBUTING.md#format-your-commit-logs-with-readability-in-mind

Ok sir I did it. Now I know that I need to pull request against master and not the latest branch. :)


No tarball for x86

Hi!
I'm updating the AUR version for 0.1.4 and there are no link for the x86 version (I'm trying this).
Thanks :)

I've created a 32 bit branch here https://github.com/jacobmischka/discord-linux/tree/x86, as far as I know there's not a way for me to submit a pull request to make a new branch so we'll need @XNBlank to manually create it.
Only three files are different between the two architectures:

The electron (discord) binary
libnode.so
snapshot_blob.bin

@jacobmischka I don't know why I didn't think of that. Created the branch.
https://github.com/XNBlank/discord-linux/tree/x86


Temperature is reported as "Unknown" for Samsung 870 EVO 2.5" SATA SSD

Checklist

[X] I have updated to the latest available Proxmox VE Custom Integration version, see the latest version here.

Describe the issue you are experiencing
I have three NVMe SSDs, two SATA HDDs and two SATA 2.5" SSDs (Samsung 870 EVO) on Proxmox Server.  All temperature and health status are reported fine except both the Samsung 870 EVO. The temperature is reported as "Unknown". They are /dev/sda and /dev/sdb on this Server.

In which version of Home Assistant Core do you have the problem?
2023.12.3
What version of Proxmox VE Custom Integration has the issue?
3.2.2
What version of Proxmox VE do you have the problem?
pve-manager/8.1.3/b46aac3b42da5d15
Diagnostics information
proxmoxve-50e327dbb6f24f8b09602c7de6c0a832-Disk pve _dev_sdb-12b769616ff13cefa5542c5e0a870a91.json.txt
Additional information
Update: I would like to add that Proxmox Web GUI reports the temperature properly. And also I was able to get temperature on command line using smartctl tool.
No response

According to the diagnostic file, this disk does not have temperature information (id 194 of the S.M.A.R.T. attributes).
So there is nothing to do on the integration side.

Thanks, @dougiteixeira for your time and effort . Now I notice these two SSDs are working fine but other two HDDs face same issues.
Can you help me in diagnosing this? Since there is no agent deployed by this integration in Proxmox, I would like to know which library/tool get gather data from Proxmox? Any hint on such will help me to debug in my case?

@swamytk
The best way to understand the behavior and the possibility of correction or addition of new features is by sending the integration diagnostic file, which will contain the information provided by the API for your instance.
The integration uses the proxmoxer package. The documentation on which the integration is based is that of the Proxmox API.
As for disk attributes, they should be standardized by the S.M.A.R.T. specification, but manufacturers often implement them outside of it.
Regarding the temperature of your disk, in #239 (to be included in a future version) I included the Airflow Temperature sensor, which may be available for your disk, the S.M.A.R.T. from Samsung is available here.
I'm also thinking about including other useful information about disk health.


Update client3:circe, client3:core, ... to 3.4.2

Updates

com.softwaremill.sttp.client3:circe
com.softwaremill.sttp.client3:core
com.softwaremill.sttp.client3:json-common

from 3.3.18 to 3.4.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.client3" } ]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #482.


cmd/gf: if env is production,swagger or openapi set auth config,eg: auth or password

What do you want to ask?
swagger setting auth config

I spent two hours thinking and figured out, he wants an authentication mechanism for swagger api path when he takes the whole project online in public.
We might provide basic auth mechanism in ghttp.Server/Request/Respose to validate the visitor.

Let me try adding this feature

Why not just adding an auth middleware for the /swagger and /api.json in production? Don't think this is problem.为什么不直接在生产环境中为 /swagger 和 /api.json 添加一个 auth 中间件呢？不要认为这是问题。

在中间件中获取不到路由path，目前这个方式需要由下往上改造， @gqcn 辛苦确认一下


Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs.

I want to use react-stonecutter with my existing project. However when I tried the simple usage example, nothing is displayed from the <CSSGrid/>. All I am getting is this error:

Uncaught Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component's render method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner).

import React from 'react'

import { CSSGrid, layout } from 'react-stonecutter';

export default class Photos extends React.Component {
	render() {
		return(

                       <button class="active_btn">Timeline Photos</button>

                       <button>Profile Photos</button>

               <CSSGrid
				  component="ul"
				  columns={5}
				  columnWidth={150}
				  gutterWidth={5}
				  gutterHeight={5}
				  layout={layout.pinterest}
				  duration={800}
				  easing="ease-out"
				>

A

B

C

				</CSSGrid>

		);
	}
}

I don't know whether this is relevant, but I am using "react": "^15.1.0", and while installing this package, I got this warning:
npm WARN peerDependencies The peer dependency<EMAIL_ADDRESS>included from react-addons-transition-group will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.

Can you please help me with this? Thank you.

Okay, I had to remove react package from inside the react-stonecutter package. And there was no error.

How did you remove react


Explorer docs updates for Stacks 2.1 readiness

@andresgalante Please add notes for docs changes required for Stacks 2.1 readiness.

There shouldn't be any changes in the docs related to 2.1


'mat-file-upload' is not a known element:

Hi Can you help with this ?
'mat-file-upload' is not a known element:

Did you add MatFileUploadModule to your imports?

@FredBesterwitch Are you still facing this issue?

closing for now.


Prism gravity and magnetic forward modeling in the frequency domain

Fatiando has modeling routines for right rectangular prisms calculated using the space domain formula of Nagy (2000) (fatiando.gravmag.prism). It would be great the have the frequency (wavenumber) domain implementation of Bhattacharyya and Navolio (1976). This might be faster or more efficient or can be used for FFT based inversions.
Reference
Bhattacharyya, B. K., and M. E. Navolio (1976), A Fast Fourier Transform Method for Rapid Computation of Gravity and Magnetic Anomalies Due to Arbitrary Bodies*, Geophysical Prospecting, 24(4), 633–649, doi:10.1111/j.1365-2478.1976.tb01562.x.

I can hop on that--I have expressions already coded up for those in python.  What I would need is for someone to give me a hand on how to PROPERLY fork and make the changes.  Any volunteers?

Hi Andy and welcome to Fatiando. Thank you for your willingness to help us.
Here in the Developers Guide you can find instructions on how to clone the repository and start to contribute to Fatiando. Again thank you

Great, thanks!  I've looked through the dev guide and I think I have most
of it down.  I have specific questions (e.g. about merging my branch back
into my forked project) but they will not become important until later.
Currently, I have a thematic question.  All of the fourier domain
expressions for a prism parallel the expressions for the spatial domain.
So, do we think there should be an additional file, say prism_fourier or
something like that, or should it be part of the current prism.py?
I would propose that there is a prism_fourier.py, which will parallel the
prism.py.  However, there would be additional user input to either get the
spatial domain response (exactly the same output as prism) or the fourier
domain response, in case more fourier operations were desired.  I'm open to
alternatives though.
Something to keep in mind, is that I'd like to implement some additional
fourier expressions in the future (e.g. kass 2008 for fourier terrain
correction/layer modeling) and maybe even fourier-domain inversion, if I
ever get around to it.  So how all this fits into the whole should kind of
be discussed now I think.
On Thu, Nov 19, 2015 at 9:22 AM, André<EMAIL_ADDRESS>wrote:

Hi Andy and welcome to Fatiando. Thank you for your willingness to help
us.
Here in the Developers Guide http://www.fatiando.org/develop.html you
can find instructions on how to clone the repository and start to
contribute to Fatiando. Again thank you
—
Reply to this email directly or view it on GitHub
https://github.com/fatiando/fatiando/issues/225#issuecomment-158107353.

--
Dum inter homines sumus, colamus humanitatem.

I'm also 100% unfamiliar with cython; my plan is to implement this completely in python, doing my best to make it general for cython.  Is that acceptable?

@drandykass about the whole github workflow, it would be best if you submit the pull request (PR) as soon as you have an initial commit of changes. You can keep making commits and the PR will update automatically, so don't worry if the code is incomplete. That way, we can comment and discuss the code there while you go along. The github docs are a great reference for this.
Regarding the modules, I agree that a prism_fourier module would be best. You can make all functions have the same signature (same input and output) as the space domain versions. That way the new module can be a drop-in replacement for the other one.
It might be best to have separate functions for getting the frequency domain outputs. That way you can even have them take inputs in the frequency domain as well (I imagine this would be good to do multiple modeling operations). The space domain functions (gz, gzz etc) could then convert to-from the frequency domain and use the frequency domain functions internally.

Sounds good.  I didn't write them that way, but it's an easy change.  Right
now they return the result in the fourier domain, and there's a final
utility to transform to space domain.  I'll submit a pull request here
shortly.
On Wed, Nov 25, 2015 at 1:53 PM, Leonardo Uieda<EMAIL_ADDRESS>wrote:

@drandykass https://github.com/drandykass about the whole github
workflow, it would be best if you submit the pull request (PR) as soon as
you have an initial commit of changes. You can keep making commits and the
PR will update automatically, so don't worry if the code is incomplete.
That way, we can comment and discuss the code there while you go along. The
github docs https://help.github.com/articles/using-pull-requests/ are a
great reference for this.
Regarding the modules, I agree that a prism_fourier module would be best.
You can make all functions have the same signature (same input and output)
as the space domain versions. That way the new module can be a drop-in
replacement for the other one.
It might be best to have separate functions for getting the frequency
domain outputs. That way you can even have them take inputs in the
frequency domain as well (I imagine this would be good to do multiple
modeling operations). The space domain functions (gz, gzz etc) could then
convert to-from the frequency domain and use the frequency domain functions
internally.
—
Reply to this email directly or view it on GitHub
https://github.com/fatiando/fatiando/issues/225#issuecomment-159729106.

--
Dum inter homines sumus, colamus humanitatem.

Sounds great!