Transparent canvas - iOS 11.3 beta

There is a problem with pixi 4.7.0 and transparent parameter.
Bug is reproducible on iPhone SE/6S/7 and iOS 11.3 beta from this link: https://jsfiddle.net/b3ctuuez/.
It is not reproducible on Chrome/Firefox/IE.

Are other iPhones or iOS devices affected aside from the ones you mentioned? Or are those only ones you've tested? Does transparent work correctly on older version of PixiJS?
Bug does not exist on latest iOS 11.2.5 on iPhone 6s.
If you can create a simple WebGL canvas (no PixiJS) and it doesn't respect transparently, then likely, this is a Safari/WebKit bug and should be filed with Apple.

I have just noticed the same behaviour. @horyzont if you report this to Apple could you post a link to the bug so I can follow the progress.
Many thanks

Hope I've reported it in proper place: https://bugreport.apple.com/web/?problemID=37234491

Thanks for posting but I think you can only see that as it's probably linked to your dev account.
Would really appreciate if you posted any feedback/movement from apple.

Thanks @horyzont for digging into this.

Workaround:
var app = new PIXI.Application(800, 600, {backgroundColor: 0x1099bb, transparent: 'notMultiplied'});
app.renderer._backgroundColorRgba[3] = 1.0;

According to forum post , Mac 10.12.6, Safari 11.0.2 (126<IP_ADDRESS>.6) has the same issue. It is not mobile-only.

This workaround:
var app = new PIXI.Application(800, 600, {backgroundColor: 0x1099bb, transparent: 'notMultiplied'});
app.renderer._backgroundColorRgba[3] = 1.0;

doesn't work. Background is still not transparent. You can verify here: https://jsfiddle.net/7w59pmmm/

Its workaround for not transparent background. Sorry, no transparent for that safari version.

Good news, looks like this is fixed in 11.3 beta 3 :)

Excellent 👍 We will check it soon.. Thanks!


HF1 - update ref tests

https://github.com/ChainSafe/eth2.0-spec-tests/releases/tag/v1.0.0-hf1.0

Reftests are updated but we need to continue enabling the Altair tests as we implement the required functionality. Leaving this open as a reminder for that.


find-moj-data: search term highlight tags

Check this is true, but I think when we highlight search terms the correct accessible approach is to use  tags
E.g. instead of

Derived table that has one row per offence for all defendants across all cases

Do this

Derived table that has one row per offence for all defendants across all cases

And then style the font-weight of mark.
Live example from our publications search here.

Strong tags in the example below are being rendered by the markdown template function.


Is RocketPants still alive?

The latest commit on the master branch is dated September 22, 2015, while the latest commit on the 2.0-rewrite branch is dated December 15, 2013.
I hate to be that guy, but is RocketPants still being maintained? I'm not using it much anymore, but I still have some projects that depend on it and I'd love to know what the future of this gem is.
Much :heart: either way.

So I realise it looks bad replying this late, but I thought I'd give a proper honest answer and wanted to muse on it for a while:
2.0-rewrite is for sure effectively dead - Everytime I set out to work on it, as tends to happen with full rewrites, I'd make a little progress and effectively nothing more.
master is generally "alive", in that when I encounter issues I will fix / merge in fixes, but I've not for a while. All of my code tends to live on older versions of Rails, and I've not been driven to update it.
A lot has happened since I started 2.0 + such, so it really does need to be revisited - but It's been far too long and I've yet to be able to really justify the time to do it.
Short answer: It's alive, but on life support. I don't plan on killing it / abandoning completely, as I still use it in my own work - but I wouldn't be against someone taking over 2.0 and running with it (with some discussion around the intentions of it etc).

Thanks for the honesty, man. That was all I needed. I'd take it on myself, but I've moved towards another architecture and I'm not using RocketPants anymore, unfortunately. RocketPants was a real timesaver when I used it, though.
I wish you the best of luck with RocketPants and future projects! :rocket: :


Update libFuzzerTutorial.md

Fixed a typo

Thanks for the fix!
We can't apply the PR w/o you signing the CLA first, so I've just fixed the typo myself.
(If you would like to contribute further, please do sigh the CLA)


Blur celluar blobs during generation

Blur celluar blobs during generation. Use a convolution.

https://forum.unity.com/threads/contribution-texture2d-blur-in-c.185694/


Not available on Play Store

This plugin has not been available on the Play Store for a while. Could we get it back up again? :)
This screenshot shows how it looks after following the link to the plugin from within JuiceSSH

I have the same problem since I've updated to Android 8.1. I think it's not supported...

Install it via apkpure

@KMe0w it seems to not be there
https://m.apkpure.com/search?q=Juicessh+plugin&region=

https://drive.google.com/file/d/1_vF0Tsui0uLXInGIeCYsbvkzflJWyEi8/view?usp=drivesdk
Try with this or build it from source.

I think you need to get some pussy homeboy

I also found that it wasn't available on the app store Google Play store so what I did did because I kept getting a picture of a satellite for the :-( appearing so I exited the Play Store and went back into it manually searched for the app and happened question and somehow I was able to access the app in question I do hope this was helpful please let me know thank you.
You may also contact me at this email address<EMAIL_ADDRESS>


Release the 3.8.0 version

@poliorcetics @Killavus @codybloemhard @ecnelises @Cube707 @Yestercafe @ydirson @zanchey @8bitZeta @MysticalDevil
I have finally published a new release. Thanks again for your pull requests!


Error: unknown option: --config-file

GH Action Config
javascript-e2e-tests:
    name: JS e2e Tests
    runs-on: ubuntu-16.04
    steps:
      - uses: actions/checkout@v2
      - name: Install dependencies
        uses: cypress-io/github-action@v1
        with:
          runTests: false
          working-directory: MY_DIR
      - name: Run e2e tests
        uses: cypress-io/github-action@v1
        with:
          install: false
          working-directory: MY_DIR

Problem
The first steps run fine - checkout and installation of the dependencies. When GH actions starts to run the Run e2e tests step it errors with the following:
Skipping install because install parameter is false
Cypress test command: npx cypress run --config-file cypress.json
/usr/local/bin/npx cypress run --config-file cypress.json

  error: unknown option: --config-file

Are you using Cypress version that does not understand --config-file? https://docs.cypress.io/guides/references/changelog.html#3-5-0

Ah that could very well be it. I didn't setup cypress in our environment - just tasked with creating a CI workflow with actions!


run time error in Windows Phone

Hi aritchie,
You have done a great work with this library, keep it up. I implemented your library in a Xamarin Forms PCL project, there it worked well in Android and iOS but on Windows Phone it throws an invalid cross thread access exception.
I have created a simple test page and implemented the same code as your sample code here https://github.com/aritchie/barcodes/blob/master/src/Samples/Samples/Pages/MainPage.cs
I tried reading a bar code by clicking on the Bar code reading button, and then only this occurs on WP8 !
I have also called the BarCodes.Init(); method in my WP8 project MainPage.cs so I can not figure out the issue here. Please look into this issue.
Thank you.

The first exception is what matters.  You haven't granted your app camera privileges

Thank you very much for your quick response. Now it works like a charm ! :)


resolve.alias not works

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
Resolve.alias not works as mentioned in https://webpack.js.org/configuration/resolve/#resolve-alias
/* ./webpack/base.js */
  ...
  resolve: {
    extensions: [ '.js', '.json', '.css' ],
    modules: [
      config.compile.entry,
      'node_modules'
    ],
    alias: {
      Actions: config.compile.entry + '/actions/'
    }
  }
  ...

If the current behavior is a bug, please provide the steps to reproduce.
1- git clone https://github.com/raminious/react-universal-boilerplate
2- cd react-universal-boilerplate
3- git checkout webpack-alias
4- yarn (or npm install)
5- npm run dev

What is the expected behavior?
import { types } from 'Actions/app' should work but getting this error:
Error: Cannot find module 'Actions/app'
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Node version: v6.6.0
Webpack version: 2.2.1
OS: OSX El Capitan

What is the value of config.compile.entry? Are you sure the final path is correct?

@trusktr You can find it in config/index.js file
const config = {
  compile: {
    entry: path.resolve(__dirname, '../src')
  }
}

Yes I doubt and checked that many times, that was okay

I am having the same issue. resolve.alias seems to be doing absolutely nothing

Same here! I was kicking tires with a simple sample using 2.2.1 and I'm facing the same issue.

same

Could you update enhanced-resolve and check again?

@sokra I updated to<EMAIL_ADDRESS>and still getting same error

+1 same error

@sokra Any good news ?

This happens for me:

set up the alias: OurComponents: path.resolve(__dirname, '../app/components/index.js'),
use it in one file like import {App} from 'OurComponents';
start webpack (dev server)

Works fine 🥇

Add it to another file, like import {Hamburger} from 'OurComponents';
Refresh the page

Works fine

Restart webpack (not making any change to the code)

I get Error: Cannot find module 'OurComponents'
So for me at least it seems to be something when it's used in more than one file and when webpack is first starting causing this error, that isn't happening when webpack is re-compiling or when it's only used in one file.
The full thing:
Error: Cannot find module 'OurComponents'
    at Function.Module._resolveFilename (module.js:472:15)
    at Function.Module._load (module.js:420:25)
    at Module.require (module.js:500:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:/web/davidg-site/app/components/App/App.jsx:12:1)
    at Module._compile (module.js:573:32)
    at loader (C:\web\davidg-site\node_modules\babel-register\lib\node.js:144:5)
    at Object.require.extensions.(anonymous function) [as .jsx] (C:\web\davidg-site\node_modules\babel-register\lib\node.js:154:7)
    at Module.load (module.js:490:32)
    at tryModuleLoad (module.js:449:12)

I set resolve.alias = path.resolve(__dirname, './src/styles/')
and when I use import "styles/common.css" it failed,
getiing error : Cannot find module 'styles/common.css'
but when i use require('styles/common.css') it just worked
what happened?

I am doing this successfully in a new project, and it seems to be working well. What I am doing is:
base-ui/client/package.json
"devDependencies": {
    ...
    "webpack": "^2.2.0"
}

webpack.dev.config.js
resolve: {
            modules: [path.resolve('./node_modules')],
            alias: {
                Common: path.resolve(__dirname, '../../../../base-ui/client')
            },
            extensions: ['.js', '.jsx', '.json', '.scss']
        },

We have different applications that use the components inside "base-ui" and these applications live in the same parent directory as base-ui.
base-ui/client/components/index.js
export { default as Button } from './button/Button';
export { default as SingleInput } from './singleInput/SingleInput';

base-ui/client/components/button/Button.jsx
...
export default Button

In these applications we can do things like:
account-ui/client/page/ForgotPassword.jsx
import { Button, SingleInput } from 'Common/components';

This method seems to be working across the board. It has it's challenges when it comes to Jest testing and using things like wallabyjs which I am still figuring out, but as for webpack and resolve.alias it is working great.
I hope this helps.

In my case, I don't get any errors, but the exact same import in two different files produces different values:
// file 1:
import { StatusBar } from 'Components' // works great!

// file 2:
import { StatusBar } from 'Components' // undefined :(

Also, just as a friendly reminder, if you're using Babel, make sure you deactivate modules,
{
  "presets": [["env", {"modules": false}], "react"],
}

@epitaphmike which OS? I'm using Windows, was doing something very similar and it wasn't working. alias.modules isn't working for me either.

I am using OS X El Capitan.

I wonder if this is a Windows issue then. I've just tried resolve.modules instead of resolve.alias and it doesn't work either.
Hopefully I just doing something dumb. Should the below work in theory?
I have a file my-site/buildTools/dev.js with my dev config that looks in part like this:
    resolve: {
        modules: [
            path.resolve(__dirname, '../app'),
            'node_modules',
        ],
    },

(I've tried fifty different combos of relative paths and absolute paths)
Then I have my-site/app/components/index.js:
export { default as Home } from './pages/Home/Home';

(I've also tried doing this as my-site/app/components.js)
Then I import my component like so
import { Home } from 'components'; // "cannot find modules 'components'"

But the below two methods work, so I know at least the paths are right:
import Home from '../pages/Home/Home'; // works
import { Home } from '../../components/index.js'; // works

Could it be another part of my setup? I wonder if using babel-register is causing the problem.

I am not using babel-register anywhere.
My main babel imports include
base-ui/client/package.json
"devDependencies": {
    "babel-jest": "^18.0.0",
    "babel-plugin-transform-class-properties": "^6.22.0",
    "babel-plugin-transform-object-rest-spread": "^6.22.0",
    "babel-polyfill": "^6.22.0",
    "babel-preset-es2015": "^6.22.0",
    "babel-preset-react": "^6.22.0",
    "enzyme": "^2.7.1",
    "enzyme-to-json": "^1.4.5",
    "fetch-mock": "^5.9.3",
    "jest": "^18.1.0",
    "jest-fetch-mock": "1.0.5",
    "nock": "^9.0.2",
    "react": "^15.4.2",
    "react-addons-test-utils": "^15.4.2",
    "react-dom": "^15.4.2",
    "react-test-renderer": "^15.4.2"
  },

also I made a few adjustments in our directory structure that you may want to try.
base-ui/client/components/button/
button----
    Button.jsx
    index.js
    propTypes.js

base-ui/client/components/button/Button.jsx
import React from 'react';
import RaisedButton from 'material-ui/RaisedButton';
import { buttonProps } from './propTypes';

const Button = ({ label, style = {}, href, onClick }) => (
    <RaisedButton
        label={ label }
        style={ style }
        href={ href }
        onMouseUp={ onClick }/>
);

Button.PropTypes = buttonProps;

export default Button;

base-ui/client/components/button/index.js
import Button from './Button';
export default Button;

base-ui/client/components/index.js
export { default as Button } from './button';

account-ui/client/page/ForgotPassword.jsx
This is unchanged.
import { Button, SingleInput } from 'Common/views/components';

I had a similar issue with aliases not working. I fixed it by removing node_modules folder and installing packages again (running yarn).

@filmic  I had the same issue even do I am using yarn and did that still got the issue

Same issue here.
Node version: v6.10.1
Webpack version: 2.2.1
OS: OSX El Capitan
resolve: {
  extensions: ['.js', '.vue', '.json'],
  alias: {
    '@': resolve('src')
  }
},

import App from<EMAIL_ADDRESS>
ERROR in ./src/js/dashboard.js
Module not found: Error: Can't resolve<EMAIL_ADDRESS>

The AliasPlugin in enhanced-resolve looks to be operating correctly, it changes the request obj as you expect in this code https://github.com/webpack/enhanced-resolve/blob/0d0c5f09a03a03399d7344e56a2810c3aa212c0e/lib/AliasPlugin.js#L45
I think the issue is that the alias value isn't an absolute path, so it's the resolving following the alias changes that fails. I'll debug a bit more.

The UnsafeCachePlugin seems to be the only enhanced-resolve plugin applied to the newly constructed request object, both before and after resolve appear to have no plugins registered so it's applied at the resolve stage.
https://github.com/webpack/enhanced-resolve/blob/0d0c5f09a03a03399d7344e56a2810c3aa212c0e/lib/UnsafeCachePlugin.js#L29

It looks to me like the ModulesInHierachicDirectoriesPlugin doesn't handle absolute modules values, joining an absolute directory to another absolute one will fail https://github.com/webpack/enhanced-resolve/blob/0d0c5f09a03a03399d7344e56a2810c3aa212c0e/lib/ModulesInHierachicDirectoriesPlugin.js#L24 ?

It doesn't look like modules would ever be passed into enhanced-resolve, if we use this resolver https://github.com/webpack/enhanced-resolve/blob/0d0c5f09a03a03399d7344e56a2810c3aa212c0e/lib/node.js#L18 the options are hardcoded in during creation...

That means our resolver has these options hardcoded into it and our webpack config options aren't applied https://github.com/webpack/enhanced-resolve/blob/0d0c5f09a03a03399d7344e56a2810c3aa212c0e/lib/ResolverFactory.js#L38

OK so I was looking at the wrong resolver creation, it's this one that is used by webpack https://github.com/webpack/webpack/blob/master/lib/WebpackOptionsApply.js#L283 and that's OK it does get the webpack config options.

request.module is false even though the alias is pointing toward a module https://github.com/webpack/enhanced-resolve/blob/0d0c5f09a03a03399d7344e56a2810c3aa212c0e/lib/ModuleKindPlugin.js#L16
Should we use onlyModule: true for aliases from now on?

It appends the file extension and the FileExistsPlugin checks if the file exists, then after a while you get an error that the file without the .js extension doesn't exist (which it doesn't) you then expect the file with .js to be found (it does exist at the path) but we then get a ModuleNotFound error. Is it not allowing all the plugins to complete execution?

It looks like every new entry to resolve.modules increases build time linearly
I think webpack keeps looking for modules even after a file has been found, given it's async/callback approach it's very hard to cancel ongoing work, is that correct?

I am not positive this is the same issue, however I created a project that shows that alias order matters, and it probably should not (since a hash does not guarantee order). I can open a seperate bug report if deemed not the same as this one. With  webpack 2.4.1.
See Sample Repo:
https://github.com/jspears/webpack-alias-bug
But might be useful to have another sample of the issue.

Same issue. Is this still being investigated?

I can't get it working at all.
I've been searching the test cases, I can't find a test for alias.  Does anyone know of one?
@jspeas, maybe a separate issue for ordering.  @raminious original issue only has one alias.

This is crazy.  I can't seem to get anything at all to work with resolve.alias (on Windows 7 x64 with webpack 2.4.1 and node 6.10.1).  I'm going to try to find a few boilerplate repos using alias to see if I can get any of them to compile.  I just wanted to start cleaning up a project that has a bunch of relative paths and stumbled upon this issue after banging my head against a wall for an hour.  Is this an isolated issue or are there people out there who aren't having any problems?

@dlong500 try to use this boilerplate, just put resolve: {} for example and you I'll be able to reproduce this issue.

I've given up on this for now and just started using babel-plugin-module-resolver because I'm already using babel anyway.  That allows me to create the same type of aliases through a babel transform.

same issue here

@filmic it works for me too! Thanks

Same for me on Mac OS Sierra 10.12.3, node v.6.10.2 and webpack 2.2.1. It works using require though as pointed above.

@sokra any updates? Is this a bug, or ... feature? :)

I'm having the same issue. I'm aliasing multiple modules to filesystem dirs, and all of them work... except one. For this one, its looking relative to the 'src' directory of the app with the aliases.. ie, as if i said import './mymodule' instead of 'mymodule' .

using require('module') works, and I also found that renaming the module in the import statement, and in the alias, causes it to work. perhaps some sort of caching problem?

When im using alias like this one:
alias{
H:path.resolve(__dirname,'resources/assets/handlebars')
}
and have loader for handle bars
{ test: /.hbs$/, loader: "handlebars-loader" }
i have tested to require the same file but with different prefix,with .js extension that alias is working,but when i change extension to hbs im getting error too

ah, I found my issue was that I was also using babel-resolver plugin
https://www.npmjs.com/package/babel-plugin-resolver
seems like this plugin was eagerly trying to resolve the module name relative to the 'resolveDirs' rather than using the aliased value.
Switching to similar plugin https://github.com/tleunen/babel-plugin-module-resolver
fixed the issue.
I will also mention this on the babel-plugin resolver github.

Having same issue.
I ended up using resolve.modules config instead for the time being.
resolve : { modules: [path.resolve(__dirname, "app"), "node_modules"] }
So instead of referencing import file by relative path, you can reference it from the project directory.

@kemhwd Why you added "node_modules" to resolve.modules list? Is one special reason for that?

my issue turned up, that I was wrongly using path.resolve(__dirname, "app/some/path")
correct is path.resolve(__dirname, "app", "some", "path") and that works...
quite a lot comments on this issue xD

@jancassio "node_modules" is the default value. referring from its doc.
https://webpack.js.org/configuration/resolve/#resolve-modules
I guess if you remove it, webpack won't be able to find JS files in node_modules directory.

@kemhwd Ok, seems this makes things more clear

If you want to add a directory to search in that takes precedences over node_modules/:
modules: [path.resolve(__dirname, "src"), "node_modules"]

Thanks to @MartanLV I managed to fix my issue.  To be honest, webpack could be better at emitting useful error messages. Saying that an alias cant be found is as useful as saying 'something's wrong'

@jarecsni By googling lots and lots of webpack errors without a useful error messages, I discovered the great flag "--display-error-details" which actually helps a lot. It displays a boatload of error details that actually help quite often. HTH.

I recently stumbled onto a solution that works for me. If you're using Typescript 2.0+ (which you should be) and awesome-typescript-loader (which you should be) you can obviate the need for resolve.alias by using the tsconfig parameters baseUrl and paths inside of the top-level compilerOptions parameter. It's great because it works regardless of how you manage your modules and if you're using a linter (which you should be) will automatically be understood. Here's an example from my code:
"compilerOptions": {
  ...
  "baseUrl": ".",
  "paths": {
    "@Client/*": ["client/*"],
    "@Components/*": ["client/src/components/*"],
    "@Containers/*": ["client/src/containers/*"],
    "@Repository/*": ["server/src/repository/*"],
    "@Server/*": ["server/*"],
    "@Shared/*": ["shared/*"]
  }
  ...
}

To allow webpack to access these aliases, add the following require and also add the following plugins configuration to your webpack config's resolve:
const { TsConfigPathsPlugin } = require('awesome-typescript-loader');

resolve: {
  ...
  plugins: [
    new TsConfigPathsPlugin(/* { tsconfig, compiler } */)
  ],
  ...
},

Now, when you want to import something from the {projectDir}/shared directory you can reference it like this:
import { MyType, MyInterface } from "@Shared/types";
🎉

I just hit an issue which caused all aliases to stop resolving due to the me adding a second package.json file within one of the src directories.
This error was thrown up in the eslint feedback and it seems to be further related to the use of eslint-import-resolver-webpack to resolve imports within my src files.
A rather specific use case but thought it may help some shed a little light on things.

In case anybody using Rails with webpack runs across this, the place to put in an alias for @ paths is:
config/webpack/shared.js

Just add to the resolve: hash:
  alias: {
       '@': resolve(settings.source_path + '/packs'),
  },

@raminiousbug

thanks

don't use eslint-loader and everything will be ok

I fixed it by removing node_modules  and run npm install

This happens to me with Webpack 3

Same issue: I using latest webpack with Angular4 and added some fast paths via resolve.alias and got errors:
ERROR in [at-loader] ./src/app/app.module.ts:39:8
    TS2307: Cannot find module 'core'.

ERROR in [at-loader] ./src/app/app.module.ts:47:8
    TS2307: Cannot find module 'shared/layouts'.

ERROR in [at-loader] ./src/main.browser.aot.ts:10:36
    TS2307: Cannot find module '../compiled/src/app/app.module.ngfactory'.
Child html-webpack-plugin for "index.html":

But I was wondered that it's eventually works despite the error.  I sent to log obtained objects in place where those errors have been appeared:
import {
  RootErrorHandler,
  LoggerService
} from 'core';

import {
  APP_LAYOUTS_DECLARATIONS
} from 'shared/layouts';

console.log('>>> LoggerService:', LoggerService);
console.log('>>> APP_LAYOUTS_DECLARATIONS:', APP_LAYOUTS_DECLARATIONS);

And got properly output in my browser:
>>> LoggerService: ƒ LoggerService(http) {
        this.http = http;
    }
>>> APP_LAYOUTS_DECLARATIONS: (2) [ƒ, ƒ]

And application starts and working without any errors. What it's means? The error in some loader or plugin?

Update, excuse me. It seems, it s not WebPack problem but  problem of 'awesome-typescript-loader' in my case.

For me this issue was triggered when changing the Webpack context. By setting the Webpack context to the src dir, aliases DO NOT work:
// webpack.config.js:
module.exports = {
  context: path.resolve(__dirname, './src'),
  entry: {
    app: ['./index.js']
  }
  // ...
}

When using the root of the project as the Webpack context, aliases DO work:
// webpack.config.js:
module.exports = {
  context: path.resolve(__dirname, '.'),
  entry: {
    app: ['./src/dashboard/index.js'],
  }
  // ...
}

I can confirm that the problem is connected with using custom context in my case too

I resolved the issue by doing join, instead of resolve
alias: {
    Ui: path.join(__dirname, '/resources/assets/js/ui/'),
}

@tugayilik It's working. May I ask you to explain why is it making any difference? I'm curious

@imam According to node.js documentation;
Simply how resolve works;
path.resolve('/foo', '/bar') outputs /bar
This will always result in absolute url, simply passing __dirname as first argument doesn't matter in this case. Calling path.resolve() without any argument will give you __dirname.
According to my example, if i want to use path.resolve i need to use it like path.resolve('resources/assets/js/ui/'). It outputs __dirname/resources/assets/js/ui
How join works is simple, it brings all given arguments together and and gives you to path string;
path.join(__dirname, '/foo') outputs __dirname/foo

I've been having this issue for the last hour trying all sorts of different combinations.
NOTE: This works fine when using modules, but alias is where I see the issue.
I'm on windows and have my Webpack config in a different directory than my project root and my project is on my secondary D: drive. The path I'm sending in is absolute:
D:\Projects\Companies\[PROJECT_NAME]\app

Webpack config:
{
	resolve: {
		alias: {
			'~': 'D:\Projects\Companies\[PROJECT_NAME]\app',
		},
		extensions: ['.js'],
		modules: ['node_modules'],
	},
}

In a component, I import like this:
import Sample from '~/components/samples/Sample'

I receive this error:

ERROR in ./app/entrypoints/client/index.js
Module not found: Error: Can't resolve '~/components/samples/Sample' in 'D:\Projects[PROJECT_NAME]\app\samples\Sample'

Yep same, still getting this issue too. Doesn't seem to work at all

I was able to resolve this issue on my end.
I was merging Webpack config objects and was accidentally overriding an undefined alias prop with the one that had data.

As a work around I've used webpack.Define plugins to get environment specific config. That seems to be working pretty well. I pass the environment through a command line parameter when running or building. I then use that to import a .json file with specific environment settings. Hope someone finds that useful too...
`
module.exports = env => {
var config = require(../config/${env}.json)
return {
...
plugins: [
  new webpack.DefinePlugin({
    'env': JSON.stringify(config)
  })
]

};
};
`

Hello everyone
I had a problem with resolving files outside my project directory. It worked for some files and didn't work for others like @aryzing mentioned above..
I just managed to solve this problem with a simple edit: putting a @ character in front of the alias...
Before it was
config.resolve.alias['global'] = path.join(__dirname, '../_global')
Now it is
config.resolve.alias['@global'] = path.join(__dirname, '../_global')
And it works..
Hope this will help others

Adding @ in front of the alias name solve the issue

Why? Where is this documented?

@aryzing i couldn't find any documentation. just did a random experiment and it worked 🥇

@Cedric1994 I think your problem was; your alias common  has the same name with the existing directory common. The solution was not @at the beginning, it was different name than common.

Didn't work either. added aliases to the preprocessor config, worked!

One thing that tripped me up is that aliases are ordered.
wrong order:
const aliases = {
  preact: require.resolve('preact'),
  'preact/devtools': require.resolve('preact/devtools'),
}

right order:
const aliases = {
  'preact/devtools': require.resolve('preact/devtools'),
  preact: require.resolve('preact')
}

You'll want to have your more specific aliases come before more general aliases.

Not a single solution worked from this discussion for @React

I have not found a solution yet, but this occurs in all new Vue-CLI projects - works in my older ones...
This is (at least for me) down to the addition of using @Types in my node modules, I guess Vue uses this now.. but i'm in the middle of trying to solve this without pulling my hair out. It is interesting to know that @Babel does not trip up the use of @ aliases within paths...
Thought it was one/two of my VS-Code extensions for intellisense paths, but that turned out to be a red herring.

I forked create-react-app so I could add support for importing some previously created bower components. We've proven this works with a minimal webpack config but we want to create our app with create-react-app so we can get all the react-script goodness.
The only thing that's problematic is resolving our aliases. No idea why this isn't working. There is a single bower component that has a vendor directory. The alias definition looks as follows.
Alias:
backbone: path.resolve(__dirname, 'glu/vendor/backbone/backbone')

Error:
./bower_components/glu/model.js
Module not found: Can't resolve 'backbone' in '/Users/ralph.smith/Workspace/bfs/bower_components/glu'

What's kind of interesting is if I remove the alias and add a module definition:
 modules: ['node_modules', paths.appNodeModules, 'bower_components', 'glu/vendor']

The above error goes away but I get other errors for things in the vendor directory:
./bower_components/glu/appBus.js
Module not found: Can't resolve 'backbone.wreqr' in '/Users/ralph.smith/Workspace/bfs/bower_components/glu'

I solved my alias problem by using the resolveApp utility in react-scripts/config/path.js.
e.g.
const appBowerModules = resolveApp('bower_components')
const gluVendor = resolveApp('bower_components/glu/vendor')

// put this in the webpack alias array
const alias = {
  backbone: path.resolve(appBowerModules, gluVendor, 'backbone/backbone'),
}

Any working solution for this?

@milangupta511 Please specify your issue again. It could be different but Yes! Since I know this issue is resolved.

Given the following folder structure:
~/src/components

Storybook Webpack config
.storybook/webpack.config.js
module.exports = {
  resolve: {
    alias: {
      '@components': path.resolve('src/components/')
    }
  }
};

Your component
~src/components/Button.js
import React from 'react'

export default ({ children, ...rest }) => (
  <button {...rest}>{children}!!!</button>
)

Storybook stories
index.stories.js
import React from 'react';

import { storiesOf } from '@storybook/react';
import { action } from '@storybook/addon-actions';

import Button from '@components/Button'

storiesOf('Button', module)
  .add('with text', () => <Button onClick={action('clicked')}>Hello Button</Button>)
  .add('with some emoji', () => (
    <Button onClick={action('clicked')}>
      <span role="img" aria-label="so cool">
        😀 😎 👍 💯
      </span>
    </Button>
  ));

It should work. 😎
Things to notice
Exports/Imports
import { Button } from '@components/Button' != import Button from '@components/Button'

Given the following folder structure: ~/src/components/Button.js
Storybook Webpack config
~/.storybook/webpack.config.js
module.exports = {
  resolve: {
    alias: {
      '@components': path.resolve('src/components/')
    }
  }
};

Your component
~/src/components/Button.js
import React from 'react'

export default ({ children, ...rest }) => (
  <button {...rest}>{children}!!!</button>
)

Storybook stories
~/stories/index.stories.js
import React from 'react';

import { storiesOf } from '@storybook/react';
import { action } from '@storybook/addon-actions';

import Button from '@components/Button'

storiesOf('Button', module)
  .add('with text', () => <Button onClick={action('clicked')}>Hello Button</Button>)
  .add('with some emoji', () => (
    <Button onClick={action('clicked')}>
      <span role="img" aria-label="so cool">
        😀 😎 👍 💯
      </span>
    </Button>
  ));

It should work. 😎
Things to notice
Exports/Imports
import { Button } from '@components/Button' != import Button from '@components/Button'

@Sawtaytoes  can you explain more what you do? I'm stuck so bad in making static path

@javadbat
In my Webpack config, I have this:
  resolve: {
    alias: {
      '@shared': path.dirname(require.resolve('app')),
      '~': path.join(fs.realpathSync(process.cwd()), 'app'),
    },
    extensions: ['.js'],
    modules: [paths.nodeModules],
  },

All of my browser code is in the app/ directory. This particular project has a differentiation between a package's app/ folder and the current project's app/ folder.
In this example, @shared is the package, ~ is the project. I wouldn't do it this way in the future, but I know this configuration works.

 If you don't want to type ../ consider using something like path.resolve(__dirname, '../src') so you can do
import Stuff from 'client/components/stuff'; // relative to root of project

instead of:
import Stuff from 'COMPONENTS/stuff'; // this is dumb

or:
import Stuff from './../stuff; // once upon a time highly paid web devs didn't complain about relative paths now they do

I think alias is broken or maybe the documentation needs to explain it better.
resolve: {
      alias: {
        _self: path.join(__dirname, 'src/web'),
        _shared: path.join(__dirname, 'src/shared'),
        _components: path.join(__dirname, 'src/web/components'),
        _helpers: path.join(__dirname, 'src/web/helpers'),
        _layers: path.join(__dirname, 'src/web/layers'),
        _mutations: path.join(__dirname, 'src/web/mutations'),
        _routes: path.join(__dirname, 'src/web/routes')
      }
    }

import { something } from '_components';

RESULT:
"export 'something' was not found in '_components'

But it's in the components/index.js, if I do normal relative import it works fine. I also think it does not understand export * from './module'; and export {default as something} from './module';.

Your problem might be that you have your webpack config in some nested folder, f.e.:
project-name/configs/webpack/dev.js
Then you would need something like this:
const srcDir = path.resolve(__dirname, '../../src'); // resolve project src directory

module.exports = {
	resolve: {
		alias: {
			'@components': path.join(srcDir, 'components'),
			'@modules': path.join(srcDir, 'modules'),
			'@store': path.join(srcDir, 'store')
		}
	}
       //...
}

This worked for me.

@alexeychikk my webpack config is on the root directory, the import I'm aliasing though is OUTSIDE the directory of where the entry file is located, it's one directory up.
My directory looks like this:
/ root
| -- src
|     | -- web
|     ` -- shared
| -- webpack.prod.js

But I assumed it does not matter where the folder is located since the alias is specifically directed to that folder via _shared: path.join(__dirname, 'src/shared')
So doing something like this should work:
import SomeModule from '_shared/someModuleDirectoryWithIndexJSinIt';
import { anotherModule } from '_shared/directory/anotherModuleDirectoryWithIndexJSinIt';

Unless there's a reason it shouldn't. console.logs show that there's no problem with the paths. I can also verify that the aliased paths are being looked up because when I remove the aliases I get a different error. If I take @aryzing's advice, I would get an error complaining about my webpack config:
import MiniCssExtractPlugin from 'mini-css-extract-plugin';
       ^^^^^^^^^^^^^^^^^^^^

SyntaxError: Unexpected identifier
    at new Script (vm.js:80:7)

Here's a repo where you can see this being used and work -->  webpack-multi-build-template.

Not having any success with achieving this in a react project.

@asos-oliverwilson how did you instantiated that react project? via create-react-app?

Had an alias issue with tsx files, turns out that path.resolve was indeed the fix on my end
what used to be
'#': './src/'

is now
'#': path.resolve('src/')

Also for me the issue was the "./".
After removing it from the path Webpack finally resolves the alias!! 🎉
(Actually I am using Encore but the it should be the same for pure Webpack config)
let config = Encore.getWebpackConfig(); config.resolve.alias["~"] = path.resolve(__dirname, 'assets/js'); module.exports = config;

In case someone runs into similar issue when using CSS modules via babel-plugin-react-css-modules, here's my solution: https://github.com/gajus/babel-plugin-react-css-modules/issues/25#issuecomment-478661715.

    resolve: {
        extensions: ['.js', '.vue', '.json'],
        alias: {
            // vue: 'vue/dist/vue.esm.js',
            config: path.resolve(__dirname, '../config'),
            vue: 'vue/dist/vue.js',
            // vue: 'vue/dist/vue.js',
            // 'vue$': 'vue/dist/vue.common.js',
            src: path.resolve(__dirname, '../src'),
            store: path.resolve(__dirname, '../src/store'),
            assets: path.resolve(__dirname, '../src/assets'),
            components: path.resolve(__dirname, '../src/components'),
            '@': path.resolve(__dirname, '../src'),
        },
    },

Module not found: Error: Can't resolve '@/store/modules/public/common/getters' in

    "webpack-bundle-analyzer": "^3.4.1",
    "webpack-cli": "^3.3.6",
    "webpack-dev-server": "^3.8.0",
    "webpack-merge": "^4.1.4"

I still have this problem when I have nested alias, for example:
 '@graphql-schema/order': path.resolve('src/graphql-schemas/order/'), // doesn't work
 '@graphql-schema': path.resolve('src/graphql-schemas/'), // works

I thought that the second line would be enough to resolve imports like import orderSchema from '@graphql-schemas/order/schema'; but I get Module not found: Error: Can't resolve '@graphql-schemas/order/resolvers' in '/my-app/src/graphql'
:(

@renatoagds can you create minimum reproducible test repo?

I am sorry @evilebottnawi just realized it was a problem on my side, please disregard.

Issue should be solved, but some loaders can't support alias so need improve them, i am closing this issue due a lot of comments with spam like :+1, Same issue and etc, it is not help to solve issue so feel free to open new issue with reproducible test repo if you have problems

I've given up on this for now and just started using babel-plugin-module-resolver because I'm already using babel anyway. That allows me to create the same type of aliases through a babel transform.

I haven't been able to get resolve.alias to work. At the time of writing I am using "webpack": "4.19.1".
I have instead opted to use babel-plugin-module-resolver and this seems to be working great. Definitely an alternative if like myself you have spent far too long bashing your head against the wall!

 If you don't want to type ../ consider using something like path.resolve(__dirname, '../src') so you can do
import Stuff from 'client/components/stuff'; // relative to root of project

instead of:
import Stuff from 'COMPONENTS/stuff'; // this is dumb

or:
import Stuff from './../stuff; // once upon a time highly paid web devs didn't complain about relative paths now they do

This is not dumb at all. It is exceedingly common to use aliases. It's not about being lazy, it's about writing portable code.

I'm still getting this issue in version 4.29.6.

still doesnt work

Having this issue when trying to use Option 3  when configuring node-env for Webpack (https://github.com/lorenwest/node-config/wiki/Webpack-Usage)


Hollow square java

Created the hollowsquare pattern in Java and added myself to the readme

I assume that you already check and test your code. Thanks for contributing

Yup! Should work for any input > 1. Thanks


Botframework maintenance

Updated Nuget packages to walkthrough bot dot net start and end projects

@rcervantes Can I proceed with the merge? I updated the Nuget package references for both solutions


ESP12F is now a "standard assembly only" part on JLCPCB

As the title states, this steeply increases the cost of JLCPCB assembly as "economic assembly" is no longer an option with this part in the component list.
Any possible solutions or do we just have to bear the added cost now?

It’s possible that ESP-12F is no longer supported because it may get damaged under economic PCBA. Here are three solutions:

Since ESP-12F is not too difficult to solder, if you have a soldering iron or heat plate, you might choose to skip PCBA assembly and assemble it yourself (though this may require extra time).

There are still ESP-12F modules that can be used with economic PCBA, such as C784365 or C19949064. However, these are generally out of stock. You can use global sourcing or similar options to purchase them and have them sent to your personal warehouse at JLCPCB, then select them as replacements during PCBA.

Based on feedback from many DIY enthusiasts, using economic PCBA assembly can increase the DOA (Dead on Arrival) rate, with extreme cases reporting a DOA rate as high as 20/30. So if you are unable to repair PCBs yourself, it’s better to opt for standard PCBA, which will save you from a lot of hassle.

Appreciate the response, will look into all available options


Ufunc support

Description
Add support for overloading ufuncs and their methods (like accumulate).
Fixes #23
PR Checklist

[ ] Check out the contributing guidelines and code of conduct
[ ] Check out the contributing workflow ( for a practical example click here )
[ ] Give a detailed description of the PR above.
[ ] Document changes in the CHANGES.rst file. See existing changelog for examples.
[ ] Add tests, if applicable, to ensure code coverage never decreases.
[ ] Make sure the docs are up to date, if applicable, particularly the docstrings and RST files in docs folder.
[ ] Ensure linear history by rebasing, when requested by the maintainer.

@mhvk, obviously still a work in progress, but I've solved the ufunc overloads. And it still compiles with mypyc. https://overload-numpy--25.org.readthedocs.build/en/25/

@nstarman - in principle sounds interesting but sadly having limited time to actually look at this -- probably better to meet in person at some point.
But obviously, if this makes things like adding two quantities quite a lot faster, that would be great! I'm not sure that for Quantity, __array_ufunc__ itself is the main bottleneck, but the unit handling stuff can perhaps be compiled too? Anyway, would indeed be good to benchmark...

Codecov is erroneously counting TYPE_CHECKING and ... lines against the code coverage. When I run this locally, the coverage is 92%, which is expected. I'll fix the codecov error in a later PR.


Unified api groundwork

This pr contains the groundwork needed to begin deduplicating and centralizing the two api trees:

disable log output for regular cli commands (so we can keep log statements in the registry api code)
Use a shared interface and implementation for http roundtripping
move daemon/registry to registry
embed registry.Client in api.Client. From here, the next PR can start removing implementations from api.Client and allow the underlying registry.Client implementation to kick in.

LGTM


JavaScript warning with auto play carousel, which prevents rest of the page to render.

When trying to render some dynamic content than image using carousel, most of the times, I encounter following issue.
"Warning: setState(...): Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op."
from call stack:
play() and then
this.setState({
animating: true,
currentSlide: targetSlide
}, function () {
ReactTransitionEvents.addEndEventListener(this.refs.track.getDOMNode().children[currentSlide], callback);
});

This has been fixed in #101

Published 0.6.7 version on npm with fix


profile title changes, css fixes

patient profile title changes, address this story:
https://www.pivotaltracker.com/story/show/150118632
for patient profile title:

use name if available, otherwise use email
css fixes
fix email saving (for no email)

Sorry I didn't get a chance to talk to you about your new commit- should be good to merge now :+1:

@ivan-c
Ivan, ignorance on my part but how come the user's name doesn't need to be enclosed in trans tag?  ( it was originally assigned to a variable in the trans tag).  I saw your change, that is why I ask.  Will it be translated correctly?

This should be ready for merging.  @ivan-c Ivan, please ignore my previous comment.  I did chat with Paul about it.


In updateIndicator function, fromIndex and toIndex are inverted on left swap

In the following method, called when we swap or press one of the bar buttons, when we navigate to the left the 'fromIndex' and 'toIndex' are inverted ...
override func updateIndicator(for viewController: PagerTabStripViewController, fromIndex: Int, toIndex: Int, withProgressPercentage progressPercentage: CGFloat, indexWasChanged: Bool)

For example, if we have 3 ViewControllers [V1][V2][V3], and we are on [V3] and either swap to [V1] or press the button in the button bar we will have {fromIndex = 1 : toIndex = 2} then {fromIndex = 0 : toIndex = 1}

Closing, this issue is fixed in the current version.


New Feature Request - Allow use of macros

Others are asking for the ability to save/load code snippets, which would be fantastic.  This request is of a similar nature in that it would be great to have access to Syntax Editor Macros within Xplore.
Thanks.

Noted. Closing as duplicate of #27


Entire set of Boost Libraries (Work in Progress)

Hi all! I'm working on adding all the boost libraries, still got a bit to do before my mess will be useful to anyone else to help with, but had a few people asking so wanted to get this up here so others can start to look through. No action required right now, will update as I progress!
Note:
Check out boost.rules.tools which is where all the common utilities used by all the modules is, plus some super handy maintenance tools. Probably not super helpful until I finish the readme though, sorry!
Credit to https://github.com/nelhage/rules_boost and https://github.com/Vertexwahn/rules_boost/tree/add-bzlmod-support which both provided inspiration and help with parts of the code.
Fixes #292 and Fixes #787

Hey just wondering what the best way to point source urls to git tags is? I've done for example "https://github.com/boostorg/safe_numerics/archive/refs/tags/boost-1.83.0.tar.gz", but looks like that errors out as an unstable url. Looking at how other modules are done, it uses urls like "https://github.com/aspect-build/bazel-lib/releases/download/v1.34.2/bazel-lib-v1.34.2.tar.gz". I don't think we can get these for the boost libraries though, as they have tags, but not releases?

Hey just wondering what the best way to point source urls to git tags is? I've done for example "https://github.com/boostorg/safe_numerics/archive/refs/tags/boost-1.83.0.tar.gz", but looks like that errors out as an unstable url. Looking at how other modules are done, it uses urls like "https://github.com/aspect-build/bazel-lib/releases/download/v1.34.2/bazel-lib-v1.34.2.tar.gz". I don't think we can get these for the boost libraries though, as they have tags, but not releases?

There isn't, unfortunately GitHub doesn't provide a way to get a stable source archive without manual maintainer effort. This is a widespread issue and we will have to find a better solution to this, but for now all we can do is apply a, unfortunately very common, exception (see the label I added).

CI/CD pipeline is happy to build now! Looks like we've got 13 modules not building, that's what I was getting in my local testing too. They are the ones I haven't gotten around to yet, mostly the tricky ones like beast and log. I'll hopefully sort out the tests so the ones that are building have matching test suites and can be verified working, then will get onto the last few that aren't at build stage yet.

Been working on boost.rules.tools and boost.rules to solve a few requests and make it super easy to contribute to maintaining or working on these modules. For anyone wanting to help out with this PR, check it out!
See This Thread for some discussion about the benefits of this system.

Task List
Fix Compiling issues

[ ] boost.test
[ ] boost.align
[ ] boost.log
[ ] boost.property_map.parallel
[ ] boost.mpi
[ ] boost.beast
[ ] boost.wave
[ ] boost.iostreams
[ ] boost.numeric.odeint
[ ] boost.graph.parallel
[ ] boost.locale
[ ] boost.python
[ ] boost.parameter_python
[ ] boost.local_function
[x] The rest are compiling!!

Potentially needs work (reference their cmakelists.txt and compare to what BUILD.bazel file is doing)

[ ] Add asio SSL!
[ ] atomic
[ ] filesystem
[ ] gil (+ extra optional deps)
[ ] hof
[ ] math
[ ] callable_traits
[ ] chrono
[ ] compute
[ ] hana
[ ] iostreams
[ ] json
[ ] nowide
[ ] stacktrace
[ ] url

Random TODO:

[ ] Make WINAPI boost only
[ ] make config_settings boost only (same package list as winapi)
[ ] iostreams: Other external deps
[ ] Work out what flags to provide based on compiler abilities. See results of boost.config test to see what works or doesn't in your compiler. How do we provide the right flags per compiler? Maybe this should be run automatically as a macro/dep of every target??
[ ] (boost.accumulators) p_square_quantile_extended test should use extended_p_square_quantile.hpp ??
[x] Remove default visibilities - they are done in boost_library
[ ] Enforce cxx minimum versions on particular libs. (Should we enforce a higher like 20 when extra features are available with that version?)
boost.geometry --cxxopt='-std=c++14'
boost.hana --cxxopt='-std=c++14'
boost.stl_interfaces --cxxopt='-std=c++14'
boost.histogram --cxxopt='-std=c++14'
boost.pfr --cxxopt='-std=c++17’
boost.spirit --cxxopt='-std=c++17’

Tests Passing (hence fully operational and ready to be used)

[ ] bazel test @boost.accumulators//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.algorithm//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.align//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.any//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.array//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.asio//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.assert//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.assign//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.atomic//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.beast//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.bimap//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.bind//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.callable_traits//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.chrono//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.circular_buffer//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.compute//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.concept_check//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.config//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.container//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.container_hash//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.context//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.contract//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.conversion//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.convert//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.core//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.coroutine//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.coroutine2//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.crc//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.date_time//test:tests --test_verbose_timeout_warnings -k
[ ] bazel test @boost.describe//test:tests --test_verbose_timeout_warnings -k
[x] bazel test @boost.detail//test:tests --test_verbose_timeout_warnings -k
[ ] TODO - add tests for the rest of the libs

Tests Not Needed:

boost.compatibility

Test Notes

Test results here are on my local machine (Apple Arm M2 pro, Ventura). Some may fail in CI/CD when being built cross platform, we will have to re-check after the tests are run in the pipeline.
A lot of the tests are failing due to boost.test not linking properly. That needs some work in the BUILD.bazel file.

Testing Process
I've been iteratively doing the cycle of:

Run test for a module
Fix issues
Update patches using interactive script in boost.rules.tools
bazel clean --expunge
(Repeat)

I've also been doing this with a .bazelversion file with 6.4.0 as bazel 7.0.1 has not been clearing caches for me properly. I literally have not found a way (even manually deleting cache files) for it to actually realise the hash and module has been updated, even though the module version from the local repository is the same. Weird and highly annoying, I would've though bazel clean --expunge would get rid of everything, but apparently not with my config🤷♀

You need to set --lockfile_mode=off in addition to using bazel clean --expunge if you use a local registry.
Since Bazel 7 raised the C++ default to C++17, setting flags on individual libraries may not be necessary anymore. Fixed flags could lead to differing C++ standards across the build.

Since Bazel 7 raised the C++ default to C++17, setting flags on individual libraries may not be necessary anymore. Fixed flags could lead to differing C++ standards across the build.

@fmeum Just for the records: If I use Bazel 7.0.2 the default C++ standard is C++14. If I use 8.0.0-pre.20240108.6 the default C++ Standard is C++17 (tested on Ubuntu 22.04)

Hello @Vertexwahn, modules you maintain (xz) have been updated in this PR. Please review the changes.

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (boost.accumulators, boost.algorithm, boost.align, boost.any, boost.array, boost.asio, boost.assert, boost.assign, boost.atomic, boost.beast, boost.bimap, boost.bind, boost.callable_traits, boost.chrono, boost.circular_buffer, boost.compatibility, boost.compute, boost.concept_check, boost.config, boost.container, boost.container_hash, boost.context, boost.contract, boost.conversion, boost.convert, boost.core, boost.coroutine, boost.coroutine2, boost.crc, boost.date_time, boost.describe, boost.detail, boost.dll, boost.dynamic_bitset, boost.endian, boost.exception, boost.fiber, boost.filesystem, boost.flyweight, boost.foreach, boost.format, boost.function, boost.function_types, boost.functional, boost.fusion, boost.geometry, boost.gil, boost.graph.parallel, boost.graph, boost.hana, boost.heap, boost.histogram, boost.hof, boost.icl, boost.integer, boost.interprocess, boost.intrusive, boost.io, boost.iostreams, boost.iterator, boost.json, boost.lambda, boost.lambda2, boost.leaf, boost.lexical_cast, boost.local_function, boost.locale, boost.lockfree, boost.log, boost.logic, boost.math, boost.metaparse, boost.move, boost.mp11, boost.mpi, boost.mpl, boost.msm, boost.multi_array, boost.multi_index, boost.multiprecision, boost.nowide, boost.numeric.conversion, boost.numeric.interval, boost.numeric.odeint, boost.numeric.ublas, boost.optional, boost.outcome, boost.parameter, boost.parameter_python, boost.pfr, boost.phoenix, boost.poly_collection, boost.polygon, boost.pool, boost.predef, boost.preprocessor, boost.process, boost.program_options, boost.property_map.parallel, boost.property_map, boost.property_tree, boost.proto, boost.ptr_container, boost.python, boost.qvm, boost.random, boost.range, boost.ratio, boost.rational, boost.regex, boost.rules.tools, boost.safe_numerics, boost.scope_exit, boost.serialization, boost.signals2, boost.smart_ptr, boost.sort, boost.spirit, boost.stacktrace, boost.statechart, boost.static_assert, boost.static_string, boost.stl_interfaces, boost.system, boost.test, boost.thread, boost.throw_exception, boost.timer, boost.tokenizer, boost.tti, boost.tuple, boost.type_erasure, boost.type_index, boost.type_traits, boost.typeof, boost.units, boost.unordered, boost.url, boost.utility, boost.uuid, boost.variant, boost.variant2, boost.vmd, boost.wave, boost.winapi, boost.xpressive, boost.yap, boost, zstd) have been updated in this PR. Please review the changes.

Oh oops. Sorry @Vertexwahn, ignore this plz

Closing this PR for the moment due to reorganising branches on my repo


Handle assignment to shared object in Lint/UselessSetterCall

When a local variable is assigned to a shared object, the referenced object is effectively no longer local, so calling a setter method on it might very well be useful and should not be reported as an offense.

What's the high level idea to discern a non-local object from a local one? Looking at the tests - those examples could have just as easily been non-shared objects as well.

The idea is that setting something inside a method-local object is useless but if the object can be accessed from outside the method, then the setter call might be useful and shouldn't be reported.

those examples could have just as easily been non-shared objects as well

We can only detect that that some_lvar refers to an object that's accessible from outside the method. Whether the object is actually being accessed is unknown, so there could be false negatives. I'm not sure if that's what you meant, @bbatsov.

@bbatsov Did that answer your question? I tried to clarify, but maybe I'm missing something.

We can only detect that some_lvar refers to an object that's accessible from outside the method.

I don't think we can actually detect this - we can only assume that it's an object that's accessible outside the method. After all you can't know if a method returns some shared object or something else, right?

I see what you mean now, and you're right. We're can't know if it's a shared object. But it could be and we want to err on the side of caution and avoid false positives at all costs.
So I want to keep the logic as it is but maybe clarify in the code about the possibly shared objects?

I honestly don't know. I'm leaning towards just ignoring that problem and leaving the code as it is. I don't think that many people ran into that particular issue anyways. Perhaps we should just document the shortcomings of the cop better?


Reg : Adding Custom Pin Image

Hi Team,
I added custom pin image and getting following error in out put window. Here is the error details.
11-12 14:53:44.133 W/View    ( 5147): requestLayout() improperly called by md5497d5d63940cc55d309adb7f5044b052.AnimationNavigationRenderer{ee9c98e V.E...C.. ......ID 0,48-768,1184 #3} during second layout pass: posting in next frame
An unhandled exception occured.
11-12 14:53:45.166 W/DynamiteModule( 5147): Local module descriptor class for com.google.android.gms.googlecertificates not found.
11-12 14:53:45.166 W/DynamiteModule( 5147): Failed to load module via V2: java.lang.ClassNotFoundException: Didn't find class "com.google.android.gms.dynamite.DynamiteModule$DynamiteLoaderClassLoader" on path: DexPathList[[zip file "/data/app/com.AROMTKMAP-1/base.apk"],nativeLibraryDirectories=[/data/app/com.AROMTKMAP-1/lib/x86, /data/app/com.AROMTKMAP-1/base.apk!/lib/x86, /vendor/lib, /system/lib]]
11-12 14:53:45.167 I/DynamiteModule( 5147): Considering local module com.google.android.gms.googlecertificates:0 and remote module com.google.android.gms.googlecertificates:2
11-12 14:53:45.167 I/DynamiteModule( 5147): Selected remote version of com.google.android.gms.googlecertificates, version >= 2
Can you please help me with this?
Thanks,
Sakthi

please make sure your Android SDKs are up-to-date.

No solution? Exact same problem here... google play services 8.1.0


Support for S3A Connector

Currently conntroller and servers able to start with s3a path but while creating the segments during ingestion facing following error. The reason is while preparing file names we are prefixing the s3 scheme instead of s3a.
This will be useful to make use s3 compatible storages as a deep store.
Working on it.
Caused by: java.lang.IllegalStateException: Unable to extract out the relative path for input file 's3://testhadoop/pinot/batch/airlineStats/rawdata/2014/01/28/airlineStats_data_2014-01-28.avro', based on base input path: s3a://testhadoop/pinot/batch/airlineStats/rawdata/
at org.apache.pinot.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:515) ~[pinot-all-1.2.0-jar-with-dependencies.jar:1.2.0-cc33ac502a02e2fe830fe21e556234ee99351a7a]
at org.apache.pinot.common.segment.generation.SegmentGenerationUtils.getRelativeOutputPath(SegmentGenerationUtils.java:162) ~[pinot-all-1.2.0-jar-with-dependencies.jar:1.2.0-cc33ac502a02e2fe830fe21e556234ee99351a7a]
at org.apache.pinot.plugin.ingestion.batch.standalone.SegmentGenerationJobRunner.lambda$submitSegmentGenTask$1(SegmentGenerationJobRunner.java:278) ~[pinot-batch-ingestion-standalone-1.2.0-shaded.jar:1.2.0-cc33ac502a02e2fe830fe21e556234ee99351a7a]
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) ~[?:?]
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) ~[?:?]
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) ~[?:?]
at java.base/java.lang.Thread.run(Thread.java:840) ~[?:?]
java.lang.RuntimeException: Caught exception during running - org.apache.pinot.plugin.ingestion.batch.standalone.SegmentGenerationJobRunner
at org.apache.pinot.spi.ingestion.batch.IngestionJobLauncher.kickoffIngestionJob(IngestionJobLauncher.java:152)
at org.apache.pinot.spi.ingestion.batch.IngestionJobLauncher.runIngestionJob(IngestionJobLauncher.java:125)
at org.apache.pinot.tools.admin.command.LaunchDataIngestionJobCommand.execute(LaunchDataIngestionJobCommand.java:132)
at org.apache.pinot.tools.Command.call(Command.java:33)
at org.apache.pinot.tools.Command.call(Command.java:29)
at picocli.CommandLine.executeUserObject(CommandLine.java:2045)
at picocli.CommandLine.access$1500(CommandLine.java:148)
at picocli.CommandLine$RunLast.executeUserObjectOfLastSubcommandWithSameParent(CommandLine.java:2465)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2457)
at picocli.CommandLine$RunLast.handle(CommandLine.java:2419)
at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:2277)
at picocli.CommandLine$RunLast.execute(CommandLine.java:2421)
at picocli.CommandLine.execute(CommandLine.java:2174)
at org.apache.pinot.tools.admin.PinotAdministrator.execute(PinotAdministrator.java:173)
at org.apache.pinot.tools.admin.PinotAdministrator.main(PinotAdministrator.java:204)
Caused by: java.lang.RuntimeException: Failed to generate Pinot segment for file - s3://testhadoop/pinot/batch/airlineStats/rawdata/2014/01/28/airlineStats_data_2014-01-28.avro
at org.apache.pinot.plugin.ingestion.batch.standalone.SegmentGenerationJobRunner.lambda$submitSegmentGenTask$1(SegmentGenerationJobRunner.java:287)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: java.lang.IllegalStateException: Unable to extract out the relative path for input file 's3://testhadoop/pinot/batch/airlineStats/rawdata/2014/01/28/airlineStats_data_2014-01-28.avro', based on base input path: s3a://testhadoop/pinot/batch/airlineStats/rawdata/
at org.apache.pinot.shaded.com.google.common.base.Preconditions.checkState(Preconditions.java:515)
at org.apache.pinot.common.segment.generation.SegmentGenerationUtils.getRelativeOutputPath(SegmentGenerationUtils.java:162)
at org.apache.pinot.plugin.ingestion.batch.standalone.SegmentGenerationJobRunner.lambda$submitSegmentGenTask$1(SegmentGenerationJobRunner.java:278)
... 5 more

Hello! I’m currently studying Computer Science, and I’m very interested in contributing to open-source projects. I'm eager to learn, apply my skills, and collaborate with the community. If there are any tasks or areas where I could get started, please let me know. Thank you

@chrajeshbabu  Thanks

@Jackie-Jiang  @mayankshriv help me contribute to this community

Support added in #14474


Docstring section warning with NumpyDoc 1.2

Documentation build for the dependabot branch to update NumpyDoc to 1.2 is failing with a warning, it looks as though the expected order for docstring sections may be enforced more strongly:

We should fix this before merging the dependabot branch

See this PR: https://github.com/numpy/numpydoc/pull/302


move #ifdefs used to enable or disable features from function scope t…

…o file scope
Takes the #ifdefs used to disable and enable features like filesystem logging, ESP-NOW, LoRa, Debug, WiFi, etc. from function by function to including or excluding entire header files thus being a cleaner or more straightforward and simpler approach.

After modifying the code I went though and made sure all examples compiled using Arduino 1.8.19.  I went through the config files and commented and uncommented the USE_xxx features out and compiled different combinations to make sure all the code works.

Awesome, thanks! That's gonna make things a lot simpler. I'll get this in before the release, which I'm hoping to do tomorrow.

ESP8266 does not like your const changes in ESP-NOW.

Thanks for testing.  I tested against ESP32 board only.   Guess I will have to test ESP8266 in the future.  I've been wondering if there are some automated compile tests that can be done to make sure changes compile against all configurations and all platforms.  I'm not sure if that's called unit testing or what that automated testing would be called.  I gotta believe there is a way to set that up.

After I finish making these timekeeping changes I'll go back and compile against ESP8266 and update this PR.

No rush... I'm not going to finish up tonight so I won't get around to pulling it until tomorrow afternoon.

I gotta believe there is a way to set that up.

Maybe with Arduino CLI and a batch file? That would be really handy.
Actually... I should look into that in general to streamline my process of editing in the git folder, drag/copy to Arduino folder, click confirm, then clicking compile in Arduino IDE. It's not too bad til you have to fix three small errors in a row and suddenly want to give up 😅

Fixed issue with const declaration in commit https://github.com/timmbogner/Farm-Data-Relay-System/pull/144/commits/9b5323e447870e7672bccaa8290489dcfc72594d


Add line chart JavaScript to Chart Block

Updates the chart block from PRs #2657 and #2656, for entering metadata to generate d3 charts for the Consumer Credit Trends pages. This PR adds JS for the line charts to render based on the fields from the Wagtail block.
Content entered in the Chart Block fields will replace the metadata that currently powers the charts in this file: https://github.com/cfpb/consumer-credit-trends/blob/master/src/static/js/templates/charts.js
This will allow our product owner to enter and manage the content for each chart.
Additions

Atomic chart organism JavaScript, based on JS from consumer-credit-trends line.js, including dependencies
In the spirit of iterative updates, this PR includes the Line Chart code only, for easier review. Subsequent PR's should be submitted to add the Bar + Tile Map charts.
chart.less adds styles from  consumer-credit-trends charts.less, with updated atomic class names
New Wagtail block fields required to make the JavaScript render each chart. These include what type of chart to load (this can be used later to determine which JS file to call), and the group property, which is used to filter data for many line charts.

Removals

elementID field from Chart Block. We don't want to rely on an ID for each chart to render any longer, so this is a step towards that. The JS now expects a matching title + class name instead of the ID. This will require manually updated migration.

Changes

chart.html template class names have been atomicized to match project conventions
The original helper functions in the  consumer-credit-trends line.js assume that no chartInfo.group property is defined for charts that don't need it. Because this updated JS grabs the group property from the HTML data attribute, group property will exist for all charts.
Another note about groups. Right now the JS expects the following properties for certain types of graphs. We can probably do the data munging/filtering on the Jenkins job that @contolini and @hillaryj are working on for these, instead of in the JS:

Origination activity, number/volume line charts: no group
Origination activity, year over year number/volume bar charts: "Number of loans" or "Dollar Volume"
Borrower Risk Profiles, Line charts: Credit score group (Subprime, prime, etc)
Income level line charts: income group (low, moderate, etc)
Borrower age line charts:  age group (younger than 30, 30-44, etc)

Testing

check out and create a "Chart block" element on a browse page to test the fields display on the page.
add required fields, use screenshot below and charts.js properties as a guide
test that multiple line charts can be added to a page
test that colors of line charts match the report type specified in the CSS

Screenshots
Wagtail admin fields

Chart on browse page front end

Todos
For this PR, my goals are to:

[x] get the JavaScript for a line chart to render svgs for multiple charts on the page
[x] use the data attributes output on the page HTML to target JS for each graph
[x] whittle the admin fields for Chart Block so we only use those necessary for charts to render

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[ ] Reviewers requested with the Assignee tool :arrow_right:

Closing in favor of #2688.


fix(dependencies): 💫 update dependencies

Description
Update dependencies.  notify-debouncer-mini required two small code changes, removing a no longer needed argument in new_debouncer call.
Fixes #48
Type of change

[X] Dependency update

How Has This Been Tested?

[X] cargo test run with all tests passing

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] I have added tests that prove my fix is effective or that my feature works
[X] New and existing unit tests pass locally with my changes
[X] Any dependent changes have been merged and published in downstream modules

Current dependencies on/for this PR:

main

PR #49   👈

This comment was auto-generated by Graphite.

Merge Activity

Aug 28, 3:15 AM: @rodneylab started a stack merge that includes this pull request via Graphite.


autoversion: Support CSS selectors

autoversion currently only supports XPath for searching for versions
in an HTML page.
This works great, but CSS selectors are arguably
more approachable for newcomers, and more widely understood.
This change adds support for CSS selectors to autoversion
using the github.com/andybalholm/cascadia package (BSD2 licensed)
for matching them.
To fit that in, this extracts the search logic into a new abstraction
called htmlMatcher with an implementation for XPath and one for CSS.
Following this change, you can do something like the following:
auto-version {
  html {
    url = "https://example.com"
    css = "div.version"
  }
}

It is invalid to specify both xpath and css
in the same auto-version block.

That's awesome! I originally chose XPath because it's much more powerful, allowing selection of regex subgroups, among other things. But I think you're right, CSS is much more approachable and should be fine for most use cases.


Why will this issue section be closed?

I understand that responding to all the issues raised is a lot of work but I do not see any valuable reasons why the issue section should be closed. Not everyone in the community has the ability to contribute in terms of coding, yet it is important to provide a publicly visible area to discuss issues (bugs, suggestions, problems) related to the use of SoftEtherVPN. Only referring to pull requests or e-mail contact is not an acceptable practice. I encourage you to reconsider. Thank you.

My guess is that the goal is not be to discourage issue reporting. Rather, an attempt to force people to write code to fix the bugs as a part of the public reporting process.

For the "Issues" forum:
Currently, this project has two duplicated forums: Issues and VPN Users Forum. The actual usage of both forums are very similar. It is very inefficient for users to seek for / post to both forums to ask questions or post feature requests.
The VPN Users Forum has been active before I created this GitHub repository. Spam posts are bothering. While there is a problem of spam posts, spams are periodically removed, and the forum has some anti-spam script features to avoid them as possible.

xortim,

an attempt to force people to write code to fix the bugs as a part of the public reporting process.

In my thought, forcing people to write code is not a good idea. It is impossible to "force" people to work. Every person can gently request to other person to write a code (or do something). However, any person may not "force" to other person to do something for a speficic person or a group of people, even for public interests.

For issue posting, discussion and pull requests processing on the project, I'd like to discuss about them on the https://github.com/SoftEtherVPN/SoftEtherVPN/issues/268 page.

@dnobori - thanks for your reply. I apologize if I gave the wrong impression. Force is a little hyperbolic, but rather encourage people to author code alongside their bug reports :)

Co new maintener wanted
https://github.com/SoftEtherVPN/SoftEtherVPN/issues/341


Maven artifacts added with a uri have classifier and version switched

System information:

DBeaver version 21.3.0

Describe the problem you're observing:
We actually have three problems here:

[x]  Wrong classifier and version
[x]  Raw as a name of the tab is confusing
[x]  Manual as a name of the tab is confusing
[x]  We need an info label on how it can be used

I want this in 21,3 versions of commercial products badly.

Can't add more than one artifact with maven declaration

Also now artifacts can't be edited

Verified


The bro is empty :(

While searching for agnostig ways to have my own rag with ollama, I ended up here but the bro is empty :(
Do you have a sample you plan to commit some tims?

give me a few days. :).

here is the first version with gui @kucukkanat .


https://router.vuejs.org/   can't open

Version
2.6.0
Reproduction link
https://router.vuejs.org/
Steps to reproduce
https://router.vuejs.org/   can't open
What is expected?
Web page display normally
What is actually happening?
Web page display exception

Please repair it as soon as possible.  It's seriously

it works. It must be something on your end blocking it


Election test TestUnsupportedElectionParams() is expecting the incorrect reason code

In this test, an election id is sent in all primary mode.  According to the gribi.proto file:
    // If the server is currently operating in ALL_PRIMARY mode the server
    // should return an error specifying ELECTION_ID_IN_ALL_PRIMARY reason. The
    // status (canonical error code) should be FAILED_PRECONDITION.

But the test is currently expecting fluent.ParamsDifferFromOtherClients.  Shouldn't this be fluent.ElectionIDNotAllowed?

Thanks for catching this, yes -- this looks to be a copy&paste error. Will submit a fix.


MAC check Failed.

I can encrypt and decrypt data in Java but if I encrypt data in Java then I can't decrypt it in PHP and I get MAC check failed error.
Java Code:
AesEncryption aes = new AesEncryption("cbc", 256);
byte[] encryptedData = aes.encrypt("Hello", "PASSWORD");
String encryptedString = new String(encryptedData);

Now when I try to decrypt encryptedString in PHP using the same password, I get this error:
MAC check failed!

I can't reproduce the error (with java version "17.0.1" and PHP 7.4.27). For example, the code below works fine,
Java
    AesEncryption aes = new AesEncryption("cbc", 256);
    byte[] encryptedData = aes.encrypt("Hello", "PASSWORD");
    System.out.println(new String(encryptedData));

    //JnTRpJ2ql5ATHmiRWJsAO8Ek6DDLiAy/9HV0EncIPzFFfY4FnytwCQFvcb5z/lms1mp0VBP6w02SJLHW2BpycUZMD0vioTx96LzkEnmRZNU=

PHP
    $aes = new AesEncryption("cbc", 256);
    $ct = 'JnTRpJ2ql5ATHmiRWJsAO8Ek6DDLiAy/9HV0EncIPzFFfY4FnytwCQFvcb5z/lms1mp0VBP6w02SJLHW2BpycUZMD0vioTx96LzkEnmRZNU=';
    $pwd = "PASSWORD";
    var_dump($aes->decrypt($ct, $pwd));

    //string(5) "Hello"

Could you give me you Java and PHP versions, and a more detailed example of code usage and output?

Tested using both PHP v7.4.25 and v7.4.3.
Java (Microsoft Build of OpenJDK):
java --version
openjdk <IP_ADDRESS> 2022-08-12 LTS
OpenJDK Runtime Environment Microsoft-40354 (build <IP_ADDRESS>+1-LTS)
OpenJDK 64-Bit Server VM Microsoft-40354 (build <IP_ADDRESS>+1-LTS, mixed mode, sharing)

Anything I encrypt in Java I cannot decrypt in PHP as it fails with MAC check failed error, however, anything I encrypt in PHP I can decrypt in Java.
Java:
AesEncryption aes = new AesEncryption("cbc", 256);
byte[] encryptedData = aes.encrypt("Hello", "PASSWORD");
System.out.println(new String(encryptedData));

//Rj65uM9cRkuGNdggFf4gUTUkF5G+HINn4Gp+4CBhRS481uMAvhvk4OmEUejkfDps0kcyvJLhGHj3QLp3uq794up9Uol/nsiXdApzOoxY0yc=

PHP
$aes = new AesEncryption("cbc", 256);
$ct = 'Rj65uM9cRkuGNdggFf4gUTUkF5G+HINn4Gp+4CBhRS481uMAvhvk4OmEUejkfDps0kcyvJLhGHj3QLp3uq794up9Uol/nsiXdApzOoxY0yc=';
$pwd = "PASSWORD";
var_dump($aes->decrypt($ct, $pwd));

//MAC check failed!NULL

Thanks for all the details. Unfortunately, I still can't reproduce the error. Your Java ciphertext decrypts fine with PHP in my environment. Can you do me a favor? Can you remove verification (comment out https://github.com/tasos-py/AES-Encryption-Classes/blob/master/AesEncryption.class.php#L109), to see what the plaintext looks like?

I get:
Padding is invalid!NULL

when I comment out the following line:
$this->verify($iv.$ciphertext, $mac, $macKey);

Any suggestions or ideas are welcomed. I would be happy to debug this issue in any way you wish.

AES-Encryption-Classes is quite stable and helpful library. I have tested encryption decryption using C++ and PHP and it work flawlessly. However, in case of Java and PHP I face the issue mentioned above.

I don't get this issue on my PC, so I really appreciate you helping me in debugging. So, now we know the problem is somewhere in padding. Could you replace Cipher.unpad(), https://github.com/tasos-py/AES-Encryption-Classes/blob/master/AesEncryption.class.php#L486 with the code bellow?
    private function unpad($data) {
        $pad = ord(mb_substr($data, -1, 1, "8bit"));
        $count = substr_count(mb_substr($data, -$pad, $pad, "8bit"), chr($pad));

        var_dump(bin2hex($data));
        var_dump($pad);
        var_dump($count);

        if ($pad < 1 || $pad > 16 || $count != $pad) {
            throw new RuntimeException("Padding is invalid!");
        }
        return mb_substr($data, 0, -$pad, "8bit");
    }

This should show us the last block, pad and pad length. It should be
string(32) "48656c6c6f0b0b0b0b0b0b0b0b0b0b0b"
int(11)
int(11)

Here is the output:
string(32) "e74851067cc8f5195e6b27b802770ee9" int(233) int(1) Padding is invalid!NULL

Actually, the problem is not padding, because MAC check happens before decryption. It's either in key generation or data slicing. Please go to https://github.com/tasos-py/AES-Encryption-Classes/blob/master/AesEncryption.class.php#L108 and add those lines,
            var_dump($salt);
            var_dump($iv);
            var_dump($ciphertext);
            var_dump($mac);
            var_dump($aesKey);
            var_dump($macKey);

Snapshot for reference:

string(16) "1234567890123456" string(16) "1234567890123456" string(16) "<������Q��|:l" string(32) "�G2���x�@�w�����}R��ȗt s:�X�'" string(32) "��}�ԣ�6�v�v�yY�{��2�&8�Mv� �" string(32) "������u��>ܬ����]�s�r���d a��" string(32) "e74851067cc8f5195e6b27b802770ee9" int(233) int(1) Padding is invalid!NULL

Updated previous comment with required changes.

Updated previous comment with required changes.

I am ashamed to take up so much of your precious time even though the mistake was on my part. I had accidentally hardcoded the salt and iv.

@tasos-py Thank you very much for your valuable time. I am very grateful to you.
Programmers like me are forever in your debt for such a great library!

Glad to hear that! I'll be closing this issue now, since it's just a typo basically. And don't worry about it, those things happen all the time


"Cypress could not verify that this server is running"

The server is running and accessible at the URL set in the baseUrl config property; what mechanism is used to test and verify availability?

I found and reviewed cypress-io/cypress#3122: I’m not spinning up a local environment, it’s a website on the World Wide Web.

Well how exciting, another GitHub repository that's unmaintained. 😞 👎

I'm having the same problem :(

Closing, since this issue is stale and sorry for your experience. I wasn't involved at the time.
If there are still current problems then please submit a new issue with relevant details. Alternatively there is an active user community on
 (click on button)


Add a website link in Remote Jobs Section

I have added a remote job website link named NoDesk → https://nodesk.co/

@mrdanishsaleem There are a ton of merge conflicts in this PR. Can you please submit a new one, and please check the PR before submitting it? Thanks!


Marshalling based on instance-variable dumping for primitive types is surprising to the user

Psych currently attempts to use a special-case strategy for marshalling primitive objects when they have instance variables defined within them.
require 'psych'; Psych.dump("foo".tap { |s| s.instance_variable_set(:@bar, 88) })
#=> "--- !ruby/string\nstr: foo\nbar: 88\n"

Here's an (admittedly contrived) example of the kinds of problems that can happen.
require 'psych'
s = "foo"
s.instance_variable_set(:@str, 88)
Psych.load(Psych.dump(s)) #=> 88

For a real world example, see issue #216.
I would argue that this behavior is surprising, and should be opt-in only with a flag the user can specify on Psych.dump.  Ruby objects of a class that does not correspond directly to a YAML primitive could still be serialized implicitly (including subclasses of a class that corresponds to a primitive, as requested in issue #43).
If we can agree on how to proceed, I'm happy to do the work of crafting a PR.

Going through the source to work on the PR here, I've noticed that psych already distinguishes between Array and subclasses of Array.
https://github.com/tenderlove/psych/blob/47adf879591570daebde62895b3712c216710661/lib/psych/visitors/yaml_tree.rb#L423-L431
So hopefully we can agree to treat Strings and Hashes this same way?  I'll craft a PR.


Handle cases where KillBillClient is not configured

/cc @pierre Added https://github.com/killbill/killbill-bridge-plugin/pull/11/commits/2d4d59a8eae19dda66effab1da415de686742484 -> Had don't allow to have a null config (either we need a per-tenant config or a global config, otherwise NPE...)

If this looks fine, i'll merge and re-archive...


Scripture pane in TQ-TSV

Found that scripture pane is missing for the TQ TSV format.
It would be good to have consistency throughout the TSV resources to have scripture pane displayed.

Looks good in translationCore Create - v1.4.0-rc.3 build 104-85b41fb. Scripture pane is available in TQs.


CC Free Tier / CC dedicated docs for bulk features

Closes #10799
Pulled in examples for CockroachCloud Free Tier and CockroachCloud in the CockroachCloud docs hierarchy.
Also added the userfile examples for BACKUP to the current userfile storage doc.

This change is

Hey @mwang1026 @amruss @livlobo , could you review these new docs particularly for the examples per the CC tier?
As per the original issue, I have not included EXPORT in the free tier, but did you want me to document the alternative process?
Thanks!

cc @mikeCRL

FYI Here is the preview link to the new page: https://deploy-preview-10945--cockroachdb-docs.netlify.app/docs/cockroachcloud/run-bulk-operations.html

Only core changefeeds are available on CockroachCloud Free Tier. An enterprise license is required to create a changefeed into a configurable cloud storage sink, Kafka, etc.

I think this is a little confusing - at the moment you must use Cockroach Cloud dedicated to get enterprise changefeeds. You can't just buy an enterprise license and have them enabled on your free tier cluster.

In the changefeed example:

CREATE CHANGEFEED FOR TABLE name, name2, name3
INTO 'experimental-scheme://host?parameters'
WITH updated, resolved;

We should probably use 'experimental-s3' instead of 'experimental-scheme' since we say we are using s3, we are using s3 in all of the other examples, and it's not obvious that you should replace "scheme" with "s3"

Only core changefeeds are available on CockroachCloud Free Tier. An enterprise license is required to create a changefeed into a configurable cloud storage sink, Kafka, etc.

I think this is a little confusing - at the moment you must use Cockroach Cloud dedicated to get enterprise changefeeds. You can't just buy an enterprise license and have them enabled on your free tier cluster.

Yep, really good point. Maybe I'll adjust that note to:

Only core changefeeds are available on CockroachCloud Free Tier. To create a changefeed into a configurable sink, like cloud storage sink or Kafka, use CockroachCloud Dedicated.

Also, are you OK with the following in the CC filtered section:

An enterprise changefeed targets and allowlist of tables, called "watched rows". Each change to a watched row is emitted as a record to a configurable sink, like Kafka or a cloud storage sink. You can manage your enterprise changefeeds with create, pause, resume, or cancel.

Or, do you think altering to lean more on CockroachCloud Dedicated wording + being able to create a changefeed to a sink would be better than "enterprise".

Another minor nit: I think we should explain what changefeeds are a little more in the Cockroach Cloud example, since they are not as obvious as most other bulk commands. Maybe take the line from one of our main docs: "Change data capture (CDC) provides efficient, distributed, row-level change feeds into a configurable sink for downstream processing such as reporting, caching, or full-text indexing."
I also think we should reference the create changefeed page somewhere  (https://www.cockroachlabs.com/docs/stable/create-changefeed.html) and not just the "stream data out of cockroach" page (https://www.cockroachlabs.com/docs/v20.2/stream-data-out-of-cockroachdb-using-changefeeds.html) - since there is a lot of rich information on that page

Only core changefeeds are available on CockroachCloud Free Tier. An enterprise license is required to create a changefeed into a configurable cloud storage sink, Kafka, etc.

I think this is a little confusing - at the moment you must use Cockroach Cloud dedicated to get enterprise changefeeds. You can't just buy an enterprise license and have them enabled on your free tier cluster.

Yep, really good point. Maybe I'll adjust that note to:

Only core changefeeds are available on CockroachCloud Free Tier. To create a changefeed into a configurable sink, like cloud storage sink or Kafka, use CockroachCloud Dedicated.

Also, are you OK with the following in the CC filtered section:

An enterprise changefeed targets and allowlist of tables, called "watched rows". Each change to a watched row is emitted as a record to a configurable sink, like Kafka or a cloud storage sink. You can manage your enterprise changefeeds with create, pause, resume, or cancel.

Or, do you think altering to lean more on CockroachCloud Dedicated wording + being able to create a changefeed to a sink would be better than "enterprise".

Okay with the first change, to your second point - I do think you're right. The reference to enterprise is kind of confusing since all CC clusters have enterprise licenses, and some enterprise features are enabled on free tier

Incorporated the comments so far from Liv & Abbey. Have gone ahead and requested docs reviews from @ianjevans & @gemma-shay given the tight deadline. Feel free to leave further feedback if needed @livlobo @mwang1026. Thanks!

Noticed some overlap with this page: https://www.cockroachlabs.com/docs/cockroachcloud/backups-page.html#back-up-and-restore-data-manually. I think it would be okay to remove the manual backup and restore info from backups-page.html and link out to your new doc instead. Also, assuming the Troubleshooting section applies to both Console and manual restores, it could be included on both pages.

Noticed some overlap with this page: https://www.cockroachlabs.com/docs/cockroachcloud/backups-page.html#back-up-and-restore-data-manually. I think it would be okay to remove the manual backup and restore info from backups-page.html and link out to your new doc instead. Also, assuming the Troubleshooting section applies to both Console and manual restores, it could be included on both pages.

YES! Such a good point Gemma. Hmmmm, so there is the connection command to the SQL shell in the backup and restore manually section...
Maybe I'll link to this page https://www.cockroachlabs.com/docs/cockroachcloud/connect-to-a-free-cluster.html before the Examples section on the new page. And, agree, I'll link to the troubleshooting section from the new page too.
Thanks!

LGTM - I'm not sure if you had a chance to update the example to IMPORT Table (I still see IMPORT INTO on the Run bulk operations page) - but otherwise LGTM.

Oh weird! Yes, that's updated and viewable on the deploy link: https://deploy-preview-10945--cockroachdb-docs.netlify.app/docs/cockroachcloud/run-bulk-operations.html?#import-data-into-your-cockroachcloud-cluster

LGTM - I'm not sure if you had a chance to update the example to IMPORT Table (I still see IMPORT INTO on the Run bulk operations page) - but otherwise LGTM.

Oh weird! Yes, that's updated and viewable on the deploy link: https://deploy-preview-10945--cockroachdb-docs.netlify.app/docs/cockroachcloud/run-bulk-operations.html?#import-data-into-your-cockroachcloud-cluster

Ah, I see it now. Thanks, Kathryn!


Terracotta stairs and slabs bugged

When I try to either paint, or break the terracotta stairs or blocks it doesn't work.
I've used different tools for breaking, none of which work. The breaking is obsidian level slow, and I don't get the block back.
I am able to dye the terracotta blocks, but not the others, sadly.

At the moment, only full blocks can be dyed using the block painter, because of issues I ran into with copying complex block state data from other colored blocks. That said, I want to enhance the painter to allow painting more things, such as slabs, stairs, beds, etc.
As for the breaking issue, that's definitely a bug. Which version of Minecraft and Minekea are you on? From the sound of it, I may have missed adding those blocks to the relevant vanilla tool tag. If that's the case, it should be a fairly quick fix. If not, I will have to do some more digging. But let's hope for the first scenario.

I just uploaded 2.8.3 and 3.1.2 of the mod for Minecraft 1.18.2 and 1.19, respectively. Everything should be working as expected now!

Sorry! didn't get a notification that you responded.
I was on 2.8.2. Going to update and test it now :). thank you for fixing it!


Ability to delete an existing forked from relationship

Can you please add the ability to delete an existing forked from relationship in ProjetApi ?
DELETE /projects/:id/fork

@cpottiers
This functionality has been added to release 4.8.57
ProjectApi.deleteForkedFromRelationship(Object projectIdOrPath)

Please verify and close when you have a chance.

Good job.
Thanks you for you reactivity.
:+1:


Cloud support

Would be nice to be able to save the skill configs somewhere so we can use them on other devices. Maybe an export/import is enough.

AutoSkill configurations are dependent on the Servant/CE images used. So, there's no point in moving them around without the images. So, we'll have to zip the configurations along with the images.
Considering the upcoming Android 11 will have heavy restrictions on storage access, we should use a MediaStore or Sharing API for this, so migrating from the current folder structure is easy.
To do this properly will be a LOT of effort. Don't expect anytime soon.

See #196. I've added an option to export individual AutoSkill configs and an option to Import multiple AutoSkill configs.
I'm not doing the packing images together thing because it is too much work.
The images can just be copied to the other device so it is not a problem I think.


chore: add Prettier as devDependency + add pre-commit hook

Add Prettier as devDependency
Run Prettier on full codebase
Add pre-commit hook

Ping @jlengstorf

Ping @jlengstorf

:tada: This PR is included in version 1.3.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Add/verilog courses #2151

Renamed SystemVerilog section to Verilog / VHDL / SystemVerilog because they are 3 different hardware description languages. Grouped them together so that all the Verilog resources can be found in one spot. Added new course as suggested in #2151

This is really helpful! Much appreciated.