Add dev site notice

would probably be good to have a small message somewhere stating that this is the dev site, and any data shared is openly available. This wouldn't be shown on live site, but the code might be adapted for cookie policy or any other requirements

#272 added a little icon on top of the page that lived in src/components/Dev/DevNotice.tsx based on the isDebug node variable.
What would be nice to have is on hover a little tooltip with this indication :
"This is the dev site and all datas posted here can be public"

@sanjuskm05 is now working on this ⚡

Submitted the pull request. Whenever possible, please review and merge it

reviewed, minor changes requested, please update the PR when complete. Thanks


Escaping of label contents

Hi, i've just composer updated a project with "adamwathan/bootforms": "^0.8.2" and  "propaganistas/laravel-translatable-bootforms": "~1.3" (on composer.json) and now the labels for the translatable inputs aren't being escaped.
I have opened an issue with propagandistas but they informed me I should open an issue with you, since the escaping of the labels was done bu the form package. (see more here: https://github.com/Propaganistas/Laravel-Translatable-Bootforms/issues/24 ).
Will there be a fix, or I need to revert the update?
Thank you for this package!

Reverted that change and tagged v0.9.0, thanks.
https://github.com/adamwathan/form/commit/d44534bf812512daa9d5a3b68d0ef7928def99b8

Great, thanks!


Pre chained with request

If I do a check in the app.pre() and it failed, I expect it just response the error message in app.pre() and terminate the request. But turned out, it sent out response in app.pre(), and still keep running the intent request.
Any thoughts?

One of the common purposes of using app.pre() is to check the application id. When a failure occurs (e.g. the app ID is unexpected), you can throw an exception or use response.fail. For example:
// Ensure it is our intended application sending the requests
alexaApp.pre = function (request, response, type) {
    if (request.sessionDetails.application.applicationId !== Config.applicationId) {
        // Fail ungracefully
        //console.log('Invalid applicationId: ' + request.sessionDetails.application.applicationId);
        //throw 'BAD_APP_ID';
        response.fail('Invalid applicationId: ' + request.sessionDetails.application.applicationId);
    }
};

thanks

Closing this.
It would be helpful if someone could clarify this in README. Maybe @tekkkon?


Add sequential nonce and direction to prevent MITM attack

Support sequential nonce to prevent replay, re-order and packet drop attack
Add stream direction (initiator) to prevent reflection attack
Compatibility with old version is achieved through DisableNonceVerification config

This PR should fix #7. In the future we can add native support for noise framework for easier usage.


migration draft

Issue #
Bug
Fix
Testing

MOVING TO #2456 -- all relevant comments applied to new PR.


Review reentry and add reentry guard if necessary

https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/utils/ReentrancyGuard.sol

Hummm, not sure if we have to address the issue that slither raised https://gist.github.com/ChihChengLiang/3875964fc1bd49ae38033ea33074acb5

Not intent to address


directive build error

Hi guys,
I added your directive to my project, also added  ngStorage, but I all the same got this error:
Failed to instantiate module *** due to:
Error: [$injector:modulerr] Failed to instantiate module ngDropImage due to:
Error: [$injector:nomod] Module 'ngDropImage' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
any suggestion?

Hi @anteriovieira, thanks for your support.
It is conf.js in my gulp directory. Do you means this file ?
/**

This file contains the variables used in other gulp files
which defines tasks
By design, we only put there very generic config values
which are used in several places to keep good readability
of the tasks
*/

var gutil = require('gulp-util');
/**

The main paths of your project handle these with care
*/
exports.paths = {
src: 'src',
dist: 'dist',
tmp: '.tmp',
e2e: 'e2e'
};

/**

Wiredep is the lib which inject bower dependencies in your project
Mainly used to inject script tags in the index.html but also used
to inject css preprocessor deps and js files in karma
*/
exports.wiredep = {
exclude: [//bootstrap.js$/, //bootstrap.css/],
directory: 'bower_components'
};

/**

Common implementation for an error handler of a Gulp plugin
*/
exports.errorHandler = function(title) {
'use strict';

return function(err) {
gutil.log(gutil.colors.red('[' + title + ']'), err.toString());
this.emit('end');
};
};

It is conf.js in my gulp directory. Do you means this file ?

No, sorry, I meant the file where you put your dependencies.

Try https://www.npmjs.com/package/bower-npm-resolver for npm packages

This my package.json{
"name": "inspinia",
"version": "2.7.1",
"dependencies": {
"angular-drop-image": "^1.0.8"
},
"scripts": {
"test": "gulp test"
},
"devDependencies": {
"browser-sync": "~2.9.11",
"browser-sync-spa": "~1.0.3",
"chalk": "~1.1.1",
"del": "~2.0.2",
"eslint-plugin-angular": "~0.12.0",
"estraverse": "~4.1.0",
"gulp": "^3.9.1",
"gulp-angular-filesort": "~1.1.1",
"gulp-angular-templatecache": "~1.8.0",
"gulp-autoprefixer": "~3.0.2",
"gulp-eslint": "~1.0.0",
"gulp-filter": "~3.0.1",
"gulp-flatten": "~0.2.0",
"gulp-inject": "~3.0.0",
"gulp-less": "~3.0.3",
"gulp-load-plugins": "~0.10.0",
"gulp-minify-css": "~1.2.1",
"gulp-minify-html": "~1.0.4",
"gulp-ng-annotate": "~1.1.0",
"gulp-protractor": "~1.0.0",
"gulp-rename": "~1.2.2",
"gulp-replace": "~0.5.4",
"gulp-rev": "~6.0.1",
"gulp-rev-replace": "~0.4.2",
"gulp-size": "~2.0.0",
"gulp-sourcemaps": "~1.6.0",
"gulp-uglify": "~1.4.1",
"gulp-useref": "~1.3.0",
"gulp-util": "~3.0.6",
"http-proxy-middleware": "~0.9.0",
"karma": "~0.13.10",
"karma-angular-filesort": "~1.0.0",
"karma-coverage": "~0.5.2",
"karma-jasmine": "~0.3.6",
"karma-ng-html2js-preprocessor": "~0.2.0",
"karma-phantomjs-launcher": "~0.2.1",
"lodash": "~3.10.1",
"main-bower-files": "~2.9.0",
"phantomjs": "~1.9.18",
"uglify-save-license": "~0.4.1",
"wiredep": "~2.2.2",
"wrench": "~1.5.8"
},
"engines": {
"node": ">=0.10.0"
}
}

1 - Install the package to resolve npm's package
npm install bower-npm-resolver

2 - Add the resolver in your .bowerrc file:
{
  "resolvers": [
    "bower-npm-resolver"
  ]
}

3 - Once configured, your bower.json files may reference packages using npm: prefix:
{
  "dependencies": {
      "angular-drop-image": "npm:angular-drop-image",
  }
}

Hi @anteriovieira,
After 3 point when I added  dependencies, I can't serve my project. "gulp serve" got error
Error: Error: angular-drop-image is not installed. Try running bower install.
at /Users/newuser/Sites/ProjectName/admin/node_modules/wiredep/wiredep.js:30:56
at /Users/newuser/Sites/ProjectName/admin/node_modules/wiredep/lib/detect-dependencies.js:145:29,
Seems bower-npm-resolver not included right

:thinking:  Let me see your .bowerrc file.

and bower.json

.bowerrc
{
"directory": "bower_components"
},
{
"resolvers": [
"bower-npm-resolver"
]
}

bower.json
{
"name": "inspinia",
"version": "2.7.1",
"dependencies": {
"angular-toastr": "~1.5.0",
"angular-animate": "~1.5.0",
"angular-cookies": "~1.5.0",
"angular-touch": "~1.5.0",
"angular-sanitize": "~1.5.0",
"angular-messages": "~1.5.0",
"angular-aria": "~1.5.0",
"jquery": "^3.1.1",
"angular-resource": "~1.5.0",
"angular-ui-router": "~0.2.15",
"bootstrap": "~3.3.7",
"angular-bootstrap": "~1.1.2",
"moment": "~2.10.6",
"animate.css": "~3.4.0",
"angular": "~1.5.0",
"pace": "~1.0.2",
"metisMenu": "~2.0.2",
"fontawesome": "~4.7.0",
"angular-file-model": "^0.3.1",
"ngclipboard": "^1.1.3",
"ng-img-crop": "~0.3.2",
"amitava82-angular-multiselect": "~1.2.0",
"chosen": "",
"angular-summernote": "0.7.1",
"angular-drop-image": "npm:angular-drop-image"
},
"devDependencies": {
"angular-mocks": "~1.5.0"
},
"overrides": {
"bootstrap": {
"main": [
"less/bootstrap.less",
"dist/fonts/glyphicons-halflings-regular.eot",
"dist/fonts/glyphicons-halflings-regular.svg",
"dist/fonts/glyphicons-halflings-regular.ttf",
"dist/fonts/glyphicons-halflings-regular.woff",
"dist/fonts/glyphicons-halflings-regular.woff2"
]
},
"fontawesome": {
"main": [
"less/font-awesome.less",
"fonts/fontawesome-webfont.eot",
"fonts/fontawesome-webfont.svg",
"fonts/fontawesome-webfont.ttf",
"fonts/fontawesome-webfont.woff",
"fonts/fontawesome-webfont.woff2"
]
}
},
"resolutions": {
"jquery": "^3.1.1",
"angular": "~1.5.0"
}
}

You have installed the angular-drop-image package with npm? and bower-npm-resolver


Output link as dat://

It's time.
It'll make it easier to tell what is a dat archive vs another random 64 char hash.

https://github.com/joehand/dat-next/pull/35


Operational Intelligence: Using Pinot as Backend for Timeseries Data

We have a request to use pinot to process time series data. This issue will track the progress of adding time series functionality to Pinot.

As someone looking to use Pinot for storing time series data right now, I am assuming that by processing you are referring to adding time series analytical functions such as decaying average, sliding windows, etc, right?

@elonazoulay can you please start a design doc on what you plan to add

Yes, some example functions:

#7422 for the design for some time-series aggregation

https://github.com/apache/pinot/issues/7213 for the design of generic window functions (sliding window, rolling average, etc).


Virtual Pet Game added

PR Description 📜
Fixes #3555
Mark the task you have completed ✅

[ ✅ ] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[ ✅ ] I have performed a self-review of my own code or work.
[ ✅ ] I have commented my code, particularly in hard-to-understand areas.
[ ✅ ] My changes generates no new warnings.
[ ✅ ] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[ ✅ ] I have added screenshot for website preview in assets/images
[ ✅ ] I have added entries for my game in main README.md
[ ✅ ] I have added README.md in my folder
[ ✅ ] I have specified the respective issue number for which I have requested the new game.

Add your screenshots(Optional) 📸

Thank you soo much for contributing to our repository 💗

Thank you @Nayanika1402 ,for creating the PR and contributing to our GameZone 💗
Review team will review the PR and will reach out to you soon! 😇
Make sure that you have marked all the tasks that you are done with ✅.
Thank you for your patience! 😀

@Nayanika1402 resolve merge conflicts !

@kunjgit Resolved the conflicts

@Nayanika1402 resolve merge conflicts!

Thank you  @Nayanika1402 , for your valuable time and contribution in our GameZone 💗.
It’s our GameZone, so Let’s build this GameZone altogether !!🤝
Hoping to see you soon with another PR again 😇
Wishing you all the best for your journey into Open Source🚀


python310Packages.jupyterlab-lsp: 4.0.0 -> 4.0.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.jupyterlab-lsp is: Language Server Protocol integration for Jupyter(Lab)
meta.homepage for python310Packages.jupyterlab-lsp is: https://github.com/jupyter-lsp/jupyterlab-lsp
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 4.0.1 with grep in /nix/store/z1m4nv5n8vmcafg8k9j9lyj79gby6y92-python3.10-jupyterlab-lsp-4.0.1
found 4.0.1 in filename of file in /nix/store/z1m4nv5n8vmcafg8k9j9lyj79gby6y92-python3.10-jupyterlab-lsp-4.0.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.jupyterlab-lsp
python311Packages.jupyterlab-lsp

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z1m4nv5n8vmcafg8k9j9lyj79gby6y92-python3.10-jupyterlab-lsp-4.0.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z1m4nv5n8vmcafg8k9j9lyj79gby6y92-python3.10-jupyterlab-lsp-4.0.1
ls -la /nix/store/z1m4nv5n8vmcafg8k9j9lyj79gby6y92-python3.10-jupyterlab-lsp-4.0.1/bin

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

2 packages built:

python310Packages.jupyterlab-lsp
python311Packages.jupyterlab-lsp

Maintainer pings

@ofborg build python310Packages.jupyterlab-lsp python310Packages.jupyterlab-lsp.passthru.tests

Result of nixpkgs-review pr 225484 run on aarch64-darwin 1

4 packages built:

python310Packages.jupyterlab-lsp
python310Packages.jupyterlab-lsp.dist
python311Packages.jupyterlab-lsp
python311Packages.jupyterlab-lsp.dist


Good scrolling when navigating by moving the cursor

Is your feature request related to a problem? Please describe.
I usually don't use the scroll wheel or page down/up keys to navigate emacs, I skip around by paragraph. This causes the window to snap to the new position, but I would prefer if it scrolled smoothly instead of snapping, like this package does when scrolling with the scroll wheel or page down/up keys.
Describe the solution you'd like
When the window snaps to the new position, it could be snapped back to where it was (or as far back as possible while keeping the cursor inside the window), and then running the regular good-scroll movement logic to move smoothly to where the window was originally snapped.
Describe alternatives you've considered
Entirely reimplementing the window snapping that happens when moving around with the cursor, so that it uses the good-scroll scrolling functionality straight away. However, this seems like it would require a lot of replacing functionality that isn't needed by the solution above.
Additional context
This feature feels like it would be better off being its own package, but on the other hand, good-scroll has scrolling logic that I think would be beneficial to share with this feature. In any case, I've implement a sort-of-working proof of concept in my fork, but it still requires some tweaking, and might be overall relatively misguided, as it's the first elisp thing I've written. The actual functionality also looks a little weird when scrolling a lot (out-pacing the smooth scrolling), but I think that's a necessary side-effect of the solution I came up with.
And finally, thank you for writing this package, it's made my daily emacs use a much nicer experience!

Don't have anything useful to contribute atm, but just chiming in that this would be a fantastic feature! I hadn't checked out good-scroll in a while, but coming back to it I'm elated to see how good it is now, and with this feature it would definitely be the ideal package!

I pushed what I have so far to the cursor-scrolling branch. What's confusing is something's setting (point) to a value less than (window-start) in between window-scroll-functions and good-scroll--render. This causes an error when moving the cursor backwards one line when it's at the top of the window. I haven't figured out so far what's trying to move the cursor between the end of window-scroll-functions and the beginning of good-scroll--render. It might be related to Bug #22404.

I think the point movement inside window-scroll-functions/good-scroll--after-window-scroll is being reset, possibly by the C redisplay code. This happens with both Emacs 27.2 and df2438d3695e065d4037e1c26a0c769c373f914c (the latest git commit).

Yeah, seems to be reverted at the very end of redisplay_window() in xdisp.c.


New HXE Tutorials for July 2017

This includes tutorials for HXE for python, ruby, golang and nodejs (outside of XSA). They cover web frameworks such as Flask, Express, Ruby-Sinatra and more. And it covers deploying to Cloud Providers GCP, AWS and Azure.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.csoane seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


request: ability to save temp files as jpgs

Would it be possible to make an option to change the format of the temp images? I use the image stacks and import them into my video editor, but for long videos the hires PNG files I use take up a ton of space. I'd like to tell the program to save them out as jpgs if possible as that would make things a lot easier to manage. Thanks.

Hi @kellyluck, thanks for the suggestion. It makes sense to have such option, I will add it later today :)


Data Model Update

Overview
This will redo the current Data Model on the Pilosa website. It is reorganizing the structure of the page and providing more explanation.
Pull request checklist

[x] I have read the contributing guide.
[x] I have agreed to the Contributor License Agreement.
[x] I have updated the documentation.
[x] I have resolved any merge conflicts.
[x] I have included tests that cover my changes.
[x] All new and existing tests pass.
[ ] Make sure PR title conforms to convention in CHANGELOG.md.
[ ] Add appropriate changelog label to PR (if applicable).

Code review checklist
This is the checklist that the reviewer will follow while reviewing your pull request. You do not need to do anything with this checklist, but be aware of what the reviewer will be looking for.

[ ] Ensure that any changes to external docs have been included in this pull request.
[ ] If the changes require that minor/major versions need to be updated, tag the PR appropriately.
[ ] Ensure the new code is properly commented and follows Idiomatic Go.
[ ] Check that tests have been written and that they cover the new functionality.
[ ] Run tests and ensure they pass.
[ ] Build and run the code, performing any applicable integration testing.
[ ] Make sure PR title conforms to convention in CHANGELOG.md.
[ ] Make sure PR is tagged with appropriate changelog label.

Switching to "bitmaps" and "records" would be kinda funny, but that's preferable to the situation where rows/columns have the opposite meaning in pilosa vs molecula.


MP talk at GeeCon - A different flavor of the distributed transaction

Conference Name:
GeeCon Prague 2019
Conference website and social media links:
https://2019.geecon.cz
https://twitter.com/GeeCON
Talk name:
A different flavor of the distributed transaction
Talk Link:
https://2019.geecon.cz/speakers/?id=580
Date and time: Oct 18, 10:10 - 11:00, Room 4
Speaker Names:
Martin Štefanko (or Stefanko :)), a software engineer at Red Hat
Tweet Message:
either retweet please https://twitter.com/GeeCON/status/1181114171917778944
or something generic will be fine.

@xstefank
Dobrý den,
All good to go.  I will schedule it on social media to go out a couple times.

Tweet:
Join Martin Štefanko @xstefank @GeeCON where he will present "A different flavor of the distributed transaction” Oct 18, 10:10 - 11:00, Room 4, Prague Czech Republic
@MicroProfileIO #opensource #OSS #MicroProfile

@rstjames Thanks a lot!


Check spelling using GitHub Actions + Baseline

Opening as a draft PR to prevent bringing in a wide audience of reviewers. It might be necessary to use admin capabilities to merge this one.
This PR:

Sets baseline spelling configs

Use root cspell.json for words that appear correctly spelled and are seen in 10 or more services
Use specification/<service>/cspell.json for other errors, flattened to list words instead of targeting specific files with overrides

Update documentation
Uses GitHub Actions to run spell check:

In PRs on changed files
On all specification/ files when pushing to targeted branches (matching TSV - All config), a schedule, or when run manually

Example PR with spelling error (PR):

Workflow run for same PR with no spelling error (workflow run):

Check Spelling - All runs:

With error: https://github.com/danieljurek/azure-rest-api-specs/actions/runs/12286391575/job/34286427815
Without error: https://github.com/danieljurek/azure-rest-api-specs/actions/runs/12286201345

Future improvements to Invoke-Cspell.ps1 should include the ability to silence the entire list of files checked.

There is currently a merge conflict because of contention in the custom-words.txt file. I'll establish a new baseline before merging this PR.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.AwsConnector


support AWS STS assume role feature

This is support PR for AWS Security Token Service's "assume role" feature.
Here is the primary PR with technical info: https://github.com/ManageIQ/manageiq-providers-amazon/pull/538
Here is UI PR with pictures: https://github.com/ManageIQ/manageiq-ui-classic/pull/5621
I would like to avoid current PR, since it introduces Amazon-related code in a core repo, but other options should require much more coding, quite big refactoring, as I think, so I'm trying to be simple.

@agrare Adam, that's the second part of "assume role" story, I'm not sure who to ask to review it, can you please help?


fix: clean command not finding rimraf

When I tried to run the build command in the monorepo, I got the following error:
medusa-plugin-strapi-ts: ><EMAIL_ADDRESS>clean
medusa-plugin-strapi-ts: > ./node_modules/.bin/rimraf dist/ types/ services/ models/ migrations/ api/ subscribers/ utils/ index.js index.map.js
medusa-plugin-strapi-ts: sh: ./node_modules/.bin/rimraf: No such file or directory

That's because rimraf was installed in the root of the monorepo rather than in the medusa-plugin-strapi-ts package.
By changing the command to use npx, the path to rimraf will be inferred without having to guess where it's located.

@shahednasser can you please rebase on to the development branch

@SGFGOV done!

@shahednasser thank you. Will you be able to fix the integration test also? There seems to be some issue building the tests


fix(cargo): require tokio 0.2.11

JoinError::is_cancelled was introduced in this version
Closes #2250

You'd need to open the pull request against https://github.com/hyperium/hyper, this is a PR on your fork, which I can't merge into the main repo.


Ability to run an image would be nice

Just selecting over an image and hitting a key (like s) to perform docker run -d {image}.

Implemented in commit 5d5e9bf and should be available in next build


Fix Setting page crash when adapter is deployed.

Notes for Reviewers
This PR fixes #
Before:
https://github.com/meshery/meshery/assets/79860504/ff8a79b0-915b-4756-8fcb-dd2b6d0f5789
After:
https://github.com/meshery/meshery/assets/79860504/176f3838-4e1d-4a45-ae65-58472004279b
Signed commits

[ ] Yes, I signed my commits.

// @leecalcote


Can't install package with dependency group without editable mode

uv version
0.1.6
Platform
Darwin
Description
This works:
pip install ".[dev]"

and this works:
uv pip install -e ".[dev]"

but this doesn't:
uv pip install ".[dev]"

I get
 uv::requirements::from_source source=.[dev]
error: Failed to parse `.[dev]`
  Caused by: Expected package name starting with an alphanumeric character, found '.'
.[dev]
^

when running with --verbose.
I'm installing my package from a pyproject.toml and the dependency groups are defined under [project.optional-dependencies].

Thanks, this is a duplicate of https://github.com/astral-sh/uv/issues/313. You can use uv pip install "package-name @ .[dev]" for now, but we'll lift this restriction in the future.

This is supported as of v0.1.24. You can uv pip install .[dev] directly, without including a package name.


feat: add feed image to readme

Fix for https://linear.app/knock/issue/KNO-230/add-in-app-feed-screenshot-to-react-feed-readme

@cjbell good to get a quick review on this?


How to fix it? please help me thank you.

When i use AudioPlayer play items(queue) the player have error.
follow :

code :

Hey,
From what I see, your URL has a custom scheme and is not HTTP(s)? Could you confirm?

Hello,
The solution is to change:
URL(string: mediaDatas[i]["url_media"].stringValue)!
to
URL(fileURLWithPath: mediaDatas[i]["url_media"].stringValue)!
Reason is that you need to play local file, i guess...

Well if your file is local then yes.


Search results URL are wrong

When ever I search for a phrase in the documentation, the results links are coming back with wrong URL. It seems that they don't consider multi level. Also the URL comes with readthedocs.org domain and not the our domain. Is this a bug or we missing configuration?

Seems to work ok for the pip project: https://pip.pypa.io/en/stable/search.html?q=setuptools&check_keywords=yes&area=default
Can you provide us with a link to a malfunctioning search?

Yes, I see it is working for you.
In http://docs.backand.com search for ORM, the result looks different (doesn't use the highlight cool feature) and if you click on the link to the page you see it is broken.
Thanks for the help

Ok thanks for the example. I assume the reason is that there is no specific theme for a mkdocs based documentation. However it should ofcourse take the configured CNAME into account. We'll need to have a look there.

I think we can't address this issue currently in a proper way as readthedocs.org does not know anything about configured CNAMEs. I created #1632 as a new issue in order to propose some way to configure the "main" domain that should be used to link to a project's documentation.

How can I setup the search to return results with highlighted text and not in the way it is now.
Regarding the CNAME, the URL is broken not just because of the domain name but also it doesn't include folder structure (try to replace the result domain with docs.backand.com and still remain broken).

Thanks for pointing out the broken links! I missed that in the first look through. I've opened #1633 to track it separately.
Regarding the highlighting: the text is actually highlighted, but only by making it italic:

You can see the word ORM being in italic.
Actually while writing this, I realized that you mean the highlighting of the words when following the link from the search to the docs, right? For example, the following link should highlight the word "database", correct? http://backand-docs.readthedocs.org/en/latest/?highlight=database

Yes, database was supposed to be highlight

That feature did not exist so far for mkdocs projects. I created #1640 to suggest an implementation of this.

Seems like there have been three main points in this ticket that we did split out into:

#1632
#1633
#1640

I'm closing this ticket as we have the other three open to track the individual progress.
@itayher I hope this addresses all of your issues. Respond here if I have forgotten something.


Adding nightly

Once this completes, I'll update the image references to point to istionightly.
I think we can combine lint/build in a single circleci job - in istio/istio things are super slow and need to be in parallel, hopefully we'll not end up in the same state in this repo.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: rshriram
If they are not already assigned, you can assign the PR to them by writing /assign @rshriram in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Can someone with the merge button merge this?
Not sure why helm lint is failing like this:


Fix RefSpec.Src()

Previously, the Src() function was assuming there are no “+” characters in the refspec src
and erroneously used the strings.Index() function to compute the start index of src in the
refspec.  This change now uses the IsForceUpdate() method to decide how to elide the
force update token.
Signed-off-by: Alan Cabrera<EMAIL_ADDRESS>

So, I don't have karma to merge the request.  Can someone do that for me?

May thanks!


Excitatory neuron currently only has retinal bipolar neuron under it

This is definitely not right as most glutamatergic neurons are excitatory - problem being not ALL glutamatergic neurons are excitatory, and not all excitatory neurons are glutamatergic neurons (I can't give an example off my head, but im 100% sure I've learnt that developmental period GABA/Glut Inhibitatory/excitatory is not as straightforward a dichotomy
Will need to think about how to handle this

CL call decision:
obsolete excitatory and inhibitory, as these are too difficult to populate
HOWEVER - check if any downstream is affected first

Hello,
The "excitatory neuron" term was used to annotate some datasets submitted for the ENCODE project prior to the term's deprecation: https://www.encodeproject.org/search/?type=Experiment&biosample_ontology.term_name=excitatory+neuron
Does CL have any further information about the decision to remove this term? We spoke briefly with some of the labs involved and are concerned that the suggested replacement "glutamatergic neuron" is overly specific for our use case, whereas the superclass "neuron" would be overly general. Any additional info would help us decide how to resolve our use of the obsolete term.
Thank you in advance!

Hi @jenjou - our concern with excitatory neuron is that we need to manually populate these (for the same reason why glutamatergic neuron is overly specific for your use case. If we have excitatory neuron, we are not confident in properly populating it completely, which would be problematic for the ontology. I do however understand that it might be required for annotation, and I wonder if there is a possibility of more specific terms, the obvious one being glutamatergic neurons where appropriate.
I'm happy to bring this up in the next CL call (which happens to be tmr), but perhaps you can help us by letting us know the use case for the term, or rather a case where you need excitatory neurons but glutamatergic neurons is too specific. I see mostly RNA-seq based experiments in the link you gave, in which case, from my understand, excitatory mainly means glutamatergic no? (ie RNA sequencing doesn't tell you the excitatory or inhibitory nature of a cell, but instead tells you biomarkers of cell types that, for example, express glutamate). I'm not sure if there are some techniques that I am unaware of that filters out excitatory neurons specifically, in which case that's a good argument for having something like excitatory neurons.
Thanks

Thanks for the explanation! We'll need to reach out to the labs to get more detailed information about these samples -- I'm not sure we'll have a follow up by tomorrow, but I will reach out again if we have more specifics on the methods used.

@dosumis and I think it was a mistake to obsolete these.
Rather than re-open this ticket, I made a new one https://github.com/obophenotype/cell-ontology/issues/2083 with some additional observations in it


Unicode ligatures and combining characters not displaying properly

Many South and Southeast Asian scripts make frequent use of ligatures and combining characters, which are not rendering properly. Examples of Oriya, Khmer and Dzongkha below:

There are problems with ligatures and combining characters in all of the above screenshots, but that seems to be downstream of maplibre/maplibre-gl-js#50.
Originally posted by @claysmalley in https://github.com/ZeLonewolf/openstreetmap-americana/pull/801#discussion_r1141519934

I have a proof of concept for a fix in 1ec5/maplibre-gl-js#1. It needs a bit of cleanup and requires some major changes to How Things Have Always Been Done, so it’ll need some discussion before I can formally move forward with it.


How to create Ollivander

Hello, I activate the example of harry potter, The server give me the ticket but I don't find how to create the npc of Ollivander to change the ticket for a wand.

Thanks and sorry for my bad english.

With a Citizens NPC selected, perform the following commands:
'''
/trait magic
/mtrait ollivander
'''

Thanks, you're nice


Missing images in search results

Sometimes images are not showing up next to their story in the results list.
For example, see this story on the support site.
Then search for guid 83b6d846-d6ae-4b74-ac3a-8992e7dea39d in the plugin (an NPR story in api-production).  The image is missing.

Also seeing on some PRX content, such as - https://support.pmp.io/search?text="1405%3A Cops%2C Dumpster Diving%2C and Mental Illness"&profile=story

Note: this bug probably also affects featured images.

Another note: for some PRI's The World stories, you can probably expect to see null images in the attached items.  These are Reuter's images that you don't have permission to use.  (But the support site WILL show them, as it runs as an all-access user).

It looks like this is happening because the only enclosures available for the stories mentioned do not match any of the crop sizes that we give preference. See: https://github.com/publicmediaplatform/pmp-wordpress/blob/master/assets/js/pmp.js#L102
For the first example, I'm only seeing crops enlargement and custom. For the PRX example, only medium.
So, it sounds like we need a more robust fallback strategy here.
Also interesting to note -- despite there being no thumbnail shown in the search results, creating a draft based on the PRX story example does result in a featured image being pulled in. This is not the case for the first example, though. Is this what you're referring to when you say this bug probably also affects featured images?

My strategy has been to start with a list of "known" crops, then if you can't match one of those, just grab the first image 'links.enclosure[0].href` as a backup.
I think I was just guessing that the "featured image" code would have the same problem.  But maybe it doesn't.

Excellent. Makes sense to me.
I believe this is fixed now. See: c061dba7340db3af467cc14150fbdd9f98787029.
Also see sort-of related: 89add440795ae0de1f869b1fce0a43149207cc0b. I added this because I noticed a max_input_vars warning when sending info to the server as url encoded form data. This fixes an issue where, when creating a draft or publishing a post, everything except for the featured image makes its way into WordPress.


Icon Packs

Hello, I'm hoping to fully move over from Visual Studio Code however there's one thing I'd like to know before I do so.
Is there a possibility to have 'icon packs'?
Like Material Icon Theme except for lite, just so we can spice the icons up a bit more!
Thanks-
Ryan

Use https://github.com/lite-xl/lite-xl with nonicons plugin.


Minor Error

I am getting this Error.

I fixed it and more in my forked repository -
here is a link to my fork
Hope it will help you


Add explanation of flat priors

Flat priors aren't well explained.
From @johndcook There are many approaches to this problem. Here are three.

The subjective Bayes approach says the prior should simply quantify what is known or believed before the experiment takes place. Period. End of discussion.
The empirical Bayes approach says you can estimate your prior from the data itself. (In that case your "prior" isn't prior at all.)
The objective Bayes approach says to pick priors based on mathematical properties, such as "reference" priors that in some sense maximize information gain. Jim Berger gives a good defense of objective Bayes here.
In practice someone may use any and all of these approaches, even within the same model. For example, they may use a subjective prior on parameters where there is a considerable amount of prior knowledge and use a reference prior on other parameters that are less important or less understood.
Often it simply doesn't matter much what prior you use. For example, you might show that a variety of priors, say an optimistic prior and a pessimistic prior, lead to essentially the same conclusion. This is particularly the case when there's a lot of data: the impact of the prior fades as data accrue. But for other applications, such as hypothesis testing, priors matter more.
Definition: A prior distribution is non-informative if the prior is “flat”
relative to the likelihood function.

We chose these priors because in this case we are trying to have as little impact on the posterior distribution as possible. We are trying to have a reasonable model and let inference happen from the data set.

Added explanation


Fix dropdown docs about autoclose and esc key.

Fixes #35756.

LGTM

According to our js code, ESC event is independent of autoClose option, so we are fine

Thanks for the quick review and merge.


Incorrect, can you add how to do this using GPP's as Microsoft recommend not using the Templates for Root Certificates

Hi,
We used the method explained on this page to add the cert for Microsoft Configuration Manager to Trusted Root certification authority, and it has worked for a long time, however we have been getting a lot of errors over past months.
It is documented in the following document (link further down) that you should NOT use the Admin Templates to distribute the cert even though that is how we've done it for the past 20 years.  Currently we are seeing around 5% of our machines failing to deploy M365 updates with the cert error and this tracks back to the information in the link below.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/valid-root-ca-certificates-untrusted
bit of background
the error that occurs when you deploy your M365 app updates via config Manager is
800B0109A - "certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider."
this appears in several of the MCM logs and if you enable the Capi2 log in event logs and run a check for updates, it will also show there.
the point is that this is no longer the appropriate way to add the cert and the cert should be added using the GPP option detailed in that link - apparently.

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

ID: f13fd851-31ac-05a2-f1f1-642f5d59fcd7
Version Independent ID: 35f0e42d-a950-ce93-0f7c-11784a6623fd
Content: Distribute Certificates to Client Computers by Using Group Policy
Content Source: WindowsServerDocs/identity/ad-fs/deployment/Distribute-Certificates-to-Client-Computers-by-Using-Group-Policy.md
Product: windows-server
Technology: ad-fs
GitHub Login: @billmath
Microsoft Alias: billmath

This statement is inaccurate "the point is that this is no longer the appropriate way to add the cert and the cert should be added using the GPP option detailed in that link"  The text in https://learn.microsoft.com/en-us/windows-server/identity/ad-fs/deployment/distribute-certificates-to-client-computers-by-using-group-policy should be left as is as the Troubleshooting article is explicitly meant for correcting an issue caused by certain conditions in a subset of customer's environments.

We hugely appreciate your contribution, feedback, and support to our technical documentation.
We’ve phased out GitHub Issues on this repository as the feedback mechanism for content and have replaced it with a new feedback system. For more information see, Content User Feedback. As part of this rollout, we are migrating your issue where our team will use your comments to improve the documentation experience. Unfortunately, this does mean you won't be able to access this issue after the migration is complete.
All issues will be migrated by Thursday 29th August 2024.
Once again, thank you for your valuable feedback, we hope you’ll continue to contribute using our new feedback system.


iOS Label: remove one-line limitation

UILabel defaults to numberOfLines = 1 which is bad, mmkay

Resolves #48

Seems legit :+1:


Consider ResourceAttributes add k8s.node.ip and k8s.pod.ip

Area(s)
area:k8s
Is your change request related to a problem? Please describe.
ResourceAttributes add k8s.node.ip and k8s.pod.ip  Quickly locate the host
Describe the solution you'd like
ResourceAttributes add k8s.node.ip and k8s.pod.ip  Quickly locate the host
Add node and pod ip env vars automatically
Add node IP and pod IP to env vars automatically.
Describe alternatives you've considered
No response
Additional context
No response

We have a new issue for this, so I will close this as duplicated: https://github.com/open-telemetry/semantic-conventions/issues/1160


Bug Report

Use newest verison of Firefox
Only audio is playing and screen is black
Versions of DPlayer is 1.26.0-1, Firefox on Linux/Windows/Android

Unable to reproduce, please provide the minimum reproduction demo


fix: 'react/bridging/CallbackWrapper.h' file not found

This PR fixes build error: 'react/bridging/CallbackWrapper.h' file not found
Changes
This PR adds s.dependency "ReactCommon" to VisionCamera.podspec
Tested on
* iPhone 15, iOS 17.3.1

Related issues
* Fixes #2603

@mrousavy I've created a PR adding this:
https://github.com/mrousavy/react-native-vision-camera/pull/2620

Hey - sorry for the late reply, but I don't think this is needed anymore. I separated VisionCamera into three subspecs :)


Hypothesis plugin raises ZeroDivisionError for no apparent reason

Checks

[X] I added a descriptive title to this issue
[X] I have searched (google, github) for similar issues and couldn't find anything
[X] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
...

I'm developing a library using pydantic. While testing some code with hypothesis, i encountered an error stemming from the pydantic plugin - which i do not actually use.
E   ZeroDivisionError: float division by zero

pydantic/_hypothesis_plugin.py:298: ZeroDivisionError

Note, my own code handles zeros without raising an error at all - and the following test works without issue:
def test_handle_constrained_float_handles_multiple_of_zero_value():
    assert handle_constrained_float(confloat(multiple_of=0), faker) == 0

I second this. This occurs without even using the floats strategy, or builds on a Pydantic Model with float fields. Just importing hypothesis.given with the Pydantic plugin active causes it.

Cc @Zac-HD

Python 3.10.4 with hypothesis 6.45.0 and pydantic 1.9.0:
from hypothesis import given
<frozen importlib._bootstrap>:1027: in _find_and_load
    ???
<frozen importlib._bootstrap>:1006: in _find_and_load_unlocked
    ???
<frozen importlib._bootstrap>:688: in _load_unlocked
    ???
/usr/local/lib/python3.10/site-packages/_pytest/assertion/rewrite.py:168: in exec_module
    exec(co, module.__dict__)
/usr/local/lib/python3.10/site-packages/hypothesis/__init__.py:56: in <module>
    run()
/usr/local/lib/python3.10/site-packages/hypothesis/entry_points.py:63: in run
    hook = entry.load()
/usr/local/lib/python3.10/importlib/metadata/__init__.py:171: in load
    module = import_module(match.group('module'))
/usr/local/lib/python3.10/importlib/__init__.py:126: in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
pydantic/_hypothesis_plugin.py:362: in init pydantic._hypothesis_plugin
    ???
pydantic/_hypothesis_plugin.py:196: in pydantic._hypothesis_plugin._registered
    ???
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/core.py:1809: in register_type_strategy
    elif isinstance(strategy, SearchStrategy) and strategy.is_empty:
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/strategies.py:134: in accept
    recur(self)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/strategies.py:130: in recur
    mapping[strat] = getattr(strat, calculation)(recur)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/lazy.py:88: in calc_is_empty
    return recur(self.wrapped_strategy)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/strategies.py:130: in recur
    mapping[strat] = getattr(strat, calculation)(recur)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/strategies.py:607: in calc_is_empty
    return all(recur(e) for e in self.original_strategies)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/strategies.py:607: in <genexpr>
    return all(recur(e) for e in self.original_strategies)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/strategies.py:130: in recur
    mapping[strat] = getattr(strat, calculation)(recur)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/lazy.py:88: in calc_is_empty
    return recur(self.wrapped_strategy)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/lazy.py:108: in wrapped_strategy
    base = self.function(*self.__args, **self.__kwargs)
/usr/local/lib/python3.10/site-packages/hypothesis/strategies/_internal/numbers.py:359: in floats
    raise FloatingPointError(
E   FloatingPointError: Got allow_subnormal=True, but we can't represent subnormal floats right now, in violation of the IEEE-754 floating-point specification.  This is usually because something was compiled with -ffast-math or a similar option, which sets global processor state.  See https://simonbyrne.github.io/notes/fastmath/ for a more detailed writeup - and good luck!

The bandaid fix that I'm using for now is using daz:
import daz
daz.unset_ftz()
daz.unset_daz()

Oh boy, this is going to be a fun one.

denormals-are-zero violates IEEE-754 semantics, and there's no solution short of tracking down the evil compiler option and turning it back off - as https://simonbyrne.github.io/notes/fastmath/ notes, simply loading a shared library can change the results in completely unrelated code!

multiple_of=0 is inherently invalid, because the jsonschema standard defines multipleOf in terms of division.  Since we're now in the position of dealing with absurdity, the best option for Pydantic is probably to either:

raise an error on multiple_of=0 which explains this issue, or
silently convert it to a constrained number which must be equal to zero based on min and max values

For @Goldziher's test, I would just add from hypothesis import assume and assume(multiple_of != 0) to reject invalid examples.
(after which you'll discover that the modulo approach to multiple_of gives different results, but that's a whole separate semantic issue for whoever has to write that test.  hypothesis-jsonschema was not an easy project 😬)

@Zac-HD If a stack is based on widely-used Docker images, and the PyPi version of both pydantic and Hypothesis, how would you suggest avoiding the error, at least only on import (avoiding usage of floats)?

If "the error" is multiple-of-zero, you could write a PR for Pydantic as I suggest above.  If "the error" is denormals-are-zero, I'd suggest using images that don't compile with unsafe math flags.

We’re no longer actively developing Pydantic V1 (although it will continue to receive security fixes for the next year or so), so we’re closing issues solely related to V1. If you really think this shouldn’t be closed, please comment or create a new issue 🚀.


Rust fails on optional "any" properties

Given this schema
{
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "foo": {}
  }
}

and the input {}, Rust fails:
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ErrorImpl { code: Message("missing field `foo`"), line: 1, column: 2 }', src/libcore/result.rs:906:4
note: Run with `RUST_BACKTRACE=1` for a backtrace.

Test case in this branch: https://github.com/quicktype/quicktype/tree/optional-any

@krk @waywardmonkeys


Feature/activity support

Here we go.
Still not using behaviors. But it works now.
The test producer creates an activity (like this would be an HttpRequest).
Activity.Current.Id: MyGuid
Then a child activity is created, as result of produce.
Activity.Current.Id:  |MyGuid.1   this is sent over the wire.
In the consumer, again a new activity is started.
Activity.Current.Id:  |MyGuid.1.OtherGuid_
That means it behaves exactly like the HttpClient and the WebHost.
Btw. they tuned the documentation a bit. It is now understandable:
https://github.com/dotnet/corefx/tree/master/src/System.Diagnostics.DiagnosticSource/src
EDIT: Is a draft. Do not merge!

(I may not know how to properly reply to a review message, sorry for that)

You know how to do this? I only know how to do this with Serilog..

@msallin I don't know, I don't use NLog. It's in here for historical reasons but I also use Serilog normally. Feel free to switch to Serilog if needed!

Also didn't use Github that much.. So let's find out how to use it...
Okay. I'll do the switch. Should be an easy thing.


Upgrading from v1.0.42 to v2.0.42

Hello!
Im currently updating our cookbook to the newest version with intention to upgrade openshift cluster from 1.4 to 3.7. Currently i've uploaded v2.0.42 to chef server and just target it in environment.
Currently masters and nodes failing with:
ERROR: resource template[/etc/origin/cloudprovider/aws.conf] is configured to notify resource service[origin-node] with action restart, but service[origin-node] cannot be found in the resource collection. template[/etc/origin/cloudprovider/aws.conf] is defined in /var/chef/cache/cookbooks/cookbook-openshift3/recipes/cloud_provider.rb:28:in `from_file'

Fixing it now by adding
service "#{node['cookbook-openshift3']['openshift_service_type']}-node"

to services.rb
I will update this with all the issues i face during the run

Defaults for these attributes has changed
['cookbook-openshift3']['openshift_master_sdn_cluster_network_cidr']
['cookbook-openshift3']['openshift_master_sdn_host_subnet_length']

Hi, yes, there are a subset of attributes that should not be changed. We intend to add more checking to the validate script to ensure that this does not happen on existing clusters. Thanks for raising, it will give us more motivation to pursue that work. Ian

Okay, so i followed upgrade instructions:

Set up upgrade attributes:

cookbook-openshift3:
  control_upgrade:                           true
  control_upgrade_flag:                      /tmp/upgrade-from-14-to-15
  control_upgrade_version:                   15

Created control_upgrade_flag on control plane: etcd and master instances

touch /tmp/upgrade-from-14-to-15

Chef run was successful on all instances.

INFO: Upgrade for MASTERS [STARTED]
...
Upgrade for MASTERS [COMPLETED]
...
Upgrade for NODE [STARTED]
...
Upgrade for NODE [COMPLETED]

After that i removed control_upgrade flags from attributes, and changed main version:

openshift_docker_image_version:            v1.5.1
ose_major_version:                         1.5
ose_version:                               1.5.1-1.el7

Next chef run on all instances except for etcd i got this:

yum_package[origin-master] installing origin-master-1.5.1-1.el7 from centos-openshift-origin15 repository
yum[82106]: Updated: krb5-libs-1.15.1-19.el7.x86_64
yum[82106]: Installed: libtdb-1.3.15-1.el7.x86_64
groupadd[82409]: group added to /etc/group: name=printadmin, GID=989
groupadd[82409]: group added to /etc/gshadow: name=printadmin
groupadd[82409]: new group: name=printadmin, GID=989
yum[82106]: Installed: samba-common-4.7.1-6.el7.noarch
yum[82106]: Installed: avahi-libs-0.6.31-19.el7.x86_64
yum[82106]: Updated: libtevent-0.9.33-2.el7.x86_64
yum[82106]: Installed: libldb-1.2.2-1.el7.x86_64
yum[82106]: Installed: 1:cups-libs-1.6.3-35.el7.x86_64
yum[82106]: Installed: samba-common-libs-4.7.1-6.el7.x86_64
yum[82106]: Installed: libwbclient-4.7.1-6.el7.x86_64
yum[82106]: Installed: samba-client-libs-4.7.1-6.el7.x86_64
yum[82106]: Installed: cifs-utils-6.2-10.el7.x86_64
yum[82106]: Updated: origin-clients-3.9.0-1.el7.git.0.ba7faec.x86_64
yum[82106]: Updated: origin-3.9.0-1.el7.git.0.ba7faec.x86_64
yum[82106]: Installed: origin-node-3.9.0-1.el7.git.0.ba7faec.x86_64
yum[82106]: Updated: 1:openvswitch-2.6.1-3.git20161206.el7.x86_64
yum[82106]: Updated: origin-sdn-ovs-3.9.0-1.el7.git.0.ba7faec.x86_64
yum[82106]: Updated: origin-master-3.9.0-1.el7.git.0.ba7faec.x86_64
yum[82106]: Erased: tuned-profiles-origin-node-1.4.1-1.el7.x86_64
chef-client[40460]: [2018-05-17T18:22:30+00:00] INFO: yum_package[origin-master] installed origin-master at 1.5.1-1.el7

================================================================================
Error executing action `install` on resource 'yum_package[origin-clients]'
================================================================================
Chef::Exceptions::Package
-------------------------
Installed package origin-clients-3.9.0-1.el7.git.0.ba7faec is newer than candidate package origin-clients-1.5.1-1.el7
Cookbook Trace:

any suggestions?

None, I thought that cookbook installes all of them and the picks up correct one based on version I’m installing? I guess I was wrong(
So I MUST set a correct repository in the attributes when I do version upgrade?

Yes you need to. Can you please send over your list of attributes (environment or role?)
I would like to check what you have got setup

You also need to remove the flag stuff... (Just put an underscore before the variable name)
That is why it tries to update again....
cookbook-openshift3:
control_upgrade:                           true
_control_upgrade_flag:                      /tmp/upgrade-from-14-to-15
control_upgrade_version:                   15

chef_type:           environment
cookbook_versions:
  cookbook-openshift3:               = 2.0.42
default_attributes:
  chef_client:
    config:
      chef_server_url: < chef server url >
    interval: 600
    splay:    60
  cookbook-openshift3:
    deploy_containerized:                      false
    deploy_dnsmasq:                            true
    deploy_example:                            false
    docker_version:                            1.10.3-59.el7.centos
    etcd_servers:
      fqdn:      ip-10-239-122-109.ec2.internal
      ipaddress: <IP_ADDRESS>

      fqdn:      ip-10-239-122-158.ec2.internal
      ipaddress: <IP_ADDRESS>

      fqdn:      ip-10-239-122-172.ec2.internal
      ipaddress: <IP_ADDRESS>
    master_servers:
      fqdn:        ip-10-239-122-115.ec2.internal
      ipaddress:   <IP_ADDRESS>
      labels:      region=primary
      schedulable: false

      fqdn:        ip-10-239-122-134.ec2.internal
      ipaddress:   <IP_ADDRESS>
      labels:      region=primary
      schedulable: false

      fqdn:        ip-10-239-122-175.ec2.internal
      ipaddress:   <IP_ADDRESS>
      labels:      region=primary
      schedulable: false
    node_servers:
      fqdn:      ip-10-239-122-141.ec2.internal
      ipaddress: <IP_ADDRESS>
      labels:    region=primary

      fqdn:        ip-10-239-122-115.ec2.internal
      ipaddress:   <IP_ADDRESS>
      labels:      region=primary
      schedulable: false

      fqdn:      ip-10-239-122-100.ec2.internal
      ipaddress: <IP_ADDRESS>
      labels:    region=infra

      fqdn:        ip-10-239-122-134.ec2.internal
      ipaddress:   <IP_ADDRESS>
      labels:      region=primary
      schedulable: false

      fqdn:      ip-10-239-122-153.ec2.internal
      ipaddress: <IP_ADDRESS>
      labels:    region=infra

      fqdn:        ip-10-239-122-175.ec2.internal
      ipaddress:   <IP_ADDRESS>
      labels:      region=primary
      schedulable: false

      fqdn:      ip-10-239-122-177.ec2.internal
      ipaddress: <IP_ADDRESS>
      labels:    region=infra

      fqdn:      ip-10-239-122-101.ec2.internal
      ipaddress: <IP_ADDRESS>
      labels:    region=primary

      fqdn:      ip-10-239-122-174.ec2.internal
      ipaddress: <IP_ADDRESS>
      labels:    region=primary
    oauth_Identities:
      HTPasswdPasswordIdentityProvider
      GitHubIdentityProvider
    openshift_HA:                              true
    openshift_cloud_provider:                  aws
    openshift_cluster_name:                    < internal master elb >
    openshift_common_default_nodeSelector:     region=primary
    openshift_common_public_hostname:          < external master elb >
    openshift_deployment_type:                 origin
    openshift_docker_image_version:            v1.5.1
    openshift_hosted_cluster_metrics:          false
    openshift_hosted_manage_registry:          false
    openshift_master_ca_certificate:
      data_bag_item_name: ca
      data_bag_name:      certificates
    openshift_master_console_url:              < external master elb >
    openshift_master_debug_level:              2
    openshift_master_public_api_url:           < external master elb >
    openshift_master_router_subdomain:         < router domain >
    openshift_master_sdn_cluster_network_cidr: <IP_ADDRESS>/16
    openshift_master_sdn_host_subnet_length:   8
    openshift_node_cadvisor_port:              4194
    openshift_node_debug_level:                2
    openshift_node_image_gc_high_threshold:    60
    openshift_node_image_gc_low_threshold:     50
    openshift_node_max_pod:                    500
    openshift_node_read_only_port:             10255
    ose_major_version:                         1.5
    ose_version:                               1.5.1-1.el7
description:         qa-001-us-east-1 environment
json_class:          Chef::Environment
name:                qa-001-us-east-1

Im trying to rollback packets to v1.4 but chef keeps installing latest packets v3.9.0
I checked available packets with yum search --showduplicates origin-node
origin-node-1.4.1-1.el7.x86_64 : Origin Node
origin-node-1.5.1-1.el7.x86_64 : Origin Node
origin-node-3.6.0-1.0.c4dd4cf.x86_64 : Origin Node
origin-node-3.6.1-1.0.008f2d5.x86_64 : Origin Node
origin-node-3.7.0-1.0.7ed6862.x86_64 : Origin Node
origin-node-3.7.1-1.el7.git.0.0a2d6a1.x86_64 : Origin Node
origin-node-3.7.1-2.el7.x86_64 : Origin Node
origin-node-3.8.0-1.el7.git.0.dd1558c.x86_64 : Origin Node
origin-node-3.9.0-1.el7.git.0.ba7faec.x86_64 : Origin Node
origin-node-3.9.0-1.el7.git.0.ba7faec.x86_64 : Origin Node

something weird in dependencies
yum install origin-node-1.4.1-1.el7
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: packages.oit.ncsu.edu
 * epel: ewr.edge.kernel.org
 * extras: mirror.ash.fastserv.com
 * updates: mirror.ash.fastserv.com
Resolving Dependencies
--> Running transaction check
---> Package origin-node.x86_64 0:1.4.1-1.el7 will be installed
--> Processing Dependency: tuned-profiles-origin-node = 1.4.1-1.el7 for package: origin-node-1.4.1-1.el7.x86_64
--> Processing Dependency: origin = 1.4.1-1.el7 for package: origin-node-1.4.1-1.el7.x86_64
--> Running transaction check
---> Package origin.x86_64 0:1.4.1-1.el7 will be installed
--> Processing Dependency: origin-clients = 1.4.1-1.el7 for package: origin-1.4.1-1.el7.x86_64
---> Package origin-node.x86_64 0:3.9.0-1.el7.git.0.ba7faec will be installed
--> Processing Dependency: origin = 3.9.0-1.el7.git.0.ba7faec for package: origin-node-3.9.0-1.el7.git.0.ba7faec.x86_64
--> Running transaction check
---> Package origin.x86_64 0:1.4.1-1.el7 will be installed
---> Package origin.x86_64 0:3.9.0-1.el7.git.0.ba7faec will be installed
--> Processing Dependency: origin-clients = 3.9.0-1.el7.git.0.ba7faec for package: origin-3.9.0-1.el7.git.0.ba7faec.x86_64
---> Package origin-clients.x86_64 0:1.4.1-1.el7 will be installed
--> Running transaction check
---> Package origin-clients.x86_64 0:3.9.0-1.el7.git.0.ba7faec will be installed
--> Finished Dependency Resolution

Dependencies Resolved

can you : 'ls -l /etc/yum.repos.d'

ls -l /etc/yum.repos.d
total 52
-rw-r--r--. 1 root root 1664 Dec  9  2015 CentOS-Base.repo
-rw-r--r--. 1 root root 1309 Dec  9  2015 CentOS-CR.repo
-rw-r--r--. 1 root root  649 Dec  9  2015 CentOS-Debuginfo.repo
-rw-r--r--. 1 root root  630 Dec  9  2015 CentOS-Media.repo
-rw-r--r--. 1 root root 1331 Dec  9  2015 CentOS-Sources.repo
-rw-r--r--. 1 root root 1952 Dec  9  2015 CentOS-Vault.repo
-rw-r--r--. 1 root root  290 Dec  9  2015 CentOS-fasttrack.repo
-rw-r--r--. 1 root root  259 Apr 20  2017 centos-openshift-origin.repo
-rw-r--r--. 1 root root  265 May 17 10:56 centos-openshift-origin14.repo
-rw-r--r--. 1 root root  265 May 17 18:21 centos-openshift-origin15.repo
-rw-r--r--. 1 root root  240 Apr 20  2017 datadog.repo
-rw-r--r--. 1 root root 1056 Dec 27  2016 epel-testing.repo
-rw-r--r--. 1 root root  957 Dec 27  2016 epel.repo

Can you cat centos-openshift-origin.repo ?

cat /etc/yum.repos.d/centos-openshift-origin.repo
# This file was generated by Chef
# Do NOT modify this file by hand.

[centos-openshift-origin]
name=Centos-openshift-origin aPaaS Repository
baseurl=http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin/
enabled=1
fastestmirror_enabled=0
gpgcheck=0

That is your issue get rid of it :-1:
It has got too many packages

any idea where it came from?
this cluster was setup using this cookbook at v1.10.42
is this what you used back then?

I do not know. I believe before we did not know what we were doing :-)
Thanks to @ianmiell we have put a lot of effort on our tests and QA.

okay, so i reverted cluster to a initial state on v1.4
i ran oc adm diagnostics and everything passed
i've added control upgrade attributes back to environment in chef
    control_upgrade:                           true
    control_upgrade_flag:                      /tmp/upgrade-from-14-to-15
    control_upgrade_version:                   15

all chef run succeed, but nothing upgraded
i checked /etc/yum.repos.d/ and there's no repo for 1.5, only for 1.4
am i missing something again?

i've added upgrade_repos for the attributes:
    upgrade_repos:
      baseurl:  http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin15/
      gpgcheck: false
      name:     centos-openshift-origin15

but nothing changed(
chef just won't add this repo:
...
Recipe: cookbook-openshift3::packages
  * yum_repository[centos-openshift-origin14] action create
    * template[/etc/yum.repos.d/centos-openshift-origin14.repo] action create (up to date)
    * execute[yum clean metadata centos-openshift-origin14] action nothing (skipped due to action :nothing)
    * execute[yum-makecache-centos-openshift-origin14] action nothing (skipped due to action :nothing)
    * ruby_block[yum-cache-reload-centos-openshift-origin14] action nothing (skipped due to action :nothing)
     (up to date)
Recipe: cookbook-openshift3::upgrade_control_plane15
  * execute[Disable origin-excluder (Best effort < 3.5)] action run (skipped due to only_if)
  * execute[Disable origin-docker-excluder (Best effort < 3.5)] action run (skipped due to only_if)
  * log[Upgrade for MASTERS [STARTED]] action write
...

Starting investigating. Will come back to you ASAP.

control_upgrade: true
control_upgrade_version: '15'
control_upgrade_flag: "/tmp/ready15"
upgrade_repos:
- name: centos-openshift-origin15
  baseurl: http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin15/
  gpgcheck: false

@tpolekhin You missed a '-' on the upgrade_repos. It should be an array not a hash.
upgrade_repos:
- baseurl: 'http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin15/'
gpgcheck: false
name:     'centos-openshift-origin15'

This is just how knife show outputs it. I Json it is array with {} object inside

knife environment show qa-001-us-east-1 --format json
"default_attributes": {
    "cookbook-openshift3": {
      "control_upgrade": true,
      "control_upgrade_version": "15",
      "control_upgrade_flag": "/tmp/upgrade-from-14-to-15",
      "upgrade_repos": [
        {
          "gpgcheck": false,
          "name": "centos-openshift-origin15",
          "baseurl": "http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin15/"
        }
      ],

I have created a 1.4 cluster and run an upgrade to 1.5 (Everything worked as expected so I need to check what is wrong with your setup.
Recipe: yum::default

yum_globalconfig[/etc/yum.conf] action create

template[/etc/yum.conf] action create (up to date)
(up to date)
Recipe: cookbook-openshift3::packages

yum_repository[centos-openshift-origin15] action create

template[/etc/yum.repos.d/centos-openshift-origin15.repo] action create

create new file /etc/yum.repos.d/centos-openshift-origin15.repo
update content in file /etc/yum.repos.d/centos-openshift-origin15.repo from none to a97776
--- /etc/yum.repos.d/centos-openshift-origin15.repo	2018-05-18 08:29:40.346105280 +0100
+++ /etc/yum.repos.d/.chef-centos-openshift-origin1520180518-4071-1hf7ny8.repo	2018-05-18 08:29:40.345105278 +0100
@@ -1 +1,10 @@
+# This file was generated by Chef
+# Do NOT modify this file by hand.

+[centos-openshift-origin15]
+name=Centos-openshift-origin15 aPaaS Repository
+baseurl=http://mirror.centos.org/centos/7/paas/x86_64/openshift-origin15/
+enabled=1
+fastestmirror_enabled=0
+gpgcheck=0

change mode from '' to '0644'
restore selinux security context

execute[yum clean metadata centos-openshift-origin15] action run

execute yum clean metadata --disablerepo=* --enablerepo=centos-openshift-origin15

execute[yum-makecache-centos-openshift-origin15] action run

execute yum -q -y makecache --disablerepo=* --enablerepo=centos-openshift-origin15

ruby_block[yum-cache-reload-centos-openshift-origin15] action create

execute the ruby block yum-cache-reload-centos-openshift-origin15

execute[yum clean metadata centos-openshift-origin15] action nothing (skipped due to action :nothing)
execute[yum-makecache-centos-openshift-origin15] action nothing (skipped due to action :nothing)
ruby_block[yum-cache-reload-centos-openshift-origin15] action nothing (skipped due to action :nothing)

Recipe: cookbook-openshift3::upgrade_control_plane15

execute[Disable origin-excluder (Best effort < 3.5)] action run (skipped due to only_if)

execute[Disable origin-docker-excluder (Best effort < 3.5)] action run (skipped due to only_if)

log[Upgrade for ETCD [STARTED]] action write

execute[Generate etcd backup before upgrade] action run

execute etcdctl backup --data-dir=/var/lib/etcd --backup-dir=/var/lib/etcd-pre-upgrade15

execute[Copy etcd v3 data store (PRE)] action run

execute cp -a /var/lib/etcd/member/snap/db /var/lib/etcd-pre-upgrade15/member/snap/

execute[Copy etcd v3 data store (PRE)] action nothing (skipped due to action :nothing)
Recipe: cookbook-openshift3::etcd_packages

yum_package[etcd] action install (up to date)

yum_package[etcd] action install (up to date)

cookbook_file[/etc/profile.d/etcdctl.sh] action create (up to date)
Recipe: cookbook-openshift3::etcd_cluster

iptables_rule[firewall_etcd] action enable

What did you do to run upgrade?
What i did is added control_upgrade attributes as above,
and created flag files on etcd and master nodes touch /tmp/upgrade-from-14-to-15
Is that suppose to be enough?

moved control_upgrade attributes from default_attributes to override_attributes in environment to mach the example. did not helped

@tpolekhin Would it help if we can talk directly? can you send me your email?

The issue with chef upgrade logic was in outdated version of chef-client v12.11.18
After upgrading chef-client version to v12.17.44 upgrade logic works as expected

Feel free to ping us when needed :+1:
Thanks for your feedback we shall add more checks to it. #243 has been created to cover that matter/

post here for consistency:
after upgrade to 3.6 origin-node process fails with:
failed to run Kubelet: failed to create kubelet: misconfiguration: kubelet cgroup driver: "systemd" is different from docker cgroup driver: "cgroupfs"
docker version
Client:
 Version:         1.10.3
 API version:     1.22
 Package version: docker-common-1.10.3-59.el7.centos.x86_64
 Go version:      go1.6.3
 Git commit:      3999ccb-unsupported
 Built:           Thu Dec 15 17:24:43 2016
 OS/Arch:         linux/amd64

Server:
 Version:         1.10.3
 API version:     1.22
 Package version: docker-common-1.10.3-59.el7.centos.x86_64
 Go version:      go1.6.3
 Git commit:      3999ccb-unsupported
 Built:           Thu Dec 15 17:24:43 2016
 OS/Arch:         linux/amd64

cat /usr/lib/systemd/system/docker.service
...
ExecStart=/usr/bin/docker-current daemon \
          --exec-opt native.cgroupdriver=systemd \
...

tried to upgrade docker version to 1.12.6 but failed to find packets for docker in origin repos
i have a feeling that i saw docker packets before in origin repos, maybe they got removed...

this guy has a similar issue with docker 1.12 not available in centos repos anymore
https://github.com/openshift/openshift-ansible/issues/8342

found docker-1.12.6 http://vault.centos.org/7.3.1611/extras/x86_64/Packages/

@tpolekhin I forgot to tell you yesterday to remove the line:
docker_version:                            1.10.3-59.el7.centos
You do not need that repository.
The only thing you need is located within the extra repository (Should be there by default)
In case it is not:
#additional packages that may be useful
[extras]
name=CentOS-$releasever - Extras
mirrorlist=http://mirrorlist.centos.org/?release=$releasever&arch=$basearch&repo=extras&infra=$infra
#baseurl=http://mirror.centos.org/centos/$releasever/extras/$basearch/
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7

Extras has only docker 1.13.1 - is this what I should have now? One of my guys that runs rhel openshift said that docker 1.13 breaks everything

No it is fine.
Will be suitable as you are upgrading 1.5 3.6 etc..
On Sat, 19 May 2018, 10:14 Tymofii Polekhin<EMAIL_ADDRESS>wrote:

Extras has only docker 1.13.1 - is this what I should have now? One of my
guys that runs rhel openshift said that docker 1.13 breaks everything
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/IshentRas/cookbook-openshift3/issues/241#issuecomment-390391754,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH0-B7epaMQParspyzrqGD9BUOLK2Pseks5tz-JlgaJpZM4UC1vG
.

Okay, thanks!

faced this issue after upgrading from 1.5 to 3.6
https://bugzilla.redhat.com/show_bug.cgi?id=1467775
tried to clean everything out(except for etcd) and reinstall - no luck(
any suggestions?

Hey,
Sorry for my late reply as I have been busy with other topics.
Look I am available when you are.
Just let me know when it is convenient and I am going to help/assist
you debug that problem.
William
On Mon, 2018-05-21 at 14:40 +0000, Tymofii Polekhin wrote:

faced this issue after upgrading from 1.5 to 3.6
https://bugzilla.redhat.com/show_bug.cgi?id=1467775
tried to clean everything out(except for etcd) and reinstall - no
luck(
any suggestions?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.

upgrade from 3.6 to 3.7 fails on first master with:
Recipe: cookbook-openshift3::upgrade_control_plane37_part2
  * log[Pre master upgrade - Upgrade all storage] action write

  * execute[Confirm OpenShift authorization objects are in sync] action run
    - execute /usr/bin/oc adm             --config=/etc/origin/master/admin.kubeconfig             migrate authorization
  * execute[Migrate storage post policy reconciliation] action run
    - execute /usr/bin/oc adm             --config=/etc/origin/master/admin.kubeconfig             migrate storage --include=* --confirm
  * execute[Create key for upgrade all storage] action run

    ================================================================================
    Error executing action `run` on resource 'execute[Create key for upgrade all storage]'
    ================================================================================

    Mixlib::ShellOut::ShellCommandFailed
    ------------------------------------
    Expected process to exit with [0], but received '128'
    ---- Begin output of ETCDCTL_API=3 /usr/bin/etcdctl --cert /etc/etcd/peer.crt --key /etc/etcd/peer.key --cacert /etc/etcd/ca.crt --endpoints https://`hostname`:2379 put /migration/storage ok ----
    STDOUT:
    STDERR: Error:  open /etc/etcd/peer.crt: no such file or directory
    ---- End output of ETCDCTL_API=3 /usr/bin/etcdctl --cert /etc/etcd/peer.crt --key /etc/etcd/peer.key --cacert /etc/etcd/ca.crt --endpoints https://`hostname`:2379 put /migration/storage ok ----
    Ran ETCDCTL_API=3 /usr/bin/etcdctl --cert /etc/etcd/peer.crt --key /etc/etcd/peer.key --cacert /etc/etcd/ca.crt --endpoints https://`hostname`:2379 put /migration/storage ok returned 128

there's no peer files on master in /etc/etcd folder, like on etcd nodes, only ca folder:
ls -ls /etc/etcd/
drwx------. 5 root root 212 May 31 13:00 ca

also, this
https://github.com/IshentRas/cookbook-openshift3/blob/master/recipes/upgrade_control_plane37_part2.rb#L38
this
https://github.com/IshentRas/cookbook-openshift3/blob/master/recipes/upgrade_control_plane37_part2.rb#L45
and this
https://github.com/IshentRas/cookbook-openshift3/blob/master/recipes/upgrade_control_plane37_part2.rb#L76
all run on master, but use different etcd certificates
i think first 2 should be corrected to match 3rd

upgrade from 3.6 to 3.7 fails on master nodes with:
Recipe: cookbook-openshift3::master_packages
  * yum_package[origin-master] action install
    - install version 3.7.1-2.el7 of package origin-master
Recipe: cookbook-openshift3::services
  * execute[daemon-reload] action run
    - execute systemctl daemon-reload
Recipe: cookbook-openshift3::master_packages
  * yum_package[origin-clients] action install

    ================================================================================
    Error executing action `install` on resource 'yum_package[origin-clients]'
    ================================================================================

    Chef::Exceptions::Package
    -------------------------
    Installed package origin-clients-3.7.2-1.el7.git.0.cd74924 is newer than candidate package origin-clients-3.7.1-2.el7

@tpolekhin  thanks checking and correcting ASAP

for some reason origin-node did not updated on master nodes, while control plane did
Recipe: cookbook-openshift3::upgrade_node37
  * log[Upgrade for NODE [STARTED]] action write

  * execute[Disable origin-excluder] action run
    - execute origin-excluder enable
  * execute[Disable origin-docker-excluder] action run
    - execute origin-docker-excluder enable
Recipe: cookbook-openshift3::node
  * ruby_block[Turn off SWAP for nodes] action run (skipped due to only_if)
  * file[/usr/local/etc/.firewall_node_additional.txt] action create (up to date)
  * iptables_rule[firewall_node] action enable
    * template[/etc/iptables.d/firewall_node] action create (up to date)
     (up to date)
  * directory[/etc/origin/node] action create (up to date)
  * template[/etc/systemd/system/origin-node.service] action create (up to date)
  * template[/etc/sysconfig/origin-node] action create (up to date)
  * yum_package[origin-node] action install (up to date)
  * yum_package[origin-sdn-ovs] action install (up to date)
  * yum_package[conntrack-tools] action install (up to date)
  * remote_file[Retrieve certificate from Master[ip-10-239-122-113.ec2.internal]] action create_if_missing (up to date)
  * execute[Un-encrypt node certificate tgz files] action nothing (skipped due to action :nothing)
  * execute[Extract certificate to Node folder] action nothing (skipped due to action :nothing)

btw, i changes this https://github.com/IshentRas/cookbook-openshift3/blob/master/attributes/update.rb#L44
to be default['cookbook-openshift3']['upgrade_ose_version'] = '3.7.2-1.el7.git.0.cd74924' to make it work for the control plane

i think this still needs to be changed:
https://github.com/IshentRas/cookbook-openshift3/blob/master/recipes/cloud_provider.rb#L34
there's no service[#{node['cookbook-openshift3']['openshift_service_type']}-node] in services.rb

Thanks. Fixed

tried to utilize wildcard node certificate but failed with:
Jun 04 11:39:41 ip-10-239-122-113.ec2.internal origin-node[99371]: E0604 11:39:41.674334   99371 kubelet_node_status.go:106] Unable to register node "ip-10-239-122-113.ec2.internal" with API server: nodes "ip-10-239-122-113.ec2.internal" is forbidden: node wildcard_nodes cannot modify node ip-10-239-122-113.ec2.internal

is thee some additional config needs to be done?

@ianmiell @IshentRas kind bump :)

We are 2.0.70 now lol

@tpolekhin Sorry for this long wait. Busy with other topics...
So you are right it does not work with 3.7 out of the box because 3.7 enforce NodeRestriction admission plugin prevent the API to use a different name than the real hostname of the node. Therefore the wildcard trick name does not work as it does not match the real name of your node.
system:node:wildcrad_nodes, which uses the system:node: format, but does not match the actual name of your node (ip-10-239-122-113.ec2.internal)
You can disable it (Not recommended) :-1:
admissionConfig:
pluginConfig:
NodeRestriction:
configuration:
kind: DefaultAdmissionConfig
apiVersion: v1
disable: true
Let me check if we can do something else instead :+1:
Obviously it is specific to 3.7+

Closing this topic. Coming work for 3.10 fixes that issue with node bootstrapping support.
https://docs.openshift.com/container-platform/3.10/architecture/infrastructure_components/kubernetes_infrastructure.html#node-bootstrapping


Ensembles

Research the possibility of having cxflow ensemble subcommand that would merge multiple computationals graph into one and dumping a regular checkpoint.
@petrbel :
Just to sum up the discussion we had last week

we need to benchmark few nets (various number of params, rnn/cnn, ..) in order to determine how fast/slow is the

decoding the network from file
loading the network to the GPU

then we should determine whether manualy force the computational graphs to merge somehow or simple evaluate multiple networks serially

I prefer the later option, hence I suggest creating both cxtream and fuel NetApplier of EnsembleApplier.

This is in fact back-end specific. I suggest to move this issue to cxflow-tensorflow repo. Any objections @FloopCZ @petrbe l?

I prefer the later option

Me too. Merging the TF graphs isn't that easy.

This is in fact back-end specific.

Is it? I think we want cxflow ensemble command regardless the backend. However, the TF implementation obviously belongs to TF. So whatever :)

You both are right. I believe that implementation is backend specific and interface is backend agnostic. So I agree with @red that this should be moved.

Well I can imagine cxflow predict --ensemble which would take a list of configs/dirs instead of a single one. The question is how to actually implement the ensembling. Averaging? Majority voting? And how to determine what should be ensembled, i.e. which variable is the actual prediction.


Fix links to doc pages on new site

What this PR does / why we need it:
When linking from github->sonobuoy.io the links shouldn't put
.md suffix on the files or else it will actually render the
markdown instead of the webpage.
Which issue(s) this PR fixes
Fixes #793
Release note:
NONE

Just a basic doc change with easily verifiable changes. Merging w/o review.


SSH-Chat <-> Discord: Links posted in discord are duplicated across the bridge back to discord

I can't figure out a reliable way to replicate this bug, but it's apparent in the following screenshot (please excuse the foul language) in the red-outlined sections that the bridge is repeating messages in discord which contain links. Not sure how to investigate it further, but happy to assuming the bridge gets used. (Use case is to connect a mining rig OS command to a direct chat with those that would offer support from Discord).

Making the issue in order to track this problem over time... if someone has a clue where to look to debug or diagnose this, please let me know!

I was able to figure out how to replicate this. It appears any time a link is posted, it causes this duplication... Here's another screenshot showing this:

Cool, someone is actually using ssh-chat 👍

The bug should be now fixed in master.
Can you retry building from master or using the dev build on https://bintray.com/42wim/nightly/Matterbridge/_latestVersion

Thanks for the quick response, although this version seems to be somewhat buggier. Here is an invite to the discord server if you want to test it out.
The ssh server is
ssh -p 2022 app.chosn.run
the discord room is https://discord.gg/Jd9S3A

Hi, neither the discord invite or ssh works
I can't seem to reproduce the double messages either

@42wim sorry, bad timing, I'm between hosting providers at the moment. I'll update this thread again as soon as those issues are sorted, with a repro


usage

Hello,
can you tell me about the specific steps of this project?
What is the format of the data set's storage path?

Sorry, you may need to spend a little time to read the code. x_x


building project with beego failed

i try to build my go  project which depends on beego with gogradle. build.gradle is:
plugins {
    id 'com.github.blindpirate.gogradle' version '0.7.0'
}

golang {
    packagePath = 'ytx/java-backend/futures/simulator'
}

build.dependsOn check

build {
    targetPlatform = ['linux-386', 'darwin-amd64']
    outputLocation = 'output/simulator_${GOOS}_${GOARCH}${GOEXE}'
}

dependencies{
    golang{
        build name:"github.com/gorilla/mux"
        build name:"github.com/astaxie/beego"
    }
}

when i do ./gradlew build, it goes wrong and output message is
What went wrong:
Execution failed for task ':resolveBuildDependencies'.
> Exception in resolution, message is:
  Cannot recognized package: golang.org/x/crypto/pbkdf2
  Resolution stack is:
  +- ytx/java-backend/futures/simulator
   +- github.com/astaxie/beego#c5118e9535f237996bae7c7baebe4ed4247cb2c6
    +- github.com/couchbase/go-couchbase#b2479ad629a58de79501b021497525f0ea27e226
     +- github.com/couchbase/cbauth#01e92ad5306dd0ea025a0d3faa535766fe1ad948
      +- github.com/couchbase/gomemcached#56481a09982ccef7e3e408a3b97dd818821f42f2

i have already downloaded pbkdf2 with command  go get -v golang.org/x/crypto/pbkdf2 ,but it still cannot work

I'm afraid you're GFWed.


MultiplayerSpawner does not function when using WebRTCMultiplayerPeer

Godot version
v4.1.1.stable.official [bd6af8e0e]
System information
Windows 10 - Godot v4.1.1 stable
Issue description
MultiplayerSpawner works fine with ENet multiplayer, but it does not work WebRTC. Using the same code base and switching between the two allows it to work when switching to ENet.
I have not yet found a fully working WebRTC example game that implements MultiplayerSpawner, so it is entirely possible that I am just doing it wrong.
However, it works with ENet, and the game works if I manually spawn the scenes on other devices, including MultiplayerSynchronizers work fine over WebRTC, just not the Spawners.
Steps to reproduce
Build a basic WebRTC game, including signaling server and attempt to add scenes that are tied to MultiplayerSpawner and they do not show up on peer games.
Minimal reproduction project
I have created a repo to demonstrate my findings here:
https://github.com/chrisl8/godot-webrtc-test
It requires running a Node.js based signalling_server to function.
The webrtc-native and node modules are both included in the repo, so it should be easy to pull down and run.
I cut my example down to the bone, so it does not include any MultiplayerSynchronizers. If you need me to add more to the example let me know and I can.

A little update. There's a signal in MultiplayerSpawner  - spawned - that is emitted once a scene has been replicated. In case when we're using ENet - it's emitted (and the scene has been replicated), no problem there. But when it's WebRTC - nothing happens.
I've also rechecked the networking code and, from the first sight, there're no problems/bugs with it, the peers are interconnected. So I suspect the problem might be in the scene replication code itself.
I will keep you updated once I know more.

You seem to be using the create_mesh setup, where each peer is connected to each other in mesh form and there is no "server".
Since the server (1) is the default authority of nodes, you will need to set the MultiplayerSpawner authority to the player ID you want to act as server.
In this specific case, this patch in your game solves the issue:
diff --git a/main-user-client/User.gd b/main-user-client/User.gd
index 95b1d9a..d114024 100644
--- a/main-user-client/User.gd
+++ b/main-user-client/User.gd
@@ -20,7 +20,10 @@ var game_scene_initialized: bool            =  false
 var level_scene                             := preload("res://scene.tscn")
 var is_server: bool                         =  false
 var server_name: String                     =  ""
-var server_id                               := -1
+var server_id                               := -1 :
+	set(value):
+		server_id = value
+		get_tree().get_root().get_node("Main/LevelSpawner").set_multiplayer_authority(value)
 var server_password: String                 =  ""
 var local_debug_instance_number             := -1
 var mult: SceneMultiplayer                  =  null

@chrisl8 That's weird, it works on my end. Scenes are being replicated but with a slightly bigger delay than when using ENet. Maybe there's a syntax error lurking somewhere? Pasting Faless' code just in case:
var server_id                               := -1 :
	set(value):
		server_id = value
		get_tree().get_root().get_node("Main/LevelSpawner").set_multiplayer_authority(value)

@Faless @azuloo The solution provided works for TWO instances, but running 3+ breaks it. You can see this by setting Run instances to 3 or 4 in Debug.
If I add a greater delay for the startup I can see that it works at first when only 2 are connected, but fails when a 3rd client connects.

@chrisl8 well, this is a matter of timing in your code, not in the replication code.
You simply need to set the User.server_id (i.e. set the multiplayer authority) before you add the peer to WebRTCMultiplayerPeer.

@chrisl8 well, this is a matter of timing in your code, not in the replication code. You simply need to set the User.server_id (i.e. set the multiplayer authority) before you add the peer to WebRTCMultiplayerPeer.

It doesn't matter how long I delay things, if there are more than 2 peers, it fails.
I will keep working on it though, perhaps this is not a bug after all.

I didn't quite liked the solution where we created new WebRTCMultiplayerPeer, new mesh and established new interconnections between peers each time a new peer appeared. So I've decided to try to not do that and move the initialization part into a separate func. In init_connection() I've only left the part where we establish a new connection (and adding a new peer essentially) but only for those peers that haven't been already interconnected.
And it actually worked! Here's the changes (along with the Faless' code from earlier):
User.gd
func init_rtc_peer():
	rtc_peer = WebRTCMultiplayerPeer.new() # Comment to disable WebRTC
	#rtc_peer = ENetMultiplayerPeer.new() # Comment to disale ENet
	if User.is_server:
		rtc_peer.create_mesh(ID) # Comment to disable WebRTC
		#rtc_peer.create_server(8080)
	else:
		rtc_peer.create_mesh(ID) # Comment to disable WebRTC
		#rtc_peer.create_client('<IP_ADDRESS>', 8080)

	get_tree().get_multiplayer().multiplayer_peer = rtc_peer

func init_connection():
	for peer_id in peers.keys():
		if connection_list.has(peer_id):
			continue # This peer has already been initiated, skipping
		var connection := WebRTCPeerConnection.new()
		connection.initialize({"iceServers": [ { "urls": ["stun:stun.l.google.com:19302"]}]})
		connection.session_description_created.connect(session_created.bind(connection))
		connection.ice_candidate_created.connect(ice_created.bind(connection))
		connection_list[peer_id] = connection
		rtc_peer.add_peer(connection, peer_id) # Comment to disable ENet

	network_initialized = true

Client.gd
...
if type == Message.USER_INFO:
		User.user_name = data
		User.ID = id
		print("Received User name = %s ID# %s" %[data, id])
		User.init_rtc_peer()
		user_name_feedback_received.emit()
		return
...

I've tested it with 4 windows and the scene has spawned in all of them. Please let me know if I didn't break any logic in your code, because it was quite a fast solution.

@azuloo and @Faless Thank you so much for your assistance!
You have proven clearly now that MultiplayerSpawner does indeed work with WebRTCMultiplayerPeer along with pushing me in the right direction to make it work.
Each of your contributions was a key to the puzzle.
If anyone else finds themselves here and is in need of help, feel free to check out the repo I used to open this ticket at https://github.com/chrisl8/godot-webrtc-test and please open Issues against that repository if it doesn't work for you and I will be happy to work with you to improve the example to be more clear and usable. I am happy to use that repo of mine as a "general user help forum" on WebRTC multiplayer in Godot.
I am closing this now as it is clear that there is no bug with Godot here. Thank you.


fix: Correct typos fixed

6.laravel-passport.md
Correct typos fixed
Closes #322 .
Checklist:

[x] issue number linked above after pound (#)

replace "Closes " with "Contributes to" or other if this PR does not close the issue

[x] manually checked my feature / checking not applicable
[x] wrote tests / testing not applicable
[x] attached screenshots / screenshot not applicable

Thanks @initred ❤


HIVE-26675: Update Iceberg from 0.14.1 to 1.0.0

What changes were proposed in this pull request?

Why are the changes needed?

https://iceberg.apache.org/releases/#100-release
The 1.0.0 release officially guarantees the stability of the Iceberg API.
Does this PR introduce any user-facing change?

How was this patch tested?

Strangely, I can't trigger the continuous-integration.

Strangely, i can not trigger the continuous-integration to run qtest.

LGTM. +1


Rework organization creation flow

At present, when creating a new organization, a user fills out two forms:

Email confirmation

email confirmation form

Organization details + account details

org creation form

With this structure, there is a lack of clarity regarding the overall process when the user is asked to provide their email. Instead, we should ask for information about the new organization at the same time as we ask for the email.
New organization sign-up, part 1

Title: Create a new Zulip organization
Fields (no section heading): Organization name, Organization type, Organization URL, Your email [same logic, hints, etc., as in the current form]

Other changes:

Fix the bug where the organization name cursor is currently a pointer, rather than a text cursor.
Put the form on the right side of the screen, and add a few bullet points about Zulip's features next to it (content details TBD).
Below those bullet points, add logos of organizations using Zulip based on what's implemented in #24082.

Notes:

At this point, we are not creating the organization in the database yet. We do need to pass the collected data on to the next form (see below).

Form:

Same 2-section structure as now, with the same fields.
Pre-fill all the data from part 1, and show it as just text (like we currently do with the email), to make it clear that no action is required on that part of the form. (We should drop the "Shorter is better than longer." hint for organization names at this stage.)
Pencil icon next to "Your organization" heading should make that part of the form editable, in case use wants to make any last-minute changes.

Button: "Create organization"

Follow-ups / questions:

We probably want to include the organization details the user has provided in part 1 in the confirmation email.
Should any changes be made to the page the user sees after submitting part 1?

email submission confirmation

Hey @alya I'll like to work on this issue

@zulipbot claim

Still working on this.

I think this was completed in https://github.com/zulip/zulip/pull/24689; are there follow-ups we should open?

There are a couple of points left for first form mentioned above like having the form on right side and mention about Zulip features in the left and having organization details in confirmation email.
We can open follow-up issues for them and close this.

Filed #25898, #25899 and #25900 for all the remaining follow-ups.


Importing custom Timeline font, app says existing data will be cleared

Seems to not happen for Bold Timeline Font
Version 4.0.6

this is description of import button.

You can export data to any app that can receive data, but maybe you can import data only from device's storage or Google drive.
Column background image may be not exported/imported over device.
Timeline font is not exported/imported.
Custom notification sound may be not exported/imported over device.

Oops, by 'importing' I meant 'Selecting' a font from app settings/appearence/Timeline Font to apply it

fixed. please wait next release.


Project 2: Asset Files Flags

Very important! The flagfiles from Github are all writen in lowercase (If you add them by copy paste). But in the array on the SwiftUI-Tutorial every country starts with uppercase and then lowercase. So once you are coding and building, the asset files cant be found(---> case-sensitive). You need to rename the files or easier rename the country names in the array. Hope this helped.

I have a dumb question how do I download the asset file of the flags ?

I have a dumb question how do I download the asset file of the flags ?

I have the same question. Been trying for some time and can't figure it out.

You can download the assets here: https://github.com/twostraws/HackingWithSwift/archive/refs/heads/main.zip
The files all have the correct case – just make sure you use the SwiftUI files, not the Classic files.


Added IoTHub Custom Policies

This PR fixes

Added IoTHub Custom Policies

@jtracey93
Azure IoT Hub

Policy Name
Policy Area
Description

Append-IotHub-MinimalEncryption
Encryption
Enforces minimal tls version 1.2 for iot hub.

Deny-IotHub-Sku
Busget
Enforces iot hub SKUs.

@krnese May require your help to work on one of the deployIfNotExists policies (Azure Defender for IoT Hub). Let me know, if you have time for that. I have written a policy but had some trouble with getting it to work. If I remember correctly, it was not triggered as expected.

@krnese I would enforce the following on the Corp Management Group:
Deny PublicNetworkAccess (Definition ID: /providers/Microsoft.Authorization/policyDefinitions/2d6830fb-07eb-48e7-8c4d-2a442b35f0fb)


When I manually trigger a task, it always reports an error

Describe the bug
When I manually trigger a task, it always reports an error.As shown in the following figure.
Screenshots

When I manually trigger a task, a stack overflow error is reported

An error will be reported when a task is triggered manually

Desktop (please complete the following information):

OS: macOS  12.3.1 (21E258)
Browser: chrome

Hi!
Looks like the same overflow on debian bullseye (rust 1.57- 1.62):

May be the errors happen because of using the deprecated tokio_unblock_process_task_fn ?
warn(deprecated)]` on by default

warning: use of deprecated function `delay_timer::utils::functions::tokio_unblock_process_task_fn`
   --> delicate-utils/src/consensus_message/task.rs:210:25
    |
210 |                 move || tokio_unblock_process_task_fn(command.clone(), id as u64)

source
@BinChengZhao  as the creator of delay-timer and delicate can know it as no one else.


should act like default formatter for pug and jade files

right now if you press alt+shift+f in windows, default or installed formatter / beautifier is used depending on extension of file.
but if you press on pug file after installing this extension it says "There is no formatter for jade files"

linux too

beautify.ignore=["**/*.pug"] and disabling editor.action.format
doesn't help
VSCode or Beautify hang with error on pug.
any ideas about workaround?

Only separated key binding for pugBeautify.execute

drop issue, vote it? please!
https://github.com/Microsoft/vscode/issues/54346

Currently, it can work again after language switch, deleting and installing extension, removing and adding key bindings in json file. I think, the reason in reinstalling. After VSCode upgrade some plugins SHOULD be reinstalled.

Now the pug key binding at the top, that may too helps to suspend the error.

An update: workaround makes editor.action.format broken. E.g. order in the key bindings is matter.
Answer from VSCode developer:
The extension is to blame because it doesn't integrate into our formatter infrastructure but uses a separate command. We have blogged about this https://code.visualstudio.com/blogs/2016/11/15/formatters-best-practices and it's on the extension to integrate better.

I have a replacement for this: pug (jade) formatter

I have a replacement for this: pug (jade) formatter

It might also be worth considering combining efforts on this with the Prettier plugin for Pug that's currently in beta. Thanks for your time and effort in publishing the extension in the first place!


List public actions

Add command to list public actions.
Research:

how to use & invoke from VSCode
package bindings

Closing as project is being archived.


Solve the next export problem

With the current implementation of zero-config, we detect the builder that should be used using the dependencies property.
That will continue to work! However, we might have to mix it with detecting the build property, otherwise people have no way to opt out of the @now/next builder, if their build command is for example next build && next export && another command (we should not use the @now/next builder for that and instead use the static builder).

Solved now!


incorrect curlification of fedora systemd macros

See following diff:
%if 0%{?suse_version}
%service_del_preun %{name}.service
%else
-%systemd_preun %{name}.service
+%{systemd_preun} %{name}.service
%endif

Done