Bug in Animation when playing with frame size and position

Take any UIView (like an UIImageView).
Set it's image.
Set it's frame to, for instance,  myView.frame = CGRectMake (50,50,100,200);
now run this code:
[UIView animateWithDuration:0.3
animations:^{
myView.frame = CGRectMake (0,0,10,20);
}
completion:^(BOOL finished){
}];
you'll see that the animation is completely wrong.

There is a workaround:
Use myView.transform=CGAffineTransformScale(myView.transform,2.0,2.0);
and that's working fine.

Can you elaborate on what you saw?  I ran it and it appeared to work alright.  Were there any other animations being applied to the view?

The image start to grow, then jump to the right position with the right size. No other animation were applied on the view.

Do you have a sample project you could share that repros the issue?  I stuck this into an empty project and it looked fine:
UIImageView *view = [UIImageView new];
view.image = [UIImage imageWithContentsOfFile: @"Logo.scale-100.png"];
[self.view addSubview: view];
view.frame = CGRectMake (50,50,100,200);
view.backgroundColor = [UIColor redColor];

[UIView animateWithDuration:0.3

animations:^{
view.frame = CGRectMake (0,0,10,20);
}
completion:^(BOOL finished){
}];

Try to include your imageview in another one.
I can't provide you right now a sample project.
Le mardi 24 novembre 2015, bdrlamb-ms<EMAIL_ADDRESS>a écrit :

Do you have a sample project you could share that repros the issue? I
stuck this into an empty project and it looked fine:
UIImageView *view = [UIImageView new];
view.image = [UIImage imageWithContentsOfFile: @"Logo.scale-100.png"];
[self.view addSubview: view];
view.frame = CGRectMake (50,50,100,200);
view.backgroundColor = [UIColor redColor];
[UIView animateWithDuration:0.3
animations:^{
view.frame = CGRectMake (0,0,10,20);
}
completion:^(BOOL finished){
}];
—
Reply to this email directly or view it on GitHub
https://github.com/Microsoft/WinObjC/issues/243#issuecomment-159384502.

Did you try to insert a UIImageView as a subview of another UIImageView and to animate its frame?

I did, it still looked OK.  Are you using autolayout or an autoresizing mask on any of these views?

We have made some changes to our animation recently. If you still see this problem, please reactivate and provide more information.


hi, can you support some shortcut to create cron expresions, such as daily?

please check cron_clock

Thanks @vidyli  for the bug report.
The cron crate (https://github.com/zslayton/cron)  I'm using for parsing the cron statements supports '@hourly',  '@daily',  '@weekly',  '@monthly' and  '@yearly'.
As I'm using the upstream parser, I'll rather defer you to them if you've got another use case.

I've updated the README to reflect this


11493 integration test travis

Removed the volumes which have write permissions for the eventkit user (and is unneeded for the code since the Dockerfile_test configuration copies the data to the correct directory from github.
Updated the SITE_NAME and SITE_IP.

Coverage remained the same at 81.995% when pulling a7740abcd8da4c852b3f3491528e53b8ab078f56 on 11493-integration-test-travis into 0cfb650abe9d46775f9f4a34be7fb79fba0394b5 on master.

Coverage remained the same at 81.982% when pulling 5cd5241010d7631a836737aeb7e4bb129f3e633f on 11493-integration-test-travis into 33b76cfa15b243b3c81656f2d5d433f5a34afb89 on master.


Remove timing info from WriteState

These prints can have a negative impact on the performance of WriteState in total

CI gfxreconstruct build queued with queue ID 291081.

CI gfxreconstruct build # 5240 running.

CI gfxreconstruct build # 5240 passed.


AttributeError: 'module' object has no attribute 'client'

Dear Zipline Maintainers,
Before I tell you about my issue, let me describe my environment:
Environment

Operating System: Linux ubuntu-new-install 4.4.0-34-generic #53-Ubuntu SMP Wed Jul 27 16:06:39 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
Python Version: Python 3.4.5
Python Bitness:  64
How did you install Zipline: pip
Python packages:

backports-abc==0.4
bcolz==0.12.1
Bottleneck==1.1.0
cachetools==1.1.6
click==6.6
contextlib2==0.5.4
cycler==0.10.0
cyordereddict==1.0.0
Cython==0.24.1
decorator==4.0.10
entrypoints==0.2.2
intervaltree==2.1.0
ipykernel==4.4.1
ipython==5.1.0
ipython-genutils==0.1.0
Jinja2==2.8
jsonschema==2.5.1
jupyter-client==4.3.0
jupyter-core==4.1.1
Logbook==1.0.0
lxml==3.6.1
MarkupSafe==0.23
matplotlib==1.5.1
mistune==0.7.3
multipledispatch==0.4.8
nbconvert==4.2.0
nbformat==4.1.0
networkx==1.11
notebook==4.2.2
numexpr==2.6.1
numpy==1.11.1
pandas==0.18.1
pandas-datareader==0.2.1
patsy==0.4.1
pexpect==4.2.0
pickleshare==0.7.4
prompt-toolkit==1.0.6
ptyprocess==0.5.1
Pygments==2.1.3
pyparsing==2.1.8
python-dateutil==2.5.3
pytz==2016.6.1
pyzmq==15.4.0
requests==2.11.0
requests-file==1.4
scipy==0.18.0
simplegeneric==0.8.1
six==1.10.0
sortedcontainers==1.5.3
SQLAlchemy==1.0.14
statsmodels==0.6.1
TA-Lib==0.4.9
terminado==0.6
toolz==0.8.0
tornado==4.4.1
traitlets==4.2.2
tushare==0.5.0
wcwidth==0.1.7
zipline==1.0.1

Now that you know a little about me, let me tell you about the issue I am
having:
Description of Issue

What did you expect to happen?
I am testing the notebook tutorial(https://github.com/quantopian/zipline/blob/master/docs/notebooks/tutorial.ipynb).
What happened instead?
But when I ran the command in jupyter notebook as below, I got the error message instead.
!python /usr/local/lib/python3.4/site-packages/zipline/utils/run_algo.py --help

Full error message:
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/site-packages/pandas/compat/__init__.py", line 46, in <module>
    import __builtin__ as builtins
ImportError: No module named '__builtin__'

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/local/lib/python3.4/site-packages/zipline/utils/run_algo.py", line 17, in <module>
    from zipline.algorithm import TradingAlgorithm
  File "/usr/local/lib/python3.4/site-packages/zipline/__init__.py", line 19, in <module>
    from . import data
  File "/usr/local/lib/python3.4/site-packages/zipline/data/__init__.py", line 1, in <module>
    from . import loader
  File "/usr/local/lib/python3.4/site-packages/zipline/data/loader.py", line 18, in <module>
    import logbook
  File "/usr/local/lib/python3.4/site-packages/logbook/__init__.py", line 14, in <module>
    from .base import (
  File "/usr/local/lib/python3.4/site-packages/logbook/base.py", line 22, in <module>
    from logbook.helpers import (PY2, cached_property, integer_types, iteritems,
  File "/usr/local/lib/python3.4/site-packages/logbook/helpers.py", line 60, in <module>
    from http import client as http_client
  File "/usr/local/lib/python3.4/http/client.py", line 69, in <module>
    import email.parser
  File "/usr/local/lib/python3.4/email/parser.py", line 12, in <module>
    from email.feedparser import FeedParser, BytesFeedParser
  File "/usr/local/lib/python3.4/email/feedparser.py", line 27, in <module>
    from email import message
  File "/usr/local/lib/python3.4/email/message.py", line 16, in <module>
    from email import utils
  File "/usr/local/lib/python3.4/email/utils.py", line 29, in <module>
    import socket
  File "/usr/local/lib/python3.4/socket.py", line 53, in <module>
    from enum import IntEnum
  File "/usr/local/lib/python3.4/site-packages/zipline/utils/enum.py", line 27, in <module>
    import pandas as pd
  File "/usr/local/lib/python3.4/site-packages/pandas/__init__.py", line 22, in <module>
    from pandas.compat.numpy import *
  File "/usr/local/lib/python3.4/site-packages/pandas/compat/__init__.py", line 59, in <module>
    import http.client as httplib
AttributeError: 'module' object has no attribute 'client'

Here is how you can reproduce this issue on your machine:
Reproduction Steps

Compiling python 3.4.5 from source and successfully installed pip.
Install jupyter notebook, and upgrade to 5.0.
Replace the run_algo.py path with my one.
Run.

What steps have you taken to resolve this already?

I tried Pandas 0.17, the error message is the same. So I also tried the 0.18 version, nothing changed.
I tried two commands like below in Jupyter notebook, they worked!
from http import client as http_client import http.client as httplib
...

Sincerely,
Yuan

Hi @yuanhuanglin !  Sorry for the trouble - looks like that doc uses the old command and no longer works.  From the command line, you can run zipline run --help, or in a jupyter notebook you can import zipline and then use the %%zipline cell magic.

Regarding the AttributeError, as the package containing the entry point, the zipline/utils directory is added to your PYTHONPATH, and then zipline.utils.enum is shadowing python3's stdlib enum.  So then we're importing pandas again, which is partially initialized... and so on.

I updated the docs in https://github.com/quantopian/zipline/pull/1409.  Let us know if the new command works for you.

Haven't heard anything, so closing for now.


Bug: registerUpdateListener gives stale state after clearing formatting

Lexical version: 16.0.0
Already reported before. My previous issue was closed with unrelated fix.
https://github.com/facebook/lexical/issues/3456
Steps To Reproduce

open playground (https://playground.lexical.dev/)

select text

click bold

click on clear formatting

bold still active

Interesting it works in safari but doesn't work in chrome

I think this is a bug in the playground's clearFormatting button, it clears the formatting from the node but not the selection… although I think maybe there's some APIs that selection should have but does not in order to facilitate this.


Fix: 24 | additional null check for initial call arguments

fix: #24
Also additional test case and fix for no-deps useEffect since it can cause tearing on significant renders

@axelson
This should fix the issue, we'd like you to check it through using the codesandbox builds above until a new release is published

@barelyhuman thanks for this fix! Is there a way I can run eslint in the codesandbox? I'm not seeing a console where I can run npx eslint

@barelyhuman thanks for this fix! Is there a way I can run eslint in the codesandbox? I'm not seeing a console where I can run npx eslint

nah, you can’t.
though, you can use the builds generated by codesandbox
https://ci.codesandbox.io/status/pmndrs/eslint-plugin-valtio/pr/25/builds/250278
use the “local install instructions” to use this PR’s build

@barelyhuman Thanks for the testing instructions!
Unfortunately on my production project I'm still running into: https://github.com/pmndrs/eslint-plugin-valtio/issues/24 even when I'm using "eslint-plugin-valtio": "https://pkg.csb.dev/pmndrs/eslint-plugin-valtio/commit/13591806/eslint-plugin-valtio"

is it possible for you to create a reproduction project for the same? not a sandbox, a normal repo. i can’t seem to get the same error

@barelyhuman Thanks for the testing instructions!
Unfortunately on my production project I'm still running into: #24 even when I'm using "eslint-plugin-valtio": "https://pkg.csb.dev/pmndrs/eslint-plugin-valtio/commit/13591806/eslint-plugin-valtio"

@axelson
Make sure you re-install the node-modules and do that after removing any .lock files
and test that again.
If not, I'd be happy to help with a simple github repo reproducing this issue :)


radiance: init at 5.4

Description of changes
Adds radiance, a light simulation tool.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

It might make sense to source the code from the official page instead of the github mirror. I just found out about that. Leaving a link here for future me
https://www.radiance-online.org/download-install/radiance-source-code/latest-release

When you make the changes to replace the GitHub mirror with the official release URL could you also please re-work the commits, so that there are two commits only? One for the license with the message lib/licenses: add radiance and one for the package with the message radiance: init at 5.4?

When you make the changes to replace the GitHub mirror with the official release URL could you also please re-work the commits, so that there are two commits only? One for the license with the message lib/licenses: add radiance and one for the package with the message radiance: init at 5.4?

Yeah sure 👍🏼 Probably would've done a cleanup rebase anyways later on ;p

Thanks for the review! I just implemented all the suggestions and rebased for clean commits

Thanks, @RobWalt, mind squashing the commits, so that we are left with only two? One for the license and one for the nee radiance package?

@afh done, sorry it took so long

Result of nixpkgs-review pr 307683 run on aarch64-darwin 1

Result of nixpkgs-review pr 307683 run on x86_64-linux 1

2 packages blacklisted:

nixos-install-tools
tests.nixos-functions.nixos-test

2 packages built:

nixpkgs-manual
radiance

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1870

Thanks for your contribution and continued effort on this PR, @RobWalt, and thanks @SuperSandro2000 for merging 👍


Remove hardcoded URLs in favor of Config.routes

As discussed previously, the primary motivation here is to be able to host a staging/testing environment for Pokemon Showdown's current set up.  Starting with the server side changes here because the client changes are more involved.

After this change, running git grep pokemonshowdown | grep -v "* Pokemon Showdown - http://pokemonshowdown.com/":
LICENSE:Copyright (c) 2011-2019 Guangcong Luo and other contributors http://pokemonshowdown.com/
PROTOCOL.md:> `http://play.pokemonshowdown.com/action.php?act=upkeep&challstr=CHALLSTR`
PROTOCOL.md:> Otherwise, you'll need to make an HTTP POST request to `http://play.pokemonshowdown.com/action.php`
README.md:  [1]: http://pokemonshowdown.com/
README.md:  [4]: http://pokemonshowdown.com/
README.md:- See http://pokemonshowdown.com/credits

Docs
config/config-example.js:exports.loginserver = 'http://play.pokemonshowdown.com/';
config/config-example.js:	root: 'pokemonshowdown.com',
config/config-example.js:	client: 'play.pokemonshowdown.com',
config/config-example.js:	dex: 'dex.pokemonshowdown.com',
config/config-example.js:	replays: 'replay.pokemonshowdown.com',
package.json:  "homepage": "http://pokemonshowdown.com",

Config
data/rulesets.js:		// implemented in sim/battle.js, see https://dex.pokemonshowdown.com/articles/battlerules#endlessbattleclause for the specification.
server/chat-plugins/info.js: * Pokemon Showdown - https://pokemonshowdown.com/
server/ladders-local.ts: * play.pokemonshowdown.com.
server/ladders-remote.ts: * play.pokemonshowdown.com.

Comments
server/chat-plugins/info.js:			`- <a href="https://replay.pokemonshowdown.com/gennextou-120689854">Zergo vs Mr Weegle Snarf</a><br />` +
server/chat-plugins/info.js:			`- <a href="https://replay.pokemonshowdown.com/gennextou-130756055">NickMP vs Khalogie</a>`

Specific replays which wouldnt exist on another server
server/chat.js:const LINK_WHITELIST = ['*.pokemonshowdown.com', 'psim.us', 'smogtours.psim.us', '*.smogon.com', '*.pastebin.com', '*.hastebin.com'];
server/chat.js:			'pokemonshowdown.com': 1,

Whitelisting
server/ladders-remote.ts:		return [`<tr><td><strong>Please use the official client at play.pokemonshowdown.com</strong></td></tr>`];

Only 'play.pokemonshowdown.com' is official, so this is still correct
server/static/404.html:
This is a Pokémon Showdown server.

server/static/index.html:
This is a Pokémon Showdown server!

PITA to change without introducing a build for these files to replay the constants. Will need to do that on the client, but seems like overkill here. Also contains a reference to psim.us, once again, not sure worth what it would take to generalize
test/server/chat.js:			`<a href="//dex.pokemonshowdown.com/pokemon/oshawott" target="_blank"><psicon pokemon="Oshawott"/></a> >w<`
test/server/chat.js:			`<a href="//dex.pokemonshowdown.com/items/beastball" target="_blank">[Beast ball]</a> >w<`

Tests
translations/dutch.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-nl",
translations/english.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "",
translations/french.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-fr",
translations/german.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-de",
translations/hindi.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-hi",
translations/italian.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-it",
translations/japanese.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-ja",
translations/portuguese.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-pt",
translations/simplifiedchinese.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-zh",
translations/spanish.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-es",
translations/traditionalchinese.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-tw",
translations/turkish.json:		"[TN: Link to the PS rules for your language]https://pokemonshowdown.com/rules": "https://pokemonshowdown.com/pages/rules-tr",

Should probably also not be hardcoded, but translations are half baked anyway

Looks good. One day, though, we should strongly type the Config object exported from config-loader.
Maybe it should extract the type exported from config-example.

There's a pending review request from Hoeen so I guess I'll leave this unmerged for now?

The pending review request is automatic due to CODEOWNERS, but I dont think this is a change Hoeen would care about...


Restrict selectorLink from being set for external Services and ability to add service links to external services.

Server version - Build from master = Oct 7
Steps to reproduce the problem:
Created a External service S1 with - selector_link as "foo=bar".
Created a service S2 with label = "foo" and value as "bar.
External service gets linked with S2.
Create service S3 with service link to S1.
From containers of S3 , there is no way to resolve containers of S2.
Since this is not supported , expected behavior should be for API to not allow externalServices being created with external Services field set.
On a similar note, we should also restrict the ability to add service links to External Services.

Tested with latest build from master
We do not have the ability to add  selectorLink  for external Services. Also add/set/remove service links are not permitted actions on external services anymore.


Fix tests post-CASSANDRA-10783

This test is still going to run on versions without 10783, so we need to filter the expected error message based on cluster version

You're right, updated the patch to deal with that.

+1, Thanks


Strings drops accents and other symbols

Strings drop accented letters and other symbols such as the em dash after compilation.
For example...
"I am — was — friends with Rød"

...becomes...
"I am  was  friends with Rd"

...after compilation, which is undesirable. Strings should contain all text contained within the quotes.

Saving the script in UTF-8 format fixes this problem.


[FE] Optimize image performance

When running build-dev, several warnings and suggestions related to images show up.

Update the component to resolve this change.

There are some NextJS recommendations with npm i sharp, please resolve this as well.

Hey, @ninman27
@edichoska mentioned you implemented sharp for the project.
I keep seeing this recommendation: (as mentioned in point 2. of the ticket)

However, after a little bit of investigating, I noticed this only shows up when using yarn build and not when using npm run build.  It seems there's a minor version upgrade 0.33.2 -> 0.33.3 for sharp.
Can you look into this and let me know what you find?
If just the version upgrade solves the problem, that's fine by me.

@RevanchistX I tried with yarn build and it is OK. I don't see Next.js's recommendation about the sharp.

Thanks for the feedback @kire21
It seems we have different yarn versions, but I don't think this is an issue anymore.
I will update the ticket.


Default all URLs to https:// by default  #44

Generating non-secure URLs is still possible, by passing in $secure = false.

@henrikbjorn any update for merge this? Using SSL is almost mandatory for search engines as Google if you don't want display "not secure" warning.

It's still usable, you just have to explicitly add a boolean true to all the Twig calls you want to use rather than having it default to secure all the time (which is always safe anyway).
Gravatar profile


Fix documentation for scipy.special comb()

Change return type documentation
Fixes #7110

Thanks @milindl. We would like to not have the merge commit of master into your branch. When you address my comment, can you please rebase to get rid of it?

@rgommers The commit 3a643e already addresses this fix, so I think it is best now if this PR is closed.
Please tell me if this is not the case, and I can then make the requisite changes.
Meanwhile I'll close this PR.
Thanks


Warn when invalid configuraiton

Is your feature request related to a problem? Please describe.
I accidentally copied the wrong .env value and the image just simply didn't load.
Would it make sense to include warning you're missing the environment variable so its an easy assist for someone trying to get started?
Describe the solution you'd like
Maybe a console.warn if the Cloud Name isn't found, meaning its not set.
Describe alternatives you've considered
A thrown error might be too much, but broken images could be considered a breaking feature 🤷

Added in https://github.com/nuxt-modules/cloudinary/commit/0a3a78e6d821f77ab3fc48a3783cc90e212b354a


Add the ability to disable Haptics on network API failure

We love using Debug swift, can you please provide a way to optionally disable the following as it interferes with the haptics in our app?
if !success {
  UIImpactFeedbackGenerator(style: .medium).impactOccurred()
}

Thanks for your feedback, I'll do soon as possible :)


[Publisher] Add Business Information and Meta Information UI to API details

Description:

Provide UI to add/view/edit following API properties in Publisher API details page

Business Information
Meta Information

Those were in Manage step(3rd) in APIM 2.2.x

and
Meta Information

Already fixed in master branch


Add methods for verifying presentations.

@mikelodder7 i think a rebase will resolve the CI failures here and in the other PR

@mikelodder7 I'll merge this one next as soon as rebase is resolved

Verified that these commits are on develop now. GH messing up again on merged state.


[Fix #10335] Fix a false positive for Naming/BlockForwarding

Fixes #10335.
This PR fixes a false positive for Naming/BlockForwarding when using multiple proc arguments.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Looks good. Thanks!

Looks good. Thanks!


Bid history table view / Bid button

This is implementing the table view that shows the bid history as well as the button to place a bid. Note this does not cover how to see more of the bid history, for the purposes of this issue, we're sticking to a table view that's just really really short
Implementation Idea
Standard table view stuff, but there are a lot of different designs. Luckily it's congruent within compact/regular environments.
Estimate
1 Day

@katarinabatina should we show the Live Lot button if on closed lots?

@orta yes


Support Python 3

What does this PR do?
Support Python 3 in System Swap. No changes were necessary for this PR. It supported it already.
Motivation
Python 3 is on its way. 🚂
Review checklist

[x] PR has a meaningful title or PR has the no-changelog label attached
[x] Feature or bugfix has tests
[x] Git history is clean
[ ] If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
[ ] If PR adds a configuration option, it has been added to the configuration file.

Additional Notes
Anything else we should know when reviewing?

Codecov Report

Merging #2830 into master will increase coverage by 15.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #2830       +/-   ##
==========================================
+ Coverage   84.65%    100%   +15.34%
==========================================
  Files         660       4      -656
  Lines       37759      36    -37723
  Branches     4535       0     -4535
==========================================
- Hits        31963      36    -31927
+ Misses       4462       0     -4462
+ Partials     1334       0     -1334


Org page

We need an Org page, just like our project page. It shows:

[ ] Name
[ ] Members

And it's the workspace for org admins to:

[ ] add members
[ ] set member roles.

Permissions:

Org admins

member CRUD (for now they will be auto added, but we may want that to be an invite process in the future)

Org members

view member list

Non org members

view org
list admins (including email tbd?), not other members

I assume we'll want the same member workflows we currently use for adding members to projects and setting their roles.
I think it would be very easy and reasonable to share a component with the project page for the general layout:

Header
Badges (Not sure what might go here for orgs)
Attributes (description)
History (eventually)
More settings (delete, leave etc.)

Some minimal, but distinct style/color differences would be wonderful, so that the project page and org page can't be confused. And maybe so that the org page feels a tad "fancy", fresh and desirable.
Adding a project list to the org page is tracked in #788

This seems like the first one to start with; once the org page exists, then creating and listing orgs would be the next steps.


Echo the current branch in Travis

This is helpful for understanding how Travis is interacting with commits pushed to a PR.

👍

https://travis-ci.org/gratipay/gratipay.com/builds/136260351#L167-L168

Ready for review/merge @rohitpaulk @aandis et al.

Wait.. How exactly is this helpful? Travis shows the commit hash in the UI.

@rohitpaulk That is the merge commit that GitHub automatically creates between the PR branch and master. However, what we were looking for is the commit on the PR branch that is being merged into master.
The scenario is that we were trying to rebase nine or ten commits (https://github.com/gratipay/gratipay.com/pull/4046#issuecomment-224719594) in such a way that Travis would test each of the new commits just as it had tested the old ones. We wanted to do this as fast as possible, meaning, we didn't want to wait for Travis to complete the test suite for one commit before pushing the next commit. What we discovered is that we could push the next commit as soon as Travis cloned the repo for a given commit—but not sooner. If we push too commits in too-quick succession, then the first build ends up cloning the second commit, and the test results are therefore inaccurate. Having the PR commit in the Travis log will enable debugging this kind of situation.

Aha! Gotcha.

!m @rohitpaulk


C++ code reviewers needed

A lack of reviewers is once again slowing down the development and maintenance of the PiSCSI C++ core code: Tickets ready for a PR and existing PRs cannot be merged within a reasonable timeframe. Other tickets cannot be worked upon because they require pending PRs to have been merged before.
Help is appreciated by anybody who is familiar with OOP and modern C++, and in the ideal case also with SCSI.

I have significant C++ experience, but no real experience with SCSI. Would be willing to review code; please let me know what you're looking for in terms of help!

@dialtr That's really cool!
From my perspective, the main problem we have had with the C++ code in the past is that the original rascsi legacy code was more C than C++ and suffered from countless problems. This is not just my subjective view but was confirmed by a huge number of issues reported by SonarQube. Since then, besides adding a lot of new features (https://www.piscsi.de/en/piscsi.html provides a list with the most important), substantial work on the code structure etc. was required in order to address these problems. Reviewing these changes is a lot of work and in the past @akuker was the only one who did the reviews, while I was almost the only code contributor working on getting the C++ code into a better shape. In the meantime I have re-implemented large parts of the C++ core, resolved more than 1500 SonarQube issues and added quite a lot of unit tests. cpp/devices/cfilesystem.cpp still shows how the old code was looking like, and just this file causes most of the remaining SonarQube issues.
Anyway, there are development phases with a lot of resolved C++ tickets (related to new features, structural changes or to improvements like C++-20 support) where it would be great to have more than one potential reviewer. This is why I ask for help in this ticket.
IMO skills in modern C++ and OOP are more important than a deep insight into SCSI. Most of the code (except for the /hal folder) is not that low-level, but it is more about how controllers/devices/command executors/threads interact and how they are structured. The goal is C++ code that is up to date, portable, robust and expressive. It should make use of best practices of contemporary C++, both from the language and the design perspective. Just because this projects deals with old computers does not mean that the C++ code should look like C code from the 80s or 90s ;-).
I just created an new PR, by the way, https://github.com/PiSCSI/piscsi/pull/1247. I did not manage to add you to the reviewer list, though.

Uwe, thanks for the note.
I definitely have experience with old, anachronistic codebases and have been involved in modernizing them in the past. Where I may also face challenges is that my own C++ knowledge is a bit stale. I've been working towards learning the modern features lately, but in my role as a manager, it's not part of my day-to-day to code much anymore.  At the same time, I think that if some of the problems are deeper than just C++20 migration, I could be of help.  I'm going to start by taking a look at the code and any docs that exist in the repo, as well as the PR.

Sounds good, thank you!
Before getting involved in this project I had not used C++ for more than a decade, and the state of the rascsi codebase 3 years ago was a good incentive to update my outdated C++ knowledge. Since then I have read numerous books on modern C++ and watched quite a lot of conference talks (videos) on current C++ and the STL. All this has hopefully had some benefits ;-). Regarding modernizing codebases I needed to do that quite a lot for C++ and Java.
Wrt the C++ features we may use we are restricted to a subset of C++-20, because the versions of both g++ and clang++ supported by Debian/Raspberry Pi OS are usually quite old. What I would have liked to have is views and not just ranges, and maybe support for "using enum", but so far I could live with the compiler limitations.
We should ensure that the code compiles and runs on bullseye and bookworm, on Raspberry Pi OS and Ubuntu, 32 and 64 bit.


Cannot set a custom query parser after app.use() has been called

If I set a custom query parser, as explained in the docs, the custom query parser only gets used if I define it immediately after the app is created (ie. before any middleware is added).
This works:
const app = express();
app.set('query parser', function(str) {
  return qs.parse(str, { arrayLimit: Infinity });
});
app.use(bodyParser.json())
app.use(Router())

This does not:
const app = express();
app.use(bodyParser.json())
app.set('query parser', function(str) {
  return qs.parse(str, { arrayLimit: Infinity });
});
app.use(Router())

In both cases, the call to app.set() succeeds, and app.settings reflects the custom query parser that I provided.
However, the custom query parser is never invoked in the second example, and express continues to use the default "extended" parser.

Personally, I do not have any particular problem with this limitation, as it seems exceedingly unlikely that one would need to alter this setting at runtime.
However, the documentation should probably indicate this caveat, and it may be beneficial for app.set() to throw an error when making configuration changes that are known to be ineffective or illegal.

Ah, yes. This is a known issue that we already fixed in the current 5.0 alpha, since it wasn't backwards compatible. We can certainly document this limitation at expressjs.com if it isn't already (just file a ticket or even make the change at https://github.com/expressjs/expressjs.com).
As for throwing an error, didn't really think about that one before. I'm not really sure how disrupting that may be, though, without access to see how apps would react, especially if they had some complex logic that it worked but accidentally called a second time, not sure.
Do you think that it's fixed in 5.0 and docs (if there aren't already some) for 4.x about the limitation is good enough? If we want to throw, I'm not sure if there's a good way to assess the impact of such a change.

If this works as expected in 5.x (ie. you can set a custom query parser after attaching middleware), I wouldn't stress too much over this issue.  I haven't tried the 5.x alpha yet, but it seems like it's worth adding a test-case to validate that this has indeed been fixed.
I'll open a PR to add a note to the documentation for 4.x.
I reluctantly agree that we can't change this behavior in 4.x, as it could potentially change the current behavior of existing applications.
On the other hand, the current behavior is very clearly wrong.  It's also not entirely unreasonable to expect app.set() to throw an exception when illegally setting the query parser -- app.set() already throws an exception if an unknown/invalid query parser value is passed in.
However, again, this might still be too disruptive of a change to make in a semver-minor release.
Is there any precedent for printing warnings to the console in situations like this?  That might be a happy middle-ground that will hopefully alert developers to the fact that their code isn't going to do what they think it will...

Not sure if there is a test in the 5.0 branch, but feel free to PR one there for sure :) ! For warnings, there are none today. There have been a couple fringe uses were we could add some, but the issue was (1) what mechanism would be provided for users to capture these in their existing logging framework and (2) what mechanism would be provided to silence the warnings. Ideally we would use some kind of standardized warning mechanism (not console.warn which is hard to capture / silence, but also provides no context when needed to track down where it's coming from).

Any chance of this fix being ported to 4.x given 5.x is on hold?

Hi @cabbiepete the reason the fix was not backported is because it was not backwards compatible, as noted above. I left this issue open really because there was some discussion points, but it seems like there was no further follow up after my comment, and it's been a few years :) So I'm going to close this issue for now.
If you have any specific suggestions, for example documentation or implementation changes, you're welcome to make pull requests for either of those :) ! And if you haven't already tried out the 5.0 alpha, please feel free to.
As for it being "on hold", I'm not sure where that is stated. In fact, it is the number one thing we are currently working on. We had a TC meeting today talking about this exact topic, even :O https://youtu.be/kkcpQlXRfgY

@dougwilson Thanks for the reply. I forget the issue where I read expresses 5.x was on hold waiting for http2 to land in core, never mind if you guys are working on it that's great :-)

Thanks for open that issues, that helps me save a ton of time,


Event Listener (On Upload)

Hey peeps,
This is not actually a issue or a problem, but can't find anywhere else the answer
Is it possible each uploader object has their own event listener (onUpload)?
I have declared both on services, but it is only going to the first one.
app.rpl_evidence_listener:
    class: AppBundle\EventListener\RplEvidenceListener
    arguments<EMAIL_ADDRESS>    tags:
        - { name: kernel.event_listener, event: oneup_uploader.post_persist, method: onUpload }

app.credit_evidence_listener:
    class: AppBundle\EventListener\CreditEvidenceListener
    arguments<EMAIL_ADDRESS>    tags:
        - { name: kernel.event_listener, event: oneup_uploader.post_persist, method: onUpload }

Cheers

Hi there
What is the output of php bin/console debug:event-dispatcher oneup_uploader.post_persist?

Hey,
this is what i got
**Registered Listeners for "oneup_uploader.post_persist" Event

Order   Callable                                                     Priority

#1      AppBundle\EventListener\RplEvidenceListener::onUpload()      0
#2      AppBundle\EventListener\CreditEvidenceListener::onUpload()   0

**

So, your  CreditEvidenceListener is not called? Looks good to me, actually.


runtime: bsdthread_register error on macOS 12

Everything has been working perfectly for a while until I decided to upgrade Mac OS to Monterey.
What version of Go are you using (go version)?

go version go1.17.2 darwin/amd64

Does this issue reproduce with the latest release?
Yes. I have tried updating go to the latest version, as well as updating to the latest of xcode and command tools. Also ran brew upgrade to make sure everything is updated. Also tried diffrent shells to see if that makes any difference.
I am also running the latest version of docker.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/deanwronowski/Library/Caches/go-build"
GOENV="/Users/deanwronowski/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/deanwronowski/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/deanwronowski/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/Cellar/go/1.17.2/libexec"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.17.2/libexec/pkg/tool/darwin_amd64"
GOVCS=""
GOVERSION="go1.17.2"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/1p/q77885x9157c_yvzss7zx1480000gn/T/go-build2753144081=/tmp/go-build -gno-record-gcc-switches -fno-common"

What did you do?
When running the following command to connect to a server running docker it produces the error. It does not matter if the server is hosted on AWS EC2 or Digital Ocean droplets.
It seems this issue is not related just to Docker, as I am also getting this error when running a command in the terminal inside of VS.
eval "$(docker-machine env machinegoeshere)"

What did you expect to see?
Usually nothing displays which indicates its connected to the server.
What did you see instead?

fatal error: runtime: bsdthread_register error

runtime stack:
runtime.throw(0x20594e0, 0x21)
	/usr/local/go/src/runtime/panic.go:619 +0x81 fp=0x7ff7bfeff878 sp=0x7ff7bfeff858 pc=0x1029751
runtime.goenvs()
	/usr/local/go/src/runtime/os_darwin.go:129 +0x83 fp=0x7ff7bfeff8a8 sp=0x7ff7bfeff878 pc=0x10272d3
runtime.schedinit()
	/usr/local/go/src/runtime/proc.go:496 +0xa4 fp=0x7ff7bfeff900 sp=0x7ff7bfeff8a8 pc=0x102c014
runtime.rt0_go(0x7ff7bfeff930, 0x3, 0x7ff7bfeff930, 0x1000000, 0x3, 0x7ff7bfeffab0, 0x7ff7bfeffabf, 0x7ff7bfeffac3, 0x0, 0x7ff7bfeffacc, ...)
	/usr/local/go/src/runtime/asm_amd64.s:252 +0x1f4 fp=0x7ff7bfeff908 sp=0x7ff7bfeff900 pc=0x1052c64

I have seen reports starting to appear with similar issues as well

https://stackoverflow.com/questions/69844856/how-to-fix-vs-code-fatal-error-runtime-bsdthread-register-error-on-macos-mon
https://github.com/golang/go/issues/49138#issuecomment-960994361
https://github.com/rancher/rancher/issues/35346

I noticed this error popped up a few years ago, I wonder if its just a case of waiting for everyone to recompile their code again, although surprised this has not been done yet?

cc @cherrymui

same here

+1

Same for me

+1

a reminder of our no +1 policy
please use the voting at the top if you have nothing to add

@DeanWronowski Thanks for the report. What binaries are failing? (The docker command,  docker-machine, or anything, it wasn't very clear in the original post)  What versions of Go the binaries are built with? You may be able to find that out  by running go version <binary>. Thanks.

I'm seeing the same thing with Kubernetes. I was on version 1.18.0 of kubectl and that uses golang 1.13.9. I know that's a really old version, but everything was working fine until I upgraded to Monterey and now I'm seeing this same error.

@cherrymui - Sorry, my apologies.
The docker command seems to be working fine, as well as docker-compose build namegoeshere.
However, when running the following commands the error is presented
eval "$(docker-machine env -u)"
docker-machine -  even without any parameters
docker-machine ls
When running the command go version docker-machine inside of /usr/local/bin/  it says it cannot find the go version.
Hope that helps

@koryhutchison what version of Go  that kubectl was built with?
As far as I can tell, the "bsdthread_register error" last appears in Go 1.10 and is removed since Go 1.11.

@DeanWronowski thanks, and no worries. For newer versions of Go I'd think go version would work, so I guess your docker-machine binary would be build with an old version of Go. Would it be possible  to update/rebuild it with a newer  version of Go?  Thanks.

Just upgraded my iMac machine (separate machine to the original one) to Monterey and ran the command docker-machine which worked perfectly fine. This machine did not have go binary installed though. After installing Go via brew install go it still works fine. Not sure why it works on one machine and not the other.
They are both Intel Core i7
These are the architectures for both machines:

Darwin Deans-MBP-2.lan 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64
Darwin Deans-iMac.lan 21.1.0 Darwin Kernel Version 21.1.0: Wed Oct 13 17:33:23 PDT 2021; root:xnu-8019.41.5~1/RELEASE_X86_64 x86_64

@cherrymui - The original source code for docker-machine (https://github.com/docker/machine) is archived and recommends you to use Docker Desktop for Mac, which I have installed. However, not sure they have released the source code for it. I could try recompiling the docker-machine and see what happens?

I have the same problem using terraform on version 0.11.7 and with kubectl on 1.10.13

Docker released a new update for Docker Desktop - https://docs.docker.com/desktop/mac/release-notes/#docker-desktop-420 - but hasn't made any difference.

@cherrymui I went ahead and upgraded my kubectl version to v1.20.0 and I still get the error. But you can see from the output from the kubectl version --client command that it's using go1.15.5:
Client Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0", GitCommit:"af46c47ce925f4c4ad5cc8d1fca46c7b77d13b38", GitTreeState:"clean", BuildDate:"2020-12-08T17:59:43Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"darwin/amd64"}

Also I verified it in the Kubernetes CHANGELOG.

Sorry, I'm not familiar with docker and what can or cannot be built from source. Just as an experiment, you could try building docker-machine from the archived source with a new version of Go and see if the issue occurs.
It still looks like it fails with a binary built with an early (or unknown) version of Go. Does anyone see the issue with a newly built binary, preferably built from source? Thanks.

@koryhutchison how do you run kubectl version --client command? Doesm't kubectl fail at startup? If it is built with Go 1.15.5, go version /path/to/kubectl would likely work and print the Go version. Could you try that? Thanks.

No so kubectl works until I try to kubectl get pods. So like, any time it tries to make a network request. When I run go version /path/to/kubectl I get zsh: command not found: go. I don't know if macOS is supposed to have go installed by default, but yeah I don't have it on my machine. But I've never had to install it to get kubectl to work.

No so kubectl works until I try to kubectl get pods

That looks like kubectl probably spawns a subprocess and that subprocess fails. Would it be possible to find out what that subprocess is?
Yeah, kubectl should work without installing Go. If you don't mind, you could install Go from https://golang.org/dl/ . Or if your kubectl binary is downloaded from the internet, could you provide the URL for that binary? Thanks.

Update: turns out that the problem is solved if aws-iam-authenticator gets installed via homebrew. Not exactly sure why, but my guess is they have an updated version in homebrew. So as for me, everything is working now. They must be using an older version of go or something. 🤷

@koryhutchison Yeah, I think you're right. The newly installed aws-iam-authenticator is probably built with a new version of Go. Thanks!

With regards to docker-machine not working. I found a fork repo from Gitlab that has kept the docker-machine project active, with builds using more up to date Go versions. This has fixed my issue.
The link to the builds are here https://gitlab-docker-machine-downloads.s3.amazonaws.com/main/docker-machine-Darwin-x86_64

It appears that this issue only occurs with binaries built with old unsupported versions of Go. Closing. See https://github.com/golang/go/wiki/MacOS12BSDThreadRegisterIssue
If anyone has a reproduce with a program built with Go 1.16 or later, feel free to reopen. Thanks.

I'm having this same issue but with my own go executables compiled using go 1.17.2

@rokjoana What binary it is?  Also, could you check if the binary spawns a subprocess that may be an old binary?

I'm using just go build -v -o binary-name. Our application is not spawning any subprocess from other binaries directly.

@rokjoana Could you paste the error message you saw? Could you double check your Go version? Go 1.17.2 does not have the "bsdthread_register" error message, so it must be something else. What is the output  of go version your-binary?

I reviewed the compiling steps and it was actually a custom tool used before compilation that was failing. But even so, its compiled in go 1.17.2 and its giving the following error:
fatal error: runtime: bsdthread_register error

runtime stack:
runtime.throw(0x1573b72, 0x21)
        /usr/local/go/src/runtime/panic.go:619 +0x81 fp=0x7ff7bfeff5b8 sp=0x7ff7bfeff598 pc=0x1029531
runtime.goenvs()
        /usr/local/go/src/runtime/os_darwin.go:129 +0x83 fp=0x7ff7bfeff5e8 sp=0x7ff7bfeff5b8 pc=0x10270b3
runtime.schedinit()
        /usr/local/go/src/runtime/proc.go:496 +0xa4 fp=0x7ff7bfeff640 sp=0x7ff7bfeff5e8 pc=0x102bdf4
runtime.rt0_go(0x7ff7bfeff670, 0x3, 0x7ff7bfeff670, 0x1000000, 0x3, 0x7ff7bfeff840, 0x7ff7bfeff845, 0x7ff7bfeff84c, 0x0, 0x7ff7bfeff851, ...)
        /usr/local/go/src/runtime/asm_amd64.s:252 +0x1f4 fp=0x7ff7bfeff648 sp=0x7ff7bfeff640 pc=0x1051ee4

the command used compile the tool is the following
CGO_ENABLED=0 GOOS=darwin GOARCH=amd64 go build -a -ldflags -X 'main.version=v1.9.0' -o ../../release/Darwin/x86_64/kiya/bin/kiya ./cmd_list.go ./flags.go ./cmd_delete.go ./utils.go ./cmd_template.go ./cmd_put_paste_generate.go ./main.go ./cmd_move.go

the go version for that binary is returning
$ go version release/kiya-Darwin-x86_64
release/kiya-Darwin-x86_64: go1.17.2

I ended up running the binary successfully by removing the unnecessary CGO_ENABLED=0. Thanks for your help @cherrymui .

@rokjoana Thanks. It is still weird that in Go 1.17.2 the line at runtime/os_darwin.go:129 cannot panic.

-installsuffix cgo

Maybe there are some old files in your $GOROOT/pkg/darwin_amd64_cgo directory that confused it? That would be weird, too. Anyway, good to know it is solved :)

Hello,
I add this message to say that the same error occured on my side when trying to use the "gitlab-runner" CLI on my macOS Monterey 12.0.1.
After reading all messages, I tried to update it with brew as suggested and I no longer have the error.
Thank you all

If anyone still have this issue, I installed the last official version of the deprecated project they had a last release in Sep 02, 2019, with the Gitlab fork some machines with older hosts were not working.
Install on liner:
curl -L https://github.com/docker/machine/releases/download/v0.16.2/docker-machine-uname -s-uname -m >/usr/local/bin/docker-machine &&
chmod +x /usr/local/bin/docker-machine

Hi all, I am also facing the same issue
I have upgraded to macos monteray and I am just running simple git command so getting this below error
`fatal error: runtime: bsdthread_register error
runtime stack:
runtime.throw(0x115021a, 0x21)
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/runtime/panic.go:616 +0x81 fp=0x7ff7bfeff0d8 sp=0x7ff7bfeff0b8 pc=0x1027a21
runtime.goenvs()
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/runtime/os_darwin.go:129 +0x83 fp=0x7ff7bfeff108 sp=0x7ff7bfeff0d8 pc=0x10255a3
runtime.schedinit()
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/runtime/proc.go:501 +0xd6 fp=0x7ff7bfeff170 sp=0x7ff7bfeff108 pc=0x102a316
runtime.rt0_go(0x7ff7bfeff1a0, 0x3, 0x7ff7bfeff1a0, 0x1000000, 0x3, 0x7ff7bfeff408, 0x7ff7bfeff433, 0x7ff7bfeff447, 0x0, 0x7ff7bfeff44f, ...)
/home/travis/.gimme/versions/go1.10.2.linux.amd64/src/runtime/asm_amd64.s:252 +0x1f4 fp=0x7ff7bfeff178 sp=0x7ff7bfeff170 pc=0x104f2c4
`

@sameer-dighe See
https://github.com/golang/go/wiki/MacOS12BSDThreadRegisterIssue
or
https://zchee.github.io/golang-wiki/MacOS12BSDThreadRegisterIssue/ (my personal fork of golang wiki with mkdocs)

This program means which program @zchee

https://gitlab-docker-machine-downloads.s3.amazonaws.com/main/docker-machine-Darwin-x86_64

@DeanWronowski Could you provide a bit more details how you installed custom docker machine.
I use command:
base=https://gitlab-docker-machine-downloads.s3.amazonaws.com/main/docker-machine-Darwin-x86_64 \   && curl -L $base/docker-machine-$(uname -s)-$(uname -m) >/usr/local/bin/docker-machine \   && chmod +x /usr/local/bin/docker-machine
but during checking docker-machine ls I'm getting:
/usr/local/bin/docker-machine: line 1: syntax error near unexpected token newline'
/usr/local/bin/docker-machine: line 1: <?xml version="1.0" encoding="UTF-8"?>'

Am still getting this error while trying to use git commit, can some one please help to see how I can resolve it
git version: 2.35.0
go version: go1.17.6 darwin/amd64

@justme-sports git by itself is not a Go program.  You'll need to find out what that is (such as by looking at .git/hooks) and rebuild that program with a newer version of Go.

@justme-sports git by itself is not a Go program.  You'll need to find out what that is (such as by looking at .git/hooks) and rebuild that program with a newer version of Go.

@cherrymui Thanks so much for the information, really grateful. I do see gofmt in my /usr/local/bin/ folder.
Can you please help me: When we say rebuild the program with newer version of Go, how should i do it ?
Appreciate all your help so much!

@justme-sports you can copy GOROOT/bin/gofmt to /usr/local/bin/, where GOROOT is the top-level directory of your Go 1.17.6 installation.

Still facing the same issue!! is there a way we can screen share to look at this ?

I can confirm having this issue (and it is expected) after upgrade to macOS Monterey Version 12.2 (21D49) with https://github.com/shyiko/kubesec . It's latest version of binary compiled for macOS back in 2019 was built with go 1.9.1 ....
$ kubesec --version

atal error: runtime: bsdthread_register error

runtime stack:
runtime.throw(0x156bf2a, 0x21)
	/home/shyiko/Development/golang/go1.9.1.linux-amd64/src/runtime/panic.go:605 +0x95 fp=0x7ff7bfeff060 sp=0x7ff7bfeff040 pc=0x1029ad5
runtime.goenvs()
	/home/shyiko/Development/golang/go1.9.1.linux-amd64/src/runtime/os_darwin.go:108 +0x83 fp=0x7ff7bfeff090 sp=0x7ff7bfeff060 pc=0x1027373
runtime.schedinit()
	/home/shyiko/Development/golang/go1.9.1.linux-amd64/src/runtime/proc.go:482 +0xa1 fp=0x7ff7bfeff0d0 sp=0x7ff7bfeff090 pc=0x102c481
runtime.rt0_go(0x7ff7bfeff108, 0x2, 0x7ff7bfeff108, 0x0, 0x1000000, 0x2, 0x7ff7bfeff378, 0x7ff7bfeff380, 0x0, 0x7ff7bfeff38a, ...)
	/home/shyiko/Development/golang/go1.9.1.linux-amd64/src/runtime/asm_amd64.s:175 +0x1eb fp=0x7ff7bfeff0d8 sp=0x7ff7bfeff0d0 pc=0x1053d4b

Just updated with Software Updates to macOS Monterey 12.2.1 and each binary became broken. Tested with either<EMAIL_ADDRESS>or<EMAIL_ADDRESS>using brew.

I had to the system reformat unfortunately due to this issue !! @serhiiromaniuk and @azec-pdx

@justme-sports it's totally not a fix, reformatting or deleting some stuff

So, as @zchee mentioned before, https://github.com/golang/go/wiki/MacOS12BSDThreadRegisterIssue
we should rebuild our software tools

@justme-sports Did you resolve the issue with your git? or you reformat your system.  I have the same issue and I removed the GO but the reference is still there and folder does not exist.

@justme-sports Did you resolve the issue with your git? or you reformat your system. I have the same issue and I removed the GO but the reference is still there and folder does not exist.

Unfortunately as much as I hate the reformat route, I had to go that route - when i faced this issue there was not much guidance on what could have been done to solve it !!

If anyone still have this issue, I installed the last official version of the deprecated project, they had a last release in Sep 02, 2019, with the Gitlab fork some machines with older hosts were not working. Install one liner:
curl -L https://github.com/docker/machine/releases/download/v0.16.2/docker-machine-`uname -s`-`uname -m` >/usr/local/bin/docker-machine && \
  chmod +x /usr/local/bin/docker-machine

still worked.thanks

I've started getting the same error with git 2.30.1 on MacOS Monterey 12.3.1 after having upgraded Command Line Tools.  The following error only happened to git commit and no other git commands:
fatal error: runtime: bsdthread_register error

runtime stack:
runtime.throw(0x1364ecc, 0x21)
	/usr/local/go/src/runtime/panic.go:616 +0x81 fp=0x7ff7bfeff2c8 sp=0x7ff7bfeff2a8 pc=0x1028e51
runtime.goenvs()
	/usr/local/go/src/runtime/os_darwin.go:129 +0x83 fp=0x7ff7bfeff2f8 sp=0x7ff7bfeff2c8 pc=0x10269d3
runtime.schedinit()
	/usr/local/go/src/runtime/proc.go:501 +0xd6 fp=0x7ff7bfeff360 sp=0x7ff7bfeff2f8 pc=0x102b746
runtime.rt0_go(0x7ff7bfeff398, 0x4, 0x7ff7bfeff398, 0x0, 0x1000000, 0x4, 0x7ff7bfeff5e0, 0x7ff7bfeff5ef, 0x7ff7bfeff5f4, 0x7ff7bfeff5fb, ...)
	/usr/local/go/src/runtime/asm_amd64.s:252 +0x1f4 fp=0x7ff7bfeff368 sp=0x7ff7bfeff360 pc=0x1051804

Following the tips above about 1) this being caused by an old version of some go program and 2) git isn't a go program itself therefore there must be some hook in place,
I found an old hook in my global git configuration and managed to fix this error removing it via
git config --global --unset core.hookspath

One of our team had this problem recently, turns out the version of kubectl we were downloading was not the one being executed (despite being first in PATH) but rather an older version of kubectl which was part of Docker CE, installation of the latest Docker resolved the issue. Though still leaves the mystery as to why the downloaded version was ignored despite being first in the PATH.

in my case I had this line for kops completion in my zshrc file, which caused the problem:
source <(kops completion zsh)
removed it and the problem is vanished.


Send milliseconds in timestamp to Logstash. Reduce dependencies. Add TCP (+optional SSL)

I installed this yesterday and noticed that the milliseconds were missing from all my timestamps. This PR fixes that issue. I've also modernized the date / time handling code and made the JSON encoder module configurable (also changed the default to Jason).
I've updated the TravisCI config to remove Elixir 1.3.0 from the build targets.

And now also updated to gracefully handle not being able to reach logstash (so your whole app doesn't crash if logstash is down for whatever reason).

I've updated this further to add some timeouts. We were having issues where a new deploy of our app wasn't detecting a closed connection for an hour before it crashed and re-opened the connection. That should happen much quicker now.

Hi @marcelog, I've just been adding to and improving this PR as I go along, any chance you'll be able to find some time to review it soon?


Feature: Multiple colors in themes and automatic mapping

Bug, feature request, or proposal:
Feature request
What is the expected behavior?
It would be great to be able to pass in a single color to md-palette() and automatically generate the map, as well as using more colors for brands with >3 main colors.
What is the current behavior?
Theming is limited to three built-in colors, and you have to create your own map to customize with brand colors.
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: http://plnkr.co/edit/o077B6uEiiIgkC0S06dd
What is the use-case or motivation for changing an existing behavior?
Many developers will want to customize the built-in colors, and may want to extend to more than 3 colors.
Which versions of Angular, Material, OS, browsers are affected?
All
Is there anything else we should know?
Take a look at Ionic Framework's theming, which allows you to pass in an unlimited number of colors.

I am finding it difficult to use material2, because my organization has very specific brand colors that I am trying to match.

I agree, I really need to be able to define more than 3 colors !

There's no algorithm for generating such map, the ux guys that are working on the material design spec handpicked (and i'm not kidding) each color.
if you want your own palette you can create a scss variable like this one and pass it to the md-palette mixin

Yeah I know there isn't a real algorithm, but perhaps a mock algorithm that is close to the MD spec is in order.

There's really no simple way to compute a range of colors and contrast colors from a single point in the spectrum. It's something a machine learning algorithm could probably handle, but not something we could handle in scss :wink:
Our current thinking is that it's not too burdensome to create a palette matching the format of our's: https://github.com/angular/material2/blob/master/src/lib/core/theming/_palette.scss


TipKit Implementation

A tip should be shown only the first time.
For reseting "the first time" need .task { try? Tips.resetDatastore() }

Just a blank space floating over one line, but seems a good integration of TipKit!!!


Add requires.io badge to README

Hi,
Adding a badge I was talking about.
I think it would be useful to enable notifications about outdated versions from this service.

@webknjaz Talking about where? I can't find the conversation.

In PR correcting dependencies

Go for it.
I'm still getting the hang of JazzBand; are you allowed to merge yourself or do I need to do something?

I don't have such permissions on this repo

@aaugustin everything is pretty much the same as any other repo, except that you have a greater pool of devs who can review and merge pull requests  ;)

I just noticed that the [Jazzband member] label tells me who has merge permissions.

Hey all, welcome to the Jazzband :)
This isn't entirely unexpected, so don't fret, the change in this URL ironically doesn't work since it points to the old requires.io URL. The badge code should be:
.. image:: https://requires.io/github/jazzband/django-debug-toolbar/requirements.svg?branch=master
     :target: https://requires.io/github/jazzband/django-debug-toolbar/requirements/?branch=master
     :alt: Requirements Status

Ugh, requires.io is currently working through a long task queue, so activation of that URL is taking longer than expected, in case you're seeing errors behind that URL. What a demo effect this is :)


 error styles being overriden when inside a

Bug Report
Steps
Use Create react app
import semantic.min.css from semantic-ui-css package in App.js
add a  component and place a  component inside it
add the "error" flag to the  component
Expected Result
For the input to have error styles applied to it i.e. red-ish border color, red "color".
Actual Result
styles applied to .ui.form input[type=text] and .ui.input>input  override the one for the error which is .ui.input.error>input 💣
Version
semantic-ui-css 2.4.1
semantic-ui-react 0.84.0
Testcase
https://codesandbox.io/s/zkmk2l1xpx

OK I got it...noob mistake. I need to use Form.Field and Form.Input inside the Form component


I really need help with a Java program, please

Hello! I must create the next Java program, maybe you could help me, please: given two lists (you must choose the data lists lines that are considered suitable for the solution of the project: ----Simple Linear Lists, Linear Circular Lists, Double Chained Linear Lists----) polynomial1 and polynomial2, which represent polynomials, elaborate the methods that return in a list sumapoli the sum of the polynomials (polynomial1 + polynomial2) and in a list of multiplication products of the polynomials (polynomial1 * polynomial2). The list is stored in an object of the class "Polynomial" and each element of the list is an object of the class Term; at a general level, a Polynomial will be made up of a finite number of Terms. The polynomials are read through a plain text of the name "Polin.txt", with the following format:
Coefficient-1, exponent-1; Coefficient-2, exponent-2;
The file must contain ONLY two lines, where each one represents polynomial, these can not be, SECURE, that the terms are not repeated. According to the following example:
2x ^ 2 + 3x + 2
It would be represented in the plain text file as:
2.2; 3.1; 2.0
The independent term "2" will have the exponent "0". FOR EFFECTS OF THE PROBLEM, SUPPOSE THAT THE VARIABLE IS ALWAYS "X".
An interface must be created to carry out the project, objects for the operation and tests of this.
(The thing is I got the program to read plain text, but it reads the "comas" as the exponent, and I need it to read each number. I already have the Double Chained Linear Lists too).

This is not related to the repo, please ask your questions on Stack Overflow.


Angular/Aurelia/React Template: IE9 Support

Hi
Currently using the latest version of the generator, 0.6.1, the Angular 2 Template is broken in IE9 due to the browser not supporting WeakMaps.

I've noticed that previously an effort was made to fix IE9 issues, https://github.com/aspnet/JavaScriptServices/issues/172. Thinking a shim could maybe be added to improve legacy browser support? IE10 and up is working beautifully 👌

Also as per #504 we need to polyfill Object.assign.

Also as per #386, we need to polyfill Promise for the Aurelia template.

With regards to the Redux template ... I've just added
import 'es5-shim';
import 'es6-shim';

to boot-client.tsx (and made npm installs of course).

Hi,
Is there any update on this. Have been experiencing the same issue as #891 and #926.

Sorry but no. If there was an update it would be posted here already.

Hi Steve, Thank you for your response. Is there any chance on this getting fixed. We followed the guide on browser support and are more than half way through our project.

I can't speak for Aurelia and React as I'm not sure this fixes those, but for Angular you need these polyfills:

/***************************************************************************************************
 * BROWSER POLY FILLS
 */

/** IE9, IE10 and IE11 requires all of the following polyfills. **/
 import 'core-js/es6/symbol';
 import 'core-js/es6/object';
 import 'core-js/es6/function';
 import 'core-js/es6/parse-int';
 import 'core-js/es6/parse-float';
 import 'core-js/es6/number';
 import 'core-js/es6/math';
 import 'core-js/es6/string';
 import 'core-js/es6/date';
 import 'core-js/es6/array';
 import 'core-js/es6/regexp';
 import 'core-js/es6/map';
 import 'core-js/es6/set';

/** IE10 and IE11 requires the following for NgClass support on SVG elements */
// import 'classlist.js';  // Run `npm install --save classlist.js`.

// import 'web-animations-js';  // Run `npm install --save web-animations-js`.

/** Evergreen browsers require these. **/
import 'core-js/es6/reflect';
import 'core-js/es7/reflect';

/**
 * Date, currency, decimal and percent pipes.
 * Needed for: All but Chrome, Firefox, Edge, IE11 and Safari 10
 */
// import 'intl';  // Run `npm install --save intl`.

IE polyfills is no longer something we'd control from the code in this repo (or the templating repo). Since we're now moving to use the standard project structures for each SPA framework (e.g., Angular CLI, create-react-app), the decision on whether or not to include polyfills would come from the SPA frameworks themselves.


Installation guide and welcome screen

This issue tracks the addition of a general installation screen when any of the kraftkit programs is used for the first time.  The purpose of this screen is to help guide users with a mini-tutorial but also help customize their installation, e.g. with configuration options.

Is this still an ongoing issue?

Yes it is! We can assign you if you would like to tackle it.
This starts with introducing a new subcommand to kraft called kraft config set which modifies user's configuration and sets a corresponding value, e.g.:
kraft config set log-level trace

This will update ~/.config/kraftkit/config.yaml to have log_level: trace.
Once this is done, we can utilize this subcommand following a successful installation and provide a few prompts for setting values:

Whether they would like kraft to check for updates;
Whether they would like to use an existing buildkit installation;
Whether they would like to use containerd as a store.
(Not related to kraft config set) Whether they would like to perform an initial package update (kraft pkg update).


Start of documentation

Here's some basic READMEs to get us started

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Can you add the following to the readme?
**Want to learn more?** Reach out on [the Slack channel](https://fairwindscommunity.slack.com/messages/fairwinds-insights-support), send an email to<EMAIL_ADDRESS>or join us for [office hours on Zoom](https://fairwindscommunity.slack.com/messages/office-hours)

The office hours stuff I have at the bottom, line 26, want me to move to the top?

You can check out rok8s-scripts or rbac-manager for where we normally put it - usually right under the description

Sure enough that's pretty consistently handled. Moving it up


License

This code needs a license or it remains proprietary regardless of whether we can see the code.

License added (see commit 80268e2fa971389a3e94c430966a7943c2631dbf), but I'm not sure this is going to stop MGame from coming for you.


Script errors can be seen when you source the mysql 5.7 scripts against DB.

Script errors can be seen when you source the mysql 5.7 scripts against DB.
Server version: 5.7.17
Note :  I have renamed mysql-5.7.sql as mysql.sql
mysql> source /home/ushani/WSO2_WORK/Products/IS/5.5.0/alpha2/wso2is-5.5.0-alpha2/dbscripts/mysql.sql
Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.19 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.18 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.08 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.08 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.19 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.23 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected, 1 warning (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 1

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.18 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.18 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.19 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.18 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.17 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.18 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.16 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.18 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.05 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.20 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected, 1 warning (0.05 sec)
Records: 0  Duplicates: 0  Warnings: 1

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.05 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.11 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.05 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.06 sec)

mysql> source /home/ushani/WSO2_WORK/Products/IS/5.5.0/alpha2/wso2is-5.5.0-alpha2/dbscripts/identity/mysql.sql
Query OK, 0 rows affected (0.07 sec)

Query OK, 1 row affected (0.01 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.08 sec)

ERROR 1067 (42000): Invalid default value for 'TIME_CREATED'
ERROR 1146 (42S02): Table 'WSO2CarbonDB.IDN_OAUTH2_ACCESS_TOKEN' doesn't exist
ERROR 1146 (42S02): Table 'WSO2CarbonDB.IDN_OAUTH2_ACCESS_TOKEN' doesn't exist
ERROR 1146 (42S02): Table 'WSO2CarbonDB.IDN_OAUTH2_ACCESS_TOKEN' doesn't exist
Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.05 sec)
Records: 0  Duplicates: 0  Warnings: 0

ERROR 1215 (HY000): Cannot add foreign key constraint
Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.07 sec)

ERROR 1067 (42000): Invalid default value for 'EXPIRE_DATE'
Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.06 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.16 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.20 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.18 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.17 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.16 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.17 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.16 sec)
Records: 0  Duplicates: 0  Warnings: 0

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.05 sec)

Query OK, 0 rows affected (0.06 sec)

ERROR 1067 (42000): Invalid default value for 'UPDATED_AT'
Query OK, 0 rows affected (0.05 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.06 sec)

ERROR 1215 (HY000): Cannot add foreign key constraint
ERROR 1215 (HY000): Cannot add foreign key constraint
Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.09 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.07 sec)

Query OK, 0 rows affected (0.06 sec)

Query OK, 0 rows affected (0.08 sec)

Query OK, 0 rows affected (0.05 sec)

Query OK, 0 rows affected (0.05 sec)

Query OK, 0 rows affected (0.07 sec)

ERROR 1215 (HY000): Cannot add foreign key constraint
ERROR 1215 (HY000): Cannot add foreign key constraint
ERROR 1215 (HY000): Cannot add foreign key constraint
Query OK, 0 rows affected (0.07 sec)

mysql>
mysql>
mysql> show tables;
+-------------------------------+
| Tables_in_WSO2CarbonDB        |
+-------------------------------+
| FIDO_DEVICE_STORE             |
| IDN_ASSOCIATED_ID             |
| IDN_AUTH_SESSION_STORE        |
| IDN_BASE_TABLE                |
| IDN_CERTIFICATE               |
| IDN_CLAIM                     |
| IDN_CLAIM_DIALECT             |
| IDN_CLAIM_MAPPED_ATTRIBUTE    |
| IDN_CLAIM_MAPPING             |
| IDN_CLAIM_PROPERTY            |
| IDN_IDENTITY_META_DATA        |
| IDN_IDENTITY_USER_DATA        |
| IDN_OAUTH1A_ACCESS_TOKEN      |
| IDN_OAUTH1A_REQUEST_TOKEN     |
| IDN_OAUTH2_AUTHORIZATION_CODE |
| IDN_OAUTH2_RESOURCE_SCOPE     |
| IDN_OAUTH2_SCOPE              |
| IDN_OAUTH2_SCOPE_BINDING      |
| IDN_OAUTH2_SCOPE_VALIDATORS   |
| IDN_OAUTH_CONSUMER_APPS       |
| IDN_OIDC_JTI                  |
| IDN_OIDC_PROPERTY             |
| IDN_OPENID_ASSOCIATIONS       |
| IDN_OPENID_REMEMBER_ME        |
| IDN_OPENID_USER_RPS           |
| IDN_PASSWORD_HISTORY_DATA     |
| IDN_RECOVERY_DATA             |
| IDN_SAML2_ASSERTION_STORE     |
| IDN_SCIM_GROUP                |
| IDN_THRIFT_SESSION            |
| IDN_USER_ACCOUNT_ASSOCIATION  |
| IDP                           |
| IDP_AUTHENTICATOR             |
| IDP_AUTHENTICATOR_PROPERTY    |
| IDP_CLAIM                     |
| IDP_CLAIM_MAPPING             |
| IDP_LOCAL_CLAIM               |
| IDP_METADATA                  |
| IDP_PROVISIONING_CONFIG       |
| IDP_PROVISIONING_ENTITY       |
| IDP_PROV_CONFIG_PROPERTY      |
| IDP_ROLE                      |
| IDP_ROLE_MAPPING              |
| REG_ASSOCIATION               |
| REG_CLUSTER_LOCK              |
| REG_COMMENT                   |
| REG_CONTENT                   |
| REG_CONTENT_HISTORY           |
| REG_LOG                       |
| REG_PATH                      |
| REG_PROPERTY                  |
| REG_RATING                    |
| REG_RESOURCE                  |
| REG_RESOURCE_COMMENT          |
| REG_RESOURCE_HISTORY          |
| REG_RESOURCE_PROPERTY         |
| REG_RESOURCE_RATING           |
| REG_RESOURCE_TAG              |
| REG_SNAPSHOT                  |
| REG_TAG                       |
| SP_APP                        |
| SP_AUTH_SCRIPT                |
| SP_AUTH_STEP                  |
| SP_CLAIM_MAPPING              |
| SP_FEDERATED_IDP              |
| SP_INBOUND_AUTH               |
| SP_METADATA                   |
| SP_PROVISIONING_CONNECTOR     |
| SP_REQ_PATH_AUTHENTICATOR     |
| SP_ROLE_MAPPING               |
| UM_ACCOUNT_MAPPING            |
| UM_CLAIM                      |
| UM_DIALECT                    |
| UM_DOMAIN                     |
| UM_HYBRID_REMEMBER_ME         |
| UM_HYBRID_ROLE                |
| UM_HYBRID_USER_ROLE           |
| UM_MODULE                     |
| UM_MODULE_ACTIONS             |
| UM_PERMISSION                 |
| UM_PROFILE_CONFIG             |
| UM_ROLE                       |
| UM_ROLE_PERMISSION            |
| UM_SHARED_USER_ROLE           |
| UM_SYSTEM_ROLE                |
| UM_SYSTEM_USER                |
| UM_SYSTEM_USER_ROLE           |
| UM_TENANT                     |
| UM_USER                       |
| UM_USER_ATTRIBUTE             |
| UM_USER_PERMISSION            |
| UM_USER_ROLE                  |
| WF_BPS_PROFILE                |
| WF_WORKFLOW                   |
| WF_WORKFLOW_ASSOCIATION       |
| WF_WORKFLOW_CONFIG_PARAM      |
+-------------------------------+
96 rows in set (0.00 sec)

For the time being I proceeded after using https://github.com/wso2/carbon-identity-framework/tree/5.11.x/features/identity-core/org.wso2.carbon.identity.core.server.feature/resources/dbscripts script

This cannot be reproduced with the "mysql-5.7.sql" script. However, same error log could be observed when "mysql.sql" (which is supposed to use with mysql 5.6 and below) script is used.


bootloader: Switch to using bootupd to do BIOS

install: use ghcr.io for oscore
See https://github.com/cgwalters/bootc-demo-base-images/commit/2917d146b86b339bae4b3bbf1f848301b48386aa

bootloader: Switch to using bootupd to do BIOS
This means we now get unified management.

@HuijingHei This uses your changes to bootupd!


Format error: 'list_iterator' object has no attribute 'next'

I am using Sublime Text version 3 with the package CodeFormatter.
All the formaters works great, except the HTML part.
WHen i tried to use that, i am receiving this error:
Format error: 'list_iterator' object has no attribute 'next'

This will be addressed by #219.

@RevanProdigalKnight  Nice,it worked!

thanks buddy!

@RevanProdigalKnight yes, I did... and it worked out???? Thanks :dancer:


Add responsive margin-bottom utility classes

A pluggable margin-bottom that is 20px in xs, 30px in sm/md, and 40px in lg.
This is something I find myself needing increasingly in diverse projects. Who knows if I need a margin on component XYZ? Shouldn't be built-in into the component, but optional, IMO.
I also keep anti-component-margin classes undoing the previous components margin (by negative margin-top), for example when an element with component-margin is visible only in certain screen sizes.
Dunno if it can be something to add as a responsive utility.
@component-margin-xs: 20px;
@component-margin-sm: 30px;
@component-margin-md: 30px;
@component-margin-lg: 40px;

.component-margin {
  margin-bottom: @component-margin-xs;

  @media (min-width: @screen-sm-min) {
    margin-bottom: @component-margin-sm;
  }
  @media (min-width: @screen-md-min) {
    margin-bottom: @component-margin-md;
  }
  @media (min-width: @screen-lg-min) {
    margin-bottom: @component-margin-lg;
  }
}

.component-margin-xs {
  margin-bottom: @component-margin-xs;

  @media (min-width: @screen-sm-min) {
    margin-bottom: 0;
  }
}

.component-margin-sm {
  @media (min-width: @screen-sm-min) {
    margin-bottom: @component-margin-sm;
  }
  @media (min-width: @screen-md-min) {
    margin-bottom: 0;
  }
}

.component-margin-md {
  @media (min-width: @screen-md-min) {
    margin-bottom: @component-margin-md;
  }
  @media (min-width: @screen-md-min) {
    margin-bottom: 0;
  }
}

.component-margin-lg {
  @media (min-width: @screen-lg-min) {
    margin-bottom: @component-margin-lg;
  }
}

Thanks, but we'll pass for now. Too many utility classes and if we do this one direction, folks will ask and expect all four directions.

This is too bad. The new responsive helpers (e.g. text-xs-left, pull-md-right) are useful, but if it came down to it, I'd rather have responsive spacing helpers. They go well with the grid system.
I will often build something out using the grid classes, then still end up having to target specific elements in CSS, only to adjust margins at specific widths.
Maybe in a future version? Let's hope!