Unable to configure CLI on Vue 3 to fix warning from web components

Version
4.4.5
Reproduction link
https://github.com/blacksonic/todomvc-vue-composition-api
Environment info
Environment Info:

  System:
    OS: macOS 10.15.5
    CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
  Binaries:
    Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
    Yarn: Not Found
    npm: 6.13.4 - ~/.nvm/versions/node/v12.16.1/bin/npm
  Browsers:
    Chrome: 83.0.4103.106
    Edge: 83.0.478.54
    Firefox: 76.0.1
    Safari: 13.1.1
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0
    @vue/babel-plugin-transform-vue-jsx:  1.1.2
    @vue/babel-preset-app:  4.4.1
    @vue/babel-preset-jsx:  1.1.2
    @vue/babel-sugar-functional-vue:  1.1.2
    @vue/babel-sugar-inject-h:  1.1.2
    @vue/babel-sugar-v-model:  1.1.2
    @vue/babel-sugar-v-on:  1.1.2
    @vue/cli-overlay:  4.4.1
    @vue/cli-plugin-babel: ^4.4.1 => 4.4.1
    @vue/cli-plugin-e2e-cypress: ^4.4.1 => 4.4.1
    @vue/cli-plugin-eslint: ^4.4.1 => 4.4.1
    @vue/cli-plugin-router:  4.4.1
    @vue/cli-plugin-unit-mocha: ^4.4.1 => 4.4.1
    @vue/cli-plugin-vuex:  4.4.1
    @vue/cli-service: ^4.4.1 => 4.4.1
    @vue/cli-shared-utils:  4.4.1
    @vue/compiler-core:  3.0.0-beta.15
    @vue/compiler-dom:  3.0.0-beta.15
    @vue/compiler-sfc: ^3.0.0-beta.15 => 3.0.0-beta.15
    @vue/compiler-ssr:  3.0.0-beta.15
    @vue/component-compiler-utils:  3.1.2
    @vue/preload-webpack-plugin:  1.1.1
    @vue/reactivity:  3.0.0-beta.15
    @vue/runtime-core:  3.0.0-beta.15
    @vue/runtime-dom:  3.0.0-beta.15
    @vue/shared:  3.0.0-beta.15
    @vue/test-utils: 2.0.0-alpha.3 => 2.0.0-alpha.3
    @vue/web-component-wrapper:  1.2.0
    eslint-plugin-vue: ^6.2.2 => 6.2.2
    vue: ^3.0.0-beta.15 => 3.0.0-beta.15
    vue-cli-plugin-vue-next: ^0.1.3 => 0.1.3
    vue-eslint-parser:  7.0.0
    vue-hot-reload-api:  2.3.4
    vue-loader:  15.9.2 (16.0.0-beta.3)
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.6.11 => 2.6.11
    vue-template-es2015-compiler:  1.9.1
    vuex: ^4.0.0-beta.2 => 4.0.0-beta.2
  npmGlobalPackages:
    @vue/cli: 4.3.1

Steps to reproduce

Create a webcomponent
Use it in a Vue component
Warning starts to popup: [Vue warn]: Failed to resolve component: x-username
at
at
Try to configure Vue SFC compiler with option

// vue.config.js
module.exports = {
  chainWebpack: config => {
   // get the existing vue-loader rule and tap into its options
    config.module.rule('vue-loader').tap(options => {
      options.compilerOptions = {
         ...(options.compilerOptions || {}), // merge existing compilerOptions, if any
         isCustomElement: tag => /^x-/.test(tag)
      }
    })
  }
}

Unable to reach the config

What is expected?
By modifying the webpack config the warning can be solved, but unable to reach the vue compiler config
What is actually happening?
The warning still remains there

Related issue https://github.com/vuejs/vue-next/issues/1414
I've tried using the official Vue CLI documentation for configuring vue-loader, but no success
https://cli.vuejs.org/guide/webpack.html

I've found the fix.
The Vue CLI config is:
module.exports = {
  chainWebpack: config => {
    config.module
      .rule('vue')
      .use('vue-loader')
      .loader('vue-loader')
      .tap(options => {
        options.compilerOptions = {
          ...(options.compilerOptions || {}),
          isCustomElement: tag => /^x-/.test(tag)
        };
        return options;
      });
  }
};

And in addition, I needed to install the beta version of vue-loader

While the config by @blacksonic worked somewhat, there was one error I was getting::
"export 'staticRenderFns' was not found in './component.vue?vue&type=template&id=6b62fe10&'

To fix this, just replace the .loader() call with .loader(require.resolve('vue-loader-v16')). This seems to be necessary as we're waiting for v3 to finalize.
https://github.com/vuejs/vue-cli/blob/9e5b16b00140ef62fa26abd5ff938b7cd8380192/packages/%40vue/cli-service/lib/config/base.js#L135

This is not works for me at all. It compiles project, but noisy messages failed to resolve component still present.
Does somebody know, how to make it work?
I am using the same config as posted above with .loader(require.resolve('vue-loader-v16')).

@blacksonic's solution worked like a charm for me to ignore <ion-icon ...> web component elements. I did not need to modify the loader as @spaceemotion needed to a few months ago -- I'm assuming this is because I have a more updated version of Vue (v3.0.5)?
I did get some errors when initially I copied/pasted @blacksonic solution--not sure exactly what I changed but the following is working for me:
module.exports = {
  lintOnSave: 'warning',
  outputDir: '../app/assets/javascripts/vue-cli',
  // ---------------------------------------------
  // Below we are modifying the webpack config to properly ignore <ion-icon>
  //      web component elements. This is how it is done in Vue 3
  // Inspiration:
  // https://github.com/vuejs/vue-cli/issues/5610#issuecomment-648998597
  // https://cli.vuejs.org/guide/webpack.html#modifying-options-of-a-loader
  // ---------------------------------------------
  chainWebpack: config => {
    config.module
      .rule('vue')
      .use('vue-loader')
      .tap(options => {
        // modify the options...
        options.compilerOptions = {
          ...(options.compilerOptions || {}),
          isCustomElement: tag => /^ion-/.test(tag)
        }
        return options
      })
  }
}

This is basically the same code as originally posted, with some other options shown only for context. But I think a lot of people are specifically trying to ignore ion-icon or other "ion-" elements so hopefully this can save them some time

You need to write:
...
.loader( require.resolve( "vue-loader-v16" ) )
...

until @.*** will be released.
On 14.03.2021 07:42, Kamal wrote:

@blacksonic https://github.com/blacksonic's solution worked like a
charm for me to ignore |<ion-icon ...>| web component elements. I did
not need to modify the loader as @spaceemotion
https://github.com/spaceemotion needed to a few months ago -- I'm
assuming this is because I have a more updated version of Vue (v3.0.5)?
I did get some errors when initially I copied/pasted @blacksonic
https://github.com/blacksonic solution--not sure exactly what I
changed but the following is working for me:
|module.exports = { lintOnSave: 'warning', outputDir:
'../app/assets/javascripts/vue-cli', //
--------------------------------------------- // Below we are modifying
the webpack config to properly ignore  // web component
elements. This is how it is done in Vue 3 // Inspiration: //
https://github.com/vuejs/vue-cli/issues/5610#issuecomment-648998597 //
https://cli.vuejs.org/guide/webpack.html#modifying-options-of-a-loader
// --------------------------------------------- chainWebpack: config =>
{ config.module .rule('vue') .use('vue-loader') .tap(options => { //
modify the options... options.compilerOptions = {
...(options.compilerOptions || {}), isCustomElement: tag =>
/^ion-/.test(tag) } return options }) } } |
This is basically the same code as originally posted, with some other
options shown only for context. But I think a lot of people are
specifically trying to ignore |ion-icon| or other "ion-" elements so
hopefully this can save them some time
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vuejs/vue-cli/issues/5610#issuecomment-798838546,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH2MSD66K7FZRHLNDP2RELTDQ5BZANCNFSM4OFPY73Q.


Providers Form unavailable in v2.9, opens YAML Editor instead

With the currently released versions of turtles-operator v0.10.0 and capi-ui-extension v0.5.0 in Rancher v2.9.0-head, there is a problem with adding a new CAPI/Provider over Web UI.
The interactive UI Form for adding a provider (Custom or any other) is missing and the YAML Editor opens instead on attempting to add one. Additionally, the Back to Form button does nothing. Maybe worth to mention, the YAML Editor is not available under rancher v2.8-head when using the same versions.
Broken UI Form in rancher:v2.9-head:

Working UI Form in v2.8-head:

Versions:
turtles-operator v0.10.0
capi-ui-extension v0.5.0
rancher v2.9-head (ba8d1e3664c7e3504f01db3618025200ecc0ea0f)
dashboard: release-2.9 870c9d7

This is related to breaking changes between 2.8 and 2.9. New shell version fixes this problem.


Feature: Increased maximum volume label length to 128 characters for UDF images

Resolved / Related Issues

[x] Were these changes approved in an issue or discussion with the project maintainers? In order to prevent extra work, feature requests and changes to the codebase must be approved before the pull request will be reviewed. This prevents extra work for the contributors and maintainers.
Closes #12901

NB: added a new nuget dependency (DiscUtils.Udf) as winapi GetVolumeInformation only returns up to 32 chars. I won't raise a fuss if PR is refused due to this :)
Validation
How did you test these changes?

[x] Did you build the app and test your changes?
[ ] Did you check for accessibility? You can use Accessibility Insights for this.
[ ] Did you remove any strings from the en-us resource file?

[ ] Did you search the solution to see if the string is still being used?

[ ] Did you implement any design changes to an existing feature?

[ ] Was this change approved?

[x] Are there any other steps that were used to validate these changes?

Mount attached ISOs
Check UDF formatted ISO label is > 32 characters

Screenshots (optional)

udf_long_name.zip

added a new nuget dependency (DiscUtils.Udf) as winapi GetVolumeInformation only returns up to 32 chars. I won't raise a fuss if PR is refused due to this :)

I think adding this functionality is worth taking another dependency, how large is the package?

Around 350KB, I've added the minimum needed for dealing with UDF.

The full library has more functionality, e.g create and extract ISO files and VHD disks.

@gave92 is this working for you?


Update README.md

Hi @MuTsunTsai, I had to do some tinkering to get this working in webpack and it turned out to be a simple solution so hopefully this can help someone else!
Thanks for writing a great library :)

Hi, thanks for the PR and compliment! I've merged it and will put a new version on NPM later.


Connection Status and add Interval Icons

New icon package including connection status and add interval icons.
I changed the names as suggested to ConnectionStatusButton_online.png and ConnectionStatusButton_offline.png for the regular online/offline icons and then ConnectionStatusButton_connected and ConnectionStatusButton_notconnected for the connectivity icons.
The names for the add interval buttons are named "AddInterval", "AddInterval_pressed", etc..
StraboIcons_v23.zip

Added with commit f01d3ef9d520bafaa8b01002feeb53e7c6e13288
Noticed you have the following duplicates in your package. I removed them so there is no need for a new icon zip but you may want to take them out of your files. Also in the list below I think SedInterval_pressed.png is wrong (not the same style as the other files ending in _pressed.png but  SedInterval_pressed_1.png is correct.
SedInterval_pressed.png and SedInterval_pressed_1.png
SedIntervalButton.png and SedIntervalButton_1.png
SedIntervalButton_pressed.png and SedIntervalButton_pressed_1.png


Use coroutines instead of xpcall

If this promise implementation wrapped each callback in a coroutine instead of using xpcall, then wrapping APIs that yield wouldn't require spawn. It would also help guard against cases where users yield intentionally or otherwise.
One thing to note is that we probably lose the ability to track errors after a yield has occurred. The current version bans yielding entirely, a previous version allowed it by virtue of using pcall, and this version would catch errors, but only if they occur before the first yield.

You might want to take a look at my fork of the F3X Try library. The documentation is available here. I don't really like it though because it doesn't really have any specifications like Promises does, so what it should do is really just whatever I thought GigsD4X may have told me one night. However, it does have a few cool things that might give you good ideas for this library. It wraps all calls in a coroutine, and tracks the traceback along the way. If you do somehow arrive upon an error, it will "compile" the tracebacks into a single error message. It also doesn't create a new Attempt object internally, it reuses the same table object the entire time and simply changes the values accordingly.

Last I checked, xpcall doesn't allow yielding. I had to make a homebrew solution that just called pcall then called the provided function if it errored.


[WIP] osm namespace add should fail when adding osm-system NS

fixes: https://github.com/openservicemesh/osm/issues/1196
This has changes to return an error when a user tries to add a namespace which has osm control plane running in it.
Please mark with X for applicable areas.

New Functionality      [ ]
Documentation          [ ]
Install                [X]
Control Plane          [ ]
CLI Tool               [x]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests / CI System      [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution? No

todo:

[ ] update tests

@Sheshagiri, thanks for the change, would you mind adding tests prior to merging?

@Sheshagiri, thanks for the change, would you mind adding tests prior to merging?

Sure, I have a todo. I'll add those and mark this as ready for review.


How to view the version of the python library included in ironpython？

thx.

Don't know of a way to do this other than looking through commits:
IronPython 2.7.9  -> 2.7.15
IronPython 2.7.10 -> 2.7.16
IronPython 2.7.11 -> 2.7.18 (final release of the CPython standard library)


Could you please provide requirements.txt or environment.yml for environment dependencies?

I ran into endless errors while run code sh scripts/run.sh, such as easydict, tensorboardx missing, and sacred version conflict with python 3.10, etc.
Could you please provide your requirements.txt or environment.yml for environment dependencies, even pip list result.
Thanks for your help.

It maybe a little bit too late, but I figure out the dependency on python 3.7.
Save the following as requirements.txt and pip install -r requirements.txt
albumentations==1.3.1
easydict==1.13
matplotlib==3.5.3
numpy==1.21.6
opencv_python==<IP_ADDRESS>
opencv_python_headless==<IP_ADDRESS>
Pillow==10.3.0
sacred==0.8.2
scipy==1.7.3
tensorboardX==<IP_ADDRESS>
torch==1.13.0+cu117
torchvision==0.14.0+cu117


Option to change font size

Could we get an option to change the font size of the text? My eyes aren't great these days and being able to make the text bigger would be nice.

Sure! I'll add it asap ✌

Thanks!

Just pushed a commit with this feature. You can read about the config option in docs ✌

I might expand upon it later so the icons and size of the statusline increases with the font size but unless you make it huge it shouldn't be an issue.

I am not seeing how to change the font size? can I get an example


Story text selectable & Hotfix "entity in Compendium undefined"

Make story text selectable
Also contains a hotfix that checks if entityInCompendium is undefined before checking it's property.
Fixes #71

@ultrakorne can we merge that?

@DanielBoettner yep, doing it now. sorry for the delay


update_spring_version

Tech debt ticket:

Update Spring boot to latest version
Clear vulnerability
Update jib plugin docker images

CI: No security warnings found

CI: No security warnings found


Implement skeleton text for loading data

Issue Description
Loading times can lead to a less than optimal user experience when waiting for content to load. To improve user perception of loading times, we should implement a skeleton text UI pattern that provides a visual indication of content loading in place of actual data.
Apps Checklist

[ ] Job Manager
[ ] Pre-order management

Below are the current findings for possible implementations -

Through custom directives - A top-of-the-head direct approach for doing low-level DOM access in Vue. Yet we cannot do direct DOM manipulations (https://stackoverflow.com/questions/42508040/dynamic-dom-elements-add-remove-with-vue).
Through dynamic components - Dynamic components are intended to dynamically switch between elements/components (similar to routing). Hence, this approach is similar to creating a custom skeleton text component only.

Figured out a way to implement the skeleton loading part of the solution through directives. More handling on the template level will be done later.


Cow: Watch creativevisionglobal.com

Cow requests the watch of the watch_keyword creativevisionglobal\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

creativevisionglobal\.com has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


change title on README

Adding description for the the PR so that it will be easy for the reviewers

Done


package.json incorrectly defines location of Typescript types

Bug Report
Current Behavior
Installed rxjs into my TypeScript project.  Tried using rxjs but the TypeScript compiler gave me an error message saying
Could not find a declaration file for module 'rxjs'.
'D:/myWork/node_modules/rxjs/dist/cjs/index.js' implicitly has an 'any'
type.Try npm i --save-dev @types/rxjs if it exists or add a new declaration (.d.ts) file containing
declare module 'rxjs';
Expected behavior
TypeScript should be able to find the types defined inside the rxjs project.
Environment

RxJS version: 7.3.0
TypeScript v4.4.3
npm v7.18.1
node v14.15.3

Possible Solution
I had a look in rxjs's package.json file and I see
"types": "index.d.ts"
This is incorrect.   If I change this line to the following then everything starts working again.
"types": "./dist/types/index.d.ts"
I don't know why the "typesVersions" settings don't work.

It is not incorrect: https://github.com/ReactiveX/rxjs/issues/6466#issuecomment-859186944
If you see this issue on tsc > 4.2.4, please provide reproducible repo.

Closing as inactive.


Add asmdefs as LF line endings.

Description
Add asmdefs as LF line endings.
How did you test these changes prior to submitting this pull request?
What automated tests are included in this PR?
How is this documented (for example: release note, upgrade guide, feature page, in-code documentation)?

Does this mean the files should be modified for this PR?

@firtina-improbable I don't think so, the .gitattributes file only describes how files should be checked out. I.e. - auto means whatever the system you are on.
On that, should we also set *.sh to LF to stop people getting trolled by that (possibly the problem in #70). Driveby @jared-improbable ?


Change NatsSubscription to a throwing AsyncSequence

Signed-off-by: Piotr Piotrowski<EMAIL_ADDRESS>

This might be good for checking - both ways actually @piotrpio
https://github.com/nats-io/nats-architecture-and-design/pull/282

Great. Ready for review? :)


Error with raw SQL queries

I'm using django-pyodbc to make some raw SQL queries, and I've seen an error when using a LIKE statement. If I make this query with a sqlserver client (tsql, for example), I get some valid results:
SELECT * FROM [MYTABLE] WHERE [FIELD] LIKE '%27%'

But if I make the same query using django-pyodbc, I don't get any error, but the result is empty (and it shouldn't):
cursor = connections['myDB'].cursor()
sql = "SELECT * FROM [MYTABLE] WHERE [FIELD] LIKE '%27%'"
cursor.execute(sql)
rows = cursor.fetchall()
print rows

Making some tests, the bug seems to happen when the LIKE statement contains just numbers. If I make the query with something like LIKE '%7A%', the result is OK. It happens with NCHAR and NVCHAR fields.

Take a look at this StackOverflow answer to print the exact SQL being sent to the server out to the console:
http://stackoverflow.com/a/10155661/20712
Then, run Django with python manage.py runserver [...] and post the exact SQL string being sent to the server, please.

Hi Tapia,
Please re-open this ticket if it remains unresolved.  Closing.


the architecture mentioned audio process but i didnt find any code to process audio in app.py

The app.py file is set up using Gradio, which is responsible for reading videos and displaying content. The actual code for processing videos, extracting audio and frames, is located in the minigpt4/conversation/conversation.py file.


fix: vim.has doesn't exist, use vim.fn.has instead

It errors when you try to rename a file otherwise

#411 fixes this as well

Thanks for fixing this, merged #411 which was the same change


[$1000] No space between text and emoji in multiline message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to any chat
type anything(like gggg)
in next line type emojis
send the message

Expected Result:
should be some space between text and emoji
Actual Result:
No space between text and emoji
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[x] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.282-3
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/224438153-9ed98c8a-c8f6-4bec-b5d5-62cea083e12a.mp4

Expensify/Expensify Issue URL:
Issue reported by: @gadhiyamanan
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1678439509796459
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01d174e9bde5da9bfd
Upwork Job ID:<PHONE_NUMBER>578596864
Last Price Increase: 2023-03-12

Triggered auto assignment to @MitchExpensify (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

Job added to Upwork: https://www.upwork.com/jobs/~01d174e9bde5da9bfd

Current assignee @MitchExpensify is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to Contributor-plus team member for initial proposal review - @s77rt (External)

Triggered auto assignment to @robertjchen (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

Proposal
Please re-state the problem that we are trying to solve in this issue.
There is no space between the emoji and the message text in the report item.
What is the root cause of that problem?
The root cause of this problem is the missing line height of the message item.
What changes do you think we should make in order to solve the problem?

We can add appropriate line height here.
What alternative solutions did you explore? (Optional)
None

@MitchExpensify This is a dupe https://github.com/Expensify/App/issues/14445.

Not overdue. Probably a dupe. @MitchExpensify https://github.com/Expensify/App/issues/15864#issuecomment-1465180632

Not overdue. @MitchExpensify ^

Waiting for @MitchExpensify

Wow, sorry for the delay here! Not sure how I missed it. This is indeed a dupe, thanks for the catch @s77rt


feat: Fixes #91 add README.md

Adding this PR to resolve #91

In addition to small fixes in readme.go file, please fix:

commit messages to conform with conventional commit format

Added suggested changes and merged


The ose-on-aws.py --rhsm-pool parameter does not work with Subscription Management Pool ID's

The rhsm-pool parameter only seems to work when using Subscription Name. When passed the Subscription Management Pool ID (A fully numeric value) it does not seem to work properly and fails to attach the given pool.
Here's a snipit from ose-on-aws.py --help:

--rhsm-pool TEXT                Red Hat Subscription Management Pool ID or Subscription Name

Excellent find. Will resolve
On Jun 1, 2017 7:51 PM, "Nick Schuetz"<EMAIL_ADDRESS>wrote:

The rhsm-pool parameter only seems to work when using Subscription Name.
When passed the Subscription Management Pool ID (A fully numeric value) it
does not seem to work properly and fails to attach the given pool.
Here's a snipit from ose-on-aws.py --help:
--rhsm-pool TEXT Red Hat Subscription Management Pool ID or Subscription
Name
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/openshift/openshift-ansible-contrib/issues/425, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADoslFmbT-rBvuN6yx9tAnAm2SrKIDqxks5r_05zgaJpZM4NtrUb
.

This also affects GCP and probably others. Related PR #422 , but I don't think that's a correct fix.


[Discussion] Communication improvement

Communication improvement
Hello folks,
First, I think it would be a good idea to have a "discussion" label for issues which deals with chats about roadmaps, some new ideas, etc...
Then, let's face it, many contribution are coded outside working schedules. Is there a way to reach asynchronously the cummunity (repo maintainers, but also all contributors?). AXA's MS Teams does not seem appropriate here (IMHO).

Good idea, I added a Type: Discussion label.
To communicate asynchronously the best way is to use the Github issues as many open source project.

I agree, but sometimes you need a bit more (something closer to "instant messenging" - slack, teams, ...)

For the moment, we are only able to discuss with issues. If team grow & find more time, maybe we can add an instant messenger.

I'm not sure that adding a new way to communicate will improve it, on the contrary some channel will probably never receive any answer.
Furthermore, if everything is here we can have an history of the discussion and it's public.

@youf-olivier & @samuel-gomez-axa , your opinion ?

The instant messenging would also be public and archived, @xballoy :)


Variables binding: disable for a particular script/query

Sometimes it is needed to disable variables/parameters binding just for one query/script.
It is inconvenient to do this thru preferences.
Maybe option in the context menu or option in the variables binding dialog will solve the issue.


[TypeError: Cannot read property 'id' of undefined] from req.session.id

I am getting the error above  and a 500 server errror when I visit my route for my localhost:1337/user/:id/newsfeed.  Can you help me with this error? It's driving me to madness..
User.js
module.exports = {

schema: true,

//User attributes
attributes: {
    facebookId: {
        type: 'string',
        unique: true,
        notNull: true,
        required: true
    },
    friends : {
         collection: 'user',
          via: 'id'

    },
  }

routes.js
 'get /user/:id/newsfeed': {
    controller: 'UserController',
     action: 'newsfeed'
  }

UserController.js
   module.exports = {
    newsfeed: function (req, res) {
     var userId = req.session.id;
    sails.log("Searching for user's friends: " + userId);

   User.find({ userId: userId })
   .populate('friends')
  .populate('posts')
  .exec(function (err, found) {
    if (err) return res.status(err).json(400);
    res.status(found).json(found);
  });

}
};
Any help would be greatly appreciated!  Also using mongo database, redis and deploying to heroku.

CORRECTION ^^:  I meant to put id not user in user model as shown below.
friends : {
collection: 'user',
via: 'id'
},

Actually I think I got this working by changing it around some.  If it looks like just a syntax error please close it.  But can you guys put out some more documentation!!!!! Or where is that book McNeil's working on???

I don't see the error just by eyeballing, but i just came across an area I thought the docs were light. I ended up sending a PR on https://github.com/balderdashy/sails-docs. Pretty painless process.

Thanks @foobar8675!

@OwaysisApp going to go ahead and close this- but as an aside in case this helps, my hunch is that the connect session adapter can't access your session store.  Be sure and check that you're using the right version of connect-redis/connect-mongo, that the session is configured correctly in config/sessions.js and any other relevant config files / env vars, and that the session hook is enabled.  If you come across stuff that would be useful for us, it would be awesome if you could send a PR to sails-docs.  Thanks!

Don't know if this is the right thread to post, but when attempting to do "req.session.id = docs_id" today, it didn't updated the req.session, but when I changed "id" to "userId", i.e: "req.session.userId = docs_id", it worked!! Don't know why, though..


Changes to the metabolic generator

Instead of pulling directly from the food bar could you pull from the saturation first, it makes eating impossible if you have the saturation potion effect from something like the environmental controller from rftools after your food is exhausted you cant eat because of a full saturation bar.

As of 0.2.6 the interaction with Saturation is still odd.  Saturation should keep your food bar filled, but the Metabolic Generator decreases it in a way Minecraft doesn't seem to notice.  You don't take starvation damage while Saturation is active, but taking damage from any other source will trigger Saturation to refill your food bar, so you can avoid loss of food in these circumstances by poisoning yourself.  O.o

I've been tricking it by stepping on wooden spikes from extra utilities


Show stacktrace instead of 1xxx error page in wrangler dev

If a script throws an uncaught exception, an ambiguous 1xxx HTML page is rendered. This happens in wrangler dev too. Unless.. in dev mode, we wrap the script in a try/catch handler, and print out the stacktrace. Here is an example:
import worker from "./path/to/entrypoint"

export default {
  async fetch(request, env, ctx) {
    try {
      return await worker.fetch(request, env, ctx)
    } catch (err) {
      return new Response(err.stack, { status: 500 })
    }
  }
}

Miniflare uses youch to render the stacktrace, which could also be used to create a pretty output.

This would only work for module style workers ofc.

This is fixed by the move to local mode by default in Wrangler v3 (Miniflare's pretty error pages are shown). Worth noting that it also works for service workers 🎉 thanks to @cameron-robey's middleware system


Auto launch wish

What was the feature/problem?
We have changed the desired wisher workflow to automatically launch the rocket after saving the wish
How does this PR address the above feature/problem?
Removed the Fulfill my wish button
Triggers rocket launch after saving wish
Check lists (check x in [ ] of list items)

[x] Test passed
[x] Coding style (indentation, etc)

Additional Comments (if any)

Codecov Report

Merging #140 into master will decrease coverage by 1.61%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #140      +/-   ##
==========================================
- Coverage   94.67%   93.06%   -1.62%
==========================================
  Files          29       21       -8
  Lines         451      274     -177
  Branches       51       27      -24
==========================================
- Hits          427      255     -172
+ Misses         21       17       -4
+ Partials        3        2       -1

Flag
Coverage Δ

#api
?

#ui
93.06% <100%> (+0.02%)
:arrow_up:

Impacted Files
Coverage Δ

ui/src/childinfo/ChildInfo.js
94% <100%> (+0.12%)
:arrow_up:

api/src/app.js

api/src/routes/wish.js

api/src/db/bootstrap-mongoose.js

api/src/db/Account.js

api/src/util/util.js

api/src/db/Wish.js

api/src/routes/index.js

api/src/routes/auth.js

Continue to review full report at Codecov.

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


nodeSelector for rabbitMQ

Is this a request for help?:

Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST

Version of Helm and Kubernetes:
any
Which chart:
rabbitmq
What happened:
Add nodeSelector to stable\RabbitMQ, please.
Make it as resources, like this:
resources:
{{ toYaml .Values.resources | indent 10 }}
nodeSelector:
{{ toYaml .Values.nodeSelector | indent 9 }}
What you expected to happen:
Easy way to specify needed pools and nodes
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

@m1t1l Thank you for the feature request. The charts maintainers have been cc'd (below). Pull requests are welcome to add features.
cc: @prydonius @tompizmor @sameersbn


fix(content-group): adding h-tags to headings

Related Ticket(s)
Jira

The H3 and H4 headings are not properly configured in the AEM template. They should be tagged as the H1 and H2 (from the same AEM template). Otherwise, they won't have the same SEO relevancy because it's not recognized as H2 & H3.

Description
Adding the respective H tags to content-group-heading and content-item-heading components.

V2 version of this PR
https://github.com/carbon-design-system/carbon-for-ibm-dotcom/pull/11739

It seems that in addition to adding the h3/h4 elements to the shadowroot, we'll need to remove the role and aria-level properties in use here. As it is now, the headings appear twice in screen readers.

There are some subtle but noticable differences in the typography with the new heading elements. Can we get some designer input on what this is supposed to be rendering as?

Hey @marcelojcs , I'm seeing the heading for content item rendering differently than it should. It should use the fixed$heading-02 token for the heading in the v1 package.
This PR:

Spec samples:

Hey @marcelojcs and @andy-blum ,
content item looks fixed. I noticed that for content group, the heading does not appear to be updating its size as $expressive-heading-04 across breakpoints. It should be 28px up to @lg and then update to 32px for @lg – @max.
Right now, I only see the heading render as 28px across breakpoints.

@RichKummer
Addressed in my latest commit.

Thanks @marcelojcs ! Both content item and group look fixed. I did see that for some reason the content item horizontal's header updated to a different type token than it should.
It should appear with the heading as $expressive-heading-03

@RichKummer updated font rules to inherit their font letter-spacing and line-height rules from the parent components.


[TACHYON-592] Fix Mac OS X HFS+ available provisioning size for ramdisk

https://tachyon.atlassian.net/browse/TACHYON-592

@qnu Thanks for the patch. With this change, is the ram disk size guaranteed to be greater than or equal to the configured space (for example, if I ask for 4 GB, will I always get >= 4GB)?

@calvinjia Yes, as its inline comments noted.

+1 LGTM

+1 LGTM


Remove comment causing docgen issue

Removes comment in order to fix the docgen issue described in elastic/logstash#6692.
@ph This topic does have a description. I think the docgen issue is being caused by the comment, so I've removed the comment. Let me know if this looks Ok, and I'll change the checklist in 6692.

LGTM


Small refactoring

Thank you for CombineCocoa @freak4pc 😊
In this PR, I am just removing some things which appears to be unused and unnecessary.

Thank you @jdisho 🙏❤


Add "description" key to opendistro-security tenant create call

Add description json body key to opendistro-security tenant create call used in the sync:opendistro-security command

Checklist

[x] Affected Issues have been mentioned in the Closing issues section
[ ] Documentation has been written/updated
[ ] PR title is ready for changelog and subsystem label(s) applied

Opendistro-security's API endpoint for creating tenants has been updated (I couldn't find the change, maybe someone else can?) to require a description so this PR updates our API call to include a generic description.

Closing issues
closes #2577

superseeded by https://github.com/uselagoon/lagoon/pull/2772
@tobybellwood can we make sure we give @KorvinSzanto credits on the release notes as he found it first? Thanks!

Yup! Sorry I forgot about this PR!


Fix: If metadata name element does not exist, insert a new one as a child

We were assuming that the akn:FRBRname node would exist and could be edited,
but in some cases this node does not exist if the parser was unable to find a
case name in the judgment.
Check to see if a akn:FRBRname node exists in the document, and if it does
replace it, otherwise create a new one.

We did, but in that one we were returning a node to the editor, it was being edited and saved on the editor side. This was causing the namespaces to be wiped out. Everything is now being amended in ML via XQueries, but when I released 4.5.1 I forgot that sometimes the elements don't exist 🤦
We can probably strip out the XMLTools functions which return elements, eventually.


Added diagrams for flows.

It took me a little while to get my head back into this again, so I thought it would help if we had some diagrams describing the flows we've implemented in code.
I've added three here, and think it would be good to have a couple more for OAuth1 where I've indicated with titles.
Please could you review what I've done here, and see if you could create the extra two for OAuth1 (think you have a better understanding of the flow than me)?
I've using this tool to generate the diagrams: https://excalidraw.com/
As you can see I've saved both the exported image and the .excalidraw source file into the repo, so we can modify the diagrams.  You can also open the OAuth2 equivalent diagram, and modify it to save the OAuth1 ones.

Great, thanks very much.


Using the "latest" babel preset

This configuration:
{
	babelrc: false,
	presets: [
		[
			"latest",
			{
				"modules": false
			}
		]
	],
	exclude: 'node_modules/**',
	plugins: [
		"external-helpers"
	]
})

fails with: It looks like your Babel configuration specifies a module transformer. Please disable it. See https://github.com/rollup/rollup-plugin-babel#configuring-babel for more information
If I replace latest with es2015 the error goes away. Why is that?

I got further by replacing "modules": false with:
"es2015": {
	"modules": false
}

I no longer get an error from rollup-plugin-babel. Unfortunately, babel isn't transforming the files as I expected. My source-code contains Object.entries() which is supposed to get picked up by the es2017 but it does not in this case. Any ideas?

Not a Babel user so I could have this wrong, but I was under the impression that the es2017 preset didn't do anything to Object.entries(), because it's an environment feature rather than a language feature — in other words you need a polyfill, either babel-polyfill or (recommended) individual polyfills for the features you need, e.g. es-shims/object.entries.

Good catch. This worked for me: http://stackoverflow.com/a/35382020/14731
Thanks for your help.


How to use this HighlightFields property that is read only

Library name and version
Azure.Search.Documents 11.5.1
Query/Question
After checking this https://github.com/Azure/azure-sdk-for-net/issues/41321 i see that highlight is not working any more like is explained there.
HighlightFields = new[] { "", "" } is not working but HighlightFields = { "rating desc", "test" } is.
Better documentation on this should be appreciated
Environment
No response

Thank you for your feedback.  Tagging and routing to the team member best able to assist.


Cannot decode domain in uppercase

Library doesn't parse encoded domain in uppercase like XN--D1ABBGF6AIIY.XN--P1AI
However domains in uppercase form are mentioned in many places including IANA domains list http://data.iana.org/TLD/tlds-alpha-by-domain.txt
I think uppercased domains should be treated as valid as well

I have investigated php native idn_to_utf8 function - it works with uppercase domains.
So I've created pull request #17 with necessary fix for the handling of uppercase encoded domains

Fixed by #17.


Fix attrdict issues in python 3.10

This should fix the slew of CI errors related to attrdict importing an old path for collections: https://github.com/wallento/wavedrompy/issues/32#issuecomment-1306701776
Longer term fix is to not use this library and probably just simplify the logic to dicts/json throughout the script, but I don't think it's worth refactoring the script right now.
@mc-nv this will need to be picked into the release/mchornyi-u22.04 branch

@rmccorm4  can you target it to mchornyi-u22.04

Done @mc-nv 👍


Make accessible over Tor without requiring CAPTCHA solving

Users who try to access your website over Tor for anonymity / privacy reasons get presented with a really annoying CAPTCHA which is sometimes unsolvable or flat out doesn't render. The CAPTCHA being served looks like the standard one served by CloudFlare.
Please consider changing your settings in CloudFlare to not show this CAPTCHA at all. I can't imagine Nodejs.org being a high target for botnets or ddos attacks!

I'm no Tor expert, how can I reproduce this issue? Trying TorBrowser now and havent seen a CAPTCHA anywhere on nodejs.org yet..

@phillipj it does not happen 100% of the time for me. My hunch is some Tor exit nodes seem to trigger CAPTCHA's (perhaps due to IP reputations or such) others do not. Here is what I see through one of my Tor circuits

I believe CloudFlare has a sliding scale that determines when to show CAPTCHAs. I've found the only way to not make this show up for Tor is to have it at the lowest! It would be much appreciated by Tor users :-)

@rvagg could you have a look at the CloudFare firewall settings?
https://support.cloudflare.com/hc/en-us/articles/200170096-How-do-I-turn-the-CloudFlare-captcha-challenge-page-off-
Some background on the captcha protection: https://support.cloudflare.com/hc/en-us/articles/203306930-Does-CloudFlare-block-Tor-

fair 'nuff, we're not doing ecommerce or anything, turned off(ish)

Awesome. Thanks @rvagg @phillipj :+1: :smile:


Simplify code-gen tooling use-case

I am working on a stub generator for GRPC and would like to use ktlint to just do a simple format of the code.
Google java format has a simple 3 liner for usage in code gen tooling.
I'm having to read through the code to figure out how to do the same.This is where I am at with trying to figure out what I need to plug into the third param to get the formatting to occur ;)
     val content = applyTemplate("common/grpc/gen/protoc-gen-grpc-kotlin/templates/KtStub.mustache", context).let {
            KtLint.format(
                it,
                listOf(StandardRuleSetProvider().get()),
                { _, _ ->}
            )
        }

A utility method for vanilla code formatting or an example in the readme would be very helpful.

Will be done in #340. 🙇


android can not link the library

After following the android linking guide, can not link the library
React Native 0.33
error:
react-native-permissions:compileReleaseJavaWithJavac FAILED

Same issue for me. Also on React Native 0.33

Having same issue with:

react-native: 0.34.0
react-native-permissions: 0.2.5

Same with me

I've had to put my react-native apps on hold for a while to work on a new project. Because of this, I haven't been keeping up to date with the latest RN and iOS changes. I'll be picking this back up in January '17, but in the meantime, I would welcome pull requests if anyone has figured it out.
Sorry to leave you guys hanging... :/

anyone can update it?

Adding:
import com.joshblour.reactnativepermissions.ReactNativePermissionsPackage;
to MainApplication.java worked for me.

@Michaelprothero  It didn't work for me.

@xwarts @all - are you still experiencing this issue in the latest RN (0.40.0 ATM)?

@xwartz - closing for now, if you're still experiencing this issue, please reopen


Write a program to reverse an array or string in  c++

put the program with the name reverse_string.cpp

Can you assign me this issue?

bro just send pr no need to get assign and pls star this repo for more such questions and follow me.
Also check the rules in  readme file of this repo bro


Generator param for 8192-bit Group is incorrect

It appears that the generator param for 8192 bits is incorrect here:
https://github.com/alax/jsrp/blob/master/src/parameters.coffee#L128
The spec calls for this value to be 19
https://tools.ietf.org/html/rfc5054#appendix-A
Thanks

Thanks for the report! If you look take a look here:
https://github.com/alax/jsrp/blob/master/src/parameters.coffee#L169
You'll see that the generator is specified in hexadecimal in my code. The spec calls for the value to be 19 in decimal, which is the value 13 in hexadecimal. Thanks!

Indeed!  Thanks for the quick clarification.


demand() does not play well with commands

Usage: tool do-stuff <arg>

If I have a command tool do-stuff <arg> that demands at least one argument (arg), I'll have to use demand(2). The default error message will be weird in this case:
Not enough non-option arguments: got 1, need at least 2

Of course you can override the message with your own, but I think I'd rather not have a message at all in this case, because the help will be self-explanatory in that it's expecting non-optional arguments (<arg>).
Using demand() with empty string as msg will not work, it's the same as not passing it at all. So maybe we could have a way to use demand() without a message, as that at alone will print the help which is an message in itself.
What do you think?
Cheers.

To clarify, even allowing an empty string would in my opinion not be sufficient, because it prints an unnecessary empty line. Unless of course empty string meant no line at all.

What about something like this:
https://github.com/raine/yargs/commit/f57430ce02491ec75c26a25cc59b92daeaa533d7
Fail with help without showing a specific error if msg is explicitly set as null?
.demand(1, null)

@raine published your changes in<EMAIL_ADDRESS>with one slight modification '' will also result in no output.

Makes sense. Thanks.
Sent from my iPhone
--
Raine

On 12.3.2015, at 7.58, Benjamin E. Coe<EMAIL_ADDRESS>wrote:
@raine published your changes in<EMAIL_ADDRESS>with one slight modification '' will also result in no output.
—
Reply to this email directly or view it on GitHub.


Experiments and results on Fourier Neural Operator

Hello,
Thank you for the excellent paper.
I am very interested in the experimental results of applying some of the techniques to the FNO. However, I faild to find the corresponding code in this repository.Maybe I missed it or is the code not yet released?

Thank you for you reply!


Atrophy effect persists if deactivated too quickly

Activate atrophy and hit "take all" or just exit and it'll stay up on the other clients

Couldn't recreate


Re-Enable DB Integrity Check (?)

#1192
Can we do this in the background in a separate thread?

Hmm, what if we just used PRAGMA schema.quick_check; instead? https://www.sqlite.org/pragma.html#pragma_quick_check
And maybe a full integrity check after bootstrap.
I don't know if we need a separate command, since the user can just do the integrity check with the sqlite3 REPL if they want.

FWIW there is already command check-db which do an integrity check.


Chapter 6 - command to register meme errors out

Describe the bug
The command mentioned in Chapter 6 to register a meme, fails with this error:
{"ExecutionError":"Exceeded the prepaid gas."}

Example failed transaction.
To Reproduce
Run this command with your testnet account:
near call museum.testnet add_meme \
'{"meme" : "bob", "title" : "god", "data" : "https://9gag.com/gag/ad8K0vj", "category" : 4}' \
--accountId YOUR_ACCOUNT_NAME.testnet --amount 3

Expected behavior
Meme creation should succeed, like this transaction.
Additional context
The command should be corrected to add gas as clarified by Benji on Discord. Working command is:
near call museum.testnet add_meme \
'{"meme" : "bobarana", "title" : "bobarana", "data" : "https://9gag.com/gag/ad8K0vj", "category" : 4}' \
--accountId maharana.testnet --amount 3 --gas=75000000000000

Thanks for reporting this, which relates to https://github.com/NEAR-Edu/near.academy/pull/10
I wonder how this wasn't already fixed.
We'll look into it. Thanks.

I see that the main branch https://github.com/NEAR-Edu/near.academy/blob/main/src/frontend/src/pages/Courses/near101/Chapters/Chapter-6/course.md does already have gas mentioned in https://github.com/NEAR-Edu/near.academy/commit/46b304dd540f77d49cc70cb21517e682ed6c30b3
So my guess is that the problem is that we're trying to migrate from one server to another, and right now the https://near.academy/ domain is pointing to the original server, whose code is presumably out of date.
We'll hopefully be switching over to the new server in the next day or so. cc @oceanByte

I just deployed the newest main branch. Can you see if this problem still persists @ryancwalsh ?

@oceanByte Thanks, I was just checking here on this issue, too. https://near.academy/near101/chapter-6 looks good to me now, so I'm closing this issue. Thanks.

Great, thanks!


Migrate to Karma for testing

Translate Jest assertions and spies to Chai/Sinon.
Use inject-loader for mocking require()'d dependencies. I tried both karma-commonjs-plus and mockery and couldn't get either of them to work after much debugging and fiddling around. inject-loader's API is quite unwieldy, but it's the only one that worked.
Fixes up the flow type annotation syntax in two modules; the trailing commas were causing an error to be thrown during transformation, not sure why.
Remove all references to Jest
Add Node 0.12 back to the Travis config
I made a point to keep all the babel dependency versions the same, so I'm not sure why the dist files changed slightly.

fixes #225

Wow nicely done! Please revert the dist files, we only generate them when
tagging releases.
On Thu, Jul 2, 2015 at 5:58 PM Brian Beck<EMAIL_ADDRESS>wrote:

Translate Jest assertions and spies to Chai/Sinon.
Use inject-loader for mocking require()'d dependencies. I tried both
karma-commonjs-plus and mockery and couldn't get either of them to
work after much debugging and fiddling around. inject-loader's API is
quite unwieldy, but it's the only one that worked.
Fixes up the flow type annotation syntax in two modules; the
trailing commas were causing an error to be thrown during transformation,
not sure why.
Remove all references to Jest
Add Node 0.12 back to the Travis config
I made a point to keep all the babel dependency versions the same,
so I'm not sure why the dist files changed slightly.

fixes #225 https://github.com/FormidableLabs/radium/issues/225
You can view, comment on, or merge this pull request online at:
https://github.com/FormidableLabs/radium/pull/240
Commit Summary

Migrate to Karma for testing

File Changes

M .eslintrc
https://github.com/FormidableLabs/radium/pull/240/files#diff-0 (2)
M .travis.yml
https://github.com/FormidableLabs/radium/pull/240/files#diff-1 (5)
M dist/radium.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-2 (32)
M dist/radium.min.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-3 (7)
D jest/coverage-config.json
https://github.com/FormidableLabs/radium/pull/240/files#diff-4 (22)
D jest/preprocessor.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-5 (15)
A karma.conf.coverage.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-6 (12)
A karma.conf.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-7 (81)
M modules/tests/enhancer-test.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-8 (45)
M modules/tests/get-state-test.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-9 (9)
M modules/tests/keyframes-test.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-10 (88)
M modules/tests/prefixer-test.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-11
(162)
M modules/tests/resolve-styles-test.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-12
(198)
M modules/get-state.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-13 (2)
M modules/keyframes.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-14 (2)
M package.json
https://github.com/FormidableLabs/radium/pull/240/files#diff-15 (35)
M webpack.config.js
https://github.com/FormidableLabs/radium/pull/240/files#diff-16 (5)

Patch Links:

https://github.com/FormidableLabs/radium/pull/240.patch
https://github.com/FormidableLabs/radium/pull/240.diff

—
Reply to this email directly or view it on GitHub
https://github.com/FormidableLabs/radium/pull/240.

Appveyor's failing (https://ci.appveyor.com/project/ryan-roemer/radium/build/1.0.118) and this seems familiar. Probably related, Karma has historically been wonky with installing internal deps on practically all CI systems.
We can try kicking Appveyor, but in addition we can consider a few extra hacks I have here for a Karma CI build https://github.com/FormidableLabs/full-stack-testing/blob/master/appveyor.yml

OK. I've kicked Appveyor. Let's watch build https://ci.appveyor.com/project/ryan-roemer/radium/build/1.0.119

@exogen -- Great work! And nice to see v0.12 enabled on both Travis and AppVeyor.
I'll leave you to @ianobermiller and @alexlande for the rest of the substantive approval here...

Thanks for the assertion tips, @ryan-roemer – I'll open a separate issue to track those once this PR is merged.

Added "iojs" to the Travis config, which will pick up the latest stable release. For Appveyor, the docs say this will pick up io.js:   - nodejs_version: "1.0" which seems a bit sketch to me (just the version number differentiating the runtime). Should we add it there too anyway?

I don't see why not. Can always change it back if there are issues.
On Tue, Jul 7, 2015 at 6:32 PM Brian Beck<EMAIL_ADDRESS>wrote:

Added "iojs" to the Travis config, which will pick up the latest stable
release. For Appveyor, the docs say this will pick up io.js: -
nodejs_version: "1.0" which seems a bit sketch to me (just the version
number differentiating the runtime). Should we add it there too anyway?
—
Reply to this email directly or view it on GitHub
https://github.com/FormidableLabs/radium/pull/240#issuecomment-119276979
.

Awesome work @exogen, thank you!


Sample app consume memory over 600MB

Plugin Version or Commit ID
v0.10.1
Unity Version
2021.3.4f
Your Host OS
MacOS 12.3
Target Platform
iOS
Target Device
iPhone 12
[Windows Only] Visual Studio C++ and Windows SDK Version
No response
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
No response
[iOS Only] XCode Version
13.4.1
Build Command
Download plugin from release
Bug Description
I built a sample app and it consumed memory of more than 600 MB. I want to reduce memory usage because my app often crashes due to memory limits.
I built <1> including StartScene and Holistic Scene, and built <2> including only StartScene.
And ScreenShots are the profile result.

Can I optimize those texture2Ds that mediapipe use?
What's going on in "Untracked Memory"?

Could you help me to optimize memory?
Steps to Reproduce the Bug

build sample app for ios
run and profile

Log

Screenshot/Video
<1> StartScene + Holistic Scene

<2> only StartScene

Additional Context
No response

Reduce webcamtexture resolution on the webcam component in the scene?

@ROBYER1 Sorry for the late reply. I'll check it soon. Do you have an idea what is going on "Untracked Memeory"?

@ROBYER1 Sorry for the late reply. I'll check it soon. Do you have an idea what is going on "Untracked Memeory"?

I don't but see if the webcamtexture resolution is the main cause first

I think there is possibility to lower the pooling parameter (default is 10) in TextureFramePool.
Btw - don't you think there is a memory leak connected with webcam texture? Those textures seems to not be disposed after changing scenes.


Add this tuple elimination optimisation

Currently when doing:
let success, value = dictionary.TryGetValue(key)
This allocates a Tuple needlessly. Because of this, much performance-critical code including in F#'s own libraries use the out parameter explicitely. Someone proposed a patch to the compiler to optimize this away:
https://gist.github.com/zeux/1638442
I tried it on my machine and it seems to work well, however I can't say I understand enough what it's doing to tell whether it's safe or not. Thus I'm creating this issue so someone with more experience with the F# compiler code can look at it and integrate it if possible.

This fixed by #335.


Possible memory leak leading to unexpected restarts at regular intervals

We have started hitting an issue about a week ago where Kapacitor memory usage starts increasing constantly and when host memory utilization reaches near 100% Kapacitor restarts without any specific error message (nothing in the syslog either). This repeats about every 6 hours.
Initially I suspected that this is due to the amount of incoming metrics exceeding the amount that Kapacitor can ingest. I've included below the pprof showing the top 2 memory consumers which seem to indicate this.
However, I tried to decrease the amount of points being sent to the Kapacitor instance to just the measurements we are interested about. This dropped the data rate from 150k points per second to 30k but we are still seeing these crashes.
I'm sending the metrics directly via a HTTP stream and not using InfluxDB subscriptions. I tried to also tweak the HTTP batching but this did not seem to have much impact.
 The first entries in that file aren't necessarily what is consuming your memory. You need to load the profile into something like go tool pprof.
See also #1749

The top consumers are similar to the linked issue:
(pprof) top10
Showing nodes accounting for 4.05GB, 87.21% of 4.65GB total
Dropped 186 nodes (cum <= 0.02GB)
Showing top 10 nodes out of 108
      flat  flat%   sum%        cum   cum%
    1.13GB 24.36% 24.36%     1.13GB 24.41%  github.com/influxdata/kapacitor/vendor/github.com/influxdata/influxdb/models.(*point).unmarshalBinary
    1.08GB 23.12% 47.49%     1.08GB 23.12%  github.com/influxdata/kapacitor/tick/stateful.NewFunctions
       1GB 21.58% 69.06%        1GB 21.58%  github.com/influxdata/kapacitor/vendor/github.com/influxdata/influxdb/models.Tags.Map
    0.24GB  5.12% 74.18%     0.24GB  5.12%  github.com/influxdata/kapacitor/models.Fields.Copy
    0.20GB  4.30% 78.48%     0.20GB  4.30%  github.com/influxdata/kapacitor/edge.(*pointMessage).ShallowCopy
    0.14GB  2.93% 81.41%     0.14GB  2.93%  github.com/influxdata/kapacitor/edge.(*pointMessage).GroupInfo
    0.10GB  2.09% 83.50%     0.19GB  3.99%  github.com/influxdata/kapacitor/edge.(*statsEdge).incCollected
    0.08GB  1.69% 85.19%     0.08GB  1.69%  github.com/influxdata/kapacitor/models.ToGroupID
    0.05GB  1.07% 86.25%     0.05GB  1.07%  github.com/influxdata/kapacitor/alert.newHandler
    0.04GB  0.95% 87.21%     1.28GB 27.45%  github.com/influxdata/kapacitor/edge.(*groupedConsumer).getOrCreateGroup
(pprof) list unmarshalBinary
Total: 4.65GB
ROUTINE ======================== github.com/influxdata/kapacitor/vendor/github.com/influxdata/influxdb/models.(*point).unmarshalBinary in /root/go/src/github.com/influxdata/kapacitor/vendor/github.com/influxdata/influxdb/models/points.go
    1.13GB     1.13GB (flat, cum) 24.41% of Total
         .          .   1483:		p.time.Round(d).UnixNano())
         .          .   1484:}
         .          .   1485:
         .          .   1486:func (p *point) unmarshalBinary() Fields {
         .          .   1487:	iter := p.FieldIterator()
  506.25MB   506.25MB   1488:	fields := make(Fields, 8)
         .          .   1489:	for iter.Next() {
         .          .   1490:		if len(iter.FieldKey()) == 0 {
         .          .   1491:			continue
         .          .   1492:		}
         .          .   1493:		switch iter.Type() {
         .          .   1494:		case Float:
  643.28MB   643.28MB   1495:			fields[string(iter.FieldKey())] = iter.FloatValue()
         .          .   1496:		case Integer:
    9.01MB     9.01MB   1497:			fields[string(iter.FieldKey())] = iter.IntegerValue()
         .          .   1498:		case String:
    1.50MB     3.50MB   1499:			fields[string(iter.FieldKey())] = iter.StringValue()
         .          .   1500:		case Boolean:
         .          .   1501:			fields[string(iter.FieldKey())] = iter.BooleanValue()
         .          .   1502:		}
         .          .   1503:	}
         .          .   1504:	return fields

@oplehto Is the top10 profile you share in alloc_space or inuse_space?
Note that if its alloc_space and unmarshalBinary is the top then that just means that writing points to Kapacitor dominates its memory usage. Which makes sense.
However if its alloc_space then stateful.NewFunctions being high implies that you are defining/reloading tasks very frequently as that code is purely about parsing and interpreting TICKscript, which seems too high personally.
If you can clarify which alloc_space vs inuse_space that would help a lot. In addition if you can share the entire heap profile that would be even better.

My suspicion is that the data in these extra lines accumulate in the join buffer causing the leak.
Adding a |where(lambda: isPresent("uptime")) to filter out the extra lines from uptime_stream seems to make the memory consumption a lot healthier.

This makes sense to me. If the join is constantly receiving data that it will not be able to join with another point, it will be buffering that data.
I'll close this issue now. If the problem resurfaces we can investigate further.


Two config files

Since updating there are now two config files.
I assume pjp.conf is the currently used file and I can safely delete config.conf
Portals 0.13.7

Yeah the new config manager i wrote changes the config naming standard. You can safely delete it the old or rename it to pjp.conf

I just opened them both, changed the settings in the new one to match the old, then deleted the old.  Problem solved!


Cannot complete manual steps at end.  Error: AADSTS650056

At the end of the Configure script it asks you to navigate to the todoList_web_daemon_v1 API Permissions and to click on "Grant admin consent for (your tenant)."
I try that but get the following error:

Request Id: 26f0629a-b0f4-496e-9d64-79d1fbf25300
Correlation Id: 09bf39ee-14e0-452a-8c4d-2459f1fba730
Timestamp: 2019-06-06T14:48:29Z
Message: AADSTS650056: Misconfigured application. This could be due to one of the following: The client has not listed any permissions for 'AAD Graph' in the requested permissions in the client's application registration. Or, The admin has not consented in the tenant. Or, Check the application identifier in the request to ensure it matches the configured client application identifier. Please contact your admin to fix the configuration or consent on behalf of the tenant. Client app ID:

@AlphaCreative : do you see the app roles in the manifest?

The manifest for "todoListService_web_daemon_v1" shows "access_as_application" in it's app roles array but "todoList_web_daemon_v1" has an empty array for app roles.

OK, I have more information.  I originally was logged in with an account that was setup as a "Limited Administrator".  I changed it to a "Global Administrator" and it worked.  I have another issue though that I'm going to enter where a "Global Administrator" that is of account type "Guest" cannot run the scripts in the sample at all.

You are right @AlphaCreative that for this sample (all the samples involving daemon apps / client credentials), you need to be a global tenant admin.
Do you think we need to be more explicit? we have written it in https://github.com/Azure-Samples/active-directory-dotnet-daemon#how-to-run-this-sample ?

I think the updated readme is good.  As for the other issue I mentioned.  It was a Microsoft Account and as the readme says, that won't work.  I think this issue can be closed at this point.


Convert project to gradle

Hi,
you should give a try for gradle instead of maven.
http://gradle.org/
gradle is more powerfull than maven in many ways.

Yes, as elasticsearch moved from maven to gradle in version 2.2, it will switch to gradle in the next elasticsearch upgrade.

Cool

+1 for Gradle. May it will be include in this issue: https://github.com/strapdata/elassandra/issues/88

Done with Elassandra <IP_ADDRESS>-beta1 (Based on Elasticsearch 5.5.0 + Cassandra 3.11.0)


Can't get it to work.

When I try using the command:
image-sdf img.png >img-sdf.sdf
on the example png (the one that is just an X) I don't get any errors but the output is not readable as a valid PNG file.

Same

You are using it wrong. Check examples in README.md.
You need to specify output with -o flag:
$ image-sdf img.png -o img-sdf.sdf


how to balance the training data

Does the comments "Due to the class imbalance in WebVision, we duplicated the file items in train.txt such that different classes have equal number of training samples." in the Readme mean that every class is up-sampled to the same number as the maximum number of classes, and the number of items of each class in the trianlist.txt is the same ?

Yes, we duplicated the items in trainlist.txt so that each class has the same number of items as the largest class has.

Check utils/upsample.py for an example.


feat(huff_lexer): lexer using the logos crate

Lexer written using the logos with tweaks/benefits:

A lot of complexity is abstracted thanks to logos.
All of tokens are now lexed properly incl. opcodes, hex/string literals etc. Able to lex entire erc20.huff without errors.
Opcodes/evm types based on context e.g. address is both a evm primitive type and opcode, but it'll be lexed as opcode only when used within a macro body, as type only when inside param list of functions/events and as ident otherwise. Same goes with EVM primitive types and array types.
Eof and Whitespace are removed. Whitespaces are simply ignored and EOF can be simply inferred when lexer iterator gives out None value.
Lexer's iterator's assoc. type is now simply Token instead of a Result. So, you just do token.unwrap() instead of token.unwrap().unwrap().
A notable change is that TokenKind enum variants hold data (if any) of type &'a str only avoiding mixed types - making it more memory efficient because of the way enums behave in rust. Necessary conversion is done at parser or wherever required.

lmk any suggestions :)

this has gotten really old now.  changing to draft.


M3-5552: Fix Linode Add Disk Drawer UI width bug

Description 📝
What does this PR do?
Fixes the bug causing misalignment of Password and SSH Key fields by removing the default MUI theme padding.
For consistency, applied a bottom margin to match the top margin once bottom padding was removed.
Preview 📷

How to test 🧪
What are the steps to reproduce the issue or verify the changes?
Using the browser Developer Tools, view the component with the React Developer Tools > Components tab and search for 'AccessPanel'. Verify that the component's padding has been removed and a bottom margin added in its place.

Nice work getting your first PR up! 🎉
The <AccessPanel /> component is used in a few different files (you can do a keyword search in VSC for "<AccessPanel" to see which ones). Although the changes you made work in the "Add Disk" drawer, in some other contexts the formatting has become misaligned, for example in the Linode Create flow:

One option would be for us to make a change at a level closer to this specific individual instance the component is used in, perhaps adding some styling in ImageAndPassword.tsx, for example.

Thanks for catching that @DevDW!
I've now checked that the Create Linode page, the Add Disk Drawer, and the Rebuild from Image or StackScript, where the AccessPanel is used, all seem to be aligned correctly with this updated change. I went ahead and moved the styling to the ImageAndPassword component. Let me know if there are any further revisions I should make there; I modeled my styling changes after the styling in AccessPanel.

@DevDW Makes a lot of sense! Latest commit reflects those code pattern improvements.

@jdamore-linode
Could you give this a once over and let me know if my updates to ImageAndPassword.test.tsx look correct? I noticed that the test-manager build failed and found this error that seemed to be causing it in the logs:
  ● Test suite failed to run

    TypeError: theme.spacing is not a function

      12 | const useStyles = makeStyles((theme: Theme) => ({
      13 |   root: {
    > 14 |     margin: `${theme.spacing(3)}px 0 ${theme.spacing(3)}px 0`,
         |                      ^
      15 |     padding: 0,
      16 |   },
      17 | }));

I updated the unit test to include the wrapWithTheme helper function, like RebuildFromImage.test.tsx and re-ran the unit tests locally, and no longer noticed the failure.

@mjac0bs Nicely done, that is correct!
Without wrapWithTheme(...), the theme object that gets passed to your makeStyles(...) callback is just {}, so that's why you were seeing an error saying that theme.spacing() doesn't exist. Any component with custom styling that depends on the theme object will need to use wrapWithTheme() in its tests :)
It's also worth mentioning that this is an older unit test that uses enzyme rather than React Testing Library. That fact isn't really relevant to your question, just pointing it out since some of the patterns you see in our older tests won't line up exactly with the patterns we use in our newer tests!


[Azure CLI]: Created demo function for listing scope-based roles assigned to a backup vault

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
The precondition is to put your code inside this repository and upgrade the version in the pull request but do not modify src/index.json.

data protection


[Bug] App Crash: NullPointerException

Device: SM-S908B (samsung - b0s), SDK: 34 (14), App: 3.1.0-beta02 (155)java.lang.NullPointerException: Expected to unbox a 'boolean' primitive type but was returned nullat $Proxy2.isVisible(Unknown Source)at Re.B.a(SourceFile:1)at wf.f.x(SourceFile:753)at wf.d.v(SourceFile:17)at ma.a.k(SourceFile:9)at Ub.B0.p(SourceFile:54)at Ub.a.k(SourceFile:23)at ma.a.k(SourceFile:32)at Ub.B0.p(SourceFile:54)at Ub.a.k(SourceFile:23)at ma.a.k(SourceFile:32)at Ub.H.run(SourceFile:107)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)at java.lang.Thread.run(Thread.java:1012)Suppressed: Zb.e: [r0{Cancelling}@669290a, Dispatchers.Main.immediate]

Fixed already, will be in next beta


Permissions my plugin.yml used to use as "default: false" - anti-permissions?

Description
Until a few versions ago when I received a bug report from a LuckPerms user, this is how I have been defining a certain "anti-permission" to basically allow a server owner to declare a select group "newbies" and restrict usage of my plugin:
https://github.com/slipcor/PVPStats/blob/4e3b954794cdc229124e9d05cde2dbe7777e18d2/src/main/resources/plugin.yml#L39
This has been working well for years - maybe only with other permissions plugins - or without even - and it seems that recently either LuckPerms changed its way of verifying permissions, or I had an influx of LuckPerms users and LuckPerms always gives OPs the '*' permission as people call it, which gives all permissions.
I assumed that this is the case and it only applies to permissions mentioned in the plugin.yml and subsequently removed that "newbie" permission and replaced this with a positive-default "nonewbie" permission.
I wanted to keep it backwards compatible for the - I have to assume - vast majority of users who already have set up their permissions system to work with what I had before.
Now I learned while testing a new feature I planned, that the default LuckPerm setup actually still returns TRUE for the nonexisting permission "newbie" which I removed to only be used for server owners who set it up to work with "newbie" anti-permission rather than "nonewbie" permission. As I wanted to have the "newbie" be backwards compatible and be of higher priority, this now still breaks the newbie check of new LuckPerms users, until they set "newbie" to false ... which is not documented
Reproduction steps

download PVP Stats
check OPs for the permission "pvpstats.newbie" - which is not documented, but "all is true" ?
one player kill another player - either player is OP
the kill will not count

Expected behaviour
As both setups did not work, I guess I expected two different results and neither was the case:
A) (plugin.yml version from back in the day) - LuckPerms should load the permissions in the "plugins.yml" and default to "false" all the permissions that are set that way. All permissions that are supposed to be for OPs, I set to "op".
B) (current plugin.yml) - LuckPerms should only return "true" for any permission nodes that the plugin actually claims to register in the yml
Environment details

Server type/version: Paper running version 1.12.2 build October (players have been reporting bugs like this with other server versions)
LuckPerms version: v5.2.35

Any other relevant details
This is the current plugin.yml
https://github.com/slipcor/PVPStats/blob/master/src/main/resources/plugin.yml#L39
So there is two ways that this could have been resolved - if I would be allowed to keep my backwards compatibility for the confusing anti-permission setup, as my expectations in A / B above:
A) Is there a way for me to ask LuckPerms to allow my yml to have anti-permissions, is there a denominator or value I could add to my permission definition so that LuckPerms would know to not add it to the mix? If not, could this become a feature request then? - If LuckPerms is not going through the plugin.yml at all anyway and just returning "yes" for all perms then that might be touch :D
B) Fixing this, expecting LuckPerms to only ever add perms that we as plugin developers specifically define would break all other plugins that currently might rely on this OP-cheat or permissions that "start with" a known permission... so that is probably not a viable option. Could plugins get an opt-in for this?

At the end of the day, I am open for tips in how to resolve this. Any change on my end that allows for backwards compatibiliy even if it inconveniences the people who have adapted in the last weeks to my attempt to fix this, it should be worth the try.  I would very much appreciate a solution that would not require me to manually hook into LuckPerms, but if it is not possible otherwise, I'd rather do this than lose servers because they fall into my anti-permission trap :)

I can't seem to reproduce the issue, I defined in my test plugin's plugin.yml:
permissions:
  some.permission:
    default: false

The only thing that comes to my mind is the apply-bukkit-default-permissions setting. Make sure it is set to true in your LP config: https://github.com/lucko/LuckPerms/blob/5c443338927104da858beca9d1306628671bdcac/bukkit/src/main/resources/config.yml#L490-L495

Thank you for your time!
I tried addressing this by reintroducing the permission setting, defaulting to false in my plugin.yml.
This works out of the box, as you pointed out, but then what happens is that admins give themselves the "*" permission to test out all the features, assuming that they have "all permissions", in turn giving themselves a permission that is restrictive in my logic.
Is there a way that I can set up a permission in a way that it will not be granted if a server admin gives themselves '*'? I fully understand that this is expected behaviour for all permissions that are considered allowing permissions, and not "anti-permissions" as I have it set it up to be.
For now I added a small workaround, checking for an undefined/unclaimed permission. If a player has this, we assume that they are operator / have all permissions and probably did no want to be excluded from the functionality of my plugin.
So is my workaround then the most accurate fix then?

You just set the specific permission to false. * perm node is not recommended as well. See: https://v2.nucleuspowered.org/docs/nowildcard.html

I know that it is not recommended. No need to convince me :)
But what can I do when server owners do use them when setting everything up and then expect my plugin to work the way they think it should?
If there is no way to prevent this while defining or checking permissions on my end, I will just stick to my current setup that checks for undefined permissions :)
An upcoming version will display warnings about this and maybe explain this behavior to affected server owners.

You just ask them to set the permission node to false, bcu that how permission works, its just true or false, no special whitelist/blacklist to over complicate things.

... and then expect my plugin to work the way they think it should?

And that's the issue and why we are against wildcards, admins and owners not knowing any better blindly sticking * here and there.
Bukkit defaults are used as an ultimate fallback if the permission ends up undefined by any other means (specific permission, Regex, shorthand, wildcard, sponge wildcard, Bukkit child permissions); the wildcard (like any of the other kinds of permissions mentioned) is doing its job, this is the exact same reason in the discord server when people ask for support he don't really recommend the usage of the root wildcard and I personally suggest to use the auto-op feature instead, but of course I can't account for everyone, can I?
What you can do from the plugin side is check for both the permission you want and *, although that is a bit hacky IMO.

Thing is that everything in here is working as intended. I see where you're coming from (as I myself had to deal with this, ended up checking for * too) and I would love to see Luck's opinion on the matter :)

Hopefully the above change will solve this issue for you. :)
You'll need to insert the new option into your config, as it defaults to being disabled if the section is missing.
# If the plugin should apply negated Bukkit default permissions before it considers wildcard
# assignments.
#
# - Plugin authors can define permissions which explicitly should not be given automatically to OPs.
#   This is usually used for so called "anti-permissions" - permissions which, when granted, apply
#   something negative.
# - If this option is set to true, LuckPerms will consider any negated declarations made by
#   plugins before it considers wildcards. (similar to the way the OP system works)
# - If this option is set to false, LuckPerms will consider any wildcard assignments first.
apply-default-negated-permissions-before-wildcards: true

Yes, this is very helpful and validating because it is in agreement with how I understand how permissions were defined to work.
I hope that this does not break functionality with plugins that might rely on the asterisk flipping their false to true - however I think we are in agreement that the absolute wildcard should not be used, and specific (parent) wildcards can and should be defined and then used to flip groups of permissions, and also, perms should be set and used as verbose as reasonably possible which would allow for expected convenience behaviour.
Thank you very much for this swift response! I am absolutely fine with this not changing everyone's config, I will include a warning in my plugin, so people can update their config if they really need to give out the asterisk.
Have a healthy rest of the year!

Hi, this is in fact breaking to other plugins yes.
After the fifth or so user came into the Citizens channel to ask why they couldn't use Citizens anymore, I looked into it and found this breaking change was at fault.
While I do think it fair to change Citizens permissions to default: op and don't find the commit inherently unreasonably, I must very strongly protest the issue post here...

"Anti-permissions" do NOT EVER EVER EVER SUPER NO NOT EVER belong in the permissions system.
Permissions are PERMISSIONS. They are not SETTINGS. They are not USER CHOICES. They are not something a user chose to enable. They are things the user IS ALLOWED to enable. A player should never be vanished, restricted, or anything else by a PERMISSION.
The concept of things that happen automatically to a player by choice is called user configuration. (In Bukkit this is usually janked into a <uuid>.yml file somewhere, though in both modern Spigot and Sponge there are better persistent data options available.)

The opposite of a permission is... well, not having that permission. In LuckPerms that'd be setting the permission to false. In other permissions plugins that's usually just prefixing the permission with a -. Or, of course, in any permission plugin... simply not giving the relevant permission in the first place.
Restricting a user's actions is reasonable in the case of LACKING a permission, not HAVING that permission.
Granting a * permission is fundamentally saying "you are allowed to do whatever you want"... any plugin that does not obey that fundamentally does not understand what the word "permission" means.
That is what commands and user configuration data are for. Please, please... NEVER mix permissions and user settings. These are two fundamentally separate concepts.

Hi, this is in fact breaking to other plugins yes.
After the fifth or so user came into the Citizens channel to ask why they couldn't use Citizens anymore, I looked into it and found this breaking change was at fault.
While I do think it fair to change Citizens permissions to default: op and don't find the commit inherently unreasonably, I must very strongly protest the issue post here...

"Anti-permissions" do NOT EVER EVER EVER SUPER NO NOT EVER belong in the permissions system.
Permissions are PERMISSIONS. They are not SETTINGS. They are not USER CHOICES. They are not something a user chose to enable. They are things the user IS ALLOWED to enable. A player should never be vanished, restricted, or anything else by a PERMISSION.
The concept of things that happen automatically to a player by choice is called user configuration. (In Bukkit this is usually janked into a <uuid>.yml file somewhere, though in both modern Spigot and Sponge there are better persistent data options available.)

The opposite of a permission is... well, not having that permission. In LuckPerms that'd be setting the permission to false. In other permissions plugins that's usually just prefixing the permission with a -. Or, of course, in any permission plugin... simply not giving the relevant permission in the first place.
Restricting a user's actions is reasonable in the case of LACKING a permission, not HAVING that permission.
Granting a * permission is fundamentally saying "you are allowed to do whatever you want"... any plugin that does not obey that fundamentally does not understand what the word "permission" means.
That is what commands and user configuration data are for. Please, please... NEVER mix permissions and user settings. These are two fundamentally separate concepts.

I only just noticed that the default for this "fix for anti permissions" is true by default. maybe that needs to be changed? everyone setting this setting to "false" will experience the old behaviour and I think it is fair to say that the anti-permission logic is deviating from the norm :)

I only just noticed that the default for this "fix for anti permissions" is true by default. maybe that needs to be changed? everyone setting this setting to "false" will experience the old behaviour and I think it is fair to say that the anti-permission logic is deviating from the norm :)

Permissions are PERMISSIONS

NEVER mix permissions and user settings

I agree with you on this, and think that it should just be easy to just grant * to give users access to everything permission related.
However, the reality of the situation is that plugin authors are using the system for "anti-permissions", and that's something that LuckPerms should therefore aim to support in my opinion.
The idea behind this change was exactly that - to allow plugin authors to mark in their plugin.yml permissions that explicitly should not be given in bulk to "super users" / OPs, either through /op or the * permission. (this is the way Bukkit intended for the system to work, before permission plugins added the auto wildcard resolution (root * etc) we now have)
However, it seems like on Bukkit at least, plugin authors / server admins are set in their ways and expect even the root wildcard to override plugin defined false defaults. I do understand this, and it's the reason why LP worked in the way it did until the change was made in response to this issue.
We have also noticed a fair amount of users running into unexpected issues with this in our support channels.
It's a shame because I personally think the setting should default to true, but, I appreciate we're well past the point of making improvements to the way Bukkit permissions work.
So, I've swapped it back to false by default for new installs. The setting remains true by default on Sponge though.

Permissions are PERMISSIONS

NEVER mix permissions and user settings

I agree with you on this, and think that it should just be easy to just grant * to give users access to everything permission related.
However, the reality of the situation is that plugin authors are using the system for "anti-permissions", and that's something that LuckPerms should therefore aim to support in my opinion.
The idea behind this change was exactly that - to allow plugin authors to mark in their plugin.yml permissions that explicitly should not be given in bulk to "super users" / OPs, either through /op or the * permission. (this is the way Bukkit intended for the system to work, before permission plugins added the auto wildcard resolution (root * etc) we now have)
However, it seems like on Bukkit at least, plugin authors / server admins are set in their ways and expect even the root wildcard to override plugin defined false defaults. I do understand this, and it's the reason why LP worked in the way it did until the change was made in response to this issue.
We have also noticed a fair amount of users running into unexpected issues with this in our support channels.
It's a shame because I personally think the setting should default to true, but, I appreciate we're well past the point of making improvements to the way Bukkit permissions work.
So, I've swapped it back to false by default for new installs. The setting remains true by default on Sponge though.

I think the core issue of that whole ordeal is that what permissions default to true or false are not visible to the user at all!
Mean they are tapping around in the dark with no chance of figuring out why that specific set of permissions is false even though they believe they should have those permissions. If there was a way to visualize the default permissions this whole issue should become a non-issue as then people can actually find the root cause.

I think the core issue of that whole ordeal is that what permissions default to true or false are not visible to the user at all!
Mean they are tapping around in the dark with no chance of figuring out why that specific set of permissions is false even though they believe they should have those permissions. If there was a way to visualize the default permissions this whole issue should become a non-issue as then people can actually find the root cause.


Update filters, add nin (does not equal) operator

Changes include:

cleanup filters parsing, error handling for unsupported operators.
add support for nin (does not equal) operator.
add ; separator for array values (for == and != operators)

:tada: This PR is included in version 1.0.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Added filtering to buildAutoChooser for C++

Added a new input for buildAutoChooser for C++ which allows filtering out autos based on their internal data like name or start position.
Default Option is guaranteed to be unfiltered to prevent nullptr.
GetSelected() causes a default initialized Command* to nullptr.
Added buildAutoChooser with filtering to writerside wiki explaining how it works.

A note to add about the filtering function: the pointers are only valid if the function returns true. If a user want a do a shallow copy of the pointer, it needs to return true, otherwise they will get a nullptr because the function deletes unused commands. They must do a deep copy if they want to store it for later.
I don't know if you want to put this info in the API and wiki but it could be a edge case for some users.

Needs some conflicts to be resolved then I can merge this. It looks like its just conflicts with includes. You can accept the version from the current main branch.

It been a while since I reviewed my code and I am just going to remove this pull request and make a new one since pathplanner has changed a bit.
I also want to address some of my inefficiencies which I brought into code such as always making new commands reference everytime a new frc::SendableChooser is requested. I want to get this done before my code needs to become backward capability.


chore(api): add critical error for funder balance

approved, although tests are failing, seems one is related to a linting issue resulting from the diff of this PR


Update header.html

This website is based on the Lab Website Template.
See its documentation for working with this site:
https://greene-lab.gitbook.io/lab-website-template-docs

lkm;jkj


get_version endpoint is never cached

This is a small bug in RBC I just found yesterday.
https://github.com/xnd-project/rbc/blob/cacf447af6b599c914964b3f2d27fbce430f4b81/rbc/omniscidb.py#L280-L285
self._version is never assigned, and the thrift endpoint is always called.

Fixed in #362


Constant messages on closed PRs that "release failed to be created"

You can see an example of the issue here: https://github.com/open-telemetry/opentelemetry-js-contrib/pull/671
We believe we have properly configured release-please and it seems to work ok, but it constantly spams us with messages on old merged PRs that it has failed to create a release. Is there something we've done wrong in our configuration?

Is this still a problem?

Yes this is still a problem


great article

thanks for article published by authors.
But I could not able to understand because  , I am not a programmer , to read this article, first I need to learn programming languages .
This article is very helpful for designing of gpu.

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

ID: bbeaad59-c4c0-b98d-da80-cfcda9da2ce5
Version Independent ID: 1e213c93-4bb7-dad0-49c9-c996c73bc04a
Content: GpuMmu model - Windows drivers
Content Source: windows-driver-docs-pr/display/gpummu-model.md
Product: windows-hardware
GitHub Login: @nabazan-microsoft
Microsoft Alias: windowsdriverdev

@RAJU2529
Hi Varadharajan, Thank you for you comment! Yes, that is correct, in order to develop on GPUs, you must learn driver development. You can start by learning the programming language C++, and then learn how to write drivers.
Best,
Mimi


How to get json from remote config

Please fill in the following fields:
Firebase C++ SDK version: Latest
Firebase plugins in use (Auth, Database, etc.): RemoteConfig
Additional SDKs you are using (Facebook, AdMob, etc.): None
Platform you are using the SDK on (Mac, Windows, or Linux): Android
Platform you are targeting (iOS, Android, and/or desktop): Android
Please describe the issue here:
Please provide example how to read arbitrary JSON from remote config.
In https://console.firebase.google.com I set
level_to_star_count = {"level_1":9,"level_2":8}
How can I read those data from C++
I would expect interface similar to GetLong, GetBoolean
std::map<firebase::Variant, firebase::Variant> GetMap(const char* key)

or some generic:
firebase::Variant GetVariant(const char* key);
... and
const firebase::Variant variant = GetVariant("level_to_star_count");
if(variant.is_map())
{
     const std::map<firebase::Variant, firebase::Variant>& map = variant.map()
}

Please answer the following, if applicable:
Have you been able to reproduce this issue with just the Firebase C++ quickstarts (this GitHub project)?
What's the issue repro rate? 100%

Seems like you could use the methods in the remote config quickstart. See here.

@crazyhappygame
Currently Remote Config API only support boolean, double, string and byte array. Unfortunately it does not support map or any nested data structure yet.
I think the closest thing you can do is to serialize the JSON into string or byte array, and deserialize it after fetching.
Another options for you is parameter grouping
https://firebase.google.com/docs/remote-config/parameters
This allow you to create a group, ex. level_to_star_count, and put level_1, level_2 into this group so that you can organize them better.
Note that the group name does not change how you reference the parameter.  That is, you still need to use the parameter name like GetVariant("level_1");
Hope this helps.


Softlocks the game if you request a Rare item that's already in your inventory

I mistakenly obtained 2 Chasseur's Tricornes +2, one in my storage slip, one in my inventory.
I used /lac unpack to get all of my gear set up as I usually do, and when I did, Porter got in an infinite loop of trying to grab the hat, failing because I already have one in my inventory, and trying again.
Because porter blocks all input while it's trying to gather gear, the only way to escape this loop was to kill the game from the task manager.

Fixed in 1.11, thank you for reporting.


Preserve newlines in eval output

In --allow-eval, newlines are removed from the output. This fixes it to preserve line breaks.

Seems plausible - thanks!


Revert "Create 615 Glenwood Ave Owosso"

Reverts Maxjo275/Emma#1
For your best request kindly contact us we have so many projects we have so many designs I'm so many industrial cleaning you have so many things you can need in the world kindly contact us ok thanks

You are here live to give you exactly what you want kindly contact us


Integerate SentenceBert

TODO: Semantic Embedding using SentenceBert and Cosine similarity

Integerated SentenceBert to extract semantic vectors out of user queries and using cosine similarity to choose the most similar answer.


[WIP] Customizable Key exchange

[x] Implementation of key exchange trait with 3DH example.
[x] fix genericity violations in key-exchange (Repr = Key constraints)
[x] Implementation of key exchange trait with snow / Noise, under flag,
[ ] generic serialization for key exchange states and messages,
[ ] generalize opaque.rs in terms of the traits, not the 3DH implementation,
- [x] fix CI to run with --all-features (backported)
[ ] test key exchange trait with snow / Noise,
[ ] doc examples for the trait implementation,
[ ] integration in the CipherSuite machinery.

Addresses #3

Replaced by #20 as a base for further development