ng update - Migration failed: Unexpected token '', "{   "nam"... is not valid JSON

Command
update
Is this a regression?

[x] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
Unsure
Description
ng update @angular/core fails from v17.0.8 to latest
Minimal Reproduction
Attempt ng update @angular/core from a project on 17.0.8
Exception or Error
with the message:

Using package manager: npm
Collecting installed dependencies...
Found 126 dependencies.
Fetching dependency metadata from registry...
× Migration failed: Unexpected token '', "{
  "nam"... is not valid JSON
  See "C:\Users\danin\AppData\Local\Temp\ng-ckaJxh\angular-errors.log" for further details.

From log file:
[error] SyntaxError: Unexpected token '', "{
  "nam"... is not valid JSON
    at JSON.parse (<anonymous>)
    at _buildPackageInfo (C:\Users\danin\AppData\Roaming\fnm\node-versions\v20.9.0\installation\node_modules\@angular\cli\src\commands\update\schematic\index.js:429:30)
    at C:\Users\danin\AppData\Roaming\fnm\node-versions\v20.9.0\installation\node_modules\@angular\cli\src\commands\update\schematic\index.js:708:53
    at Map.forEach (<anonymous>)
    at C:\Users\danin\AppData\Roaming\fnm\node-versions\v20.9.0\installation\node_modules\@angular\cli\src\commands\update\schematic\index.js:707:27
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async callRuleAsync (C:\Users\danin\AppData\Roaming\fnm\node-versions\v20.9.0\installation\node_modules\@angular\cli\node_modules\@angular-devkit\schematics\src\rules\call.js:77:18)

Your Environment
CLI: 17.1.2
Node: 20.9.0
Package Manager: npm 10.1.0
OS: win32 x64

Angular: 17.0.8
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, router, upgrade

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1701.2 (cli-only)
@angular-devkit/core         17.1.2 (cli-only)
@angular-devkit/schematics   17.1.2 (cli-only)
@ngtools/webpack             17.0.9
@schematics/angular          17.1.2 (cli-only)
rxjs                         7.8.1
typescript                   5.2.2
webpack                      5.89.0
zone.js                      0.14.2

Anything else relevant?
The first time I ran the command it seemed to start working. It updated the package.json and logged installing dependencies. I aborted the process with HOST + C. I thought that had potentially partially installed files and quit writing midstream. That would explain the "nam" is not valid JSON message. However, I get the exact same error on two different machines.

The @angular/* packages should all come from the NPM registry. We do have XLTS as well for legacy AngularJS. It's a hybrid app.
I created a very simple angular.json manually, so I imagine that has something to do with it. On the other hand, generators and test work fine.
{
  "$schema"<EMAIL_ADDRESS>  "version": 1,
  "newProjectRoot": "projects",
  "projects": {
    "AppNgx": {
      "projectType": "application",
      "schematics": {
        "@schematics/angular:component": {
          "style": "scss"
        }
      },
      "root": "",
      "sourceRoot": "./AppNgx",
      "prefix": "kno2",
      "architect": {
        "test": {
          "builder": "@angular-devkit/build-angular:jest",
          "options": {
            "polyfills": [
              "zone.js",
              "zone.js/testing"
            ],
            "tsConfig": "tsconfig.spec.json"
          }
        }
      }
    }
  }
}

# .npmrc
@xlts.dev:registry=https://registry.xlts.dev/
//registry.xlts.dev/:_authToken=${XLTS_TOKEN}
//registry.xlts.dev/:always-auth=true
//registry.npmjs.org/:_authToken=${NPM_TOKEN}

{
  "name": "kno2fy-web",
  "description": "kno2fy.client",
  "readme": "../readme.md",
  "version": "1.0.0",
  "author": "Kno2, LLC",
  "license": "UNLICENSED",
  "private": true,
  "repository": {
    "type": "git",
    "url": "https://github.com/Kno2/kno2fy-web.git"
  },
  "scripts": {
    "start": "npm run start:web",
    "start:ngrok": "start powershell -c ngrok start auth0 && npm run start:web",
    "start:web": "webpack-dev-server --env IS_LOCAL=true --progress --color",
    "build": "webpack --env IS_LOCAL=true --progress --color",
    "build:ci": "webpack",
    "test": "ng test",
    "test:ng1": "karma start ./app/config/karma.conf.js --single-run",
    "test:ng1:ci": "karma start ./app/config/karma.conf.js --reporters junit --single-run --colors false",
    "test:ng1:w": "karma start ./app/config/karma.conf.js"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "^17.0.8",
    "@angular/compiler-cli": "^17.0.8",
    "@babel/core": "^7.23.6",
    "@babel/plugin-transform-runtime": "^7.23.6",
    "@babel/preset-env": "^7.23.6",
    "@ngneat/spectator": "^16.0.0",
    "@ngtools/webpack": "^17.0.9",
    "@types/angular": "^1.8.4",
    "@types/angular-ui-router": "^1.1.44",
    "@types/jest": "^29.5.12",
    "@types/lodash": "4.14.177",
    "@types/node": "~12.12.6",
    "angular-mocks": "^1.7.5",
    "autoprefixer": "^8.6.5",
    "babel-loader": "^9.1.3",
    "babel-plugin-angularjs-annotate": "^0.10.0",
    "cheerio": "^1.0.0-rc.1",
    "copy-webpack-plugin": "^11.0.0",
    "css-loader": "^6.8.1",
    "css-minimizer-webpack-plugin": "^5.0.1",
    "debug": "^3.1.0",
    "html-loader": "^4.2.0",
    "html-webpack-plugin": "^5.5.4",
    "imports-loader": "^4.0.1",
    "is-docker": "^1.1.0",
    "jasmine-core": "^3.1.0",
    "jest": "^29.7.0",
    "jest-environment-jsdom": "^29.7.0",
    "karma": "^6.4.2",
    "karma-chrome-launcher": "^3.2.0",
    "karma-jasmine": "^5.1.0",
    "karma-junit-reporter": "^2.0.1",
    "karma-sourcemap-loader": "^0.4.0",
    "karma-spec-reporter": "^0.0.36",
    "karma-webpack": "^5.0.0",
    "karma-xml-reporter": "^0.1.4",
    "mini-css-extract-plugin": "^2.7.6",
    "ng-mocks": "^14.12.1",
    "ngtemplate-loader": "^2.1.0",
    "postcss-loader": "^7.3.3",
    "prettier": "^3.2.4",
    "sass-loader": "^13.3.2",
    "style-loader": "^3.3.3",
    "terser-webpack-plugin": "^5.3.9",
    "typescript": "~5.2.2",
    "webpack": "^5.89.0",
    "webpack-bundle-analyzer": "^4.10.1",
    "webpack-cli": "^5.1.4",
    "webpack-dev-server": "^4.15.1"
  },
  "dependencies": {
    "@angular/animations": "^17.0.8",
    "@angular/common": "^17.0.8",
    "@angular/compiler": "^17.0.8",
    "@angular/core": "^17.0.8",
    "@angular/forms": "^17.0.8",
    "@angular/platform-browser": "^17.0.8",
    "@angular/platform-browser-dynamic": "^17.0.8",
    "@angular/router": "^17.0.8",
    "@angular/upgrade": "^17.0.8",
    "@babel/runtime": "^7.23.6",
    "@kno2/ccdaview": "^1.0.11",
    "@kno2/ngx-pdf-viewer": "^2024.2.0",
    "@microsoft/applicationinsights-web": "^2.6.0",
    "@progress/kendo-theme-bootstrap": "^3.4.2",
    "@progress/kendo-ui": "^2017.1.118",
    "@types/minimatch": "^3.0.5",
    "@uirouter/angularjs": "1.0.30",
    "@uirouter/core": "6.0.8",
    "@webcomponents/custom-elements": "^1.5.0",
    "@webcomponents/shadydom": "^1.9.0",
    "angular": "npm<EMAIL_ADDRESS>    "angular-animate": "npm<EMAIL_ADDRESS>    "angular-auth0": "^3.0.6",
    "angular-bootstrap-toggle": "^0.4.2",
    "angular-cache": "^3.2.4",
    "angular-chart.js": "^1.1.1",
    "angular-chosen-localytics": "^1.9.2",
    "angular-cookies": "npm<EMAIL_ADDRESS>    "angular-filter": "^0.5.17",
    "angular-flot": "~0.0.17",
    "angular-http-batcher": "^1.11.2",
    "angular-loader": "^1.8.3",
    "angular-sanitize": "npm<EMAIL_ADDRESS>    "angular-spinner": "^1.0.1",
    "angular-touch": "npm<EMAIL_ADDRESS>    "angular-ui-bootstrap": "https://github.com/kno2/bootstrap#90340ec325188f0d76ebeeddbba62f702af51cb9",
    "angular-ui-utils": "https://github.com/kno2/ui-utils#3f4fc0754a2067079fcf8c3dfbec0ffac76dbdf1",
    "angulartics": "^1.6.0",
    "angulartics-google-tag-manager": "^0.0.1",
    "auth0-js": "^9.23.3",
    "bootstrap": "^4.5.0",
    "bootstrap-chosen": "https://github.com/kno2/bootstrap-chosen#bd187f9eb77eb191b7437a99132229398dae6ce8",
    "chart.js": "^2.9.4",
    "chart.piecelabel.js": "^0.11.0",
    "clipboard": "^1.7.1",
    "components-font-awesome": "^4.7.0",
    "core-js": "^3.22.7",
    "daterangepicker": "^3.0.3",
    "dom-autoscroller": "^2.3.3",
    "dompurify": "^2.0.17",
    "dragula": "^3.7.2",
    "file-saver": "1.3.3",
    "Flot": "https://github.com/flot/flot#v0.8.3",
    "flot-aggregate": "https://github.com/kno2/flot-aggregate#16a36666a1af40944f35595bc92eac00b73010b6",
    "iscroll": "5.2.0",
    "jquery": "^3.5.1",
    "jquery-sparkline": "^2.4.0",
    "jquery-validation": "^1.19.5",
    "ladda": "^1.0.0",
    "launchdarkly-js-client-sdk": "^3.1.4",
    "lodash": "^4.17.21",
    "lodash-es": "^4.17.15",
    "moment": "^2.29.4",
    "ng-file-upload": "~9.1.2",
    "ng-idle": "^1.3.2",
    "ng-infinite-scroll": "^1.3.0",
    "ng-iscroll": "https://github.com/kno2/ng-iScroll#e22356fae88af1481f1f8e6531006add0ac524bc",
    "ng-tags-input": "^3.1.1",
    "ngclipboard": "^1.1.1",
    "ngx-bootstrap": "^12.0.0",
    "ngx-file-drop": "^16.0.0",
    "node-sass": "^9.0.0",
    "noty": "^2.4.0",
    "pdfjs-dist": "2.5.207",
    "pnotify": "3.2.0",
    "popper.js": "^1.14.6",
    "rxjs": "^7.8.1",
    "signalr": "^2.2.1",
    "socket.io-client": "^2.5.0",
    "ua-parser-js": "^0.7.36",
    "url-polyfill": "^1.0.13",
    "web-streams-polyfill": "^2.1.1",
    "zone.js": "~0.14.2"
  }
}


remove Python 3.8

Seeing that dependency resolution for older pytables versions is giving us headaches and 3.8 is now officially EOL, I think it is good to drop support in the next release. Also dropping 3.9 would resolve all pytables related issues (for now). Moreover, all NumFocus projects that we rely on have dropped 3.9 support in the latest versions.
But I have a feeling that @esarradj would like too keep it :wink:
~I've added support for 3.13 because I don't see any reason not to.~
I see the reason now ...

Don't keep 3.9 for me ...
If there is a good reason (and the dependencies dropping 3.9 support is) then we can surely drop it. Who requires 3.9 can still use older Acoular versions.


Command to download actual mirrrors for mirrors.txt

curl  https://www.torproject.org/getinvolved/mirrors.html.en -o mirror1.html  &&  cat mirror1.html | grep ' mirrors.txt
*it only create a file with https:// links
if you have a better idea for the command.....

curl https://www.torproject.org/getinvolved/mirrors.html.en -o mirror1.html && cat mirror1.html | grep ' mirrors.txt
I modify it in this  part grep -Eo "(https)://[a-zA-Z0-9./?=_-]*/dist"

I think trying to make torbrowser-launcher automatically download the list of mirrors probably isn't worth it, especially since a main reason to use a mirror is because torproject.org is being censored, so it likely wouldn't work anyway. I think just shipping updated lists of mirrors with torbrowser-launcher is a better plan.
Also, torproject.org could change the web design of that page at any moment and break things (in fact, I know they're about to launch a new design). But that said, cool command :).


Make the format strings compatible with Python 2.6

This should restore compatibility with Python 2.6, current version fails with:
Traceback (most recent call last):
...
  File "/usr/lib/python2.6/site-packages/prometheus_client-0.5.0-py2.6.egg/prometheus_client/exposition.py", line 194, in write_to_textfile
    f.write(generate_latest(registry))
  File "/usr/lib/python2.6/site-packages/prometheus_client-0.5.0-py2.6.egg/prometheus_client/exposition.py", line 119, in generate_latest
    output.append(sample_line(s))
  File "/usr/lib/python2.6/site-packages/prometheus_client-0.5.0-py2.6.egg/prometheus_client/exposition.py", line 86, in sample_line
    s.name, labelstr, floatToGoString(s.value), timestamp)
  File "/usr/lib/python2.6/site-packages/prometheus_client-0.5.0-py2.6.egg/prometheus_client/utils.py", line 21, in floatToGoString
    mantissa = '{}.{}{}'.format(s[0], s[1:dot], s[dot+1:]).rstrip('0.')
ValueError: zero length field name in format

Can you add the DCO?

Done.

The tests are failing on 2.6, are you sure this is broken?

Looking into the tests failing.

So, I think I figured things out. The tests fail in Python 2.6 because of this line.
The test tests that all those values generate ValueErrors. This passes in Python 2.7 because floatToGoString('1.5555555555555201e+06') is '1.55555555555552e+06' -- see this line.
In Python 2.6, without my changes, the test passes because this line, coincidentally, throws ValueError (because 2.6 requires numbers for placeholders).

The difference in the result of floatToGoString is that in 2.6 repr(1.5555555555555201e+06) is '1555555.5555555201' and in 2.7 it is '1555555.55555552'.
Obviously I don't know why this specific value was chosen for this test, but maybe we should remove it? What do you think @brian-brazil?

Odd that CI let this though.

Obviously I don't know why this specific value was chosen for this test, but maybe we should remove it?

It's there specifically to catch this. This sounds like https://bugs.python.org/issue7117 or https://bugs.python.org/issue7632

Odd that CI let this though.

This passed in CI for 2.6 because the only test path exercising this code happens to be in a test that expects ValueError.
I pushed a change that makes floatToGoString work the same for the existing test cases in 2.6 and 2.7.

We should still fix the format bug on 2.6

So what do you want to do about the test failing on 2.6?

Can skip the test on 2.6 only with a message referencing the floating point formatting compatibility issue.

Thanks!


0.5.2 + 0.5.3 noop version can not be downloaded

releaseCompile(group: "at.favre.lib.hood", name: "hood-core", version: "0.5.2", classifier: "noop", ext: "aar", transitive: true)
does not work:
Gradle sync failed: Could not find hood-core-noop.aar (at.favre.lib.hood:hood-core:0.5.2).
Searched in the following locations:
https://jcenter.bintray.com/at/favre/lib/hood/hood-core/0.5.2/hood-core-0.5.2-noop.aar
Consult IDE log for more details (Help | Show Log)

These are all on bintray, but I will see what the problem is.

So this seems to be an syncing issue from bintray to jcenter (since merge 2 repos, it seems hood-core will not be synced).
See
https://jcenter.bintray.com/at/favre/lib/hood/hood-core/
vs.
https://jcenter.bintray.com/at/favre/lib/hood/hood-extended/
I'm in contact with the support team and I hope they can relink it.
In the meanwhile you could use the private repo
repositories {
maven {
url  "https://dl.bintray.com/patrickfav/maven"
}
}
or use maven central (but noop seems to not be synced)
https://repo.maven.apache.org/maven2/at/favre/lib/hood/hood-core/
https://repo.maven.apache.org/maven2/at/favre/lib/hood/hood-extended/

So problem should be resolved, needed direct contact to JFrog's twitter to get someboday to fix it.
Please report back if you have any more issues


Gulp build suite

I figured the project could benefit from a modern & extensible build suite. Gulp is almost the de facto  build system for web these days, so that is what I used. It will help people new to the project get up-and-running as the configuration for the build tools are already completed - it now takes only two commands to have Legacy build from source (assuming you have node installed). Most open source web projects provide a similar build system. It also makes build setup very easy and should significantly speed up testing and modification of the source as all changes are immediately compiled and rendered in connected local browsers.
I've included an npm package for built tool dependencies, and configured gulp to process Legacy's sass, auto-prefix and minify the source, and inject it into all connected browsers via browsersync. I have also updated the readme to reflect the new tools.
Hit me up on the slack channel if you have any questions/suggestions!

Before I merge this, could you give me a demo? Would like to see exactly what it does.

@georgejenkins @nloveladyallen
==
As soon as someone demos this to me, I'll merge it.

@joexn The next commit will have some improvements, so don't merge yet.
@georgejenkins Can you push the latest commit?


Add Gradle 8 support

The most important this isn't the example app update but rather plugin's config. Without this change, dependent projects can't migrate to AGP 8.
Example app was updated automatically 😇


chore: ban Instant::now via semgrep

is this getting ignored somehow?
fm (97d1200) rg -w 'Instant' fedimint-core

fedimint-core/src/task.rs
9:use std::time::{Duration, Instant};
399:    pub async fn sleep_until(deadline: Instant) {
449:    pub async fn sleep_until(deadline: Instant) {
450:        sleep(deadline.saturating_duration_since(Instant::now())).await

fedimint-core/src/task.rs

#[cfg(not(target_family = "wasm"))]
mod imp {

#[cfg(target_family = "wasm")]
mod imp {

Maybe due to this? BTW. How does it work? I thought Instant doesn't work in wasm ... so why is it in conditional compilation for ... wasm?
Oh well. We'll take what we can.


Accept APXSFLAGS argument to apxs

We need to be able to pass in some extra flags to the APXS compile line (namely -Wc,-fno-strict-aliasing).  This allows that.

Thank you, merged.


Remove output env variable for log output method

Description
Please include a summary of the change, motivation and context.

Testing
Please describe the tests that you ran to verify your changes. Please summarize what did you test and what needs to be tested e.g. deployed and tested helm chart locally.
Checklist:

[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] Any dependent changes have been merged and published in downstream modules

Documentation
Make sure that you have documented corresponding changes in this repository or hypertrace docs repo if required.

please merge the pr


fix: revert and optimize showHover action behavior

Background
The behavior of the editor.action.showHover action in vscode was changed in version 1.73.0 (https://github.com/microsoft/vscode/pull/176057). Previously, it would show a hover, but now it only shows the hover if it is not already visible, and focuses on it if it is visible.
However, this change has caused issues for some third-party extensions, particularly translation plugins. These plugins rely on user text selection and use the editor.action.showHover action to display translation results in a hover.
Unfortunately, the new behavior introduced in vscode version 1.73.0 causes the editor to lose focus when subsequent showHover actions are triggered, preventing users from deleting or editing code and negatively impacting the user experience.
Related issues: https://github.com/microsoft/vscode/issues/176640, https://github.com/intellism/vscode-comment-translate/issues/181
The known affected extensions include:

Extension
Installs
Affected code

Comment Translate
265K
select.ts#L63

Translator Helper
8K
selection.ts#L52

What's this PR
This PR reverts the default behavior of the showHover action to its pre-1.73.0 state to solve the following issues:

fixes https://github.com/microsoft/vscode/issues/196890
closes https://github.com/microsoft/vscode/issues/176640

Additionally, it introduces a new parameter called focusOnVisible, which allows users to configure whether the hover should be focused. This change does not affect the original functionality of scrolling up and down the editor hover widget, as discussed in https://github.com/microsoft/vscode/issues/69836.
To use the keybindings cmd+k cmd+i for focusing the hover, you can define settings in the keybindings.json file to specify whether the hover should automatically receive focus when triggered by the keyboard. By default, this setting is false. Here is an example:
// keybindings.json
[
  {
    "key": "cmd+k cmd+i",
    "command": "editor.action.showHover",
    "args": {
      "focus": true, // Specifies whether the hover should immediately receive focus when triggered with the keyboard.
      "focusOnVisible": true // Specifies whether the hover should receive focus when it is already visible.
    },
    "when": "editorTextFocus"
  }
]

@idootop please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

cc: @aiday-mar @alexdima  Thanks ;)

Hi @aeschli, what do you think about this proposal?

After looking at the PR, I find the text descriptions confusing with the new option. Perhaps instead of introducing a new option we could add a new state to the existing option focus. Currently it is a boolean, but it could take one of three string values:
immediately -> when hover appears it will focus immediately
never -> the hover is never focused, even if already visible
ifVisible -> the hover is focused only if it already visible
In your case you would set the value of never on calling showHover.
What do you think @aeschli @alexdima ?

Hi @idootop, apologies for the delay in answering and thanks for the work so far. I discussed with the team and we think it would be a good change to indeed use the enum with the three possible states immediately, never and ifVisible. Feel free to implement this and we can merge the PR.

Hi @aiday-mar, thanks for the update. I agree, using the enum with the three states sounds like a good solution. I'll make sure to implement this later. Thanks again for your help!

Hi @aiday-mar,
I have completed the implementation of the enum with the three possible states (immediately, never, and ifVisible) as per our discussion. I have also thoroughly tested all the options to ensure everything works as expected. Could you please review the changes at your earliest convenience?
Thanks ;)

Hey @idootop, I looked at the PR and pushed some code to polish the PR. More specifically I extracted an enum and removed the surfacing of the boolean option in the enum (but kept a check in the run method).
@aeschli Do you think you could give a second review to the PR? Thank you.


ES-122 set chart version to 5.0.0

Set our Corda chart version to 5.0.0 prior to GA we currently override this dynamically when building releases.

Downstream consumers also to be updated (associated PRs to follow which will be linked here)

ENT PR:
https://github.com/corda/corda5-enterprise/pull/42
Shared lib:
https://github.com/corda/corda-shared-build-pipeline-steps/pull/729

@davidcurrie flagging for visibility, but I will get a PR for enterprise and any other dependencies lined up and linked in the description with appropriate comms / docs updates before undrafted.

Opening for review but this doc and email comms to be sent before merge


Cannot remove the first parent operator

Blocked by #840
Describe the Bug:
There is no button to remove the first parent operator:

If you change the radio box to "no", it doesn't remove the first parent operator
Probability (how likely the bug is to happen, scored from 1-5):
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5):
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Screenshots:
Additional information:

OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional context

Just kidding, radio button works


using root saga or multiple sagas

Hi. I'm new to redux-saga and cannot figure this out:
The documentations says that an array of sagas can be passed to createSagaMiddleware.
But all the examples are using composition of saga into a root saga.
Is there a difference between the to ways, or is createSagaMiddleware with multiple sagas just a syntactic sugar over the root saga pattern?

I think there's not much difference.
The only difference I can see right now is probably related to error/cancellation propagation, but I think it has not been implemented properly yet. Probably that starting sagas as an array instead of forks isolates them better?

the middleware support for passing multiple sagas is a just a convenience. If you need to control top Sagas (like cancelling them) you should use a single root Saga. You can't do this with the createSagaMiddleware(..topSagas) because you can't get a reference to the forked tasks.

@yelouafi I know this is an old issue, just wanted to clarify: using .run actually mitigates this issue, as it allows us to get a reference to each run task. Is there any downside to this? We're using this in our codebase to dynamically register sagas across multiple code-split chunks and still be able to wait for them when rendering on the server-side and I haven't come across any issues yet.

Redux Saga uses the all function in the recent version (0.15.3) where you can combine multiple sagas to one root saga for the Redux store.
import { takeEvery, all } from 'redux-saga/effects';

...

function *watchAll() {
  yield all([
    takeEvery("FRIEND_FETCH_REQUESTED", fetchFriends),
    takeEvery("CREATE_USER_REQUESTED", createUser)
  ]);
}

Is it ok to do this?
// foo.js
export function *fooSagas() {
  yield all([
    takeEvery("FOO_A", fooASaga),
    takeEvery("FOO_B", fooBSaga),
  ]);
}

// bar.js
export function *barSagas() {
  yield all([
    takeEvery("BAR_A", barASaga),
    takeEvery("BAR_B", barBSaga),
  ]);
}

// index.js
import { fooSagas } from './foo';
import { barSagas } from './bar';

export default function* rootSaga() {
  yield all([
    fooSagas,
    barSagas
  ])
}

Is there any downsides on doing that? I like to use takeEvery (I think it's more idiomatic than hand-writing the infinite loop, and it's faster to test the actual forked saga), but I don't konw if I should compose them that way.

Its just fine, the only downside (but rly a minor) is slightly more memory used up. I'll explain this only for completeness ;)
Each saga - what u pass to the sagaMiddleware.run/runSaga and every generator passed into the call, apply, fork, spawn, all, race effects is internally becoming a Task. So if u add another layer of the generators in between they all get instances internally etc.
And as every effect is just an object you can actually export them instead of the generators.
So slightly more performant would be to:
// foo.js
export const fooSagas = [
  takeEvery("FOO_A", fooASaga),
  takeEvery("FOO_B", fooBSaga),
]

// bar.js
export const barSagas() = [
  takeEvery("BAR_A", barASaga),
  takeEvery("BAR_B", barBSaga),
];

// index.js
import { fooSagas } from './foo';
import { barSagas } from './bar';

export default function* rootSaga() {
  yield all([
    ...fooSagas,
    ...barSagas
  ])
}

But you know how it is... dont optimize prematurely ! :)

@Andarist,
Thank you so much for the explanation, it all makes more sense now. 👍

@Andarist
Thank you for the answer.
There is an all function in this code snippet.
But it seems there is no function called all in the redux-saga export:
import {all} from 'redux-saga'

throws the error:
"export 'all' was not found in 'redux-saga'

How to combine sagas correctly?

all is an effect therefore it should be exported by redux-saga/effects

@Andarist
Thank you!
I've found correct import path right after I posted a question here.
Sorry for worrying you.

@Andarist thank you very much. We will follow this pattern in our projects :)

@Andarist, i use like u say, but have warning:
[...effects] has been deprecated in favor of all([...effects]), please update your code

@Dictory the warning is probably from some other part of your code, just setup a breakpoint on the console.log's line, stop there and see what has caused it in the stack trace

@Andarist could u answer please, what a difference between a
export default function* rootSaga() {     yield [         fork(fooSagas),         fork(booSagas),     ]; }
and
export default function* rootSaga() {   yield all([     fooSagas,     booSagas,   ]) }
What should I prefer to use?

@SmirnovW it depends what fooSagas and booSagas are, if they are the same thing in both examples then your second example probably is not working at all. First snippet should work, but yielding arrays directly is deprecated at the moment and the array should be wrapped in all effect.

@Andarist yes, this is the same things, and of course, the second example should be with called functions :)

In that case its just a matter of passing effects and non-effects (promises and iterators) to the redux-saga. While it is capable of handling those, the preferred way is to wrap them in effects (thus delaying their execution)

@Andarist . Hi, I have a question.
export default function* rootSaga() {
  yield all([
    fooSagas,
    booSagas,
  ])
}

As the document said.  booSagas will be abort if fooSagas throw an error and vice versa. it would be better if we use
export default function* rootSaga() {
  yield all([
   spaw(fooSagas),
   spaw(booSagas),
  ])
}

Right?

@dfee as mentioned - it depends on what fooSagas are, all accept any effects (+ promises/awaitables and iterators), if fooSagas is a factory which returns an effect then yes - it has to be called

@Andarist Hello, great feedback. I am working on a project with multiple:
export default function* rootSaga(): * {
    yield all(...

And i get copies of the same saga, resulting in the same saga being called multiple times. Any suggestions on how to avoid this? I believe they added a rootSaga per page (some sagas are common over multiple plages). But is it a good practice to have a rootSaga containing all sagas in the project, even if they never get used?
Thank you.

Ideally you wouldnt have to do that, i think its a viable approach to call sagaMiddleware.run multiple times in your app. This allows you to prepare a good code-splitting architecture, but how to do that in your app is up to you.

@Andarist Thank you! But in the case of calling sagaMiddleware.run multiple times in the app, how do i avoid duplicates. Is there a way to check already registered sagas?

You shouldnt call this with the same set of sagas - you should just be able to start new sagas by using this. How you organize the whole thing is up to you though.

Its just fine, the only downside (but rly a minor) is slightly more memory used up. I'll explain this only for completeness ;)
Each saga - what u pass to the sagaMiddleware.run/runSaga and every generator passed into the call, apply, fork, spawn, all, race effects is internally becoming a Task. So if u add another layer of the generators in between they all get instances internally etc.
And as every effect is just an object you can actually export them instead of the generators.
So slightly more performant would be to:
// foo.js
export const fooSagas = [
  takeEvery("FOO_A", fooASaga),
  takeEvery("FOO_B", fooBSaga),
]

// bar.js
export const barSagas = [
  takeEvery("BAR_A", barASaga),
  takeEvery("BAR_B", barBSaga),
];

// index.js
import { fooSagas } from './foo';
import { barSagas } from './bar';

export default function* rootSaga() {
  yield all([
    ...fooSagas,
    ...barSagas
  ])
}

But you know how it is... dont optimize prematurely ! :)

@Andarist With this approach if any saga fails will it kill the root saga or the other sagas as mentioned in this comment
https://github.com/redux-saga/redux-saga/issues/760#issuecomment-273737022.


Release into Foxy

https://build.ros2.org/job/Fbin_uF64__turtlebot3_gazebo__ubuntu_focal_amd64__binary/ builds are also failing

Hi @SteveMacenski
Thank you for the kind ping.
I'll look into it and rectify the simulation package.
This will be included in the February release next week.

Thanks! We've had a bunch of users run into this as they try to use the getting started / build instructions for TB3 and Nav2.

Updates had been merged and successfully built as a binary package for Foxy.
https://github.com/ros/rosdistro/pull/28404
Thanks!

Awesome thanks!


Language

Tell me how to change the default language?
Or how to change the name of a specific text

I don't think thats currently possible without forking the package/plugin in question. However we have a similar use case, so perhaps a better question is whether an internationalization support PR would be accepted. Perhaps the in form of a locale option which is a Map from translation key to string


NVS initialisation error while running ble_compatibility_test on stable (v4.2.2) (IDFGH-8399)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
v4.4.2
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
No response
Development Kit.
Custom Board
Power Supply used.
External 3.3V
What is the expected behavior?
Test runs without error
What is the actual behavior?
Error logged
Steps to reproduce.
Install esp-idf v4.2.2
idf.py set-target esp32
idf.py -p /dev/ttyUSB0 flash monitor

Debug Logs.
vbox@vbox:~/esp/esp-idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test$ idf.py -p /dev/ttyUSB0 flash monitor
Executing action: flash
Running ninja in directory /home/vbox/esp/esp-idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test/build
Executing "ninja flash"...
[1/5] cd /home/vbox/esp/esp-idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test/build/esp-idf/esptool_py && /home/vbox/.espressi...able/partition-table.bin /home/vbox/esp/esp-idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test/build/ble_compatibility_test.bin
ble_compatibility_test.bin binary size 0xa8c10 bytes. Smallest app partition is 0x100000 bytes. 0x573f0 bytes (34%) free.
[2/5] Performing build step for 'bootloader'
[1/1] cd /home/vbox/esp/esp-idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test/build/bootloader/esp-idf/esptool_py && /home/vbox/.espressif/python_env/idf4.4_py3.10_env/bin/python /home/vbox/esp/esp-idf/components/partition_table/check_sizes.py --offset 0x8000 bootloader 0x1000 /home/vbox/esp/esp-idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test/build/bootloader/bootloader.bin
Bootloader binary size 0x6330 bytes. 0xcd0 bytes (11%) free.
[2/3] cd /home/vbox/esp/esp-idf/components/esptool_py && /usr/bin/cmake -D IDF_PATH="/home/vbox/esp/esp-idf" -D SERIAL_TOOL="/home/vbox/...idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test/build" -P /home/vbox/esp/esp-idf/components/esptool_py/run_serial_tool.cmake
esptool.py esp32 -p /dev/ttyUSB0 -b 460800 --before=default_reset --after=hard_reset write_flash --flash_mode dio --flash_freq 40m --flash_size 2MB 0x1000 bootloader/bootloader.bin 0x10000 ble_compatibility_test.bin 0x8000 partition_table/partition-table.bin
esptool.py v3.3.2-dev
Serial port /dev/ttyUSB0
Connecting....
Chip is ESP32-D0WDR2-V3-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 44:17:93:ba:b7:80
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 460800
Changed.
Configuring flash size...
Flash will be erased from 0x00001000 to 0x00007fff...
Flash will be erased from 0x00010000 to 0x000b8fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Compressed 25392 bytes to 15884...
Writing at 0x00001000... (100 %)
Wrote 25392 bytes (15884 compressed) at 0x00001000 in 0.8 seconds (effective 249.1 kbit/s)...
Hash of data verified.
Compressed 691216 bytes to 410590...
Writing at 0x00010000... (3 %)
Writing at 0x0001d996... (7 %)
Writing at 0x0002962d... (11 %)
Writing at 0x000332d8... (15 %)
Writing at 0x00038d42... (19 %)
Writing at 0x0003e8bb... (23 %)
Writing at 0x00044293... (26 %)
Writing at 0x00049bf9... (30 %)
Writing at 0x0004f333... (34 %)
Writing at 0x00055814... (38 %)
Writing at 0x0005b7fa... (42 %)
Writing at 0x000617b1... (46 %)
Writing at 0x00067421... (50 %)
Writing at 0x0006d171... (53 %)
Writing at 0x000730ae... (57 %)
Writing at 0x0007938f... (61 %)
Writing at 0x0007f390... (65 %)
Writing at 0x00084ef6... (69 %)
Writing at 0x0008a971... (73 %)
Writing at 0x00090ef0... (76 %)
Writing at 0x00098f48... (80 %)
Writing at 0x000a1662... (84 %)
Writing at 0x000a7166... (88 %)
Writing at 0x000ace05... (92 %)
Writing at 0x000b260c... (96 %)
Writing at 0x000b851f... (100 %)
Wrote 691216 bytes (410590 compressed) at 0x00010000 in 10.0 seconds (effective 552.7 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 103...
Writing at 0x00008000... (100 %)
Wrote 3072 bytes (103 compressed) at 0x00008000 in 0.1 seconds (effective 320.7 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...
Executing action: monitor
Running idf_monitor in directory /home/vbox/esp/esp-idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test
Executing "/home/vbox/.espressif/python_env/idf4.4_py3.10_env/bin/python /home/vbox/esp/esp-idf/tools/idf_monitor.py -p /dev/ttyUSB0 -b 115200 --toolchain-prefix xtensa-esp32-elf- --target esp32 --revision 0 /home/vbox/esp/esp-idf/examples/bluetooth/bluedroid/ble/ble_compatibility_test/build/ble_compatibility_test.elf -m '/home/vbox/.espressif/python_env/idf4.4_py3.10_env/bin/python' '/home/vbox/esp/esp-idf/tools/idf.py' '-p' '/dev/ttyUSB0'"...
--- idf_monitor on /dev/ttyUSB0 115200 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 153911750, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,�ets Jul 29 2019 12:21:46

rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 153911750, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:6660
load:0x40078000,len:14848
ho 0 tail 12 room 4
load:0x40080400,len:3792
0x40080400: _init at ??:?

entry 0x40080694
I (30) boot: ESP-IDF v4.4.2 2nd stage bootloader
I (30) boot: compile time 11:21:39
I (30) boot: chip revision: 3
I (33) boot_comm: chip revision: 3, min. bootloader chip revision: 0
I (40) boot.esp32: SPI Speed      : 40MHz
I (44) boot.esp32: SPI Mode       : DIO
I (49) boot.esp32: SPI Flash Size : 2MB
I (53) boot: Enabling RNG early entropy source...
I (59) boot: Partition Table:
I (62) boot: ## Label            Usage          Type ST Offset   Length
I (70) boot:  0 nvs              WiFi data        01 02 00009000 00006000
I (77) boot:  1 phy_init         RF data          01 01 0000f000 00001000
I (85) boot:  2 factory          factory app      00 00 00010000 00100000
I (92) boot: End of partition table
I (96) boot_comm: chip revision: 3, min. application chip revision: 0
I (103) esp_image: segment 0: paddr=00010020 vaddr=3f400020 size=1a9e0h (109024) map
I (151) esp_image: segment 1: paddr=0002aa08 vaddr=3ffbdb60 size=046f0h ( 18160) load
I (159) esp_image: segment 2: paddr=0002f100 vaddr=40080000 size=00f18h (  3864) load
I (161) esp_image: segment 3: paddr=00030020 vaddr=400d0020 size=72c98h (470168) map
I (336) esp_image: segment 4: paddr=000a2cc0 vaddr=40080f18 size=15f14h ( 89876) load
I (373) esp_image: segment 5: paddr=000b8bdc vaddr=50000000 size=00010h (    16) load
I (384) boot: Loaded app from partition at offset 0x10000
I (385) boot: Disabling RNG early entropy source...
I (396) cpu_start: Pro cpu up.
I (396) cpu_start: Starting app cpu, entry point is 0x400811a4
0x400811a4: call_start_cpu1 at /home/vbox/esp/esp-idf/components/esp_system/port/cpu_start.c:160

I (0) cpu_start: App cpu up.
I (413) cpu_start: Pro cpu start user code
I (413) cpu_start: cpu freq: 160000000
I (413) cpu_start: Application information:
I (417) cpu_start: Project name:     ble_compatibility_test
I (423) cpu_start: App version:      v4.4.2
I (428) cpu_start: Compile time:     Sep 27 2022 11:21:32
I (434) cpu_start: ELF file SHA256:  51370288d402ba91...
I (440) cpu_start: ESP-IDF:          v4.4.2
I (446) heap_init: Initializing. RAM available for dynamic allocation:
I (452) heap_init: At 3FFAFF10 len 000000F0 (0 KiB): DRAM
I (459) heap_init: At 3FFB6388 len 00001C78 (7 KiB): DRAM
I (465) heap_init: At 3FFB9A20 len 00004108 (16 KiB): DRAM
I (471) heap_init: At 3FFC66A8 len 00019958 (102 KiB): DRAM
I (477) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (483) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (490) heap_init: At 40096E2C len 000091D4 (36 KiB): IRAM
I (497) spi_flash: detected chip: winbond
I (501) spi_flash: flash io: dio
W (505) spi_flash: Detected size(4096k) larger than the size in the binary image header(2048k). Using the size in the binary image header.
I (519) cpu_start: Starting scheduler on PRO CPU.
I (0) cpu_start: Starting scheduler on APP CPU.
I (1269) BTDM_INIT: BT controller compile version [bf9c077]
I (1269) system_api: Base MAC address is not set
I (1269) system_api: read default base MAC address from EFUSE
I (1279) phy_init: phy_version 4670,719f9f6,Feb 18 2021,17:07:07
E (1289) phy_init: esp_phy_load_cal_data_from_nvs: NVS has not been initialized. Call nvs_flash_init before starting WiFi/BT.
W (1299) phy_init: failed to load RF calibration data (0x1101), falling back to full calibration
E (1729) BT_OSI: config_new: NVS not initialized. Call nvs_flash_init before initializing bluetooth.
W (1729) BT_BTC: btc_config_init unable to load config file; starting unconfigured.

E (1739) BT_OSI: config_save: NVS not initialized. Call nvs_flash_init before initializing bluetooth.
E (1749) BT_OSI: config_save, err_code: 0x2

E (1829) BT_OSI: config_save: NVS not initialized. Call nvs_flash_init before initializing bluetooth.
E (1829) BT_OSI: config_save, err_code: 0x2

E (1839) BT_OSI: config_save: NVS not initialized. Call nvs_flash_init before initializing bluetooth.
E (1849) BT_OSI: config_save, err_code: 0x2

E (1849) BT_OSI: config_save: NVS not initialized. Call nvs_flash_init before initializing bluetooth.
E (1859) BT_OSI: config_save, err_code: 0x2

E (1869) BT_OSI: config_save: NVS not initialized. Call nvs_flash_init before initializing bluetooth.
E (1879) BT_OSI: config_save, err_code: 0x2

I (1899) BLE_COMP: create attribute table successfully, the number handle = 11

I (1909) BLE_COMP: (0) ***** advertising start successfully *****

More Information.
First time using esp-idf so I'm not sure where to begin looking for further debugging. Pointers are welcome
Same error message in https://github.com/espressif/esp-idf/issues/5566 closed with no actionable fix

You can fixed this bug by commenting out line 630 of code in ble_compatibility_test.c.
//ESP_ERROR_CHECK(nvs_flash_erase());
We will fix it ASAP.

Thanks, what's the underlying issue?

If the nvs is initialized, nvs_flash_erase() first de-initializes it. Afterwards, the nvs has to be initialized again to be used.

Cheers, thought it might have been something like that

Thanks for reporting and sharing the updates, feel free to reopen.


Label  own dataset

Hi, please ask How to  annotate own dataset in the same format as Tusimple? I want to test model  on my own dataset

Sorry for being late, tough months about lots of deadlines.
Actually, the question about how to get the same format is hard to give you, maybe you can e-mail the authors of TuSimple to borrow their labeling tools and basic codes.
Here, I can only give you some tips about how we annotate images.
Annotating your image and training
1-1. How to annotate? (Some recommendations)
1). Annotate each lane with keypoints (10 ~ 20 points is ok, you can sparsely label the close part and densely label remote curved part for better performance on remote curved structures).
2). Make sure the occluded part is correctly imaged when you annotate a lane
3). Make sure the heavily occluded lane is labeled as ignored
4). 2) and 3) are important to form consistent shape guidance, which avoids the problem of marker-appearance misalignment brought about by arbitrary markers.
5) 2), 3) and 4) are found based on the fact that we treat each lane as a whole object (like a cat or dog in the object detection field) rather than low-level pixels.
6) Remember and think 5), you will make your mind about the advantages and disadvantages of LSTR.

Sorry for being late, tough months about lots of deadlines.
Actually, the question about how to get the same format is hard to give you, maybe you can e-mail the authors of TuSimple to borrow their labeling tools and basic codes.
Here, I can only give you some tips about how we annotate images.
Annotating your image and training
1-1. How to annotate? (Some recommendations)
1). Annotate each lane with keypoints (10 ~ 20 points is ok, you can sparsely label the close part and densely label remote curved part for better performance on remote curved structures).
2). Make sure the occluded part is correctly imaged when you annotate a lane
3). Make sure the heavily occluded lane is labeled as ignored
4). 2) and 3) are important to form consistent shape guidance, which avoids the problem of marker-appearance misalignment brought about by arbitrary markers.
5) 2), 3) and 4) are found based on the fact that we treat each lane as a whole object (like a cat or dog in the object detection field) rather than low-level pixels.
6) Remember and think 5), you will make your mind about the advantages and disadvantages of LSTR.


Animations Failing on iPad w/o jQuery

Hi,
This: Velocity(element, {left:1000}, 2000);
Produces: TypeError: undefined is not an object (evaluating 'offsetParent.style.position')

SOLVED (but I don't like it...) MUST set left:0 in CSS for element on iOS...
On Chrome (including Android) I do NOT need to set left in the CSS.
However on the iPad it will fail if I do not have: left:0 for that element...
Have no clue what the fix would be... but I love your library :)

What version of iOS? And is the element attached to a DOM when you start the animation?

10 and yes it is visible and attached. Was in the html.
On Sun, Sep 25, 2016, 10:09 AM Rycochet<EMAIL_ADDRESS>wrote:

What version of iOS? And is the element attached to a DOM when you start
the animation?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/julianshapiro/velocity/issues/699#issuecomment-249433400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATnPKAK8yVFGnnzS_L4QKVhgtuZJhugks5qtqrSgaJpZM4KF7hm
.

--
Matt Lockyer
+1-778-686-2625
http://www.mattlockyer.com

That's plain weird - if you can put a quick example on jsfiddle / codepen etc for me to look into (I've got an iOS 10 iPad to test with) then it might be fixable - though tbh I don't know how as jQuery has no effect on anything related to that bit of code afaik...

https://jsfiddle.net/qkzaak99/
will not start on iPad iOS 10

Confirmed on my iPad too - I'll start looking into it when I get a chance - definite browser bug, but should be able to work around it :-)

Found it -
/* setPropertyValue() returns an array of the property name and property value post any normalization that may have been performed. */
/* Note: To solve an IE<=8 positioning bug, the unit type is dropped when setting a property value of 0. */
var adjustedSetData = CSS.setPropertyValue(element, /* SET */
	property,
	tween.currentValue + (parseFloat(currentValue) === 0 ? "" : tween.unitType),
	tween.rootPropertyValue,
	tween.scrollData);

Looks like this is a legacy bit of code that should really be checking if it's IE to do anything anyway...

That... Couldn't have been fun :)
On Sat, Oct 22, 2016, 4:37 AM Rycochet<EMAIL_ADDRESS>wrote:

Found it -
/* setPropertyValue() returns an array of the property name and property value post any normalization that may have been performed. /
/ Note: To solve an IE<=8 positioning bug, the unit type is dropped when setting a property value of 0. /
var adjustedSetData = CSS.setPropertyValue(element, / SET */
property,
tween.currentValue + (parseFloat(currentValue) === 0 ? "" : tween.unitType),
tween.rootPropertyValue,
tween.scrollData);
Looks like this is a legacy bit of code that should really be checking if
it's IE to do anything anyway...
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/julianshapiro/velocity/issues/699#issuecomment-255523376,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AATnPKiwi4Ot08KH6JGfUIC18seqfl99ks5q2fV6gaJpZM4KF7hm
.

--
Matt Lockyer
CEO and Founder - Skayle Software Inc.
+1-778-686-2625
http://www.skayleapps.com

Finally got around to testing this with 1.4.0 - and can confirm it's fixed :-)


Feature/30 search mechanism

Add search functionality on desktop and mobile views

Oh wait, you just merged it...


A callback to next() of beforeRouteEnter executed before mounted()

Version
3.4.6
Reproduction link
no reproduction link
must compile more than once
Steps to reproduce

have beforeRouteEnter and mounted hooks in a component
have next() with callback in beforeRouteEnter
use different version of vue-router before(3.4.5 or other) and after 3.4.6

What is expected?
the order of the executions of callback in next() of beforeRouteEnter and mounted are same in different version of view-router
What is actually happening?
the order of the executions of callback in next() of beforeRouteEnter and mounted are different in different version of view-router

https://new-issue.vuejs.org/?repo=vuejs/vue-router-next#why-repro
the callback passed to next is always executed after mounted: https://router.vuejs.org/guide/advanced/navigation-guards.html#the-full-navigation-resolution-flow

https://new-issue.vuejs.org/?repo=vuejs/vue-router-next#why-repro
the callback passed to next is always executed after mounted: https://router.vuejs.org/guide/advanced/navigation-guards.html#the-full-navigation-resolution-flow

I know, maybe it's more clearly in this way:
In version 3.4.6+, the callback passed to next is executed before mounted.

I can confirm this behavior as @huajianreno described.


HLS Fairplayback

Have you read the Tutorials?
yes
Have you read the FAQ and checked for duplicate open issues?
yes
What version of Shaka Player are you using?
3.2.0
Please ask your question
I am trying to play the content on Mac Safari (HLS Fairplay) but it doesn't play the video.
I have perfectly configured the DRM license URL and apply Fairplay cert in the player configuration but it still doesn't work.
First approach: I manually fetched the server cert and converted it in Uint8Array and passed it in drm.advanced.com\\.apple\\.fps\\.1_0.serverCertificate but it doesn't play the content
The second approach I pass my cert URL directly to serverCertificateUri in drm.advanced but it still doesn't work correctly.
Can you please suggest to me a better approach for playing FairPlay content as these both are confusing?

Duplicate of https://github.com/google/shaka-player/issues/3530


Requirements are broken due to new dependency releases

The repository cannot be installed at the moment probably due to new releases of dependencies. I suspect the issue is that the version of tensorflow_io is not specified and some versioning around the tensorflow-probability library is incorrectly specified somewhere upstream.
This seems to work but the versions likely differ from what you have used
ml-collections==0.1.0
tensorflow-gan==2.0.0
tensorflow_io==0.17.1
tensorflow_datasets==3.1.0
tensorflow==2.4.0
tensorflow-addons==0.12.0
tensorboard==2.4.0
absl-py==0.10.0
flax==0.3.1
jax==0.2.8
jaxlib==0.1.59
tensorflow-probability==0.12.2

Would it be possible for you to report the version of python that you are using and run pip freeze > requirements.txt to help with reproducibility?

Hi samedii. I am currently facing the same questions with you, have you find these requirements out?

The repository cannot be installed at the moment probably due to new releases of dependencies. I suspect the issue is that the version of tensorflow_io is not specified and some versioning around the tensorflow-probability library is incorrectly specified somewhere upstream.
This seems to work but the versions likely differ from what you have used
ml-collections==0.1.0
tensorflow-gan==2.0.0
tensorflow_io==0.17.1
tensorflow_datasets==3.1.0
tensorflow==2.4.0
tensorflow-addons==0.12.0
tensorboard==2.4.0
absl-py==0.10.0
flax==0.3.1
jax==0.2.8
jaxlib==0.1.59
tensorflow-probability==0.12.2

Would it be possible for you to report the version of python that you are using and run pip freeze > requirements.txt to help with reproducibility?

Hi samedii. I am currently facing the same questions with you, have you find these requirements out?


Suggestion: Make explicit the version of Erlang in the book

As stated here, it may be helpful to explicitly state somewhere in the book which version it targets.
Then readers can guess about the contents of the book even after the implementation is changed later. Since sometimes there are major changes that affect the contents of this book.

Yes, I have been thinking about this.
One problem is that right now there are old pieces of text written when Erlang was on version 14 and and 15 and newer parts that cover version 18 and 19.
Perhaps we would need to tag each chapter with which Erlang version it is updated to?
The goal right now is to cover Erlang 19 but we can not really state in the preface or introduction that the book covers 19 since some chapters have not been revised to that version.
I am all for making this information clear in some way so any suggestion on how to do it is welcome.

I think a [NOTE] at the start of each chapter describing which version it was written for would be great.

OTP 21 changes how messages are added to other processes, but I'm not 💯 if the diagrams need to change.

Agreed with @garazdawi 's comment above, I think just adding OTP version to [NOTE] would work. If there is more to say, we can always add descriptions to it.

How bad did it look in the PDF? (or did it not even build?)

It built, but looks as below:

I see it's using dblatex, but asciidoctor-pdf can not be used?
Also, shaape does not look being maintained anymore (https://github.com/christiangoltz/shaape/issues/20), the last commit was 2014. Does it make sense to look for an alternative ?

Yes it might be a good time to update the build process. My plan is to get to finish the missing chapters in the near future and I will work more actively on the book now.
If you have some suggestions please let me know.

The addition of missing chapters would be great. Does it help in any way to try to improve the formatting or layout at the moment, or better to wait for now?

If you want to do it please go ahead, I would appreciate it.

Got it.

As part of https://github.com/happi/theBeamBook/pull/135, Admonition icon works in pdf as below:

On HTML, it looks as below:


Update Driver.cs

Provided a better error code without complete application exit.

Hello! I'm the build bot for the Mono project.
I need approval from a Mono team member to build this pull request. A team member should reply with "approve" to approve a build of this pull request, "whitelist" to whitelist this and all future pull requests from this contributor, or "build" to explicitly request a build, even if one has already been done.
Contributors can ignore this message.

PR needs to be updated, closing for now.


Swashbuckle isn't generating correct information for XML examples

Swashbuckle.AspNetCore version 6.5.0
It looks like Swashbuckle is not generating the appropriate information in swagger.json for Swagger UI to display XML examples in APIs that return collections.
Steps to reproduce

I very similar complete .NET 7 project can be found in this repository.

Controller code:
[ApiController, Route("[controller]")]
public class ContactsController : ControllerBase
{
    [HttpGet(Name = "GetContacts")]
    [ProducesResponseType(typeof(Contact[]), StatusCodes.Status200OK)]
    public IEnumerable<Contact> Get() => new Contact[]
    {
        new(Guid.NewGuid(), "John"),
        new(Guid.NewGuid(), "Mark"),
    };
}

In Program.cs, add the XML output formatter
builder.Services.AddControllers(options =>
{
    options.OutputFormatters.Add(new XmlDataContractSerializerOutputFormatter());
});

For the GetContacts endpoint, the JSON generated looks like this
"/Contacts": {
  "get": {
    "tags": [
      "Contacts"
    ],
    "operationId": "GetContacts",
    "responses": {
      "200": {
        "description": "Success",
        "content": {
          "// other content-types omitted for brevity",

          "application/xml": {
            "schema": {
              "type": "array",
              "items": {
                "$ref": "#/components/schemas/Contact"
              }
            }
          },
          "text/xml": {
            "schema": {
              "type": "array",
              "items": {
                "$ref": "#/components/schemas/Contact"
              }
            }
          }
        }
      }
    }
  }
}

But, for Swagger UI to display the examples correctly, the schema property should be like
"schema": {
  "type": "array",
  "items": {
      "$ref": "#/components/schemas/Contact"
  },
  "xml": { // this property is not being generated
    "name": "contacts"
  }
}

Am I missing something or is this a bug? If it's a bug, I would be happy to contribute with a PR, I just need a little help with the starting point.

        /// <summary>
        /// This MAY be used only on properties schemas. It has no effect on root schemas.
        /// Adds additional metadata to describe the XML representation of this property.
        /// </summary>
        public OpenApiXml Xml { get; set; }

This sounds like a feature. Is there some reason why it should have the xml property defined?

Hey,
I want to give this a try. Is there a place for new contributors with more information/ documentation, except for the Readme or Contribution file?
Or could someone give me a direction where to look at.
Thanks!

A contribution to fix this would be welcome @Daissy538 - we don't currently have any specific documentation beyond the existing README and contributing files.
Most of the XML-comments related code lives here, so that should be a good place to start.

It is very good features and we need it

Hey everyone,
I fixed the issue of the missing XML array examples 😄.
Feel free to give me feedback on my PR. First-time contributing to an open-source project 😉


Add optimum information

Add optimization information to the benchmark functions

Thanks Michaela! I'm generally good with this, if you could just comment briefly on the question about where we think the weird precision values come from. Can you also summarize for us if there are files you did things other than just add the minima to? It's hard to see cause the diff is so big.

benchmark.py - added abstract properties global_minimum and global_minimum_location

all files - added global minimum and global minimum location to all functions

denschn.py - reorganize functions so they are in alphabetical order

esfl.py - changed to using the gms code in the _function method

fermat.py - changed to using the gms code in the _function method for problems fermat_vareps and fermat2_vareps.

median.py -  changed to using the gms code in the _function method for median_vareps

palmer.py - changed to using the gms code in the _function method for problems palmer2a, palmer3, palmer4, and palmer8a.

yfit.py - changed to using the gms code in the _function method for yfit

growth.py - changed to using the gms code in the _function method for problems growth and growthls

least.py - added 20 to the first upper bound of least

himmel.py - changed bounds of himmelbf from [[0, 0.378], [0, 0.378], [0, 0.378], [0, 0.378]] to [[-10, 0.378], [0, 200], [0, 1800], [-50, 0.378]]

s.py - changes to s245, s266, s267, s351 that I will put in a separate list so it's not all one line.

s245 - changed bounds from [[-9.0000000001, 0], [-7.90000065364893e-09, 0], [-8.9999999998, 0]] to [[-9.0000000001, 2], [-7.90000065364893e-09, 15], [-8.9999999998, 10]]

s266 - use gms code

s267 - increase upper bound of last dimension by 2

s351 - increase upper bound of 3rd dimension by 20

Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: mzbush @.>
Sent: Friday, May 3, 2024 6:08:11 PM
To: biomodsquad/smolyak-surrogate-modeling @.>
Cc: Christopher Kieslich @.>; Mention @.>
Subject: [EXT] Re: [biomodsquad/smolyak-surrogate-modeling] Add optimum information (PR #22)
CAUTION: Email Originated Outside of Auburn.
@mzbush commented on this pull request.

In smolyay/benchmark/biggs.pyhttps://github.com/biomodsquad/smolyak-surrogate-modeling/pull/22#discussion_r1589760800:

@@ -9,6 +9,14 @@ def domain(self):
[-1.96500000271271e-07, 17.99999982315],
[-5.0000001349, 13.49999987859]]

@property
def global_minimum(self):

   return 0

@property
def global_minimum_location(self):

   return [0.9999999832, 9.9999998035, 4.9999998651]

There were 5 functions where the rounding brought them farther from the recorded locations than usual, an around 1e-3 difference. These are himmelbb sisser, powell, s256, and s275. Looking at the functions written down, though, it's clear all of them have a global minima at 0 for all variables.
—
Reply to this email directly, view it on GitHubhttps://github.com/biomodsquad/smolyak-surrogate-modeling/pull/22#discussion_r1589760800, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOI4MG4IDWHCZUOEFKOUASTZAQDEXAVCNFSM6AAAAABGVRMHN6VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAMZZGA2TEOJSGY.
You are receiving this because you were mentioned.Message ID: @.***>

What work (if any) needs to be done to finalize this PR?


Release propagators-datadog

Any plans to release https://github.com/iand675/hs-opentelemetry/tree/main/propagators/datadog ?
I've been able to get Datadog correlation fully working as far as I can tell by just adding a trace-id to my logs. The collector handles translating ids for traces, I guess, and then I just set my Trace ID field on log injecting, and it all matches up.
Thing is, I've had to in-line the bit fiddling though to do it, which I'd rather not. I'm not actually sure what a full-on Propagator will do for me, but I'd at least like to rely on the package for the bit-fiddler functions.

I am going to upload the package to Hackage, @iand675 is it OK?

Yes, sounds good!
Met vriendelijke groet,
Ian Duncan
On Wed, Sep 27 2023 at 11:46 AM, Kazuki Okamoto < @.*** > wrote:

I am going to upload the package to Hackage, @iand675 (
https://github.com/iand675 ) is it OK?
—
Reply to this email directly, view it on GitHub (
https://github.com/iand675/hs-opentelemetry/issues/98#issuecomment-1737068143
) , or unsubscribe (
https://github.com/notifications/unsubscribe-auth/AAAQ4WMIKHNMQKFHR4TWAWLX4PYXTANCNFSM6AAAAAA5GCH6XI
).
You are receiving this because you were mentioned. Message ID: <iand675/hs-opentelemetry/issues/98/1737068143
@ github. com>

Released https://hackage.haskell.org/package/hs-opentelemetry-propagator-datadog-<IP_ADDRESS>

Thanks! Are there any docs on using non-default propagators? I.e. those not known here?

Here is an example to create TracerProvider with a Datadog propagator.
do
  otlpConfig <- loadExporterEnvironmentVariables
  exporter <- otlpExporter otlpConfig
  batchProcessorConfig <- detectBatchProcessorConfig
  processors <- (:[]) <$> batchProcessor batchProcessorConfig exporter
  (_, tracerProviderOptions) <- getTracerProviderInitializationOptions
  let tracerProviderOptions' =
        tracerProviderOptions
          { tracerProviderOptionsPropagators = datadogTraceContextPropagator
          }
  createTracerProvider processors tracerProviderOptions'


correct URLs by escaping quotes

closes issue #13408

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[ ] Tested changes locally.
[x] Closes currently open issue (replace XXXX with an issue no): Closes #13408

Description

Changed the a tags from "<a href=\"https://atjonathan.github.io/catphotoapp\" to "<a href=\"http://freecatphotoapp.com/\"

:sparkles: :sparkles: LGTM. :sparkles: :sparkles:
Thanks @nellarro ! Congratulations on your first contribution to freeCodeCamp!
P.S: Next time, we suggest you need not add the issue no in the commit message, they should only be in PR description. Thanks a lot for this change.


new offer example file, completely anonymous

the title finally splits in multiple lines now. @ggabernet when you have time it makes sense to have a look at this and merge it :)


Update and rename index.md to independent Women

Why:
Closes [issue link]

What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[ ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

This XML file does not appear to have any style information associated with it. The document tree is shown below.

Copyright: Creativity at Work
http://blogs.loc.gov/copyright/feed/
A blog that explores a wide variety of copyright-related topics, including special project updates, interesting copyright court cases and case law, current copyright issues, and current events.
en-us

Wed, 15 Dec 2021 13:00:18 -0600
My Food, My Culture
50402877
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/301163d

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

My Food, My Culture

12/15/2021 01:34 PM EST

I love food, and the foods I love I really love. Many of my favorite foods and meals are the ones I ate with my family and are part of my cultural heritage as the son of Greek parents and the grandson of Greek immigrants. It was a fundamental part of festivals, holidays, family gatherings, […]

Fri, 03 Dec 2021 14:00:17 -0600
The CASE Act: Copyright Claims Board to Begin Hearing Cases in Spring 2022
50276476
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2ff287c

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

The CASE Act: Copyright Claims Board to Begin Hearing Cases in Spring 2022

12/03/2021 02:47 PM EST

The Copyright Office is setting up the Copyright Claims Board (CCB) as directed by the Copyright Alternative in Small-Claims Enforcement Act of 2020. The CCB will begin hearing cases in Spring 2022.

Mon, 29 Nov 2021 14:00:11 -0600
Find Poetry in Copyright: Joy Harjo
50226649
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2fe65d9

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Find Poetry in Copyright: Joy Harjo

11/29/2021 02:55 PM EST

U.S. Poet Laureate Joy Harjo has engaged her creativity through poetry, books, plays, and music. Read more about her copyright journey and place in the exhibit, Find Yourself in Copyright.

Tue, 23 Nov 2021 14:00:22 -0600
Discovering Native American Cultures through Illustrated Stories
50176376
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2fda178

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Discovering Native American Cultures through Illustrated Stories

11/23/2021 02:30 PM EST

Illustrated stories from Native American authors can provide a great introduction to Indigenous cultures.

Fri, 19 Nov 2021 14:00:29 -0600
Barbara Ringer’s Legacy of Fighting for Equity at the Copyright Office: An Interview with Amanda Levendowski
50141318
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2fd1886

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Barbara Ringer’s Legacy of Fighting for Equity at the Copyright Office: An Interview with Amanda Levendowski

11/19/2021 02:23 PM EST

Forty-eight years ago, Barbara Ringer was appointed Register of Copyrights. Amanda Levendowski, associate professor of law at Georgetown Law, discusses how she inspires current and future intellectual property professionals.

Wed, 13 Oct 2021 15:00:49 -0500
Artificial Intelligence: The Copyright Connection
49763838
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2f755fe

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Artificial Intelligence: The Copyright Connection

10/13/2021 03:50 PM EDT

Developments in artificial intelligence raise copyright questions, some of which will be discussed at a virtual event on October 26, 2021.

Thu, 07 Oct 2021 16:01:20 -0500
Six Songs to Celebrate Hispanic Heritage Month
49707331
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2f67943

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Six Songs to Celebrate Hispanic Heritage Month

10/07/2021 04:30 PM EDT

The Copyright Office’s records comprise millions of registrations and recorded documents from Hispanic and Latin Americans, many featuring works that share their cultures and traditions and enrich the nation. We're celebrating Hispanic Heritage Month with few recognizable songs steeped in Hispanic musical culture.

Thu, 07 Oct 2021 16:01:19 -0500
Seis canciones para celebrar el Mes de la Herencia Hispana
49707330
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2f67942

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Seis canciones para celebrar el Mes de la Herencia Hispana

10/07/2021 04:30 PM EDT

Los registros de la Oficina del Derecho de Autor constan de millones de registros y archivos de hispanos y latinoamericanos, mucho de los cuales presentan obras que comparten sus culturas y tradiciones y enriquecen la nación. Estamos celebrando el Mes de la Herencia Hispana con algunas canciones reconocibles impregnadas de la cultura musical hispana.

Thu, 16 Sep 2021 09:00:31 -0500
The Inspiring Life and Work of Selena Quintanilla-Pérez
49397832
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2f1c048

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

The Inspiring Life and Work of Selena Quintanilla-Pérez

09/16/2021 09:07 AM EDT

Selena Quintanilla-Pérez was a musical powerhouse who continues to be an important creative influence decades after her death. Read about some of the ways she has inspired others.

Fri, 25 Jun 2021 09:00:48 -0500
Copyright and Drag
48594981
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2e58025

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Copyright and Drag

06/25/2021 09:29 AM EDT

Drag performances are one of the many creative contributions to come out of the queer community. The history of drag within the copyright record runs deep, and many aspects of it are protected by copyright.

Mon, 07 Jun 2021 09:00:23 -0500
Creating to Inspire Social Change: A Brief Look into Gwendolyn Brooks
48426137
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2e2ec99

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Creating to Inspire Social Change: A Brief Look into Gwendolyn Brooks

06/07/2021 09:54 AM EDT

The following is a guest post by Chandel Boozer, spring 2021 law clerk in the Office of Policy and International Affairs. In the United States, authors can share their unique perspectives based on their varying life experiences, ethnicities, and beliefs. Amongst those authors, poets have the ability to succinctly capture an emotion or experience with […]

Fri, 28 May 2021 11:01:05 -0500
Celebrating Asian American Representation in Film
48351418
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2e1c8ba

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Celebrating Asian American Representation in Film

05/28/2021 11:33 AM EDT

Over the past century, film has become one of the more popular and influential forms of entertainment, helping us feel seen and realize what could be. For Asian Pacific American Heritage Month, celebrate some recent films and the writers, directors, producers, and stars changing the face of American cinema.

Mon, 24 May 2021 09:00:39 -0500
Ode to Cicadas
47972074
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2dbfeea

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Ode to Cicadas

05/24/2021 09:44 AM EDT

They’re flying, buzzing, and crawling everywhere! Washington, DC, neighborhoods around the U.S. Copyright Office are teeming with Brood X cicadas, taking their next steps on a seventeen-year journey. Along the way, they’re also inspiring musicians, photographers, artists, and authors to create copyrighted works. These cicadas belong to a genus called magicicada, whose very name evokes […]

Tue, 13 Apr 2021 09:01:09 -0500
The Register: The Historical and Unique Title for American Copyright Leadership
46965098
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2cca16a

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

The Register: The Historical and Unique Title for American Copyright Leadership

04/13/2021 09:11 AM EDT

The following is a guest blog post by Marilyn Creswell, Librarian-in-Residence at the U.S. Copyright Office. In most conversations, a register is usually a list, and a registrar is usually a person who keeps lists. The U.S. Copyright Office is a rare example of a Register being the person who keeps a register.1 The origin […]

Wed, 31 Mar 2021 11:00:40 -0500
Zitkála-Šá: On Creativity, Copyright, and Cultural Empowerment
46833679
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2caa00f

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Zitkála-Šá: On Creativity, Copyright, and Cultural Empowerment

03/31/2021 11:53 AM EDT

Zitkála-Šá was a prolific writer, political activist, and musician, credited as the first Native American to write an opera, The Sun Dance Opera. However, despite her contributions, Zitkála-Šá does not appear on the copyright records for the work.

Wed, 24 Mar 2021 16:00:41 -0500
Houdini and the Magic of Copyright
46750233
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2c95a19

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Houdini and the Magic of Copyright

03/24/2021 04:11 PM EDT

The following is a guest blog post by Marilyn Creswell, Librarian-in-Residence at the U.S. Copyright Office. Magicians do not always reveal their tricks, even when they register their copyright claims. The legendary Hungarian immigrant Harry Houdini registered three of his famous illusions as “playlets,” or short plays, with the U.S. Copyright Office between 1911 and […]

Mon, 15 Mar 2021 14:00:20 -0500
The Copyright Office: Marking One Year of Pandemic Operations
46613100
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2c7426c

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

The Copyright Office: Marking One Year of Pandemic Operations

03/15/2021 02:38 PM EDT

The following is a guest blog post by Shira Perlmutter, Register of Copyrights and Director, U.S. Copyright Office. On Friday, March 13, 2020, the Library of Congress closed its buildings to the public and initiated pandemic operations. At the end of October, I was sworn in virtually by the Librarian of Congress, Dr. Carla Hayden. […]

Mon, 08 Mar 2021 16:00:44 -0600
Revisiting the Copyright Office’s Focus on Women in Copyright
46518876
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2c5d25c

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Revisiting the Copyright Office’s Focus on Women in Copyright

03/08/2021 04:57 PM EST

  The following is a guest post by Librarian-in-Residence Marilyn Creswell. Over the years, the U.S. Copyright Office has explored the many ways women have influenced creativity, copyright, and the Office itself. Women authors and the women within our own institution are key participants in the country’s copyright system. As part of our celebration of […]

Mon, 01 Mar 2021 09:00:29 -0600
Celebrating Women’s History Month: The Gee’s Bend Quilters and Copyright
46426584
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2c469d8

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Celebrating Women’s History Month: The Gee’s Bend Quilters and Copyright

03/01/2021 09:01 AM EST

The Gee's Bend quilters have a rich creative history. Through educational outreach from various organizations, the women of Gee's Bend have learned about copyright and their intellectual property rights.

Mon, 22 Feb 2021 11:00:34 -0600
The Marrakesh Treaty in Action: Exciting Progress in Access to Published Works for the Blind and Print-Disabled Communities
46324381
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2c2da9d

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

The Marrakesh Treaty in Action: Exciting Progress in Access to Published Works for the Blind and Print-Disabled Communities

02/22/2021 11:19 AM EST

Two years ago, the United States joined the Marrakesh Treaty, which has proven to be a success.

Thu, 18 Feb 2021 13:00:20 -0600
A Family of Creative Works in Celebration of Black History Month
46290428
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2c255fc

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

A Family of Creative Works in Celebration of Black History Month

02/18/2021 01:37 PM EST

The following is a guest post by Annette James. As I reflect upon the 2021 Black History Month theme, The Black Family: Representation, Identity, and Diversity, the word family captures a wealth of emotions. It calls up memories of childhood and retrospection on lessons learned. It brings to mind the sounds and stories cherished by […]

Fri, 12 Feb 2021 12:00:41 -0600
The Enduring Copyright Legacy of Justice Ruth Bader Ginsburg
46201639
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2c0fb27

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

The Enduring Copyright Legacy of Justice Ruth Bader Ginsburg

02/12/2021 12:25 PM EST

When Justice Ginsburg died on September 18, 2020, she left a lasting and wide-ranging legacy, most notably in her lifelong fight for women's rights and gender equality. Perhaps a lesser-known aspect of her influence is her impact on copyright law.

Fri, 29 Jan 2021 08:00:51 -0600
The Lifecycle of Copyright: 1925 Works Enter the Public Domain
45988110
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2bdb90e

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

The Lifecycle of Copyright: 1925 Works Enter the Public Domain

01/29/2021 08:46 AM EST

On January 1, a new raft of creative works of expression entered the public domain in the United States. The term of copyright has ended for works published or registered in 1925, which now join pre-1924 works already in the public domain and available for use by everyone without restrictions. Expiration of copyright term is […]

Fri, 15 Jan 2021 11:00:49 -0600
Three New Year’s Resolutions for Songwriters
45715216
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2b98f10

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Three New Year’s Resolutions for Songwriters

01/15/2021 11:55 AM EST

Let’s face it. This past year has been tough in many ways. For the music community, this has been especially true. There is one bright spot. On January 1, 2021, big updates were made to the way songwriters can get paid when their music is played online via interactive streaming and download services. Specifically, the […]

Thu, 14 Jan 2021 15:00:25 -0600
Coming Soon: New Look and Navigation for Copyright.gov
45654358
https://content.govdelivery.com/accounts/USLOCCOPYRIGHT/bulletins/2b8a156

You are subscribed to Copyright: Creativity at Work for U.S. Copyright Office. This information has recently been updated, and is now available.

Coming Soon: New Look and Navigation for Copyright.gov

01/14/2021 03:18 PM EST

The U.S. Copyright Office is updating the look and navigation of its website.


Explore Dart localization

Explore options for localization in Dart on both AngularDart & Flutter.

@Kenny11CZ Finish this task, please, this week. Write down how to use it, how to configure it, …

Write down here how the whole process with translations works, how to switch languages, etc... :-)


customer javascript object.it's properties isn't in suggestions.

Not sure if TS would support this.

I test the 'window', it doesn't work also.

but when I use 'window' keywords. It can work well.

@tonn2y This is because you are using JavaScript not TypeScript. The type of the variable is determined at the point of declaration. i.e. for the parameter 'win' in your anonymous function, there is no way for the language service to know what type win will be. You could pass anything into it. Just because your own usage passes window into it, does not mean that it should definitely be of type window. However, perhaps that's an improvement that should be made? i.e. types being inferred from usages.
And in the case above where you do var todoList = this; the variable todoList is assigned the type of this. If no type can be detected, then it has no type (or type 'any'). You are then adding new properties dynamically which will not be 'added' to the variable's original type. Because of the nature of the TypeScript language service (which I believe powers the JS language service), you would only get suggestions based on the type detected at the point of declaring the variable.
However, in JavaScript it certainly would be nice if the language service could alter the type of the variable after it was declared, or detect its type based on usage (i.e. parameters), due to the lack of interfaces and type annotations, so that better code completion could be offered... Although I'm pretty sure this would not be desirable in TypeScript as you should be doing that using interfaces/type annotations.

@tonn2y If you can use TypeScript in your project it's probably a good idea

@tonn2y Yes you're right. I've read that in the January release they might add Salsa support, which from what I gather will be a smarter language service for JavaScript editing. However I don't know if this will be supported with Salsa or if it will require separate work.

thinks.

Closed with the adoption of Salsa (https://code.visualstudio.com/Updates#_languages-javascript).


Fixed Typo in README

Cool. Why not merge?

fyi jsonl is actually a thing, you might want to make sure it's actually a JSON output and not a jsonl (a list of multiple JSON's).


Fix text in About Page

Description
The text under the 'About' header doesn't seem right as the meaning of the second sentence is not clear.

We can change the below text:

To help you grow, scale, and dominate through the power of link management.Whether you’re sharing one link ,lets you personalize, track.

to:

To help you grow, scale, and dominate through the power of link management. Whether you’re sharing a single link or multiple links, Shorty lets you personalize and track your links with ease.

Screenshots

Additional information
I would like to work on this as part of GSSoC'23.

@Sriparno08 Assigned


docs(samples): updated samples code to use async await

Fixes googleapis/google-cloud-node#2869 (it's a good idea to open an issue first for discussion)
Fixes https://github.com/googleapis/nodejs-cloud-container

[ ] Tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Already completed and Closed


Watch date filter

Closes #95

@loulawrence  the timeline supplied dates for the filter should be fixed now


Timing out when accessing tract data

> tracts19 <- load_oeps(scale="tract",
+                          year=2018,
+                          geometry=TRUE)
trying URL 'https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables//T_Latest.csv'
Error in download.file(file, tmpFile, method = method, mode = "wb", quiet = !showProgress) :
  cannot open URL 'https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables//T_Latest.csv'
In addition: Warning message:
In download.file(file, tmpFile, method = method, mode = "wb", quiet = !showProgress) :
  URL 'https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables/T_Latest.csv': Timeout of 60 seconds was reached

> tracts19 <- load_oeps(scale="tract",
+                          year=2018,
+                          geometry=FALSE)
trying URL 'https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables//T_Latest.csv'
Error in download.file(file, tmpFile, method = method, mode = "wb", quiet = !showProgress) :
  cannot open URL 'https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables//T_Latest.csv'
In addition: Warning message:
In download.file(file, tmpFile, method = method, mode = "wb", quiet = !showProgress) :
  URL 'https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables/T_Latest.csv': Timeout of 60 seconds was reached
>

Both of these options work  on their own:
tracts19.read <- read.csv("https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables/T_Latest.csv")
library(data.table)
tracts19.fread <- fread("https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables/T_Latest.csv")

On the back end, the package makes the fread call above, which makes this behavior very interesting and weird. As that load_oeps call also works on my system (albeit very slowly), my gut instinct is that this is a networking hiccup of some sort. Does the load_oeps call still fail on your end if you retry now (or when you try on different connections)?
Either way, there is currently no back end logic to help catch and provide useful feedback/error handling of timeouts and networking hiccups in general, so that may end up being a welcome addition to the package (especially if this does turn out to be one).

One strange thing is double slashes near the end of the URL. Not sure it's related but we should get that fixed.

Looks like fread can also target gzipped files (docs), so compressing each CSV is something else we could do to reduce the chance of this timeout happening in the future.

Interestingly, this is happening in the docs build as well:
Error in `download.file()`:
! download from 'https://raw.githubusercontent.com/GeoDaCenter/opioid-policy-scan/main/data_final/full_tables//T_2000.csv' failed

https://github.com/healthyregions/oepsData/actions/runs/11466984292/job/31909157660

The job completes successfully after I removed the extra slash, for what it's worth. @Makosak can you try this again when you get a chance?

Closing now, I can't reproduce this locally so hopefully the problem has been solved, or was just due to a spotty connection at the outset.


Implement UnpublishPageAction and Admin API for un-publishing pages

See #7682.

Do the tests still pass? Yes
Does the code comply with the style guide? Yes
For Python changes: Have you added tests to cover the new/fixed behaviour? Yes

Thanks @kaedroho! I've addressed your comments.

I merged main branch into this one.

@Tijani-Dia I have just rebased this on main, now that the publish page action work is in, will merge into main once the checks have passed.

@kaedroho as per other comment, I have merged this in but have not included any release notes for this and other API work, will leave that to you.
@Tijani-Dia thanks for the epic solution here also.


More flexible host selectors for deployment groups

Support inequality conditions. E.g. 'role=my_role canary!=yes'
Use a more storage format for host selectors, enabling implementing
more advanced host selectors in the future.

Note that the host list command has not be updated (yet!), and currently
does not support the != operator.

@rohansingh @rculbertson @davidxia

Rebase on master to get the test fix from #532.

OK, I just rebased. Had to force push though.

:+1: After a quick read through. Maybe use more immutable lists? :)

@davidxia: there are now more immutable lists


publish cli commands as python api

Currently using zappa from another python application that needs to call zappa on the command line. Would be great if the cli commands can be exposed as a published python api so it can be used programmatically.

@maebert  ++

@Miserlou And I had a discussion about this on Slack. I could be convinced to work on that if we get #542 reviewed and merged first. :)


Update Username & GitHub Link for Rana Jahanzaib

Hello CODEOWNERS,
I had my username updated a few months ago. Please, head over to https://github.com/Jahanzaibv2 to confirm the redirect I've placed.
Previously: @Jahanzaibv2
Now: @ranajahanzaib
Thank you @hafizusman530 for starting a list of developers and organizations contributing to the Open Source. :heart_eyes:

@ranajahanzaib I was on sleep mode, Your PR is merged with the updated username.


Get a passing CI build of JDK 11.

@swankjesse requesting post review.  Happy to discuss and iterate from a point of a green build in CI.


fix member cluster's node controller can not clean orphan clusternode

What type of PR is this?

fix: fix bug
What does this PR do?

fix member cluster's node controller can not clean Orphan clusternode
Which issue(s) does this PR fix?

Fixes #
Special notes for your reviewer:

Screenshots (if applicable):

Additional Comments:

/lgtm

/approve

/approve


Issue with from icecube.icetray import I3Tray in container

When running against a modern IceTray installation one gets a warning about from I3Tray import I3Tray being deprecated.
However in CI from icecube.icetray import I3Tray fails due to I3Tray not having an Add attribute.
Currently I had to revert PR #7 to the old-style import for the sake of CI testing.

@dsschult any suggestion?

It looks like the docker image is at least 6 months old, and you should use the icetray-prod-current-ubuntu22.04-X64 tag.

I'd probably ask @briedel why the -X64 got added to the tag name, and the generic tag no longer works.

also that warning is completely harmless, but you should upgrade to the latest icetray

Will be fixed in #15 , thanks to all for the inputs!


Update .travis.yml after Python 3.8 release

Codecov Report

Merging #69 into master will increase coverage by 0.6%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master      #69     +/-   ##
=========================================
+ Coverage   91.35%   91.95%   +0.6%
=========================================
  Files           6        6
  Lines        2232     2400    +168
=========================================
+ Hits         2039     2207    +168
  Misses        193      193

Impacted Files
Coverage Δ

pyodata/v2/service.py
89.98% <0%> (+0.28%)
:arrow_up:

pyodata/v2/model.py
92.49% <0%> (+0.76%)
:arrow_up:

Continue to review full report at Codecov.

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


Build: remove bower and requirejs

Btw, this closes: https://github.com/adobe-community/issues/issues/10445  ( :) )

Travis failure:
ERROR in ./test/specs/ractive/Model.js
Module not found: Error: Cannot resolve module 'Ractive' in /home/travis/build/behance/BeFF/test/specs/ractive
 @ ./test/specs/ractive/Model.js 1:0-137:2
11 09 2016 03:36:15.442:INFO [karma]: Karma v1.1.2 server started at http://localhost:9876/
11 09 2016 03:36:15.444:INFO [launcher]: Launching browser PhantomJS with unlimited concurrency
11 09 2016 03:36:15.476:INFO [launcher]: Starting browser PhantomJS
11 09 2016 03:36:15.814:INFO [PhantomJS 2.1.1 (Linux 0.0.0)]: Connected on socket /#YxjTdEWiCtB1IfI6AAAA with id 68895236
PhantomJS 2.1.1 (Linux 0.0.0) ERROR
  Error: Cannot find module "Ractive"
  at undefined:2

👍  once Travis passes

👍

👍


Ticking plant error with VFECore

Describe the bug
A conflict with VFE causes the plant threads to throw an error and restart endlessly.
Steps to reproduce the behavior (VERY IMPORTANT)

Press play on the supplied save file (don't know if error triggers on a new save)
Wait a bit
Game freezes, wait for it to unfreeze
See error

Error Log
Player.log: https://gist.github.com/robmart/9d8516cf6221b323579b563a1de27455
Save file
https://easyupload.io/evmhxa
Mod list (Preferably a RimPy compatible list.)
File is a RimPy exported mod list, just change it to a xml to import it. Highly Modded 1.3.txt

This one gets fixed by my last commit on 2.5.12

You are using RT 2.5.7 this issue was fixed in the latest RT versions. This issue can be closed


React-PropTypes to prop types: unnecessary import 'react'

If I have separate file for proptypes, it still imports react
-import { PropTypes } from 'react'
+import 'react';

semicolon issue is already mentioned #108

I believe this has been fixed in master! Please reply here if I am incorrect. Sorry for the inconvenience.


[Integration] Tests too impatient when checking crc status

Extend the wait time in Start CRC scenario in all story_* feature files. Tests sometimes fail due to timeout (crc status check passes right in the next scenario, so it is an actual timeout). Suggesting to change the number of tries and wait periods from 4x2mins to 15x1min.
See attached screenshot when this was the cause of a failed test.

Optimistic is a better term to describe this.
However, we should not have to wait multiple times, but wait until something happened and break when it didn't happen in time. Concept of retry is flawed anyway as we do not really retry the action from CRC such as calling the same action; we merely wait for a certain state to eventually be consistent.

Optimistic is a better term

Haha
@gbraad about the latter: true, but...

we should not have to wait multiple times, but wait until something happened and break when it didn't happen in time

We basically do that. One can understand 15x1min wait as a 15min wait (and break if not satisfied by that point) with an option to leave the step earlier if satisfied earlier. This saves test time on "good days" :).

we do not really retry the action from CRC such as calling the same action; we merely wait for a certain state to eventually be consistent

I see how retry is misleading, but we're merely retrying the checks of the state (re-checking), not retrying to make the state consistent. Seems just an issue with phrasing, not the actual content of the test step. Do I understand you correctly?

Right. The wording "retry" for me would have retriggered the action for CRC and not just testing ;-)
But each time we have a wait statement in our tests I grinch... We should have to be able to do a better job.

@jsliacan Is this still an issue?

Nope, closed is OK. Thanks.


X::IO::Link not documented

It is already linked from here: http://doc.perl6.org/routine/link
And it does actually exist: https://github.com/rakudo/rakudo/blob/a80414edc1194b0852be5b19130bec670f2bb45e/src/core/IO/Path.pm#L376

49e72a2e34

That looks alright. Thanks!


[FEATURE] - Update dependencies - uuid, http, linkify

Hello,
Please update dependencies for packages uuid, http and linkify, I get errors from many libraries that use newer versions of these packages.
used in super editor : uuid ^3.0.3; latest: uuid: ^4.5.0
used in super editor : http ^0.13.1; latest: http: ^1.2.2
used in super editor : linkify ^4.0.0; latest: linkify: ^5.0.0
Thank you

@angelosilvestre please update all our dependencies to the latest version, wherever you can.
If there are non-trivial blockers to upgrade a given dependency, then please note the blocker here, and skip that one.