Empire doesn't run : 'NoneType' object has no attribute 'getitem'

root@kaliTesting:/# apt-cache show python | grep "Version" Version: 2.7.13-2 Version: 2.7.9-1 root@kaliTesting:/# apt-cache show empire | grep "Version" Version: 1.14-1 Version: 1.12-1 root@kaliTesting:/# uname -r 4.9.0-kali1-amd64
I downloaded the latest version of Empire-master and i installed it by run ./setup/install.sh
But i saw an error here :
root@kaliTesting:~/Téléchargements/Empire-master# ./setup/install.sh
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
libssl-dev is already the newest version (1.1.0c-2).
python-dev is already the newest version (2.7.13-2).
python-m2crypto is already the newest version (0.24.0-1).
python-pip is already the newest version (9.0.1-2).
swig is already the newest version (3.0.10-1.1).
0 mis à jour, 0 nouvellement installés, 0 à enlever et 95 non mis à jour.
Requirement already satisfied: pycrypto in /usr/lib/python2.7/dist-packages
Requirement already satisfied: iptools in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: pydispatcher in /usr/local/lib/python2.7/dist-packages
Requirement already satisfied: flask in /usr/lib/python2.7/dist-packages
Requirement already satisfied: pyOpenSSL in /usr/lib/python2.7/dist-packages

 [>] Enter server negotiation password, enter for random generation: anything
Traceback (most recent call last):
  File "./setup_database.py", line 128, in <module>
    )''')
sqlite3.OperationalError: table config already exists

 [*] Certificate written to ../data/empire.pem

 [*] Setup complete!

And when i launch it it give me this error :
root@kaliTesting:~/Téléchargements/Empire-master# ./empire Traceback (most recent call last):   File "./empire", line 10, in <module>     from lib.common import empire   File "/root/Téléchargements/Empire-master/lib/common/empire.py", line 31, in <module>     import agents   File "/root/Téléchargements/Empire-master/lib/common/agents.py", line 22, in <module>     import http   File "/root/Téléchargements/Empire-master/lib/common/http.py", line 67, in <module>     class RequestHandler(BaseHTTPRequestHandler):   File "/root/Téléchargements/Empire-master/lib/common/http.py", line 73, in RequestHandler     serverVersion = helpers.get_config('server_version')[0] TypeError: 'NoneType' object has no attribute '__getitem__'
Thanks you very much for your help !

Can you please use the reset script and report back?

thanks for your reply :`root@kaliTesting:~/Téléchargements/Empire-master/setup# ./reset.sh
[>] Enter server negotiation password, enter for random generation: anything
Traceback (most recent call last):
File "./setup_database.py", line 131, in
c.execute("INSERT INTO config VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)", (STAGING_KEY,STAGE0_URI,STAGE1_URI,STAGE2_URI,DEFAULT_DELAY,DEFAULT_JITTER,DEFAULT_PROFILE,DEFAULT_CERT_PATH,DEFAULT_PORT,INSTALL_PATH,SERVER_VERSION,IP_WHITELIST,IP_BLACKLIST, DEFAULT_LOST_LIMIT, "", "", API_USERNAME, API_PASSWORD, "", API_PERMANENT_TOKEN))
sqlite3.ProgrammingError: You must not use 8-bit bytestrings unless you use a text_factory that can interpret 8-bit bytestrings (like text_factory = str). It is highly recommended that you instead just switch your application to Unicode strings.
Traceback (most recent call last):
File "./empire", line 10, in
from lib.common import empire
File "/root/Téléchargements/Empire-master/lib/common/empire.py", line 31, in
import agents
File "/root/Téléchargements/Empire-master/lib/common/agents.py", line 22, in
import http
File "/root/Téléchargements/Empire-master/lib/common/http.py", line 67, in
class RequestHandler(BaseHTTPRequestHandler):
File "/root/Téléchargements/Empire-master/lib/common/http.py", line 73, in RequestHandler
serverVersion = helpers.get_config('server_version')[0]
TypeError: 'NoneType' object has no attribute 'getitem'
`

Ok i resolve the problem by adding conn.text_factory = lambda x: unicode(x, "utf-8", "ignore") after the line 100
Thanks you anyway killswitch-GUI :+1:

was this a lang issues @Martou1 ?

I figured that much

I don't know...i work on french OS effectively...
But why did you say that ? Anything in relation with the lang can cause this issue ?


Create a parent mixin class for AnalogSignal and IrregularlySampleSignal

There is a lot of repeated code in many of the methods of AnalogSignal and IrregularlySampleSignal. This should be moved to a mixin class that can be a parent of both classes.

as @JuliaSprenger suggested in the discussion on #382, we should also harmonize the unit tests, and develop a suite of tests common to both classes.

This is almost complete, but the common implementation of merge() wasn't working for IrregularlySampledSignal, so I had to re-add a sub-class-specific merge() implementation.


The README file in this repo has a bad link - [404:NotFound]

The README file in this repo has a bad link - [404:NotFound]
Status code [404:NotFound] - Link: https://github.com/microsoft/PowerToys/releases/tag/v0.24.0-Experimental
This was found by an new experimental hobby project that I have just created: https://github.com/MrCull/GitHub-Repo-ReadMe-Dead-Link-Finder
If this has been in any way helpful then please consider giving the above Repo a Star.

Removing the "-experimental" part does the trick. I think it's because the update mechanism had trouble with this extra bit.

fixed, good catch


No programmatic support for rule "enabled "attribute

As per the description of #4101, this package does not surface the enabled attribute on rules via the LoggingRule class. This attribute is defined in the official XSD at https://nlog-project.org/schemas/NLog.xsd:
<xs:attribute name="enabled" type="xs:boolean" default="true">
  <xs:annotation>
    <xs:documentation>Enable this rule. Note: disabled rules aren't available from the API.</xs:documentation>
  </xs:annotation>
</xs:attribute>

It appears that the comment "disabled rules aren't available from the API" is correct, as calling LogManager.Configuration.FindRuleByName("myDisabledRuleName") returns null. Why is this?
The current way this is setup means I cannot define a rule as disabled in my configuration file, then load and tweak it at runtime, and finally enable it.
NLog version: 4.7.5
Platform: .NET Core 3
Current NLog config
(using https://github.com/NLog/NLog.Extensions.Logging to define logging config in appsettings.json)
    "NLog": {
        "targets": {
            "ErrorFileTarget": {
                "type": "File",
                "layout": "${longdate} | [${threadid}] | ${callsite} | ${message}",
                "fileName": "${basedir}/Logs/${date:format=yyyyMMdd_HH00}.log"
            },
            "logFileTarget": {
                "type": "File",
                "layout": "${longdate} | [${threadid}] | ${callsite} | ${message}",
                "fileName": "/Logs/${date:format=yyyyMMdd_HH00}.log"
            }
        },
        "rules": [
            {
                "ruleName": "ErrorFileRule",
                "minLevel": "Error",
                "maxLevel": "Fatal",
                "writeTo": "ErrorFileTarget"
            },
            {
                "ruleName": "logFileRule",
                "minLevel": "Trace",
                "maxLevel": "Fatal",
                "writeTo": "logFileTarget",
                "enabled": false
            }
        ]
    }

What is the current result? N/A
What is the expected result? N/A
Did you checked the Internal log? N/A
Please post full exception details (message, stacktrace, inner exceptions) N/A
Are there any workarounds? No
Is there a version in which it did work? N/A
Can you help us by writing an unit test? N/A

Did a bit of digging and found https://github.com/NLog/NLog/blob/dev/src/NLog/Config/LoggingConfigurationParser.cs#L636 when parsing rules:
            if (!enabled)
            {
                InternalLogger.Debug("Logging rule {0} with filter `{1}` is disabled", ruleName, namePattern);
                return null;
            }

Why not still add the rule, but as enabled = false? What harm would it cause?

enabled came first, and allowed one to use NLog-Config-Variables to control the enabled-flag for all relevant LoggingRules.
ruleName was introduced much later, to make it easier to lookup and adjust an existing logging-rule. So the use-case of performing lookup of disabled logging-rules never existed until then.

Why not still add the rule, but as enabled = false? What harm would that cause?

Could the same not be implemented like this:
            {
                "logger": "*",
                "ruleName": "logFileRule",
                "level": "Off",
                "writeTo": "logFileTarget",
            }

Alternative you can dynamically control the level-filter: https://github.com/NLog/NLog/wiki/Filtering-log-messages#semi-dynamic-routing-rules

So the use-case of performing lookup of disabled logging-rules never existed until then.

Fair enough, but I have that use-case now, so is there any good reason not to support it?

Could the same not be implemented like this:

Yes, in that it has the same practical effect.
No, in that it has a different semantic meaning:

level: Off means I still want the rule to be evaluated and executed, it will just do nothing if it is hit
enabled: false means I want the rule to be ignored entirely, i.e. it will exists but not be evaluated or executed at all

No, in that it has a different semantic meaning:

Well that is exactly how NLog works right now. Enabled = false means it is thrown away and never evaluated again (ignored entirely). level: Off means that it sticks around, and can be adjusted to actually redirect logevents to configured target(s).
Anyway breaking change to suddenly having disabled logging-rules dangling. You are welcome to create a pull-request for NLog 5, and if it source-code is elegant and it is not hurting performance to have 1000 dangling logging-rules, then it will probably be accepted.

Anyway breaking change to suddenly having disabled logging-rules dangling. You are welcome to create a pull-request for NLog 5, and if it source-code is elegant and it is not hurting performance to have 1000 dangling logging-rules, then it will probably be accepted.

Thank you, that's the kind of feedback I was hoping for. Would you be open to adding a top-level configuration option to control the behaviour around disabled rules? Something like a boolean called loadDisabledRules:

If not present or set to false (default), NLog functions as currently: rules marked as enabled: false are effectively ignored at runtime.
If present and set to true, NLog will load all rules, even those marked as enabled: false, but disabled rules won't be evaluated.

The Enabled boolean property can then be added to LoggingRule and will behave as follows:

If loadDisabledRules is not present or set to false, attempting to get/set LoggingRule.Enabled will throw an InvalidOperationException informing the caller that what they're doing will have no effect.
If loadDisabledRules is present and set to true, get/set of LoggingRule.Enabled will work as expected.

The implementation of LoggingRule.Enabled behaviour is up for debate. I'm not sure how NLog works internally, but my guess would be that it effectively uses a single IEnumerable<LoggingRule> which is iterated when evaluating rules. The simplest (but not necessarily most performant) change is therefore to alter that iteration to skip rules that have Enabled = false via a simple if or predicate. Alternatively we could have two lists, one for the enabled and the other for the disabled rules, and only iterate the former when evaluating rules - that however makes things more difficult in the case that we want to iterate all rules, e.g. FindRuleByName.
As all of the above is new, current code using NLog will continue to function as normal, without the potential penalty of many disabled rules. Anyone who wants the ability to manipulate disabled rules, and/or enable or disable rules at runtime, needs to opt-in to this new functionality via setting loadDisabledRules: true. LoggingRule.Enabled similarly does not yet exist and current code will not break if that property is added.

option to control the behaviour around disabled rules? Something like a boolean called loadDisabledRules:

Sounds a little convolutted. Just make sure that performance is good. Prefer to have good default behavior without special options. Special options leads to frozen code (code only executed once a year) and fear of change.

Closing as inactive

Man this bites me today... I have a rule for a console logger that by nlog.config is enabled=false but added some code tied to pressing L key to gradually increase the console logging from "enabled=false" -> loglevel.info -> loglevel.debug -> "enabled=false"
Was disappointed to find out the rule is never added to configuration for manipulating via code.
I will look and see if the pull request was ever started.

Instead of using enabled="false" then one could just use  minLevel="Off".
See also: https://github.com/NLog/NLog/wiki/Filtering-log-messages#semi-dynamic-routing-rules
See also: #4948


116 dependent

Adds the ability to select which plots will be shown
Click the button on the middle right, below the reset zoom (home button)

Select which traces you want to see:

Press OK:

Will implement  ALL or NONE for asssiting in selecting on large datasets. For now buttons are disabled
@DanielSank @jwenner @maffoo

While I'd like to be able to test this, all the computers I have access to are Windows computers. Could you please do a setup on a Linux computer? (Either that or I can't test this). Note I'd like to see how the selection menu handles long lists of dependent variables (see any of the DAC ScanPhases datasets for instance - example either at ['','Test','GHzFPGA','Ivan DAC 59','151030','0_0',3] or see Austin for a dataset at Google). I'd also like to see what you do in the case of a 2D dataset, where the menu icon is already used for "draw with vargrid"
But overall, I like the idea as seen in the photos you provided. Don't know enough to comment on the code, though.

Thanks for taking a look Jim. I don't know how to deploy this branch on Matrix-reloaded for testing so I'll wait until this gets through review. If you have any suggestions from what you can see of the GUI in the screenshots, let me know

@joshmutus, could you please post screenshots of the following:

What happens to the menu when there's a lot of dependent variables. See the GHzDAC ScanPhases I mentioned above for examples.
What happens to the buttons in the case of a 2D dataset? Example: ['','Jim','AliceBobRes','Cooldown160406','160503','7-T1 Stability'].
What is the text which appears when you hover the mouse over the button?
What happens when the label of the traces does not match that of the first trace? For the example you showed, what happens to the y-axis label if you selected traces 1 and 3 (i.e., the two phases)?

What happens to the menu when there's a lot of dependent variables. See the GHzDAC ScanPhases >I mentioned above for examples.

I hadn't thought of this. I'll make a it a scrollable dialog so they'll all show up.

What happens to the buttons in the case of a 2D dataset? Example:
['','Jim','AliceBobRes','Cooldown160406','160503','7-T1 Stability'].

Nothing. Not implemented yet.

What is the text which appears when you hover the mouse over the button?

"select trace"

What happens when the label of the traces does not match that of the first trace? For the example you > showed, what happens to the y-axis label if you selected traces 1 and 3 (i.e., the two phases)?

Good catch. Not the correct thing. I'll fix that.

@jwenner So I've changed the behavior for the axis label for selecting traces.
If you have multiple traces with multiple labels and units, the axis label will take on the value of the lowest order of the selected trace.
For example if I have
1 - magnitude
2 - phase
3 - magnitude
4 - phase
and I select traces 2 and 4, the label will show phase (with the legend and units fields filled in)
If I select traces 1 and 3 it will label magnitude.
If I select traces 3 and 4 it will label magnitude
If I select traces 2 and 3 it will label phase
I worry displaying lots of axis labels will get cluttered, so I'm just displaying one right now. Is that behavior good for now?

Seems reasonable to me. I think this is akin to what the old Delphi grapher does (but I don't know the particular ordering that it uses). But you should definitely leave a comment in the code to this effect.
Long term, I don't know what a good solution is. One conceivable idea is to only plot traces with the same label as the first selected trace? Or to show all labels but color-coded? Or something else? Maybe @DanielSank or @maffoo has an idea.
But as for now, I think that what you propose for the axis label should work.

Also, just fixed the dialog so it will be scrollable for lots of dependents. I don't have a dataset locally with very many dependents, so I can't post a nice screenshot, but it works if I scrunch the screen up to be super duper small :)

Since at least Austin has done the DAC ScanPhases script at Google, you all probably have a dataset with lots of dependents there. Typical location is something like ['','Test','GHzDAC', boardName,...].

I actually have no idea how to deploy on that machine either :(

Plot limits now change with selected traces:
All Traces

Phase:

Mag:

Thanks for the UI feedback @jwenner ! Very handy peer review even without knowing the code.

From what you've said and the screenshots you've posted, a provisional LGTM (provisional based on not having tried it myself and not knowing the code). Although, we should either not close #116 or raise a new issue until this is made available in the 2D scan case as well.

Thinking about it, one additional idea. On the "Select Traces" menu, would it be good to show both the label and legend (so "Magnitude S11" instead of "Magnitude")?

Sure that's easy to add

added the thing.
I don't really feel comfortable merging before someone takes a look at the code. Also, even if it gets merged I don't know how to deploy to matrix-reloaded.
@DanielSank @ejeffrey do you know how to build and deploy on matrix reloaded?

See my comments above about the ALL and NONE buttons. Don't know why they show up as outdated diffs...

@joshmutus off the top of my head, I do not.

2D datasets are now selectable using some radio buttons:

There's a small but in the rendering of that dialog, but once this bit gets reviews I think it's safe to close that issue.
A nice feature to add would be if selecting traces updated the URL and if traces could be selected via URL. This can be done in principle by setting this.displayTraces array from the URL

Still the same provisional LGTM (provisional based on not having tried it myself and not knowing the code).

Thanks Jim. I want to get @maffoo's take on this. This waited 6mo, it can wait another week, I think.

I have a few comments about the code but mostly this looks good. However, it doesn't actually work for me. After I select some traces the displayTraces array is a bunch of NaNs, so the plotting fails. Haven't tracked down the problem, but this will all work differently after changing the submitTraces to not use form serialization anyway, so I didn't look too hard. I agree it would be nice to make it possible to reflect these kind of changes in the url so that it can be shared, but I think that could happen in a separate PR.

Thanks for the comments. I'll get to those right away.
I'll change the serialization and push that and see if your problem persists. Did you try plotting different 2D datasets?

I only tried with 1D datasets so far, then ran into the problem.

@maffoo can you take a look when you get a chance. I just fixed the way the checkboxes are read. It should log what traces are selected and which are added to this.displayTraces let me know if it works now.

@joshmutus, works, though I get a typescript compiler error on lines 611 and 612. I think you need to cast to the appropriate element type:
if ((<HTMLInputElement>checkbox).checked) {
  selected.push((<HTMLInputElement>checkbox).dataIndex);
}

BTW, I wish there were a better way to do that...

Cool. I noticed the errors, just wanted to make sure it's functional.
On Mon, May 16, 2016, 11:25 AM Matthew Neeley<EMAIL_ADDRESS>wrote:

BTW, I wish there were a better way to do that...
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/labrad/scalabrad-web/pull/176#issuecomment-219504513

Pushed to the branch addressing most of the comments. I'm having trouble casting the radio button types:
app/elements/labrad-plot.ts(617,56): error TS2339: Property 'dataIndex' does not exist on type 'HTMLElement'.
app/elements/labrad-plot.ts(623,58): error TS2339: Property 'selected' does not exist on type 'HTMLElement'.

AFAICT there are no HTMLElements with the properties selected or dataIndex, those come from IronSelectableBehavior, which isn't included in the polymer-ts typings. Should I just make that typing manually? Where do I put it?

So I just renamed  tab-index because it exists on <HTMLInputElement> and is of the correct type. Is that reasonable?

I don't think you want to use tab-index to just store some data, since that is meant for controlling tabbing in the UI. It worked fine for me to use dataIndex and checked with a cast to <HTMLInputElement> as in the snippet I posted earlier.

@maffoo
Data Index doesn't work for me on `` ```
app/elements/labrad-plot.ts(617,56): error TS2339: Property 'dataIndex' does not exist on type 'HTMLInputElement'.

So, this quiets the compiler and allows me to create my own custom properties:
I made a new class:
class CustomSelector extends HTMLElement {
  //Is this a hack?
  selected: string;
  dataIndex: number;
}

And I call
(<CustomSelector>radio).selected and (<CustomSelector>checkbox).dataIndex
Is that a total hack?

Technically, DOM attributes that start with data- are supposed to be accessed in javascript through the dataset field, so this should be
selected.push((<HTMLInputElement>checkbox).dataset.index);

Does that work for you? I tried that and while the typescript compiler accepted it, it didn't work at run time. I'm just curious if that works for you. I'm guessing polymer is doing something non-standard with data attributes. Also, it would appear that you and I have different typescript and/or other library versions and maybe that is the source of the different behavior we're seeing here.
Rather than create a class just to cast to it, I would suggest just casting to <any> and adding a comment with a TODO to come back and investigate this further.

That neither works for me at runtime or compiles cleanly:
app/elements/labrad-plot.ts(617,64): error TS2339: Property 'index' does not exist on type 'DOMStringMap'

Ok, I figured out how to make this work with data- attributes.
First, you have to use "explicit attribute binding" in labrad-plot.html, as described here:
<paper-checkbox checked name="traces" data-index$="{{index}}">{{index}}</paper-checkbox>

Then, you need to use square-bracket indexing to get at items inside the dataset object in labrad-plot.ts (the type definiton for DOMStringMap is here):
selected.push(Number(checkbox.dataset['index']));

All that being said, I'm not sure using a data- attribute like this is really worth it given that polymer already has mechanisms to pass things through the DOM to javascript.
How about this: use a new attribute name, say, trace-index and then just cast to <any> to make typescript happy:
in labrad-plot.html:
<paper-checkbox checked name="traces" trace-index="{{index}}">{{index}}</paper-checkbox>

in labrad-plot.ts
selected.push((<any>checkbox).traceIndex);

Sorry for all the back and forth on this. I figure if we work out a reasonable pattern here we can just use it in the future. Does this latter proposal seem reasonable to you?

Thanks for figuring this out. Totally cool with the back and forth, I'm glad we can find a way to do this properly as I think we'll be having to expand on this feature in the near future for dataset specific plotting. I'll add all this as soon as I can.
One question, that DOMStringMap typing... should that already be in typescript? Do I have to upgrade it or do I have to add this typing manually?

That DOMStringMap definition is in lib.d.ts which is bundled with typescript. Basically, it provides typescript definitions for all of the built-in browser APIs. You can find it inside node_modules if you're curious, but there's nothing you need to do to use these definitions.

Alright. I think I made all the changes you commented on. Please take a quick look when you get the chance.
Thanks for the input!

Choosing a trace on a 2D plot does not work for me. If I choose trace 0, the console log shows [NaN] for selected traces and the plotting does not work. If I choose trace 1, the console log shows [1] and it does seem to plot the new trace, although the coloring is wrong; it seems the z data limits need to be recomputed in that case.

Hm.
You're on the latest commit of the branch? One of the earlier commits broke
2D trace selection.
At least the color scale should recompute each time...
On Tue, May 17, 2016, 5:26 PM Matthew Neeley<EMAIL_ADDRESS>wrote:

Choosing a trace on a 2D plot does not work for me. If I choose trace 0,
the console log shows [NaN] for selected traces and the plotting does not
work. If I choose trace 1, the console log shows [1] and it does seem to
plot the new trace, although the coloring is wrong; it seems the z data
limits need to be recomputed in that case.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/labrad/scalabrad-web/pull/176#issuecomment-219893006

Yeah, I'm on the latest commit. The radio buttons display strange behavior as well; when the dialog opens neither is selected, and I can select both or neither options, which I wouldn't expect with a radio button.

I've seen all those problems in the past, but I'm not seeing them on my end. You sure you're on 	68c0177??
Maybe polymer components are out of date? Do a bower install?

After fiddling with bower packages, it works. LGTM

Cool, thanks for figuring that out. It's a bit troubling this is fragile in regards to the bower packages...
How do we feel about squashing and merging through the web interface on this repo?

Merging through the web interface is fine by me. I just changed the repo settings to only allow squash merges.

Shoot, forgot to say this fixes 116


Feature request: ignore space characters

I would love to see an option to exclude space characters in the settings, as is done with the newline characters.

Hey @bendix3,
I'm torn on this, word count has a bunch of setting already. And I fear it becomes more and more confusing to people opening the settings tab. In writing when you reference a article word/character count spaces are usually included. I wonder what is your exact use case, would you care to share?
Would you see any option to incorporate this into any existing feature/setting?

Hey @nesQuick,
Incorporating this into an existing feature doesn't seem feasible to me, as they're all very specific. I do admit that for most use cases characters are counted including spaces, but I stumble upon other cases from time to time, currently the application form for the German open source fund Prototypefund. I certainly wouldn't mind another setting after Ignore Markdown code blocks.
Because adding 10% of the character count without spaces usually gives you roughly the amount with them included, the problem isn't exactly dire. I suppose adding the feature only makes sense if there's others that would find it useful.

I know of several online systems for research grants that only count non-whitespace characters. I'm currently using one of them, which prompted me to post this.

I'm happy to see any PR that addressed this issue – however simply adding another option with another if will probably increase the complexity of the plugin to an extent I'm not willing to support. So I'm happy to take ideas and encourage you all to propose an implementation.


Font size in posts

The font size in posts should be increased just a little bit as of now it's too small.
Would like to improve on it under GSSOC' 21.
Thanks!
Screenshot Reference:

/assign


Option to add swap space to vm

Description
Add option to configure a swapping amount for the vm created by lima.

Was also discussed in:

https://github.com/lima-vm/lima/discussions/941


Imported contract symbols not resolving properly

Instructions
Problem
There seems to be some sort of issue resolving imported symbols.  This appeared in https://github.com/onflow/vscode-cadence/issues/312 when we updated vscode-langaugeclient from 8.0.2 to 8.1.0 - we have since downgraded to prevent this error message.
I think what happened was not that this actually created any new issue, but rather that vscode just was not displaying the error prior (see https://github.com/microsoft/vscode-languageserver-node/commit/55eb8e349c58d276ed672064b81b5c4d271e0d16).  I say this because if you install the VSCode Cadence extension right now and type in the name of an imported contract and start typing one of its children (i.e. FlowToken.Vau) you will not see any sort of autocomplete suggestion (i.e. FlowToken.Vault).
I did some logging in order to debug this.  Below is the output of the textDocument/documentSymbol response for the FlowToken contract.

Below now is the output of the textDocument/documentSymbol response for the FungibleToken contract.

Notice how the contract defined in the file itself resolves fine (all the children exist and everything) but imported contracts are not properly resolved.  They are simply empty with no children and no name (the error we see is because of the empty name which is invalid).
Steps to Reproduce
Try to update vscode-languageclient in vscode-cadence and use the extension on a file with one or more imports.  It will begin to throw the error.

I'm not sure if this is related to #97, but it might be.


Update command-line.yml

verbosity level OutputInterface::DEBUG is also valid: https://symfony.com/doc/3.0/console/verbosity.html

Hi @LaurynasGerbutavicius,
You are confusing with OutputInterface :: VERBOSITY_DEBUG .
OutputInterface :: DEBUG doesn't exist.
Regards


docs: update import

@kewinzaq1 thanks a lot!

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Run tests in CI

Revive the work we previously did on https://github.com/CommunitySolidServer/CommunitySolidServer/pull/592 /
https://github.com/CommunitySolidServer/CommunitySolidServer/pull/597

@mrvahedi68 is working on this in https://github.com/pdsinterop/community-server/pull/19

We have one failing test for solid-crud-tests
     FAIL  test/surface/fetch-pod-root.test.ts
  Alice's storage root
    ✕ is an ldp BasicContainer (99 ms)

  ● Alice's storage root › is an ldp BasicContainer

    Fetcher: <http://localhost:3000/> Unauthorized

It is maybe forALICE_WEBID that not set in the environments before run.

all web-access-control-tests failed.

trying to fix Alice's storage root failure.

CRUD tests Passed completely without any changes.
Continue by adding WAC: Continue in https://github.com/pdsinterop/community-server/issues/21


Add missing setter to PropertySerializationName property

Adds a missing setter to the property which was overlooked as part of https://github.com/microsoft/typespec/pull/4591.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.Generator.CSharp.Customization


add regex err

i think we need the regex err.

Thanks for your help. I don't think we want to print the error to console since it's not going to seen by users.


Elcomsoft.ProactivePasswordAuditor version <IP_ADDRESS>40

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

This package uses the wrong package name in its UAC prompt:

This package uses the wrong package name in its UAC prompt:

I don’t care about any mismatched names, these names were just part of the MSI file and I cannot change it due to the limitations of GitHub Web

This package uses the wrong package name in its UAC prompt:

I don’t care about any mismatched names, these names were just part of the MSI file and I cannot change it due to the limitations of GitHub Web

Oh yeah, everything is named “elcomsoft password recovery” when in reality they are all different password recovery tools.

This package uses the wrong package name in its UAC prompt:

I don’t care about any mismatched names, these names were just part of the MSI file and I cannot change it due to the limitations of GitHub Web

Oh yeah, everything is named “elcomsoft password recovery” when in reality they are all different password recovery tools.

I found another way to validate these that doesn't invoke this issue.


Remove type annotations from docstrings

This removes all type annotations from docstrings. They aren't needed since griffe generates them automatically.

Yo, thanks for all this cleanup work!


change demo link

→ https://flowhub.github.io/the-graph/examples/demo-full.html

Where? The Github website link? If so that is fixed now. Any other places I think we're up to date?


Link is not working in desktop

[REQUIRED] Step 2: Describe your environment
Operating System version: Ubuntu 18.04
Firebase SDK version: 3.12.0
Library version: ?
Firebase Product: messaging
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Clicking in received notfication (which does not open the target link).
Relevant Code:
func SendFCMNotification(title, body string, tokens []string) ([]string, error) {
        batchResp, err := fcm.SendMulticast(context.Background(), &messaging.MulticastMessage{
            Webpush: &messaging.WebpushConfig{
                Notification: &messaging.WebpushNotification{
                    Title: title,
                    Body:  body,
                    Icon:  "https://cdn2.somesite.com/heart.png",
                },
                FcmOptions: &messaging.WebpushFcmOptions{
                    Link: "https://google.com",
                },
            },
            Tokens: tokens,
        })

        if err != nil {
            return nil, fmt.Errorf("error sending multicast FCM notification: %w", err)
        }

        invalidTokens := []string{}
        for i, resp := range batchResp.Responses {
            if messaging.IsInvalidArgument(resp.Error) {
                invalidTokens = append(invalidTokens, tokens[i])
            }
        }
        return invalidTokens, nil
    }

// TODO(you): code here to reproduce the problem
`N/A
`

Hi @hume12 , I cannot identify a problem by looking at the code. Could you file a support ticket https://firebase.google.com/support/troubleshooter/contact to provide more information to the Firebase support team? Thanks!


Feat/validate json update

What I am changing

How the validation is done for Geometry to increase readability of specific type validation.

How I did it

Using functools.singledispatchmethod.

How you can test it

Run already existing tests.

Important notes
This is for Python >= 3.9. https://github.com/python/cpython/issues/83860

Error: The operation was canceled. for 3.9 and 3.8

is because the tests fails directly for 3.7 so GitHub actions kills all the other matrices

This libraries fails on 3.7. I will investigate, but later this week.

closing this. See https://github.com/developmentseed/geojson-pydantic/discussions/66#discussioncomment-3294233


Add tracing support

To be able to trace Python code (including limp.py) with this module: https://docs.python.org/3.6/library/trace.html

Hi @XVilka , you can certainly already use trace with lymp, since you can execute any arbitrary Python code using it, unless I'm missing something ? :)

Yes, just modified the limp.py. Thought there are may be a better ways for seamless tracing/debugging.


📱 Vertical Snippets & Films

Hi !
First of all, thanks for your amazing work on One Second Diary.
I was really frustrated by the-equivalent-paid-proprietary-app, which had a lot of bugs, and recently increased prices. So when I saw this open-source alternative, my decision was taken : I have to make the step.
My issue is that I was used to capture all my snippets with vertical videos, it felt just more instinctive to me.
So this is where this issue leads to : I think it would be nice to have the possibility to configure the app so to create vertical (9:16) snippets and films.
What would you think about the fesability and utility of this ? 😌

Hey, thanks for your kind words 😊
It surely is possible, but there are some drawbacks and I wonder if it's really worth the implementation effort because of the following reasons:

No backward compatibility. All the videos recorded/uploaded in portrait are transformed into landscape videos at the moment you save them. That means we don't have a way to restore the original video unless there is some cropping/zooming processing to create a vertical video out of the horizontal one, but I wonder what the quality will look like.

The reason videos are processed at the moment they are saved is to make exporting super fast: is uses ffmpeg concat filter, which requires all videos to have the same parameters (orientation, codec, streams, etc). Since all videos are already processed before the moment of exporting, the Create Movie functionality simply generates a txt file declaring all the selected videos and executes the concatenation command. Not processing vertical videos beforehand means we wouldn't be able to keep this approach, making the movie creation significantly slower. I am against this because the app is intended for long-term: compiling 1000 videos should be done in 2-3min maximum imo, so that's what I strived for with this implementation decision.

So, in order to keep both the "all orientation" export fast and make a new "vertical only" export, we would need to save both the vertical and horizontal version of the video, and add a checkbox Vertical only in the export screen, so we know we should use only the vertical videos. But is it really worth the extra storage usage since it would only benefit mobile visualization? (After all, it would essentially look the same watching on PC).
Maybe there's a better way to handle this that I am not seeing. What are your thoughts on it?

Hey @KyleKun 👋
Thanks for your quick and detailed answer about this issue.
I understand now better how the app works. I agree that your approach is the best in the long term use.
It is sure that having the option to create a movie with both vertical and horizontal snippets would require a larger architecture. And I'm not even talking of the lost of quality in a final movie containing both 16:9 and 9:16 snippets in one movie (black bars, lost in quality because of the zooming ...).
But in the end, most of people will only record in vertical, or horizontal. Not both.
So I think having the option to configure the app so it creates vertical snippets & movies only would already be a huge game changer.
Here's how that could work :
1 - When first launching the app, the user would have a "Vertical Mode" checkbook. When ticked, the app would prevent the user that if they let this checkbook on, they could only import and export vertical videos.
2 - When saving snippets, if the "Vertical Mode" is activated, create 9:16 files.
3 - Before executing the concat command, add a verification that all the snippets are in the same format. Just in case.
4 - In the setting, there would be a greyed out "Vertical Mode" checkbox, which let the user know that this format is active. When clicking it, we could add a Alert Dialog which explains that it is not possible to create both vertical and horizontal movies, and suggesting the user to reset the app if they want to change it.
In the future, we could even add the option to switch from vertical mode to horizontal by re-encoding all 9:16 files into 16:9 ones.
I think that would be a good start and would benefit a lot of users who capture all their snippets in this format.
Because I've already been interested in development on fluttter, I'll try to see if I can free up some time in the next few weeks to propose a pull request, if you agree of course.
What would you think of this ? I look forward to hearing your feedback on this principle or if you have better ideas.

Hey @phileastv, thanks for the suggestions! It gave me some insights in how to approach it better.
1 - I think this won't be needed in app first launch, just a checkbox in the settings should suffice.
2 - Agreed.
3 - Won't be needed in this approach I thought.
4 - Agreed.
Basically, I think we can create an "admin profile" called something like default_portrait in the same routines we create the app folders, so this will be taken care automatically.
The Portrait Mode checkbox in the settings, if enabled, will store the videos inside that dedicated folder. We can do the check for orientation on the save function, preventing landscape uploads and informing that if wanted, it should be done outside Portrait Mode (using default folder for storing the videos). This way we ensure only portrait videos in this mode, and keep the default method (mixed orientation) working as it is now. Movie creation will still be fast since we know all videos are in portrait.
The implementation effort will be:

Create the specific editing for portrait videos (all the ffmpeg stuff, like position of date and locale that will change, no resizing is needed, etc);
Also allow Profiles inside the Portrait Mode (separated from the Profiles we have now);
Perform the extra checks before saving to ensure it's a portrait video;
Adapt the movie creation routine to use that folder if Portrait Mode is enabled.

What do you think of it?

Because I've already been interested in development on fluttter, I'll try to see if I can free up some time in the next few weeks to propose a pull request, if you agree of course.

And for sure, it'll be a pleasure to review and help out, feel free to do so 😊

Hi !
Thanks a lot for your message.
I think were going somewhere with this ! Having the option to create Vertical profies, separated from horizontal ones is a perfect idea to keep things organised.
I started cloning the project and tried to create the vertical profiles page, but I had a bit of trouble figuring out how to organize it so that it would persist in the application's memory. Unfortunately I think this is a bit beyond my development skills, (although it probably shouldn't be that complicated!).

Hi !
Thanks a lot for your message.
I think were going somewhere with this ! Having the option to create Vertical profies, separated from horizontal ones is a perfect idea to keep things organised.
I started cloning the project and tried to create the vertical profiles page, but I had a bit of trouble figuring out how to organize it so that it would persist in the application's memory. Unfortunately I think this is a bit beyond my development skills, (although it probably shouldn't be that complicated!).

Tbh the code is not that much organized so don't worry, even I get lost sometimes 😅
The video is saved "automatically" when we execute the ffmpeg command passing the storage path, you can start understanding by taking a look here.

Hi, where are you with this feature @phileastv? I just discovered the project (thanks @KyleKun <3) and I'm really looking into having a way to compile the videos into a vertical mode!

Hey @EmileRolley,
I've been trying to make progress on this, but it requires creating a separate type of profile only for vertical snippets, and it's a bit beyond my very limited dev skills. So I put it aside as I don't have much time to devote to it.

Hey !
I also come from 1SE app and found this amazing project that i want to use and support !
Unfortunately, I also take all of my snippets vertically so I won't be able to use this app until this feature is included.
I also won't be able to help coding it because I don't know android at all but I had an implementation idea in order to avoid the "vertical configuration checkbox".
Isn't it possible to store every video in horizontal format (exactly the same as now), but when you're creating your daily snippet, you can choose to rotate the vertical snippet to make it horizontal ? It would be stored exactly the same as a "native" horizontal one.
Unfortunately, it adds two more (light) functions : being able to render the date and subtitles vertically when rotating a vertical (maybe ask the user beforehand) and then being able to rotate the full movie during the rendering.
I know this is not an optimal way of implementing it, but it seems to be a nice (and light) workaround.
What do you think ?

Hey @Hkllopp , thanks!
I gave it some more thought and agree it's better to store both versions of the videos by default after all. Will very likely implement this until the end of the year, as it's been requested by many people.

Hey !
It's really cool that contributors are coming to work on the project right now. It gets bigger and bigger !
Do you think you'll be able to implement this feature for the end of the year ? Not wanting to pressure you in any way, I just would like to know if there are any updates on this :)

Hey !
It's really cool that contributors are coming to work on the project right now. It gets bigger and bigger !
Do you think you'll be able to implement this feature for the end of the year ? Not wanting to pressure you in any way, I just would like to know if there are any updates on this :)

Hey, yeah, I'm working on some other projects this month but this feature is my top 1 priority for December.

So cool, thanks !

Hi @KyleKun !
Have you had the time to work on this issue ? Because I really want to enter my 2023 vertical snippets for 2024, I gave a second shot at trying to develop this feature by myself and made some progress.
For the moment, I added the option to create "Vertical Profiles" in the "Profiles" pages. When you create a profile, there is a toggle to enable "Vertical Mode" on this profile. If you do so, the folder will save as yourprofilename_vertical on the storage. Every profile retrieved with this name will have the an isVertical value applied to it.
I am now trying to put this logic on the snippet page and save the snippets as 1080x1920 files when you have a Vertical Profile selected.
Would you be interrested in me making a pull request with thoses changes ? I'm not a professional developer so my code must not be perfect, but if it can save you time implementing this feature that would be great !

Hi @KyleKun !
Have you had the time to work on this issue ? Because I really want to enter my 2023 vertical snippets for 2024, I gave a second shot at trying to develop this feature by myself and made some progress.
For the moment, I added the option to create "Vertical Profiles" in the "Profiles" pages. When you create a profile, there is a toggle to enable "Vertical Mode" on this profile. If you do so, the folder will save as yourprofilename_vertical on the storage. Every profile retrieved with this name will have the an isVertical value applied to it.
I am now trying to put this logic on the snippet page and save the snippets as 1080x1920 files when you have a Vertical Profile selected.
Would you be interrested in me making a pull request with thoses changes ? I'm not a professional developer so my code must not be perfect, but if it can save you time implementing this feature that would be great !

Hey, that's nice to hear! You can open the PR and I'll expand on it this weekend, or at least use it as a reference. And no worries, the feature will be ready before 2024 :)

Great ! I just added my pull request here. Maybe I will have the time to work more on it next week #113

Sorry guys for it not being exactly before 2024, but I tested the PR thoroughly and am making some changes, so probably tomorrow I'll be releasing the apk here (thanks a lot @phileastv !). Just keep on recording vertical videos and you will be able to add them through the calendar after Playstore update is available.

Don't worry :)
Happy new year 🥳

Don't worry :)
Happy new year 🥳

Hi guys,
I really love this app and was stunned to see that it is open-source.
I'm glad to see this feature is prioritized and tackled.
I'm not a good programmer, but I could be a beta tester if you need !

Hi! I would like to ask if there have been any updates regarding this project? Thank you!


Finish all OData operations (PUT, PATCH, DELETE)

All OData methods are not fully implemented
Stopped after POST. Finish the rest

Completed in v6.0.34


Identifiers validation failed for dataset Museo de Entomología Escuela Superior Politécnica de Chimborazo

Identifier validation failed for the dataset Museo de Entomología Escuela Superior Politécnica de Chimborazo:

Crawler attempt: 89
Publishing organization: Museo de Entomología de la Escuela Superior Politécnica de Chimborazo
Publishing country: ECUADOR
Installation: GBIF Ecuador - MAATE
Number of occurrences indexed for this dataset at the time of the issue: 1059
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 2102 total records; 2102 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3426748/step

New IDs sample:

Old IDs sample:

ESPOCH:ESPOCHME:000961
ESPOCH:ESPOCHME:000962
ESPOCH:ESPOCHME:000963
ESPOCH:ESPOCHME:000964
ESPOCH:ESPOCHME:000965
ESPOCH:ESPOCHME:000967
ESPOCH:ESPOCHME:000968
ESPOCH:ESPOCHME:000969
ESPOCH:ESPOCHME:000970
ESPOCH:ESPOCHME:000972

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Museo de Entomología Escuela Superior Politécnica de Chimborazo : https://doi.org/10.15468/8zkfnz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Museo de Entomología Escuela Superior Politécnica de Chimborazo:

Crawler attempt: 90
Publishing organization: Museo de Entomología de la Escuela Superior Politécnica de Chimborazo
Publishing country: ECUADOR
Installation: GBIF Ecuador - MAATE
Number of occurrences indexed for this dataset at the time of the issue: 1059
Cause: GBIF ID problems exceed 50% threshold: 54% duplicates; 2102 total records; 1134 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3426753/step

New IDs sample:

ESPOCH:ECESPOCH:000905
ESPOCH:ECESPOCH:000794
ESPOCH:ECESPOCH:000552
ESPOCH:ECESPOCH:000906
ESPOCH:ECESPOCH:000819
ESPOCH:ECESPOCH:000907
ESPOCH:ECESPOCH:000908
ESPOCH:ECESPOCH:000313
ESPOCH:ECESPOCH:000909
ESPOCH:ECESPOCH:000797

Old IDs sample:

ESPOCH:ESPOCHME:000961
ESPOCH:ESPOCHME:000962
ESPOCH:ESPOCHME:000963
ESPOCH:ESPOCHME:000964
ESPOCH:ESPOCHME:000965
ESPOCH:ESPOCHME:000967
ESPOCH:ESPOCHME:000968
ESPOCH:ESPOCHME:000969
ESPOCH:ESPOCHME:000970
ESPOCH:ESPOCHME:000972

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Museo de Entomología Escuela Superior Politécnica de Chimborazo : https://doi.org/10.15468/8zkfnz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Museo de Entomología Escuela Superior Politécnica de Chimborazo:

Crawler attempt: 91
Publishing organization: Museo de Entomología de la Escuela Superior Politécnica de Chimborazo
Publishing country: ECUADOR
Installation: GBIF Ecuador - MAATE
Number of occurrences indexed for this dataset at the time of the issue: 1059
Cause: GBIF ID problems exceed 50% threshold: 54% duplicates; 2102 total records; 1134 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3426756/step

New IDs sample:

ESPOCH:ECESPOCH:000905
ESPOCH:ECESPOCH:000794
ESPOCH:ECESPOCH:000906
ESPOCH:ECESPOCH:000552
ESPOCH:ECESPOCH:000819
ESPOCH:ECESPOCH:000907
ESPOCH:ECESPOCH:000908
ESPOCH:ECESPOCH:000313
ESPOCH:ECESPOCH:000909
ESPOCH:ECESPOCH:000797

Old IDs sample:

ESPOCH:ESPOCHME:000961
ESPOCH:ESPOCHME:000962
ESPOCH:ESPOCHME:000963
ESPOCH:ESPOCHME:000964
ESPOCH:ESPOCHME:000965
ESPOCH:ESPOCHME:000967
ESPOCH:ESPOCHME:000968
ESPOCH:ESPOCHME:000969
ESPOCH:ESPOCHME:000970
ESPOCH:ESPOCHME:000972

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Museo de Entomología Escuela Superior Politécnica de Chimborazo : https://doi.org/10.15468/8zkfnz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Note the migration of occurrences wasn't enough because the dataset had doubled the number of records. I also allowed the failed identifiers.


sigmoid_cross_entropy_loss_with_logits: ReLU input is not finite

W tensorflow/core/common_runtime/executor.cc:1076] 0x7fc328bccbd0 Compute status: Invalid argument: ReluGrad input is not finite. : Tensor had NaN values
	 [[Node: nl_1_hs_100_lr_0p1/gradients/nl_1_hs_100_lr_0p1/logistic_loss/Relu_grad/nl_1_hs_100_lr_0p1/logistic_loss/Relu/CheckNumerics = CheckNumerics[T=DT_FLOAT, message="ReluGrad input is not finite.", _device="/job:localhost/replica:0/task:0/cpu:0"](nl_1_hs_100_lr_0p1/add)]]
W tensorflow/core/common_runtime/executor.cc:1076] 0x7fc328bccbd0 Compute status: Invalid argument: ReluGrad input is not finite. : Tensor had NaN values
	 [[Node: nl_1_hs_100_lr_0p1/gradients/nl_1_hs_100_lr_0p1/logistic_loss/Relu_grad/nl_1_hs_100_lr_0p1/logistic_loss/Relu/CheckNumerics = CheckNumerics[T=DT_FLOAT, message="ReluGrad input is not finite.", _device="/job:localhost/replica:0/task:0/cpu:0"](nl_1_hs_100_lr_0p1/add)]]
	 [[Node: _send_nl_1_hs_100_lr_0p1/div_1_0 = _Send[T=DT_FLOAT, client_terminated=true, recv_device="/job:localhost/replica:0/task:0/cpu:0", send_device="/job:localhost/replica:0/task:0/cpu:0", send_device_incarnation=6247430638048453470, tensor_name="nl_1_hs_100_lr_0p1/div_1:0", _device="/job:localhost/replica:0/task:0/cpu:0"](nl_1_hs_100_lr_0p1/div_1)]]
Traceback (most recent call last):
  File "rnn.py", line 80, in <module>
    training=True)
  File "rnn.py", line 18, in run_epoch
    model.seq_targets: seq_targets
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 368, in run
    results = self._do_run(target_list, unique_fetch_targets, feed_dict_string)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/client/session.py", line 444, in _do_run
    e.code)
tensorflow.python.framework.errors.InvalidArgumentError: ReluGrad input is not finite. : Tensor had NaN values
	 [[Node: nl_1_hs_100_lr_0p1/gradients/nl_1_hs_100_lr_0p1/logistic_loss/Relu_grad/nl_1_hs_100_lr_0p1/logistic_loss/Relu/CheckNumerics = CheckNumerics[T=DT_FLOAT, message="ReluGrad input is not finite.", _device="/job:localhost/replica:0/task:0/cpu:0"](nl_1_hs_100_lr_0p1/add)]]
Caused by op u'nl_1_hs_100_lr_0p1/gradients/nl_1_hs_100_lr_0p1/logistic_loss/Relu_grad/nl_1_hs_100_lr_0p1/logistic_loss/Relu/CheckNumerics', defined at:
  File "rnn.py", line 70, in <module>
    train_model = Model(set_config(config, "train"))
  File "/Users/yoav/projects/music_rnn/model.py", line 61, in __init__
    .minimize(self.loss)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/training/optimizer.py", line 186, in minimize
    aggregation_method=aggregation_method)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/training/optimizer.py", line 232, in compute_gradients
    aggregation_method=aggregation_method)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/gradients.py", line 445, in gradients
    in_grads = _AsList(grad_fn(op_wrapper, *out_grads))
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/nn_grad.py", line 126, in _ReluGrad
    t = _VerifyTensor(op.inputs[0], op.name, "ReluGrad input is not finite.")
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/nn_grad.py", line 119, in _VerifyTensor
    verify_input = array_ops.check_numerics(t, message=msg)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/gen_array_ops.py", line 48, in check_numerics
    name=name)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/op_def_library.py", line 664, in apply_op
    op_def=op_def)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1834, in create_op
    original_op=self._default_original_op, op_def=op_def)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1043, in __init__
    self._traceback = _extract_stack()

...which was originally created as op u'nl_1_hs_100_lr_0p1/logistic_loss/Relu', defined at:
  File "rnn.py", line 70, in <module>
    train_model = Model(set_config(config, "train"))
  File "/Users/yoav/projects/music_rnn/model.py", line 58, in __init__
    losses = tf.nn.sigmoid_cross_entropy_with_logits(outputs, targets_concat)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/nn.py", line 273, in sigmoid_cross_entropy_with_logits
    return math_ops.add(nn_ops.relu(logits) - logits * targets,
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/gen_nn_ops.py", line 547, in relu
    return _op_def_lib.apply_op("Relu", features=features, name=name)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/ops/op_def_library.py", line 664, in apply_op
    op_def=op_def)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1834, in create_op
    original_op=self._default_original_op, op_def=op_def)
  File "/usr/local/lib/python2.7/site-packages/tensorflow/python/framework/ops.py", line 1043, in __init__
    self._traceback = _extract_stack()

When training a model using tf.nn.sigmoid_cross_entropy_loss_with_logits and RMSPropOptimizer, I am running into a ReLu gradient error. Since the initial learning rate for this instance of the model is quite high and this is a RNN, I am pretty confident that this is an exploding gradient issue. However, the ReLU operation that my model is exploding on is part of an optimization to "ensure stability and avoid overflow", but it seems to be having the opposite effect.

For quick reference, here is the full source code of sigimoid_cross_entropy_with_logits
def sigmoid_cross_entropy_with_logits(logits, targets, name=None):
  """Computes sigmoid cross entropy given `logits`.

  Measures the probability error in discrete classification tasks in which each
  class is independent and not mutually exclusive.  For instance, one could
  perform multilabel classification where a picture can contain both an elephant
  and a dog at the same time.

  For brevity, let `x = logits`, `z = targets`.  The logistic loss is

        z * -log(sigmoid(x)) + (1 - z) * -log(1 - sigmoid(x))
      = z * -log(1 / (1 + exp(-x))) + (1 - z) * -log(exp(-x) / (1 + exp(-x)))
      = z * log(1 + exp(-x)) + (1 - z) * (-log(exp(-x)) + log(1 + exp(-x)))
      = z * log(1 + exp(-x)) + (1 - z) * (x + log(1 + exp(-x))
      = (1 - z) * x + log(1 + exp(-x))
      = x - x * z + log(1 + exp(-x))

  To ensure stability and avoid overflow, the implementation uses

      max(x, 0) - x * z + log(1 + exp(-abs(x)))

  `logits` and `targets` must have the same type and shape.

  Args:
    logits: A `Tensor` of type `float32` or `float64`.
    targets: A `Tensor` of the same type and shape as `logits`.
    name: A name for the operation (optional).

  Returns:
    A `Tensor` of the same shape as `logits` with the componentwise
    logistic losses.
  """
  with ops.op_scope([logits, targets], name, "logistic_loss") as name:
    logits = ops.convert_to_tensor(logits, name="logits")
    targets = ops.convert_to_tensor(targets, name="targets")
    # The logistic loss formula from above is
    #   x - x * z + log(1 + exp(-x))
    # For x < 0, a more numerically stable formula is
    #   -x * z + log(1 + exp(x))
    # To avoid branching, we use the combined version
    #   max(x, 0) - x * z + log(1 + exp(-abs(x)))
    return math_ops.add(nn_ops.relu(logits) - logits * targets,
                        math_ops.log(1 + math_ops.exp(-math_ops.abs(logits))),
                        name=name)

This sounds like an issue with your model rather than a bug in TensorFlow, you may get more help from stackoverflow community on an issue like this

@yaroslavvb: Sorry, I should have been more clear: I agree with you that this is an exploding gradient issue with my model.
The reason I believe this is also a bug with tensorflow is that I am using a loss function from the official tensorflow API (sigmoid_cross_entropy_loss_with_logits). The documentation of this function leads me to believe that it is supposed to ensure numerical stability during training, and this is a counterexample where it did not. Perhaps I am misunderstanding the documentation?

Numerical stability means the result of computation is more accurate. But when you have exploding gradients, the growth in magnitudes is a feature of your model rather than some numerical error. It's like putting i=i**2 in a loop, you are going to run out of range at some point.


Enable News menu, since that will be useful going forward

We're now at the point were News items will be appearing, so let's re-enable the menu.
This year, we created that container page as 'news', not 'events', probably from manually copying last years' menu structure for pages not in the selected fixture list.

:+1:


DESCRIPTION file Error for Phyloseq

I will try to reproduce this later, but I was having trouble building the package on my laptop.  My laptop didn't have phyloseq installed at the time, and I was unable to build the package.  I tried so many things in order to get it to install as a dependency of our package, but in the end I had to manually install it.
TODO:

Reproduce this bug.
Find a way to fix this bug

Installation hooks?

This has resolved itself.


Removes embed link from paragraph

Fixes #210

Removed embed feature from paragraph of article in wagtail CMS

@dannyparsons kindly check and let me know.


CAMPAIGN STATUS: SENT, but NOTHING is DELIVERED.

Hi!
We have sucessfully configured the mail-for-good with google and amazon. We created a test subscriber list with our addresses only, made a template and a created a test campaign.
A test email option is working well (we've got a test email). While trying to send a CAMPAING, it is showing that all passed but we got NOTHING to our mailboxes.
This is strange! The TEST EMAIL functionality is working and a an email passes (amazon mail counter limit decreases -- see attached screenshots), whether the SEND campaign function is not, in spite of showing all have been sent successfully.
Any ideas what could it be and how to solve it ?
Thanks in advance!
see ya !

Have you checked the console log ? Any errors ? And did you try again ? with any other Email IDs ?


Moved call to internalSwap outside of try/catch so that we don't igno…

…re legit errors thrown by internalSwap.

Coverage increased (+0.04%) to 97.518% when pulling 4830119b758d19d210953f6767e868ade4bb274f on feature/json-redact into bcf78b25f6e566d2af03cc7bae7d8d91f9f42ea0 on master.

We found that sometimes some JSON strings were showing up in our error logs and they had PII within them. This change adds a check on string values to see if they are JSON strings, and if so parse them to an object, then redact PII within that object.


Add keypoint-detection task to Hub

I have opened PR to keypoint detection because we already have around 30 keypoint detection models on Hub (currently opening PRs to change pipeline tag), one model in transformers, and this doesn't fall under any other task.

also cc @NielsRogge

lol I opened too many PRs Hub thinks I'm spamming


Change cm to retrieve credentials (if available) regardless of cluster status

As an end user of cm cli I want to retrieve managed cluster credentials, thus:
cm create cc clusterpool-sno-1 sno-1
cm get cc sno-1
cm use cc sno-1
oc get nodes

Alternatively:
cm get cc sno-1 --creds --timeout 1

Currently cm checks cluster state but due to HIVE-1743 the cluster state might be misidentified as Resuming. In this case cm aborts before attempting to retrieve the credentials.
A workaround is available to retrieve credentials:
oc extract -n clusterpool-sno-1-bxtjn secret/sno-1-g5pml-admin-password --to=-
oc extract -n clusterpool-sno-1-bxtjn secret/sno-1-g5pml-admin-kubeconfig --keys=kubeconfig --to=-

See also issues/247 related to KUBECONFIG creds management. Both issues are applicable to internal automation using ACM+Hive, for example compliance, interop, and scale testing, and related to credentials retrieval and management. Both really useful features for automation.
References

https://coreos.slack.com/archives/CSZLMKPS5/p1661212440817929?thread_ts=1660769209.832339&cid=CSZLMKPS5

Dupe of https://github.com/stolostron/cm-cli/issues/252
Feel free to close either ticket as dupe.


build: Remove cargo lint

Duplicate crate lint is too noisy and sensitive to upstream changes

See https://github.com/ratatui/ratatui/actions/runs/12168652987/job/33939894968?pr=1546


docs(i18n): add list of translatable footer links

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

Based on the discussion in the i18n team meeting.

Thank you @sidemt for making this PR. This will be very helpful for current and future Language leads to get a clear start on what to begin translating, specifically for important articles/guides in the footer.


Color channel order is inconstant across platforms.

The order of the colors in OpenFL's BitmapData class should be ARGB, and set to big endian. However, the getPixels() call returns a ByteArray that has RGBA, and still set to big endian. Because the alpha channel is now on the other side of the color channels, it's not an endian problem. Although OpenFL displays what it loads  through Lime correctly, the app's interpretation of the pixel will be incorrect for apps that directly manipulate or generate pixel information because they will expect it to be in ARGB.

Thanks!

Thanks!


🐛 BUG: wasm error when using engineType = wasm into prisma

Which Cloudflare product(s) does this pertain to?
Workers Runtime, Wrangler core
What version(s) of the tool(s) are you using?
3.24.0
What version of Node are you using?
No response
What operating system are you using?
Mac
Describe the Bug
So basically I'm following this PRISMA + Cloudflare WORKER + Neon, to have on the edge runtime environment connection between prisma + neon into an cloudflare worker.
I'm following exactly this config but when running yarn dev (wrangler dev), I'm getting this issue:
> node worker.build.js

✘ [ERROR] No loader is configured for ".wasm" files: ../../packages/content/node_modules/.prisma/client/query-engine.wasm

    ../../packages/content/node_modules/.prisma/client/edge.js:259:29:
      259 │         return (await import(`./query-engine.wasm`)).default
          ╵                              ~~~~~~~~~~~~~~~~~~~~~

I don't know what is related.
Please provide a link to a minimal reproduction
No response
Please provide any relevant error logs
No response

We don't maintain that guide, so unfortunately we can't provide specific support with the setup. However, the error message you're getting is quite strange, since Wrangler should recognise .wasm files by default. Would you be able to put together a reproduction repo?

Closing as there has been no response from the OP for a while and there is nothing actionable for us here.


Is there a way to pause and resume a sphere or graph?

If not, what would it cost to implement such a feature?

It's not possible currently, but you could implement it by making a new AudioBackend with that functionality for a Sphere/top level graph. There may be side effects for certain scheduling operations that have to be tested though.
Another way is to add a Gen which wraps a Graph and runs it or not based on some input. This is not straight forward using the Handle API since the Graph isn't directly exposed, but that could be easily fixed by adding a method to KnystCommands which returns the local Graph. Scheduling issues may occur with this approach as well.
Could you describe your use case in greater detail?
Den 1 november 2024 17:48:12 CET, Michiel Roos @.***> skrev:

If not, what would it cost to implement such a feature?
--
Reply to this email directly or view it on GitHub:
https://github.com/ErikNatanael/knyst/issues/27
You are receiving this because you are subscribed to this thread.
Message ID: @.***>

I have a 'session' defined a file. It consists of several tonesets that can change over time based on envelopes.
The session is meant to be played as a whole. But pausing / resuming / scrubbing would be fantastic.

In that case, I think the most versatile solution is to have a play head Gen which outputs the read position. You could use atomics or channels to communicate with the Gen from the outside and tell it to stop moving, or even change the speed or direction of it's movement (for your scrubbing). Then make every envelope take this as an input for where in the envelope you are.
If you want to completely stop the audio thread, and not just stop the play head and mute the output, you can free everything and then add it back when you want to start playing again.
Would this be a satisfactory solution?
Den 1 november 2024 18:23:14 CET, Michiel Roos @.***> skrev:

I have a 'session' defined a file. It consists of several tonesets that can change over time based on envelopes.
The session is meant to be played as a whole. But pausing / resuming / scrubbing would be fantastic.
--
Reply to this email directly or view it on GitHub:
https://github.com/ErikNatanael/knyst/issues/27#issuecomment-2452274166
You are receiving this because you commented.
Message ID: @.***>

Sounds good. I'll have a go at it.


[FEATURE]: Bigint as string

Describe what you want
I'd like to add a new string alongside mode for bigint. Some popular Postgres libraries already do this such as node-pg.
This is my current workaround:
const bigint = customType<{
  data: string
}>({
  dataType: () => 'bigint',
})

Was looking for the same as I'm looking into migrating my code from raw sql using mysql2/database-js which both return bigints as string by default to be fully compatible, think having this additional mode, potentially even as default would be fantastic, tho I'll go with the workaround for now 🙌

I was also looking for this as I'm using drizzle schemas & inferred types alongside postgres-js for querying which treats bigints as strings.

Not sure why I couldn't get these customType examples to work above;
I ended up making this, which allowed me to provide strings in my queries, as well as receive strings when getting results for a bigint, while storing it in the database as a bigint;
import { customType } from 'drizzle-orm/pg-core';

export const bigintString = customType<{ data: string; driverData: bigint }>({
  dataType() {
    return 'bigint';
  },
  fromDriver(value: bigint): string {
    return value.toString();
  },
});

however, I still continue to get an inaccurate bigint, though its only for when it is included as a relation. For example:
media.schema:
export const media = pgTable('media', {
  id: bigintString('id').primaryKey(),
  label: varchar('label', { length: 255 }),
  ...

language.schema:
export const language = pgTable('language', {
  id: varchar('id', { length: 2 }).primaryKey(), //iso
  name: varchar('name', { length: 100 }).notNull(),
  mediaId: bigintString('media_id').references(() => media.id, {
    onDelete: 'cascade',
  }),
});

export const languageRelations = relations(language, ({ many, one }) => ({
  speakers: many(profileLanguage),
  icon: one(media, {
    fields: [language.mediaId],
    references: [media.id],
  }),
}));

query:
   const result = await this.db.query.language.findMany({
          with: {
            icon: true,
          },
        });

result:
[
  {
    id: 'en',
    name: 'English',
    mediaId: '34037499974189057',
    icon: {
      id: '34037499974189056',

note the one number difference on the last number (7 and 6), where the instance of id inside of icon (from the relation) is always the inaccurate version. the mediaId is always the correct version in the database.


AKS cluster metrics are not shown, Prometheus installed and running.

Describe the bug
Lens version 4.0.8 on Windows 10 does not show metrics from AKS cluster v 1.17.6
Prometheus is installed and running in lens-metrics namespace
Expected behavior
I expect metrics to be shown in Lens,
Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Lens Version: 4.0.8, prometheus: 2.17.2
OS: Windows 10
Installation method : Prometheus is installed by Lens as "Prometheus installation method Lens"

After prometheus pod restart metrics are populated. Issue is resolved.


config: Remove trusted/untrusted support for 1.14

As announced when RuntimeClass has been implemented as part of CRI-O,
the deprecated flags trusted/untrusted qualifying the workload will
be removed starting from 1.14.
This patch takes care of removing any reference to those annotations,
which simplifies greatly the code complexity.
Fixes #2139
Signed-off-by: Sebastien Boeuf<EMAIL_ADDRESS>

/cc @mrunalp

/test integration_rhel

Codecov Report

Merging #2153 into master will decrease coverage by 0.31%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master    #2153      +/-   ##
==========================================
- Coverage   31.71%   31.39%   -0.32%
==========================================
  Files          76       76
  Lines        6849     6785      -64
==========================================
- Hits         2172     2130      -42
+ Misses       4560     4537      -23
- Partials      117      118       +1

/test kata-containers

/test e2e_rhel

@mrunalp I had to repush, make lint was complaining...

/retest

/test e2e_rhel

/lgtm


Automating steps (unpack, add arrangement, build)

I'm wondering if there is a built-in method (ie command-line args) to automate some of the tasks, specifically to unpack a psarc, add an arrangement, and then build a new psarc?  (And potentially to remove an arrangement, although I'm not 100% sure I'll use that yet)
If not, can you point me in the right direction of which libraries/classes/methods to use for these activities?  I'm mostly a C# dev, and am finding myself lost while looking at the F# code!
What I'm trying to do is automate the creation of a Ukulele arrangement for each song.  I was able to do this manually with DLC Builder by opening the psarc, manually creating a ukulele arrangement from the bass arrangement, adding the ukulele arrangement as a bonus bass arrangement, and then building a new psarc.
I wrote some code to create the ukulele xml from the bass xml, so that part doesn't need me to manually edit the xml anymore, but I still need to manually open the psarc, click the +, and click build, so it'd be amazing if I could automate that portion too.
Thanks!
EDIT: Am I on the right track by using the logic for UnpackPSARC and PackDirectoryPSARC from Misc Tools?
EDIT 2: After more digging, it looks like PsarcImporter.import might be what I'm looking for.

Think I've got a working proof-of-concept now, so I'll close the issue.
In case anybody wants to do something like this in the future, the important methods are:

PsarcImporter.import to import a .psarc and extract it to a temp directory or DLCProjectModule.load to load a .rs2dlc if you previously extracted the .psarc
PackageBuilder.buildPackages to build a .psarc from the temp directory

And you can't modify the project's Arrangements collection, so you need to instantiate a new DLCProject with the new Arrangements, something like:
FSharpList<Arrangement> newArrangements = FSharpList<Arrangement>.Cons(fromFileResult.ResultValue.Item1, project.Arrangements);
project = new DLCProject(project.Version, project.Author, project.DLCKey, project.ArtistName, project.JapaneseArtistName,
    project.JapaneseTitle, project.Title, project.AlbumName, project.Year, project.AlbumArtFile, project.AudioFile,
    project.AudioPreviewFile, project.AudioPreviewStartTime, project.PitchShift, project.IgnoredIssues,
    newArrangements, project.Tones);

I guess you got it working? I haven't had the need for automating stuff with CLI tools myself so that's why there aren't any (and nobody has asked before).

Yes, the library is working perfectly for importing and building a psarc, so that part is good.  Just need to iron out some bugs in the bass -> ukulele logic now.
Thanks for the great library!


Split @iov/tendermint-types

Everything from #514 except the package renaming.
The only 7 base types shared between tendermint and BCP now are
export declare enum Algorithm {
    Ed25519 = "ed25519",
    Secp256k1 = "secp256k1"
}
export declare type PublicKeyBytes = Uint8Array & As<"public-key">;
export interface PublicKeyBundle {
    readonly algo: Algorithm;
    readonly data: PublicKeyBytes;
}
/** Used to differentiate a blockchain. Should be alphanumeric or -_/ and unique */
export declare type ChainId = string & As<"chain-id">;
export declare type SignatureBytes = Uint8Array & As<"signature">;
export declare type PostableBytes = Uint8Array & As<"postable">;
export declare type TxId = Uint8Array & As<"txid">;

Also, please set the project on the right hand sidebar, so it shows up in the issue tracker

Did you change your mind, or is that a different pr?

The renaming would increase the diff dramatically so I decided to do it separately. This keeps the important stuff and the dumb stuff separated for easier review.


WIP: bos-tasks-b9kwg: [no-test] Update translations from Fedora Zanata

Update translations from Fedora Zanata

[ ] FAIL: po-refresh

po-refresh in progress on centosci-tasks-mzwnz.
Log: https://<IP_ADDRESS>:8493/logs/po-refresh-640-20190418-053636/

po-refresh in progress on bos-tasks-pp8r1.
Log: https://<IP_ADDRESS>:8493/logs/po-refresh-640-20190418-054545/

Command '['make', 'upload-pot', 'clean-po', 'download-po']' returned non-zero exit status 2.: https://<IP_ADDRESS>:8493/logs/po-refresh-640-20190418-053636/

po-refresh in progress on bos-tasks-b9kwg.
Log: https://<IP_ADDRESS>:8493/logs/po-refresh-640-20190418-054646/

Command '['make', 'upload-pot', 'clean-po', 'download-po']' returned non-zero exit status 2.: https://<IP_ADDRESS>:8493/logs/po-refresh-640-20190418-054545/

dupe of #645


More consistent / thicker header icons and spacing.

I increased the font size of the studio header to give the icons a little more room, but also resized some of the icon so that they fill the space more consistently, and made a go of standardizing the overall line widths between them.
It's not 100%, but I think it's an improvement for readability.
Studio Before/After:

Visualizer:

Thanks! I might have a go at it after you merge this (can you merge actually, not sure how github works by default for this?).

I cannot! I believe only people with write access to the repository would be able to merge it, though I think there are some options for automatic merging in github somewhere.

If you want to play with the last icon remaining for the share screen you can open /share/test-shape to play with the share visualiser.

Is that the 'focus' icon? I think it looks alright currently because of the thicker center dot, but I'm not sure

Hope getting into this code wasn't too much of a headache!

Not at all, everything's pretty much where I'd expect :ok_hand:
The only thing I might suggest is adding setup steps to the readme for contributors to get up and running (pnpm install, prepare-packages, pnpm start).


Module not defined

When adding Bash Run Configuration, I get "Run Configuration Error: Module not defined", however there is not combobox for module selection. I can run the configuration, but the error still persists in its properties and it is marked by the red cross in the configuration select box.
OS: macOS Sierra
IntelliJ 2016.3.2

Fixed with 1.6.3.


QR CODE TAKING LONG

IT TAKES MORE THAN A SECOND TO GENERATE THE QR CODE

QR Code works well with phone with high ram unfortunately for phones with small ram it takes long.


chore(deps): bump kumahq/kuma-website from de020b87 to 35f7b328

Auto upgrade PR log:
35f7b32858bfcbfe2d6bf405c384b4070b503330 docs(posts): adjust madr numbers (kumahq/kuma-website#1754)
170c48733e41750fba2e76a2c7aa3ab815c29aa4 docs(gatewayapi): fix and adjust gateway api documentation (kumahq/kuma-website#1738)
a5904de62f3d713805d525fb992d21989b51c818 fix(docs): small fixes in production/cp-deployment/multi-zone (kumahq/kuma-website#1694)
227ae867ec2ca94a03298777ec980d9afaa55c6c feat(guides): transition to the new policies (kumahq/kuma-website#1749)
4ae3dabff8df8178224a71866a257c6aef7ca6b7 docs(gateway/builtin): update gateway docs after service tag deprecation in MeshGatewayInstance (kumahq/kuma-website#1748)
Triggered by action.
labels: skip-changelog,review:general

This fails because this include doesn't exist in docs.konghq.com.
Currently, the platform doesn't support looking for includes in the submodule. We've been working around this problem by adding the required includes to the docs site, I'll create a ticket to add support for this.

@bartsmykla can we remove this snippet? Why did we end up with this in the first place?

We've ended up using it as it was reused in 3 places, and I didn't know it won't work with Kong Mesh docs. Let me remove it


Does it work with Vanilla theme?

Is there any way to implement this amazing view on the admin panel using vanilla theme?

What view do you mean?
All extra fields could be added to any theme.


flash_gemv installation issue

After I run pip install -r requirements.txt; cd flash_gemv; pip install -e . I get the following error when I try to import flash_gemv. Do you know how I can fix this? For reference, this is using PyTorch 2.1.2 with CUDA 12.1
OSError                                   Traceback (most recent call last)

Cell In[1], line 1

----> 1 import flash_gemv

File ~/CATS/flash_gemv/flash_gemv/__init__.py:33

     30 spec = importlib.machinery.PathFinder().find_spec(

     31     library, [osp.dirname(__file__)])

     32 if spec is not None:

---> 33     torch.ops.load_library(spec.origin)

     34 else:

     35     raise ImportError(f"Could not find module '{library}' in "

     36                       f'{osp.dirname(__file__)}')

File ~/miniconda3/envs/code-tree-search/lib/python3.9/site-packages/torch/_ops.py:852, in _Ops.load_library(self, path)

    847 path = _utils_internal.resolve_library_path(path)

    848 with dl_open_guard():

    849     # Import the shared library into the process, thus running its

    850     # static (global) initialization code in order to register custom

    851     # operators with the JIT.

--> 852     ctypes.CDLL(path)

    853 self.loaded_libraries.add(path)

File ~/miniconda3/envs/code-tree-search/lib/python3.9/ctypes/__init__.py:382, in CDLL.__init__(self, name, mode, handle, use_errno, use_last_error, winmode)

    379 self._FuncPtr = _FuncPtr

    381 if handle is None:

--> 382     self._handle = _dlopen(self._name, mode)

    383 else:

    384     self._handle = handle

OSError: /home/sanjayss/CATS/flash_gemv/flash_gemv/_C.so: undefined symbol: _ZN2at4_ops19empty_memory_format4callEN3c108ArrayRefINS2_6SymIntEEESt8optionalINS2_10ScalarTypeEES6_INS2_6LayoutEES6_INS2_6DeviceEES6_IbES6_INS2_12MemoryFormatEE

Hi Sanjay,
Could you let me know which python version you are using now?

@sanjayss34

Python 3.9.18

@vxbrandon


Can custom Cursors CSS on Browservice? but not Work

Add all Type cursors CSS

This is all Cursors css

.alias {cursor: alias;}
.all-scroll {cursor: all-scroll;}
.auto {cursor: auto;}
.cell {cursor: cell;}
.context-menu {cursor: context-menu;}
.col-resize {cursor: col-resize;}
.copy {cursor: copy;}
.crosshair {cursor: crosshair;}
.default {cursor: default;}
.e-resize {cursor: e-resize;}
.ew-resize {cursor: ew-resize;}
.grab {cursor: grab;}
.grabbing {cursor: grabbing;}
.help {cursor: help;}
.move {cursor: move;}
.n-resize {cursor: n-resize;}
.ne-resize {cursor: ne-resize;}
.nesw-resize {cursor: nesw-resize;}
.ns-resize {cursor: ns-resize;}
.nw-resize {cursor: nw-resize;}
.nwse-resize {cursor: nwse-resize;}
.no-drop {cursor: no-drop;}
.none {cursor: none;}
.not-allowed {cursor: not-allowed;}
.pointer {cursor: pointer;}
.progress {cursor: progress;}
.row-resize {cursor: row-resize;}
.s-resize {cursor: s-resize;}
.se-resize {cursor: se-resize;}
.sw-resize {cursor: sw-resize;}
.text {cursor: text;}
.url {cursor: url(myBall.cur),auto;}
.w-resize {cursor: w-resize;}
.wait {cursor: wait;}
.zoom-in {cursor: zoom-in;}
.zoom-out {cursor: zoom-out;}

This Custom Cursors CSS by URL

.module {
  cursor: url('path-to-image.png'), auto;
}

Try https://www.cursors-4u.com/ on Browservice but CSS Custom Cursors Not work

The set of available cursors is currently limited to the most important ones (normal, link pointer and text selector) due to the limitations in how the server can send signals to the JavaScript client on old browsers (the pointer information has to be sent in the size information of the image; to make this feasible, there should not be too many options). One could implement this by adding a special cursor that would trigger the client to download information about the cursor as another image. However, this is not easy to make portable and risks hurting performance, so I won't be working on this in the near future as priorities are elsewhere (but good pull requests are welcome).

Trying CSS Cursor Cur files on Browservice?
.module {
cursor: url('path-to-image.cur'), auto;
}


Cluster changes

Make it possible to update cluster name. Drop display name for clusters.

Coverage decreased (-0.05%) to 37.779% when pulling fd98ac7f41f8046aa377014b80757203c5dec458 on feature/update-cluster into 49449be2961bc8e107446ec7f78031d3c6f0b62e on main.


Eureka Client dependency conflict Jersey 1.x / Jersey 2.x

We have to add the spring-boot-starter-jersey to put Jersyey 2.14 on the classpath. The mix of both versions lead to strange NoSuchMethodErrors during application startup! The only solution seems to be to use JAX-RX 1.x (Jersey 1) . How to deal with that?
https://github.com/Netflix/eureka/issues/600#issuecomment-126602889

If netflix is not planning on doing anything, there's not much we can do.

Not sure what the issue with upgrading to javax.ws.rs 2.0.1. Why stick with the very outdated javax.ws.rs:jsr311-api:1.1.1?

We don't control the dependency, it's a Netflix/eureka issue. They don't plan on upgrading in the near term.

Now that I made my last comment, looks like things are changing! See this comment

Hi @spencergibb yes, I asked them directly about this. Good news. Let's keep an eye for that to hit master. :+1:

Yes, hope it happens soon too

I'm going to close this. We track eureka changes regularly.


Add VCF data donation

Add a generic VCF data donation data source.
Illumina UYG data should get migrated into this once it's running.

@madprime looks good; 👍 for merging

oops; forgot about the one typo; good to merge after that :)

[Current coverage][cc-pull] is 88.95%

Merging [#541][cc-pull] into [master][cc-base-branch] will decrease coverage by 0.45%

@@             master       #541   diff @@
==========================================
  Files           203        209     +6
  Lines          7973       8122   +149
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           7129       7225    +96
- Misses          844        897    +53
  Partials          0          0

Powered by Codecov. Last updated by [bc8c54f...0768e29][cc-compare]
[cc-base-branch]: https://codecov.io/gh/PersonalGenomesOrg/open-humans/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/PersonalGenomesOrg/open-humans/compare/bc8c54f2e9581e793f7936bf0a0ca5e778001ae2...0768e29d8d91419a8658be5e63b11dd9fb6bb052?src=pr
[cc-pull]: https://codecov.io/gh/PersonalGenomesOrg/open-humans/pull/541?src=pr


Inconsistency with starting script - apikey required?

Hi @stefek99 - thanks for this report. I made the pull request that added Windows support yesterday. Did indeed forget to include that option. Going to make another pull request to add it.


pytorch version comparison code fails for pytorch 1.10

A warning is produced when running clip using pytorch version 1.10 or greater.
The version check code performs a comparison using strings. This fails for version 1.10 because string comparison is left to right and 1 is less than 7.
>>> ["1", "10", "0"] < ["1", "7", "1"]
True
>>> ["1", "9", "0"] < ["1", "7", "1"]
False

There is the TorchVersion class that would make this comparison easier to perform however that does not exist in pytorch 1.7. I suggest converting the strings into integers before performing the comparison.

This was suggested in #160 but using TorchVersion does look cleaner. I'll look into fixing this

Ah dammit I've just written an identical comparison. Looking at the 1.7 branch of torch I do not see TorchVersion as the torch_version.py file is missing.

Got a problem when torch version is 1.9.0a0+2ecb2c7

Did anyone try packaging.version from setuptools? It seems to work well for the following test cases:
>>> from packaging import version
>>> version.parse("1.5.0") < version.parse("1.7.1")
True
>>> version.parse("1.10.0") < version.parse("1.7.1")
False
>>> version.parse("1.9.0") < version.parse("1.7.1")
False
>>> version.parse("1.9.0a0+2ecb2c7") < version.parse("1.7.1")
False

>>> import torch
>>> type(torch.__version__), torch.__version__
(<class 'torch.torch_version.TorchVersion'>, '1.10.0')
>>> version.parse(torch.__version__) < version.parse("1.7.1")
False

This can be closed now since 573315e solves the issue.


Test Week

Following architecture week we're going to have test week, where we'll move our test coverage up to 100% (or at least as close as possible) and write tests that intentionally probe our software for bugs and failures.
Between architecture week and test week though I'd like to release an update. The update would contain the refactored code, the desktop app, balances that can be spent in many outputs even if you don't have enough outputs to spend, and a less buggy file uploading and hosting process.
Tests to write for consensus:

[ ] Submit a comprehensive set of illegal financial transactions in blocks
[ ] Submit illegal contracts
[ ] Submit illegal storage proofs
[ ] Submit blocks where the illegal transaction is buried under a bunch of legal transactions, make sure the state hash is still the same after the block is rejected
[ ] Submit blocks with many complex and many simple transactions (all piled into one block)
[x] Submit blocks that are too large
[x] Apply and reverse every block multiple times, travel down multiple forks, make sure state hash is always consistent
[ ] Try to adjust the difficulty beyond the maximum adjustment (in both directions)
[x] Try to submit blocks that have too early timestamps
[ ] Check that the difficulty moves in the right direction when adjusting
[x] Try to submit orphan blocks, then connect them and see if they connect correctly

I'm going to supplement this by saying 'code review +  test week'. We'll review all of the code, and write tests as we go.

Closing this because we're taking a slightly different attitude towards testing. Test only what's necessary to get the beta out, then ramp up the testing as the dust settles and we approach an actual release.