Remove redundant variable.

Do we really need this var?

Codecov Report

Merging #37 (8ff9326) into master (0afdf87) will not change coverage.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##              master       #37   +/-   ##
===========================================
  Coverage     100.00%   100.00%
  Complexity       853       853
===========================================
  Files             34        34
  Lines           1599      1598    -1
  Branches         256       256
===========================================
- Hits            1599      1598    -1

Impacted Files
Coverage Δ

.../statistics/distribution/NakagamiDistribution.java
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

The code is meant to be self-documenting. A Nakagami distribution is parameterised by mu and omega; the gamma distribution by shape and scale. You can sample from a Nakagami using a Gamma. Removing the variable does not enhance the code and will not change efficiency. Any caller who requires a sampler will be spending negligible time constructing a sampler and all the time using it.


Remove the rootfs patcher

Is your feature request related to a problem? Please describe.
The upstream eirini helm chart uses a "rootfs patcher" to download newer versions of the rootfs.
Describe the solution you'd like
We can't download things from the internet like this, so we should not be using the patcher.
There is a setting to disable it.
After doing so, also check to see what it does for upgrading apps to the new version of a rootfs, and create a new story, detailing if we need to implement a Job that does something similar on KubeCF upgrades.

Draft PR made for this: #801
Planning to test local using minikube SA, verify that job is gone, and that smoke works.

Minikube testing ok. confirmed that job and service account are gone (and present without the change).
Smoke has one test failure, same independent of the change. As such smoke is considered working.

Eirini Notes
These notes came out of investigating the rootfs patcher and its operation.
Summary

The patcher just patches statefulsets, changing the labels on the
sts itself and its pod template (rootfs version to use).

This change triggers redeployment through the standard sts
controller. The generic Eirini mechanism for app deloyment
involved in that then uses the new rootfs version, and also
(apparently) (triggers to) pulls the necessary image.

To avoid this internet access see if we can

prefill whatever store is used with the necessary image,
and if that then prevents the actual download.

Not seeing the need for a new KubeCF specific job.
Eirini is a sub chart of KubeCF AFAIK/CT.
We should be able to run a helm upgrade on the KubeCF chart
which does not change anything in KubeCF itself, only in Eirini.

General architecture
Eirini apparently uses two namespaces, .Release.Namespace and
.Values.opi.namespace, for its control plane, and the applications,
respectively.
The control plane contains Eirini's deployment and associated pods,
etc. The other is where the statefulsets for applications deployed via
Eirini are placed and run. Properly separated from the control plane.
Rootfs
All cloundfoundry applications are based on a rootfs image which
contains the basic tooling shared across all. This is separate from
buildpacks and the image they will use/insert for the specific kind of
application (php, python, ...).
Eirini provides its own set of rootfs images, outside of
cloudfoundry's cflinuxfsNNN, or SUSE's opensuse/sle images.
See cloudfoundry-incubator/eirinifs for the repository and releases.
I have not determined yet if the images for the Eirini chart come with
a baked-in rootfs tarball matching the initial/default version.
Even so, AFAICT from descriptions given Eirini will certainly pull a
rootfs tarball from the net (github) when it does not have the
requested version. This likely involves the bits service.
Rootfs Version
The version of the rootfs to use for applications managed by Eirini is
specified via .Values.global.rootfs_version. The current default
v75.0.0. The most current release is v150.0.0.
This information is templated into the Eirini kube definitions and
from there into various config files, command line arguments,
etc. This means that the version is pretty much baked into the running
processes in one kind or other.
Updating the Rootfs version
Given the information in the preceding section changing/updating the
rootfs version to use involves a helm upgrade. In other words, set
.Values.global.rootfs_version to a new value, then helm upgrade
the entire Eirini deployment. This restarts all the necessary
pods/processes of the control plane which will then contain/know the
new version.
An application started after this upgrade is given the new version,
and the system retrieves the tarball from the internet as part of
that. The limitation of this is that it only updates the Eirini
control plane, and only affects applications started after.
Existing applications are not touched. Further, restarting, even
restaging such will not make a difference. The rootfs version is baked
into the statefulsets representing them, and a simple restart/stage
does not change that.
Patcher
The patcher comes in to patch(sic) the limitation mentioned in the
preceding section.
It is a job which is run when Eirini is deployed, or upgraded. During
initial deployment this job does not matter, it will not find any
application to modify and thus simply ends.
Of the job's two containers the init container only ensures that
Eirini's bits service/deployment exists and is ready. As it will be
needed to pull/store the new tarball for the new version.
The action container talks to the application namespace, locates the
statefulsets, i.e applications, and modifies the labels for
statefulset and pod template to contain the new rootfs version.
Any application/statefulset from before the upgrade to the new version
will see an actual change, thus the sts controller will terminate the
existing pods of the application, and then restage and redeploy new
pods. In contrast to the simple restage (see preceding section)
however the changed label ensures that the new rootfs version is now
used, as desired.
KubeCF
It is my understanding that Eirini is deployed as a sub chart of KubeCF.
That means, should I understand helm correctly, that a helm upgrade
of KubeCF can be used to perform an upgrade of Eirini as well, or just
of Eirini. Dependent on which .Values are modified.
IMHO if we can solve the rootfs image download done by Eirini then
nothing speaks against using the standard rootfs patcher coming with
Eirini.
Issues
Internet access
The patcher does not pull anything by itself. It simply triggers a
redeployment of applications using the old version, in a manner which
then causes the regular Eirini staging/deployment mechanisms to pull
the new rootfs image from the world.
If we wish to prevent this internet access as part of a rootfs version
change I believe that we should investigate how the rootfs image is
pulled and stored, and if we can prefill the store (bits ?) with the
image needed before triggering the helm upgrade.
bits-waiter --namespace misdocumentation
This is the command used by the patcher's init container to check and
wait for the bits service to be present and ready.
As the bits service is part of the control plane is has to access the
namespace .Release.Namespace.
This is configured correctly in command line, role, and role binding.
Contrariwise, the application sources incorrectly claims that the
associated --namespace option references the
Namespace where eirini runs apps.
This is only a nit where the option is misdocumented. Use and
configuration are all ok.

Note #806

@f0rmiga @viovanov
Thulio mentioned in the standup that the eirinifs in use is distributed as part of the kubecf setup, right ?
So in normal operation there will not be an update of the eirinifs version ... And we do not plan to update the eirinifs between kubecf releases ?
So version updates for eirinifs would match (be synced to) kubecf releases ? ...
If yes ... I still don't believe we would need our own rootfs patcher ... A kubecf release with an eirinifs bump could simply activate the eirini rootfs patcher during the update, then deactivate it again after it has down its thing. I.e. the helm upgrade ... to the new kubecf version would actually be multiple commands instead of single.
Thoughts ?

Closing this now, #808 is the followup to look into the underlying download issue


Suggestion: Initial State

not the end of the world but Podedit uses <target state="needs-adaptation"> would be nice to be able to specify this on the command line ..
Thanks for the awesome tool

xliffmerge uses the correct states specified within the xliff specs here: http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html. It might be poedit that is not respecting the correct states. Have you tried if poedit works better with xliff 2.0?

I havent... but this is a good suggestion. I guess the docs have been updated for version 8 and i had not refereed to them https://angular.io/guide/i18n#output-options

The main problem with this spec is, that it is a little bit theoretical. How should a tool know wether a translation needs non textual information review an what does it mean?
And in xliff2 they totally changed the allowed states.
At the end the translator only needs to know wether he has to look at the translation or not.
So for xliffmerge I decided to only use the basic states to keep it simple.


Add issue template

Signed-off-by: Erica Windisch<EMAIL_ADDRESS>

@ewindisch I'd prefer something more structured that will give us more info than what we might get with this version. Serverless has a good template going:
https://github.com/serverless/serverless/blob/master/.github/ISSUE_TEMPLATE.md
I like the split bug/feature report sections, and asking about versions etc in additional data.


Implement transport compression

I implemented transport compression.
I keep code difference small as much as I can.
I split changes to some commits so that it is easy to review.
I explain detail.
~- 0206648: Change nio-websocket-client to my fork.~
~This commit is submitted as this PR https://github.com/vapor/nio-websocket-client/pull/4~
~It solves problems them.~
~- WebSocket binary frame support~
~- Fix bug that WebSocket stream lost sometimes.~

b0f6909: Set TLSConfiguration if URL has wss: scheme.
8238f94: Pass URL to websocket.
It fix bug that query string parameters such like compress does not work at all.
b0923b4: Implement some CodingKeys to parse message from Discord server.
~- c3ff2ef: Implement Sword.request.~
8c1333e: Fix simple bug that use wrong variable.
~- 246f2dd: Implement logic that recreate zlib stream context when socket reconnect.~
~This PR add didConnect method in GatewayHandler to do this.~

I'd be willing to take b0f6909, 8238f94, b0923b4, and 8c1333e. I'd prefer to stay depending on vapor's repo, I have some changes to request that I have locally that I want to push soon, and I'd really like to fix zlib if you don't mind (I might ditch it in favor of something else maybe).

Thanks to check.
I rebased PR to pick these 4 commits up and dropped others.
I will open issues about dropped topics to tell that you recognize these problems for other library users.
When your changes to be shared, I close them.


MAINT: Trigger CircleCI for latest numpydoc release

Numpydoc just cut a new release, let's make sure our doc builds properly with it.

Looks like xref works properly in param lists
https://12350-1301584-gh.circle-artifacts.com/0/dev/generated/mne.Epochs.html#mne.Epochs
Merging just to make sure the full doc builds (it should)


Expense not showing in 'ready to pay' when it should be

Describe the bug
This expense did not show up under "ready to pay" even though it was ready to pay. The user had to contact support or I would never had seen it.
Expected behavior
The expense should have appeared in the list under the "ready to pay" filter.
Screenshots
The expense is payable:

But nothing is showing up here:

@alanna in this expense, you say that you had to reduce the total slightly to cover paypal fees.
Do you think the problem could be related to that?
Now that it's paid, it's difficult to troubleshoot.

I don't think it's due to the paypal fees situation, because we often have expenses where there isn't enough to cover fees come up in 'ready to pay'. I don't think the system checks that until you press 'Pay' and if there's not enough to cover fees it throws an error.

Here's another example. This one has not been paid yet because we're waiting on an updated invoice.
https://opencollective.com/volteuropa/expenses/8082
I think in both cases the amount of the expense was the full balance of the Collective so maybe that's a clue?
@znarf can you have a look at this please? If expenses don't show as ready to pay they will be missed.

Here's another example that wasn't showing up in ready to pay so I didn't know about it until the user contacted support upset by the delay.
This is a big problem because it's going to cause expenses to be missed. Can it please be investigated?

@alanna Sure. If you want us to investigate, please don't pay the expense so that we can have a look at the live data. We'll act quickly so you can pay the expense after ~24 hours.


Time entries not commited when new task added in session

Steps to reproduce:

Start titr, make some time entries, commit
Type 'config' to open configuration file
Add a new task, save and close
Add new time entries with new task
Commit new time entries
Type 'today' to view new entries

Expected behavior:

New time entries committed
New time entries show up in today's log

Resulting behavior:

Time entires do not show up in today's log

Investigation:

Need to write unit test to show that this is indeed a problem
Look at edit_config() function in titr_main.py. Claims to reload the configuration, but maybe isn't working.
Make sure that the hours aren't being recorded and they just aren't showing up under 'today' command.

Note that the new task type does show up with the ls command in titr, so the configuration seems to be reloaded successfully.


Is dup working properly?

Given
v1 = Daru::Vector.new(1.upto(5).to_a)
df1 = Daru::DataFrame.new(v1: v1)

I would expect that dup would create a new dataframe object with new vectors.  However, if I recode the vector in df1, the vector in df2 is changed too.
df2 = df1.dup

df1[:v1].recode! { |v| v * 2 }
df2[:v1] == df1[:v1]

Returns true when I would expect it to return false.
I can get the result I want if I dup each vector individually.  But this is cumbersome when I've got a larger dataframe.
df2 = df1.dup
df2[:v1] = df1[:v1].dup

df1[:v1].recode! { |v| v * 2 }
df2[:v1] == df1[:v1]

Returns false as expected.

Ok we're using to_a in dup and I just realized that when you're using Array#to_a returns the same Array and not a duplicate.
Adding a dup ahead of the to_a should fix this. Could you send me a PR? Also add a test?
Thanks for reporting.


Event handle_link_up should trigger the setup of an failover path

Hi,
Depending on the topology and the link down/up events, it may happen that no failover path is found (there is no path minimally disjoint from the current path):
Jan 30 17:15:58 2ff3d06b16b7 kytos.napps.kytos/mef_eline:WARNING evc:788:  Failover path for EVC(c9ea3a86c99b4e, my evc1) was not deployed: No available path was found

However, the topology may change later, and a new link becomes UP, making it possible to find a failover path. Mef_eline should take that opportunity to set up the "pending" failover path (i.e., the EVC is eligible to have a failover path, but it hasn't yet because no minimally disjoint path was previously found).
It would be interesting to also take a link_up event as an opportunity to optimize the failover path, setting up a new one that has better disjointness than the current one (or maybe leveraging another Napp to do this kind of optimization).

Italo, excellent idea, I've marked this as enhancement and priority_medium (feel free to adapt the priority accordingly if you wish), depending how things are going on 2023.1 we can include later on in this scope.


Switches, Radio Buttons, Checkboxes, Tests (#8) (#21) (#22)

Closes #8, closes #21, and closes #22.

Coverage decreased (-10.3%) to 89.655% when pulling 5bcea695dd89b06dbd32bbbc5560164b0a989a89 on checkbox into 8950fb5450863f1183b329d2b6cf8509c11380e0 on master.


Simplify connectors and connection references across environments

We have several connectors for the same service and severla connection references for the same connectors.
It might be good to simplify tbhis and only depend on 1 connector per service and 1 connection reference per connector or app.
Also, we should remove any connections made by any account different than the bot's.
However, this redudnancy does not represent a masive impact in the performance of the apps, so this would be low priority.

Done!


Monaco Text Editor

Checklist:

[ ] Apply Basic Changes to panels

[ ] LogViewer
[x] OperationCodeEditor
[x] OperationDepEditor
[x] TabbedTextEditor
[x] SerializeEditor

[x] Add Support for different themes, via contextmenu

[x] Add support for keybindings

It is to be noted that the current LogViewerWidget doesn't print ANSI colors correctly.
Python terminal(Bash Shell)

Output in deepforge:

Can you share the raw text before it is rendered?

The raw text is the following:
\033[31;1;4mHello\033[0m

Ah, I see. The first one is using underlines and other SGR parameters; it currently only supports colors and expected there to be only two options. This should be pretty easy fix but could be fixed in it's own PR.

I am marking this active. There is one issue left to sortout: Somehow, 2 editor workers are being assingned when viewing stdout in LogViewerWidget.
Also, following issues will stem and should be addressed after this is merged:

Integrate python language server and code completion support. Sources and providers are already available at https://github.com/umesh-timalsina/monaco-webgme-viz
Integrate Emacs?
Add a ANSI text rendering via Monarch or any other decorators? I am not sure if it is even possible via Monarch.

I am still seeing the following warning :/

This PR only is part one of the two needed to close #571. This Introduces Monaco Text Editor, which has support for a language server protocol.


BusyHandler problem

I am setting Connection.busyTimeout and Connection.busyHandler but don't seem to be able to handle database locking in a particular scenario I am testing.  I have two processes connecting to the database.  If you look at the iOS device log entries below, I was expecting the times in the busyHandler to be separated by about 5 seconds in time but you can see that are almost all at the same instant.  Am I setting this up wrong?
Here is the code for setting up the busyTimeout and busyHandler:
        dateFormatter = DateFormatter()
        dateFormatter.dateFormat = "y-MM-dd H:m:ss.SSSS"
        connection.busyTimeout = 5
        connection.busyHandler({ (tries) -> Bool in
            let date = self.dateFormatter.string(from: Date())
            self.logMessage("busyHandler: tries = \(tries) time = \(date)")
            if (tries >= 5) {
                return false
            }
            return true
        })

Here is what I see in the iOS device log:
Mar 29 09:59:33 FileProvider(libswiftFoundation.dylib)[2296] : busyHandler: tries = 0 time = 2018-03-29 9:59:33.6720
Mar 29 09:59:33 FileProvider(libswiftFoundation.dylib)[2296] : busyHandler: tries = 1 time = 2018-03-29 9:59:33.6720
Mar 29 09:59:33 FileProvider(libswiftFoundation.dylib)[2296] : busyHandler: tries = 2 time = 2018-03-29 9:59:33.6730
Mar 29 09:59:33 FileProvider(libswiftFoundation.dylib)[2296] : busyHandler: tries = 3 time = 2018-03-29 9:59:33.6730
Mar 29 09:59:33 FileProvider(libswiftFoundation.dylib)[2296] : busyHandler: tries = 4 time = 2018-03-29 9:59:33.6730
Mar 29 09:59:33 FileProvider(libswiftFoundation.dylib)[2296] : busyHandler: tries = 5 time = 2018-03-29 9:59:33.6730
Mar 29 09:59:33 FileProvider(libswiftCore.dylib)[2296] : Fatal error: 'try!' expression unexpectedly raised an error: database is locked (code: 5): file /BuildRoot/Library/Caches/com.apple.xbs/Sources/swiftlang/swiftlang-9<IP_ADDRESS>/src/swift/stdlib/public/core/ErrorType.swift, line 181

As I have continued to test I realize that if I don't set a busyHandler, the busyTimeout seems to do the trick.  My questions are:

How are you supposed to use the busyHandler?
Why does the database lock result in a fatal error?

I can't speak for SQLite.swift, but generally in SQLite, busy timeouts are a kind of busy handler. So you have to chose: set a busy timeout, or set a custom busy handler. But you can't do both.
For more information, see https://www.sqlite.org/c3ref/busy_timeout.html

There can only be a single busy handler for a particular database connection at any given moment. If another busy handler was defined (using sqlite3_busy_handler()) prior to calling this routine, that other busy handler is cleared.

Yes, they are two different things but only one is active at a time, this needs clarifying in the documentation


Question about prediction

Hi Caff,
Could you explain this output:
0 Prediction: 2 Odds diff: 0.11324374429110817
2 Prediction: 0 Odds diff: -0.24205590011481948
3 Prediction: 0 Odds diff: 0.07680052518844604
4 Prediction: 0 Odds diff: 0.1709744695757256
5 Prediction: 0 Odds diff: 0.21310876174406573
5 Prediction: 1 Odds diff: 0.12287358726773945
6 Prediction: 2 Odds diff: 0.13119223288127357
7 Prediction: 2 Odds diff: 0.4968955679248167
8 Prediction: 1 Odds diff: 0.2426253722773658
10 Prediction: 0 Odds diff: 0.36622321605682373
Is this the 10 games of the fixtures for the premier league, right?
but where in the prediction about Home winner, Draw, Away winner?
Cheers!

0 is home
1 is draw
2 is away
is that right?

Hi,
Yeah that's right; 0 is home win, 1 is a draw and 2 is away win.
Thanks for bring that to my attention, I'll make that clearer when I next update this repo.


Bugfix dns testcases.

Issues associated with this PR
Your PR should present related issues you want to solve.
Solutions
You should show your solutions about the issues in your PR, including the overall solutions, details and the changes. At this time, Chinese is allowed to describe these.
UT result
Unit Test is needed if the code is changed, your unit test should cover boundary cases, corner cases, and some exceptional cases. And you need to show the UT result.
Benchmark
If your code involves the processing of every request, you should give the Benchmark Result.
Code Style

Make sure Goimports has run
Show Golint result

Codecov Report

Merging #1170 into master will increase coverage by 0.13%.
The diff coverage is 66.48%.

@@            Coverage Diff             @@
##           master    #1170      +/-   ##
==========================================
+ Coverage   56.18%   56.32%   +0.13%
==========================================
  Files         268      274       +6
  Lines       25540    25889     +349
==========================================
+ Hits        14350    14582     +232
- Misses       9816     9907      +91
- Partials     1374     1400      +26

Impacted Files
Coverage Δ

pkg/config/v2/upstream.go
68.91% <ø> (ø)

pkg/proxy/downstream.go
36.33% <0.00%> (+0.19%)
:arrow_up:

pkg/proxy/proxy.go
7.75% <0.00%> (-0.13%)
:arrow_down:

pkg/types/constant.go
0.00% <0.00%> (ø)

...filter/stream/flowcontrol/stream_filter_factory.go
58.33% <58.33%> (ø)

pkg/filter/stream/flowcontrol/stream_filter.go
58.62% <58.62%> (ø)

pkg/network/dns.go
69.04% <69.04%> (ø)

pkg/upstream/cluster/strict_dns_cluster.go
72.28% <72.28%> (ø)

pkg/filter/stream/flowcontrol/callbacks.go
75.00% <75.00%> (ø)

pkg/upstream/cluster/cluster.go
82.30% <100.00%> (+1.34%)
:arrow_up:

... and 9 more

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 92a078e...66d1c39. Read the comment docs.


Julia "available" kernel's default.nix not reflecting most recent IJulia rev

Hello - just to point out that the documentation as it stands doesn't work perfectly for getting a Julia kernel up and running. If you add the IJulia kernel without specifying the version (as suggested in: https://jupyterwith.tweag.io/how-to/#kernels) then it currently defaults to rev 6TIq1, whereas the default in kernels/available/julia/default.nix is ijuliaRev ? "AQu2H". This causes an error when running the notebook via nix run.

Hey thanks for submitting this issue. We stumbled upon this recently as well and it has to do with the version of IJulia that is installed. When the kernel was created, IJulia version 1.23.3 was the latest and that corresponds to AQu2H, but now version 1.24.0 is the latest and that puts it under 6Tiq1. I'm not sure how Julia determines that mini hash.

Yes, actually it wasn't obvious to me where that mini-hash comes from either, I've asked on Julia discourse and there's an answer there: https://discourse.julialang.org/t/source-for-the-5-character-hash-in-home-julia-packages-pkgname/92793/3

Nice find!
After looking at the code, I don't think there is a nice way to fix this with the way the kernel is currently setup. Julia is the only stateful kernel we have and there isn't a way to inspect the users folder for which version of IJulia is installed. I've updated the repo so it uses the newer 6TIq1 hash but this is just a bandaid till we can use a reproducible version.
We've looked at using Julia2Nix.jl in the past. Will have to revisit this after a the next update.

Hey @harris-chris
I'm adding the following to the How To page under the "Julia Kernel" section.

If there is anything else I can help with, please let me know. Otherwise, feel free to close out the issue.


code action window size too small on launch

Describe the bug
Code action preview window width is not enough on launching :Lspsaga code_action, need to move up or down once till it gets right.
After launching code action:

After moving up or down:

Steps to reproduce
as described above
Expected behavior
as described above
Neovim version (nvim -v)
v0.10.0-dev-709+gce56ad2ba
lspsaga commit
4c097f78add8d38eba2f9aa0e32a41feec84effe
Terminal name/version
alacritty

Soooo responsive man


Package Structure

Hello @EiffL @Justinezgh @aboucaud  ! This first issue is to keep track of development needed to build the SBI package.
In this PR, we can find the first prototype for the general structure. There's a lot more to do!
Task

[ ] #14
[ ] Track/Update the requirements.txt
[ ] Track/Update the setup.py
[ ] #12
[ ] #13

If you think something else we should do, please add a TODO list in this issue! :-)

[ ] Add pre-commit config


ValueError in MVPA tutorial

Hi,
I'm trying to run this tutorial using mne 0.15.2: [https://www.martinos.org/mne/stable/auto_tutorials/plot_sensors_decoding.html].
When running coef = get_coef(time_decod, 'patterns_', inverse_transform=True), I get the following error:
'ValueError: This estimator does not have a patterns attribute.'
If I simply leave out 'patterns_' to let it default to 'filters_', by running the following line:
coef = get_coef(time_decod, inverse_transform=True), I get an equivalent error:
'ValueError: This estimator does not have a filters_ attribute.'
Can you help? Thank you very much for your time!
Best wishes,
Kata

Hi Kata,
Did you use the LinearModel wrapper class as demonstrated here
http://martinos.org/mne/stable/auto_tutorials/plot_sensors_decoding.html?highlight=linearmodel
?
Best,
Denis
On Sun, Apr 29, 2018 at 11:46 PM katarinaslama<EMAIL_ADDRESS>wrote:

Hi,
I'm trying to run this tutorial using mne 0.15.2: [
https://www.martinos.org/mne/stable/auto_tutorials/plot_sensors_decoding.html
].
When running coef = get_coef(time_decod, 'patterns_',
inverse_transform=True), I get the following error:
'ValueError: This estimator does not have a patterns attribute.'
If I simply leave out 'patterns_' to let it default to 'filters_', by
running the following line:
coef = get_coef(time_decod, inverse_transform=True), I get an equivalent
error:
'ValueError: This estimator does not have a filters_ attribute.'
Can you help? Thank you very much for your time!
Best wishes,
Kata
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/mne-tools/mne-python/issues/5171, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB0fitk7XtUzITvLOrcD9WApFoWdzTqfks5ttjS5gaJpZM4Tr-LF
.

No, I didn't! That fixed it. Thank you so much for your quick response.


added discoverable subtype resolver to standard object mapper

gatekeeper relies on discoverability for dynamic subtype resolving, we could omit it but people's client will break unless they explicitly modify the om.

I think this is probably a bad addition. The ObjectMappers stuff is pluggable, if we need to provide a factory to construct the standard delegates we should do that. Also, we should maybe consider not using the discoverable objectmapper stuff in favor of explicit sub-type resolution.

sure, as long as there is a standard. do other projects explicitly register subtypes and provide a unified object mapper?

I've been largely unable to convince others that type polymorphism is practical and reasonable, but GK's data structure make it impossible to ignore. Where we've had to do it (Stemma is in this boat, for instance), explicit sub-type annotations have been used over the discoverable object mapper. I'm generally afraid of taking a dropwizard dep here because it means http-remoting becomes a driver for dropwizard upgrades, which is net negative, IMO.

okay, so the recommendation is to have something like: https://github.palantir.build/elements/multipass/pull/221/files#diff-ed973ce939454dce96155647833a2461L1 and GK providing the right object mappers?

No, I'd advise GK switch to explicit annotations and use the standard object mappers, or alternatively keep just a custom ObjectMappers class and still use the http-remoting constructors.

okay, I'm going to change the GK annotations then to prevent clients from having to care.


[The Space] add getTokensByOwner method

Note that this impl may not be gas-optimized  because of using ERC721Enumerable.

I think there should be a custom erc721 contract inheriting ERC721Enumerable  and inherited by HarbergerMarket. getTokensByOwner and some methods/state variables in  HarbergerMarket should be moved to this erc721 contract. @guoliu @robertu7

@gary02 before merging, can you run a make snapshot to keep track of the gas fee?

sure, but I encounter trouble when run make snapshot:
Failed tests:
[FAIL. Reason: Invalid data. Counterexample: calldata=0x55a34fd7000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, args=[0, 0, 0]] testTokenURI(uint8,uint8,uint16) (runs: 0, μ: 0, ~: 0)
[FAIL. Reason: Invalid data. Counterexample: calldata=0x65ba286500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, args=[0, 0]] testForkRecursively(uint8,uint96) (runs: 0, μ: 0, ~: 0)
[FAIL. Reason: Invalid data. Counterexample: calldata=0xd15566e6000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, args=[0, 0, 0]] testSplitRoyalty(uint8,uint8,uint96) (runs: 0, μ: 0, ~: 0)

Encountered a total of 3 failing tests, 38 tests succeeded
Makefile:9: recipe for target 'snapshot' failed
make: *** [snapshot] Error 1

any tips to fix this?

@gary02 before merging, can you run a make snapshot to keep track of the gas fee?

sure, but I encounter trouble when run make snapshot:
Failed tests:
[FAIL. Reason: Invalid data. Counterexample: calldata=0x55a34fd7000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, args=[0, 0, 0]] testTokenURI(uint8,uint8,uint16) (runs: 0, μ: 0, ~: 0)
[FAIL. Reason: Invalid data. Counterexample: calldata=0x65ba286500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, args=[0, 0]] testForkRecursively(uint8,uint96) (runs: 0, μ: 0, ~: 0)
[FAIL. Reason: Invalid data. Counterexample: calldata=0xd15566e6000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, args=[0, 0, 0]] testSplitRoyalty(uint8,uint8,uint96) (runs: 0, μ: 0, ~: 0)

Encountered a total of 3 failing tests, 38 tests succeeded
Makefile:9: recipe for target 'snapshot' failed
make: *** [snapshot] Error 1

any tips to fix? @guoliu

What's your Foundry version?
➜  contracts git:(develop) forge
forge 0.2.0 (95857c9 2022-04-11T00:19:01.219885+00:00)
Build, test, fuzz, formally verify, debug & deploy solidity contracts.

USAGE:
    forge <SUBCOMMAND>

make snapshot is ok now after update foundry from 0.1.0 to 0.2.0.   Thx @robertu7

I find that make snapshot do not include fuzz tests by default.
run forge snapshot --gas-report --include-fuzz-tests will fail:
Failed tests:
[FAIL. Counterexample: calldata=0x55a34fd7000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001, args=[1, 1, 1]] testTokenURI(uint8,uint8,uint16) (runs: 0, μ: 0, ~: 0)

Encountered a total of 1 failing tests, 40 tests succeeded

My Foundry version now:
$ forge
 forge 0.2.0 (b3fe652 2022-04-18T07:41:40.363902807+00:00)

@robertu7

I find that make snapshot do not include fuzz tests by default. run forge snapshot --gas-report --include-fuzz-tests will fail:
Failed tests:
[FAIL. Counterexample: calldata=0x55a34fd7000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000001, args=[1, 1, 1]] testTokenURI(uint8,uint8,uint16) (runs: 0, μ: 0, ~: 0)

Encountered a total of 1 failing tests, 40 tests succeeded

My Foundry version now:
$ forge
 forge 0.2.0 (b3fe652 2022-04-18T07:41:40.363902807+00:00)

which installed by cargo install --git https://github.com/foundry-rs/foundry --locked @robertu7

I figure out that testTokenURI failed  because of  missing 'ehthers' in node env. After run npm install ., all tests is ok now.


Do autostart only when data-bibi-autostart is true

@satorumurmur
Hi,
I found setting data-bibi-autostart="false" doesn't follow expected behavior, don't autostart, on embedding style:
<a
  autostart="false"
  href="http://your.web.site/somewhere/bib/i/?book=my-book.epub"
  data-bibi="embed"
  data-bibi-style="[[ CSS for embeded BiB/i, as you like ]]">
  My Great Book Title
</a>
<script src="http://your.web.site/bib/i.js"></script>

I think we should fix this behavior. If you agree with me, we have, I think, two choices: aria-*'s true/false way and video's autoplay way.
WAI-ARIA's way
Now default value of bibi-data-autostart is false, so, we set it to true only when data-bibi-autostart attributes' value is exactly the same to the string true. Even if it is set to yes, we evaluate it as false.
Fix for this is in this pull request.
video element's way
We assume autostart is true if a element has the attribute data-bibi-autostart(we can test it by hasAttribute method), even when it is the string false like video's autoplay attribute.
I prefer this way because probably most of people who write HTML code are familiar with this than WAI-ARIA's way.
But I guess you might like WAI-ARIA's way, so, it is used in this pull request.
Could you consider this issue?

It is an interesting suggestion. Thanks.
I agree with you that the one who write "data-bibi-autostart" attribute is almost always the one who wants BiB/i to start automatically like HTML's autoplay attribute of video element's way, so I code it as that. But, as you also said, when "data-bibi-autostart" is "false", I don't want BiB/i to start automatically.
So, now I pull your request, and later, I'll edit it as this:
var Autostart = (As[i].hasAttribute("data-bibi-autostart") && /^false|no$/.test(As[i].getAttribute("data-bibi-autostart")));

data-bibi-autostart attribute doesn't exist ... does NOT start automatically.
data-bibi-autostart="false" ... does NOT start automatically.
data-bibi-autostart="no" ... does NOT start automatically.
data-bibi-autostart="true" ... DOES start automatically.
data-bibi-autostart="yes" ... DOES start automatically.
data-bibi-autostart="" ... DOES start automatically.
data-bibi-autostart="boo" ... DOES start automatically.

Thanks!


Update README.md

incremented copyright year

This repo is deprecated.
GitHub.com/bleach86/tuxcoin-V2 is the current repo


BUG: playback broken on iOS

playback is broken, not sure why lol
does iOS not like h264??? it can't be DASH, because that should be built into the player (video.js).
tell me why it's broken and i'll try to fix

this is resolved now that we've switched from DASH to HLS.


[SPARK-32028][WEBUI][FOLLOWUP][BRANCH-2.4] fix app id link for multi attempts app in history summary page

This is simply a backport of https://github.com/apache/spark/pull/28867 to branch-2.4

@zhli1142015 does this back port look correct? It wasn't a 100% clean cherry-pick but I think I got the change mapped correctly.

Jenkins, test this please

@srowen , thanks for taking care this. This looks good to me.

Jenkins test this please

Thank you, @srowen and @zhli1142015 .

Test build #124650 has started for PR 28949 at commit 697bbd2.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/29267/
Test PASSed.

Test build #124650 has finished for PR 28949 at commit 697bbd2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/124650/
Test FAILed.

Jenkins retest this please

Test build #124693 has started for PR 28949 at commit 697bbd2.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/29305/
Test PASSed.

Test build #124693 has finished for PR 28949 at commit 697bbd2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/124693/
Test PASSed.


Is there an existing issue for this?

[X] I have searched the existing issues.

Which plugins are affected?
Analytics
Which platforms are affected?
Android, iOS
Description
I don't know if anybody else is experiencing this issue but Im trying to use FirebaseAnalytics.instance.logPurchase to log a purchase with items.
FirebaseAnalytics.instance.logPurchase(
      transactionId: 'order ID',
      value: 9.99,
      shipping: 0.00,
      currency: 'GBP',
      items: order.products
          .map(
            (item) => AnalyticsEventItem(
              itemId: item.someID,
              itemBrand: item.brand,
              currency: item.currency,
              itemListName: item.name,
              price: item.price,
            ),
          )
          .toList(),
    );

All seems fine app side, I don't get any errors however in the Firebase Console Debug view the event comes through like this.

The error code 21 seems to relate to it not accepting an array and if I remove the array of items from the call it works fine.
Reproducing the issue
Attempt to call the function to log a purchase with items.
FirebaseAnalytics.instance.logPurchase(
transactionId: 'order ID',
value: 9.99,
shipping: 0.00,
currency: 'GBP',
items: order.products
.map(
(item) => AnalyticsEventItem(
itemId: item.someID,
itemBrand: item.brand,
currency: item.currency,
itemListName: item.name,
price: item.price,
),
)
.toList(),
);
Firebase Core version
2.12.0
Flutter Version
3.22.1
Relevant Log Output
No response
Flutter dependencies

Expand Flutter dependencies snippet

Replace this line with the contents of your `flutter pub deps -- --style=compact`.

Additional context and comments
No response

Hi @JonBenson, I'm unable to reproduce this issue. Could you try upgrading firebase_analytics to see if it resolves your issue? Seems to work fine on the latest version.

The SDK update did the trick thanks SelaseKay


Qestion bout nd.waitall()

I want to test the inference time about yolov3.I I wrote two versions.like bellow:
1.tic = time.time() class_IDs, scores, bounding_boxs = net(x) toc = time.time() print("Inference time is :",toc-tic)
2.tic = time.time() class_IDs, scores, bounding_boxs = net(x) **nd.waitall()** toc = time.time() print("Inference time is :",toc-tic)
The results of the two versions vary greatly.Which one is right? and Why?

@mxnet-label-bot add [Question]

2 is right.
MXNet computes operators asynchronously, so it is necessary to call 'nd.waitall()' to wait for all computation over.

@Jessespace
MXNet ndarray use lazy evaluation, the previous operations may not finished yet. For benchmark purpose, you should use nd.wait_to_read() or nd.waitall().
See: https://mxnet.incubator.apache.org/api/python/ndarray/ndarray.html#mxnet.ndarray.NDArray.wait_to_read
And: https://mxnet.incubator.apache.org/api/python/ndarray/ndarray.html#mxnet.ndarray.waitall
If

@Jessespace
MXNet ndarray use lazy evaluation, the previous operations may not finished yet. For benchmark purpose, you should use nd.wait_to_read() or nd.waitall().
See: https://mxnet.incubator.apache.org/api/python/ndarray/ndarray.html#mxnet.ndarray.NDArray.wait_to_read
And: https://mxnet.incubator.apache.org/api/python/ndarray/ndarray.html#mxnet.ndarray.waitall

I'm still not clear about this problem.I use nd.waitall() to test a single image.
But I got 0.49 FPS.Please help me figure out  the problem.
path = os.path.join(read_dir, '000204.jpg')
tic = time.time()
img_path = os.path.join(read_dir, path)
x, img = data.transforms.presets.yolo.load_test(img_path, short=shape,max_size=shape)
x = x.as_in_context(ctx)
time_loadimage = time.time() - tic

class_IDs, scores, bounding_boxs = net(x)
nd.waitall()
all = time.time() - tic

print("every picture time cost:", (all - time_loadimage))
print("FPS:", 1.0 / (all - time_loadimage))

It is unclear from your question. Is the problem that you think it is slower than it should be?
If you are using the GPU, just FYI there is a lot of overhead for the first operation you perform on the GPU. So for benchmarking purposes you need to "warm up" the GPU by processing at least one item on the GPU, and then start timing for real after the initialization overhead is finished.

You'll want to start 'time_loadimage' after the load and context change has finished: remember that MXNet operations are asynchronous. And it's better to use wait_to_read() instead of waitall() if you're wanting to time certain operations. And even better still you should check out the MXNet Profiler instead of writing your own profiling code.
path = os.path.join(read_dir, '000204.jpg')
tic = time.time()
img_path = os.path.join(read_dir, path)
x, img = data.transforms.presets.yolo.load_test(img_path, short=shape,max_size=shape)
x = x.as_in_context(ctx)
# block until data load and context switch have completed
x.wait_to_read()
time_loadimage = time.time() - tic

class_IDs, scores, bounding_boxs = net(x)
# block until net has completed
bounding_boxs.wait_to_read()
all = time.time() - tic

print("every picture time cost:", (all - time_loadimage))
print("FPS:", 1.0 / (all - time_loadimage))

You'll want to start 'time_loadimage' after the load and context change has finished: remember that MXNet operations are asynchronous. And it's better to use wait_to_read() instead of waitall() if you're wanting to time certain operations. And even better still you should check out the MXNet Profiler instead of writing your own profiling code.
path = os.path.join(read_dir, '000204.jpg')
tic = time.time()
img_path = os.path.join(read_dir, path)
x, img = data.transforms.presets.yolo.load_test(img_path, short=shape,max_size=shape)
x = x.as_in_context(ctx)
# block until data load and context switch have completed
x.wait_to_read()
time_loadimage = time.time() - tic

class_IDs, scores, bounding_boxs = net(x)
# block until net has completed
bounding_boxs.wait_to_read()
all = time.time() - tic

print("every picture time cost:", (all - time_loadimage))
print("FPS:", 1.0 / (all - time_loadimage))

You'll want to start 'time_loadimage' after the load and context change has finished: remember that MXNet operations are asynchronous. And it's better to use wait_to_read() instead of waitall() if you're wanting to time certain operations. And even better still you should check out the MXNet Profiler instead of writing your own profiling code.
path = os.path.join(read_dir, '000204.jpg')
tic = time.time()
img_path = os.path.join(read_dir, path)
x, img = data.transforms.presets.yolo.load_test(img_path, short=shape,max_size=shape)
x = x.as_in_context(ctx)
# block until data load and context switch have completed
x.wait_to_read()
time_loadimage = time.time() - tic

class_IDs, scores, bounding_boxs = net(x)
# block until net has completed
bounding_boxs.wait_to_read()
all = time.time() - tic

print("every picture time cost:", (all - time_loadimage))
print("FPS:", 1.0 / (all - time_loadimage))

I followed your advice and tried to use profile. Still some confusion about some places.
code:
profiler.set_state('run')
tic = time.time()
x, img = data.transforms.presets.yolo.load_test(img_path, short=shape)
x = x.as_in_context(ctx)
class_IDs, scores, bounding_boxs = net(x)
bounding_boxs.wait_to_read()
all = time.time() - tic
profiler.set_state('stop')
print("time:", all)
print(profiler.dumps())`
Result:

time: 5.4537177085876465
profile result：

I add  all the MXNET_C_API time ,it is about the 5.4s which similar to 5.45s using tic toc. But I can't understand Device Storage time and operator time ,they take too long.

You'll want to start 'time_loadimage' after the load and context change has finished: remember that MXNet operations are asynchronous. And it's better to use wait_to_read() instead of waitall() if you're wanting to time certain operations. And even better still you should check out the MXNet Profiler instead of writing your own profiling code.
path = os.path.join(read_dir, '000204.jpg')
tic = time.time()
img_path = os.path.join(read_dir, path)
x, img = data.transforms.presets.yolo.load_test(img_path, short=shape,max_size=shape)
x = x.as_in_context(ctx)
# block until data load and context switch have completed
x.wait_to_read()
time_loadimage = time.time() - tic

class_IDs, scores, bounding_boxs = net(x)
# block until net has completed
bounding_boxs.wait_to_read()
all = time.time() - tic

print("every picture time cost:", (all - time_loadimage))
print("FPS:", 1.0 / (all - time_loadimage))

You'll want to start 'time_loadimage' after the load and context change has finished: remember that MXNet operations are asynchronous. And it's better to use wait_to_read() instead of waitall() if you're wanting to time certain operations. And even better still you should check out the MXNet Profiler instead of writing your own profiling code.
path = os.path.join(read_dir, '000204.jpg')
tic = time.time()
img_path = os.path.join(read_dir, path)
x, img = data.transforms.presets.yolo.load_test(img_path, short=shape,max_size=shape)
x = x.as_in_context(ctx)
# block until data load and context switch have completed
x.wait_to_read()
time_loadimage = time.time() - tic

class_IDs, scores, bounding_boxs = net(x)
# block until net has completed
bounding_boxs.wait_to_read()
all = time.time() - tic

print("every picture time cost:", (all - time_loadimage))
print("FPS:", 1.0 / (all - time_loadimage))

I followed your advice and tried to use profile. Still some confusion about some places.
code:
profiler.set_state('run')
tic = time.time()
x, img = data.transforms.presets.yolo.load_test(img_path, short=shape)
x = x.as_in_context(ctx)
class_IDs, scores, bounding_boxs = net(x)
bounding_boxs.wait_to_read()
all = time.time() - tic
profiler.set_state('stop')
print("time:", all)
print(profiler.dumps())`
Result:

time: 5.4537177085876465
profile result：

I add all the MXNET_C_API time ,it is about the 5.4s which similar to 5.45s using tic toc. But I can't understand Device Storage time and operator time ,they take too long.

I recommend that you should not use both the mxnet profiler and the time function at the same time. MXNet profiler will incur additional overhead and result in a wrong time result.


simulator.deleteAndRelaunchApp with fbsimctl is still slower than apple's

fbsimctl uninstall org.reactjs.native.example.example
vs
xcrun simctl uninstall booted org.reactjs.native.example.example
the apple version is still faster, we need to improve fbsimctl

not anymore


under Education, web UI to explain investing to first-time investors and entrepreneurs

foreach document, explain: why is this document necessary?

it would be nice to send them a package of "if you're thinking about being part of this deal, here's the info package that answers some questions you may have."


add permissions for policySets

Signed-off-by: Will Kutler<EMAIL_ADDRESS>

/cc @JakobGray
/cc @nathanweatherly

/lgtm


error: method emit_enum_struct_variant has 0 type parameters but its trait declaration has 1 type parameter

Good morning! toml seems to have been broken by the closure updates and the changes to Encoder and Decoder:

toml-0.1.4/src/serialization.rs:222:5: 228:6 error: method emit_enum_struct_variant has 0 type parameters but its trait declaration has 1 type parameter [E0049]

I'm trying to fix this in one of my own libraries, and it's trickier than I expected.

Fixed some time ago I believe


Can't exclude moudle when build PIXI.

Because the bug #3662 , I have to build pixi without  interaction.
But I found
npm run build -- --exclude interaction

is useless.
the  --exclude interaction can't be pass to pixify.
What can't do for it ?

You need to do "npm run dist -- --exclude interaction". Use dist not build.

https://github.com/pixijs/pixi.js/blob/dev/README.md#how-to-build

@bigtimebuddy  , I found  use 'build' is OK .
If use  two -- , the parameters will be pass two level.
npm run build -- -- --exclude interaction

npm run build -- -- --exclude interaction
I think you could update the document.


NPM version not latest

Commit 71c3f21 fixed a error in routes.js line 67 from an install from NPM.  NPM also has version 0.9.3 while master is 0.9.2 Perhaps the version in NPM need to be updated?

In my package.json, I just changed the source to point to git repo:
"dependencies": {
  "mers": "jspears/mers"
}


can not creat account

when using create account it gives an error

steps to produce :

go to mastodon
click on create account

Should be fixed in https://github.com/threefoldtech/www-mastodon/pull/162

I just tested it and it worked quite well.
Screencast from 28-05-23 08:04:42.webm

Verified on https://getmastodon.threefold.io/
Account creations is working.

And when i imported the seed in polkadot i was able to check the account details from the dashboard and the twin, relay were set up correctly.


Add view basic styles

:dart: Requirements acheived in this PR

:heavy_check_mark: Implement the design from the sneak peek wireframes.

Everything functions. (Note: Ignore login logic, you would be using Devise in coming milestone)

All Users page wireframe:
Single User page wireframe:
All Posts by a given User page wireframe:
Single Post page wireframe:

:heavy_check_mark: Use methods that you have created in the Blog App - processing data in models.

Hint: Data was added to the database through the seed.rb file

:speech_balloon: Feel free to shoot me a message in the pull request if you have any questions.
Thank you for your time!

Thank you for reviewing my code! 🙏


the confusion of k8s-deployment

I have tried the draonboat in the hostnetwork mode ,that is the nodeaddress is host ip:port . It runs ok ,  great ! Thanks for sharing so  useful lib .
At present , i hope to  deploy it on k8s . However , the  IP address will be recreated every reboot . I tried to use the "servicename:serviceport " to replcase "ip:port" , but it won't work .
I refer to the link  https://github.com/lni/dragonboat/issues/140  and use  NodeHostConfig.AddressByNodeHostID and gossip config ,and  yet i have some confusing problems .
When I deploy the dragonboat server in k8s , i can not get the  ip  of remote pod . So how could i set the value of config.GossipConfig.seed ?
The reference doc says so
" Seed is a list of AdvertiseAddress of remote NodeHost instances. Local
// NodeHost instance will try to contact all of them to bootstrap the gossip
// service. At least one reachable NodeHost instance is required to
// successfully bootstrap the gossip service. Each seed address is in the
// format of IP:Port, Hostname:Port or DNS Name:Port."
So the null value is forbidden . Can you give me some advice ?
Thank you and i am looking forward to your reply.

@wh-afra
As described by the docs, you should put a list of AdvertiseAddress values in that Seed field. AdvertiseAddress is the Hostname:Port or IP:Port pair from which your node can be accessed, they should be specified every time when you start a NodeHost instance.
It is your application's responsibility to figure out what is the correct Hostname:Port or IP:Port pair. You also need to implement a mechanism to allow at least a few (not all of them) of such NodeHost instances' AdvertiseAddress values to be available to all of your NodeHost instances to bootstrap their gossip process.

@lni
Thank you .  But  I could not get your point.
for example, I have 3 host as raft node A，B，C ,and I deploy the raft server on them in k8s。
Of course ,in the pod A ,i can get the local hostname/hostip, so the AdvertiseAddress  can be figured out .
However, theI can not get the hostip of pod B  and podC ，so how can i set the seed value?
I am not sure if  using kuberenetes-releated lib will allow mt to get the  hostip of pod B  and podC.
Even so , the pod might not succeed ,and the problem might be more complex.
Have I misunderstood your intention ?Or have i missed any important information?
Thank you for your patience.

Best way would be to use a StatefulSet.
If the name of your StatefulSet is dragonboat-example, then Kubernetes will automatically name the pods in your stateful set:

dragonboat-example-0
dragonboat-example-1
dragonboat-example-2

That's what you'd use for your member list.
StatefulSets have some other useful features like Volume Claim Templates which are basically mandatory when running persistent workloads in Kubernetes.

If the node crashes, a new pod will be created with the missing hostname on a different node. Any changes to the local disk will likely be lost, but any persistent disks (block storage) will be attached automatically to the new pod. In this way, the Host ID can survive a machine failure.
Alternatively, if the Host ID is stored on the local disk and it is lost during a crash then the new pod will have a new Host ID but the same AdvertiseAddress as the previous Pod/Host. This should not cause any issues because Gossip and Raft are separate and Kubernetes will always route network traffic to either the new pod or the old pod, never both.

@kevburnsjr  Thank you for your detailed explanation.
In our scenario, there is communication between a business service and a Raft node for data, and I am using the ondisk mode of Dragonboat. Will this be affected?
Thank you .

Will what be affected?

@kevburnsjr
Perhaps I did not express myself clearly.
In my scenario, PVC currently only supports local storage class  and some nodehostid-related information is saved on the local disk because of  using the on-disk mode of dragonboat (Use pebble to store key-value pairs.).
I'm not sure if this is feasible using k8s's  pvc .
And， How can I associate the physical machine with the final running pod?
for example ,i have 3 machine to deploy server in k8s ,A,B,C
then i  deploy statefulset with replica=3 ,so it can start 3 pod (pod-0,pod-1,pod-2)  ,the related pvc : pvc-0,pvc-1,pvc-2。
when pod crashed , it can restart .
when node crashed , the pod-0 is not executed on A ,but on B. then pvc-0 will be associated with machine B .
The nodehostid of machine B will not match with the storage class, which will cause an error.
Maybe we should extend the storage class ?

You will need to use anti-affinity.
https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity
Configuration of the Kubernetes scheduler is well outside the scope of this repository.
I suggest you read a book on Kubernetes before seeking further advice here on this topic.
I highly recommend this book by Brendan Burns:
Kubernetes: Up and Running
https://www.amazon.com/dp/109811020X


Vector consistently throws NotSupportedException for .NET 5

Vector consistently throws NotSupportedException for .NET 5
Vector<T> is designed to work with only a limited subset of types. These types are currently byte, sbyte, short, ushort, int, uint, long, ulong, float, and double.
When T is not one of these supported types, you are meant to get a NotSupportedException. However, due to some code paths that exist to better support hardware acceleration, this exception was not always thrown.
Version introduced
.NET 5
Old behavior
For certain functions, you would not get a NotSupportedException when using an unsupported T. For example, Vector<bool> + Vector<bool> would return default rather than throwing. However, this would only occur for platforms which had no hardware acceleration, such as ARM32, or if hardware acceleration was disabled for the current platform.
New behavior
Unsupported T will now consistently throw NotSupportException on all hardware and configurations.
Reason for change
Outside the explicitly supported types, Vector<T> does not behave as expected and the behavior was inconsistent across various platforms and hardware configurations.
Recommended action
Do not use unsupported T. In .NET 5 and prior, the supported types are byte, sbyte, short, ushort, int, uint, long, ulong, float, and double.
In a future revision of .NET, this support could be expanded to additional types and the relevant docs should be checked to determine which types are valid for use.
Category

Core .NET libraries

Affected APIs
This change impacts all members of Vector

Issue metadata

Issue type: breaking-change

This is relevant for:

PR - https://github.com/dotnet/runtime/issues/37506
Issue - https://github.com/dotnet/runtime/issues/37506

It should be going out in preview 8.


GPKG writing slow when using write() loop

Expected behavior and actual behavior.
I am writing 300,000 features to a file. Depending on the driver, the performance of a write() loop is vastly different from a writerecords() call.

ESRI Shapefile
GeoJSON
GeoPackage

write() loop
16
28
62

writerecords()
16
20
20

I noticed this when writing onto a slow USB stick, so probably there is no buffering of the GeoPackage .write() calls. That totally makes sense but I had assumed Fiona did some magic buffering in the background. After all, the docs say in https://fiona.readthedocs.io/en/latest/manual.html#appending-data-to-existing-files:

Buffering
Fiona’s output is buffered. The records passed to write() and writerecords() are flushed to disk when the collection is closed. You may also call flush() periodically to write the buffer contents to disk.

The GeoJSON result is also almost 50% slower with a loop than with writerecords(), as that is not as drastic as with GPKG I did not focus on it.
Steps to reproduce the problem.
Write lots of features... :B
Sorry, no time for writing a shareble example right now.
for feature in features:
  output.write(feature)

vs
output.writerecords(features)

Proposed fix
If the magick buffering is missing for GPKG (and others?), that should be fixed. If there is no way to do that, the docs should mention that in the note mentioned above.
Operating system
Archlinux
Fiona and GDAL version and provenance
Fiona from Pypi:
    $ pip freeze | grep Fiona
    Fiona==1.8.6

gdal from Archlinux repositories:
$ aurman -Qs gdal
community/gdal 2.3.2-11 [installed]
community/python-gdal 2.3.2-11 [installed]
community/python2-gdal 2.3.2-11 [installed]

The reason why
for feature in features:
  output.write(feature)

is slower than
output.writerecords(features)

Is that there is one geopackage transaction within each write call and only one per 20,000 features within each writerecords call.
I expect the following code to be just as slow as your first example, demonstrating that the transactions are the culprit.
for feature in features:
  output.writerecords([feature])

Transactions in the GeoJSON are less costly because they do nothing in comparison to the geopackage transactions, but they do have a noticeable overhead.

That's what I assumed.
So the buffering mentioned in the docs is really just about file integrity? Buffering is the first thing I look for when writing something is slow that's why I assumed it to be relevant here.

I mention buffering to warn users about the state of the output file in the (rare) case that they have opened it multiple times: writes from one collection object won't necessarily appear immediately in the file and be available from a second opened collection.


Resolved foreign key constraint error in PostgreSQL

When I tried to store the data in the favorites table, I encountered the problem of the foreign key, which caused the PostgreSQL database to give an error.
I made this change in the table and it was fixed

Resolved foreign key constraint error in PostgreSQL


[LIBCLOUD-749] CloudStack: fixed method ex_authorize_security_group_ingress

Corresponding ticket in the JIRA issue tracker: LIBCLOUD-749
This PR fixes the following bugs:

The docstring doesn't match parameters of the method.
Only ICMP and TCP is allowed even if the doc of the parameter protocol mention TCP and UDP.
Moreover ICMP cannot be used because there is no way to specify the two required parameters icmptype and icmpcode.
The parameter endport is not used if it's defined.
The return type is not a list but a dict.
The unit test doesn't use parameters in the correct order.

This PR also does the following changes:

Improve the docstring to be a bit more detailed (the previous one comes from the official Apache CloudStack documentation).
Add a kwargs to allow to provide extra parameters defined in the API and in the docstring.
Improve the unit test.
Add support for other protocols like AH, GRE and ESP which are available on some Cloud like Exoscale.

Added one comment, besides that, LGTM. Thanks.
/cc @runseb

LGTM, I will merge in the coming days

@Kami : Thanks for the comment which allowed me to discover a small issue in the docstring (securitygroupid and usersecuritygrouplist were noted as :param instead of :keyword).

Can you please explicitly declare all the supported arguments instead of using **kwargs?

Yes, of course. I used kwargs because it's the way some "unusual" parameters (like domainid and projectid) are passed with this driver. For example the method create_key_pair  takes the name of the keypair and then parameters like domainid and projectid are passed via kwargs.
To be consistent I would suggest to keep it like this.
Please tell me if you still want than these parameters to be explicitly declared.

Sorry for the delay - I went ahead and merged the changes.
For now, lets keep kwargs, but in the future it would be great if we can get rid of it and explicitly declare all the supported arguments - (ab)using kwargs makes many things such as "static" analysis hard / impossible.


I would like to create a tutorial for SSO for my software

Hi
I would like to create a tutorial for SSO for my software, similar to this one, but for my learning management system.
https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/learnupon-tutorial
What is the process please?
Thanks
Lynton

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

ID: dbcbc01a-98c6-33f7-88f2-283737a955f2
Version Independent ID: f619e0c8-b70f-02ff-ee24-9e7b8acc5659
Content: Tutorial: Azure Active Directory integration with LearnUpon
Content Source: articles/active-directory/saas-apps/learnupon-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @jeevansd
Microsoft Alias: jeedes

@SimplifyLMS
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.

HI James
This seems to be wrong. The author of that page has nothing to do with this
request. I want to create a new page such as:
https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/
simplifyLMS-tutorial
It's more the owner of this page who may be the relevant person to advise?
https://docs.microsoft.com/en-us/azure/active-directory/saas-apps/tutorial-list
Thank you
[image: photo]
Lynton Howes
Managing Director, Simplify LMS
0406 049 830 | www.SimplifyLMS.com.au http://www.simplifylms.com.au/
http://www.linkedin.com/company/simplify-lms
http://www.facebook.com/SimplifyLearningManagementSystem/
http://twitter.com/Simplify_LMS
On Thu, Aug 12, 2021 at 1:31 AM James Tran-MSFT @.***>
wrote:

@SimplifyLMS https://github.com/SimplifyLMS
Thanks for your feedback! I've assigned this issue to the author who will
investigate and update as appropriate.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/79568#issuecomment-896926768,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVFLDJKMP2DGVKC6Z3P55ILT4KJTNANCNFSM5B6OW6KQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email
.

@SimplifyLMS You cannot create a new tutorial here. Usually when our team publish the applications in the gallery then we create these tutorials for SAML applications. Please make sure that you follow the process documented here https://aka.ms/AzureADAppRequest to list your application in the gallery.

#please-close


tandoor-recipes: 1.5.10 -> 1.5.12

Description of changes
https://github.com/TandoorRecipes/recipes/releases/tag/1.5.12
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

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

[ ] sandbox = relaxed
[X] sandbox = true

[X] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Adding @drupol and @wegank for reviewing, as I recall you both taking a look in past PRs.


JSON columns not supported

Hi,
i am using tap-mysql and tap-postgresql to sync database tables into target-postgres.
In both taps i have tables with the field type JSON. But on the target postgres table it is has field type string and i cannot query the fields inside anymore.
Is it intended to not support field type JSON? I know singer uses JSON Schema and that does not supported embedded JSON. Maybe JSON could be a custom string format?
JSON Schema string formats
Or is there any other solution for that?
Thanks in advance.

👋 Hey @ehuebner!
It's true that we currently do not support JSON types. There are a number of hurdles to this, one of which you mentioned: JSONSchema not having a type for this.
String formats have been thrown out as an option.
Out of curiosity, can you leverage ::JSON JSON casting in Postgres to query these fields? That's how we're currently using this for similar data.

Hi @AlexanderMann!
Your suggested method works quite well. Performance could become an issue since the strings are parsed per query and there are no indices. For a full table sync it would be possible to have a post sync process that changes the JSON fields like this:
ALTER TABLE table1 ALTER COLUMN col1 TYPE JSON USING col1::JSON;
This was mentioned here:
https://stackoverflow.com/questions/16074375/postgresql-9-2-convert-text-json-string-to-type-json-hstore
But the problem still exists: On the target side there is no way to identify what field was a JSON field on the tap side. 😕

Yeah, there have been some conversations around how to add this programmatically based on the depth of parsing/denesting. But for a single field, it's tricky to have it consistently identify a single field as being needed to be parsed as JSON.
Would allowing target-postgres to throw everything after a certain depth of unnesting into a catchall JSONB column solve this problem for you, or is this really about a single field which is a JSON string and unnesting that into JSONB?

I have multiple tables with with each two (for this context interesting) fields:
type & payload
Type is basicly a name for a schema of the payload.
Payload is a JSON field. It can have different schemas in the same table.
So it is about single fields that could be transported as string but that need to be parsed to JSON on the target side again.
I was thinking about having some post sync process that checks all string fields for JSON values and runs the ALTER COLUMN command. But that is really brute force.

Gotchya. Would a materialized view work? Also, target-postgres has post hooks which might work for you

@ehuebner How do the fields come across in Singer? What are the JSON Schema types and what does the JSON object look like?
I'm assuming it's either coming across as either a:

JSON that is part of the record structure
Stringified JSON in a string typed field

I use tap-mysql, tap-postgres & target-postgres.
Both taps are transforming a JSON field to a string stream.
@awm33 I was thinking a bit about having the JSON field as a part of the record structure. I do not know if this is really a good idea. We have different schemas in the same table field. That would mean the record structure is a mixture of different schemas. Bad idea. If you habe only rows with the same schema and you also maintain the schema in postgres to validate your insert statements based on that schema it would be a good idea.
I think using string type in the singer stream is the more resilient solution. Like mentioned the target side is missing the information that a field is a JSON and not just a string.
@AlexanderMann Can you give some additional words to your idea how a materialized view could solve the problem?

@ehuebner I think something like this would work, but I'm not sure as to your setup etc.
CREATE VIEW as_json AS
    SELECT
        *,
        json_string_column::JSONB AS json_column
    FROM singer_target_postgres_table

@ehuebner I think @AlexanderMann 's proposal is your best bet. In a view, your data modeling layer, or in a your queries, just cast the column to JSON.
At this point, it's a string, the tap choose that as the best representation, which it honestly might be. Without a schema declared it would be rejected by target-postgres anyway (we use the JSON schema to construct tables) and you can still use it as a JSON column in the destination.

I'm closing this out since this is really more if an issue with the tap, and the tap emits postgres JSON as string by design.


⚠ 366.ru has degraded performance

In c1109c2, 366.ru (https://366.ru) experienced degraded performance:

HTTP code: 200
Response time: 1084 ms

Resolved: 366.ru performance has improved in 6a3e2e2.


feat: add mocked resources

Can you also add a link to the Juno branch which would come in Tandem with this update

Can you also add a link to the Juno branch which would come in Tandem with this update

I don't have permissions to push new branches, so I've sent the patch file to the Slack

Juno branch: bohdan/mocked-resources

Codecov Report
Attention: Patch coverage is 48.98990% with 101 lines in your changes missing coverage. Please review.

Project coverage is 80.45%. Comparing base (b976dcd) to head (2cbe44e).
Report is 2 commits behind head on native2.6.4.

Files
Patch %
Lines

crates/blockifier/src/debug.rs
0.00%
61 Missing :warning:

.../blockifier/src/transaction/account_transaction.rs
76.78%
9 Missing and 4 partials :warning:

crates/blockifier/src/transaction/transactions.rs
66.66%
3 Missing and 8 partials :warning:

crates/native_blockifier/src/py_validator.rs
0.00%
6 Missing :warning:

.../blockifier/src/blockifier/transaction_executor.rs
66.66%
3 Missing :warning:

...lockifier/src/transaction/transaction_execution.rs
86.36%
1 Missing and 2 partials :warning:

...es/blockifier/src/blockifier/stateful_validator.rs
77.77%
0 Missing and 2 partials :warning:

crates/native_blockifier/src/py_block_executor.rs
0.00%
2 Missing :warning:

Additional details and impacted files
@@               Coverage Diff               @@
##           native2.6.4     #111      +/-   ##
===============================================
- Coverage        81.02%   80.45%   -0.57%
===============================================
  Files               77       78       +1
  Lines            10872    10925      +53
  Branches         10872    10925      +53
===============================================
- Hits              8809     8790      -19
- Misses            1588     1657      +69
- Partials           475      478       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Stale for now


Use Chai to perform diffs

This chai-subset plugin has its own "comparison" implementation that is shown when an assertion does not match. In my test, the output looks like:
  11 passing (20ms)
  1 failing

  1) plain object should pass for smaller object:
     AssertionError: expected
{
	"a": "b",
	"c": "d"
}
to contain subset
{ a: 'ba' }

Yes, the spacing is actually misaligned in the console, but that is not a big deal.
I think this can be improved by letting Chai handle the diff process like it does for its core assertions. Developers can set the Chai config showDiff to either true or false, with true being the default.
Here is what Chai's built-in diff looks like:
  11 passing (16ms)
  1 failing

  1) plain object should pass for smaller object:

      AssertionError: expected { a: 'b', c: 'd' } to contain subset { a: 'ba' }
      + expected - actual

       {
      +  "a": "ba"
      -  "a": "b"
      -  "c": "d"
       }

When delegating the diff process to Chai, the spacing is correctly aligned and you get some neat green text where there should be additions (+) to the object and red text for the opposite case (-).
Please try it out with a failing test case and let me know what you think!

Hi @RobertHerhold Thanks a lot for this contribution.
We're doing open open source. The extra "open" in there means:
Open Open Source: individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.
Inspired by io.js: http://www.pubnub.com/blog/node-js-vs-io-js-creating-open-open-source-contributions/#sthash.sjyGZ4ri.dpuf
There is also a nice video about why here: http://www.pubnub.com/blog/node-js-vs-io-js-creating-open-open-source-contributions/
You should still do pull requests, so we can discuss before merging. But we are giving you the right to merge.

Hmmm, I'm experiencing some issues with giving you access, seems we have to make you part of our org, and that has unwanted implications.

Works perfect! Thanks a lot, i'll publish new version soon with updated dev deps


resolved PR comments [Authors & Acknowledgements]

fixes #66 .  (Authors and acknowledgements sections )
@katherinepeterson resolved the your comment on previous PR #74 comments .
(i.) To remove the ' . ' from the section-templates file .
(ii.) Formatted the file using prettier with settings taken from .prettierrc file .
I believe it's proper now , please approve PR if looks good .

closing this PR as merging my two issue changes in one PR #80

@saurabhchaturvedy I'm confused as to why you created a new PR (this one) instead of fixing the comments directly at #74. If you'd like, I'd be happy to assist with how that could be done.
I also don't understand why you decided to combine two separate changes in the same PR (#80). It is much easier to review and merge if each PR deals with its own set of changes. I would suggest closing #80 and reopening #74 and #67, updating them with the fixes. Let me know if there's anything I can help with that!


AVX builds don't support arbitrary grids

Currently, the AVX enabled-build, which is the default, only supports grid sizes divisible by 8. This is definitely not the ideal case and should be addressed ASAP. The error is also silent and generates corrupted grids with garbage memory values.

Simple fix is to disable AVX all together
Dynamic dispatching depending on the grid size requested

@szaman19 can you simplify this fix with padding to sizes divisible by 8?

@denfromufa Yup, realized later that that'd probably be the ideal solution. In effect we just need the innermost loop to have a stride of 8 (be divisible by 8). So padding needs to be only along a single dimension along the grid.


⚠ Shakedown Social - Homepage has degraded performance

In 84f0ca1, Shakedown Social - Homepage (https://shakedown.social) experienced degraded performance:

HTTP code: 200
Response time: 10841 ms

Resolved: Shakedown Social - Homepage performance has improved in 8f1e316 after .


Add support for Discord mentions from IRC

Discord autocompletes @User to @User#Discriminator client-side, but the bot doesn't do that, so @User doesn't work as expected.

Discriminators are going away, but that issue remains with new usernames.


[requires.io] dependency update on master branch

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 36.27%. Comparing base (513eb39) to head (9ca36da).
Report is 407 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master      #28      +/-   ##
==========================================
+ Coverage   35.01%   36.27%   +1.25%
==========================================
  Files          13       13
  Lines        1028     1180     +152
  Branches      187      240      +53
==========================================
+ Hits          360      428      +68
- Misses        643      715      +72
- Partials       25       37      +12

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update button-dropdown.mdx

Checklist

[x] Fix linting errors
[] Tests have been added / updated (or snapshots)

Change information
Fix typo in example code

Hi @zainimran, thanks for your contribution!
This section is no longer relevant in the new documentation.


Addons mechanics

For QA: this ticket will be able to testing after next points:

Implementation addons supporting on studio side
Publishing at least one frontend addon. At now, data-tools addon is under development. It's not ready yet. https://app.zenhub.com/workspaces/jmix-frontend-issues-5fe0992a4308f20011f1c913/issues/haulmont/jmix-frontend/512


issue 89: User update removes all user roles

fixed bug in SpringSecurityUiService that was removing all of a User's Role associations upon user update

inspiration was taken from the PR at https://github.com/grails-plugins/grails-spring-security-ui/pull/90

fixed bug where, if all Roles were unchecked for a User, after update, no roles would be displayed
modified test to support change to support change to Role display
fixed failing integration/functional tests by updating chromedriver and geckodriver versions

This PR is for issue #89

@ddelponte could we have a test which verifies this issue?

@sdelamo I think this may be ready for merge

@sdelamo conflicts have been resolved. I think this is ready to merge


DRILL-5113: Upgrade Maven RAT plugin to avoid annoying XML errors

Upgrade to eliminate XML compiler warnings that appear for each sub-project in the Drill build.
Also fixes a Maven warning about a duplicated version error for the dependency plugin (version is inherited from root pom.xml). And removes some trailing spaces.

+1

+1


ClrMD on Linux throws IOException

Using .NET Core 3.1.101:
 $ dotnet --info
.NET Core SDK (reflecting any global.json):
 Version:   3.1.101
 Commit:    b377529961

Runtime Environment:
 OS Name:     clear-linux-os
 OS Version:  32570
 OS Platform: Linux
 RID:         linux-x64
 Base Path:   /home/dmg/dotnet/sdk/3.1.101/

Host (useful for support):
  Version: 3.1.1
  Commit:  a1388f194c

.NET Core SDKs installed:
  2.1.801 [/home/dmg/dotnet/sdk]
  2.2.401 [/home/dmg/dotnet/sdk]
  3.0.100 [/home/dmg/dotnet/sdk]
  3.1.100 [/home/dmg/dotnet/sdk]
  3.1.101 [/home/dmg/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.12 [/home/dmg/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.2.6 [/home/dmg/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.12 [/home/dmg/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.2.6 [/home/dmg/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.0.0 [/home/dmg/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.0 [/home/dmg/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.1 [/home/dmg/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.12 [/home/dmg/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.2.6 [/home/dmg/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.0.0 [/home/dmg/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.0 [/home/dmg/dotnet/shared/Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.1 [/home/dmg/dotnet/shared/Microsoft.NETCore.App]

Running JitDasm with ClrMD 1.1.61812 throws an IOException:
 $ ./JitDasm -l /tmp/hw/linux-x64/hw.dll
System.IO.IOException: I/O error occurred.
   at Microsoft.Diagnostics.Runtime.Linux.Reader.Read[T](Int64 position)
   at Microsoft.Diagnostics.Runtime.Linux.ElfFile..ctor(Reader reader, Int64 position, Boolean isVirtual)
   at Microsoft.Diagnostics.Runtime.Linux.LinuxLiveDataReader.GetVersionInfo(UInt64 baseAddress, VersionInfo& version)
   at Microsoft.Diagnostics.Runtime.ModuleInfo.get_Version()
   at Microsoft.Diagnostics.Runtime.DataTargetImpl.InitVersions()
   at Microsoft.Diagnostics.Runtime.DataTargetImpl.get_ClrVersions()
   at JitDasm.Program.GetMethodsToDisassemble(Int32 pid, String moduleName, MemberFilter typeFilter, MemberFilter methodFilter, Boolean heapSearch) in /home/dmg/projects/public/JitDasm/JitDasm/Program.cs:line 270
   at JitDasm.Program.Main(String[] args) in /home/dmg/projects/public/JitDasm/JitDasm/Program.cs:line 53

Reverting JitDasm to ClrMD to 1.1.57004 solves the issue:
$ ./JitDasm -l /tmp/hw/linux-x64/hw.dll
; ================================================================================
; hw.Program..ctor()
; 30 (0x1E) bytes
; 10 (0xA) instructions

00007F3FD771FE20 55                   push    rbp
00007F3FD771FE21 4883EC10             sub     rsp,10h
00007F3FD771FE25 488D6C2410           lea     rbp,[rsp+10h]
00007F3FD771FE2A 48897DF8             mov     [rbp-8],rdi

00007F3FD771FE2E 488B7DF8             mov     rdi,[rbp-8]
00007F3FD771FE32 E85102FEFF           call    System.Object..ctor()

00007F3FD771FE37 90                   nop
00007F3FD771FE38 488D6500             lea     rsp,[rbp]
00007F3FD771FE3C 5D                   pop     rbp
00007F3FD771FE3D C3                   ret

; ================================================================================
; hw.Program.Main(System.String[])
; 39 (0x27) bytes
; 11 (0xB) instructions

00007F3FD7720110 55                   push    rbp
00007F3FD7720111 4883EC10             sub     rsp,10h
00007F3FD7720115 488D6C2410           lea     rbp,[rsp+10h]
00007F3FD772011A 48897DF8             mov     [rbp-8],rdi

;             Console.WriteLine("Hello World!");
00007F3FD772011E 48BFA07500C03F7F0000 mov     rdi,7F3FC00075A0h
00007F3FD7720128 488B3F               mov     rdi,[rdi]
00007F3FD772012B E880F6FFFF           call    System.Console.WriteLine(System.String)

;         }
00007F3FD7720130 90                   nop
00007F3FD7720131 488D6500             lea     rsp,[rbp]
00007F3FD7720135 5D                   pop     rbp
00007F3FD7720136 C3                   ret

Fixed in #528

@NextTurn Thanks for responsing!
Is there a 1.1 release planned where this will be nugetized?

There should be a new 1.1 release soon. @leculver

Yes, I plan to build one tomorrow assuming everything goes to plan.  (Sometimes our build system for producing new builds gives me trouble.)

The internal build server producing signed builds is, in fact, broken again.  I'm working on fixing it now.  Not sure if I'll get a package out this week.  =/

I've published this build which should contain the fix:  https://www.nuget.org/packages/Microsoft.Diagnostics.Runtime/1.1.116301.  It will show up in visual studio a few hours from now.  Please let me know if you have more problems.
I'm still not able to publish 2.0-beta builds but we are working on that.


Feature / Support links in descriptions

Project organization

Closes #130
Related to trello card

Description

Add react-linkify library to check if text has a link or not to render <Link /> component.
Added new linkfy component which returns JSX.Element

How to test
Check tokens/80001-0x7c68c3c59ceb245733a2fdeb47f5f7d6dbcc65b3-58362971627494992624046520962426828227416842488217022595161705245161716926817 on polygon mumbai testnet
Checklist

[x] Base branch of the PR is dev

I don't see the linkify for the collection. We should have:

user
token
collection

Whoever implemented collections for starter kit seems to be copied content from o-mee, so in this case collection uses <Truncate /> component for description, which in this case, the changes are already there 👍


consolidate builds - reduce number of binaries

We create a new binary for each environment - PRIVNET, TESTNET, and MAINNET.
This results in a a lot of binaries for each release and is difficult to manage.
It would be easier for all operators if they had one zetacored binary and could set the network from a flag or config file.

TODO

[ ] Remove BlockOneDeploySystemContracts
[ ] Find alternative to BlockOneDeploySystemContracts => add it as part of initGenesis or automated script (or no alternative since testnets are launched)
[ ] Add CoreParams as part of genesis state
[ ] Consolidate config (cmd/config_mainnet)
[ ] Consolidate ZetaClient config
[ ] Group all default chain together
[ ] Remove PRIVNET build for smoketests
[ ] Remove TESTNET in CLI helper tests, intx tracket and outtx tracker tests
[ ] Delete test_privnet and test_testnet
[ ] Remove build-specific make commands


Tolerations/NodeSelector for Zarf registry

Is your feature request related to a problem? Please describe.
We'd like to be able to add a NodeSelector and tolerations to the Zarf registry via deployment variables for the zarf init command with --set. The immediate need driving this request is to work around https://github.com/defenseunicorns/zarf/issues/2104, but I think other users would benefit by being able to fine-tune their registry placement or enable the use of Zarf on nodes already tainted for different reasons.
Describe the solution you'd like

Modify the Zarf registry charts to allow templating of the nodeSelector and tolerations keys in the spec.
Add Zarf variables the Zarf registry zarf.yaml to enable setting these w/ --set during zarf init.

Describe alternatives you've considered
Manual modification and/or deployment of custom zarf init package with these set, or patching the registry manifests post-deployment.

Adding good first issue - this would be relatively simple to add as another Zarf variable in the registry zarf.yaml file.  It would just need to be passed down to the deployment.yaml in the chart which we also control.
https://github.com/defenseunicorns/zarf/blob/main/packages/zarf-registry/zarf.yaml#L60
https://github.com/defenseunicorns/zarf/blob/main/packages/zarf-registry/registry-values.yaml#L46
https://github.com/defenseunicorns/zarf/blob/main/packages/zarf-registry/chart/templates/deployment.yaml#L28
https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/

Hello 👋, I would like to pick this issue up if it's available.

Nevermind, I see @waveywaves got it, thanks!


Failed to restore connection to window within the allocated timeout.

What is your Test Scenario?

As per:
https://stackoverflow.com/questions/66555583/is-there-a-way-to-wait-for-a-window-to-close-with-testcafe
We have a few test flows which go through the PayPal window twice. It seems that TestCafe fails to return to the main window, once the child window is closed (after opening for the 2nd time).
What is the Current behavior?

TestCafe fails with Failed to restore connection to window within the allocated timeout. (for desktop chrome).
What is the Expected behavior?

What is your web application and your TestCafe test code?

Your website URL (or attach your complete example):

Your complete test code (or attach your test files):

 import { Selector, t } from 'testcafe';

const submitWithPaypalButton = async (ppmu = false) => {
  const paypalIframe = Selector('[data-testid="paypal-button"] iframe').withAttribute('src');
  const ppmuPaypalIframe = Selector('#modal-paypal-button iframe').withAttribute('src');
  const payWithPaypalButton = Selector('[data-funding-source="paypal"]').filterVisible();

  const paypalIframeSelector = ppmu ? ppmuPaypalIframe : paypalIframe;
  await t
    .expect(paypalIframeSelector.visible)
    .ok()
    .switchToIframe(paypalIframeSelector)
    .hover(payWithPaypalButton)
    .click(payWithPaypalButton)
    .wait(500);
};

const paypalLogin = async () => {
  const emailInput = Selector('#email');
  await t
    .expect(emailInput.visible)
    .ok({ timeout: 30000 })
    .typeText(emailInput<EMAIL_ADDRESS>    .click(Selector('#btnNext'))
    .typeText(Selector('#password'), 'password1')
    .click(Selector('#btnLogin'));
};

const completePaypalMiniWindow = async ({ shouldLogin = true, oneTimePayment = false } = {}) => {
  const consentButton = Selector('#consentButton, [data-test-id="continueButton"]').filterVisible();
  const submitButtonInitial = Selector('[data-testid="submit-button-initial"]');
  if (shouldLogin) {
    await paypalLogin();
  }

  const continueButton = oneTimePayment ? submitButtonInitial : consentButton;
  const paymentOptions = Selector('#paymentMethod, [data-testid="stacked-payment-options"]').filterVisible();

  await t
    .expect(paymentOptions.visible)
    .ok()
    .hover(continueButton)
    .click(continueButton);
};

fixture('This is a demo fixture').page('https://www.change.org');

test.only('This is a demo test', async () => {
  // Navigate to the Sponsorship page, enter promotion amount and pay with PayPal

  await t
    .navigateTo('/p/change-org-to-test-a-small-petition/sponsors/new?country_code=FR&lang=fr-FR')
    .click(Selector('[data-testid="cookie-wall-accept"]'))
    .expect(Selector('.js-payment-form').visible)
    .ok()
    .typeText(Selector('[data-testid="payment-form-amount-input"]'), '1', { replace: true })
    .click(Selector(`[data-testid="payment-option-button-paypal"]`));

  await t
    .typeText(Selector('[data-testid="input_email"]').filterVisible<EMAIL_ADDRESS>    .typeText(Selector('[data-testid="input_confirmation_email"]').filterVisible<EMAIL_ADDRESS>    .typeText(Selector('[data-testid="input_first_name"]'), 'first')
    .typeText(Selector('[data-testid="input_last_name"]'), 'last');
  await submitWithPaypalButton();

  // PayPal Window
  await completePaypalMiniWindow({ oneTimePayment: true });

  // Accept Upsell
  await submitWithPaypalButton(true);
  await completePaypalMiniWindow({ shouldLogin: false });
  await t.expect(Selector('[data-testid="ppmu-ty"]').visible).ok();
});

Your complete configuration file (if any):

{
  "browsers": ["chrome"],
  "src": "./tests/**/*.js",
  "clientScripts":[
    {
      "module":"axe-core/axe.min.js"
    }
  ],

  "assertionTimeout": 15000,
  "pageLoadTimeout": 30000,
  "selectorTimeout": 15000,

  "disableMultipleWindows": false,

  "quarantineMode": false,
  "skipJsErrors": true,

  "disablePageCaching": true,

  "reporter": [
    {
      "name": "xunit",
      "output": "artifacts/test-results/results.xml"
    },
    {
      "name": "spec"
    }
  ],

  "screenshots": {
    "fullPage": true,
    "takeOnFails": true,
    "pathPattern": "${TEST_ID}/${RUN_ID}_${FILE_INDEX}.png",
    "path": "artifacts/screenshots"
  }
}

Your complete test report:

    ✖ This is a demo test (screenshots: /pathqaa/artifacts/screenshots/test-1/_errors/1.png)

   1) Failed to restore connection to window within the allocated timeout.

      Browser: Chrome 89.0.4389.90 / macOS 10.15.7
      Screenshot: /path/artifacts/screenshots/test-1/_errors/1.png

         72 |  await completePaypalMiniWindow({ oneTimePayment: true });
         73 |
         74 |  // Accept Upsell
         75 |  await submitWithPaypalButton(true);
         76 |  await completePaypalMiniWindow({ shouldLogin: false });
       > 77 |  await t.expect(Selector('[data-testid="ppmu-ty"]').visible).ok();
         78 |});

         at <anonymous> (/path/tests/demo/test.js:77:63)
         at asyncGeneratorStep (/path/tests/demo/test.js:3:302)
         at _next (/path/tests/demo/test.js:3:640)

 1/1 failed (1m 26s)

Screenshots:

![1](https://user-images.githubusercontent.com/37812673/111845361-e8c19b00-88c1-11eb-8030-d27ff24fc411.png)

Steps to Reproduce:

Go to my website ...
Run test code (use your own email and password)...
See the error...

Your Environment details:

testcafe version: 1.12.0
node.js version: 12.14.1
command-line arguments:  testcafe chrome
browser name and version: Chrome 89.0.4389.82
platform and version:
other:

The error message does not match the test you submitted. Please check the data so that we can reproduce the problem and offer you a solution.

I'll update the configuration file to use chrome rather than chome:emulation.... That should let you see the error.
Can you tell me what other error you're seeing? (I'm about to raise a separate bug around PayPal being blocked in emulation mode)

I didn't get any errors. I mean that in your test report, there is code that is not available in your test file. For instance, the assertPPMUThankYou function is missing in the test. Check the test report and the test you submitted so that we can verify the issue. Also, please modify the test so that there is no payment process in it. Thank you.

Also, please modify the test so that there is no payment process in it.

I've been unable to reproduce this issue without  the payment process. I'll keep trying though. In the meantime, we can refund all of the promotions made for that petition.
I've updated the error, I converted assertPPMUThankYou to the individual steps, and forgot to copy in the new console error. I've also added a screenshot, which just shows our Thank You page (so you can see it successfully navigates to that page after completing the PayPal window).

Hello @rob4629,
Please share a web app project sample so that we can reproduce the issue by using the PayPal sandbox account.

I'm working on trying to reproduce this in my sample web app... but not having much luck. I'll continue with it next week and update you then. Sorry for the inconvenience

Sorry for the delay, we're going to set up access to our deployment environment, so you can test using a sandbox paypal account. I'll send an email to<EMAIL_ADDRESS>with the details, once its ready.

For the team: take a look at this private ticket to reproduce the issue - https://supportcenter.devexpress.com/internal/ticket/details/T990544

I also have similar issue. Is there any updates on this?