async support

SQLAlchemy 1.4 includes async support. Can this be used from Flask-SQLAlchemy?

It is not a huge change to enable this, but it will probably not happen for quite some time. You can already override the engine and session method of the extension to return whatever you want, so it's already possible to get this. The extension itself doesn't need any async code, it only needs to return async engine and session objects.

@davidism Thanks for the reply and yes I've already considered to manually overide the engine.
I just think it will be great to add this feature to flask-sqlalchemy, just my own thought :)


Improve documentation for indent rule

The documentation for indent rule doesn't explain the options for the indent rule -- and additionally, it looks like the sample tslint is out of date with regards to that rule. These should be fixed.

sample.tslint.json was fixed by #545


not able to download PhantomJS exe for windows.

Which version of PhantomJS are you using? Tip: run phantomjs --version.
Latest build 2.1.1-windows
What steps will reproduce the problem?
**1.
Windows
Did you use binary PhantomJS or did you compile it from source?
Trying to download the exe
Please provide any additional information below.
This is the error XML appearing on download page -

AccessDenied
Request has expired
2016-09-12T07:25:14Z
2016-09-12T07:28:04Z
179FC405AF33C85D

KUq1YsjwL3WbpZyIL/VvOX+U8bBDUF/V4CFVfme5kEqOl8tF6fMK2ahNXT8L//PMbz92RKAtNUo=

That's okay. Sometimes Amazon S3 acts weird and disallows downloading it. Just wait a bit.

Currently I can't reach download address :
https://bbuseruploads.s3.amazonaws.com/fd96ed93-2b32-46a7-9d2b-ecbc0988516a/downloads/98d51451-997f-40e3-b9e6-a8e635dcdcb3/phantomjs-2.1.1-windows.zip?Signature=Hfiex540S1LOSBze4ZKVmIoxvWI%3D&Expires=1601626128&AWSAccessKeyId=AKIA6KOSE3BNJRRFUUX6&versionId=null&response-content-disposition=attachment%3B filename%3D"phantomjs-2.1.1-windows.zip"
Page Error
This site can’t be reachedbbuseruploads.s3.amazonaws.com unexpectedly closed the connection.

I am having the same problem with @cansuk page not OK!

I finally downloaded phantomjs.exe 2.1.1 from https://repo1.maven.org/maven2/com/github/klieber/phantomjs/2.1.1/

thank you @furkankatman


Update AudioParam automation rate

https://www.w3.org/TR/webaudio/#dom-audioparam-automationrate
The automation rate, barring some constraints, can be changed by the control thread.

change AudioParam automation_rate to something like an AtomicBool
add set_automation_rate to impl AudioParam
how to deal with constraints? We can panic for now, but where do we encode this logic?
fetch automation_rate in the Renderer and use it accordingly
reconsider signature of AudioParamValues.get(..). It now returns a slice of full render quantum length always. But the spec says it can be length 1 too (for k-rate and for constant pieces) [1]. For type safety we can also make it return an enum.

[1] https://www.w3.org/TR/webaudio/#audioworkletprocess-callback-parameters

Marking it a prerequisite for v1.0, but only because of the possible breaking API change in the last bullet

My two cents:

add set_automation_rate to impl AudioParam
how to deal with constraints? We can panic for now, but where do we encode this logic?

Maybe a new field in AudioParamOptions that would optionally contain a coercion Fn would be quite clean? e.g.:
// node.rs
let param_options = {
   // ...
  constraint: Some(|rate: AutomationRate| -> AutomationRate { ... })
}

// param.rs
set_automation_rate(rate: AutomationRate) {
  if self.constraint.is_some() {
     rate = self.constraint.unwrap()(rate);
  }

  self.automation_rate = rate;
}

if you think it's a good approach, I can try to propose something.

reconsider signature of AudioParamValues.get(..). It now returns a slice of full render quantum length always. But the spec says it can be length 1 too (for k-rate and for constant pieces) [1]. For type safety we can also make it return an enum.

This question is more tricky somehow and unfolds other ones I have the impression.
The spec does not even say that the length is related to a-rate or k-rate (so I'm really not sure about the enum type in this case):

if no automation is scheduled during this render quantum, the array MAY have length 1 with the array element being the constant value of the AudioParam for the render quantum.

At first sight, it kind of sounds to me more like: "Chrome people (or whoever) did that and they don't want to change their implementation, so let's consider it's valid because it doesn't hurt" :)
But, at contrary, it also seems like this is the only way (maybe I missed something here...) to know if a param is a-rate or k-rate (or "constant during this block") in the AudioWorklet::process.
My impression here is that we could also be defensive for v1.0: deliberately avoid the extensibility problem (be it called AudioWorklet or "implement your own node") and mark all that as pub(crate) until we are pretty sure that it's the best possible solution (...I still have the impression that even in the AudioWorklet the audio param guts are not that much exposed)
In any case, let me know what you think I can also have a look on that point, I'm pretty confident the unit tests will allow us to see quite fast if some unexpected problem reveals itself. Beyond the fact we decide or not to keep this len() == 1 solution, I think trying to implement it could actually help to clean the automation code.

Thanks for the comments!
Regarding the constraints, your solution is fine but maybe it is a bit over-engineered. Reading the spec, I think we can get away with a simple option force_k_rate_processing: bool (defaulting to false). Agree?
I'm looking at the current signature of the audio param values:
pub fn get(&self, index: &AudioParamId) -> &[f32]
This is maybe already fine, as it allows for both the len=1 and len=QUANTUM_SIZE cases. The comment needs to be updated though
- For both A & K-rate params, it will provide a slice of length crate::RENDER_QUANTUM_SIZE
+ In the current implementation, the slice will always have a length of crate::RENDER_QUANTUM_SIZE,
+ but one should not rely on this. A slice of length 1 may be returned in the future if all values in the
+ current quantum are identical (e.g. for k-rate processing)

Then we can don't need to make the final decision before release v1.0
In any case, if you want to go ahead and simplify the value calculations for k-rate processing, go ahead!

Regarding the constraints, your solution is fine but maybe it is a bit over-engineered. Reading the spec, I think we can get away with a simple option force_k_rate_processing: bool (defaulting to false). Agree?

Yep, you are right, I didn't check the spec and I was thinking there was more special cases. I'm not completely sure the flag will be enough for panner with HRTF (but my solution neither... :), but HRFT will be a tricky thing anyway.

I'm looking at the current signature of the audio param values: (...)

Yep, that looks like a good tradeoff

In any case, if you want to go ahead and simplify the value calculations for k-rate processing, go ahead!

Yes I think it worth the case to at least try to see what we get there, I'd really like the advance on the Oscillator sub-quantum scheduling first but I will check that after (assigning myself to the issue as it is somehow related to #20)

Regarding the discussion at #98 I'm removing the V1 milestone here


Transfer repo to org

Hey,
i am a core member of telescope and i really like your extension. I have some thoughts and improvements for the code but we can talk about that later.
My question right now do you wanna transfer that repo to the https://github.com/nvim-telescope org? You will obviously have admin permissions :)
Best regards

Hi,
I am glad you like it. This is only my second lua project (and also second neovim plugin), so I would appreciate any suggestions to my code.
I would love to contribute by tranfering it to the org. Hopefully more people can find and use it this way :)

Hi,
I am glad you like it. This is only my second lua project (and also second neovim plugin), so I would appreciate any suggestions to my code.
I would love to contribute by tranfering it to the org. Hopefully more people can find and use it this way :)

Okay i currently try to figure out how to progress.

I could create a repo: nvim-telescope/telescope-bibtex.nvim
give you rights
you create do a new git remote and push your current tree to that remote

Okay i currently try to figure out how to progress.

I could create a repo: nvim-telescope/telescope-bibtex.nvim
give you rights
you create do a new git remote and push your current tree to that remote

That should work.

That should work.

Sounds good to me :)
Just open a PR and we can continue the discussion :)
I am closing this issue for now

Sounds good to me :)
Just open a PR and we can continue the discussion :)
I am closing this issue for now


Numba 0.55.0rc1 Checklist

Numba 0.55.0rc1

[x] Merge to master.

[x] https://github.com/numba/numba/pull/7082

[x] Merge change log changes.

[x] https://github.com/numba/numba/issues/7644

[x] Create 0.55 release branch. https://github.com/numba/numba/tree/release0.55
[x] Pin llvmlite to >=0.38.0rc1,<0.39.
[x] Pin tbb https://github.com/numba/numba/issues/7620
[x] Pin Numpy to <=1.21
[x] Annotated tag 0.55.0rc1 on release branch.
[x] Build and upload conda packages on buildfarm (check "upload").
[x] Build wheels ($PYTHON_VERSIONS) on the buildfarm (check "upload").
[x] Upload wheels and sdist to PyPI (upload from ci_artifacts).
[x] Verify packages uploaded to Anaconda Cloud and move to numba/label/main.
[x] Verify wheels for all platforms arrived on PyPi.
[x] Upload PyPi source distribution (sdist)
[x] Initialize and verify ReadTheDocs build.
[x] Clean up ci_artifacts.
[x] Send RC announcement email / post announcement to discourse group. https://numba.discourse.group/t/numba-0-55-0-rc1/1075
[x] Post link to Twitter. https://twitter.com/numba_jit/status/1471785352159326209

Post Release:

[x] Tag 0.56dev0 to start new development cycle on master.
[ ] Update llvmlite dependency spec to match next version via PR to master.
[ ] Update release checklist template with any additional bullet points that
may have arisen during the release.
[ ] Close milestone (and then close this release issue).

It seems no wheel landed (or remained) on pypi for numba-0.55.0rc1-cp310-cp310-win_amd64.whl.
Is it normal ?

It seems no wheel landed (or remained) on pypi for numba-0.55.0rc1-cp310-cp310-win_amd64.whl. Is it normal ?

This is correct, we were unable to build the wheels for that platform in December 2021. Hopefully this will be remedied in the upcoming release candidate 2.

Hi - Do you have the timeline for the release? I am updating NumPy >= 1.21, following https://github.com/advisories/GHSA-6p56-wp2h-9hxr and  currently restricted by Numba restriction.

Hi - Do you have the timeline for the release? I am updating NumPy >= 1.21, following GHSA-6p56-wp2h-9hxr and currently restricted by Numba restriction.

Thank you for asking about this. There is no concrete timeline, but since we are in the middle of a release candidate phase the final should become available in a couple -- maybe two to five -- of weeks or something like that.

Hi - Do you have the timeline for the release? I am updating NumPy >= 1.21, following GHSA-6p56-wp2h-9hxr and currently restricted by Numba restriction.

Thank you for asking about this. There is no concrete timeline, but since we are in the middle of a release candidate phase the final should become available in a couple -- maybe two to five -- of weeks or something like that.

Feel free to look at https://github.com/numba/numba/milestone/62 as a rough indicator of progress.

@sklam FYI: llvmlite v0.39.0dev0 was tagged this morning and build artifacts are available in numba/label/dev on anaconda.org: https://anaconda.org/numba/llvmlite/files?version=0.39.0dev0

@sklam FYI: llvmlite v0.39.0dev0 was tagged this morning and build artifacts are available in numba/label/dev on anaconda.org: https://anaconda.org/numba/llvmlite/files?version=0.39.0dev0

This means, we can proceed with: Update llvmlite dependency spec to match next version via PR to master.

release checklist update is now here: https://github.com/numba/numba/pull/7732

With 0.55.0 out now, https://numba.discourse.group/t/numba-0-55-0-and-llvmlite-0-38-0-final-release/1136 closing this!


Channel: linebreak for video credits

Can we insert an extra linebreak above the 'Video Credits' module for responsive layout? At the moment there's no break for smaller devices—see the image below.
URL: https://stories.mplus.org.hk/en/channel/ho-fan-on-the-decisive-moment
Browser: Chrome
Devices: all

Implemented in d96b8f7c0ecb56674c80cc16145d7dac5f8e8910.


esbuild: 0.14.27 -> 0.14.28

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/esbuild/versions.
meta.description for esbuild is: "An extremely fast JavaScript bundler"
meta.homepage for esbuild is: "https://esbuild.github.io"
meta.changelog for esbuild is: ""
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/5g216jyk5lmidhg78lcssmxcjnx6c4hm-esbuild-0.14.28/bin/esbuild had a zero exit code or showed the expected version
0 of 1 passed binary check by having a zero exit code.
0 of 1 passed binary check by having the new version present in output.
found 0.14.28 with grep in /nix/store/5g216jyk5lmidhg78lcssmxcjnx6c4hm-esbuild-0.14.28
found 0.14.28 in filename of file in /nix/store/5g216jyk5lmidhg78lcssmxcjnx6c4hm-esbuild-0.14.28

Rebuild report (if merged into master) (click to expand)

15 total rebuild path(s)

10 package rebuild(s)

10 x86_64-linux rebuild(s)
5 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
code-server
deltachat-desktop
esbuild
libsForQt5.bismuth
libsForQt512.bismuth
libsForQt514.bismuth
libsForQt515.bismuth
openvscode-server
plasma5Packages.bismuth
vscode-extensions.matklad.rust-analyzer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5g216jyk5lmidhg78lcssmxcjnx6c4hm-esbuild-0.14.28 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A esbuild https://github.com/r-ryantm/nixpkgs/archive/cb479c5a92d2234668a2d9cdf67011df161ac61b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5g216jyk5lmidhg78lcssmxcjnx6c4hm-esbuild-0.14.28
ls -la /nix/store/5g216jyk5lmidhg78lcssmxcjnx6c4hm-esbuild-0.14.28/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages marked as broken and skipped:

libsForQt512.bismuth
libsForQt514.bismuth

6 packages built:

code-server
deltachat-desktop
esbuild
libsForQt5.bismuth
openvscode-server
vscode-extensions.matklad.rust-analyzer

Maintainer pings
cc @Lucus16 @kalbasit for testing.

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

3 packages built:

deltachat-desktop
esbuild
vscode-extensions.matklad.rust-analyzer


Document Steps to Get Container Running

When you do this, we'll probably add this to the readme? Maybe at the bottom where we go deeper into the project.

Or maybe create a file like BUILDING.md or DEPLOYING.md that can go into more detail.


Dependencies for this library?

Hello,
are there any dependencies of this library or the examples? If so, what are they?

No, there are no any dependencies for promise-lua. The mentioned function setTimeout is an example of async methods, which can be implemented by yourself. For quick testing, you may also take a look at luvit's setTimeout.


offline zipformer2 int8 issue

When i try the int8 version of the offline onnx zipformer2, get this error:
what():  Failed to load model with error: /onnxruntime_src/onnxruntime/core/graph/model_load_utils.h:46 void onnxruntime::model_load_utils::ValidateOpsetForDomain(const std::unordered_map<std::basic_string, int>&, const onnxruntime::logging::Logger&, bool, const string&, int) ONNX Runtime only guarantees support for models stamped with official released onnx opset versions. Opset 19 is under development and suppor
t for this is limited. The operator schemas and or other functionality may change before next ONNX release and in this case ONNX Runtime will not guarantee backward compatibility. Current official support for domain com.ms.internal.nhwc is till opset 18.
the plain onnx version works fine.
Both the export and the attempted inference is done on the same installation.

Have you fixed it?
If not, please downgrade your onnxruntime python package from 1.15.0 to 1.14.0 or below and re-export your model.
Even though you didn't mention the version of your onnxruntime python package, it must be 1.15.0 or above, otherwise you wouldn't get such an error.
Another fix is to upgrade the onnxruntime from 1.14.0 to 1.15.0 or above in sherpa-onnx.

Thank you!
I confirm that pip3 install onnxruntime==1.14.0 before export resolves the issue.

Closing as it has been fixed.


Minor changelog regression

PR #183 resolves the original changelog issue when a web vistor navigates to https://<IP_ADDRESS>:8000/article/all_content_dump/ however I just realized that PR #183 breaks this page: https://<IP_ADDRESS>:8000/article/content_changelog/. See here:
This needs to be corrected

The bulleted list under "Change log" heading needs to parse like it does here on all_content_dump:

Resolved in #191. Thanks, Abu!


Multiple level admin layer display

This fixes issue #582
How to test the feature:

[ ] Choose a admin layer
[ ] Find a district with no admin level 2 data (with admin level 1 data)
[ ] Click this district on the map
[ ] Witness the Admin Level in the tooltip (matches that of admin level 1)

Screenshot/video of feature:

Hi @sifelix. Great work, we've just got a few things to address:

Change the button to just say 'download'
It looks like the button style isn't consistent with other functions in the legend area. Exposure analysis is an example
A user shouldn't see the download option for all WMS layers, only those that are accessible via the STAC API.

The screenshot below shows a WMS layer that can't be downloaded via STAC. The button shouldn't appear in this scenario. The button style also isn't consistent with 'exposure analysis'

This is looking good, thanks @ajanim! For anyone else testing, a couple of countries where the fallback data comes into play are Mauritania and Cote d'Ivoire. Over to @sifelix @ericboucher for technical review, but this works well from my side.


Sanity Check with Reinforcement benchmark

System has 10 cores, 20 HT with a single RTX Titan.
The reinforcement benchmark was left at the default termination accuracy of 0.4. On the reference quality progression chart 34% is achieved around the 60hr mark.  I'm currently about 48hrs in and if I'm reading the logs correctly, I'm only at 3%. Check out the output below:
:::MLPv0.5.0 minigo<PHONE_NUMBER>.120585442 (loop_train_eval.py:261) eval_accuracy: {"value": 0.03314917127071823, "epoch": 57}
DEBUG:mlperf_compliance::::MLPv0.5.0 minigo<PHONE_NUMBER>.120585442 (loop_train_eval.py:261) eval_accuracy: {"value": 0.03314917127071823, "epoch": 57}
Thoughts? Am I missing something?

I also encountered this problem and ran for 90 hours without getting results :(

This is obsolete. With v0.6, the benchmark reliably converges


CSRF protection

In the process of creating a form using Flask-WTForms for a FlexMeasures plugin, I encountered the following recommendation to protect an application against CSRF attacks:
https://flask-wtf.readthedocs.io/en/0.15.x/csrf/
In summary, it consist of adding a CSRF token into the form and let the Flask-WTForms validate the data by registering the CSRFProtect Flask extension.
The CSRF protection can be disabled at the endpoint or blueprint level.
As I'm not a cybersecurity expert, I asked ChatGPT to provide me an example on how an attacker would exploit this vulnerability:
<!DOCTYPE html>

    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>CSRF Attack Simulation</title>

CSRF Attack Simulation

<form action="http://victim.com/create_user" method="POST" id="csrf-form">
    <input type="hidden" name="username" value="attacker">
    <input type="hidden" name="password" value="maliciouspassword">
    <input type="submit" value="Submit Form">
</form>

See also #42


Add option to disable blurred artwork background on the Lyrics Plus page

When using the Lyrics plus custom app there's an option called "colorful background" which enable/disable a background based on the album cover's color. However when using the theme there's no way to disable the option.
Option behavior without the theme :

Disabled

Enabled

Option behavior with the theme :

Disabled

Enabled

It could be related to the var(--spice-main) parameter maybe ?

It is not a bug, the background you see is a theme custom background, not a Lyrics Plus ones. Lyrics Plus background is hidden, so its settings have no effect

For now I can suggest a workaround for you:

Open Marketplace
Go to snippets
Press "Add CSS"
Paste .lyrics-lyricsContainer-LyricsBackground { visibility: visible !important; } to the Custom CSS field
Save snippet

Okay thanks, it works fine.

@Yashirow now you need .lyrics-lyricsContainer-LyricsBackground { display: unset !important; }

@SunsetTechuila Is there a new workaround for this?

@InsrtRandomUserHere nothing changed
if it is not working for you, try this :root .lyrics-lyricsContainer-LyricsBackground { display: unset !important; }
sorry for the late response

if it is not working for you, try this :root .lyrics-lyricsContainer-LyricsBackground { display: unset !important; }

Yup, thanks that worked. Though the only problem I have now is that the scrollbar appears on the side

@InsrtRandomUserHere im closing the issue! open an issue anytime if anything goes wrong! until we meet again, keep blooming ^_~


API response not recognised by the plugin

Describe The Problem:
The log displays the below and hence it's a bit hard to debug further even from the user perspective:
To Reproduce:

Set any section to Away

Note that the section is not set as Away, and the log displays only the below.
Logs:
5/27/2023, 3:52:28 PMJablotron BridgeJablotronSetting section state: section_2 => 1
5/27/2023, 3:52:28 PMJablotron BridgeJablotronSwitching section section_2 (using section_2) to new state: set
5/27/2023, 3:52:30 PMJablotron BridgeJablotron[object Object]
5/27/2023, 3:52:30 PMJablotron BridgeJablotronError: bypass_dialog_default
5/27/2023, 3:52:30 PMJablotron BridgeERROR[Jablotron Bridge C250@Upstairs@Upstairs@Security System Target State] SET handler returned write response value, though the characteristic doesn't support write response

Environment:

Hoobs Version: 4.3.0
Homebridge Version: 1.6.0
Node Version: 16.20.0
Homebridge-jablotron plugin version: 2.6.0
Operating System and OS Version: Hoobs

Hello, thanks for reporting.
Are you able to control your Jablotron when using the same user in the app?

Thanks!
Seems you are right, it works now for a section that is OK. Though, this is the log it produces anyway:
5/29/2023, 10:38:57 PMJablotron BridgeJablotronSetting section state: section_3 => 1
5/29/2023, 10:38:57 PMJablotron BridgeJablotronSwitching section section_3 (using section_3) to new state: set
5/29/2023, 10:38:57 PMJablotron BridgeJablotron[object Object]
5/29/2023, 10:38:57 PMJablotron BridgeJablotronSwitching section section_3 (using section_3) to new state: set
5/29/2023, 10:39:01 PMJablotron BridgeERROR[Jablotron Bridge C250@Garage@Garage@Security System Target State] SET handler returned write response value, though the characteristic doesn't support write response

However, this time, the section is armed.


[Docs] - Clarify multi collector

None of the docs seem to mention (at least, where I could find it), that for the MultiSyncCollector (and async) you need to run your code using:
if __name__ == "__main__":
    training_loop()

otherwise, you'll get this error:
RuntimeError:
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.

        To fix this issue, refer to the "Safe importing of main module"
        section in https://docs.python.org/3/library/multiprocessing.html

Fair point! We should mention that

I'll prep a PR - hopefully today, if not early next week :-).

Closed by #2126


Create README.md

close #1

Thanks, but I prefer either be without a README (to serve as reminder that it needs to be done), or do it more or less right. I've pushed a somewhat detailed README now.


Making a file available while in transit

Just a quick question. When is a file being uploaded with this module going to be served for incoming requests? Can it be made available before the upload is completed for clients asking for chunked tranfers?
I understand that the behaviour of the DAV ngix module is to make it available only at the end when the size is known, but being able to do that would be great for streaming purposes.

Sorry, I reread the description of the plugin and I realized its purpose is to add missing verbs, and it's not a different implementation.


Not working if the language is Russian

I am using this package for slug. But this is working well for English. But not working well for Russian, Korean, Chinese, Japanese and etc.
Do you have any suggestion for this?
Regards.

You would need to modify the underlying Cocur\Slugify object to handle this.  Doing this is now supported in version 4.0.0 via the customizeSlugEngine method.


Download link edit

Updating the download links to go directly to the chrome store as per requirements for ad campaign

just missing commit signature


[Service Bus] Session Lock Renewal UnpartitionedQueueWithSessions: Streaming Receiver: lock will not expire until configured time failing in nightly runs

Service Bus nightly test runs are failing with:

Error message:
Error Thrown flag value mismatch: expected true to equal false
Stack trace:
AssertionError: Error Thrown flag value mismatch: expected true to equal false
at Object.should.equal (/Users/runner/work/1/s/common/temp/node_modules/.pnpm/chai@4.3.7/node_modules/chai/lib/chai/interface/should.js:98:35)
at testAutoLockRenewalConfigBehavior (/Users/runner/work/1/s/sdk/servicebus/service-bus/test/public/renewLockSessions.spec.ts:355:12)
at Context.<anonymous> (/Users/runner/work/1/s/sdk/servicebus/service-bus/test/public/renewLockSessions.spec.ts:119:7)
+ expected - actual
-true
+false

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=2699657&view=results

not seeing this recently.


How to use package if conda-forge must be accessed through a proxy channel?

Not sure what the right terminology here is, but the problem setup is like this:
I have an environment where access to conda-forge must happen through some jfrog artifactory. This is supposed to work by using channel_alias in the .condarc file.
The problem however is that the channel name itself is also changed to something like conda-forge-proxy. For example, packages normally available in https://conda.anaconda.org/conda-forge are available in https://artifactory.url/conda-forge-proxy.
From what I can tell there is no way to make the translation "conda-forge" => "conda-forge-proxy" in the .condarc as micromamba always adds whatever is after the -c at the end of the URL, resulting in micromamba trying to access either https://artifactory.url/conda-forge-proxy/conda-forge  or https://artifactory.url/conda-forge, neither of which is valid.
Is there anyway to change the channels of a dependencies?
From reading the source code of CondaPkg, it seems that conda-forge is hardcoded as the default channel there. Would it be better to just leave it empty and use whatever defaults the user might have in their .condarc?
Fwiw, I'm not very experienced with neither conda nor artifactory so there might be aspects of it I don't know, but the lack of possibility to remap channel names in conda in combination with artifactory allowing this seems a bit baffling to me.

I'm also not an expert in this aspect of Conda.
From what I can tell, the only problem is with the channel name (conda-forge-proxy instead of conda-forge) and you have the base proxy URL working ok via Conda settings?
From reading about Conda config it doesn't look like there is a setting to rename channels. I'd be happy to add such a setting to CondaPkg - or better still you could make a PR for this feature.

User preferences in CondaPkg are set using env vars or Julia preferences (https://github.com/JuliaPy/CondaPkg.jl/?tab=readme-ov-file#preferences).
But yeah, ideally you'd just have artifactory set up to use the correct channel names.

I managed to get an admin to sit and cross check logs with me and they did something on their side (don't know what exactly) that made it work for me.
Sorry for the noise. Didn't really know where to start with this problem.


Propose the usual way of styling buttons

I thought it'd be useful if we show the reader how we can create both normal and link buttons without much hassle.

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Looks good @JeffreyCamphens, thanks for contributing to freeCodeCamp!


[New Port Request] wxcharts

Library name:
wxcharts
Library description:
A library to create charts in wxWidgets applications.
Source repository URL:
https://github.com/wxIshiko/wxCharts
Project homepage (if different from the source repository):
https://www.wxishiko.com/wxCharts/
Anything else that is useful to know when adding (such as optional features the library may have that should be included):
Is there any good library for charts in vcpkg now?
BTW, there is a port called wxchartdir, but it is a wrapper of a commercial one.

If you wish to add this port in the future, you can reopen this issue, but we're closing it for now.


Fixes race condition of TrackJS

This occurred when TrackJS took longer to load than what our application took to render, thus, not allowing TrackJS to monkey-patch the JS methods it wanted and causing an exception when switching pages.

run integration tests

retest this please

run integration tests

run integration tests

run integration tests

I see failures when running the test locally...
Test Logs
  1) Node Health Tab [0fa] Navigate to tab [0fb] navigates to health tab [0fc]:
     CypressError: Timed out retrying: Expected to find element: '.menu-tabbed-item', but never found it.
      at Object.cypressErr (http://localhost:4200/__cypress/static/js/cypress.js:5628:15)
      at Object.throwErr (http://localhost:4200/__cypress/static/js/cypress.js:5592:22)
      at Object.throwErrByPath (http://localhost:4200/__cypress/static/js/cypress.js:5620:21)
      at $Cy._retry (http://localhost:4200/__cypress/static/js/cypress.js:6554:26)
      at http://localhost:4200/__cypress/static/js/cypress.js:8689:28
      at tryCatcher (http://localhost:4200/__cypress/static/js/vendor.js:42833:31)
      at Promise._settlePromiseFromHandler (http://localhost:4200/__cypress/static/js/vendor.js:40968:31)
      at Promise._settlePromiseAt (http://localhost:4200/__cypress/static/js/vendor.js:41044:18)
      at Promise._settlePromises (http://localhost:4200/__cypress/static/js/vendor.js:41160:14)
      at Async._drainQueue (http://localhost:4200/__cypress/static/js/vendor.js:38527:16)
      at Async._drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38537:10)
      at MutationObserver.Async.drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38365:14)

  2) Node Health Tab [0fa] Health Tab [0fd] "before each" hook for "filters by health [0fe]":
     CypressError: Timed out retrying: Expected to find element: '.menu-tabbed-item', but never found it.

Because this error occured during a 'before each' hook we are skipping the remaining tests in the current suite: 'Health Tab [0fd]'
      at Object.cypressErr (http://localhost:4200/__cypress/static/js/cypress.js:5628:15)
      at Object.throwErr (http://localhost:4200/__cypress/static/js/cypress.js:5592:22)
      at Object.throwErrByPath (http://localhost:4200/__cypress/static/js/cypress.js:5620:21)
      at $Cy._retry (http://localhost:4200/__cypress/static/js/cypress.js:6554:26)
      at http://localhost:4200/__cypress/static/js/cypress.js:8689:28
      at tryCatcher (http://localhost:4200/__cypress/static/js/vendor.js:42833:31)
      at Promise._settlePromiseFromHandler (http://localhost:4200/__cypress/static/js/vendor.js:40968:31)
      at Promise._settlePromiseAt (http://localhost:4200/__cypress/static/js/vendor.js:41044:18)
      at Promise._settlePromises (http://localhost:4200/__cypress/static/js/vendor.js:41160:14)
      at Async._drainQueue (http://localhost:4200/__cypress/static/js/vendor.js:38527:16)
      at Async._drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38537:10)
      at MutationObserver.Async.drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38365:14)

  3) Nodes Detail Page Navigate to node detail page navigates to node detail page:
     CypressError: Timed out retrying: expected '<div.page-header>' to contain 'dcos-01'
      at Object.cypressErr (http://localhost:4200/__cypress/static/js/cypress.js:5628:15)
      at Object.throwErr (http://localhost:4200/__cypress/static/js/cypress.js:5592:22)
      at Object.throwErrByPath (http://localhost:4200/__cypress/static/js/cypress.js:5620:21)
      at $Cy._retry (http://localhost:4200/__cypress/static/js/cypress.js:6554:26)
      at http://localhost:4200/__cypress/static/js/cypress.js:8689:28
      at tryCatcher (http://localhost:4200/__cypress/static/js/vendor.js:42833:31)
      at Promise._settlePromiseFromHandler (http://localhost:4200/__cypress/static/js/vendor.js:40968:31)
      at Promise._settlePromiseAt (http://localhost:4200/__cypress/static/js/vendor.js:41044:18)
      at Promise._settlePromises (http://localhost:4200/__cypress/static/js/vendor.js:41160:14)
      at Async._drainQueue (http://localhost:4200/__cypress/static/js/vendor.js:38527:16)
      at Async._drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38537:10)
      at MutationObserver.Async.drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38365:14)

  4) Nodes Detail Page Navigate to node detail page shows error in node detail page when node is invalid [10a]:
     CypressError: Timed out retrying: Expected to find element: '.page-body-content h3', but never found it.
      at Object.cypressErr (http://localhost:4200/__cypress/static/js/cypress.js:5628:15)
      at Object.throwErr (http://localhost:4200/__cypress/static/js/cypress.js:5592:22)
      at Object.throwErrByPath (http://localhost:4200/__cypress/static/js/cypress.js:5620:21)
      at $Cy._retry (http://localhost:4200/__cypress/static/js/cypress.js:6554:26)
      at http://localhost:4200/__cypress/static/js/cypress.js:8689:28
      at tryCatcher (http://localhost:4200/__cypress/static/js/vendor.js:42833:31)
      at Promise._settlePromiseFromHandler (http://localhost:4200/__cypress/static/js/vendor.js:40968:31)
      at Promise._settlePromiseAt (http://localhost:4200/__cypress/static/js/vendor.js:41044:18)
      at Promise._settlePromises (http://localhost:4200/__cypress/static/js/vendor.js:41160:14)
      at Async._drainQueue (http://localhost:4200/__cypress/static/js/vendor.js:38527:16)
      at Async._drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38537:10)
      at MutationObserver.Async.drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38365:14)

  5) Service Versions Configuration Tab "before each" hook for "opens the current service version on default":
     CypressError: Timed out retrying: Expected to find element: '.services-version-select button', but never found it.

Because this error occured during a 'before each' hook we are skipping the remaining tests in the current suite: 'Configuration Tab'
      at Object.cypressErr (http://localhost:4200/__cypress/static/js/cypress.js:5628:15)
      at Object.throwErr (http://localhost:4200/__cypress/static/js/cypress.js:5592:22)
      at Object.throwErrByPath (http://localhost:4200/__cypress/static/js/cypress.js:5620:21)
      at $Cy._retry (http://localhost:4200/__cypress/static/js/cypress.js:6554:26)
      at http://localhost:4200/__cypress/static/js/cypress.js:8689:28
      at tryCatcher (http://localhost:4200/__cypress/static/js/vendor.js:42833:31)
      at Promise._settlePromiseFromHandler (http://localhost:4200/__cypress/static/js/vendor.js:40968:31)
      at Promise._settlePromiseAt (http://localhost:4200/__cypress/static/js/vendor.js:41044:18)
      at Promise._settlePromises (http://localhost:4200/__cypress/static/js/vendor.js:41160:14)
      at Async._drainQueue (http://localhost:4200/__cypress/static/js/vendor.js:38527:16)
      at Async._drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38537:10)
      at MutationObserver.Async.drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38365:14)

  6) Add Repository Form Modal should display error if both fields aren't filled out:
     CypressError: Timed out retrying: Expected to find element: '.modal .form-control-feedback', but never found it.
      at Object.cypressErr (http://localhost:4200/__cypress/static/js/cypress.js:5628:15)
      at Object.throwErr (http://localhost:4200/__cypress/static/js/cypress.js:5592:22)
      at Object.throwErrByPath (http://localhost:4200/__cypress/static/js/cypress.js:5620:21)
      at $Cy._retry (http://localhost:4200/__cypress/static/js/cypress.js:6554:26)
      at http://localhost:4200/__cypress/static/js/cypress.js:8689:28
      at tryCatcher (http://localhost:4200/__cypress/static/js/vendor.js:42833:31)
      at Promise._settlePromiseFromHandler (http://localhost:4200/__cypress/static/js/vendor.js:40968:31)
      at Promise._settlePromiseAt (http://localhost:4200/__cypress/static/js/vendor.js:41044:18)
      at Promise._settlePromises (http://localhost:4200/__cypress/static/js/vendor.js:41160:14)
      at Async._drainQueue (http://localhost:4200/__cypress/static/js/vendor.js:38527:16)
      at Async._drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38537:10)
      at MutationObserver.Async.drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38365:14)

  7) Add Repository Form Modal should display error if not a valid url:
     CypressError: Timed out retrying: Expected to find element: '.modal .form-control-feedback', but never found it.
      at Object.cypressErr (http://localhost:4200/__cypress/static/js/cypress.js:5628:15)
      at Object.throwErr (http://localhost:4200/__cypress/static/js/cypress.js:5592:22)
      at Object.throwErrByPath (http://localhost:4200/__cypress/static/js/cypress.js:5620:21)
      at $Cy._retry (http://localhost:4200/__cypress/static/js/cypress.js:6554:26)
      at http://localhost:4200/__cypress/static/js/cypress.js:8689:28
      at tryCatcher (http://localhost:4200/__cypress/static/js/vendor.js:42833:31)
      at Promise._settlePromiseFromHandler (http://localhost:4200/__cypress/static/js/vendor.js:40968:31)
      at Promise._settlePromiseAt (http://localhost:4200/__cypress/static/js/vendor.js:41044:18)
      at Promise._settlePromises (http://localhost:4200/__cypress/static/js/vendor.js:41160:14)
      at Async._drainQueue (http://localhost:4200/__cypress/static/js/vendor.js:38527:16)
      at Async._drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38537:10)
      at MutationObserver.Async.drainQueues (http://localhost:4200/__cypress/static/js/vendor.js:38365:14)

@orlandohohmeier how di you run the tests locally? And how did you start the application server? `npm run testing?

@rcorral I started the test environment using npm run testing and ran the test using cypress run.

Some tests that were passing locally for me yesterday have started failing today... 😠

this probably means we're probably not chaining thing correctly in cypress and it's a race condition. I'll investigate and pass it onto the team for best practice.

run unit tests

@orlandohohmeier I fixed the issue that caused the failed tests. It was because I increased the request interval. So I've removed that now.

💥


Separate out output directories for multiple playwright runs

Starting with https://github.com/Azure/communication-ui-library/pull/2072, browser tests involve multiple invocations of playwright. Before this PR, the multiple invocations end up overwriting the output directory from previous invocations.

Use a new output directory for each invocation. This PR simply adds a sub-directory with the current Unix timestamp for each invocation.
Update workflow to upload all playwright test stats from all the invocations.
Add a new flag runBrowserTests.mjs -x to skip further invocations on failure (builds atop playwright -x)

Fixes

Missing snapshots from some test failures in CI.
Missing per-test metrics for analysis.

Does not affect the results of CI runs.

https://github.com/prprabhu-ms/acr-e2e-analysis/commit/dd0b0e0b0e3265dab170e8eef0051c021deef3b8 updates the analysis pipeline and verifies that the data from CI runs for this PR is correctly processed.


remove externalNodes and fix uploading resource on Cluster lvl

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

/retest


Update actions/checkout: v2 -> v3

Coverage: 97.059%. Remained the same when pulling 4d3e43658ac3bf670c1e21dd8abbefa8c278ce47 on update_actions/checkout into f15b4edd230ae398c7a15d4b68731362a3e64af3 on 1.2.


InfluxDB v2: alert checks not working

I configured a simple alert check with a threshold to set a critical status at specific points and schedules it for every 10 seconds. After running it there are no data logged to the alert history. Does somebody else encountered this issue or has an idea how to solve it?
My InfluxDB version is 2.0.4

+1

+1


Reference error when referencing parameter array

I'm trying to reference an array of parameter objects and I get a reference error when I run it through the linter.
Detailed description
In my main openapi.yaml file, I have a path that is defined as follows:
  /datasets/{datasets}/parts:
    get:
      tags:
      - Datasets
      operationId: datasets.parts
      summary: Get Dataset Parts
      description: Get parts for a given group of datasets.
      parameters:
        $ref: parameters/parts.yaml
      responses:
        '200':
          description: Parts Response
          content:
            application/json:
              schema:
                $ref: schemas/parts.index.json
        '401':
          $ref: '#/components/responses/UnauthorizedError'

parameters/parts.yaml looks like the following:
- in: path
  name: datasets
  description: One or more dataset numbers, separated by commas.
  required: true
  schema:
    type: array
    items:
      type: integer
  explode: true
- in: query
  name: filters
  description: One or more query objects.
  required: false
  schema:
    type: array
    items:
      $ref: ../schemas/filter.json
- in: query
  name: partnumber
  required: false
  description: One or more comma separated part numbers. API will return any part numbers that match the strings.
  examples:
    single:
      value: ABC123
    multiple:
      value: ABC123,ABC1234,DEF456
  schema:
    type: array
    items:
      type: string
- in: query
  name: partnumber_vendor
  required: false
  description: One or more comma separated part numbers. API will return any part numbers that match the strings.
  examples:
    single:
      value: ABC123
    multiple:
      value: ABC123,ABC1234,DEF456
  schema:
    type: array
    items:
      type: string

When I run the linter, I get the following error:
Expected object or boolean as schema, got array
ReferenceError: err is not defined
    at /media/jloosli/storage/projects/partners/node_modules/oas-resolver/index.js:215:26
ReferenceError: err is not defined
    at /media/jloosli/storage/projects/partners/node_modules/oas-resolver/index.js:215:26
err is not defined

If I keep that same definition inline, then I don't have any errors.
Context
When displaying my API with Redoc, it handles the parameters correctly. I can keep this inline, but I'd like to separate out components a little more since my openapi.yaml file is getting quite large. It seems like this would be valid, but I'm not 100% sure.
Your environment

Ubuntu 18.04
Node 10.9.0

API isn't live yet, so no external links right now.

I don't think that's a valid usage of $ref. I know it seems like it should work anywhere, but it's only available in certain locations. https://swagger.io/docs/specification/using-ref/#considerations


Adopt a Code of Conduct

As part of becoming a NumFocus project (#1) we'd need to adopt a Code of Conduct (CoC). A few examples:

Contributor Covenant (used by many projects)
Python Community CoC
Jupyter's CoC
Django's CoC

I would suggest something lightweight such as the Python (really PSF) CoC.

One way in which these codes differ is in the extent to which they enumerate specific classes of acceptable and unacceptable behavior.  As I see it the benefit to non-enumeration is that it has longevity and also doesn't allow for people to say "but my behavior wasn't specifically listed".  As I see it the benefit to enumeration is that it welcomes people who might feel specifically at-risk for a particular type of bad behavior, and it also makes it easier for community maintainers to point to the code in the case of an infraction.  "You clearly said X, which is clearly listed on our code" rather than "You said something that was offensive as I interpret it".
Given the short lifespan of software projects (Python excluded) I'm somewhat inclined towards more specific enumeration of common forms of harrassment today.  I don't expect this list to change significantly over the lifetime of the project, which I anticipate as lasting no more than 10 years.
I like the PSF CoC, but I like the explicit style of the Contributor Covenant a bit more.  This is mostly because if someone makes crude statements like a "yo momma's so fat that ..." joke or "that's gay" then I can very clearly point to a line in the CoC and have a very short discussion, rather than have to go back and forth about what should or should not be considered offensive within this community.
To be clear, I apologize using the statements above, both of which I consider to be offensive and not acceptable within this community.  It's just very useful to have a couple concrete examples when discussing this topic.

+1 for Contributor Covenant . I find it a good compromise between lightweight and explicit enough.

I also vote for the Contributor Covenant.
How should we as a community go about making a decision here? Do we want all org members to weigh in in a vote, or should we just move forward once a few people agree unless someone explicitly disagrees?

How should we as a community go about making a decision here?

I recommend that we wait for a while so that people can express their thoughts.  My hope is that we eventually come to concensus in this case, but only after having discussed it for a while.  Having this discussion within the community may be as important as adopting the document itself.
Other projects presumably saw the Contributor Covenant before and decided to modify it based on their experience.  I encourage people who haven't yet spoken up to read some of the other documents, compare them a bit, and speak up if anything strikes them as interesting.

Yes, I agree that explicit lists can be seen as exhaustive, which can be problematic.  I think that general statements of "be good humans" are useful, and not mutually exclusive with enumerated lists.  Would additional statements like "this list is not meant to be exhaustive, but merely to enumerate some common kinds of behaviors" address this problem?
This is similar in some sense to the US Constitution's ninth amendment

The enumeration in the Constitution, of certain rights, shall not be construed to deny or disparage others retained by the people.

Also

Practically, what this says is: we may discriminate you based on political opinions because we are a bunch of bigots as well

I think that this is bound to happen regardless based on the beliefs and cultural norms uniformly held by whatever group manages disputes.  This is one reason, I think, to ensure that this group comes from a group of broad backgrounds, beliefs, ages, life experiences, and so on.
I think that the choice to enumerate or not enumerate common topics doesn't particularly help or hurt this issue.  I could easily be wrong about this though.

Would additional statements like "this list is not meant to be exhaustive, but merely to enumerate some common kinds of behaviors" address this problem?

It would definitely make things better IMHO.

It would definitely make things better IMHO.

But would it make things good enough?
I agree with the concern that you raised generally.  Personally I'm comfortable if we add language something like what's above, but I only have one perspective here.  Are there other ways that we could improve things?  Would listing specific common issues be ok with such a disclaimer?

I find the phrasing of https://www.contributor-covenant.org/version/1/4/code-of-conduct good enough in that respect.
The lists in the "Our standards" sections are explicitly not meant to be exhaustive: they are "Examples of behavior" that are either encouraged or considered inappropriate. The list in the Pledge section is wide enough in my opinion.

@ogrisel Well, the list in "Our Pledge" is apparently exhaustive. I agree the "Our Standards" part is ok.
There is also this thing:

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.

Apparently it's not enough to follow and enforce the CoC, you must do so in "good faith". What does it mean? How is good faith or bad faith to be proven? It means some kind of religious adherence is expected.
I don't want to overdo this. In practice I'm sure most people don't care about the words a CoC uses, they just contribute as they see fit (hopefully without insulting anyone). Still, if we're discussing which CoC we want to choose, paying attention to words is probably desired.

Apparently it's not enough to follow and enforce the CoC, you must do so in "good faith". What does it mean? How is good faith or bad faith to be proven? It seems some kind of religious adherence is expected.

"Good faith" is a common phrase that is not intended to be related to religion.  Google defines it as "honesty or sincerity of intention".  Sometimes people use the latin equivalent "bona fides" instead.
I think that this sentence means to say that it is not only enough to follow/enforce this CoC technically, as a laywer might follow/enforce it.  Additionally we should follow the spirit of the agreement broadly.  I use spirit above as is it used in the phrase "to follow the spirit, rather than the letter of the law", which has the same meaning.  (sorry to explain English idioms with yet more English idoms).
Given the multi-lingual readership perhaps we should find a better way around the word faith here.

That's what I assumed as well. But, if someone is attacked on that basis, how are they supposed to prove their sincerity of intention?
A sentence about following the spirit, rather than the letter, would state it in a positive way, even though it's still rather vague.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership

I think that the intent of this text is to say two things:

"Maintainers are also subject to the CoC"
"Maintainers are required to enforce the code of conduct well.  If they don't do so, then the system should stop them from being project maintainers"''

Do you agree with these two points generally?
I agree with you also, that we should keep the tone positive, rather than talk about repercussions, which seems blame-y and negative.  I think that the far more likely break of these rules is that a maintainer is busy and so neglects enforcement.  I wouldn't want "repercussions" or any intentional harm done to the maintainer in this case.  I would just want the maintainer to be removed and another more active maintainer put in that place.  My guess is that in this situation this would likely be welcome on all sides.

I agree with the first point. The second point looks more contentious to me. Not everyone is apt in delicate mediation roles, and I'm not sure it's a good idea to chastise an otherwise competent and diligent maintainer for lack of skill in enforcing a CoC.
From a broader point of view, if a project has several maintainers, not all maintainers need to be involved in CoC enforcement (the same way that not all of them need to be involved in release management, etc.).

Yeah, I can see two different views on this (both of which seem reasonable to me).  I'll try to present arguments for each one.  I don't see an immediately clear answer here.  I encourage other people who haven't spoken up to speak up.

All Maintainers should be responsible to enforce CoC violations:  I think that this essentially boils down to the fact that having a "powerful" person not enforce violations is implicitly seen as condoning the activity.  The typical example would be in a company if employees say crude jokes around their boss and the boss doesn't react negatively, then they feel like it's ok to say crude jokes more generally.  Lack of action by "powerful" people ends up looking like support, which has negative consequencies.

I didn't sign up for this responsibility: In OSS we tend to give people authority/rights for volunteering their time/expertise/effort and being generally helpful in a variety of ways.  This includes people who want to engage mostly on a technical basis, and have no interest in managing people or personal-conflicts.  It seems incorrect that extensive volunteering or work suddenly makes you responsible for the behavior of those around you.  This goes from seeming incorrect to being scary if there are negative consequencies for inaction, especially if you don't have confidence that you'll be able to identify what other people think is inappropriate behavior.

For the CoC part, I'm happy to have a list of examples, be it as exhaustive as possible, but the

additional statements like "this list is not meant to be exhaustive, but merely to enumerate some common kinds of behaviors"

is mandatory too.
For the maintainer role on enforcing CoC, I'm leaning toward the didn't sign up for this responsibility side. But in this case, everyone, maintainer or not, can refer to the CoC to condemn/signal/highlight a bad behavior. Let maintainers who are confortable with this kind of mediations do the job then.

I'm also in favor of enumerating common unacceptable behaviors with an explicit statement that the list is not meant to be exhaustive. As @mrocklin pointed out this has the added benefit that we

can very clearly point to a line in the CoC and have a very short discussion, rather than have to go back and forth about what should or should not be considered offensive within this community

Regarding enforcement of the CoC, a third viewpoint would be to have a Code of Conduct Committee (similar to how Jupyter handles CoC enforecement) that is responsible for enforcing the CoC. Anyone can report if they think there are violations of the CoC, and the CoC committee is responsible for enforcement. This could serve as a middle ground between the "All Maintainers should be responsible to enforce CoC violations" and "I didn't sign up for this responsibility" viewpoints.
Not sure how much enthusiasm there is for forming a CoC committee, but I thought I would at least propose it as an option.

OK, it seems as if conversation has died down a little.  I propose that someone (any volunteers) draft a PR to this repository that includes the Contributor Covenant verbatim as a first commit, and then adds in a few modifications based on the conversation here in other commits.  That way we should have a good history of what we've changed and we can hopefully have a more targetted conversation on phrasing using GitHub's PR review machinery.
Is this ok with everyone?  Is anyone interested in drafting the original PR (we should all be able to modify it afterwards anyway).


Multiple FanzyZones with easy switching

📝 Provide a description of the new feature
What is the expected behavior of the proposed feature?  What is the scenario this would be used?
I need to use multiple layouts for different workflows. I need to be able use a particular layout and snap a window in that layout. If there is a layout switching shortcut, I can easily switch to a layout I need and snap a window according to that layout.
If you'd like to see this feature implemented, add a 👍 reaction to this post.

Tracker for this issue https://github.com/microsoft/PowerToys/issues/1411


Update aad-account.md fixed a couple of typos

Fixed one type and one mistake (removed global admin)

Docs Build status updates of commit 3bcafe3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/extensions-chromium/publish/aad-account.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


How to update session.userData in bot with username from browser after a user login

I am trying to greet the user without prompting for username in the bot rather getting it when they login..How to do this?

This is a super tricky problem. The short answer is you can do it but it's some pretty nasty code. We have a C# example that does it and I started implementing support for doing it in Node but we decided to rewrite a whole bunch of related code so I'm just starting that re-write and it will be a few weeks before I get "official" auth support working.
Basically you have to send the user a link in message that they need to click to login. This link should run through standard oauth flow and the challenge is what do you do when you get to the end of the flow.  As you said you need to store the users token on their session.userData object. But that's not actually enough. You should also send a message to the user telling them they're logged in or continue the task they were trying to achieve.
For the first part we have a REST API you can call that lets you read & write the userData object. You just need to save off the conversationId & userId for the person being logged in (this needs to be embedded in your oauth link somewhere.) For the second part you could generate a proactive message by calling bot.begingDialog(). That way is sort of the hacked way of achieving this.
The cleaner way that I started implementing does the same basic thing, sends the user a link with conversationId & userId embedded. But on completion of the oauth flow it packs the token into a message and routes it through the dialog system as if it was sent from the user. The advantage of that is that you could be in the middle of a waterfall, decide you need to log someone in, wait for the login to complete, and then simply continue the waterfall.
I've been calling these web actions and when I'm done there will probably just be a new Prompts.webAction() prompt you can use to achieve this. But as I said this is probably a 2-4 weeks out.

@Stevenic , please share the link of C# example for this. I'm also looking solution for similar requirement of greeting the user upon user login to the site.

https://github.com/Microsoft/BotBuilder/tree/master/CSharp/Samples/SimpleFacebookAuthBot

@Stevenic, I'm looking to intgerate web chat with one of out custom .Net application which FBA authentication. I would like to get the user details from session and show on web chat window with greeting user.
is it possible? is yes can you please share/point me to an example.

@srinivasamyneni you can pass the authtoken from your .Net application to the bot and use the auth token in the bot to get the information about user and send back the result to user in the web chat window.

how to get user name with node to greet with user name?

@Stevenic was Prompts.webAction() actually implemented? Cannot see in v3. Also since this is now closed, is there already a good way to achieve this ?
I want to do oauth and save the auth token in userdata and notify user. as @Stevenic mentioned above routing the callback to the dialog is a cleaner way than starting a proactive message. So was just wondering.
Thanks,
Palash


Kaisen Backup - Source Request

Source name
Kaisen Backup
Source link
https://www.kaisenbackup.com/
Source language
Portuguese (Brazil)
Other details
No response
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[ ] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I will fill out all of the requested information in this form.

Source has been down for 3 weeks. Closing.
And by down I mean there have been no chapters available.


fixed link to pydantic docs (#6204)

Pull request opened by the merge tool on behalf of #6204

Merged into branches iso6 in 325b305023eae7ecb9fb02e810b84396bc607e19


state / stateChange behavior

Disclaimer: I am actually using https://github.com/jacobrosenthal/react-native-ble with Android, however I am looking to find out whether I simply have a poor understanding of how this works, or if this is an issue with either react-native-ble or noble.
I am a bit confused as to how state / stateChange work...I initially assumed that a stateChange event would be automatically emitted when the user enables / disables bluetooth, but this doesn't seem to be the case. I then thought I should check whether bluetooth is on or off (whenever I need it), and change the state + emit event myself (" noble.state = 'poweredOn; noble.emit('stateChange', 'poweredOn' "), but even though this changes the noble.state to whatever I want it to, when I try and scan for devices, the scan actually starts but doesn't actually find anything (even though there are devices to be found).
In short: if I start the app with bluetooth off, I don't seem to be able to find devices even though I subsequently enable bluetooth, change noble state to 'poweredOn', and emit the appropriate 'stateChange' event.
I am sure I'm missing something obvious or grossly misunderstanding how these should be used, but I've been trying to figure it out with no success. I would greatly appreciate anyone shedding some light on this, and whether this behavior is normal (but I'm doing it wrong), or is it a bug?
Also, I was wondering whether noble supports serial data by any chance? After having a look around I believe the answer is no, but wanted to make sure? If no, is there a plan to implement this functionality at some point?

I am a bit confused as to how state / stateChange work...I initially assumed that a stateChange event would be automatically emitted when the user enables / disables bluetooth, but this doesn't seem to be the case.

That's the expected behaviour.

Also, I was wondering whether noble supports serial data by any chance? After having a look around I believe the answer is no, but wanted to make sure? If no, is there a plan to implement this functionality at some point?

There is no standard for serial data over BLE. Even if there was, noble would only be used as the lower level to build upon by another Node.js library/module.
Closing for now, I suggest you follow up with the react-native-ble maintainers (and observe some patience).


kabanero build pipeline failing with java-spring-boot2 stack

Describe the bug
Deployments using kabanero pipelines for java-spring-boot2 stacks failing in the build-step-build-push-step container. Logged here: https://github.com/kabanero-io/kabanero-pipelines/issues/16
To Reproduce
Steps to reproduce the behavior:

use appsody CLI to create local java-spring-boot2 app
push to git repo
deploy using kabanero pipeline

Expected behavior
Application deploys to cluster and starts.
Actual behaviour
Build fails with error with the following log in the build-step-build-push-step container:
  ...
  inflating: kotlinc/lib/kotlin-source-sections-compiler-plugin.jar
INFO[0046] Taking snapshot of full filesystem...
INFO[0049] Using files from context: [/workspace/extracted]
INFO[0049] COPY . /project
INFO[0049] Taking snapshot of files...
error building image: error building stage: lstat /workspace/extracted/.mvn-stack-settings.xml: no such file or directory

Environment Details (please complete the following information):

OS: any
Browser N/A
OKD 3.11
Kabanero Foundation (https://kabanero.io/docs/ref/general/#scripted-kabanero-foundation-setup.html)

If applicable please specify:

CLI version: appsody 0.2.8
Stack you are using: appsody/java-spring-boot2:0.3

Additional context
It appears that the kaniko build of the container is failing at https://github.com/appsody/stacks/blob/cf540803f2a7b09527f8b7c53ceda293f6b65165/incubator/java-spring-boot2/image/project/Dockerfile#L23 because of the missing file. The file is missing because
https://github.com/appsody/appsody-docker/blob/3ff31d134b1662653a964d87b3a5f4cd3ef36f31/setupAndRunExtract.sh#L44 will not match dot files from the source project directory and that's exactly what https://github.com/appsody/stacks/blob/cf540803f2a7b09527f8b7c53ceda293f6b65165/incubator/java-spring-boot2/image/Dockerfile-stack#L22 creates.
Two possible fixes depending on intent for setupAndRunExtract.sh in appsody-docker. If dot files at the top level of the extracted directory are to be included, then the match needs to be updated. Other stacks at present seem not to require this functionality.
In this case it seems preferable to not use a dot file for mvn-stack-settings.xml in the stack container for java-spring-boot2.

@ebullient

fixed by https://github.com/appsody/stacks/pull/210


Race/cascade in DefaultInstanceProfileAWSCredentials

Expected Behavior
Only one request to the metadata service should be made, even at startup
Current Behavior
When a container starts up under load the code in https://github.com/aws/aws-sdk-net/blob/master/sdk/src/Core/Amazon.Runtime/Credentials/_bcl%2Bnetstandard/DefaultInstanceProfileAWSCredentials.cs#L88 allows every task/thread to call the metadata service.  This leads to rate limiting to kick in on the metadata service which then cascades down to other containers when they try and start or refresh the creds.
Possible Solution
An double checked lock, Lazy or semphoreslim should be used to prevent every task/thread from making requests to IMDS
Steps to Reproduce (for bugs)
This occurs in EKS under load testing conditions
Context
This severely hurts load tests since adding capacity actually hurts the performance due to IMDS rate limiting
Your Environment

Service assembly and version used:

<PackageReference Include="AWSSDK.Core" Version="<IP_ADDRESS>" />
<PackageReference Include="AWSSDK.Extensions.NETCore.Setup" Version="3.3.101" />
<PackageReference Include="AWSSDK.S3" Version="<IP_ADDRESS>" />

Operating System and version:
FROM mcr.microsoft.com/dotnet/core/aspnet:3.1
Visual Studio version:
2019
Targeted .NET platform:
core 3.1

Any news?  This is my workaround that fixes the issue for me: https://gist.github.com/DTTerastar/f373bb6dbfc8d1437665f7b23e0a2cbb

I've opened sourced a small nuget library to help others fix this: https://github.com/AwsEx/AwsEx.Creds

This has been fixed in version 3.5.2 of AWSSDK.Core

This has been fixed in version 3.5.2 of AWSSDK.Core


Pre-load banner, show on request.

Is there a way to load the banner, without showing it?
Here is my issue: One of the views of my app has a banner. I show it with AdMob.showBanner(options). However, if the user navigates away from the view quickly enough, the banner shows up in another view, where it is not supposed to.
I assume that after calling .showBanner(), the module sends request for an ad and then displays it as soon as it loads. However, the view might already navigate away at that point. Is there a way to load the banner, without showing it? Similar to .prepareRewardVideoAd() and .showRewardVideoAd().

Banner AD has method to show and hide did you check it.?
https://github.com/rahadur/capacitor-admob#resumebanner-promise-value-boolean-

Hello, @rahadur
Thank you, for the suggestion. I do use hide and show methods to control the banner display between different views. They work well for their purpose, however my issue is different.
I probably didn't explain my issue clearly, for which I apologize. The hide method works well if the banner is loaded, but not during the very first call of .showBanner(). Here is a pseudo sequence as an example. Lets say a banner should be seen in view A, but not in view B.

View A is opened
AdMob.showBanner(options)
User clicks a button to open view B
View B is opened
AdMob.hideBanner()
Banner loads and shows on screen

The hide method doesn't work in this scenario, since the banner is not loaded yet.


stateEvents polyfill causes browser not to change URL on browser properly

When I use the polyfill provided with v1.0.0-rc.1 my URL does not seem to change, even though the state itself changes (the ui gets updated). If I remove the script from the code, then it works as expected.
Moreover, when the script is on, I can't change the URL directly through the browser - it "flashes" the target state and gets back to where I was -, even though changing states by the visualizer project works properly. All my URLs are computed by using $state.href on a ng-href, and those do not change the URL either, only if I click on them for several times.
I do need this polyfill since angular-permission does not provide support for rc.1 yet, and thus, rely on using $stateChangeStart.

I ended up with ui-router 0.4.2 (I've run into some problems with 1.0) and angular-permission 5.2.0. No states polyfill, only ui-router-route-to-components which is required to route to components (Angular 1.5+). Feel free to ping me via email for more details that are not pertinent to ui-router.

Good to know @mbenedettini. What I ended up doing was watching $transitions.onStart and calling directly PermStateAuthorization from angular-permission.
Not the best to be done, but it did the job as a workaround.


[2.1 RC] Query: Fix for GroupBy with Where Aggregate produces incorrect SQL

Issue: Due to the shape of QM we incorrectly identified the query for Group By SQL translation.
Which is not the case hence we generate a SQL which produces incorrect result
Fix: During result operator processing, we more carefully identify if we are selecting from a grouping source.
Also relax criterea that group by aggregate should be only 1 level deep. This also allows us to translate group by aggregate when it is inside join
Resolves #11695

@maumar - Updated.

@smitpatel Approved for RC1. /cc @divega


[DO NOT MERGE] Use components in finders

This PR must not be merged until this PR in publishing components is merged and deployed
Updating the finders to use components for form elements, so they look like this:

Example: https://finder-frontend-pr-684.herokuapp.com/aaib-reports
Trello card: https://trello.com/c/fhhTwfLo/178-use-form-element-components-in-finders

@andysellick I'm a bit confused by the heroku review app - it seems to always go to the Latest on GOV.UK?
https://finder-frontend-pr-684.herokuapp.com/aaib-reports
https://finder-frontend-pr-684.herokuapp.com/news-and-communications

@andysellick I'm a bit confused by the review app - the link you posted to aaib-reports doesn't actually go to the aaib finder?

@vanitabarrett yeah I'm confused too - I've tried other links and they all go to that same place. Something's not right, not sure what.

This should be fine for review now.  I've removed the DEVELOPMENT_FINDER_JSON environment variable from the review app and it's now working as expected again.  🤦♂

When the text that accompanies a checkbox wraps, the spacing looks a little odd.  I'm not sure I am able to suggest an obvious improvement though.  (There are longer examples than this in the people finder on https://finder-frontend-pr-684.herokuapp.com/news-and-communications)


Filter Forces Key Based Lookup

It appears that
ODataClient.For<TEntity>().Filter(f => f.Id == EntityId);

does not preserve the $filter semantic and gets translated to a key based url TEntity('EntityId'). This creates issues with the ASP.NET core implementation as $expands have to be explicitly implemented on a key based lookup but work as part of the framework when doing a filter.
See
https://github.com/OData/AspNetCoreOData/issues/520
https://github.com/OData/WebApi/issues/1188
This really does not seem like the correct behavior because it overrides the intent of the programmer to perform a filter.

ASP.NET Core SingleResult fixes the issue in ASP.NET Core. See https://github.com/OData/AspNetCoreOData/issues/520


Movie Recommendation System

The model takes input data of various users, the movies they have watched and if they like it or not. Later on, the model is trained on that data by implementing Real Boltzmann Machine using Pytorch to predict the movies in the test set that the concerned user may like to watch.

@Jogesh-Mishra kindly provide the description

@Jogesh-Mishra kindly provide the description

Done.

Sir I would like to work on this issue

Sir I would like to work on this issue


Describe the implications of IMPORT_FORCE=/ --import.force true vs. false

README.md doesn't really say much about these two except:

Enable force import of realm config

:-)
de.adorsys.keycloak.config.service.RealmImportService#updateRealmIfNecessary has:
    private void updateRealmIfNecessary(RealmImport realmImport) {
        if (importProperties.isForce() || checksumService.hasToBeUpdated(realmImport)) {
            updateRealm(realmImport);
        } else {
            logger.debug(
                    "No need to update realm '{}', import checksum same: '{}'",
                    realmImport.getRealm(),
                    realmImport.getChecksum()
            );
        }
    }

So I'm guessing that if the input is unchanged since last run, the realm is left as-is, but if anything in the input has changed, the checksum is different, and everything is applied. Is that correct?

Correct, thats all. Feel free to provide an understandable description as PR.

Resolved by #357


hugozan9

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: fd61abe1-251f-1409-d386-145d93c8f18f
Version Independent ID: b340c591-d6bf-ae5f-e9b1-b32be18d6bee
Content: Verify eligibility for Microsoft 365 Education subscriptions
Content Source: microsoft-365/commerce/subscriptions/verify-academic-eligibility.md
Service: o365-administration
GitHub Login: @cmcatee-MSFT
Microsoft Alias: cmcatee

@yogkumgit   There is no proper feedback so close this issue #8260,


netclient: 0.25.0 -> 0.26.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/gravitl/netclient/releases.
meta.description for netclient is: Automated WireGuard® Management Client
meta.homepage for netclient is: https://netmaker.io
meta.changelog for netclient is: https://github.com/gravitl/netclient/releases/tag/v0.26.0
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.26.0 with grep in /nix/store/78wqqjhg53hgndnpcz53mfcbifr9q90h-netclient-0.26.0
found 0.26.0 in filename of file in /nix/store/78wqqjhg53hgndnpcz53mfcbifr9q90h-netclient-0.26.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

netclient

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/78wqqjhg53hgndnpcz53mfcbifr9q90h-netclient-0.26.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A netclient https://github.com/r-ryantm/nixpkgs/archive/6ec5b8d597ba70452eee4208efc5fccda1c0946e.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/6ec5b8d597ba70452eee4208efc5fccda1c0946e#netclient

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/78wqqjhg53hgndnpcz53mfcbifr9q90h-netclient-0.26.0
ls -la /nix/store/78wqqjhg53hgndnpcz53mfcbifr9q90h-netclient-0.26.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review

x86_64-linux

:white_check_mark: 1 package built:

netclient

Maintainer pings
cc @wexder for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

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

nixpkgs-review result
Generated using nixpkgs-review.
Command: nixpkgs-review pr 354525

aarch64-darwin

:white_check_mark: 1 package built:

netclient


Heavily Modded Crash

My game is heavily modded and I attempted to add in the compression mod to make the game a little simpler via additional storage capabilities. However, when I attempt to start the game I now get a crash. Can anyone figure out what is causing this? I, unfortunately, am unable to understand the log.
http://pastebin.com/E7fTKfSc

While I don't really understand error logs either, I do know that I was having a similar issue with the mod. It turned out to be an incompatibility issue with the mod 'Adventure Backpacks'. If you have that mod installed I'd recommend disabling that mod's jar file (add '.disabled' to the end of the jar name, after the .jar extension) and trying to run the game then.
If you don't have 'Adventure Backpacks' or the error still happens, all I can suggest is disabling mods one by one until you identify the one where the incompatibility is.

It is likely there is a block or item that is causing compression to error out. Next time I get a chance, I'll take a look at the compression side of things. If you add the full minecraft log to this issue, I'll be able to more quickly diagnose what is causing the error.

You're build of RFTools is WAY too old for me to find in https://github.com/McJty/RFTools
You are going to need to submit this bug to RFTools before we can figure out what is going on here (they have done a lot of refactoring since this version of the mod was built).
If you have already done that, please link the issue on the RFTools tracker so that I can read that. Otherwise, please feel free to come back to this issue when you have more information!

Also, you are using a much older version of Compression. Correct me if I am wrong, but this is still scala code (in the log you will see it says "CBlocks.scala"). The last version of scala code I used was like 1.8/1.9ish. The mod is updated for 1.12, and you should use that.


AADB2C90118: The user has forgotten their password.

I'm getting below error When I click the forgot password link the custom sign page,
AADB2C90118:+The+user+has+forgotten+their+password. Correlation+ID:+0124482e-0fd6-4576-89aa-aa257312a694

Hello @Vasanth1981 Thank you for your feedback! This channel is for driving improvements towards MS Docs. In order to best address your question with the right team, could you provide us with the URL of the MS Doc that you were following, if any?

Hey @Vasanth1981 Just following up on my previous comment, please let us know if there's a specific documentation that you were following, otherwise, we'll proceed to close this issue.

Here you go,
https://docs.microsoft.com/en-us/azure/active-directory-b2c/tutorial-customize-ui
[Description: beam suntory]
Vasanth Prabu
Technical Lead – IDM & IT Development, IT
Vasanth.Prabu<EMAIL_ADDRESS>P:<PHONE_NUMBER> extn 1940
C:<PHONE_NUMBER>
Please consider the environment before printing this message.
From: Mike Urnun<EMAIL_ADDRESS>Sent: Friday, December 07, 2018 2:21 PM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Vasanth Prabu<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] AADB2C90118: The user has forgotten their password. (#20128)
Caution: External Email
Hey @Vasanth1981https://github.com/Vasanth1981 Just following up on my previous comment, please let us know if there's a specific documentation that you were following, otherwise, we'll proceed to close this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/20128#issuecomment-445354035, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AUHITdZhk3k6UwZUt_q1LGzIDVr6gKtDks5u2s3AgaJpZM4ZHX0Q.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 36c209d9-c15f-87a4-a7ee-bb2bd3416961
Version Independent ID: 2f76d983-a940-fa5f-abe0-4c851e377608
Content: Tutorial - Customize the user interface of your applications in Azure Active Directory B2C
Content Source: articles/active-directory-b2c/tutorial-customize-ui.md
Service: active-directory
GitHub Login: @davidmu1
Microsoft Alias: davidmu

When you create a sign-up or sign-in user flow (with local accounts), you see a Forgot password? link on the first page of the experience. Clicking this link doesn't automatically trigger a password reset user flow.
Instead, the error code AADB2C90118 is returned to your app. Your app needs to handle this error code by invoking a specific password reset user flow. For more information, see a sample  that demonstrates the approach of linking user flows.

Let us know if this has helped or you need further assistance

@neeleshray Thanks for the sample. However, I will try it in AngularJS with HelloJS.

gg


Added typescript definition file

I wanted to introduce some Typescript definitions.
This may be a work in progress, but the basic usage is covered and a Typescript based project won't complain when adding this library (personal experience :P)
Any comments are welcomed.
Thanks

Thanks!!

@diego-caceres can we add ref as well in defination file.


footer in autoescape.html has missing images

http://twig.sensiolabs.org/doc/tags/autoescape.html
The footer is not displaying correctly.

fixed now.


updated the slack.yml file

Description
This PR fixes #18
Notes for Reviewers
To fix this issue, updated the code of slack.yaml as per  slack.yaml of meshery
Signed commits

[x] Yes, I signed my commits.

@saurabh100ni please review and let me know what you think!

@ritiksaxena124 @Rajdip019 //


What exactly does the deprecation warning mean?

The warning says:

Feedback report deprecation on April 15th 2020 This report will no longer be supported after April 15th 2020. Data on this report will not refresh after this date and the report will be removed in future without further notice. You can continue to view feedback received from your customers directly in the Feedback Hub.

What does it really mean? Which report? Does it mean that I should not ask my users to leave their feedback in the Feedback Hub? Is this whole feature being deprecated?
I came to this page to learn how to use this feature. I can use this code in my app
await Microsoft.Services.Store.Engagement.StoreServicesFeedbackLauncher.GetDefault().LaunchAsync();
that will launch Feedback Hub, where user can leave feedback about my app. Is this now being deprecated? Or is it some other feature that I don't know of that is being deprecated?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 89cc1b93-b31f-09c7-681f-02a43a5fc682
Version Independent ID: 76d7a4eb-90f8-3501-3513-9637577dc999
Content: Feedback report - UWP applications
Content Source: windows-apps-src/publish/feedback-report.md
Product: uwp
Technology: publish
GitHub Login: @hickeys
Microsoft Alias: hickeys

I'm a little unclear on what you're asking. It says in the deprecation notice that "You can continue to view feedback received from your customers directly in the Feedback Hub." The report itself is being deprecated, but not Feedback Hub. Can you clarify your concerns?

I just don't know what "Feedback report" is. I have never used Feedback Hub to collect feedback from my users, so I am now unsure if I can even begin using it, because the message says that something (I don't what) is being deprecated now. Please, clarify it, if you can :-)


fFtT repeats do not work with vim-cutlass

When svermeulen/vim-cutlass is registered after lightspeed the repeating single character searches does not work. The initial single character search still works, but pressing, as an example, f again just starts a new f single character search.
I'm able to work around this issue by
nnoremap s <nop>
Plug 'svermeulen/vim-cutlass'
unmap s
Plug 'ggandor/lightspeed.nvim'

but thought you might want to be aware of the potential conflict. In particular cutlass does not, that I can tell, ever mess with any of fFtT.

Thanks for reporting! Interesting issue, I will read through the cutlass script and get to the bottom of this, when I find the time.

I am also getting this.

I just switched to lightspeed (great plugin btw) over from sneak and this annoyed the heck out of me too :see_no_evil:
After digging through the cutlass script and your code I am confident I found the reason for this behavior.
cutlass is registering a mapping in select mode for every single character, so that when you start typing the selected text which gets deleted is not written into the default delete register (see here)
When looking into the ft.to function of lightspeed I found that there is a check if a <Plug>Lightspeed_[fFtT] mapping is mapped in the current mode (see line 507)
(set self.instant-repeat?
   (and ok? (string.match (vim.fn.maparg in2) "<Plug>Lightspeed_[fFtT]")))

If you call vim.fn.maparg without the second mode parameter it will check the default mapping as if using :map <characters> from within NVIM. Now the issue appears as :map will check normal, visual, operator and select mode for bindings to the given characters. If you have lightspeed and cutlass installed and enter :map f your output should show the following:
s  f           * <C-O>"_cf
o  f             <Plug>Lightspeed_f
x  f             <Plug>Lightspeed_f
n  f             <Plug>Lightspeed_f

The first binding is the cutlass binding from the function I mentioned at the start of this comment.
Now when you execute :lua print(vim.fn.maparg('f')) you will not get an array of all bindings available but just of the first one:
<C-O>"_cf

Therefore the check for the instant repeat will always fail and we get the behavior we have monitored.
To solve this the current mode needs to be passed to the maparg function.
But beware that maparg use different characters to describe some modes than you would get from vim.fn.mode() (which returns the current mode). So simply passing vim.fn.mode() as second parameter here will only fix the issue for normal mode but not for visual. vim.fn.mode() in visual mode will return "v" or "V", but maparg uses "v" for visual AND select mode, so we have to use "x" instead (check the documentation of both functions). I don't think any other mode besides normal and visual is interesting here :thinking:
Based on this I came up with a simple solution in lua as I have no experience writing fennel.
(see the compiled (?) lua code at line 645)
local current_mode = vim.fn.mode()
if current_mode:find('[vV]+') then
     current_mode = "x"
end
self["instant-repeat?"] = (ok_3f and string.match(vim.fn.maparg(in2, current_mode), "<Plug>Lightspeed_[fFtT]"))

@ggandor maybe you can "translate" my lua version into the appropriate fennel code for the plugin :slightly_smiling_face:

@TheBlob42 Awesome. Thank you for the fix and the detailed explanation.
Moreover, checking the mode also handles the unlikely (but technically possible) case if someone maps different keys for ft-search in Normal and Visual mode.
For the current mode, we should check blockwise (<ctrl-v>) too, so [vV]+ wouldn't suffice I guess, we need to call replace_termcodes, etc., starts to become too complex to do that on the spot. On the other hand, we could get away with a much simpler solution, since I have only exposed  keys for x mode (not v). Since we are not in operator-pending mode (that has been checked above), if it the mode is not Normal, then it should be Visual. (Well, one could technically make Select-mode mappings that call the Lua functions directly, but it's their responsibility from then on, the ft table is not part of the official API.)
You're more than welcome to do a PR yourself if you want some contribution credit :) Here is the Fennel snippet:
(set self.instant-repeat?
     (and ok?
          (let [mode (if (= (vim.fn.mode) :n) :n :x)]  ; vim-cutlass compat (#28)
            (string.match (vim.fn.maparg in2 mode) "<Plug>Lightspeed_[fFtT]"))))

If you download the most recent Fennel executable, and put it on the path, you can just make it before commiting. (But of course I can just push this right now if you don't want to bother with it.)

@ggandor thanks for providing me with the Fennel snippet :slightly_smiling_face:
Can you check if the opened PR is correct and if so merge it?

@TheBlob42 Everything's fine, thanks very much again for the fix!


navbar hover effect ui

Enhancing User Engagement with Effective Navbar Hover Effects
Assign it to me .. I will look into this
Thank You :)
Ping @anjalit03

The navbar has been updated already if you want to you can fix the navbar on the home page it is not properly arranged same for the footer :)

yeah I can assign me and please label it as hacktoberfest (:

I am working on it @anjalit03 don't worry about that


Allow dyn traits to be used with io::Read

Add a ?Sized constraint to read::signed and read::unsigned, allowing dyn
traits to be used with those functions. This also makes them consistent
with the write functions, which already impose that constraint.
Apparently, cargo fmt also restyled some code.

 Out of curiosity, when will this change be reflected in crates.io?

Already published!


enable speech_recognition and recommedation new api examples for pytorch

Type of Change
speech recognition (change torchaudio eager+dynamic to fx+static)and recommedation.
Description
enable examples for recommendation, speech recognition
detail description
JIRA ticket: ILITV-2466
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

retest after bug fix: extension test

torchaudio: hubert_fx: https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/3837/

https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/3839/artifact/report.html

https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/3871/

https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/3874/

https://inteltf-jenk.sh.intel.com/job/intel-lpot-validation-top-mr-extension/3885/


Signature for this request is not valid

{     "code": -1022,     "msg": "Signature for this request is not valid." }
i set everything as well like binance api key and secret.
i check all of it.
X-MBX-APIKEY is true.
i can get every result as well at market and accout tabs like Account Trade List but when i try under of Order tab like All Orders i got an signature error.

Hi.
Could you double check if all optional parameters without values are all unchecked?
If so, can you extract the raw query string for that specific request? It will be helpful for the investigation.

@ishuen thanks, i checked 'All Orders' for an example and i was not type symbol. i filled symbol by BTCUSDT and it works.


Implement review button and its functionality

Performance tracking and previous chat message storage were not implemented for the application's current version.


Add nextjs tag

It seems apps using Next.js are adding the "nextjs" tag on their GitHub page. Maybe it would make sense to add it to Next.js itself too...

I like this. Can't add it though. cc @nkzawa

Done, thanks for your suggestion !


angryziber.AngryIPScanner version 3.7.6

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

I've stuffed this one up. Withdrawing it.