Composer keep requiring mbstring - apache

i've installed composer and now trying to run composer require maknz/slack. However i keep getting an error, that i can't seem to fix. i've tried to install mbstring, but it still give me this error? what am i doing wrong?
- Installation request for maknz/slack ^1.7 -> satisfiable by maknz/slack[1.7.0].
- maknz/slack 1.7.0 requires ext-mbstring * -> the requested PHP extension mbstring is missing from your system.
To enable extensions, verify that they are enabled in those .ini files:
- /etc/php/7.0/cli/php.ini
- /etc/php/7.0/cli/conf.d/10-opcache.ini
- /etc/php/7.0/cli/conf.d/10-pdo.ini
- /etc/php/7.0/cli/conf.d/20-calendar.ini
- /etc/php/7.0/cli/conf.d/20-ctype.ini
- /etc/php/7.0/cli/conf.d/20-exif.ini
- /etc/php/7.0/cli/conf.d/20-fileinfo.ini
- /etc/php/7.0/cli/conf.d/20-ftp.ini
- /etc/php/7.0/cli/conf.d/20-gettext.ini
- /etc/php/7.0/cli/conf.d/20-iconv.ini
- /etc/php/7.0/cli/conf.d/20-json.ini
- /etc/php/7.0/cli/conf.d/20-phar.ini
- /etc/php/7.0/cli/conf.d/20-posix.ini
- /etc/php/7.0/cli/conf.d/20-readline.ini
- /etc/php/7.0/cli/conf.d/20-shmop.ini
- /etc/php/7.0/cli/conf.d/20-sockets.ini
- /etc/php/7.0/cli/conf.d/20-sysvmsg.ini
- /etc/php/7.0/cli/conf.d/20-sysvsem.ini
- /etc/php/7.0/cli/conf.d/20-sysvshm.ini
- /etc/php/7.0/cli/conf.d/20-tokenizer.ini
You can also run `php --ini` inside terminal to see which files are used by PHP in CLI mode.
Installation failed, reverting ./composer.json to its original content.

Related

dbt- synapse models\example generating error

The problem Iā€™m having is after the profiles.yml All checks passed! (the connection successful)
when i run dbt get this message
Configuration paths exist in your dbt_project.yml file which do not apply to any resources. There are 1 unused configuration paths:- models.dbt_project.example
when I run
dbt --version
Core: - installed: 1.4.1
- latest: 1.4.1 - Up to date!
Plugins: - sqlserver: 1.3.0 - Not compatible!
- synapse: 1.3.2 - Not compatible!
At least one plugin is out of date or incompatible with dbt-core.
You can find instructions for upgrading here:
https://docs.getdbt.com/docs/installation
The error message is telling you what is wrong. There is config in your dbt_project.yml file that does not apply to any files in your models directory.
When you run dbt init, it creates some example models (.sql files) in the models/example directory, like my_first_dbt_model.sql. It also adds some example config to dbt_project.yml that looks like this:
# towards the bottom...
models:
your_project_name:
# Config indicated by + and applies to all files under models/example/
example:
+materialized: view
You need to delete the example key, since you deleted that directory. You could also delete the keys above it, or keep them, since you'll probably add config at some point.
The OTHER error is probably because you installed dbt-core separately from dbt-synapse. You should delete your virtual environment and start over by just running pip install dbt-synapse, which will automatically install a compatible version of dbt-core. You should NEVER pin versions of dbt-core, only the version of your adapter (since the adapter will specify its compatible versions of dbt-core).

Cannot find module 'metro-symbolicate/src/Symbolication'

I got this error while i follow the tutorial on react native of Mosh ( youtube link )
I'm totaly new to react native so someone can explain what is going on and how to solve it ?
here the prompt i get when i launch expo start command
MacBook-Pro-de-MAC:DoneWithIt mac$ expo start
Starting project at /Users/mac/Documents/projects/loto/test/DoneWithIt
Developer tools running on http://localhost:19002
Unable to reach Expo servers. Falling back to using the cached dependency map (bundledNativeModules.json) from the package "expo" installed in your project.
Cannot find module 'metro-symbolicate/src/Symbolication'
Require stack:
- /Users/mac/Documents/projects/loto/test/DoneWithIt/node_modules/metro/src/Server/symbolicate.js
- /Users/mac/Documents/projects/loto/test/DoneWithIt/node_modules/metro/src/Server.js
- /Users/mac/Documents/projects/loto/test/DoneWithIt/node_modules/metro/src/index.js
- /usr/local/lib/node_modules/expo-cli/node_modules/#expo/dev-server/build/metro/importMetroFromProject.js
- /usr/local/lib/node_modules/expo-cli/node_modules/#expo/dev-server/build/HermesBundler.js
- /usr/local/lib/node_modules/expo-cli/node_modules/#expo/dev-server/build/MetroDevServer.js
- /usr/local/lib/node_modules/expo-cli/node_modules/xdl/build/start/startDevServerAsync.js
- /usr/local/lib/node_modules/expo-cli/node_modules/xdl/build/internal.js
- /usr/local/lib/node_modules/expo-cli/node_modules/xdl/build/index.js
- /usr/local/lib/node_modules/expo-cli/build/exp.js
- /usr/local/lib/node_modules/expo-cli/bin/expo.js

issue in upgrading odoo11 to odoo13 via OpenUpgrade

I'm trying to upgrade odoo11 to odoo13 via openupgrade, I know you can't directly upgrade odoo11 to odoo13, you have to upgrade odoo11 to odoo12 and from odoo12 upgrade to odoo13.
after I upgrade odoo11 to odoo13, I try to run odoo13 based on database odoo11 that I've upgrade to odoo13, but I've got error when I'm Login,
the error like this (let say this error_1)
Could not get content for /web_clearbit/static/src/less/web_clearbit.less defined in bundle 'web.assets_backend'.
Could not get content for /account_reports/static/src/less/account_financial_report.less defined in bundle 'web.assets_backend'.
Could not get content for /stock_barcode/static/src/less/stock_barcode.less defined in bundle 'web.assets_backend'.
Could not get content for /stock_barcode_mobile/static/src/less/stock_mobile_barcode.less defined in bundle 'web.assets_backend'.
Could not execute command 'lessc'This error occured while compiling the bundle 'web.assets_backend' containing:
 - /web/static/lib/bootstrap/scss/_functions.scss
 - /web/static/lib/bootstrap/scss/_mixins.scss
 - /web/static/src/scss/bs_mixins_overrides.scss
 - /web/static/src/scss/utils.scss
 - /web/static/src/scss/primary_variables.scss
 - /web_enterprise/static/src/scss/primary_variables.scss
 - /web_editor/static/src/scss/web_editor.variables.scss
 - /mail/static/src/scss/variables.scss
 - /portal/static/src/scss/primary_variables.scss
 - /account/static/src/scss/variables.scss
 - /web_editor/static/src/scss/secondary_variables.scss
 - /web_enterprise/static/src/scss/secondary_variables.scss
 - /web/static/src/scss/secondary_variables.scss
 - /web_editor/static/src/scss/bootstrap_overridden_backend.scss
 - /web_editor/static/src/scss/...
and after I ignore that error , I see odoo UI is messed up I check for the data , and I see the data from odoo11 is still there (not change).
another error that I've got is when I'm going to setting app, the error is like this (let say error_2)
Error context:
View `res.config.settings.view.form.inherit.mail.push`
[view_id: 360, xml_id: mail_push.res_config_settings_view_form, model: res.config.settings, parent_id: 244]
and after I get error_2 I can't go to another app (purchase, sale, inventory, etc), can you help me how to solve this.

selenium2 for composer install facing with phalcon/incubator error in PHP

I am using window command prompt,When I update composer facing with below error
C:\xampp\htdocs\myproject>composer update
Warning: This development build of composer is over 60 days old. It is recommend
ed to update it by running "C:\ProgramData\ComposerSetup\bin\composer.phar self-
update" to get the latest version.
Loading composer repositories with package information
Updating dependencies (including require-dev)
Failed to decode response: zlib_decode(): data error
Retrying with degraded mode, check https://getcomposer.org/doc/articles/troubles
hooting.md#degraded-mode for more info
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for phalcon/incubator dev-master -> satisfiable by ph
alcon/incubator[dev-master].
- phalcon/incubator dev-master requires ext-phalcon >=2.0.4 -> the requested
PHP extension phalcon is missing from your system.
The last line should give you a clue: You haven't yet installed PhalconPHP on your system, which is required by the Incubator package.
Also, run a composer self-update as recommended.

LiveReload with Guard not working, even though it says it does

I'm trying to use Guard with LiveReload plugin for Chrome on Windows 7. It's not working and I don't know how I can trouble shoot this really. I'm using Bash to initiate guard, then activating LiveReload in the browser.
This is what it tells me:
$ guard
17:42:43 - INFO - Guard is using TerminalTitle to send notifications.
17:42:43 - INFO - Guard is now watching at 'c:/wamp/www/test'
17:42:43 - INFO - LiveReload is waiting for a browser to connect.
Please add the following to your Gemfile to avoid polling for changes:
require 'rbconfig'
gem 'wdm', '>= 0.1.0' if RbConfig::CONFIG['target_os'] =~ /mswin|mingw|cygwi
n/i
[Listen warning]:
[1] guard(main)> 17:43:14 - INFO - Browser connected.
17:43:14 - INFO - Browser connected.
17:43:22 - INFO - Sass [0.01s] styles.scss -> styles.css
ā†]2;[Guard::Sass] styles.scss -> styles.css
17:43:23 - INFO - Reloading browser: css/styles.css
17:43:33 - INFO - Sass [0.00s] styles.scss -> styles.css
ā†]2;[Guard::Sass] styles.scss -> styles.css
17:43:34 - INFO - Reloading browser: css/styles.css
09:00:34 - INFO - Sass [0.01s] styles.scss -> styles.css
ā†]2;[Guard::Sass] styles.scss -> styles.css
09:00:35 - INFO - Reloading browser: css/styles.css
[1] guard(main)>
So, it says it is reloading the browser. But nothing is happening. Any ideas about what could be wrong here?
Hi I think that the thing which you need is to install a livereload extention for you browser.
this one is for google chrome
https://chrome.google.com/webstore/detail/livereload/jnihajbhpnppcggbcgedagnkighmdlei
thant after runing the command guard
click on the livereload icon :
Good luck
d_rails's comment helped me: use
guard --debug
In my case, I saw:
21:34:51 - ERROR - Guard::LiveReload failed to achieve its <start>, exception was:
> [#cddd037a00ab] RuntimeError: no acceptor (port is in use or requires root privileges)
Oddly, the output is ERROR, not debug. I have no clue why that's not important enough to show if --debug is not specified.
To find out what was using that port, I ran (for Ubuntu 14.04) lsof -i :35729 (the default port of livereload) and found out that my Sublime Text livereload plugin was already using that port. I decided to change the port used by my ruby app with livereload. In my guardfile, I used:
guard :livereload, port: 12345 do
...
end