Savage Worlds compatibility

Hello! I'd like to use this module to display information from a Savage Worlds setting but I'm having trouble getting it to recognize the unique trackers that SW uses. The IDs should be wounds and woundsMax but this just displays an "undefined" error, and searching through the console is of no help (in fact, the site may be out of date with what it suggests searching for as I couldn't find "game.modules" anywhere).
In addition, the initiative tracker places a numerical indicator next to the combatants, but not the actual card # and suit as it does in Foundry. The combatants appear to be in the correct order, so I don't know if a numerical identifier was used in place of card/suit, but it would be great to have that instead!
Lastly, I'd love for a way to show things like the Adventure Deck or Action Deck card draws. Not sure if there's a way to do that or not.
Anyway, thank you!

I did get Wounds to show up! I had the id incorrect. It's "system.wounds.value" and "system.wounds.max". So that's working! It goes a little backwards since you GAIN wounds rather than LOSING hit points, but it works if you just max out the wounds and subtract.
Now to figure out the initiative tracker display! Any help would be most appreciated. Thanks!

Amazing, thank you!!


how to save different events on different difficulties Psych Engine

What is your question?
now this is my problem: i was trying to save different event's on different difficulties because for EX. the event Is loaded on all the difficulties but i wanted was they got separate event's (pls 0.4.2 version pls) if anyone got a solution thx!

You can save specific events to specific charts. Including separate difficulties. Just make sure the events you want are saved inside of your chart, "songname-difficulty.json" and not in an events.json.

You can save specific events to specific charts. Including separate difficulties. Just make sure the events you want are saved inside of your chart, "songname-difficulty.json" and not in an events.json.

what is the version for this?? of psych engine of course

You can save specific events to specific charts. Including separate difficulties. Just make sure the events you want are saved inside of your chart, "songname-difficulty.json" and not in an events.json.

what is the version for this?? of psych engine of course

this works for both 0.4 and 0.5+

You can save specific events to specific charts. Including separate difficulties. Just make sure the events you want are saved inside of your chart, "songname-difficulty.json" and not in an events.json.

hmmmm... right but i also find out another which was events-difficulty. suprisingly no one found it yet. I think it also works like you said so I think both of these solutions are the key so I think it is time to close thx for the help!


covering threading

I'm a little nervous that the recent refactoring of forms #199 might have affected threading, which was used inside the old skfem.utils.asm function and is now used in the assemble methods of LinearForm and BilinearForm.  Threading with more than one thread isn't covered in tests or docs/examples.  (During development of #199 I regularly ran pytest -n auto tests and parallel python {} ::: docs/examples/ex??.py.)
There was a snippet in the old docstring for asm:
https://github.com/kinnala/scikit-fem/blob/a2bdb953e26df1b7228284d481a4bb87ddbb3335/skfem/assembly/asm.py#L38-L50
but I never attempted to extend that into a complete example.
Should nthread > 1 in LinearForm or BilinearForm be tested or demonstrated?
I'm not sure what the use case is.  The profiling I've done has been on quite narrow classes of problems but in no case has assembly been significant compared to meshing or solving.  I mean it looks like a good idea, I just don't know what kind of example to write to showcase it.

I actually never had a real use case in mind. I just had an example where
the assembly took around 2 minutes without threading and less than a minute
with threading. I think the resulting matrix was so big that I'd never be
able to solve that on my laptop.
I could try to recreate that. Maybe now it needs to be a different
decorator altogether.
On Fri, 21 Jun 2019 at 6.23, Geordie McBain<EMAIL_ADDRESS>wrote:

I'm a little nervous that the recent refactoring of forms #199
https://github.com/kinnala/scikit-fem/pull/199 might have affected
threading, which was used inside the old skfem.utils.asm function and is
now used in the assemble methods of LinearForm and BilinearForm.
Threading with more than one thread isn't covered in tests or
docs/examples. (During development of #199
https://github.com/kinnala/scikit-fem/pull/199 I regularly ran pytest
-n auto tests and parallel python {} ::: docs/examples/ex??.py.)
There was a snippet in the old docstring for asm:
https://github.com/kinnala/scikit-fem/blob/a2bdb953e26df1b7228284d481a4bb87ddbb3335/skfem/assembly/asm.py#L38-L50
but I never attempted to extend that into a complete example.
Should nthread > 1 in LinearForm or BilinearForm be tested or
demonstrated?
I'm not sure what the use case is. The profiling I've done has been on
quite narrow classes of problems but in no case has assembly been
significant compared to meshing or solving. I mean it looks like a good
idea, I just don't know what kind of example to write to showcase it.

This seems to work:
import numpy as np

from timeit import timeit
from numba import njit
from skfem import *
from skfem.assembly.form.bilinear_form import BilinearForm

m = MeshTet()
m.refine(5)
basis = InteriorBasis(m, ElementTetP2())

class ThreadablePoissonForm(BilinearForm):
    @staticmethod
    @njit(nogil=True)
    def kernel(A, ix, u, v, w, dx):
        for k in range(ix.shape[0]):
            i, j = ix[k]
            A[i, j] = np.sum((u[j][1][0]*v[i][1][0] +
                              u[j][1][1]*v[i][1][1] +
                              u[j][1][2]*v[i][1][2]) * dx, axis=1)

@bilinear_form
def bilinf(u, du, v, dv, w):
    return sum(du * dv)

def asm_multithreaded():
    return ThreadablePoissonForm(None).assemble(basis, nthreads=8)

def asm_singlethreaded():
    return asm(bilinf, basis)

print("Multithreaded assembly took " +
      str(timeit(asm_multithreaded, number=2)) + " s")
print("Singlethreaded assembly took " +
      str(timeit(asm_singlethreaded, number=2)) + " s")

But not so greatly:
Multithreaded assembly took 6.666582662001019 s
Singlethreaded assembly took 8.072949173998495 s

With larger problem:
Multithreaded assembly took 31.915914687000623 s
Singlethreaded assembly took 37.448626509998576 s

I wonder if this support should be dropped since the difference is not that great after all...

Remark: Changes are required after Numba 0.46.0 release. It seems that they are dropping support for some of the type inference required here. This works now with 0.44.0 but you get a deprecation warning.


Multidimensional json in json-server

In some cases such as the need to return to the multi-dimensional json:
{
"posts": [
{ "id": 1, "title": "json-server", "author": "typicode" }
],
"comments": [
{ "id": 1,  "name": "hu","body": "good", "postId": 1 },
{ "id": 2, "name": "jin","body": "awesome json-server", "postId": 1 }
]
}
http://localhost:3000/posts/1/  could  return like:
{
"posts": [
{
"id": 1,
"title": "nothing",
"author": "su",
"comments":[
{
"author": "hu",
"body": "good"
},
{
"author":"jin",
"body":"awesome json-server"
}
],
}]
}
bad english :P

No worries about the english, with examples I can understand.
You can't right now.
No promise, but I'll see what can be done.

I'm not sure if I've got the skills yet, but I'll have a look and see what I can manage.

Just published v0.7.10. You can now do:
GET /posts/1?_embed=comments

@Shakyamuni177te thanks for offering help :)

@typicode  awesome  and thx

Hi! Doesn't work for me
GET http://localhost:3000/posts/1
returns:
{
"id": 1,
"title": "json-server",
"author": "beto",
"comments": [
{
"id": 1,
"author": "juampi",
"body": "Un comentario de juampi"
},
{
"id": 2,
"author": "diego",
"body": "Un comentario de diego"
},
{
"id": 3,
"author": "juampi",
"body": "Un comentario de juampi"
}
]
}
GET http://localhost:3000/posts/1?_embed=comments
returns the same json
My version of json server is
eeeee@desktop:~/Documentos/api-posts$ json-server --version
0.7.21
Sorry my english and thanks


Q: should admin be able to update old rounds?

@euglazer and i stumbled upon that the UI allows you to attempt to create buckets in previous rounds, but the API errors, so i just wanted to bring up the question of what is the expected functionality.

Really interesting question. Tricky because it doesn't necessarily make sense for you to retroactively update rounds, but an admin needs to be able to make changes. I'd say for now, no buckets in previous rounds. Let's talk about it in the next sprint planning though.
<3


[TS migration] Migrate 'GrowlNotification' component to TypeScript

Details

Migrated GrowlNotification and all the related components to TypeScript.
Fixed Issues

$ https://github.com/Expensify/App/issues/25127
Tests

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

cc: @kubabutkiewicz

Please refer to this conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1704193571187889
This PR is currently blocked and I'm waiting for Bank Refactor PR to be merged into main, after which we should look into removing the Growl from the application and swapping it for internally declared functionality. After the PR is merged I will work on finding non-growl ways of replacing the old functionality.

Let's fix lint and make this PR as ready for review @cdOut

@blazejkustra working on it right now, currently writing test steps and recording videos.

Reviewer Checklist

[x] I have verified the author checklist is complete (all boxes are checked off).
[x] I verified the correct issue is linked in the ### Fixed Issues section above
[x] I verified testing steps are clear and they cover the changes made in this PR

[x] I verified the steps for local testing are in the Tests section
[x] I verified the steps for Staging and/or Production testing are in the QA steps section
[x] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[x] I checked that screenshots or videos are included for tests on all platforms
[x] I included screenshots or videos for tests on all platforms
[x] I verified tests pass on all platforms & I tested again on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[x] I verified proper code patterns were followed (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I verified that this PR follows the guidelines as stated in the Review Guidelines
[x] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] If a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[x] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[x] All JSX used for rendering exists in the render method
[x] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[x] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native
https://github.com/Expensify/App/assets/2590174/e0796acb-063c-4229-96b7-4acef763307a

Android: mWeb Chrome
https://github.com/Expensify/App/assets/2590174/ac1376db-a39b-46ef-b99e-7f78f0ea28b7

iOS: Native
https://github.com/Expensify/App/assets/2590174/b7b93f08-06b1-4f39-9411-1eb43f507de2

iOS: mWeb Safari
https://github.com/Expensify/App/assets/2590174/ef4c0df4-dff9-44fb-b934-3438f0cc43fb

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/2590174/4bdc91cf-db7a-4eb1-8481-ae1241609149

MacOS: Desktop
https://github.com/Expensify/App/assets/2590174/ff9df58d-7309-44b0-9570-8bcca7255e3b

@hayata-suenaga I've implemented your review suggestions, could you please take a look at this PR again?

@hayata-suenaga I've implemented your review suggestions, could you please check the PR again?

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

All tests were passing. don't know why Melvin thinks otherwise 🤔

🚀 Deployed to staging by https://github.com/hayata-suenaga in version: 1.4.52-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/Beamanator in version: 1.4.52-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


I am not able to understand how to download my resume or save it in my pc.

Please help me out. I have spent all my day writing a resume on your website.
After Saving it in the p.c, it is not getting open. It is showing me all the code of respective saved files instead of the resume.

Hi @Winter-bear123 ,
There is an export button on the right side menu.  You can use the Download PDF option.
Hope this helps! 😄

Thank you for your response. I panicked last time that I could not figure
that. Thanks and it did help
Regards
On Thu, 15 Apr, 2021, 5:02 PM Shivani Jadhav, @.***>
wrote:

Hi @Winter-bear123 https://github.com/Winter-bear123 ,
There is an export button on the right side menu. You can use the Download
PDF option.
Hope this helps! 😄
[image: rxresume-export]
https://user-images.githubusercontent.com/36772500/114862623-6074de00-9e0c-11eb-8cd4-0380c281746a.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/AmruthPillai/Reactive-Resume/issues/480#issuecomment-820352852,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOUHV4ZM3XHIZRPYYRGA6YTTI3FGNANCNFSM42ZT66TQ
.

For anyone trying to host this application themselves, you'll need to host it on the Google Cloud Platform. After you've run npm install from the Google cloud console,
you'll need to
cd Reactive-Resume/functions/
and then again run
npm install
in order to install the cloud functions that allow you to export the pdf. Oh, and GCP wants a credit card on file for hosting.

I am not able to download my resume.It is saying there is some problem.

Closing this in favor of Reactive Resume v3 release.
If you continue to face this issue, please raise a new one and I'll have a look at it as soon as I can.
In the meantime, if you are able to, please consider donating to keep supporting the project: https://www.buymeacoffee.com/AmruthPillai :)
Thank you!

I'm unable to download the full resume. Pls check this link and try to download
https://rxresu.me/nishantop/nishant-raj


qlpfpga-symbiflow-plugins submodule checkout error

When following the steps at https://symbiflow.readthedocs.io/en/latest/symbiflow-arch-defs/docs/source/getting-started.html#prepare-environment, and cloning the repository like:
git clone https://github.com/SymbiFlow/symbiflow-arch-defs.git

It looks like a submodule is referring to a commit that no longer exists:
...
Submodule path 'third_party/symbiflow-xc-fasm2bels/third_party/prjxray/third_party/python-sdf-timing': checked out '0afbbfe5cec97330b3261d811a4d604a471a5d98'
Submodule path 'third_party/symbiflow-xc-fasm2bels/third_party/prjxray/third_party/sanitizers-cmake': checked out '99e159ec9bc8dd362b08d18436bd40ff0648417b'
Submodule path 'third_party/symbiflow-xc-fasm2bels/third_party/prjxray/third_party/yaml-cpp': checked out '33316d531bd9032d66f5bcc3ba1fd114a4ab0e1c'
Submodule path 'third_party/symbiflow-xc-fasm2bels/third_party/prjxray/third_party/yosys': checked out '54294957ed15d954c69c2722028209077cf91cfe'
Submodule path 'third_party/symbiflow-xc-fasm2bels/third_party/prjxray-db': checked out '8372b58fe62c67f8f5896d78cd1611d01621dfae'
Submodule path 'third_party/symbiyosys': checked out '091222b87febb10fad87fcbe98a57599a54c5fd3'
Submodule path 'third_party/vtr-xml-utils': checked out 'eebb820539465870124d1140b30d56f6f273a24c'
Submodule path 'third_party/xc-fasm': checked out '14afc2bae24cbf6ee5e7d057a58b4cbd776358d0'
fatal: Unable to checkout 'a598aa2d3c5157d33d6a7aa2abab609f592ea1a8' in submodule path 'third_party/qlfpga-symbiflow-plugins'
make: *** [third_party/make-env/conda.mk] Error 1

This PR https://github.com/SymbiFlow/symbiflow-arch-defs/pull/2211 should fix the issue as it removes the submodule in question and adds mechanism for fetching relevant data from GCS


Discrepancy between Java examples.

There is a discrepency between the Java examples. PlainHello uses Map<String, String> for input while Hello and ManualHello use String. It was originally String but was changed to Map<String, String>, but Hello and ManualHello were changed back to String. So at least for the hello examples, do we want valid input to be:
String:
"Stephanie"

or Map<String, String>:
{
    "name": "Stephanie"
}

?

Okay, so after talking with @pselle on Slack. She went back to using String so that the examples could be executed by CloudWatch, we additionally discussed PlainHello and we have decided that this baseline example is not really needed so I will delete it in a PR.

Clarifying that I went to Map, not String, for the notes :)


aminal: init at 0.7.4

[InProgress] Working on darwin
Motivation for this change
Nice terminal emulator.
Things done

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

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

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

@GrahamcOfBorg build aminal

Success on aarch64-linux (full log)
Attempted: aminal
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/j13ldjm5fi8vliawpi7q2443s73r5li0-aminal-0.7.4-bin
shrinking /nix/store/j13ldjm5fi8vliawpi7q2443s73r5li0-aminal-0.7.4-bin/bin/aminal
strip is /nix/store/qjrnv0qw44bw1hc23zhfh26xd1c25dfs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/j13ldjm5fi8vliawpi7q2443s73r5li0-aminal-0.7.4-bin/bin
patching script interpreter paths in /nix/store/j13ldjm5fi8vliawpi7q2443s73r5li0-aminal-0.7.4-bin
checking for references to /build in /nix/store/j13ldjm5fi8vliawpi7q2443s73r5li0-aminal-0.7.4-bin...
strip is /nix/store/qjrnv0qw44bw1hc23zhfh26xd1c25dfs-binutils-2.30/bin/strip
/nix/store/j13ldjm5fi8vliawpi7q2443s73r5li0-aminal-0.7.4-bin

Success on aarch64-linux (full log)
Attempted: aminal
Partial log (click to expand)
/nix/store/j13ldjm5fi8vliawpi7q2443s73r5li0-aminal-0.7.4-bin

Success on x86_64-linux (full log)
Attempted: aminal
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/s40zyjz35zi4jjswh3mld6l1gq7y2g4s-aminal-0.7.4-bin
shrinking /nix/store/s40zyjz35zi4jjswh3mld6l1gq7y2g4s-aminal-0.7.4-bin/bin/aminal
strip is /nix/store/n4hb93w6j076xcjw5pm09rdmc09s075b-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/s40zyjz35zi4jjswh3mld6l1gq7y2g4s-aminal-0.7.4-bin/bin
patching script interpreter paths in /nix/store/s40zyjz35zi4jjswh3mld6l1gq7y2g4s-aminal-0.7.4-bin
checking for references to /build in /nix/store/s40zyjz35zi4jjswh3mld6l1gq7y2g4s-aminal-0.7.4-bin...
strip is /nix/store/n4hb93w6j076xcjw5pm09rdmc09s075b-binutils-2.30/bin/strip
/nix/store/s40zyjz35zi4jjswh3mld6l1gq7y2g4s-aminal-0.7.4-bin

Success on x86_64-darwin (full log)
Attempted: aminal
Partial log (click to expand)
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory
find: '/nix/store/4a6vr5kvpy11jpnifcd50663kai2i3ym-aminal-0.7.4': No such file or directory

@NixOS/darwin-maintainers can I get a review on this PR, my first involving Darwin-specific code.

@LnL7 PTAL.

Success on x86_64-darwin (full log)
Attempted: aminal
Partial log (click to expand)
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory
find: '/nix/store/19wn33h0h63n2qiwhpdpx4m9pfv4wj57-aminal-0.7.4': No such file or directory

Success on x86_64-linux (full log)
Attempted: aminal
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/8zslpb5gzmhiwnymqi2f7nxv73dzv9qp-aminal-0.7.4-bin
shrinking /nix/store/8zslpb5gzmhiwnymqi2f7nxv73dzv9qp-aminal-0.7.4-bin/bin/aminal
strip is /nix/store/n4hb93w6j076xcjw5pm09rdmc09s075b-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/8zslpb5gzmhiwnymqi2f7nxv73dzv9qp-aminal-0.7.4-bin/bin
patching script interpreter paths in /nix/store/8zslpb5gzmhiwnymqi2f7nxv73dzv9qp-aminal-0.7.4-bin
checking for references to /build in /nix/store/8zslpb5gzmhiwnymqi2f7nxv73dzv9qp-aminal-0.7.4-bin...
strip is /nix/store/n4hb93w6j076xcjw5pm09rdmc09s075b-binutils-2.30/bin/strip
/nix/store/8zslpb5gzmhiwnymqi2f7nxv73dzv9qp-aminal-0.7.4-bin

Success on aarch64-linux (full log)
Attempted: aminal
Partial log (click to expand)
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/349pgr8yn3m1ihrwjlqlw4avkw3acrb0-aminal-0.7.4-bin
shrinking /nix/store/349pgr8yn3m1ihrwjlqlw4avkw3acrb0-aminal-0.7.4-bin/bin/aminal
strip is /nix/store/qjrnv0qw44bw1hc23zhfh26xd1c25dfs-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/349pgr8yn3m1ihrwjlqlw4avkw3acrb0-aminal-0.7.4-bin/bin
patching script interpreter paths in /nix/store/349pgr8yn3m1ihrwjlqlw4avkw3acrb0-aminal-0.7.4-bin
checking for references to /build in /nix/store/349pgr8yn3m1ihrwjlqlw4avkw3acrb0-aminal-0.7.4-bin...
strip is /nix/store/qjrnv0qw44bw1hc23zhfh26xd1c25dfs-binutils-2.30/bin/strip
/nix/store/349pgr8yn3m1ihrwjlqlw4avkw3acrb0-aminal-0.7.4-bin


Problems with log-scaling Pseudocolor plot

Amit reported a difference in how 2.3.2 and 2.4 draw a Pseudocolor plot with log scaling. I've attached a tarball with Amit's data, screenshot of the difference between 2.3.2 and 2.4, and a python script for reproducing.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 987
Status: Resolved
Project: VisIt
Tracker: Bug
Priority: Normal
Subject: Problems with log-scaling Pseudocolor plot
Assigned to: Kevin Griffin
Category: -
Target version: 2.9.1
Author: Kathleen Biagas
Start: 03/01/2012
Due date:
% Done: 100%
Estimated time:
Created: 03/01/2012 12:37 pm
Updated: 03/19/2015 11:08 pm
Likelihood: 3 - Occasional
Severity: 4 - Crash / Wrong Results
Found in version: 2.4.0
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
Amit reported a difference in how 2.3.2 and 2.4 draw a Pseudocolor plot with log scaling. I've attached a tarball with Amit's data, screenshot of the difference between 2.3.2 and 2.4, and a python script for reproducing.
Comments:
Appears to be a problem in how textures are used for coloring. If the 'Apply color using textures' flag is turned off, the coloring is the same as for 2.3.2. We had another user recently hit this issue and so I reverted this ticket to the new state for a short discussion The problem is with the vtkMapper::SetInterpolateScalarsBeforeMapping(int) method which gets called in the avtVariableMapper::SetColorTexturingFlag() method. Code below for reference during our discussion. Two things to note:1. By default, vertex color is used to map colors to a surface. Colors are interpolated after being mapped. This option avoids color interpolation by using a one dimensional texture map for the colors (scalars are interpolated then color applied from the one dimensional texture map)2. Cell data always uses vertex color. Only point data can use both texture and vertex coloring.#define ColorTextureMapSize 256// a side effect of this is that this>ColorCoordinates and // this>ColorTexture are set.void vtkMapper::MapScalarsToTexture(vtkDataArray* scalars, double alpha) { double** range = this>LookupTable>GetRange();// Get the texture map from the lookup table. // Create a dummy ramp of scalars. // In the future, we could extend vtkScalarsToColors. double k = (range1range0) / (double)(ColorTextureMapSize1); vtkFloatArray** tmp = vtkFloatArray::New(); tmp>SetNumberOfTuples(ColorTextureMapSize); float* ptr = tmp>GetPointer(0); for (int i = 0; i < ColorTextureMapSize; i) { **ptr = range0 ((float)(i)) ** k; ptr; } this>ColorTextureMap = vtkImageData::New(); this>ColorTextureMap>SetExtent(0,ColorTextureMapSize1, 0,0, 0,0); this>ColorTextureMap>SetNumberOfScalarComponents(4); this>ColorTextureMap>SetScalarTypeToUnsignedChar(); this>ColorTextureMap>GetPointData()>SetScalars( this>LookupTable>MapScalars(tmp, this>ColorMode, 0)); // Do we need to delete the scalars? this>ColorTextureMap>GetPointData()>GetScalars()>Delete(); // Consistent register and unregisters this>ColorTextureMap>Register(this); this>ColorTextureMap->Delete(); tmp->Delete();..} Hello:Fixed a bug in VTK Mapper color texturing not using Log coordinates when Log scaling is selected. Also added test for pseudocolor plots using color texturing and log scale.2.9RC:Sending svn_bin/bv_support/bv_vtk.shTransmitting file data .Committed revision 26006.Adding baseline/plots/pseudocolorAdding (bin) baseline/plots/pseudocolor/pseudocolor_01.pngAdding tests/plots/pseudocolor.pyTransmitting file data ..Committed revision 26007.Trunk:Sending svn_bin/bv_support/bv_vtk.shTransmitting file data .Committed revision 26009.Adding baseline/plots/pseudocolorAdding tests/plots/pseudocolor.pyCommitted revision 26010.Kevin

0996_PC_Log_Bug.tar.gz


Add Support for Favourite (Media) Groups.

Issue #489 discusses a similar feature, but I believe that is for favourite/saved searches. This feature request is to allow for grouping favourite media. I will try to implement it myself at some point but can't guess when that would be.

I would like to try implementing this sometime soon, although it may take a long time for me to get anywhere. Any hints/suggestions would be appreciated.
My initial goals will be:

Create an S.Q.L. database that will track which images have been favourited and which favourite groups they are in.
Check that database when loading an image in the viewer, so the existing favourite buttons can reference it.
Update the database when the existing favourite buttons on the viewer are used.
Add a button to the viewer that allows the image to be added to a favourite group, also creating a new group if necessary.
Add some U.I. to the viewer that allows users to see which groups the image is currently in, and allow it to be removed from them selectively.
Add settings that allow users to specify distinct save paths, possibly including file names, for each favourite group.

Future goals may include:

Supporting symlinks/shortcuts, to reduce storage space used by favourites that exist in multiple groups.
Offering a setting to indicate favourite/group status on the image thumbnails in the main window.
Offering controls to search, and possibly sort search results, based on images' favourite/group status.
Functionality to search/browse through favourites already saved (i.e. registered in the database).
Add keyboard shortcuts in the viewer window to toggle favourite group membership for the displayed image.

Does this seem like a good approach? The first thing I will do is look at how the current database is designed and how hashes are stored/compared.

It seems like the current database has a single table with columns for the media hash and saved path. Since it seems like sqlite does not support arrays, here are some ideas for how this could be handled:

Add a table to store the user defined groups and group-specific settings.
Add a string column to the existing table that would be formatted as a comma-separated list of group ids.

OR

Add a table to store the user defined groups and group-specific settings.
Add a group lookup table that stores entries with a non-unique reference integer and another integer for the actual group I.D., so each combination of groups that has been used would have one row in that table for each group in the combination.
Add an integer column to the existing table that represents the reference integer of the group lookup table.

I don't know which would be best for most users but I suspect the second method. There may be better methods-- I am not very familiar with sqlite.
In either case, it should be possible to reduce database size by changing the md5s table's path column to only specify the filename and saving non-favourite media to a group like "non-favourite" for simplicity. The directory path could be queried based on the value(s) of the new column. This would take slightly longer to query the full path, but I'm not sure if there are currently any circumstances where the full path would have to be queried. There is no need to do any of this right away, it's just an option to consider.

As previously discussed in Discord, these groups will be tentatively called "save groups" rather than "favourite groups". The plan to migrate existing users is to import the files they have already favourited, either automatically or with a utility, registering them to a save group called "favourites". I might try replacing the current (non-favourite) saving code with a save group called "default", but this could also be done later if it seems like it would require re-designing too much of the current code.


Illegal temperature value, exceeds 100.

Describe The Bug:
Illegal temperature value, exceeds 100.
To Reproduce:
Start HomeBridge
Expected behavior:
Temperature value within acceptable range
Logs:
[01/09/2021, 22:12:01] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.6809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:05] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.781 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:09] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:11] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:13] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:15] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.6809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:25] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.781 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:27] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:29] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:32] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:50] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:52] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:54] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.781 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:12:56] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:10] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.681 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:31] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:33] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.781 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:37] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:39] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:41] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.6809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:47] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:49] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:53] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:13:57] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:01] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:03] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:07] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:11] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:13] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:15] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:17] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:24] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:26] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:30] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:32] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:34] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:36] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:38] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:46] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:14:50] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:00] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:10] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:29] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:31] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:39] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7808 exceeded maximum of 100. See https://git.io/JtMGR for more info.
[01/09/2021, 22:15:41] [homebridge-plugin-govee] This plugin generated a warning from the characteristic 'Current Temperature': characteristic was supplied illegal value: number 839.7809 exceeded maximum of 100. See https://git.io/JtMGR for more info.

Plugin Config:
{
            "name": "Govee",
            "batteryThreshold": 25,
            "debug": false,
            "humidityOffset": 0,
            "platform": "GoveeHomebridgePlugin"
        },

Screenshots:

Environment:

Plugin Version: 1.1.2
Homebridge Version: 1.3.4
Node.js Version:  14.15.4
NPM Version:  6.14.11
Operating System: Raspbian

This looks like another instance https://github.com/asednev/homebridge-plugin-govee/issues/16


Telemetry: replace log4rs with tracing

Adds tracing, and sets it up to instrument the main process_slots function. Didn't do a deeper dive on it as we still have to settle on where do we want the logs to go and whatnot.
Closes #11.

@PJColombo should be ready too!

Let's go! :rocket:


not working with multiplatform desktop and/or material3

within the field formbuilderscope when adding TextField or Row/Column etc. my IDE shows me the following error: @Composable invocations can only happen from the context of a @Composable function

@tdascoli Thanks for submitting the issue
I'll check and get back to you as soon as I can!


Space world

New Area Suggestion
NOTE: If you wish to present more than one area in this suggestion write each one in a comment and use the following structure
What will this area look like?
The area would be like the moon (grayish with craters) and we would be able to see the other planets and stars when looking up.
What slimes will exist in this area?
Because this is a space world then we should have moon slimes, earth,mars,sun,star and meteorite slimes rock slimes to represent the moon effect and some pink slimes.
What foods will exist in this new area?
Dried cubberies, favorite of: earth slime and star slime
Alien hens, favorite of: sun slime and meteorite slime
Dried heart beets, favorite of: moon slime and mars slime
What is the reason for this area to exist?
This area exists to add more difficulty to the game and actually making the lab mecanism useful for other than crafting machines and drones.
How do you get to this area?
To get to this area you will have to craft some special extractors that extract petrolium or oil and some iron and with another machine that will be called a molder (you can change the name) that transform this iron into screws so with screws some more iron and the petrolium/oil you can craft a spaceship that will take you to the area.
Materials to be found (Optional)
Cooper and iron that could be sold in a new shop area where you can sell minerals you collect from the area and can also be used for some additional crafts.
Possible names for the area? (Optional)
Space world or outer space
Additional context
Add any other context or screenshots about the suggestion here.

Seeing as there is an entire chapter based on the moon I'm not sure you've read up on what's already planned. That being said. The moon is already fairly well thought out so I'm not sure if what you're suggesting is going to fit in. Especially when it's all fairly vanilla level gameplay.

Ric can correct me on this. But I'll wait and see what he says. Otherwise I'll close this.


Human now accepts Exception for anErrorOccurred.

This fixes #48

@rultor merge pls

@rultor merge pls

@aliceice OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge pls

@aliceice Done! FYI, the full log is here (took me 2min)


3.3 still plays adds and add some freezing feature too

after the 3.2 desaster and downgrading to  2.9.  i tried 3.3 today...
looked good at the start but then i had two times the youtube tab freez... and now... i see ADD spam!
win 11
firefox 115,6,0esr

Try Version 2.9. you will still get the please update me Promt from the script but no ads.

This was fixed in the latest version


Feedback component button/link alignment

"Page not useful" form button / link alignement is not the best on certain widths

it would be really beneficial to be able to add a class to the button component and add a 15px right margin.
below is with display:inline-flex on the link

Maybe just drop the link onto the line below regardless?

yeah i could make the breakpoint shift to desktop widths where there definitely is enough space for them to be side-by-side.
would be nice to use that space beforehand though.


False positive on json contains whitespace during signature

Version is 2.16.3 ran on LNX
Payload :
{"account_number":"53479","chain_id":"cosmoshub-4","fee":{"amount":[{"amount":"12807","denom":"uatom"}],"gas":"512272"},"memo":"Ledger Live","msgs":[{"type":"cosmos-sdk/MsgUndelegate","value":{"amount":{"amount":"107694","denom":"uatom"},"delegator_address":"cosmos14q7965clxk5vfuw232p3qdk8x5cg6mfhxd9yxe","validator_address":"cosmosvaloper1qdxmyqkvt8jsxpn5pp45a38ngs36mn2604cqk9"}}],"sequence":"16"}

Sent as
55020100fa7b226163636f756e745f6e756d626572223a223533343739222c22636861696e5f6964223a22636f736d6f736875622d34222c22666565223a7b22616d6f756e74223a5b7b22616d6f756e74223a223132383037222c2264656e6f6d223a227561746f6d227d5d2c22676173223a22353132323732227d2c226d656d6f223a224c6564676572204c697665222c226d736773223a5b7b2274797065223a22636f736d6f732d73646b2f4d7367556e64656c6567617465222c2276616c7565223a7b22616d6f756e74223a7b22616d6f756e74223a22313037363934222c2264656e6f6d223a227561746f6d227d2c2264656c656761746f725f61

and
5502020096646472657373223a22636f736d6f7331347137393635636c786b3576667577323332703371646b3878356367366d6668786439797865222c2276616c696461746f725f61646472657373223a22636f736d6f7376616c6f706572317164786d79716b7674386a7378706e35707034356133386e677333366d6e3236303463716b39227d7d5d2c2273657175656e6365223a223136227d

I'm expecting a signature back, but instead I have
4a534f4e20436f6e7461696e73207768697465737061636520696e2074686520636f727075736984

which seems to be DATA_INVALID with "JSON Contains whitespace in the corpus". The only whitespace I see in this payload is the one in the memo, and I don't think it should trigger the error. Is there something I'm missing ?

Pretty sure it was actually a Heisenbug. Thanks for your help on Slack :)


Update to 2.14.1

@conda-forge please rerender

@conda-forge-admin  please rerender

Hi! This is the friendly conda-forge automerge bot!
I considered the following status checks when analyzing this PR:

linter: passed
azure: passed

Thus the PR was passing and merged! Have a great day!


Possible major bug in evaluation

Hi @Spijkervet !
I played around with the pretrained Magnatagatune weights and discovered something. The predicted values were relatively low and I was wondering what's up.
Now I discovered, that in the evaluation.py in line 29 there is output = torch.nn.functional.softmax(output, dim=1). But, as far as I understand, the Magnatagatune (and the MSD dataset) are multi-label tasks - their loss functions are also the binary cross entropy in code. Hence, I suppose that instead of the softmax there should be a torch.sigmoid being used there.
Please let me know if I'm wrong, but as I see it now this could change the results of CLMR quite significantly (for the better), given that this code was used to generate the results.

Hi @NotNANtoN !
Thank you for your accurate observation. At some point, I changed the BCELoss to BCEWithLogitsLoss (removing an nn.Sigmoid() call) for the training scheme, but missed adding a sigmoid operation during evaluation. I will report back the results to you, thank you!

This changes results for a linear classifier from the reported:
ROC-AUC_tag = 88.49
PR-AUC_tag = 35.37
To:
ROC-AUC_tag = 88.73
PR-AUC_tag = 35.58

And it changes results for a 2-layer multi-layer perceptron from the reported:
ROC-AUC_tag = 89.3
PR-AUC_tag = 35.9
To:
ROC-AUC_tag = 89.3
PR-AUC_tag = 36.0
(the values obtained in recent commits are a bit lower because they indeed uses .softmax instead of .sigmoid for multi-label datasets)

Thanks again for your accurate observation! I hope our work has been useful to you :)


No virtual method getColor()

I'd like to report a bug that occured for Android 5 (motorola Moto X (1st Gen)) when using
setProgressColorResource

java.lang.NoSuchMethodError: No virtual method getColor(I)I in class Landroid/content/Context; or its super classes (declaration of 'android.content.Context' appears in /system/framework/framework.jar)
at com.github.guilhe.views.SeekBarRangedView.setProgressColorResource + 460(SeekBarRangedView.java:460)

Context.getColor(int) method is from SDK 23 so please switch to ContextCompat.getColor(this, colorId) :)

Hello Adam and thanks for you PR.
The idea is to keep at minimum the project dependencies, that's why I didn't import the support-compat in the first place.
In the code you can see that I have a comment and  @RequiresApi(api = Build.VERSION_CODES.M):
    /**
     * You can simulate the use of this method with by calling {@link #setProgressColor(int)} with ContextCompat:
     * setProgressColor(ContextCompat.getColor(resId));
     */
    @RequiresApi(api = Build.VERSION_CODES.M)
    public void setProgressColorResource(@ColorRes int resId) {
        setProgressColor(getContext().getColor(resId));
    }

If you're compiling for min API >= M you won't have a problem. Otherwise you should use setProgressColor(ContextCompat.getColor(resId).
Cheers.

When you look into the method definion you can see it, but compiler didn't highlight this usage with any warning/error though my min is 21 ;)
Yes, adding dependency would be maybe too much, libraries usually include some custom helper methods. Depends how you prefer :)
I already use setProgressColor() but had colleced some crashes.
Thx for the work anyway!

When you look into the method definion you can see it, but compiler didn't highlight this usage with any warning/error though my min is 21 ;)

Really? Now that's strange, I've added the annotation @RequiresApi(api = Build.VERSION_CODES.M) (M = 23) to prevent situations like these.

Thx for the work anyway!

Hey np, thanks for using it :)


Wrong message by CC after peer's registration

After peer's registration to bazaar CC shows me error

Everything is fine, just wrong message, cuz peer's registration was successfully

fixed on master.

fixed on prod.


Database, Engine and Table workings

contains:

FlatFile as first step to engine
Re-factorization of Table structure
Functionality to database
More Error Handling

The compiler warns about the following things in your module. Please remove all warnings:
src/storage/flatfile.rs:3:5: 3:12 warning: unused import, #[warn(unused_imports)] on by default
src/storage/flatfile.rs:3 use std::io;
                              ^~~~~~~
src/storage/flatfile.rs:4:28: 4:32 warning: unused import, #[warn(unused_imports)] on by default
src/storage/flatfile.rs:4 use std::fs::{ OpenOptions,File,create_dir };
                                                     ^~~~
src/storage/flatfile.rs:4:33: 4:43 warning: unused import, #[warn(unused_imports)] on by default
src/storage/flatfile.rs:4 use std::fs::{ OpenOptions,File,create_dir };
                                                          ^~~~~~~~~~
src/storage/flatfile.rs:24:32: 24:36 warning: unused variable: `cols`, #[warn(unused_variables)] on by default
src/storage/flatfile.rs:24     fn create_table(&mut self, cols: &[Column]) -> Result<(), DatabaseError> {
                                                          ^~~~
src/storage/flatfile.rs:25:13: 25:21 warning: unused variable: `file`, #[warn(unused_variables)] on by default
src/storage/flatfile.rs:25         let mut file = try!(OpenOptions::new()
                                       ^~~~~~~~
src/storage/flatfile.rs:25:13: 25:21 warning: variable does not need to be mutable, #[warn(unused_mut)] on by default
src/storage/flatfile.rs:25         let mut file = try!(OpenOptions::new()
                                       ^~~~~~~~
src/storage/mod.rs:9:5: 9:20 warning: unused import, #[warn(unused_imports)] on by default
src/storage/mod.rs:9 use std::path::Path;
                         ^~~~~~~~~~~~~~~
src/storage/mod.rs:10:21: 10:29 warning: unused import, #[warn(unused_imports)] on by default
src/storage/mod.rs:10 use std::fs::{self, DirEntry};
                                          ^~~~~~~~
src/storage/mod.rs:15:28: 15:32 warning: unused import, #[warn(unused_imports)] on by default
src/storage/mod.rs:15 use std::fs::{ OpenOptions,File,create_dir };
                                                 ^~~~
src/storage/mod.rs:84:1: 84:43 warning: enum is never used: `FileMode`, #[warn(dead_code)] on by default
src/storage/mod.rs:84 enum FileMode{ LoadDefault, SaveDefault, }
                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/storage/mod.rs:132:9: 132:18 warning: unused result which must be used, #[warn(unused_must_use)] on by default
src/storage/mod.rs:132         t.save();
                               ^~~~~~~~~
src/storage/mod.rs:218:37: 218:41 warning: unused variable: `name`, #[warn(unused_variables)] on by default
src/storage/mod.rs:218     pub fn remove_column(&mut self, name: &str, data_type: DataType) {
                                                           ^~~~
src/storage/mod.rs:218:49: 218:58 warning: unused variable: `data_type`, #[warn(unused_variables)] on by default
src/storage/mod.rs:218     pub fn remove_column(&mut self, name: &str, data_type: DataType) {
                                                                       ^~~~~~~~~

About the Database type. First of all: The method should not be named load_database and so on. You should always imagine the names in use. And one would use it like that: Database::load_database(). That isn't as nice as Database::load(), so just drop the _database from all names.
Furthermore: You use create_database just once in new_database... I doubt that create_database will be used somewhere else, so there is no point in putting the code into a seperate function. I would suggest: Rename load_database to load and merge new_database and create_database into create.

Currently the storage engine (engine_id) is always saved as a u8. Please change this to a StorageEngine enum with the attribute #[repr(u8)]. Such things should always be an enum.

You are serializing the whole Table type into the table file. We had worked out a TableMetaData type that contained just the data fields which should be written to file. Now name and name_of_database is also written into the file, which is unnecessary and even bad.


Browse the code and see if there are missings in the docs or code hard to read

One of the main desire of the lib is to have a clean code. That does not mean to respect the shortest algorithm, but to have the easiest to understand.
Also, each public fn / struct must be documented

Missing doc in the builders : ScionConfigBuilder, WindowConfigBuilder
Missing fields in the same builders
Missing doc in the mod.rs files
Missing doc in Collider.rs
The number of fields on Transform is too hight. Need to use more sub structs
Missing doc in Rectangle, Square, Triangle, Sprite, Tileset, Tilemap, UiImage, UiText, Color, Texture, Events, InputsController, Keyboard, PathBuilder, Dimensions
contents does not mean a lot in Sprite,
Each system should have a description to be more understandable.
scion2D needs a bit of rework to extract fn in dedicated files with explanation
shader pipeline should be crate visible


Gorilla websocket concurrency

Per docs,
Connections support one concurrent reader and one concurrent writer.
Applications are responsible for ensuring that no more than one goroutine calls the write methods (NextWriter, SetWriteDeadline, WriteMessage, WriteJSON) concurrently and that no more than one goroutine calls the read methods (NextReader, SetReadDeadline, ReadMessage, ReadJSON, SetPongHandler, SetPingHandler) concurrently.
The Close and WriteControl methods can be called concurrently with all other methods.
Need to setup a way to make sure this is done correctly in DiscrodGo

Below example of an error that may be received due to this not being done yet..

goroutine 39 [running]:
panic(0x438bf60, 0xc8208ee0b0)
    /usr/local/go/src/runtime/panic.go:464 +0x3e6
github.com/gorilla/websocket.(*Conn).flushFrame(0xc820a04600, 0x1, 0x0, 0x0, 0x0, 0x0, 0x0)
    /Users/username/Desktop/Workspaces/Go/src/github.com/gorilla/websocket/conn.go:450 +0x5ba
github.com/gorilla/websocket.messageWriter.Close(0xc820a04600, 0x1, 0x0, 0x0)
    /Users/username/Desktop/Workspaces/Go/src/github.com/gorilla/websocket/conn.go:579 +0xa4
github.com/gorilla/websocket.(*messageWriter).Close(0xc8208ee010, 0x0, 0x0)
    <autogenerated>:7 +0xa4
github.com/gorilla/websocket.(*Conn).WriteJSON(0xc820a04600, 0x443b720, 0xc8208ee000, 0x0, 0x0)
    /Users/username/Desktop/Workspaces/Go/src/github.com/gorilla/websocket/json.go:27 +0x156
github.com/bwmarrin/discordgo.(*Session).heartbeat(0xc8200601c0, 0xc820a04600, 0xc8207c8c00, 0xa122)
    /Users/username/Desktop/Workspaces/Go/src/github.com/bwmarrin/discordgo/wsapi.go:191 +0x158
created by github.com/bwmarrin/discordgo.(*Session).onReady
    /Users/username/Desktop/Workspaces/Go/src/github.com/bwmarrin/discordgo/discord.go:240 +0x55```


Unaccessible file mounts with VirtualBox

Another case related to access rights (Dinghy 4.5.0)

eval $(dinghy env)
export DINGHY_HOST_MOUNT_DIR=/Volumes/
export DINGHY_GUEST_MOUNT_DIR=/Volumes/

When I log in with dinghy ssh I find /Users/ElmarHinz mapped to root:root and those directories are mountable. /Volumes is mapped to the user 501:80 and is not mountable.

On my local machine both directories have the same user and group settings.
UPDATE: In another try /Users/ElmarHinz changed to  501:80, too, while I was browsing the directory.
My startup script:
https://github.com/elmar-hinz/TYPO3.docker-development/blob/master/run.sh
There is no error, but the directories are not mounted.  (The script works with docker-for-mac).
Possible solution
My other Vagrant based VirtualBox sets /Volumes/ to root:root  basically proving the issue is solvable.
    6             #################
    5             # NFS
    4             #################
    3             config.vm.synced_folder "#{mount['src']}",
    2                 "#{mount['target']}",
    1                 :nfs => { :mount_options => [ "dmode=775", "fmode=774" ] }

I don't know what it does different. Maybe it the trick to write to /etc/exports. Maybe the alldirs mapall parameters are OS X special. I don't find them documented for unfsd.
 # VAGRANT-BEGIN: 501 0e101423-03fe-4b72-98ad-b0745111e9d8
 "/Users/ElmarHinz" <IP_ADDRESS> -alldirs -mapall=501:20
 "/Volumes/Work" <IP_ADDRESS> -alldirs -mapall=501:20
 # VAGRANT-END: 501 0e101423-03fe-4b72-98ad-b0745111e9d8

(I did remove those lines and recreated dinghy to check troubles are not caused by them.)

When I log in with dinghy ssh I find /Users/ElmarHinz mapped to root:root and those directories are mountable. /Volumes is mapped to the user 501:80 and is not mountable

Right now Dinghy only supports NFS mounting one directory at a time, if you use DINGHY_HOST_MOUNT_DIR to change the mount dir to /Volumes that means /Users/ElmarHinz will no longer be NFS shared. Am I understanding correctly that is what is going on?
Also I suspect a problem here:
eval $(dinghy env)
export DINGHY_HOST_MOUNT_DIR=/Volumes/
export DINGHY_GUEST_MOUNT_DIR=/Volumes/

It looks like you're exporting those env vars after dinghy is already running, which means they aren't taking effect. dinghy up needs to see those env vars.

Hi, I'm closing this due to inactivity, please re-open if you'd like to continue digging into it.


Cartridge: reaction tests fail with psql 9.1

SET rdkit.ignore_reaction_agents=false;
ERROR:  unrecognized configuration parameter "rdkit.ignore_reaction_agents"
SET rdkit.agent_FP_bit_ratio=0.2;
ERROR:  unrecognized configuration parameter "rdkit.agent_fp_bit_ratio"
SET rdkit.difference_FP_weight_agents=1;
ERROR:  unrecognized configuration parameter "rdkit.difference_fp_weight_agents"
SET rdkit.difference_FP_weight_nonagents=10;
ERROR:  unrecognized configuration parameter "rdkit.difference_fp_weight_nonagents"
SET rdkit.move_unmmapped_reactants_to_agents=true;
ERROR:  unrecognized configuration parameter "rdkit.move_unmmapped_reactants_to_agents"
SET rdkit.threshold_unmapped_reactant_atoms=0.2;
ERROR:  unrecognized configuration parameter "rdkit.threshold_unmapped_reactant_atoms"
SET rdkit.init_reaction=true;
ERROR:  unrecognized configuration parameter "rdkit.init_reaction"

This has to do with the configuration variables not being available in 9.1 until a function from the extension is called.
It's not actually a problem (because the code is working), but I will still get the tests working.

Ok, now I'm hitting a different problem due to whitespace. I'll try to fix this either later tonight or tomorrow morning.

I think I have fixed issue #836 with the my last pull request. I fixed the failing test on Windows by adding a PGDLLEXPORT to _PG_init(), while I have added a cartridge function before any parameter is referenced to avoid errors on PostgreSQL 9.1.

"My last", not "the my last"


Make Blish portable by creating a Settings directory in path

Creating a 'Settings' directory in Blish will shift all settings to be defaulted to there instead of 'My Documents'.
This helps with easy portable deployment without using --setting parameter.
--settings is still honored if set as parameter.

Should we call the directory 'Settings' or 'Portable'?


Build error on v1.1.2 java.lang.reflect.InvocationTargetException

`
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':geolocation:kaptDebugKotlin'.

A failure occurred while executing org.jetbrains.kotlin.gradle.internal.KaptWithoutKotlincTask$KaptExecutionWorkAction
java.lang.reflect.InvocationTargetException (no error message)`

On Flutter 2.10.3
I've added all the proguard rules etc.

Did anyone ever find a solution/workaround for the above? I get the same error when trying to compile.


iPad: Multiple windows

I believe this is iOS 13, but I’d like to have NewsBlur open in multiple windows. (This is the feature where you tap on a iPad dock icon while the app is already open and it switches into the window switch dialog).
Is this feasible? Are there assumptions that the app makes that can’t be resolved with multiple windows? I feel like this would require those callback pointers that you pass between pages so you can context switch and not lose your place, but I don’t know that this is absolutely necessary. I just want multiple NewsBlur windows open side by side on different feeds. A callback pointer would be necessary if it was the same feed but at different pages, which we don’t need to support.

Yeah, that would be a nice enhancement. Anything is possible, but I haven't looked into it yet, so I'm not sure how difficult it'd be.  I expect that there are numerous assumptions of a single window that would have to be changed, but I can think of various ways of solving that. I'll investigate sometime.

Work on this (and much more) is underway; see #817 for more info.


Add a test for REST API, for existing "where ... $exists" behavior.

What this PR does:
Add one more IT for REST API (and extends another)
Which issue(s) this PR fixes:
Fixes #1517
Checklist

[ ] Changes manually tested
[x] Automated Tests added/updated
[ ] Documentation added/updated

Changed things a bit so that 2 tests (one unit test, one IT) actually verify the way Stargate v1 REST API (v2) actually works wrt "$EXISTS". Bigger contextual discussion on right/wrong behavior is at #1519 -- I suspect deprecation makes sense, but we still need to verify that existing behavior remains as-is.


Distance function

Similar to these:
https://pkg.go.dev/github.com/corona10/goimagehash#ImageHash.Distance
https://pkg.go.dev/github.com/Nr90/imgsim#Distance

Hey there ! Almost a year later, this is done, tested and released !


Using the store in router.beforeEach() breaks VueNavBar component Storybook

Describe the bug
Because the global CLIENT is undefined in store.ts, if the store gets imported indirectly by a story in Storybook, it will break Storybook with a rather cryptic error. I assume this is because Storybook is setting the "use strict" pragma somewhere.
The error looks like this:
index.js:16 ReferenceError: CLIENT is not defined
    at Module../src/app/store.ts (store.ts:12)
    at __webpack_require__ (bootstrap:764)
    at fn (bootstrap:127)
    at Module.<anonymous> (router.ts:1)
    at Module../src/app/router.ts (router.ts:47)
    at __webpack_require__ (bootstrap:764)
    at fn (bootstrap:127)
    at Module.<anonymous> (VueNavBar.stories.ts:1)
    at Module../src/app/shared/components/VueNavBar/VueNavBar.stories.ts (VueNavBar.stories.ts:14)
    at __webpack_require__ (bootstrap:764)

In my case, this was because the VueNavBar.stories.ts imports the router, which in turn was importing store.ts (to make use of a getter).
Fixing this means that adding authentication right after setting up the starter won't immediately break Storybook.
To Reproduce
Steps to reproduce the behavior (from a fresh install of vue-starter):

In router.ts make use of the story in any way, for example, by adding this line to the router.beforeEach() function:

router.beforeEach((to: Route, from: Route, next: any) => {
+  var mycount = store.getters.counter;
   if (to.matched.some((record: RouteRecord) => record.meta.requiresAuth)) {

Run npm run storybook
Open http://localhost:6006/
See error

Expected behavior
Setting up navigation guards that use store getters to check state should not cause Storybook to break.
Screenshots

Desktop:

OS: MacOS
Browser: Chrome
Version: 68

Smartphone (please complete the following information):
Not tested
Additional context
Add any other context about the problem here.

I wouldn't suggest accessing the store inside a shared component. That is against the concept of having decoupled, reusable components.
Try to always pass down this values as a prop 👍

In this case, the component isn't accessing the store, but the story is importing the router (in order to pass it to the component), which in turn imports the store.
Is there a better way to reference the store in the router, without importing it directly?

ok, I understand. I'll try to come up with a solution 👍

I found a way to mock the router for storybook: https://github.com/devCrossNet/vue-starter/pull/234/files#diff-67a42cc74b668d1e7710029c548f276c
I'll try to reproduce your example and mock the router, if this works I'll close this issue.

The mocking of the router in stories solves this issue.


volume mode change, two volume read/write read/only mode

support
Signed-off-by: kevin xu<EMAIL_ADDRESS>

Codecov Report

Merging #418 into master will increase coverage by 0.27%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #418      +/-   ##
==========================================
+ Coverage   41.48%   41.75%   +0.27%
==========================================
  Files          22       22
  Lines       11091    11091
==========================================
+ Hits         4601     4631      +30
+ Misses       5302     5268      -34
- Partials     1188     1192       +4

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 99dc1bf...334192d. Read the comment docs.


⚠ Bofrost.fr has degraded performance

In 04ad5f8, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 893 ms

Resolved: Bofrost.fr performance has improved in 1e8f4f0.


Add support for pip install -e

Allow shutil to follow symlinks through copytree.

Condor doesn't follow symlinks though?
Or at least that was the case in
https://github.com/CoffeaTeam/lpcjobqueue/blob/fa5d0a110663769f1898e295cb81aafb3ed37c1c/bootstrap.sh#L23

Can you confirm that this worked? Because at least at one point it didn't appear that HTCondor would copy the symlink in transfer_input_files

No - you're right it does not. Only real directories function here.

Closing for now. It would be a nice feature but I suppose it requires some refactor. Perhaps zipping the environment and then using the job_script_prologue to unzip on the worker would work well enough?


One error should be solved and one improvement for reducing the CUDA memory

1.One error should be solved
when install apex, there will be 4 erors about "convert unsigned long to long", you need to edit:
(1) line 65 in apex_22.01_pp/csrc/mlp.cpp
    auto reserved_space = at::empty({reserved_size}, inputs[0].type());
change to:
    auto reserved_space = at::empty({static_cast<long>(reserved_size)}, inputs[0].type());
(2) line 138 in apex_22.01_pp/csrc/mlp.cpp
    auto work_space = at::empty({work_size / sizeof(scalar_t)}, inputs[0].type());
change to:
    auto work_space = at::empty({static_cast<long>(work_size / sizeof(scalar_t))}, inputs[0].type());
or you need to change the compile option
2.one improvement for reducing the CUDA memory
when launch the owl_demo.py using a GPU with 16G, I ran into a CUDA memory overflow error. Then I edit here:
line 33 and 34 in interface.py:
    model = model.to(device)
    model = model.to(dtype)

change to:
    model = model.to(dtype)
    model = model.to(device)

Then, After the demo is started, the memory usage is about 14 GB. It can run very well on a 16GB GPU.

Just a reminder. My env is V100, gcc-7, cuda11.7, python3.10

Nice work!


Emitting code with declaration compiler option undesirably reduces keyof into string literal type instead of preserving origin type

Bug Report
Emitting code with declaration compiler option undesirably reduces keyof into string literal type instead of preserving original type
🔎 Search Terms
typescript, compiler options, declaration, minify, string literal type
🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about type minifications in type declarations files.

⏯ Playground Link
Playground link with relevant code
💻 Code
export type SomeAction = {
  id: string,
}

export interface AllActions {
  Some: SomeAction,
}

export type Type = keyof AllActions

export const foo = <TYPE extends Type>(type: TYPE): void => {
}

🙁 Actual behavior
produces declaration file (*.d.ts). See extends part, where "Some" is instead of Type.
export declare type SomeAction = {
    id: string;
};
export interface AllActions {
    Some: SomeAction;
}
export declare type Type = keyof AllActions;
export declare const foo: <TYPE extends "Some">(type: TYPE) => void;

🙂 Expected behavior
export declare type SomeAction = {
    id: string;
};
export interface AllActions {
    Some: SomeAction;
}
export declare type Type = keyof AllActions;
export declare const foo: <TYPE extends Type>(type: TYPE) => void;

what causes problems if we are extending the AllActions interface later in the application by module augmentation.

Duplicate of #27171. Used search terms: emit keyof string in:title

@MartinJohns thx a lot, according to the discussion I was able to workaround the issue with function notation
export function foo <TYPE extends Type>(type: TYPE): void {
}


Fix #97526

This PR fixes #97526

@jrieken why it isn't merged yet?

I tested it in different cases including the case from #97526. And it works perfectly


Mod conflicts with ProtocolSupport

This mod pretty much makes ProtocolSupport useless. As explained in the issue here: https://github.com/ProtocolSupport/ProtocolSupport/issues/1024
When you have this mod on your client you cannot render any of the blocks on the server that has protocol support.
Protocol Support allows you to connect to a latest 1.13.2 server using older protocols down to 1.4.7. Allowing bungeecord networks to simply have 1 HUB/Vanilla server instead of multiple for every minecraft version.
I am using this on my 1.7.10 Modpack.
Is there any way you could add support for this plugin?

1.7.10 Isn't supported anymore. Sorry for that =(

Seriously? Why? It is the most used and developed for version of minecraft.
https://bot.notenoughmods.com/
Over 1200 mods made for 1.7.10 compared to a couple hundred for other versions.
This is a very serious issue, cant you make a one time patch to fix this?
@fewizz

Ok, ill try ❤

Thank you.

works 🤔

With protocol support on a large modpack?
Ive tested it with and without NotEnoughItems it most certainly does not work.
It looks like this on the vanilla server:

And like this on the modpack server:

I used a modified protocolsupport plugin.  :D
Thank you so much, might i ask why the jar is so bulky now? went from 7MB to 25MB thats a pretty big jump.
And could you do a merge request to the ProtocolSupport github in hopes this will be supported in future versions?

It doesnt work on vanilla now tho :(
Is there no way to work for both vanilla and modded?

I can do that, but not today. =P

Awesome, let me know when you got another version to test :)

https://drive.google.com/file/d/1GrAisxWCaqXo16nCe8RT_mV0HlRJvxH_/view?usp=sharing

Issue discussed & fixed on discord. Thank you <3!


Catch IOException parsing manifest

Description of Change
Catch and log IOException when parsing manifest for two reasons:

To prevent an ExceptionCollection exception being thrown by engine.analyzeDependencies() when analyzing unreadable jars/zips. This is useful because these errors could be common (x) and unnecessarily bloat any ExceptionCollection. Also it would make it easier to determine whether to continue or not especially for external uses of engine.analyzeDependencies().

(x) when compressing files on macOS it may create mirror ._ files (same filename except with the ._ prefix), these files aren't actual copies they just contain file information, but if engine.analyzeDependencies()  sees ._some_file.jar it will fail to parse its manifest throwing an IOException because it's unreadable.

To be consistent with other usages of try (JarFile jar = new JarFile(dependency.getActualFilePath()))

https://github.com/jeremylong/DependencyCheck/blob/fb2b3159e8dedaad06cb3b6f667975616fbd848f/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/JarAnalyzer.java#L313
https://github.com/jeremylong/DependencyCheck/blob/fb2b3159e8dedaad06cb3b6f667975616fbd848f/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/JarAnalyzer.java#L914
Edit: this has since been updated to incorporate suggestions - see https://github.com/jeremylong/DependencyCheck/pull/848#issuecomment-323534760
https://github.com/jeremylong/DependencyCheck/pull/848#issuecomment-323737697
Have test cases been added to cover the new functionality?
yes

Can one of the admins verify this patch?

Completely understand the reason why you would want this. However, instead of just removing the exception it would be better to see if the file name, in this case ._some.jar, starts with a ._ and if the dependency collection contains a some.jar - if that is the case skip and remove the ._some.jar.  Another option, if we run into ._some.jar and the magic bytes don't match a zip - skip and remove it?  Thoughts?

Completely understand the reason why you would want this. However, instead of just removing the exception it would be better to see if the file name, in this case ._some.jar, starts with a ._ and if the dependency collection contains a some.jar - if that is the case skip and remove the ._some.jar. Another option, if we run into ._some.jar and the magic bytes don't match a zip - skip and remove it? Thoughts?

These both sound like good ideas, I've made some changes in 5d87dc2 to reflect this. Note especially the early return at https://github.com/mealingr/DependencyCheck/blob/5d87dc2942c9319eca3533d8a7b54a84be411d2d/dependency-check-core/src/main/java/org/owasp/dependencycheck/analyzer/JarAnalyzer.java#L255
which allows the AnalysisException to be avoided. Is there a reason it wasn't returning early before? If so maybe the early return should be restricted to just when the macOS metadata files or non-zip files are encountered.

Thanks for the PR and the quick response to the requested changes! I will be pushing a new release today or tomorrow.


Add support for @Past bean validation annotation

🆕🐥:dog: First Timers Only
This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
:space_invader: Description of the issue
Currently the dolphin-platform-bean-validation module do not provide support for all default bean validation annotations. One that is missing is the @Past annotation. For solving this issue the support for the @Past annotation must be added like it is done for several other bean validation annotations in the dolphin-platform-bean-validation module and at least one unit test must check that the annotation is supported.
📋 Step by Step

🙋 Claim this issue: Comment below.
🔄 replace the up for grabs label with in progress.
:fork_and_knife: fork the repository in github by simply clicking the 'fork' button.
:arrow_heading_down: check out the forked repository
:twisted_rightwards_arrows: create a feature branch for the issue. We do not have any naming definition for branches.
💾 Commit your changes.
🔀 Start a Pull Request.
🏁 Done 👍 Ask in comments for a review :)
🔬 If the reviewer find some missing peaces or a problem he will start a discussion with you and describe the next steps how the problem can be solved.
:boom: you did it! We will merge the fix in the master of the Dolphin Platform project.
:bouquet: Thanks, thanks, thanks for being part as an open source contributor for Dolphin Platform

🤔❓ Questions
You can join our community chat at Slack

Aaaand I'll try to implement this as well.

@Ampretuzo ok, do you have knowledge in java bean validation? Do you want to do all 3 issues in one PR?

I'm not exactly an expert, but I've seen the code and it does not seem to be too difficult. If I'm mistaken correct me :)
If I'll encounter some difficulties I'll keep you posted.
Yes, one PR.

ok :)

Henrik, I implemented and tested this one with unit test, but I had to work around abstract validator.
It does not integrate with JSR-303 well and requires further type checkings in its implementations when multiple types need to be supported (in this case it is Date and Calendar classes).
There are two ways to do this task: (i) write with work arounds quickly to get things done, or (ii)  modify/change abstract validator class to comply with JSR nicely. I'll do (i) first, not to mess things up and only afterwards an issue should be made to fundamentally improve abstract validator.
I really need to sleep right now so I'll finish other two issues (#657, #655) tomorrow :)

Using the abstract class is not a must :) I think your idea sounds good 👍


Empty "From" in test mail

Version: <IP_ADDRESS>8
Config (Notification section):
{
  "SmtpServer": "smtp.XXXX.yy",
  "SmtpPort": 587,
  "SmtpUser"<EMAIL_ADDRESS>  "SmtpPassword": "XXXXXXXXXXXXXXX",
  "SmtpSecure": true,
  "SmtpSecureMode": 1,
  "SenderName": null,
  "SenderAddress"<EMAIL_ADDRESS>  "ReceiverAddresses": [<EMAIL_ADDRESS>],
  "EmailOnSuccess": true
}

Received mail:
Return-Path<EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: from [IPv6:XXXX] (pc.XXXX.yy [XXXX]) by server.XXXX.yy
 with ESMTPSA (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256)
 ; Sun, 29 Mar 2020 14:33:12 +0200
X-AuthUser<EMAIL_ADDRESS>From:
Date: Sun, 29 Mar 2020 14:33:11 +0200
Subject: Test notification
Message-Id: <2ZT5YJQE8AU4.42Y80E10AABO2@XXXX-PC>
Sender: win-acme<EMAIL_ADDRESS>To<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Id: <NC1CYJQE8AU4.MM3UTC3T4UQK2@XXXX-PC>

If you are reading this, it means you will receive notifications about critical errors in the future.

Sent by win-acme version <IP_ADDRESS>8 from XXXX-PC

As you can see, the "From" header is empty.

Even though none is explicitly set from the program, my own tests show a From header in the emails. I guess some mail servers fill in the blank value based on either the Sender information and/or the account used to send the message. It's also difficult to guess what the impact of this problem is, I guess it also depends on the client and how it handles this.
In any case if you are impacted by this issue you can get a new build here:
https://ci.appveyor.com/project/WouterTinus/win-acme-s8t9q/builds/31800016/artifacts

That's a good theory. I don't think my mailserver (hMailServer) is that clever to fix the missing From header.
I've tested the build and now the mail looks the same again like in version <IP_ADDRESS>2. Thanks!


Test feature flag combinations in CI

Motivation
Once #1192 merges, Mio will have several feature flags that can be used in different combinations of each other. CI should test that the combinations are correct. Currently, it would just test --all-features.
Solutions

I've been using cargo-hack's --feature-powerset. Cons: It's a little expensive to run right now because it mixes in guide doubling the number of combinations that needs to be tested. CI could download cargo hack and run it in place of cargo check steps.

Explicitly test the combinations we care about. Cons: A combination could be missed, and it would need to be updated as features are added (probably not that often..)

Little script to run the current combos locally:
#!/bin/bash

set -eu

declare -a feature_matrix=(
	"" # None.
	os-poll
	os-poll,os-util
	os-poll,os-util,tcp
	os-poll,os-util,tcp,udp
	os-poll,os-util,tcp,udp,uds
	os-util
	os-util,tcp
	os-util,tcp,udp
	os-util,tcp,udp,uds
	tcp
	tcp,udp
	tcp,udp,uds
	udp
	udp,uds
	uds
	guide
)

for features in "${feature_matrix[@]}"; do
	cargo check --features "$features"
done