implements common pill interface, adds userspace to +solid

This PR updates all our pills to use a consistent interface: a 3-tuple of boot-formulas, kernel/module events, and userspace events. (These events are technically (list ovum), ie, (list (pair wire card)).)
This interface is basically the already existing interface to of +brass, except that all three elements are now lists. The boot formulas are to be evaluated with the lifecycle formula [%2 [%0 3] %0 2], producing the formal Arvo interface (the outer gate). The subsequent event-lists are to be enqueued as normal events.
This is a pretty natural structure for +brass, which exists as a recipe for creating the True Boot Sequence. I've extended it to +solid and +ivory to lower the conceptual overhead of what exactly a pill is, and to increase developer flexibility moving forward. You can think of these various pills as occuping positions on a dial that controls how long it takes to boot a ship -- +solid is more-or-less already booted, +brass is completely proper and double-compiled, and +ivory is lightweight.
+solid has also been extended to include a full copy of userspace -- non-galaxy ships now boot into a working :dojo as quickly as galaxies, and initial syncs now take place in the background, no longer blocking userspace. (This further convergences us with cc-release, which boots from the +brass pill into a full Arvo.)
There's an issue worth noting here; stars/planets/moons cannot sync a desk with their sponsor/parent unless they share a common-ancester commit (a merge-base, for %clay's 3-way diff). Booting into a full Arvo means there is no merge-base. The solution implemented here is to perform %init merges up to and including the first merge caused by a sync (an %init merge throws away local state and fully accepts the remote state). This works as implemented, for all classes of ships. But it's definitely awkward, and potentially error prone (if the network is slow and a user makes local edits before the first sync merge, for instance). In the long run, it would be preferrable for %clay to have some kind of internal content-addressing, or some other mechanism for converging with a remote desk without a merge-base.

urbit/urbit#1085 is the dual of this PR.

I worry a bit about blowing away user data, even if it only happens once a minute after the user boots. This may not be a problem in practice in the short run, but I can totally see this being a real issue once we start using the filesystem for real things.
Otherwise, I don't see anything wrong with this patch; I do wonder how it feels. If I type .p/pill +solid in the dojo, what's the additional overhead of generating the filesystem event? If I'm booting from a pill, is there no additional overhead since we're replacing the synthetic event created with -A with the one in the pill?

I agree. I also don't like that it's a hardcoded number of revisions (different for the home desk) that marks the threshold between %init and normal merges. I don't know how to implement this differently from outside of %clay, and it seems like it'd be nontrivial to do it properly within %clay.
There aren't any substantial timing changes to first-boot or +solid. Adding userspace to the pill is shockingly fast (almost 400 files!).
Here's some timing examples. I didn't rigorously test each scenario multiple times, so I'm not sure what the normal variance is -- I've seen a couple seconds in either direction of these numbers. These were all debugoptimized builds.
First, booting a new fake-zod. Note that these exit after the first clay %into, but before the second.
release-candidate:
$ time debug/urbit -F zod -A ./arvo -s -c -x rc-zod
...
real    0m34.802s
user    0m33.217s
sys     0m0.761s

This PR, with a local Arvo sync:
$ time debug/urbit -F zod -A ./arvo -s -c -x zzzod
...
real    0m37.553s
user    0m35.617s
sys     0m0.858s

This PR, syncing from the pill:
time debug/urbit -F zod -u https://bootstrap.urbit.org/git-51ca94d192.pill -c -x zzzod
...
real    0m38.452s
user    0m36.520s
sys     0m0.842s

Soliding a pill on release-candidate:
> :time _* +solid
>=
[%took ~m1.s28..a737]

Soliding a pill on this PR:
> :time _* +solid
>=
[%took ~m1.s34..9077]

I would guess that the boot overhead is in downloading an 8 MB pill. I expected a slight speedup retrieving the filesystem sync from the pill instead of constructing it from disk, but maybe that's also offset by the time it takes to read the pill into an atom (twice, unfortunately, due to the vagaries of the startup process).

My comment was vague, but so's my idea ... I mean something like "%clay should use content-addressing of files and/or commits to find something like a merge-base". I haven't thought through what our options are in the case that there is no true merge-base (ships booted from different pills, no one commit in either's history is the same).
There's also the somewhat related need to reduce network traffic, see #551.

I like @belisarius222's idea of blocking any filesystem changes until the parent sync has finished.
I forget if it was ever properly implemented, but in theory %clay should ask for the parent's yaki (or maybe the whole ankh), check which lobes it doesn't already have, and ask for only those.  In this case, syncing the parent's data should be very fast if its files are pretty similar to what's in the pill.
If that is implemented, another option is to not initialize a child with a full filesystem, but only with lat.ran (ie sync the blob store but not the commits), so the sync from the parent is genuinely the first commit, but it should be quite fast.

Long-term, presumably we want the not-O-all-files thing of having directory
entries also in the blob store, as git does it; in which case you would be
able to just compare the root directory hashes.
On Tuesday, 4 December 2018, Philip Monk<EMAIL_ADDRESS>wrote:

I like @belisarius222 https://github.com/belisarius222's idea of
blocking any filesystem changes until the parent sync has finished.
I forget if it was ever properly implemented, but in theory %clay should
ask for the parent's yaki (or maybe the whole ankh), check which lobes it
doesn't already have, and ask for only those. In this case, syncing the
parent's data should be very fast if its files are pretty similar to what's
in the pill.
If that is implemented, another option is to not initialize a child with a
full filesystem, but only with lat.ran (ie sync the blob store but not
the commits), so the sync from the parent is genuinely the first commit,
but it should be quite fast.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/909#issuecomment-444313014, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhlqXrHIidU9OQ9BIkStJSMMuml_kks5u1xTdgaJpZM4ZBlx5
.

@philipcmonk has some war stories back from when sync was directly in clay!
But it might be time for another go; and even if we keep the update loop in
userspace, merges themselves still need to work correctly at that level,
and right now definitely don't.
On Tuesday, 4 December 2018, Ted Blackman<EMAIL_ADDRESS>wrote:

@belisarius222 commented on this pull request.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/urbit/arvo/pull/909#discussion_r238902656, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxXhr6BUXpKFIMZGK6RGyQKLoI76_WUks5u1yDrgaJpZM4ZBlx5
.


[SPARK-34211][SQL][TEST] Benchmark TPC-DS with 1GB scale factor

What changes were proposed in this pull request?
This pr add a new Github action to benchmark TPC-DS with 1GB scale factor.
Why are the changes needed?

To track performance changes:
http://apache-spark-developers-list.1001551.n3.nabble.com/VOTE-Release-Spark-3-1-1-RC1-tt30579.html#a30603
To track the compatibility of Parquet upgrades:
https://issues.apache.org/jira/browse/SPARK-26346

Does this PR introduce any user-facing change?
No.
How was this patch tested?
N/A.

Test build #134395 has started for PR 31303 at commit e8faad3.

Test build #134395 has started for PR 31303 at commit e8faad3.

Test build #134395 has finished for PR 31303 at commit e8faad3.

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

Test build #134395 has finished for PR 31303 at commit e8faad3.

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

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

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

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

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

Test build #134397 has started for PR 31303 at commit 9da5102.

Test build #134397 has started for PR 31303 at commit 9da5102.

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38983/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38983/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38983/

Kubernetes integration test status success
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/38983/

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

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

Test build #134397 has finished for PR 31303 at commit 9da5102.

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

Test build #134397 has finished for PR 31303 at commit 9da5102.

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

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

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

cc @Ngone51, @dongjoon-hyun, @cloud-fan, @peter-toth FYI

cc @Ngone51, @dongjoon-hyun, @cloud-fan, @peter-toth FYI

Is the perf inconsistency big? It will give you a rough numbers to check. I was also thinking this as a test. I remember we faced a case that TPSDS was broken whereas the Spark tests pass.
The resource is indeed a problem. It has been a problem so far. I think we have added some jobs if they are worthwhile though.
I'm okay to wait until we have some more resources and don't add new jobs for the time being.

Is the perf inconsistency big? It will give you a rough numbers to check. I was also thinking this as a test. I remember we faced a case that TPSDS was broken whereas the Spark tests pass.
The resource is indeed a problem. It has been a problem so far. I think we have added some jobs if they are worthwhile though.
I'm okay to wait until we have some more resources and don't add new jobs for the time being.

Actually, I understand the requirement and the intention because I also reported SPARK-33822 (TPCDS Q5 fails if spark.sql.adaptive.enabled=true).

I remember we faced a case that TPSDS was broken whereas the Spark tests pass.

@wangyum  Could you provide a result in your repository together which is requested by @HyukjinKwon ? It depends on the characteristic of the job.

Is the perf inconsistency big? It will give you a rough numbers to check.

BTW, on top of the above issues, this is not safe in terms of security. Recently, Apache Infra team introduced strict security enforcements by banning the runnable source of GitHub Action and we have no available option when the 3rd party repositories are compromised . Even the docker image repo, we should migrate ApacheSparkGitHubActionImage to Spark's official branch. For the two repositories in this PR, the migration is possible?

Actually, I understand the requirement and the intention because I also reported SPARK-33822 (TPCDS Q5 fails if spark.sql.adaptive.enabled=true).

I remember we faced a case that TPSDS was broken whereas the Spark tests pass.

@wangyum  Could you provide a result in your repository together which is requested by @HyukjinKwon ? It depends on the characteristic of the job.

Is the perf inconsistency big? It will give you a rough numbers to check.

BTW, on top of the above issues, this is not safe in terms of security. Recently, Apache Infra team introduced strict security enforcements by banning the runnable source of GitHub Action and we have no available option when the 3rd party repositories are compromised . Even the docker image repo, we should migrate ApacheSparkGitHubActionImage to Spark's official branch. For the two repositories in this PR, the migration is possible?

If I remember correctly, the purpose of banning GitHub Actions and 3rd part repository was to avoid running unreviewed codes (https://github.com/apache/spark/pull/31104#discussion_r554498229), and we used it by using a specific commit.
Yeah, it would be great if we can tell if the perf diff is considerably big, @wangyum. If it's too big, it will be less making sense to add.

If I remember correctly, the purpose of banning GitHub Actions and 3rd part repository was to avoid running unreviewed codes (https://github.com/apache/spark/pull/31104#discussion_r554498229), and we used it by using a specific commit.
Yeah, it would be great if we can tell if the perf diff is considerably big, @wangyum. If it's too big, it will be less making sense to add.

Yeah, it would be great if we can tell if the perf diff is considerably big, @wangyum. If it's too big, it will be less making sense to add.
And, yes it would be great if there are ways around to use them. If I remember correctly, the purpose of banning GitHub Actions and 3rd part repository was to avoid running unreviewed codes (#31104 (comment)).

Yeah, it would be great if we can tell if the perf diff is considerably big, @wangyum. If it's too big, it will be less making sense to add.
And, yes it would be great if there are ways around to use them. If I remember correctly, the purpose of banning GitHub Actions and 3rd part repository was to avoid running unreviewed codes (#31104 (comment)).

We can either fork spark and run benchmarks with Github actions under your own account, or set up AWS machines to run benchmarks like @maropu did.

I agree that we can still track some big perf differences (like 10x slower) with Github actions, but running benchmarks in Github action takes a lot of resources and may not pay off if it can only catch big perf differences that are rare.
We can either fork spark and run benchmarks with Github actions under your own account, or set up AWS machines to run benchmarks like @maropu did.

Close it. Thank you all.

Close it. Thank you all.

running benchmarks in Github action takes a lot of resources

Just be correct, doing 1GB is not a lot. It takes less than an hour which is same as other parts of our tests. As I said earlier, it's not only performance but also test, see SPARK-33822.
But it's fine to drop it given that the resource issue going on globally in ASF repos.

running benchmarks in Github action takes a lot of resources

Just be correct, doing 1GB is not a lot. It takes less than an hour which is same as other parts of our tests. As I said earlier, it's not only performance but also test, see SPARK-33822.
But it's fine to drop it given that the resource issue going on globally in ASF repos.

Once we resolve the resource limitation issue, it would be great if we can bring this back.

Once we resolve the resource limitation issue, it would be great if we can bring this back.

Thank you for the decision all!

Thank you for the decision all!


Mr 12

About

Another splendid idea. Would you mind adding a test to test_console_script.py? When pytest runs it'll run coverage too so you should end up with 100% coverage at the end (actually it's 99.x%

I need that the issue on missing  https://github.com/masaccio/compact-json/issues/17 be fixed to have the pytest working my side first.


Use Unit8Array instead of Buffer

I would like to propose that we change Buffer to Uint8Array in this library.
The current library utilizes the Buffer class from Node.js. When Node.js first came out, Uint8Array didn't exist, so we had to create a Buffer. However, Buffer is now outdated. Now, Buffer is an instance of Uint8Array, but Buffer is not supported in browsers and never will be. Furthermore, Buffer exposes information in global variables, which can cause potential security issues.
Now we can use Uint8Array, a general-purpose byte array that can be used consistently across servers and browsers.
By switching to Uint8Array, this library gains the following benefits:

Cross-platform compatibility:
Uint8Array is a standard data structure in JavaScript, so it can be used seamlessly in both server and browser environments. This makes the library more accessible and easier to integrate into a wider range of projects.
Consistent with modern JavaScript practices:
Using Uint8Array aligns with the trend toward using typed arrays in JavaScript, which is more consistent with how data is represented and processed in modern programming languages.

Implementing this change may require some changes, as there are subtle incompatibilities between Uint8Array and Buffer.
I believe this proposal will benefit current library and users, and welcome any feedback on this topic.

Thank you :) I will try it too


Submit function

This PR adds the Submit function and some helpers functions to submit transactions to the XRP Ledger.
I also renamed a "client" directory to requests which is more appropriate in my opinion as most of the XRPL requests are in this directory. I did this as I had some import conflicts.

@GuillemGarciaDev I updated the code. As we are passing a tx_blob to the function, I thought that SubmitTransactionBlob would make more sense as a name.
We could then implement another function SubmitTransaction that would also accept a wallet as argument and the transaction object (Payment, TrustSet...).
With that wallet we would sign the transaction and then submit to the ledger.
What do you think ?


scss support

It looks like the sass support works fine, but there's no option for scss by default, or am I missing something? I can submit a pull request tomorrow if I haven't missed anything :D

it looks like theres a compass flag, but that uses compass middleware. should there be a scss flag that uses node-sass with indent syntax set to fault?

$ express -h

  Usage: express [options] [dir]

  Options:

    -h, --help          output usage information
    -V, --version       output the version number
    -e, --ejs           add ejs engine support (defaults to jade)
        --hbs           add handlebars engine support
    -H, --hogan         add hogan.js engine support
    -c, --css <engine>  add stylesheet <engine> support (less|stylus|compass|sass) (defaults to plain css)
        --git           add .gitignore
    -f, --force         force on non-empty directory

When you create a project with express -css sass command, you can use both sass and scss file extensions and node-sass will handle them both. This command will add node-sass-middleware dependency and use it as
app.use(require('node-sass-middleware')({
  src: path.join(__dirname, 'public'),
  dest: path.join(__dirname, 'public'),
  indentedSyntax: true,
  sourceMap: true
}));

in your code. As you can see from their README, it recompiles both sass and scss files:

Recompile .scss or .sass files automatically for connect and express based http servers.

I don't get where the problem is. Do you exactly want a css option like scss which will eventually do the same thing as sass? Or is there anything that you can do with another middleware but not this one?

I just took a look into this and indeed, .scss is not compiled with the --css=sass option, even though node-sass-middleware can do it. Looks like it's because the indentedSyntax option for the module chooses between .scss and .sass support.
Adding a scss option that outputs without that option will get scss support as a direct option :)

So looking more into this, the --css is meant to declare the engine you want to use, which is going to be sass for the sass engine. I'm updating the generator to include a comment for what code to change to choose between sass and scss files for the sass engine 👍

Generating with --css=sass will now have the following code block in app.js:
app.use(sassMiddleware({
  src: path.join(__dirname, 'public'),
  dest: path.join(__dirname, 'public'),
  indentedSyntax: true, // true = .sass and false = .scss
  sourceMap: true
}));


The scores are presented in the form of a ‘score board’ where the top guesser is on position 1. etc.

This means during the game right? @radubauzh

@radubauzh I created the scoreboard during game but it is still not sorted...

@sumsumcity I'll look at it this saturday

@sumsumcity as discussed, the scoreboard is already sorted.


[HW] Michel de Ru

Name: Michel de Ru
Email<EMAIL_ADDRESS>Linkedin Profile: https://www.linkedin.com/in/mderu/
Attach the homework screenshots below for both step II and step III:

Thank you Michel
here is your well deserved badge:
<EMAIL_ADDRESS>


Quarantine in audit logs

@ArvindHarinder1 : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Add CFLAG -fPIC compiler in Makefile

On Linux Ubuntu 16.4 (Digital Ocean) I had this output trying to compile:
/usr/bin/ld: /tmp/cctjVSzX.o: relocation R_X86_64_32S against .rodatacan not be used when making a shared object; recompile with -fPIC
I added -fPIC flag in Makefile and the library was generated without errors.

Thanks. I've added the flag to the Makefile.


Change constructor visibility for WebSocketSubscribtionTransport

Linked to #2347 .
I'm not sure what's your git workflow, feel free to change the base if it's not supposed to be merged directly to master.
I only made the WebSocketSubscriptionTransport constructor public, to be able to use this class in a custom implementation of SubscriptionTransport.Factory.

@k-misztal: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/


Update Mailpit to latest version 1.20.2

Is there an existing issue for this?

[X] I have searched the existing issues

Is your feature request related to a problem?
I discovered some strange problems with urls in emails caught by mailpit.
Some urls in emails get two points ("..") where only one point should be.
For example an url should look like this:
https://test.ddev.site/?jumpurl=https://test.ddev.site/_assets/0ded769/Images/mailerping.gif

but looks like:
https://test.ddev.site/?jumpurl=https://test.ddev.site/_assets/0ded769/Images/mailerping..gif

See the last part /mailerping..gif which has two points.
This happens not always at the same place. In some generated mails the double point appear at a different place like so:
https://test.ddev.site/?jumpurl=https://test..ddev.site/_assets/0ded769/Images/mailerping.gif

I don't know if this is a problem in mailpit 1.19.3 but there where two node library updates happens until 1.20.2 which may contain a fix for this issue.
Describe your solution
Update Mailpit to latest version 1.20.2
Describe alternatives
No response
Additional context
No response

After some more tests, I discovered that this problem only appears if more than 10 mails in the inbox of mailpit.
I sent the same two mails several times.
The 10th mail is the first one with the described problem. Also the 11th is corrupt, this the wrong additional point at a different place.

Hi @mediaessenz - You can update to latest mailpit by adding a .ddev/web-build/Dockerfile.mailpit with these contents:
RUN set -x && set -o pipefail && tag=$(curl -L --fail --silent "https://api.github.com/repos/axllent/mailpit/releases/latest" | jq -r .tag_name) && curl --fail -sSL "https://github.com/axllent/mailpit/releases/download/${tag}/mailpit-linux-${TARGETPLATFORM##linux/}.tar.gz" -o /tmp/mailpit.tar.gz && tar -zx -C /usr/local/bin -f /tmp/mailpit.tar.gz mailpit && rm /tmp/mailpit.tar.gz

Please do that and see what happens, and if the error is still there, please open a comprehensive issue in https://github.com/axllent/mailpit/issues (I do see https://github.com/axllent/mailpit/issues/348 and https://github.com/jhillyerd/enmime/issues/340, not sure if they're related to the problem you're reporting)
Note that mailpit will automatically be the latest version when the next DDEV release comes out.

After updating mailpit to 1.20.2, the problems have become even worse.
With this version I have the behaviour in every mail, independent of the number of mails in the inbox.
I will report it to the mailpit project.

So it sounds like we do have work to do? I wonder why we haven't seen this before then. If we have work to do, please open an issue with the exact work to be done.


Zoe: Watch simcitymodapk.info

Zoe requests the watch of the watch_keyword simcitymodapk\.info. See the Metasmoke search here and the Stack Exchange search here.

simcitymodapk\.info has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Coverage remained the same at 65.091% when pulling c9cc060d55ab1ce40f4846fd9da4eeb3b75ec597 on auto-blacklist-1524416551.6164942 into 70215016a2c0f1074d77f5ca7cf67831a00313ca on master.

!!/approve


4.11.0 minimal bundle => No renderer for attachment for screen reader of type XY

Screenshots

Version
4.11.0 / NPM ('botframework-webchat/lib/index-minimal') / (but it also happening using CDN minimal bundle)
Describe the bug
We're using the minimal bundle for our webchat. We're rendering all of the messages by our self.
Since we've updated to 4.11.0, all activities are still rendered as before, but there are errors in the console about missing renderers for screen readers, like:
ErrorBox.js?ffa8:44 Error: No renderer for attachment for screen reader of type "application/vnd.microsoft.card.hero"
Steps to reproduce

Run this sample 01.getting-started/b.minimal-bundle
Open console in developer tools
Type "help"
Observe errors

Expected behavior
I expect to have one of the following:

renderers in that bundle
no renderers but no errors
documented a way how to suppress/ignore errors from missing renderers => any idea to work around the issue?

[Bug]

Hi @martinoss, thanks for filing this issue. I have a repro of this, and will investigate the problem. I don't think I'll get an answer to this thread today, but I will get it in as soon as possible early next week.

Composer.js:

A couple of things:

I agree that these errors should be suppress-able, particularly for situations like using minimal bundle. It looks like you can disable the warning by adding the following middleware: (code from __tests__/html/middleware.liveRegionAttachment.noWarning.returnFalse.html)

But making this necessary for minimal bundle seems a bit much.

At the very least, we should have a sample or documentation for the above.
In the end, if the customer doesn't want to make a live renderer for the attachment, it's not our job to force them. If we make it suppress-able, at least the customer is guaranteed to see these errors, and will have to take action to suppress them (though of course, we recommend making the renderer instead)

We should verify that the screen reader error in particular is only showing up for:

No renderer at all
Using a middleware renderer, but doesn't have a screen reader one

Create a sample for screen reader renderer. If the customer is using their own renderer, there should be an easy way to verify how to write the screenreader middlware, particularly because a11y is a high priority for this project.

In the past, we have asserted that we won't guarantee our samples being accessible as they are code examples only, and not meant to be used in production. I think this is a different situation in that we are 'enforcing' an accessible live region/screen reader renderer, and the customer needs to be able to easily find how to do that.
@martinoss please try the test code from the second screencap above. If this does not suppress the errors, feel free to report back here.

@corinagum Thank your for investigating this. Your suggestion successfully suppress the errors, many thanks for this.
I also want to let you know that I had to implement the same workaround for activity type "messageReaction" in the activity middleware.
activityMiddleware = () => (next: any) => (...setupArgs) => {
  const [card] = setupArgs

  if (card.activity.type === "messageReaction") {

    // There is no renderer for this activity, so skip it to avoid console errors.
    return false;
  }

  return next(...setupArgs)
};

Thanks for reporting back. 👍

I had to implement the same workaround for activity type "messageReaction" in the activity middleware.

Web Chat doesn't natively support messageReaction, so this is the expected behavior when receiving that activity type.

I added needs-team-attention label to discuss how to appropriately handle lack of screen reader renderer in minimal bundle. See first item in https://github.com/microsoft/BotFramework-WebChat/issues/3625#issuecomment-740261281 for potential R12 planning.

I added needs-team-attention label to discuss how to appropriately handle lack of screen reader renderer in minimal bundle. See first item in https://github.com/microsoft/BotFramework-WebChat/issues/3625#issuecomment-740261281 for potential R12 planning.

change to warning, not error
suppress warning? React props.ref - console log ==> warning, align with this behavior / production

npm build - production vs start (dev)
if suppressable, write sample
default props (not style options)
suppress red box in production & no announcement in screenreader (when WC dep in CRA)

Sample for suppressing warnings (from test code)
dev mode, non-suppressed - have screenreader renderer saying activity could not be rendered

change to warning, not error
suppress warning? React props.ref - console log ==> warning, align with this behavior / production

npm build - production vs start (dev)
if suppressable, write sample
default props (not style options)
suppress red box in production & no announcement in screenreader (when WC dep in CRA)

Sample for suppressing warnings (from test code)
dev mode, non-suppressed - have screenreader renderer saying activity could not be rendered


Update resource-manager-cluster.md

Updated commitment-tier after new support agreement

@guywi-ms

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

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


Log user defined values

Allow users to store custom information in runs, something like recipy.logValue(name, value)
The use case is workflow engine noodles https://github.com/NLeSC/noodles where we want to keep track of which function/process/machine created a result.
But it is also useful when working with multiple people on the same project.
This could be a way of solving #48, although it is not effortless.

What do you think is the best way to deal with this? Should have a custom-values key in the data for a run and then store as a set of key-value pairs within that?

Yes, seems like a reasonable approach!

This should be pretty easy to implement, if one of the 'newbies' from the PyConUK sprint want to have a go at it? @trbedwards @DavidS48 @BevelledEdge

I'll have a go at this


runMigration() fails while importing the migration file using ESM

Describe the bug
The dynamic import in the migrator.ts line 411 const migrationFunctions = await import(migrationFilePath) as IMigrationModule fails with the following TypeError:
TypeError: Unknown file extension ".ts" for /migrations/1704814522221-test.ts at new NodeError (node:internal/errors:405:5) at
Object.getFileProtocolModuleFormat [as file:] (node:internal/modules/esm/get_format:79:11) at defaultGetFormat
(node:internal/modules/esm/get_format:124:36) at defaultLoad (node:internal/modules/esm/load:84:20) at nextLoad
 (node:internal/modules/esm/loader:163:28) at ESMLoader.load (node:internal/modules/esm/loader:603:26) at
ESMLoader.moduleProvider (node:internal/modules/esm/loader:457:22) at new ModuleJob
(node:internal/modules/esm/module_job:64:26) at ESMLoader.#createModuleJob (node:internal/modules/esm/loader:480:17) at
ESMLoader.getModuleJob (node:internal/modules/esm/loader:434:34) {code: "ERR_UNKNOWN_FILE_EXTENSION", stack:
"TypeError: Unknown file extension ".ts" for /Users…duleJob (node:internal/modules/esm/loader:434:34)", message: "Unknown file
extension ".ts" for /Users/stephan/Do…object-pool-data/migrations/1704814522221-test.ts", toString: Function,
Symbol(kIsNodeError): true}

To Reproduce
Create a new migration using the CLI in an nestJS application in ESM
Start the nestJS Service with the on startup migration functionality in place.
Expected behavior
The dynamic import should also handle the migration files in ESM mode by rewriting the ts file-ending to .js

Short answer is no, since transpilation of .ts migration files happens on runtime not compile time, interesting case...

@stephan-mitt can you provide a sample repo with minimal setup of nest ESM + ts-migrate-mongoose and how you configured it, so I can run same repo for tests?

@ilovepixelart I have quickly converted your nestJS example to run in our ESM setup with the same error at service startup: https://github.com/stephan-mitt/ts-express-nest/tree/esm-problem

Spent some time yesterday evening researching this stuff, tried ts-node/register, esbuild-register, @swc-node/register and all of them fail, and found a not on @babel/register:
https://babeljs.io/docs/babel-register
Note: @babel/register does not support compiling native Node.js ES modules on the fly, since currently there is no stable API for intercepting ES modules loading.
Now I'm wondering, how we can approach this if node does not have APIs to do that


remove system calls in favor of FileUtils and RubyZip

remove system calls in favor of FileUtils and RubyZip for Win compatibility

:+1:

2.1.0? 2.0.1?

I'd personally call it a bug that it didn't run on Win- I don't think the
API changed. So I'd vote for 2.0.1.
On Sat, Feb 7, 2015 at 5:22 PM, Chris Beer<EMAIL_ADDRESS>wrote:

2.1.0? 2.0.1?
—
Reply to this email directly or view it on GitHub
https://github.com/projecthydra/jettywrapper/pull/37#issuecomment-73386133
.


Invoke-RestMethod DNS issue

`` Invoke-RestMethod` : The remote name could not be resolved: 'umcs.comcast.net'
At C:\telegraf\Get-Comcast-Usage.ps1:64 char:16

... obal:resp = Invoke-RestMethod -WebSession $session -Method POST -Body ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Invoke-RestMethod], WebException
FullyQualifiedErrorId : System.Net.WebException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

Invoke-RestMethod : The remote name could not be resolved: 'umcs.comcast.net'
At C:\telegraf\Get-Comcast-Usage.ps1:69 char:15

... lobal:tmp = Invoke-RestMethod -WebSession $session -Method POST -Body ...

            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

CategoryInfo          : NotSpecified: (:) [Invoke-RestMethod], WebException
FullyQualifiedErrorId : System.Net.WebException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand ``

Should be noted it was working before, I know these scripts are "As Is" but thought would let you know


fix: detect smart contracts for every evm chains

Description
The useIsSmartContractAddress address hook and isSmartContractAddress helper should take an non-optional chainId parameter because we need to take in account the multichain nature on features such as the swapper

Pull Request Type

[x] :bug: Bug fix (Non-breaking Change: Fixes an issue)
[ ] :hammer_and_wrench: Chore (Non-breaking Change: Doc updates, pkg upgrades, typos, etc..)
[ ] :nail_care: New Feature (Breaking/Non-breaking Change)

Issue (if applicable)

closes #7328
Risk
⚠  High, this PR already did cause us to revert because it was blocking a few trades such as RUNE => BTC
Testing
With a smart contract wallet such as gnosis safe, and with another classic wallet such as metamask:

Please be sure that the swapper is entirely working as expected, including non EVM trades/bridges such as RUNE => BTC
use the swapper and verify that the from asset trigger the manual destination address input if it's a smart contract wallet or not depending if the wallet is not a smart contract
Thorchain savers works as expected (deposit, withdraw
Fox voting power is working as expected
Thorchain deposit liquidity into pool is working as expected
Loan repay (I couldn't test as I don't have any loans)

Engineering

Operations

Screenshots (if applicable)
Safe wallet with avalanche

Safe wallet with ethereum

Another wallet

Ethereum

Thorchain smart contract wallet not supported

Add Liquidity smart contract wallet not supported

add liquidity non-smart contract address

Savers deposit confirm smart contract address

Savers deposit confirm classic wallet

Withdraw savers confirm smart contract address

Withdraw savers deposit confirm classic wallet
I couldn't test because I don't have any position on this wallet and not enough funds
Fox voting power smart contract wallet
I couldnt test as I have no FOX on my smart contract wallet
Fox voting power with classic wallet

Rune => Avax

Rune => BTC

A couple follow up questions:

Are both isLoading and isFetching necessary? Haven't seen much use of isFetching and just curious the rationale
Do we actually want to use the loading/fetching state as part of the disabled logic? I would think we would use those for the loading state of the button and then disable only on the isSmartContract value being true basically. Doesn't really change behavior (if also being used for loading state), but could be less lines of code in the disabled memo at least haha

A couple follow up questions:

Are both isLoading and isFetching necessary? Haven't seen much use of isFetching and just curious the rationale
Do we actually want to use the loading/fetching state as part of the disabled logic? I would think we would use those for the loading state of the button and then disable only on the isSmartContract value being true basically. Doesn't really change behavior (if also being used for loading state), but could be less lines of code in the disabled memo at least haha

big 🧠 kev, this is a sign that I should stop working late in the night after our retro/meeting

isLoading is enough in that case because the only query key that could cause a refetch is the chainId, meaning that isLoading is enough and will be refired itself if the chainId change and hasn't been fetch in the past, I removed all those isFetching calls in 4dc06f1
This is true, I removed all those checks in isDisabled occurences in 54afc21
Also initially in 4dc06f1 I removed all the loading checks in useMemo where we verify that this is a smart contract or not because it's handled in the end button every time

Thanks for the super valuable review @kaladinlight , can I ask you to do a deep test again? I performed the same tests than submitted in the initial review and everything looks good but as we changed pieces of code at every place I don't feel so confident now!


ZSY: Only issue interrupt to M processes; not mupip or anything else.

Issuing an interrupt to mupip can apparently break replication.

Fixed in e187d72360f3df5e6a271c7df1c4b28513803d53.


Replace Resume Section in the Navbar with Blog

It should basically open hashnode.com in a new tab.

Hey @smaranjitghose can I work on this issue?


truncate a number to the decimal

There is already a "truncate number function", but I thought that it'd be fun to make using bitwise operators.

I don't see the content of snippet file. Maybe you forget to include it?

Fixed. Thanks!

Thank you, @onelifemedia :+1:
The snippet is interesting, and it's now available here https://1loc.dev/#truncate-a-number-at-decimal


Should we create collection if it does not exist?

const collection = state[entityTypeName];
// TODO: consider creating a collection if none exists.
//       Worried now that later implementation would depend upon
//       missing collection metadata.
if (!collection) {
throw new Error(No cached collection named "${entityTypeName}"));
}

Done. The library creates a collection on the fly when you start to access it.


openapi - add components

🔗 Linked issue
Fixes https://github.com/nitrojs/nitro/issues/2920

❓ Type of change

[ ] 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
Add components support for OpenAPI module.
Usage:
defineRouteMeta({
  openAPI: {
    responses: {
      200: { description: 'OK ', content: { 'application/json': { schema: { $ref: '#/components/schemas/User' } } } },
    },
    components: {
      User: {
        type: 'object',
        properties: {
          id: { type: 'integer' },
          name: { type: 'string' },
        },
      }
    },
  },
});

Result:

📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

@pi0 what do you think about it?

Quickly looking, seems lovely1

Can we merge this? 😄

@pi0 Can you merge this PR please? 😄

Dear @OskarLebuda it still needs proper testing before merge (or further change requests). reading this might be good.

Great! Didn't know about that! I'll check that and get back to you soon! Thanks!


Add Sokoban May update

#139

Merged, thanks for the PR!

Thanks for merging and for all the hard work coordinating @ozkriff!


streamDecrypt not working for custom disk using "S3" driver

Using the code doesn't download the file.
       return
            response()->streamDownload(function () use ($decFilename) {
                FileVault::disk('s3')->streamDecrypt($decFilename);
            }, Str::replaceLast('.enc', '', basename($decFilename)));

I keep getting the error ** Failed to open stream: No such file or directory** meanwhile the upload to bucket works and the file is actually there in the bucket. Using Local bucket, it works fine but doesn't work with the s3 driver.

Update on this @soarecostin
I noticed it was because I am using a custom disk configuration. e.g
'test-disk' => [
            'driver' => 's3',
            'key' => env('AWS_ACCESS_KEY_ID'),
            'secret' => env('AWS_SECRET_ACCESS_KEY'),
            'region' => env('AWS_DEFAULT_REGION'),
            'bucket' => env('AWS_BUCKET'),
            'url' => env('AWS_URL'),
            'endpoint' => env('AWS_ENDPOINT'),
        ],

The streamDecrypt doesn't work as it fails to check if the disk is actually using the s3 driver here
https://github.com/soarecostin/file-vault/blob/ee40ef4a3a7a23e64599a00f9ae5ff1c3b3597b5/src/FileVault.php#L175
here this->disk returns test-disk and thus fails with file not found.


Cannot run on macOS.

Missing systemctl, ip, and iw commands. In fact, I hope to directly accept Airdrop from any Apple device, which must be manually confirmed on macOS.

oh sorry but this is loooong forgotten script
i think owl, which it bases on, stopped working stable, and many ios updates came out in time...
good luck with that tho!


Update Colossal AI docs and integration

What does this PR do?
The colossal-ai repo is now public: https://github.com/Lightning-AI/lightning-colossalai and pending a pypi release.
The readme + documentation gets updated on both sides and getting cross-linked.
cc @borda @carmocca @akihironitta

pkg is up https://pypi.org/project/lightning-colossalai/


Read Parquet data as a  Stream?

I have very successfully created Parquet data and streamed it to an AWS S3 object with Carpet (performance turned out to be quite good) but now I would like to read an S3 Parquet object in the same way. I do not see a constructor for CarpetReader that accepts a stream - is this something you are considering to support? Not sure if this is even supported by the Apache Parquet libraries?!
Reading Parquet in streaming mode (row group by row group and iterate record by record within them) would be useful to consume larger datasets than what fits on local disk and also allow quicker reading if data does not need to be stored on disk first.
In my case I would have liked to read an huge S3 object in Parquet format as a stream, filter the received data (exclude some outdated records), add some new records in the right place and directly upload to a new version to S3 using a steam (already supported by Carpet).
This is of course a somewhat limited use-case as one cant sort the whole dataset (as I am not holding it in memory or even on disk) only merge in new records into the existing sorting order but in some cases it is all that is needed.

Hi @javafanboy
No, you can not read a Parquet file in streaming. To support writing in streaming, Parquet persist all metainformation generated writing the information at the end of the file. Then, to start reading the file it needs to go to the end of the file and read the footer. With that information seeks around the file reading requested information.
In this article you can learn about its structure and explanation of the footer:
https://www.linkedin.com/pulse/all-you-need-know-parquet-file-structure-depth-rohan-karanjawala/
To implement a stream reader Parquet ask you to extend the class SeekableInputStream that has a seek method.
With a streaming strategy you can not implement features like schema projection or predicate pushdown.

Thanks for the quick reply I had forgotten that Parquet uses a footer and
not a header for the metadata :-)
On Fri, Sep 20, 2024, 09:24 Jeronimo López @.***> wrote:

Hi @javafanboy https://github.com/javafanboy
No, you can not read a Parquet file in streaming. To support writing in
streaming, Parquet persist all metainformation generated writing the
information at the end of the file. Then, to start reading the file it
needs to go to the end of the file and read the footer. With that
information seeks around the file reading requested information.
In this article you can learn about its structure and explanation of the
footer:
https://www.linkedin.com/pulse/all-you-need-know-parquet-file-structure-depth-rohan-karanjawala/
To implement a stream reader Parquet ask you to extend the class
SeekableInputStream
https://github.com/apache/parquet-java/blob/08a4e7e6279f8c3b8558bd294fee4489a96d0db1/parquet-common/src/main/java/org/apache/parquet/io/SeekableInputStream.java#L49
that has a seek method.
With a streaming strategy you can not implement features like schema
projection or predicate pushdown.
—
Reply to this email directly, view it on GitHub
https://github.com/jerolba/parquet-carpet/issues/46#issuecomment-2363010743,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADXQF3VX7BJDKUCMIMCGA3ZXPERVAVCNFSM6AAAAABORJTX2WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNRTGAYTANZUGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add missing PHPMailer namespaces

Without these sending emails from the app will not work and will throw missing class exceptions.

It's worth noting that this has possibly come from the the recent composer updates and there is likely to be more missing namespace declarations throughout the project.

That is a bit strange. I have just done a fresh installation from the master and emails are generated and sent without any exceptions.
Did you run composer update or composer install for the recent updates?

Hi @samapraku
I saw your reply come through via email but i don't see it on here. To answer your question the reason the installer is able to send emails out without any exceptions is because it doesnt use PHPMailer. it uses php's builtin mail functions as seen here:
private function _sendMail($ns)
    {
        $admin_name = $ns->get('admin_name');
        $admin_email = $ns->get('admin_email');
        $admin_pass = $ns->get('admin_pass');

        $content = "Hi $admin_name, " . PHP_EOL;
        $content .= "You have successfully setup BoxBilling at " . BB_URL . PHP_EOL;
        $content .= "Access client area at: " . BB_URL . PHP_EOL;
        $content .= "Access admin area at: " . BB_URL_ADMIN . " with login details:" . PHP_EOL;
        $content .= "Email: " . $admin_email . PHP_EOL;
        $content .= "Password: " . $admin_pass . PHP_EOL . PHP_EOL;

        $content .= "Read BoxBilling documentation to get started http://docs.boxbilling.com/" . PHP_EOL;
        $content .= "Thank You for using BoxBilling." . PHP_EOL;

        $subject = sprintf('BoxBilling is ready at "%s"', BB_URL);

        @mail($admin_email, $subject, $content);
    }

I have confirmed this.
It is caused by https://github.com/boxbilling/boxbilling/pull/603
It has been stated in the PHPMailer readme:
https://github.com/PHPMailer/PHPMailer

Hi @samapraku
I saw your reply come through via email but i don't see it on here. To answer your question the reason the installer is able to send emails out without any exceptions is because it doesnt use PHPMailer. it uses php's builtin mail functions as seen here:

I deleted my first comment because I realised that I did the test on a different installation.


OAuth

Recently ran into an issue, where my unity program isn't receiving a short code to be displayed and in turn cannot be used. I'm not sure of the cause, but can it please be fixed soon or some feed back be given so I know I'm not completely insane

Let us know if you are still having issues. There were issues with the service APIs yesterday.


Bookmark dosen't launch at all

Ive copied the Ingot code exactly, and when I go to click the bookmark nothing happens :/

Visit the website and drag the button into your bookmarks bar.  If that still doesn't work, then your admin blocked it or the device was updated to the latest version which blocks bookmarklets (like this one) from running if developer tools are disabled.


cjk characters cannot be displayed correctly

Sorry about that!  Can you paste the output of the locale command for me?

❯ bfs ./Desktop/bqb -name '*截图*'
./Desktop/bqb/$'\xE5\xB1\x8F\xE5\xB9\x95\xE6\x88\xAA\xE5\x9B\xBE 2021-12-25 103614.png'
./Desktop/bqb/$'\xE5\xB1\x8F\xE5\xB9\x95\xE6\x88\xAA\xE5\x9B\xBE 2022-02-10 205237.png'
./Desktop/bqb/$'\xE5\xB1\x8F\xE5\xB9\x95\xE6\x88\xAA\xE5\x9B\xBE 2022-04-01 033635.png'
./Desktop/bqb/$'\xE5\xB1\x8F\xE5\xB9\x95\xE6\x88\xAA\xE5\x9B\xBE 2022-10-14 081805.png'
./Desktop/bqb/$'\xE5\xB1\x8F\xE5\xB9\x95\xE6\x88\xAA\xE5\x9B\xBE 2022-10-22 033037.png'

Hmm okay I tried those filenames locally and they work for me, so this is probably a platform-specific bug.  Can you please tell me

What version of bfs you're using?
How you installed it?
What operating system (including version) you're using?

Thanks!

@tavianator
bfs version: 3.0.4
installed by: nix-env
os: Debian 12 (WSL2)

I think the issue is that Nix packages won't use system locale information by default.  https://nixos.wiki/wiki/Locales says to do
$ export LOCALE_ARCHIVE=/usr/lib/locale/locale-archive

which fixed it for me in a similar environment to yours (Nix on Debian 12 on Docker).
To use Nix's locale data rather than Debian's, this worked instead:
$ nix-env -iA nixpkgs.glibcLocales
$ export LOCALE_ARCHIVE=/nix/store/ghvznirxqkw0f2wnbmgfk7i70igz66b4-glibc-locales-2.38-27/lib/locale/locale-archive
$ bfs ~/foo
/home/user/foo
/home/user/foo/屏幕截图 2021-12-25 103614.png

Anyway, whether bfs should behave like this when locale data is missing is a good question.  The goal is to avoid printing control characters to the terminal that may do dangerous things.  Currently it checks isprint()/iswprint() to determine what's safely printable.

Anyway, whether bfs should behave like this when locale data is missing is a good question. The goal is to avoid printing control characters to the terminal that may do dangerous things. Currently it checks isprint()/iswprint() to determine what's safely printable.

I just checked and GNU find does pretty much the same thing (they use wcwidth(c) >= 0 which is close enough).  If you run GNU find without locale data, you'll get
$ find foo
foo
foo/???????????? 2021-12-25 103614.png

As of https://github.com/tavianator/bfs/commit/023482caa20c0d3b5ab1641f26d8384829b1e43f we'll print a warning if setting the locale fails, which should help.  I think that's about as much of a fix as possible.


limit output

Is there a way to limit the number of tokens in Bard's response? It's providing a lot of output, usually too much and unnecessary details.

This is the Google Bard response, not my bot's. There is really nothing we can do at Python level because it's not even API, the communication goes through the value of cookie.


upgrade Net Framework to 4.5 and improved folder dialog

replace System.Windows.Forms.FolderBrowserDialog to Ookii.Dialogs.WinForms.VistaFolderBrowserDialog for better user experience
Please fill out the following checklist:

[ ] Added tests for any bug fixes that changed existing code
[ ] Added tests for any new behavior
[x] All unit tests are passing (please make sure all tests are passing for your branch/PR at https://ci.appveyor.com/project/activescott/lessmsi/history )

If you need any help at all, feel free to submit the PR and @-mention activescott and I'll be happy to assist!

Thanks for the proposal @pedoc but I'm not interested in updating to 4.5 nor to take on another dependency.


[WIP] Introduce consensus code for Whisk (SSLE)

Ethresearch post: https://ethresear.ch/t/whisk-a-practical-shuffle-based-ssle-protocol-for-ethereum/11763
Opening this PR as a place for comments and reviews on Whisk (the SSLE protocol)
Please add the "DO NOT MERGE" label.

Heads up: currently revamping/polishing/simplifying the document :)

Closing this PR in favor of https://github.com/ethereum/consensus-specs/pull/3205 which is rebased to latest dev and is executable.

Loved the work!


Upgrade Instruction

Category

[X] Question
[ ] Bug
[ ] Enhancement

I need to upgrade from version 1.3 to the latest version to solve some bug issues.  Are there instructions to complete this?  Please let me know.  Thanks.

I am looking for upgrade instruction also.  I want to upgrade the existing starter kit to a new version.

Are you looking to just upgrade the web parts? You can download the solution and upload the .sppkg file into your environment's app catalog.

Thanks for the info.  I figured this out as being the solution.  It worked well.  Thanks again!
From: Beau Cameron<EMAIL_ADDRESS>Sent: Wednesday, July 24, 2019 9:49 AM
To: SharePoint/sp-starter-kit<EMAIL_ADDRESS>Cc: Beasley, Mark A<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-starter-kit] Upgrade Instruction (#295)
[External Email]
Are you looking to just upgrade the web parts? You can download the solution and upload the .sppkg file into your environment's app catalog.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub [github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_SharePoint_sp-2Dstarter-2Dkit_issues_295-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAMM25NO2VTHWGAEV3GSI7Z3QBBMWRA5CNFSM4HZN6E62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2WMSSA-23issuecomment-2D514640200&d=DwMCaQ&c=Scw5Q-w0YkzmgQckG2UMv_F15wUD7DoFbJjMRh6PGnA&r=r68bPu7xKLd9WCA3UeotLqo4gzKI4KfJkQ-Xd03Pll4&m=tVdasCEGXaVhMIeWdRjCDWy9A31U0UjEAve3oD243cE&s=JACClc2H0qBI7xExy5xsTtkoAN_-lZNiVXXdEaaA5w4&e=, or mute the thread [github.com]https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AMM25NJ6YQCRVIGQBLYOM2DQBBMWRANCNFSM4HZN6E6Q&d=DwMCaQ&c=Scw5Q-w0YkzmgQckG2UMv_F15wUD7DoFbJjMRh6PGnA&r=r68bPu7xKLd9WCA3UeotLqo4gzKI4KfJkQ-Xd03Pll4&m=tVdasCEGXaVhMIeWdRjCDWy9A31U0UjEAve3oD243cE&s=WGcIt5jDTVYjw0IeX-SF8k-0IcSXNVWurav0n9oZAUk&e=.

This e-mail may contain proprietary information of the sending organization. Any unauthorized or improper disclosure, copying, distribution, or use of the contents of this e-mail and attached document(s) is prohibited. The information contained in this e-mail and attached document(s) is intended only for the personal and private use of the recipient(s) named above. If you have received this communication in error, please notify the sender immediately by email and delete the original e-mail and attached document(s).

This e-mail may contain proprietary information of the sending organization. Any unauthorized or improper disclosure, copying, distribution, or use of the contents of this e-mail and attached document(s) is prohibited. The information contained in this e-mail and attached document(s) is intended only for the personal and private use of the recipient(s) named above. If you have received this communication in error, please notify the sender immediately by email and delete the original e-mail and attached document(s).

Are you looking to just upgrade the web parts? You can download the solution and upload the .sppkg file into your environment's app catalog.

I am looking to update changes to the starter kit.  I see that there are some changes to the footer code.  If I upload the solution .sppkg will it update any code changes?

Yes they will.

Closing - Answered and Confirmed by Author


Contributor spotlight rajiv singh

Create contributor spotlight story for Rajiv Singh

I think Rajiv's spotlight should be turned on by updating :page-featured: false to :page-featured: true, while Harsh's spotlight should be turned off.

I think Rajiv's spotlight should be turned on by updating :page-featured: false to :page-featured: true, while Harsh's spotlight should be turned off.

We should do that next week when we're ready to publish, right?

I think Rajiv's spotlight should be turned on by updating :page-featured: false to :page-featured: true, while Harsh's spotlight should be turned off.

We should do that next week when we're ready to publish, right?

No, we don't have to wait because the changes will not be shown until the PR is merged.

I think Rajiv's spotlight should be turned on by updating :page-featured: false to :page-featured: true, while Harsh's spotlight should be turned off.

I've changed Harsh's spotlight false

I think Rajiv's spotlight should be turned on by updating :page-featured: false to :page-featured: true, while Harsh's spotlight should be turned off.

I've changed Harsh's spotlight false

Hi @alyssat Could we do that in this PR instead of a new one #152?

@lemeurherve Please review again and approve of the changes made


5: Gadget: Thermometer Encoding

This is the first step in the BTHOWeN pipeline:

Basically, for each pixel, we have an intensity $i$ (8 bit) and (also for each pixel!) a list of increasing thresholds $(t_1, t_2, t_3)$. The output should be a list of booleans $(i \ge t_1, i \ge t_2, i \ge t_3)$.
One way to do that would be via a table lookup for the tuple $(i, t, b)$ where $b := i \ge t$. This would need a table of size $2^{16}$ though; maybe there's a better approach! I'm not sure how many distinct thresholds appear in practice; it could be way less than the $256$ possible bytes.
Lastly, we could also use the same thresholds for all pixels, which I think should be fine for MNIST! However, that would be a change to the BTHOWeN model.

I'm not sure how many distinct thresholds appear in practice; it could be way less than the $256$ possible bytes.

Unfortunately no, in the case of the MNIST small model, there are $179$ distinct values, so for large models, we can expect this to approach $256$.
What this means is that we'll need $2^{16}$ rows for this column, so probably we'll have to use k=17. That's 2 larger than what we currently need for the small MNIST model (k = 15, see #12).
I think we should still do it like this for now and potentially optimize this if we realize that $2^{16}$ rows are much more than what we otherwise need for the models that we care about. We'll might end up needing more rows anyway.

This would need a table of size $2^{16}$ though; maybe there's a better approach!

Yes, it could be done as follows:

intensity
threshold
diff
is_ge

$i$
$t$ (copy)
$i - t$
$i \ge t$

The following constraints are checked:

intensity is a byte (via table lookup)
diff = intensity - threshold (note that this overflows iff. $i < t$)
is_ge is a bit
is_ge * diff is a byte (via table lookup)


Data stored in timestamptz column not being correctly returned

Environment
Knex version: 0.14.6
PostgreSQL 9.6.2 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
Bug
I have a column named post_date in timestamptz type, example date: 2018-08-10 17:05:07+00
When I run
knex.raw('SET timezone="Australia/Brisbane"; select post_date from TABLE_NAME')
Result is 2018-08-10T17:05:00.000Z, which is wrong, no offset.
However, if I run
knex.raw('SET timezone="Australia/Brisbane"; select post_date::timestamp from TABLE_NAME')
Result is 2018-08-11T03:05:00.000Z. which is correct, it has 10 hours offset.
Why do we still need cast timestamp type to it when the column is already in timestamptz type? Is this the only way to get the correct date?

You cannot put multiple queries separated with semicolon in single raw call. You don't have to cast timestampz to timestamp...
Its easier if you handle your timestamps always in UTC and only cast them to certain timezone when you really need to do it (for example when showing in UI to the end user). You can do timezone conversions for example with luxon on JS side https://moment.github.io/luxon/
Anyways, the behavior you are experiencing is not bug in knex. If you need more help how to use  knex + timestamps + timezones you could try stackoverflow.

And if you like to setup your DB to always return timestamps in Australia/Brisbane timezone, you should use pool's afterCreate attribute to set timezone to where you want when new connection / session is created.


Use ~/.forest_config (or similar) to load network settings

Host, port, proxy, etc.

Host, port, proxy, etc.

Greens, beans, tomatoes, potatoes.


Update Okta Configuration Guide with HA methodology

During configuration of the Okta authentication provider in an HA Environment the Validation and Enablement step kept failing with a 502 Bad Gateway
After investigation it was discovered:
Okta won't be enabled on Rancher until it can be validated
This meant that as we were HA whenever we begun the validation request the returned validation saml token would be routed by the external LB to a different rancher server than the requester (causing the bad gateway)
Rancher could never complete the validation for at least one node and never became enabled on any of them as a result and would continuously fail
To resolve this we cordoned off two of the nodes in the GUI to force traffic to the requester and from there completed the validation, this then synced the Okta configuration to the two other nodes
We tested each node cordoned individually to ensure the Okta configuration had been synced and also when all three were uncordoned with no difficulties
This has not yet being validated with any other providers except Okta yet but may require it
However looking in the guide I can't see this described anywhere
Could we please update the docs to reflect this necessary step for HA Envs with Okta if possible?

Catherine to ask Sangeetha if Okta was validated with HA setup


🐛  Unable to Vote on Non-Info Governance Actions on Sanchonet

Area
Voting Pillar
Domain
dev-sanchogov.tools
Which wallet were you using?
Demos 1.8.2
Context
I am encountering an issue where, as a registered dRep, I am unable to vote on any governance actions other than Info actions on Sanchonet.
Steps to reproduce

Connect your registered dRep wallet.
Navigate to a governance action other than an Info action.
Observe the details page for the governance action.

Actual behavior
As a registered dRep, I am unable to vote on governance actions other than Info actions on Sanchonet.

Expected behavior
I should be able to vote on all types of governance actions, including treasury and other actions, on Sanchonet.
Allure Report

4G. Should display correct vote counts on governance details page for DRep
5A. Should show relevant details about governance action as DRep
5C. Should show required field in proposal voting on registered as DRep
5D_1. Should accept valid data in provide context
5D_2. Should reject invalid data in provide context
5E. Should re-vote with new data on a already voted governance action
5F. Should show notification of casted vote after vote
5I. Should view the vote details,when viewing governance action already voted by the DRep

@kneerose possibly #2008  was a duplicate?

@jdyczka  Yes, it is related to #2008. I can now see the vote option for registered dReps on Non-Info Governance Actions in full governance mode (protocol major version 10).
This issue can be closed. CC: @bosko-m

Closing as per the comment above.


Fix core-utilities typescript tests

zurg, callback-queue, auth, and fetcher tests could not be run with the command: yarn workspace @fern-typescript/{zurg|callback-queue|auth|fetcher} test. These changes (with yarn installs) allow the tests to successfully run. Fetcher is fixed here: https://github.com/fern-api/fern/pull/3977

Should fetcher be here too or is that in the other PR?

Yea I added the fetcher fixes to the other PR


GitOps with Helm of AKS on Azure Stack HCI

Scenario for GitOps configuration with Helm for AKS on Azure Stack HCI

Applied all changes

Minor lingo update
Remove helm operator version
Update 1 screenshot


how to use in objective c project?

really awesome project, but how to integrate with objective-c project?

Thanks @xjiaoyang. Are you using Cocoapods?

@gmertk  yes, i use cocoapods, and i installed the pod but i can not import BusyNavigationBar header file.
i even want translate this project to objective-c, but i dont yet have much time. please help me, thanks!


[gardening] Remove unused #define requireTrueAndSILOwnership

Remove unused #define requireTrueAndSILOwnership.
Last requireTrueAndSILOwnership(…) usage removed in commit 8d4aac47e8297cd7b2242eb58fca4d853deee3a7 by @gottesmm

@swift-ci please smoke test

@gottesmm Judging from git grep it appears that isSILOwnershipEnabled, EnableSILOwnership and enable-sil-ownership is unused. Is there a plan for those or is it dead code that I can remove? :-)

I wouldn't rip them out. I may need them in a bit and I don't want to replumb. Also I thought these were used at least in the parser... but maybe my memory is wrong.

@gottesmm As far as I can see there are no usages left, but I might be reading it wrong :-)  Anyways, I'll leave it in there since you have a plan for those :-)

@practicalswift I am preparing a proposal for the ownership verifier. I am going to be developing it in tree, so I need a way of disabling it ; ).

But you are correct, there aren't any uses in tree for now.


Refine Lab 7 & Lab 8

Currently, the lab 7 can not run separately
lab 7 4. Internal ACA
when create the service connections between the apps and MySQL database, there will be errors prompt:
"message": "Execution failed. Attempt to get outboundIps: Failed to get IPs of source resource to set firewall rules, /subscriptions/6c933f90-8115-4392-90f2-7077c9fa5dbd/resourceGroups/rg-sonwan-vnet/providers/Microsoft.App/containerapps/customers-service.. Resource has internal VNet Configuration in environment."
At this moment, the connection between container apps and MySQL DB use public IP, but container app do not have outbound ip list
Even in MySQL, we allow public IP address and allow <IP_ADDRESS> - <IP_ADDRESS>, this error persistent.
Lab 7 & Lab 8 are focus on security:
Lab 7: Protect endpoints using Web Application Firewall
Lab 8: Secure MySQL database and Key Vault using a Private Endpoint
For the above issues, we should use private endpoint together for "vnet internal" scenario.
Or we import private endpoint for database in a single lab:
For Lab 7: Secure MySQL database using private endpoint
-- build vnet internal container apps environment, and use private endpoint for database
For Lab 8: Protect endpoints using Web Application Firewall
-- in this lab we import kv for WAF and custom domain, and we use private endpoint for kv

for container apps in vnet, no outbound ip property in app, so there is no direct way to tell what is the outbound ip.
internally:
For legion apps, the outbound ip list is the list of legion, long list
For non-legion apps, the outbound ip list is the AKS outbound ip list
More ref:
https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access

For external components,

if the target component support private endpoint, we use private endpoint, like we planed with MySQL & KV
if the target component do not support private endpoint, we should add "NAT gateway", and configure the outbound IP in target. (TODO) https://learn.microsoft.com/en-us/azure/virtual-network/ip-services/default-outbound-access

Per discussed offline, this is more like to be a service connector command issue in ACA VNET environment, which needs to be fixed.
Let's not rush into heavy refactoring of Lab 7 and Lab 8, as this will require too much implementation effort in our team and the communication burden in external teams.

hide it


Active Learning task

Hello, I am interested in the active learning task in your paper.
Could you release the code related to active learning?
Thanks!
And My email is<EMAIL_ADDRESS>

I sent the code file to your email


IREE should only initialize LLVM targets that are enabled for LLVM

In LLVMAOTTarget.cpp, we have the following:
#define INIT_LLVM_TARGET(TargetName)        \
  LLVMInitialize##TargetName##Target();     \
  LLVMInitialize##TargetName##TargetMC();   \
  LLVMInitialize##TargetName##TargetInfo(); \
  LLVMInitialize##TargetName##AsmPrinter(); \
  LLVMInitialize##TargetName##AsmParser();
    INIT_LLVM_TARGET(X86)
    INIT_LLVM_TARGET(ARM)
    INIT_LLVM_TARGET(AArch64)
    return std::make_unique<LLVMAOTTargetBackend>(queryOptions());
  });

This breaks if the LLVM that is installed/depended on does not enable a target. It would be nice if either, we just initialized all of them or used the #include "llvm/Config/Targets.def" include API to only initialize the intersection of what we know about and the LLVM was compiled for.

+1 - being able to configure this locally too when compiling LLVM from source would be useful!

Definitely being able to just have #include "llvm/Config/Targets.def" is very nice. We can do this now at the cost of having LLVMAOT lib depends on all targets in https://github.com/google/iree/blob/main/build_tools/bazel/third_party_import/llvm-project/overlay/llvm/BUILD.bazel#L29. Ultimately we want this list to be configurable too when building third_party/llvm_project. The target dependency list for LLVMAOT can either be forward to or queried by running llvm-config.
Same for cmake.
cc: @GMNGeoffrey @marbre For build systems aspect of this.

#3736 is the best solution to this - not needing to have them linked into our binaries at all but rely on the user having a linker with them built in - even if that means they are just configuring and building lld themselves. For cases where we can't use LTO we can enable an optional list of backends to link that is unpopulated by default so if you are using a linker for your aarch64 target that doesn't support AOT you can just add aarch64 as a target and go.
Orthogonal but also relevant is #1823, which would at least reduce the build time and file size burden of the multiple backends and I'm sure there's a way to register whatever is built in to the LLVM dylib.

Did https://github.com/google/iree/pull/8423 fix this?

I think it did, closing this.


Update tslint to v2.0.1

Starting in v2 the formatters are no longer zero based.
I also had to update how the file name was supplied due to tslint crashing when a file is in a subdirectory. See https://github.com/palantir/tslint/issues/288 for more details on this.
I'll update this as needed based on the feedback in that issue.

Looks good, but I think we should wait for palantir/tslint#288 to be resolved, as the file.relative change might not be necessary.

Just updated to v2.1 and backed out the path.basename change. So far I'm not having any issues with the update.

:+1: Thanks!


add new browsers, devices and tests

Fixes #196.
Fixes #197.
Fixes #198.

Pull Request Test Coverage Report for Build 1598

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 1592:
0.0%

Covered Lines:
819

Relevant Lines:
819

💛  - Coveralls


fix(docs): Fixed Typos in README and docs/snippets/6_supported-models.snippet

Fixed MosaicML spelling

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


Configure NIX_SSL_CERT_FILE with WSL2 and ZSCALER or similar enterprise Proxy

I cannot reliably or declaratively configure NIXOS-WSL to detect and abide my Zscaler SSL cert file.  nix-channel --update and nixos-rebuild switch due not function due to ssl errors.

I cannot reliably or declaratively configure NIXOS-WSL to detect and abide my Zscaler SSL cert file.  nix-channel --update and nixos-rebuild switch due not function due to ssl errors.

Then you need to build a custom tarball with that certificate already included. See the readme on how to built that and the generel nixos options. For general support use the matrix channel or discussions

Forgive me for jumping in to a closed issue, but was considering opening a discussion thread and then realized this can be solved without rebuilding the tarball by following this: https://github.com/NixOS/nix/issues/8022#issuecomment-2036710205.
The difficulties of trusting a cert with certain nixos commands I believe is a nixos issue, not nixos-wsl one.


Read wavfiles of size > 4GB

Adds the ability to open a .wav file with the 'RF64' format for files with a file size > 4GB, I'm not sure how to write a unit test for this, since it'd require uploading a huge .wav file.

Would it be a lot of extra work to add the equivalent writer? If not, then a round-trip test could work.

Or, add a small wav file in the large-file format. Presumably, the
format can describe also small files.

I've added the corresponding writer, however I'm still not sure how to go about implementing the test, since the format only really makes sense for data > 4GB, so the writer should only use the format if the data is too large for RIFF.

the format only really makes sense for data > 4GB, so the writer should only use the format if the data is too large for RIFF.

Although this might be true in practice, can you opt in to using the RF64 format even for files < 4 GB (even if just for the purpose of testing round-trip IO)?

According to the official specs, the standard filesize-locations should be used if the file is smaller than 4GB: https://tech.ebu.ch/docs/tech/tech3306-2009.pdf
It‘d be possible to force the RF64 format with a smaller file but then a large part (writing/reading the new 64bit-size-fields) of the changes wouldn’t be tested.
Alternatively one could disregard the specs, and write the filesize into the 64Bit fields even if it’s < 4GB. Let me know which of these options is the best and I’ll try to implement it

According to the official specs, the standard filesize-locations should be used if the file is smaller than 4GB

This makes sense, and seems like reasonable behavior for SciPy to follow.

Alternatively one could disregard the specs, and write the filesize into the 64Bit fields even if it’s < 4GB.

This is what I propose to do for testing purposes only, yes. Especially if there is some way to do it that does not expose the option to the user (since it's non-standard). Maybe a private function that does the heavy lifting could be used for this purpose.

This would be a valuable addition!!

Alternatively one could disregard the specs, and write the filesize into the 64Bit fields even if it’s < 4GB.

This is what I propose to do for testing purposes only, yes. Especially if there is some way to do it that does not expose the option to the user (since it's non-standard). Maybe a private function that does the heavy lifting could be used for this purpose.

@TimFelixBeyer are you interested in returning to do this? Sounds like it's all that is needed to test this properly and get this in. Judging by the recent comment, there is still some demand for this feature.

Sure, I’m currently busy but can take another look in about 3 weeks if that’s ok.

@lucascolley I'd like some input regarding testing.
In addition to testing with small modified RF64 files, I have a working test on my local machine that just performs a round-trip write of a large (>4GB) array, but it obviously takes quite a while and requires a large amount of memory to complete.
However, I think a round-trip test would be valuable in principle.
Are there any guidelines regarding how long test cases are allowed to last?

We have a marker for extremely slow tests, which can be applied with pytest.mark.xslow, to avoid running on every CI job. How about you add the test with that marker, then we can see how long it takes?

Opened #20079 to avoid having to rebase etc. @lucascolley feel free to check out the new PR


fix(minimal-blog): remove falsy values from plugins list

Currently, build fails when using feed: false in gatsby-config.js because falsy values are not removed from the plugins list. This PR fix this.

Thanks! Forgot that there 😬

Successfully published:
 -<EMAIL_ADDRESS>


Fix Fog::Compute::Google::Servers#all paging

If there are more instances than will fit in a page a next_page_token is returned.  This has to be passed in to subsequent calls in order to retrieve the full list of servers.

I built https://github.com/ManageIQ/fog-google/pull/4 on top of this commit so I'll just close this one.


Add more exception annotation

Last PR on the "exception" track @olivervogel.
NB: @throws void is a tips to tell phpstan than even if the method is technically throwing exception, it does throws nothing in this case.

Thank you.

Thank you.

You're welcome ; does a new release would be possible ?

You're welcome ; does a new release would be possible ?

The project follows a monthly release cycle for minor releases. The next one will on March 16, 2024.


chore: release 2.0.3

:robot: I have created a release *beep* *boop*
2.0.3 (2019-06-26)
Bug Fixes

remove path params when provided via API level options (#147) (96d940a)
docs: link to reference docs section on googleapis.dev (#150) (3ac41da)

This PR was generated with Release Please.

Release is at https://github.com/googleapis/nodejs-googleapis-common/releases/tag/v2.0.3

The release build has started, the log can be viewed here. :sunflower:

:egg: You hatched a release! The release build finished successfully! :purple_heart:


added explicit version to pods

Added two explicit versions to Podfile
  pod 'SDWebImage', :git => "https://github.com/rs/SDWebImage.git", :tag => '3.8.1'
  pod 'SBJson', '~> 4.0.2'

Since Jasonette can not work with more updated versions
it's best to use explicit versions until the core change the function calls to these libs.

👍👍


[backport] Fix cpu codes of indexing in F.softmax_cross_entropy

Backport of #5238

[automatic post] Jenkins, test this please.

Jenkins CI test (for commit 3f894ea02a329f841616979e6ab298d8228efad2, target branch v4) succeeded!


What browsers to test?

Any thoughts about which browsers and their specific version we should run tests on?
We initially tried to run tests on 25 different browser versions, but reduced it to latest chrome and firefox because it took 15-25 minutes to run.
These were the 25 we had at the beginning:
browsers:
  - name: chrome
    version: latest
  - name: firefox
    version: latest
  - name: safari
    version: 6..latest
  - name: opera
    version: 11..latest
  - name: ie
    version: 8..latest
  - name: iphone
    version: 6.0..latest
  - name: android
    version: 4.0..latest

I felt the need to test with IE locally, so added IE into the mix aswell. Feel free to reopen this or open a new issue if someone thinks we should tests more browsers.


Add addMap() method

I'm working toward using the flumedb map as a Scuttlebot plugin, but it seems like the first step would be to accept a function as opts.map that gets passed to flume. Is this the best way to go about that change?
Backlink: https://github.com/flumedb/flumedb/pull/19.

I ran the bench marks, and didn't detect a difference. can you add documentation and then merge and publish?

Based on these benchmarks I think the performance is reasonable again. I've added some documentation, please let me know if you'd like any other changes made. Thanks!

great, it i'm not so picky about internal style things, unless there is a performance reason or something. (external apis are worth arguing about though!) merging!!!

I doubt this actually broke anything, but it's technically a breaking change so published as 13.0.0
also, update to<EMAIL_ADDRESS>so get addMap by @christianbundy (a key step towards private-groups, although his reason for it was to experiment with blobs-as-content)

merged into 18.5.0, and scuttlebot@13 !


Svg path not completey animated except its stroke only

I'm trying to animate complete svg as shown in my example but only its stroke part is animated.  I have added both actual and expected results in my codesandbox. How can we interpolate the remaining parts of it (filled one) like in this example of react-mvt-svg-lines
PS I have already interpolated strokeDashoffset atribute. What other attributes needs to be interpolated.
Here is my codesandbox:  https://codesandbox.io/s/9llxp0zx8o

This is just svg/dasharray knowledge, react-spring just animates props. I don't know svg good enough to tell you which props do what but if you find a resource that tells you how to operate dasharray correctly then you'll be able to animate it like that with react-spring.

PS. i found this example, someone else made it: https://codesandbox.io/embed/4zppn84yj4 no idea if it helps but it looks like what you want to me: https://codesandbox.io/embed/4zppn84yj4

Thanks @drcmda  for this example. What I've figured out. We need SVGs with stroke along single line path. Here is the issue with my SVG. It's not created as desired to be. Anyways thanks to you. I'll try to make right SVG and would love to make a PR in examples.md.

sure, looking for good examples ...


Fix v20160930 package name in validate.go

Hi @raveeram, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Rakesh Veeramacheneni). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

This fixes #165


Fix colorize stream target

Colorize's surround method uses STDOUT by default, if command's output is a different IO, then ANSI escape codes would still be printed to STDOUT and contents to @output.
Includes updated spec helper capture_lines wich calls uncolorize by default.
Updates Webmock to latest version c673f393 because specs would not run with old version.

Thanks! I'll give it a quick review and merge it ASAP

Good catch! While it didn't cause any real issue because only STDOUT is supported, the bug was there waiting for a -o / --output option to be implemented to show up, so thank you!

Your welcome. I was just browsing through some crystal code to get to know the language a bit better and happend to notice a possible error.
If crystal-lang/crystal#3925 gets merged, there might be some changes how colorize works. But there's a spec now ;)


enabler: propose observability toolset

We have decided on an audit module from db-ally. We need to address error handling issues, but the core interface should remain the same.


insmod unable to insert module

Thanks for taking the time to write and put up this driver. It's quite nifty!
I'm able to compile everything, but when I attempt to load the video driver I get the following error message:
$ sudo depmod
$ sudo insmod gvusb2-video.ko
insmod: ERROR: could not insert module gvusb2-video.ko: Invalid module format

dmesg gives me the following information:
$ sudo dmesg | tail
[ 2510.239706] usb 5-4: cannot get connectors status: req = 0x81, wValue = 0x700, wIndex = 0x302, type = 0
[ 2510.595923] rfkill: input handler disabled
[ 2515.388184] usb 5-4: 3:0: usb_set_interface failed (-113)
[ 2515.388897] rfkill: input handler enabled
[ 2516.225958] usb 5-4: cannot get connectors status: req = 0x81, wValue = 0xa00, wIndex = 0x302, type = 0
[ 2516.423460] usb 5-4: cannot get connectors status: req = 0x81, wValue = 0x700, wIndex = 0x302, type = 0
[ 2516.495861] rfkill: input handler disabled
[ 2522.082133] usb 5-4: 3:0: usb_set_interface failed (-113)
[ 2959.133482] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 000000005a938964, val ffffffffc0f62408
[ 3142.588739] module: x86/modules: Skipping invalid relocation target, existing value is nonzero for type 1, loc 000000005a938964, val ffffffffc0f62408

modinfo seems to indicate I'm running the same kernel that I've compiled for.
$ modinfo gvusb2-video
filename:       /lib/modules/5.11.0-7620-generic/kernel/drivers/gvusb2/gvusb2-video.ko
license:        Dual BSD/GPL
author:         Isaac Lozano<EMAIL_ADDRESS>description:    gvusb2 video driver
srcversion:     57B317953AA4641366C956D
alias:          usb:v04BBp0532d*dc*dsc*dp*ic*isc*ip*in*
depends:        videobuf2-v4l2,videodev,videobuf2-vmalloc,videobuf2-common
retpoline:      Y
name:           gvusb2_video
vermagic:       5.11.0-7620-generic SMP mod_unload modversions

$ uname -r
5.11.0-7620-generic

Perhaps I'm missing something important? Any places to start looking would be a big help.

Just following up, I ended up reinstalling my operating system (an upgrade to Pop!_OS 21.04 from an older version) and I was able to build and load the kernel module.
Part of me suspects it was compiling against the wrong version of the headers, but it's difficult to tell.


Fix py3 issue with exception handling

I think this fixed the issue noted in #172

Seems to be resolved, thanks!


getobjbound() returns info from tim.lst

Added a method to parse bound from tim.lst as documented in page 13-14 in http://www.minlp.com/downloads/docs/baron manual.pdf.
Saw a special case where tim.lst return lower bound (dual bound) as "-.100000000000E+52", which should be 0. But Julia will consider it as a "very negative" number when parsing.
===========================================================================
 Doing local search
 Preprocessing found feasible solution with value -.407176866688E-006
 Solving bounding LP
 Starting multi-start local search
 Done with local search
===========================================================================
  Iteration    Open nodes         Time (s)    Lower bound      Upper bound
===========================================================================
 User did not provide appropriate variable bounds.
 Some model expressions are unbounded.
 We may not be able to guarantee globality.
 Number of missing variable or expression bounds =     15
 Number of variable or expression bounds autoset =     15
===========================================================================
          1             1             2.00    -6.11308         -0.407177E-06
*       494            88             2.86    -0.421280E-01    -0.333700E-04
       1320             0             3.91    -0.343700E-04    -0.333700E-04

 Cleaning up

                         *** Normal completion ***

 Wall clock time:                     4.00
 Total CPU time used:                 3.91

 Total no. of BaR iterations:    1320
 Best solution found at node:     494
 Max. no. of nodes in memory:     109

 All done
===========================================================================
tl = SubString{String}["problem", "5", "7", "167", "29", "-.100000000000E+52", "-.333700197003E-04", "1", "4", "2", "1320", "494", "109", "3.9", "4"]

So you're saying that BARON is incorrectly returning a very large negative number instead of zero? Is there a ticket open or a note in their documentation to this effect?


Support for Windows ARM64

What feature would you like seen in Chunker?
I tried to compile Chunker App to Windows 11 ARM64, but got this error:
\Users\MaxRM\Downloads\GitHub\Chunker>gradlew build

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\Users\MaxRM\Downloads\GitHub\Chunker\app\build.gradle.kts' line: 4

* What went wrong:
An exception occurred applying plugin request [id: 'com.github.node-gradle.node', version: '7.0.2']
> Failed to apply plugin 'com.github.node-gradle.node'.
   > A problem occurred starting process 'command 'uname''

* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
> Get more help at https://help.gradle.org.

BUILD FAILED in 2s

This seems related to the node plugin we use for gradle which I believe they're aware of and a fix is in the pipeline - https://github.com/node-gradle/gradle-node-plugin/issues/315
To work around this you could need to build the cli folder, then install/use your own node/npm to build the app folder

This should be fixed in the latest version 1.1.3 if you wanted to try rebuilding, let us know if it's not :)

Это должно быть исправлено в последней версии 1.1.3. Если вы хотите попробовать пересобрать, дайте нам знать, если это не так :)

Ok I will try again.

This should be fixed in the latest version 1.1.3 if you wanted to try rebuilding, let us know if it's not :)

Hi. Now I got this error:
Chunker.txt

This should be fixed in the latest version 1.1.3 if you wanted to try rebuilding, let us know if it's not :)

Hi. Now I got this error:
Chunker.txt

Have you tried clearing the directory the log specifies C:\\Users\\MaxRM\\Downloads\\GitHub\\Chunker\\app\\node_modules?

This should be fixed in the latest version 1.1.3 if you wanted to try rebuilding, let us know if it's not :)

Hi. Now I got this error:
Chunker.txt

Have you tried clearing the directory the log specifies C:\\Users\\MaxRM\\Downloads\\GitHub\\Chunker\\app\\node_modules?

Not yet

Have you tried clearing the directory the log specifies

Chunker000.txt
Now this error

That error seems to indicate that it ran out of memory while building

No. I have 7 GB of free space. Should be enought

ran out of memory

Or you meant RAM, not ROM?

That error seems to indicate that it ran out of memory while building, you can try building without tests -x test

Problem was in fact that after previous attemps JAVA still was in process list and take about 2 GB of RAM. After close those process I got new error:
Chunker001.txt

@FormallyMyles

That error seems to indicate that it ran out of memory while building, you can try building without tests -x test

Problem was in fact that after previous attemps JAVA still was in process list and take about 2 GB of RAM. After close those process I got new error:
Chunker001.txt

I would guess this might still be related to you running out of memory (RAM) since the daemon shouldn't just die, I did a quick test and this works for me on a ARM machine using 8GB of RAM.
You may want to disable tests e.g. gradlew build -x test as they do consume quite a bit of memory / time.

That error seems to indicate that it ran out of memory while building, you can try building without tests -x test

Problem was in fact that after previous attemps JAVA still was in process list and take about 2 GB of RAM. After close those process I got new error:
Chunker001.txt

I would guess this might still be related to you running out of memory (RAM) since the daemon shouldn't just die, I did a quick test and this works for me on a ARM machine using 8GB of RAM.
You may want to disable tests e.g. gradlew build -x test as they do consume quite a bit of memory / time.

This time I watched in the task manager and there was no RAM overflow. The maximum was 80%. but I'll try again with the 'gradle build -x test`

That error seems to indicate that it ran out of memory while building, you can try building without tests -x test

Problem was in fact that after previous attemps JAVA still was in process list and take about 2 GB of RAM. After close those process I got new error:
Chunker001.txt

I would guess this might still be related to you running out of memory (RAM) since the daemon shouldn't just die, I did a quick test and this works for me on a ARM machine using 8GB of RAM.
You may want to disable tests e.g. gradlew build -x test as they do consume quite a bit of memory / time.

Still not enought memory but this time It took longer.
Chunker002.txt
But I have another idea.
Can you just send here your build?

I did a quick test and this works for me

Can you send your compiled build here?
I just want to run it on my device.

I did a quick test and this works for me

Can you send your compiled build here? I just want to run it on my device.

I sent you an email with a copy of it as i'm unable to upload it here, I did briefly test it and it seemed to work but obviously windows and arm64 is still a relatively new thing in the development world so your mileage might vary.

Ok. Btw Windows ARM32 will never get support?

I did a quick test and this works for me

Can you send your compiled build here? I just want to run it on my device.

I sent you an email with a copy of it as i'm unable to upload it here, I did briefly test it and it seemed to work but obviously windows and arm64 is still a relatively new thing in the development world so your mileage might vary.

Ok. Btw Windows ARM32 will never get support?

We'll definitely have automatic builds when GitHub supports ARM64 for linux / windows, unsure on 32 though

We'll definitely have automatic builds when GitHub supports ARM64 for linux / windows, unsure on 32 though

Ok

I did a quick test and this works for me

Can you send your compiled build here? I just want to run it on my device.

I sent you an email with a copy of it as i'm unable to upload it here, I did briefly test it and it seemed to work but obviously windows and arm64 is still a relatively new thing in the development world so your mileage might vary.

Ok. Btw Windows ARM32 will never get support?

We'll definitely have automatic builds when GitHub supports ARM64 for linux / windows, unsure on 32 though

I will ask my friend to try compile it

I did a quick test and this works for me

Can you send your compiled build here? I just want to run it on my device.

I sent you an email with a copy of it as i'm unable to upload it here, I did briefly test it and it seemed to work but obviously windows and arm64 is still a relatively new thing in the development world so your mileage might vary.

Ok. Btw Windows ARM32 will never get support?

We'll definitely have automatic builds when GitHub supports ARM64 for linux / windows, unsure on 32 though

It works

I would guess this might still be related to you running out of memory (RAM) since the daemon shouldn't just die, I did a quick test and this works for me on a ARM machine using 8GB of RAM.
I think I understand why we have same space of RAM, but it failed on my side.
I have disabled "SWAP FILE" because of lack of ROM.

I will enable it again and try to compile again.

unsure on 32 though

What about make something like custom auto script to compile it?
Because I think GitHub will never support ARM32 platforms.

unsure on 32 though

What about make something like custom auto script to compile it? Because I think GitHub will never support ARM32 platforms.

One of those things that we don't have plans for official support unless there's great demand for it and considering ARM64 seems a lot more popular (at least from my perspective).

unsure on 32 though

What about make something like custom auto script to compile it? Because I think GitHub will never support ARM32 platforms.

One of those things that we don't have plans for official support unless there's great demand for it and considering ARM64 seems a lot more popular (at least from my perspective).

ок. Btw here is latest Chunker app 1.3.0 (exe was unpacked because it will work faster if unpack it)
https://www.mediafire.com/file/9foc6yln7qesg6c/Chunker-app-1.3.0-arm64.7z/file


Added Hungarian translation

Hi, Thanks for your work!
It seems your translation does not contain the last changes that occurred the past few days (such as the new --foreign flag in --help). You might want to update the .po file and add the missing translation. Refers to the HOWTO file for instruction (see "Update a translation").

Thanks for pointing that out! I've made the changes.

Merged both patches into one commit and pushed to master. Thanks a lot!


Deform handlers are not visible in Unity 2021.2.x with Gizmos enabled

Describe the bug
In Unity 2021.2.x deformer handlers not shown in Scene window when Gizmos enabled
To Reproduce

Just install the package in empty Unity 2021.2.x project and try deformer component
Turn On Gizmos in Scene window

Expected behavior
Handlers are shown
Screenshots

OS: MacOSx 11.6
Unity: 2021.2.2f1
Deform version: 1.2.1

Additional note
Same issue existed on LeanTouch asset. It was fixed by developer, and he said something was changed on Unity side in 2021.2.x

Hmm, it seems to be working for me on 2021.2.5. What's minor version are you on?

Hm, seems the changes/fixed something in next versions.
I am on Unity: 2021.2.2f1

Ok, great. Since it appears to be an issue with Unity that's fixed in a new minor release I'll mark this as resolved


Can Called Shot targets even if you don't have visuals on them

As reported in rogueticket-631, you can tab-cycle through called shot targets even with the restriction in place. Need to find the logic that controls called-shot targets and block it when the source has not visuals to target.

Possible fix in 1.0.0


add osgWidget::Viewer subclass to keep OSG from setting the CPU affinity

As discussed!

Thanks for your efforts! I am pulling that in and will make it configurable for users of the widget.