EE 10 changes for CDI

This is built on top of Brian's changes in https://github.com/wildfly/wildfly/pull/15252 as a PoC.
It adds some of missing CDI bits that are fairly easy to implement in WFP.
I created a PR out of it simply to get a CI run on all the tests and show the scope of needed changes. I was initially trying to do this locally but the runs take a considerable amount of time and CPU, so I decided to let it run here to be able to get back to it in an async manner :-)

Ok, there is about 250 tests that are broken by this change. I'll look into them in the coming days; most should be easily fixable by either adding a non-empty beans.xml or by annotating anything that's supposed to be a CDI bean.

The JDK 11 failure of org.jboss.as.test.integration.weld.deployment.BeanDiscoveryTest is related - I've changed that test to expect Weld 5 behavior in case of deployments with empty beans.xml.
We could @Ignore it with a comment for the time being, but I am pretty sure nobody will remember to flip that back on later.
Alternatively, I could switch it back to original behavior and exclude it from EE 9 but I am -1 for that as it will again show the same problem at a later stage.
Meanwhile, I am adding more TCK setup changes and getting green results locally. I'll push my changes shortly.

I've ignored the two test methods that are causing mayhem for JDK 11 testing.
I've also modified more MP TCK modules that spotted failures in and force-pushed it here. I was able to get a pass locally but I'll let the CI tell me what else I missed.

/retest

@bstansberry I think this PR should be ready for review. It is a lot of files, but the separate commits have individual changes which might be easier to review.
TL;DR is:

Switched default empty beans.xml behavior to annotated discovery mode
Introduced subsystem configuration allowing users to switch to previous behavior (mode all)
Fixed WFLY tests that were crashing because of this change

NOTE: I noticed a lot of exluded tests for EE 9 testing; these possibly still have this issue, but it should be trivial to fix once they are enabled again

Lots of MP TCKs were failing so I've altered several POMs to make use of the new Weld config and run in legacy mode which makes them pass

I am planning to look into those failures and contribute them upstream, but this temporary fix should do the trick for WFLY

There are 14 failing tests because of Hibernate and/or JSF impl using now removed CDI API methods; all of these tests are excluded in this PR and can be re-enabled once we get the dependencies updated

@manovotn I sent you https://github.com/manovotn/wildfly/pull/1 re the transformer stuff. Other than that everything here looks good, so if that change looks good to you, this should be good, except I'd like a WFLY-xxxxx mention in any commit messages and in the PR title. That could be WFLY-15687 or a separate one for this "initial" work. A separate issue will help us better track incremental progress.

@bstansberry I have created https://issues.redhat.com/browse/WFLY-16100 as a subtask of the original issue.
All commits in this PR are now attributed to either WFLY-16100 or WFLY-16056 (test fixes) and the title has been adapted as well.


Remove Bazel 0.4.4 from supported versions [phab:D1513]

Created by schroederc at 2017-04-12 16:16:28:
Bazel 0.4.4 now emits the following error during a build:
ERROR: tools/cpp/clang_configure.bzl:777:15: unexpected keyword 'environ' in call to repository_rule(implementation: function, *, attrs: dict or NoneType = None, local: bool = False)
ERROR: package contains errors: kythe/data
ERROR: error loading package '': Extension file 'tools/cpp/clang_configure.bzl' has errors

schroederc commented inline (context lost during migration) at 2017-04-12 16:18:26:
Also, the build error happens even before this check somehow... :-(

fromberger commented inline (context lost during migration) at 2017-04-12 16:33:43:
Ah, because the load statements are resolved during load, whereas I think this check doesn't happen till analysis. :(

fromberger accepted this revision at 2017-04-12 18:52:27

schroederc closed via commit 3336777c4b361fe7351257fae13150024326b1bd at 2017-04-12 18:53:39


[DEV] - Ensure we have adequate instance sizes in nebari

Summary
Right now, all the instance sizes are too small, they need adjusting based on:

Small/Large/High Mem/Cheap GPU etc
Is our default conda store pod size reasonable
Are our Dask workers configured correctly for our instance sizes
We may be able to use the ESIP deployment as an example.

Tasks to complete

[ ] Determine new sizes needed
[ ] Update the corresponding configuration/infra items
[ ] Ensure dask workers are configured accordingly
[ ] Increase conda store pod size

Related to

https://github.com/Quansight/qhub/issues/1111

Assign to Peyton

Closed by https://github.com/Quansight/qhub/pull/1338.


Running composer update not pulling in middleware changes

Hi. I've been trying to update this package as the middleware changes got merged a couple of days ago. For the life of me, it doesn't update even though composer seems happy each time I ran it. My composer.json looks like this:
"require": {
// other packages
"zizaco/entrust": "dev-laravel-5",
//  other packages
},
How do I update zizaco entrust to pull in the latest changes, please?

I did a full composer reset - backed up my vendor/ and composer.lock and ran composer install. That didn't help.
Then I changed the version to "dev-master" as the laravel-5 branch doesn't have the middleware changes. After another full reset, middleware got pulled but no tests/ folder. To make composer happy, I cloned the master branch somewhere and copied the tests folder across. After another composer update, everything seems to be happy.
I don't know if something's broken at my end but composer update should have pulled the entire package for me.

I am having the same exact issue!

 Give it a go please.

I know your solution work, but I will wait for the official fix. If it takes too long, I will fallback to laravel-5 and copy out the Middleware to my own since I need just the Role Middleware.

Yeah, that's an option I'm even considering now. Prior to this merge, I'd already applied the original patch with some modification as I didn't want to do abort(403) or something.
If in the next couple of days master or laravel-5 branch isn't fixed, I'll probably revert myself.

Caused me a bit of a headache - Could do a PR if it'd help?

Gimme a call when there is an update :)

:+1:
As per my comment on the commit above, this is because of https://github.com/Zizaco/entrust/pull/389 , which adds the test file to the composer autoloads (seems like a bad move to me...?), but the zip doesn't include the tests dir, so composer fails.
A temporary workaround is to force the source to be used instead of the zip:
rm -rf vendor/zizaco/entrust
composer install --prefer-source

Hopefully someone will revert the commit and fix this, as currently master is completely broken.

Interesting, I use "zizaco/entrust": "dev-master" in my project's composer.json and seems to work fine. Composer downloaded tests folder for me so it works on my machine.
Anyhow, I'm making a PR for this fix in a minute.

Meanwhile waiting for PR to be accepted. Here's a workaround by adding "repositories" and changing zizaco/entrust to use dev-middlewaretest-fix.
{
    ...
    "repositories": [
        {
            "url": "https://github.com/tuwannu/entrust.git",
            "type": "git"
        }
    ],
    "require": {
        ...
        "zizaco/entrust": "dev-middlewaretest-fix",
        ...
    },
    ...
}

This problem should already be resolved since #397.
Request closing this issue.


add #' @noRd to internal functions.

cfr recommendations

More useful will be `@keywords internal.
From : https://cran.r-project.org/web/packages/roxygen2/vignettes/rd.html

Keywords are not very useful, except for @keywords internal. Using the internal keyword removes the function from the documentation index and is useful for functions aimed primarily at other developers, not typically users of the package.`


Fix Twitter logo

Although I've seen people say it shouldn't need to be done, when I run into this I fix it with a width and height attribute on the <svg> or set the width/height in the stylesheet.  The ViewBox size alone doesn't do it.

So I'm in the latest version of Chrome (59) and Edge 41.16227
Everything appears to be appearing correctly for me on Mac and my Surface Book.

Looking fine now in all my machines :/


may you share code for your papers

it would be great to share a code for
Mining Mobile Internet Packets for Malware Detection
Multi-layer Anomaly Detection for Internet Traffic Based on Data Mining
thanks

It is not an autokeras related issue.

thanks for the answer, but how to write you by another way
what is your email?


chore: upgrade tibuild

Why:

https://github.com/PingCAP-QE/ee-apps/pull/89
https://github.com/PingCAP-QE/ee-apps/pull/84
https://github.com/PingCAP-QE/ee-apps/pull/82
https://github.com/PingCAP-QE/ee-apps/pull/81

/approve


bcrypt_sha256_file.ahk always outputs the same hash

Hello, as title says I've been using this ahk script for long time but now I noticed it always outputs the same hash for a file I'm using for testing purposes, this file has a size of 4,5mb (I think that might be the problem). I'm using w10 version.
This problem doesn't occur when using https://github.com/jNizM/HashCalc/blob/master/src/HashCalc.ahk

Tested with W7 version (using w10 computer) and it works as expected. There is a problem with w10 version.

nvm, it was a weird bug caused by resource hacker. It added duplicated resources and that made w10 hash function always return the same value. For some reason this didn't happen on w7 version.

Since BCryptHash performs a single hash computation, it will consume the full memory for string and file hashes. So if the file is 4 GB, the ram usage will be also 4 gb for the hash calculation. Its also slower than the other one and not compatible on windows 7.
Thats why I decided to remove the "win10" part.


fix STS token initializaiton in tableslurp

this should fix: https://github.com/JeremyGrosser/tablesnap/issues/55

Would you please cut this to a bugfix release on PyPI soon? Thanks in advance! :heart:


Upgrade to yq v4?

/kind bug
What steps did you take and what happened:
make test fails at yq with Error: 1:1: invalid input text "d".
What did you expect to happen:
I did see in the instructions that the recommended version to install is v3 for this specific reason, but it looks like the Apple Silicone compatible binaries arent built for yq v3. Is it time to think about moving to a newer version of yq?
Environment:

Kubernetes version: (use kubectl version): v1.25.0
OS (e.g. from /etc/os-release): macOS 12.5.1 (21G83) Darwin 21.6.0

@yuzisun Is it ok to do this now? Just want to know if there is anything else thats blocking this.

@yuzisun Is it ok to do this now? Just want to know if there is anything else thats blocking this.

@jagan120 nothing is blocking this, just need work to convert to use yq 4 as there are quite a few things changed.

I can give it a shot and see how it goes


Not able to check if a table exists

Just started using dexie.
How can you check if a table exists?
Tried (v3.2.0):
db.tables // Only returns used tables (with 1 or more rows)
db['table'] // Only returns 'true' when the table is used (with 1 or more rows)

Suggestion:
db.tables // Returns all existing tables (whit 0 or more rows!)
db['table'] // Returns 'true' when the table exists (with 0 or more rows!)

If you are looking for a way to open a database without declaring the schema using version().stores(), and instead inspect what tables there are on the database, have a look in these docs: https://dexie.org/docs/Dexie/Dexie.open()#sample and learn the difference between opening a declared database and open one in dynamic mode.
When you declare the database using version().stores(), the table-properties are there instantly before the call to db.open() completes. Table properties won't reveal any rows until you query them with for example db.myTable.toArray().
When you do not declare the database using version().stores(), you can never know anything about the database tables until you've opened it. To do that, call db.open() and await its Promise, Then you can inspect the schema that it found.

I am just trying dynamic mode, but I am a bit confused about what the idea behind this is.
const db = new Dexie('organizer').open()
What are the differences with 'normal mode'?
Tried:
db.tables // Returns undefined (with 3 'stores'  inside the 'organizer' database)
await db.tables // Returns undefined (with 3 'stores'  inside the 'organizer' database)
await db.friends.add({ name: "Josephine", age: 21 }); // Returns 'Cannot read properties of undefined (reading 'add')'
await db // Returns dexie but without the stores like in 'declaration' mode?

Just my notes after reading the docs:

I though I explained everything in the docs.
db.open() returns a Promise. Promises must be waited for.
Either using await:
try {
  const db = await new Dexie('organizer').open();
  console.log(db.tables);
} catch (error) {
  console.error(error);
}

...or using .then():
new Dexie('organizer').open().then(db => {
  console.log(db.tables);
}).catch(error => {
  console.error(error);
});

Thank you, I indeed was missing await when calling open. Unfortunately I am still not able to read/write in 'dynamic mode'
import Dexie from 'dexie'
// this.db = new Dexie('organizer')
// const db = await new Dexie('organizer').open()
export default {
  data() {
    return {
      db: undefined
    }
  },
  async mounted() {
    // this.db = new Dexie('organizer') // Normal mode
    this.db = await new Dexie('organizer').open() // Dynamic mode
  },

db.tables // Returns undefined (with 5 'stores'  inside the 'organizer' database)
await db.tables // Returns undefined (with 5 'stores'  inside the 'organizer' database)
await db.friends.add({ name: "Josephine", age: 21 }); // Returns 'Cannot read properties of undefined (reading 'add')'
await db // Returns dexie but without the stores like in 'declaration' mode?

In 'normal mode' I get:

I am getting the 'correct _StoreNames', but I still can't read/write like in the 'normal mode'.
In 'dynamic mode' I get:

Looks like the 'table objects' are only there in 'normal mode' after declaration. Is this expected?

db.tables // Returns undefined (with 5 'stores'  inside the 'organizer' database)

You are not describing where you get this db from. If it's tables property returns undefined, it's probably not a Dexie instance.
No generated props on db are only when opening non-dynamically: https://dexie.org/docs/Dexie/Dexie.[table]

Tried setting up a sandbox to show what I mean but I get unknown error
https://codesandbox.io/s/black-brook-fcdpw?file=/src/App.vue
Do you also have a working sandbox for vue? The one provided for vue doesn't seem to work
https://codesandbox.io/s/vue-dexie-livequery-87exj?file=/src/main.js

Need to close this for book keeping.
The example codesandbox for vue that we link to from the web page (and that you also link to here) is working in my various browsers (chrome, firefox, safari, different profiles etc).

Not sure what the problem was previously but the sandbox is now also working on my end.
I forked it and added 'dynamic mode'.

'Static mode' is working as expected with adding, clearing, deleting, etc.
But with 'dynamic mode' I get errors

Can you have a look? It's really driving me crazy why I don't understand 'dynamic mode' yet🤪
https://codesandbox.io/s/vue-dexie-dynamicmode-iek4o

In dynamic mode you store a promise in this.db, not a Dexie instance.

If you need more assistance, you are welcome to order private support

I am not sure if private support will help anymore. I will stick to 'static mode' and will write a script to automaticly declare the tables. I was hoping 'dynamic mode' could do this trick for me
Something like:

Thank you for your support and your great work on this cool library


edit-message event not emit if we clear all file

Describe the bug
edit-message event not emit if we clear all file
Steps to reproduce

Create message with one file
Click edit message
keep content and remove file
edit-message not being emit

Expected behavior
If we change file or remove file, i think it should emit event two
Device (please complete the following information)

OS: Ubuntu
Browser: Chrome
Package version: latest

Additional context
i think we need to check editedMessage's old file with files instead
https://github.com/antoine92190/vue-advanced-chat/blob/219fe6bf2c89a69c368d0825d11dc9bbc5aa688f/src/lib/Room/Room.vue#L816

Fixed in https://github.com/antoine92190/vue-advanced-chat/commit/4876b8a46630941d8c545c8da7064369a16892fe


Support for DID web

Overview
This PR adds support for resolution of DID who's method is web.
Description
Note that creation wasn't added, as there are questions around how it should work. The main one,

Given the SDK will not be able to modify the file in an external web domain, should the SDK facilitate creation and verification, similar to what https://github.com/TBD54566975/ssi-service/blob/main/doc/howto/didweb.md does?

But importantly, should we wait on #96 to be merged?
How Has This Been Tested?
Unit tests.

Also, should you update the DidResolvers.kt file in this pr too?


Feature request: get css pseudo :hover, :active :focus rules

Feature Description
Hi!
Provide a check and get changed css color or etc rules on element hover
Problem
I have css rules
before hover
.button[data-v-14f27f51] {
background-color: var(--14f27f51-backgroundColor);
padding: 10px 30px;
border: none;
color: var(--14f27f51-color);
cursor: pointer;
}
after hovering there are additional rules
.button[data-v-14f27f51]:hover {
filter: brightness(1.2);
}
Expected behaviour
after await wrapper.trigger("mouseover") or new await wrapper.trigger("hover")
Getting access to css rules on hover, focus or active
.button[data-v-14f27f51]:hover
Alternatives
What are the alternative solutions? Please describe what else you have considered?

Hi @FanilZarip
Can you provide us a small repro online using https://stackblitz.com/github/vuejs/create-vue-templates/tree/main/typescript-vitest?file=src%2Fcomponents%2F__tests__%2FHelloWorld.spec.ts to show us what you are trying to test and how it is failing?
It only takes a few minutes, and we'll be able to take a look

Hi @FanilZarip
Can you provide us a small repro online using https://stackblitz.com/github/vuejs/create-vue-templates/tree/main/typescript-vitest?file=src%2Fcomponents%2F__tests__%2FHelloWorld.spec.ts to show us what you are trying to test and how it is failing?
It only takes a few minutes, and we'll be able to take a look

Hi! I simplified HelloWorld and also added alias to vite config for v-bind css rules
I add hover to '.test' class. And expect that style color will be changed on hover.
style="--e17ea971-hoverColor: blue;" should be something like style="--e17ea971-hoverColor: darkgreen;"
Maybe it can be resolved with anoter way?
https://stackblitz.com/edit/github-cb45tg?file=src%2Fcomponents%2FHelloWorld.vue,src%2Fcomponents%2F__tests__%2FHelloWorld.spec.ts,vitest.config.ts,src%2FApp.vue,vite.config.ts

Hi @FanilZarip
Can you provide us a small repro online using https://stackblitz.com/github/vuejs/create-vue-templates/tree/main/typescript-vitest?file=src%2Fcomponents%2F__tests__%2FHelloWorld.spec.ts to show us what you are trying to test and how it is failing?
It only takes a few minutes, and we'll be able to take a look

Hi! I simplified HelloWorld and also added alias to vite config for v-bind css rules
I add hover to '.test' class. And expect that style color will be changed on hover. style="--e17ea971-hoverColor: blue;" should be something like style="--e17ea971-hoverColor: darkgreen;" Maybe it can be resolved with anoter way?
https://stackblitz.com/edit/github-cb45tg?file=src%2Fcomponents%2FHelloWorld.vue,src%2Fcomponents%2F__tests__%2FHelloWorld.spec.ts,vitest.config.ts,src%2FApp.vue,vite.config.ts

Hi!
I've added how can get hover styles at HelloWorld.vue file. But I don't know how to use it with vue-test-utils. Or maybe you can take screenshots of the components for visual comparison?
See the function showCssRules
https://stackblitz.com/edit/github-cb45tg?file=src%2Fcomponents%2FHelloWorld.vue,src%2Fcomponents%2F__tests__%2FHelloWorld.spec.ts,vitest.config.ts,src%2FApp.vue,src%2Fcomponents%2FTheWelcome.vue

There are several issues with jsdom and nwsapi around this: I'm not even sure this is possible at the moment.
I would strongly suggest not trying to test this in unit tests, and use end-to-end tests (with Cypress, Playwright, Nightwatch...). With these tools, you can do a visual comparison (I use Playwright in my projects and it is built-in https://playwright.dev/docs/test-snapshots).
Anyway I don't think Vue Test Utils can help in these scenarios, so I'll close.


[Update Snap] Dedaub

Checklist
All items in the list below needs to be satisfied.

[ ] Is the summary of the change documented in this ticket?
[ ] Has a MetaMask Snaps team member reviewed whether the changes need to be vetted?
[ ] If there are changes that need to be vetted, attach a description and the relevant fixes/remediations to this issue.
[ ] The corresponding pull request in this repo has been merged.

This update modifies the API endpoint and removes a gas calculation that is no longer needed: https://github.com/Dedaub/metamask-snap/commit/5b816c3ee58e02db70b5661c402528d40c6cbb2b
The new version is 1.0.3


feature(grid): add option for frame and icons for view-selectors

Describe Problem
Suggest Solution
Grid plugin could have an option for adding a frame with icons, title, and resize possibility.
"Selector" plugin could use the option for adding customized icons and labels to entries of each view.
The could simply be added to the "View" Blueprint for consumption of the plugin.
Additional Details

From the text description alone its difficult to understand what the final design should look like.
We need a design session and sketches  before we can start on this

duplicate


Dependabot wont recognise package with vulnerability from WhiteSource Vulnerability Database

I created this issue a while back but since the issue stills remain I would like to put some light on it.

Package manager/ecosystem
JavaScript
Manifest contents prior to update
yarn.lock
package.json
Description
One of hour packages, hellojs, is flagged with a vulnerability in WhiteSource Vulnerability Database all version below 1.18.6 is affected. However dependabot won't recognise this vulnerability. You could go to WhiteSource Vulnerability Database and search for CVE-2020-7741.
I have created a repo where I can reproduce the issue. I have added hellojs and jquery at a version that has a vulnerability. We can see that dependabot finds the jquery vulnerability and creates a PR but not for hellojs.
Is this a bug or have I missed something?

The WhiteSource db is not a source for Dependabot security updates, the advisory will have to be ingested in the GitHub Advisory DB. Our advisories team curates the data that is ingested in that DB, and they might be a little behind in this case.
I'll check with the team that curates these and will get back to you

The WhiteSource db is not a source for Dependabot security updates, the advisory will have to be ingested in the GitHub Advisory DB. Our advisories team curates the data that is ingested in that DB, and they might be a little behind in this case.
I'll check with the team that curates these and will get back to you

I see that this has been highlighted now here: https://github.com/advisories/GHSA-7jh9-6cpf-h4m7

I see that this has been highlighted now here: https://github.com/advisories/GHSA-7jh9-6cpf-h4m7

@christoferolaison thanks for the clean repository that reproduces this issue!
Since https://github.com/christoferolaison/depandabot-test/pull/2 is open, this was just lag curating this specific CVE. Thanks for flagging it.

@christoferolaison thanks for the clean repository that reproduces this issue!
Since https://github.com/christoferolaison/depandabot-test/pull/2 is open, this was just lag curating this specific CVE. Thanks for flagging it.


Why train the code so slow?

Thanks for your nice code.  I use  tensorflow-gpu==1.15.0 to train your code on single Titan Xp GPU, but the GPU is occupied on 0%  and the memory usage is only 158M?  In addition, on GTX 1070,  I also meet the same problem.  Can you explain why? Thanks.
I follow your README and run the following command (for single gpu, and I also  reduce the batch size and NUM_GPU):
CUDA_VISIBLE_DEVICES=7 python train.py configs/car_auto_T3_train_train_config configs/car_auto_T2_train_config

Could you check if the process is still running on the CPU side? In the current training code, the 1st epoch is slower as the dataloader loads the data the first time. It might take several minutes before the training on the GPU start.
Also, the training on train split takes around 9GB memory space, if the system runs out of memory, it might be swapping the memory to disk, which might slow down things a lot.

@WeijingShi

The time cost is too long. I use your default settings and train the model by  two GPUs with batch_size=4


Allow illegal decks to be published if marked as "Casual" legality

Currently, there seem to be some fairly strict rules which prevent decks from being published under certain circumstances (I'll trawl the code to figure out what they are soon), but people want to use sites like anrsealed.com to generate sealed or draft decks which may well not conform to these rules, but which they still want to publish so they can be shared with others.
Could we relax the logic which prevents decks being published so that a deck with a legality of "Casual" can always be published, regardless of it's contents?


bump autosklearn

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

requirements: run: pynisher <= 0.7 should not contain a space between relational operator and the version, i.e. pynisher <=0.7


Access is denied errors on IE11 latest

I'm running on windows 8.1 x64 and I noticed that I'm getting access denied errors. If it matters I'm running es5 and es6 shim on ie edge.
if (!objectGOPNAcceptsPrimitives) {
      var originalObjectGetOwnPropertyNames = Object.getOwnPropertyNames;
      defineProperty(Object, 'getOwnPropertyNames', function getOwnPropertyNames(value) {
        return originalObjectGetOwnPropertyNames(ES.ToObject(value));
      }, true);
      Value.preserveToString(Object.getOwnPropertyNames, originalObjectGetOwnPropertyNames);
    }

+1

Thanks for the report! I'll check on this asap. Is this the latest published version of es6-shim (which specifically?)?

I was seeing this in 0.27.x as well as 0.28.2

The code looks fine as well as the passed in objects, I'm not sure why ie is blowing up but it is.

Are you using any other libraries? react, core.js, things like that?

Angular: Here is the site I saw this error on: https://github.com/exceptionless/Exceptionless.ui

Interestingly.

Any ideas on the cause?

Object.getOwnPropertyNames is working just fine in my manual testing. Exceptionless is pretty big so I'm not sure how I'd figure out the problem, but since this has happened a couple times before, I suspect that something in Exceptionless is either a) modifying globals, or b) using host objects in unexpected ways.

I'm wrapping everything inside of a function and using strict mode. No where am I aware of adding a global / leaking/modifying anything.

I get it on any screen, any of the auth ones / status page are not loading up very much.

Okay! good news, I can reproduce it in a very simple sample:
<!DOCTYPE html>
<html>
    <head>
        <title>Exceptionless</title>
    </head>
    <body>
        <script type="text/javascript" src="https://js.stripe.com/v2/"></script>
        <script src="bower_components/es6-shim/es6-shim.js"></script>
    </body>
</html>

ooh, ok so it may be a conflict with Stripe's code. I'll look into that, thanks

I just sent them an email as well with a link to this issue.

Please let me know if there is anything I can do. I think this issue is causing other js errors (because this one is uncaught) on our site with ie11.

I work on Stripe.js and am trying to reproduce the problem. I'm not seeing the same thing on a Windows 8.1 VM with a slightly older version of IE. Does something like this repro the problem for you or do I need something standalone that doesn't frame the content?
https://jsfiddle.net/n09c2jww/1/

Thanks for looking into this. Yes, I can reproduce using that fiddle:

Simple reproducible case with this script, .call(Object, it) not works too:
<script>
var getOwnPropertyNames = Object.getOwnPropertyNames;
Object.getOwnPropertyNames = function(it){
  return getOwnPropertyNames(it);
}
</script>
<script src="https://js.stripe.com/v2/"></script>

F***** IE :)

@metcalf Thanks for responding so quickly!
I can not reproduce the error with https://jsfiddle.net/n09c2jww/1/ on IE 11 TP, fwiw.
@zloirock Are you saying that the .call(Object is what's breaking it?

@ljharb any wrapper breaking this code.

@metcalf Are you doing anything with Object.getOwnPropertyNames in stripe's code besides calling it directly?

If you guys can't reproduce I'll let you repo on my machine :). I've been able to reproduce on two machines.

Oddly enough I can't reproduce it on Windows 8.1 IE 11, but I can on Windows 7 IE 11 (on browserstack)

ah HA - it's because it's receiving a window object that the same origin policy doesn't allow it to access.
At the moment it's failing, value !== window and originalObjectGetOwnPropertyNames(window) works, but originalObjectGetOwnPropertyNames(value) gives an access denied error.
@metcalf This is almost certainly related to iframes, and attempting to enumerate the child iframe's global object from within the parent window - does that seem like it might be right?

I'm seeing this in our app and we have no iframes....

@niemyjski stripe uses one though, i believe

@ljharb ahh :) I haven't looked through their code.

OK, I upgraded IE inside my VM to the latest version and can now reproduce.
@ljharb we do create an iframe for some of the communications back to our API server. This seems to be a more general problem with scripts that work with iframes given that it affects Stripe Checkout as well:
https://jsfiddle.net/tm0bsbt1/
I'm trying to come up with a minimal repro and suspecting something to do with posting messages to the frame or doing some of the related feature detection.

This appears to reproduce simply by embedding a cross-domain iframe in the page somewhere:
https://jsfiddle.net/tm0bsbt1/9/
The issue goes away if you point the frame at "about:blank":
https://jsfiddle.net/tm0bsbt1/12/

@metcalf I can't reproduce it on https://jsfiddle.net/tm0bsbt1/9/ - but still can on https://jsfiddle.net/tm0bsbt1/ . Could you provide the lines of your stripe code that's calling Object.getOwnPropertyNames? https://checkout.stripe.com/checkout.js is minified.

I don't actually see anything from our code in the stack trace, nor do we call getOwnPropertyNames anywhere in checkout.js. I just double checked the repro on https://jsfiddle.net/tm0bsbt1/9/. Are you using Windows 8.1 with build 11.0.9600.0.17960?
My suspicion is that IE is calling getOwnPropertyNames internally somewhere in the layout engine. The native implementation has special, elevated permissions but overriding it means that the engine calls out to "user space" javascript and drops permissions. Just a guess but it seems consistent with the lack of stack trace, lack of call to getOwnPropertyNames and repro with a simple iframe.

I'm able to reproduce (ran windows updates yest) using that sample on

@metcalf I think you're correct.
I'm not sure sure what to do here:

It would be a change to make Object.getOwnPropertyNames not accept primitives in the shim everywhere just to accomodate this one specific IE 11 on specific Windows versions.
It wouldn't be acceptable imo to have it only not accept primitives on that one browser - since that'd just be pushing the exception to a later time.

Reproduces like described by @niemyjski, with a twitter widget iframe. It appears that somehow IE uses the patched Object inside the iframe and can no longer access the code which originated from a different domain (the parent frame).
@ljharb, given this limitation, it may not be possible to polyfill object static methods to accept primitives on IE. It would be safer to treat this as non-polyfillable and exclude it completely, adding a notice about this limitation on the readme, similar to WeakMap-s. I wonder why/if this happens for other polyfilled methods in a similar manner or it's just specific to Object or Object.getOwnPropertyNames. It could have bigger implications.
The second option that you suggested doesn't help at all, because it defeats the purpose of the polyfill, which is to provide the API on any non-ES6 compliant browsers. Writing a browser dependent polyfill makes no sense imho.

@use-strict In order to avoid polyfilling it on IE (and it seems specific to IE 11 only), I'd need a reliable way to detect it in JS - the iframe approach doesn't seem try/catchable, and using window.onerror is not something I'd feel comfortable doing.
I agree that the second option defeats the purpose of the polyfill.
Since this seems to only occur for getOwnPropertyNames, that's the only one I'm concerned with at the moment.

I've spoken to the IE team and this bug has been filed, so hopefully that will either/both shed some light on how to detect/avoid this problem, and fix it in future versions (hopefully in an IE 11 patch even).

I'm having this same issue too.  Works great in everything but ie11.

@ljharb did you ever hear back from the IE team?

I'm afraid nothing just yet. I'll ping again.

Any progress on this?

It's not looking like it'll be fixed in anything but the latest IE, if that.
I'm likely to remove this from the shim if I can't come up with a way to fix it.

+1 for fix or remove in short run

+1 for remove (or disable for IE11)

I definitely won't conditionally disable it for IE. I think I can probably fix it, but I'll need time to figure that out.

@ljharb fix is even better -- I was just in panic mode last night because I got a "sev 1" bug report due to updating ES6-shim from v0.20.4 to v0.31.2 in a QA environment without testing in IE (shame on me), which resulted in a large number of pages blowing up. I downgraded to v0.24.0 to resolve for now. It just seemed to me that it'd be better not to have a feature than to break things :)
BTW, thanks for your huge contributions to this project.

@ljharb Do you know when this fix will be released?

I should have it out today or tomorrow.

Released as v0.31.3

Thank you!
On 6/2/15, Jordan Harband<EMAIL_ADDRESS>wrote:

Released as
v0.31.3

Reply to this email directly or view it on GitHub:
https://github.com/paulmillr/es6-shim/issues/333#issuecomment-108107685

--
Thanks
-Blake Niemyjski


Cache a result of checking updates

When klio runs a command it checks for its updates in the background. Since this operation can slow down command execution, we should cache its result for some time (let's say 24 hours).

where the cache should be stored?

I was thinking about using ~/.klio/registries.json as default, and fallback to <project_dir>/.klio/registries.json if "global" directory is not writable. This file would contain data of all used registries + last update time for each of them.

I would add global option that switches off checking for update. I mean if you don't need it then just explicitly say it. Is there any reason why it may need to be implicit?


how to get Replication lag?

Hello,how to get the current length of replication lag???
rs.printSlaveReplicationInfo():
source: m1.example.net:27017
syncedTo: Thu Apr 10 2014 10:27:47 GMT-0400 (EDT)
0 secs (0 hrs) behind the primary
source: m2.example.net:27017
syncedTo: Thu Apr 10 2014 10:27:47 GMT-0400 (EDT)
0 secs (0 hrs) behind the primary
How do I get this zero second？？？thank you very much!

mongodb version: 4.0.10
python: 2.7
pymongo:3.8

The mongodb template I used is from this connection.：
https://github.com/denisgolius/zabbix-mongodb
This worked great for me. Unfortunately, replication lag between primary and secondary cannot be obtained


Use a HashSet for detecting orphan pages

This offers a big performance bump for large sites:
small-kb (100 pages)
before: 530ms
after: 500ms
medium-kb (1000 pages)
before: 2.9s
after: 1.5s
huge-kb (10,000 pages)
before: 150s
after:   9.1s


[admin] Improved custom admin site implementation #42

Simplifies the implementation of OPENWISP_ADMIN_SITE_CLASS
in order to avoid having to change all the openwisp modules.
Meaningless work saved.

CC: @okraits @oltarzewskik

Coverage increased (+3.2%) to 94.273% when pulling db0f502a23804a4d9f2424141e9bc7dc2836f1a0 on improved-admin-site-class into 342e0785e84b4673de30d08e367647a625ff7374 on master.


libmodsecurity: 3.0.4 -> 3.0.6

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libmodsecurity/versions.
meta.description for libmodsecurity is: "ModSecurity v3 library component.\n"
meta.homepage for libmodsecurity is: "https://modsecurity.org/"
meta.changelog for libmodsecurity is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
/nix/store/0fyvqr4a6dbxhcvdcph0qm6dva8sfnfg-libmodsecurity-3.0.6/bin/modsec-rules-check passed the binary check.
1 of 1 passed binary check by having a zero exit code.
1 of 1 passed binary check by having the new version present in output.
found 3.0.6 with grep in /nix/store/0fyvqr4a6dbxhcvdcph0qm6dva8sfnfg-libmodsecurity-3.0.6
found 3.0.6 in filename of file in /nix/store/0fyvqr4a6dbxhcvdcph0qm6dva8sfnfg-libmodsecurity-3.0.6

Rebuild report (if merged into master) (click to expand)

6 total rebuild path(s)

3 package rebuild(s)

3 x86_64-linux rebuild(s)
3 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
docbookrx
libmodsecurity
tengine

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/0fyvqr4a6dbxhcvdcph0qm6dva8sfnfg-libmodsecurity-3.0.6 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libmodsecurity https://github.com/r-ryantm/nixpkgs/archive/468575937ecf84b59a6730f18d1d2f5b75bc5c4a.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/0fyvqr4a6dbxhcvdcph0qm6dva8sfnfg-libmodsecurity-3.0.6
ls -la /nix/store/0fyvqr4a6dbxhcvdcph0qm6dva8sfnfg-libmodsecurity-3.0.6/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

libmodsecurity
tengine

Maintainer pings
cc @izorkin for testing.

Duplicate - https://github.com/NixOS/nixpkgs/pull/149591

PR #149821 merged.


[SPARK-18687][Pyspark][SQL]Backward compatibility - creating a Dataframe on a new SQLContext object fails with a Derby error

What changes were proposed in this pull request?
Change is for SQLContext to reuse the active SparkSession during construction if the sparkContext supplied is the same as the currently active SparkContext. Without this change, a new SparkSession is instantiated that results in a Derby error when attempting to create a dataframe using a new SQLContext object even though the SparkContext supplied to the new SQLContext is same as the currently active one. Refer https://issues.apache.org/jira/browse/SPARK-18687 for details on the error and a repro.
How was this patch tested?
Existing unit tests and a new unit test added to pyspark-sql:
/python/run-tests --python-executables=python --modules=pyspark-sql
Please review http://spark.apache.org/contributing.html before opening a pull request.

Test build #69562 has started for PR 16119 at commit d0585d8.

ping @holdenk @srowen

Test build #69562 has finished for PR 16119 at commit d0585d8.

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

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

Merged build finished. Test PASSed.

Since the current tests pass without this change I'd say that we should add a test for the behaviour we are planning to support that isn't currently supported (would also make the purpose of the change a bit clearer).

Test build #69801 has started for PR 16119 at commit dcd8063.

Test build #69801 has finished for PR 16119 at commit dcd8063.

This patch fails Python style tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

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

Test build #69802 has started for PR 16119 at commit 6641469.

Test build #69802 has finished for PR 16119 at commit 6641469.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #69818 has started for PR 16119 at commit 9a7f366.

Test build #69819 has started for PR 16119 at commit 5ec733d.

Test build #69818 has finished for PR 16119 at commit 9a7f366.

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

Merged build finished. Test PASSed.

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

Test build #69819 has finished for PR 16119 at commit 5ec733d.

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

Merged build finished. Test PASSed.

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

@holdenk test case added

@holdenk reminder
also pinging @davies

@vijoshi do you mind updating your PR according to the dicussion? i.e. simplify the fix and test

@cloud-fan sure, i'll push an update soon

Test build #70590 has started for PR 16119 at commit 750eb18.

Test build #70590 has finished for PR 16119 at commit 750eb18.

This patch fails Python style tests.
This patch does not merge cleanly.
This patch adds no public classes.

Build finished. Test FAILed.

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

Test build #70592 has started for PR 16119 at commit d1b6f26.

Test build #70592 has finished for PR 16119 at commit d1b6f26.

This patch fails Python style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

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

Test build #70593 has started for PR 16119 at commit b2c1355.

@cloud-fan @viirya - rebased and updated the code change per review comments.

Test build #70593 has finished for PR 16119 at commit b2c1355.

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

Merged build finished. Test FAILed.

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

retest this please

Test build #70605 has started for PR 16119 at commit b2c1355.

Test build #70605 has finished for PR 16119 at commit b2c1355.

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

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

Merged build finished. Test FAILed.

The test failure is caused by another issue. I've submitted another PR to fix it: #16454. Once that is fixed, this test can be passed.

thanks @viirya. will wait for your PR to go through.

https://github.com/apache/spark/pull/16454 has been merged

@vijoshi Can you solve the conflict?

Test build #71305 has started for PR 16119 at commit e5c822a.

Test build #71305 has finished for PR 16119 at commit e5c822a.

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

Merged build finished. Test PASSed.

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

thanks, merging to master/2.1/2.0!


Contacts returns Error: Invalid Date

Since I started using Ionic 1.3 (vs 1.0), the cordova-plugin-contacts module returns Invalid Date error on iOS 9. Still works on Android.
This has torpedoed my app so I am hoping someone can point me in the direction of how to troubleshoot it! Thanks.
The error

  var opts = { //search options
      // filter: '',                                 // 'Bob'
      //  multiple: true,                                      // Yes, return any contact that matches criteria
      fields: ['displayName', 'name'], // These are the fields to search for 'bob'.
      desiredFields: ['name', 'phoneNumbers'] //return fields.
  };
  $cordovaContacts.find(opts).then(function(allContacts) {}).catch(function(error) {
      //error is caught here;
  });

Cross-referenced http://stackoverflow.com/questions/36798316/ionic-cordova-contacts-plugin-returns-invalid-date

The issue is that in Ionic 1.3 the birthday field is returned as an invalid date (see screenshot below) and that all subsequent attempts to access the Contact's properties involve a serialization of the whole object that generates the error. My (hacky) solution was to copy the Contact properties except for birthday into a plain Javascript object and access it from there.

Why was this closed?    So now on IOS if I want to update an existing contact my only option is to clobber the birthday with a dummy Date().  There is no other way update an existing contact.    What's strange is when I use 'find()' to just get all the contacts and I look at the contact i'm going to update, it HAS a valid date.   but when i next use a filtered find to just get that one contact, the contact shows invalid date.    I don't get it..


Fluent layer for VMSS NIC list operations

Addresses https://github.com/Azure/azure-sdk-for-java/issues/1325

@martinsawicki thanks for the review comments, updated PR.


It looks like some examples are repeated

These lines, for example, are repeated twice per method:
"The following query shows including a single level of related entities.
context.Blogs.Include(blog => blog.Posts);"

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

ID: d5f7a5f6-21f4-f4bf-39fd-36af12aa1277
Version Independent ID: bd1c0b9f-39c8-61f9-d3aa-3420d5edb570
Content: EntityFrameworkQueryableExtensions.ThenInclude Method (Microsoft.EntityFrameworkCore)
Content Source: dotnet/xml/Microsoft.EntityFrameworkCore/EntityFrameworkQueryableExtensions.xml
Product: ef-core-api
GitHub Login: @dotnet-bot
Microsoft Alias: divega

Source code does not have duplication.
Bug in doc generation tool.

Got it.  Didn't realize docs were auto generated.  Thanks.

No longer being repeated in latest docs.


how get list messages from directmessage

how get list messages from directmessage ?

InstagramGetInboxRequest

how to use it correctly? I did it and he does not return anything
kotlin:
val instagram = Instagram4j.builder().username("login").password("password").build()
instagram.setup()
instagram.login()
val test =  instagram.sendRequest(InstagramGetInboxRequest());
object test empty

I watched the output of Instagram4j:this.sendRequest(new InstagramGetInboxRequest());
This returned the inbox of my user, so not sure about your set up sorry.

In my case, it returns an object
StatusResult(status=ok, message=null, spam=false, lock=false, feedback_title=null, feedback_message=null, error_type=null, checkpoint_url=null)

Where list?

@Pipka091 you're right!
InstagramGetInboxRequest simply returns StatusResult which is simply the generic status result type. You'll need to fork the project and change that to return a result type specific for the inbox request.

ok, thx

It only returns latest message of all conversations.
Is it possible to view each user's message thread-history?


[help] document the default mappings' meaning in slash.vim

Would be nice if the source contained short explanation of the mappings.
Eg what are gD & gd about?

it was to highlight definition. read :h gd and :h gD


Sandstorm by Darude

Song Name
Sandstorm
Artist Name
Darude
Source
Youtube
Youtube Link
y6120QOlsfU
Direct File Link
No response
Song ID
595342
Start Offset [ms]
0
Extra
Created from Auto Nong.
Created for level: 60776293

This is mainly for low death


Start showing the filesize

Shown in red when the file exceeds the maximum of 100k

I'm reluctant to pull in all this (buffer) just to find out the filesize. Here is a much shorter alternative: http://stackoverflow.com/a/23329386/3753599
The other question is do you really find yourself editing the bundled code?

I've already removed buffer. On the other hand, before having the functionality of wt update, I had to troubleshoot extensions using the editor.


Add mi_heap_stl_allocator

Rationale: heap-specific C++ allocator that can skip memory deallocation.
I use a shared_ptr to manage the lifetime of the heap, hence >= C++11. It's worth noting that the instance inside shared_ptr is allocated inside the same heap. Please tell me what you think.

@microsoft-github-policy-service agree [company="Athenian SAS"]

@microsoft-github-policy-service agree company="Athenian SAS"

Hi @vmarkovtsev -- thank for the extensive PR! Especially since I am not a C++ expert this is quite appreciated. I took your code and rewrote it a bit so I pushed it all as separate commit by me -- hope that is ok?
The enable_free, disable_free are a bit unsafe in general; instead I created to separate classes mi_heap_stl_allocator and mi_heap_destroy_stl_allocator where one deletes the heap, and the other destroys it making it fixed by construction. This also removes the boolean check on free.
Also, I added a constructor to allow creating it with a given heap (which is not destroyed or deleted).
Finally, I am not quite happy and maybe you (or some other C++ wizard) can help:

I needed to make the heap field public or I got errors for the generic copy constructor :-(
There is a lot of (complex) definitions shared between the three STL allocator instances -- is there a way to make this shorter??

Thanks again! Best, Daan

Thanks a lot @daanx! I will PR some refactorings addressing the issues you noted.
Indeed, we are not using the enable_free feature anywhere in our production but always do disable_free instead.

https://github.com/microsoft/mimalloc/pull/651

Am I missing something here? Why is the shared_ptr being used? It does absolutely nothing from what I can tell. The mi_heap_t type is nothing but an empty struct "handle" type; so deleting it like this makes no sense. The comment also says "will not delete nor destroy the passed in heap". Due to this on Visual Studio this also triggers the following (correct) warning:
warning C4150: deletion of pointer to incomplete type 'mi_heap_s'; no destructor called
Is this by design? I would love to know if i'm doing something wrong here.


Issues/224 completed timezone

@lemonboston please review.

I think I found a little inconsistency in how the timezone of the task gets set automatically:
Steps:
Create a task with quick add dialog, open its details and then edit.
The Time Zone field is preset to local time zone.
If I set any of the 3 dates manually there, the local time zone is kept.
But if all 3 are empty and I complete the task by either setting percent to 100% or status to done, then save, then the task's time zone will be UTC.
Otherwise, as much as I could check, it works correctly for me.

The problem is that a task has no time zone if no start or due date is specified. The COMPLETED field must not have any time zone, so a task that has only a completed date doesn't have any time zone at all. I'll check again if that's an issue, but I think it's not a blocker and we're going to release it anyway.

Ok, I see, and I suppose this is not part of this bug anyway.
Just one note: If I set the completed date-time with the COMPLETED field on edit screen of an otherwise empty task, the local time zone is kept. So it looks like it saves a time zone in this case even with no start or due date.
If completion is done with status or percent, then it will be UTC.

Ah, got it. That's because when you set a specific completed date, the time zone is always set as well now (that didn't happen prior to this patch). When you just complete a task (in the details view or from a notification), the completed date is set by the task provider, which doesn't set a time zone. I suppose we can also set a time zone in the task provider in that case (I just created dmfs/opentasks-provider#9). But even if we do that, this will only work on the device the task was completed on. If the task is synced to another device, the time zone will be lost (due to iCalendar restrictions).

So there is nothing else to do about this PR. I've merged it into staging.


add gpus

node1.json
node2.json
node3.json
node4.json
node5.json
node6.json
node7.json
node8.json

JSON file has been updated with models in this issue


Examples with wasm compilation target broken because of missing crate::async_io

Ran into this while trying to run examples:

cw
wgpu
spectrum
wasm

The error:
   Compiling futuresdr v0.0.18 (/home/jck/workspace/FutureSDR)
error[E0433]: failed to resolve: could not find `async_io` in the crate root
  --> src/runtime/mocker.rs:72:16
   |
72 |         crate::async_io::block_on(async move {
   |                ^^^^^^^^ could not find `async_io` in the crate root

error[E0425]: cannot find function `block_on` in this scope
   --> src/runtime/runtime.rs:119:9
    |
119 |         block_on(rx).expect("run_flowgraph did not signal startup completed");
    |         ^^^^^^^^ not found in this scope
    |
help: consider importing one of these items
    |
5   | use futures::executor::block_on;
    |
5   | use futures_lite::future::block_on;
    |
5   | use futures_lite::stream::block_on;
    |

Some errors have detailed explanations: E0425, E0433.
For more information about an error, try `rustc --explain E0425`.
error: could not compile `futuresdr` due to 2 previous errors
Error: Compiling your crate to WebAssembly failed
Caused by: failed to execute `cargo build`: exited with exit status: 101
  full command: "cargo" "build" "--lib" "--target" "wasm32-unknown-unknown" "--features=wgpu"
make: *** [Makefile:4: wasm] Error 1

I guess it's caused by conditional compilation of async_io re-export while code compiled to wasm still requires it (src/lib.rs):
// re-exports
#[cfg(not(target_arch = "wasm32"))]
pub extern crate async_io;

If you can think of easy enough fix I'd be glad to contribute.

Hi, thanks for bringing this up! I noticed it last week but forgot to push the changes to the upstream repo :-/ sorry. Can you try the current main branch and see if it works for you? I hope I find some time to add a WASM CI build soon.

Yes, it does work now, thanks :).


Razor Pages: pages files structure creates hard-coded namespace hierarchy

I have created sample ASP.NET Core Razor Pages app (VS 2017 15.4.0 Preview 1).
I have the following folders structure:

Strategy class (in OrdersContext.cs file)
Data
---OrdersContext.cs

Its code:
namespace FrezaWeb.Data
{
    public class Strategy { }
}

Edit page
Pages
---Dictionaries
------Strategy
---------Edit.cshtml
------------Edit.cshtml.cs
------------Edit_page

The code of EditModel:
using FrezaWeb.Data;

namespace FrezaWeb.Pages.Dictionaries // <- Note the absence of "Strategy" namespace
{
    public class EditModel
    {
        public Strategy Strategy { get; set; } // <== HERE'S THE PROBLEM
    }
}

I want to use Strategy class from FrezaWeb.Data namespace. I removed "Strategy" namespace from "FrezaWeb.Pages.Dictionaries.Strategy" - and this would solve the problem. However, Visual Studio STILL thinks there's a Strategy namespace! A picture is worth a thousand words:

@NTaylorMullen @rynowak any ideas on this?

Yes, this an issue with Razor tooling.
Right now when we open a document in the editor (edit.cshtml) it's opened in the project it lives in. This isn't how compilation actually works, it's just an artifact of VS. This is something we plan to change in the future, but right now it's pretty fundamental to our tooling experience.
The namespace of the generated C# code of edit.cshtml is in the FrezaWeb.Pages.Dictionaries.Strategy namespace, which is causing your problem.
If you want to have fine-grained control of the namespace of the generated code you can use @namespace in the razor file to configure it.

https://github.com/aspnet/Tooling/issues/883


Adding 2022 to supported windows version .

We migrated to Windows 2022 for our Image build server and started getting the unsupported windows version warning so added the 2022 versions.

Thank you for adding that


v1.14 stops me connecting to my Cosmos emulator locally

I get the error:
"Error Invalid API version. Ensure a valid x-ms-version header value is passed"
There is no update to the emulator.
Dropping to 1.13 stops the issue from happening.

This SDK version requires the latest version of Azure Cosmos DB Emulator available for download from https://aka.ms/cosmosdb-emulator. We will update the changelog to reflect the same, shortly

@srinathnarayanan thanks - that worked. Wish the Cosmos Emulator would auto-update, but that's another question for another day!


Failed to preview production build

Hi @sodatea,
I used this plugin in my project and it works on the dev server but failed on the preview build with the error process is not defined
When I used my custom configuration like the following, it works both on the dev server and the preview build
import path from 'path'
import WindiCSS from 'vite-plugin-windicss'
import nodeStdlibBrowser from 'node-stdlib-browser'
import inject from '@rollup/plugin-inject'

export default defineConfig({
  root: 'demo/',
  plugins: [
    vue(),
    WindiCSS(),
    // https://github.com/niksy/node-stdlib-browser#vite
    {
      ...inject({
        global: [
          require.resolve('node-stdlib-browser/helpers/esbuild/shim'),
          'global',
        ],
        process: [
          require.resolve('node-stdlib-browser/helpers/esbuild/shim'),
          'process',
        ],
        Buffer: [
          require.resolve('node-stdlib-browser/helpers/esbuild/shim'),
          'Buffer',
        ],
      }),
      enforce: 'post',
    },
  ],
  resolve: {
    // Enable polyfill node used in development to prevent from vite's browser compatibility warning
    alias: {
      'vue-dapp': path.resolve(__dirname, './src/index.ts'),
      ...nodeStdlibBrowser,
    },
  },
  optimizeDeps: {
    include: ['buffer', 'process'], // pre-bundle buffer and process
    // Enable polyfill node used in development, refer to https://github.com/sodatea/vite-plugin-node-stdlib-browser/blob/b17f417597c313ecd52c3e420ba8fc33bcbdae20/index.cjs#L17
    esbuildOptions: {
      target: 'esnext', // Enable Big integer literals
    },
  },
  build: {
    target: 'esnext', // Enable Big integer literals
    commonjsOptions: {
      transformMixedEsModules: true, // Enable @walletconnect/web3-provider which has some code in CommonJS
    },
  },
})

But in my case, the vite complains Sourcemap for "xxxx" points to missing source files as I noted here:

https://github.com/niksy/node-stdlib-browser/issues/25#issue-1502344412

Do you have any insight about how to adjust the configuration to let it work?

With the following configuration and Vite v3.2.4, it works without Sourcemap for "xxx" points to missing source files warning
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'
import path from 'path'
import WindiCSS from 'vite-plugin-windicss'
import nodeStdlibBrowser from 'node-stdlib-browser'
import inject from '@rollup/plugin-inject'

export default defineConfig({
  root: 'demo/',
  plugins: [vue(), WindiCSS()],
  resolve: {
    alias: {
      'vue-dapp': path.resolve(__dirname, './src/index.ts'),
      ...nodeStdlibBrowser, // Add browser polyfills of Node.js built-in libraries for Vite projects
    },
  },
  optimizeDeps: {
    esbuildOptions: {
      inject: [require.resolve('node-stdlib-browser/helpers/esbuild/shim')],
      target: 'esnext', // Enable Big integer literals
    },
  },
  build: {
    target: 'esnext', // Enable Big integer literals
    commonjsOptions: {
      transformMixedEsModules: true, // Enable @walletconnect/web3-provider which has some code in CommonJS
    },
    rollupOptions: {
      plugins: [
        // @ts-ignore
        inject({
          global: [
            require.resolve('node-stdlib-browser/helpers/esbuild/shim'),
            'global',
          ],
          process: [
            require.resolve('node-stdlib-browser/helpers/esbuild/shim'),
            'process',
          ],
          Buffer: [
            require.resolve('node-stdlib-browser/helpers/esbuild/shim'),
            'Buffer',
          ],
        }),
      ],
    },
  },
})

But in Vite v4, it complains an error when starting the dev server (but works well on the website
The error message is The injected path  /Users/xxx/xx/node-stdlib-browser/helpers/esbuild/shim.js cannot be marked as external


Fix TLS security configurations

Problem description
This PR https://github.com/pravega/pravega/pull/3693 has introduced changes to Pravega TLS security configurations which is used in connector system/integration tests. We need to fix the corresponding security configuration files used in connector according to the changes implemented in this PR https://github.com/pravega/pravega/pull/3693.
Problem location
Security related integration tests
Suggestions for an improvement

closed https://github.com/pravega/flink-connectors/pull/239


Add MIP-B13

Script output:
Script ran successfully.

== Logs ==
  deployerAddress:  0x9A187663E454e99CAFd40a2712606CC306e301b2

calldata for execution on temporal gov: abi.encode(temporalGovernor, targets, values, payloads)
  0x0000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e5000000000000000000000000edc817a28e8b93b03976fbd4a3ddbc9f7d176c22000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000627fe393bc6edda28e99ae648fd6ff362514304b0000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000cb1dacd30638ae38f2b94ea64f066045b7d45f440000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd000000000000000000000000e1dd796dbeb5a67ce37cbc52dcd164d0535c901e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000024bdacf6bbebaf567123da16cdb79a266597e92b00000000000000000000000000000000000000000000000000000000

  temporal governance calldata
  0xb19a437e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000005000000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e5000000000000000000000000edc817a28e8b93b03976fbd4a3ddbc9f7d176c22000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000627fe393bc6edda28e99ae648fd6ff362514304b0000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000cb1dacd30638ae38f2b94ea64f066045b7d45f440000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd000000000000000000000000e1dd796dbeb5a67ce37cbc52dcd164d0535c901e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000024bdacf6bbebaf567123da16cdb79a266597e92b00000000000000000000000000000000000000000000000000000000
  wormhole publish governance calldata
  0xb19a437e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c80000000000000000000000000000000000000000000000000000000000000584b19a437e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000005000000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e5000000000000000000000000edc817a28e8b93b03976fbd4a3ddbc9f7d176c22000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000627fe393bc6edda28e99ae648fd6ff362514304b0000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000cb1dacd30638ae38f2b94ea64f066045b7d45f440000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd000000000000000000000000e1dd796dbeb5a67ce37cbc52dcd164d0535c901e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000024bdacf6bbebaf567123da16cdb79a266597e92b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

calldata for execution on temporal gov: abi.encode(temporalGovernor, targets, values, payloads)
  0x0000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d510000000000000000000000000000000000000000000000000000000000000080000000000000000000000000000000000000000000000000000000000000014000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000005000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c000000000000000000000000fbb21d0380bee3312b33c4353c8936a0f13ef26c0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e5000000000000000000000000edc817a28e8b93b03976fbd4a3ddbc9f7d176c22000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000500000000000000000000000000000000000000000000000000000000000000a0000000000000000000000000000000000000000000000000000000000000012000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000000000022000000000000000000000000000000000000000000000000000000000000002800000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000627fe393bc6edda28e99ae648fd6ff362514304b0000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee000000000000000000000000cb1dacd30638ae38f2b94ea64f066045b7d45f440000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044e4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000ad31dde0cce0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd000000000000000000000000e1dd796dbeb5a67ce37cbc52dcd164d0535c901e000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd00000000000000000000000024bdacf6bbebaf567123da16cdb79a266597e92b00000000000000000000000000000000000000000000000000000000

  artemis governor queue governance calldata
  [encoded data, 7114 characters]

Proposal Description:

# MIP-B13: Gauntlet's Base Recommendations

# Simple Summary

### Risk Parameters

A proposal to adjust 5 risk parameters:

| Risk Parameter           | Current Value | Recommended Value |
| ------------------------ | ------------- | ----------------- |
| wstETH Collateral Factor | 77%           | 78%               |
| rETH Collateral Factor   | 77%           | 78%               |
| cbETH Collateral Factor  | 77%           | 78%               |
| wstETH Supply Cap        | 800           | 1000              |
| wstETH Borrow Cap        | 320           | 350               |

<sub> \*Cap Recommendations will be implemented via Guardian </sub>

### IR Parameters

A proposal to adjust cbETH's IR curve:

| cbETH IR Parameters | Current  | Recommended |
| ------------------- | -------- | ----------- |
| Base                | 0        | 0           |
| Kink                | 0.45     | 0.45        |
| Multiplier          | **0.06** | **0.05**    |
| Jump Multiplier     | **3.15** | **3.00**    |

A proposal to adjust USDC's IR curve:

| USDC IR Parameters | Current  | Recommended |
| ------------------ | -------- | ----------- |
| Base               | 0        | 0           |
| Kink               | 0.8      | 0.8         |
| Multiplier         | **0.05** | **0.065**   |
| Jump Multiplier    | 8.6      | 8.6         |

---

Our recommendation post is located in the forums with further analysis and supporting data.

By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos.

------------------ Proposal Actions ------------------
  1). Set collateral factor for Moonwell wstETH to updated collateral factor
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
value: 0
payload
  0xe4028eee000000000000000000000000627fe393bc6edda28e99ae648fd6ff362514304b0000000000000000000000000000000000000000000000000ad31dde0cce0000

  2). Set collateral factor for Moonwell rETH to updated collateral factor
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
value: 0
payload
  0xe4028eee000000000000000000000000cb1dacd30638ae38f2b94ea64f066045b7d45f440000000000000000000000000000000000000000000000000ad31dde0cce0000

  3). Set collateral factor for Moonwell cbETH to updated collateral factor
  target: 0xfBb21d0380beE3312B33c4353c8936a0F13EF26C
value: 0
payload
  0xe4028eee0000000000000000000000003bf93770f2d4a794c3d9ebefbaebae2a8f09a5e50000000000000000000000000000000000000000000000000ad31dde0cce0000

  4). Set interest rate model for Moonwell cbETH to updated rate model
  target: 0x3bf93770f2d4a794c3d9EBEfBAeBAE2a8f09A5E5
value: 0
payload
  0xf2b3abbd000000000000000000000000e1dd796dbeb5a67ce37cbc52dcd164d0535c901e

  5). Set interest rate model for Moonwell USDC to updated rate model
  target: 0xEdc817A28E8B93B03976FBd4a3dDBc9f7D176c22
value: 0
payload
  0xf2b3abbd00000000000000000000000024bdacf6bbebaf567123da16cdb79a266597e92b


Handle 1x1 textures in GLSL Image Nodes

The glsl shaders generated for image nodes all start with a check that the width is strickly greater than 1. So every texture that is 1xH will get the defaultval, instead of the texture color. Since it is a common pattern to use 1x1 textures, it would be prefable if the default value was not used for the 1x1 texture case.

I think the easiest way to fix this is to do like OSL, and pass over a flag to indicate if the texture is provided. Then there are no hardware limitation to testing for this condition, no additional dummy textures required, and default color changes are not resource binding Nora toploical change (I.e no new shadergen is required).The renderer will need to set this uniform. A suitable flag name will need to be injected as shader function arg, but this can be generated and published as a known notation.
Does this sound acceptable?

Thanks for posting this issue @klucknav, and now that our teams have returned from the SIGGRAPH conference, I'd like to make this a high priority to resolve in the next few weeks.
@kwokcb Although that's the simplest solution, the reason I'd recommend against it is the need for a second shader uniform for every image node in a MaterialX graph, in addition to the dynamic branch for each image node that currently exists.  My recommendation would be to go in the opposite direction, making the renderer responsible for replacing missing images with 1x1 textures, and removing the dynamic branch that currently exists in GLSL/MSL shader code.  This way, we could resolve the issue that @klucknav notes and improve real-time render performance at the same time.

Very good points on dynamic branching and the extra uniform.
To check, we can remove the  the "default color" argument from the shader so advantage of 1 less uniform. However, "default color"  is now up to the renderer now to create textures from a color.
BTW: The reasoning for the flag input (which in OSL is not an additional uniform since it's a struct) is to allow for not requiring any texture uniform to be emitted at all as no texture is required to be bound. Also to allow for "default color" to change dynamically without a texture (re)bind.

To "discover" what is the default, suggest to add a defaultinput attribute value on the output. This would reference to the default color input so that a renderer can discover what color to use. This would be for <image>, <tileimaged> and <triplanarmapping> nodes I think.

Here's an initial proposal to resolve this issue, and if this looks like a good step forward, perhaps we can include this in the upcoming 1.38.8 release:
https://github.com/AcademySoftwareFoundation/MaterialX/pull/1452

@klucknav The proposal in #1452 has been merged to main, and let us know how this works out in Hydra/Storm!


#1383 Added the mentioned algorithms under String Algorithms

📥 Pull Request
Description
Added the following algorithms under string algorithms:
1)Berry-Ravindran Algorithm
2)Not So Naive Algorithm
3)Optimal Mismatch Algorithm
Fixes #1383
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules

@ajay-dhangar Please review this ... Thanks :)

@ajay-dhangar Hi Ajay , Can you please review my PR.....Thanks :)


chore(deps): update renovate/renovate docker tag to v35.10.0

This PR contains the following updates:

Package
Update
Change

renovate/renovate
minor
35.6.0 -> 35.10.0

Release Notes

renovatebot/renovate
v35.10.0
Compare Source
Features

manager/bitbucket-pipelines: add support for docker-based pipes (#20938) (5d82120)

v35.9.1
Compare Source
Bug Fixes

Revert "fix: Add support for PAT in Bitbucket Server. Closes #14900" (#20979) (1a8088c)

Documentation

platform/bitbucket-server: add Data Center (#20980) (79cfad9)

v35.9.0
Compare Source
Features

manager/gradle: add support for plugins in inlined version catalogs (#20969) (85834b2)

Bug Fixes

Add support for PAT in Bitbucket Server. Closes #14900 (#20974) (d739141)
Prevent uninitialized cacheProxy from being accessed in cleanup (#20975) (15c7e8d)

Miscellaneous Chores

deps: update actions/checkout action to v3.4.0 (#20970) (a5c9f24)
deps: update dependency rimraf to v4.4.0 (#20973) (c31eb5f)

v35.8.3
Compare Source
Bug Fixes

config: migrate includeForks properly (#20965) (ccec42f)

v35.8.2
Compare Source
Bug Fixes

platform/bitbucket: use uuid instead of username for issues filter (#20960) (1789d34)

Build System

deps: update aws-sdk-js-v3 monorepo (#20956) (c2bf909)

Tests

Refactor tests for package cache decorator (#20958) (095c84e)

Documentation

update references to renovate/renovate to v35.7.0 (#20962) (b0753df)

v35.8.1
Compare Source
Bug Fixes

manager/npm: quote yarn args (#20955) (03d966c)

v35.8.0
Compare Source
Features

preset: add containerbase replacements (#20941) (62e91af)

Bug Fixes

cache: use cached git values for branch cache (#20837) (25ea3d1)
manager/gradle: drop stdout from gradlew :dependency command (#20820) (3e92cdd)

Documentation

config options: use admonition (#20948) (14f7815)
config options: use note admonition, fix styling (#20947) (e83ef5a)

Miscellaneous Chores

capitalize brandname in log message (#20950) (54cae9e)
deps: update github/codeql-action action to v2.2.7 (#20952) (f32a1e0)
replacements: improve descriptions (#20942) (d54e6aa)

v35.7.0
Compare Source
Features

datasource: support range constraints filtering (#20842) (2e25de1)
presets: include replacements:all in config:base (#20933) (ca03555)

Miscellaneous Chores

deps: update node.js to 5c0dbac (#20935) (e476727)
deps: update peter-evans/create-pull-request action to v4.2.4 (#20937) (3a32190)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 4.4.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Can't set cookie

When you go to the extension's settings to set the cookie, the setting just isn't there

What if you try searching for 'cookie'?

That also does not work


feat: update layout

Description
Fix up rviz layout.

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@mebasoglu That still needs a bit of work to be integrated without the need for manual setup from users, for now i'd still ask you to just do the setup of the dark mode manually until a later time where this will be automatically done by some script for every install


weggli: init at 0.2.4

Closes #207828
This PR has been around for around 8 months & I was unable to edit it.
/cc @arcz
Description of changes
Changelog: https://github.com/weggli-rs/weggli/releases/tag/v0.2.4
Signed-off-by: Muhammad Falak R Wani<EMAIL_ADDRESS>
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

I found that the Cargo.lock file seems not to be necessary and pushed a patch for that to this PR. Feel free to squash the patch into your commit and ping me for final review!
Either way: Thanks for your contribution! :+1:

I found that the Cargo.lock file seems not to be necessary and pushed a patch for that to this PR. Feel free to squash the patch into your commit and ping me for final review!
Either way: Thanks for your contribution! 👍

I saw a few files having Cargo.lock.
I am new, so was wondering, what is the rationale - when do we add them and when we rely on the hash ?

Result of nixpkgs-review pr 251611 run on x86_64-linux 1

1 package built:

weggli

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2610

Result of nixpkgs-review pr 251611 run on x86_64-linux 1

1 package built:

weggli


[WIP] tests: switch to using SysProcAttr for non-root

Evidently the LockOSThread approach is a disaster in go. However, the
os/exec.Command struct does expose some ability to control the execution
parameters via the SysProcAttr - and in particular the Credentials
struct which (in principle) allows us to safely set the uid/gid for the
execed rkt process.

Waiting #1571

I'm really missing why the permissions aren't getting propagated correctly.

I'm really missing why the permissions aren't getting propagated correctly.
Do you mean the db/sha512/ba/ now has 0777? I think we should pass PathPerm/FilePerm to the diskv.
Also let set the defaultFilePerm to 0660, and here

BTW, we should not let the such consts scattered everywhere.

Ready for review.

@jonboulle Thanks for the fix, LGTM.
btw can you uncomment these two lines to enable the test cases as the related prs should be merged now
https://github.com/coreos/rkt/pull/1569/files#diff-b8f7293584997a92e048ae9e5f8078a2L52
https://github.com/coreos/rkt/pull/1569/files#diff-b8f7293584997a92e048ae9e5f8078a2L68

@yifan-gu go to sleep :)

LGTM except the issue mentioned aboved. Will be fixed on a follow-up


⚠ Friends API Endpoint has degraded performance

In b9de07d, Friends API Endpoint (https://friends.roblox.com/v1/metadata) experienced degraded performance:

HTTP code: 200
Response time: 1542 ms

Resolved: Friends API Endpoint performance has improved in 441a1da.


When parsing big integrals, json_object_get_number() returns incorrect results.

Hi,
If I’m not missing other alternatives, the json_object_get_number() method is the only method for reading number values, but since the method returns a double, casting with big integral values is not guaranteed to work on all platforms.
For example, if a JSON document contains a "timestamp" property with an epoch value (i.e. time_t/int64_t/long long), the conversion returns an incorrect result, and casting won't work either:
{
"responseTimestamp":<PHONE_NUMBER>791,
"httpCode": 200,
"statusCode": 0
}

...
double dTimestamp = json_object_get_number(rootObject, "responseTimestamp"); // returns<PHONE_NUMBER>078 (incorrect)
time_t t = (time_t)json_object_get_number(rootObject, "responseTimestamp"); // returns 0x7fffffff (incorrect)
...

While reading the values of httpCode and statusCode return correct values, reading responseTimestamp, which was serialized from a time_t, doesn't.
Are there possible workarounds, besides implementing a method to specifically process big integrals (long long)?
Thanks!

Hi, this was already discussed in https://github.com/kgabis/parson/issues/134.

Hi, this was already discussed in https://github.com/kgabis/parson/issues/134.


Randomizer for spanish

Is there any way to make it work in a spanish rom?
It would be so useful

I'm not aware of a way myself, though I don't know much about Emerald. My patch is to the decompiled source, so someone wanting to do this would have to be able to compile the Spanish version of vanilla Emerald, and then apply my source patch on top of that.


GO:0075113    induction by symbiont of host transmembrane receptor-mediated signal transduction

GO:0052028    induction by symbiont of host signal transduction pathway
Any process in which an organism activates, maintains or increases the frequency, rate or extent of the host signal transduction pathways, the cascade of processes by which a signal interacts with a receptor.
1 annotation (I think this is also in another branch)
this descendant is  the same (definition is the same, and distinction not necessary)
GO:0075110    induction by symbiont of host receptor-mediated signal transduction
Any process in which the symbiont activates, maintains or increases the frequency, rate or extent of receptor-mediated signal transduction in the host organism.
and this
GO:0075113    induction by symbiont of host transmembrane receptor-mediated signal transduction

I always wonder if the 'inductions' are really physiological. The pathways induced that I can think of are defense pathways, so the fact that they are induced is not the real function of the symbiont/pathogen/virus protein.
@pmasson55 @SIBvirus What do you think about those terms ?

from the abstract, the single annotion looks OK
"Through activation of NF-kappaB, v-CARMEN may regulate the expression of the cellular and viral genes important for viral replication."
I just think only one term is required because they mean the same thing?

Well isn't the viral protein hijacking the host into producing factors the virus needs for replication ?
I think those would be better as MF (regulator of host enzyme activity) and part of 'viral replication' (I may be missing a step in between)
Pascale

@pmasson55 does this exist ?

Obsoleted in https://github.com/geneontology/go-ontology/issues/25395


Better class name detection

This PR improves the regexes used to detect CSS class names.
I looked through all plugins, so that should be all of the over-accepting regexes.

Thank you @ExE-Boss for bringing this issue to my attention.

It might be a good idea to add tests for this.

Tests would require a virtual DOM, which we don't have right now. So no tests for now.

You could probably use JSDOM  for that, but that’s probably for a separate PR.

#1646


[5.7][Runtime] Fix rare crash when fixing up dynamic subclasses.

Cherry-pick https://github.com/apple/swift/pull/60236 to release/5.7.
Swift vtables can contain NULL entries. This happens when the compiler is able to prove that a method is never called.
When ptrauth is enabled, those NULL entries are still signed. However, there's an inconsistency in the runtime. Most places where we copy a vtable with swift_ptrauth_copy_code_or_data, we accept an unsigned NULL value. But when fixing up a dynamic ObjC subclass with swift_objc_classCopyFixupHandler, we don't.
Since the compiler seems to always sign these NULL values, this still works, except in the case where a signed NULL value coincidentally has a ptrauth signature of all zeroes. When that happens, the code to accept an unsigned NULL value sees this NULL with an all-zero signature as an unsigned NULL, and copies it verbatim. Then we really do have an unsigned NULL in the destination.
If that class is then dynamically subclassed, we'll call swift_objc_classCopyFixupHandler which does not accept unsigned NULL values, and fail ptrauth.
Adjust swift_objc_classCopyFixupHandler to accept unsigned NULL like the rest. These entries should never be called, and any attempt to call them will crash regardless, so it makes little difference.
rdar://92800322

@swift-ci please test


Fix java version in CI

Sonar is complaining about java version:
The version of Java (11.0.21) you have used to run this analysis is deprecated and we will stop accepting it soon. Please update to at least Java 17.
Read more [here](https://docs.sonarsource.com/sonarcloud/appendices/scanner-environment/)

It could be fixed similar way to this https://github.com/exasol/project-keeper/blob/main/.github/workflows/ci-build.yml

Will be fixed with #57


[Bug]The video is not displayed in the Omni bar for a few of the widgets which is present in the official docs

Description
[What happened] The video is not displayed in the Omni bar for a few of the widgets which is present in the official docs but not in the Omni bar
Steps to reproduce the behaviour:
The widget list which doesn't display the video when the user searches for the widget in the Omni bar:
Select widget-> not able to search in Omni bar
Filepicker widget->no video
Image widget->no video
Input widget->no video
List widget->no video
Map widget->no video
Modal widget->no video
Radio widget->no video
Rich text editor->no video
Switch widget->no video
tab widget->no video
Video Widget->no video
To set appsmith on docker and Heroku When the user searched for it in Omni bar the video is not displayed in Omni bar but it is present in Docs
Important Details

Version: [Cloud ]
OS: [MacOSX]
Browser  chrome
Environment  release

There are two type of youtube we are using for embedding. Will add another regex to match the missed link format.


Fix typing issues

Hey! There is a naming clash between your Function and discopy.python.Function.
Maybe a better name could be CallableFromDict? The user won't see that name anyway.


Ionic 2 - ion-slides [options] are not considered

Hi,
I am using ionic 2 version - 2.2.1
In the view, I used ionic slides like, <ion-slides [options]="slideOptions" >
In the controller,
constructor(public params: NavParams) {
this.images = this.params.get('images');
this.index = this.params.get('index');
this.slideOptions = {
pager: false,
initialSlide: this.index,
loop: true,
zoom: true
};
}
None of the options are considered. Then I changed the view like, <ion-slides [initialSlide]="index" [pager]="false" [loop]="true" [effect]="coverflow">
except zoom and effect, other options are taken in effect.
Please let me know if I am missing anything or it is a defect.
Thanks,

Hello, thanks for using Ionic! You can read this part of the RC5 changelog to see why options is not supported anymore and to see the new way to handle them.


update documentation for ssh keys

Fixes #58
A little more info on ssh keys.

+1

May be adding a sentence to clarify how the ssh keys are usually obtained would help users. E.g. for the private keys: "extract them from the user X on machine Y".

Gave more clarity on private vs public. I don't want to get down in the weeds about how to create/obtain ssh keys.

I think a sentence about which ssh key is supposed to be used would help the users, e.g. the one asking the recent question on the mailing list. Currently at least to me it is unclear from which user on the repo machine the private key is required to be on the master.

@dirk-thomas How can I make this clearer? https://github.com/ros-infrastructure/buildfarm_deployment/pull/59/files#diff-04c6e90faac2675aa89e2176d2eec7d8R89

I missed that it is in the "On all three" section - I only looked at the "Repo" section. That is absolutely sufficient. Sorry for the noise.
+1


Add button to share all logs from the sample app

All the console logs from the sample app should be logged in a text file on the device
On clicking of the button - "Report Issue" a prompt should appear to share this file along with some message

Currently this functionality is commented in the build.

Not able to send logs from the "Send Logs" button on the app
Steps:
click settings button
click send logs cta
share on the desired app
"Cannot send. Try again" (File size: 0B txt)


Typo "Cognitive services"→"Cognitive Services"

https://docs.microsoft.com/en-us/gaming/playfab/features/multiplayer/networking/party-unreal-engine-oss-cognitive-services-interface
#PingMSFTDocs

@hyoshioka0128 Thank you for the edit.