rdf statements for describing the generation of a tika-hash

With #59 , we introduce the tika-tlsh hash. Now, we'd like to express the generation of such a hash from a sha256 referenced content  in rdf statements.

I stopped TikaHashingActivity from emitting <activityUUID> <used> <hash://sha256/blubbub> because that statement was causing the activity to keep running in an endless loop. I can't think of a nice way to prevent that statement from running another tika-tlsh hashing activity. The uses statement was also a little redundant with <hash://tika-tlsh/blahblah> <wasDerivedFrom> <hash://sha256S/blubbub> <activityUUID> ., so I don't think anyone will miss it much. Now we see something like this:
<something> <isRelatedTo> <hash://sha256/blabla> .
<3f531feb-6139-4c07-839a-474c3ec8c7ba> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/ns/prov#Activity> <3f531feb-6139-4c07-839a-474c3ec8c7ba> .
<hash://tika-tlsh/532a4237d1782aa7576f40d213f91ce46b1fb886498bebcedc507680db323a9415f> <http://www.w3.org/ns/prov#wasDerivedFrom> <hash://sha256/blabla> <3f531feb-6139-4c07-839a-474c3ec8c7ba> .
<hash://tika-tlsh/532a4237d1782aa7576f40d213f91ce46b1fb886498bebcedc507680db323a9415f> <http://www.w3.org/ns/prov#wasGeneratedBy> <3f531feb-6139-4c07-839a-474c3ec8c7ba> <3f531feb-6139-4c07-839a-474c3ec8c7ba> .

Also, I stopped the tika-tlsh hashing activity from running when it sees "hash://tika-tlsh/..." in the subject, so the last two lines no longer cause the activity to run again. I'm gonna assume that's good enough for now.
@jhpoelen feel free to close this issue if you don't object to these changes.

Hey @mielliott - thanks for having a look at this. Why not simply prevent generated messages from getting inserted into the processing queue and only accept new quads from stdin?

I was reluctant to give up that beautiful feature of preston. If we do that, then the tikatlsh processor still won't be able to play with other processors in the future. I guess that's okay for now though.
Doing what you suggest might look like this:

@Parameters(separators = "= ", commandDescription = "Generates Tika TLSH associated with any encountered hash://sha256 IRIs")
public class CmdTika extends CmdProcess {

    @Override
    protected Stream<StatementListener> createProcessors(BlobStore blobStore, StatementListener queueAsListener) {
        return Stream.empty();
    }

    @Override
    void processQueue(Queue<Quad> statementQueue, BlobStore blobStore, ActivityContext ctx, StatementListener[] listeners) {
        Queue<Quad> generatedQueue = new ConcurrentLinkedQueue<Quad>();

        StatementListener[] processors = Stream.of(
                new TikaHashingActivity(blobStore, generatedQueue::add)
        ).toArray(StatementListener[]::new);

        handleQueuedMessages(statementQueue, listeners);

        StatementEmitter emitter = statement -> {
            handleStatement(statement, listeners);
            handleStatement(statement, processors);
            handleQueuedMessages(statementQueue, listeners);
            handleQueuedMessages(generatedQueue, listeners);
        };
        new EmittingStreamRDF(emitter, this).parseAndEmit(getInputStream());
    }
}

It passes the CmdTikaTests. Let me know if you prefer this and I'll make the changes.

Actually, that code does not let processors listen in the first pass over statementQueue. I'll fix that. You get the idea though.

Thanks for sharing the example. I see the tika-tlsh processor independent from how the queue is managed, so you'd still be able to use the processor in other commands / workflows. I'll have a look at the implementation shortly and hoping to discuss in today's meeting.

I see the tika-tlsh processor independent from how the queue is managed, so you'd still be able to use the processor in other commands / workflows

But it explodes if it reads from the same queue that it writes to. If we use the tika-tlsh processor in the update or process commands, it will explode. Right? Looking forward to discussing this.

I think some context is needed for the Activity to be somewhat smart about making a decision to process or not. Perhaps if we emit a graph (a collection of related statements) instead of individual statements, an activity like TikaTLSH can decide to not process statement originating from a named graph that was produced by that same TikaTLSH in the past.
So, instead of:
Quad statement = ...
something.emit(statement)

we'd say:
Graph<Quad> graph = ...
something.emit(graph)

or similarly:
List<Quad> statements = ...
something.emit(statements)

I'm all for that. We discussed something very similar in the past when trying to link activities with wasInformedBy statements, but I don't think we had considered that it could address some recursive loop issues.
Since all of our processors group their generated statements as inputs to aemitAsNewActivity/emitAsNamedActivity function, we already have a little bit of a batch messaging structure in place.
Note that this would only let us detect "one-step" cycles (A -> A), but we could still have multi-step cycles (A -> B -> A). If we use a Graph struct as you proposed, we would have the option of extending it in the future, if needed, to keep some memory to detect multi-step cycles.

Nice! I tried it and got the same output. Closing issue.


feat: update a11y model

Alaska Airlines Pull Request
Summary:
This PR updates the HTML template of the popover to allow for users to place the trigger inside or outside the scope of the shadow DOM slots.
This also updates the a11y interaction by visually hiding the content allowing for screen readers to pick up the test, and applying the role of tooltip so that the screen reader identifies it as such.
Type of change:
Please delete options that are not relevant.

[x] New capability
[x] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Now that .Net 4.8 has fixed "Keyboard Focus ToolTips"; So Krypton Tooltips be displayed also on Focus

•Fixed the WinForms control tooltip's issue where it does not appear when moving keyboard focus to the control A control's tooltip is displayed now when a user uses a keyboard to focus the control. This change is effective in applications that have Switch.System.Windows.Forms.UseLegacyToolTipDisplay value and either Switch.UseLegacyAccessibilityFeatures.3 value is set to false or application is built to target .NET version 4.8. App.config file content is shown below (in 642548). [548792, System.Windows.Forms.dll, Bug, Build:3646]

•A ToolStrip item's tooltip is displayed now when a user uses a keyboard to focus the ToolStrip item. This change is effective in applications that have Switch.System.Windows.Forms.UseLegacyToolTipDisplay value and either Switch.UseLegacyAccessibilityFeatures.3 value is set to false or application is built to target .NET version 4.8. [549360, System.Windows.Forms.dll, Bug, Build:3673] App.config file content example:
  <configuration>   ...   <runtime>     <!-- AppContextSwitchOverrides values are in the form of 'key1=true|false;key2=true|false  -->     <!-- Enabling newer accessibility features (e.g. UseLegacyAccessibilityFeatures.2=false) requires all older accessibility features to be enabled (e.g. UseLegacyAccessibilityFeatures=false) -->     <AppContextSwitchOverrides value=""Switch.UseLegacyAccessibilityFeatures=false;Switch.UseLegacyAccessibilityFeatures.2=false;Switch.UseLegacyAccessibilityFeatures.3=false;Switch.System.Windows.Forms.UseLegacyToolTipDisplay=false""/>   </runtime>   </configuration>

•The keyboard tooltips feature is "opt-in" now - it is no longer switched on implicitly when app targets .NET 4.8. "Switch.UseLegacyAccessibilityFeatures.3=false", which is a default value for .NET 4.8 apps, is still required by the feature. [686499, System.Windows.Forms.dll, Bug, Build:3694] App.config file content example with enabled keyboard tooltips for apps targeting .NET 4.7.2 or older:
`

...

<AppContextSwitchOverrides value=""Switch.UseLegacyAccessibilityFeatures=false;Switch.UseLegacyAccessibilityFeatures.2=false;Switch.UseLegacyAccessibilityFeatures.3=false;Switch.System.Windows.Forms.UseLegacyToolTipDisplay=false""/>

App.config file content example with enabled keyboard tooltips for apps targeting .NET 4.8:

  ...

`


chore: ensure yarn duplicate is run for keeping the amount of package variants smaller

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@ee0d137). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #225   +/-   ##
=======================================
  Coverage        ?   80.00%
=======================================
  Files           ?       28
  Lines           ?      685
  Branches        ?      149
=======================================
  Hits            ?      548
  Misses          ?      137
  Partials        ?        0

Continue to review full report at Codecov.

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

@n1ru4l I had some trouble with rebasing/force-push because you created the branch from your fork, so I merged it through this PR:  https://github.com/dotansimha/envelop/pull/248


I1, I7 & I3 Challenges

Changes

Fixed rc.local, wrote boot scripts
Init passwd, shadow files for iotgoat and root user accounts
Pushed vulnerable API directory to /vulnapi
Implemented vulnerable login & OS command injection challenges
Implemented hard-coded encryption key to /etc/dropbear under /keys

/etc/shadow overwrites the already created hardcoded password.
Curious to know that file size of the compiled image with both php, python, and Django. I applaud the idea of including an already vulnerable API to ease development efforts although there is no context how this relates to IoT Security. From the tiredful-api documentation it appears the API is based on a book store, ads, and a blog? Perhaps the theme can be modified to a more applicable subject?

Yes, it overwrites the file because the root password was changed to a password that can be bruteforced using a famous word-list named darkc0de.lst
And, the tiredful-api was used as in a router, generally there's no REST API, but, I was said to implement one.

Could you share the updated password out of band?
What are the router use cases in the API?

Done

Closed this PR. Not enough information on the  API, passwords, or the file size of the compiled firmware with php, python, and Django framework.


Disable Opponent's Strum Glowing on note hit

What feature do you want to get added on the base engine?
In Options, there would be an option to toggle the Opponent's Strum Glowing whenever they hit a note, similar to the Base FNF Engine.

No

I don't feel like doing it and don't feel like i want it


Replace unmaintained phantonjs dependency

PhantomJS is no longer maintained, it might be a good idea to find a suitable replacement.

@ariejan Thanks! Picked this up and migrated to Selenium Webdriver for system/integration/JS tests: #238


New version: Changepoints v0.4.0

Registering package: Changepoints
Repository: https://github.com/STOR-i/Changepoints.jl
Created by: @fairbrot
Version: v0.4.0
Commit: d4878f4f3f98f2dc23230dc36f97ff5556365c88
Git reference: master

@fairbrot can you please see the message above?  Once you add the missing compat bounds, you can trigger registration again without changing the version number, so that this pull request will be updated automatically.  Thanks!
[noblock]


annh5ad2rds.R: Error: Missing required datasets 'levels' and 'values'

/BGFS1/usr/share/packages/R/4.3.1/bin/Rscript annh5ad2rds.R --infile seurat_out.h5ad --outfile seurat_obj.rds
Attaching package: ‘dplyr’
The following objects are masked from ‘package:stats’:
filter, lag

The following objects are masked from ‘package:base’:
intersect, setdiff, setequal, union

The legacy packages maptools, rgdal, and rgeos, underpinning the sp package,
which was just loaded, will retire in October 2023.
Please refer to R-spatial evolution reports for details, especially
https://r-spatial.org/r/2023/05/15/evolution4.html.
It may be desirable to make the sf package available;
package maintainers should consider adding sf to Suggests:.
The sp package is now running under evolution status 2
(status 2 uses the sf package in place of rgdal)
Attaching SeuratObject
Registered S3 method overwritten by 'SeuratDisk':
method            from
as.sparse.H5Group Seurat
Warning: Unknown file type: h5ad
Creating h5Seurat file for version <IP_ADDRESS>00
Adding X as data
Adding X as counts
Adding meta.features from var
Adding spatial as cell embeddings for spatial
Adding raw_cellname to miscellaneous data
Adding raw_counts to miscellaneous data
Adding raw_genename to miscellaneous data
Adding sn to miscellaneous data
[1] "Finished! Converting h5ad to h5seurat file at:"
[2] "seurat_out.h5seurat"
Validating h5Seurat file
Warning: Feature names cannot have underscores (''), replacing with dashes ('-')
Initializing Spatial with data
Adding counts for Spatial
Adding feature-level metadata for Spatial
Adding reduction spatial
Adding cell embeddings for spatial
Adding miscellaneous information for spatial
Adding command information
Adding cell-level metadata
Error: Missing required datasets 'levels' and 'values'
In addition: Warning message:
Cannot add objects with duplicate keys (offending key: spatial), setting key to 'spatialxj_'
Execution halted

This is caused by the compatibility between R script annh5ad2rds.R and higher version AnnData(higher than 0.7.5), you can download the new version R script h5ad2rds.R to solve this error.

problem solved!  thank you very much.


Performance settings

There is no discussion so opening an issue.
The backup seems to be going slow. I know it will take time (it is 6.6 TB), but the odd thing is that it seems to work faster when I have the interface open. This is the exact opposite of how these things are supposed to be programmed.
I used Crashplan many years ago when they still had personal backup. In the client, there used to be settings for priority when active and idle. I do not see those now.
Are there any docker settings to keep it "active" or give it more priority?
For the X11 it is running on, is there any way to make it think the process is in the foreground even when not connected to the interface?
I have given it about a GB of memory per TB.
Do you have any other suggestions for improving performance?
Thanks. This thing you have created is saving me time and money.

I used Crashplan many years ago when they still had personal backup. In the client, there used to be settings for priority when active and idle. I do not see those now.

These are under Settings->Network.  Do you have any bandwidth limit set there ?

These are under Settings->Network. Do you have any bandwidth limit set there ?

I have bandwidth set there, but I was referring to the CPU throttling settings. Does the business client not throttle the CPU?

Ok I see.  CPU throttling seems to have been removed from the application, but you can still configure it from the CrashPlan console (by logging in to crashplan.com)

Ok I see. CPU throttling seems to have been removed from the application, but you can still configure it from the CrashPlan console (by logging in to crashplan.com)

Awesome thanks.
I still am curious about the added performance quirks that may be added by the virtual X11 and docker if anyone knows.

The X server running in the docker container is the same as the one running on a regular desktop.  So normally CrashPlan should behave the same way.
There is a way for an application to ask the X server for the idle time of the user (i.e. time since the last keyboard/mouse activity).  I don't know if there is an easy way to affect that.


Update index based command errors

Remove redundant GUI footer displaying data path
change error messages for index-based commands to be clearer
Remove a temp log message from previous iterations

Codecov Report

Merging #190 (1c7ccba) into master (3aa22a9) will decrease coverage by 0.17%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #190      +/-   ##
============================================
- Coverage     60.93%   60.75%   -0.18%
  Complexity      683      683
============================================
  Files           125      124       -1
  Lines          2757     2765       +8
  Branches        263      264       +1
============================================
  Hits           1680     1680
- Misses          982      990       +8
  Partials         95       95

Impacted Files
Coverage Δ

...main/java/seedu/address/commons/core/Messages.java
0.00% <ø> (ø)

...in/java/seedu/address/logic/parser/ParserUtil.java
88.23% <ø> (ø)

src/main/java/seedu/address/ui/MainWindow.java
0.00% <ø> (ø)

src/main/java/seedu/address/ui/TaskCard.java
0.00% <ø> (ø)

.../java/seedu/address/model/util/SampleDataUtil.java
18.18% <0.00%> (-15.16%)
:arrow_down:

Continue to review full report at Codecov.

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


Use build.outDir from vite for custom public/sw.js file

I'm really new to service worker, workbox and PWA. Got following situation:
My vite setup is located inside ~/app/frontend/vite.config.ts thus contains build.outDir which links to ../../public/dist.
I'd need to configure the same for the PWA plugin or that at least the PWA automatically checks whether build.outDir has been configured and makes use of it instead of searching for public/sw.js at the relative path of the vite.config.ts.
I might be wrong, but that's so far my assumption of this issue to me, correct me in case I'm wrong! :)
Thanks

Welp just found out that there's srcDir...
VitePWA({
    srcDir: '',
})


Relative mouse input support

Hi,
I´ve been discussing a protocol extension with @pnowak from gnome-remote-desktop to allow relative mouse input with RDP.
For FreeRDP https://github.com/FreeRDP/FreeRDP/pull/7565 will implement a dynamic channel that can replace the [MS-RDPBCGR] mouse input and allow this.
If there is need/interest/... feel free to add support too.

Thanks for the heads-up!

Probably @jsorg71 and @Nexarian might be interested in this here. Relative mouse input is necessary to be able to play e.g. shooters in a remote desktop session, as they rely on it.

I've been thinking about an extension like this too.  I search the MS docs and can't find any.
This is a problem with MSRDP servers too, these games don't work right.  Hard to believe they have not addresses this.
I looked at this extension, it has one message from client to server.
Can we add another one from server to client to tell the client to capture the mouse.  That should be the event that tells the client to start using this channel for mouse input.

@jsorg71 it should be fairly easy to add a rdp channel plugin for windows that injects mouse input, so we could also cover that with this extension.

@jsorg71 as for the capture mouse message, so you want to dynamically switch between absolute and relative input depending on what the server tells?
Currently we do that with a client flag as you need client support to actually get relative input data. The channel is used whenever it is available (e.g. client & server support it and the channel major version matches)
trying to keep it simple, every message comes with a price (long term)

@jsorg71 but better keep the conversation over at https://github.com/FreeRDP/FreeRDP/pull/7565 as this issue here is for xrdp implementing what we come up with ;)

I am definitely interested in helping out here! Getting it such that you could play 3D FPS games over XRDP is the dream :)

Any update on relative mouse movement support? I'm trying to do Unreal engine development over RDP from my laptop to my Ubuntu server, and this is a major blocker.


use cabal 1.22

This works for me. I also removed the sqlite libraries.

Merged these changes in via a different commit rather than asking for a rebase.


fix: export named as code generation with tree shaking.

Summary

There are some inconsistencies when storing the ExportNamedDeclaration during code generation phase and tree shaking phase, this pull request fixes the inconsistency.

Test Plan

!canary


Add more Javascript programs in the existing repo.

you can add any program related to the concepts of javascript.  Anything that can help beginners to learn the concepts of javascript

i want to contribute to it

i want to contribute to it

Go ahead and add any program you like and make a pull request. Good luck !!

@Abhijay007 Would you mind adding hacktoberfest in the list of topics on this project to participate on Hacktoberfest 2020?
I would love to add a simple program to contribute on Hacktoberfest 2020.
Thanks!

Hello, I have added a program, see: https://github.com/Abhijay007/Javascript-Practice-programs/pull/6

Check my program, #12

Please check this, #9

Please check this, #9

ok

Hello, I have added another program, see PR https://github.com/Abhijay007/Javascript-Practice-programs/pull/18

#21

not able to push changes to my forked repo, permission denied

kindly check my pull request #22

Hey, @Abhijay007 I have added a countdown timer program. Please check my PR #23.

i want to contribute

Please Check my Pull Request #25

Please check my pull request #42


error on setup

I get this on setup after putting in peoples names
4:46:11 PM	Info	Deployed Overall Rank sheet
4:46:17 PM	Info	Deployed Overall Percent sheet
4:46:17 PM	Info	runFirstStack TypeError: Cannot read properties of undefined (reading 'alert')
at runFirst (Code:84:28)
at GS_INTERNAL_top_function_call.gs:1:8

sorry, I see you said to wait, just and FYI for you.
Thanks for the efforts.

Hi @pcalder3 -- thanks for checking out the script. I'm not sure what exactly generated this error for you, but I'm in the process of heavily updating the script, which I hope to release in the next few days.

You just need to move this to line 84 of your code to the survivor pool
popup works.
Hope that helps.
var ui = SpreadsheetApp.getUi();
On Wed, Aug 23, 2023 at 9:25 PM boilermaker-ben @.***>
wrote:

Hi @pcalder3 https://github.com/pcalder3 -- thanks for checking out the
script. I'm not sure what exactly generated this error for you, but I'm in
the process of heavily updating the script, which I hope to release in the
next few days.
—
Reply to this email directly, view it on GitHub
https://github.com/boilermaker-ben/Google-NFL-Pick-Ems/issues/2#issuecomment-1690849973,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTHBRR47OSX3J5D73W2QUTXW2UQBANCNFSM6AAAAAA34BBKVY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Good work figuring out what the error was. I just posted this on Reddit:
https://www.reddit.com/r/fantasyfootball/comments/167j788/run_your_own_pickems_or_survivor_group_free/
And here's the new version on GitHub:
https://github.com/boilermaker-ben/Google-Sheets-NFL-Pick-Ems-and-Survivor-Pool/
Good luck and let me know if you run into any issues!


Spottable: added guards and removed focused state

Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[x] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
Spotlight was taking a long time to run focus and blur
Resolution
Removed focused state and have a guard for focusWhenDisabled
Additional Considerations
doing some hacky things to avoid lifecycle methods, but this works.
Links
ENYO-5878

I've removed the failing 'should not re-render when a non-Spottable prop does not change' test, which was added when we originally added the shouldComponentUpdate lifecycle to Spottable, so no functionality has been changed from the initial Spottable implementation. To run such a test, we would need to consider turning Spottable into a pure component


Try to properly disconnect and delete nodes on shutdown

Should fix crashes like https://gitlab.com/dashpay/dash/-/jobs/408198109#L3474
Note: most of it is just moving some code around to reuse it, see https://github.com/dashpay/dash/commit/035a84173?w=1 for a no-whitespace-changes version

Sounds like https://github.com/dashpay/dash/issues/3331

What's blocking this? Is there a reason to not merge?


⚠ SceneTime has degraded performance

In 346ef85, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 1416 ms

Resolved: SceneTime performance has improved in c3739c3 after 6 minutes.


[error] Missing Dependency of LXD

Setting up two LXD instances and trying to pulling a snapshot from the other one failed:
>>> lxc copy mexico:bdr local:bdr
error: Couldn't find criu binary on the source server. Is it installed in LXD's path?

You can't copy or move a running container unless you're using CRIU.
LXD doesn't depend on CRIU because the right version of it isn't available in Ubuntu (nor upstream really) and isn't available on all architectures.

You can't copy or move a running container unless you're using CRIU.
Oh, I didn't know that. Could we add that to the error message?

LXD doesn't depend on CRIU because the right version of it isn't available in Ubuntu (nor upstream really) and isn't available on all architectures.
If I understand correctly, it will be a long way before we get live migrations of LXD containers working out of the box.

Thanks for your help, @stgraber .


create these wallet instances by a list of configs

I guess in the future we could create these wallet instances by a list of configs, so that dont need to write this similar component.

Yes, as we have right now, at least 7 wallets in ecosystem, it would be really nice to have
ht @Jarsen136
Originally posted by @yangwao in https://github.com/kodadot/nft-gallery/issues/4178#issuecomment-1291701410

👋


Implement reset offsets

What does this PR do?

Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

Current dependencies on/for this PR:

master

PR #13918

PR #14078

PR #14103   👈
PR #14095
PR #14094
PR #14080
PR #14079

PR #14077
PR #14076

This comment was auto-generated by Graphite.

Current dependencies on/for this PR:

master

PR #13918

PR #14078

PR #14103   👈
PR #14095
PR #14094
PR #14080
PR #14079

PR #14077
PR #14076

This comment was auto-generated by Graphite.

Current dependencies on/for this PR:

master

PR #13918

PR #14078

PR #14103   👈
PR #14095
PR #14094
PR #14080
PR #14079

PR #14077
PR #14076

This comment was auto-generated by Graphite.


Training custom dataset

Hi there,
Seems that the code has being customize to train on synthetically generated data where you can decide that each batch sample has the same number of datapoints per cluster. i.e the K is uniform within the batch. How can you adapt the model to train on less uniform data?

This is a great question!
The code fully supports mini-batches where batch samples have different numbers of clusters (K), different numbers of data points in each cluster, as well as different total numbers of data points (N). However, we have yet to release an example demonstrating this use case (we'll do that soon).
You'll need to use model.forward_train_mask(...) rather than model.forward_train(...) as shown in the following lines:
https://github.com/aripakman/attentive_clustering_processes/blob/34ce5e5699be573098717f6bbc283733e062a0d9/acp/train_acp.py#L178
Here, the batch labels will be a list of length batch_size containing tensors of cluster labels for all batch samples. We use a List[Tensor] rather than 2D tensors because the number of data points in each sample may be different, but I think a 2D tensor of shape [batch_size, num_points] should also work. Note that you'll need to run labels = [relabel(x) for x in labels] before feeding the labels to the model, so that the first occurrence of each unique cluster ID is in ascending order.
Let us know if you have other questions.

thank you for the fast answer :) That solve most of my doubts
If each of the samples have a variable number of datapoints how would you represent that on data tensor. The labels are List[Tensor] as you pointed out, but data is a Tensor with dimensions [batch_size, num_points, feature_dimension]. Do you need to pad with 0s the shorter samples?

For graphs, both DGL and torch_geometric has a batch data structure to represent a batch of graphs, so that they can be processed more efficiently by the GNN encoder, see below:
https://github.com/aripakman/attentive_clustering_processes/blob/34ce5e5699be573098717f6bbc283733e062a0d9/acp/data_generator/sbm_beta_generator.py#L109
The output of the GNN is then transformed into a list of tensors of variable shape:
https://github.com/aripakman/attentive_clustering_processes/blob/34ce5e5699be573098717f6bbc283733e062a0d9/acp/models/acp_model.py#L244
Then we copy these tensors to a fixed-size tensor of shape [batch_size, max_num_points, feature_dimension] with padding, and use a binary mask tensor to represent the non-empty indices. The neural network will use the mask tensor for downstream computations.
https://github.com/aripakman/attentive_clustering_processes/blob/34ce5e5699be573098717f6bbc283733e062a0d9/acp/models/acp_model.py#L246-L253
If you're not working with graph data, you can concatenate the data tensors in the batch to shape  [total_num_points, feature_dimension]. The size of the labels will tell the model how to split the batch and create a mask tensor. Alternatively, a data tensor of shape [batch_size, max_num_points, feature_dimension] with padding should also work -- you'll need to skip the batch splitting operation enc_data_raw = enc_data_raw.split(Ns, dim=0).

Thanks, that worked!


Improve presentation of the repository

Improve the public impression of the project by setting up a straightforward github workspace.
Add 'About' Statement on landing page.
Add explanation text whereever needed to 'sell' our work to the public.

Closed for the first week, but stays at "To Do" because the presentation of the repo should be improved continuously.

Closed for the first week, but stays at "To Do" because the presentation of the repo should be improved continuously.


go-controller: Sync services.

Signed-off-by: Gurucharan Shetty<EMAIL_ADDRESS>

I gave it a round of testing. Please have a re-look.


farmmanagement packages always returns all farms iso the logged in user's farms

commit https://github.com/threefoldtech/jumpscaleX_threebot/commit/4957d9607f4c8f3cfe86dbff5a8938ed7b3e34ef

1 - i installed 3bot and run  j.tools.threebot.init_my_threebot
2 - then i go to farm management and install package
3- it gives me a white page , is this correct ?, i think should give me message like "now farm owned by your 3bot user  "

verified


Shareable is not used in this contract

good catch!

Love the standardization you bring, just trying to give back if I notice something while using your contracts! Keep up the good work! Your contracts will be a big part in the next version of https://settlemint.io/databroker/ !


Naming conflicts

Log shortcuts like:
#define debug(logId, message, ...) logger.log(logId, DEBUG, message, ##__VA_ARGS__)

are breaking other libraries which uses keywords like warning, debug.
In file included from from src/main.cpp:31:
.pio/libdeps/.../ESP Async WebServer/src/ESPAsyncWebServer.h:280:19: error: macro "warning" requires 3 arguments, but only 1 given
     const String& ASYNCWEBSERVER_REGEX_ATTRIBUTE pathArg(size_t i) const;

I would suggest making those definitions optional and disabled by default. Putting them to separate header file could be flexible solution. So everyone can define own aliases header file if needed.

Same experience here when using library TinyGSM in the same project with elog.

I moved it into its own header now.
You can include them by:
#include <ElogMacros.h>

That should fix it - if not you can open another issue


Weird glitchy render with the preview

TressFX 2.2 render : http://puu.sh/mKo82/21b2cdd9f6.jpg
TressFX 3.0 render : http://puu.sh/mKo9U/11de724e15.jpg
The hair on the 3.0 is glitchy, i had to zoom so it's easier to see.
Built at the same hour, on the same computer.

Thanks for the feedback. What card and what driver?
For driver version, I'm interested in the Driver Packaging Version. For pre-Crimson drivers, it's in Catalyst Control Center, Information -> Software. It will be a long number. For example: 15.201.1151.1008-151104a-296217E
In Crimson drivers, you get to the information in a different way. But if you are running Crimson, you can just say, "I'm running Crimson."
Thanks again.

Using a R9 290 Card
I'm running Crimson (16.1) with package :
Driver Packaging Version
15.301.1201-151223a-297971C

Thanks again. I'll look into it.

Yep having lots of issues with it as well. Running Crimson 16.1 hotfix with a 290 4gb card. No issues in games.
The preview of the bear here: https://raw.githubusercontent.com/GPUOpen-Effects/TressFX/master/amd_tressfx_viewer/media/Thumbnail.png
shows lighting correctly, but when trying to run it myself I see lots of issues as seen here:
https://youtu.be/-6roJowfmxI
Issues shown in video: when walking there are lots of flashs and black areas that appear. When not animating there are odd "wiggly" areas that I tried to zoom in on, but its also not clean like TressFx 2 demo.
Used Visual Studio 2015 for both, TressFx 2 looks same as OP, nice clean lines. TressFx 3 is very blocky and otherwise, glitchy looking as described and shown in the video above (video seems to be blurry until ~10 seconds in, not sure if thats just for me or youtube is still processing, but quality is normal after 10 seconds).

@jmackay
I believe the flashes of black that you're seeing are caused by the bear mesh clipping through the hair strands, which in turn is caused by the skinning animation and hair simulation being out-of-sync.
The "wiggly" areas are probably the result of numerical instability in the simulation. I was able to get rid of them on my system be increasing the Local shape matching iterations count (located under the Simulation Menu) to 20.
The "blocky" look is probably just the result of the default strand thickness value.  Try decreasing the Hair thickness value to 0.02.  Also, make sure that Strand Antialiasing is checked, and that Distance adaptive LOD is unchecked.
The hair simulation operates at a fixed frequency, which appears to be controlled by the target_frame_rate member of the TressFX_Desc structure.  The bear mesh skinning animation simply updates once-per-frame.
A quick hack that seems to work well enough is to force the hair simulation to also update once-per-frame.  In TressFXSimulation.cpp, find the TressFXSimulation::Simulate function and comment out the following lines:
if((m_elapsedTimeSinceLastSim < targetFrameRate) && !warp)
	{
	return S_OK;
	}

You'll also need to change
	pCSPerFrame->timeStep = targetFrameRate;

to
	pCSPerFrame->timeStep = fElapsedTime;

Please note that while the simulation still appears to be stable enough for the short bear fur, I haven't tested it on long human hair.  There is a warning in the comments about the simulation being sensitive to frame rate, so your results may vary. :)
Here's a quick screen capture of what the bear looks like on my system after implementing the aforementioned fixes:

Interesting thanks :), I also noticed that the change hair color option did absolutely nothing, so I don't think the color is being applied (which is also why they look like long thick strands instead of nice colored hair).
with full density and minimum thickness and supposedly green hair color (applied and then re-opened for screenshot)
http://i.imgur.com/LOPyIT1.jpg
Also trying to changing those lines seems to have fixed the shimmer issue, still looks funny but I think thats mostly just the textures not applying correctly.
I did also have to cast targetFrameRate to void:
(void)targetFrameRate;

to get it to build, since it was no longer being referenced.

@jmackay
I think that the bear's fur color is being read from a texture, since nothing happens when I change the color within the viewer either.
In your screenshot, it looks like one of the problems is that your hair strands are being rendered as fully opaque.  They also don't appear to be sorted correctly, as you can see the larger (closer) strands on the bear's front leg/torso being clipped by the smaller (farther) strands on its rear legs.
Here's a close up of what I see when using similar settings:

R7 360
Crimson 16.1.1 (15.301.1801.1001-160130a-298922E)
Windows 10 (Preview Build 14251.1000)
A side-by-side for comparison sake. Only built and run the viewer so far... just providing this to denote the 'out-of-the-box' is having some issues too (some similar).

Yep, anything we can do to fix the viewer? Really hurts the "Out of the box" look.
2.2

3.0

290 Crimson 16.1.1 hotfix feb 3rd
Windows 10
Visual Studio 2015 Update 1

I have the same artifacts with the Crimson Drivers and my HD7970.
With the Intel Graphics the artifacts are not appearing  (apart from the bear hear simulation, which is out of sync with the animation), so I guess it's a driver bug.

I'm new to TressFX but noticed in the shader (TressFxRender.hlsl) that there's a couple of macros that might affect the appearance.
#define SIMPLESHADING           // no specular term
#define SIMPLESHADOWING         // no filtering except PCF
#define SUPERSIMPLESHADING      // constant diffuse (doesn't change with light angle)
there's also KBUFFER_SIZE which is the number of samples to depth sort.
the VS project didn't seem to have a step to notice source changes -- the line I used to generate the .inc files was:
fxc /T ps_5_0  /E PS_KBuffer_Hair  /Fh  PS_KBuffer_Hair.inc   TressFXRender.hlsl

By the way it's been like a month, is there any news/fix @jstewart-amd ?

Apologies for the delay. I hope to push out a fix this week.

The original issue with hair rendering reported by @ExtReMLapin is fixed in 2734dce711db2b9c8af6eb42ce417fb956288dd1
Bear animation flashing is a separate issue. I hope to have another update for that soon. Leaving this issue open until then.

My quick attempt to improve the bear animation flashing, similar to what @starquail mentioned, caused issues with longer hair. This is going to need a deeper look. We are in the midst of the annual pre-GDC scramble, so I do not know if this will be resolved until after GDC.
Again, the original issue reported by @ExtReMLapin is fixed. I'm only talking about the bear flashing issue.

I suppose I should mention that if someone wants to take a shot at improving the bear flashing in a general way that does not negatively impact the simulation of longer strands, we accept pull requests. Talk to us first, though, to tell us what your plan is, and so that multiple people are not working on it simultaneously and independently.
See CONTRIBUTING.md for contribution guidelines.
Otherwise, it is next on our to-do list for TressFX (with the major caveat that progress may be stalled until after GDC).

Well, if I read the code correctly, the skinning transforms are applied to the guide hairs in the simulation, and the output positions of the guide hairs is in object space. I think instead the guide hairs should be relative to the respective bones/skinningTransforms, so they can be rendered at the correct location even when the simulation is completely disabled.
It might be that I am missing something, but It's hard to get an overview without any kind of documentation.

@mrgreywater said: "It's hard to get an overview without any kind of documentation."
I just added overview slides to amd_tressfx/doc. These slides contain information about how the skinning works (among other things).
There was already documentation for the viewer here: amd_tressfx_viewer/doc
And for the Maya exporter here: amd_tressfx_tools/MayaPlugin/doc

@jstewart-amd is there any plan on adding engine plugins samples like this one there

My proposal to fix the skinning issue:
Additionally to the skinningTransform matrices, generate the inverse matrices into another RWStructuredBuffer<Transforms> here: https://github.com/GPUOpen-Effects/TressFX/blob/master/amd_tressfx/src/Shaders/TressFXSimulation.hlsl#L1015#L1016
Apply this inverse matrix when finishing with the simulation, to make sure the strand positions are stored relative to the triangle: https://github.com/GPUOpen-Effects/TressFX/blob/master/amd_tressfx/src/Shaders/TressFXSimulation.hlsl#L377#L381
Apply the skinningTransform again when rendering the Strands: https://github.com/GPUOpen-Effects/TressFX/blob/master/amd_tressfx/src/Shaders/TressFXRender.hlsl#L298#L299
I don't know what the performance overhead would be, but it's the only good solution I see right now.

@jstewart-amd  works great thanks for fixing it!

@mrgreywater, the primary author of the TressFX simulation shaders is out of the office this week, but he's back on Monday. I'll be in full GDC scramble mode, but I'll try to coordinate with him to get this looked at next week.

@jmackay

works great thanks for fixing it!

No problem. Thanks for letting me know the fix worked for you. It's always good to get independent verification.

@ExtReMLapin

is there any plan on adding engine plugins samples

Well, we definitely recognize that having example integrations for the major engines would be useful. But we are not ready at this time to say one way or the other what our plans are for that sort of thing.

I fixed the bear issue as I proposed, by storing the positions (additionally) relative to the mesh surface. I still need to clean it up before I can create a PR, and it should be tested if it's faster to have the vertex positions stored twice (relative for drawing and absolute for physics), or recalculate the absolute values whenever the physics needs it (one additional matrix multiplication per access).

@jstewart-amd I think this issue is resolved or are there still outstanding issues? Looks like the other fix from @mrgreywater was merged so might want to close this or is something left?

There were several unrelated issues reported in this thread. The primary ones have been addressed and so, yes, I will close the issue.
Summary:

The issue from the original post reported by @ExtReMLapin was a driver regression. A shader workaround was submitted in 2734dce711db2b9c8af6eb42ce417fb956288dd1, and the underlying issue has since been fixed in the driver.
There are a few things going on in @jmackay's video from https://github.com/GPUOpen-Effects/TressFX/issues/1#issuecomment-175480442:

The original guide/follow setup on the bear made the fur look clumpy. This got cleaned up in 7da2e52a4c5d1394e1cb36db66e325a0abd3180f. Specically, the follow hair growing radius was increased from 0.2 to 1.2 in bear.tfxproj: https://github.com/GPUOpen-Effects/TressFX/commit/7da2e52a4c5d1394e1cb36db66e325a0abd3180f#diff-92cb88380cf91ab43da2c7b4d34a414e
The fur simulation was out of sync with the underlying model animation. This was addressed by @mrgreywater's pull requests: https://github.com/GPUOpen-Effects/TressFX/pull/6, https://github.com/GPUOpen-Effects/TressFX/pull/16
The specular lighting is "flashy". This is a different issue than the model clipping through the fur (i.e. different than the simulation/animation sync issue mentioned above). It is caused by a combination of things. It has been improved, but it is still there. I created a separate issue for it: https://github.com/GPUOpen-Effects/TressFX/issues/19
And then, in addition to the above-mentioned items, the video also has the rendering bug mentioned in the original post (which is fixed).

It was also mentioned that the color picker doesn't do anything for the bear. This is expected behavior, as the bear's fur color comes from the bear model texture. I created an issue to disable the color button in the UI when the color is coming from a texture, to avoid confusion: https://github.com/GPUOpen-Effects/TressFX/issues/18


Bagel Update 13

Bagel station was my first map I made for ss14 and it shows in a lot of the design. It has been updated significantly and many parts of the map were deleted and remade from scratch. The general layout and feel will be the same but you'll notice it's very different.
changelog
-the bridge has been remade with a mostly similar layout but with improvements to its shape and overall design.
-security has cannibalized R&D and takes up the entire block now. the prison is based off the 18th century design of the panopticon. perma has been moved into central bagel.
-science now occupies the westmost quadrant and is fit with R&D, robotics, toxins, artifact research, and a proper office for RD.
-the northern part of the map has been completely redone from scratch. atmos has been separated from engineering and put to the northwest. engineering is now much more spacious but all power sources are a lot closer together. this makes the threat of singulo a lot greater again. supermatter room connects atmos and engi but is unused for now. atmo takes after the marathon atmos design and should feel a lot better and less cramped than old bagel's.
-the chapel and dorms have been shifted southwest of their previous location.
-arrivals now has several connecting maints so people wont be cutoff from the rest of the station if something ahead is spaced
-bar now sports shutters and firelocks so the tenders dont get obliterated from bar bombings
-botany has been reorganized and now has a tool room
-chem has been scrunched up
-medical has received an overall touchup focusing on minimizing the massive lobby and putting more emphasis on patient care and doctor safety.
-cargo has been shortened significantly (sorry i was told to) and salvage now sits above the cargobay. the ore processor sits in the wall between them.
-evac has been modified for evac shuttle
-grav gen is now connected to the main portion of bagel but is in a similar location
-theater has been moved to be right above the bar.
-libraries layout has changed but still sports a DND table
-atmos is fully equipped gas wise. (gotta rip the bandaid off some time)
-hop bedroom has been shrunk and office expanded
-all heads of staff now have a proper desk to talk to employees at
-significantly reduced amounts of lights on map and in maints especially
ill now provide some candid photos
bridge

perma

the panopticon

toxins and R&D

cargo lobby

engineering

atmos front desk

botany and chem

left half of medbay

theater above the bar

i hope you guys enjoy the update as much as i did making it

Window to grav-gen room have no grille.

Might be a bit too easy to break into gravgen and the HoS office.
Morgue is a bit too thin, little walk room, but it's likely fine.

gravgen is about the same level of fortified as marathon and packed except now its even closer to sec, morgue i can definitely expand rn. i dont see why people would break into hos room personally unless they havent spawned and taken their weapon yet so i dont think thats a big deal in most cases, lemme expand morgue tho

Are these functional. Trit miner doesn't make sense, plasma is questionable but honestly worth a shot I guess?

logic here was that we have to re add these at some point so might as well rip the bandaid off now that we have atmo techs

Plasma's good. Trit can simply be made.


Support generate crds

Please briefly answer these questions:

what problem are you trying to solve? (or if there's no problem, what's the motivation for this change?)

Generate crds,  it can be used other case and other language, i supose major is golang.
In the future, this file need to released simultaneously with the operator if the crds have changed.

what changes does this pull request make?

It's create a new binary to generate crds, and the second idea is move it  to build.rs. i can update it to build.rs if it's necessarily.
CI is failed but feature is ready for review.
Since I'm not a rust expert, feel free to comment.
lan@lan:$ cargo run --bin crdgen
...
     Running `target/debug/crdgen`
lan@lan:$ ls
CODE_OF_CONDUCT.md  Cargo.toml  LICENSE    build     operator-k8s         sidecar  tests  xlineoperator.xline.cloud_xlinecluster.yaml

are there any non-obvious implications of these changes? (does it break compatibility with previous versions, etc)

cc @iGxnon

Consider writing them in the build.rs file instead. Then, utilize some compile-time environment variables (such as CRD_VERSION) to generate YAMLs?

This PR is not need any more due to the xline-operator is rewriting with golang, check https://github.com/xline-kv/xline-operator/pull/40
closing...


[DONOTMERGE] debug spglib in stable octopus

copied changes in https://github.com/fangohr/octopus-in-docker/pull/8 inorder to make it easier to debug the issue with spg lib on released version of octopus which uses old spglib and seems to work out of the box.
MR NOT TO BE MERGED

looks like this version doesnt link to libsymspg at all, hence no problem


Override WagtailImageForm

I need to override the WagtailImageForm to implement SVG support on my site.
Normally, I would just extend the model Field and override the formfield method to inject a custom form_class.  Wagtail  bypasses this in formfield_for_dbfield, forcing fields with the name file to always use the WagtailImageField
As a Django developer, I find this frustrating. It breaks the OO DX I expect as a Django developer and makes a usually trivial task impossible.
Describe the solution you'd like
An option that would work for this specific case would be...

implement a wagtail.images.models.ImageField that extends django.db.models.ImageField that  overrides the  formfield method to injects wagtail.images.field.WagtailImageField into the form_class.
remove the if db_field.name == "file": from wagtail.images.forms.formfield_for_dbfield

A more generic option that would provide form_class injection more generally to all fields would be

implement wagtail.model.WagtailField that extends django.models.Field by adding a form_class argument to the __init__ method and override the default implementation of the formfield method to inject the form class into the Field.formfield implementation.
Update all wagtail fields to extend WagtailField instead of Field to inherit the form customization behavior.
Implement wagtail.images.models.ImageField that extends WagtailField and django.db.models.ImageField
remove the if db_field.name == "file": from wagtail.images.forms.formfield_for_dbfield and clean up any additional code that could be streamlined using the form_class injection technique.

The collection field seems to need similar handling on images as well and might be a case for the latter approach. Additionally, it could be something worth pursuing upstream in Django.

I figured out how to monkeypatch it locally in the meantime in case anyone else has a similar issue.

class MyApp(AppConfig):
    name = "Inelegant"

    def ready(self):

        """
        monkeypatch formfield_for_dbfield
        we're trying to fix this upstream, https://github.com/wagtail/wagtail/pull/9089
        this is a temporary fix until then
        """
        import wagtail.images
        from wagtail.images.forms import formfield_for_dbfield

        def mokeypathed_formfield_for_dbfield(db_field, **kwargs):
            print("mokeypathed_formfield_for_dbfield", db_field, kwargs)
            # Check if this is the file field
            if db_field.name == "file":
                return db_field.formfield(**kwargs)

            return formfield_for_dbfield(db_field, **kwargs)

        wagtail.images.forms.formfield_for_dbfield = mokeypathed_formfield_for_dbfield

Flagging we also have an RFC for svg support in Wagtail - https://github.com/wagtail/rfcs/pull/77
I know this is a generic issue but any feedback on the specific problem of svg support would be useful to add to that RFC

I thought I had already left my feedback on that RFC. I went and looked and it was sitting there pending. Done., https://github.com/wagtail/rfcs/pull/77#pullrequestreview-1065681621

@lb- I wouldn't mind some feedback on the more generic WagtailField approach or the ImageField specific approach. I'm focused on the former for now since I don't know what kind of can of worms I might be opening hitting all the model fields. there may be reasons for these functions I'm just not seeing.

I think your reasoning is sound here @dopry but I am not super familiar with that code so maybe others can chime in.
My only thought is that it may be written this way to work better with custom image models.


Cannot exit convert wallet view

There is no way to back out of converting a wallet (from portfolio view) besides closing the app.
Add a X button top left and a heading up the top "Enable multi-wallet" for this view. The same as it is in the wallet > Enable multi wallet view.

fixed


Access external webpages

im unable to view webpages that are not on my local machine, is it possible to use this extension to access external webpages? in my case i've to access a webpage on hosted on a webserver inside a vpn

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 94630cc3-dd1a-7c4d-1784-c1d8bd7f16b4
Version Independent ID: 94630cc3-dd1a-7c4d-1784-c1d8bd7f16b4
Content: Getting in touch with the Microsoft Edge DevTools Extension team - Microsoft Edge Development
Content Source: microsoft-edge/visual-studio-code/microsoft-edge-devtools-extension/contact-devtools-extension-team.md
Product: microsoft-edge
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Yes, external sites are supported, like in Edge.

In VS Code, in Activity Bar on left, click Microsoft Edge Tools icon.
Click the Launch Instance button.  The Edge DevTools tab and the Edge DevTools Browser tab open in VS Code.
In VS Code, in the Edge DevTools Browser tab, in the Address bar, replace the default URL by microsoft.com, and then press Enter.  The external site appears, and the Address bar shows: https://www.microsoft.com/en-us/

Thanks for reaching out @orlandobianco, and thanks @mikehoffms for providing an answer.
I'm going to close this for now, since the question was answered. But please do comment here again if the problem isn't resolved.
Also, for bugs and feature requests to the extension itself (rather than feedback about the docs), then please open issues on this repository instead: https://github.com/microsoft/vscode-edge-devtools/


[question] in a plugin, how to add js text first then include js file

I am writing a nuxt plugin for piwik and can't get the plugin to work in the way I think would be best.
The default example code to include Piwik on your webpage is as follows:
<!-- Piwik -->
<script type="text/javascript">
  var _paq = _paq || [];
  /* tracker methods like "setCustomDimension" should be called before "trackPageView" */
  _paq.push(['trackPageView']);
  _paq.push(['enableLinkTracking']);
  (function() {
    var u="//piwik.example.com/";
    _paq.push(['setTrackerUrl', u+'piwik.php']);
    _paq.push(['setSiteId', '1']);
    var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0];
    g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'piwik.js'; s.parentNode.insertBefore(g,s);
  })();
</script>
<!-- End Piwik Code -->

So you have to set setTrackerUrl and setSiteId before loading the piwik.js file. If you do this in plugin.js it works fine, but I think it would be cleaner to do this in index.js to avoid adding js src files
during runtime.
Unfortunately I am unable to make sure that after rendering the code is still loaded in this order.
What I tried:

call this.options.head.script.push in index.js, one time to add the _paq.push's with innerHTML and one time to add the src to piwik.js.

  let config_js = '_paq.push(["setTrackerUrl", "' + (options.trackerUrl || options.piwikUrl+'piwik.php') + '"]);'
  config_js += '_paq.push(["setSiteId", "' + options.siteId + '"])'
  this.options.head.script.push({
    innerHTML: config_js, type: 'text/javascript'
  })
  this.options.head.script.push({
    src: options.scriptUrl || options.piwikUrl+'piwik.js',
    async: true,
    defer: true
  })

This doesnt work because using innerHTML encodes double & single quotes to htmlentities and afaik you can only disable encoding with vue-meta for the whole script group (and maybe interfering with other plugins)

<script data-n-head="true" type="text/javascript">_paq.push(["setTrackerUrl", "//piwik.example.com/piwik.php"]);_paq.push(["setSiteId", "1"])</script>

set _paq.push's at beginning of plugin.js and add piwik.js deferred in index.js with this.options.head.script.push({ defer: true }).

This doesnt work because the script tag for piwik.js will have a defer tag but is not added at the bottom of the document (e.g. after window.__ NUXT__) while the _paq.push's are in /_nuxt/app.js at the very bottom of the page.

Are there any other possibilities to keep the javascript in the required order that I havent thought of?

In the page that you need the script, add a script property to the head() function.
export default {
  ...
  head() {
      return {
          script: [{
              src: "the-piwik-script.js"
          }]
      }
  }
}

@see
https://nuxtjs.org/guide/views/#pages
https://github.com/declandewet/vue-meta#script-object

@pi0 @RichAyotte Thanks but this is not what I am asking / looking for, I am writing a nuxt plugin so at this stage I am not looking for solutions that requires adding code to every page. E.g. I want to have the same functionality as the Google Analytics plugin, so when the piwik plugin is included in nuxt.config.js the piwik page statistics code should be added to all pages by default.
I know its my fault for explaining too much and thus having too much text in this issue, but I'd really would like to find a solution for use within my plugin code.


--hub-name seems to be mandatory parameter but is listed as an optional

On this page, --hub-name is listed under the optional parameters.  I think its mandatory, although maybe via the --login or something it wouldn't be needed if used instead?  It still feels that one of them is required.
I looked at here also listed hub-name as optional but I'm almost positive its required, so if what I'm raising is indeed an issue and not my az tool naivete then should look at other places.
My repro of not having --hub-name
C:\developer\local> az iot hub module-identity create --device-id $deviceId --module-id $filterModule
DLL load failed while importing win32file: The specified module could not be found.
Please provide an IoT Hub entity name (via the '--hub-name' or '-n' parameter) or IoT Hub connection string via --login...

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 5c84a1ae-e98a-c7e0-9b40-ae61ab6a0560
Version Independent ID: 7732a739-03ab-ca9c-404e-6849ec2c2602
Content: az iot hub module-identity
Content Source: latest/docs-ref-autogen/iot/hub/module-identity.yml
Service: iot-hub
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

This is something by design: we require users to provide either --hub-name or --login parameters so the --hub-name is not required as long as --login is provided.
We will improve the help section to make this distinction clearer.

route to service team


Registration generates Error message

When registering, user receives this error message flagging syntax

Able to register
Received activation email
Able to activate and login

Same on test


EPG Update

telly release with the issue:

Last working telly release (if known):
Operating environment (Docker/Windows/Linux/QNAP, etc.):

Description of problem:
EPG doesn't update automattacly in Plex. I'm not sure if this is a telly or Plex issue. I have telly update the EPG and it didn't pull anything. I restarted telly which redownload the epg from the provider then stuff showed up. Should I just have telly reboot every night to download the new EPG?
Contents of telly.config.toml [if you're using a version above 1.1]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

Command line used to run telly [if applicable]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

Docker run command used to run telly [if applicable]:

REMEMBER TO DELETE ANY CREDENTIALS IN CONFIG FILES OR COMMAND LINES

telly or docker log:

Additional information:

Closing since this seems to be sorted.


How to start the 5959 service in KVM-VDI

Hi,
Am installed the wesockyfi and am also changed ws in the run.js file but still am get the black screen while am click the html5 console there is no firewall running in that server i can get the spice console through the remore-virt but html5 only showing black screen am check all the closed issues but my scenario is different
while am run the netstat command for 5959 port is not running in my server how could i start the port service please tell me.

Did you start websockify server?

./run --token-plugin TokenFile --token-source /tmp/kvm-vdi 5959 --daemon
this is the command to start the websockify. am right?

Yes. Try running it without --daemon option. You will get output to std, when trying to connect with HTML5.

yes am did but same presist

yes it is working because the websockify am clone the websockify again its working


Phone Number showing in status bar while call is in progress

Did you follow all the instructions as specified in the Twilio Quickstart repositories? - Yes
RN Version - 0.66.1
react-native-twilio-programmable-voice version - 4.4.0
What device are you using? - OnePlus 8 (Android 11)
The app is open and the calling screen is in focus (Outbound call)
Is there any relevant message in the log? - No
Step to reproduce

Place a outbound call using any device
Pull down the status bar, you can see the contact number is displayed

Found a round about but not an ideal solution
Sending name in To and number in number.
await TwilioVoice.connect({                 To: this.props.route.params.buyerName,                 Number: this.props.route.params.numberToCall,             })


Operator is not eligible for application

Problem:
WARNI keep-ecdsa: operator is not eligible for application [0x14dC06F762E7f4a756825c1A1dA569b3180153cB] registration.go:138
It's been about a day since the launch of ECDSA node and I still see this error
I'm configure my ECDSA node according this manual https://gist.github.com/afmsavage/8fc19937a6b263f05c3e215d8860629c
Client version: keepnetwork/keep-ecdsa-client:v1.1.2-rc
-staked 300K test KEEP
-authorized contracts in dasboard
Port 3919 is available if i check it from another ip
nc -t -vv $EXTERNAL_IP 3919
Connection to MY_IP 3919 port [tcp/*] succeeded!
/multistream/1.0.0

Log file: ecdsa_node_log.txt
Config file:
[ethereum]
  URL = "wss://ropsten.infura.io/ws/v3/$INFURA_TOKEN"
  URLRPC = "https://ropsten.infura.io/v3/$INFURA_TOKEN"

[ethereum.account]
  Address = "0xc2C5b1F115b4c82fB0c1ce6208AcD7089e3B506D"
  KeyFile = "/mnt/keep-ecdsa/keystore/keep_wallet.json"

[ethereum.ContractAddresses]
  BondedECDSAKeepFactory = "0xe7BF8421fBE80c3Bf67082370D86C8D81D1D77F4"

[SanctionedApplications]
  Addresses = ["0x14dC06F762E7f4a756825c1A1dA569b3180153cB"]

[Storage]
  DataDir = "/mnt/keep-ecdsa/persistence"

[LibP2P]
  Peers = ["/dns4/testnet.keep-client.hashd.dev/tcp/3920/ipfs/16Uiu2HAmJsBiNVFNxsJ27NSQEByv39B1M7AKx5FrAc1htqYhHGhU","/ip4/<IP_ADDRESS>/tcp/3919/ipfs/16Uiu2HAmEZpkf1Td8rSBMmgPoa66si2kJLb83Rd2eztJ6f5oLvhp","/dns4/ecdsa-2.test.keep.network/tcp/3919/ipfs/16Uiu2HAmNNuCp45z5bgB8KiTHv1vHTNAVbBgxxtTFGAndageo9Dp",
"/dns4/ecdsa-3.test.keep.network/tcp/3919/ipfs/16Uiu2HAm8KJX32kr3eYUhDuzwTucSfAfspnjnXNf9veVhB12t6Vf","/dns4/bootstrap-1.ecdsa.keep.test.boar.network/tcp/4001/ipfs/16Uiu2HAmPFXDaeGWtnzd8s39NsaQguoWtKi77834A6xwYqeicq6N"]
Port = 3919
 AnnouncedAddresses = ["/ip4/$EXTERNAL_IP/tcp/3919"]

[TSS]
  PreParamsGenerationTimeout = "2m30s"

I have the same issues with all my ECDSA nodes in Ropsten. The nodes staked 300K test KEEP each and a large amount of Ropsten ETH (200-300). Node restart does not help to resolve this warning.

Experienced the same issue operator is not eligible for application [0x14dC06F762E7f4a756825c1A1dA569b3180153cB]

Thanks for reporting, we're looking into it.  To be clear bonded > 100 eth, means you have 100 eth available for bond, or 100 ETH that's already been bonded?

Thanks for reporting, we're looking into it. To be clear bonded > 100 eth, means you have 100 eth available for bond, or 100 ETH that's already been bonded?

already bonded

Thanks for reporting, we're looking into it. To be clear bonded > 100 eth, means you have 100 eth available for bond, or 100 ETH that's already been bonded?

Both > 100 eth: already bonded and available to bond, look at screenshot, for example (ecdsa operator 0x6b2535194feb6f5834a3579889a702d4498aa5cc)

Thanks for reporting it. I looked at the operator address provided by @c29r3 and I see it's now both eligible for the application and registered to the application. I have also looked at the operator address provided by @k0kk0k and I see it's now eligible for the application but not yet registered (maybe the client is not running).
I think the issue here is related to #506. We accidentally tweaked the price to be very high when we meant it to be very low, so most bonds became insufficient. When we opened a deposit under the very high price, the bond expectations in the sortition pool skyrocketed and a lot of clients became no longer eligible for tBTC pool. Over the weekend, we fixed the price (tx 0xe8275ee1d935e949678354cc4020200f8235382775e7ae2524d312c23d859646) and I think it helped - we had 12 operators in the pool this morning and I see we have 16 now and new deposits opened.
I'll wait for confirmation from @c29r3, @k0kk0k, and @JaviAnibarro - if everything works as expected now, I would consider this issue as fixed. I am also very interested if your clients automatically joined the pool once they became eligible or if you had to restart them - please see #500.

I'll wait for confirmation from @c29r3,

That's right, today I rebooted the ECDSA operator and it successfully registered (reboot didn't help before).

I am also very interested if your clients automatically joined the pool once they became eligible or if you had to restart them

No, it can't join automatically. Manual register via js script or docker container restart ecdsa

@c29r3 Can you please post your client logs from the moment before and after the restart in #500? I can't replicate the issue about the client not registering in the pool automatically and any hints are helpful.

@pdyraga this is what my operator shows me before and after restarting the node. It changed from operator is not eligible for application into this automatically.

@c29r3 Can you please post your client logs from the moment before and after the restart in #500? I can't replicate the issue about the client not registering in the pool automatically and any hints are helpful.

Such messages were today before manual registration by a script (I reboot the rest of the ecdsa nodes). I think that you will not be able to reproduce this problem. I noticed these messages appeared after someone did a lot of mint in a row
https://discord.com/channels/590951101600235531/723194152925397062/733267579405074512

ecdsa_log_2020-07-21.zip

the message Operator is not eligible for application was automatically disappear on my nodes. a restart was not required. I attach a log file, but it will be difficult to find the moment where this change occurred.
logs.tar.gz

Now when i try to create a deposit (mint), the smart contract returns the following error:
execution reverted: Insufficient signer bonds to cover setup fee
0x08c379a00000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000002c496e73756666696369656e74207369676e657220626f6e647320746f20636f766572207365747570206665650000000000000000000000000000000000ed4e00

transaction was sent from: 0x9c4d6bB6f874f3D522fc9f45034DFfB2dAF383be

Sorry folks, we think we know what happened here:

Late last week, I made an off-hand suggestion to reduce the apparent ETHBTC price on Ropsten to reduce the bond requirement, allowing more deposits to be opened while requiring less testnet ETH from operators.
Unfortunately, because I was doing this while doing several other things, I actually increased the ETHBTC price 2 orders of magnitude instead of decreasing it. This led to a situation where most available bonds were insufficient to cover any deposits.
We then fixed this, reducing the ETHBTC price as intended. At this point, however, the sortition pool that handles choosing operators was set to expect a higher bond amount, and this amount adapts based on new deposits---so we needed to be able to open a deposit with the lower amount to let all operators rejoin.
We juiced up a few of our operators to get past that hurdle. Here, we saw new deposits failing to open due to a different issue (“Insufficient signer bonds to cover setup fee”). This was where I finally devoted more than “off hand” time to the problem, and remembered the fact that our bottom limit on bonds isn't just limited by the apparent ETHBTC price, but also by the opening cost of a deposit.

We've reverted the apparent ETHBTC price to what it was originally (which is a realistic amount based on relative mainnet prices from a couple of months ago), so new instances of “operator is not eligible for application” should not be related to this issue.
Thanks for bearing with us y'all… We've been focused on getting the relevant bits for a redeploy out the door, so we've had our attention reduced on the community and the Ropsten deploy the last few weeks. We expect that to start changing this week.


Discounted amount is not displaying in invoice and invoice pdf at both customer end and admin end.

Framework Version: 0.1.6

Framework Version: 0.1.6

Fixed


SOLR-16564: Migrate to using DEFAULT_TEST_COLLECTION_NAME constant through out tests

https://issues.apache.org/jira/browse/SOLR-16564
Description
Following up from #1149 where we started replacing "collection1" strings with the DEFAULT_TEST_COLLECTION_NAME constant, this continues that process.
Solution
Use constants where it makes sense.
If a test was interaction with a collection1 and a collection2, then I left it, as I found that more readable.
Tests
Please describe the tests you've developed or run to confirm this patch implements the feature or solves the problem.
Checklist
Please review the following and check all that apply:

[ ] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[ ] I have created a Jira issue and added the issue ID to my pull request title.
[ ] I have given Solr maintainers access to contribute to my PR branch. (optional but recommended)
[ ] I have developed this patch against the main branch.
[ ] I have run ./gradlew check.
[ ] I have added tests for my changes.
[ ] I have added documentation for the Reference Guide

This is starting to appear to be a sisphean task...  106 test files..  admittedly, not everyone needs the constant....

Okay, I think I found a few more places, and at this point think I am done..  I don't know that this is the most impactful of PR's, but I'd love to merge it and call it done and close the JIRA if I can get a LGTM...

I think I question the value in this.  "collection1" is friggin pervasive.  We all know what it is.  To the vast majority of tests, the test doesn't actually care what the collection it's going to create is named.  It's whatever.

l'll add a disclaimer that, I've observed to some developers, use of constants is like some sort of religion.  I am most definitely not religious about any coding practice.  I think sometimes constants are a needless indirection to discern a value (not very relevant to this PR) and sometimes a bit more verbose as well.  Yet another import statement.

Just not feeling it....


Duplicate Sub Nuget published?

Brief bug description
There appears to be a problem with your nuget publish I think.
There is Kentico.Kontent.Management.Helpers published to nuget (latest version 2.0.1) published Dec 10.
Then there is also Kentico.Kontent.Management version 2.0.1 also published to nuget.
Which is the ideal version? They appear to be the same except that the .Helpers version might be .NET Full framework only? BUt hard to tell as they point to the same repo (this one) which appears to be for .NET Core?
A bit confused.

Hey @xantari , thanks for pointing this out!
Kentico.Kontent.Management  -> Management SDK
Kentico.Kontent.Management.Helpers -> A helper library for generating edit URLs (links leading to specific content items in app.kontent.ai)
I tried to make it more clear in the readme: https://github.com/Kentico/kontent-management-sdk-net#kentico-kontent-management-net-sdk


[deps] Add support for django 3.2 and 4.0 #263

~This PR drops support for Python 3.6~
Closes #263

Will there be a new release soon, with this fix?

Hi @stianjensen there should be a release soon once some more issues are fixed

@stianjensen the release is out.


Adds "aad administrativeunit list" command. Closes #5569

Closes #5569
The new command requires permission AdministrativeUnit.Read.All.

@Jwaegebaert Should I rename AadAdministrativeUnitListCommand to AadAdministrativeunitListCommand.
I missed that the name of the class should follow some convention.

Hi @MartinM85, thanks for your submission, that's fast! We'll review this ASAP.
Regarding the naming: I think in this case it should be AadAdministrativeUnitListCommand. As it's two words.

Hi @martinlingstuyl, with the name AadAdministrativeUnitListCommand, one test has failed. https://github.com/pnp/cli-microsoft365/actions/runs/6532988278/job/17738145375

Hi @MartinM85, I think you must add 'administrative' and 'unit' to the .eslintrc.cjs...

Merged manually, thank you! 👏🚀

Hi @MartinM85, if you like I can mention you in a linkedin post I'll be making on the topic of this release. Do you have a linkedin account?

Also: if you have an emailaddress, I'll add you to the contributors list in the project.

Hi @MartinM85, if you like I can mention you in a linkedin post I'll be making on the topic of this release. Do you have a linkedin account?

Hi @martinlingstuyl, why not. Here is a link to my linkedin profile: https://www.linkedin.com/in/martin-macháček-a8662086/

It turns out there are so many Martin Macháčeks that you'll need to accept my invite so that you'll pop up above the others 😀

If only linkedin just accepted the handle... that would have been enough....

Ok thanks @MartinM85, I've added a reference to you to my post.


Update manage-device-identities.md

@MicrosoftGuyJFlo

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


Fix SystemModeler fmus getting terminated before reaching end of simulation

When running the FMI Cross-Check tests for SystemModeler the FMU's will be terminated bevore reaching the end of the simulation.
When disabeling debugLogging we get:
julia> main("test/fmi-cross-check/fmus/2.0/me/linux64/SystemModeler/5.0/ControlledTemperature/ControlledTemperature.fmu")
Extracted FMU to /mnt/d/ubuntu/julia/JuliaFMI/test/fmi-cross-check/fmus/2.0/me/linux64/SystemModeler/5.0/ControlledTemperature/FMU_ControlledTemperature
┌ Warning: SimpleType "Real" not implemented
└ @ Main /mnt/d/ubuntu/julia/JuliaFMI/src/modelDescriptionParsing.jl:76
typesPlatform: default
FMI version: 2.0
Unload FMU
ERROR: Solution got terminated before reaching end time.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] main(::String) at /mnt/d/ubuntu/julia/JuliaFMI/src/FMUSimulator.jl:627
 [3] top-level scope at none:0

and with debug Logging:
julia> main("test/fmi-cross-check/fmus/2.0/me/linux64/SystemModeler/5.0/ControlledTemperature/ControlledTemperature.fmu")
Extracted FMU to /mnt/d/ubuntu/julia/JuliaFMI/test/fmi-cross-check/fmus/2.0/me/linux64/SystemModeler/5.0/ControlledTemperature/FMU_ControlledTemperature
┌ Warning: SimpleType "Real" not implemented
└ @ Main /mnt/d/ubuntu/julia/JuliaFMI/src/modelDescriptionParsing.jl:76
typesPlatform: default
FMI version: 2.0
Unload FMU
ERROR: StackOverflowError:
Stacktrace:
 [1] fmi2NewDiscreteStates!(::Ptr{Nothing}, ::Ptr{Nothing}, ::EventInfo) at /mnt/d/ubuntu/julia/JuliaFMI/src/FMIWrapper.jl:1386
 [2] top-level scope at none:0

I have no clue why though.

It's still not working but the FMU is not compliant with current FMI Cross-Check rules, so we simply don't test it any more. OMSimulator gets a segmentation fault as well, so it's probably a problem of the FMU.
See cffb3d4ba2613ef812953c8353fe4a794a9fc1b1


runtime: "attempt to execute system stack code on user stack" during heap scavenging

From the linux-amd64-nocgo builder (https://build.golang.org/log/abbb70348ec45659c8032defde341c61e90ec995):
fatal error: attempt to execute system stack code on user stack

goroutine 8 [running]:
runtime.throw(0x65ad83, 0x32)
	/workdir/go/src/runtime/panic.go:774 +0x72 fp=0xc000030610 sp=0xc0000305e0 pc=0x430562
runtime.morestackc()
	/workdir/go/src/runtime/stack.go:1315 +0x27 fp=0xc000030630 sp=0xc000030610 pc=0x44b117
runtime.stackfree(0xc000492000, 0xc000494000)
	/workdir/go/src/runtime/stack.go:422 +0x35c fp=0xc000030638 sp=0xc000030630 pc=0x448b2c
runtime.allocm(0xc00001e500, 0x65e5f8, 0x1)
	/workdir/go/src/runtime/proc.go:1517 +0xdb fp=0xc000030678 sp=0xc000030638 pc=0x43556b
runtime.newm(0x65e5f8, 0xc00001e500)
	/workdir/go/src/runtime/proc.go:1841 +0x39 fp=0xc0000306a8 sp=0xc000030678 pc=0x435d39
runtime.startm(0x0, 0xc000000c01)
	/workdir/go/src/runtime/proc.go:2006 +0x12a fp=0xc0000306d8 sp=0xc0000306a8 pc=0x43630a
runtime.wakep(...)
	/workdir/go/src/runtime/proc.go:2087
runtime.ready(0xc000000c00, 0x0, 0xd5731d01)
	/workdir/go/src/runtime/proc.go:666 +0x12f fp=0xc000030728 sp=0xc0000306d8 pc=0x43359f
runtime.wakeScavenger()
	/workdir/go/src/runtime/mgcscavenge.go:236 +0x85 fp=0xc000030750 sp=0xc000030728 pc=0x422d55
runtime.bgscavenge.func1(0x0, 0x0, 0x0)
	/workdir/go/src/runtime/mgcscavenge.go:295 +0x20 fp=0xc000030760 sp=0xc000030750 pc=0x45e6b0
runtime.timerproc(0x806140)
	/workdir/go/src/runtime/time.go:294 +0x6e fp=0xc0000307d8 sp=0xc000030760 pc=0x44fabe
runtime.goexit()
	/workdir/go/src/runtime/asm_amd64.s:1375 +0x1 fp=0xc0000307e0 sp=0xc0000307d8 pc=0x463cd1
created by runtime.(*timersBucket).addtimerLocked
	/workdir/go/src/runtime/time.go:166 +0x10e

The failure message is the same as in #30591, but the entry here seems to be through runtime.wakeScavenger rather than runtime.LockOSThread so the root cause may differ.
CC @mknyszek @aclements

Looking into it.

OK so ready() needs to be called on the system stack.
Either wakeScavenger should be go:systemstack or ready should be goready. I'm not sure whether it actually matters which one we do. No other part of wakeScavenger needs the system stack and I have a slight preference for allowing it to be run mostly anywhere, though in some cases (like SetGCPercent) this means we'll go onto the system stack twice. It doesn't happen in any place that's particularly performance sensitive.
@aclements, @randall77, WDYT?

I'd rather just put things on the system stack that need it. It serves as useful documentation, if nothing else. If that means we have to switch stacks twice for non-performance-sensitive code, so be it.

@mknyszek @rsc do you know when this fix might appear in Go 1.13?
We're running into this occasionally in some integration tests. In what sorts of scenarios would this panic appear? (I don't know much about Golang GC). How does this panic get triggered?

@gopherbot, please open a backport to 1.13.


Updating to an incompatable version.

Did it never occur to the update software team to check to see if a machine will be able to run the update??!!?
The app sure checks to see if it will run on the machine.  And it wont.  I'm in the middle of work, and the app politely asks for an update, no information about the update, and which promptly says it wont run on the machine.   Its a breaking update, and no information about that.
 And is the responsibility of the developer.
Not every machine is the same as the developers machine. We've had 'updates' for 50 years. We've been checking for requirements updates for 50 years. We have had changelogs for 50 years, and we have the ability to present any breaking changes to the user BEFORE they install the software.  I can't decide which.
"Why are you using that version?"

Red herring. Doesn't matter. The update broke a thing that was working. It's stupid simple to check that it will break a thing, and it should do it, so that it doesn't break a thing that is working.  The idea that "this is not a concern"  or "a user problem" if prevalent, and is built on a logical flaw.

Whats insidious that is that it happened from inside the very app that was working.  It allows a user to click a button INSIDE the app, that destroys the app.   Bad design.

@zaphodddd sorry about the bad experience caused by the auto-update. we will revisit our auto update process.
I added a section to the troubleshooting document for instructions to revert to an older version. It should help you revert to a previous compatible version for a resolution to your issue.

@zaphodddd I'm sorry to hear about your bad experience with JupyterLab Desktop. The macOS version auto-updates without checking Electron's compatibility with your OS version and without displaying the release notes, which state that macOS 10.15 or later is required for JupyterLab Desktop 4.0.7-1.
All contributors to Jupyter projects are expected to follow the Jupyter Code of Conduct, which includes being considerate and respectful. Referring to the application's developers as "lazy, ignorant, or arrogant" for not checking whether an updated version is compatible with macOS 10.14 is not being considerate or respectful. As an open source project, we would gladly consider a pull request to add an OS compatibility check to the upgrade check. Please let us know if you need any assistance with your patch.


Create pull_request_template.md

Describe the changes
Related Jira tickets
My Ticket Number
Developer check list
General

[ ] Is the PR as small as it can be?
[ ] Has the Jira ticket been updated with any relevant comments?
[ ] Is the README up to date?
[ ] Has the POM been updated for the latest versions of dependencies?
[ ] Has the code been double-checked against main?
[ ] Does the code adhere standards in this repository including SonarQube

Testing

[ ] Do the code changes have unit and integration tests with code coverage > 80%?
[ ] Has the code been tested locally and/or passed the API Karate tests on Tilt?
[ ] Are all the test data resources up to date?

Release preparation

[ ] Have these changes been included in a release ticket?
[ ] Are changes required to the docker-chs-development deployment or test data?
[ ] Are any changes required to the environment added to chs-configs?

Notes to the tester

Soon we can add "check mandatory test cases"


Missing .gitignore means unwanted files

I'm doing the App Indexing codelab and I've noticed that all the sample code here contains local.properties files... You get warning from AS when importing the code because of course the SDK location is not the one defined in that file (points to some guy's Linux home folder). The repo also contains some .gradle and .idea folders and .iml files than shouldn't be there. Please clean up the repo.

Hopefully a PR will help speed along the process ;)


perf(vm): Fix VM performance regression on CI loadtest

What ❔
Fixes VM performance regression on CI loadtest introduced in https://github.com/matter-labs/zksync-era/pull/2760.
Why ❔
Changes in the VM interface made the VM eagerly clone compressed bytecodes if compression hasn't failed. Compressed bytecodes aren't used during sandboxed VM execution in the API server (the sandbox only checks that compression is successful).For new VMs, bytecodes can be borrowed from the VM state, which is what this PR does using Cow.
Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[x] Documentation comments have been added / updated.
[x] Code has been formatted via zk fmt and zk lint.

Not sure whether it's just wishful thinking, but the changes in the load test config seem to make the load test more stable (decreasing the number of accounts and concurrent API requests; increasing the number of in-flight txs and randomizing polling interval between polling tx status).


Hotfix for compatibility with latest ESPHome versions

For some reason, something changed that broke the vector initialisation of sensor types. This PR removes that initialisation and it seems to fix compilation with newer ESPHome versions.

Thanks!


k8s stateful cluster

I'm trying to spin up a rabbitmq cluster on kubernetes with persistent disks.
I create three deployments. (PetSets are not possible in my environment right now, but we use the same logic to archive this) And 4 services. One for each pod and one loadbalancing service. I found some PR that added k8s_address_type to enable PetSets, so i tried to added this as well, but it did not work. What am i doing wrong?
Pods:
p-tracking-broker-multi-r1-1-99375647-mm08c     2/2       Running   1          1m
p-tracking-broker-multi-r1-2-1739282980-tdlzt   2/2       Running   1          1m
p-tracking-broker-multi-r1-3-3379190313-ztdk3   1/2       Error     3          1m

Services:
p-tracking-broker-multi-r1-ci     <IP_ADDRESS>   <none>        4369/TCP,5671/TCP,5672/TCP,15672/TCP,25672/TCP,9108/TCP   12m
p-tracking-broker-multi-r1-ci-1   <IP_ADDRESS>    <none>        4369/TCP,5671/TCP,5672/TCP,15672/TCP,25672/TCP,9108/TCP   12m
p-tracking-broker-multi-r1-ci-2   <IP_ADDRESS>   <none>        4369/TCP,5671/TCP,5672/TCP,15672/TCP,25672/TCP,9108/TCP   12m
p-tracking-broker-multi-r1-ci-3   <IP_ADDRESS>   <none>        4369/TCP,5671/TCP,5672/TCP,15672/TCP,25672/TCP,9108/TCP   12m

Envs (for all deployments the same)
env:
            - name: HOSTNAME
              value: p-tracking-broker-multi-r1-ci-{index}
            - name: RABBITMQ_USE_LONGNAME
              value: 'true'
            - name: AUTOCLUSTER_LOG_LEVEL
              value: debug
            - name: AUTOCLUSTER_TYPE
              value: k8s
            - name: LANG
              value: en_US.UTF-8
            - name: MY_POD_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
            - name: AUTOCLUSTER_LOG_LEVEL
              value: debug
            - name: AUTOCLUSTER_CLEANUP
              value: 'true'
            - name: CLEANUP_INTERVAL
              value: '60'
            - name: CLEANUP_WARN_ONLY
              value: 'false'
            - name: RABBITMQ_ERLANG_COOKIE
              value: goPuIuuBulD028f9CaOTgj0nK47XwX0v6X1aalBMt4E=

Rabbitmq config:
...
,{autocluster, [
    {k8s_service_name, "p-tracking-broker-multi-r1-ci"},
    {k8s_address_type, "hostname"}
]}
...

              RabbitMQ 3.6.8. Copyright (C) 2007-2016 Pivotal Software, Inc.
  ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
  ##  ##
  ##########  Logs: tty
  ######  ##        tty
  ##########
              Starting broker...

=INFO REPORT==== 29-May-2017::12:35:26 ===
Starting RabbitMQ 3.6.8 on Erlang 19.3
Copyright (C) 2007-2016 Pivotal Software, Inc.
Licensed under the MPL.  See http://www.rabbitmq.com/

=INFO REPORT==== 29-May-2017::12:35:26 ===
node           : rabbit@p-tracking-broker-multi-r1-ci-1
home dir       : /var/lib/rabbitmq
config file(s) : /etc/rabbitmq/rabbitmq.config
cookie hash    : L2eV63REmmsnMRSA8SgHVQ==
log            : tty
sasl log       : tty
database dir   : /var/lib/rabbitmq/mnesia/rabbit@p-tracking-broker-multi-r1-ci-1

=INFO REPORT==== 29-May-2017::12:35:30 ===
autocluster: log level set to debug

=INFO REPORT==== 29-May-2017::12:35:30 ===
autocluster: Using k8s backend

=INFO REPORT==== 29-May-2017::12:35:30 ===
autocluster: Delaying startup for 3434ms.

=INFO REPORT==== 29-May-2017::12:35:33 ===
autocluster: Starting k8s registration.

=INFO REPORT==== 29-May-2017::12:35:33 ===
autocluster: GET https://kubernetes.default.svc.cluster.local:443/api/v1/namespaces/p/endpoints/p-tracking-broker-multi-r1-ci

=INFO REPORT==== 29-May-2017::12:35:34 ===
autocluster: Response: [{ok,{{"HTTP/1.1",200,"OK"},
                             [{"date","Mon, 29 May 2017 12:35:34 GMT"},
                              {"content-length","1525"},
                              {"content-type","application/json"}],
                             "{\"kind\":\"Endpoints\",\"apiVersion\":\"v1\",\"metadata\":{\"name\":\"p-tracking-broker-multi-r1-ci\",\"namespace\":\"p\",\"selfLink\":\"/api/v1/namespaces/p/endpoints/p-tracking-broker-multi-r1-ci\",\"uid\":\"2a1debd1-446b-11e7-8721-42010a840146\",\"resourceVersion\":\"27367780\",\"creationTimestamp\":\"2017-05-29T12:34:31Z\",\"labels\":{\"microservice\":\"tracking\",\"revision\":\"r1\",\"site\":\"multi\",\"stage\":\"p\",\"subservice\":\"tracking-broker\",\"zone\":\"europe-west1-c\"}},\"subsets\":[{\"addresses\":[{\"ip\":\"<IP_ADDRESS>\",\"nodeName\":\"gke-live-europe-west1-c-pool-2-3aa68a69-zltw\",\"targetRef\":{\"kind\":\"Pod\",\"namespace\":\"p\",\"name\":\"p-tracking-broker-multi-r1-1-3851573885-lhftf\",\"uid\":\"2a87ffcd-446b-11e7-8721-42010a840146\",\"resourceVersion\":\"27367713\"}},{\"ip\":\"<IP_ADDRESS>\",\"nodeName\":\"gke-live-europe-west1-c-pool-2-3aa68a69-cjm5\",\"targetRef\":{\"kind\":\"Pod\",\"namespace\":\"p\",\"name\":\"p-tracking-broker-multi-r1-2-1537235587-7zzmf\",\"uid\":\"2befb46f-446b-11e7-8721-42010a840146\",\"resourceVersion\":\"27367664\"}},{\"ip\":\"<IP_ADDRESS>\",\"nodeName\":\"gke-live-europe-west1-c-pool-2-3aa68a69-kbn3\",\"targetRef\":{\"kind\":\"Pod\",\"namespace\":\"p\",\"name\":\"p-tracking-broker-multi-r1-3-3516881545-kq2j1\",\"uid\":\"2cd33735-446b-11e7-8721-42010a840146\",\"resourceVersion\":\"27367668\"}}],\"ports\":[{\"name\":\"bro-4369\",\"port\":4369,\"protocol\":\"TCP\"},{\"name\":\"exp-9108\",\"port\":9108,\"protocol\":\"TCP\"},{\"name\":\"bro-25672\",\"port\":25672,\"protocol\":\"TCP\"},{\"name\":\"bro-5671\",\"port\":5671,\"protocol\":\"TCP\"},{\"name\":\"bro-15672\",\"port\":15672,\"protocol\":\"TCP\"},{\"name\":\"bro-5672\",\"port\":5672,\"protocol\":\"TCP\"}]}]}\n"}}]

=INFO REPORT==== 29-May-2017::12:35:34 ===
autocluster: Registering node with k8s.

=INFO REPORT==== 29-May-2017::12:35:34 ===
autocluster: Registered node with k8s.

=INFO REPORT==== 29-May-2017::12:35:34 ===
autocluster: Discovered ['rabbit<EMAIL_ADDRESS><EMAIL_ADDRESS>
=ERROR REPORT==== 29-May-2017::12:35:34 ===
autocluster: Can not communicate with cluster nodes.

=INFO REPORT==== 29-May-2017::12:35:34 ===
Memory limit set to 2048MB of 70484MB total.

=INFO REPORT==== 29-May-2017::12:35:34 ===
Disk free limit set to 1000MB

=INFO REPORT==== 29-May-2017::12:35:34 ===
Limiting to approx 1048476 file handles (943626 sockets)

=INFO REPORT==== 29-May-2017::12:35:34 ===
FHC read buffering:  OFF
FHC write buffering: ON

=INFO REPORT==== 29-May-2017::12:35:34 ===
Database directory at /var/lib/rabbitmq/mnesia/rabbit@p-tracking-broker-multi-r1-ci-1 is empty. Initialising from scratch...

=INFO REPORT==== 29-May-2017::12:35:34 ===
    application: mnesia
    exited: stopped
    type: temporary

=INFO REPORT==== 29-May-2017::12:35:34 ===
Waiting for Mnesia tables for 30000 ms, 9 retries left

=INFO REPORT==== 29-May-2017::12:35:34 ===
Waiting for Mnesia tables for 30000 ms, 9 retries left

=INFO REPORT==== 29-May-2017::12:35:34 ===
Waiting for Mnesia tables for 30000 ms, 9 retries left

=INFO REPORT==== 29-May-2017::12:35:34 ===
Priority queues enabled, real BQ is rabbit_variable_queue

=INFO REPORT==== 29-May-2017::12:35:34 ===
Starting rabbit_node_monitor

=INFO REPORT==== 29-May-2017::12:35:34 ===
Management plugin: using rates mode 'basic'

=INFO REPORT==== 29-May-2017::12:35:34 ===
msg_store_transient: using rabbit_msg_store_ets_index to provide index

=INFO REPORT==== 29-May-2017::12:35:34 ===
msg_store_persistent: using rabbit_msg_store_ets_index to provide index

=WARNING REPORT==== 29-May-2017::12:35:34 ===
msg_store_persistent: rebuilding indices from scratch

=INFO REPORT==== 29-May-2017::12:35:34 ===
Adding vhost '/'

=INFO REPORT==== 29-May-2017::12:35:34 ===
Creating user 'tracking-broker'

=INFO REPORT==== 29-May-2017::12:35:34 ===
Setting user tags for user 'tracking-broker' to [administrator]

=INFO REPORT==== 29-May-2017::12:35:34 ===
Setting permissions for 'tracking-broker' in '/' to '.*', '.*', '.*'

=INFO REPORT==== 29-May-2017::12:35:34 ===
started TCP Listener on [::]:5672

=INFO REPORT==== 29-May-2017::12:35:34 ===
autocluster: (cleanup) Timer started {60,false}

=INFO REPORT==== 29-May-2017::12:35:34 ===
Management plugin started.
Note:
This fork is currently not under active development. rabbitmq/rabbitmq-autocluster is the new temporary home for this project, including new releases. Please consider that fork as well.
Please check this full example that use  StatefulSet in the rabbitmq/rabbitmq-autocluster repo.  StatefulSet is PetSets renamed starting form K8s 1.5

@Gsantomaggio Thats great! I got it working with the PetSet example. I also made the mistake to use different hostnames for the pods. They need to be the same.
But I have one more question:
As far as I know, rabbitmq saves it's database to /var/lib/rabbitmq/mnesia/.
This usually leads to problems with pods if they restart. This is why I think, that
- name: RABBITMQ_NODENAME
   value: "rabbit@$(MY_POD_IP)"

is not a good idea or example. Is there a way to use rabbit@<service_name> ? I tried to use K8S_ADDRESS_TYPE hostname with RABBITMQ_NODENAME rabbit@p-tracking-broker-multi-r1-ci-{index} , but it is not working. Any suggestions?

Node database directory can be anything and is orthogonal to RABBITMQ_NODENAME (which is what you are referring to). The example can override it to be more resilient to IP changes (since that's kind of the point here), see RabbitMQ docs.

@michaelklishin is followed your suggestion and write the database to a specifc folder via RABBITMQ_MNESIA_DIR.
I ran a performance test and deleted two of the rabbit pods. The rabbits are not rejoining the cluster.  Now. I get the following Error, that is not really meaningful to me:
kubectl logs p-tracking-broker-multi-r1-2-1927507952-qvcg4 broker -f

=INFO REPORT==== 29-May-2017::14:47:49 ===
    application: mnesia
    exited: stopped
    type: temporary

              RabbitMQ 3.6.8. Copyright (C) 2007-2016 Pivotal Software, Inc.
  ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
  ##  ##
  ##########  Logs: tty
  ######  ##        tty
  ##########
              Starting broker...

=INFO REPORT==== 29-May-2017::14:48:08 ===
Starting RabbitMQ 3.6.8 on Erlang 19.3
Copyright (C) 2007-2016 Pivotal Software, Inc.
Licensed under the MPL.   It seems that I've run into a similar error as you posted above. Have you solved this since?

This plugin was forked by the RabbitMQ team and is now part of RabbitMQ. More information can be found @ https://github.com/rabbitmq/rabbitmq-autocluster


Features/assets

Added in all of the assets to the project and ensured that all of the links were functional.

Correction. I added the assets for the email, github, and linkedIn icons as well as a profile Picture for the info component.


feat: add http proxy support

Relies on: https://github.com/nitrictech/nitric/pull/467 to then bump the nitric version.
Can be reviewed but not merged

Can you rebase this onto the preview features branch? This will allow us to release HTTP proxies as a preview feature in the CLI initially.

LGTM, let's get the dependencies updated once the core functionality is released on the core repo.

A couple of issues:

on hot reload, ports keep incrementing
not found paths should return 404
nitric run does not seem to work with a connection refused error (double check)

All this was tested on windows 11 with latest node rc