Editor/Linting Advice?

Hi,
I'm really appreciating this great package! The one thing that's giving me a headache is linting in my editor (I'm currently using VS Code). I can't seem to configure it correctly recognize the header files. I'm following the docs on Cargo-based builds.
It seems like you're doing some very fancy magic to make all of the headers available at compile time, but it doesn't seem like any header files are actually being written to disk. Any advice here would be appreciated!
Thanks,
Oliver

They are written to disk. I don't use VS Code so I can't directly help, but you'd need to make sure the editor's/linter's C++ include path contains the directories that build.rs feeds to the C++ compiler invocation. includePath in https://code.visualstudio.com/docs/cpp/c-cpp-properties-schema-reference seems relevant. If you put a panic!() at the bottom of build.rs it'll print out the list of include directories under a heading "CXX include path".

They are written to disk. I don't use VS Code so I can't directly help, but you'd need to make sure the editor's/linter's C++ include path contains the directories that build.rs feeds to the C++ compiler invocation. includePath in https://code.visualstudio.com/docs/cpp/c-cpp-properties-schema-reference seems relevant. If you put a panic!() at the bottom of build.rs it'll print out the list of include directories under a heading "CXX include path".

Thanks! I've been struggling with VSCode includePath for C++ unrelated to cxx, but I think I just got it working using bear to generate compile_commands.json which VSCode will read to know the specific import paths for each file.
I just did bear -- cargo build, which produces compile_commands.json in the project root, then set "compileCommands": "./compile_commands.json" in my configuration in .vscode/c_cpp_properties.json. The squiggly lines have disappeared!
One concern, though, is that cxx seems to append a hash to the generated directory name, e.g. target/debug/build/my-project-754f540b5e93b54c/out/cxxbridge/include. I have multiple versions of this in my target directory. How can I know when a new one will be generated and I should re-run bear -- cargo build?

Thanks! I've been struggling with VSCode includePath for C++ unrelated to cxx, but I think I just got it working using bear to generate compile_commands.json which VSCode will read to know the specific import paths for each file.
I just did bear -- cargo build, which produces compile_commands.json in the project root, then set "compileCommands": "./compile_commands.json" in my configuration in .vscode/c_cpp_properties.json. The squiggly lines have disappeared!
One concern, though, is that cxx seems to append a hash to the generated directory name, e.g. target/debug/build/my-project-754f540b5e93b54c/out/cxxbridge/include. I have multiple versions of this in my target directory. How can I know when a new one will be generated and I should re-run bear -- cargo build?

That's done by cargo, not cxx. I would guess probably when you change cargo versions would be sufficient.

That's done by cargo, not cxx. I would guess probably when you change cargo versions would be sufficient.

Great, thanks a lot!

Great, thanks a lot!


fix(og:image): use absolute path

Closes https://github.com/carbon-design-system/carbon-website/issues/2987
Uses the absolute path to the static GitHub hosted image rather than a relative path.
Changelog
Changed

changed og:image URL to an absolute path rather then relative

@tay1orjones any idea why this build is failing?


Just adding it to a UIImageView

Hi Daniel,
I am just attempting to add the curved label to a UIImageView. It doesn't seem to be rendering the text though. I create the same UILabel and add it to the view and it works (without the curved part). But then when I add the curved label (DGCurvedLabel) it doesn't work... Heres the code
- (void)layoutSubviews {
    [super layoutSubviews];

    self.profileImageView.frame = CGRectMake( 0.0f, 0.0f, self.frame.size.width, self.frame.size.height);
    self.profileButton.frame = CGRectMake( 0.0f, 0.0f, self.frame.size.width, self.frame.size.height);
    self.curvedLabel.frame = CGRectMake( 10.0f, 10.0f, self.frame.size.width - 20, self.frame.size.height - 20);
}
- (void)setUserForImage:(PFUser *)user
{
    [self.curvedLabel setText:[user objectForKey:kPHUserFirstNameKey]];
}
- (DGCurvedLabel *)curvedLabel
{
    if (!_curvedLabel) {
        _curvedLabel = [[DGCurvedLabel alloc] init];
        [_curvedLabel setFont:[UIFont fontWithName:kPHFont size:16.0f]];
        [_curvedLabel setBackgroundColor:[UIColor clearColor]];
        [_curvedLabel setTextInside:YES];
    }
    return _curvedLabel;
}

Sorry for the additional code but I just copy and pasted. So I have a lazy loading DGCurvedLabel and I add it to the subview in the initializer method. The current class that this is all embedded in is a UITableViewCell. If I change DGCurvedLabel to a UILabel, it works as said before. But then changing it back to a DGCurvedLabel, nothing is being rendered... But maybe it is but it may be outside the bounds of the UIImageView? But I explicitly set the frame of the Label in layoutSubviews. Any ideas?

Have you set the 'radius' around which you wNt to curve the label?

Hi Daniel,
Yes I have set it to 5.0f

On Feb 19, 2015, at 10:41 AM, Daniel Cohen Gindi<EMAIL_ADDRESS>wrote:
Have you set the 'radius' around which you wNt to curve the label?
—
Reply to this email directly or view it on GitHub https://github.com/danielgindi/DGCurvedLabel/issues/1#issuecomment-75110176.

Well I'd have to take a look at it...
In the meanwhile can play with it in Interface Builder just to see how it behaves with the same data you are passing.

Aight no prob. Thanks for your quick response

On Feb 19, 2015, at 10:47 AM, Daniel Cohen Gindi<EMAIL_ADDRESS>wrote:
Well I'd have to take a look at it...
In the meanwhile can play with it in Interface Builder just to see how it behaves with the same data you are passing.
—
Reply to this email directly or view it on GitHub https://github.com/danielgindi/DGCurvedLabel/issues/1#issuecomment-75111247.

If you want to give me the exact inputs, like frame, text, radius etc - that could help in reproducing the problem

Any news on that?


FEATURE: basic progress for image generation

previously you would have to wait quite a while to see the prompt this implements
a very basic implementation of progress so you can see the api is working.

failure is unrelated ...


Update release tags to install via pip

Would it be possible to update the release tags such that installing flask-unittest with the latest fix https://github.com/TotallyNotChase/flask-unittest/pull/4 could be done through pip. Currently the release tags 0.1.2 does not include this fix

whoops, I had forgotten to do this. I uploaded v0.1.3, let me know if it works for you.

Amazing! It works now. Thank you!  :)


Live Server Fails to initiate localhost

I'm submitting a...
Malfunction, error, or issue

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
[x ] Other: <!-- Please describe: -->

Current behavior
No response when attempting to run Live Server

Expected behavior
Live Server should initiate localhost <IP_ADDRESS>:5500 nothing happens no error no warning and local hosted webpages time out.

Environment
OS Version: Windows 10.0.19043 N/A Build 19043
VSCode: 1.57.1
Browser:

- [ X] Chrome (desktop) version XX
- [ X] Firefox version 90.0b12(64bit) dev
- [ ] Safari (desktop) version 93.0.4557.4 dev
- [ ] IE version XX
- [ ] Edge version XX

For Tooling issues:

- Live Server: <!-- Check which version is installed -->
- Platform:  <!-- Windows 10.0.19043 N/A Build 19043 -->
- Visual Studio Code: <!-- 1.57.1 -->

Others

Issue resolved:
FIx:  ctrl+shift+p to bring up the command pallete
Type "reload" to bring up all developer options
Select: Developer: reload with extensions disabled , VSCode will prompt to reload with the extensions enabled (DO IT)
This should resolve the issue of Live Server not responding or running a local host server.


svn: E170001: Authentication error from server: Internal server error in authentication

Hi,
First of all great project, I tried to migrate my old (dsm 6.x) based SVN data directory to your system.. using the instructions. That all was straight forward. Except when I try to checkout the repository I get this error:
svn co svn://<IP_ADDRESS>/lumina
svn: E170013: Unable to connect to a repository at URL 'svn://<IP_ADDRESS>/lumina'
svn: E170001: Authentication error from server: Internal server error in authentication

So my SVN repo is in place.. my directory structure looks like:
/volume1/svn/svnserver.svn.mh/volume/svnrepo/lumina
I cannot get it work.. any suggestions?

check user/password in file conf/passwd
https://github.com/MarkusH1975/svnserver.svn.mh#svn-access-control

Closed

See updated ACL:
https://github.com/MarkusH1975/svnserver.svn.mh#svn-access-control


feat(web-app): create library catalog component

Closes #371
Changelog
New

LibraryCatalog Component

Changed

Refactored libraries page to use LibraryCatalog component
small tweak on sort to Catalog component

Testing / reviewing
Test search and filter, make sure the individual library card looks same as in prod:
http://localhost:3000/libraries
Ensure still works/looks the same as prod:
http://localhost:3000/catalogs/components
http://localhost:3000/catalogs/patterns
http://localhost:3000/catalogs/templates
http://localhost:3000/catalogs/functions
http://localhost:3000/collections/data-visualization

Marked as draft for now, need clarification on "Consider adding a description of libraries above search and filter"


Internal all lower-case layer leaks on searches

Visiting
https://docs.generic-mapping-tools.org/latest/search.html?q=basemap&check_keywords=yes&area=default#
gives

-b
define tick marks, annotations, and labels for basemaps and axes
-j
select a map projection or coordinate transformation
-r
define the extent of the map/plot region...

But the real page,
https://docs.generic-mapping-tools.org/latest/cookbook/options.html
shows the truth:

-B
Define tick marks, annotations, and labels for basemaps and axes
-J
Select a map projection or coordinate transformation
-R
Define the extent of the map/plot region

Indeed, there are also

-b
Select binary input and/or output

etc. on the page.
What apparently is happening is some internal all-lowercase comparison
layer, has inadvertently been leaked to public view.
Such internal layers, if any, should be well protected, and only
original-cased forms exposed.
Yes you might say, "What's the big deal? Afraid of a little lower case?"
(Let me know if this is intentional.)
Note that I am simply the lowest end user. All I used was my browser, like grandma clicking things, and never used a documentation package.

Is this still an issue? If so, feel free to re-open and expand on it. I'm not sure to understand what's happening and what's the expected behavior.


Add message matches to pytest.rases(TransactionFailure)

whenever require() texts are available.

In ./test_channel_withdraw.py, error messages are not available.  This is because of the bytecode size limit.


⚠ Bofrost.de has degraded performance

In 8e89c01, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1496 ms

Resolved: Bofrost.de performance has improved in ca5a55d.


Instructions for manually installing TF on OpenStack

From #docs on Slack today:
00:13 <sapd> I would like to install tungsten fabric with openstack queens manually.
00:13 <sapd> But I can't find any documents about that.

And also in #users:
07:29 <sapd> I would like to integrate tungsten fabirc with openstack (queens, rocky) . But I don't see any documents for manual install.
07:32 <andrey-mp> @sapd I don't know about any docs that describes how to configure installed OpenStack with new deployed TF
07:34 <sapd> Today I have installed TF on Kubernetes. But I would like to manual install to clear understand about architecture and all components
08:11 <andrey-mp> you need to provide keystone auth params to TF of existing OpenStack
08:13 <andrey-mp> in OpenStack you need to run compute/neutron/heat containers to bring required binaries/modules and then you need to configure neutron/heat
08:15 <sapd> I will check contrail-heat

Migrated to Jira: https://jira.tungsten.io/browse/TFB-1406


disqus integration

Hi,
Great theme but I am unable to get disqus comments working.
I have entered my shortname in config.js
http://mrneilypops.org

I was not able to load disqus using the config.js file.
The only way to make this was editing var disqus_shortname and var disqus_url manually on comments.hbs.
I am using the default ghost template on Digital Ocean.


Updating existing fingerprint to support both China 2017 & 2019 CRV-H

Add extra keys:
408: 6,
415: 6,
428: 8,
930: 8,
931: 8,
1626: 5,
1627: 5
new fingerprint has been tested on 2017 & 2019 CRV Hybrid (China Ver)

As usual... I'll need a cabana drive with stock system (not openpilot) of the cars you want to add support for. Tnx!

@rbiasini https://community.comma.ai/cabana/?route=c9ea5789a10a55ac|2019-06-05--23-28-32&max=2&url=https%3A%2F%2Fchffrprivate.blob.core.windows.net%2Fchffrprivate3%2Fv2%2Fc9ea5789a10a55ac%2Fc563ee5bef53ec31ae11b9482c501dd2_2019-06-05--23-28-32
here is my cabana drive log
I own this  2017 CR-V hybrid car
does this cabana link useful?:smile:

looks good. Fingerprint verified on the 2017 CR-V hybrid. Not sure about the 2019 CRV-H, but this PR is ok as is.


e9s some triggers are not working after recent update

Description
Those triggers alerted after these triggers below are not working.
E9S The Second Art Of Darkness Right
E9S The Second Art Of Darkness Left
E9S The Third Art Of Darkness Right
E9S The Third Art Of Darkness Left
I guess these trigger E9S The Second / Third Art Of Darkness Charge Solver and E9S The Second / Third Art Of Darkness Callout are not working.
Don't know if this happens on KR server only. I heard other person also had this problem.
I've checked tuesday working well. This happened after the recent update.

I've checked tuesday working well. This happened after the recent update.

This is "Final Fantasy XIV update," correct? Not "cactbot update"? Not that the recent swaths of refactoring are infallible, but I don't see anything substantial that changed in the cactbot code with respect to those triggers; however, the code for those triggers hinges upon some assumptions about the flow of the fight. What's interesting here is I feel like I wrote this code to be fairly generic; we know the first sweep based off abilityId and we simply increment from there. My fear here would be that each headMarker has been randomized individually instead of having a randomized offset. The flip side is maybe headMarkers were silently patched in one of the downstream dependencies to take account of the offset? That feels unlikely though, and I would expect this code to still work in the event that all the headMarkers were shifted by the same number.
Do you have a network log you would be able to share? I also am worried about TEA if the offset is no longer one value per instance.

ah, there wasn't game client update this week on Korean server. You might confused it because SQEX server was updated.

Nevermind, looks like @valarnin found it: https://github.com/quisquous/cactbot/issues/2995
I didn't realize that https://github.com/quisquous/cactbot/commit/ae3c263feac53003698504356be6ce8821d4a833 had only just been committed this last patch

Was about to link that PR when I noticed this issue but panic beat me to it :)

Please test all the listed triggers though, I'm not sure if my PR fixes everything, I just noticed the debug output in console when testing raidemulator changes.

umm I had only Second Art Of Darkness and Third Art Of Darkness problem.
I don't know the other zone, I only tested on e9s.

Both Second and Third art triggers use a collector -> callout pattern, so they were probably both impacted by the same issue, but the only e9s log I have handy is in chinese which I can't speak/read so I can't actually verify that this fixes everything.

I didn't have any other reports on Korean community, so I guess that's all.

I think the question would be if the Phaser callouts worked, but I think they do. I remember when that PR was first opened that I went to confirm the ordering of array shifting returning and making sure nothing broke there. But, I apparently missed the missing const in my review.

Phaser worked.


Failed to install LOOP

RaspiBlitz v1.5.1
Tried to install LOOP from the RaspiBlitz Menu System - getting this error -
Created symlink /etc/systemd/system/multi-user.target.wants/loopd.service → /etc/systemd/system/loopd.service.
OK - the Lightning Loop service is now enabled
./bonus.loop.sh: line 85: loop: command not found
Failed to install Lightning Loop
Tried running the bonus.loop.sh script manually (as directed) with same result.

There were some reports on Problems with Loop on v1.5.1 .. that should be fixed and was restested with the lastest v1.6 release. Please try that one and re-open issue if you still have problems.

So are you saying that the latest version (0.8.0) of LOOP installs and runs without any errors on RaspiBlitz v1.6 ? Has this been tested?
I had no problems installing v0.6.5  and v0.7.0 of LOOP on RaspiBlitz v1.5.1.
This 0.8.0 version is the first one to fail - maybe its a LOOP problem - worth investigating further.

On the v1.6 release we still use Loop 0.6.5 - that worked well with the rest of the setup of the 1.6.

Well yes - LOOP v0.6.5 worked fine for me too but all these third party apps are being updated with new functionality all the time, not to mention all the bug fixes, so RaspiBlitz should be taking advantage of this.
There should be a menu option to upgrade all apps to the latest versions as and when they become available.
So how do I go back to v.0.6.5 of LOOP? The git pull downloads the latest version available. Is there a parameter I can add to get a specific version?

So how do I go back to v.0.6.5 of LOOP?

Thats why maybe just putting there a button that lets user update users all apps to the latest versions not a good idea ;)
With everything changing so fast testing what works together is part of our RaspiBlitz releases - at least we try our best. Everybody is free to try updates by themselves on their own risk - we even depend on reporting on that experience ... but as you can see on your own question, if we offer something by default we are also expected to offer down-grades. But that adds a lot of additional complexity .. there could be data migrations between vesion that cannot be reversed, etc.
You can try to go with a fresh sd card, that will rebuild your system will all the old app versions.

No - a fresh SD card is not an option as then I will have 3 apps to upgrade to the latest versions - Bitcoin, LND and RTL.
There must be a simpler way to go back to v0.6.5 (or v0.7.0) - I will ask LOOP support for help and advice.

Where do you end up with in the RaspiBlitz SERVICES menu turning Loop OFF and then ON again?

As my first message says - getting this error -
Created symlink /etc/systemd/system/multi-user.target.wants/loopd.service → /etc/systemd/system/loopd.service.
OK - the Lightning Loop service is now enabled
./bonus.loop.sh: line 85: loop: command not found
Failed to install Lightning Loop
The loopd service isn't running and calling the 'loop' command fails.

Ah right you were on that old v1.5.1 and updated LND, Bitcoind and RTL even over the versions that v1.6 provides. So from the support side I can just say you would need to wait until v1.7 (what will be a while) are experiment on your own (always make a LND backup before tyring stuff out).

Yes I am and I don't have any problems running the latest releases of Bitcoin, LND and RTL.
I don't understand why now, the bonus.loop.sh script fails on line 85 and fails to install/start the loopd service and why the loop command does not exist no matter what version of LOOP I try to install.
The script worked fine before and there have not been any changes to it at all.

Try to replace it with the bonus.loop.sh from the master branch.

Yes - just done it now - installing v0.6.5. Will let you know..........

OK - now its failing on line 83 -
admin@raspberrypi:~/config.scripts $ sudo ./bonus.loop.sh on
making sure the loop service is not running
*** INSTALL LIGHTNING LOOP ***
Check Framework: Go
Installed go version go1.13.3 linux/arm
Cloning into 'loop'...
remote: Enumerating objects: 59, done.
remote: Counting objects: 100% (59/59), done.
remote: Compressing objects: 100% (44/44), done.
remote: Total 2578 (delta 21), reused 36 (delta 15), pack-reused 2519
Receiving objects: 100% (2578/2578), 1.28 MiB | 2.26 MiB/s, done.
Resolving deltas: 100% (1669/1669), done.
HEAD is now at 9c503fc Merge pull request #245 from joostjager/bump-v0.6.5-beta
[Unit]
Description=Loopd Service
After=lnd.service
[Service]
WorkingDirectory=/home/bitcoin/loop
ExecStart=/usr/local/gocode/bin/loopd --network=mainnet
User=bitcoin
Group=bitcoin
Type=simple
KillMode=process
TimeoutSec=60
Restart=always
RestartSec=60
[Install]
WantedBy=multi-user.target
Created symlink /etc/systemd/system/multi-user.target.wants/loopd.service → /etc/systemd/system/loopd.service.
OK - the Lightning Loop service is now enabled
./bonus.loop.sh: line 83: loop: command not found
Failed to install Lightning Loop

Your go install seems not to run ... there should be a lot of go: downloading ... outputs

So what is the cause of that?

Well the 'go install ./...' command has been running for 10 mins now with no output to the terminal.

Got something now -
admin@raspberrypi:/home/bitcoin/loop/cmd $ go install ./...
github.com/lightninglabs/loop/cmd/loop
panic: runtime error: index out of range [-1445]

maybe something with your go install went wrong ... try
/home/admin/config.scripts/bonus.go.sh off
/home/admin/config.scripts/bonus.go.sh on

OK - done that - this is what I got -
admin@raspberrypi:/home/bitcoin/loop/cmd $ /home/admin/config.scripts/bonus.go.sh off
Check Framework: Go
Installed go version go1.13.3 linux/arm
admin@raspberrypi:/home/bitcoin/loop/cmd $ /home/admin/config.scripts/bonus.go.sh on
Check Framework: Go
Installed go version go1.13.3 linux/arm

hmmm do this again:
sudo rm -rf /usr/local/go
/home/bitcoin/loop/cmd $ /home/admin/config.scripts/bonus.go.sh on

And then try the bonus loop script again.

OK - installing GO now - watch this space.

Ok - LOOP now installed with no errors.
I've just rebooted the RPi4 to get a clean start and I will check if LOOP is available in RTL again when back up and running.

OK that maybe the right moment to remind that there is a way to donate to the project on my tallycoin page ;)
https://tallyco.in/s/r5lx23/

Sure! - no worries! - As soon as my node spends some time online making money, donations to the project will start flowing.

Yep! - LOOP v0.8.0 now working fine.
Who would have thought the problem was caused by a corrupt GO installation - you learn something new every day!
Thanks for your help.


unbundle libcrypt

There is an ABI change from SONAME 1 to SONAME 2 from alma/rocky 8 to alma/rocky 9 for libxcrypt. Some of our packages don't run out of the box on alma 9 without extra an extra compatibility package  installed on the runtime OS.
We should

[x] remove libcrypt.so/libcrypt.a from our current sysroots

https://github.com/conda-forge/linux-sysroot-feedstock/pull/54
https://github.com/conda-forge/linux-sysroot-feedstock/pull/55
https://github.com/conda-forge/linux-sysroot-feedstock/pull/56

[ ] remove the remaining libcrypt*.so* from our current sysroots
[x] ~possibly rename the libxcrypt package to libxcrypt2 to reflect the ABI~

cc @jakirkham @isuruf

SGTM!
Though, I wouldn't change libxcrypt to libxcrypt2.
We already have a libxcrypt1 compatibility package for libcrypt.so.1 and the x in libxcrypt depicts the changed ABI anyway, AFAIK.

(For reference, these changes would be very similar to what we did for libnsl in https://github.com/conda-forge/linux-sysroot-feedstock/pull/40 .)

I've updated the issue description with links to @beckermr's PRs and added an item for removing the library files that current packages link to in the future (this is mostly just for the case of us using the sysroot package for QEMU_LD_PREFIX; see https://github.com/conda-forge/linux-sysroot-feedstock/pull/54#discussion_r1433302209 ).
I'd say removing the remaining files in a few month before we switch to CentOS 7 as the default linking target would make sense.

Hi, My company is using conda-forge to build C extensions against Python 3.6.15 and 3.7.12. Our compilations now fail because we cannot include a crypt.h, and our investigation eventually led us to this changeset. I see that it was necessary for conda-forge to rebuild Python 3.8 and newer with a new recipe in order to work with the latest sysroot, and it makes sense to me that this would not occur for Python 3.6.15 and 3.7.12 since they are no longer being built by conda-forge.
My question is: what do you believe my company's path forward should be to retaining our ability to build Python 3.6 and 3.7 C extensions using current day conda-forge? Obviously we shouldn't use old Pythons, but that is something that we're actively working on, bridging our ecosystem into Conda, and is why we encountered this problem. We also could fix the sysroot to the old version, but this is a difficult fix to implement in a large number of conda recipes, and we're worried about how we can document this process and publicize it fast enough. We could try to proxy conda-forge and remove this new sysroot, but that feels like it might be missing the whole point of this changeset. It's not clear to me that a repodata patch for the existing Python 3.6 and Python 3.7 builds would work either. So, our current inclination is to try and revive the old Python recipes and rebuild them against libxcrypt and put them into our third party package channel, but we have no idea how successful this would actually be. I'd be happy to hear your thoughts as we try to work through the problem.

You should be able to include the libxcrypt package in your env and it should build against that.

From an ABI perspective, it should be safe AFAIK.
I will defer to my colleagues on core about patching older pythons for this change.
cc @conda-forge/core
If you have a list of feedstocks that need the change, we may be able to use our bot infrastructure to help with the migration.

What would it take to rebuild the old Pythons? A build/number bump? More than that (if so what other pieces)?

If you have a list of feedstocks that need the change, we may be able to use our bot infrastructure to help with the migration.

I should have been more clear: the recipes I was referring to in my post that need patching are private proprietary packages (i.e. not public) inside of my company's private conda channels.

Ah I see. Well we will do our best to help, but we do focus our limited efforts on public packages and OSS.

My builds compile if I add libxcrypt to the host section. However, I am not sure that this is actually proper from an ABI standpoint, since it implies we're using different header files in the compilation process than the ones that were used to build Python (CentOS6). I am not an expert on ABI though, and could be wrong about this. FWIW, I tried to build with the libxcrypt1 compatibility package mentioned above, but I found that it does not actually have any header files: is that intentional?

If this can be solved by rebuilding the old python's with build/number bumps, would suggest creating PRs to do that. It's probably the simplest solution we can offer

So ABI is about runtime linking whereas the problem of possibly different headers is an API question. I only point this out to ensure that we keep the discussion straight.

I uploaded a PR that I think would address the issue for Python 3.7. Linux and OSX builds are working, however, the Windows build is failing, and I have no ability to determine what is wrong (I haven't debugged a Windows build in almost 10 years), and the fault appears to be in some of the other recipe changes from conda-smithy. I would appreciate any assistance in resolving it.
Assuming that we can overcome that issue, I can put up a Python 3.6 build afterward.

Thanks Aaron! 🙏
Added a suggestion on that PR. It's possible we will need to adjust that depending on how it goes

Unbundled now


A happy path for installation on Linux

I have to install git-identity on many boxes because it is just too useful!! :-)
To avoid figuring/typing the right commands here is the one-liner I have written:
cd ~ && git clone https://github.com/madx/git-identity.git && sudo ln -
s ~/git-identity/git-identity /usr/local/bin/git-identity && sudo chmod ugo+x !$

You might consider adding this to the README.md as the happy path for installation on Linux.
Creating this as an Issue instead of a pull request because it might be worth discussing/correcting first.

It's a bit overkill to use sudo for this. You can link it to $HOME/.local/bin (mkdir -p that if it doesn't exist), since that's likely to be on the $PATH already.
The nicer option is to integrate this on your distro's repositories. With #9, this is unblocked now.

https://aur.archlinux.org/packages/git-identity/
This is now on AUR, if you use Arch Linux.

Thanks for your submission @Dabbrivia , I also agree with @Dabbrivia that this is a bit overkill to use sudo for this. I'll think about adding such a section to the README


pp3: prevent checksum overflows

This PR cuts off any bits from the final checksum words that could cause checksum overflow.
@tpagarani, @mkurc-ant please have a look at this.
Signed-off-by: Paweł Czarnecki<EMAIL_ADDRESS>

LGTM


chore(buildpacks): update heroku-buildpack-go to v31

Adds Go 1.6 support.
See https://github.com/heroku/heroku-buildpack-go/compare/v30...v31

wouldn't the end-to-end tests cover this since the default app is example-go? :)

wouldn't the end-to-end tests cover this...?

You're right. Sometimes we get lucky.


Background color for selected comment makes it unreadable in Night Mode

eSteem Surfer v1.0.2
steps to reproduce:
Go to Profile/Comments or Profile/Replies, click on any comment  - it will be distinguished from other comments with yellow background; turn on Night Mode - the text color changes to pale violet/blue but background color stays unchanged which means the contrast is very weak and text is unreadable.

Good find, we will fix it with this week's release! @talhasch

Seems to be fixed in Surfer 1.0.3
To be honest I didn't notice in earlier version, so maybe it was always like this (and then it would not be a bug but enhancement worthy of separate issue) but only the top comment is ever distinguished with special colors (by top I mean comment to main post as opposed to comment on other comment). If you choose comment/reply that is deeper and then go to full context you will not have that visual aid - seems weird since that's where the feature would be even more useful (also going to full context should move the view to the comment instead of top of main post - scrolling to main post is always easy, scrolling down/through pages and finding relevant branch of discussion... not so much).

Would you elaborate on your thoughts and perhaps suggest how you see comments could be improved more... on separate new issue?! Thanks


Use appropriate atomic type for inter-thread sync

The RV tool analysis reported several cases of reading/writing shared memory variables without a lock.
The intention behind the code was that the data type being read/written simultaneously here was atomic in nature, thus the parallel access would be safe, as it is not possible to catch an atomic value mid-update.
To be more portable the code should use the C99 type sigatomic_t to ensure that the data type is in fact atomic on the given platform.  Currently it is using uint32 which is not guaranteed to be atomic on all platforms.
Calling this "minor" because the uint32 type will be atomic on all the platforms that the code in question is actually used on.  There is no bug currently here, this is just to prevent a future bug if this code is expanded to smaller CPUs (microcontrollers) where uint32 is not atomic.

Trac comment by jphickey on 2017-02-14 13:43:06:
Also need to make sure that we include the volatile keyword on these globals as well.

Imported from trac issue 183.  Created by jphickey on 2017-02-14T13:00:24, last modified: 2019-08-14T14:11:46

Trac comment by glimes on 2017-02-14 13:47:43:
The case we hit in Biosentinel is in CFE, I'll go update the
ticket over there -- but it's due to CFE_ES_ApplicationSyncDelay
spinning on CFE_ES_Global.SystemState and .AppReadyCount, which
are not themselves marked as volatile.


Any other ideas to add to the Django document?

It's a stub now.

Off top of my head:

Class naming conventions
Path conventions
Template-writing hygene


LocationMediaItem displaying  empty bubble

Hi all,
I am trying to implement Location media in  xamarin iOS , i have given CLLocations values(longitude and latitude )values to Locationitem  .
I have tried the following code,
CLLocation cl = new CLLocation (17.3850,78.4867);
var locationItem = new LocationMediaItem (cl);
locationItem.AppliesMediaViewMaskAsOutgoing = true;
var locationmessage = new JSQMessagesViewController.Message(SenderId, SenderDisplayName,msgDate, locationItem);
messages.Add (locationmessage);

@SagarVarmaD I think you should look up methods like - (void)finishReceivingMessage; and - (void)finishSendingMessage;. I think your code is okay, you will need to tell JSQMessageViewController that you finish sending or receiving messages and it should update the UI. Otherwise, only the data model is updated. It's like when you are using UITableView, you will need to call reloadData to update the table view.

@jessesquires Looks like MKMapSnapshotter does indeed return a valid snapshot, see the attachment. But the problem is still there, smell like a bug. I can investigate more later.

@SagarVarmaD Hey, if you read the docs carefully, you will find out that it's actually not the correct method to use. See the description of
/**
 *  Initializes and returns a location media item object having the given location.
 *
 *  @param location The location for the media item. This value may be `nil`.
 *
 *  @return An initialized `JSQLocationMediaItem`.
 *
 *  @discussion If the location data must be dowloaded from the network,
 *  you may initialize a `JSQLocationMediaItem` object with a `nil` location.
 *  Once the location data has been retrieved, you can then set the location property
 *  using `setLocation: withCompletionHandler:`
 */
- (instancetype)initWithLocation:(nullable CLLocation *)location;

You should use - (void)setLocation:(nullable CLLocation *)location withCompletionHandler:(nullable JSQLocationMediaItemCompletionBlock)completion;. 😃

@jessesquires not a bug, sorry for that.

thanks @Lucashuang0802 ! 🎉

JSQLocationMediaItem is setting location each time when collectionview reloads. so it returns empty bubble until location reloads. i don't want to reload other JSQLocationMediaItem while adding new item, anyone having solution for this?


Global list styles prevent disabling colors

We set up this stylesheet of global css rules that apply to all lists: https://github.com/microsoft/vscode/blob/7d2c73944dba9e957ccc52557be681f5a7ae0cb0/src/vs/platform/list/browser/listService.ts#L82-L83
We also set up rules per-list, which usually override the global rules

and so I have never understood what the purpose of the global rules are. If I try to disable a style rule by setting a style to undefined in overrideStyles when I create my tree, then the per-list rule is gone but the global list rule still applies, so I can really only override it with my own !important rule. This has caused issues in notebooks and chat, and after talking to @aeschli about it I noticed that it shows up in the problems view with this black lightbulb as well

and in chat we have to work around it for the avatar codicon and our toolbars

so I want to find out what the purpose of the global list rules is and whether we can get rid of it. Do you know @joaomoreno?

I really don't any more. If you find out that we'd do just fine without it, I'd be happy to review a PR!

Removed this in #228173. I tested a bunch of lists throughout the workbench but please let me know if you notice any regressions


ng build - ES5 bundles -> Unknown helper createSuper

🐞 Bug report
Command (mark with an x)

[ ] new
[x] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[ ] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Is this a regression?

 Yes, the previous version in which this bug was not present was: 9.0.6
Description
Any ng build ends up with An unhandled exception occurred: C:\my\path\main-es2015.js: Unknown helper createSuper
🔬 Minimal Reproduction

ng build or ng build--prod
🔥 Exception or Error

Generating ES5 bundles for differential loading...
An unhandled exception occurred: C:\my\path\main-es2015.js: Unknown helper createSuper
See "C:\Users\Me\AppData\Local\Temp\ng-sYZMmM\angular-errors.log" for further details.

and the angular-errors.log:

[error] ReferenceError: C:\my\path\main-es2015.js: Unknown helper createSuper
    at loadHelper (C:\my\path\node_modules\@babel\helpers\lib\index.js:225:27)
    at Object.ensure (C:\my\path\node_modules\@babel\helpers\lib\index.js:270:3)
    at File.addHelper (C:\my\path\node_modules\@babel\core\lib\transformation\file\file.js:203:15)
    at pushInheritsToBody (C:\my\path\node_modules\@babel\plugin-transform-classes\lib\transformClass.js:471:384)
    at pushConstructorToBody (C:\my\path\node_modules\@babel\plugin-transform-classes\lib\transformClass.js:461:5)
    at pushConstructor (C:\my\path\node_modules\@babel\plugin-transform-classes\lib\transformClass.js:449:5)
    at pushBody (C:\my\path\node_modules\@babel\plugin-transform-classes\lib\transformClass.js:187:11)
    at buildBody (C:\my\path\node_modules\@babel\plugin-transform-classes\lib\transformClass.js:133:5)
    at classTransformer (C:\my\path\node_modules\@babel\plugin-transform-classes\lib\transformClass.js:537:5)
    at transformClass (C:\my\path\node_modules\@babel\plugin-transform-classes\lib\transformClass.js:573:10)
    at PluginPass.ClassExpression (C:\my\path\node_modules\@babel\plugin-transform-classes\lib\index.js:63:54)
    at newFn (C:\my\path\node_modules\@babel\traverse\lib\visitors.js:179:21)
    at NodePath._call (C:\my\path\node_modules\@babel\traverse\lib\path\context.js:55:20)
    at NodePath.call (C:\my\path\node_modules\@babel\traverse\lib\path\context.js:42:17)
    at NodePath.visit (C:\my\path\node_modules\@babel\traverse\lib\path\context.js:90:31)
    at TraversalContext.visitQueue (C:\my\path\node_modules\@babel\traverse\lib\context.js:112:16)

🌍 Your Environment

Angular CLI: 9.0.7
Node: 12.3.1
OS: win32 x64

Angular: 9.0.7
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.900.7
@angular-devkit/build-angular     0.900.7
@angular-devkit/build-optimizer   0.900.7
@angular-devkit/build-webpack     0.900.7
@angular-devkit/core              9.0.7
@angular-devkit/schematics        9.0.7
@angular/cdk                      9.1.3
@angular/flex-layout              9.0.0-beta.29
@angular/material                 9.1.3
@ngtools/webpack                  9.0.7
@schematics/angular               9.0.7
@schematics/update                0.900.7
rxjs                              6.5.4
typescript                        3.7.5
webpack                           4.41.2

Anything else relevant?
Tried to install @babel/compat-data (mentioned here) as it seems babel related , did not help
EDIT:
Downgrading to

    "@angular-devkit/build-angular": "^0.900.6",
    "@angular/cli": "^9.0.6",
    "@angular/compiler-cli": "^9.0.6",

which returned the environment to:

Angular CLI: 9.0.6
Node: 12.3.1
OS: win32 x64

Angular: 9.0.7
... animations, common, compiler, core, forms, language-service
... localize, platform-browser, platform-browser-dynamic, router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.900.6
@angular-devkit/build-angular     0.900.6
@angular-devkit/build-optimizer   0.900.6
@angular-devkit/build-webpack     0.900.6
@angular-devkit/core              9.0.6
@angular-devkit/schematics        9.0.6
@angular/cdk                      9.1.3
@angular/cli                      9.0.6
@angular/compiler-cli             9.0.6
@angular/flex-layout              9.0.0-beta.29
@angular/material                 9.1.3
@ngtools/webpack                  9.0.6
@schematics/angular               9.0.6
@schematics/update                0.900.6
rxjs                              6.5.4
typescript                        3.7.5
webpack                           4.41.2

returned the functionality of ng build back.

Related to https://github.com/babel/babel/pull/11298

Closed via https://github.com/angular/angular-cli/pull/17280


TLS handshake error from xx: read tcp xx -> xx: read: connection reset by peer

Version

Karpenter Version: v0.27.0

Kubernetes Version: v1.24.0
Expected Behavior
Karpenter should not produce these TLS handshake errors generated by a bad connection from the control-plane kube-apiserver to the Karpenter defaulting/validating webhooks.
Actual Behavior
Karpenter generates TLS handshake errors on some calls that are processed through the control-plane kube-apiserver that are then routed to Karpenter's validating/defaulting webhooks. These TLS errors appear to be related to https://github.com/kubernetes/kubernetes/issues/109022 which states that these handshake errors may be generated by some caching mechanism that is happening in the standard library that causes TLS errors on a cert rotation.
Steps to Reproduce the Problem
Unable to repro personally but have seen instances from users of this happening.
Resource Specs and Logs
N/A
Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

Is this something that is likely to go away with the move to the new beta in v0.32.x?

I have completely cleaned up karpenter (delete helm charts, crds and the namespace) and reinstalled.  I still see the TLS errors from the webhook.  My bigger concern is that the pods fail the health check and restart every few minutes.

After upgrade to v0.32.1 this starts happening, brainless reinstall of helm chart(delete old karpenter chart, not karpenter-crd) and install new.
Don't afraid, deletion of helm chart not deletes worker nodes=)

I was using fargate as a way to run Karpenter and I gave up on that and I create a three node NoeGroup to make sure Karpenter has two different nodes to run on and one extra node for updates.  That has gotten rid of all of my Karpenter issues for now.

We should be able to close this now that we have released v0.33. Webhooks are fully dropped so we should stop seeing these TLS handshake errors if you enable DISABLE_WEBHOOK=true and drop the mutating webhook configurations and valdiation webhook configurations from your cluster 🎉
Closing this one for now since the newest version of Karpenter won't run into this problem by default. Please feel free to continue discussion on this one if you are running an older version of Karpenter with the webhooks and need more support.

So I'm a bit confused. I still see this after upgrading to karpenter v1.0.6. Karpenter appears to be working fine. Do I need to set DISABLE_WEBHOOK=true? I thought the closing comment above indicated the latest version wouldn't have this issue. I have not explicitly set DISABLE_WEBHOOK=false anywhere, but when describing my pod, I do see it is set to false in the env vars of the pod. Did I miss a step in the upgrade to change this setting?

Note, I did try disabling the webhook, in helm it was webhook.enabled = "false". The error has gone away and Karpenter appears to still be working. I don't fully understand the repercussions of this though, so if someone else does and can confirm that's the correct action, that would be great. Thanks!

What about this one?
Starting with 0.37.3 Karpenter has enabled conversion webhooks by default to improve the v1 migration experience. If working with a cluster with a network policy that blocks Ingress, ports 8000, 8001, 8081, 8443 will need to be allowlisted.

I also spotted similar issue after upgrading from 0.35.5 to 1.0.5.
As @andrewhharmon mentioned we have webhook enabled in 1.0.5 pod description, where in 0.35.5 there is no reference to this env.
Pod description from 0.35.5
  - env:
    - name: KUBERNETES_MIN_VERSION
      value: 1.19.0-0
    - name: KARPENTER_SERVICE
      value: karpenter
    - name: LOG_LEVEL
      value: info
    - name: METRICS_PORT
      value: "8000"
    - name: HEALTH_PROBE_PORT
      value: "8081"
    - name: SYSTEM_NAMESPACE
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.namespace
    - name: MEMORY_LIMIT
      valueFrom:
        resourceFieldRef:
          containerName: controller
          divisor: "0"
          resource: limits.memory
    - name: FEATURE_GATES
      value: Drift=false,SpotToSpotConsolidation=false
    - name: BATCH_MAX_DURATION
      value: 30s
    - name: BATCH_IDLE_DURATION
      value: 5s
    - name: ASSUME_ROLE_DURATION
      value: 15m
    - name: CLUSTER_NAME
      value: xxxxxxx
    - name: VM_MEMORY_OVERHEAD_PERCENT
      value: "0.075"
    - name: INTERRUPTION_QUEUE
      value: xxxxxxx
    - name: RESERVED_ENIS
      value: "0"
    - name: AWS_STS_REGIONAL_ENDPOINTS
      value: regional
    - name: AWS_DEFAULT_REGION
      value: eu-central-1
    - name: AWS_REGION
      value: eu-central-1
    - name: AWS_ROLE_ARN
      value: arn:aws:iam::xxxx
    - name: AWS_WEB_IDENTITY_TOKEN_FILE
      value: /var/run/secrets/eks.amazonaws.com/serviceaccount/token

Same from 1.0.5
  - env:
   - name: KUBERNETES_MIN_VERSION
     value: 1.19.0-0
   - name: KARPENTER_SERVICE
     value: karpenter
   - name: WEBHOOK_PORT
     value: "8443"
   - name: WEBHOOK_METRICS_PORT
     value: "8001"
   - name: DISABLE_WEBHOOK
     value: "false"
   - name: LOG_LEVEL
     value: info
   - name: LOG_OUTPUT_PATHS
     value: stdout
   - name: LOG_ERROR_OUTPUT_PATHS
     value: stderr
   - name: METRICS_PORT
     value: "8080"
   - name: HEALTH_PROBE_PORT
     value: "8081"
   - name: SYSTEM_NAMESPACE
     valueFrom:
       fieldRef:
         apiVersion: v1
         fieldPath: metadata.namespace
   - name: MEMORY_LIMIT
     valueFrom:
       resourceFieldRef:
         containerName: controller
         divisor: "0"
         resource: limits.memory
   - name: FEATURE_GATES
     value: SpotToSpotConsolidation=false
   - name: BATCH_MAX_DURATION
     value: 30s
   - name: BATCH_IDLE_DURATION
     value: 5s
   - name: CLUSTER_NAME
     value: xxxxx
   - name: VM_MEMORY_OVERHEAD_PERCENT
     value: "0.075"
   - name: INTERRUPTION_QUEUE
     value: xxxxxx
   - name: RESERVED_ENIS
     value: "0"
   - name: AWS_STS_REGIONAL_ENDPOINTS
     value: regional
   - name: AWS_DEFAULT_REGION
     value: eu-central-1
   - name: AWS_REGION
     value: eu-central-1
   - name: AWS_ROLE_ARN
     value: arn:aws:iam::xxxxxx
   - name: AWS_WEB_IDENTITY_TOKEN_FILE
     value: /var/run/secrets/eks.amazonaws.com/serviceaccount/token

Im feeling lost now. Should we manually disable it via variables in helm? Or we this one is required for performing migration?

What are the downsides of having web-hooks disabled?
What benefits do web-hooks bring?

Same issue after the v1 upgrade...
Should we open a new issue instead of commenting here, looks like it's not being watched?

same issues on 1.0.8

I've only started seeing this problem when going from v0.37.0 to v0.37.1 which is interesting

same here we have upgrade to v0.37.3 we are seeing this issue


Studio Cleanup

Switched from jotai to zustand (https://docs.pmnd.rs/zustand/getting-started/introduction)
Switched from axios to ky (https://github.com/sindresorhus/ky)
Added ts-reset (https://www.totaltypescript.com/ts-reset) to tweak some TypeScript behaviours
Added t3-env (https://github.com/t3-oss/t3-env) for env var management
Added a style-guide.md for TypeScript
Use neverthrow for Result type

lgtm, but there are a lot of changes. Apart from the zustand change, it's simply name changes. What was the process to ensure that there is no regression or unknown state change that breaks something?

We'll run the e2e tests when it gets marked ready for review and ensure those pass, aside from those though it would probably be good to do a quick manual  test of the major features to make sure that nothing glaringly obvious broke.

Cancel the flowchart doesn't work for me. Error:
[2024-03-04 16:03:21] - asyncio - ERROR - Exception in callback _ProactorBaseWritePipeTransport._loop_writing(<_OverlappedF...hed result=14>)
handle: <Handle _ProactorBaseWritePipeTransport._loop_writing(<_OverlappedF...hed result=14>)>
Traceback (most recent call last):
  File "C:\Users\zzzgu\AppData\Local\Programs\Python\Python311\Lib\asyncio\events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "C:\Users\zzzgu\AppData\Local\Programs\Python\Python311\Lib\asyncio\proactor_events.py", line 381, in _loop_writing
    assert f is self._write_fut
           ^^^^^^^^^^^^^^^^^^^^
AssertionError

Cancel the flowchart doesn't work for me. Error:
[2024-03-04 16:03:21] - asyncio - ERROR - EAxception in callback _ProactorBaseWritePipeTransport._loop_writing(<_OverlappedF...hed result=14>)
handle: <Handle _ProactorBaseWritePipeTransport._loop_writing(<_OverlappedF...hed result=14>)>
Traceback (most recent call last):
  File "C:\Users\zzzgu\AppData\Local\Programs\Python\Python311\Lib\asyncio\events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "C:\Users\zzzgu\AppData\Local\Programs\Python\Python311\Lib\asyncio\proactor_events.py", line 381, in _loop_writing
    assert f is self._write_fut
           ^^^^^^^^^^^^^^^^^^^^
AssertionError

Regression

Feedback Button doesn't do anything

I'm not able to import any pytest tests in the test sequencer:
Uncaught (in promise) TypeError: data.missingLibraries is not iterable
    at getTests (useTestImport.ts:68:28)

When the flowchart play, I can't re-run it. It's stuck in the Cancel state

When the flowchart fail (error was raise in block), I can't re-run it. It's stuck in the Cancel state

fixed :white_check_mark:

 Feedback Button doesn't do anything

fixed :white_check_mark:


Setup WSL

Install

[ ] Activate WSL
[ ] Install Ubuntu in Windows
[ ] GUI APPs (https://docs.microsoft.com/en-us/windows/wsl/tutorials/gui-apps)

Dev Tools

[ ] VSCode
[ ] CUDA toolkit : https://docs.nvidia.com/cuda/wsl-user-guide/index.html

Download: https://developer.nvidia.com/cuda-downloads?target_os=Linux&target_arch=x86_64&Distribution=WSL-Ubuntu&target_version=2.0

[ ] Command prompt e.g. zsh
[ ] Hugo SSG
[ ] Node JS
[ ] Micromamba
[ ] Julia

Caveats

[ ] No systemd and thus no snap app support by default.

CUDA

Once you are on your favorite Linux distro through WSL 2, and after the NVIDIA Windows driver is installed there is nothing more to do to run existing CUDA applications that were built on Linux.

Chinese (Traditional) Reference : https://hackmd.io/@billsun/BJByCIUHf?type=view


Reading samples directly at runtime (port to STM32)

Given:
STM32 micro with ~384Kb-512Kb RAM;
SD card connected to STM32 with fast SDIO 6-wire interface running at 24MHz clock;
FatFS, so files at SD-card can operate fopen() fclose() fseek() etc...
In your opinion, is it possible to read SF2 samples not into the main memory, but directly in pieces of the required size from a file (stream) at the runtime of sound rendering? Or into a small buffer?
Is it difficult to implement?
Thanks in advance.

I don’t think you want to do any file io ops in real time.. see #4 in this article https://atastypixel.com/four-common-mistakes-in-audio-development/


Debug and Release targets with CocoaPods

@confile - can you take a look at this, I think there's a path to do what's needed here and I'd appreciate you help on this.
The LIBRARY_SEARCH_PATHS should be different for Debug and Release builds in Xcode. Currently it only points to the debug version. The following is based on: https://github.com/CocoaPods/CocoaPods/issues/2847
Podfile changes:
target 'TapTap' do
// You don't need to add targeting for arm64 or x86 for the simulator as the linker will automatically choose the right architecture from the fat binary
pod 'j2objc-base-debug', :path => "${project.buildDir}", :configurations => ['Debug']
pod 'j2objc-base-release', :path => "${project.buildDir}", :configurations => ['Release', 'AppStore']
end
Two podspec files: 'j2objc-base' and 'j2objc-base-debug'. The differences are fairly minor:
Debug:
'LIBRARY_SEARCH_PATHS' => '${getJ2ObjCHome()}/lib ${project.buildDir}/j2objcOutputs/lib/iosDebug'
Release:
'LIBRARY_SEARCH_PATHS' => '${getJ2ObjCHome()}/lib ${project.buildDir}/j2objcOutputs/lib/iosRelease'

Apparently this change took a year to get in to CocoaPods: https://lookback.io/blog/cocoapods-by-configuration
It was lauded in the release notes:
Finally you can specify dependencies per build configuration. This is one of the most requested CocoaPods features… ever.


A small change to omit comments in html body

Reason: comments might mislead following link parsing
In function: Crawler.prototype._getAllUrls = function(baseUrl, body)
body = body.replace(//g, '');  // Added by @tibetty to omit commented contents which might mislead following link-parsing

Thank you, seems reasonable, as commented out links should be ignored by a browser. I will merge it now and a bit later publish a newer version of js-crawler. I want to do some re-factoring of js-crawler and add more tests before this.


Adding a "Moving Squares" Background

Prerequisites

[X] I am an Open Source Contributor
[X] I checked to make sure that this issue has not already been filed

Description
To add a "Moving Squares" background on the Backgrounds Component section
(The Text is just for reference)
Screenshots

https://github.com/Rakesh9100/Beautiify/assets/140642394/80372d20-3b3a-4c50-8f21-5d402c34d382
Code of Conduct

[X] I follow Contributing Guidelines of this project.

Proceed @NikmanGT


Use registries.conf.d instead of main registries.conf

What type of PR is this?
/kind feature
What this PR does / why we need it:
This allows compatibility with the golang-github-containers-image package which writes /etc/containers/registries.conf. We now fallback to a CRI-O specific drop-in.
Which issue(s) this PR fixes:

Follow-up on https://github.com/cri-o/packaging/issues/3
Special notes for your reviewer:
Ref https://github.com/cri-o/packaging/issues/3#issuecomment-1759713675
PTAL @afbjorklund
Does this PR introduce a user-facing change?

Switched to registries.conf.d drop-in instead of main registries.conf to make the packages compatible with `golang-github-containers-image`.

Sounds good to me, haven't tested yet if it works as written out.


Confusion around STATE messages

We have been attempting to use the new STATE message support in target-postgres to enable LOG_BASED syncing. We use tap-postgres as the corresponding tap and meltano to orchestrate the ELT process.
What we are experiencing is captured in a meltano ticket. However, based on input from a developer on the project, it appears that the root issue is due to a difference in how this target is handling STATE versus how it is handled elsewhere. Quoting from that ticket:

Looking at https://github.com/datamill-co/target-postgres/pull/130 it seems like they are indeed  sending the full STATE message downstream, whereas Singer themselves only write the value  out in their targets.
See https://github.com/singer-io/target-csv/blob/a98d4633a97e3b7183a99a4f790722535b97c238/target_csv.py#L91 for target-csv example.

I'd also note that the singer-target-template and target-gsheet duplicate the approach taken by target-csv.

@robmoore Though the feature was added with some guidance by us, we don't use this feature since we record state at the end from a parent process, though would like to switch to using it for better partial recovery from a target failure.
I think a simple fix would be adding an output format option to the configuration.
@airhorns May have some thoughts too.
Some background on the why Data Mill don't use targets to track state (though may change):
One of the issues with STATE management is that beyond the message, there hasn't been an official spec on using it, just some examples, most not using a complex target. Stitch also doesn't really use Singer targets, it's "target" dumps the schema and records to a queue and a fairly different proprietary tech stack loads data into destinations. Not much has been thought of is using a STATE during the actual load. We also will load against different targets and track messages rather than STATE in that case. Eg with only state tracking through a target, you can't load into two different sources (like S3/Athena and Redshift using only one tap run).

Crud, this stinks. Just so that we're all on the same page, the issue seems to be that target-postgres emits STATE messages differently to the other taps that emit STATE messages. The other taps emit the states without the wrapping STATE: {"value": ...} string sigil and JSON object, and I set target-postgres up to emit it with the wrapping sigil and {"value": ...} wrapper.
I did that because that's what the spec says is a valid STATE message, see https://github.com/singer-io/getting-started/blob/master/docs/SPEC.md#example , but I guess that only applies to STATE messages from taps, and that the prior art for targets is to strip the surrounding hooplah.
I think we should fall into line with the other targets, I'll prepare a PR. Sorry all!

I think for what it's worth the behaviour of the other targets is indirectly documented in the singer spec by means of specify the state file contents here: https://github.com/singer-io/getting-started/blob/master/docs/CONFIG_AND_STATE.md#state-file , which as you can see, has no {"value": ...} wrapper. I think you're supposed to be able to write a state file by doing tap-something | target-something > state_file.json, so to me it's pretty clear that the {"value": ...} wrapper shouldn't be included in the output of target-postgres.


Cannot enable TCP_DEFER_ACCEPT: protocol not available

/www/spiral/app $ ./spiral serve -v -d
DEBU[0000] [headers]: disabled
DEBU[0000] [grpc]: disabled
DEBU[0000] [amqp]: disabled
DEBU[0000] [beanstalk]: disabled
DEBU[0000] [sqs]: disabled
DEBU[0000] [ws]: disabled
DEBU[0000] [health]: disabled
DEBU[0000] [reload]: disabled
DEBU[0000] [rpc]: started
DEBU[0000] [http]: started
DEBU[0000] [jobs]: started
DEBU[0000] [broadcast]: started
DEBU[0000] [metrics]: started
ERRO[0000] [rpc]: [rpc]: cannot enable TCP_DEFER_ACCEPT: protocol not available
DEBU[0000] [http]: stopped
DEBU[0000] [jobs]: stopped
DEBU[0000] [broadcast]: stopped
DEBU[0000] [metrics]: stopped
Error: [rpc]: cannot enable TCP_DEFER_ACCEPT: protocol not available

@php-rock what version of server do you use? Did you try to update and then run vendor/bin/spiral get ?
@48d90782

TCP_DEFER_ACCEPT Should work under all modern operating systems. @php-rock Could you please provide more info about:

Type of OS which you use. If that Ubuntu or other - uname -r, if Windows, if that WSL - same, uname -r inside it and also OS build version (could be found in settings section).
if that windows 7 or lower, we do not support operating systems lower that 18xxx builds of Win 10.
RR version.
FYI - TCP_DEFER_ACCEPT will work only in WSL2 (https://docs.microsoft.com/en-us/windows/wsl/install-win10). We generally do not support WSL, but WSL2 will work as a general server Linux os.
Thanks.

We do not support WSL1, please update to WSL2 @php-rock


fix: change tabSize to 4

Description
Since that's the standard indention in Python. Right? :)
I'm not sure why we've set it to 2?
Closes #
Reviewer Focus

This PR needs a quick review. Focus on CHANGES.
Checklist
N/A

Anything related to Python project settings is in template-python-project repo. Closing this.


Thank you for the very detailed description.

Thank you for the very detailed description.
Please be aware that there have been issues with the Windows 10 SDK component recently, caused by errors on Microsoft side (https://github.com/jberezanski/ChocolateyPackages/issues/107). The symptoms were different than in your case (the component simply failed to install with a clear error message), but still, you can try again now that the issue has been fixed.
Assuming your problem does not go away, I'd like to ask you to provide the (numerous) log files generated by the Visual Studio Installer: $Env:TEMP\chocolatey\dd_*.log. They usually are enough to identify any problems with the VS install itself.
The fact that the Chocolatey log just stops is curious indeed and yes, it may indicate that choco.exe is being killed by something. Now, I'm not familiar with Packer, but perhaps by correlating the VS installer logs with the Packer log it might be possible to determine whether the VS installer continues running in the background.

choco install visualstudio2019buildtools && choco install visualstudio2019-workload-vctools

I noticed you do not pass -y to choco.exe, which is normally required on a default install. I assume you are enabling the allowGlobalConfirmation feature - is that correct? What other Chocolatey settings do you change from the default values?

I wonder if there is a timeout

Yes, there is:
     --timeout, --execution-timeout=VALUE
     CommandExecutionTimeout (in seconds) - The time to allow a command to
       finish before timing out. Overrides the default execution timeout in the
       configuration of 2700 seconds. '0' for infinite starting in 0.10.4.

I believe, however, that choco.exe would write a clear message if the timeout was reached (but I'm not 100% sure about it). You can try with some large value, such as --execution-timeout 108000 (it's what I use on slow virtual machines when testing the VS packages).
Originally posted by @jberezanski in https://github.com/jberezanski/ChocolateyPackages/issues/108#issuecomment-860192381

What is the purpose of this issue? The description is just a copy+paste from my post.


Device orientation fixes for Firefox Android

Adds support for landscape device orientation with Firefox Android.

uses window resize and mediaquery list object to detect orientation in absence of having orientationchange events.
swaps orientationevent axis' when in portrait orientation.

Sorry to pull the rug from under you, but moving to a sensor fusion model, which is much more performant. New implementation relies on devicemotion events. I tested a bit with FF for Android, and the sensor data seems to be coming in really slowly. Any ideas why?

@borismus Just filed a bug for that here: https://bugzilla.mozilla.org/show_bug.cgi?id=1217942
Nothing we can really do about that until there is a fix in platform for the issue.
Just so that it's serviceable in Firefox Android, the Polyfill should fallback to deviceOrientation with FF.   Will update this PR.

Thanks!
On Fri, Oct 23, 2015 at 11:48 AM Casey Yee<EMAIL_ADDRESS>wrote:

@borismus https://github.com/borismus Just filed a bug for that here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1217942
Nothing we can really do about that until there is a fix in platform for
the issue.
Just so that it's serviceable in Firefox Android, the Polyfill should
fallback to deviceOrientation with FF. Will update this PR.
—
Reply to this email directly or view it on GitHub
https://github.com/borismus/webvr-polyfill/pull/13#issuecomment-150661370
.

There are patches inbound for devicemotion and orientationchange into Firefox.  Cancelling PR and will work on patches for the fusion sensor device instead.


Doesn't support DATE/TIME types in WHERE clause

I don't know if this is a problem with PDO or with this library.
I am trying to use this WHERE clause:
->where("date", ">", "CURRENT_DATE - INTERVAL '90 days'")

but I get this exception:
Uncaught exception 'PDOException' with message 'SQLSTATE[0A000]: Feature not supported: 7 ERROR:  date/time value "current" is no longer supported' in .../vendor/slim/pdo/src/PDO/Statement/StatementContainer.php:404

Is it possible to use DATE/TIME variables in PostgreSQL like CURRENT_DATE?

Here's the alternative way to do it:
->where("issue_date", ">", date("Y-m-d", strtotime("90 days ago")))

@stevevance sorry for the delay... I have address this in 2.x with the Raw SQL clause:
->where("date", ">", new Raw("CURRENT_DATE - INTERVAL '90 days'"))


[FIX] MASTER AMP and onnxruntime issue with master PT

This PR:

fix amp usage for master arch in both frameworks
fix onnxruntime issue with MASTER PT  (instead of tril triu with transpose works fine)

Any feedback is welcome :hugs:
Closes:
#789

all slow tests passes :)

slow tests passes / amp tested also again


Support previous version(s) of .NET

The template currently allows for creating .NET 6 projects, would be great to be able to target .NET 5 and potentially earlier versions of .NET (Core) too.

Fixed with the creation of the .net 5 branch.
From now on any changes to the .NET 5 version of the template will need to be handled via that branch.
Future (non .NET 5) work is expected to take place on the main branch and new releases can be pushed to NuGet by merging the latest changes into the .net 6 release branch which will automatically build, pack and push the Nuget package.


When using horizontal cursor, the animation doesn't start at frame 0

Using the horizontal scroll functionality, when the cursor moves from left to right the animation seems to start from the middle frame, and not frame 0. It can be seen using this example:
https://lottiefiles.com/interactivity?url=https%3A%2F%2Fassets7.lottiefiles.com%2Fpackages%2Flf20_ltf45w.json#ninth
If you add controls to the lottie-player, you can clearly see the animation doesn't start from the beginning. I don't think this is a problem due to this specific animation as i've noticed it using others too, so I think its a player problem.
LottieInteractivity.create({
  player: '#zipper',
  mode: 'cursor',
  actions: [
    {
      position: { x: [0, 1], y: [-1, 2] },
      type: 'seek',
      frames: [0, 60],
    },
    {
      position: { x: -1, y: -1 },
      type: 'stop',
      frames: [0],
    },
  ],
});

This issue is being worked on. Will update once completed

Fixed on package "version": "0.1.4"

Can anyone please tell me the meaning of  position y values. [ -1, 2].
Is position of x and y = -1 means outside the container ?


Manual GIT rename

Since sometimes Git does not detect file renames, it would be good to have manual way of marking staged changes as renames, for example select deleted file and select new file and then enable "Git Rename" on right click or something similar.

https://stackoverflow.com/a/433142


When arrows visible and i hold alt and rotate or drag camera it zooms out a lot

bug: when arrows visible and i hold alt and rotate or drag camera it zooms out a lot
Unity 2019.4.17f
https://user-images.githubusercontent.com/16543239/106351422-bdb8c300-62e4-11eb-948a-6ad641c319db.mp4

https://github.com/LogicalError/realtime-CSG-for-unity/blob/03adff579cc82167b2dd5d226ec89cd6745249fe/RealtimeCSG/Assets/Plugins/RealtimeCSG/Editor/Scripts/View/GUI/EditModeGUI/EditModes/Generators/Generator.Base.cs#L663
Seems to be the code causing it.  I've commented it out

Does this issue still persist with the current version?

Fixed with #349

Confirmed fixed in #349 using 2019.4.31f1 but it appears you cannot press F to focus on the block being generated. Minor but notable.


neither setDefaults or configure apis are working any way possible

neither of the given api's are changing the notification text title or color
i implemented the plugin like this
cordova.plugins.backgroundMode.enable();
cordova.plugins.backgroundMode.configure({
  title: 'live on aaa',
  text:'close the app if you want to go offline on your aaa account.',
  color: 'ff0829',
  resume: true
});

cordova.plugins.backgroundMode.setDefaults({
  title: 'live on aaa',
  text:'close the app if you want to go offline on your aaa account.',
  color: 'ff0829',
  resume: true
});
cordova.plugins.backgroundMode.enable();

please guide us how to use it you are great

I am facing the same issue on Android 9.1. I have tried both setDefaults() and configure() before and after backgroundMode.enable() or backgroundMode.on('activate').subscribe() but no luck unfortunately

Same issue if I create my project wich 9.0.0<EMAIL_ADDRESS>

All settings must be valid or it will fail:

You need an icon on Android for the notification (omit the ".png", and it must be in the folder mentioned)
If you include a color, omit the "#"

BTW, from what I can tell, this plugin is really only useful for immediately resuming a session, instead of a cold-start.  That said, that was what I was looking for at this point.  It would be nice if I could do more things in the background, but such is the world of cordova open-source...


[TUBEMQ-433] add tubemq perf-consumer/producer scripts

Codecov Report

Merging #330 (05d2e8b) into master (ca9ffbe) will decrease coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master    #330      +/-   ##
===========================================
- Coverage      8.03%   8.02%   -0.02%
+ Complexity      468     466       -2
===========================================
  Files           249     249
  Lines         27115   27115
  Branches       4440    4440
===========================================
- Hits           2179    2176       -3
- Misses        24466   24468       +2
- Partials        470     471       +1

Impacted Files
Coverage Δ
Complexity Δ

.../apache/tubemq/corebase/policies/FlowCtrlItem.java
38.88% <0.00%> (-1.12%)
8.00% <0.00%> (-1.00%)

.../tubemq/corebase/policies/FlowCtrlRuleHandler.java
43.98% <0.00%> (-0.59%)
34.00% <0.00%> (-1.00%)

Continue to review full report at Codecov.

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

ok, I'll update this pr today

@gosonzhang
sh tubemq-producer-perf-test.sh
sh tubemq-consumer-perf-test.sh

[2020-12-02 15:15:07,974] INFO [Producer] Producer status from ready to running! (org.apache.tubemq.client.producer.ProducerManager)
[2020-12-02 15:15:07,983] INFO [Publish begin 2] publish topicSet [teg_inner_drtest1], address = org.apache.tubemq.client.producer.ProducerManager@583562e5 (org.apache.tubemq.client.producer.ProducerManager)
[2020-12-02 15:15:07,991] INFO [Publish begin 2] already get meta info, topicSet: [teg_inner_drtest1], waste time 7 Ms (org.apache.tubemq.client.producer.ProducerManager)
[2020-12-02 15:15:11,153] INFO Send 1000 message, keyCount is 251 (org.apache.tubemq.example.MAMessageProducerExample)
[2020-12-02 15:15:11,656] INFO Send 2000 message, keyCount is 501 (org.apache.tubemq.example.MAMessageProducerExample)
[2020-12-02 15:15:12,526] INFO Send 3000 message, keyCount is 751 (org.apache.tubemq.example.MAMessageProducerExample)
[2020-12-02 15:15:12,950] INFO Send 4000 message, keyCount is 1001 (org.apache.tubemq.example.MAMessageProducerExample)
[2020-12-02 15:15:14,990] INFO Send 5000 message, keyCount is 1251 (org.apache.tubemq.example.MAMessageProducerExample)
[2020-12-02 15:15:18,017] INFO Send 6000 message, keyCount is 1501 (org.apache.tubemq.example.MAMessageProducerExample)
[2020-12-02 15:15:18,832] INFO Send 7000 message, keyCount is 1751 (org.apache.tubemq.example.MAMessageProducerExample)

[2020-12-02 15:39:07,835] INFO Starting Fetch Worker Pool ! (org.apache.tubemq.client.consumer.MessageFetchManager)
[2020-12-02 15:39:07,835] INFO Prepare to start Fetch Worker Pool, total count:1024 (org.apache.tubemq.client.consumer.MessageFetchManager)
[2020-12-02 15:39:07,901] INFO Fetch Worker Pool started ! (org.apache.tubemq.client.consumer.MessageFetchManager)
[2020-12-02 15:32:31,844] INFO Receive messages:63000 (org.apache.tubemq.example.MsgRecvStats)
[2020-12-02 15:33:41,768] INFO Receive messages:116000 (org.apache.tubemq.example.MsgRecvStats)
[2020-12-02 15:34:25,348] INFO Receive messages:148000 (org.apache.tubemq.example.MsgRecvStats)
[2020-12-02 15:34:52,044] INFO Receive messages:168000 (org.apache.tubemq.example.MsgRecvStats)
[2020-12-02 15:35:00,441] INFO Receive messages:174000 (org.apache.tubemq.example.MsgRecvStats)

@yuanboliu  Thanks!
Version 0.7.0 is being released, and I will merge it later.


Play spot

Motivation and Context
 Providing spot yaml file for Habitat 3.0, and users who want to test Spot in replica scene. It fixs
(1) Calibrate Spot camera parameters to align them with the real camera parameters, including resolution, field of view
(2) Update Spot radius in yaml file to be consistent with the real robot
(3) Update actions.py to consider the base offset, and force the leg to stand still when moving.
(4) Update actions.py to mask up certain control joints what are not in the real robot
(4) Adjust Spot base offset parameters.
How Has This Been Tested
Both RGB and Depth images are aligned. The following is the image when the gripper is close.

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have completed my CLA (see CONTRIBUTING)
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Spot arm control parameters and the order

video
https://user-images.githubusercontent.com/55121504/222530069-8ea8f1fd-5285-41c7-9457-103787944354.mp4


Tabs setting in .editorconfig not used for new file - have to reopen file before it work

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T18:05:38.342Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

vscode-eslint
dba
1.2.11

gitlens
eam
4.4.3

csharp
ms-
1.12.1

PowerShell
ms-
1.4.1

debugger-for-chrome
msj
3.2.0

material-icon-theme
PKi
2.2.0

vscode-icons
rob
7.12.0

(1 theme extensions excluded)

Steps to Reproduce:

Have an .editorconfig somewhere in the file system where the "indent_style = tab" setting is.
Right-click in the explorer-pane to create a new .js file
When you click "tab" spaces are inserted and not tabs as expected from the .editorconfig
Close the file and open gain. NOW it works correctly.

Reproduces without extensions: No. Even after reloading the file the indent_style setting of .editorconfig file is NOT used. Maybe the support for .editorconfig comes from one of the extensions?

VS Code does not support editorconfig without installing the corresponding extension.


Something when wrong dialog

What's the Problem?
Just to make thing quicker
Solution/Idea
Open logs folder and open new bug report on GitHub. doesn't make sense to go to the chose template page since a crash wouldn't be a feature request. And the log folder should open when clicking it so it quicker to make the report/help user who don't know where the logs are to attach them.
Alternatives
None
Priorities
No response
Files Version
1.9.21
Windows Version
10.0.19043.1151
Additional comment
No response

Closing due to inactivity


Bot is not deleting messages in captcha mode

Basically, Strict mode is on, Captcha is used as authentication.

User A joins.
A sends some link to a scam site
Bot Does not delete message until the user is kicked

Expected Behaviour:

Bot deletes any messags that does not have to do with the captcha until they solved the captcha.

Try giving Shieldy super admin right (all admin rights). Telegram seems to throttle non-super admins ability to delete messages and ban people for some reason. Please, reopen this issue if the issue persists.

Also, try /restrict.


allTopicPartitionsNumber not equals expected error

Description of issue encountered
Hi everyone,
i face an issue using apache pulsar client v2.6.1 in my java program that subscribe to a topic pattern with following exception:
Failed to subscribe for topic [persistent://xxxxx/agent_xx/event-967b12df-cd08-4467-a31d-9a38928f0727] in topics consumer java.lang.IllegalStateException: allTopicPartitionsNumber 124 not equals expected: 123.
What i can see in my logs is:

my program try to create a consumer on a specific topic.
my program is successfully connected on the specific topic with  just created consumer
warnings logs are thrown with exception.
consumer is directly closed.

Below a piece of related stacktrace:

2020-09-07 12:43:13,410 INFO  [pulsar-client-io-1-1] org.apache.pulsar.client.impl.ConsumerImpl: [persistent://xxxxx/edge_xx/event-967b12df-cd08-4467-a31d-9a38928f0727][data_subscription] Subscribing to topic on cnx [id: 0x52b7b3b6, L:/<IP_ADDRESS>:57566 - R:pulsar-proxy.default.svc.cluster.local/<IP_ADDRESS>:6650]
2020-09-07 12:43:13,411 INFO  [pulsar-client-io-1-1] org.apache.pulsar.client.impl.ConsumerImpl: [persistent://xxxxx/edge_xx/event-967b12df-cd08-4467-a31d-9a38928f0727][data_subscription] Subscribed to topic on pulsar-proxy.default.svc.cluster.local/<IP_ADDRESS>:6650 -- consumer: 5898
2020-09-07 12:43:13,411 WARN  [pulsar-client-io-1-1] org.apache.pulsar.client.impl.MultiTopicsConsumerImpl: [MultiTopicsConsumer-ff083] Failed to subscribe for topic [persistent://xxxxx/edge_xx/event-967b12df-cd08-4467-a31d-9a38928f0727] in topics consumer java.lang.IllegalStateException: allTopicPartitionsNumber 124 not equals expected: 123
2020-09-07 12:43:13,413 INFO  [pulsar-client-io-1-1] org.apache.pulsar.client.impl.ConsumerImpl: [persistent://xxxxx/edge_xx/event-967b12df-cd08-4467-a31d-9a38928f0727] [data_subscription] Closed consumer
2020-09-07 12:43:13,413 WARN  [pulsar-client-io-1-1] org.apache.pulsar.client.impl.MultiTopicsConsumerImpl: [MultiTopicsConsumer-ff083] Failed to subscribe for topic [persistent://xxxxx/edge_xx/event-967b12df-cd08-4467-a31d-9a38928f0727] in topics consumer, subscribe error: java.lang.IllegalStateException: allTopicPartitionsNumber 124 not equals expected: 123
2020-09-07 12:43:13,413 WARN  [pulsar-client-io-1-1] org.apache.pulsar.client.impl.PatternMultiTopicsConsumerImpl$PatternTopicsChangedListener: [MultiTopicsConsumer-ff083] Failed to unsubscribe topics: java.lang.IllegalStateException: allTopicPartitionsNumber 124 not equals expected: 123
2020-09-07 12:43:13,413 WARN  [pulsar-client-io-1-1] org.apache.pulsar.client.impl.PatternMultiTopicsConsumerImpl: [MultiTopicsConsumer-ff083] Failed to recheck topics change: java.lang.IllegalStateException: allTopicPartitionsNumber 124 not equals expected: 123

On the other side of broker, there are many producers and the producer that should push data in same topic where the previous consumer failed to subscribe was temporary disconnected. I think i faced this error just after this disconect but not sure.
Did someone face this issue of mismatch counter ?

@otmanel31 Thanks for reporting this issue, This looks like a race condition, we should remove the check in method: MultiTopicsConsumerImpl.doSubscribeTopicPartitions.

yeap thanks

@jiazhai I too have the same issue. Is there anything that can be done meanwhile you publish a bug fix ? By the way is there an ETA on the bug fix ? Thank you.

is it solved in the 2.6.2 ? anybody knows ? :)


Add exercises for unstructured mesh as Jupyter notebook

I created a Jupyter notebook from the README.md of the unstructured mesh tutorial.
@andrewwinters5000 can you please confirm that everthing looks ok and that the notebook actually works for you?

Thanks a lot for your feedback!

* You should add a cell instantiating the project in the main directory

Done.

* You should clear all output before uploading the notebook

Done.

* I got an error message when loading the notebook for the first time

Do you still get that error and could you post it here please?

* I get an error `unable to determine if out/solution_000180.vtu is accessible in the HDF5 format (file may not exist)` from `trixi2vtk("out/solution_000*", output_directory="out", nvisnodes=12)`

Should be fixed - could you please retry?

* The notebook doesn't cover everything from the README.md - that is on purpose? Maybe you could add a note that the remaining part is explained in the README.md?

Oops, that was an oversight... Could you point me to the part that's missing?

Do you still get that error and could you post it here please?

Notebook failed to load

The error was:
TypeError: ext.toLowerCase is not a function

See the error console for details.

Oops, that was an oversight... Could you point me to the part that's missing?

You stop at Exercise 2a. Thus, the remaining part is missing completely

* I get an error `unable to determine if out/solution_000180.vtu is accessible in the HDF5 format (file may not exist)` from `trixi2vtk("out/solution_000*", output_directory="out", nvisnodes=12)`

Should be fixed - could you please retry?

Yes, it works for me now :+1:

Oops, that was an oversight... Could you point me to the part that's missing?

You stop at Exercise 2a. Thus, the remaining part is missing completely. The last sentence I see is

Now we are ready to generate an unstructured quadrilateral mesh that can be used by Trixi.

That must be an issue on your end, I think: https://nbviewer.jupyter.org/github/trixi-framework/tutorial-2021-icosahom/blob/exercise-in-jupyter/unstructured_mesh/exercises_unstructured_mesh.ipynb

I never had such issues with Jupyter notebooks before. If it happens for me, chances are that others will get similar problems, too. Maybe it's related to the error message I get?

Could you add HOHQMesh.jl to the Project.toml/Manifest.toml?

Anyway, if I'm the only one getting this error we can go ahead and merge this. We will remember to tell people to look at the README.md when the notebook is broken for them, too

Do you still get that error and could you post it here please?

Notebook failed to load

The error was:
TypeError: ext.toLowerCase is not a function

See the error console for details.

I tried to search the interwebs but couldn't find anything useful. Others have reported issues with Jupyter after upgrading their installation - did you do something like that recently? If not, could you maybe post the output of the error console?

Could you add HOHQMesh.jl to the Project.toml/Manifest.toml?

Done in 8ca7a79/

Anyway, if I'm the only one getting this error we can go ahead and merge this. We will remember to tell people to look at the README.md when the notebook is broken for them, too

Do you think it's necessary to keep the README if both nbviewer and the GH preview of the notebook work properly? TBH, I'd prefer to remove the README to retain a single source of truth.

I tried to search the interwebs but couldn't find anything useful. Others have reported issues with Jupyter after upgrading their installation - did you do something like that recently? If not, could you maybe post the output of the error console?

No, I didn't do anything like that. The other notebooks run fine and without any error on my system...

Well, everything is fine after your latest update :partying_face:

Well, everything is fine after your latest update partying_face

Thanks again for your feedback. I just ditched the now obsolete Markdown file for the unstructured tutorial. If @andrewwinters5000 agrees, feel free to merge this PR. It still uses HOHQMesh v1.0.0 (since the new package seems not to be picked up by the Pkg servers yet), but since we don't need the newest version for these exercises, I think we're good to go.

I added code to remove the margins of the Jupyter notebook. This makes it a bit easier to read the output of HOHQMesh (which is quite wide)

@andrewwinters5000 Feel free to merge this PR if everything looks good to you

LGTM! Thanks @sloede for converting this into a Jupyter notebook


update to portainer section in documentation with mention of security control options

And thanks for using Portainer!!!

Thanks for your valuable comment! I really appreciate it.
If you know someone who might find this project useful, please, do not hesitate to talk about it :smile:
I will merge your commit in the dev branch and later update main with all changes.


Add serve-favicon to backend

Add serve-favicon to backend/server.js
Reources: https://www.npmjs.com/package/serve-favicon

Can I try this ?

@ayush015
Sure 👍

Assigned it you.
Let me know if you have any questions.

Hey @ayush015
Any word on this ?

working on it . Will try to finish it by today

@lelouchB Done please review #131


Triggering async data request in ES6 "constructor()" or "componentWillMount()" or "componentDidMount()"

(I'm fairly new to React and Redux, and so I'm still trying to figure out the best coding patterns and practices, so apologies if this is obvious to everybody but me.)
I'm working on a React/Redux app which has several components which request their own data.  For example, when a "/users" route is invoked, the <Users /> component gets invoked, and that component triggers an async call (via redux-thunk) which updates the Redux store with the fetched user data, and then ultimately the users data appears within the <Users /> component.
The render() function within <Users /> is just watching for changes to this.props. The parent of <Users /> watches the Redux store, and of course passes the user data down.
This all worked fine in React 0.13.  Or at least it "worked" with no errors/warnings in the console.  I updated to 0.14 late last week, and started to see the following warning in the logs:
Warning: setState(...): Cannot update during an existing state transition (such as within render). Render methods should be a pure function of props and state.
I floundered around, and finally figured out that the problem was that my async data request was in the class constructor. Something like this:
constructor(props) {
    super(props);
    fetchUsers();
}

render() {
    return ( do the stuff to output the user data );
}

If I moved the fetchUsers() call to either componentDidMount() or componentWillMount(), everything functioned properly, and the error went away.
So my question is ultimately this:  what is going on here? What is the functional difference between these three functions? My (obviously incorrect) assumption was that I should request the data when the class gets initialized, which is why I put the async call in constructor().  Why does that not work, why do those two React lifecycle methods work, and which one of the two is preferable?  React's docs say componentDidMount() is the right method to use, but I would think I'd want the data before the component is mounted, which make me think componentWillMount() should be the method I use.

Is the warning coming from React Redux's usage of state?
Or are you putting data from store into the state manually?
Can you provide an example reproducing the issue?
That said, using componentWillMount is the way to go. Why React doesn't encourage setState() calls inside constructor, I'm not sure, but it's better to ask in React issues than here.

Thanks for the reply, Dan.  I posted the question here because the problem seems to be originating in redux-thunk.
I can do my best to piece together an example.  This isn't exactly the code I have executing, but it is, I think, a close enough approximation to illustrate the issue.
index.js:
ReactDOM.render(
    <Provider store={store}>
	<App />
    </Provider>,
    document.getElementById('root')
);

app.js:
render () {
    <GetUsers />
}

export default connect (state => state)(App);

getusers.js
import React, { Component, PropTypes } from 'react';
import {connect} from 'react-redux';
import { fetchUsersFromServer } from "../actions"
class GetUsers extends Component {

constructor (props) {
	super(props);
	this.props.dispatch ( fetchUsersFromServer () );
}

render () {
	return (
		<OutputStuffHere data={this.props.users} />
	);
}
};

export default connect( (state) => {
return {
	users: state.users
}
})(GetUsers);

actions.js
function getUsers (payload) {
return {
	type: GET_USERS,
	payload: payload
}
}

function receiveGetUsers (payload) {
return {
	type: RECEIVE_GET_USERS,
	payload: payload
}
}

export function fetchUsersFromServer () {
return (dispatch) => {
	dispatch ( getUsers() );
            // doesn't matter if you make an async call here or not
            // a single "dispatch()" call will trigger the error
	// dispatch ( receiveGetUsers() );
}
}

reducers.js
function getUsers (state = defaultState.users, action) {
switch (action.type) {
	case GET_USERS:
		return Object.assign({}, state, {
			isFetching: true
		})
	case RECEIVE_GET_USERS:
		if (action.payload.success === true) {
			return Object.assign ({}, state, {
				isFetching: false,
				courses: action.payload.data
			});
		} else {
			return Object.assign ({}, state, {
				isFetching: false,
				data: {},
				error: {
					hasError: true,
					message: action.payload.message
				}
			});
		}
	default:
		return state;
}
}

I hope the sample code is somewhat useful.  What I found somewhat interesting was that in the fetchUsersFromServer() call, it didn't matter if I actually made an async request or not, as I indicate in the comment above. I guess maybe that means this is just me not understanding the React lifecycle properly. Again, I posted this problem here because the problem gets exposed within the thunk, though I realize that doesn't mean the thunk itself is at fault.
So if the real answer here is "make async calls in componentWillMount(), then I'm happy with that answer. I suppose I'm just trying to get a better understanding of how these parts work together, and why this issue only became apparent when I upgraded to React 0.14.
Thanks again!

Is it too much to ask of you to create a test in this project that emits this warning?
This would help us fix it and ensure the right thing happens instead.

Sure, I'll do that.

Okay, I've got a simple working test, based on npm/webpack. I'm not sure what I should do with it at this point. I could upload it to my own github account, and then point you to it, I suppose. I wasn't sure if you actually wanted me to upload the whole thing to the react-redux repo. What makes the most sense from your perspective?

Sorry, I meant a unit test.
git clone https://github.com/rackt/react-redux.git
cd react-redux
npm install
npm run test:watch

This should launch our test runner.
Then you can add the test emitting the warning to connect.spec.js (see other tests there for inspiration). To make it easier, you can write it.only() instead of it() so only your test runs.
Does this make sense?

Yes, it does. I admit I've never written a unit test before, so figuring out how to do that is a) useful for me, but b) will take some time. This isn't urgent for me, but if it's somewhat urgent for you, i could at the very least zip up the sample project I have and get that to you somehow--at least that would illustrate the issue I'm seeing.

No urgency—take your time!

By the way, I wasn't able to reproduce this myself.
Are you sure it's a problem with react-redux@latest?

I’ve set this aside for now, but yeah, let me fire it up again, make sure I’m on the latest libraries from NPM, and test again.
On Oct 7, 2015, at 1:09 PM, Dan Abramov <notifications<EMAIL_ADDRESS>wrote:
By the way, I wasn't able to reproduce this myself.
Are you sure it's a problem with react-redux@latest?
—
Reply to this email directly or view it on GitHubhttps://github.com/rackt/react-redux/issues/129#issuecomment-146281090.

I just encountered this issue with
react-redux: 3.1.0
redux: 3.0.2
react: 0.14.0
Moving async actions to componentWillMount fixed it for me...

Note that I could not consistently reproduce this; sometimes it raised warning and sometimes it did not, I assume it could be related to batching of updates that React does to optimize perf?

@jesenko Can you try creating a test that emits the warning?

Hi Dan,
I know this may be somewhat less than ideal, but I'm not going to be able to create a unit test in timely fashion, so in absence of that, I have created a small sample project that should demonstrate the problem.  Or, at least, it demonstrates it on my machine.  Here's the repo:
https://github.com/bmueller-sykes/redux-setstate-test
Once you run npm install and start, you should be able to to go localhost:3000, and then toggle between the two links. If you look in the console, you should see the setState() warnings.
FWIW, this project is on React 0.14, react-redux 3.1.0, redux 3.0.2, and redux-thunk 1.0.0.
The code which appears to trigger the error is in src/components/users.js.  You'll see that the fetchUsers() call is currently invoked in constructor(). If you move the call to the currently commented-out componentWillMount(), then everything appears to work properly.
Again, apologies that this is not an official unit test, but at this point it seems like getting a working test in front of you sooner rather than later is at least a decent step forward.
Thanks!

Thanks for putting up a repro! I'll look into it with a couple of days.
If somebody feels like turning this into a failing test, please do.

Cool. Let's hope it's useful!

Tried creating a failing test for this
https://github.com/rackt/react-redux/compare/master...epeli:fail129?expand=1
but it's not failing! I don't know why. Seems like it should because the constructor and dispatch is called between the component render calls which would indicate it's part of the render but I guess it's not...

@bmueller-sykes your example is not actually async but actually this issue seems to be about sync dispatches from constructor anyway.
https://github.com/epeli/redux-setstate-test/commit/62c3dc885fb17b598ac74559ac6f6adc15ef401c

Yes, my apologies if I didn't say that. I had thought that the problem was with an async data call, and therefore perhaps some race condition was being encountered.  Then I pulled out the async data call, but left the "thunk" stuff in place, and just made the two dispatch calls, and I still saw the problem.  And it doesn't happen every time, either--in the test I built, it appears to happen roughly every other time. That kind of looks like a React lifecycle issue, but again, that's only a marginally informed guess.
As I said at the top, things work (or at least I see no errors in the log) if the call is put in componentWillMount(). Maybe this means that React is doing some type of cleanup on calls that are in that method as opposed to constructor()?

I also tried creating isolated unit test for this, but could not get it to emit warning...dispatching multiple actions in constructor resulted in no warnings...

This is not a bug in React Redux.
This happens when dispatch() inside one component's constructor causes a setState() inside another component. React keeps track of the “current owner” for such warnings—and it thinks we're calling setState() inside the constructor when technically constructor causes a setState() inside some other part of the application.
I don't think we should handle this—it's just React trying its best do its job. The solution is, as you correctly noted, to dispatch() inside componentWillMount() instead.

Hi Dan,
Thanks for the reply.  I was never certain this was a “bug” or just "bad practice by me", nor if it were a bug, where the bug was. It just seemed like this repo was the most likely place I’d get an answer (if it was in react, redux, or react-redux).
So I have a question and a reaction.
The question is, regarding the sample app I posted, what are the two components in question? You said a dispatch() in one component triggers a setState() in another component. In my example, is that App and Users?  And why did dispatch() in one component cause a setState() in another? Is that due to a bad coding pattern, or something internal to React?  I think I'm still trying to understand what the functional difference is between constructor() and componentWillMount(), since they are both called once at the start of a component's life cycle.
My reaction to this is that perhaps I wish there were documentation somewhere about when constructor() and componentWillMount() should be used in React. It seems like the lesson here is that you shouldn't use constructor to execute Redux calls, but I don't know if there are other gotchas out there.  I don't think I'm suggesting that you need to be the one to write this documentation--I'm more just throwing it out to the universe.
Anyway, thanks!

My reaction to this is that perhaps I wish there were documentation somewhere about when constructor() and componentWillMount() should be used in React.

Just don't execute side effects in constructor. It's only for initializing state (and perhaps other variables). Don't make calls or change the state of your app from there.

The question is, regarding the sample app I posted, what are the two components in question? You said a dispatch() in one component triggers a setState() in another component. In my example, is that App and Users?

A route change caused dispatch which caused mounting Users which caused another dispatch in its the constructor.

And why did dispatch() in one component cause a setState() in another? Is that due to a bad coding pattern, or something internal to React?

Any time you call dispatch(), all connect()-ed component wrappers have their setState() called so that the connected component receive that new state as their props. It's just how React Redux works.

Ok, thanks.