Pasting doesn't work in the mediumjs textfields (e.g. create post)

same as #680?

Yep it is.

Medium.js seems to have a fix on it's master-branch. I've added that to our jspm dependencies instead of the npm-package (that's still at 1.0.1)

Trying to get that master-branch to initialize properly. Importing seems to be a bit tricky and I usually run into an error, that window.rangy isn't defined:

Error: (SystemJS) Cannot read property 'rangePrototype' of null
	TypeError: Cannot read property 'rangePrototype' of null
	    at eval (https://localhost:8443/owner/jspm_packages/github/jakiestfu/Medium.js@master/medium.js:2567:6)
	    at eval (https://localhost:8443/owner/jspm_packages/github/jakiestfu/Medium.js@master/medium.js:2576:4)
	    at eval (https://localhost:8443/owner/jspm_packages/github/jakiestfu/Medium.js@master/medium.js:2587:4)
	    at eval (https://localhost:8443/owner/jspm_packages/github/jakiestfu/Medium.js@master/medium.js:2589:3)
	    at eval (<anonymous>)
	Evaluating<EMAIL_ADDRESS>	Error loading<EMAIL_ADDRESS>as<EMAIL_ADDRESS>from<EMAIL_ADDRESS>	    at eval (https://localhost:8443/owner/jspm_packages/github/jakiestfu/Medium.js@master/medium.js:2567:6)
	    at eval (https://localhost:8443/owner/jspm_packages/github/jakiestfu/Medium.js@master/medium.js:2576:4)
	    at eval (https://localhost:8443/owner/jspm_packages/github/jakiestfu/Medium.js@master/medium.js:2587:4)
	    at eval (https://localhost:8443/owner/jspm_packages/github/jakiestfu/Medium.js@master/medium.js:2589:3)
	    at eval (<anonymous>)
	Evaluating<EMAIL_ADDRESS>	Error loading<EMAIL_ADDRESS>as<EMAIL_ADDRESS>from<EMAIL_ADDRESS>
Gotta research a way to ensure rangy is loaded and attached to window-scope before mediumjs starts.

Currently, on the branch, they're imported via <script>-tags. I'm trying to find a way to keep them as part of the bundle.
The systemjs-docu on modules might hold a solution. If no better way to do this is found, this snippet might also work.

Some resources:
* https://github.com/systemjs/systemjs/issues/666
* https://github.com/jspm/jspm-cli/issues/689
* https://github.com/jspm/jspm-cli/issues/1993
* https://github.com/systemjs/systemjs/blob/master/docs/system-api.md#systemregister-name-deps-declare
* https://github.com/jspm/registry/wiki/Configuring-Packages-for-jspm#map-configuration
* https://github.com/systemjs/systemjs/blob/master/docs/module-formats.md
* https://superdevelopment.com/2016/04/14/a-dive-into-systemjs-loading-and-translating/
* https://github.com/systemjs/systemjs/blob/master/docs/config-api.md
* https://github.com/systemjs/systemjs/blob/master/docs/es6-modules-overview.md
* https://github.com/systemjs/systemjs/blob/master/docs/overview.md

Currently trying to get in touch with the jspm-developers over at https://gitter.im/jspm/jspm
So far I've tried putting these in meta['Medium.js'].globals, including
a commonjs-based helper-script that would usually load them and
Medium.js in order, and having the dependencies in an amd-based
helper script and have that as dependency via:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    meta['Medium.js'].deps
    reinstalling Medium.js via ./node_modules/.bin/jspm install Medium.js=github:jakiestfu/Medium.js@master -o "{shim:{'Medium.js': ['medium-import-helper']}}"

In each case the executed bundle would first execute the main script
and crash there, before the dependencies are loaded. If, for testing
 purposes, I use another module that can finish initialization without
 the dependencies, I can see that they get loaded after the main
 script (judging by when I reach the respective breakpoints)

Currently trying to get in touch with the jspm-developers over at https://gitter.im/jspm/jspm
So far I've tried putting these in meta['Medium.js'].globals, including
a commonjs-based helper-script that would usually load them and
Medium.js in order, and having the dependencies in an amd-based
helper script and have that as dependency via:

<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>    meta['Medium.js'].deps
    reinstalling Medium.js via ./node_modules/.bin/jspm install Medium.js=github:jakiestfu/Medium.js@master -o "{shim:{'Medium.js': ['medium-import-helper']}}"

In each case the executed bundle would first execute the main script
and crash there, before the dependencies are loaded. If, for testing
 purposes, I use another module that can finish initialization without
 the dependencies, I can see that they get loaded after the main
 script (judging by when I reach the respective breakpoints)

Reverting to the <script>-style import for now, to get on with this issue. However, this means that these three scripts aren't contained in the bundle and won't go through any linting, should we ever decide to use such. Should the people on jspm/jspm get back to me, I'll fix this.

Places to change:

index.html:33-35
jspm_config.js:16ff
jspm_config.js:56-57
[the amd-style helper](https://github.com/researchstudio-sat/webofneeds/blob/fix_copy-paste_%23680/webofneeds/won-owner-webapp/src/main/webapp/app/medium-import-helper.js]
the commonjs-style helper
the previous helper that shouldn't have done much.


Add Bambu Lab PA6-GF filament colors

I'm not sure about the name I gave (PA6-GF) as it is the name Bambu uses. They also have carbon fiber alternative (PA6-CF). You have Nylon in the materials file, hence my doubt.

This is related to https://github.com/Donkie/SpoolmanDB/pull/9, ho you have any suggestions?

PA6-GF / CF seems to be its own thing and not just regular PA so this name is fine to use imo.


Add alpha parameter for points and interactive methods in umap.plot

This is an initial PR for https://github.com/lmcinnes/umap/issues/613. I added an optional alpha parameter for the points and interactive methods. I intentionally ignored adding it to the interactive plots for large datasets where holoviews is used. This is due to the fact holoviews/datashader has a min_alpha parameter which is used if alpha < min_alpha. If we want to support this we would also need to set min_alpha appropriately but that might be more trouble than it's worth IMO. I also fixed a bug where the holoviews plots wouldn't display in a Jupyter notebook and were throwing deprecation errors.

Hello @gclen! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file umap/plot.py:

Line 301:89: E501 line too long (91 > 88 characters)
Line 306:89: E501 line too long (91 > 88 characters)
Line 326:89: E501 line too long (91 > 88 characters)
Line 334:89: E501 line too long (91 > 88 characters)
Line 431:89: E501 line too long (94 > 88 characters)
Line 586:1: W293 blank line contains whitespace
Line 663:1: W293 blank line contains whitespace

Coverage decreased (-0.2%) to 88.734% when pulling 3dc561faa31aa5295c1aead68058433222d99f59 on gclen:issue-613 into ae5255be571c4a90bd93611a07612b4565c7984d on lmcinnes:master.

This should also address #491. I can pull that change out into a separate PR if you would like

Looks good. Thanks!


Enhance User Status Schema for Storing Previous Status History

Issue Description
The current user status schema lacks the ability to store previous status history, specifically for Out of Office (OOO) changes. We need to enhance the schema to maintain a record of both past and future status changes.
Expected Behavior
The updated schema should include provisions for storing historical data of both past and future status changes, allowing us to maintain a comprehensive history of user status updates.
Current Behavior
The current schema only supports a single future status without preserving the history of past status changes.
Screenshots
N/A
Reproducibility

[ ] This issue is reproducible
[x] This issue is not reproducible

Steps to Reproduce
N/A
Severity/Priority

[ ] Critical
[ ] High
[x] Medium
[ ] Low

Additional Information
N/A
Checklist

[x] I have read and followed the project's code of conduct.
[x] I have searched for similar issues before creating this one.
[x] I have provided all the necessary information to understand and reproduce the issue.
[x] I am willing to contribute to the resolution of this issue.

Thank you for contributing to our project! We appreciate your help in improving it.

User Status Schema
{
  "id": "String",
  "userId": "String",
  "statusHistory": [
    {
      "state": "OOO | IDLE ",
      "updatedAt": "TimeStamp",
      "from": "TimeStamp",
      "until": "TimeStamp",
      "message": "String"
    }
  ],
  "futureStatus": {
    "state": "OOO ",
    "updatedAt": "TimeStamp",
    "from": "TimeStamp",
    "until": "TimeStamp",
    "message": "String"
  },
  "currentStatus": {
    "state": "OOO | IDLE | ACTIVE",
    "updatedAt": "TimeStamp",
    "from": "TimeStamp",
    "until": "TimeStamp",
    "message": "String"
  },
  "monthlyHours": {
    "committed": "Number",
    "updatedAt": "TimeStamp"
  }
}

Example:
{
    "id": "dfdsfdsf3423fdsf",
    "userId": "frw42sskl3232",
    "statusHistory": [
        {
            "state": "OOO",
            "updatedAt": "2019-01-01T00:00:00.000Z",
            "from": "2019-01-01T00:00:00.000Z",
            "until": "2019-01-01T00:00:00.000Z",
            "message": "I am on vacation"
        },
        {
            "state": "IDLE",
            "updatedAt": "2019-01-01T00:00:00.000Z",
            "from": "2019-01-01T00:00:00.000Z",
            "until": "2019-01-01T00:00:00.000Z",
            "message": "Doing nothing" //Hardcoded
        },
        {
            "state": "OOO",
            "updatedAt": "2019-01-01T00:00:00.000Z",
            "from": "2019-01-01T00:00:00.000Z",
            "until": "2019-01-01T00:00:00.000Z",
            "message": "Have to go to the doctor"
        },
        {
            "state": "OOO",
            "updatedAt": "2019-01-01T00:00:00.000Z",
            "from": "2019-01-01T00:00:00.000Z",
            "until": "2019-01-01T00:00:00.000Z",
            "message": "I am on vacation"
        }
    ],
    "futureStatus": {
        "state": "OOO",
        "updatedAt": "2019-01-01T00:00:00.000Z",
        "from": "2019-01-01T00:00:00.000Z",
        "until": "2019-01-01T00:00:00.000Z",
        "message": "Preparing for the exam"
    },
    "currentStatus": {
        "state": "ACTIVE",
        "updatedAt": "2019-01-01T00:00:00.000Z",
        "from": "2019-01-01T00:00:00.000Z",
        "until": "",
        "message": "Working on the task"
    },
    "monthlyHours": {
        "committed": 160,
        "updatedAt": "2019-01-01T00:00:00.000Z"
    }

}


[SPARK-30440] Flaky test: org.apache.spark.scheduler.TaskSetManagerSuite

Found a race in testcase introduced in SPARK-30359  between reviveOffers in org.apache.spark.scheduler.TaskSchedulerImpl#submitTasks and org.apache.spark.scheduler.TaskSetManager#resourceOffer, in the testcase
What changes were proposed in this pull request?
No need to do resourceOffers as submitTask will revive offers from task set
Why are the changes needed?
Fix flaky test
Does this PR introduce any user-facing change?
No
How was this patch tested?
Test case can pass after the change

cc @HeartSaVioR @Ngone51 @cloud-fan

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Updated with review comments. Please review cc @srowen @Ngone51 @cloud-fan

Jenkins test this please

Test build #116248 has started for PR 27115 at commit fc38c64.

Merged build finished. Test PASSed.

Test build #116248 has finished for PR 27115 at commit fc38c64.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class FakeLongTasks(

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/116248/
Test PASSed.

@dongjoon-hyun Updated as per comments, Please review

Updated as per comments. Please review @cloud-fan @dongjoon-hyun @srowen

Retest this please.

Test build #116319 has started for PR 27115 at commit b1099b9.

Merged build finished. Test PASSed.

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

Retest this please

Test build #116321 has started for PR 27115 at commit b03d205.

Merged build finished. Test PASSed.

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

Test build #116319 has finished for PR 27115 at commit b1099b9.

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/116319/
Test PASSed.

Test build #116321 has finished for PR 27115 at commit b03d205.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
class FakeLongTasks(stageId: Int, partitionId: Int) extends FakeTask(stageId, partitionId)

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/116321/
Test PASSed.

Thanks for the quick fix of flaky test!


Fix minor typo in README.md

This PR fixes a small typo found while reading the docs as a newcomer to the project.

I signed


replay integration plus Andrew's changes for articulated-objects branch

Motivation and Context
I don't intend for this to merge. I'm using the PR to document this branch. I expect @ASzot can use these commits.
f2503b8b3a036a7eeed991f520bb03e6bbcac230 - some core replay integration that will merge to master soon and probably end up in facebookresearch/articulated-objects-prototype next time we rebase it to master.
e80c19f714fb9038e002eaae42a7ac893a642b74 - some replay integration specific to the URDF branch
228d18a457bc0c1a489daa6e4ae98cc2cca15fe6 , e86f1407a8afa4c9d5551a81e06a9cac2c20d2a6, and others - Andrew's changes present in aszot/articulated-objects-prototype . All of these were cherry-picked without any merge conflict; there's nothing new in these cherry-picked commits.
See also my pvizplan PR that tests the replay: https://github.com/ASzot/p-viz-plan/pull/4

How Has This Been Tested
p-viz-plan orp/play.py recording and playback. Todo: link to that test branch.
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[ ] 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 change)

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

This is for reference, not merging. Closing.

This is for reference, not merging. Closing.


Google font not loading (http vs https URL)

This appears in the browser console: Blocked loading mixed active content “http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700|Raleway:400,800,900” and the font does not get loaded.

The fix is to change http to https in main.css import url(http://fonts.googleapis.com/css?family=Source+Sans+Pro:400,700


Resubscribe if service worker lost push subscription

Potential fix for #411

However, I have an idea for a possible workaround (without really fixing the underlying issue since we don't know what is causing this):
We could delete the push subscription in IndexedDB if the user manually unchecks the push subscription.
In that case, we know that if the service worker has no push subscription but there is a push subscription in IndexedDB during SYNC_SUBSCRIPTION, this is probably the bug and we can register a new push subscription in the background and send that one to the server. Currently, we aren't able to distinguish between the bug and manually unsubscribing since in both cases, there would still be a push subscription in IndexedDB.
So this means that during unsubscribeFromPushNotifications, we would add code that also deletes the push subscription in IndexedDB

-- https://github.com/stackernews/stacker.news/issues/411#issuecomment-1790675861
simulating the bug by unsubscribing but not deleting the subscription in IndexedDB:
https://github.com/stackernews/stacker.news/assets/27162016/76c11081-8ef6-4753-81b5-c00a0e5bcc93
That it shows Stacker News notification are now active on resubscribing may be annoying but I think it would be useful to keep this for now. With this notification, we can see if it's working or not since you will see this notification if you got resubscribed automatically if you lost your subscription for unknown reasons.
Since we delete the push subscription in IndexedDB on manual unsubscription, you won't get automatically resubscribed in this case.

Just FYI, I just had push notifications re-enabled on my desktop machine which I had disabled a while ago. I imagine since we didn't use to clear IndexedDB, this PR's code detected this as a lost subscription and re-enabled them for me? It might be good to let people know what's happening if they mysteriously get push notifications re-enabled without their action.

I had something similar where it requested push notifications again when I previously denied it.

Every time I visit the site after not having been on it in any tab, it asks me to subscribe now. Is this expected?

Just FYI, I just had push notifications re-enabled on my desktop machine which I had disabled a while ago. I imagine since we didn't use to clear IndexedDB, I suspect this PR's code detected this as a lost subscription and re-enabled them for me? It might be good to let people know what's happening if they mysteriously get push notifications re-enabled without their action.

Ohh, yes, turns out this change wasn't backwards compatible :sweat_smile:
I forgot about the devices which used to have a push subscription and thus still have a subscription in IndexedDB. This is now detected as the bug from #411 and it tries to resubscribe. I can make this backwards compatible via #616

Every time I visit the site after not having been on it in any tab, it asks me to subscribe now. Is this expected?

Mhh, no, that wasn't expected. Maybe it's related to the above so that would also be fixed via #616

Every time I visit the site after not having been on it in any tab, it asks me to subscribe now. Is this expected?

I hope this is no longer the case?

I hope this is no longer the case?

Yep no longer the case that I get resubscribed every time


Algorithm as required for Model Entity & improve tests

Describe your changes :
Fixes #725 & #687.
The first Model Entity version was rather raw, so now we are improving it by having algorithm as a required field for the Model creation. Moreover, we have improved a bit the tests to cover more logic.
Type of change :

[ ] Bug fix
[x] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[x] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[x] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

Thanks for the patch @pmbrull . LGTM

Thanks for the patch @pmbrull . LGTM

Thanks! 🙏


Isolate cause of compilation failure issues

It appears that after registering ts-node, the code then overwrites the methods assigned to require.extensions['.ts'] and require.extensions['.tsx'] with the original method designed for use with javascript.
This PR lets the newly registered methods stand.

It fixes https://github.com/whitecolor/ts-node-dev/issues/185 ?

It fixes #185 ?

Yes. It fixes #185 for me.

Ok I've published new version, check it. This PR, contains the issue that we should revert back extensions each time reregistering ts-node (after an error).

I patched in the fix locally and it also seems to work for me.
Looking at logs with --debug it seems like its less aggressive trying to run code.  It will load a ts file and all its import/require dependencies and then run the code.  Prior to that I would see cases where the code in a .ts file may actually start executing (based on log output) before all the dependencies had finished compiling.
Anecdotal example .. before changes
Loading base config ../webpack/web/webpack.config.ts
/tooling/webpack/web/webpack.config.ts added to watcher
/tooling/webpack/web/webpack.config.ts compiled in 243 ms
/tooling/scripts/getAssetHost.ts added to watcher
/scripts/getAssetHost.ts compiled in 10 ms
/webpack/web/web.plugins.ts added to watcher
Building with assetPath as:  /assets/ **<======= (webpack.config.ts emits this log)**
/webpack/web/web.plugins.ts compiled in 20 ms
Error encountered TypeError: web_plugins_1.getPlugins is not a function

After changes
Loading base config ../webpack/web/webpack.config.ts
/webpack/web/webpack.config.ts added to watcher
/webpack/web/webpack.config.ts compiled in 259 ms
/scripts/getAssetHost.ts added to watcher
/scripts/getAssetHost.ts compiled in 7 ms
/webpack/web/web.plugins.ts added to watcher
/webpack/web/web.plugins.ts compiled in 16 ms
Building with assetPath as:  /assets/ **<======= (webpack.config.ts emits this log)**

In the "after" log it looks from the console output with debugging that webpack.config.ts is not executed until all its dependencies have been loaded.  Prior to this it seems that the code was executed while web.plugins.ts was still compiling.

Tested again after latest changes.  Still working for my use case.  I do not see anything that looks like ts code being executed optimistically/prematurely before all imports have been compiled.
But my results here are anecdotal.  I do not understand the code enough to understand all the nuances of what these changes imply  :-(

Okay. I don't know why this works, but changes those 3 line from:
extensions.forEach(function (ext) {
  require.extensions[ext] = originalJsHandler
})

to
require.extensions['.js'] = originalJsHandler
extensions.forEach(function (ext) {
  require.extensions[ext] = empty
})

solves the problem. But the test that uses compilerOptions fails now.
I'm digging into the ts-node code to see how it treats things the first time through. Maybe there's some other reset that's necessary...
I'm still confused by a lot of this code, but am slowly figuring things out.

I don't understand why reverting back extensions before registring ts-node causes issues.

I'm really confused by this too. The re-registering should be fine.
From what I can tell, ts-node builds up a chain for file handlers. When the service starts, require.extensions['.ts'] and require.extensions['.tsx'] are undefined. If I run a script that generates a GraphQL schema with ts-node it works fine. If I then run it with ts-node-dev and leave those values undefined, it fails. Even though, ts-node automatically fills them with the default JavaScript handler.
Does ts-node-dev apply any defaults that ts-node doesn't?

Somehow these options from ts-node-dev:
{
  dir: undefined,
  scope: undefined,
  emit: undefined,
  files: undefined,
  pretty: undefined,
  transpileOnly: undefined,
  ignore: undefined,
  preferTsExts: undefined,
  logError: undefined,
  project: undefined,
  skipProject: false,
  skipIgnore: false,
  compiler: undefined,
  compilerHost: undefined,
  ignoreDiagnostics: undefined,
  compilerOptions: undefined
}

Turn into this in ts-node, but I can't figure out how they are being translated:
{
  _: [ 'tools/updateSchema.ts' ],
  deps: false,
  'all-deps': false,
  dedupe: false,
  poll: false,
  respawn: false,
  notify: true,
  'tree-kill': false,
  clear: false,
  cls: false,
  'exit-child': false,
  'error-recompile': false,
  scope: false,
  emit: false,
  files: false,
  pretty: false,
  'transpile-only': false,
  T: false,
  'prefer-ts-exts': false,
  'prefer-ts': false,
  'exec-check': false,
  debug: false,
  'log-error': false,
  'skip-project': false,
  'skip-ignore': false,
  'compiler-host': false,
  H: false,
  'script-mode': false,
  s: false,
  rs: false,
  'type-check': true,
  priorNodeArgs: [],
  log: [Function: log] {
    debug: [Function],
    info: [Function],
    warn: [Function],
    error: [Function]
  }
}

All I'm doing is logging these just before tsNode.register() is called in ts-node-dev and on the first line of register in ts-node.

I figured out where those extra values are coming from, but this problem still doesn't make any sense. I need to spend some more time playing with ts-node and see what is different about it's environment.

@jrosspaperless @whitecolor any progress?

@jrosspaperless @whitecolor any progress?

I gave up. Sorry.

I might have a start of an understanding of whats going on here: https://github.com/whitecolor/ts-node-dev/issues/185#issuecomment-726375197


ConcretizationTypeError in nd_coords

I'm trying to implement a class that uses jax.lax.cond such that I can use conditional statements under jit. My class calls the nd_coords function and gives this error:
ConcretizationTypeError: Abstract tracer value encountered where concrete value is expected: traced array with shape int64[].
It arose in the jnp.arange argument 'stop'
The error occurred while tracing the function <lambda> at [/Users/mcha5804/miniconda3/envs/dLux/lib/python3.10/site-packages/dLuxToliman/layers/detector_layers.py:309](https://file+.vscode-resource.vscode-cdn.net/Users/mcha5804/miniconda3/envs/dLux/lib/python3.10/site-packages/dLuxToliman/layers/detector_layers.py:309) for cond. This value became a tracer due to JAX operations on these lines:

It's erroring out in the pixel_fn defined within nd_coords which looks like:
def pixel_fn(n, offset, scale):
    # TODO: calculate the start and end points first and then use linspace
    # so that ops are done on floats not arrays
    # scale = diam / n
    pix = np.arange(n) - (n - 1) / 2.0
    pix *= scale
    pix -= offset
    return pix

I rewrote the function according to the TODO and committed it to the coord-concrete branch (97a05bec3aba3a539cffb99a6b145d93e59815dd). It now looks like:
def pixel_fn(n, offset, scale):
    start = -(n - 1) / 2 * scale - offset
    end = (n - 1) / 2 * scale - offset
    return np.linspace(start, end, n)

This obviously gives essentially the same error:
ConcretizationTypeError: Abstract tracer value encountered where concrete value is expected: traced array with shape int64[].
'num' argument of jnp.linspace
The error occurred while tracing the function <lambda> at [/Users/mcha5804/miniconda3/envs/dLux/lib/python3.10/site-packages/dLuxToliman/layers/detector_layers.py:309](https://file+.vscode-resource.vscode-cdn.net/Users/mcha5804/miniconda3/envs/dLux/lib/python3.10/site-packages/dLuxToliman/layers/detector_layers.py:309) for cond. This value became a tracer due to JAX operations on these lines:
...

Anyway my understanding is that it doesn't like n because it could take on any value and jax doesn't like that? Is there a way around this / is this actually a problem or am I just silly for wanting to use jax.lax.cond in the first place. ...

This pixel coords function is called many many times throughout dLux under jit, I suspect it's the formulation of the function you're using that is generating the value n conditionally on some traced value, hence the error. Can you give a full mwe of this error including how you're using lax.cond? It has some extra constraints that could be giving rise to this

Basically I'm trying to generate a convolution kernel where the kernel size is determined by the jitter parameter A in the kernel_size method. Kernel size is restricted to odd integers.
However I don't want to generate a kernel size of 1 as that leads to yucky issues. So essentially I had
def generate_kernel(self, pixel_scale: float) -> Array:
    if self.kernel_size == 1:
        return np.array([[0, 0, 0], [0, 1, 0], [0, 0, 0]])
    else:
        ... generate the kernel normally ...

Which kinda needs a conditional there. So this is the class in it's current state which is me trying to get around that:
class SHMJitter(BaseJitter):

    A: float
    phi: float

    def __init__(
        self: DetectorLayer,
        A: float,  # amplitude in arcseconds
        phi: float,  # angle
    ):
        # setting parameters
        self.A = A
        self.phi = phi

        # calling parent constructor
        super().__init__()

    def kernel_size(self, pixel_scale: float) -> int:

        kernel_size = np.ceil(2 * self.A / pixel_scale).astype(int)
        kernel_size += 1 - kernel_size % 2  # ensuring odd integer

        return kernel_size

    @staticmethod
    def delta_kernel(pixel_scale: None) -> Array:
        return np.array([[0, 0, 0], [0, 1, 0], [0, 0, 0]])

    def extended_kernel(self, pixel_scale: float) -> Array:
        ... generate kernel the normal way using self.A ...
        return kernel / np.sum(kernel)

    def generate_kernel(self, pixel_scale: float) -> Array:

        # checking for if kernel is a single pixel
        # in which case just return a delta function
        return jax.lax.cond(
            self.kernel_size(pixel_scale) == 1,
            lambda: self.delta_kernel(pixel_scale),
            lambda: self.extended_kernel(pixel_scale),
        )

Okay yep so this isn't going to work no matter which way you slice it. The kernel size parameter (even though it's an int) is determined by pixel scale which is a tracer -> therefore kernel size will always be a tracer and can't be used as a shape parameter. This is a consequence of XLA requiring static array sizes, there's no fancy footwork with the code that you can do that will fix this.
Because of this limitation, easiest way around this is probably just making kernel size an attribute of the class. Not an ideal solution but there is simply no way to compile a function with dynamic arrays sizes to XLA no matter how hard you try.

:(


Program fails when I switch rendering modes to AO or binary

Thank you for feature but sometimes when I switched rendering modes to AO or binary program fails with
Fatal : VkResult is ERROR_DEVICE_LOST in C:/msys64/home/thr/RVPT/src/rvpt/vk_util.cpp at line 167
Assertion failed: res > VK_SUCCESS, file C:/msys64/home/thr/RVPT/src/rvpt/vk_util.cpp, line 167
164 void Queue::submit(VkSubmitInfo const& submitInfo, Fence const& fence)
165 {
166 std::lock_guard lock(submit_mutex);
167 VK_CHECK_RESULT(vkQueueSubmit(queue, 1, &submitInfo, fence.get()));
168 }
tested on windows 10 and ubuntu 21.10 with geforce gtx 1050ti.
same result - program aborted.
How to fix it?

I fixed it with commit 3bc9c00b2587d5164e97548b9a67f5bdce36efe5 in my forked repo
https://github.com/tigrazone/RVPT/commit/3bc9c00b2587d5164e97548b9a67f5bdce36efe5


Jenkins Docker based agents.

I understand that the Docker agent approach involves running Jenkins agents as Docker containers. This offers flexibility and scalability, as containers can be dynamically created and destroyed based on demand. However, running multiple containers on a single node can lead to resource contention, potentially overloading the node, right? How can we overcome this?

To manage resource contention when running multiple Jenkins agents as Docker containers on a single node, you can set resource limits for CPU and memory using Docker's flags, implement dynamic scaling with orchestration tools like Kubernetes, and monitor resource usage with tools like Prometheus. Additionally, optimize job configurations to reduce resource consumption, utilize Jenkins' queue management features to control job concurrency, and consider separating resource-intensive jobs onto dedicated nodes. By combining these strategies, you can ensure efficient resource utilization and maintain optimal performance.

correct me if i am wrong


OrganizationsService: Add projects methods

ListProjects returns list of organization projects
CreateProject creates organization project

Thanks for working on this @shawncatz, it's looking great overall.

@shurcooL I've moved the definition and updated the comment to include references to both places it's used.
This should be complete, let me know if there's anything else I can do.
Thanks :)

Because the change of signature of RepositoriesService.ListProjects method is a breaking change, can you bump up the version by one at https://github.com/shawncatz/go-github/blob/1fe303ba3b6789190206f9652c8316f8d9d96bb5/github/github.go#L30?

of course, didn't even think of that

could I get an idea of when this might be merged? don't mean to push, just curious

Thanks!
--
Shawn Catanzarite
408-605-7744
http://shawncatz.com/
http://linkedin.com/in/shawncatanzarite
On March 21, 2017 at 9:23:02 AM, Glenn Lewis<EMAIL_ADDRESS>wrote:

Merged #599 https://github.com/google/go-github/pull/599.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/google/go-github/pull/599#event-1008901079, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABlbhiTqtGPrmpUm9lYdHDaQXlQR26fYks5rn_lmgaJpZM4Mh23V
.


fix formatting of strings within a macro

close #3302

Thank you for the PR! The fix looks good.
This PR fixes an idempotency bug, so this does not require the version gate (the current behavior is already broken, so we need not worry about introducing breaking changes). Sorry, but could you remove it please?

Sorry I didn't comment a description of the fix @topecongiro
This bug is related to #3270 where commented strings were indented. The PR #3284 did not account for commented strings inside a macro: the commented string at https://github.com/rust-lang/rustfmt/pull/3326/files#diff-defb319f41585c123bd17193dcfc0310R26 was indented.
The idempotency bug stems from #3284 not fixing  https://github.com/rust-lang/rustfmt/pull/3326/files#diff-b4aea3e418ccdb71239b96952d9cddb6R442 as well.
Therefore, I think the version-gate is needed at https://github.com/rust-lang/rustfmt/pull/3326/files#diff-3dbd16223f25e8b5e0bcf099743107e9R582.

Thanks for your explanation, I missed the context.


Cannot build project, pfx is missing

Hi Erich, great your project to create Swiss QR codes within excel. I downloaded the git repo but cannot build it (with VS2019).
It "complains":
Severity	Code	Description	Project	File	Line	Suppression State
Error		Unable to get MD5 checksum for the key file "SwissQRCode_1_TemporaryKey.pfx". Could not find file 'C:\Users\imfeldc\Source\Repos\SwissQRCodeExcel2\SwissQRCode_1_TemporaryKey.pfx'.	SwissQRCode
The file is missing. Do I need to create them? How?
Thanks in advance.

I've solved it; it is required to create a new "test certificate".
Within your Solution Explorer:

right click on your project
click on properties
usually on the left-hand side, select the "Signing" tab
press "Create test certificate" button


Feature  monolithic container

Large update to docker setup.  Allows tau to be compiled into a single container (using sqlite3 instead of postgres, and a local instance of redis), to allow easier deployment to cloud services.  Also allows user to disable ngrok and use the public url of the server.

This is awesome!


enforced hill climbing

generalizes hill climbing to keep searching even if no immediate improvement can be found
it's very slow with depth>0, as you can imagine. i'm not sure if will use this, or if it's better than GBFS, but maybe? it can't hurt to have in our arsenal...

@ronuchit good thing you made me test, I found some issues... (not affecting anything we were doing yet though)


Adding micahhausler as reviewer and security contact

Micah is an official security contact for EKS so I'm
adding him to the contacts in this repository.
Additionally proposing adding Micah as a reviewer due to his
knowledge of and interest in the project.

/cc @micahhausler

Thanks! Happy to help

/lgtm


Harmentz Inn (NIght) Softlock

13679_60.txt
As you enter the the inn, the screen fades to black and softlocks.

fixed in patch 00141


[BUG]:  In Query mode, will there still be an output of answers if the content of the query cannot be found in the knowledge base?

How are you running AnythingLLM?
Local development
What happened?
When the chat mode is set to Query mode, responses are generated even if the content of the question is completely unrelated to the knowledge base. However, the chat mode settings mention: "Query will provide answers only if document context is found." This implies that answers should only be given when the document context is identified. Is there a contradiction here?

Are there known steps to reproduce?
No response

When displaying the cited documents, can the similarity of the documents be shown, or is there a sorting by similarity, otherwise the displayed content has a very low similarity and essentially no reference value?

That context means that the RAG process determined that is was semantically similar (not that it was useful! It does not do an evaluation, only similarity). So it is possible to get context that is fundamentally useless for your question but did somehow get something from the vector db.
We can add the score to each chunk though - which I think would be useful for debugging - which again is only the score of its semantic similarity from the vector db, not that it will answer your question fully.


Missing @RabbitHandler support in tracee-springrabbitmq?

Hi,
in tracee-springrabbitmq, there is only example on how to message sending. Is there any support for listener/handler in planning？
 2016-01-22 10:16:07.650  INFO [] [Z15JS50DA3AGAD0WT273ZZGTLLBDZAL9] 12786 --- [io-11001-exec-1] e.s.Application                    : Saying how are u
 2016-01-22 10:16:07.650  INFO [] [Z15JS50DA3AGAD0WT273ZZGTLLBDZAL9] 12786 --- [io-11001-exec-1] e.s.Application                    : Trying to tell friends I said how r u
 2016-01-22 10:16:07.657  INFO [] [Z15JS50DA3AGAD0WT273ZZGTLLBDZAL9] 12786 --- [io-11001-exec-1] e.s.Application                    : Done telling friends I said how r u
 2016-01-22 10:16:09.376  INFO [] [] 12786 --- [cTaskExecutor-1] e.s.Application                    : Receiving how r u

The last line of the above logs is generated by
@RabbitHandler
protected void process(@Payload String howAreU) {
    log.info("Receiving {} ", howAreU);
}

By debugging, I find there is a TPC header in this message. But it seems that I have to put it into MDC manually?

Hi @Hippoom. You are right, we are missing an example there!
I am not really familiar with spring-ampq but from it quickstart docs it looks like as if you could just pass in your TraceeMessagePropertiesConverter into the MessageListenerAdapter constructor.
Hope that helps!

@danielwegener I am a little bit confused.
The MessageListenerAdapter constructor accepts a delegate and a MessageConverter, but  TraceeMessagePropertiesConverter is a subclass of MessagePropertiesConverter.

@Hippoom : Sorry for the delay. The rabbitmq part was a contribution and it sticks to spring-rabbit 1.3.9. When I got you right you're missing some features of the newer 1.4.x/1.5.x series of the spring-amqp module.
(See https://spring.io/blog/2015/05/08/spring-amqp-1-4-5-release-and-1-5-0-m1-available )
Currently we stick to Spring 3.2 due compatibility reasons. I'll check the version dependencies or we should add this with TracEE 2.0 and Spring 4.x.

The dependencies:
spring-rabbit 1.5.x => Spring 4.2
spring-rabbit 1.4.x => Spring 4.1
spring-rabbit 1.3.x => Spring 3.2
@danielwegener : EoL of Spring 3.2 is the 31.12.2016. Maybe we've to upgrade Spring to 4.1 in TracEE 2.0 to fix our issues and get a more modern Spring integration. Currently I don't see any reason to change to protocoll how we transfer the TPIC, so TracEE 2.0 could be fully backward compatible on communication level.
Let's discuss this on the phone later on ...

I tend to agree. We have to see then if we continue to maintain the TracEE 1.x branch then.

Perhaps we should reconsider how we release bindings of non-standard frameworks like spring.
Usually standard frameworks are much more stable and usually backward compatible with older versions We do not have that guarantee with frameworks like Spring.
So it might be a good idea to release those Spring related bindings independently from trace core artifacts. In that way we would be able to support multiple versions of external frameworks with one single tracee release too.
In general we should have any problems regarding compatibility of those bindings with tracee. Because most bindings just use the Tracee and TraceeBackend class which shouldn't change in the future.

From our perspective you're right. It's easier for us to maintain several versions of a third party library and it's the cleanest way to release modules only if they really have changed.
On the other hand some of TracEE users like to use the BOM and don't want to investigate which version of the binding should work with the TracEE-version.
So for the user perspective I think it's a no-go to use several different versions of modules just for a helper library like TracEE.
10 Minutes ago I tried to figure out the right versions of ActiveMQ modules and it's a mess if a developer get lost in the dependency hell. That's why I like to have the same version for all of our modules.
Maybe we should discuss this in the office how we handle this in the feature - and how we handle SLF4j upgrades, which is one of our main dependencies ...

@SvenBunge @danielwegener
Sorry for the late response, maybe I got myself misunderstood. I raised this issue because for message receiving part, if implemented there should usually be something to decorate the listener. For example,
in tracee-jms, we have TraceeMessageListener which is an interceptor, writes the context and cleanup when finished. in the pull-request for tracee-springjms, I proposed a subclass to override the default listener method which also writes the context and cleanup when finished. But I don't see anything like this in tracee-springrabbitmq. Yes there is a method handing incoming message but there is no cleanup!
I'm not asking to support @RabbitHandler directly, in my experience of the pull-request for tracee-springjms, there should be something like MessageListenerAdapter to adapter the method annotated @RabbitHandler  underhood. And usually this MessageListenerAdapter is released with the initial version of spring-amqp.

@Hippoom ahh ok. The current module works only in conjunction with the RabbitTemplate. This isn't applicatble for your application?
The structure of springs rabbitmq implementation is quite similar to spring-jms. So look into org.springframework.amqp.rabbit.listener.adapter.MessageListenerAdapter we can try the reflaction aproach by implementing some
 public class TraceeMessageDelegate {
   public void handleMessage(Message message) {
... read TPIC from the message ...
   }
 }

But maybe I understand the reflection stuff wrong ...
(I'll look into some production code, when I'm back at home. But I think currently they use only the RestTemplate to read messages from the queue.


Suspense + Hydration is broken in React 16.10+

original issue
https://github.com/facebook/react/issues/16938
test which explains everything
https://github.com/facebook/react/pull/16945/files#diff-ab371863932cd2e8f0ba14ff2eaab380R687

Mostly for your information.
The last React version which will work out of the box with the provided examples API is 16.9. After that one has to use <Suspense fallback={undefined}> during the hydration, or it will fail.
In other words this moment might be changed a little - renderFallback should return undefined during hydration https://github.com/atlassian-labs/react-loosely-lazy/blob/f3f19d0058feaca11b075a7ecaaa9889f8b0476e/src/suspense/component.tsx#L116-L118
Questions yet to answer

can one render Suspense first time without fallback and add it using useEffect a render tick later?

That is indeed what LazySuspense does internally however to do that we need to detect SSR vs non SSR render.
So if you see the error while SSRing, it is because the library thinks that you are running the code in client side mode, and that renders a real Suspense instead of the custom "markers" (so it is not an error due to react > 16.9).
We have a function called isNodeEnvironment that tries to automatically detect if you are running on node, but I guess it returns false on your SSR env so we need to fix that.
Can you provide more info so we can tweak that function? Or do you have better recommendations on how to  do that?
One option I thought about was to use the babel plugin to set that value, but a runtime check should be doable anyway 🤔

So the problem is on the client side, not on the server.
React, since 16.10 "knows" that you cannot use Suspense during SSR, and if sees it during hydration - ignores content inside unless fallback set to undefined.

Yet again - any <Suspense fallback="something/> during hydration will break markup.

Wrapped content is expected to be recreated - https://github.com/sebmarkbage/react/blob/185700696ebbe737c99bd6c4b678d5f2a923bd29/packages/react-dom/src/tests/ReactServerRenderingHydration-test.js#L668-L682
The problem was discovered not with loosely implementation, but reported for imported-components. After a quick investigation I've found the root cause and here the story ends.
From now on my duty is to fix the problem in the projects I maintain, and let other projects aware of the problem.

Ah, I see what you mean. I actually didn't know about the <Suspense fallback={undefined} /> option. I've found a different solution (render the Suspense boundary only after hydration) but might investigate if, as you say, we can simply getting it working by rendering undefined.
Given with the current trick we are already supporting React 16.10+ (and React 17 beta), I'll mark this as enhancement

Not sure how you render Suspense boundary after hydration as long as that should lead to local tree remount. And could not find corresponding logic in the code.

Sorry, I wrote that wrongly. What I meant to say is that we don't really use Suspense fallback for hydration, as the content of SSR is collected and rendered by a sibling component. The flow is:

LooselyLazy collects all html for render/hydration on init
LazySuspense renders children inside Suspense with fallback prop rendered by DynamicFallback (but never happens really)
children finds the corresponding hydration html and calls setFallback on LazySuspense
children renders React.lazy, which throws an error promise that hits the boundary straight away
LazySuspense Suspense boundary re-renders to render the fallback, but this time DynamicFallback output changes as  hydrationFallback has been set  (as setFallback is sync) and it returns null
LazySuspense resumes its content rendering, and renders a Suspense sibling with hydration html (again DynamicFallback  does the magic here as is able to consume the fresh hydrationFallback value)

So at this point, inside LazySuspense, what we have is a Suspense boundary that holds the lazy promise, rendering null as a fallback followed by a sibling that is rendering the hydrated fallback.
As soon as Suspense is done with the promises and unmounts DynamicFallback, we clean the hydration html value and make LazySuspense re-render, killing the Suspense sibling from the tree and let React render the content inside Suspense normally.
Didn't have time to fully investigate the performance implications of this last step (as whenever React recreates all DOM nodes or if it picks them up somehow) so that might be where your suggestion of using undefined instead of the current special render-prop component could be performing better.

From what I know (spent a few years fighting among HotLoader) - React always discards the old tree on component change. Replacing fallback with actual component might resolve to the same HTML, but the original DOM tree would be rejected.
So it should have some perf implications (at least non properly cached images might "blink"), and the question is that implication bearable or not quite.

PS: Your partial hydration implementation without the need of wrapping div is 🥳
PPS: That might be a solution for "non nested" splitting points - if the actual LazySuspense can detect "content is inside", then it might skip own hydration via suppressHydrationWarning, but that would require outer DOM node
https://gist.github.com/theKashey/8b54d9a5c050d8faa929aad9682aa485#file-hydrate-js-L28-L32


Could not import runpy module

Your OS (including version) where you are running AlexaPi:
Raspian Jessie Lite April 2017

Your hardware platform and model you are running on:
Raspberry Pi 2 Model B

Python release (python2 --version):
Python 2.7.9

Description of problem:
When installing through the shell script I get the error Could not import runpy module then a traceback follows which ends in FileNotFoundError: [Errno 2] No such file or directory (full traceback included below). I attempted first on Raspian Jessie with Pixel and then did a clean install of Raspian Jessie Lite and followed installation instruction step-by-step. Further up in the output are two groups of four sh: 0: getcwd() failed: No such file or directory errors; I'm pretty sure this is the root of the error. There are no other errors that I can see but its possible I missed them.
Traceback (if applicable):
Could not import runpy module
Traceback (most recent call last):
  File "<frozen importlib._bootstrap>", line 2237, in _find_and_load
  File "<frozen importlib._bootstrap>", line 2222, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 2164, in _find_spec
  File "<frozen importlib._bootstrap>", line 1940, in find_spec
  File "<frozen importlib._bootstrap>", line 1911, in _get_spec
  File "<frozen importlib._bootstrap>", line 1879, in _path_importer_cache
FileNotFoundError: [Errno 2] No such file or directory

Additional info:
AlexaPi.service status:

AlexaPi.service - Alexa client for all your devices
   Loaded: loaded (/usr/lib/systemd/system/AlexaPi.service; enabled)
   Active: failed (Result: exit-code) since Sat 2017-05-06 19:17:18 UTC; 54min ago
     Docs: https://github.com/alexa-pi/AlexaPi/wiki
  Process: 703 ExecStart=/usr/bin/python /opt/AlexaPi/src/main.py --daemon (code=exited, status=1/FAILURE)
 Main PID: 703 (code=exited, status=1/FAILURE)

May 06 19:17:14 raspberrypi systemd[1]: Started Alexa client for all your devices.
May 06 19:17:18 raspberrypi python[703]: CRITICAL: Can not find configuration file. Exiting...
May 06 19:17:18 raspberrypi systemd[1]: AlexaPi.service: main process exited, code=exited, status=1/FAILURE
May 06 19:17:18 raspberrypi systemd[1]: Unit AlexaPi.service entered failed state.

Hey. This seems like a broken python install.
Check out https://github.com/rg3/youtube-dl/issues/523#issuecomment-10780325

@ryjo1026 have you solved your issue?

Closing due to inactivity. Feel free to reopen.


Chore: update artifact actions

The master tag was pointing to a very old build that sometimes failed (the "master" branch is now "main"). More appropriately pointing to a version now. Also, changed to avoid compressing artifacts that are already compressed.
In the process, also updated other actions including setup-go, which comes with its own caching for Go deps so we don't need the custom cache tasks

There are conflicts now.

There are conflicts now.

Fixed


feat : graph plotter

Closes: #82

Title : Graph Plotter Program
Name: Akarsh Ghildyal
Idenitfy yourself: SSOC Contributor

Describe the add-ons or changes you've made 📃
I have integrated a graph plotter application, that asks for function type : Linear, Quadratic, Sine, Cosine then asks for the corresponding values to display it in a graph.
Give a clear description of what have you added or modifications made
I have utilised plotly for the graphical representation.
Type of change ☑

What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested? ⚙

I ran the program locally and tested it.
Checklist: ☑

[x] My code follows the Contributing Guidelines & Code of Conduct of this project.
[x] This PR does not contain plagiarized content.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly wherever it was hard to understand.
[x] My changes generate no new warnings.

Screenshots 📷

https://github.com/user-attachments/assets/620d1826-76ba-48c8-8924-f00d5d2e0065
Note to reviewers 📄

none.

@Avdhesh-Varshney added some more functions, polynomial degree can be increased.
kindly review and merge
https://github.com/user-attachments/assets/d10b3c12-849d-4090-a54b-90e3fa190656


firefox support

https://bugzilla.mozilla.org/show_bug.cgi?id=1210906

I think the best way is to use Frame Timing API. Now I try to get the timing of fist painting via that API.


Works just in terminal, but not in console.

I think this lib just supports Linux terminal style coloring.


Invalid XHTML in docs

The docs contain things like:

Concepts

This is invalid, you cannot nest an  element inside another  element.

A key is a part of the element type used to identify and retrieve

This is invalid, you cannot have a  child of
.

typedef begin<Sequence>::type i1;

You cannot have  inside
 (there are other cases like this with  too).

Sequences

Concepts

You cannot have multiple elements with the same id attribute.

<colgroup>
<col width="39%" />
<col width="61%" />
</colgroup>

You can't have a  as a child of
.
These validation errors cause problems for packagers, as invalid XML is a potential security risk.
Either don't pretend the files are XML (e.g. change the doctype to HTML 5), or validate them and fix the errors please.

@jwakely did you resolve all the issues with your PR?

I think I fixed all the problems at the time. There might be new ones introduced since then, I haven't checked.


Clears unacceptable date on input focus or calendar button click.

Summary
Closes #828.
Changed Behavior

When the default date is out of range or excluded, putting focus on the input field or clicking on the calendar button will clear that unacceptable default date as if no default date was provided.

Deployment Links
For functional review go to the last two tests in these links and verify that the defaulted date/time is cleared when putting focus on the date or time input field or clicking on the calendar button to show the picker.

https://terra-core-deployed-pr-974.herokuapp.com/static/#/tests/date-picker-tests
https://terra-core-deployed-pr-974.herokuapp.com/static/#/tests/date-time-picker-tests

Functional verification completed. The date and time test examples display and function as expected when given an unacceptable date.


multiple impl blocks & generics

From looking through some older issues i found that generics and custom traits are not supported by pyo3.
Is that something that is on the roadmap?
or is it an "impossible" issue?
I am used to using pybind11's interface which allows for py::class_ being defined in (templated) functions, making it easy to bind existing libraries. I think there is no counterpart in pyo3 and probably this is impossible too?
EDIT: I got multiple impl blocks working by enabling the "multiple-pymethods" feature in cargo.toml
#[pyclass]
pub struct TestPyVector {
    v: TestVector<2>
}

#[pymethods]
impl TestPyVector {
    #[new]
    pub fn __new__(v: [f64; 2]) -> PyResult<Self> {
        Ok(Self {v: TestVector::new(v)})
    }

    pub fn dot(&self, other: &Self) -> f64 {
        let result = self.v.dot(&other.v);
        result
    }
}

#[pymethods]
impl TestPyVector {
    pub fn length(&self) -> f64 {
        self.v.length()
    }
}

I'm leaving the error message for other users of this library to find it in case.
error[E0119]: conflicting implementations of trait `pyo3::class::impl_::PyMethods<vector::TestPyVector>` for type `pyo3::class::impl_::PyClassImplCollector<vector::TestPyVector>`
  --> src/vector.rs:60:1
   |
47 | #[pymethods]
   | ------------ first implementation here
...
60 | #[pymethods(parent=TestPyVector)]
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ conflicting implementation for `pyo3::class::impl_::PyClassImplCollector<vector::TestPyVector>`

See https://pyo3.rs/v0.15.1/migration.html?highlight=inventory#new-multiple-pymethods-feature

thanks @aviramha, actually i did open an issue for two things and found the multiple-pymethods mysefl.
I will open a new issue for the generics.


Use OverlordClient for all Overlord RPCs.

Continuing the work from #12696, this patch removes HttpIndexingServiceClient and the IndexingService flavor of DruidLeaderClient completely. All remaining usages are migrated to OverlordClient.
Supporting changes include:

Add a variety of methods to OverlordClient.

Update MetadataTaskStorage to skip the complete-task lookup when
the caller requests zero completed tasks. This helps performance of
the "get active tasks" APIs, which don't want to see complete ones.

Nice! I had started #14537 but I can close that one in favor of this.

Ah, I didn't notice that one! It looks somewhat different though. In this patch I tried not to change any logic, just change the RPC client that is used. In #14537 you're changing the logic too by making it more async. It's still worth considering separately from this effort to switch out all the RPC clients.

Yes, @gianm , that PR is about unblocking coordinator runs if the Overlord is slow to accept compaction tasks. As you suggest, I will probably proceed with the alternate approach (of using a separate thread for each duty group) there and remove the OverlordClient-related changes.

@kfaraz Thanks for reviewing. I just updated the PR based on some of your comments. Let me know if you have any further comments, otherwise I'll merge this once CI is clean.

Changes look good to me, @gianm , we can proceed with the merge.

@gianm , Since we merged this, auto-compaction integration tests have been timing out after 6 hours and failing. Failing tests include ITAutoCompactionTest, ITAutoCompactionLockContentionTest. From what I could tell, compact tasks are not getting submitted by the coordinator duty to the overlord.
I tried one of the tests locally (ITAutoCompactionLockContentionTest) but it ran fine. Not sure if there is a problem in the IT environment or something.


deps: update content-disposition to v0.5.3

Safe Buffer >> https://github.com/jshttp/content-disposition/blob/master/HISTORY.md#053--2018-12-17

Ref #comment


39 angular velocity

Hola,
You can make a pull request and merge this branch with the release :)

Yap, but Jeremy wants to do some tests so I don't wanna merge the changes
before that in the cleosat repo... I'll take ur advice though, but in a
cloned local repo ;)
Le mer. 15 juin 2022 à 7:11 PM, Christian Adam, PhD <
@.***> a écrit :

Hola,
You can make a pull request and merge this branch with the release :)
You can view, comment on, or merge this pull request online at:
https://github.com/CLEOsat-group/satellite-tracking/pull/41
Commit Summary

b613cbc
https://github.com/CLEOsat-group/satellite-tracking/pull/41/commits/b613cbccff25dcb8848255aebbe3a59c2401c78a
feature: compute angular velocity with RA and DEC using spherical geometry
acaf1fe
https://github.com/CLEOsat-group/satellite-tracking/pull/41/commits/acaf1fe5c1ce4446ee9ba4a14212b095ad94880f
Merge pull request #40 from ed-ortizm/angular-velocity

File Changes
(2 files
https://github.com/CLEOsat-group/satellite-tracking/pull/41/files)

M leosTrack/track/visible.py
https://github.com/CLEOsat-group/satellite-tracking/pull/41/files#diff-baecb516d79b08b9b8c27f93894bc191e53f4af905dd4ae9aa73b8df5abcd4aa
(35)
M track.ini
https://github.com/CLEOsat-group/satellite-tracking/pull/41/files#diff-30c9a02560a1be202ab540e0c36a0a6911c50832c80a8072417900c97f2c0572
(4)

Patch Links:

https://github.com/CLEOsat-group/satellite-tracking/pull/41.patch
https://github.com/CLEOsat-group/satellite-tracking/pull/41.diff

—
Reply to this email directly, view it on GitHub
https://github.com/CLEOsat-group/satellite-tracking/pull/41, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AB2AEHAB2XRI2MJPBCHIUQDVPJPLHANCNFSM5Y45SCFQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Option to use reference the latest version

Should double check that all references are using identity and not persisitentIdentity.
Should include an option on the edit part dialog as to whether the part should "Always reference the latest version".  The default should be false.  If checked, the reference to this part should be changed to use the persistentIdentity.

The PartEditDialog gets all the information on its state from the CD that is used to create it.  Therefore, adding a checkbox that controls whether the CD being edited is always the latest version or not would be simple, but having the state of this checkbox persist every time the dialog is used would be difficult.

The way you could make it persist is to check the Definition for the Component and see if it is using an identity or persistentIdentity.  Namely, when you fetch the CD, you can compare the definition reference to the identity and persistentIdentity to see which one matches.

On Jun 17, 2016, at 11:33 AM, Michael Zhang<EMAIL_ADDRESS>wrote:
The PartEditDialog gets all the information on its state from the CD that is used to create it. Therefore, adding a checkbox that controls whether the CD being edited is always the latest version or not would be simple, but having the state of this checkbox persist every time the dialog is used would be difficult.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SynBioDex/SBOLDesigner/issues/29#issuecomment-226832108, or mute the thread https://github.com/notifications/unsubscribe/ADWD946iPlwql3waT81TBMKsOOwcK74Dks5qMtpsgaJpZM4I2u1F.

No longer relevant


[Feature / SWP-1902]: Solve Tritium formatting display problem

Description
Every time an MIS user updates the revenue profile (public group) for a Tritium unit, we want to make sure that the message displayed on the Payter reader (cost info) is aligned with the revenue profile.
Every time the pre-auth amount is updated for a Tritium unit, we want to make sure that the message displayed on the Payter reader (pre-auth info) is showing the correct value.
Acceptance criteria
Updating the tier of the public group in a revenue profile (p/kWh) for a Tritium unit on MIS, will update the custom message on the Payter reader showing the correct revenue profile in p/kWh.
Updating the tier of the public group in a revenue profile (£/h) for a Tritium unit on MIS, will update the custom message on the Payter reader showing the correct revenue profile in £/h.
Amends to A/C
If there's no revenue profile don't think display the message as the unit will be free and won't require contactless.
Dynamic preauth - We shouldn't / can't be concerned with it becoming dynamic in the scope of your card IMO
PreAuth format can be £30.00 instead of £30

Can you add a description to this PR also please?

Can you add a description to this PR also please?

yaaaassss, sure

The description on this PR is exactly the same as the MIS PR https://github.com/Pod-Point/admin-tool/pull/1117#issue-495631913
Can we please just specify what is being changed in each PR instead of copying over what's on the card, twice :pray:


malformed data check logic deletes most of the data

Accidentally used "splice" instead of "slice" to examine the fields that must be numbers.
Imported from Georgia Tech github:
{"created_at":"2019-04-18T11:16:14Z","updated_at":"2019-04-18T11:16:22Z","closed_at":"2019-04-18T11:16:22Z","html_url":"https://github.gatech.edu/ekobrin3/2019-Spring-CSE6242-flowgridviz/issues/46","id":78871}

Fixed in b8a2a632c2ae76475d3ed11ba2fb0b1311c50875
Imported from Georgia Tech github:
{"created_at":"2019-04-18T11:16:22Z","updated_at":"2019-04-18T11:16:22Z","html_url":"https://github.gatech.edu/ekobrin3/2019-Spring-CSE6242-flowgridviz/issues/46#issuecomment-42131","id":42131}


Discuss AWS marketplace

https://aws.amazon.com/marketplace

When to use
How appliances work
Major players
Stats or overview

This is my baby! (& Lynn Langit's)!!!


Refactor is_valid_uuid method

Today the is_valid_uuid method in JujuTopology class, utilises a regex to validate UUID v4:
def is_valid_uuid(self, uuid):
    """Validates the supplied UUID against the Juju Model UUID pattern."""
    regex = re.compile(
        "^[a-f0-9]{8}-?[a-f0-9]{4}-?4[a-f0-9]{3}-?[89ab][a-f0-9]{3}-?[a-f0-9]{12}$"
    )
    return bool(regex.match(uuid))

An old friend told me many years ago:

If you have a problem and you use regular expressions to solve it, you now have two problems.

Jokes aside, regular expressions are powerful but complex to read sometimes.
We can avoid regex in this case by using the python uuid module. The result is much easy to read and maintain.
def is_valid_uuid(self, _uuid) -> bool:
     """Validate the supplied UUID against the Juju Model UUID pattern."""
     try:
         return True if uuid.UUID(_uuid).version == 4 else False
     except (TypeError, ValueError):
         return False

The method was updated:
    def is_valid_uuid(self, uuid):
        """Validate the supplied UUID against the Juju Model UUID pattern."""
        # TODO:
        # Harness is harcoding an UUID that is v1 not v4: f2c1b2a6-e006-11eb-ba80-0242ac130004
        # See: https://github.com/canonical/operator/issues/779
        #
        # >>> uuid.UUID("f2c1b2a6-e006-11eb-ba80-0242ac130004").version
        # 1
        #
        # we changed the validation of the 3ed UUID block: 4[a-f0-9]{3} -> [a-f0-9]{4}
        # See: https://github.com/canonical/operator/blob/main/ops/testing.py#L1094
        #
        # Juju in fact generates a UUID v4: https://github.com/juju/utils/blob/master/uuid.go#L62
        # but does not validate it is actually v4:
        # See:
        # - https://github.com/juju/utils/blob/master/uuid.go#L22
        # - https://github.com/juju/schema/blob/master/strings.go#L79
        #
        # Once Harness fixes this, we should remove this comment and refactor the regex or
        # the entire method using the uuid module to validate UUIDs
        regex = re.compile(
            "^[a-f0-9]{8}-?[a-f0-9]{4}-?[a-f0-9]{4}-?[89ab][a-f0-9]{3}-?[a-f0-9]{12}$"
        )
        return bool(regex.match(uuid))

The fix in the Operator framework was merged in this PR

I would like to work on this issue

Hi @grequa
We are happy that you want to work on this issue!
Let me know if you need any guidance.
You can chat with us in this Mattermost channel


Issue 136 - Scope handling in Toolkit fixed

Description
Current behavior:
For SMART on FHIR, you need to create a custom FHIR audience, not the FHIR server name. When you set the scopes in Toolkit in the binding, it does not get passed down to the builder in the Toolkit. Right now it assumes that the audience is the server name.
Expected behavior: Honor the correct audience name when scopes are set in the binding.
Related issues
Addresses [issue #].
Testing
Using the Quickstart sample project, the scopes were added to RestOptions binding, which were defined as Audience in FHIR Service. Was able to fetch patient information without any errors.
Reviewer Checklist

[ ] Update the title of the PR to be succinct and less than 50 characters
[ ] Tag the PR with the type of update: Bug, New-Sample, Enhancement, or New-Feature
[ ] CI is green before merge

@v-ajajvanu @shashanknarang27 - CodeQL is reporting a vulnerability with Azure.Identity while doing a dotnet restore.
https://github.com/advisories/GHSA-m5vv-6r4h-3vj9

/azp run

/azd up


I-186 - add reduced chi squared to .fit export

Describe your changes
Closes #186
I added the reduced chi squared value to both the summary section and the verbose section of the fit export. @benfrandsen does this look like what you're looking for approximately?

Checklist before merging your PR

[ ] I have tagged the relevant issues in this PR
[ ] I have performed a self-review of my code
[ ] I have documented my code as necessary for clarity
[ ] I have ensured the tests are passing
[ ] I have written or updated tests as necessary
[ ] I have updated the README if necessary
[ ] I have checked any security advisories brought up by the CodeQL action

@jaredblack This is all looking great!


Self hosting images

I have a running instance of those modifications (and a couple of other improvements I'll push in a few days) running here: http://<IP_ADDRESS>:8080/
This will allow users to upload images to the server instead of using filepicker. I've developed the backend code to support attachments and also customised our markdown editor to use the new attachments APIs.
Please, take a look, @leocwolter :-)

Couldn't access your instance :(

I've finished to fix your comments, @leocwolter, I'm :ship:ing it now!
Thanks!!!


grpc success/failure stat should count more than 0 as success

https://github.com/lyft/envoy/blob/3e62653863125c07fc78fcc4bd967a10f026114b/source/common/grpc/common.cc#L34
We use this success stat to calculate our services' success rate. In the REST world, I've generally seen success rate calculated as 2xx+3xx+4xx/total_count. What envoy does now for grpc seems like the equivalent of just having 2xx in the numerator. For example, FailedPrecondition should not count as a failure in calculating SR, right?

I think @fengli79 and @lizan have some thoughts on future work on the gRPC stats. Perhaps they have some thoughts here.

It depends on how you define the "success".
gRPC always use 200 as response code, and its status is encoded in grpc-status header, a "0" value means the rpc is success and others are failure.
In that sense, the stats is correct.
However, if you want to count FailedPrecondition as success when calculating SR, you have to do that by yourself. It's not feasible, as today, we only record either success or failure.
I'm going to create a PR to add additional stats for each gRPC status code, thus you can use them calculate the SR which meets your business logic.

@richunger yeah it's a little unclear to me how FailedPrecondition is not an app error here so it does seem to me like the stats are correct for gross success/fail. In any case, as @fengli79 says we will soon have per code stats like we do for HTTP so can do custom stuff as needed.

Yeah, per-code stats seem like the best path overall.
IMHO FailedPrecondition is a client error (the moral equivalent of an HTTP 400), and not a failure of the service being measured.

@richunger I agree with you that from app perspective, it's an error. From sever perspective, it's not. Let's get the per code stats in place then we can figure out how to change our internal alarms to be better.

@richunger calling this fixed via https://github.com/lyft/envoy/issues/1125. Will get deployed next week. We can discuss alarm/graph changes internally.


Album photos cannot be zoomed

If you take a photo from the album you cannot zoom it. Even if you zoom in you do not get the photo in the selected size.

Great test @confile.
I added this improvement to our Todo list.


Support for FreeCAD

What is needed for this project to generate BOMs from FreeCAD ?

This project is specialized for electronics PCB bom. FreeCAD and 3d modeling is a completely different category.
I have no idea what a BOM for a 3d model even is. Listing of components for an assembly? Either way, this project is not for that.


MFA Code Invalid

Describe the bug
Whenever I solve a captcha, it says the MFA code is invalid or expired. I double checked that the totp was set correctly; I can login perfectly fine using the same totp token on my phone.
Screenshots or Logs
epicgames-freegames_1  | [2021-03-04 18:38:13.736 -0500] INFO  (45 on a2a43dab41d3): Checking free games for <EMAIL>
epicgames-freegames_1  | [2021-03-04 18:38:18.951 -0500] INFO  (45 on a2a43dab41d3): Action requested. Waiting for Captcha to be solved
epicgames-freegames_1  |     user: "<EMAIL>"
epicgames-freegames_1  |     id: "6d0a4b65-1bac-4b4e-b5c2-b0230ec1747c"
epicgames-freegames_1  | [2021-03-04 18:38:31.365 -0500] INFO  (45 on a2a43dab41d3): Action requested. Waiting for Captcha to be solved
epicgames-freegames_1  |     user: "<EMAIL>"
epicgames-freegames_1  |     id: "91b313ae-665e-40fe-af58-11702552f407"
epicgames-freegames_1  | [2021-03-04 18:38:46.029 -0500] ERROR (45 on a2a43dab41d3):
epicgames-freegames_1  |     errorCode: "errors.com.epicgames.accountportal.mfa_code_invalid"
epicgames-freegames_1  |     message: "The security code is invalid or expired."
epicgames-freegames_1  |     metadata: {}
epicgames-freegames_1  |     correlationId: "c31f8b30-7d42-11eb-8d41-1ffbe012b43e"
epicgames-freegames_1  | [2021-03-04 18:38:46.029 -0500] ERROR (HTTPError/45 on a2a43dab41d3): Response code 400 (Bad Request)
epicgames-freegames_1  |     HTTPError: Response code 400 (Bad Request)
epicgames-freegames_1  |         at PromisableRequest.<anonymous> (/usr/app/node_modules/got/dist/source/as-promise/index.js:124:28)
epicgames-freegames_1  |         at processTicksAndRejections (internal/process/task_queues.js:97:5)

Configuration (please complete the following information):

Browser: Windows 10 Firefox 86.0 (64-bit)
Hosting solution [e.g. reverse proxy, HTTPS/HTTP, caching, localhost]: HTTPS Reverse proxy + Docker

I just activated TOTP on a test account was able to login with this project. Just wanted to make sure Epic Games didn't change anything on their side to break it.
Your TOTP secret should be a 52 character Base32 string. Mine looks like this: KI2EUTKZLFHUWSKPJBEVIUKGGNMUSVJVJA3VANBUKZCVQRZUGVJA. (it's deactivated don't worry)
I was able to just copy it directly from the screen on Epic's prompt, no conversion required.
Can you check if your TOTP secret is 52 characters?

I just checked and mine is 54 characters, no clue why. It looks identical to your TOPT secret (its definitely Base32), but has an extra 2 characters. It has been working for a while on an older version but I can't remember which one.
This is my old TOTP secret:
JZLUOWCDGVCUONZWIFDUQNKIK5JVMURWKJLDMNSEIJMUMV2ZJBKQ (I deactivated it)
I deactivated and reactivated my 2FA and I got a 52 character string instead.
Maybe Epic changed their 2FA recently? I'm not sure,

It works perfectly with this new TOTP. No clue what the issue was before.
Thank you for your help.