Flask does not reload modified code when running under WSL

I am developing a Flask app on a Linux machine, which does correctly reload itself when I modify a Python source code file (when running in debug mode). Sometimes though I need to develop on a Windows machine, using WSL, but the very same Flask app sources. That basically works fine, however, under WSL the auto-reload feature does not seem to work any more. I can change the Python sources, but nothing happens - I need to manually shutdown and restart the Flask server.
Is this a known bug under WSL? Do I need to start the Flask application in a certain way?
As reference, here is how I start the application under VS Code:
"configurations": [
    {
        "name": "Run Server",
        "type": "python",
        "request": "launch",
        "module": "flask",
        "env": {
            "FLASK_APP": "run.py",
            "FLASK_ENV": "development",
        },
        "args": [
            "run"
        ],
    }
]

... which starts the the Flask appliacation under WSL with these output:
 * Serving Flask app "run.py" (lazy loading)
 * Environment: development
 * Debug mode: on
 * Running on http://<IP_ADDRESS>:5000/ (Press CTRL+C to quit)
 * Restarting with inotify reloader
 * Debugger is active!
 * Debugger PIN: 182-804-918

That output looks fine to me, but still no auto-reload.
Any ideas?
Environment

Python version: 3.8.2 64-bit (from Ubuntu on WSL)
Flask version: 1.1.2
Werkzeug version: 1.0.1

It's probably due to inotify not working well under the WSL. Try uninstalling the watchdog package, as that will force Flask to use the default "stat" reloader, which should behave better.

You can also use --reloader stat for the same effect ;)

You can also use --reloader stat for the same effect ;)

How do I start Flask with this option (in VS Code)?
I tried this:
mfb@Sector2:/data/Development/Python/MLserver$ FLASK_APP="run.py" FLASK_ENV="development" flask run --reloader stat
Usage: flask run [OPTIONS]
Try "flask run --help" for help.

Error: no such option: --reloader

nevermind, i somehow thought this option existed but apparently there's only --reload/--no-reload...

It's probably due to inotify not working well under the WSL. Try uninstalling the watchdog package, as that will force Flask to use the default "stat" reloader, which should behave better.

That solved my issue, after uninstalling watchdog auto-reloading worked now, thanks!


Actor annotated protocols don't work

If you annotate a protocol with a global actor, such as @MainActor, its generate mock doesn't compile:
Given
/// @mockable
@MainActor
protocol RootController: AnyObject {
    var viewController: UIViewController { get }
}

the mock will fail with this compilation error:

❌ /usr/local/var/buildkite-agent/builds/7003-local-1/varun-santhanam/{}/Project/{}Tests/Mocks.swift:226:16: call to main actor-isolated initializer 'init()' in a synchronous nonisolated context
--
  | return RootControllerMock()

The solution, I believe, would be to also add the actor annotation to the Mock
An identically generated mock, with the @MainActor annotation would work just fine.
I believe there would be similar errors for per-member annotations as well.

@vsanthanam
I can generate mocks with no problem.
Would the same error occur if you use the latest version of Mockolo (1.7.0)?

Seems to be happening even on 1.7
note that generating the mocks isn't the problem. Its that the mocks aren't compilable.
❌ /Users/vsanthanam/Desktop/convusic-monorepo/Project/ConvusicMobileTests/Mocks.swift:498:16: call to main actor-isolated initializer 'init()' in a synchronous nonisolated context
        return MainControllerMock()

The mocks cannot invoke the initializers of their actor dependent mocks because they are not annotated correctly
Here's an attached generated but non-compiling example:
Mocks.swift.txt


App devs can replace mbedtls cleanly in enclave apps

While tasks #68 & #72 have defined API surfaces which insulate OE runtime direct invocations of the underlying crypto library, the layering of the enclave libraries and where the OE crypto abstraction functions are implemented mean that an app dev must still modify OE enclave sources to use a different crypto library in the enclave.
This can be addressed by introduce a new generic oecrypto library, which includes:

The crypto wrapper functions used by OE (now in oeenclave)
The entropy wrapper function for mbedtls (now in oecore)
mbedx509
mbedcrypto

This reduces the library dependencies to this.

oeenclave
crypto
oelibc
oecore

The encapsulates all of the extensibility points into the oecrypt component so that it can be replaced without further modification of oeenclave or oecore directly.

This is ongoing effort. In v0.6 we have refactored crypto headers to specify which ones are to be implemented by new crypto libs.  After v0.6 we will publish a sample and also the crypto APIs on openenclave org.


[Auto SDK]: Alexa responds "Music and radio playback are not supported in this device"

Briefly summarize your issue:
Alexa says 'Music and radio playback are not supported in this device"
What is the expected behavior?
• Music plays on the connected device, NOT on the Smartphone or tablet.
• After the Alexa Auto device is disconnected, ensure that Music stops playing.
What behavior are you observing?
Alexa says 'Music and radio playback are not supported in this device"
[Precondition]
Music - Verify play on Smartphone and Tablet
Ensure that a smartphone or tablet AVS Application will NOT stream any music unless connected to the Alexa Auto client device it supports.
Connect the Alexa Auto client device which is running on a Smartphone or tablet application to the appropriate Audio speaker (i.e. connect a wired or Bluetooth device to an external speaker system).
Provide the steps to reproduce the issue, if applicable:
[Test steps]

Play music.
Verify Music is playing on the connected Alexa Auto client.
Disconnect or switch off the Alexa Auto device.
Stop the music.

Utterance:

Play music
Stop

Tell us about your environment:
SW:  app-local-debug.apk on Android Mobile
What version of the AVS Device SDK are you using?
 AUTO SDK

Tell us what hardware you're using:

[ ] Other - Android phone

Tell us about your OS (Type & version):

[ ] Other - Android Phone

Hello @DeepikaBalaga,
Please use this link for assistance with the Auto SDK: https://github.com/alexa/alexa-auto-sdk/blob/2.3/NEED_HELP.md
Best regards,
-SWH

Hello @DeepikaBalaga,
Closing as this is an Auto SDK issue. Of course, if it the root cause is found to be in the AVS Device SDK, please feel free to create a new issue with information to help is reproduce and diagnose the issue.
Best regards,
-SWH


resource will not utilize notifications

Hi, I'm having a little trouble.
No matter what I try I cannot chain things together with either of the notifies or subscribes notifications.  After the selinux resource is updated nothing happens.
node.default['selinux']['state']                           = "permissive"
selinux_state "SELinux #{node['selinux']['state'].capitalize}" do
  action node['selinux']['state'].downcase.to_sym
  notifies :write, 'log[I was notified by selinux]', :immediately
end

log "I was notified by selinux" do
  action :nothing
  level :warn
end

@ngtjah
I am unable to replicate with the current cookbook version.
   [2017-02-27T21:13:06+00:00] INFO: template[enforcing selinux config] updated file contents /etc/selinux/config

         - update content in file /etc/selinux/config from 8a6a4a to bd48e3
         --- /etc/selinux/config	2017-02-27 21:11:37.930891117 +0000
         +++ /etc/selinux/.chef-config20170227-1387-1unv847	2017-02-27 21:13:06.266629003 +0000
         @@ -3,7 +3,7 @@
   #       enforcing - SELinux security policy is enforced.
   #       permissive - SELinux prints warnings instead of enforcing.
   #       disabled - SELinux is fully disabled.
         -SELINUX=disabled
         +SELINUX=enforcing
   # SELINUXTYPE= type of policy in use. Possible values are:
   #       targeted - Only targeted network daemons are protected.
   #       strict - Full SELinux protection.

   [2017-02-27T21:13:06+00:00] INFO: selinux_state[SELinux Enforcing] sending write action to log[log_selinux_state] (immediate)
     * log[log_selinux_state] action write[2017-02-27T21:13:06+00:00] INFO: Processing log[log_selinux_state] action write (selinux::default line 36)
   [2017-02-27T21:13:06+00:00] WARN: LOGGED: SELINUX_STATE WAS UPDATED

Updated recipe:
selinux_state "SELinux #{node['selinux']['status'].capitalize}" do
action node['selinux']['status'].downcase.to_sym
notifies :write, 'log[log_selinux_state]', :immediately
end
log 'log_selinux_state' do
message 'LOGGED: SELINUX_STATE WAS UPDATED'
action :nothing
level :warn
end
Please update your cookbook use and if you are still having problems, please open a new issue which will use the github issue template. Make sure to include full information about your platform and recipe in use. Thanks!


Fix typo in link to GitHub Actions for Azure docs

Removed extraneous s in the text for the GitHub Actions for Azure docs link

Learn Build status updates of commit 165884e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

articles/aks/integrations.md
:white_check_mark:Succeeded

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 learn.microsoft.com contributor guidesPost your question in the Learn support channel

Looks good; thanks, @techneaux


have some trouble

Hi, I trained with the following config and I did not change the code
python main/train.py --model 'ICON-S' --dataset '/data2/lanjun/dataset/sod_dataset/datasets/DUTS/Train' --lr 2e-3 --decay 2e-4 --momen 0.9 --batchsize 6 --loss 'CPR' --savepath 'checkpoint/finetune/ICON-S/' --valid True
but I get the following result，it doesn't match the result in the paper. Did I do something wrong? need help
Method:ICON-valid-59,Dataset:ECSSD||Smeasure:0.927; meanEm:0.954; wFmeasure:0.911; MAE:0.032; fnr:0.065||adpEm:0.955; meanEm:0.954; maxEm:0.963; adpFm:0.918; meanFm:0.916; maxFm:0.941
Method:ICON-valid-59,Dataset:PASCAL-S||Smeasure:0.875; meanEm:0.912; wFmeasure:0.834; MAE:0.054; fnr:0.115||adpEm:0.908; meanEm:0.912; maxEm:0.921; adpFm:0.843; meanFm:0.849; maxFm:0.872
Method:ICON-valid-60,Dataset:ECSSD||Smeasure:0.926; meanEm:0.953; wFmeasure:0.911; MAE:0.032; fnr:0.069||adpEm:0.955; meanEm:0.953; maxEm:0.962; adpFm:0.919; meanFm:0.917; maxFm:0.94
Method:ICON-valid-60,Dataset:PASCAL-S||Smeasure:0.874; meanEm:0.91; wFmeasure:0.833; MAE:0.055; fnr:0.122||adpEm:0.907; meanEm:0.91; maxEm:0.919; adpFm:0.843; meanFm:0.849; maxFm:0.87

The results you obtained are indeed one point lower than the paper, so if it is convenient for you, please retrain a version (adjust the learning rate) and provide me with additional feedback. Actually, in my experiments, the ICON-S, ICON-P have very stable performance. So I will try it in my side.

I use the default config as follow, what learning rate should I set?
python main/train.py --model 'ICON-S' --dataset '/data2/lanjun/dataset/sod_dataset/datasets/DUTS/Train' --lr 2e-3 --decay 2e-4 --momen 0.9 --batchsize 6 --loss 'CPR' --savepath 'checkpoint/finetune/ICON-S/' --valid True

Sorry, I did something wrong, and I get the same result with you. Thank you

@yelanlan  Thanks for feedback. This is my WeChat: tjpxiaoming.


Binary Lifting For LCA on Trees

Type
Algorithm
Directory
Algorithms=>Tree-Algorithm=>Binary_Lifting
Description
Binary lifting is a technique which is used to find the LCA of two nodes in a tree in O(logn) time. This technique uses some a precomputation time of O(nlogn).
Programming Language

[X] c++
[ ] c
[x] python
[x] java
[ ] kotlin
[ ] javascript
[ ] typescript
[ ] c#
[ ] swift
[ ] ruby
[ ] scala
[ ] go
[ ] php
[ ] haskell
[ ] bash

Could you assign this issue to me for c++?

I can do this in Java. Do assign if required

i can do this in python can u assign this to me

I can do this in C++. Do assign if required

Please assign me this task I will do it in Javascript.
Thank You

I can do this in C#. Please assign me this issue.

javascript=>1Day


Implement a first draft of the RoutingResourceStore

This implements a first draft of the RoutingResourceStore that I wrote in my remaining time.
A RouterRule decides if it can forward the request to a certain instance of a ResourceStore based on the incoming parameters, if not it will return undefined and ask the same question to the next rule.
If no rule given to the ResourceRouter can decide, an Error is thrown (can be adapted to a specific error).
Some simple rule implementations have already been written, such as a DefaultRouterRule that always returns an instance from the FileResourceStore. But more rules need to be written.
In this implementation an instance of the ResourceStore is given to the RouterRule, this can be changed but was my first logical thought.
No tests were written yet.
This idea was discussed in #59.

The travis test should build and succeed once this PR is merged with #72.
(It uses the SparqlResourceStore in some RouterRules.


Reporting in Protractor (Other than Html Reporter)

hi,
Can u people help me in finding the reporter for Protractor other than NPM Html Reporter or Npm Html Screenshot reporter or can u help me in customizing the Npm Html Reporter. I want to handle the reporting and screenshots in scripts. Please advice which is the best solution for this. As of now im using the npm html reporter

Hi there!
Your question is better suited for StackOverflow or Gitter. Please ask a question there with the 'protractor' tag or post in the Gitter Channel to get help.
From the the getting help section of the README:

Please ask usage and debugging questions on StackOverflow (use the "protractor" tag) or in the Angular discussion group. (Please do not ask support questions here on Github.)


DevCheck ExitCode if issues detected. Fix dependencies

DevCheck: set ExitCode to non-zero if 1+ issues detected
Fix KozaniManagerRuntimeTests' Dependencies

/azp run

/azp run

ship ship ship

/azp run


CUSTOM SCROLL-BAR

Description

This PR does the following:

Updates SCROLLBAR

Related Issues
Fixes #502
Changes

Added a new feature to scrollbar

DEMO
https://github.com/user-attachments/assets/11e53e28-71ae-4991-ac79-d8f1244c6d40
Checklist

[x ] I have performed a self-review of my code
[x ] I have commented my code, particularly in hard-to-understand areas
[x ] My changes generate no new warnings
[x ] I am working on this issue under GSSOC

@Soujanya2004 Review PR..

let it be just red dont add hover color

let it be just red dont add hover color

want to change background black ? or white  or anyother color ??

@Soujanya2004 Chnaged based on your requirement

@Soujanya2004 please review Pr.. i changed the color that you give me


Use {arch}/{os}/remote/installDb.sh to install db on a remote machine instead of Ubuntu_14.04/installDb.sh (common/scripts/installDb.sh)

https://github.com/Shippable/pm/issues/10227

this is done, closing


fix: memory leak in Import (backport #773)

don't reference the children, which recursively retain the whole subtree in memory.

@tac0turtle @alexanderbez can you review this one too?


Namespace istio-system Pods istio-egressgateway goes to restart.

-Problem Description : In the Namespace istio-system Pods istio-egressgateway goes to restart.

- Problem location: After deployment of Omnia it will generate istio deployment yaml files in /root/k8s/omnia-kubeflow/kustomize/istio-install/base
-suggested solution: Update the Pod resources CPU size as needed in istio-noauth.yaml for istio-egressgateway

@j0hnL after increasing limits it worked, tested locally.


Can you provider your codes about cpp_wrappers based on tf2 and cuda11.0?

Can you provider your codes about cpp_wrappers based on tf2 and cuda11.0? I can compile it when I using tf2 and cuda11.0. Looking forward to your reply.

Can you provider your codes about cpp_wrappers based on tf2 and cuda11.0? I can compile it when I using tf2 and cuda11.0. Looking forward to your reply.
I using 3090,this is a problem, I
File "/home/lab601/anaconda3/envs/py36/lib/python3.6/site-packages/tensorflow/python/client/session.py", line 1394, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InternalError: 2 root error(s) found.
(0) Internal: Op kernel context needs to provide a rendezvous.
[[{{node args_0/_1}}]]
[[IteratorGetNext]]
[[gradients/layer5/edge_conv1/BiasAdd_grad/BiasAddGrad/_1037]]
(1) Internal: Op kernel context needs to provide a rendezvous.
[[{{node args_0/_1}}]]
[[IteratorGetNext]]
0 successful operations.
0 derived errors ignored.

I guess the problem is that your package cpp_wrappers  is compiled incorrectly. Can you provide a package that can be compiled with tf2?

Hi @longmalongma,
Sorry I am not working on this repo anymore so I can't provide new stuff. If you want to compile this in tf2, you will need to figure out the changes by yourself. Sorry that I cant be of any help here, and good luck with your problem.
Best,
Hugues

Hi @longmalongma,
Sorry I am not working on this repo anymore so I can't provide new stuff. If you want to compile this in tf2, you will need to figure out the changes by yourself. Sorry that I cant be of any help here, and good luck with your problem.
Best,
Hugues

Can you give me a concrete idea of how to solve this problem? I can hardly finish it by myself.


Add simple Bag of Words example, Fix Canned Estimator

The main reason the canned Estimator was failing was that it was using the wrong kind of feature column. You were passing the word indexes as a numeric column... switching to:
xc = tf.contrib.layers.sparse_column_with_integerized_feature('x',NUM_WORDS)
xc = tf.contrib.layers.embedding_column(xc,30)

Mostly fixes it for me. There were a couple of other things I fixed:

Use "post" in sequence.pad_sequences. The default adds padding to the start of the sequence, while the estimator expects you to pad the end.

I pull out the sequence lengths since the Estimator does use them if supplied.

I added the "bucket by sequence length" logic.

I added some dropout ... but it still overfits (The DNN BOW could also use some dropout).

The simple Bag-of-Words example I also attached makes a nice performance baseline, but the first half of the notebook also explores how feature_columns work with these things.
The BOW example file also shows how to convert back from the keras word indices to text.

Thanks so much for the contribution Mark, it looks great!


notify.telegram: data_template + Markdown - Can't find end of the entity starting at byte offset N

Home Assistant release (hass --version):
0.33.3
Python release (python3 --version):
3.4.2
Component/platform:
notify.telegram
Description of problem:
Telegram notifications fail when building the message with a data_template and using {{ trigger.entity_id }} and the number of _ (markdown for italic text) is not even. So if the template resolves to device_tracker.device, there's a final _ missing to finish the italic text. This leads to the traceback posted below.
Expected:
Working notifications.
Problem-relevant configuration.yaml entries and steps to reproduce:
- alias: "Loginnotify"
  trigger:
    platform: state
    entity_id: device_tracker.daniel
    to: "home"
  action:
    - service: notify.tele
      data_template:
        message: >
          {{ trigger.entity_id }}

Traceback (if applicable):
Nov 24 00:21:01 homeassistant hass[21793]: INFO:homeassistant.core:Bus:Handling <Event call_service[L]: service_call_id=1975746672-11, service=tele, service_data=message=device_tracker.daniel, domain=notify>
Nov 24 00:21:01 homeassistant hass[21793]: ERROR:homeassistant.components.notify.telegram:Error sending message
Nov 24 00:21:01 homeassistant hass[21793]: Traceback (most recent call last):
Nov 24 00:21:01 homeassistant hass[21793]: File "/srv/hass/hass_venv/lib/python3.4/site-packages/homeassistant/components/notify/telegram.py", line 122, in send_message
Nov 24 00:21:01 homeassistant hass[21793]: parse_mode=parse_mode)
Nov 24 00:21:01 homeassistant hass[21793]: File "/home/hass/.homeassistant/deps/telegram/bot.py", line 124, in decorator
Nov 24 00:21:01 homeassistant hass[21793]: result = func(self, *args, **kwargs)
Nov 24 00:21:01 homeassistant hass[21793]: File "/home/hass/.homeassistant/deps/telegram/bot.py", line 150, in decorator
Nov 24 00:21:01 homeassistant hass[21793]: result = self._request.post(url, data, timeout=kwargs.get('timeout'))
Nov 24 00:21:01 homeassistant hass[21793]: File "/home/hass/.homeassistant/deps/telegram/utils/request.py", line 205, in post
Nov 24 00:21:01 homeassistant hass[21793]: **urlopen_kwargs)
Nov 24 00:21:01 homeassistant hass[21793]: File "/home/hass/.homeassistant/deps/telegram/utils/request.py", line 152, in _request_wrapper
Nov 24 00:21:01 homeassistant hass[21793]: raise BadRequest(repr(message))
Nov 24 00:21:01 homeassistant hass[21793]: telegram.error.BadRequest: "Bad Request: Can't parse message text: Can't find end of the entity starting at byte offset 6"

Additional info:
Workaround: Add a _ to the template. Which only works if I don't add entity_ids as triggers with even number of _.
I believe line 116 is part of the problem.

Telegram should really fix this their end, I've encountered it outside of this project. If they don't see a closing notation they should just display the first.
You're absolutely right that it's because we're using markdown - as it's failing to parse it. I think it's time to allow parsemode to be configurable.

Hmm... i have kind of a similar problem i guess:
Traceback (most recent call last):
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/core.py", line 1045, in execute_service
    service_handler.func(service_call)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/notify/__init__.py", line 110, in notify_message
    notify_service.send_message(**kwargs)
  File "/usr/local/lib/python3.4/dist-packages/homeassistant/components/notify/telegram.py", line 122, in send_message
    parse_mode=parse_mode)
  File "/root/.homeassistant/deps/telegram/bot.py", line 124, in decorator
    result = func(self, *args, **kwargs)
  File "/root/.homeassistant/deps/telegram/bot.py", line 150, in decorator
    result = self._request.post(url, data, timeout=kwargs.get('timeout'))
  File "/root/.homeassistant/deps/telegram/utils/request.py", line 205, in post
    **urlopen_kwargs)
  File "/root/.homeassistant/deps/telegram/utils/request.py", line 132, in _request_wrapper
    resp = self._con_pool.request(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/urllib3/request.py", line 72, in request
    **urlopen_kw)
  File "/usr/lib/python3/dist-packages/urllib3/request.py", line 135, in request_encode_body
    **urlopen_kw)
TypeError: urlopen() got multiple values for keyword argument 'body'

I can not figure out how to get telegram in general working, might be connected i didn't want to open another issue, before it is clear.


glibc should be patched to look for /etc/protocols in /nix/store

Describe the bug
Certain functions in glibc look for files present in /etc such as getprotobyname which reads /etc/protocols.
If you are using Nix over a Linux installation, this file may not be present, and therefore it will cause errors.
Nix should strive to be as reproducible and hermetic as possible.
Rather than looking for the files at /etc, glibc should be patched to look for these files in the /nix/store; very similar to how Nix does LOCAL_ARCHIVE.
Right now the guidance is to use libredirect (https://nixos.wiki/wiki/Packaging/Quirks_and_Caveats#Test_cannot_access_.2Fetc.2Fprotocols.2C_.2Fetc.2Fservices_or_expects_a_special_.2Fetc.2Fpasswd_when_building_in_sandbox) which seems unfortunate and annoying to users.
Useful links:
https://github.com/bminor/glibc/blob/595c22ecd8e87a27fd19270ed30fdbae9ad25426/resolv/netdb.h#L47
Notify maintainers
I did not see any explicit maintainers, so tagged a few from the history of the file.
@thefloweringash
@Mic92
@vcunat
@edolstra
@ma27

Is this file not supposed to be configurable? Or do you mean there should be environment variables to redirect it?

The file in glibc is hardcoded.
For instance on a Debian installation you must have sudo apt-get install -y netbase.
Ultimately shouldn't everything be self-contained to the /nix/store ?
Seems like it's less of a problem on NixOS but on Nix on other Linux distributions it should doing to another nixpkg similar to LOCAL_ARCHIVE.

I think that adding such variables should only be done very carefully.  I suspect there are some reasons for restricting some of these (say, LD_LIBRARY_PATH) in setuid binaries, and we might just be adding a security hole this way (a small-ish one if any, I expect, but still).

I'm not really following your logic @vcunat: reading files outside of the /nix/store and relying on the environment though is antithesis to the concept of Nix and it's versioning.
I think this aligns close to many other similar patches such as that to clang/gcc to not read from default library paths or the locales as mentioned.

/etc/protocols is runtime configuration data, just like /etc/resolv.conf or /etc/nsswitch.conf or /etc/hosts. You don't want to rebuild the entire system just to change protocols. Now, in practice nobody ever changes /etc/protocols so we could get away with hard-coding it, but it would be a bit fishy. The same applies to /etc/services BTW.

See also https://github.com/NixOS/nixpkgs/pull/111194, which proposes adding an environment variable for the NSS search path, and https://gist.github.com/Infinisil/3366e7dfc9a01f6eeb25b5cb475cc585 which proposes a generic environment variable.

I guess rather than hardcode, I am advocating for something similar to make an environment variable override.
It's just a bummer than out-of-the-box on Debian, Nix can cause failures since glibc does not find these files.
Maybe a fallback to an entry in the /nix/store ?

Uh, I wonder what Debian's glibc does then.  Any package with a binary using these syscalls should declare a dependency on netbase?

That's my understanding; and-or it's brought eventually and the problem stabilizes.
(That non-determinism seems perfect for Nix to solve)

We might also make nix depend on netbase on Debian :trollface: (say, for the short term)

It might be worth noting that go in nixpkgs actually does hardcode this, since 6039f2effea02c1ee6a716d0487f787293cd081b.
Maybe that has been reverted at some point, but when I looked into this (#101038) it was still the case.

Interesting; well that's only for golang built binaries in Nixpkgs.
Should I put time on this for a patch or is there a broader discussion here that is more well suited for an RFC?

No. just make a PR.

@Mic92 PR incoming today.

Wow; I spent time trying to dig through the glibc code @Mic92 -- intense.
The getproto code is very macro heavy

Wow; I spent time trying to dig through the glibc code @Mic92 -- intense.
The getproto code is very macro heavy

The glibc code quality is quite bad. Mainly because of one former long-term maintainer.

:(
I really wanted to patch it. Maybe I'll give it another shot to walk the macros later ...

If it's runtime configuration data, oughtn't we include it in the sandbox?


goctl 8月28日 新增的API生成代码的自定义类型有误

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior, if applicable:

The code is
以looklook中定义的api配置生成为例，实际应该生成如下代码，但目前生成的是2中的错误代码
应该是tools/goctl/api/gogen/util.go中的getRefProperty方法代码有问题
type CommentListResp struct {
 List []HomestayComment `json:"list"`
}

The error is
type CommentListResp struct {
 List struct {
 }
 }

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Environments (please complete the following information):

OS: [e.g. Linux]
go-zero version [e.g. 1.2.1]
goctl version github master

More description
Add any other context about the problem here.

Use the goctl stable version: go install github.com/zeromicro/go-zero/tools/goctl@latest

在 #2368 已修复

It has already fixed on #2368


Support specifying total reactor power through power density

For some analysis cases, it is easier to investigate concepts that share a power density but may differ in total size or fuel mass. Therefore the total power would differ. Meaning if one were to create a parameter sweep that tried to keep power density constant, there are some hoops to jump through.

Settings modifier to modify power : pretty easy to implement once you know the power.
Other input modifiers to perturb your reactor

But, input modifiers work on the blueprints, so the entire reactor isn't created to be able to do something like power = powerDensity * reactor.getVolume() (for a W/cc power density) or powerDensity * reactor.getHMMass() (for W/gHM power density)
This ticket proposes allowing the total power to be set via power density specified in the settings file. Or maybe two power density settings, for volumetric and gravimetric power density)
Some settings pairs could be

powerPerVolume and powerPerHM (short but no units explicitly stated)
volumetricPower and gravimetricPower (no units, a little archaic naming?)
powerPerCC and powerPerGHM (units are there, maybe confusing GHM for grams HM or giga-HM)

These settings should be mutually exclusive with each other and with power. But I think after some initial conversion, the total power should be the metric used by ARMI like it is already.

First, I'll clarify that one can modify case settings as part of a sweep (there is an example of such here). I'm not sure if you were meaning to say that this is not possible, or rather just your specific example of doing power density is not possible. I guess the power density case is somewhat tricky because you need to dynamically evaluate the reactor volume without the reactor object existing yet.
Regardless, specifying a reactor power level by power density is pretty normal, so I think this is a valid and valuable request.
I would expect that this should be a possible change to make, but I've found in the past that it is sometimes difficult to thread the needle of resolving the case settings at the right times. In this case, you're going to need a reactor object to be instantiated before you can ever query the power level.
Typically people are used to querying reactor power via something like self.cs["power"], which unfortunately can only return a static value. In other words, the case settings are not aware of the reactor state, which you'll need to access in order to get the volume of the reactor. One way that this has been resolved in the past is to resolve the settings onto the operator, as is done for the various cycle history settings. This is a little bit annoying to implement as it will require you to scan through the entire code base and replace calls like self.cs["power"] with something like self.o.power, but allows for settings to be queried in such a way that they can see the current state of the reactor. Since this would break a lot of external plugins, you'll probably have to but a barrier in place that prevents a plugin from accessing cs["power"] if cs["powerDensity"] also exists, since cs["power"] has a default (sigh) and thus is always accessible.
Not sure that is the best way to go, but just my initial thoughts.

@drewj-usnctech have you taken a look at User Plugins? It might be a good way to get some of the behavior you're looking for without too many code changes. The only challenge that I see with power density is that sometimes (well maybe more than sometimes) it is defined in different ways in terms of what the denominator actually is. Is it active fuel volume, total volume of the core, total volume of fuel assemblies (with structure and coolant). If we were to implement this as a setting or parameter that is used to derive power then we would also need to be picky and prescriptive of the definition that might not be one-sided fits all.
I only suggest user plugins (I haven't used them personally) because it could be a way to parameterize some new setting that is added by a plugin dynamically and then to interpret that after the reactor is constructed using the plugin hooks.
What do you think?

@jakehader

The only challenge that I see with power density is that sometimes (well maybe more than sometimes) it is defined in different ways in terms of what the denominator actually is

Very good perspective on what the volume should actually be. And probably enforcing (and supporting) one variation opens the door to people wanting to support more variations...

have you taken a look at User Plugins?

Yes but last I checked UserPlugins cannot define settings. A unique ArmiPlugin might get there, but then there's a weird user experience where, because settings:power is required, you could have a settings file like
settings:
  power: 1 # this is fake and set by volumePowerDensity
  volumePowerDensity: 2 # w / cc

which feels weird? It would work, presuming the plugin can set cs["power"] early on so that everything in ARMI uses the real power derived from the power density and however the plugin / interface sets the power

I see the issue now. I'll brainstorm and come back 🧠

This is a fun idea.
Let's take a look at a UserPlugin approach as Jake said.  Though, honestly, this could just be part of your regular plugin super easily.  It's just easier to use show a UserPlugin example, for instance, we have a very similar example in the ARMI docs already:
https://terrapower.github.io/armi/tutorials/making_your_first_app.html?highlight=userplugins#define-the-userplugin-in-python
Now, this isn't exactly what you want, but this modifies the power in the Core in some arbitrary way:
    @staticmethod
    @plugins.HOOKIMPL
    def onProcessCoreLoading(core, cs, dbLoad):
        for b in core.getBlocks(Flags.FUEL):
            b.p.power += 1.0

You can see here in the Plugin we are calling onProcessCoreLoading(core, cs, dbLoad), where we have access to the CaseSettings object (cs).  So, you could imagine your Plugin (or in this case UserPlugin defines a new Parameter called "powerDensity" on the Core, and loop through all the Blocks in the core and adjust the power/powerDensity in the Block to match the setting:
    @staticmethod
    @plugins.HOOKIMPL
    def onProcessCoreLoading(core, cs, dbLoad):
        powerDensity = cs["powerDensity"]
        if powerDensity > 0:
            power = powerDensity * core.getVolume()
            core.p.power = power

            # or, optionally
            for b in core.getBlocks():
                b.p.power = stuff
                b.p.powerDensity = whatever

So, I have two questions:

Would the above method, added to your Plugin with a new setting also added to your Plugin, technically do everything you need?  (I am just making sure I understand the goal.)
If the above does solve your use case, do you think there is still a need to add the above functionality to ARMI proper?

@john-science A plugin would allow us to define a power density and apply that to the reactor model.
Where adding this to ARMI proper becomes handy is there would then be two ways to define the total power of the reactor from the settings file
settings:
  power: 1 # this is fake and set by volumePowerDensity
  volumePowerDensity: 2 # w / cc

since ARMI requires the power setting to be provided. The plugin that accepts volumePowerDensity (or however else it's defined) would be able to set cs["power"] using logic like you provided. But any other plugin that acts with cs["power"] prior to the "real" power being set with power density will be using the wrong power

@drewj-usnctech Okay, I'm convinced.
Now to the details.  (These names are not final, I'm just trying to be clear.)

Does it make sense to you that we have two settings power and powerDensityOfSomeKind, and the user species either one or the other, but they get an error if they specify both?
Should we add powerPerHeavyMetalMass or powerPerHeavyMetalVolume or both?  I tend to thing "less is more" and "there should only be one way of doing things".  So I lean towards just doing the "volume" one.  But... I have my biases. Thoughts?
Right now the Reactor/Core-level "power" parameter is used EVERYWHERE, at every step of the modeling process.  Every time step, people grab the current power from a block/component in global flux calculations or TH things, you name it.  I envision here that we would use the new "power density" parameter only at the start/setup/init/preprocessing, and leave all the current code alone. Is that what you were also thinking?


OptimizeDeviceDialling Parameter

Hello,
brushing up my Teams CmdLet knowledge, I now tackle Dial Plans. :)
To fully understand all they have to offer, I found the Parameter OptimizeDeviceDialling which does not have a Description in New-CsTenantDialPlan and Set-CsTenantDialPlan. I never used this switch before, nor did I have to use ExternalAccessPrefix...
I do not know how relevant this switch (and the corresponding ExternalAccessPrefix Parameter) are in Teams, so I did not want to propose a change to the doc just yet.
Set-CsDialPlan (for Skype) has had this description for it:

Setting this parameter to True will apply the prefix in the ExternalAccessPrefix parameter to calls made outside the organization. This value can be set to True only if a value has been specified for the ExternalAccessPrefix parameter.

May I ask that a decision is made about this parameter, either to add a description or mark it as deprecated if that is truely the case :)
Thank you,
David
[Enter feedback here]

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

ID: 6f9dccd1-bc3b-6c14-eb66-2a566a71d94f
Version Independent ID: 545fa8ce-0abe-4921-04ef-3cd1bf496f24
Content: Set-CsTenantDialPlan (SkypeForBusiness)
Content Source: skype/skype-ps/skype/Set-CsTenantDialPlan.md
Service: skypeforbusiness-powershell
GitHub Login: @tomkau
Microsoft Alias: tomkau

Thanks for your feedback @DEberhardt David, will try to clarify thru a pr.


Having external document store instead of default

Hi guys,
Great job with this module.
Right now, document store is in memory and we are loading index from files all at once.
What i working on is to add that in external document storage for same so that i can add lots of index without having out of memory issue.
Here is my concern:
Right now we are adding all the links in this format:
{"link": {attr key value}}
which is great for one site, i want to add multiple site in the elastic lunr at Server side and want to share the common front-end across various sites and while doing search I dont want to fetch content of abc.com [eg] even though keyword match because user is searching on pqr.com.
What you guys suggest about optimal schema for same considering less code changes in the module.

Hi @codeforgeek ,  Sorry for the late reply.
I'm not quite understand your issue.
But according to my understanding, with Elasticlunr.js you could setup it that do not store source documents, this means you just build index and store index.
And, for another issue, that return only user fetched document fields, I think currently Elasticlunr.js will only return document ID & score, then you could retrieve document by ID, this require user design their documents storage themselves.
But if you want to use powerful search engine, I think elasticsearch is a better choice.

"And, for another issue, that return the only user fetched document fields, I think currently Elasticlunr.js will only return document ID & score, then you could retrieve a document by ID, this requires user design their documents storage themselves."
-- I am working on same. I will store the indexes which are docInfo object in memory as it is for faster search but will store docs i.e docs object in the persistent database because of memory issue. Right now docs are key value object and I need to modify same to make it work.
What I wanted from you is a recommendation and the best way to do it since you wrote this :) ElasticSeach is of course something I wanna do but in future.


small typo on the Reactjs implementation

just enclosing the boolean in curly brackets, otherwise it throws an error, thanks for the project bro

Good catch, thanks!


Yellow atlas source warning exclamation mark is REALLY hard to see in light mode

Tested versions

Reproducible in v4.2.1.stable.official [b09f793f5], v4.3.dev2.official [352434668]

System information
Windows 10.0.22631 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 4080 Laptop GPU (NVIDIA; <IP_ADDRESS>33) - 13th Gen Intel(R) Core(TM) i9-13900HX (32 Threads)
Issue description
When there is an issue with the tiles of an atlas source, a yellow exclamation mark will warn the user about it. When hovering, it might show useful information, like "The current atlas source has tiles outside the texture" or something like that. Unfortunately, it is really hard to see in light mode:

While you certainly notice that it's there if you know about it, when I wondered why I'm getting so many errors I tried debugging for at least an hour before I learned of its existence online.
Steps to reproduce

Set your Editor to light mode
Create a tile texture, a tileSet and an atlas source loading the texture.
Add tiles to the atlas source.
Edit the texture and remove some tiles.

Minimal reproduction project (MRP)
Exclamation.zip

A similar yellow warning icon (for node and script warnings) is handled properly in this scenario:

Dark Theme
Light Theme

However, for some reason, this particular icon (StatusWarning.svg) is being ignored, so no color conversion is allowed: https://github.com/godotengine/godot/blob/36e943b6b20cb7a8a89bc30489c4a81c3e149d74/editor/themes/editor_color_map.cpp#L174

So, this (and other icons) were added to the exception list in https://github.com/godotengine/godot/pull/15817. The node warning was also added on this PR, but was removed with https://github.com/godotengine/godot/pull/51220 due to the similar visibility issue.
So it seems safe to remove this icon from the list as well. It should also fix a couple of other scenarios:

To extend off of this, the "Debugger" tab font color is now also impossible to read for me on v4.3.dev (current master)

Not sure if the colors have changed since 4.2 as it seems a little brighter than the screenshots you have above

@RobProductions I've just tested it on the latest commit (5f05e2b9b1a3fedcdd7ecb2ab976a2687fd6f19a), before and after applying #88058, and I can't reproduce that. Can you try out the CI build (https://github.com/godotengine/godot/actions/runs/7949675459) and see if it still occurs? And if yes, provide more details about your setup/settings?


Fix some RTL issues

While using this library in an RTL app, I ran into some problems in some parts, which I fixed in this PR.
I hope it's useful.

Thank you very much, the relevant code commits will be merged into the next beta release!


Support accessing the prose mirror schema instead of HTML/markdown

Summary
I want to write a portable text parser for the wysiwym.
Basic example
Add an experimental API to the wysiwym with format “custom” and an input and output option that each take a function that respectively receives the input data and expects the return of a proawmirror schema, and receives the prosemirror schema and allows you to output your own document format.
Motivation
This will make the wysiwym open to extension but not modification, allowing more formats to be used with it.

I updated the name of this issue to better reflect how the editor works.

Editor Docs
Translator Abstract Class


correcting typo

Updated the two scss files with the affected typo and the main.css (not sure if this one needs to be committed)

Thanks, but I think it brings other issues, such as the link color is too bright, and the nav link color should be white. I'm working on it.
https://deploy-preview-185--hugo-theme-bootstrap.netlify.app

Fixed by<PHONE_NUMBER>5be1a01a5a6671ac1de8fd3a0ad8ee.

That's fair. It looks like you found a good solution. I'll pull it,update, and retest. For the contrast ratios on the text to see if we are still getting the flag on some of the test site I use.


Better configuration of target repository ID

When uploading RPM artifacts to Nexus, the target repository ID for snapshot and release artifacts may be significantly different, especially when the release repository is actually a staging profile.
It would be useful to have an option to define separate names for snapshot and release repository and also an option to tell that --staging argument shall be added for the release repository.
Example:
RELEASE_REPO=releases-el
SNAPSHOTS_REPO=snapshots-el

make uploadrpms VERSION=1.2.3 RELEASE=SNAPSHOT
make uploadrpms VERSION=1.2.3

In the above example the first command would deploy RPMs to snapshots-el5/6/7, while the second would deploy RPMs to releases-el5/6/7.

Target repositories can be configured through variables RELEASE_REPOSITORY and SNAPSHOT_REPOSITORY. Both can contain a $(os_version) placeholder for OS version.
Additional options to artifact upload can be specified using RELEASE_UPLOAD_OPTIONS and SNAPSHOT_UPLOAD_OPTIONS, or the original UPLOAD_OPTIONS (which overrides the previous two).
Documentation in README.md has been updated.


Requests made using Request object request the wrong URI

Given the following Guzzle client, instantiated with a base URI including a path:
$client = new GuzzleHttp\Client([
    'base_uri' => 'http://example.com/API/',
]);

These two styles of making requests, the first using a magic method and the second creating a GuzzleHttp\Psr7\Request object, should (I believe) request the same URI---however they do not.
try {
    $response = $client->get('foobar');
} catch (Exception $e) {}

try {
    $request = new \GuzzleHttp\Psr7\Request('GET', 'foobar');
    $response = $client->send($request);
} catch (Exception $e) {}

The first approach makes a request of http://example.com/API/foobar  (which we'd expect given the examples in the docs re: RFC 3986), while the second makes a request of http://example.com/foobar (note: the missing API/ in the path). I'm guessing/hoping this divergent behavior is not expected.
The reason this is happening is that the path I'm passing into GuzzleHttp\Psr7\Request, in this case foobar, gets transformed into /foobar in GuzzleHttp\Client::sendAsync() when $request->getUri() gets called on line 97.
This is happening because the Request object is transforming the string URI I pass into a GuzzleHttp\Psr7\Uri object, and in the process, GuzzleHttp\Psr7\Uri::filterPath() is called, which automatically prepends the path with a slash (line 574). Now as far as why filterPath() needs to do this or what needs to change to fix this (without breaking something else) I don't know.

This will be fixed in the next tagged release of the PSR-7 package (planning on tagging in the next couple days). In the meantime, you could pull in the dev-master branch of the psr7 package.

:boom: Thanks.

Btw, the obvious workaround (for anyone else who might be reading) was to set the base_uri to http://example.com/ and update my request uri to /API/foobar which I'll revert once the PSR-7 package is tagged.

The guzzlehttp/psr7 package has been updated and tagged with a fix.


Why an environment variable?

I don't understand why this article tells people to use an environment variable. The vast majority of use cases will store the connection string in a config file. An environment variable may work on a developers local machine if they only connect to one storage account but this seems unlikely.
What am I missing?

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

ID: 60e56e69-1c44-2056-ad5f-319535e4b525
Version Independent ID: 49fa6098-0b8e-ebf5-efe7-f50f3604e325
Content: Quickstart: Azure Blob storage library v12 - .NET
Content Source: articles/storage/blobs/storage-quickstart-blobs-dotnet.md
Service: storage
Sub-service: blobs
GitHub Login: @mhopkins-msft
Microsoft Alias: mhopkins

Hello @speciesunknown
In the past, when we've had samples with credentials in configuration files, we found that some people would forget about it and would end up shipping their personal credentials as part of the project. We came up with this solution of using environment variables instead. It's not perfect, but it does solve that problem of people accidentally passing around their personal credentials.
Thanks for the question.
~ Mark
#please-close


hotfix/PTX-3795 fix an issue when checking px is up

Signed-off-by: Thiago Gonzaga<EMAIL_ADDRESS>
What this PR does / why we need it:
this PR adds a third check when px reporting up before it really is.

tested here https://jenkins.portworx.dev/job/Torpedo/view/Torpedo NextPX/job/tp-ocp-candidate-csi/39/

tested here https://jenkins.portworx.dev/job/Torpedo/view/Torpedo NextPX/job/tp-ocp-stable/81/console
now you see
19:54:42 [36mINFO[0m[2021-09-30 22:54:42] Using <IP_ADDRESS>:17017 as endpoint for portworx volume driver

19:54:42 [37mDEBU[0m[2021-09-30 22:54:42] Running command on pod debug-g2sbz [[nsenter --mount=/hostproc/1/ns/mnt /bin/bash -c which pxctl]]

19:54:42 [37mDEBU[0m[2021-09-30 22:54:42] Running command on pod debug-g2sbz [[nsenter --mount=/hostproc/1/ns/mnt /bin/bash -c /usr/local/bin/pxctl -j status]]

19:54:42 2021/09/30 22:54:42 Failed to wait for px status on: ip-10-0-156-117.ec2.internal due to err: node ip-10-0-156-117.ec2.internal status is up but px cluster is not ok. Expected: STATUS_OK Actual: STATUS_INIT Next retry in: 10s

19:55:33 [36mINFO[0m[2021-09-30 22:55:32] Using <IP_ADDRESS>:17017 as endpoint for portworx volume driver

19:55:33 [37mDEBU[0m[2021-09-30 22:55:32] Running command on pod debug-g2sbz [[nsenter --mount=/hostproc/1/ns/mnt /bin/bash -c which pxctl]]

19:55:33 [37mDEBU[0m[2021-09-30 22:55:33] Running command on pod debug-g2sbz [[nsenter --mount=/hostproc/1/ns/mnt /bin/bash -c /usr/local/bin/pxctl -j status]]

19:55:33 [36mINFO[0m[2021-09-30 22:55:33] px on node: ip-10-0-156-117.ec2.internal is now up. status: STATUS_OK

19:55:33 [37mDEBU[0m[2021-09-30 22:55:33] checking if PX pod is up on node: ip-10-0-156-117.ec2.internal


Format model data before posting to api?

Is it currently possible to format the json object in a certain way before making the POST request to the api?
In sails/sails-rest when I create a new user, the body of the create method looks like
{
    "first_name": "Stanley",
    "last_name": "Ipkiss"
}

The api that I'm connecting to with sails-rest wants a more explicit format for new users though, such as
{
"user": {
    "first_name": "Stanley",
    "last_name": "Ipkiss"
}
}

Is there a way to add this explicit wrapper key to the body before sending to the api?

@dylanbathurst please check out v0.1.0-waterline-v0.10 which is a complete re-write of the adapter, with support for before and after hooks that let you modify data before sending it.
Would love to hear what you think.


fix(theme): set correct background and text color for panels

When documenting, I noticed that the --tk-elements-panel-backgroundColor was not used. I'm not entirely sure if I fixed it in all the correct locations. For instance, is the content on the left also a panel? And thus, should the background be impacted by this token? (currently it's not)

I also added a new token to set the default text color of the panel. I figured, if there's a way to specify the background color, there should also be a way to specify the text color. cc @donmckenna We should not forget to add this to figma then.

I think I haven't used the panel background because it's was not used in the Figma design. So if we change the system to use the panel background instead of the app background then we need to update the design file as well. Maybe that was just by accident @donmckenna or was there a particular reason to not use the panel background token?

For instance, is the content on the left also a panel?

Personally I would say the left side (tutorial content) is not a panel because it doesn't have a panel header and it's different from the panels we have on the right. So for the left side I'd say that it is not impacted if you'd change the panel background color and instead is impacted when the app background color gets changed.

To be honest, currently the only thing the app background impacts is the background of the steps that are running like "Booting WebContainer" and running the prepare commands. But the terminal has it's own background, and so does the editor.

Oh yea? Wait, shouldn't the tutorial content background be impacted as well? At least that's how it's defined in Figma 🤔

Oh sorry, I was referring to the panel background, my bad.


[Feature] Contributors Section

Description

I would like to add a category called Contributors that displays contributors with a similar card structure as the existing resources. - To be included in this category, contributors should meet a minimum threshold of 5 or more contributions.
To automate the process and avoid manual entry, I will implement an automatic mechanism.
Each card in the category will include the following details:

Profile Avatar
Profile Name (not username)
Commit history

The contributors will be displayed in descending order based on their contribution count.

This is an exciting feature, and I would love to try to contribute this major section.

@rupali-codes
Please review this idea. It is taking a while to merge the pull requests or even assign the issues. Should I start working on the task without an assigned issue?
Screenshots
No response
Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue (optional)
[X] I am a GSSoC'23 contributor

@Anmol-Baranwal thanks.. so are you talking about to create a sperate page for it? And yeah, you can start working on the issue :)

@Anmol-Baranwal thanks.. so are you talking about to create a sperate page for it? And yeah, you can start working on the issue :)

I was thinking to make it similar to a category and list all the contributors in that category ( which will act as a page)

@Anmol-Baranwal thanks.. so are you talking about to create a sperate page for it? And yeah, you can start working on the issue :)

I was thinking to make it similar to a category and list all the contributors in that category ( which will act as a page)

Hmm.. the Landing is being made, how about adding it there?

@Anmol-Baranwal thanks.. so are you talking about to create a sperate page for it? And yeah, you can start working on the issue :)

I was thinking to make it similar to a category and list all the contributors in that category ( which will act as a page)

Hmm.. the Landing is being made, how about adding it there?

Please indicate where I should attach a screenshot. It will fetch at least 20 contributors, so please share your thoughts accordingly.
Additionally, I have semester exams coming up soon, but I will resolve all the issues by the 16th. Therefore, please don't rush, and feel free to provide specific details on what you would like me to add.

@rupali-codes This issue reminded me that we were planning to include a maintainer section,
and if I remember correctly someone was working on that along with adding it to new landing page ?!

@rupali-codes This issue reminded me that we were planning to include a maintainer section, and if I remember correctly someone was working on that along with adding it to new landing page ?!

Yup, you're correct @ujjawaltyagii. I think it's issue #500.

@rupali-codes This issue reminded me that we were planning to include a maintainer section, and if I remember correctly someone was working on that along with adding it to new landing page ?!

Yup, you're correct @ujjawaltyagii. I think it's issue #500.

yeah, and for the landing page its this PR #605


Remove coaching pitch from README template

We no longer offer 1-on-1 coaching,
so it shouldn't be part of our standard template.

:+1:


Upon selecting a multiplayer game mode the user is considered as the “Game Master” and directed to the “Game Master Screen”.

commit: 2ef404b


Feedback on How to Access the Azure Functions App with Google Authentication Using JavaScript

Type of issue
Missing information
Feedback
I created a sample Azure Function locally and deployed it to Azure using the URL https://.azurewebsites.net/.auth/login/google/callback. After that, I was able to access the URL: https://.azurewebsites.net/api/. The Function App URL is now working as expected, and here are the logs:

I am trying to access the https://.azurewebsites.net/api/, which should return a JSON response: Hello, using JavaScript.
I have tried using both @react-oauth/google and passport-google-oauth2.
const GoogleStrategy = require( 'passport-google-oauth2' ).Strategy;

//Middleware
app.use(session({
    secret: "secret",
    resave: false ,
    saveUninitialized: true ,
}))

app.use(passport.initialize()) // init passport on every route call
app.use(passport.session())    //allow passport to use "express-session"

//Get the GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET from Google Developer Console
const GOOGLE_CLIENT_ID = "3184701-tn6finlstvgcgvte2381.apps.googleusercontent.com"
const GOOGLE_CLIENT_SECRET = "XyLuTLHX6Ov_93IP"

authUser = (request, accessToken, refreshToken, profile, done) => {
    return done(null, profile);
  }

//Use "GoogleStrategy" as the Authentication Strategy
passport.use(new GoogleStrategy({
    clientID:     GOOGLE_CLIENT_ID,
    clientSecret: GOOGLE_CLIENT_SECRET,
    callbackURL: "http://localhost:3001/auth/google/callback",
    passReqToCallback   : true
  }, authUser));

passport.serializeUser( (user, done) => {
    console.log(`\n--------> Serialize User:`)
    console.log(user)
     // The USER object is the "authenticated user" from the done() in authUser function.
     // serializeUser() will attach this user to "req.session.passport.user.{user}", so that it is tied to the session object for each session.

    done(null, user)
} )

However, I am receiving a 403 error. I am trying to use either @react-oauth/google or passport-google-oauth2. Any help would be appreciated. Thank you!
Page URL
https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/app-service/configure-authentication-provider-google.md
Content source URL
https://learn.microsoft.com/en-us/azure/app-service/configure-authentication-provider-google
Author
Rageking8
Document Id
2b2f9abf-9120-4aac-ac5b-4a268d9b6e2b

@Sampath280
Thanks for your feedback! We will investigate and update as appropriate.

@Sampath280
Thanks for your feedback! I've assigned this issue to the author who will investigate and update as appropriate.


Update install set up and rename preprocess def

Bonjour,
Merci pour le code, je trouve cela très instructif ! Je vous propose un petit update du readme pour l'installation et du nom d'une fonction.
Pourriez-vous me préciser pourquoi vous ne faites qu'une seule EPOCH ?
Je n'arrive malheureusement pas à converger au delà de 70%, auriez-vous une piste à me donner ?
Using TensorFlow backend.
Train on 82332 samples, validate on 35068 samples
Epoch 1/1
2018-12-30 12:18:28.991691: I tensorflow/core/platform/cpu_feature_guard.cc:141] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
82332/82332 [==============================] - 37s 449us/step - loss: 0.9234 - categorical_accuracy: 0.6660 - val_loss: 0.8513 - val_categorical_accuracy: 0.7093
/home/r3dlight/.local/lib/python3.6/site-packages/keras/callbacks.py:569: RuntimeWarning: Early stopping conditioned on metric val_binary_accuracy which is not available. Available metrics are: val_loss,val_categorical_accuracy,loss,categorical_accuracy
(self.monitor, ','.join(list(logs.keys()))), RuntimeWarning
175341/175341 [==============================] - 17s 95us/step
loss on test data: 0.8494550091447903
accuracy on test data: 70.88131127349541 %
Saved model to disk
Thanks !

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
chrisckwong821, @mprather1, @Parker-Quinn, @IndoAltcoin, @Maimartava, @Bisquick69, @ranpo, @Agigi, @gpahal, @rhslack, @mkhb654, @weihao, @cefigueiredo, @sbagency, @meatflavourdev, @th3outcast, @zhichicao, @AN8991, @ken-y2017, @dariuszsetlak89


Added CSS variable for changing the font size of title bar

Added CSS Variable --title-bar-font-size for changing the font-size of the title bar

Thanks for your contribution 🙂
Only changing this would probably not have been enough to fully customize the size of the title, so I decided to fix this with this commit cb12fd7bd762d8587b8776c137834dc6492d47ab
There is now a variable for the sizing of every parts of this component 😉


[CELEBORN-1783][FOLLOWUP][0.4] Compatible with UT

What changes were proposed in this pull request?
Compatible with UT for branch-0.4, followup https://github.com/apache/celeborn/commit/de436f7151ee4859e4ab62efa41aae3122086506
Why are the changes needed?
Does this PR introduce any user-facing change?
How was this patch tested?

UT passed, cc @RexXiong


Webpack automate set process.env.NODE_ENV to 'production' when start with --mode development

Bug report
What is the current behavior?
Webpack automate set process.env.NODE_ENV to 'production' when start with --mode development
If the current behavior is a bug, please provide the steps to reproduce.

Expect process.env.NODE_ENV to development when set mode: 'development'
Other relevant information:
webpack version:  4.9.1
Node.js version:  v10.1.0
Operating System:  macOS 10.13.4
Additional tools:

@gsmlg Not related to webpack, it is part of webpack-cli https://github.com/webpack/webpack-cli/blob/30dd10d51c0c9e64ec2369fbb09c10464e6e7a40/bin/config-yargs.js#L318

@evilebottnawi Nice catch. Completely missed the -p flag.


Export as Jupyter Notebook option saves files in wrong location

When I choose the "Export as Jupyter Notebook" icon in VS Code, it brings up a standard Windows file picker window. I choose the directory and file name that I want and say OK. However, the file doesn't show up in that location; instead, it shows up in C:\Users\Username\AppData\Local\Programs\Microsoft VS Code\c:\path\chosen\for\output\notebook.ipynb.

@forsakenquantum I just tried this but cannot reproduce the problem. Please could you fill our our bug template? At a minimum it would really help to have your VS Code version, Jupyter extension version, and operating system info. If you can provide detailed logs that would also be helpful.

@joyceerhl sure; can you point me to the bug template? I tried finding one but I couldn't. Also, are there instructions somewhere that I can follow about capturing logs?
In the mean time, here are the specs I'm working with:
VS Code info:
Version: 1.54.2 (user setup)
Commit: fd6f3bce6709b121a895d042d343d71f317d74e7
Date: 2021-03-11T00:56:19.848Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Jupyter extension: ms-toolsai.jupyter 2021.3.619093157
Device info:
Processor	Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz   2.11 GHz
Installed RAM	16.0 GB
Device ID	3EDE34B0-EF44-431E-9142-5753ECA0FFC0
Product ID	00330-62964-96164-AAOEM
System type	64-bit operating system, x64-based processor
Pen and touch	Pen and touch support with 10 touch points

Windows info:
Edition	Windows 10 Pro
Version	20H2
Installed on	11/14/2020
OS build	19042.867
Experience	Windows Feature Experience Pack 120.2212.551.0

The bug template is https://github.com/microsoft/vscode-jupyter/issues/new?assignees=&labels=bug&template=1_bug_report.md. An extra question:
Are you exporting from the interactive window? If so did you create the interactive window in association with a Python file, and where is that Python file located?
You can get debug logs by going to your settings and setting jupyter.logging.level to 'debug', reloading VS Code, repeating the repro steps, and then pasting the output of the Jupyter output tab:


Does not work with aws-vault / STS credentials

This project works fine with permanent credentials provided in env vars, but when I use aws-vault to supply temporary credentials generated by STS it fails:
~/src/banks[lein-essthree]$ aws-vault exec spark -- lein essthree com.amazonaws.services.s3.model.AmazonS3Exception: Status Code: 403, AWS Service: Amazon S3, AWS Request ID: 6CF10E37F11D0A02, AWS Error Code: InvalidAccessKeyId, AWS Error Message: The AWS Access Key Id you provided does not exist in our records.
Curious if you have any debugging tips.

https://github.com/dparis/lein-essthree/pull/7 seems to fix it

Any update on this?

I wound up writing a new maven wagon that uses the AWS CLI to sidestep dependency hell: https://github.com/SparkFund/aws-cli-wagon


Innodb engine DDL. Add config for timeout and load sample.

Change dict_dataset, dict_field_detail table engine to InnoDB. We always found the front end is blocking when there is some backend job loading in these tables. This is because MyISAM will optimize some query to table lock in some situation. For now the easier way is change database engine from MyISAM to InnoDB. InnoDB have better support for concurrency.
As we change to InnoDB, we need to set innodb_lock_wait_timeout to a higher value as some query will exceed the default timeout of a transaction.
Add an option configuration that can skip Teradata sample data ETL. Default is doing the ETL.

LGTM.
The timeout can be set to 3~5 minutes.


This document page is dated.

The information on this doc page is dated, and is not correct anymore. It is not clear how to set the various storageEncryptionMonitoringEffect-like (Policy names reference) parameters anymore. as of Sep. 2019, the Security Policy blade on this page does not point to the options mentioned on this page. Am I missing something?

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

ID: a224f020-9828-db10-d927-4f0bc875e0a6
Version Independent ID: d5d7dd34-0997-0338-0e10-1aa7ec40dc4a
Content: Working with security policies
Content Source: articles/security-center/tutorial-security-policy.md
Service: security-center
GitHub Login: @monhaber
Microsoft Alias: v-mohabe

@sonnycloudtp Thanks for the feedback! We will review and update accordingly.

@sonnycloudtp I checked the article and I believe the details for storageEncryptionMonitoringEffect-like (Policy names reference) parameters are deprecated and it may need removal from the article. The current list of controls in the policy assignment does not contain the Audit missing blob encryption for storage accounts option. Apart from that I do not see any other changes in the security policy screenshots. If we go to duplicate the assignment we see the following which tells us that the current option is indeed deprecated and hence its not available.

The security policy blade is also the same as i can see in my test lab . Since I do not have any management groups hence I do not see them and I only see the subscription in the security policy blade.

I will have the content author have this article completely evaulated with Product engineering and change this as needed. Please let us know in case you were referring to any other screenshot as well.
Thank you.

Hi @sonnycloudtp,
Thanks for letting us know about this issue. Since you raised your concerns this page has undergone a significant number of revisions.
I'm marking this as closed because I think everything you've raised has been addressed.
If you feel that there are still things that need updating, please reopen this issue and we'll handle them.
#please-close


Log org.hibernate at ERROR

Re: #1149
@swankjesse I presume this would work as a sensible default unless overridden in app-specific configs?

slf4j is a log API, not a logger. You'd still need a logging engine behind it. Log4j2 is the newest, with all the benefits of Logback plus some other niceties including minimal GC impact. There's almost no point in even talking about the original log4j, which is so outdated.
Hibernate uses JBoss Logging - another log bridge - that plays nice with most major logging engines, including Log4j2.

@maniksurtani so if I’m reading this right, we should:

Migrate from logback to log4j2 as a backend
Continue to use slf4j as a frontend

Yep.
On Wed, Aug 14, 2019 at 10:24 Jesse Wilson<EMAIL_ADDRESS>wrote:

@maniksurtani https://github.com/maniksurtani so if I’m reading this
right, we should:

Migrate from logback to log4j2 as a backend
Continue to use slf4j as a frontend

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cashapp/misk/pull/1151?email_source=notifications&email_token=AAALQKTS5KMJ7GFW6B7VVM3QEQ5VJA5CNFSM4ILOXOJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4JQHWQ#issuecomment-521339866,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAALQKXHPGCCC7ENQVVBQCLQEQ5VJANCNFSM4ILOXOJA
.

It doesn't make a difference to me, as long as we don't install 2 logging backends at the same time (that's what I removed recently), and as long as we end up logging JSON.

https://github.com/cashapp/misk/issues/1153


KeyManagerFactory should not hardcode JKS keystore type

Environment Details

Helidon Version: 2.1.0
Helidon SE or Helidon MP: MP
JDK version: 11.0.7
OS: Linux
Docker version (if applicable): N/A

Problem Description
I am trying to run Helidon in SSL mode with a third-party security provider. (Running with the standard JSSE provider is fine.) The security provide requires that the keystore used to initialize the SSL context is of a format provided by that security provider.
Current implementation of KeyManagerFactory doesn't support that; it hardcodes the keystore type that it creates from the private key file:
private static KeyManagerFactory buildKmf(KeyConfig privateKeyConfig) throws IOException, GeneralSecurityException {
....
KeyStore ks = KeyStore.getInstance("JKS");
....
}
This should be configurable like all the other SSL configuration properties. Replacing this with the desired keystore type allows the third-party provider to work properly. (And technically, there's no assurance that the JKS provider is installed in a particular JVM anyway.)

WebServerTls in WebServer, and SslContextBuilder in gRPC

@scottoaks17 - Is it sufficient to use the default keystore type of the current environment for your security provider?
Such as:
KeyStore ks = KeyStore.getInstance(KeyStore.getDefaultType());

The keystore is only used to initialize the key manager factory - not really something I would like to expose through configuration. So if the above code is sufficient, I would modify it.

Please see the referenced PR

I have merged the change. Please feel free to come back to us if this fix is not sufficient. The default keystore is configurable through Java security.


Exclude link-local IPv4s from editor host list.

IPv4 has link-local addresses like IPv6 (block <IP_ADDRESS>/16).
Those addresses should not be considered a valid option when selecting the remote_host setting for the debugger.

I might be missing something but why are link-local addresses not considered a valid option?
For example, if two Mac devices are connected directly via an Ethernet cable--when a DHCP server is not enabled--eventually they will self-assign link-local addresses which means its possible to create a connection without explicitly configuring anything.
While I've not used this approach with anything Godot-related yet, its still seems like it would a valid option.

they will self-assign link-local addresses which means its possible to create a connection without explicitly configuring anything.

Have you ever tried that out? In my very limited experience with the matter, I was not able to connect to a link-local address (<IP_ADDRESS>/16).
A friend of mine was in fact unable to listen/connect to it's own link-local address (on Windows).
We could change that if you can confirm it works.

I think this is OS-dependent. Also there might be multicast 224/8 addresses and other addresses which might not be wanted depending on particular system settings. The naive solution might break things, too.
I think currently the best bet would be

Have list of all listen-able addresses.
Have a helper function which filters these and reports them according to RFC. This thing might be already available and also can be implemented in user's application.
It is up to user to decide which addresses can be used or can't be used for listenning (UI option).
The user should be able to do final decision on what addresses to use. Godot can't handle all existing broken setups everywhere. But also there is no reason to prevent it from working on non-standard setups which work for other applications. However Godot can supply the information (list of addresses) and reasonable defaults.

Also there might be multicast 224/8 addresses and other addresses which might not be wanted depending on particular system settings.

@slapin it wouldn't make sense to list multicast addresses, as TCP can't work with multicast, so this is certainly not a problem.

2\. Have a helper function which filters these and reports them according to RFC. This thing might be already available and also can be implemented in user's application.

This is exactly what I'm trying to do here, this PR do not change the result from get_local_addreses, it just filter the value in editor settings.

3\. The user should be able to do final decision on what addresses to use. Godot can't handle all existing broken setups everywhere.

I don't think having a text edit there is a good idea. It would just be confusing to many people, and prone to errors. All for very exceptional cases (i.e. using editor-debugger connection on a broken network setup).
Command line options are not affected,
I think it's more important to have an 'listen for debugger' button instead, which you can use for any weird setup (and lunch your game app accordingly via CLI). And that yes, can have a line dit (pre-filled with last/default value, probably just a wildcard).
But this is up for debate of course :)

I agree with @Faless - having a simple button that works in 99% of cases is preferable as long as CLI options exist.
Note that we currently also exclude IPv6 link local adresses. IPv4 link local adresses in comparison are IMO both uncommon and nonstandard.
We can discuss adding UI options for more control over this, but as this is just for the Editor debugger, and only does for IPv4 (where again, link local addresses are esoteric anyhow) what is already done for IPv6, this is fine to merge by me.
We can discuss adding more elaborate handling or exposing UI options for this (maybe in a PR for that, or after having some testing done on whether this is actually wanted and working in theory), but we also don't want to overburden the user with too many options.

I think adding an option in network section of preferences will not hurt
(one of LANs
I use assigns windows auto-assign addresses (which became IPv4 "link local"
addresses)
and actually NATs them to outside world to avoid having DHCP server).
Not nice setup, but I guess quite common with older windows networks.
Patching again just for that is annoying.
On Wed, May 1, 2019 at 9:49 PM Max Hilbrunner<EMAIL_ADDRESS>wrote:

@mhilbrunner approved this pull request.
Fine to merge by me, as stated above :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/pull/27569#pullrequestreview-232701873,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAABPU3NBELUPBQYS6JZDYTPTHQZ5ANCNFSM4HCSMWJA
.


Add serviceAccountSelector and namespaceSelector to how-to docs (copy…

Deploy preview for calico ready!
Built with commit e692c449c449c63025ea3470ef0acc2ca917f8b0
https://deploy-preview-2922--calico.netlify.com


Failing Tests after Fork

I made a fork of the main branch today to take a look at the tests and Clarity costs, but when I ran npm i then npm test I get the following result:
Test Files  1 failed | 5 passed (6)
Tests  173 failed | 30 passed (203)
Start at  06:08:09
Duration  56.10s (transform 341ms, setup 108ms, collect 898ms, tests 53.91s, environment 799ms, prepare 171ms)

Did I miss a step in running the tests? Below is an example of one of the failures:
FAIL  tests/BNS-V2.test.ts > NAME-RENEWAL FUNCTION > This should fail to renew a name if the name is revoked
Error: actual value must be a Clarity "ResponseOk", received "ResponseErr" (err u109)

- Expected
+ Received

- ResponseOk
+ ResponseErr

 ❯ callRevealNamespace tests/BNS-V2.functions.ts:100:36
     98|     );
     99|   } else {
    100|     expect(revealNamespace.result).toBeOk(
       |                                    ^
    101|       Cl.bool(expectedReturnValue as boolean)
    102|     );
 ❯ Module.successfullyTwoStepRegisterANameInAnUnmanagedNamespace tests/BNS-V2.functions.ts:772:3
 ❯ tests/BNS-V2.test.ts:811

Hello, can you please try forking again? And redoing your steps

That fixed it, thank you!


Separate db refresh from tagpack ingest

Currently, materialized view updates and duplicate tag removal is performed as part of the tagpack ingest process. It would be better to handle that separately on demand (e.g., nightly). Therefore, I propose to implement the following commands that execute these actions:
tagpack-tool tagstore refresh_views
tagpack-tool tagstore remove_duplicates

Done; it is important to remember to run refresh_views regularly to maintain data consistency.
Also added a respective note to the README https://github.com/graphsense/graphsense-tagpack-tool/tree/develop#important-keeping-data-consistency-after-tagpack-insertion


Optimize toString method

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@37c1605). Click here to learn what that means.

@@            Coverage Diff            @@
##             master      #38   +/-   ##
=========================================
  Coverage          ?   87.97%
=========================================
  Files             ?       58
  Lines             ?      757
  Branches          ?       30
=========================================
  Hits              ?      666
  Misses            ?       91
  Partials          ?        0

Impacted Files
Coverage Δ

core/shared/src/main/scala/cron4s/expr/parts.scala
0% <ø> (ø)

...e/shared/src/main/scala/cron4s/expr/CronExpr.scala
20% <50%> (ø)

Continue to review full report at Codecov.

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


Outdated comment + note on blockMesh registration

Hi andy, noticed https://github.com/fenomas/noa/blob/d9fe5d1549bc4596c5756fdcac852c9b07e535f0/src/lib/registry.js#L102 has an outdated comment about the restrictions that used to be in place on number of block ids
Also, note on blockMesh registration: I noticed you were setting offsetting the x and z positions by 0.5 but not the y position - https://github.com/fenomas/noa/blob/15d8231902bfaa1c59f29bc3633596dc15701010/src/lib/objectMesher.js#L95 and https://github.com/fenomas/noa/blob/15d8231902bfaa1c59f29bc3633596dc15701010/src/lib/objectMesher.js#L249
Was there a reason for this? Otherwise, I found it pretty unintuitive - so could be good to change for accessibility purposes

Hi, thanks! I'll fix the comment.
For the location, mesh/entity positions are always assumed to be at the bottom center of the mesh/entity. I'm not sure that was the best option in retrospect, but it should work that way consistently throughout the engine.

mb, I'll leave it open till you've changed the docs


Readme updates

This does a couple of things:

Removes most of the content of the README, since all of this is now available in the actual documentation
Converts all of the documentation to RST from markdown.  This is a side-effect of using sphinx for documentation -- if it's a real pain I can write something to convert stuff back and forth (which actually wouldn't be a problem at all...)
Adds information on how to cite PyGBe
Adds a citation badge to the README
Updates how the documentation is auto-generated (simplified greatly since PyGBe is now Python 3)

I think it looks cleaner putting all the information related to the code in the documentation page.
My only concern is that is not really clear what they are going to find in the link we suggest for "more information", maybe saying something like "For installation guide, examples, documentation, and more go to [link]". Although, that phrase has a lot of nominalizations that I'm not sure how to avoid.


Fix remote shards balancer and remove unused variables

Description
Two changes here:

make sure the primary shard's AllocationStatus be set to DECIDERS_NO when it cannot be allocated to any nodes;
remove unused variables

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
[x] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[x] Public documentation issue/PR created

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@kotwanikunal can you take a look at this when you are available

@kotwanikunal can you take a look at this when you are available

Do iterate this to green please in the meantime.

Thanks @bugmakerrrrrr!

make sure the primary shard's AllocationStatus be set to DECIDERS_NO when it cannot be allocated to any nodes

This sounds like a bug. Can you provide details about when this can occur and how this change fixes it?

Thanks @bugmakerrrrrr!

make sure the primary shard's AllocationStatus be set to DECIDERS_NO when it cannot be allocated to any nodes

This sounds like a bug. Can you provide details about when this can occur and how this change fixes it?

Yes, this bug occur when all deciders return NO for each node, because we always set the throttled flag after iterating all nodes(https://github.com/opensearch-project/OpenSearch/blob/b974dfbe7208f41357ec7e8e20b77fafa99997a1/server/src/main/java/org/opensearch/cluster/routing/allocation/allocator/RemoteShardsBalancer.java#L447). I just delete this statement to fix it.

@kotwanikunal done

@bugmakerrrrrr Can you please rebase? :)


add eventName property to RCTEventEmitter

Summary

Enable to get eventName from RCTEventEmitter.

We can get eventName on subclass of RCTEventEmitter.

eventName is provided by addListener function from ReactNative.

Changelog
[General] [Added] -  From RCTEventEmitter, enable to get eventName provided by addListener function.
Test Plan

hello

Hi @ShogoSaito0607 Can you help me understand the use case for this? Thanks

Hey @ShogoSaito0607
Are you still interested in merging this?

Closing as the original author is unresponsive


Switch to the Criterion library for our benchmarks

This benchmark harness gives us nice graphs where it's easier to see how the performance varies with the input size.

Codecov Report

Merging #202 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #202   +/-   ##
=======================================
  Coverage   92.44%   92.44%
=======================================
  Files           4        4
  Lines         397      397
=======================================
  Hits          367      367
  Misses         30       30

Continue to review full report at Codecov.

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


Add Glenn's photo

This PR aims to add Glenn's photo to the repository.
Resolves #28.

LGTM!

LGTM!


feat(ReactComponentLibrary): Expose new stable implementations

Related issue
Closes #3044
Closes #3043
Overview
Expose experimental implementations as stable.
Link to preview
https://620f8cfadd0ed914212ef643--festive-wozniak-29a757.netlify.app
Reason

Prime code base for 3.x.x release. Replacing deprecated implementations with new stable ones and updating composite components to consume the new implementations.

Work carried out

[x] Remove deprecated components and update experimental namespace
[x] Update composite components to use new implementations
[x] Fix display bug with Drawer Story

Looks like we can get rid of react-responsive and @types/react-responsive now (was being used by Switch).

Looking great! 🥳
Tiny detail: https://620f8cfadd0ed914212ef643--festive-wozniak-29a757.netlify.app/?path=/docs/masthead--default
Can we change "Defence Digital Design System" to "MOD.UK Design System" on all stories please?
Also: wondering if we need both Panel and Card frame? I think we discussed getting rid of one of them, but that was a while back.
Thanks!


streamWriter.SetRow can't fill all cells in a row

Description
streamWriter.SetRow can't fill all cells in a row.
No value cell is filled.
Steps to reproduce the issue:
1.set style

style1, err := file.NewStyle(&excelize.Style{Fill: excelize.Fill{Type: "pattern", Color: []string{"#FFFF00"}, Pattern: 1}})
if err != nil {
fmt.Println(err)
}

2.stream and flush

row := make([]interface{}, 50)
for colID := 0; colID < 50; colID++ {
row[colID] = rand.Intn(640000)
}
for rowID := 2; rowID <= 100; rowID++ {
cell, _ := excelize.CoordinatesToCellName(1, rowID)
if err := streamWriter.SetRow(cell, row, excelize.RowOpts{StyleID: style1}); err != nil {
fmt.Println(err)
}
}
if err := streamWriter.Flush(); err != nil {
fmt.Println(err)
}

Describe the results you received:
streamWriter.SetRow can't fill cells have a value.
Describe the results you expected:
streamWriter.SetRow fills all cells in a row
Output of go version:
go1.17.6

Excelize version or commit ID:
v2.5.0

Environment details (OS, Microsoft Excel™ version, physical, etc.):
Windows 10, Excel 2016

Thanks for your issue. Please binding style for no-empty cells for each row, using
row[colID] = excelize.Cell{StyleID: style1, Value: rand.Intn(640000)}

instead of
row[colID] = rand.Intn(640000)

@xuri
I appreciate your quick reply.
That works for me!


Generated HTML report doesn't contain vulnarabilities

The whole feature section is empty. The json report is correct

Could you provide your json, or the docker image if it's publc?

Hi, sure!
I have tried with this image: bfops/ubuntu12
You can find the reports in both HTML and Json format from attachment!
reports.zip

Hi there,
it is so far not possible to generate html with content, i wrote a template parse the JSON report, if someone also needed, here is the code:

    <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap.min.css" integrity="sha384-1q8mTJOASx8j1Au+a5WDVnPi2lkFfwwEAa8hDDdjZlpLegxhjVME1fgjWPGmkzs7" crossorigin="anonymous">
    <link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.6/css/bootstrap-theme.min.css" integrity="sha384-fLW2N01lMqjakBkx3l/M9EahuwpSfeNvV63J5ezn3uZzapT0u7EYsXMjQV+0En5r" crossorigin="anonymous">

The report should work, I will investigate your image, why it's not working.

Hi @jgsqware , thanks.. checkout the sample link from hyperclair homepage in report section, it doesn't work either i think.. it is not really related to my image..

I second to @jaiwo99: HTML report does not work and contains only bottommost layer.
I dug around a bit and found following piece of code:
https://github.com/wemanity-belgium/hyperclair/blob/fd7248d1d00f5b72ac8269913f4aaaad9f85c9c9/clair/clair.go#L295
	// for _, l := range imageAnalysis.Layers {
For cycle is commented out that iterates over layers for some reason, so only bottommost layer is parsed into template.

+1 for fixing.
The json report is correct but not reader friendly
Html report needs fixing

using pre-release 0.4.0 works just fine & doesn't have the html reporting issue which was introduced in fd7248d1d00f5b72ac8269913f4aaaad9f85c9c9

Has this issue been fixed?

Unfortunately not.  Like I mentioned, 0.4.0 release works fine.  Feel free to check out my fork which has the fix here

I having the same problem; json report works fine but html report is blank.

As mentioned before, the HTML report only contains the information for the bottom-most layer.  This is due to an issue introduced in fd7248d.  Version 0.4.0 works fine but the report isn't as "pretty".


[Creator] Deploying multiple versions fail

When deploying multiple APIs attached to the same apiVersionSet, deployment may fail randomly due to any of the following reasons:

Since no dependencies exist between different versions, deployment happen in parrallel.
Failure may happen because: "An API with specified name already exists".
Failure may happen because: "An API with the same path already exists".

To reproduce this case, please consider the following simple config file:
https://gist.github.com/springcomp/cee9eb07720fd3633fbce42a93f49da5
I think both issues can be solved by:

Introducing an explicit dependency of subsequent versions to the main "original" API or to the previous version. This will make sure that each version is deployed sequentially indenpendantly to one another.

Versions are hosted into two sequential templates "initial" and "subsequent". It happens that the "initial" template for a version fails because another version of the API has the same path. I have not found a bug in the generated templates. However, one can circumvent this by specifying a dummy path in the "initial" template. Oddly enough, once the "initial" template succeeds, the "subsequent" template will overwrite the path to the correct value.

Triaged, will review and fix it

This issue is closed + it doesn't have a good explanation to the commits provided. Nothing to do here. Moving to to be released


Release schedule for 83

Release Request: <IP_ADDRESS>
Expected Release Date:
About 2022-05-08
Changes Included:

backup recovery mechanism based on ood-control http protocol (in ood-daemon service)
dynamic permission mechanism based on user token
app-manager function optimization
other bug fixes and performance optimization, etc.

release-notes: https://github.com/buckyos/CYFS/blob/main/doc/release-notes/release-notes-<IP_ADDRESS>.md


async package is missing from package.json

I know that his package is actually a dependency for loopback, and I am not sure why it doesn't get installed when running
   npm install

but it crashes the moment you try to run the server. I will add more issues if I figure something out.
Thanks

Please, reopen if this is still occurring in the latest version


attributes not working

Only message attribute in the tag cookie-law-banner is overrided.
<cookie-law-banner acceptButton="true" acceptText="Helloooo" message="custom message" .....

Solved. Had to write es 'acceptText' in this way 'accept-text'.
You should update the doc since is not super intuitive.

Thanks for your feedback


Add the heading of the raw GPS locations on iOS to the default position instead of relying purely on the compass for the heading

From @zezioen on February 12, 2016 10:2
When the UpdatePosition method is called it creates a new Location object and supplies it with the Latitude, Longitude, Accuracy, Altitude & Altitude Accuracy if available, Timestamp and Speed. It does not add the Heading supplied by the CLLocation by default.
The only way to get an 'heading' is by setting the 'includeHeading' in the StartListeningAsync to true but this does not report the heading of the GPS but where the user is pointing their device since it returns the compass heading.
The change I would like to see is to have the Compass heading be separate of the GPS heading and that the GeoLocator plugin reports the GPS heading on iOS instead of the Compass heading.
This issue doesn't seem to be an issue on Android as there the includeHeading doesn't trigger a compass heading but uses the real GPS Heading.
Copied from original issue: jamesmontemagno/Xamarin.Plugins#219

It looks like we are calling and setting the heading:
https://github.com/jamesmontemagno/Xamarin.Plugins/blob/master/Geolocator/Geolocator/Geolocator.Plugin.iOS/GeolocationSingleUpdateDelegate.cs#L123-L139
To TrueHeading not magnetic, so it looks correct. Reading through this: https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/LocationAwarenessPG/GettingHeadings/GettingHeadings.html
The only thing that I can see is that perhaps it needs to check to see if it should use the magnetic:
From iOS docs:
if (newHeading.headingAccuracy < 0)
      return;

   // Use the true heading if it is valid.
   CLLocationDirection  theHeading = ((newHeading.trueHeading > 0) ?
            newHeading.trueHeading : newHeading.magneticHeading);

   self.currentHeading = theHeading;
   [self updateHeadingDisplays];
}


new wrap: cmocka

Please create a new repo for cmocka (It's another gmock kind of library) https://cmocka.org/, I have a working wrap for this.

https://github.com/mesonbuild/cmocka


The ellipsis character is now recognized as punctuation

It is no longer selected by double-clicking. #7047

I restarted the CI build on this, if it's green I'll merge.


Video Recorder - Crashing

Upon starting the plugin in resizeable mode with stretched mode this error happens after crashing client.
2022-08-05 13:37:06 [Client] ERROR net.runelite.client.RuneLite - Uncaught exception:
java.lang.OutOfMemoryError: Java heap space
	at java.desktop/java.awt.image.DataBufferInt.<init>(Unknown Source)
	at java.desktop/java.awt.image.Raster.createPackedRaster(Unknown Source)
	at java.desktop/java.awt.image.DirectColorModel.createCompatibleWritableRaster(Unknown Source)
	at java.desktop/java.awt.image.BufferedImage.<init>(Unknown Source)
	at net.runelite.client.plugins.gpu.GpuPlugin.screenshot(GpuPlugin.java:1376)
	at net.runelite.client.plugins.gpu.GpuPlugin$$Lambda$1750/0x0000000100b06840.get(Unknown Source)
	at net.runelite.client.ui.DrawManager.processDrawComplete(DrawManager.java:84)
	at net.runelite.client.plugins.gpu.GpuPlugin.draw(GpuPlugin.java:1280)
	at as.z(as.java:56958)
	at as.run(as.java:340)
	at java.base/java.lang.Thread.run(Unknown Source)
2022-08-05 13:37:09 [pool-3-thread-1] WARN  c.videorecorder.VideoRecorderPlugin - Error while writing video frame
java.io.IOException: closed
	at java.desktop/javax.imageio.stream.ImageInputStreamImpl.checkClosed(Unknown Source)
	at java.desktop/javax.imageio.stream.ImageInputStreamImpl.getStreamPosition(Unknown Source)
	at com.videorecorder.video.avi.AVIWriter.getRelativeStreamPosition(AVIWriter.java:1674)
	at com.videorecorder.video.avi.AVIWriter$Chunk.<init>(AVIWriter.java:1426)
	at com.videorecorder.video.avi.AVIWriter$CompositeChunk.<init>(AVIWriter.java:1462)
	at com.videorecorder.video.avi.AVIWriter.writeProlog(AVIWriter.java:628)
	at com.videorecorder.video.avi.AVIWriter.ensureStarted(AVIWriter.java:471)
	at com.videorecorder.video.avi.AVIWriter.writeSample(AVIWriter.java:535)
	at com.videorecorder.video.avi.AVIWriter.write(AVIWriter.java:308)
	at com.videorecorder.VideoRecorderPlugin.screenshot(VideoRecorderPlugin.java:300)
	at com.videorecorder.VideoRecorderPlugin.lambda$toggleVideo$2(VideoRecorderPlugin.java:227)
	at net.runelite.client.util.RunnableExceptionLogger.run(RunnableExceptionLogger.java:41)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.base/java.lang.Thread.run(Unknown Source)

Upon starting the plugin

Does this really happen when you start the plugin or when you start a recording?

in resizeable mode with stretched mode

Do you play with a very big resolution? Does it not happen with stretched mode turned off?

happens to me also
java.lang.OutOfMemoryError: Java heap space
	at java.desktop/java.awt.image.DataBufferInt.<init>(DataBufferInt.java:75)
	at java.desktop/java.awt.image.Raster.createPackedRaster(Raster.java:467)
	at java.desktop/java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1032)
	at java.desktop/java.awt.image.BufferedImage.<init>(BufferedImage.java:324)
	at net.runelite.client.plugins.gpu.GpuPlugin.screenshot(GpuPlugin.java:1443)
	at net.runelite.client.plugins.gpu.GpuPlugin$$Lambda$2172/0x0000000100c94040.get(Unknown Source)
	at net.runelite.client.ui.DrawManager.processDrawComplete(DrawManager.java:84)
	at net.runelite.client.plugins.gpu.GpuPlugin.draw(GpuPlugin.java:1350)
	at bm.ac(bm.java:18558)
	at bm.run(bm.java:382)
	at java.base/java.lang.Thread.run(Thread.java:829)

On Pop-os! 22.04 which is Ubuntu using x.org .
Using mesa drivers on RX 580 and vanilla GPU plugin. Tested with stretched mode turned "on" and "off" and the result were the same. It  does crashes when I unfocus from the client, but not exactly instantaneously, more like, if I didn't unfocus it apparently does not crash.