Failed to create a symlink on Windows machine

Environment - Windows 11 Pro (Version 10.0.22621 Build 22621, Intel i7-9700).
Following the instruction in this repo README.md file, when running yarn build I get the following error:
symlink failed. Try running 'sudo yarn symlink' → failed ×, and obviously when launching the targeted adobe product(which is After Effects in my case) - I cannot open my CEP extension.
Trying to run yarn build using administrator account doesn't help, regardless of the terminal program in use(cmd.exe/PowerShell/Git Bash).
I did manage to bypass that issue using this workaround:

Launching Windows Command Prompt as administrator.
Executing this command: mklink /D "C:\Program Files\Common Files\Adobe\CEP\extensions\<my-panel-id>" "<path-to-my-bolt-app-root-source-code-folder>\dist\cep"

With that my CEP app is visible in After Effects Extension menu, and I can interact with it perfectly.
Please consider a fix for that issue, so we won't have to use that bandage I've mentioned above.

Is this on a new Bolt install? Is your user an Admin? Perhaps try updating the plugin yarn add vite-cep-plugin

Haven't had any other Windows users report this issue. If it comes up again feel free to re-open and provide additional details.

@justintaylor-dev updating the vite cep plugin by running yarn add vite-cep-plugin resolved the issue!

awesome!

Hi! I was having this issue and tried running yarn add vite-cep-plugin and then yarn build again. However it failed with the following error:
failed to load config from C:\[...]\vite.config.ts
error during build:
TypeError: Cannot destructure property 'iife' of 'undefined' as it is undefined.
    at jsxInclude (C:\[project folder]\node_modules\vite-cep-plugin\lib\index.js:338:23)
    at extendscriptConfig (C:\[project folder]\vite.config.ts:142:45)
    at Object.<anonymous> (C:\[project folder]\vite.config.ts:233:1)
    at Module._compile (node:internal/modules/cjs/loader:1256:14)
    at require.extensions.<computed> [as .ts] (C:\[project folder]\node_modules\vite\dist\node\chunks\dep-6e2fe41e.js:62006:20)
    at Module.load (node:internal/modules/cjs/loader:1119:32)
    at Module._load (node:internal/modules/cjs/loader:960:12)
    at Module.require (node:internal/modules/cjs/loader:1143:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at loadConfigFromBundledFile (C:\[project folder]\node_modules\vite\dist\node\chunks\dep-6e2fe41e.js:62014:17)
error Command failed with exit code 1.

I am not sure what to make of this. Any thoughts appreciated!


Fixed common::VisualizeMesh

The function wasn't linking and it wasn't connecting properly to glvis.

PR
Author
Editor
Reviewers
Assignment
Approval
Merge

#3315
@vladotomov
@tzanio
@mlstowell + @tzanio
11/9/22
⌛due 11/23/22
⌛due 11/30/22

PR Checklist

[ ] Code builds.
[ ] Code passes make style.
[ ] Update CHANGELOG:

[ ] Is this a new feature users need to be aware of? New or updated example or miniapp?
[ ] Does it make sense to create a new section in the CHANGELOG to group with other related features?

[ ] Update INSTALL:

[ ] Had a new optional library been added? If so, what range of versions of this library are required? (Make sure the external library is compatible with our BSD license, e.g. it is not licensed under GPL!)
[ ] Have the version ranges for any required or optional libraries changed?
[ ] Does make or cmake have a new target?
[ ] Did the requirements or the installation process change? (rare)

[ ] Update continuous integration server configurations if necessary (e.g. with new version requirements for each of MFEM's dependencies)

[ ] .github
[ ] .appveyor.yml

[ ] Update .gitignore:

[ ] Check if make distclean; git status shows any files that were generated from the source by the project (not an IDE) but we don't want to track in the repository.
[ ] Add new patterns (just for the new files above) and re-run the above test.

[ ] New examples:

[ ] All sample runs at the top of the example source file work.
[ ] Update examples/makefile:

[ ] Add the example code to the appropriate SEQ_EXAMPLES and PAR_EXAMPLES variables.
[ ] Add any files generated by it to the clean target.
[ ] Add the example binary and any files generated by it to the top-level .gitignore file.

[ ] Update examples/CMakeLists.txt:

[ ] Add the example code to the ALL_EXE_SRCS variable.
[ ] Make sure THIS_TEST_OPTIONS is set correctly for the new example.

[ ] List the new example in doc/CodeDocumentation.dox.
[ ] If new examples directory (e.g.examples/pumi), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add example-specific documentation, see e.g. the src/examples.md.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] In examples.md, list the example under the appropriate categories, add new categories if necessary.
[ ] Add a short description of the example in the "Extensive Examples" section of features.md.

[ ] New miniapps:

[ ] All sample runs at the top of the miniapp source file work.
[ ] Update top-level makefile and makefile in corresponding miniapp directory.
[ ] Add the miniapp binary and any files generated by it to the top-level .gitignore file.
[ ] Update CMake build system:

[ ] Update the CMakeLists.txt file in the miniapps directory, if the new miniapp is in a new directory.
[ ] Add/update the CMakeLists.txt file in the new miniapp directory.
[ ] Consider adding a new test for the new miniapp.

[ ] List the new miniapp in doc/CodeDocumentation.dox
[ ] If new miniapps directory (e.g.miniapps/nurbs), add it to MINIAPP_SUBDIRS in the makefile.
[ ] If new miniapps directory (e.g.miniapps/nurbs), list it in doc/CodeDocumentation.conf.in
[ ] Companion pull request for documentation in mfem/web repo:

[ ] Update or add miniapp-specific documentation, see e.g. the src/meshing.md and src/electromagnetics.md files.
[ ] Add the description, labels and screenshots in src/examples.md and src/img.
[ ] The miniapps go at the end of the page, and are usually listed only under a specific "Application (PDE)" category.
[ ] Add a short description of the miniapp in the "Extensive Examples" section of features.md.

[ ] New capability:

[ ] All new public, protected, and private classes, methods, data members, and functions have full Doxygen-style documentation in source comments. Documentation should include descriptions of member data, function arguments and return values, template parameters, and prerequisites for calling new functions.
[ ] Pointer arguments and return values must specify whether ownership is being transferred or lent with the call.
[ ] Any new functions should include descriptions of their intended use e.g. for internal use only, user-facing, etc., along with references to example code whenever possible/appropriate.
[ ] Consider adding new sample runs in existing examples to highlight the new capability.
[ ] Consider saving cool simulation pictures with the new capability in the Confluence gallery (LLNL only) or submitting them, via pull request, to the gallery section of the mfem/web repo.
[ ] If this is a major new feature, consider mentioning it in the short summary inside README (rare).
[ ] List major new classes in doc/CodeDocumentation.dox (rare).

[ ] Update this checklist, if the new pull request affects it.
[ ] Run make unittest to make sure all unit tests pass.
[ ] Run the tests in tests/scripts.
[ ] (LLNL only) After merging:

[ ] Update internal tests to include the new features.

This PR is now under review (see the table in the PR description). To help with the review process, please do not force push to the branch.

@vladotomov, I agree that thevec argument served no useful purpose but I'm confused by the addition of the attr GridFunctions. This leads to two questions. First, why is a GridFunction containing zeros preferred over the default of just the mesh? Second, why not put the element attributes into the GridFunction? This leads to yet another question. Shouldn't we give the user the control over what this GridFunction contains, if anything?

1st question - I couldn't figure out how to send only the mesh, I was getting glvis errors, so I though it wasn't a big deal, but I can dig more if you think it's important.
2nd question - I thought it would be confusing to get solutions when calling VisualizeMesh, but I don't have a strong preference if you want to add attributes or something else.

I wouldn't say it's a big deal but we may be able to make it a little simpler. Have a look at this. If this implementation avoids the error you were seeing we might be able to do without the GridFunction.

For 1, can you try sending the mesh with sock << "mesh\n" << *mesh << flush; ?

Those work, it's fixed.

Merged in next for testing...


Roll engine 99f3f7a9c246..66042161eba1 (1 commits)

https://github.com/flutter/engine/compare/99f3f7a9c246...66042161eba1
git log 99f3f7a9c246f1ebedc6eefd867cde250b370380..66042161eba17da968800c57ddd2c314cd787abb --no-merges --oneline
66042161e Roll src/third_party/skia 255569187f27..71a23d4195d9 (1 commits) (flutter/engine#8003)
The AutoRoll server is located here: https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md
If the roll is causing failures, please contact the current sheriff (garyq@google.com), and stop
the roller if necessary.

Auto-roller completed checks. About to merge.


addition of more footer classes

Title and Issue number
Issue No. : #99
Code Stack : HTML,CSS
Close #99
Video/Screenshots (mandatory)

Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
I have added footer classes: Connect With Us and Explore.
Are you contributing under any Open-source programme?
JWOC'24

I hope I have made the PR correctly. Thanks for the opportunity


Use https URL rather than Git url

Git url uses ssh which might be troublesome behind proxies. Using http facilities the use of an http proxy (which very likely already is set in these environment).

apm install won't work with this.
 Darwin 14.1.0
npm ERR! argv "/Applications/Atom.app/Contents/Resources/app/apm/bin/node" "/Applications/Atom.app/Contents/Resources/app/apm/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/Applications/Atom.app/Contents/Resources/app/apm/.apmrc" "--userconfig" "/Users/xxx/.atom/.apmrc" "install" "--target=0.21.0" "--arch=x64"
npm ERR! node v0.10.35
npm ERR! npm  v2.3.0
npm ERR! fetch failed with status code 406
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     http://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR!     /Users/xxx/github/atom-ternjs/npm-debug.log

seems that apm doesn't allow urls anymore (since 0.178)
changed it to:
"tern": "*",


[Pods] The pod UI-specific views

Ready for review :)

@wavesoft I added some comments I hope they can help you.

Gave this a "quick" overlook, however, this PR is big! and that makes it much harder to review. Could you break this up into PR chunks of ~300 lines a piece?

Ok, I will try to break this down into smaller PRs while addressing the comments.

This PR is broken down into the following PRs and is now closed:
#1067 , #1068 , #1069 , #1071 , #1077 , #1078 , #1079


[13824]Change check static xml discovery test from rtps tests to dds tests

Change check static xml discovery test from rtps tests to dds tests

This PR is dependent on eProsima/Fast-DDS#2817

Signed-off-by: Inés Luño<EMAIL_ADDRESS>

CI with Fast DDS corresponding changes:

Even though the badge appears as FAILING, the tests have been run correctly. The failure comes from Jenkins not knowing where to save the CI run as it is a custom one.

@richiprosima please test this

@richiprosima Please test this


Fix bad virtual relations

virtual attributes used to ignore invalid :uses => and includes() clauses.
Now, both active record and virtual attributes want valid values
I went through our :uses clauses and found those that were never valid.
These problems showed up in a bulk scan.

@kbrock Is this something we can bake into the virtual attribute definition so we can fail early and find these at dev time?


Review and refactor of code.

The refactoring splits by the different Kafka API's, and renames the files to make it easier to extend the library with our own code.

I won't merge it. Your changes are only code moves with which I don't agree with:

there is no reason to split request and responses to separate files,
moving type definitions to the top file is making the code less readable, because it's no longer top-down reading of the library to understand how it works,
api.go is containing random definitions

Requests and responses are not in separate files - they are always in the same file, split by API concern. While I agree that api.go could be structured differently, I hardly see a list of the Kafka API values as "random definitions".
This is probably a matter of opinion, but mixing repetitive implementation details for decoding and encoding in a big 1k loc file makes it harder to read than the key API concerns, which are the structure definitions.
@MikeRoetgers: can I request a second opinion?

Out of date following PR #2


Kyty is showing an error every time I launch it, can anyone help?

Initialized: Config
Initialized: Profiler
Initialized: Log
Initialized: Timer
Initialized: Pthread
Initialized: Network
Initialized: Memory
Initialized: FileSystem
Initialized: Controller
Initialized: Graphics
Initialized: Audio
Stack trace [thread = 9]:
[0]<PHONE_NUMBER>8a63ff, eboot.bin
[1]<PHONE_NUMBER>9586d7, eboot.bin
[2]<PHONE_NUMBER>000074, eboot.bin
[3]<PHONE_NUMBER>84dd72, eboot.bin
--- Stack Trace ---
[0]<PHONE_NUMBER>2a241a,<PHONE_NUMBER>2a2260, RuntimeLinker.cpp.obj, Kyty::Loader::RelocateHandler(Kyty::Loader::RelocateHandlerStack)
[1]<PHONE_NUMBER>8a63ff,<PHONE_NUMBER>000000, unknown, unknown
--- Error ---
=== Unpatched function!!! ===
[9]     n88vx3C5nW8[Posix_v1][libkernel_v1.1][Func]
in C:/projects/kyty/source/emulator/src/Loader/RuntimeLinker.cpp:514

What game are you trying to run?


 Automated cross-browser testing via Sauce Labs and Travis CI shows that the JavaScript changes in this pull request are: CONFIRMED
Commit: 9821699d90c91dcecaa4d62d4d32c12f30acfc49
Build details: https://travis-ci.org/twbs-savage/bootstrap/builds/53813088
(Please note that this is a fully automated comment.)

@hnrch02 LGTY? Seems okay to me.

The Tooltip still seems to leak a bit. What we did in our project was to also clear out the $element. This, however required also an extra check in the complete function of the hide function:
function complete() {
  if (that.hoverState != 'in') $tip.detach()
  if (that.$element) {
    that.$element
      .removeAttr('aria-describedby')
      .trigger('hidden.bs.' + that.type)
  }
  callback && callback()
}

And to be extra sure that we are not calling destroy too many times:
Tooltip.prototype.destroy = function () {
  var that = this
  clearTimeout(this.timeout)
  if (this.isDestroying == true) {
    return
  }
  this.isDestroying = true
  this.hide(function () {
    that.$element.off('.' + that.type).removeData('bs.' + that.type)
    if (that.$tip) {
      that.$tip.detach()
    }
    that.$tip = null
    that.$arrow = null
    that.$viewport = null
    that.$element = null
  })

@afinne Pleaae open a new pull request or issue.


feat: Ability to implement custom strategies

As I wanted to push often ducks into top right corner, I needed the ability to change the strategy of new positions.
This version permit ability to create new strategies to find out next position of ducks. An executable example is made in readme.
Also, the random_wandering is curried to have the hability to change get_random function to any, but it could be removed and simplified if you desire. It would not make a breaking change to make this simplification later.
I suggest to merge this PR as squash is it contains a lot of intermediate development steps and few development is finally thrown away.

Hi @worming004,
Great changes! But I'm sorry I cant merge it because its better to keep duck's implementation very simple 😅 .
If you want direction strategies, you could do a small change, for example:
https://github.com/tamton-aquib/duck.nvim/blob/d8a6b08af440e5a0e2b3b357e2f78bb1883272cd/lua/duck.lua#L23
Changing math.random() to
1 will make it 2 * pi which means right
0.5 will make it 1 * pi which means left
0.25 will make it 0.5 * pi which means down
0.75 will make it 1.5 * pi which means up.
This is just an example, by the way.
We could even make it a config option for the user to change but I'm not sure. Also there are some inconsistencies in the PR as well as the .cook() method wasn't working when i checked

I'll used a fork for me

Sounds like a good option 😄

Have fun for the future !

You too, good luck!


403 when downloading plugin

I am trying to run the following and the plugin URL is 403
sudo bin/elasticsearch-plugin install https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-security/opendistro-security-<IP_ADDRESS>.zip

Where can I download older plugin versions?

Hi @ajbeach2 ,
For all previous versions (before <IP_ADDRESS>) of security plugin, the security plugin zip is named as opendistro_security-<version>.zip
https://d3g5vo6xdbdb9a.cloudfront.net/downloads/elasticsearch-plugins/opendistro-security/opendistro_security-<IP_ADDRESS>.zip
Sorry for the confusion.

@gaiksaya Thanks for providing the correct link!
@ajbeach2 The link provided above works for me. Please re-open the issue in case that it doesn't work for you.


Scraping google play store

Is your feature request related to a problem? Please describe.
The python script scrapes through a list of app results of a search query and obtaining data like number of installs, number of reviews, stars, email, etc.
Describe the solution you'd like
The script will be implemented using selenium library in python.

@RohiniRG The search query should be the category of apps (ex: Games, utilities, books etc)

@RohiniRG updates on this? Make the PR before 2 pm so that we can review the code properly and merge it on time.


Create input for Sign Up page

Draft pull request for BC

@Ali-7s Is this PR ready for a review? if so, can we convert it from a draft by marking it ready for review?

Great job! 2 things we will need to revisit for this page and add functionality to in a separate issue and PR:

keyboard should have a check mark button that closes the keyboard when user is done entering text. See how Belindas-android sign up page functions. It's perfectly fine to incorporate what is used in that repo.
confirm password field should eventually be tied to the password field. We can also utilize the work that has already been done with the Belindas-android app as this feature is also already implemented there.

Let's get this merged in before there's conflicts!


Store post and comment vote percentages

What does this PR?
It will store the last vote percentage of post and comment in local storage.
If there is previously stored value in local storage , it will get the value from local storage and display the previous voted value.
If there is no value in local storage means user open the voting slider first time, it will display the default value in the slider.
Steps to reproduce

Open the voting slider of any post and vote to that post or just move the slider to change the value of slider. it will store the updated value of slider in local storage.
When you open the slider of any post next time, it will show and  set the previous stored value.
Same is the case with comment-voting-slider.But post-voting-slider value and comment-voting-slider value stored separately and  independent to each other.
Stored the value of slider in both Up and Down case.

Issue number
fixes #1048
Screenshots/Video
https://user-images.githubusercontent.com/106739598/205293384-87226905-d016-405f-94e4-9034421292a9.mp4

@MTSaeed Do we still show voted value? If content already has been voted, slider should show that value not localstorage value.

@feruzm @dkildar The code has been updated please review.
Currently we are saving the voted value in localstorage and showing that on slider next time if the user has voted on one post or comment. If the user just changes the value on slider and has not voted the value is not saved and the voted one will be displayed next time.

@MTSaeed I am talking about, content is voted by user with 40% and later another content was voted with 50%. If person opens first content vote again, do we show 40% or 50% ?

@MTSaeed I am talking about, content is voted by user with 40% and later another content was voted with 50%. If person opens first content vote again, do we show 40% or 50% ?

It would say 40% as that post has been voted 40%.
https://user-images.githubusercontent.com/106739598/206150706-e7d6510d-77cf-480e-8768-d615a5c50428.mp4
If a post is voted it would show the voted value instead of LS.


PMC Tools: Error when using Docker tools

VS creates a project that is set as the startup project when you are running a solution inside containers, but it doesn't have any code in it.
This means that if you run Add-Migration without specifying a startup project it will fail. I am told that for some project types we provide an error message telling people what they have to do. Given that it will never be correct to use the docker project for migrations can we do the same here?
//cc @dazhao-msft

Anything is possible, Glenn. Shun the non-believer...

I wonder if it's worth trying to work our way backwards from the Docker Compose project to the actual web application project. This will only work when there's a 1:1 relationship between them, but it seems like it would be fairly common to have multiple images in a solution. We'd also have to scan all of the projects which has been brittle in the past.


page for license/privacy notice

I think it would be beneficial to have a page for the license and privacy notice. I started a branch for a page. I based it off the 'about' page, but it still needs a lot of work.
I started by adding the license title and a link. I also mentioned that we don't actually own Gobo (that should be fairly obvious to users of scratch).
Any thoughts or suggestions?

https://gobo.cf/LICENSE


Update secure-your-business-data.md

Docs Build status updates of commit 4c8df8e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-365/admin/security-and-compliance/secure-your-business-data.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


raftstore: Peer do not print raft-id and peer-id in raft-rs lib

Bug Report
The raftstore do not print the raft-id and region-id in raft-rs.
[2024/01/18 12:23:45.245 +08:00] [INFO] [raft.rs:1532] ["starting a new election"] [term=5] [thread_id=1]
[2024/01/18 12:23:45.245 +08:00] [INFO] [raft.rs:1177] ["became pre-candidate at term 5"] [term=5] [thread_id=1]
[2024/01/18 12:23:45.245 +08:00] [INFO] [raft.rs:1151] ["became candidate at term 6"] [term=6] [thread_id=1]
[2024/01/18 12:23:45.245 +08:00] [INFO] [raft.rs:1235] ["became leader at term 6"] [term=6] [thread_id=1]

What version of TiKV are you using?

Nightly branch: e2a2e87a890ad488446b3c4a2900a74d9313a8ba
What operating system and CPU are you using?

None
Steps to reproduce

Build with nightly branch.
What did you expect?
raft-rs should print the raft-id and region-id as before.

What did happened?
raft-rs does not print the raft-id and region-id as before.

/cc @overvenus

It seems that this issue is introduced by https://github.com/tikv/tikv/pull/16399, which fixes the abnormal prints on thread-id but fails on printing raft-id and region-id.


expose /health-check/whatismyip endpoint

health-check service pulls the server public ip on startup, it makes sense to expose it for other services to use (I'm gonna need it in nginx for my work on blocking external traffic access for takedown servers)
otherwise we could create new service and expose it there but I'm not sure it makes much sense to add this complexity
closes https://github.com/SkynetLabs/skynet-webportal/issues/1955

We will include SERVER_IP in .env file.


Can't startup a sihas-canary after updated a HASS to 2022.4.7

Hi,
I had updated a sihas-canary to 1.1.2 but can't setup it with a below error message.
I think this problem is caused by changing setup_platform to async_setup_entry.
Would you mind check this case?
Thanks
SO
Apr 26 16:20:40 raspberrypi hass[15843]: 2022-04-26 16:20:40 ERROR (MainThread) [homeassistant.components.sensor] The sihas_canary platform for the sensor integration does not support platform setup. Please remove it from your config.
Apr 26 16:20:40 raspberrypi hass[15843]: 2022-04-26 16:20:40 ERROR (MainThread) [homeassistant.components.sensor] The sihas_canary platform for the sensor integration does not support platform setup. Please remove it from your config.

https://github.com/cmsong-shina/sihas-canary/blob/71882111abdc014d8bee62ca8b58074086742cb4/sensor.py#L154

Hi sungokay,
Check your configuration.yaml and remove information about this integration.
Now we use zeroconfig instead writing configuration file manually.
REAME file is not updated yet, so check this page.

I had removed the configuration from configuration.yaml and added via zeroconfig. After that, the problem had been solved.
Thanks
SO


Enable GitHub Discussions

Describe your issue
Hi, I want to suggest to enable Discussions feature on GitHub. Mailing lists are too old and inconvenient for technical discussions where you often want to share styled code snippets or embed span of the source code inline. GitHub Discusses is relatively more accessible and easy to use for many of us. Please consider it.
Discourse would also be very appreciated.
Thank you.

I'll close this issue since it's the wrong place to discuss such a change. Please ask on the current cython-users mailing list to see if you find enough support there. If users generally agree that they would prefer moving away from email, then we can make the switch.


RC npm: "hash pinning" is a confusing term

I've never heard this term in this context before. The way it's described in the npm ecosystem is "using a lockfile".

It is defined in the document. I think hash or checksum pinning is fairly common in the broader package ecosystem where this might still make sense to define here as it's fairly common, just perhaps outside the npm ecosystem.
Do you have better terminology that might be more familiar to the npm community we can use in order to make it clear that what's important is the integrity value is the hash or checksum of the package you are intending to download?

That's what a lockfile is - it wouldn't really be one without built-in integrity checking, would it?

Either way, the target audience here is the npm community - non-npm folks don't need to understand the "npm best practices" document :-)

I disagree. I think generally consumers of a thing also want to know that people are largely following best practices and how to verify those best practices. Also, it's intended to help people better understand general security and apply it to production/consumption of npm

I don't mean to suggest that the term shouldn't appear; i mean to suggest that it shouldn't be the primary one used.

I agree with Jordan that this is a term that's not particularly common or known in the JavaScript package ecosystem.
To better understand though, are we really saying "use a lockfile" as part of this best practice, or are we actually referring to the hash? the lockfile is more than just the hash too.

The best practice should be (and is) "use a lockfile".

100%, I'm just wondering whether there has been a bigger thing here that @mlieberman85 was trying to address.
There are also security concerns with lockfile injection and tampering which should be addressed as best practices, and this one doesn't cover.

I don't mean to suggest that the term shouldn't appear; i mean to suggest that it shouldn't be the primary one used.

That makes sense. Would changing the heading to "Use a Lockfile" and underneath it explain that the reasoning is it does "hash pinning" which allows you to enforce that you don't pull in anything but what was captured when you generated the lockfile, be clearer?

@mlieberman85 yes, much clearer, because virtually every person in the npm ecosystem won't know or care about the term "hash pinning", but "use a lockfile" will be straightforward.

Saying "use a lockfile" is fine as long as the lockfile includes, for each package, the "integrity" value that contains a strong cryptographic hash. As far as I know lockfiles always include integrity values, but there is a related problem...
In practice a lot of them use SHA-1, which is a big problem because SHA-1 is broken. E.g., you might see "integrity": "sha1-ml9pkFGx5wczKPKgCJaLZOopVdI=" if you use array-flatten version 1.1.1.
I think there should be encouragement to move away from SHA-1 (at least as the ONLY integrity value). Not sure how to word that.
Note that SHA-512 is fine. E.g., the integrity value "sha512-hIP3EEPs8tB9AT1L+NUqtwOAps4mk2Zob89MWXMHjHWg9milF/j4osnnQLXBCBFBk/tvIG/tUc9mOUJiPBhPXA==" you'd get from "content-type" version 1.0.4 is just fine.

yes, i think if there's no integrity hash it's not much of a lockfile :-)
I'm pretty sure that npm always uses sha-512 whenever the system supports it, and whenever the package was published recently enough that a sha512 hash exists. It'd be a great RFC to suggest a config (assuming none exists) to require sha512 hashes.

I would say the top statement should be "Use a lockfile", and somewhere in its rationale explain why. Something like:

Use a lockfile because it implements hash pinning using cryptographic hashes. "Hash pinning" means that any change to the package will be immediately rejected, so any malicious change to the dependency would be detected and rejected. Note that historically the SHA-1 algorithm was used for hash pinning, but that algorithm has been broken. Where possible, don't use SHA-1 and instead use secure algorithms (such as SHA-512).

Feel free to modify, that's just a potential starting point. But we should always justify doing something, and if there's a gotcha/warning, tell them. If there's an easier to way to force the use of SHA-512 (or something secure instead of SHA-1) that'd be even better...!


develop a strategy for paired programming on jupyterhub

https://github.com/eoas-ubc/docker_by_example/issues/2

Can we use Cocalc?
There, students can create "projects" and share them between each other. Just like overleaf/google docs.
Projects can have Jupyter notebooks which can be edited collaboratively in real time.

Real time collaboration in vanilla jupyter is a work in progress:

https://github.com/jupyterlab/rtc
https://github.com/jupyterlab/jupyterlab/issues/5382

Seems like it could work in jupyter lab

This looks interesting:  https://github.com/codefreak/codefreak


Fix misleading code in readme

Since there are ES6 modules, there is nothing useful by just requiring module. Needs to be either default or RedBoxError which is more useful in this case.

@FredyC Thank you for your contribution! I don't think that importing RedBoxError is generally a very good idea. There are use cases, but I don't think I would advertise it on the README. I just tried importing RedBox via const RedBox = require('redbox') (without default) and it worked just fine. Can you please describe or better provide a repo/gist/fiddle that reproduces your problem?

Problem is that require call is not handled by Babel so there is no way it can understand ES6 modules and grab correct export. I am pretty sure it cannot work for you unless you have some unusual setup.
require('react-redbox') gives me object like this.

Trying to render that with React fails with: Uncaught Invariant Violation: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: object.
From what I understand RedBoxError is rendered directly by React, so in this use case when are are rendering it directly with React.render() you know, that you can safely render it into your div instead of creating extra one.

@FredyC I didn't test this in a setup without babel/webpack. Could you please make a quick repo where I can play with this? It might be optional to use .default when using babel/webpack but not otherwise.
Regarding your use case, you can of course use RedBoxError if you don't need the "portal" which is exported as default.

I am using babel/webpack, but this has nothing to do with it. Babel is not touching require call so it cannot automatically grab default export. Here is a comparison.
// original
const RedBox = require('redbox-react');
import RedBox2 from 'redbox-react';

// transpiled
var _redboxReact = require('redbox-react');
var _redboxReact2 = _interopRequireDefault(_redboxReact);
function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }
var RedBox = require('redbox-react');

It's pretty obvious here that Babel does it's magic to grab default but plain require stays the same.

Regarding your use case, you can of course use RedBoxError if you don't need the "portal" which is exported as default.

That's not my use case exactly, it's the code from readme I tried to fix. It's not a big deal if there is extra div, but it's kinda more correct in my opinion.

@FredyC I tried this with webpack + babel earlier and it resolved the require call correctly. I'll test it in depth later when I'm back at my computer.

Well I am obviously bad at explaining, but there is way for this to be working with Webpack 1.x. That's how transpilation works. If you want to access default export of babelified ES6 module you have to explicitly say require('module').default. Just think about it for a moment. How else would you access named export with simple require?

@FredyC I'm sure this will turn out to be entirely my fault 😉 I'm writing this from my phone so I have no way of verifying this, but I was under the impression that wepack sets up imports so that default exports are accessible by simply calling require. I'll check that later today.

weppack sets up imports so that default exports are accessible by simply calling require

When webpack was written, there were no ES6 modules to include such functionality. Since it's pretty much breaking change, that's why there is Webpack 2.x which can understand modules this much better.
This PR isn't really about changing any code really, it's very small readme fix so other people wont stumble across same issue as me. It's pretty much possible that most people are just using babel transform plugin, but I did not like that so I found about this.

Just noticed there is actually another misleading spot in readme...
const RedBox = require('redbox-react')
const e = new Error('boom')
const box = <RedBox error={e} />

Should be...
import RedBox from 'redbox-react';
const e = new Error('boom')
const box = <RedBox error={e} />

You need to import the default export in this case because you obviously want to render using "portal" component. Using ES6 directly is better here so perhaps include that in your upcoming changes.

Ah nevermind, you have actually fixed that already, I kinda missed it ;)


About  visualization of the NNGuide

Great works!But i want to know How is this graph drawn, with which data set?

Thank you for your interest! We have used sklearn.datasets.make_moons for the dataset. We trained a single hidden layer MLP on the dataset with the SGD or Adam optimizer. We have used the softmax classifier confidence due to its limited output range and hence easier calibration in the visualization. Unfortunately, we have lost other configurations as we have lost the exact code we used to draw this.


Update README

Update README to indicate that this repository contains conceptual docs and to specify the location of reference docs.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

README.md
:white_check_mark:Succeeded

docs/publish/publish.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


[FEATURE] Office365 Updates - Use OfficeC2RClient.exe /update user

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
--- Whenever you do an update with Office it removes all office products, this causes an issue if you have to have the Access Database Tools installed for applications. Which would then require the re-install of office updates for said applications.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Would it be possible to have a Update command for M365:
"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user
Is your feature request a new application?

Include the application and a link to the vendor web site or download location
Does the application have an in-built updater or update check? If so, use Fiddler to monitor the request to determine where the application is connecting to
Does the vendor host binaries on GitHub or SourceForge, if so, include a link to the repository

Additional context
Add any other context or screenshots about the feature request here.
Here is a link that was a good source:
https://www.powershellgallery.com/packages/Update-Office365/1.0.0/Content/Update-Office365.ps1

I'm unsure what's being asked here? Could you please explain in more detail.
Evergreen already supports the Microsoft 365 Apps with:
Get-EvergreenApp -Name "Microsoft365Apps"

Hey Aaron,
Sorry for the delay and confusion, I sometimes have a hard time explaining
what I am trying to say. I think the best way for me to explain is to show
you the current steps I am running when I open a Image for maintenance in
Citrix.

Once the Maintenance Image is up and running, I run the Evergreen script
When i select my saved software that i want to update, if i select
Microsoft 365 Apps, it uninstalls all Office Products along with the
Microsoft Access Database Engines (some of the software requires 2010 still
and the updated M365 one will not work :/), Some of the software also
requires requires the 64 bit Database Engine.
M365 re-installs
Have to run a script to re-install both Database Engine 2010 32 bit and
64 bit

Ask

Once the Maintenance Image is up and running. I run the Evergreen Script
For the Microsoft 365 Apps checkbox, have another checkbox that runs
update only (or something like that). This way i dont have to run step 4
again in my current tasks as the software is not removed.

If this is not feasible, thats fine. I've created a modified Office Update
script in the past that did Teams/OneDrive/M365 in the past before I found
the script you guys have created. And the only piece that I have to do
still is the M365 updates with opening PowerShell and running the line: "&
"$env:CommonProgramFiles\microsoft shared\ClickToRun\OfficeC2RClient.exe"
/update user"
By the way, thank you very much for such a great piece of software, makes
my life so much better :D.
Justin
On Tue, Jul 6, 2021 at 7:50 PM Aaron Parker @.***>
wrote:

I'm unsure what's being asked here? Could you please explain in more
detail.
Evergreen already supports the Microsoft 365 Apps with:
Get-EvergreenApp -Name "Microsoft365Apps"
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aaronparker/evergreen/issues/204#issuecomment-875157363,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT5FZFOIGCPQWMHVIBKWJZ3TWOJEXANCNFSM475BH6RQ
.

--
Justin A. Richardson

I believe this request is not for aaron but for me.
https://github.com/Deyda/Evergreen-Script :-)

I think you just need to amend your config.xml so that it does not try to remove any MSI versions.

@JARich2006  What you're describing isn't what Evergreen is for. You'll have to script this with other means.

Awesome, thanks!
On Sat, Jul 10, 2021 at 10:21 AM Aaron Parker @.***>
wrote:

Closed #204 https://github.com/aaronparker/evergreen/issues/204.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aaronparker/evergreen/issues/204#event-5003279481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AT5FZFLGQ4VPW4XI7BXSTJTTXBJOZANCNFSM475BH6RQ
.

--
Justin A. Richardson


[Feature] Add detection and non_detection field description

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

This is solved in the multistream branch


ListOrder url bug

Found a bug where the url for ListOrders is not created correctly. I fixed this in my own repository. Fix could also be made in the fetchOrders function in the AmazonOrderList class. Possible fix could also be:
public function fetchOrders($r = true){
    [..]

    $url = $this->urlbase.'/'.$this->urlbranch;

    $query = $this->genQuery();

    $path = $this->options['Action'].'Result';
    [..]
}

My fix:
https://github.com/HMAZonderland/phpAmazonMWS/commit/bb9cf78e715b55ac5e4a1b28538f9ea50cd35e61

My bad. Forgot that the url is set in the config and should include the tailing slash.

Sounds like the issue is already resolved.
At some point in the future, I want to improve the config code so that the URL works whether or not the ending slash is included in the config file.

Added a feature to the master branch so that the URL will work with or without the slash at the end.


Convert remaining markdown into reStructuredText

The documentation for web-token still contain title written in Markdown.
In don't really know why there are two 10-files and if this is something to worry about.

Oh, I just came across #1235 before this one and merged it although this PR was open before.
Very sorry about that. Thanks for the PR!

No problem


Support creating a cluster with no default unmanaged add-ons: bootstrap_self_managed_addons=false.

Is your request related to a new offering from AWS?
Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

Yes ✅: please list the AWS provider version which introduced this functionality
v5.58.0 - https://github.com/hashicorp/terraform-provider-aws/pull/38162

Is your request related to a problem? Please describe.
I want to use a different CNI (Cilium) and I want to install CoreDNS using my own Helm chart so I can have full control over the config.
Describe the solution you'd like.
I want to pass bootstrap_self_managed_addons=false to the eks_cluster resource.
Describe alternatives you've considered.
At the moment I have a null_resource that removes the provisioned resources after the cluster is created.
Additional context
I'm happy to raise a PR and implement this.

@bryantbiggs AWS provider 5.58.0 includes the required changes. #3099 seems to already implement that.

This issue has been resolved in version 20.18.0 :tada:


entity_statistic_value should have one column for numerics and one for strings

..because we have an unsafe cast as part of #394

Have a similar unsafe cast as a part of #444.  This is because we assume a numeric when extracting the pre-calculated value.
Correcting this requires a wider refactor


Group Multiple Y-Axis  chart

Is your feature request related to a problem? Please describe.
I would Like to group multiple Series on Y-Axis . For example If I have "Number of Requests" , "Number of Users"  using a Y-Axis with  values as counts . Then I want another y-Axis average response time which is in seconds (Time) . Currently i don't see option tp group them
Describe the solution you'd like
The seriesName attribute for yAxis should be array so that we can group
Describe alternatives you've considered
Currently i have 3 yaxis
Additional context
None

Needed by us too. I'll try to make a PR for this if I can't somehow hack this for my current feature.


Create BinarySearch

@ShauryaChaubey  contribute here https://github.com/Ishaan28malik/Get-Dev-Resources instead


Added decryptImage and saveImage functions

Why don´t you implement it more general for all possible media types?

Yes, it's a WIP, but at the moment I don't have enough time to test all media types.
For the moment I think that image decrypting is a much more requested feature.

@nilsburg I would like to talk with you in private, can you reply me at this post please?


Transition to django migrations

Doing this separately will hopefully make fixing #31 more focused.

This is a bit complicated. We have a post-save signal which runs after any other model gets saved. On an initial migration, the auth and content-type apps create some model instances, which then try to run that post-save signal, which fails because the treenav migration hasn't run yet.
Is the best answer to write a post-migrate signal for treenav that only installs the post-save handler after treenav has been migrated?


Firefly unable to open from firefox [Bug]:

Issue description
Firefox is unable to open Firefly on Ubuntu 21.10 - When navigating to a Soonaverse site pop up that should open Firefly, it does not open as expected. Firefly has to be manually opened.
Expected behaviour
Firefly should open when selected from the Firefox prompt
Actual behaviour
Firefly does not open.
Can the issue reliably be reproduced?
Yes
Steps to reproduce the issue
In latest firefly
Latest version of firefox
navigate to Soonaverse web page and purchase NFT (or something that will prompt to open Firefly)
Select the FIrefly option to open Firefly
Then allow the pop up that is attempting to open Firefly...
Firefly will not open.
Diagnostics
No response
Errors
No response
Duplicate declaration

[X] I have searched the issues tracker this issue and there is none

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Hello, thanks for reporting this issue. But you should better report this on Soonaverse Discord.


Task distribution.

Hello dear members of the group. We have to distribute the tasks for the group, right? @LinxuanHu @s4il3sh

Yes. We need to do it. I will try unit testing.

Or I can also go for Algorithm.

Let's divide our roles on these basis:
Algorithm -?
Documentation - ?
Unittest -?
Maintainer - @uarif

Who is going to do the algorithm part? Can you share some insights on that?

I just realized that we need to divide our tasks on the basis of task1, task2, and task3 which is the requirement of our homework.  Well, I will choose task1. Is that ok with you guys?

Okay, I will do scond task then

I will do second task then @s4il3sh @LinxuanHu


Add support for linux target

Renamed build.windows.xml to build.xml
Added support for linux target

thanks!


Revert the changes in kustomization

Reverted change is kustomization to avoid specific name.

/assign @tliron

/lgtm
/approve


required=False not working as expected for string fields

Description:
Expected behavior:
The request should be processed successfully, even if the string field is left empty, since required=False is specified for the field.
Actual behavior:
The request fails, and a validation error is returned, indicating that the string field is required, despite setting required=False.
Additional information:
I've tested this issue on django_jsonform version 2.17.1, using Python 3.8.10 and Django 3.2.18
Relevant code snippets:
schema = {
        "type": "dict",
        "keys": {
            "required_field": {
                   "type": "string",
                   "required": False
            },
            "non_required_field": {
                  "type": "string"
             }
        },
    }

value = {"required_field": "Hello, world!"}

validator = JSONSchemaValidator(schema=schema)
validator(value)

This throws an exception, saying: These fields are missing from the data: non_required_field is required.
It's possible that the issue lies within the validation process or the way the JSON schema is handled.
Please let me know if there's any additional information required or if you have further questions.

Yes, this is kind of a "known" issue at this point.
As per the JSON Schema spec, all properties are optional by default. But I've chosen not to follow that rule and instead stick to how things work in Django.
E.g., even if a field is not required, such as — name = models.CharField(required=False)  — Django will still insert an empty string in the database.
So, we interpret the required keyword as to whether this field (key) can be empty or not.
At the very least, we require all the keys declared in the schema to be present in the data. So, the built-in JSONSchemaValidator will consider this valid: {"required_field": "", "non_required_field": ""}

I'm closing this issue because of lack of activity. And also because the existing behaviour will most likely not change.
If you have more arguments to make or questions to ask, feel free to reopen the issue.


Use containerd log trace

Based on https://github.com/containerd/containerd/pull/2111.
Please hold until https://github.com/containerd/containerd/pull/2111 is merged.

containerd/containerd#2111 is merged. Will merge this PR after test passes.


How to iOS APNS only?

Hi @ben-xD,
Thank you for having this native solution for iOS APNS, sorry I'm posting in Issues, I didn't see a Discussion section.
We currently have implemented Firebase FCM setup for Android which is finally working with the config, FlutterLocalNotifications, and event handlers, etc.
I'm assuming none of the Firebase portion needs to be part of a iOS native solution.
Is a way to use push where it doesn't handle any Android initialization and just sets up the iOS APNS portion (guessing most of it is turning on native message receiving in Swift and adding custom handlers)

Just to try answer my own question, would the easiest to be to clone / fork our own version of the push package and remove pubspec.yml > flutter: plugin: platforms: android ?  would that cover removing all the android stuff?

Hey @sonjz, I guess you would need to do that, based on https://github.com/flutter/flutter/issues/80374 and https://github.com/flutter/flutter/issues/59657
There is a Flutter PR ready/open with the long term fix for it (https://github.com/flutter/flutter/pull/137040) so you may be able to remove your fork in the future.

thanks @ben-xD, this would be great, i'd love to turn off firebase's as well and just use android.
here's some finding, i'll post my fork here for others once i can verify it working (please keep issue open until i can do so):

i'm partially way through the fork, and finally got it to compile, so I'll test out integrating it with my app now and see if can i fetch a notification.

thanks for the comments on the Federated package dependencies vs Local development dependencies, since i was using a fork locally i had to switch them all out to avoid hitting pub.dev.

i did find there was a class conflict for RemoteMessage with Firebase's package:firebase_messaging_platform_interface/firebase_messaging_platform_interface.dart' and Push's package:plugin_platform_interface/plugin_platform_interface.dart.  I ended up just refactoring the one in Push with RemoteMessage1` and it seems to compile

Hi @sonjz did you get this work? I don’t even have an android folder in my project and would love to keep it that way and your iOS only fork would be a life saver.


xfe enrichment

 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.sulakshan vajipayajula 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.

Thank you. Made those changes. @subbyte


Implementing secret support proposal in devcontainers CLI

Implement the secret support from the proposal
Below are the considerations and recommendations with regards to the potential implementation.
Using secrets
Today many consumers are leveraging remoteEnv to pass in secrets. So it is a basic requirement that secrets should be used and behave the same way as remoteEnv do.
Securely handle secrets
Secrets should be handled securely at all times.

Secrets should not be exposed in plan text at rest and in transit.
Do not persist secrets on the container labels or long lived permanent caches
Redact/mask secrets before writing to logs and output.

Notes
Notes on how this proposal may be adopted by the dev containers CLI (reference implementation).
Passing secrets to the commands
Secrets should not be passed directly in the command line since that would risk it getting stored in command history. Best way to pass secrets would be through a json file, where in the file path is supplied in a command line argument named --secrets-file.
The dev containers CLI may support a default json file path with respect to the .devcontainer root, which will be used if the user does not provide a path explicitly using --secrets-file argument.
Secrets should be passed to the following dev containers CLI commands.
Phase 1

up
run-user-commands

up, run-user-commands will use the secrets for use cases like lifecycle hooks (similar to remoteEnv). We do not plan secrets support for build command since we do not have a demonstrated requirement, as well as to avoid potentially baking in the user secrets into the docker images.
Phase 2
In phase 2 the support for secrets can be expanded to additional commands such as set-up and exec.

First round of implementation => https://github.com/devcontainers/cli/pull/493

What is in the PR?
Secret support for run-user-commands& up commands.
A json file containing secrets can be passed in via a command line argument --secrets-file.
Secrets will be applied similar to remoteEnv
File format:
{
    "SECRET_NAME": "value"
}

Special handling for the secrets such as masking them from logs is not in scope for this PR.

I believe this is now complete via https://github.com/devcontainers/cli/pull/493, but please reopen if not!


First time not opening

When I Install My app first time , not working we slide after clear cache and data its working good so.. please suggest me for that
thanks for reading my Issue
regards

Hi @vocsygautam 👋
have you tried running the examples?


Builder fails to cleanup object store slugs

Destroying an app via Deis cli does not clean up the build slugs when app name fails to match regex.
Builder Version: 2.7.1
Storage Driver: Swift
Steps to reproduce:
deis destroy --app=my-app
kubectl logs BUILDER --namespace=deis
Only log line written is clearing the cache:
Cleaner deleting cache home/my-app/cache for app my-app
Missing the lines in code at #445
log.Info("Cleaner deleting slug %s for app %s", obj, app)
my-app had over 100 builds.
Issue is potentially the regex matching:
gitRegex, err := regexp.Compile(^/ + fmt.Sprintf(gitreceive.GitKeyPattern, app, ".{8}") + "$")

@markkwasnick can you describe the slug tarball names in your object store? they should look something like /home/jangly-tailbone:git-11241b3a.

Here are a couple
fileshome/synergy-sf:git-9aed6276/push/slug.tgz
fileshome/synergy-sf:git-9dc6342c/push/slug.tgz

This issue was moved to teamhephy/builder#16


Unable to execute JS call: __fbBatchedBridge is undefined

Hi guys,
I believe a similar sounding bug has already made it here some time ago (just searching the issue tracker).
The message in the Xcode console is
2016-03-03 22:49:51.428 [warn][tid:main][RCTDevMenu.m:323] RCTSourceCode module scriptURL has not been set
2016-03-03 22:49:51.432 [fatal][tid:com.facebook.React.JavaScript] Unable to execute JS call: __fbBatchedBridge is undefined

Steps to reproduce (using "react-native": "^0.21.0")

Execute react-native init AwesomeProject
open AwesomeProject.xcodeproj in Xcode
edit AppDelegate.m, uncomment jsCodeLocation = [[NSBundle mainBundle] URLForResource:@"main" withExtension:@"jsbundle"];
Product -> Run

I'm just trying to follow the docs from here https://facebook.github.io/react-native/docs/running-on-device-ios.html#using-offline-bundle maybe I'm misunderstanding something.
I also tried generate the main.jsbundle file with react-native bundle --entry-file ./index.ios.js --platform ios --bundle-output ios/main.jsbundle but the same error happens when clicking Run
Thanks for all your work on React native, it's really fantastic!

Hey,
So, none of the already proposed solutions in the closed issues works for you yet? :(
Leaving the search link for reference: https://github.com/facebook/react-native/issues?utf8=✓&q=__fbBatchedBridge

Hey,
Thanks for getting back so quickly. Yeah, tried a handful yesterday and a few today – but it's hard to do a complete enumeration...
However, irrespectively of whether there is a fix in one of those Issues, this is likely close to a step-by-step copy&paste instructions that new users will follow, since this is the vanilla AwesomeProject.
Here is what i tried:

https://github.com/facebook/react-native/pull/5779 change url dev to false (breaks with a new error) add libReact.a to test target (same error, no change)

https://github.com/facebook/react-native/issues/5820 react-native bundle --entry-file ./index.ios.js --platform ios --bundle-output ios/main.jsbundle the reference to main.jsbundle is present (same error, no change)

https://github.com/facebook/react-native/issues/4881 running react-native run-ios with AppDelegate.m modified and Xcode turned off gives the original error message, so at least things are consistent here. the packager is running so issuing react-native start has no effect

Again, thanks for getting back so fast and providing this support.

Hey,
Can you try commenting out the following lines https://github.com/facebook/react-native/blob/master/packager/react-native-xcode.sh#L15-L18 . It was mentioned here and worked for me

That fixed for me, thanks @shahchirag and @grabbou
in node_modules/react-native/packager/packager.sh
Replace
    if [[ "$PLATFORM_NAME" = "iphonesimulator" ]]; then
      echo "Skipping bundling for Simulator platform"
      exit 0;
    fi

with
#    if [[ "$PLATFORM_NAME" = "iphonesimulator" ]]; then
#      echo "Skipping bundling for Simulator platform"
#      exit 0;
#    fi

Out of curiosity, and largely as a digression to this issue, is this a bug? Or is it due to xcode/simulator?
Additionally, i'm guessing not everybody is dependent on the xcode-heavy workflow that i go through, but how else does one upload the Archived version of the code to testflight and alike?

:+1:  This solution also worked for me. I just started a new project on React-Native 0.21.0

I know this sort of feels like a hack, but currently that's the only way to fix it. I believe this would be fixed in the coming days.

I don't know why those lines exist...you should absolutely have the option of running the bundled code on the simulator.

The hack works, but any updates on this from the React team?

Worked here too RN0.22

Same code need to comment in node_modules/react-native/packager/react-native-xcode.sh
if [[ "$PLATFORM_NAME" = "iphonesimulator" ]]; then            echo "Skipping bundling for Simulator platform"        exit 0;          fi

The uncomment solution works!
Just wondering is there any side effect for this?
My RN version: 0.26.2

@longsangstan The code is for speeding up build times as stated
# Speed up build times by skipping the creation of the offline package for debug
# builds on the simulator since the packager is supposed to be running anyways.

, so commenting it should just affect build-times, no other side-effects supposedly.

Should this still be occurring for 0.39.2?
I'm getting the same error message, and the fix is working on macOS, building for iOS.

Just ran into this issue today as well, any ideas?

@tonydiepenbrock, same here!

Occurring on 0.40.0

I am getting this issue no 0.41 as well! Commenting out fix doesn't work.. Any ideas?

Getting error on react-native 0.41.2. Commenting https://github.com/facebook/react-native/blob/master/packager/react-native-xcode.sh#L17-L20 fixes it for me.

Occurring on 0.41.0

I was having this problem on 0.42.0 when launching from vscode. I somehow got it fixed by quitting the simulator, and first running react-native run-ios. Now it works when I launch from vscode.

Running react-native-git-upgrade fixed this for me.

I have the same problem on 0.42.0, commenting didn't help me, and when I tried "react-native-git-upgrade" , it just says "command not found". Any ideas how to fix it?

@Luckygirlllll did you run npm install -g react-native-git-upgrade first?

@MattyK14 Just have tried it, so I done react-native-git-upgrade, and after that react-native run-ios, and the error didn't disappear.

I'm on the latest version 0.43 and still getting this issue? :(

Also getting this on 0.44

I was getting this in 0.44, had to import ./app/index instead of ./app for some reason

0.46 keep constantly getting this error.

Getting the exact same in 0.46.1.

same here, 0.45 with expo sdk 18

same here with expo xde 2.19.2

Same here. Every time when I do Remote JS Debugging, I get this error on my iOS simulator. If I do not do Debugging, it is fine.

I'm getting it in production on iOS. Any news?

Not getting this error anymore. Maybe because:

I started using LAN or localhost hosts of Expo.
Expo got updated
Started using simulator more often than phone itself for testing


go 1.5 already includes the SSE42 updateCastagnoli() function

I was playing with this repo mainly as a way to teach myself code and including optional assembly versions of some routines.  Very nice.
So I extended your benchmarks to test the Castagnoli version as well, and found that it wasn't any faster than the system hash, and sure enough the go 1.5 version includes the SSE 4.2 code to use the new crc32c opcode.  The IEEE crc32 is still slow.
It might be a good idea to note that in the README

I am not sure what you mean. I have adjusted the documentation, since it is carryless multiplication your CPU must support, not only SSE 4.2.

For example I added some tests like this:
func BenchmarkCCrc1KB(b *testing.B) {
	benchmark(b, New(MakeTable(Castagnoli)), 1024)
}

func BenchmarkCStdCrc1KB(b *testing.B) {
	benchmark(b, crc32.New(crc32.MakeTable(Castagnoli)), 1024)
}

And found that for Castagnoli the std library was the same speed. And looking I see it already included that support.   https://golang.org/src/hash/crc32/crc32_amd64.s
I assumed that you wrote all of the assembly files and the std library just copied part of them. Now I am guessing they always had the fast Castagnoli version and you extended it to include the SSE code for the IEEE crc as well.

Yes, I started this as a copy of the standard library.
This is the current "tip" version, which includes my code: https://tip.golang.org/src/hash/crc32/crc32_amd64.s

BTW another optimization that I notice isn't included is that the slicingBy8 optimization can still be used in the Castagnoli case.

Oh yes, that might be nice for other platforms.

Added in PR #5


only verify client cert if TLSCertAuth is active

If TLSCertAuth is not provided as one of the preferred auth types then skip verification

closes #271

@MaxFedotov I would appreciate your help on this since I have some concerns, please, @logikone feel free to join the discussion!
Could mTLS disabling allow a privilege escalation in the proxy? This shouldn't happen, theoretically, since we got the function GetUserAndGroups that is returning the user according to the preferred authentication type.

I don't think it should allow privilege escalation if the cert is not being checked for claims. Though one thing I did notice is that, once I changed the client cert that our ingress controller is sending to one that was signed by the kube ca, every request was able to list all namespaces. The cert was present and valid but had no claims, and the bearer token was not checked at all. This seems like it might be a bug. My assumption was that if the cert did not have any claims the request should have no access.
This could have been something else strange going on with the way I had things setup at the time though, and I have not done any troubleshooting to try and repro.

Though one thing I did notice is that, once I changed the client cert that our ingress controller is sending to one that was signed by the kube ca, every request was able to list all namespaces.

I'd say this happened because you were using the certificate of the Ingress Controller that has list capabilities of Namespace resources. If this isn't the case, a bug case should be rise to investigate it properly and address a fix.


Testable code defeats ignored errors 🥊🥊🥊

https://www.youtube.com/watch?v=xotfWQnwtBQ
Only 2 potential @phpstan bugs remained in ignoreErrors: :)

Why does php-cs-fixer say that \is_numeric() should be is_numeric() ??

The native_function_invocation rule has a few configuration options, one of which is configured to prefix only functions that are specially optimized by Zend

Thank you.

So is_numeric can be hijacked.
<?php

namespace Sentry;

function is_numeric($data)
{
    return new \Exception('bang!');
}

@ste93cry We've got a huge Benefit: https://github.com/phpstan/phpstan/issues/3133 is resolved in PHPStan.
I think I live in my fantasy world: I cannot bear those ignoreErrors:.
I leave this PR to you.
I'm sorry for being weak.

If you do not plan to finish this PR I will take it over and merge it once PHPStan releases the version that fixes at least the is_numeric issue. Thank you for working on this anyway, much appreciated

You're welcome.

@ste93cry An avalanche 🏔 of improvements ❤

https://github.com/phpstan/phpstan/releases/tag/0.12.40

Closing this as stale. Feel free to restart this on top of the main branch if possible.

Thank you!
I've already had my benefits.
This was an inspirational PR :)


Wiki nicer pre code handling.

can copy/paste code blocks with color. Syntax highlighting is inline css, not classes.
nicer rendering when dealing with tinymce oddity of needing to wrap a code block in a pre.

Coverage increased (+0.08%) to 83.91% when pulling 90638412ad9f78425c774eed66a5c01ecbbb56a3 on wiki-nicer-pre-code into 382911633d4c2d169fc9a877d9078780f32fe918 on master.


feat: expose description data to resolve_data

This PR brings the following changes:

more friendly error tips when tsconfig not founded.
expose description data(package.json) to resourceData. close https://github.com/web-infra-dev/rspack/issues/2298

!bench


Encapsulation

chatGPT: Yes, encapsulation can make AI safer and more ethical. Encapsulation refers to the practice of running AI algorithms and models in closed environments or "encapsulations" that restrict access to the outside world. This can minimize risks associated with the operation of AI systems, including potential privacy, security and ethical implications.
For example, encapsulation can be used to prevent AI models from accessing data that is not authorized for their use, or from being improperly trained or manipulated. Also, one can design the AI systems to be transparent and explainable, which can help build trust in their results and decisions.
However, encapsulation alone is not a panacea. There remain challenges associated with the development and implementation of AI systems, including the need to ensure that the AI algorithms and models are fair, balanced and free from bias. Also, AI systems still need to be overseen by human experts to ensure they are operating safely, ethically, and lawfully.

It's OK


Reconciliation for default broker selection

This PR is a cherry-pick of d703711f764a39db2ae8123e3ec5239e2630c699 in eventing-operator.

We need to update the manifest as well. That's why the tests fail.

/test pull-knative-sandbox-operator-upgrade-tests

@googlebot I consent

/lgtm


properly urlencode pic cached documents

I made a number of changes to make our document cache much more robust. Before deploying we need to make sure that we are properly urlencoding the urls. As we do this in a few places, I'm going to wait till @reginafcompton comes back to deploy the changes to the document cache to production.

Use the pic.staging.datamade for the new url.

I have an initial solution for this on the pic branch. It works with pic-staging.datamade.us.
However, it seems that we actually want to create a standardized version of full_text_doc_url in django-councilmatic core. We can use the work on the pic branch as a good starting point.
https://github.com/datamade/django-councilmatic/issues/136

This PR closes this issue.
Related: The PIC changes are working well. Currently, we have LA Metro pointing to pic-staging.datamade.us. @fgregg let me know if you'd like to deploy PIC to production, and we can point LA Metro accordingly.

Sounds good.
On Mon, Aug 14, 2017 at 3:51 PM, Regina Compton<EMAIL_ADDRESS>wrote:

This PR closes this issue.
Related: The PIC changes are working well. Currently, we have LA Metro
pointing to pic-staging.datamade.us. @fgregg https://github.com/fgregg
let me know if you'd like to deploy PIC to production, and we can point LA
Metro accordingly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/datamade/la-metro-councilmatic/issues/184#issuecomment-322305880,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAgxbRURx_HpBmRpW6Kk7upQMoE1y5xHks5sYLM2gaJpZM4OdTlW
.

--
773.888.2718

PIC is deployed to production, and LA Metro points to pic.datamade.us.
Closing!


show elements that are conditional by choice_field

@twinge these elements use choice_field_id instead of the conditional_* column
that I set up; they need to be displayed in the answers

This is a really high priority fix for Scott so I'm going to just merge it.. can definitely change anything after your comments


bare_io::error::Error instead of bare_io::Error

Hello!
I'm having some issues porting a std-using library to no-std using core2/bare-io. I am getting some compiler complaints when I attempt to use my now-ported library:
              |    | expected struct `bare_io::error::Error`, found struct `bare_io::Error`
              |    | help: change the output type to match the trait: `Result<(), bare_io::error::Error>`
              |    |

The library code I have ported to use core2 is here. It builds correctly and passes the built-in library tests/benchmarks in both std and no-std mode.
I don't think I did anything fancy when porting to use bare-io.... I just replaced
    std::io::Write,
    std::io::Result as IOResult,

with
    bare_io::Write,
    bare_io::Result as IOResult,

If this is my error and I am using the library incorrectly, I apologize but either way I would welcome any guidance on how to fix this issue. I believe the error originates when an error is attempted to be handled with a ?.... but I believe this sort of error chaining is one of the main purposes for core2. I'd be happy to show the full error trace if there is interest. Thank you for your time!

Your Cargo.toml includes bare-io, which predates this crate and only included equivalents to std::io. Change to using core2 = "0.3" and use core2::io for IO-related things, such as IO errors. core2::error::Error is equivalent to std's Error type.

Thank you for the help! Sorry it was such a basic issue.


conflict with ecthelionvi/NeoColumn.nvim

I install this plugin with ecthelionvi/NeoColumn.nvim same time.
bugs when enabled with ToggleNeoColumn
Error detected while processing CursorMoved Autocommands for "*":
Error executing lua callback: Vim:E803: ID not found: 1000
stack traceback:
[C]: in function 'matchdelete'
...l/share/nvim/lazy/stcursorword/lua/stcursorword/init.lua:53: in functi
on 'matchdelete'
...l/share/nvim/lazy/stcursorword/lua/stcursorword/init.lua:77: in functi
on 'highlight_same'
...l/share/nvim/lazy/stcursorword/lua/stcursorword/init.lua:158: in funct
ion <...l/share/nvim/lazy/stcursorword/lua/stcursorword/init.lua:154>

I read the source code of this plugin and noticed that it uses fn.clearmatches, which clears all existing matches, including the match for cursorword. I can fix this by using pcall, but after toggling, the cursorword is trigger at the next movement, I can't do any thing for this.

暂时也只能这样了


Postgres migrations are failing due to ordering issues

Summary
The short version is that when spinning up a new Kong node, I'm getting migration issues:
Error: /usr/local/kong/share/lua/5.1/kong/cmd/start.lua:21: [postgres error] Error during migration 2016-01-25-103600_unique_custom_id: ERROR: relation "consumers_custom_id_key" already exists

I've seen this happen several times now, and I've determined that it's due to some error in how Kong is iterating migrations to run vs migrations that have been run.
I dropped some debug code into factories.lua to see what's being compared, and it bombs out:
1: seeing if we've migrated 2015-01-12-175310_skeleton, migration at this position is 2015-01-12-175310_skeleton
2: seeing if we've migrated 2015-01-12-175310_init_schema, migration at this position is 2015-01-12-175310_init_schema
3: seeing if we've migrated 2015-11-23-817313_nodes, migration at this position is 2015-11-23-817313_nodes
4: seeing if we've migrated 2016-02-29-142793_ttls, migration at this position is 2016-02-29-142793_ttls
5: seeing if we've migrated 2016-09-05-212515_retries, migration at this position is 2016-09-05-212515_retries
6: seeing if we've migrated 2016-09-16-141423_upstreams, migration at this position is 2016-09-16-141423_upstreams
7: seeing if we've migrated 2016-12-14-172100_move_ssl_certs_to_core, migration at this position is 2016-12-14-172100_move_ssl_certs_to_core
8: seeing if we've migrated 2016-11-11-151900_new_apis_router_1, migration at this position is 2016-11-11-151900_new_apis_router_1
9: seeing if we've migrated 2016-11-11-151900_new_apis_router_2, migration at this position is 2016-11-11-151900_new_apis_router_2
10: seeing if we've migrated 2016-11-11-151900_new_apis_router_3, migration at this position is 2016-11-11-151900_new_apis_router_3
11: seeing if we've migrated 2016-09-16-141423_upstreams, migration at this position is 2016-01-25-103600_unique_custom_id
12: seeing if we've migrated 2016-01-25-103600_unique_custom_id, migration at this position is 2017-01-24-132600_upstream_timeouts
migrating core for database kong
core migrated up to: 2016-09-16-141423_upstreams

It's running 2016-09-16-141423_upstreams twice! WTF?
Checking Postgres confirms the bad data:
 core                  | {2015-01-12-175310_skeleton,2015-01-12-175310_init_schema,2015-11-23-817313_nodes,2016-02-29-142793_ttls,2016-09-05-212515_retries,2016-09-16-141423_upstreams,2016-12-14-172100_move_ssl_certs_to_core,2016-11-11-151900_new_apis_router_1,2016-11-11-151900_ne
w_apis_router_2,2016-11-11-151900_new_apis_router_3,2016-01-25-103600_unique_custom_id,2017-01-24-132600_upstream_timeouts,2017-01-24-132600_upstream_timeouts_2,2016-09-16-141423_upstreams}

Manually correcting the data:
kong=> update schema_migrations set migrations = '{"2015-01-12-175310_skeleton", "2015-01-12-175310_init_schema", "2015-11-23-817313_nodes", "2016-02-29-142793_ttls", "2016-09-05-212515_retries", "2016-09-16-141423_upstreams", "2016-12-14-172100_move_ssl_certs_to_core", "2016-11-11-151900_new_apis_router_1", "2016-11-11-151900_new_apis_router_2", "2016-11-11-151900_new_apis_router_3", "2016-01-25-103600_unique_custom_id", "2017-01-24-132600_upstream_timeouts", "2017-01-24-132600_upstream_timeouts_2"}' where id = 'core';
UPDATE 1
kong=> select * from schema_migrations;
          id           |                                                                                migrations

-----------------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------------------------------------------------------------
 core                  | {2015-01-12-175310_skeleton,2015-01-12-175310_init_schema,2015-11-23-817313_nodes,2016-02-29-142793_ttls,2016-09-05-212515_retries,2016-09-16-141423_upstreams,2016-12-14-172100_move_ssl_certs_to_core,2016-11-11-151900_new_apis_router_1,2016-11-11-151900_ne
w_apis_router_2,2016-11-11-151900_new_apis_router_3,2016-01-25-103600_unique_custom_id,2017-01-24-132600_upstream_timeouts,2017-01-24-132600_upstream_timeouts_2}

Then we restart Kong:
# service kong start
serf........not running
nginx.......not running

Error: Kong is not running at /usr/local/kong

  Run with --v (verbose) or --vv (debug) for more details
Starting service...
1: seeing if we've migrated 2015-01-12-175310_skeleton, migration at this position is 2015-01-12-175310_skeleton
2: seeing if we've migrated 2015-01-12-175310_init_schema, migration at this position is 2015-01-12-175310_init_schema
3: seeing if we've migrated 2015-11-23-817313_nodes, migration at this position is 2015-11-23-817313_nodes
4: seeing if we've migrated 2016-02-29-142793_ttls, migration at this position is 2016-02-29-142793_ttls
5: seeing if we've migrated 2016-09-05-212515_retries, migration at this position is 2016-09-05-212515_retries
6: seeing if we've migrated 2016-09-16-141423_upstreams, migration at this position is 2016-09-16-141423_upstreams
7: seeing if we've migrated 2016-12-14-172100_move_ssl_certs_to_core, migration at this position is 2016-12-14-172100_move_ssl_certs_to_core
8: seeing if we've migrated 2016-11-11-151900_new_apis_router_1, migration at this position is 2016-11-11-151900_new_apis_router_1
9: seeing if we've migrated 2016-11-11-151900_new_apis_router_2, migration at this position is 2016-11-11-151900_new_apis_router_2
10: seeing if we've migrated 2016-11-11-151900_new_apis_router_3, migration at this position is 2016-11-11-151900_new_apis_router_3
11: seeing if we've migrated 2016-09-16-141423_upstreams, migration at this position is 2016-01-25-103600_unique_custom_id
12: seeing if we've migrated 2016-01-25-103600_unique_custom_id, migration at this position is 2017-01-24-132600_upstream_timeouts
migrating core for database kong
core migrated up to: 2016-09-16-141423_upstreams
Error: /usr/local/kong/share/lua/5.1/kong/cmd/start.lua:21: [postgres error] Error during migration 2016-01-25-103600_unique_custom_id: ERROR: relation "consumers_custom_id_key" already exists

And select from psql again:
 core                  | {2015-01-12-175310_skeleton,2015-01-12-175310_init_schema,2015-11-23-817313_nodes,2016-02-29-142793_ttls,2016-09-05-212515_retries,2016-09-16-141423_upstreams,2016-12-14-172100_move_ssl_certs_to_core,2016-11-11-151900_new_apis_router_1,2016-11-11-151900_ne
w_apis_router_2,2016-11-11-151900_new_apis_router_3,2016-01-25-103600_unique_custom_id,2017-01-24-132600_upstream_timeouts,2017-01-24-132600_upstream_timeouts_2,2016-09-16-141423_upstreams}

And the bad entry is back.
At a fundamental level, this is happening because the migration code is very sensitive to indexing issues. The "migrations to run" table is receiving an order that disagrees with the DB, and then it runs an idempotent migration, which succeeds, and then writes a duplicate entry to the migrations table, which
completely breaks the ordering comparison for future runs. I think there are two issues here:

The "migrations to run" table is somehow ending up FUBAR by the time it hits migrate(). I haven't worked out why this is happening yet.
The migrator doesn't check to see if the migration to run actually appears anywhere in the list - it only checks the expected position. If there is an index mismatch, it's going to try to re-migrate. This should probably be backstopped by producing a {[name] = true} dict which each migration is checked against prior to being run.

Additional Details & Logs

Kong version 0.10.0/HEAD (0e7c8f3840d0bc6461584ff8dee1d75402ab9989)
Amazon Linux, PostgreSQL 9.5.4 via AmazonRDS

I'm thinking this might be an artifact of my packaging system - false alarm(ish). I'm seeing a dao/migrations/postgres.lua that doesn't match what's in git, and is clearly invalid. Trying to track down why that's happened, but in the meantime, I maintain that the migration procedure should be more robust in that it should check the entire current_migrations table for a potential migration, rather than just the current index, to guard against index mismatches causing migration issues in the future.

This was caused by accidentally trying to start up an rc3 node in the same cluster as a HEAD node. The mismatch in migrations screwed up my schema_migrations table, which I can fix by hand, but it would probably be a good idea to make the migrator resilient against that kind of thing.

I have the same mistake. I would really like to know how you fixed it by hand

Seems like you figured it out this @cheald, closing this now :)

+1

In my case custom_id was blank in db, just add some value.


[Bug] Distro logo getting cut off when reducing the amount of information printed

Basically I removed some information from the output as its really too much for my taste with the default configuration.
The Arch logo gets cut off where the color bar ends rather than adapting.

Merged and pushed to the AUR. Thanks for the contribution.


Use nullable type. Fixes #56

It should use nullable type but it wasn't the case for GraphQLList.

awesome, thanks a lot!


Material DisneyBxdf don't work

Material DisI test scene "100spheres+plane+ibl+disney" in scene_io_test.cpp.
The DisneyBxdf material is not rendered.neyBxdf don't work

We are currently reworking our material system, so stay tuned.


Bugfix/666 [GithubBrowserSample] Lint errors/warnings and generally adhere to the Kotlin Style Guide

CLA confirmed for all authors.

I confirm!


[C++][Parquet] Large file concerns with fseek/ftell

I've read that fseek/ftell can have issues with large files:
https://www.securecoding.cert.org/confluence/display/c/FIO19-C.+Do+not+use+fseek()+and+ftell()+to+compute+the+size+of+a+regular+file
This is not urgent, but should be examined in some more detail.
Reporter: Wes McKinney / @wesm
Assignee: Wes McKinney](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=wesm) / @wesm
Note: This issue was originally created as PARQUET-550. Please see the migration documentation for further details.

Wes McKinney / @wesm:
This was resolved by PARQUET-818 (OS file interactions are handled by libarrow_io, which does not have the large file concerns cited here)

Wes McKinney / @wesm:
Ran into this in another project recently: https://github.com/wesm/feather/issues/155. Suffice to say, Parquet files over 2 GB can't be read with parquet-cpp right now on all platforms. I'll look into addressing both of these issues at the same time


Fix typo in helm chart

Motivation
Incorrect value is being used in Pulsar Helm template autorecovery-deployment.yaml
Modifications
Proper variable name set.
Verifying this change
Fixed variable name is already set in values.yaml and values-mini.yaml.
This change is a trivial rework / code cleanup without any test coverage.
Documentation
None needed.

// Invalid color configuration option [enabled]. Supported values are (auto|always|never).
run integration tests
// ExecutionException The forked VM terminated without properly saying goodbye. VM crash or System.exit called?
run java8 tests


Ndimage generic filters

This is the final PR to close #2099 and close #3111.
Additionally, the filter code was split into multiple files as it was getting too unwieldy for a single file.
Some notes:

The generic_filter() function cannot exactly match in Cupy and Scipy. Scipy's accepts any Python function with a single ndarray parameter and single scalar return value or a wrapped C function with a specific signature. The Cupy version accepts any fuseable Python function with the same restrictions (ndarray param, scalar return), a RawKernel with almost the same C signature (just missing return value) as with Scipy. It also accepts ReductionKernel with 1 input and 1 output.

Support for new fuseable functions is hackish, the RawKernel and ReductionKernel are significantly more 'legit'

The generic_filter1d() function matches with Scipy even less. It only accepts a RawKernel with a similar C signature (just missing return value). It does not accept any Python functions. This is primarily due to the very odd way that Scipy defined the function.

Additionally due to their odd way Scipy defined the function it isn't as parallelizable and likely has significant performance issues compared to all of the other filter functions

Still in draft state since I would like:

Feedback on the design. Some of this is a bit "radical" maybe and perhaps some people more familiar with Cupy and CUDA can help me straighten it out.
There are no formal tests yet.

Some informal tests which help you gauge speed-up and my results are available at https://gist.github.com/coderforlife/e3a5fffa17be71c2f97779e0c41fb5a1
Speed Summary
1000x1000 input with 3x3, 15x15, and 25x25 filter sizes.
Using raw and reduction kernels are the fastest.
Fused functions are 1.25x to 7x slower (that is 25% to 600% slower) than directly writing the kernels - they get much closer with larger filter sizes.
Numba functions used with Scipy are 6x to 26x slower than fused functions, generally losing more ground as the filter size goes up.
Pure Python functions used with Scipy are then 10x to 200x slower than the numba functions with scipy.
Ultimately, if you can hand-write your CUDA functions expect 200x-10000x speedup over Scipy with Python function. If your function is fuseable you only get a small amount of loss and you get to write it as Python!
I have done personal tests with generic_filter1d, and for larger sizes it does improve upon Scipy, but not nearly as much. I am mainly thinking of that implementation simply to make the library complete (it is still okay, just not stellar).

I have now added the tests but would still like feedback on the design.

@emcastillo Can you give any feedback on the design of these two new functions?

I'll try to do the first pass soon, sorry for the delay

Great!
This is only 2 "public" functions. The one function does have 3 major components to it, and if I had left off fused kernels it would have cut the total code in about half or more. It's just hard since I have a ton of code ready to commit, and there are various inter-dependencies. However, in this case it clearly could have been committed without generic_filter1d and with only support for raw (and maybe reduction) kernels to get it started.

cc: @grlee77

As a note to other reviewers:
The new code that needs to be reviewed is everything in _filters_generic.py and the two functions generic_filter and generic_filter1d within filters.py.
I think all code in _filters_core.py is just pre-existing code that was split out from filters.py and has not been otherwise modified in this PR.
I support the general approach of splitting across these files as I think it is a logical organization and is preferable to one massive file.
I will try to revisit this PR again over the next couple of days.

grlee77 is correct in that much of this is simply from the breaking up of the monolithic file into a few separate files.
@leofang agreed that some of these seem more general than image processing, but I have no idea where they should go. Also, I am unaware of what other internal functions are out there. I have found some of them, but cupy is quite large... any that you see (like the internal.prod you pointed out) would be great. Anything you think should be moved to a more general location please inform me what and where.
@leofang which reduction kernel? I don't have any reduction kernels... unless you mean the RawKernel that takes the specified axis from n long, increases it to n+f+1 temporarily within the kernel, and then reduces it back to n long, but that reduction is an outside kernel. The only other kernel I have written is the ElementwiseKernel which is the major workhorse here, which along the way applies a reduction kernel, but that kernel has to be integrated into the ElementwiseKernel. The main parallelization is across 'pixels' (samples in the signal processing world) and not within the reduction needed for each pixel. Although, I would be willing to try to see if those reductions could be done with CUB, at that point I would assume that the GPU is already full taxed with dealing with each individual pixel.

Some functions that may be more general:

_fix_sequence_args - this is a fairly general function to be used whenever a function accepts a scalar or iterable of scalars
_get_inttype - discussed with someone (I think @emcastillo) about using this in the CArray implementation for deciding what type to choose for indices
a bunch of _filters_generic could be refactored out to provide general support for ripping apart kernels and converting them to C/C++ code for other kernels to be able to reuse, thinking of something like fuse functions being able to integrate from arbitrary (non-raw) kernels
_get_output - in scipy this is actually shared by all of ndimage, it is likely that the other ndimage files have their own version
_check_mode - same as above
_check_origin - same as above, only needed in filters and morphology though

@emcastillo (or maybe someone else, I just think he has had a bunch to do with CArray and CIndexer): is there a reason CArray and CIndexer have no constructor in C++?

Left some comments on my first pass.
The code for supporting fusion kernels is a bit rough, but most probably this is due to the way that fusion is being performed now. I think that to fix this we need to change the fusion interface itself?
Besides that, I don't have any major concerns with the PR. Maybe _broadcast or _transpose could be moved to cupy.core or cupy._kernel.
Regarding why CArray and CIndexers has no constructors. I have currently no idea about this, let me ask the team and I will update the reply

Yeah, I know the fusion kernel stuff is rough, but I was trying to support Python functions. I will remove it for now and we can discuss elsewhere what the interface would need to be.
The functions _indexing, _broadcast_to, and _transpose are only used for fusion kernels so they are actually about to be temporarily removed. However, the goal of all 3 of them is to do those 3 operations on the shape/strides of an array but without needing an actual array, just the shape/strides. In fact, I copied most of the the code from the real versions of those functions, just without the final creation of an array view or error-checking (I removed error-checking since it will have already occurred through the real functions at an earlier point). So maybe those functions could just be refactored to have a version that works on shapes/strides and then a version that calls the shape/stride version and just creates the view from it?
Right now you do the memory layout for CArray and CIndexer in Python. The code I have does it in C, just annoying to set each element in an array that is being casted from an object to some random int/pointer type... I think to actually make it useful from the C++ side you would need to use initializer lists, but not sure.

Thanks for the reply!
Seems reasonable to me.
Regarding the CArray, you can submit a PR to initialize these in C++ if you like and we can discuss about this in that PR.
Currently we don't have any strong argument to support the way we do it, so if your approach makes life easier we are open to change it.

Can you mark it as ready for review?
I would like to merge this today if I don't found issues with it :)

Forgot to do that after removing fusion code... thanks!

Jenkins, test this please

Jenkins CI test (for commit 7e71eb0e4edcab8fbe428059b8308ce4b271744c, target branch master) failed with status FAILURE.

It appears as though a bunch of the functions I moved into _filters_core are used by other modules in ndimage. I think these should actually be moved into common file in ndimage. Scipy has scipy.ndimage_ni_support for this and most of these functions are there. How about we call it cupyx.scipy.ndimage._util?
Functions that I saw had this issue:

_fix_sequence_arg
_generate_boundary_condition_ops

Additional functions that I think should be shared:

_get_output
_check_origin
_check_mode
_get_inttype
_generate_indices_ops

cupyx.scipy.ndimage._util sounds good to me.

Code has been moved around. I have run all of the ndimage tests now and they all passed so let's hope they all pass here as well.

Jenkins, test this please

Jenkins CI test (for commit eb01e33004bb181ba9b73e5a9e013b4356b9bcb6, target branch master) succeeded!

I notice the function signature for cupyx.scipy.ndimage.generic_filter is identical to scipy.ndimage.generic_filter, except for the inclusion of extra_arguments=() and extra_keywords=None (which aren't exposed or available in the cupy version).
I assume they're not there because it was hard to do, perhaps @coderforlife can share some insight?
Context: @jakirkham and I have been adding support for cupy arrays to dask-image, and currently we always try to pass along extra_arguments and extra_keywords and that's how I noticed this.

@GenevieveBuckley The problem is that the "function" given to cupyx.scipy.ndimage.generic_filter is actually a CUDA function. This function definitely won't support extra_keywords. It would be possible to support extra_arguments although the argument types would definitely be limited and it would likely still be very tricky/difficult to implement.

@GenevieveBuckley The problem is that the "function" given to cupyx.scipy.ndimage.generic_filter is actually a CUDA function. This function definitely won't support extra_keywords. It would be possible to support extra_arguments although the argument types would definitely be limited and it would likely still be very tricky/difficult to implement.

Right, I think our best option is what we're doing now, which is to ignore any extra_keywords/extra_arguments if we're dispatching to cupy. It is possible that a user might become confused, and we might think about adding some clarification to our own docs if we find people are running into it (I suspect this might not be a very commonly used feature though)
Thanks @coderforlife!


Net context locking missing for IPv6, CAN and packet sockets

While investigating #29444 I noticed one locking missing from net_context. Also added some way to debug locking in net_context.c and tcp2.c

@pfalcon can you help reviewing this PR, Tomasz is on vacation this week and I would like to get this merged sooner than later.


Remove hardcoded URL for Brigade API

This PR removes the hardcoded URL to the demo API and fetches the current location of the page (since we proxy all requests for /v1 to the Brigade API).
closes #203

One thing to note here: this will break https://azure.github.io/kashti/#!/. It will definitely work for development clusters though!

That's a good point, @bacongobbler, opened #205 to track this.


EditorConfig

This adds the .editorconfig file from this repository. EditorConfig helps align coding styles, using IDE-based enforcement, to ensure consistency and cleaner diffs.
This editorconfig file closely matches the official StyleCop rules. Interestingly, a lot of community conventions within C# are different from what StyleCop recommends. But every rule has some logic behind it.
For instance, requiring the use of "this" ensures that it is always explicit whether you are working with an instance variable, and then makes underscore prefixes redundant. Takes a second to get used to, but of course the rules are configurable.
I used automatic solution-wide refactorings to achieve this PR, and tested that it works with the sample project.
I will make another PR afterwards to add the official StyleCop analyzers at designtime, which have even more rules.
Fixes https://github.com/akgulebubekir/Maui.DataGrid/issues/44

Could you please update Maui.DataGrid.Sample.sln.DotSettings file according your editor settings, so everybody who uses resharper will have same?


setup-mirage-for-integration missing

Reading through the documentation I see mention of setup-mirage-for-integration to perform testing during integration, but in 0.2.0-beta8 there is no sign of this file.
Am I missing something?

I'm seeing the file here: https://github.com/samselikoff/ember-cli-mirage/blob/master/app/initializers/ember-cli-mirage.js not sure how to access this from my own ember app that's importing mirage.

Oh! Right, this file is added to your project thanks to the ember-mirage addon. Even though you may not see it explicitly in your IDE's file structure. I added the file (as instructed: http://www.ember-cli-mirage.com/docs/v0.1.x/manually-starting-mirage/) and it works well.


Fixed markdown in user README

Link pointing to the GitHub issue regarding why a full restart of VS Code is needed was broken.

bors r+