Error running mix

Laravel Mix Version: 0.8.8
Node Version (node -v): 7.6.0
NPM Version (npm -v): 4.1.2
OS: Windows 10 (Laravel Homestead)

Description:
I've run npm install straight out of the box, which works fine. However, when run "npm run dev" I get an error:
npm ERR!     node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
The error code is ELIFECYCLE.

I have no idea. Have you made any tweaks at all? Can you do:
laravel new app && cd app
npm install
npm run dev

Do you still get that ELIFECYCLE error?

Mhm, still the same error ~

Hmm, not sure at all. You're the only one who has made an issue like this.
Is anyone else experienced this, who can shed some light on a solution?

What if you run it manually?
node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

or even
set NODE_ENV=development
node node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

Can you post the full error log(s)?

Running  node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js manually gives a more fun error ~
(It seems to be unable to find som directories, even though they exist :/ )
`
ERROR  Failed to compile with 3 errors                                                                                6:16:11 PM
error  in ./resources/assets/sass/app.scss
Module build failed: Error: ENOENT: no such file or directory, scandir '/home/vagrant/Projects/app/node_modules/node-sass/vendor'
at Object.fs.readdirSync (fs.js:912:18)
at Object.getInstalledBinaries (/home/vagrant/Projects/app/node_modules/node-sass/lib/extensions.js:122:13)
at foundBinariesList (/home/vagrant/Projects/app/node_modules/node-sass/lib/errors.js:20:15)
at foundBinaries (/home/vagrant/Projects/app/node_modules/node-sass/lib/errors.js:15:5)
at Object.module.exports.missingBinary (/home/vagrant/Projects/app/node_modules/node-sass/lib/errors.js:45:5)
at module.exports (/home/vagrant/Projects/app/node_modules/node-sass/lib/binding.js:15:30)
at Object. (/home/vagrant/Projects/app/node_modules/node-sass/lib/index.js:14:35)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/home/vagrant/Projects/app/node_modules/sass-loader/lib/loader.js:3:14)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at loadLoader (/home/vagrant/Projects/app/node_modules/loader-runner/lib/loadLoader.js:13:17)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
at /home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:173:18
at loadLoader (/home/vagrant/Projects/app/node_modules/loader-runner/lib/loadLoader.js:36:3)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
at /home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:173:18
@ ./resources/assets/sass/app.scss 4:14-234
@ multi ./~/laravel-mix/src/mock-entry.js ./resources/assets/sass/app.scss
error  in ./resources/assets/sass/app.scss
Module build failed: Error
at /home/vagrant/Projects/app/node_modules/webpack/lib/NormalModule.js:141:35
at /home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:364:11
at /home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:170:18
at loadLoader (/home/vagrant/Projects/app/node_modules/loader-runner/lib/loadLoader.js:27:11)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
at /home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:173:18
at loadLoader (/home/vagrant/Projects/app/node_modules/loader-runner/lib/loadLoader.js:36:3)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
at /home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:173:18
at loadLoader (/home/vagrant/Projects/app/node_modules/loader-runner/lib/loadLoader.js:36:3)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:165:10)
at /home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:173:18
at loadLoader (/home/vagrant/Projects/app/node_modules/loader-runner/lib/loadLoader.js:36:3)
at iteratePitchingLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:169:2)
at runLoaders (/home/vagrant/Projects/app/node_modules/loader-runner/lib/LoaderRunner.js:362:2)
at NormalModule.doBuild (/home/vagrant/Projects/app/node_modules/webpack/lib/NormalModule.js:129:2)
at NormalModule.build (/home/vagrant/Projects/app/node_modules/webpack/lib/NormalModule.js:180:15)
at Compilation.buildModule (/home/vagrant/Projects/app/node_modules/webpack/lib/Compilation.js:142:10)
at moduleFactory.create (/home/vagrant/Projects/app/node_modules/webpack/lib/Compilation.js:424:9)
at /home/vagrant/Projects/app/node_modules/webpack/lib/NormalModuleFactory.js:242:4
at /home/vagrant/Projects/app/node_modules/webpack/lib/NormalModuleFactory.js:93:13
at /home/vagrant/Projects/app/node_modules/tapable/lib/Tapable.js:204:11
at NormalModuleFactory.params.normalModuleFactory.plugin (/home/vagrant/Projects/app/node_modules/webpack/lib/CompatibilityPlugin.js:52:5)
at NormalModuleFactory.applyPluginsAsyncWaterfall (/home/vagrant/Projects/app/node_modules/tapable/lib/Tapable.js:208:13)
at onDoneResolving (/home/vagrant/Projects/app/node_modules/webpack/lib/NormalModuleFactory.js:68:11)
at onDoneResolving (/home/vagrant/Projects/app/node_modules/webpack/lib/NormalModuleFactory.js:189:6)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
error
/home/vagrant/Projects/app/node_modules/extract-text-webpack-plugin/loader.js??ref--8-0!/home/vagrant/Projects/app/node_modules/style-loader/index.js!/home/vagrant/Projects/app/node_modules/css-loader/index.js!/home/vagrant/Projects/app/node_modules/postcss-loader/index.js!/home/vagrant/Projects/app/node_modules/resolve-url-loader/index.js!/home/vagrant/Projects/app/node_modules/sass-loader/lib/loader.js??ref--8-5!/home/vagrant/Projects/app/resources/assets/sass/app.scss doesn't export content
`

Getting the same error with a fresh install of Windows 10, Node and Laravel
node 6.10.0
npm 3.10.10
Laravel Framework 5.4.15
Haven't touched the package.json file or any other file and get errors on npm run dev
``
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "dev"
npm ERR! node v6.10.0
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! @ dev: node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the @ dev script 'node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Daniel\Projects\card\npm-debug.log
``
The package.json file
``
{
"private": true,
"scripts": {
"dev": "node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
"watch": "node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
"watch-poll": "node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --watch-poll --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
"hot": "node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
"production": "node node_modules/cross-env/bin/cross-env.js NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
},
"devDependencies": {
"axios": "^0.15.3",
"bootstrap-sass": "^3.3.7",
"jquery": "^3.1.1",
"laravel-mix": "^0.8.1",
"lodash": "^4.17.4",
"vue": "^2.1.10"
}
}
``

Found a solution, had originally used npm install --no-bin-links it didn't work, but didi npm rebuild --no-bin-links and npm run dev works fine @MysticSheik @JeffreyWay

I tried running "npm rebuild --no-bin-links" with no luck. Still the ELIFECYCLE. I decided to try a fresh install on my Windows 7, but got the same results after running:

"laravel new [APP NAME]"
"npm install --no-bin-links"
"npm rebuild --no-bin-links"
"npm run dev"

My errors looks like this
My NPM Debug Log file looks like this

Have you tried going to node js and installing to get the latest version?

Yes, both Node and NPM is up to date ~

Are you using Git bash if so try using command line. This didn't work for me but I also did npm clean cache command and then the npm rebuild --no-bin-links

If you have problems with this I have used windows 7 with Laravel 5.2 & 5.3 using gulp, I suggest searching that and using it instead, most of these laravel things are built by people using macs so windows aren't really top of the agenda, hope this helps, if not let me know and will try to help.

Yeah, I've used Gulp before ~
I guess I'll just continue using that then c:

Currently I am developing a non-laravel, but i want to use laravel-mix as @JeffreyWay showed in Vue2.0 lesson, but its not working.  Here is the error report,
`C:\wamp64\www\OurProject\shapecss-framework>npm run watch

@ watch C:\wamp64\www\OurProject\shapecss-framework
node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

module.js:472
throw err;
^
Error: Cannot find module 'C:\wamp64\www\OurProject\shapecss-framework\node_modules\cross-env\bin\cross-env.js'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.runMain (module.js:605:10)
at run (bootstrap_node.js:425:7)
at startup (bootstrap_node.js:146:9)
at bootstrap_node.js:540:3
npm ERR! Windows_NT 10.0.10240
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "run" "watch"
npm ERR! node v7.7.1
npm ERR! npm  v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! @ watch: node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ watch script 'node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the  package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node node_modules/cross-env/bin/cross-env.js NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     C:\wamp64\www\OurProject\shapecss-framework\npm-debug.log
`

Do npm install cross-env -D and then update your package.json file to look like this:
https://github.com/laravel/laravel/blob/master/package.json#L4-L8

@JeffreyWay Thank you. You are simply boss.
https://github.com/MicroDreamIT/ShapeCss its a shape generator, now I am trying to build a complete framework like bootstrap. I have used laravel-elixir before.
The testing repository I have just created, https://github.com/MicroDreamIT/shapecss-framework
Now I am using laravel-mix, and you lessons... :)

Just want to comment, I had the same problem as OP and the npm rebuild --no-bin-links worked for me.  I am running nodejs 8 on ubuntu 16.04 so I wasn't sure if the "do this if you're running a VM on Windows" thing would work, but it did.  Thanks!

how can i remove error on this?
@import '~bootstrap/scss/bootstrap';


adding ionics icon set back to site listing

adding ionics icon set back to IconSet by making it compatible for website
PR: https://github.com/Foysal50x/blade-ionicons/pull/8

Thanks!!


[Improvement][User] Query all users filter un enabled.

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Query all users filter un enabled.
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

closed by #11504


frequency_analysis crashes if there are empty grid cells

xclim version: 0.11.2
Python version: 3.6
Operating System:

Description
I have a Dataset on a rotated grid (EC-EARTH_HIRHAM5, from CORDEX-NA). I've made a subset for my region, and on the borders of that subset, some grid cells are empty (meaning that all values are NaN).
Following a call to frequency_analysis, the code crashes if I try to save the data to NetCDF, or even with a simple ".values" call. I receive the following error:
ValueError: zero-size array to reduction operation minimum which has no identity
What I Did
import xarray as xr
from xclim import subset
from xclim import generic as xcgen
ds = xr.open_mfdataset("/path/to/rotated/pole/data")  <--- EC-EARTH_HIRHAM5 hourly precipitation for the 1981-2010 period
ds_subset = subset.subset_bbox(ds, lat_bnds=lat_bnds, lon_bnds=lon_bnds)
da_freq = xcgen.frequency_analysis(ds_subset["pr"], mode="max", t=2, dist="genextreme", window=6, freq="YS")
da_freq.isel(return_period=0).values  <-- crashes
If I use the following code, everything works fine (except that I get data in locations that should be NaN):
import xarray as xr
from xclim import subset
from xclim import generic as xcgen
ds = xr.open_mfdataset("/path/to/rotated/pole/data")
ds_subset = subset.subset_bbox(ds, lat_bnds=lat_bnds, lon_bnds=lon_bnds)
ds_subset["pr"] = ds_subset["pr"].fillna(value=0)  <-- this is the new line
da_freq = xcgen.frequency_analysis(ds_subset["pr"], mode="max", t=2, dist="genextreme", window=6, freq="YS")
da_freq.isel(return_period=0).values

I think this is specifically caused by .dropna(dim="time") at line 263 of generic.py. If a grid cell is empty, this will create the 0-size array that is causing problems later.


Should abort trigger onclose?

Hello!
While I was working with server-sent events I've discovered similar shortcomings as you. Glad your library exists to fix them!
One issue I've discovered with your library is that calling ctrl.abort() won't result in either onclose or onerror calls. This makes it difficult to collocate code which is responsible of handling connection closing, be it by a server or manual.
Is there something I am missing? Would it make sense as a feature?

@gyzerok did you get any fixes for this, I am having the same kind of scenario where I need to stop the connection on a particular condition.

Please change toreject({ aborted:true }) here
https://github.com/Azure/fetch-event-source/blob/6fb7115ebacb90600b54383ea32f799f6f647203/src/fetch.ts#L97

Please change to reject({ aborted:true }) here
https://github.com/Azure/fetch-event-source/blob/6fb7115ebacb90600b54383ea32f799f6f647203/src/fetch.ts#L97

Has anyone tested this does fix the issue without other regressions? Should we create a PR?

As the same. I call thectrl.abort(), but it is trigger neither onclose or onerror.

Why is this closed?

Please change to reject({ aborted:true }) here
https://github.com/Azure/fetch-event-source/blob/6fb7115ebacb90600b54383ea32f799f6f647203/src/fetch.ts#L97

Has anyone tested this does fix the issue without other regressions? Should we create a PR?

I think we can create a PR for this, let's see if I can have time for this. Of course need to keep an eye on the regressions, and I think maintainers can see if that can happen.


[SVS-7] preparation for solution level conflict detection (will be done after this one)

Moved all the service-liked interfaces to be serviced by the host - this helped to simplify the test specific service injection and simplified the product code that in most cases no longer needs those interfaces to be passed from an internal constructor.
Note: this was done only for binding bits, and we should do something similar next time when working on the connection bits.

Extracted the logic from binding into a service that will be used in the last piece (i.e. find and fix conflicts in the entire solution).

[EDIT] 3: Added support for pulling rule set directories (another property) and to pass it into conflicts finding/fixing API.
I also included a code example (BindingController.CheckForConflicts) that I'll be aiming for in the last PR for this feature. In general there will be a service that I can invoke from other places and not just after binding, although in those case we will need to address some of the edge cases which I don't plan on handling at first (need to get initial feedback from Jean-Marc first).

Other than comments; LGTM


GLEAN model test--Spatial resolution must equal in_size (32)

测试命令行
python demo/restoration_demo.py configs/restorers/glean/glean_cat_8x.py checkpoint/glean_cat_8x_20210614-d3ac8683.pth ./pic/csmz2_2s_540p/00000000.png ./zjrout/picSuper/00000000_glean_8x.png --device 3
报错信息
AssertionError: Spatial resolution must equal in_size (32). Got (1080, 1920)

Traceback (most recent call last):
File "demo/restoration_demo.py", line 62, in
main()
File "demo/restoration_demo.py", line 53, in main
output = restoration_inference(model, args.img_path)
File "/home/pc/zyp/mmediting-master/mmedit/apis/restoration_inference.py", line 46, in restoration_inference
result = model(test_mode=True, **data)
File "/home/pc/anaconda3/envs/mmedit/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/home/pc/anaconda3/envs/mmedit/lib/python3.8/site-packages/mmcv/runner/fp16_utils.py", line 110, in new_func
return old_func(*args, **kwargs)
File "/home/pc/zyp/mmediting-master/mmedit/models/restorers/srgan.py", line 95, in forward
return self.forward_test(lq, gt, **kwargs)
File "/home/pc/zyp/mmediting-master/mmedit/models/restorers/glean.py", line 54, in forward_test
output = self.generator(lq)
File "/home/pc/anaconda3/envs/mmedit/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1110, in _call_impl
return forward_call(*input, **kwargs)
File "/home/pc/zyp/mmediting-master/mmedit/models/backbones/sr_backbones/glean_styleganv2.py", line 209, in forward
raise AssertionError(
AssertionError: Spatial resolution must equal in_size (32). Got (1080, 1920).

Hello,
The size of the image should be 32x32 but you use a 1080x1920 one. The desired size of the model is indicated in the config file by key model.generator.in_size.


[Bug] 'team' table seems to be optional

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the issue
We use a Fivetran connector for Github and we sync all available tables (including team and team_membership. However, we are not using that feature in Github, so those tables are not materialized in our DW. Therefore, running all github models failed.
Following the readme for REPO_TEAM, we tried adding {{ config(enabled=var('github__using_team', True)) }} to stg_github__team and stg_github__team_tmp and editing the dbt_project.yml: that worked!
Relevant error log or model output
Runtime Error in model stg_github__team_tmp (models/tmp/stg_github__team_tmp.sql)
404 Not found

Expected behavior
To run all models without errors by setting a new variable
dbt Project configurations
config-version: 2

name: 'github_source'
version: '0.5.0'

require-dbt-version: [">=1.0.0", "<2.0.0"]

models:
  github_source:
    materialized: table
    tmp:
      materialized: view

vars:
  github_source:
    issue_assignee: "{{ source('github', 'issue_assignee') }}"
    issue_closed_history: "{{ source('github', 'issue_closed_history') }}"
    issue_comment: "{{ source('github', 'issue_comment') }}"
    issue_label: "{{ source('github', 'issue_label') }}"
    label: "{{ source('github', 'label') }}"
    issue_merged: "{{ source('github', 'issue_merged') }}"
    issue: "{{ source('github', 'issue') }}"
    pull_request_review: "{{ source('github', 'pull_request_review') }}"
    pull_request: "{{ source('github', 'pull_request') }}"
    repo_team: "{{ source('github', 'repo_team') }}"
    repository: "{{ source('github', 'repository') }}"
    requested_reviewer_history: "{{ source('github', 'requested_reviewer_history') }}"
    team: "{{ source('github', 'team') }}"
    user: "{{ source('github', 'user') }}"

    github__using_repo_team: false # by default this is assumed to be true

Package versions
  - package: fivetran/github
    version: [">=0.5.0", "<0.6.0"]

(we checked the new release before opening this issue)

What database are you using dbt with?
bigquery
dbt Version
Core:
  - installed: 1.3.1
  - latest:    1.3.2 - Update available!

  Your version of dbt-core is out of date!
  You can find instructions for upgrading here:
  https://docs.getdbt.com/docs/installation

Plugins:
  - bigquery: 1.3.0 - Up to date!

Additional Context
No response
Are you willing to open a PR to help address this issue?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during our office hours for guidance
[ ] No.

Hi @paulavidela thanks so much for opening this issue!
From what you mentioned I see why there may be cases where customers (such as yourself) do not have the team table synced and therefore have no use for the team models in the GitHub dbt package.
The approach you highlighted is exactly what I would do to implement the feature to disable the team models. In addition to updating the source package we will also most likely want to update the dbt_github package (transform package) to account for the new upstream model disablement. Fortunately, it seems team is only ever used in conjunction with repo_team. Therefore, I think we may be able to consolidate the team disablement with the repo_team disablement.
This meaning, instead of creating a new variable as you have proposed, we simply repurpose the github__using_repo_team variable to be used within the team staging models. The naming convention is already similar and it would simply require an update to the staging models to include the config (as you proposed) and an update to the READMEs for both the source and the transform packages!
I noticed you are interested in contributing a PR for this fix. If so, the above plan is what I would recommend. Let me know if you have any questions and I will be happy to help in any way. Once the PRs are opened we can then move forward with review 😄. If you are not interested in opening a PR, my team can pull this into a future sprint. Let me know your thoughts.
Thanks!

Hi @paulavidela, following up to @fivetran-joemarkiewicz's comment, I have taken up this issue and should have something you can test out within the week!

Hi @paulavidela, I have incorporated your suggestion into a branch that you can test out if you like. You can install the test branch by adding the below to you packages.yml instead of the published package.
You can use this to test the transform with the source changes:
packages:
  - git: https://github.com/fivetran/dbt_github.git
    revision: release/v0.7.0
    warn-unpinned: false

Or this to test out the source changes only:
packages:
  - git: https://github.com/fivetran/dbt_github_source.git
    revision: bug/add-disable-teams
    warn-unpinned: false

If you do get a chance to test it out, please let me know how it works out for you!

Hi @paulavidela, we have released the changes mentioned in this issue into the latest version of this package. Closing out this issue, but just let us know if you have any questions.


Access control / Sharing write access

As an end user I want to share write control with other users so that they can contribute to the VSM
VSM-113

This lays the groundwork for #86. It is basically done, but would be smart to wait with releasing this until #82 is done.

Some comments from our PO
Access control in QA has been tested with two users. A couple of comments:

There is no e-mail notification to users that has been added. I guess this is what you Peder is working on. Not critical for initial release.
[ ] When a user is granted contributor or admin rights to a process someone else is owner of, it is not showing in the "Edit" view on the front page. I think this should be fixed before release
After removing contributor access to a user, the user could still open the process and add a card but got an error message.

[ ] Add sync when access changes

After refreshing the page he only had read access (no toolbar visible)
When a user without priveleges opens the share popup screen; the following message appears: "You need to be creator or admin to manage sharing". There is no role with name "creator", should probably be "owner"? Meaning error message should be "You need to be owner or admin to manage sharing"

[ ] Change text to "You need to be owner or admin to manage sharing"

User wanted to share by name instead of shortname. Not critical for initial release, but maybe a user story we should add to the backlog?


[codemod] feature request: rollback on failure

Faulty codemod

react/19/migration-recipe
https://codemod.com/registry/next-15-migration-recipe

Problem
In this case it changed a bunch of my codebase but failed on this codemod, I would like it to rollback if it fails and not leave my codebase in the failed state with only partial codmods done.
This was originally happening with the next@15 codmod.

thanks for reporting the feature request.

any reason not to use git stash?

also, you can run the individual codemods in the recipe by deselecting the unwanted ones. do you know how? (use spacebar to deselect things when you run the recipe via CLI)

and finally, if there is any specific issues with any individual codemod, feel free to open up a github issue and ping our awesome community member, @nishant2253, who built these codemods.

NOTE: these are NOT the official codemods by next.js team. you can find the official codemods built by vercel team here.

I did eventually use git to roll back, but I'd figure this is something I want codmod to do not me.
The next one just ran all of them and failed in the middle of one of them - having an interactive way to rollback or figure out a fix before exiting would be better.
Yeah, I will try to go to next 15 when it's a bit more mature it seems like react 19 isn't out yet either - but I'll keep that in mind and report if it continues to happen!

I tried running the official codemod of the vercel team and I think they used those internally, no? I used npx @next/codemod@canary upgrade latest

1 & 2: To @agamm: Got it. Thanks for the explanation. Besides "recipe," we also have another advanced workflow engine where we can technically create an advanced recipe where after each individual codemod, changes are committed. This way, if one of the changes is not good, you can revert to previous commits. Would that somehow address what you need? If not, could you explain what your desired experience would be (and how we might build it? reasonable and feasible?)
To @nishant2253: Node modules should have been excluded by default. Do you want to fix this? Feel free to ask folks in the community if you need help.
3: "I think they used those internally, no?" I don't know what you mean by that. I'm curious how they fell short. How did you find Nishant's codemods in the registry? Why did you decide to give that a try? I would love to know more and see which codemods are missing to create an awesome Next.js upgrade experience.

1-2, only if it also tracks things outside the gitignore and manages to roll them back (like dependency package changes).

Internally it's a good question on how to achieve this, maybe create a separate git history just internally for codmod and use that for rollbacks?

3 - I used the next official docs to run that :) I'
l'll try again in a few weeks to see when it's all more stable.

awesome! for now, i'll close this issue to keep things easier to navigate and prioritize other tasks, but we'll definitely keep your ideas in mind. cc @mohebifar
thanks again for taking the time to share them. keep 'em coming!
also, feel free to join our public slack community for more casual convos and brainstorming.


[WEB] new documentation format for wizard

Signed-off-by: Scott Mathis<EMAIL_ADDRESS>

@mathisscott Sizes section: M, L, XL boxes are green but should be purple like on the Modals page. That is unless you thought it needed to be different for some reason.

@reddolan
That was intentional. I went with a different color so that users would be less likely to confuse Wizards and Modals. I can make it a different color if you would prefer.

@mathisscott I don't remember seeing that green used elsewhere on the site. I think keeping it purple is fine. I am not sure if changing the color is going to help that much. And for consistency, we seem to be using that purple for callouts on the site

@reddolan
Cool. I'll change it back to purple before merging it in. Thanks!


Create an FAQ page

The page does not render, it only shows the raw text.
https://kwokyto.github.io/a-safe-space/faq.md

fixed


When will nodejs 20 be supported?

From https://mcr.microsoft.com/en-us/product/cbl-mariner/base/nodejs/about, I can see CBL only supports nodejs 16 and 18 for now. When will nodejs 20 be supported? This is the current active LTS version.

Hi @arisewanggithub, nodejs 20 will likely be supported in our Mariner 3.0 release, which is expected to be released next year.

Can we get an update on this, as node.js 18 has been out of active support for some time?

Node.JS 18 is in Maintenance mode and will be supported upstream until ~Apr 2025 -> https://nodejs.org/en/about/previous-releases
There is no plan to upgrade to  Node.JS 20 for Mariner 2.0 lifetime.
Our new major release 3.0 release will include Node.JS 20.


IFTTT for Automation?

What do you think about including IFTTT within the "Other" section?
This is because IFTTT can trigger rebuilds of a static site via webhooks when third party content changes on your site (such as an RSS feed, or a Twitter feed).
It could even be used as a basic CRON by using the date and time feature.

That's a great idea. Zapier could be included too.


Not accepting API key when passed in script, but works as environmental variable

Using python version 3.8.16
When I run the following code (I obfuscated the API key in code below):
`import mistapi
mist_api_key = "Fhsu................................................................ITNFbTS8O2N"
mist_api_url = 'api.mist.com'
apiSession = mistapi.APISession(apitoken=mist_api_key,host=mist_api_url,console_log_level=10)
apiSession.login()`
I get the following error:
`apirequest:mist_get: HTTP error occurred: 401 Client Error: Unauthorized for url: https://api.mist.com/api/v1/self
apirequest:mist_get: HTTP error description: {'detail': 'Authentication credentials were not provided.'}
apiresponse:init: response = <Response [401]>
-------------------------------- Authenticated ---------------------------------
Welcome  !
Traceback (most recent call last):
File "./mistAPI.py", line 13, in
print(mistapi.cli.select_site(apiSession,org_id=mist_org_id))
File "/usr/local/lib/python3.8/site-packages/mistapi/cli.py", line 47, in wrapper
return func(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/mistapi/cli.py", line 228, in select_site
for privilege in mist_session.privileges:
TypeError: 'Privileges' object is not iterable`
Like I said, if I set the API key as an ENV variable it works. So I know the key is good. Not sure what I am missing here to make this work. Thanks

I just fixed it in the latest version (0.41.10).
Let me know if it's good for you

I updated to the latest release and re-ran the test. I get a new error now with the same code posted above.
Traceback (most recent call last):   File "./mistAPI.py", line 4, in <module>     import mistapi   File "/usr/local/lib/python3.8/site-packages/mistapi/__init__.py", line 14, in <module>     from mistapi import api   File "/usr/local/lib/python3.8/site-packages/mistapi/api/__init__.py", line 13, in <module>     from mistapi.api import v1   File "/usr/local/lib/python3.8/site-packages/mistapi/api/v1/__init__.py", line 24, in <module>     from mistapi.api.v1 import sites   File "/usr/local/lib/python3.8/site-packages/mistapi/api/v1/sites/__init__.py", line 13, in <module>     from mistapi.api.v1.sites import webhooks   File "/usr/local/lib/python3.8/site-packages/mistapi/api/v1/sites/webhooks.py", line 17     def searchOrgWebhooksDeliveries(mist_session:_APISession, org_id:str, webhook_id:str, org_id:str=None, site_id:str=None, webhook_id:str=None, status_code:int=None, topic:str=None, start:int=None, end:int=None, duration:str="1d", limit:int=100) -> _APIResponse:     ^ SyntaxError: duplicate argument 'org_id' in function definition

Ok, that's another error due to the new API endpoints I added recently. This should have been fixed in 0.41.11.
Thanks

Confirmed working now in 0.41.11. Thank you.


BC23 NextMajor Pipeline warning AD0001 Unable to cast object of type 'Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ReferenceFieldSymbol' to type 'Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.FieldGroupSymbol'.

Please include the following with each issue:
1. Describe the bug
We receive the following in our NextMajor Pipelines.

warning AD0001: Analyzer 'Microsoft.Dynamics.Nav.AppSourceCop.Upgrade.RuleInvalidObsoleteTagsNotAllowed' threw an exception of type 'System.InvalidCastException' with message 'System.InvalidCastException: Unable to cast object of type 'Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ReferenceFieldSymbol' to type 'Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.FieldGroupSymbol'.
at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.SourceTableExtensionTypeSymbol.GetAddedFieldGroups() in D:\a_work\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\Source\SourceTableExtensionTypeSymbol.cs:line 181
at Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.TableExtensionTypeSymbol.Microsoft.Dynamics.Nav.CodeAnalysis.ITableExtensionTypeSymbol.get_AddedFieldGroups() in D:\a_work\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\Symbols\TableExtensionTypeSymbol.cs:line 58
at Microsoft.Dynamics.Nav.AppSourceCop.Upgrade.RuleInvalidObsoleteTagsNotAllowed.AnalyzeTableExtension(SymbolAnalysisContext ctx) in D:\a_work\1\s\source\Prod\Microsoft.Dynamics.Nav.AppSourceCop\Upgrade\RuleInvalidObsoleteTagsNotAllowed.cs:line 151
at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.<>c__DisplayClass49_2.b__0() in D:\a_work\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 658
at Microsoft.Dynamics.Nav.CodeAnalysis.Diagnostics.AnalyzerExecutor.ExecuteAndCatchIfThrows_NoLock(DiagnosticAnalyzer analyzer, Action analyze, Nullable`1 info) in D:\a_work\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis\DiagnosticAnalyzer\AnalyzerExecutor.cs:line 1086'

warning AD0001: Analyzer 'Microsoft.Dynamics.Nav.AppSourceCop.Upgrade.RuleInvalidObsoleteTagsNotAllowed' threw an exception of type 'System.InvalidCastException' with message 'System.InvalidCastException: Unable to cast object of type 'Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.ReferenceFieldSymbol' to type 'Microsoft.Dynamics.Nav.CodeAnalysis.Symbols.FieldGroupSymbol'.
Versions:

AL Language:  AL Compiler version <IP_ADDRESS>284

Hi @pri-kise,
It looks like it is trying to analyze Table Extensions for Obsolete fields. Please have a look if you can narrow down the issue to a AL snippet that reproduces the issue. Maybe you have a Field Group with the same name as some fields.

@thpeder we have no obsolete field in this PTE Customization.
And we only have one piece regarding fieldgroups
tableextension 50000 "PTE Item" extends Item
{
    fieldgroups
    {
        addlast(DropDown; "Description 2") { }
    }
}

+1 I found the reason of this yesterday.
The reason of this is because  Next Major Pipeline fails due to the use of AL Compiler version <IP_ADDRESS>44 that is using. If you download a version of AL in VS CODE for example v11.0.827766, and you have downloaded symbols of ver 23, the same error appears at the app.json in VS Code . It should be using v12.0.827887 instead, the version of AL that comes with 23.

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 23.0.11489.0 and VS Code Extension Version 12.0.834301.
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/


[CIVIS-9806] ENH update datascience-python base image to v8.1.0

As a follow-up of https://github.com/civisanalytics/datascience-python/pull/99, this pull request updates the civis-jupyter-python3 image to use the latest datascience-python base image v8.1.0.

[x] (For Civis employees only) Reference to a relevant ticket in the pull request title
[x] Changelog entry added to CHANGELOG.md at the repo's root level
[x] Description of change in the pull request description
[x] If applicable, unit tests have been added and/or updated
[x] The CircleCI builds have all passed

The changes look good to me but I am not sure which comments I should check in the original internal ticket.

I am not sure which comments I should check in the original internal ticket.

The comment is the one that's specifically about this civis-jupyter-python3 pull request (the other comment is about the datascience-python image / pull request).

LGTM


[core] Improve DX of importing Base UI components

Changed how components are exported. Previously we had two index files: index.ts containing unprefixed component names (such as Root, Input, Indicator) and index.barrel.ts with full names (SwitchRoot, CheckboxIndicator). The former was supposed to be used as import * as Foo from '@base_ui/react/Foo, while the latter import { FooRoot } from '@base_ui/react'.
Now we still have two index files per component, but only index.ts is meant to be imported. index.parts.ts aggregates and exports all parts of a component, while index.ts reexports them and names the exported namespace.
This makes all component parts accessible only through the component namespace:
import { Checkbox } from '@base_ui/react/Checkbox'; // or '@base_ui/react'
const CheckboxRoot = Checkbox.Root;

Closes #650

This still works with tree-shaking if you test a minimal Vite repo and build for production?

Yes, the resulting bundle does not contain the code of unused parts.


control signal output

Hi, I wonder whether the model you give now has the ability to output the control signal of both speed and course? If I set signal_type course speed, it will output a dimension error(it requires [1,768] and I give [2,768]). It just has one dimension, and what is this one dimension?

Sorry for late reply. The code would be update in a few days and looking forward to your attention


[$250] Error when copilot adds a new contact method

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

Version Number: 9.0.42-3
Reproducible in staging?: Y
Reproducible in production?: Y
Issue was found when executing this PR: https://github.com/Expensify/App/pull/49150
Issue reported by: Applause Internal Team
Action Performed:

Log in the App
Add a copilot to the user A
Login as copilot
Go to Account settings.
Click on the account switcher
Switch to user A account
Click Contact method.
Click New contact method.
Enter a new email address
Click Next

Expected Result:
The new email address is added as a new contact method.
Actual Result:
Copilot can not add new contact method. Error message "An unexpected error occurred when trying to add the new login.". RD in LHN-Profile, Profile window-Contact method, and LHP.
Workaround:
Unknown
Platforms:

[ ] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/9fbc47d6-034b-4dda-bd55-36af84193a60

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~021842646552595795235
Upwork Job ID:<PHONE_NUMBER>595795235
Last Price Increase: 2024-10-05
Automatic offers:

c3024 | Reviewer | 104335384

Issue OwnerCurrent Issue Owner: @c3024

We think that this bug might be related to #wave-collect - Release 1

@anmurali  FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors

Proposal
Please re-state the problem that we are trying to solve in this issue.
Error when copilot adds a new contact method
What is the root cause of that problem?

Copilot does not have enough authorities to add new contact methods.

What changes do you think we should make in order to solve the problem?
Option 1.

Disable New Contact Method button if current user is a copilot.

    const [account] = useOnyx(ONYXKEYS.ACCOUNT);
    const isActingAsDelegate = !!account?.delegatedAccess?.delegate ?? false;
    .
    .
    .
    <Button
        isDisabled = {isActingAsDelegate}
        large
        success
        text={translate('contacts.newContactMethod')}
        onPress={onNewContactMethodButtonPress}
        pressOnEnter
    />

https://github.com/Expensify/App/blob/3946b226d6367a719af5bc894546b95dc9b59fb4/src/pages/settings/Profile/Contacts/ContactMethodsPage.tsx#L125-L131

optionally we could add a short message above New Contact Method button to inform user that - copilot could not add new contact method.

Option 2.

Hide New Contact Method button if current user is copilot.

    const [account] = useOnyx(ONYXKEYS.ACCOUNT);
    const isActingAsDelegate = !!account?.delegatedAccess?.delegate ?? false;
    .
    .
    .
    { !isActingAsDelegate && <Button
        large
        success
        text={translate('contacts.newContactMethod')}
        onPress={onNewContactMethodButtonPress}
        pressOnEnter
    />}

https://github.com/Expensify/App/blob/3946b226d6367a719af5bc894546b95dc9b59fb4/src/pages/settings/Profile/Contacts/ContactMethodsPage.tsx#L125-L131

In addition to both of the above options - wrap NewContactMethodPage with AccessOrNotFoundWrapper to avoid copilot using deep link to access the page.

    <AccessOrNotFoundWrapper
        shouldBeBlocked = {isActingAsDelegate}
    >
        <ScreenWrapper
        .
        .
        </ScreenWrapper>
     </AccessOrNotFoundWrapper>

https://github.com/Expensify/App/blob/3946b226d6367a719af5bc894546b95dc9b59fb4/src/pages/settings/Profile/Contacts/NewContactMethodPage.tsx#L103-L152
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

Thanks for the proposal @ChavdaSachin.
@Expensify/design
Should we hide the "New Contact Method" button altogether or disable the button with a message on hover when a copilot accesses the account they are delegated to?

Hmm. We tend to not do disabling or hiding in this kind of situation, but I also think the error is enough. Keen to hear if @dannymcclain agrees.

I do agree. And if the problem is that the copilot isn't authorized to take that action, we already have a pattern for handling that:

I realize that the above is showing a restricted action because the copilot is set to Limited, but I think the same pattern can easily apply here if permissions are the issue. We could just update the copy of the modal to be something like:

Not so fast...
You don't have permission to take this action for {{user}} as a copilot.

I'm imagining this modal would pop up when the copilot clicks the New contact method button. Thoughts?

Updated Proposal
added @dannymcclain 's suggestion as alternate solution.

Love that @dannymcclain !

@c3024 - can you please review @ChavdaSachin revised proposal?

@ChavdaSachin’s alternative solution, as per design inputs, looks good to me. We can work on more specifics in the PR with reviews from the design team.
🎀 👀 🎀 C+ reviewed.

@Expensify/design
Could I have input on whether we want to change anything about 'Not So Fast....' prompt?
since the prompt has text '.....Limited Access copilot', and here for this problem we are gonna use this same prompt for Full Access Copilot as well. and there is no such different implementation for Full Access Copilot.

If it's going to be the exact same implementation across everything I think we should just change it everywhere to something like what I mentioned here:

Not so fast...
You don't have permission to take this action for {{user}} as a copilot.

@dylanexpensify @dubielzyk-expensify (and whoever else I should tag 😅) are y'all good with that? I see in the original we have limited access linked... Not sure where that goes, but if we need to maintain the link, would it still make sense to make the word copilot the link text?

This is the redirect link - https://help.expensify.com/expensify-classic/hubs/copilots-and-delegates
Link seems good enough for all kind of copilots. ✅

Oh nice. 👍

I'm okay with that change 👍

Could anyone add my following accounts to copilot beta....
<EMAIL_ADDRESS><EMAIL_ADDRESS>Thank you.

Hey @Julesssss I found the exact same issue,
When trying to issue a new Expensify card from copilot account - I got following response from BE
 response
{
    "code": 666,
    "jsonCode": 666,
    "type": "Expensify\\Libs\\Error\\ExpError",
    "UUID": "7D862FFF-854D-4AE0-B50B-6C8C96D37AB9",
    "message": "You must be a domain admin to create the virtual card.",
    "title": "",
    "data": [],
    "htmlMessage": "",
    "onyxData": [],
    "requestID": "8d2f62629dff8531-BOM"
}

Above response clearly suggests that copilot would not be able to issue the card.
So IMO we should implement exact same solution for issue new Expensify card flow,
additionally we need to check for company cards as well.
(I do not have test card data so I was unable to verify whether BE returns error for company card or not).
cc. @c3024

So IMO we should implement exact same solution for issue new Expensify card flow,
additionally we need to check for company cards as well.

Yeah I agree 👍

Added to beta. Here's the new issue.

(I do not have test card data so I was unable to verify whether BE returns error for company card or not).

We want to prevent this for company cards too.

Hey @c3024 and @ChavdaSachin can you please comment on that issue so I can assign you. Thanks

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@c3024] The PR that introduced the bug has been identified. Link to the PR: The frontend part was not implemented for this yet. So, no PR can be held responsible for this.
[x]  [@c3024] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: NA
[x]  [@c3024] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: No discussion was started because this could not have been identified earlier.
[x]  [@c3024] Determine if we should create a regression test for this bug. Yes
[x]  [@c3024] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.

Regression Test Proposal

Navigate to "Settings" > "Profile" as a copilot.
Click  on 'Contact methods'.
Click on 'New contact method' button.
Verify 'Not So Fast...' modal appears and 'New contact method' flow does not start.

Awaiting payment

@ChavdaSachin - can you please give me your Upwork profile? You are in Slack, yes?
@c3024 is paid.

I am not on slack yet.
https://www.upwork.com/freelancers/~016a0f0a12bce54a49
I have already applied for the job on upwork.

@anmurali can you get it done today?
That would be helpful.

Offer is here

Accepted

friendly bump ^ @anmurali


⚠ Elibs has degraded performance

In 552bb19, Elibs (https://elibs.unmer.ac.id) experienced degraded performance:

HTTP code: 200
Response time: 8840 ms

Resolved: Elibs performance has improved in 3215ce7.


add bottom tabs in Network layout

@FME849 can you explain why we need tokenList state? I thought we already have useTokens effect.


AMD translation for export * as ns is wrong

Bug Report
export * as x from './mod'
console.log(x)

🔎 Search Terms
AMD export
🕗 Version & Regression Information
I tried 5.0.4
⏯ Playground Link
Playground link with relevant code
💻 Code

define(["require", "exports", "./mod"], function (require, exports, x) {
    "use strict";
    Object.defineProperty(exports, "__esModule", { value: true });
    exports.x = void 0;
    exports.x = x;
    console.log(x);
});

But x is not a declared name in the module.

I don't understand what you're saying is wrong here. Which line of code should be what instead?

The original code
export * as x from './mod'
console.log(x)
//          ~

This x refers to the global variable x.
In the AMD translation,
define(["require", "exports", "./mod"], function (require, exports, x) {
    //                                                              ~
    "use strict";
    Object.defineProperty(exports, "__esModule", { value: true });
    exports.x = void 0;
    exports.x = x;
    //          ~
    console.log(x);
    //          ~
});

It refers to the ./mod


test: remove redundant page.close() calls

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[x] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

Thanks @mxschmitt ! This repo is actually generated from a template, so the change would need to be made here:
https://github.com/kjaymiller/cookiecutter-relecloud/blob/main/{{cookiecutter.__src_folder_name}}/src/tests/test_playwright.py
(And will then be propagated to quite a few repos - we use these same tests across Flask and Django as well)
I can make that change there to save you the work of another PR, if you'd like.
/CC @kjaymiller - our first PR on one of the generated repos!

Thanks @mxschmitt ! This repo is actually generated from a template, so the change would need to be made here: https://github.com/kjaymiller/cookiecutter-relecloud/blob/main/{{cookiecutter.__src_folder_name}}/src/tests/test_playwright.py (And will then be propagated to quite a few repos - we use these same tests across Flask and Django as well) I can make that change there to save you the work of another PR, if you'd like.
/CC @kjaymiller - our first PR on one of the generated repos!

yeah would be amazing if you could take over, thanks! Just saw this repo got mentioned on Twitter.

Change was made in the template generator repo and propagated to the templates, thanks!


[Feature] Default table widget should not have any scrollbars

Summary
As a user, When I drag and drop a table widget, I should not see any scrollbars by default.
Motivation
Showing a scrollbar on the default view can leave an untidy experience for the end-user.
Additional Context
The current default looks like this

We wish to reduce the column width to fit all the column in the default view
We wish to increase the table size so that there is no scroll in the header value.
In any case, the vertical scrollbar on the body should not occur as well.

The new default should look like this:

#4022 is a related issue and will be taken up with this issue

@vicky-primathon there are instances where the table shows many extra rows. Can you check to see if you can reproduce and find the issue.
@vivekverma2312 You have reproduced the issue before. Check to see if you find the issue. Do comment here in that case. We should solve scroll issues at once

@somangshu @vicky-primathon For old table in any application I am able to see extra rows and see a scrollbar.
https://www.loom.com/share/c9f158f896684fb7bbb9bba1034583ba

@somangshu can you share me any app with table widget having extra empty rows. I was not able to reproduce it at my end.

@vicky-primathon Please find the application to repro.
https://app.appsmith.com/applications/60ab3f3198f6c43a4b8550f7/pages/60ab3f3198f6c43a4b8550fc

@somangshu  parentRowSpace property of table widget in application shared has a value of 40 which is way bigger than usual value 10. This is causing pageSize to be calculated as 70 in example app. But since we have only 15 data rows we are showing remaining rows as empty. I am not aware of any recent migration that could have changed the parentRowSpace property value.

#4782 is related to this. The user points out that it could be because of the new grid size. @marks0351 can you provide some insight here?


php artisan db:seed --class=RolesTableSeeder

[Symfony\Component\Debug\Exception\FatalThrowableError]
Type error: Argument 1 passed to Zizaco\Entrust\Middleware\EntrustRole::__construct() must be
an instance of Illuminate\Contracts\Auth\Guard, none given, called in C:\xampp\htdocs\myAuth\d
atabase\seeds\RolesTableSeeder.php on line 13

i have finally got the solution

what is the solution?


Update to cqm-models 4.1.0 and cql-execution 2.4.1

Pull requests into cqm-execution require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[ ] Internal ticket for this PR:
[ ] Internal ticket links to this PR
[x] Code diff has been done and been reviewed
[ ] Tests are included and test edge cases
[x] Tests have been run locally and pass

Reviewer 1:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

Reviewer 2:
Name:

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

@adongare This now points to the updated 4.1.0 cqm-models version and 2.4.1 cql-execution.


Documenter via GithubActions fails

I just created my first project with PkgTemplates.jl, but it failed to create the Documentation.
Here is my template which I used
function template(;dir="~/.julia/dev")
  Template(
    user = "schlichtanders",
    authors = "...",
    dir = dir,
    plugins = [
      Git(name = "schlichtanders",
      	  email = "...",
          ssh = true),
      GitHubActions(),
      Documenter{GitHubActions}(),
      Codecov(),
    ]
  )
end

However if I commit and look into the github actions, the documentation creation actually failed with the following notice
Run julia --project=docs -e '
  julia --project=docs -e '
    using Pkg
    Pkg.develop(PackageSpec(path=pwd()))
    Pkg.instantiate()'
  shell: /bin/bash -e {0}
Path `/home/runner/work/Monadic.jl/Monadic.jl` exists and looks like the correct package. Using existing path.
ERROR: refusing to add package `Monadic [4a6f0533]`: package `Monadic = "0dc831cb-e86b-42f6-a94c-226003a855d9"` already exists as a direct dependency
Stacktrace:
 [1] pkgerror(::String, ::Vararg{String,N} where N) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/Types.jl:53
 [2] assert_can_add(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/Operations.jl:1016
 [3] develop(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}, ::Array{Base.UUID,1}; preserve::Pkg.Types.PreserveLevel, platform::Pkg.BinaryPlatforms.Linux) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/Operations.jl:1101
 [4] develop(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}; shared::Bool, preserve::Pkg.Types.PreserveLevel, platform::Pkg.BinaryPlatforms.Linux, kwargs::Base.Iterators.Pairs{Union{},Union{},Tuple{},NamedTuple{(),Tuple{}}}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/API.jl:102
 [5] develop(::Pkg.Types.Context, ::Array{Pkg.Types.PackageSpec,1}) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/API.jl:63
 [6] #develop#15 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/API.jl:60 [inlined]
 [7] develop at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/API.jl:60 [inlined]
 [8] #develop#11 at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/API.jl:57 [inlined]
 [9] develop(::Pkg.Types.PackageSpec) at /buildworker/worker/package_linux64/build/usr/share/julia/stdlib/v1.4/Pkg/src/API.jl:57
 [10] top-level scope at none:3
##[error]Process completed with exit code 1.

Investigating it further, it pops up that

docs/Project.toml already added my package "Monadic.jl" as a dependency
the github action includes the call to Pkg.develop(PackageSpec(path=pwd()), which tries to add it too (but fails).

So one of them seems to be too much (but which?).

using [14b8a8f1] PkgTemplates v0.7.6
julia> versioninfo()
Julia Version 1.4.1
Commit 381693d3df* (2020-04-14 17:20 UTC)
Platform Info:
  OS: macOS (x86_64-apple-darwin18.7.0)
  CPU: Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-8.0.1 (ORCJIT, skylake)
Environment:
  JULIA_NUM_THREADS = 8

I would guess the Project.toml entry is too much, as it may refer to a wrong Package version (i.e. one already registered somewhere, but not the one in dev mode which should be tested)

The problem here is that Monadic's UUID in Project.toml was different from the one in docs/Project.toml. Since you didn't create the package with PkgTemplates, I'm guessing you recently created a new package with PkgTemplates and then copied the generated files into your existing package? That's why the UUIDs don't match up.

perfekt answer! yes, that is exactly my use case!! thank you very much for thinking ahead!
I'll try changing the uuid tomorrow, will let you know

Np! Being able to update existing packages is a pretty common request, so I'll have to add real support for that at some point.

I fully agree - today I planned to upgrade about 7 packages ;D
just added the line in docs/Project.toml again, this time with the correct UUID, and it worked indeed. Thank you very much for your help.


Can't apply kyverno policy

I'm encountering an issue when trying to deploy a plugin on an EKS cluster using Helm. The policy provided within the samples folder seems to be incompatible with the chart deployment. When I attempt to apply the policy with kubectl apply -f kyverno-policy.yaml, I receive the following error:
Error from server: error when creating "../kyvernov2/templates/kyverno-policy.yaml": admission webhook "validate-policy.kyverno.svc" denied the request: policy contains invalid variables: variable substitution failed for rule call-aws-signer-extension: variable images must match regex "request\.|element|elementIndex|@|images\.|image\.|([a-z_0-9]+\()[^{}]" or patterns [tlscerts* response*]

Current Configuration:
The plugin is deployed via kyverno-notation-aws Helm Chart.
Kyverno is deployed through the kyverno Helm Chart.
Policy Configuration:
The policy I am applying is the kyverno-policy.yaml provided in the samples folder:
apiVersion: kyverno.io/v1
kind: ClusterPolicy
metadata:
  name: check-images
spec:
  validationFailureAction: Enforce
  failurePolicy: Fail
  webhookTimeoutSeconds: 30
  schemaValidation: false
  rules:
  - name: call-aws-signer-extension
    match:
      any:
      - resources:
          namespaces:
          - test-notation
          kinds:
          - Pod
          operations:
            - CREATE
            - UPDATE
    context:
    - name: tlscerts
      apiCall:
        urlPath: "/api/v1/namespaces/kyverno-notation-aws/secrets/svc.kyverno-notation-aws.svc.tls-pair"
        jmesPath: "base64_decode( data.\"tls.crt\" )"
    - name: response
      apiCall:
        method: POST
        data:
        - key: images
          value: "{{images}}"
        - key: trustPolicy
          value: "tp-{{request.namespace}}"
        - key: attestations
          value:
          - imageReference: "*"
            type:
            - name: sbom/example
              conditions:
                all:
                - key: \{{creationInfo.licenseListVersion}}
                  operator: Equals
                  value: "3.17"
                  message: invalid license version
        service:
          url: https://svc.kyverno-notation-aws/checkimages
          caBundle: '{{ tlscerts }}'
    mutate:
      foreach:
      - list: "response.results"
        patchesJson6902: |-
            - path: {{ element.path }}
              op: replace
              value: {{ element.image }}

Additional Information:
The policy deployment works without a problem when I deploy both kyverno and the plugin manually, following the instructions provided here.
However, it fails when both are deployed via Helm. Is this a version issue or an issue with the policy?

@mihirgosai5 I had the same issue...spent a lot of time for troubleshooting but thanks to your notes about installing kyverno from helm I upgraded my kyverno charts to 3.1.0-beta.4 (https://artifacthub.io/packages/helm/kyverno/kyverno) and issues with "images" variable gone

@igorgolm Hey, thanks for reaching out. I fixed the issue same way you did by changing the helm chart version to beta. It seems stable version of Kyverno (v1.10.3) does not support this kind of policies while the latest beta version does.

We need to update the docs to clarify that Kyverno 1.11 is required for the extension!


[NODE][REFACTOR] Refactor reflection system in node.

Removed the old Node, Node is now just an alias of runtime::Object
Introduce ReflectionVTable, a new columnar dispatcher to support reflection

This allows us to remove vtable from most node objects
The VisitAttrs are registered via TVM_RESGITER_NODE_TYPE,
they are no longer virtual.

Consolidated serialization and reflection features into node.

Cross posting from RFC #4116
Node System Refactor Proposal
This proposal is part of the unified object protocol RFC. The node refers to the base object structure for constructing AST/IR nodes as well as utilities manipulating them in the TVM stack.
Historically, the node folder contains a implementation of a smart pointer(NodePtr), a base object(Node) and a base reference type(NodeRef). On top of these data structures, we provide runtime checking and conversion. These features are now replaced by runtime::Object which allows further reuse by other runtime object types.
Besides the basic features provided by runtime::Object. We also provided additional features for AST/IR nodes. The important ones include:

Reflection: being able to quickly access any field of the node into frontends(e.g. python).
Serialization: any node objects can be serialized to json.
Pretty printing: we can print out most of the node objects.

On one side, we could just put support for these features into runtime(e.g. make them part of Object). However, we need to keep in mind that the runtime needs to be minimum. Additionally, these features are mainly for building compiler infra.
Some of these features are previously scattered in the project, outside the node directory.
We propose to consolidate them into a centralized location -- the node folder.
These features are implemented in a dialect independent manner and serves as base infra for compiler.
Remove vtable from Base Node
The current implementation of node reflection system requires child classes to override  a virtual function VisitAttrs. As mentioned in the unified object protocol proposal, one of our design goal is to remove vtable from common AST/IR Node classes. By doing so, these node classes can be directly exposed to other languages via C ABI -- which allows direct access to the fields of the node.
We offer an alternative solution to the c++ vtable by a columnar dispatch table indexed by the type index of the object. The data structure, ReflectionVTable, is a global singleton that keeps record of the key reflection-related functions for each object type. These functions are registered by TVM_REGISTER_NODE_TYPE. Note that we already use a similar data structure for node creation, we propose to unify them together. This change does requires a refactor to remove the final keyword from VisitAttrs functions(as they are no longer virtual).
We do not, however, forbid use of virtual functions for all node sub-classes. We only aim to expose the core IR/AST nodes for now. The sub-classes with virtual functions will still work fine as ususal as long as we do not want to expose them via ABI.

cc @icemelon9 @jroesch @zhiics @junrushao1994


Fix typo

Fixes #45
Fixed typo: 'redundent' -> 'redundant'

@mzfr sorry to nitpick on you... but could you add a DCO signed-off-by to your commit?

Merging after all. A one character change is not material


camera.containsGPSInMetadata = containsGPSInMetadata

version:4.1.0
camera.containsGPSInMetadata = containsGPSInMetadata

Error:(26, 9) value of type 'DKCamera' has no member 'containsGPSInMetadata'

Could you check your Podfile.lock file about using DKCamera version?
It should be 1.6.4
  - DKCamera (1.6.4)

@zhangao0086 I'm getting the same error too when building the Example project. The version I get for DKCamera is actually 1.6.2 as reported in the Podfile.lock
I've already ran pod install before running the project.

A workaround would be to force the 1.6.4 version in your Podfile, like this:
pod 'DKCamera', :git => 'https://github.com/zhangao0086/DKCamera.git', :commit => '1227253b029dc1271d278c321141bf8f92212955'
This commit id leads to the required version.

This issue is intermittent for me. I'm not seeing it anymore.

Well, I'm not sure what is going on here, but when you take a look at pod search DKCamera:
`-> DKCamera (1.6.2)
A light weight & simple & easy camera for iOS by Swift.
pod 'DKCamera', '~> 1.6.2'

Homepage: https://github.com/zhangao0086/DKCamera
Source:   https://github.com/zhangao0086/DKCamera.git
Versions: 1.6.2, 1.6.1, 1.6.0, 1.5.3, 1.5.2, 1.5.1, 1.5.0, 1.4.0, 1.3.4, 1.3.3, 1.3.2, 1.3.1, 1.2.11, 1.2.9, 1.2.8, 1.2.7,
1.2.6, 1.2.5, 1.2.3, 1.2.2, 1.2.1, 1.2.0, 1.1.0, 1.0.4, 1.0.3, 1.0.2, 1.0.0 [master repo]`
I may be wrong, but version 1.6.2 is the newest visible version to the cocoapods, so I don't know how this can work.

@lawicko Please run pod update

Closing this thread...


[BUG] TypeError: can't access property "isCE", currentRenderingInstance is null

<template>
  <Grid :length="orderList.length" :page-provider="pageItems" :page-size="12">
    <template #probe>
      <Order :order="orderList[0]" />
    </template>
    <template #default="{ item, style, index }">

{{ item }} {{ index }}

    </template>
    <template #placeholder="{ index, style }">

Placeholder {{ index }}

    </template>
  </Grid>
</template>

And i getting an error:
Uncaught (in promise) TypeError: can't access property "isCE", currentRenderingInstance is null
    renderSlot runtime-core.esm-bundler.js:5799
    _sfc_render vue-virtual-scroll-grid.js:6755
    renderComponentRoot runtime-core.esm-bundler.js:424
    componentUpdateFn runtime-core.esm-bundler.js:4189
    run reactivity.esm-bundler.js:160
    setupRenderEffect runtime-core.esm-bundler.js:4315
    mountComponent runtime-core.esm-bundler.js:4098
    processComponent runtime-core.esm-bundler.js:4056
    patch runtime-core.esm-bundler.js:3651
    mountChildren runtime-core.esm-bundler.js:3847
    mountElement runtime-core.esm-bundler.js:3756
    processElement runtime-core.esm-bundler.js:3728
    patch runtime-core.esm-bundler.js:3648
    mountChildren runtime-core.esm-bundler.js:3847
    mountElement runtime-core.esm-bundler.js:3756
    processElement runtime-core.esm-bundler.js:3728
    patch runtime-core.esm-bundler.js:3648
    componentUpdateFn runtime-core.esm-bundler.js:4196
    run reactivity.esm-bundler.js:160
    setupRenderEffect runtime-core.esm-bundler.js:4315
    mountComponent runtime-core.esm-bundler.js:4098
    processComponent runtime-core.esm-bundler.js:4056
    patch runtime-core.esm-bundler.js:3651
    componentUpdateFn runtime-core.esm-bundler.js:4266
    run reactivity.esm-bundler.js:160
    callWithErrorHandling runtime-core.esm-bundler.js:6656
    flushJobs runtime-core.esm-bundler.js:6895

Node: 16.9.1
Vue: 3.2.12
vue-virtual-scroll-grid: 1.2.1

I managed to convert your code snippet to a working demo at https://codesandbox.io/s/vue-virtual-scroll-grid-issue-12-zzvdr?file=/App.vue
However, I couldn't replicate the issue in you described.
I notice your code snippet has not styles. Presumably you omit it for simplicity, but please note that as an UI component, vue-virtual-scroll-grid heavily relies on CSS, perticully the CSS grid feature. Without proper style set on the container and item elements, it may behave weirdly.
Also note that you gotta export default your component instead of return it.

I managed to convert your code snippet to a working demo at https://codesandbox.io/s/vue-virtual-scroll-grid-issue-12-zzvdr?file=/App.vue
However, I couldn't replicate the issue in you described.
I notice your code snippet has not styles. Presumably you omit it for simplicity, but please note that as an UI component, vue-virtual-scroll-grid heavily relies on CSS, perticully the CSS grid feature. Without proper style set on the container and item elements, it may behave weirdly.
Also note that you gotta export default your component instead of return it.

return is mistake. i use export default

Thanks. I cant simulate my error. I found another variant without using scrollbar.


🐛 Bug ➾ The compile and Originate commands are failing when invokded from command pallet

🆘 What happened?
The CLI has change the implementation of these commands to require the file name. Previously it was optional.
🪵 Relevant log output
No response
🐘 How impactful is this bug?
No response
⏱ Prevalance
No response
💻 Operating System
No response
🕸 System Architecture
No response
🌮 Taqueria Version
No response
🌿 Node.js Version
No response
☎ Contact Details
No response
Code of Conduct

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

Is this not resolved with your new PR @AlirezaHaghshenas ?

This should have been closed automatically


Example User Story_Test

User Story
As a translator I would like to use an Android tablet to source from a global langauge, and record in to a target language
Definition of Done
Using any tablet running with Kit Kat (4.4)

Awesome Sauce with extra MSG, BUDDY! YEEE-HAW!
On Tue, Aug 25, 2015 at 2:24 PM, Redmayspecial<EMAIL_ADDRESS>wrote:

User Story
As a translator I would like to use an Android tablet to source from a
global langauge, and record in to a target language
Definition of Done
Using any tablet running with Kit Kat (4.4)
—
Reply to this email directly or view it on GitHub
https://github.com/WycliffeAssociates/5WoC/issues/15.


how to ignore less file's image url path

Module not found: Error: Can't resolve 'xxxxxxx.png'

default convert image to base64; I don't think so


Implement Heap Sort (Python)

Implement Heap Sort in Python
We need a simple heap sort algorithm written in Python for our repository.
This issue is great for beginners looking to contribute in open source. If you wish to fix this issue please comment that you are working on it. Please read the readme.md and contributing.md files to learn how to contribute.
If you wish to contribute another algorithm or the same algorithm in a different language, please see if it hasn't been implemented and issue a new request if no issue has been made.
If you are going to work on the issue yourself, make sure you comment on the issue to let others know.

I would like to work on this!...

@punkyoon I will leave it to you then. Thank you


Added encoding for toString() method

Need to specify the encoding as HTML to fix #398
(See http://xmlsoft.org/encoding.html#Default)
This PR adds the ability to provide a encoding option to toString().

I've updated this change to the latest code from master but not sure why its failing on OS X with Node > 7...!

Thanks!


"php.validate.executablePath": "c:/php/php.exe"

I have tried everything to get the php 8 and then the stable 7 version including xaamp installations and this pathway page and suggestions DO NOT WORK!  I just want to edit a php script and this is now day 4 trying.  Please help me!

Can you give some more details about exactly what you are trying? The builtin PHP support is very simple, you may want to install an extension for better intellisense.

Hello and thank you for replying to this huge frustration of mine.
The objective is to get php working in Visual Studio.  Actually, it is IntelliSense and another extension that informs me that I need to go to settings in a JSON file to correct the pathway.
It seems simple when reading the Lint screen in VS, but nothing has worked so far.
What have I tried to do?  I have downloaded and placed php on C: directly and changed the pathway in windows to the same.  Then, I did the same with xampp as c: xampp/php and tried c:xampp/php/php.  Then, I changed the php development file to a php ini file after viewing a youtube video on installations etc.,
That is why I needed to reach out, as I am completely miffed!
Earle

From: Rob Lourens @.>
Sent: March 16, 2021 5:17 PM
To: microsoft/vscode @.>
Cc: ebprince-tech @.>; Author @.>
Subject: Re: [microsoft/vscode] "php.validate.executablePath": "c:/php/php.exe" (#119029)
Can you give some more details about exactly what you are trying? The builtin PHP support is very simple, you may want to install an extension for better intellisense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/119029#issuecomment-800698708, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOPQH7Z4OZLHKD7MVLDILYTTD7YIVANCNFSM4ZHPFGYQ.

Hi, here are attachments for the json file that the extension tells me to correct!

From: Rob Lourens @.>
Sent: March 16, 2021 5:17 PM
To: microsoft/vscode @.>
Cc: ebprince-tech @.>; Author @.>
Subject: Re: [microsoft/vscode] "php.validate.executablePath": "c:/php/php.exe" (#119029)
Can you give some more details about exactly what you are trying? The builtin PHP support is very simple, you may want to install an extension for better intellisense.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/119029#issuecomment-800698708, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOPQH7Z4OZLHKD7MVLDILYTTD7YIVANCNFSM4ZHPFGYQ.

There are no attachments, they are not sent with email. But if you are trying to use a PHP extension, then please file this issue on the extension's repo.


Create branch for every Minecraft's minor versions for reference

Is your feature request related to a problem? Please describe.
People trying 1.19.70 preview scripts on stable 1.19.60, leads to this result:

Cause of this error is stable uses
player.velocity

While preview uses
player.getVelocity()

Not creating branch for each versions, instead we now use tags!
https://github.com/JaylyDev/ScriptAPI/tags


feat(CSI-245): allow specifying client group for NFS

TL;DR
Added support for specifying a custom NFS client group name in the WekaFS CSI plugin.
What changed?

Introduced a new clientGroupName parameter in the plugin configuration.
Updated the controller and node server templates to include the new clientGroupName parameter.
Modified the EnsureCsiPluginNfsClientGroup function to use the specified client group name or default to "WekaCSIPluginClients".
Updated related functions to pass and use the clientGroupName parameter.

How to test?

Deploy the WekaFS CSI plugin with a custom client group name:pluginConfig:
  mountProtocol:
    clientGroupName: "CustomNFSClientGroup"

Create a PersistentVolumeClaim and a Pod that uses it.
Verify that the NFS client group with the specified name is created and used for managing NFS permissions.
Check if the volume is successfully mounted and accessible in the Pod.

Why make this change?
This change allows users to specify an existing NFS client group or create a custom one for the WekaFS CSI plugin. It provides more flexibility in NFS configuration and permissions management, especially in environments where specific naming conventions or pre-existing client groups need to be used.

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#317
#316  👈
#314
#313
#312
#311
#315
#299
#310
dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @sergeyberezansky and the rest of your teammates on  Graphite

Merge activity

Sep 12, 6:10 AM EDT: @sergeyberezansky started a stack merge that includes this pull request via Graphite.


osal.docker v 1.0.0

branch: development_docker

features

good sal for docker for compose, build, basics run, ...

requirements

good examples
should be super easy for someone to operate docker for all basic workflows

to resolve
see also

https://github.com/freeflowuniverse/crystallib/issues/210
https://github.com/freeflowuniverse/crystallib/issues/206

We tried to use as many recipes by adding three examples :

TF Dashboard
Development environment that contains [ zinit, ssh, vim ]
Presearch Compose

if you have any specific example please tell us.


Showing contact app icon instead of dialer app icon

link the miui dialer app icon with dialer icon currently its showing contact app icon instead of dialer app icon

can you tell me the package name please

(since above didn't work) Duplicate of #462

Duplicate of #462


My unique id for widgets

Hi,
Can you modify widget.component.ts to add "widgetId" input and after modify WidgetConfig constructor with condition  this.id = generateUID if my id is null?
Regards

widgetId is actually an internal property and hence not exposed outside. Whats your use case and why would you need that to be settable from outside?


Adding close to PinotFS to support different fs reqs

Adding a close method inside PinotFS and making the abstract class closeable in case certain filesystems need to do certain operations inside close.
Also adding close to minion, server, controller shutdown

Codecov Report

Merging #3300 into master will increase coverage by 0.04%.
The diff coverage is 90%.

@@             Coverage Diff              @@
##             master    #3300      +/-   ##
============================================
+ Coverage     70.79%   70.83%   +0.04%
  Complexity        4        4
============================================
  Files           983      983
  Lines         45378    45401      +23
  Branches       6097     6100       +3
============================================
+ Hits          32124    32162      +38
+ Misses        11148    11139       -9
+ Partials       2106     2100       -6

Impacted Files
Coverage Δ
Complexity Δ

.../com/linkedin/pinot/filesystem/PinotFSFactory.java
82.75% <100%> (+0.61%)
0 <0> (ø)
:arrow_down:

...m/linkedin/pinot/controller/ControllerStarter.java
63.58% <100%> (+1.01%)
0 <0> (ø)
:arrow_down:

...pinot/server/starter/helix/HelixServerStarter.java
77.12% <100%> (+3.23%)
0 <0> (ø)
:arrow_down:

...in/java/com/linkedin/pinot/filesystem/PinotFS.java
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

.../java/com/linkedin/pinot/minion/MinionStarter.java
85.33% <75%> (-1.24%)
0 <0> (ø)

...a/manager/realtime/RealtimeSegmentDataManager.java
50% <0%> (-25%)
0% <0%> (ø)

...impl/dictionary/DoubleOnHeapMutableDictionary.java
68.88% <0%> (-13.34%)
0% <0%> (ø)

...kedin/pinot/core/util/SortedRangeIntersection.java
83.82% <0%> (-7.36%)
0% <0%> (ø)

...not/broker/broker/helix/ClusterChangeMediator.java
63.33% <0%> (-3.34%)
0% <0%> (ø)

.../com/linkedin/pinot/common/data/TimeFieldSpec.java
91.35% <0%> (-1.24%)
0% <0%> (ø)

... and 12 more

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 0d3be35...4863e34. Read the comment docs.


Fetch supporters with Open Collective GraphQL API

fetch supporters with Open Collective GraphQL API

likely more reliable and future proof, ESLint and Babel recently migrated to it for similar case:

https://github.com/eslint/eslint.github.io/pull/564
https://github.com/babel/website/pull/2031

refactor path computation with absoluteFilename
stop relying on id as it's not exposed anymore
order supporters by totalDonations, pretty JSON format for easy troubleshooting

Expected behavior changes:

the data is not computed the same, so it can be there is small differences with the current data. before merging we need to assess if the result is what's expected
backers without an avatar get a default one with their initials

Todo:

[x] support firstDonation
[x] de-duplication (due to supporters with multiple orders)
[x] pagination (limited to 1000 now)

Well, it works as expected i would say, code looks good too.
But +80 −12, is that what future is 😅
I'll leave it to the rest of maintainers

It is fine

I don't see the request in the preview version, but the supporters list is there, maybe cache?

We fetch them during build time, this is only run on node

Thanks, well structured PR too!

Thank you for merging!
@EugeneHlushko Sorry, GraphQL is a bit more verbose but I think this is worth it!
Don't hesitate if you have any feedback and feature request for the Open Collective API.


Error not handled properly in offline video player example fetch call?

@darpankumar commented on Sat Mar 07 2020
In this demo, the error is not handled properly whenever there is an error in the fetch call i.e 404 video is not available then also it says video ready to play PFA the screenshot in which the api return 404 but it says the video is ready to play. I know it is the default behaviour of fetch API it calls reject only if the service is not available but we need to handle this scenario in our code.
URl for the demo file
https://github.com/mdn/dom-examples/blob/master/abort-api/index.html

@darpankumar I've moved this to our sprints repo, where we track MDN bug work.

@chrisdavidmills  I have fixed this, if you want i can raise a pull request for merge

@darpankumar ok, great! Please do ;-)

@chrisdavidmills I have raised the pull request can you please look into this.
https://github.com/mdn/dom-examples/pull/54

Closing, as PR has been reviewed and merged. Thanks!


Use a catalogd-defined catalog to install an Operator

This issue should be closed when a demo recording is posted to the #olm-dev kubernetes slack channel that follows the below script:
Demo Script:

Install operator-controller from the main branch or its most recently tagged release using operator-controller's standard install script and manifest.
Create a Catalog object referencing quay.io/operatorhubio/catalog:latest
Show that the catalog status reflects that it was successfully unpacked.
Show that the catalogd metadata api reports objects for all packages, channels, and bundles in the catalog.
Create an Operator object referencing package strimzi-kafka-operator.
Show that aBundleDeployment is created to reflect a bundle image reference with the highest semver bundle defined in the package (as of 4/5/23, that version is 0.34.0):  quay.io/operatorhubio/strimzi-kafka-operator@sha256:42a3dce711492fae22f2d919299a0594f152396f6c2fef65ffc47226ba9c786e
Delete the Operator and Catalog objects.
Show that no catalog metadata or bundle deployment objects remain.

Related Issues:

[ ] https://github.com/operator-framework/operator-controller/pull/141

@anik120 Demoed this integration in yesterday's OLM working group meeting. Watch it here: https://youtu.be/RR88HeoCyfE?t=2322
Closing as complete.


Simplified Chinese Localization for Japanese Era Change

It's sad to see articles in Globalization section stay untranslated.
I came across this article regarding the upcoming Japanese Era change on May 1. Since even machine translation isn't available, I thought I'd do a (Simplified Chinese)[https://gist.github.com/VaslD/a31e60de4d1c8c80ab400e82c89bf273] translation. I made sure all translated menus/controls match what will be shown on a computer with Simplified Chinese UI.
I didn't find the zh-CN localization repo for UWP so the issue was created here.

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

ID: 678c458d-6ad5-f85d-bd56-9abf8760973b
Version Independent ID: 839e1cfc-82f2-0be2-efc3-62cdb58cdfac
Content: Prepare your application for the Japanese era change - Windows UWP applications
Content Source: windows-apps-src/design/globalizing/japanese-era-change.md
Product: uwp
GitHub Login: @Karl-Bridge-Microsoft
Microsoft Alias: kbridge

Hi @VaslD, thank you for pointing this out, and for your work translating the document. This is very strange, as we actually got this localized into 10 different languages (including zh-cn) but for some reason, it's not showing up. I'll follow up and get back to you.

Hi @VaslD, we've published the document's localized versions, including zh-cn, so please take a look. Thanks!


Unable to get Site ID with Site search in graph API

Describe the bug
Unable to fetch Site ID from Site sreach in Graph API since three hours. It is happening since three hours.
If you are deploying any changes to graph api, please let us know through mails. It is annoying when a working functionality suddenly stops working.
I already have consented all required permissions, yet it does not return any value. This was working fine till last three hours
To Reproduce
Steps to reproduce the behavior:

Go to 'graph api explorer'
Search for a sharepoint site

Expected behavior
A json with Site ID information should be returned.
Screenshots

What is the issue?
Our client applications have stopped working because of this issue.
I need answer as soon as possible.

Hi @Manikandhar,
Could you confirm if you are still experiencing this issue?

Hi @ElinorW ,
I am getting partial data. I have three site collections, but Graph API is returning only one site collection.
Even with individual name search, am not getting any information.
Why is this happening? Are there any changes happening on Microsoft end?
This behavior of API is really annoying as our logic purely depends on fetching information from Graph API (site collection id) based on site collection name, as you can see in the screen shot provided above.
Please let us know what is the issue? and when can it be resolved.

Hi @Manikandhar,
This must be a problem with the API. I'm not sure if something changed or why you are only getting partial data.
A different team works on the Sharepoint API. Please post this issue here https://learn.microsoft.com/en-us/answers/tags/161/ms-graph then the appropriate team can reach out and help you


19364  - Fix calculation of the hint's position. The problem was that the....

... orientationDidChangeNotification was called before the views did finish layout correctly. In landscape mode, the position was calculated based on the portrait mode bounds of the superview and vice versa

Thank you @FannyHogberg - I’ll take a look when I’m back from my trip.

I realized this fix didnt work inside the Bookbeat app, only in your test demo project. I will create a new PR with the new fix


update *-weekly pipelines to use same variables groups as *-tests

Some of the weekly pipeline builds are linked to the resource provisioner variable group, but need additional service-specific variable groups to pass.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Data Factory:0.24617036,Tables:0.24540246,App Services:0.13238305'
Label prediction was below confidence level 0.6 for Model:CategoryLabels: 'Mgmt:0.5068275,Client:0.30012435,Service:0.18402131'


remove 0.10, it's dead

The other updates aren't really necessary since it's the major we care about (the abi has changed) but just syncing with what's out there at this point in time

@juliangruber I want to release https://github.com/mafintosh/prebuild/pull/135 today. Can we merge this as well?

+1 from me, however this is a breaking change so maybe a +1 from @mafintosh would be great as well

Agree. Well then I can leave it for now and release 4.5.0.

I'd like to keep this in there as long as 0.10 is default on debian


Do not remove property after zero

I got this code with a grid value:
.class {
      grid-template-columns: 1fr 0fr 0;
    }

and when I fix the code with csscomb I get this:
.class {
      grid-template-columns: 1fr 0 0;
    }

csscomb deletes the fr from my value, how can I prevent this?

In your .csscomb.json set this option:
{
    "unitless-zero": false
}

Pretty smooth for a workaround but I think it shouldnt remove it no matter false or true
Sent with GitHawk

For me, its better to have option instead of default behavior.


Iopaint batch processing could auto paint??

many images need remove watermark ,those images's watermark in lower right corner .
can I auto remove watermark? thanks

If the watermark remains fixed in its position, you may prepare a mask image and employ it to perform inpainting on all the images.
You can activate the option "Download Mask" in IOPaint. Once activated, the mask will be downloaded along with the inpainted results.

https://www.iopaint.com/batch_process


Pagination bar is scrolling in mobile view

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
https://github.com/CircuitVerse/CircuitVerse/assets/99007201/6dd494ef-2fd9-48b2-9323-894b4480662a
Pagination bar is scrolling in mobile view
Steps To Reproduce

Go to https://circuitverse.org/ in android, or, open in mobile view
Scroll down to the end of the home page
See the scrolling pagination bar

Expected Behavior
Pagination bar should shrink with shrinking screen size.
The numbers shown in pagination bar should also accordingly.
Screenshots
https://github.com/CircuitVerse/CircuitVerse/assets/99007201/ef627563-c4dc-4d1e-83bf-d761260b64f1
Device Information [optional]
- OS: Android 11
- Browser: Chrome
- version: 120.0.6099.44

Additional context
No response
Are you working on this issue?
Yes

@sa-paul bro but it can be a feature too
because it is much easy to go 5 or 6  page next by just scrolling
or it can be a feature not a bug

can I work on this issue?

Issue verified.
For mobile devices, we can reduce the pages button.

@syntax-bot Yes, I am continuously working on it and it has also come to an end. Just merging it out.


[Constraint solver] Update type map code for recursion through salvag…

…e().
When we track which expressions we're already in the middle of type
checking, we need to ensure that we also track the constraint system
which has the types for that expression, and then transfer those types
into our current expression so that we do not fail to look them up.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please test source compatibility


[ts] 'privateFunction' is declared but its value is never read.

Got here and found an issue similar to: https://github.com/Microsoft/vscode/issues/51814 which was marked as not reproducible.
Verified that the insiders build has the same issue as the current release. So I used it to test it without any external extensions.

VSCode Version: 1.25.0-insider
OS Version: Windows 10 Pro - Version 1803 - Build 17134.112

Steps to Reproduce:
Using latest TypeScript npm package, create the typescript class below:
export class Test {
    private _someVar: boolean = false; //[ts] '_someVar' is declared but its value is never read.

    public somePublicFunction = function() {
        var lib = new ExternalLibrary();
        this._somePrivateFunction();
    }

    private _somePrivateFunction = function() { //[ts] '_somePrivateFunction' is declared but its value is never read.
        if (this._someVar) { //_someVar is read here.
            console.log(':/');
        }
    }
}

Does this issue occur when all extensions are disabled?: Yes
This happens only when we declare class functions as anonymous. Although not a best coding practice, VSCode is still flagging those variables or functions incorrectly.

This issue was moved to Microsoft/TypeScript#25232


The device is disabled by Config entry.

I've tried to setup the integration, but the device seems disabled. Any idea what's wrong?

Reinstalled the integration and is working now...


[nginx] Pass request port to real server

If nginx ingress controller is behind some loadbalancer like haproxy, which redirect other port (not 80 or 443) to nginx ingress controller.
So request may looks like http://host:port. But nginx set Host and X-Forwarded-Host as $host, which without port like host. Therefore when real server send redirects to client requests, the url looks like _http://host/redirect_url_ instead of correct url http://host:port/redirect_url.
If using $http_host instead of $host, the correct port will be passed to real server.

@danielqsj we already pass this information with the header X-Forwarded-Port

@aledbf Thanks for your reply.
But in my environment, the http_x_forwarded_port always be null. So X-Forwarded-Port will be the $server_port which is 443 (listened by nginx) not the real port (listened by haproxy).
Here is my environment:
client <-> kube-proxy <-> haproxy (used to redirect port, in tcp mode) <-> nginx ingress controller <-> real server
Will there be some misconfigurations?

@aledbf The problem seems that nginx behind tcp mode proxy of haproxy can only see haproxy's IP. And haproxy can not rewrite http head if using tcp mode.
In this scenario, I find only $http_host contain the correct port. Is there better solution ?

@danielqsj the problem with $http_host is that could be blank but $host always contains a value. I think instead of choosing one of the variables we can use map directive like:
    map $http_host $best_http_host {
        default          $http_host;
        ''               $host;
    }

@aledbf Great idea. I will fix it. Thank you a lot.

@aledbf I have fixed this PR #454 .


improved responsiveness to the website

resolved issue #249
please have a look and merge

It has been changed for desktop view too but it shouldn't be.


Fix Collapsible TS Type

New type definitions in react 18.0.0 (@types/react) flag this component for having children when it it's type definition doesn't say it has any children. This change should be backwards compatible since PropsWithChildren has existed for awhile and this is just a clarification on the underlying type.

This fixes https://github.com/oblador/react-native-collapsible/issues/450 and https://github.com/oblador/react-native-collapsible/issues/436


[Backport] [2.x] Fix for stuck update action in a bulk with retry_on_conflict property (#11153)

Backport of #11153

@reta @andrross please take a look