RFC: p5.initSound method

add initSound method

add a method p5.initSound on the global p5 object. It starts the AudioContext on a user gesture. The user can specify which element should listen for a user gesture, otherwise it falls back to creating a button on the first p5 sketch like this:

^ that's the easiest usage, to call it before preload.
But it can also be used with arguments specifying which element should be used to initialize audio, and it returns a promise, or calls a callback.
function setup() {
  background(255, 0, 0);

  var myButton = createButton('click to start audio');
  myButton.position(0, 0);

  p5.initSound(myButton).then(() => {
    var mySynth = new p5.MonoSynth();
    mySynth.play('A6');
    background(0, 255, 0);
    myButton.remove();
  });
}

or
var myButton;

function setup() {
  background(255, 0, 0);

  myButton = createButton('click to start audio');
  myButton.position(0, 0);
  myButton.mousePressed(startAudio)
}

function startAudio() {
  p5.initSound();
  var mySynth = new p5.MonoSynth();
  mySynth.play('A6');
  background(0, 255, 0);
  myButton.remove();
}

or, similar to a custom preload, we can create a custom HTML element and stylize it however we want.
<button id="p5_init_sound">Click here to start</button>

p5.initSound('#p5_init_sound')

deprecate userStartAudio method

deprecate p5.prototype.userStartAudio, which historically the same thing as initSound, but is on the prototype so cannot be called before preload. There is no need to have this method on the p5 instance, because the audio context is shared across instances (there should only be one audio context on the page)

Testing
To test in Chrome, go to People --> Add Person before loading a site so that (this resets your Media Engagement Index, which is used to determine whether autoplay is allowed on a given domain)

Hi @therewasaguy thanks for jumping on this! Sorry for the delay, I was taking a brief break from the computer. This is really exciting!
I wonder if the automatic adding of a button will feel obtrusive at times. I like it as an option but I wonder if there is a way that initSound could know if it is already in a gesture. For example, I am curious how this would work with something like:

function setup() {
  background(255, 0, 0);
}

function mousePressed() {
  p5.initSound();
  var mySynth = new p5.MonoSynth();
  mySynth.play('A6');
  background(0, 255, 0);
}

would I see a button push the canvas down for a brief second?
My only other concern is the member method dot syntax for p5.initSound(). I understand that this enables a ton of functionality (like calling outside of p5 functions) and that I proposed dot syntax in a previous comment 😛 , but it can be opaque for new learners. This is just a note for background consideration though.

Thanks for taking a look @stalgiag ! Really appreciate your perspective here.

I wonder if the automatic adding of a button will feel obtrusive at times.

Yes, probably!
Some options come to mind, option 1 is my favorite, but I would love some input.

Only create a button if the user supplies an argument for a CSS selector that does not already exist. (There is already an arg to supply an existing element, or a p5 / DOM Element)

Never create a button - depend on the user supplying (and styling) the html element

[bad idea] Create a separate method p5.initSoundAndCreateButton. But this adds to the API.

Another path...

Rethink this approach, continue to use a method that is on the p5 context, like userStartAudio, and update examples to have something like

var btn;

function setup() {
  btn = createButton("Tap to start audio");
}

function mousePressed() {
  userStartAudio(btn, removeBtn);
}

function removeBtn() {
  btn.remove();
}

I like the clarity of 4, the main downside is that this would really clutter the examples.

dot syntax

I hadn't considered this, thanks for bringing it up. I guess this could lead to some confusion because the way we instantiate p5 sound object (i.e. new p5.MonoSynth()) refers to the p5 instance, and so can't be used outside of p5 functions.
This could be a reason to lean towards 4...

I like the flexibility of 4. It might crowd some examples, but perhaps it would be possible to simplify some examples by making the arguments to userStartAudio() optional and just requiring that it is placed inside a gesture callback?
Which I guess brings up some questions about how someone would write a simple sketch that played a sound upon mouse click. Would it look like this?
let sound;

function setup() {
  sound = loadSound('mySound.mp3');
}

function mousePressed() {
  userStartAudio();
  sound.play();
}

The meaning of userStartAudio() becomes a bit obtuse in this example. I don't know if there is any way around this problem without requiring a dom element for starting sketches.
Definitely a tough design decision. Perhaps @lmccart @outofambit  @limzykenneth or any other contributors have thoughts?

From what I can come up with, there's obtrusive and unobtrusive methods. Obtrusive ones will be once the coder include userStartAudio or p5.initSound (whichever we go for) in their sketch, the user will either see an element or some kind of message to instruct them to interact somehow. Unobtrusive will be just adding those functions in mousePressed() or otherwise and let the coder handle informing the users to interact with the sketch. Each have their own details as well as pros and cons.
I wonder can we combine the two so that if it is called in setup (or globally in the case of p5.initSound) we go for the obtrusive method and maybe grey out the sketch with a semi-opaque background with a message to click; then if it is called anywhere else the coder will need to take care of informing their users themselves.

To me, at least the unobtrusive version, similar to @stalgiag's snippet above makes sense.
Maybe the name userStartAudio is confusing, because you're not actually restarting it with each mouse press. I'd assume you would check behind the scenes and start the audio context only if it didn't already exist. Something like enableAudio, while still not quite accurate, feels a little less confusing. Or ensureAudio which is more accurate but maybe less intuitively named.
Additionally having an obtrusive method, that is, putting up default element to prompt user interaction, is an interesting idea. I do like the simplicity of being able to put userStartAudio in setup.

Thank you everyone for your thoughtful comments, and happy 2020!
For now, I'm going to continue down the unobtrusive route and just revise all the examples to demonstrate the best practice of waiting for a user gesture to make any noise as described in https://github.com/processing/p5.js-sound/issues/388
I'm pretty sure this can work without any explicit call to userStartAudio, so maybe we can punt on (re-)naming this method. Though I do like ensureAudio.
For the inline documentation examples, I think we also should include some feedback to the user about how to start audio, and that it should be tied to canvas mousePressed events rather than anywhere on the page (otherwise sounds toggle while editing the example).
So that example would look something like
let sound;

function preload() {
  sound = loadSound('mySound.mp3');
}

function setup() {
  var cnv = createCanvas(100, 100);
  cnv.mousePressed(playSound);

  textAlign(CENTER);
  text('tap to play', width/2, 20);
}

function playSound() {
  sound.play();
}

For the long run, there are a few reasons I think it would be useful to have an initSound method that hooks into preload and ensures the audio context has started before setup is run:

we can start the audio context outside of p5 functions (maybe this is not necessary)
we can ensure that the audio context is started before setup and draw begin (but users can also handle this themselves)
it would be nice to get rid of this warning in Chrome: The AudioContext was not allowed to start. It must be resumed (or created) after a user gesture on the page. It would take substantial refactoring to actually initialize the audio context on that user gesture, rather than simply resume/start an existing one. (https://github.com/processing/p5.js-sound/issues/389)
If we could actually initialize the audio context on a user gesture, we could also load audioworklet modules at that point, rather than hooking into preload and p5's init hook.
starting the audio context is asynchronous, because AudioContext.resume() returns a Promise. So far this doesn't seem to be an issue.

I wonder can we combine the two so that if it is called in setup (or globally in the case of p5.initSound) we go for the obtrusive method and maybe grey out the sketch with a semi-opaque background with a message to click; then if it is called anywhere else the coder will need to take care of informing their users themselves.

I like exploring this hybrid direction!

I'm going to close this for now and keep working on revising the examples to use best practices with the api we already have, PR in progress here https://github.com/processing/p5.js-sound/pull/403


Track is locking for reading when actually writing is taking place

Codecov Report

Merging #962 into master will decrease coverage by 0.1%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #962      +/-   ##
==========================================
- Coverage   74.84%   74.74%   -0.11%
==========================================
  Files          66       66
  Lines        4937     4937
==========================================
- Hits         3695     3690       -5
- Misses        921      927       +6
+ Partials      321      320       -1

Flag
Coverage Δ

#go
76.92% <100%> (-0.12%)
:arrow_down:

#wasm
68.69% <ø> (ø)
:arrow_up:

Impacted Files
Coverage Δ

rtpsender.go
65.47% <100%> (ø)
:arrow_up:

sctptransport.go
75.38% <0%> (-3.59%)
:arrow_down:

icetransport.go
77.93% <0%> (+1.37%)
:arrow_up:

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 974d2e2...31fa746. Read the comment docs.

Fantastic! Thank you so much for the contribution, merged as 14fa0b54ef6db119a16f9ab6da99ba544cf1ec62


Created 698.Partition to K Equal Sum Subsets.cpp

Pull Request Template
Created 698.Partition to K Equal Sum Subsets.cpp
Issue no.(must) - #710
Self Check(Tick After Making pull Request)

[x] This issue was assigned to me if not it will be marked as spam.
[x] My file is in the proper folder
[x] I am following clean code and Documentation.
[x] I have added the title and what program will do first in the file
[x] I have named the file as 698.Partition to K Equal Sum Subsets.cpp
ex. 2. AddToNumbers.py

README - How to Contribute

@ngandhi369 do not make a PR until you're assigned to the issue.


Add documentation for running integration tests to all booster guides

Looking at https://appdev.prod-preview.openshift.io/docs/ and ignoring the Secured booster (for which we have #721), I see that:

The Spring Boot guide has a chapter on running integration tests for all boosters.
The Vert.x guide has a chapter on running integration tests for all boosters except REST API Level 0.
The WildFly Swarm guide has a chapter on running integration tests only for CRUD and Circuit Breaker boosters.

This doesn't sound intentional, and maybe it's just because some parts were left commented out by accident.

@Ladicek Would you propose including integration test sections for all the missions? IIRC, we've never had them for some of the missions, but adding them now will not be a problem.

I'm proposing consistency across all runtimes :-) Spring Boot has a section for integration tests for all missions, Vert.x for almost all, Swarm only for 2 of them. That's weird.

@Ladicek I agree. Let's add integration test sections for all missions/boosters, then.

Also, it might be practical to put the integration test sections into separate topics (which is currently only done for the CRUD mission).

@Ladicek Does running integration tests in an OpenShift project that already contains the booster application remove the application once the test is finished? If it does I'll inlcude a callout  about it in the docs.

Good question. I didn't verify the behavior in such situation. Let me check.

... and the answer is YES, if the application is already deployed before running the test, it will be gone when the test finishes.

I will address the WildFly Swarm integration tests with the dev team in a meeting today.


Prevent Comment Stripping

This extension is stripping comments out of the .csproj.

Should be fixed by 0.4.1.
Please re-open if there are issues.


Fix bugs

I think most features are ready after this merged. I have tested in standalone and cluster modes.
After @hanahmily supported time zone select in UI, I hope we are ready to release alpha.
@apache/skywalking-committers
FYI @liuhaoyang You are ready to go for tests.

Coverage decreased (-0.001%) to 12.298% when pulling 34c76a3127dcbe57725c5bab7fc5a77ffc7aac26 on fix-concurrency into 279c81e9fc8da798b0cc1d88ef418fa160c54e2b on master.


Redstar OS logo

Current state:
No redstar os logo
Wanted state:
Yes redstar os logo
Why the change is sensible:

Feature parity with neofetch

Bloat
Extra code and cruft
RedStar OS users are a majority of desktop Linux users [citation needed]
Why not?

Did id for the meme

Thank you for adding this, now my life is complete.


Update yakyak to 1.5.0

After making all changes to the cask:

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} left no offenses.
[x] The commit message includes the cask’s name and version.

1.5.0 is pre-release

https://github.com/yakyak/yakyak/issues/847


[FLINK-26728][python]Support min/max/min_by/max_by operation in KeyedStream

What is the purpose of the change
Support min max min_by max_by operation in KeyedStream.
Brief change log

Added basic method for max min max_by min_by.
Added min max min_by max_by operator in KeyedStream.
Added unit test case in batch and stream mode for min operator.

Verifying this change
This commits has passed by pytest flack8 etc.

Hi @dianfu
I have already summit this PR.
And merge processing max min_by max_by these operators in this PR.
When you have time to take a look, give some advice.
Thanks a lot.


[Key Vault - Certificates] Integration test libraries failing in nightly runs

Key Vault - Certificates  nightly test runs are failing with:

Error message:
[node-tests]
[node-tests]
[node-tests]   67 passing (15m)
[node-tests]   1 pending
[node-tests]
##[error]The operation was canceled.

For more details check here:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2734527&view=results

Haven't seen this issue in some time


Fix getQueryUGCResult not handling UTF-8 characters properly

Solves an issue that caused getqueryugcresult to not handle UTF-8 characters in titles and descriptions of UGC items.

Looks good.  Basically a similar fix to the one for Cyrillic characters, which was also a UTF-8 problem.  Cheers, sir!


pst exports form Exchange backup

Option to export data from Exchange backup in PST format.

This would be useful, but we don't currently have any good libraries that easily lets us create a PST from Golang. That said, we do currently export all exchange data in other standard formats like eml, ics and vcf.


Update cats-effect, cats-effect-laws to 3.3.2

Updates

org.typelevel:cats-effect
org.typelevel:cats-effect-laws

from 3.3.0 to 3.3.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #359.

Superseded by #359.


Accented characters

"Águila"
"águila"
"Aguila"
"aguila"

becomes
″Águila”
”águila”
“Aguila”
“aguila”

Thanks for bringing up the issue. That seems like a pretty lousy oversight on my part. I’ll take a look at it unless someone happens to get to it before me, but should be a pretty easy fix.


Update add-funds-and-manage-communications-credits.md

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@CarolynRowe PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Remove underscores on Blazor topic+sample members

@Rick-Anderson @wadepickett @scottaddie @serpent5
We'll be reverting work done on issues/PRs such as Alignment on underscores in Blazor examples (dotnet/AspNetCore.Docs #15853).
The subject came up at least three different times since Blazor started. Each convo led to using underscores on private fields. However, we're gong to revert and avoid underscores on members in the future. Reference
I can handle this change for Blazor because it's a small subset of topics, snippets, and sample apps.
I just looked at the whole doc set. There are several hundred underscore prefixes across text, snippets, and sample apps. There are so many that I can't reasonably set aside the time to manually fix them all. I suppose that they can be massaged out over time as the topics are addressed for other reasons.

@guardrex Thanks for including me in this.
Just to note that the quote from the comment thread you referenced comes from a section that also says this:

The field-naming guidelines apply to static public and protected fields. Internal and private fields are not covered by guidelines

That doesn't change anything here, but it's not really telling us to avoid _ on our private fields.
How do you want to proceed with this? Should there be an issue that tracks the work being done over time, or is it just a case of fix-it-as-we-go? I'd be happy to start working through some of the topics to make the change, if that's useful.
FWIW, I can see it being reasonable to keep the _ for the usual private fields, but drop it for the @code sections you mention, cos that doesn't really look like it's part of a class in the same way. I do say that as someone that hasn't worked with Blazor, though.

I don't recommend a tracking issue. It would be kind'a silly given that it would likely never be closed. 😄 It's going to take many months (years? 🙈) to get them all updated.

are not covered by guidelines

Yes, but the product unit doesn't want them used. For same names used on private fields and vars passed into ctors; AFAICT, they want the this keyword used. Ryan said (publicly) that it's under "civil debate" as to how to handle it and that there are "camps" of devs who want to go one way or the other. ⚔ Attaaaaack!!!! ⚔ lol
Now ... after this morning's PR ... all Blazor examples and samples are off of underscores, and that consistency feels good. I really didn't care either way. I just want consistency.

We should avoid _ in the future but not take any action at this point.


Add Linkerd example

work on l5d example
add files for example and work on the readme.md
add ns as well

@kostis-codefresh Done

Thank you!


Fix #2717: Make ArrayBuilder reusable in 2.11.

This is a backport of https://github.com/scala/scala/commit/23040fe8da1dfd0595f7904211b8e391dceb78a6 to our override of ArrayBuilder for 2.11, combined with the changes of 4f3115f63e4a1225cae80fa4b7193ec3c3510a2d to ArrayBuilder.generic.

Refer to this link for build results (access rights to CI server needed):
https://scala-webapps.epfl.ch/jenkins/job/scalajs-pr/3911/
https://scala-webapps.epfl.ch/jenkins/job/scalajs-matrix-build/5172/
Test PASSed.


Fix word in keep stone description

Did you check the text?

Did you check the text?

Yes. The original text reads:
"Despite its name, no stone is used in the production of keep stone. Through the use of a highly guarded process that smelts together adamantine and lead, Highhelm’s greatest crafters were able to develop a material with an appearance that more closely resembles marble than metal."


Change the upgrademode of VMSS to rolling

Which issue this PR addresses:
Fixes: ARO-6610 (Upgrade Policy Mode part)
What this PR does / why we need it:
AzSecPack team policy requires that we don't use Manual upgrade policy.  Automatic shouldn't be used as it can introduce disruption and is not suitable for production workload.  Changing this to rolling also means accepting the default values of the RollingUpgradePolicy, namely 20% maxBatchInstancePercent, maxUnhealthyInstancePercent, maxUnhealthyUpgradeInstancePercent and 0 pauseTimeBetweenBatches.
Test plan for issue:
VMSSes (rp, gateway) can still be created and have upgradepolicy set to rolling
Is there any documentation that needs to be updated for this PR?
N/A
How do you know this will function as expected in production?
VMSSes (rp, gateway) can still be created and have upgradepolicy set to rolling

/azp run ci,e2e

/azp run e2e

/azp run e2e

I deployed this PR to int, and the deployment succeeded.


question about date validator

Is there a way to do a date validation like
this date should be 3 months ( or whatever ) before this other date?
In my case I have paidToDate and paidFromDate.
I want paidFromDate to be less than 3 months before paidToDate. The diff not so important, I just curious how to achieve this kind of custom date thing where one date depends on another and I need to calculate a spread.
paidDateFrom: validator('date', {
  before: 'now',
  after() {
    let paidDateTo = moment(new Date(this.get('model.paidDateTo')));
    return paidDateTo.add(-3, 'month');
  }
})

The above was my try ( it is not working ) .. I guess because you don't support functions for after or before .. but is that a good idea?  maybe another feature to spit out? in the next release?

Hmmmm I dont know why that's not working for you because that is supported (see here).

Yikes .. I see my mistake ... your example showed me what I have to do:
paidDateFrom: validator('date', {
  before: 'now',
  after() {
    let paidDateTo = moment(new Date(this.get('model.paidDateTo')));
    return paidDateTo.add(-3, 'month').format('M/D/YYY');
  }
})

I forgot to return a string with the format method.  Thanks for the hint :)


validate hasNext() on itrerator

By contract, any implementation of the java.util.Iterator.next() method should throw a NoSuchElementException exception when the iteration has no more elements.

fair enough. thanks!


Add "-empty-" text to an empty PDA list

Added in https://github.com/nashmuhandes/PDA_Starter_Kit/commit/bd585a0dfd90b4f82303d48c2278a650fb9c24c5


pod install failure with glog

Description
I have been trying to start with npx react-native init AwesomeProject but having failure with glog.

ERROR LOG
Analyzing dependencies
Fetching podspec for `DoubleConversion` from `../node_modules/react-native/third-party-podspecs/DoubleConversion.podspec`
Fetching podspec for `Folly` from `../node_modules/react-native/third-party-podspecs/Folly.podspec`
Fetching podspec for `glog` from `../node_modules/react-native/third-party-podspecs/glog.podspec`
Downloading dependencies
Installing CocoaAsyncSocket (7.6.4)
Installing CocoaLibEvent (1.0.0)
Installing DoubleConversion (1.1.6)
Installing FBLazyVector (0.62.2)
Installing FBReactNativeSpec (0.62.2)
Installing Flipper (0.33.1)
Installing Flipper-DoubleConversion (1.1.7)
Installing Flipper-Folly (2.2.0)
Installing Flipper-Glog (0.3.6)
[!] /bin/bash -c
set -e
#!/bin/bash
# Copyright (c) Facebook, Inc. and its affiliates.
#
# This source code is licensed under the MIT license found in the
# LICENSE file in the root directory of this source tree.

set -e

PLATFORM_NAME="${PLATFORM_NAME:-iphoneos}"
CURRENT_ARCH="${CURRENT_ARCH}"

if [ -z "$CURRENT_ARCH" ] || [ "$CURRENT_ARCH" == "undefined_arch" ]; then
    # Xcode 10 beta sets CURRENT_ARCH to "undefined_arch", this leads to incorrect linker arg.
    # it's better to rely on platform name as fallback because architecture differs between simulator and device

    if [[ "$PLATFORM_NAME" == *"simulator"* ]]; then
        CURRENT_ARCH="x86_64"
    else
        CURRENT_ARCH="armv7"
    fi
fi

export CC="$(xcrun -find -sdk $PLATFORM_NAME cc) -arch $CURRENT_ARCH -isysroot $(xcrun -sdk $PLATFORM_NAME --show-sdk-path)"
export CXX="$CC"

# Remove automake symlink if it exists
if [ -h "test-driver" ]; then
    rm test-driver
fi

./configure --host arm-apple-darwin

# Fix build for tvOS
cat << EOF >> src/config.h
/* Add in so we have Apple Target Conditionals */
#ifdef __APPLE__
#include <TargetConditionals.h>
#include <Availability.h>
#endif
/* Special configuration for AppleTVOS */
#if TARGET_OS_TV
#undef HAVE_SYSCALL_H
#undef HAVE_SYS_SYSCALL_H
#undef OS_MACOSX
#endif
/* Special configuration for ucontext */
#undef HAVE_UCONTEXT_H
#undef PC_FROM_UCONTEXT
#if defined(__x86_64__)
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__rip
#elif defined(__i386__)
#define PC_FROM_UCONTEXT uc_mcontext->__ss.__eip
#endif
EOF

# Prepare exported header include
EXPORTED_INCLUDE_DIR="exported/glog"
mkdir -p exported/glog
cp -f src/glog/log_severity.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/raw_logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/stl_logging.h "$EXPORTED_INCLUDE_DIR/"
cp -f src/glog/vlog_is_on.h "$EXPORTED_INCLUDE_DIR/"

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for arm-apple-darwin-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for arm-apple-darwin-gcc... /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -arch armv7 -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS13.5.sdk
checking whether the C compiler works... no
/Users/genkiamagata/Library/Caches/CocoaPods/Pods/Release/Flipper-Glog/0.3.6-1dfd6/missing: Unknown `--is-lightweight' option
Try `/Users/genkiamagata/Library/Caches/CocoaPods/Pods/Release/Flipper-Glog/0.3.6-1dfd6/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
configure: error: in `/Users/genkiamagata/Library/Caches/CocoaPods/Pods/Release/Flipper-Glog/0.3.6-1dfd6':
configure: error: C compiler cannot create executables
See `config.log' for more details

React Native version:
npx react-native info
System:
    OS: macOS 10.15.5
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 1.80 GB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 12.16.1 - ~/.anyenv/envs/nodenv/versions/12.16.1/bin/node
    Yarn: 1.22.4 - ~/.anyenv/envs/nodenv/versions/12.16.1/bin/yarn
    npm: 6.13.4 - ~/.anyenv/envs/nodenv/versions/12.16.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 3.6 AI-192.7<IP_ADDRESS>41897
    Xcode: 11.5/11E608c - /usr/bin/xcodebuild
  Languages:
    Java: 14.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

npx react-native --version

4.10.0

xcrun -k --sdk iphoneos --show-sdk-path

/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPhoneOS13.5.sdk

xcode-select --print-path

/Applications/Xcode.app/Contents/Developer

my bash_profile
export PS1="\W \$"

export PATH="$HOME/.anyenv/bin:$PATH"
eval "$(anyenv init -)"

export PKG_CONFIG_PATH="/usr/local/opt/libxml2/lib/pkgconfig"
export LDFLAGS="/usr/local/opt/libxml2/lib"
export CPPFLAGS="/usr/local/opt/libxml2/include"
export CXXCPP="/usr/bin/cpp"

Steps To Reproduce

npx react-native init AwesomeApp
error Error: Failed to install CocoaPods dependencies for iOS project, which is required by this template.
cd ./Awesome/ios && pod install
installation error not fixed.

What I have tried

run comamnd sudo xcode-select --switch /Applications/Xcode.app
uninstall and install xcode, cocoapods
re-creating new projects

Thanks for your help.

I encounter a same error with javascript but it worked with typescript template. Please feel free to comment.
npx react-native init MyApp --template react-native-template-typescript@next

@genk1, I encounter a same error with javascript but it worked with typescript template. Please feel free to comment.
npx react-native init MyApp --template react-native-template-typescript@next

Thanks, but that didn't hel[ my problem... did you try anything else??

It can be fixed before Flipper was used (I am using react-native 0.61.5). It cannot be fixed with 0.63, I modified the  ios-configure-glog.sh with step 4, but it still can't find a modified os-configure-glog.sh. It seems it was cached in someway
The following method is only apply for  react-native <= 0.61.5, without Flipper

You are staying in the project directory

cd node_modules/react-native/scripts

vi ios-configure-glog.sh

Add these two lines and command the original c compiler directory.
export CC=/usr/local/Cellar/gcc/10.1.0/bin/gcc-10
export CXX=/usr/local/Cellar/gcc/10.1.0/bin/g++-10
#export CC="$(xcrun -find -sdk $PLATFORM_NAME cc) -arch $CURRENT_ARCH -isysroot $(xcrun -sdk $PLATFORM_NAME --show-sdk-path)"
#export CXX="$CC"

I googled this for hours and tried every solution including the one above, but I was finally able to fix it by doing
git config --global core.autocrlf false
and then running pod install again

I googled this for hours and tried every solution including the one above, but I was finally able to fix it by doing
git config --global core.autocrlf false
and then running pod install again

you are my sunshine, you saved my life.

I googled this for hours and tried every solution including the one above, but I was finally able to fix it by doing
git config --global core.autocrlf false
and then running pod install again

Paradise waiting for you brother!

I googled this for hours and tried every solution including the one above, but I was finally able to fix it by doing
git config --global core.autocrlf false
and then running pod install again

Thanks for the solution!

None of these work for me. Any suggestions?

run cmd -- sudo xcode-select --switch /Applications/Xcode.app
then try -- pod install

Clone of: https://github.com/react-native-community/cli/issues/1194


fix(bch-js): Bumping to v4.17.2

:tada: This PR is included in version 1.13.5 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


When can we expect the Black Lives Matter banner to be removed?

It's not like I want to fire up a thread between different groups of people. But I think BLM banner has served its ultimate purpose (I hope) of educating people about different racial and ethnic problems.
I feel it's time to remove it. why? Because we cannot have something perpetually considering this being a technical website (unfair) and as time passes it loses its purpose.
Also think for a second about people having different set of views on how racial inequalities has to be handled (I am one of them), instead of throwing BLM banner everywhere they might have some subtle ways of handling it. You never know which one will work, only time will tell. Need to respect difference of opinion.
If the core people are not ready to remove right now, at least start a discussion to fix end date.
Thanks.

I think we can define this date to when black people stop to be killed and have equality opportunities on our society.

Thanks, we'll consider your perspective but don't have an update to share right now.


Make winner database persistent

Coverage increased (+0.3%) to 80.311% when pulling ee21216a80cf363add44c8e4dc81d05a21bb55bd on harmoney-dev:make-winner-database-persistent into 0755f1f8c46837dce33d37e28b6f03461bfa5bed on seatgeek:master.


Unintuitive/incorrect abigen overload names

Version
1.02 from crates.io
Platform
GNU Plus Linux
Description
Using abigen to generate bindings for Uniswap/universal-router:
Functions:
execute(bytes calldata commands, bytes[] calldata inputs)
execute(bytes calldata commands, bytes[] calldata inputs, uint256 deadline)
Overloaded function expected names:
execute_with_deadline and ExecuteWithDeadlineCall
Actual:
execute_with_commands_and_inputs and ExecuteWithCommandsAndInputsCall
which are the 2 params that don't differ

the diff matching is a bit cursed and could use a refactor


Move QPY serializer to own module

Summary
This is the first step to introduce QPY for schedule done in #7300. qiskit.circuit.qpy_serialization.py has been moved to own module and split into several files.
Details and comments
qpy
  ┣ objects
  ┃  ┣ alphanumeric.py   # IO for alphanumeric object including parameters
  ┃  ┗ circuits.py       # IO for circuit and instructions
  ┣ common.py            # Helper function and Enum types
  ┣ formats.py           # Binary format defs (separate file because lines glows with versions)
  ┗ interface.py         # dump and load function exist

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

625 of 701 (89.16%)  changed or added relevant lines in 8 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 83.189%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/qpy/common.py
69
71
97.18%

qiskit/qpy/interface.py
26
28
92.86%

qiskit/qpy/objects/circuits.py
350
384
91.15%

qiskit/qpy/objects/alphanumeric.py
120
158
75.95%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
52005

Relevant Lines:
62514

💛  - Coveralls

Now that #7584 has merged this is no longer blocked and this should be the next qpy pr we merge. But, this will need a rebase to account for the changes made in #7584.

Thanks @mtreinish . I added import for these private functions under qiskit.circuit.qpy_serialization. I hope now we can merge this and move on to the pulse serialization.


Add setting for statistics collection

Which issue does this PR close?

Closes #3847
Rationale for this change

We would like to have a way to enable the collection of statistics.
What changes are included in this PR?

Are there any user-facing changes?

Looks great! Should we also document it somewhere since this seems like an important feature to accidentally miss out? (Or maybe on a subsequent PR we can try to enable this by default for 'local' parquet files, as per #3774).

https://github.com/apache/arrow-datafusion/pull/3877


[release/1.6] Fix cpu architecture detection issue on emulated ARM platform

The PR #7636 to fix cpu architecture detection issue on emulated ARM platform was part of release 1.7, but not in 1.6.
Since docker cli and many others utilize containerd/platforms to parse platform info and depends on containerd 1.6, we should backport it to the long term support release.
This PR is to cherry pick #7636 into release 1.6.

CI is failing on Windows Integration test not related to the change
=== Failed
=== FAIL: metadata TestContainersCreateUpdateDelete/DeleteLabel (0.09s)
    containers_test.go:696: timestamp for updatedat not after createdat: 2023-05-18 21:25:52.3553981 +0000 UTC <= 2023-05-18 21:25:52.3553981 +0000 UTC
    --- FAIL: TestContainersCreateUpdateDelete/DeleteLabel (0.09s)

=== FAIL: metadata TestContainersCreateUpdateDelete (0.34s)

DONE 666 tests, 8 skipped, 2 failures in 487.400s
mingw32-make: *** [Makefile:206: test] Error 1
Error: Process completed with exit code 2.

https://github.com/containerd/containerd/actions/runs/5018286183/jobs/8997603727#step:10:221

Please prefix the pr description with [release/1.6]. This makes it simple to see a backport on the pr list.

For cherry-picks as well, prefer to use -x to include information on what commit is being cherry-picked.

/ok-to-test

I wonder if this is needed for the LTS release, as the original issue was mostly for a corner-case (running containerd in a QEMU (docker-in-docker) environment.

@dcantah  Thanks for the suggestion, cherry-picked with -x option.

@thaJeztah Yeah, the original issue is about running containers in QEMU environment.  It has impact for those who want to build/test ARM binaries  in a container but without actual ARM hardware.
That's the case for all projects using github actions as CI who only has x86 runner.   The backport can help those senarios.
I am not sure when moby, docker/cli will pickup containerd 1.7, if that's happening soon, I am ok not to backport this fix to 1.6.

Hmm, k8s-ci-robot said he understands those commands.  /retest is on the list, but apparently didn't work as expected.
Anyway pushed new commits with -x option to include cherry-picked commit hash in the git message.
CI is failing on Vagrant tests not related to the change.
    default: === Failed
    default: === FAIL: . TestContentClient/ResumeTruncate (6.77s)
    default:     testsuite.go:675: ref ContentClient-n1/1/ref-2-3 locked for 520.357533ms (since 2023-05-19 02:30:39.702926127 +0000 UTC m=+4.077182710): unavailable
    default:     helpers.go:66: drwx------         40 /tmp/content-suite-ContentClient-3937161635
    default:     --- FAIL: TestContentClient/ResumeTruncate (6.77s)
    default:
    default: === FAIL: . TestContentClient (27.77s)

https://github.com/awslabs/soci-snapshotter/pull/620 encountered this bug and was effectively blocked due to the complexity of getting new containerd and docker built from source in the github actions environment. Having the fix backported to 1.6 should make it available in packaged versions of containerd and docker much sooner.

@thaJeztah Yeah, the original issue is about running containers in QEMU environment. It has impact for those who want to build/test ARM binaries in a container but without actual ARM hardware.
That's the case for all projects using github actions as CI who only has x86 runner. The backport can help those senarios.
I am not sure when moby, docker/cli will pickup containerd 1.7, if that's happening soon, I am ok not to backport this fix to 1.6.

In that scenario, all of docker (CLI), dockerd, containerd, and runc would also be running with QEMU emulation, which I definitely would not recommend.
A better solution for that would be to either set --platform when running/pulling images, or to use the DOCKER_DEFAULT_PLATFORM env-var, which sets a default for those flags. That environment variable could probably be set on the docker-in-docker container, in which case docker (and containerd) itself won't have the overhead / potential issues (QEMU is really a best-effort emulation; there's many known issues where it has issues), and only the containers are started with the emulated architecture; here's doing so on my m1 apple (so native architecture is arm64)
docker run -d --privileged -e DOCKER_DEFAULT_PLATFORM=linux/amd64 docker:dind
caafbc99d853f0781160b6ef2cf6d7ee2781f10ef9fb8b716311c1984d5a1ca7

docker run --rm --quiet alpine uname -a
Linux 55521666be9a 5.15.49-linuxkit #1 SMP PREEMPT Tue Sep 13 07:51:32 UTC 2022 x86_64 Linux

Hi, Please inform when can this fix be expected in 1.6 release - any tentative time frame.

@thaJeztah is there a risk taking this in though? The change itself looks straightforward to me

I recall the discussion at the time because it was in the "hot path"; overall it seems fairly low-risk (and there's a sync.Once, so probably won't cause overhead), so happy to remove my rejection.

@thaJeztah understood, agreed the sync.Once lowers the risk.

Hi, Please inform in which release-version of Containerd-1.6, we can expect this update & any tentative time frame ? Plz suggest.

Next 1.6.x patch release; current patch release for 1.6 is https://github.com/containerd/containerd/releases/tag/v1.6.21, so it'll be 1.6.22

Next 1.6.x patch release; current patch release for 1.6 is https://github.com/containerd/containerd/releases/tag/v1.6.21, so it'll be 1.6.22
Thank you for the update. Awaiting for this patch release. Thanks.

@thovikeerthi
Depends on your use case, if you use docker(since docker uses containerd/platforms lib to determine image platform), you need to wait for docker(moby, cli) to take the to-be-released containerd 1.6.22.

Hi Team,
I have docker version '24.0.6, build ed223bc' & containerd version '1.6.24 61f9fd88f79f081d64d6fa3bb1a0dc71ec870523' installed in my host PC (ubuntu 18.04.6 LTS).
But still seeing the same error when I try to cross-compile (host is X86 and cross-compiling source for ARM64 platform) my project code i.e. error snippet is,
""time="2023-11-15T10:27:45Z" level=error msg="failure getting variant" error="getCPUInfo for pattern: Cpu architecture: not found""
Please suggest, is there any way to confirm that fix for the original 'CPU Arch detection' issue in ContainerD is available in my host PC & working as per expectations. Thanks.

@thovikeerthi It might be better to open a ticket in the docker / moby issue tracker (https://github.com/moby/mobv/issues), with details, and a minimal example to reproduce the issue. Note that this change was merged for cases where containerd (and docker) itself are running through QEMU userland emulation; not sure if that is directly related to your issue, but if you have steps to reproduce, that may help to get a better understanding.
Depending on that case; note that docker 24.0.6 and 24.0.7 use containerd v1.6.22 module (build-time dependency);

https://github.com/moby/moby/blob/v24.0.6/vendor.mod#L28
https://github.com/moby/moby/blob/v24.0.7/vendor.mod#L28

Similarly, the BuildKit front-end (dockerfile parser / interpreter) is on a version of containerd that also does not have this patch; https://github.com/moby/buildkit/blob/dockerfile/1.6.0/go.mod#L19
So if the warning printed originates from code elsewhere using this package, that could be related.

Okay thanks

@thovikeerthi It might be better to open a ticket in the docker / moby issue tracker (https://github.com/moby/mobv/issues), with details, and a minimal example to reproduce the issue. Note that this change was merged for cases where containerd (and docker) itself are running through QEMU userland emulation; not sure if that is directly related to your issue, but if you have steps to reproduce, that may help to get a better understanding.
Depending on that case; note that docker 24.0.6 and 24.0.7 use containerd v1.6.22 module (build-time dependency);

https://github.com/moby/moby/blob/v24.0.6/vendor.mod#L28
https://github.com/moby/moby/blob/v24.0.7/vendor.mod#L28

Similarly, the BuildKit front-end (dockerfile parser / interpreter) is on a version of containerd that also does not have this patch; https://github.com/moby/buildkit/blob/dockerfile/1.6.0/go.mod#L19
So if the warning printed originates from code elsewhere using this package, that could be related.

Okay thanks


Rename it to "Tailwind Open UI"

Hello,
Your work is amazing for a newcomer to Tailwind, it really simplifies things. I believe that the basic CSS components should be part of the Tailwind library, as they are part of the Bootstrap library.  In fact, this was the case for version 1 of tailwind. But since version 2, they have become chargeable. In fact, your Starter Kit is becoming an open source version of TailwindUi. I invite you to rename it accordingly "tailwind open UI", it would make things clearer for newcomers, and it would certainly bring you a lot of participation on your repository.
Anyway, thanks again for your great work.

Hey. I am new to open source and Hacktoberfest.
I wanted to know that does this issue says that for all the web pages here, the word 'Tailwind Starter Kit' is to be renamed to 'tailwind open UI' .?


Community Handbook proposal

I propose that CHAOSS starts documenting roles and processes in a handbook.
The goal is to have a central place for community members to learn about how CHAOSS operates.
This should help with onboarding and aligning practices across committees and working groups.
The GitLab handbook served as an inspiration.
https://about.gitlab.com/handbook/

Same here @jgbarah - but love the idea and would be happy to help.
I'd suggest simpler is best to start. ODPi and some of my other projects maintain example governance docs which are good for projects they host on how to get a governance in place if they've never done one before which focuses along those lines ( see https://github.com/odpi/tsc/blob/master/process/example_governance.md ).

Thank you. Yes, let's start small and add pages as we need them.

I am slowly easing back into work and can start looking at building a requirements list for sections.


Identify in 4.2 beta doesn't work on my phone

When I do an identify on my phone with the 4.2 beta Viewer.aspx, the Details pane does not slide out from the right automatically like on the desktop and the overflow menu (3 orange dots on the upper right next to the help button) do nothing when pressed.  On the desktop the overflow button toggles the visibility of the Details pane.
I'm running Chrome 45 on a Motorola Nexus 6 with Android 5.1.1.

Details panel slides out when using Identify and three dot icon now opens and collapses the details panel in the latest development release.  Testing done: Chrome 46, Samsung S5, Android 5.0.0.

This is working for me now - thanks.


Linkable/URL-Based UI state

Apparently we're supposed to make the app state linkable meaning something like:
.../?startdate=&starttime=&enddate=&...
For all the states to be captured in the url, so that when a user copy and pastes the url, it will enter the correct UI state into the application.

Implemented with<PHONE_NUMBER>2d148f05e2e43d06b0852c959cd2ed. 👍


ignore teardown failure on Splash Page

Teardown in ODS-248 may fail if the Splash (loading) page doesn't appear making the entire TC failing (but all the TC steps are successful). So this PR wants to address the problem by adding a Run Keyword And Ignore Error
Signed-off-by: bdattoma<EMAIL_ADDRESS>

Can one of the admins verify this patch?

Jenkins Job (success): PRJOB#350


bump versions

Codecov Report

Merging #5 (9758dad) into master (f8d8089) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #5   +/-   ##
=========================================
  Coverage     81.81%   81.81%
  Complexity      150      150
=========================================
  Files            48       48
  Lines           198      198
=========================================
  Hits            162      162
  Misses           35       35
  Partials          1        1

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 f8d8089...9758dad. Read the comment docs.

Codecov Report

Merging #5 (9758dad) into master (f8d8089) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #5   +/-   ##
=========================================
  Coverage     81.81%   81.81%
  Complexity      150      150
=========================================
  Files            48       48
  Lines           198      198
=========================================
  Hits            162      162
  Misses           35       35
  Partials          1        1

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 f8d8089...9758dad. Read the comment docs.


Blog typo: “San Deigo” (in “Contributor Summit San Diego Schedule Announced!”)

This is a Bug Report

Problem: In Contributor Summit San Diego Schedule Announced! there is a typo: “San Deigo”.
Proposed Solution:
Correct the typo
Page to Update:
https://kubernetes.io/blog/2019/10/10/contributor-summit-san-diego-schedule/
Additional Information:
/area blog
/help
/kind cleanup
/priority important-soon
(I set that priority because KubeCon is imminent, feel free to lower priority)

Hello @sftim, I opened a PR this morning to fix the issue:
https://github.com/kubernetes/website/pull/16822

Thanks @raelga
/close


(Dynamic) Metadata from Pandoc Command Line

It would be great if we can use the metadata passed in command line:

for example: pandoc -M date="$(date "+%B %e, %Y")"

The filter can just parse and add the metadata from command line, and use it when parse the markdown content.
Thanks

It would be great if we can use the metadata passed in command line:

for example: pandoc -M date="$(date "+%B %e, %Y")"

@jefferyyuan, note that the same result could be achieved by redirecting the output of your "date" command to a YAML file which is referenced using pandoc-mustache. I'm also not sure what syntax would be used to implement this feature request, i.e how would metadata be referenced in the mustache style.
I've pasted the contributing section from the README below.

Contributing
Project Status: Inactive
This code is not being actively developed. It was created to fulfill my pandoc writing needs, and the current feature set is adequate for me.
If you have a feature request, it is unlikely that I will be able to implement it for you. You can create an issue to generate discussion. If you implement a feature, you can file pull request and I will review it eventually, as time permits. If you're interested in making major additions to the code, I'd be happy to welcome a new maintainer to the project.

https://github.com/michaelstepner/pandoc-mustache/pull/11 implements this.
Your example would allow {{date}} inside your markdown content and the date will be inserted. However, as @michaelstepner pointed out, you could of just redirected the date to a YAML file.


feat(popover): add svelte component over popover

Pull Request checklist
🚨 Please review the guidelines for contributing to this repository.

[*] Make sure you are requesting to pull a topic/feature/bugfix branch. Don't request your main!
[*] Check the commit's or even all commits' message styles matches our requested structure.
[*] Check your code additions will fail neither code linting checks nor unit test.
[*] Check PR name, it must follow the https://www.conventionalcommits.org pattern
[ ] If it's a new component in CSS, ask for design review

Description
I added :

a Svelte component over the popover vitamin design :)
its stories
a classnames utils, a first step to concatenate classNames and removing falsy ones.

I updated current components in order to use this util.
Please note that it could be useful in other frameworks, such as React.
I took the liberty to add support for Svelte files in prettier, and for the Svelte CSF story format.
Does this introduce a breaking change?

No (I don't think so)

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

@mlefebvre-decathlon thanks again, can you please move your dependency to devDependencies as requested? I will merge it just after :)
thanks


Can sin install just runit-base?

I looked at the runit-init module and it does a lot more than I need. I suppose I could just do a git clone of runit-base once in a while, but sin does an update check, handles directory structure, etc. Basically, I just need runit-base, since I assume using runit-init, as well as everything else Devuan provides will suffice. If you think I'm wrong in this assumption, enlighten me on the subject. If I'm going to use a Debian based distro without systemd or sysvinit with runit as PID 1 and as an init system, is runit-base truly enough?

The runit-init module in SIN was made to rebuild a sysvinit-based OS into a runit-init based system, by a single command. To modify that runit-init SIN module, you can for example:
mkdir -p /usr/local/share/sin/runit-base
cp /usr/share/sin/runit-init/install /usr/local/share/sin/runit-base/

and then edit the file /usr/local/share/sin/runit-base/install as you wish. Feel free to delete anything you don't need, the functional sections are marked in comments.  You can run your new modified script anytime by executing sin runit-base.
WARNING: If you delete everything and just keep the runit-base part, there will be some problems. Don't expect the stability of such system to be anywhere near my AWS EC2 instance. Dpkg and subsequently apt-get will not work properly, services will not start or restart, acpi power management will fail, Runit as installed from Debian/Devuan repository will be pulling conflicting dependencies like "getty-run", etc. The runit-init version in the repository still has some security issues. I fixed them and contributed the fixes, but the fixed version is currently only available in the 'unstable' repository. I recommend pulling and compilling my sources here. Also there is no "socklog" in the repository and must be compiled from source. Socklog (e.g. syslog replacement) is a dependency in some of my runscripts (incron). At the end, you might find that the runit-base alone is just not enough, and there is not much overhead in my runit-init installer.


Added Rollover example

Fixes #649
Changes:
Added the rollover example from the processing website
One thing I wasn't sure about is the category I should place the example in. Right now the pull request will put it in the "Input" category but let me know if you believe that it should be in a different category! Thank you!
Edit: I wasn't too sure how to add reviewer, so tagging @montoyamoraga for review :)

@mattfan00 my only comment before merging this PR,
is that if you heavily based it on the Processing example, or somewhere else,
i would include a credit on the header, and a link to the original one, let me know :)

@mattfan00 my only comment before merging this PR,
is that if you heavily based it on the Processing example, or somewhere else,
i would include a credit on the header, and a link to the original one, let me know :)

Yes, of course! Just pushed a new version linking to the original example


BUG - Preset save detection occationally detecting wrong save status

Can you determine, which version was used?
Version: 1.3.41
Describe the bug
The save reminder doesn't detect saved/unsaved status right. This behaviour is not reproducable by 100%. Sometimes it works correctly, sometimes not. I can't see any depency.
TRY To Reproduce
Steps to reproduce the behavior:

save a preset
close app
see: reminder says "you have unsaved work"

or -

modify a saved preset
do not save it
close the app
see: reminder does not remind me of unsaved work

disfunction only when Layout Mode is not entered during editing

please check with 1.3.41.alpha-2


Update stl to gnustl_static and compiler to gcc

Bug fix for:
https://github.com/googlesamples/android-ndk/issues/53
Updated a few C++ projects
stl to gnustl_static [c++_static/shared not mature]
use gcc to build [clang has trouble on windows(*)]
use source code from ndk directly for native_app_glue and cpufeatures
update gradle build scripts to latest dsl syntax
Tested:  MacX build, emulator and N5X
To build, I used
android studio 2.1 preview 5
ndk-r12-beta1 ( from https://github.com/android-ndk/ndk/wiki)

looks the only failure is about single quotation or double quotation for this
hello-thirdparty/app/build.gradle:        buildToolsVersion = "23.0.2"
If I touch this sample, AppVeyor will fill because this project could not compile at all. One way or the other, I could not make both CI and AppVeyer to be happy. Since it is known issue and single/double quotation does not post any risks, I am inclined to merge in this pull.

LGTM


Update dist files

Forgot to run the grunt tasks to actually make the update. @shawnlonas
BTW looks like some other junk got removed, not sure if someone else forgot to run grunt concat or what.

Looks fine.  Could you merge it, update the release number, and update the reference in goldfish-polymer to point to the new version @wejrowski ?


WIP: Add version comparison capability to Stores

Support pluggable version comparison functions in Store implementations. This
allows extending the semantics of FIFO and cache to support rejecting stale updates.

@googlebot I'm under Red Hat's CLA, probably registered under<EMAIL_ADDRESS>

This PR is a WIP. I'm not adding tests until the general concept has been accepted and an interface agreed upon. This change would help resolve a use case described in #4330  and origin#824 transparently. For example, when processing retries of events from a FIFO, the object to be retried could be safely re-fetched and Pushed onto the queue without danger of racing with a reflector also writing to the same queue, as only the latest state would be accepted internally by the FIFO.
The way I've structured this implementation is to provide a default IsOlder implementation which maintains the current semantics (which are to accept all objects without regard to their logical version).
cc @smarterclayton @bparees @pmorie @erictune @lavalamp @derekwaynecarr (AKA The cache.Store Consortium)

@bparees I think I buy the argument to avoid no-ops with IsNewer. Let's see if others agree before I go a-refactorin'.

If the fifo requeues it needs its own method to do so that calls the test function with the argument order replaced (since the provided func would be aligned with Add coming from an ordered queue

@smarterclayton

If the fifo requeues it needs its own method to do so that calls the test function with the argument order replaced (since the provided func would be aligned with Add coming from an ordered queue

I might be parsing this incorrectly: The fifo doesn't requeue- this is so that an external retry handler can safely re-queue via Add and be confident that doing while racing with a Reflector won't result in stale overwrites into the Store.
Now that I'm thinking about this again, although this closes one window, there's still one more (even smaller window). I want to collect my thoughts before describing it here though.

If FIFO re-queues on error, the re-queue is not coming from the watch (so it is not guaranteed to be newer).  The re-add has to be to the queue, and if the item is already in the queue you would simply not add it.
----- Original Message -----

@smarterclayton

If the fifo requeues it needs its own method to do so that calls the test
function with the argument order replaced (since the provided func would be
aligned with Add coming from an ordered queue

I might be parsing this incorrectly: The fifo doesn't requeue- this is so
that an external retry handler can safely re-queue via Add and be
confident that doing while racing with a Reflector won't result in stale
overwrites into the Store.
Now that I'm thinking about this again, although this closes one window,
there's still one more (even smaller window). I want to collect my thoughts
before describing it here though.

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/4463#issuecomment-74577498

If FIFO re-queues on error, the re-queue is not coming from the watch (so it is not guaranteed to be newer).  The re-add has to be to the queue, and if the item is already in the queue you would simply not add it.

I still feel like we're talking past each other. There are two things adding to the queue: a Reflector, and a retry handler. Both are fetching new data and calling Add. The FIFO itself doesn't re-queue anything.

Here's the window where old data can still get in, and having talked with @bparees I think he already identified this and I was misunderstanding:
For a rapidly changing resource going into a FIFO fed by a reflector and a retry handler and consumed by some controller:

resource.1 is pop'd by controller and fails to process, handed over to retry logic
retry logic fetches resource.2 and is about to call fifo.Add, when:
reflector fetches resource.3 and calls fifo.Add, but before #2's fifo.Add happens,
controller pops resource.3
fifo.Add from #2 completes and resource.2 is now in the queue

@bparees suggested the idea that we just stop relying on state in the queue, and instead treat them as events to trigger lookups in the controllers (e.g. store ObjectReferences and go get the latest state for an object before doing anything with it at the controller entrypoint). Need to think about it more. Would that sidestep the need for something like this PR?

I don't know what you mean by state in the queue.  The queue (and the watch that feeds it) are providing two extremely important guaranteed that are worth preserving:

When Add is invoked by the watch, any existing versions in the fifo or retry queues (if they exist) are invalid and can be discarded immediately
If an event is popped and hasn't been invalidated, it is the most recent version of the event.

I think your proposed changes loses those two characteristics.  Maybe we're talking past each other.

On Feb 16, 2015, at 5:00 PM, Dan Mace<EMAIL_ADDRESS>wrote:
@bparees suggested the idea that we just stop relying on state in the queue, and instead treat them as events to trigger lookups in the controllers (e.g. store ObjectReferences and go get the latest state for an object before doing anything with it at the controller entrypoint). Need to think about it more. Would that sidestep the need for something like this PR?
—
Reply to this email directly or view it on GitHub.

Refactored the interface to "CanReplace" for discussion.

It just occurred to me that in ReplaceIfNewer I'm doing a numerical comparison on ResourceVersion, which is a string. That would need addressed.

The comparison is provided per type, you cannot have a generic default comparator, just a generic per resource type comparator.

On Feb 18, 2015, at 12:38 PM, Dan Mace<EMAIL_ADDRESS>wrote:
It just occurred to me that in ReplaceIfNewer I'm doing a numerical comparison on ResourceVersion, which is a string. That would need addressed.
—
Reply to this email directly or view it on GitHub.

I think the only time you need to worry about stale stuff is when you re-list after a watch closes. And for that, you can probably just clear the queue anyway. Once a watch has started you shouldn't get stale stuff.
So I kind of think that you don't need to do this. And if you do, ResourceVersion comparison is not ideal.

I think the only time you need to worry about stale stuff is when you re-list after a watch closes. And for that, you can probably just clear the queue anyway. Once a watch has started you shouldn't get stale stuff.

You need to worry about stale stuff any time you have more than one goroutine writing to a single FIFO (as is the case in the scheduler- the Reflector and the retry goroutine are both adding to the queue).
As it happens, out-of-order events are okay in the scheduler context, but aren't okay downstream in our controllers. So to get in-order guarantees we have to be careful to never have more than one producer into the FIFO. I thought this PR would help make that guarantee, but I was wrong.

So I kind of think that you don't need to do this. And if you do, ResourceVersion comparison is not ideal.

I'll close this issue tomorrow most likely as we're taking a different approach that doesn't rely on multiple queue producers for retries (which is that this PR was trying to address).

You need to worry about stale stuff any time you have more than one goroutine writing to a single FIFO (as is the case in the scheduler- the Reflector and the retry goroutine are both adding to the queue).

We should fix the scheduler, then-- that's not right. I agree that retries shouldn't be done by having multiple producers.

Abandoning this approach as it doesn't solve the multiple producer scenario and doesn't directly enable safe retries in some other way.


Do not run updateDom() on hidden modules.

Some modules update their dom even when they are hidden. This PR prevents modules from running updateDom whenever the module is hidden. This should fix #2161 #2164.

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS


Missing reference interpolation breaks build

I realise this is probably intentional at the moment but if the input schema contains a comment of the form {{text}} where text is not a valid reference the the build fails with an error:
error: Task error: [Error: Unsupported interpolation encountered: str
  at /var/www/totara/src/main/node_modules/spectaql/dist/themes/default/helpers/interpolateReferences.js:17:13
  at String.replace (<anonymous>:null:null)
  at Object.interpolateReferences (/var/www/totara/src/main/node_modules/spectaql/dist/themes/default/helpers/interpolateReferences.js:13:16)
  at Object.wrapper (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/internal/wrapHelper.js:15:19)
  at eval (<anonymous>:11:344)
  at prog (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/runtime.js:268:12)
  at execIteration (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/helpers/each.js:51:19)
  at Object.<anonymous> (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/helpers/each.js:61:13)
  at Object.wrapper (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/internal/wrapHelper.js:15:19)
  at eval (<anonymous>:9:49)
  at Object.prog [as fn] (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/runtime.js:268:12)
  at Object.<anonymous> (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/helpers/if.js:29:22)
  at Object.wrapper (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/internal/wrapHelper.js:15:19)
  at Object.eval (<anonymous>:8:50)
  at main (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/runtime.js:208:32)
  at ret (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/runtime.js:212:12)
  at ret (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/compiler/compiler.js:519:21)
  at Object.invokePartial (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/runtime.js:334:12)
  at Object.invokePartialWrapper [as invokePartial] (/var/www/totara/src/main/node_modules/handlebars/dist/cjs/handlebars/runtime.js:84:39)
  at Object.eval (<anonymous>:26:28)
[snip]

We have a situation where someone used that syntax in a comment to refer to something else entirely:
     """
     ids argument is in the form "$identifier, $component" the same as in {{str}} mustache helper
     """

we can change this reference of course but it opens us the possibility that developers might accidently add a comment which breaks the docs build without realising it.
I was wondering if it's necessary to break the build or whether instead it could just throw a warning about unsupported interpolations but just ignore them and continue the build?

Option to change this is in main and will be published soon on NPM.

In main and published in v1.2.2.

Many thanks, that looks great.


Remove six from zappa dependencies

Context
Six is currently a dependency of zappa, but zappa no longer supports python 2.x, making the use of six unnecessary.
Expected Behavior
No change in behavior, reduced zappa package size.

six still appears to be a sub-dependency of boto3

Actual Behavior
six included.
Possible Fix
remove six by migrating relevant code to python 3 specific code.

released in 0.56.0, closing.


feat: add ranger-vim

Added ranger-vim to plugins

Just for the record, you only have to commit the manifest.txt. The other files will be regenerated anyway


Update Known-issues.md

Add a new systemd alternative for WSL2.
I've tested it personally. Compared to other solutions, this solution finally support launch systemd-enabled shell directly from start menu, and VSCode Remote - WSL extension. Maybe someone interested in trying it out.
https://github.com/lungothrin/bottled-shell

Thanks!


improve code quality in activites

@juslee @the-dagger @mananwason
Would like you guys to review please.

Looks good :+1: @championswimmer


Sorting Newest, Oldest and Popular is not working on Chrome

I'm confused. I have implemented the callback and everything is working fine except the newest, oldest and popular sort. It's working fine in Firefox, but in Chrome the sort is not working. I'm using ISO 8601 time format, so I think the date format should be okay on multiple browser. Could you help figure me out what's wrong? I've spent 2 days without any luck :(
My site is: www.zetizen.com, in case you need to see the problem..

Never mind.. I try to use the non minified version and it works fine..
I think you should also update the jquery-comments.min.js in the repository :)

Thanks for the comment, we'll make sure to update that in a couple of weeks once we get to work on this library again :)


Scroll bar length is variable

When working with longer MD files (think 10 or 15 pages), this problem is particularly noticeable. The scroll bar starts long when you're at the top, but then shrinks and slows down as you scroll towards the bottom. Once you scroll all the way through the document, it stays at a constant smaller size and works like a normal scroll bar.
The expected functionality, I would think, would be a scroll bar that was already at a consistent length as soon as the document was opened.
I've attached screenshots with photos of the scroll bar for a document immediately upon opening, and then the same document when scrolled all the way to the bottom.

Kind of weird. Not seeing it here. Wonder if it's something in the document.

Try composing a really long document, closing it, and then re opening it. The situation usually occurs for me under similar circumstances.On Dec 23, 2016 12:17 PM, Mike Ward<EMAIL_ADDRESS>wrote:Kind of weird. Not seeing it here. Wonder if it's something in the document.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

I tried with a document 22,000 words long (the CommonMark spec).


Simple cloud - circles over ellipse

Draws several smaller circles around the perimeter of a larger ellipse.

Looks good


Adding a team to another season does not respect the division id

Division id needs to be added to the request:
https://github.com/laingsimon/courage_scores/blob/4c7310b55ef5c7af0ffedb00473657b4aa5686e8/CourageScores/ClientApp/src/components/division_teams/AssignTeamToSeasons.tsx#L56


Pass contents of OPTIONS to memcached client

This is a fix for https://github.com/jaysonsantos/python-binary-memcached/issues/212

The intention behind this PR is to make it possible to pass configuration params through from django.conf.settings.CACHES to the BMemcached client object. At the current time, only the username and password are propagated, which means it is not possible to set other options.
This feature (passing additional options through from Django to the underlying memcached client) was introduced in 1.11 (https://docs.djangoproject.com/en/3.0/releases/1.11/#cache):

Memcached backends now pass the contents of OPTIONS as keyword arguments to the client constructors, allowing for more advanced control of client behavior. See the cache arguments documentation for examples.

The following options are available for the bmemcached client: compression, pickle_protocol, socket_timeout, pickler and unpickler. A sample config might look like
# django settings.py
CACHES = {
    "default": {
        "BACKEND": "django_bmemcached.memcached.BMemcached",
        "BINARY": True,
        "OPTIONS": {  # default values shown
            "compression": None,
            "pickle_protocol": 0,
            "socket_timeout": 3,
            "pickler": pickle.Pickler,
            "unpickler": pickle.Unpickler
        }
    }
}

Ah. So this works for Python 3.7/8 and Django 2.2/3.0 - but not for earlier versions. Not sure I can work out the correct matrix of supported versions.

@jaysonsantos I've pushed a commit with custom InvalidCacheOptions exception in it - let me know what you think (no tests so far - will add those if you approve of the approach).

Let me know if you need to do something else otherwise I will merge it

Nope - I'm done. Thanks for your help / feedback.
On Thu, 9 Jan 2020 at 10:41, Jayson Reis<EMAIL_ADDRESS>wrote:

Let me know if you need to do something else otherwise I will merge it
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jaysonsantos/django-bmemcached/pull/14?email_source=notifications&email_token=AABRB4DC6A6FIDQQOBDJNL3Q435NXA5CNFSM4KD5CT42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIP3G5A#issuecomment-572502900,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABRB4GEIYLHIR2CG5WIOXLQ435NXANCNFSM4KD5CT4Q
.

Thank you @hugorodgerbrown I just released a new version on pypi https://pypi.org/project/django-bmemcached/0.3.0/


test: add sqlness with kafka wal

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?

Add kafka wal config to sqlness
Add sqlness with kafka wal ci config

Run sqlness with kafka locally
Setup kafka standalone

Go to workdir

cd tests-integration/fixtures/kafka/

Run

docker compose -f docker-compose-standalone.yml up kafka -d

Run the Sqlness with kafka wal
cargo sqlness -w kafka -k localhost:9092

Checklist

[ ]  I have written the necessary rustdoc comments.
[ ]  I have added the necessary unit tests and integration tests.
[ ]  This PR does not require documentation updates.

Refer to a related PR or issue link (optional)

Looks like the ci Sqlness Test with Kafka Wal fails sometimes. @WenyXu

Looks like the ci Sqlness Test with Kafka Wal fails sometimes. @WenyXu

Yes, I'm trying to fix it.


Added test cases for bufferAnyIs, bufferBytesIs, constructorIsBuffer

Please, split task.
Now, I see 3 test routines.
The first task

Fix test routine bufferAnyIs
The second task
Fix test routine bufferBytesIs
The third task
Fix test routine constructorIsBuffer

If some of task is finished, make commit and push it.


Do you need help maintaining this list?

I'd love to hop in and clear up some of the pull requests/issues for you.
For reference, I am one of the homebrew-php maintainers, am prolific in the CakePHP community, and have done a similar service for the dokku project.

Hi Jose. I'd really love some help. As you can probably tell the pull requests are really starting to pile up at the moment.
I've added a code of conduct and some basic guidelines for collaborators, and added yourself and @jadb as collaborators on the project.

Awesome great. I will take a look at PRs this afternoon :)

No problem. Thanks for offering to help out. If you need me I'm on Twitter, my account's private, but @jadb can tell you my username, or pop me an email. The address is in the collaborating guidelines.


A lot of reflection functionality like Type.BaseType is not available anymore in dnxcore50

As known, a lot of reflection functionality like Type.BaseType is not available anymore in dnxcore50. A possible solution would be to use:Type.GetTypeInfo().BaseType.
I encountered this issue a lot while converting some of my projects.
I solved this compatibility issue by create a helper library (https://github.com/StefH/ReflectionBridge) : which functions as a bridge to some reflection functionality.
In my normal libraries, I just rewrite all calls from Type.BaseType to Type.BaseType() (so instead of invoking a property, I create an extension method like this:
        public static Type BaseType(this Type type)
        {
#if REFLECTIONBRIDGE && (!(NET40 || NET35 || NET20))
            return type.GetTypeInfo().BaseType;
#else
            return type.BaseType;
#endif
        }

With this new helper functionality, I don't need any ifdefs in my main code, this is solved in the extension method.
Are there any plans for Microsoft or another communicate to also create something like this to help porting code to dnxcore50 ?

@StefH Did run ApiPort and get a RecommendedChange?
@weshaggard Is anything like this planned for .NET Core?

There are currently no plans to provide a bridge between <=NET40 and .NET Core. For the reflection APIs we are adding a lot of the missing ones back but there you still need to go through GetTypeInfo() like above and GetTypeInfo() only exists in NET45 and higher. So if your code is only targeting NET45 and NETCore then there shouldn't need to be any #ifdefs for this type of change.

@StefH I'm closing this issue for now - if you didn't get a recommended change from ApiPort and you think you should, please reopen.


CacheModule in multiple modules not loading the config properly

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior
I have a helper function that creates the CacheModule dynamically based on some input. This function is called multiple times for different modules that rely on CacheModule.
The CacheModule however is not loading the settings correctly. Only one of the settings set are loaded and applied to all other modules using the same function.
function:
export function createCacheModule(options: CreateCacheModuleOptions) {
  options.inject = [ConfigService, ...(options.inject || [])];

  if (options.useFactory) {
    const inputFactory = options.useFactory;
    options.useFactory = async (configService: ConfigService) => {
      const opts = await inputFactory(configService);
      console.log({ opts });
      return opts;
    };
  }

  return CacheModule.registerAsync(options);
}

expected logs:

current logs:

in the second screenshot you can see that only the useFactory of AModule gets called and BModule gets the same config from AModule even though they are created differently.
Minimum reproduction code
https://github.com/GustavoKatel/nestjs-cache-module-test
Steps to reproduce

npm ci
npm run start
check the logs

Expected behavior
I expected the ttl and all other settings to be different for in BModule, but insteead BModule got the same settings from AModule (see screenshots above)
Package version
2.1.1
NestJS version
10.2.8
Node.js version
21.1.0
In which operating systems have you tested?

[X] macOS
[ ] Windows
[ ] Linux

Other
No response

I also ran into this. But after upgrading from 10.2.8 --><EMAIL_ADDRESS>and<EMAIL_ADDRESS>In thisprovided repo  the tests fail , there is also a working branch.

While testing with the following versions:
"@nestjs/cache-manager": "2.2.2",
"@nestjs/common": "^10.3.10",
"@nestjs/core": "^10.3.10"

the issue seems resolved, but a strange bug occurs when CacheModule is registered with the same configuration. It shares the same cache store even if it is imported by different modules. Here is the reproduction: https://codesandbox.io/p/devbox/nestjs-cache-register-bug-2snp4k?file=%2Fsrc%2Fapp.spec.ts
After investigation, I realized that the useFactory function provided by CACHE_MANAGER is only called when the options parameter is registered differently.
https://github.com/nestjs/cache-manager/blob/65d710179e3224fd2d8f3ef2ca09473f84a7e00f/lib/cache.providers.ts#L19
Is there any caching mechanism applied when initializing a dynamic provider here related to ConfigurableModuleBuilder? If so, I think we can fix this issue by generating a unique ID each time the CacheModule is registered, like the following:
static register<StoreConfig extends Record<any, any> = Record<string, any>>(
    options: CacheModuleOptions<StoreConfig> = {} as any,
  ): DynamicModule {
    return {
      global: options.isGlobal,
      ...super.register({ ...options, id: <UNIQUE_ID> }),
    };
  }

Fixed in this PR https://github.com/nestjs/nest/pull/13336


fix(TS): fix type inference for publish variants

We can never get  out of  via TypeScript any how.
Resolves a larger issue where operators with a single, static argument and a single  generic inferred too strongly from the argument and lost the additional type information from the source.

I would really like to revisit the changes you proposed in https://github.com/ReactiveX/rxjs/issues/3833. If not for v7 then for v8.

I'm rebasing this. For some reason there's a build failure in CI that I haven't been able to reproduce locally

This has already been handled.


🐛 Bug Report: AppwriteException: null, Concurrent modification during iteration: Instance(length:2) of '_GrowableList'. (0)

👟 Reproduction steps
when i tried to log in session.
👍 Expected behavior

👎 Actual Behavior
AppwriteException: null, Concurrent modification during iteration: Instance(length:2) of '_GrowableList'. (0)
🎲 Appwrite version
Version 0.11.x
💻 Operating system
Windows
🧱 Your Environment
Flutter
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@nohli, @p4-k4, are you still having problems with the latest SDK?

@stnguyen90 for me it's fixed since appwrite: ^7.0.0 👍🏽

I can confirm it was fixed in flutter windows too. I had opened #59 as duplicate. @stnguyen90. So I assume @anandsubbu007 's was fixed too


Maybe explain in docs how much is compatible with QBASIC

Maybe have compatibility modes if it isn't, to enable old programs to run well!
Awesome project.

Good suggestion as a place to start with documenting.
Yeah, invariably will hit something that clashes, so will likely need some kind of compat flags.


How to add a custom about me text?

Summary
Hi, I've run this command as specified here guide.
But I cannot find a way to add a custom about me, in the guide you say to: "Create a file at<EMAIL_ADDRESS>to edit the text.", but I cannot find the "src" folder.
Am I doing something wrong?
Relevant information
Here is my folder structure:

Theme
emilia
Environment
System:
OS: macOS 11.2.3
CPU: (4) x64 Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz
Shell: 5.8 - /bin/zsh
Binaries:
Node: 15.12.0 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 7.6.3 - /usr/local/bin/npm
Languages:
Python: 2.7.16 - /usr/bin/python
Browsers:
Chrome: 90.0.4430.85
Safari: 14.0.3
npmPackages:
gatsby: ^2.25.3 => 2.32.12
gatsby-plugin-gatsby-cloud: ^1.0.1 => 1.0.2
gatsby-plugin-google-analytics: ^2.4.1 => 2.11.0
gatsby-plugin-manifest: ^2.5.2 => 2.12.1
gatsby-plugin-netlify: ^2.4.0 => 2.11.1
gatsby-plugin-offline: ^3.3.3 => 3.10.2
gatsby-plugin-sitemap: ^2.5.1 => 2.12.0
gatsby-plugin-webpack-bundle-analyser-v2: ^1.1.13 => 1.1.22
npmGlobalPackages:
gatsby-cli: 3.3.0
File contents (if changed)
gatsby-node.js: not present
gatsby-browser.js: not present
gatsby-ssr.js: not present

Hi!
You'll need to create the folders on your own to shadow files. This is also explained in more detail in the linked guide: https://www.gatsbyjs.com/docs/how-to/plugins-and-themes/shadowing/
So simply create the folder structure src/@lekoarts/gatsby-theme-emilia/texts and place a about-me.mdx in it.


Broken Link

https://docs.substrate.io/rustdocs/v2.0.0/sc_consensus_manual_seal/index.html

Hi @demisx, that's a really old link. For more up-to-date Rust doc, try this
https://paritytech.github.io/substrate/master/sc_consensus_manual_seal/index.html


Analyses for body parts

We split them into several issues, but for now, we can have them here:

[ ] TIGER scores (body parts vs. plain cognates)
[ ] concordance analysis
[ ] splitstree
[ ] delta scores

@LinguList Do we keep the body-part related files in this repository, or are they stored elsewhere?

Can all be deleted, we moved them to https://github.com/lexibank/panobodyparts (Just had todoublecheck).


fix: don't treat zip files as windows symbols

Blocked by https://github.com/BugSplat-Git/webroot/pull/1048
Abandon the bsv1 protocol so that .zip files get treated as Unknown instead of Windows.
Fixes #114

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Rename v8x16.shuffle1 and v8x16.shuffle2_imm to v8x16.swizzle and v8x16.shuffle_imm.

@tlively tells me that the SIMD group has decided to change the names, but they haven't updated the SIMD proposal repo yet in https://github.com/WebAssembly/wabt/pull/1116#issuecomment-512884716 .

Thank you for the patch.

Should be ‘shuffle’, not ‘shuffle_imm’. Sorry for the confusion!

I've sent out a PR with that fix, and the four new LoadSplat instructions in #117.


Fix unhandled exception in set_caster

obj_iter throws python_error on failure, but type casters aren't allowed to throw! If you try to from-Python cast an object of a non-iterable type, Python will abort from the unhandled exception coming from a noexcept function
It looks like the intention here is to handle failure manually (a NULL return from the CPython call), so I did just that

Thanks!


Update monetization doc postgre script

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


vscode extension: support lit-element

Clear and concise description of the problem
I am using a framework about Lit , but i found there is any sinppets in vscode when i use unocss.
and i  found it's normal in tailwindCSS when i use vscode
Suggested solution
vscode extension will be supported Lit
Alternative
No response
Additional context
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the README.md of using the package.
[X] Already used the Interactive Docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Can you give me more info about your working environment? Such as, your file extension, VS Code extensions etc... If you can link an example project that would be nice.

i am using the template about Lit+Vite+Typescript all the time .
i used the tailwindCSS before, it was useful for me to show css snippets in Vscode.
late when i found unocss is better then tailwindCSS ,i turned twcss into unocss , but  there is any snippets in vscode when i used unocss and vscode extension--unocss.
there is a simple example in here.
https://stackblitz.com/edit/vitejs-vite-wcwrjd?file=src/my-element.js

Create a uno.config.js file in your root folder, then it should work.
https://github.com/unocss/unocss/blob/main/examples/astro/uno.config.ts

i created a  uno.config.js file , the Vscode extension also doesn't show any sinppets ..
uno.config.js
import { defineConfig } from '@unocss/vite'
import presetUno from '@unocss/preset-uno'
import transformerDirectives from '@unocss/transformer-directives'
import presetIcons from '@unocss/preset-icons'
const config = defineConfig({
  shortcuts: [
    { 'i-logo': 'i-logos-astro w-6em h-6em transform transition-800' }
  ],
  transformers: [transformerDirectives()],
  presets: [
    presetUno(),
    presetIcons({
      extraProperties: {
        display: 'inline-block',
        'vertical-align': 'middle'
      }
    })
  ]
})
export default defineConfig(config)

It seems we don't scan js files by default. You can fix that by configuring include option:
export default defineConfig({
  include: [/\.(vue|svelte|[jt]sx?|mdx?|html)($|\?)/],
  presets: [
    presetUno()
  ]
})


Add a script for the person who wants to run the sample locally

In /Users/huangzheng/web/mpflutter/packages/mpflutter_sample/
flutter run lib/main.dart
It just shows a white screen, which makes me confusing.

[ ] I think something is needed as follow.
'/Users/huangzheng/web/mpflutter/packages/mpflutter_sample/pre_install.sh'

set -e
if [ -n "`which browserify|grep 'not found'`" ] || [ -n "`which tsc|grep 'not found'`" ] || [ -n "`which terser|grep 'not found'`" ]; then
echo "Install dependencies"
npm install -g browserify uglify-js typescript terser
fi

FOLDER_PATH=$(cd "$(dirname "$0")"; pwd)

cd $FOLDER_PATH
cd ../../
# sh build.sh

cd packages/mp_dom_runtime/
npm install
npm run build
cd packages/mp_web_features
npm install
npm run build

[ ] Let someone knows that there is a sample to learn from,
And tell them, how to startup

I'm not sure where to put it, maybe a README, or something where people might see it

Second edit

The build.sh script, in addition to not installing dependencies,
which I found doing the above.
Of course, it would be nice to add judgment to whether the current "Node" is 16 or not.
if [ -z "`node --version|grep v16.`" ]; then
echo "please use node 16"
exit 1;
fi

Thanks for the suggestion, maybe you can create a PR and I'll merge it as soon as possible.


Cant get it to work

Not generating anything.

Yea, same here.
Obsidian has been updated to v1.7.7, and unfortunately, the plugin doesn't work anymore.
I think it's a great idea to integrate AI with Canvas, and I’d love to use it!
Would it be possible to add support for custom LLMs, such as local ones, perhaps by connecting with tools like LM Studio? Additionally, having the option to switch between different OpenAI model versions within the plugin would be fantastic.

Fixed in 0.1.20. I have also added gpt-4o model in the settings.

I’ve just tested the new version, and it works flawlessly! Thank you for the update!


Searching for text (CTRL+Shift+F) is too slow

VSCode Version: Code 1.6.1 (9e4e44c19e393803e2b05fe2323cf4ed7e36880e, 2016-10-13T16:21:53.542Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions: Kasik96.format-php-1.1.2, ullissescastro.theme-bracketsdark-1.0.1

Every time I search for something in my project, the search in files hangs, sometimes longer than 10 minutes. I have tried other editors (Atom and Brackets) on same project and search is not that slow for them.
Steps to Reproduce:

press CTRL+Shift+F and type in some text.
site back and enjoy your coffee break.

I know this has been merged but I wanted to comment on it.
I'm wondering if there are 2 different issues happening - slow file searching (#15384) vs broken file searching (this issue).
I was directed to this issue but mine is a bit different (I think).
But then sometimes I can search and it's instantaneous.
Could @xucaen be seeing what I am - where the search just spins out of control, but then other times it's lightening fast?
I've never been disappointed by the speed of file search, but now and then it just seems to get out of whack.  Could a plugin be getting in the way?

So you're saying that doing the same search on the same workspace, which doesn't have too many huge files, usually search is fast but sometimes hangs? How often would you say it hangs vs works correctly? Are you on Windows too?
Next time you see this, can you open the dev tools (Help > Toggle Developer Tools) and check for errors in the console?

Correct.  All files are < 11k.   And when it hangs, it pours.  It seems to happen in sprints where even killing the process doesn't seem to fix it.  Then other days it just speeds right along, even in the same project I was having an issue with before.  It's quite strange - I wish I could give you more of a pattern, but I'll keep testing it.
For example, it's been giving me fits all day, and just now I tried and it worked perfectly.
As far as frequency....hard to say, but this whole problem just started for me recently - maybe 3-4 weeks ago?
And to answer your other question, I'm on a Mac.  Latest version of everything.  I have not tried uninstalling/reinstalling it, but will soon.
I'll check out the log next time it happens (I'm pretty sure I checked it before but didn't see anything)
Have a good night Rob!

@roblourens Ignore the above!  I just figured it out, and wanted to report back so you or your team doesn't waste time chasing this down.
I realized the issue when I thought about the difference between what had changed in the previous hour - and it was a devops process I had running in a console tab.  It was creating a hidden folder with a huge amount of files in it, and then deleting when it was complete.  It kicked off when any file changed.  That answers why it would come and go.
I appreciate your help and concern - I continue to love the product!

Glad you figured it out! You may want to add that folder to your search.exclude settings.

Already done ;)  Thanks and go get some sleep.
On Mon, Nov 21, 2016 at 10:34 PM, Rob Lourens<EMAIL_ADDRESS>wrote:

Glad you figured it out! You may want to add that folder to your
search.exclude settings.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/14157#issuecomment-262151915,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEgQXiYslO2jTjW2nAYncPegQs2hNL72ks5rAn7JgaJpZM4KdN7P
.


Launch expired sign-in link feature

Context
This is a follow up to PR https://github.com/DFE-Digital/apply-for-postgraduate-teacher-training/pull/1233
We want to make it simpler for users that attempt to use an expired token to log in. Since we know who they are we can automatically send an email with a new token.
The original implementation passes a plain user id to an expired page that renders the users email address. This PR ensures that the plain user id replaced by a token and the email is no longer rendered.
Changes proposed in this pull request

[x] Replace the candidate id param sent to the expired page (CandidateInterface::SignInController#expired) with an encrypted id (u).
[x] Remove the email_address hidden field from the expired page and replace with the encrypted id (u).

Note that these features remain feature flagged and is off on production at this time.
Guidance to review

Are the tests sufficient? - I didn't think there was any need to add anything new because the existing system specs cover all the code I touched.
Does this feature introduce any holes in the authentication process?

Link to Trello card
https://trello.com/c/LkdIGwhl/887-launch-expired-sign-in-link-feature-🏈
Things to check

[x] This code doesn't rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] New environment variables have been added to the Azure config

Catching exceptions from ActiveSupport::MessageEncryptor breaks the (minor) encapsulation of Encryptor and makes the logic a little bit harder to follow than a plain if statement. What would you think about trapping the exception inside Encryptor and returning false if it didn't work?

Catching exceptions from ActiveSupport::MessageEncryptor breaks the (minor) encapsulation in Encryptor and makes the logic a little bit harder to follow than a plain if statement. What would you think about trapping the exception inside Encryptor and returning false if it didn't work?

Wasn't sure about this but having tried it I like it. Good suggestion. Thanks!