Roadmap: Alpha Release

Below is a list of what is required for an Alpha release.
Necessary Basic Static Methods
I'm cherry-picking from current RxJS2

[ ] concat
[x] empty
[ ] from
[x] fromArray
[ ] fromEvent
[ ] fromEventPattern
[x] fromPromise
[ ] interval
[ ] just/value
[x] merge
[x] never
[x] of
[x] range
[x] return
[x] throw
[x] timer
[x] zip

Necessary Basic Operators
I'm cherry-picking operators from RxJS 2 for now. I'm trying to narrow it down to what's essential to implement.

[ ] buffer
[ ] bufferWithCount
[ ] bufferWithTime
[ ] catch
[ ] combineLatest
[ ] concat
[ ] concatAll
[x] flatMap
[ ] flatMapLatest
[x] filter
[ ] forkJoin
[ ] groupBy
[x] map
[x] mapTo
[x] merge
[x] mergeAll
[x] multicast
[x] observeOn
[x] publish
[x] reduce
[ ] repeat
[ ] retry
[ ] retryWhen
[ ] scan
[x] skip
[ ] skipUntil
[ ] subscribeOn
[x] take
[ ] takeUntil
[x] toArray
[ ] window
[ ] windowWithCount
[ ] windowWithTime
[ ] withLatestFrom
[x] zip
[x] zipAll

Necessary Support Types
(Not including Observable and Subscriber, which are a given)

[x] BehaviorSubject
[x] ConnectableObservable (multicast)

[x] refCount

[x] Subject
[ ] ReplaySubject

Schedulers

[ ] immediate
[ ] nextTick

Other Requirements

[ ] some basic documentation
[x] community code of conduct
[ ] install instructions
[x] build instructions
[x] basic build pipeline
[x] license
[x] Travis integration
[ ] npm publishing
[ ] solid version starting point (4.0.0-alpha?)
[ ] interop points from es-observable spec. (Observable.from and Observable.prototype[Symbol.observable]? TBD)
[ ] Namespace to Rx from RxNext

a partition operator would be useful when dealing with forms:
//split off empty queries to reset form data
const [queryStream, emptyQueryStream] = searchStream.partition(val => val.length > 1);
//search with values
const queryResultsStream = queryStream.flatMapLatest(val => youtube.search(val));
//reset results to empty
const emptyQueryResultsStream = emptyQueryStream.map(val => []);
//use in view
this.searchResults = queryResultsStream.merge(emptyQueryResultsStream)

@robwormwald probably a separate issue. But I think you could accomplish this with groupBy more effectively. searchStream.groupBy(x => x.length > 0) would break the values into two observables, but only if it had to.

Probably missing combineLatest static operator, since you have also static zip and static merge.

@staltz hah. Yah I thought of that while I was in the car on my way home

Do we have any guidelines for documentation? Is the intent to mimic the current RxJS' wiki documentation?

I have a (suuuuuper basic) dgeni er, generator setup im about to merge in for generating API docs from the codebase. It's got a liitle hook for "guides" or whatever else we might like to stick in alongside. I was sort of winging it until somebody came up with a better idea.

On Aug 25, 2015, at 5:55 PM, Jermy<EMAIL_ADDRESS>wrote:
Do we have any guidelines for documentation? Is the intent to mimic the current RxJS' wiki documentation?
—
Reply to this email directly or view it on GitHub https://github.com/ReactiveX/RxJS/issues/100#issuecomment-134781052.

i like dgeni.
On Tue, Aug 25, 2015 at 9:00 PM, Rob Wormald<EMAIL_ADDRESS>wrote:

I have a (suuuuuper basic) dgeni er, generator setup im about to merge in
for generating API docs from the codebase. It's got a liitle hook for
"guides" or whatever else we might like to stick in alongside. I was sort
of winging it until somebody came up with a better idea.

On Aug 25, 2015, at 5:55 PM, Jermy<EMAIL_ADDRESS>wrote:
Do we have any guidelines for documentation? Is the intent to mimic the
current RxJS' wiki documentation?
—
Reply to this email directly or view it on GitHub <
https://github.com/ReactiveX/RxJS/issues/100#issuecomment-134781052>.

—
Reply to this email directly or view it on GitHub
https://github.com/ReactiveX/RxJS/issues/100#issuecomment-134781552.

Updated to add checkboxes for performance tests

Updated window and buffer names

Moving the remaining perf test additions to their own issues and putting them on Initial Beta Release milestone.
I think we've done enough here, and we already have multiple projects using this library, so it's already being "Alpha'ed", so to speak. Time to move on....


Document that we only support Elastic Search 8  (latest major ES version)

Is your feature request related to a problem? Please describe.
ES 7 as a LEC output fails.
Describe the solution you'd like
Just document that we support only ES 8.
Additional context
2022-06-27 21:18:58 +0000 [error]: #0 config error file="fluentd/etc/fluent.conf" error_class=Fluent::ConfigError error="Using Elasticsearch client 8.2.2 is not compatible for your Elasticsearch server. Please check your using elasticsearch gem version and Elasticsearch server."
The client is unable to verify that the server is Elasticsearch. Some functionality may not be compatible if the server is running an unsupported product.
2022-06-27 21:18:58 +0000 [error]: Worker 0 finished unexpectedly with status 2
2022-06-27 21:18:58 +0000 [info]: Received graceful stop

Fix version in Gemfile to ES8
Change LOG_EXPORT_CONTAINER_OUTPUT to use elasticsearch-8 instead of just elasticsearch
Update docs


feat(#91): refactor method names and modifiers

Create separate data objects for method modifiers in XMIR representation.
Closes: #91

History:

feat(#91): remove outdated puzzle for the #91 issue
feat(#91): remove the puzzle for method name strategy
feat(#91): the first implementation of DirectivesMethodProperties
feat(#91): stabilize all unit tests
feat(#91): add exceptions to the DirectivesMethodProperties
feat(#91): add javadocs for DirectivesMethodProperties
feat(#91): check method metadata in tests
feat(#91): refactor classes
feat(#91): add refactoring todo

PR-Codex overview
This PR focuses on handling method parameters in the DirectivesMethod class. It includes changes to handle method parameters and generate correct XML representation of the class.
Detailed summary

Added handling of method parameters in DirectivesMethod class
Updated XML representation of methods to include method parameters
Removed unused imports

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)


Do you have recommendation for use with ros1 or ros1/ros2 bridge?

For groups that have quite a bit of a code-base in ros1 and are not ready to move to ros2, can this package be a practical solution if used in conjunction with the ros1/2 bridge? Or any other arrangement?

Hi @rojas70 ,
In gym-gazebo2 we make use of ROS2 specific implementations like the launch system, so it would be harder to replicate in a ROS1 scenario. But you can definitely create you own environments with your own launch system. I can give you instructions if you provide more details of your project.
If the robot you are using is a robotic arm, the examples available at ROS2Learn should be valid too.

@nzlz Thanks for the feedback!
We are working primarily with the baxter robot. What might be the main challenges in running with this system?

Are your simulation drivers optimized enough for fast reinforcement learning?
Launch system. You must substitute our launch system for a custom ROS1 launchfile execution.

You might find many difficulties or just a few, can't say more without knowing the details. I would recommend to use the MARA of course, which is the robot for which we give full support in gym-gazebo2 and ROS2learn. You would probably save a lot of time fixing/improving things we have already solved.
Even if you decide to work with other robots we will be happy to assist you. Just notice that we don't have much bandwidth to support external projects.

Feel free to reopen, closing for now.


ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Nope
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): pip
TensorFlow version (use command below): 2.3.0
Python version: 3.8.5
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: 10.1
GPU model and memory: NVIDIA GeForce GTX 970, 4GB

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
When I import TensorFlow from Python, a message is printed like below.

import tensorflow
Traceback (most recent call last):
File "C:\Users\y\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 64, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.

During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\y\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\tensorflow_init_.py", line 41, in
from tensorflow.python.tools import module_util as module_util
File "C:\Users\y\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\tensorflow\python_init.py", line 40, in
from tensorflow.python.eager import context
File "C:\Users\y\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\tensorflow\python\eager\context.py", line 35, in
from tensorflow.python import pywrap_tfe
File "C:\Users\y\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\tensorflow\python\pywrap_tfe.py", line 28, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\y\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 83, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\y\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\tensorflow\python\pywrap_tensorflow.py", line 64, in
from tensorflow.python._pywrap_tensorflow_internal import *
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
Failed to load the native TensorFlow runtime.
See https://www.tensorflow.org/install/errors
for some common reasons and solutions.  Include the entire stack trace
above this error message when asking for help.

Hopefully, it is not that serious matter to resolve.
Describe the expected behavior
Import TensorFlow successfully.
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.
If environment is equivalent, then the problem may be reproduced.
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

@starjasmine
Please refer to this comment, also, refer similar issues:
#36167 #36151 #36138 #36054 #36045 #36020 #36003 #35988 #35903 #35880 #35865 #35805 #35789 #35773 #35772 #35767 #35766 #35749 #35721 #35618 #35204 #39007
Thanks!

@Saduf2019 Ok, Thanks! 😃


Plugin doesn't work in IE9

Hi. After implementing it and watching it working in Firefox and Chrome, what was my surprise when i loaded my page (http://www.universoweb.com/jordiescandell/fotografia.php?idimagen=130) in IE9 and realised that the plugin doesn´t work in this browser. Then checked your jsfiddle version and it doesn´t work either (http://jsfiddle.net/CpFDm/). Checking the code in firebug and ie9 developer tool it seems that, in IE, the image doesn´t print the new height and width values "on the fly". Hope you can find a solution because the plugin works fine in firefox and chrome. Thanks in advance.

Hey guys, I get the same problem with IE9 here, as far as refreshing I noticed that actually it only works some times. Even on greddins example page. If you keep refreshing it will load sometime and other times the images are all the same size as their originals. Really hope there is a fix soon as this is a great plugin :) Thanks!


[Snyk] Security upgrade centos from 7 to centos8

This PR was automatically created by Snyk using the credentials of a real user.Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Changes included in this PR

test/test_install_script/centos7.dockerfile

We recommend upgrading to centos:centos8, as this image has only 489 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Some of the most important vulnerabilities in your base image include:

Severity
Priority Score / 1000
Issue
Exploit Maturity

614
Out-of-Bounds SNYK-CENTOS7-BINDLICENSE-2181405
No Known Exploit

614
Reachable Assertion SNYK-CENTOS7-BINDLICENSE-2182551
No Known Exploit

714
Buffer Overflow SNYK-CENTOS7-NSS-2308137
No Known Exploit

714
Buffer Overflow SNYK-CENTOS7-NSSSYSINIT-2308141
No Known Exploit

714
Buffer Overflow SNYK-CENTOS7-NSSTOOLS-2308139
No Known Exploit

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

fixes


DB2 for i interface with Athena

Hello! I am testing some connectivity between Athena and IBM i (aka AS400). Is this lambda function compatible with Athena? I've successfully deployed this function but it fails with Task Timed Out in Athena.

The Lambda function serves as a generic interface for IBM i. Integration with most data sources is possible, but your implementation will vary. The provided code has examples of queries to IBM i, but integration with any other components (in your case Athena) will largely depend on what you are trying to do / how you want to integrate

I cannot speak for Athena connectivity, but I can help with the DB2 interface given more details. For example,

Where is the Lambda function deployed?
Have you verified network connectivity between your environment and Db2?
How is the Lambda function invoked?
Have you already written your queries within the Db2 interface?
Which errors are you receiving?

Where is the Lambda function deployed? Not sure what that means. Could you please clarify?
Have you verified network connectivity between your environment and Db2? Yes, a VM instance in the same subnet is able to reach out to the DB2 for i hosted on premise.
How is the Lambda function invoked? Lambda function is invoked by Athena through its interface. At this point, no query is performed.
Have you already written your queries within the Db2 interface? No, the queries are written in Athena's console once connection is stablished.
Which errors are you receiving? Task time out. No other information is gives that helps identify the error.

Let me try to better explain how it is setup:

I've deployed the ECR and Lambda functions using deploy scripts.
I configured a data source in Athena pointing to the lambda function.
In Athena's query editor, when I select the data source associated with lambda function, it tries to retrieve database information (before I can even run a query) but fails with Tasked time out. These are the messages in CloudWatch:

I think there may be a misunderstanding in the usage of this repo. This repo allows you to make connections to Db2 from Lambda, but the query logic is still left up to the developer to implement.
It does not act as a pure connector between a source and a target, which seems like what you are trying to accomplish with Athena, but AWS provides documentation for implementing this. It's certainly a useful feature, and I'd be happy to incorporate any changes you make to expand this functionality.
Lastly, you have a TooManyRequestsException, which means that the deployed Lambda function is being invoked too often. I would disconnect the Lambda trigger from Athena, and work on invoking the Lambda function with test events to verify connectivity with Db2 prior to connecting a trigger. For more information, see the blog post.


Changing the template

to the PM mockup

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

Opened a new PR


build: skip fossa check if it fails to install

SUMMARY

Last week fossa command became flaky and failed to install. This blocked PRs from passing build and merging. A PR to fix this was opened (https://github.com/apache/incubator-superset/pull/9769) but it didn't fix it. Eventually fossa started working again. This PR introduces a check for the fossa command and logs, but does not fail the build, if the fossa command cannot be found.
How important is it to have the fossa check? I haven't had much experience with it, is it actively monitored. Should we fail the build if a fossa report cannot be generated?
If the fossa check is absolutely necessary, can we only run it when dependency files change, eg requirements*.txt, package*.json?
TEST PLAN

[x] build passes

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[ ] Introduces new feature or API
[ ] Removes existing feature or API

@mistercrunch would be great to get your feedback on this

Is there a way to retry the installation? I worry that this will allow PRs to slip in which might violate the rulez.

I suppose we could. I don't think it'll really fix it though, as when it was failing I reran the pr a couple times and it always failed. My guess is the script broke for a while then eventually got fixed.
How do we feel about conditionally running this only when dependency files change? I think that's a fair tradeoff in security/efficiency.

I believe the fossa requirement is only really necessary when we're publishing a new apache release, as we need to guarantee all the code is licensed properly. It's good to have it running on every PR so a new dependency that doesn't comply won't sneak in, but I don't think we'd actually be violating anything as long as it's run and passes prior to releases

Except for when someone bumps a lib :). I think it makes sense to limit its cadence to only run when a requirements.txt / package.json file changes. This will be tricky, however as we still want to require this check, and skipped checks can't be required...

We can skip the fossa step based on files changed. The whole job won't be skipped though, so it'll still run and register pass/fail for the required check.

Codecov Report

Merging #9814 into master will decrease coverage by 0.16%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9814      +/-   ##
==========================================
- Coverage   70.84%   70.67%   -0.17%
==========================================
  Files         588      585       -3
  Lines       30475    30427      -48
  Branches     3154     3152       -2
==========================================
- Hits        21589    21505      -84
- Misses       8773     8804      +31
- Partials      113      118       +5

Flag
Coverage Δ

#cypress
52.79% <ø> (-0.86%)
:arrow_down:

#javascript
59.25% <ø> (+0.22%)
:arrow_up:

#python
71.02% <ø> (ø)

Impacted Files
Coverage Δ

superset-frontend/src/setup/setupPlugins.ts
12.50% <ø> (+4.50%)
:arrow_up:

superset/datasets/commands/exceptions.py
92.15% <ø> (ø)

superset/views/core.py
75.13% <ø> (ø)

...et-frontend/src/SqlLab/reducers/getInitialState.js
33.33% <0.00%> (-16.67%)
:arrow_down:

superset-frontend/src/reduxUtils.js
76.47% <0.00%> (-10.30%)
:arrow_down:

superset-frontend/src/SqlLab/actions/sqlLab.js
61.13% <0.00%> (-5.68%)
:arrow_down:

...rontend/src/SqlLab/components/TabbedSqlEditors.jsx
76.22% <0.00%> (-5.60%)
:arrow_down:

...rontend/src/SqlLab/components/SqlEditorLeftBar.jsx
44.00% <0.00%> (-4.00%)
:arrow_down:

superset-frontend/src/SqlLab/reducers/sqlLab.js
37.44% <0.00%> (-3.30%)
:arrow_down:

...end/src/SqlLab/components/TemplateParamsEditor.jsx
88.57% <0.00%> (-2.86%)
:arrow_down:

... and 3 more

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 ed1d030...a649839. Read the comment docs.


[HOW-TO] Check when ExposureTime is set

Is there a way to check when the setting of ExposureTime has been applied?
Looking at https://github.com/raspberrypi/picamera2/blob/main/examples/controls_3.py There's just sleeps scattered around, but I'm trying to minimize that, avoid it or even be perfectly sure that it's applied. I guess I can keep taking pictures and comparing the metadata, but is there a better way?
Thanks!

There is actually work on this very subject underway at the moment and that should improve the situation here, though it's not quite ready yet.
In the meantime, your best bet is probably to call capture_request and look at the metadata for the values you wanted. Alternatively, if you can set the exposure while the camera is stopped then you're guaranteed to have those values as soon as the camera starts, though stopping and starting the camera is relatively slow.

I'm afraid to say that things haven't progressed. We did do an implementation that lets you know when settings have been applied, but we haven't been able to upstream this. We're going to bring this up again, but as you can tell, it's taking time.
Can you say anything more about your application? There are quite a few folks who have been able to pipeline exposure changes frame by frame so that they can mostly get them to change "back to back". Would that help?

The idea is that you have a list of exposures/gains that you want.
Every time a frame comes back you check if it's one of the ones you wanted. And you also set the controls to request the next exposure/gain pair from your list that you haven't seen yet. So you're always cycling through that list of exposures/gains that you haven't seen yet. Mostly they come back in the order you want but it's not guaranteed because interrupt timing can occasionally cause you to fail to apply a new exposure.
There's some code here:
https://github.com/raspberrypi/picamera2/issues/399#issuecomment-1311590132
The work that I referred to above gives you a tidier way of doing this.


What does options parameter in built-in events means?

Hi!
http://backbonejs.org/#Events-catalog
What does options last parameter in built-in events means?
Is it the same value passed via method. I mean, if in some method like set, add, is passed the parameter options, then this parameter is passed as the las parameter of event handler?
I think that is not specified well.
Thanks!

As far as I understand, those are the options that are passed into the function that triggers the event.
So when you add a model to a collection like this:
let collection = new Collection();
collection.add({id: 10}, {someOption: 'with some value'});

The triggered add even on collection will have {someOption: 'with some value'} in it's optionsparameter.

Ok! thanks.


feat(getFeatureVariable): Add getFeatureVariableBoolean, getFeatureVariableDouble and getFeatureVariableInteger API

Summary

Add GetFeatureVariableBoolean as a function in client.go
Add GetFeatureVariableDouble as a function in client.go
Add GetFeatureVariableInteger as a function in client.go

Tests

Unit tests in client_test.go

Issues
OASIS-5006

@yasirfolio3 I've created a new branch we should be merging all the feature management work into. It is called fm-beta please open this PR against it. Also please make sure that we are running unit and FSC tests on PRs to that branch as well.

i've rebased the PR against fm-beta, i see 254 files changed? is this correct?

@yasirfolio3 I've created a new branch we should be merging all the feature management work into. It is called fm-beta please open this PR against it. Also please make sure that we are running unit and FSC tests on PRs to that branch as well.

closing this PR, have created a clean pr #78 for this.


[Event Request] Table 39 - Purchase Line - OnAfterCalcInternalLeadTimeDays

Requesting 1 new event publisher on table 39 - Purchase Line
Event
LOCAL [IntegrationEvent] OnAfterCalcInternalLeadTimeDays(PurchaseLine : Record "Purchase Line";PurchDate : Date;VAR TotalDays : DateFormula)
Execution
[External] InternalLeadTimeDays(PurchDate : Date) : Text[30]
EVALUATE(
  TotalDays,'<' + FORMAT(CALCDATE("Safety Lead Time",CALCDATE("Inbound Whse. Handling Time",PurchDate)) - PurchDate) + 'D>');

>>> New Code
OnAfterCalcInternalLeadTimeDays(Rec,PurchDate,TotalDays);
<<< New Code End

EXIT(FORMAT(TotalDays));

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Load SSL certificate according to git config

This PR addresses #487.
It covers the scenarios, when sslCert configured in .gitconfig points either to a certificate with private key in a keychain, or to a file, containing both public and private keys.
One thing missing is sslKey support - if our .gitconfig specifies sslCert, containing just the public part, and sslKey, containing the private key, the current PR doesn't load it. Main reason being, is that dotnet currently does not support easy handling of PEM files. I'll create a separate PR addressing that, as I believe it will lead to much more discussins.

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

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

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

@jrbriggs I think I've addressed all of the comments above. Are there any other outstanding actions, that I should take, before we can merge this PR?

There's a couple of stylecop warnings to fix.

Rebased on latest master to prevent merge-conflicts.

Thanks for the contribution, @turbonaitis !


[Issue] 5.0.5 issue

Hi Ivan, and thanks a lot for your work.
You have been updated to 5.0.5 but we can't do notificationData.showAlertOpenSettingsWhenPermissionDenied = false, because is inaccessible due to 'internal' protection level.
And I have small request, can you add Bluetooth Permission for iOS 13?
Thanks a lot

Yes, true. I publish 5.0.6.
Sorry for this.
Yes, I am soon add Bluetooth, maybe tomorrow.

About Bluetooth, you can check it in #134 issue


Remove explicit usage of ComponentVector in profile

It is the only place in this repo that depends on ComponentArrays.jl. Removing it can get rid of the package, which seems to be a good thing.
https://github.com/Yuan-Ru-Lin/HEPAnalysisUtils.jl/blob/52b1fc4185db57d7873ae92e25b2547eb5ac3a69/src/fit.jl#L17

Resolved in https://github.com/Yuan-Ru-Lin/HEPAnalysisUtils.jl/releases/tag/v0.5.1

The idea is to realize the argument of f doesn't need to be a ComponentArray. It just needs to support getproperty and a NameTuple will do.
Constructing a NameTuple is as simple as (; pois..., nuisances...) and so removing ComponentVector before the parenthesis will keep things working.


Bump vite in /End_to_end_Solutions/AOAISearchDemo/app/frontend

Bumps vite from 4.2.2 to 4.2.3.

Release notes
Changelog
Commits

updated-dependencies:

dependency-name: vite dependency-type: direct:development ...

Purpose

...

Does this introduce a breaking change?

[ ] Yes
[ ] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

tes


Create test framework for testing

As of writing we already have some commands outputting the correct values based on the test data, eg:
$ zig build run -- t test/data/test1/output_llvm-ar_gnu.a
input1.txt
input2.txt

$ zig build run -- t test/data/test2/output_llvm-ar_gnu.a
input1.txt
input2.txt
input3_that_is_also_a_much_longer_file_name.txt
input4_that_is_also_a_much_longer_file_name.txt

As we add features that replicate the functionality of llvm-ar - it would be good to have a set of tests we can use to both test for:

regression
features to be implemented

It should be quite simple. For each command using some of the example files to both parse/produce archives and then test those against what was produced by llvm-ar for the same inputs.
Was we only of the t command working (in a very limited way) so far - for the purposes of this issue focusing on that could be a good place to start.
Using what is generated for #1.

I am happy to look into this! I will have a look how llvm-ar implements tests and try to recreate that

I wouldn't start with that - look at how tests are normally done for zig projects. I terms of existing ar implementations, for now I would recommend ignoring them (or only treating them as a black box). The goal isn't to make a copy of an existing implementation but write something new in zig that's as simple as possible but does the same job.

But otherwise so feel free to work on this! I'm looking forward to seeing what you come up with. This is also related to #5.

Ok makes sense! Thanks :)

I've made a little start on this for the most simple case: https://github.com/moosichu/zar/commit/9b06af00f57bc6833d44af729a91d1a948954d3d
(BSD tests are currently commented out because they aren't working - that needs investigating).
However this is very bare-bones, so feedback & fleshing this out to cover the other operations we support as well would be great.

I'll take a look, but not before thursday!


Added the contact form

Fixes the issue #123
I have also added a footer link which works properly
Also the form have hover effects

@subhadipbhowmik If there is no problem, please accept the PR

@subhadipbhowmik i have resolved the conflicts.


Why i've this error message "Problem 1 - Conclusion: don't install jenssegers/mongodb v3.6.4" in my laravel project 7.20.0 ?

When I try to require the package  with composer, I have this error message in my Laravel version 7.20.0 project 😕 :

Installation request for jenssegers/mongodb ^3.6 -> satisfiable by jenssegers/mongodb[v3.6.0, v3.6.1, v3.6.2, v3.6.3, v3.6.4].
- Conclusion: don't install laravel/framework v7.20.0
- jenssegers/mongodb v3.6.0 requires illuminate/support ^5.8|^6.0 -> satisfiable by laravel/framework[5.8.x-dev, 6.x-dev], illuminate/support[5.8.x-dev, 6.x-dev, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9, v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.1.0, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.10, v6.18.11, v6.18.12, v6.18.13, v6.18.14, v6.18.15, v6.18.16, v6.18.17, v6.18.18, v6.18.19, v6.18.2, v6.18.20, v6.18.21, v6.18.22, v6.18.23, v6.18.24, v6.18.25, v6.18.26, v6.18.27, v6.18.28, v6.18.29, v6.18.3, v6.18.30, v6.18.31, v6.18.4, v6.18.5, v6.18.6, v6.18.7, v6.18.8, v6.18.9, v6.2.0, v6.3.0, v6.4.1, v6.5.0, v6.5.1, v6.5.2, v6.6.0, v6.6.1, v6.6.2, v6.7.0, v6.8.0].
- Can only install one of: laravel/framework[5.8.x-dev, v7.20.0].
- Can only install one of: laravel/framework[6.x-dev, v7.20.0].
- don't install illuminate/support 5.8.x-dev|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.11|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.12|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.14|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.15|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.17|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.18|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.19|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.2|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.20|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.22|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.24|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.27|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.28|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.29|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.3|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.30|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.31|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.32|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.33|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.34|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.35|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.36|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.4|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.8|don't install laravel/framework v7.20.0
- don't install illuminate/support v5.8.9|don't install laravel/framework v7.20.0
- don't install illuminate/support 6.x-dev|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.0.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.0.1|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.0.2|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.0.3|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.0.4|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.1.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.10.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.11.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.12.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.13.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.13.1|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.14.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.15.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.15.1|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.16.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.17.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.17.1|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.1|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.10|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.11|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.12|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.13|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.14|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.15|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.16|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.17|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.18|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.19|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.2|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.20|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.21|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.22|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.23|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.24|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.25|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.26|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.27|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.28|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.29|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.3|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.30|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.31|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.4|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.5|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.6|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.7|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.8|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.18.9|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.2.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.3.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.4.1|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.5.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.5.1|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.5.2|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.6.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.6.1|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.6.2|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.7.0|don't install laravel/framework v7.20.0
- don't install illuminate/support v6.8.0|don't install laravel/framework v7.20.0
- Installation request for laravel/framework (locked at v7.20.0, required as ^7.0) -> satisfiable by laravel/framework[v7.20.0].

Installation failed, reverting ./composer.json to its original content.

Unfortunately, the maintainers are in no rush to introduce version 7 support. You can use alpha

I fixed the problem by installing the development version and it works:
composer require jenssegers/mongodb:dev-develop

This has been discussed multiple times, closing.


Remove environment variables from crash.log?

Howdy! I just noticed that the crash.log dump file spits out a user's entire environment. I'm concerned that, in the event that a user has sensitive information (GitHub tokens, AWS tokens, etc), these variables will be leaked.
Poking around at random issues in this repo, I see a few places where people just straight up paste the log: https://github.com/nanoc/nanoc/issues/199, https://github.com/nanoc/nanoc/issues/405.
Would it be possible to just omit this information?
/cc @mastahyeti

Yup, totally makes sense. Having the environment available in crash.log wasn’t as useful as I imagined in the first place, and when it’s necessary, we can still get hold of it by other means.
PR: #800

Fixed in #800. This’ll be part of the 4.1.2 release.


🚀 RELEASE: v1.0.0-alpha.1

Few minor updates and patches to the project.

Big thanks to @jofftiquez and @princejoogie will enabling us to jump to the alpha version!
Let's add the remaining HTTP API (#3) so we can release the alpha version.


Performing FRF - Vibration

I am trying to use your package pyFRF to perform an FRF for ODS measurement.
I need to perform FRF between 2 data from accelerometer, which is in g unit.
I need as output H1 and phase information.
Reading the examples at the  “showcase page” (https://github.com/openmodal/pyFRF/blob/master/Showcase pyFRF.ipynb) I get confused in some points:

What are the order and mandatory input in the pyFRF?
- i.e – frf = FRF( sampling frequency, excitation, response, excitation window, response type, response window) ? or…
- i.e – frf = FRF(sampling frequency, fft length, excitation window, response window, response type, weighting , n_averages)  -  in this case it is not clear where I have to input excitation and response signal?

What are the response type option?

Others question that you can help me if possible:

Can I integrate the acceleration signal and perform ODS? (i.e velocity unit)
What is the units when I perform FRF based on the same measurement?
- Since we are splitting the same unit, I am pretty sure that is non dimensional….although I was looking for some technical material that can show how to deal with the real and imaginary part of the equations and perform the dimensional analysis in this equation.

Any help it is welcome.

Dear @guiamuchastegui
pyFRF has the capability to perform FRF in two ways:

FRF( sampling frequency, excitation, response, excitation window, response type, response window) is the typical usage for obtaining a FRF after the measurement is finished
FRF(sampling frequency, fft length, excitation window, response window, response type, weighting , n_averages) is used to perform FRF during your measurement. In this case you add data via the method .add_data(). With this you can continuously update to the user interface (after each measurement a new averaged FRF can be shown). In the showcase, the data is added in cell 35.

Response options? Please see the code:

_EXC_TYPES = ['f', 'a', 'v', 'd', 'e']  # force for EMA and kinematics for OMA
_RESP_TYPES = ['a', 'v', 'd', 'e']  # acceleration, velocity, displacement, strain

ODS?
Research the cell 26: call the method .get_ods_frf()
Units?
If you are using SI units which correspond to the excitation and response node you defined when creating the instance of object FRF, all units should be handled accordingly. See cell 26 on how to access: accelerance, mobility, receptance.


WeChat and QQ  does not apply any text or Link

I am using Cordova and plugin 4.3.0 on Android 4.3 with the following code:
window.plugins.socialsharing.share('Optional message','Optional title',http://www.baidu.com/img/bdlogo.gif, 'http://www.baidu.com');
It works well with sinaweibo but it just pass the image to Wechat(微信) and QQ without passing message and link. Can give me some hints? Thanks a lot!

Hi,
I have the same problem in wechat, when I try to share a URL doesn't appear (only the image)
Did you solve this problem?
Thanks

I hava the same problem


Use offsets for parameters of signature help

An option to use offsets was added in LSP 3.14, we should take advantage of it.

Landed in r362481


program stuck in "killing discord" [already tried the suggested methods]

Describe the bug
i was seeing the video on NTTS's ggsans to the old discord font and when i tried to install it it stuck on the killing discord page for hours.
To Reproduce
Steps to reproduce the behavior:

Go to 'the better discord installer'
Click on 'i agree the license and next'
Click on 'install better discord and next'
See error
error:

Starting Install...
Creating required directories...
✅ Directory exists: C:\Users\ANANDHI\AppData\Roaming\BetterDiscord
✅ Directory exists: C:\Users\ANANDHI\AppData\Roaming\BetterDiscord\data
✅ Directory exists: C:\Users\ANANDHI\AppData\Roaming\BetterDiscord\themes
✅ Directory exists: C:\Users\ANANDHI\AppData\Roaming\BetterDiscord\plugins
✅ Directories created
Downloading asar file
✅ Package downloaded
Injecting shims...
Injecting into: C:\Users\ANANDHI\AppData\Local\Discord\app-1.0.9008\modules\discord_desktop_core-1\discord_desktop_core
✅ Injection successful
✅ Shims injected
Restarting Discord...
Attempting to kill Discord
Expected behavior
mentioned in the NTTS's channel
Screenshots

System Information:

OS: Windows

Make sure you have the latest version of the installer from the releases page
Then in order, try:

Once the installer reaches "Attempting to kill Discord",
then Alt + f4 on Discord
then exit the installer
and reopen Discord
Reinstall Discord following this guide then retry the installer
Try out a manual install

i have already done a reinstall of discord but thank you for taking your time to suggest this.

thanks the manual install worked, thank you for your time.


Allow passing a custom elasticsearch backend url to use for log forwarding

Description
Added the ability for a user to pass an external elasticsearch url to use for a custom log forwarder backend.
Fixes

Seems like with the current implementation are not initially available
export CUSTOM_ES_URL=blablabla
$ ./deploy_logging_stack.sh
Wed 7 Apr 10:45:41 UTC 2021: Checking if oc client is installed
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2021-04-05-174735   True        False         17h     Cluster version is 4.8.0-0.nightly-2021-04-05-174735
Wed 7 Apr 10:45:44 UTC 2021: Deteting openshift-logging/openshift-operators-redhat namespaces if exists
Wed 7 Apr 10:45:51 UTC 2021: Installing the necessary objects for setting up elastic and logging operators and creating a cluster logging instance
Wed 7 Apr 10:45:51 UTC 2021: Creating cluster logging with custom elasticsearch backend
namespace/openshift-operators-redhat created
namespace/openshift-logging created
operatorgroup.operators.coreos.com/openshift-operators-redhat created
operatorgroup.operators.coreos.com/cluster-logging created
subscription.operators.coreos.com/cluster-logging created
unable to recognize "STDIN": no matches for kind "ClusterLogging" in version "logging.openshift.io/v1"
unable to recognize "STDIN": no matches for kind "ClusterLogForwarder" in version "logging.openshift.io/v1"

Seems like with the current implementation some CRDs are not initially available
$ export CUSTOM_ES_URL=blablabla
$ ./deploy_logging_stack.sh
Wed 7 Apr 10:45:41 UTC 2021: Checking if oc client is installed
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.8.0-0.nightly-2021-04-05-174735   True        False         17h     Cluster version is 4.8.0-0.nightly-2021-04-05-174735
Wed 7 Apr 10:45:44 UTC 2021: Deteting openshift-logging/openshift-operators-redhat namespaces if exists
Wed 7 Apr 10:45:51 UTC 2021: Installing the necessary objects for setting up elastic and logging operators and creating a cluster logging instance
Wed 7 Apr 10:45:51 UTC 2021: Creating cluster logging with custom elasticsearch backend
namespace/openshift-operators-redhat created
namespace/openshift-logging created
operatorgroup.operators.coreos.com/openshift-operators-redhat created
operatorgroup.operators.coreos.com/cluster-logging created
subscription.operators.coreos.com/cluster-logging created
unable to recognize "STDIN": no matches for kind "ClusterLogging" in version "logging.openshift.io/v1"
unable to recognize "STDIN": no matches for kind "ClusterLogForwarder" in version "logging.openshift.io/v1"

@rsevilla87 Yeah I opened an issue about that here: https://github.com/cloud-bulldozer/e2e-benchmarking/issues/154
Effectively we're trying to apply the cr to quickly after apply the crd. If you re-run it now it will work without an issue. I was going to look into fixing that outside of this PR as it is pre-existing to this.


Do we need the original output any more? I believe the history output has been verified.

@saraqzhang https://github.com/GEOS-ESM/GEOSldas/blob/f739a549f9c57b8ff22836371bbd2d733d601e0c/src/Components/GEOSldas_GridComp/GEOSlandassim_GridComp/GEOS_LandAssimGridComp.F90#L1748-L1759

Weiyuan,
I think this call also outputs ObsFcstAna  which goes to ana/.   One way to avoid redundant binary output of incr is to replace the argument “out_incr” in call output_incr_etc(…) with a local out_incr_bin = 0 ( false) , then it will only do the ObsFcstAna part, not the incr part.  I did this in my sandbox version.
Sara
From: Weiyuan Jiang<EMAIL_ADDRESS>Reply-To: GEOS-ESM/GEOSldas<EMAIL_ADDRESS>Date: Monday, February 24, 2020 at 12:49 PM
To: GEOS-ESM/GEOSldas<EMAIL_ADDRESS>Cc: "Zhang, Sara (GSFC-610.1)[SCIENCE APPLICATION INTL CORP]"<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: [EXTERNAL] [GEOS-ESM/GEOSldas] Do we need the original output any more? I believe the history output has been verified. (#125)
@saraqzhanghttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_saraqzhang&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=KoVvZJf1tL93veVIrV9pMZckCIcoPY33GgfPxR9EiGY&m=RU-R0gvKR-gyeIjCOhPdlW-C66beSnzypj9RgVMpt_I&s=hebNYQ-GTlT_SIMihlAEleSmURKUTDDUBQzklrxl5EI&e= https://github.com/GEOS-ESM/GEOSldas/blob/f739a549f9c57b8ff22836371bbd2d733d601e0c/src/Components/GEOSldas_GridComp/GEOSlandassim_GridComp/GEOS_LandAssimGridComp.F90#L1748-L1759https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_GEOS-2DESM_GEOSldas_blob_f739a549f9c57b8ff22836371bbd2d733d601e0c_src_Components_GEOSldas-5FGridComp_GEOSlandassim-5FGridComp_GEOS-5FLandAssimGridComp.F90-23L1748-2DL1759&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=KoVvZJf1tL93veVIrV9pMZckCIcoPY33GgfPxR9EiGY&m=RU-R0gvKR-gyeIjCOhPdlW-C66beSnzypj9RgVMpt_I&s=J58ZjU2yKbYTyqP1iDaNJovKV-47ingmfLMpIfk2iwg&e=
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_GEOS-2DESM_GEOSldas_issues_125-3Femail-5Fsource-3Dnotifications-26email-5Ftoken-3DAM3JFNVSRLEJTPMMDVF6U7LREQCCXA5CNFSM4K2NFSN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IPZY7ZA&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=KoVvZJf1tL93veVIrV9pMZckCIcoPY33GgfPxR9EiGY&m=RU-R0gvKR-gyeIjCOhPdlW-C66beSnzypj9RgVMpt_I&s=KupQ1I-xf8-JPt8PfyEu-CJi87lbgtpUhnZGLR2HDaY&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AM3JFNQ6QSHA2JJKOY46EXDREQCCXANCNFSM4K2NFSNQ&d=DwMCaQ&c=ApwzowJNAKKw3xye91w7BE1XMRKi2LN9kiMk5Csz9Zk&r=KoVvZJf1tL93veVIrV9pMZckCIcoPY33GgfPxR9EiGY&m=RU-R0gvKR-gyeIjCOhPdlW-C66beSnzypj9RgVMpt_I&s=xThuo8TvQQPNDxHSRvmpAEVdttmvB2UWXUHRnzfjmMw&e=.

There is a bug in potentially having out_incr=true while HISTORY.rc doesn't call for catch_progn_incr output.
@weiyuan-jiang  will fix this.

@weiyuan-jiang :  If we're no longer using "out_incr" (and "out_incr_format"), the subroutine output_incr_etc() is essentially a wrapper for output_ObsFcstAna().  It would be helpful to get rid of output_incr_etc() and replace the call to it with the couple of things done within the "if (out_ObsFcstAna)" block.  Let me know if you have questions.

@weiyuan-jiang @gmao-rreichle :   "out_incr" is set in .nml,  user needs to check both .nml and History.rc.   It may be better to eliminate  "out_incr"  in the code and always calculate incr_ens_avg ( currently controlled by out_incr=true) . then let history.rc alone controls whether to output incr.

addressed with pull request #132


biribussi's code in the current directory structure w conversions

Need testing on all

accidental duplicate of #12, please continue that work here

Can we insert an Auto press? What happens with these clicks if there's a crash to main screen?

If we add an auto click into the cycle it would enable and disable auto battle with every press. Could work, but i was trying to keep clicks to a minimum since i personally think in explorations more clicks = more crashes. If a crash occurs i don't think it would change anything, even with the auto click, but that will affect movement, i'll test it a little right now

Maybe i got it with diagonal inputs, should restart on crash and not press the "support" or square enix page on title screen, while continually move the pg and pressing auto battle. Can you give it a go Kas? Unfortunately i must be off for a while, tested in memu 1280x720 and it's working right now. I still don't know how to modify files without creating a new pull request, so i'll leave you a pastebin with the new script here https://pastebin.com/EjNkJvG5

Generated new commits in this branch with your latest code. I cannot test right now because I'm at work but I'll go ahead and merge if you say it's working.


Fixed topic regex pattern and added search by topic links after save

This PR fixes frontend topic length validation (single char topic cause error prompt ) and I added search links related to #4505
Done button behavior

before:

after:

Codecov Report

Merging #9219 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #9219      +/-   ##
==========================================
- Coverage   41.04%   41.04%   -0.01%
==========================================
  Files         554      554
  Lines       72410    72410
==========================================
- Hits        29723    29722       -1
- Misses      38935    38937       +2
+ Partials     3752     3751       -1

Impacted Files
Coverage Δ

modules/task/migrate.go
25% <0%> (-3.95%)
:arrow_down:

models/pull_list.go
57.74% <0%> (-2.12%)
:arrow_down:

models/error.go
32.67% <0%> (-1.79%)
:arrow_down:

modules/log/event.go
64.61% <0%> (-1.03%)
:arrow_down:

models/repo.go
47.87% <0%> (+0.05%)
:arrow_up:

models/gpg_key.go
55.59% <0%> (+0.55%)
:arrow_up:

modules/migrations/gitea.go
9.45% <0%> (+0.63%)
:arrow_up:

models/repo_list.go
74.07% <0%> (+0.92%)
:arrow_up:

modules/migrations/migrate.go
25.4% <0%> (+1.62%)
:arrow_up:

modules/indexer/indexer.go
55.26% <0%> (+10.52%)
:arrow_up:

Continue to review full report at Codecov.

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


Artifact Not Found: Kotlin 1.5.31

Hi, i am trying to integrate the library with a sample project of KMM application, but couldn't. I am facing ArtifactNotFoundException
Failed building KotlinMPPGradleModel
org.gradle.internal.resolve.ArtifactNotFoundException: Could not find bignum-0.3.2-samplessources.jar (com.ionspin.kotlin:bignum:0.3.2).
Searched in the following locations:
    https://repo.maven.apache.org/maven2/com/ionspin/kotlin/bignum/0.3.2/bignum-0.3.2-samplessources.jar
	at

Below is my build.gradle.kts:
kotlin {
    android()
    ios()
    iosSimulatorArm64()

    sourceSets {
        val commonMain by getting {
            dependencies {
                implementation("org.jetbrains.kotlinx:kotlinx-serialization-json:1.3.0-RC")
                implementation("com.ionspin.kotlin:bignum:0.3.2")
            }
        }
        val commonTest by getting {
            dependencies {
                implementation(kotlin("test-common"))
                implementation(kotlin("test-annotations-common"))
            }
        }
        val androidMain by getting
        val androidTest by getting {
            dependencies {
                implementation(kotlin("test-junit"))
                implementation("junit:junit:4.13.2")
            }
        }
        val iosMain by getting
        val iosSimulatorArm64Main by getting
        val iosTest by getting
    }

    cocoapods {
        framework {
            // Configure fields required by CocoaPods.
            summary = "Some description for a Kotlin/Native module"
            homepage = "Link to a Kotlin/Native module homepage"
            // Framework name configuration. Use this property instead of deprecated 'frameworkName'
            baseName = "SharedCode"
        }
    }
}

Below is my project build.gradle.kts:
buildscript {
    repositories {
        google()
        gradlePluginPortal()
        mavenCentral()
    }
    dependencies {
        classpath("org.jetbrains.kotlin:kotlin-gradle-plugin:1.5.31")
        classpath("com.android.tools.build:gradle:7.0.2")
    }
}

allprojects {
    repositories {
        google()
        mavenCentral()
    }
}

tasks.register("clean", Delete::class) {
    delete(rootProject.buildDir)
}

I am currently using M1 Mac with Android Studio:
Android Studio Arctic Fox | 2020.3.1 Patch 2
Build #AI-203.7717.56.2031.7678000, built on August 27, 2021
Runtime version: 11.0.10+0-b96-7249189 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 11.6
GC: G1 Young Generation, G1 Old Generation
Memory: 2048M
Cores: 8
Registry: external.system.auto.import.disabled=true
Non-Bundled Plugins: org.jetbrains.kotlin, com.jetbrains.kmm

What am I missing? Kindly assist please .. Thank you

Hi @avjiang, usually when Android Studio or IntelliJ Idea report this  "Could not find ... ...-samplessources.jar" it means that you have targets in your project that the library doesn't support. It's really an unhelpful message, but if you run ./gradlew build from the project root it should give you a more insightful error.
In any case I'm pretty sure the problem is iosSimulator64(), it;s a new target added in kotlin 1.5.30 and the library is still on 1.5.10 so I never built for that target.
As a temporary workaround you can remove the iosSimulator64() and it should build, and I'll try to bump the version of the library and add new targets to the build as soon as possible, although it will be available only in the snapshot at first.
Just for the record here are the new targets from kotlin 1.5.30:

macosArm64
iosSimulatorArm64
watchosSimulatorArm64
tvosSimulatorArm64

Ahh.. understand. Thanks mate for the information! Really appreciate the fast response.

My pleasure! Let's keep the issue open until I release the version with the new targets and then we can close it.

Hey @avjiang I've added new targets, they are available in snapshot version 0.3.3-SNAPSHOT. Tell me if you encounter any problems, especially since these new targets are for M1 hardware which I currently don't own. Forgot to say, thanks for reporting the issue in the first place!

hi @ionspin thanks for the quick progress. in the meantime i am still waiting for the other library to add support for the architecture. so i may not able to test it now. will update u again once i have tested it. thanks!


Office365 -cli and iPad

Hi
How does this work on an iPad ?
Which application do I need to run this (there is no MS-Dos on iPads) ?
Thanks
Nigel

I don't think you can run the CLI on iPad. The CLI is meant to be used on Windows, macOS and Linux computers.


KREST-578: Add configurable DosFilter support. (#238)

This PR exposes per-application DosFilter support. See https://www.eclipse.org/jetty/javadoc/jetty-9/org/eclipse/jetty/servlets/DoSFilter.html for more information about the options available.
Config names are kept equal to the ones in Jetty's DosFilter. That unfortunately includes a usage of "whitelist", which otherwise would not meet Confluent's bar.
This PR also changes several tests to use a random port, to avoid race conditions with port binding.

@confluentinc It looks like @ehumber just signed our Contributor License Agreement. :+1:
Always at your service,
clabot


feat(DIA-973): add social account linking to auth2

This PR resolves DIA-973
Description
This PR adds social account linking to auth2. It does so by adding the Link Accounts screen to the navigator, and makes the navigator accessible to the error-handling code by turning it into a hook.
https://github.com/user-attachments/assets/b9af601d-dfec-46b7-b2d1-934111183352
PR Checklist

[x] I have tested my changes on iOS and Android.
[x] I hid my changes behind a feature flag, or they don't need one.
[x] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[x] I added an app state migration, or my changes do not require one.
[x] I have documented any follow-up work that this PR will require, or it does not require any.
[x] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Added social account linking to auth2.

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (Added social account linking to auth2. - iskounen)

  Generated by :no_entry_sign: dangerJS against 613a3cc3e57a65257a204561a896cce56114f94f


[Backport 2.x] Improving the performance of date histogram aggregation (without any …

…sub-aggregation) (#11083)

Adding filter based optimization logic to date histogram aggregation

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Reading the field name for aggregation correctly

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Adding the limit on number of buckets for filter aggregation

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Applying the optimizations for match all query as well

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Handling the unwrapped match all query

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Adding logic for recursively unwrapping the query

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Restructuring the code for making it more reusable and unit testable

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Adding javadocs for fixing build failure

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Fixing minor bugs in refactoring

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Adding logic for optimizing auto date histogram

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Fixing bugs and passing unit tests for date histogram

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Temporarily reverting auto date histogram changes

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Fixing spotless check bugs

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Adding back auto date histogram and passing all unit tests

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Fixing the integration tests for reduced collector work

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Fixing the integration test regression

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Addressing code review comments

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Fixing hardbound, missing and script test cases

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Removing collect_count validation to prevent backward compatibility tests from failing

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Finally fixing hardbounds test case

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Refactoring code for reusability

Signed-off-by: Ankit Jain<EMAIL_ADDRESS>
Signed-off-by: Ankit Jain<EMAIL_ADDRESS>(cherry picked from commit 0ddbd96291d4ff05499ec53c5a04a5dda32d36ad)

Description
Backport of #11083
Related Issues
Resolves #9310
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)
~[ ] 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.

Depends on #11389

@jainankitk could you please incorporate the changes from https://github.com/opensearch-project/OpenSearch/pull/11392 here so we won't be doing yet another backport, thank you (and @msfroh for the idea).


enable and test minimal building on Windows

Building AutoKitteh requires running make, which is not supported natively on Windows. Windows users can run AutoKitteh in Docker today, but we want to remove that limitation.
Several options are described below. Are they reasonable?

https://stackoverflow.com/questions/32127524/how-to-install-and-use-make-in-windows
https://stackoverflow.com/questions/2532234/how-to-run-a-makefile-in-windows

However, our makefiles probably can't run as-is on Windows, because they use a few bash commands and *nix tools. But can they run with a reasonable amount of OS compatibility tweaks?
Alternatively, would it be easier/better/friendlier to write a separate batch/PowerShell script? Ideally not, because it would have to be maintained and tested separately, but that's a simple option if all else fails.
The scope of this issue is only these 2 commonly-used targets, as a Minimum Viable Product:

make bin (only builds the Go code)
make ak (only builds the Go code and embeds the pre-built web UI)

FYI, our codebase also uses Buf-based gRPC, and we use several make targets in our GitHub CI for building, testing, and static analysis, but there's no need to make them compatible with Windows for now.
Bonus points / next steps:

make test
make gofmt-check
make lint
make proto

What about git bash + msys/wingnu ?

@dolby360 looks like git bash is just a minimal set of tooling that can run on windows? if you can modify our makefiles to work only with that I would love to see it work.

@itayd compiling the project wasn't the issue I have to make just a few workarounds. (You can see here)
But running the server is not straight forward. I'm still checking on it.


Change width of theme

How can I change the width of the entire theme?
I tried looking for a <Container> component to shadow but couldn't find one.

You can change/style any component in your theme.js file as follows:
(Use the component name in lowercase: Container = container and H1 = h1)
import base from "@reflexjs/preset-base"
import "typeface-prata"

export default {
  preset: base,

  colors: {
    primary: "#fee440",
    secondary: "#07070a",
  },

  container: {
    // Default container width.
    width: "1200px",

    // <Container variant="sm" />
    sm: {
      width: "900px",
    },

    // <Container variant="lg" />
    lg: {
      width: "1600px",
    },
  },

  // Set the styles for all h1
  h1: {
    fontFamily: "heading",
    fontWeight: 400,
  },
}

This is called variants. You can read more on variants in the doc: https://reflexjs.org/docs/theming-styling#variants

Thanks!


DevTools: Basic expression playground

Description

This is the basic expression playground I showed in today's demo. It currently only supports "global" expressions (you cannot select a component to run it from). My current thought is to be able to choose a component in the future, maybe adding a button to the layout inspector that will open the expression playground with that component selected, or maybe just add a dropdown. Additionally, it would be nice to show better error messages similar to the pretty errors you get in the console. Even though these things are missing in this first version, I think it still adds a lot of value for very little effort so I thought I may as well just release what I have now.
I don't expect a thorough review, but I mostly copied the code from the window.evalExpression, and just hardcoded the forComponentId to null, so it is quite trivial to add support for selecting a component later.
https://user-images.githubusercontent.com/47412359/233646086-b8a03a1d-21c3-4984-921f-96506d65e06e.mov

With errors now! 🥳
https://user-images.githubusercontent.com/700139/233940660-11e2f8ec-08c7-4efc-8302-66e657be36fa.mp4

Cannot see the video, but I assume it is good 😅

Huh, I blame wf-recorder - maybe it works better if i re-encode it in ffmpeg once before publishing? 🤔
https://user-images.githubusercontent.com/700139/233994066-75a1f4da-fdfa-4600-95a1-81eeb9b9827d.mp4

same thing 😅

Arch must be great  🤣


CBO prefers index from zone nearest gateway

Fixes #4198.
Summary of changes:

Add a section to the CBO page, 'Preferring the nearest index', which
describes the feature and provides a short tutorial using a local
cluster

Update references to the --locality flag to link to the docs for
that flag

Add link from replication zones doc for secondary indexes to the new
CBO section so there is cross-linkage

This change is

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/1711b33c7a5dd8ae811b110f3a84f06c2f2e91b9/

See also: https://github.com/cockroachdb/cockroach/pull/35306

Direct links to updated docs for reference:

CBO - preferring the nearest index
Added a note to the replication zone config page's secondary indexes section linking back to CBO page so users can find the new feature
Other stuff is just docs administrivia: adding more links between things, etc.

I couldn't get the initial setup to work--kept getting i/o wait timeout errors due to the --host seeing my macbook pro. Eventually @jordanlewis taught me to use --listen-addr=localhost:26259 and I think we should update this document accordingly.

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/9f63845e1aecadd255991fbdbace0a563955c36b/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/ce0c69b05a9b88adc6653617acca22a746fa5de4/

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/98d17648020a3c3337e3da4325721b9e28eaef97/


PyCon SK 2017

- title: PyCon SK 2017
  dir: pycon-sk-2017
  youtube_list: https://www.youtube.com/playlist?list=PLeK_HepiMJKLVwUgkJZ8giEQP8Z5lLajZ
  language: slk

25 new videos were added in the list


[worker] definePageMeta is not defined

Environment

Operating System: Darwin
Node Version:     v16.13.1
Nuxt Version:     3.0.0-27385496.7a1cf62
Package Manager<EMAIL_ADDRESS>Bundler:          Vite
User Config:      head, css, build
Runtime Modules:  -
Build Modules:    -

Reproduction
https://codesandbox.io/s/hardcore-grass-965dh?file=/pages/index.vue
Describe the bug
Instructions from official Nuxt3 tutorial can't be executed

Additional context
Check out this topic: https://github.com/nuxt/framework/discussions/2770
Any of flows:

Having 'pages' folder and no lock.json/node_modules -> installing -> running (after clone)
Having 'pages' folder, deleting lock.json/node_modules -> installing -> running
Having no pages folder (e.g no vue-router)
will result in lack of definePageMeta

In this example I use definePageMeta for middleware, but it doesn't depend on it (this is not the source of the error)
I do get the following warning though:
[Vue warn]: Unhandled error during execution of setup function
at <Index onVnodeUnmounted=fn ref=Ref< undefined >  key="/some_page" >
definePageMeta is not defined
at setup (file://./.nuxt/dist/server/server.mjs:11102:1)
Logs
ERROR  [worker] definePageMeta is not defined

  at setup (.nuxt/dist/server/server.mjs:11102:1)
  at _sfc_main.setup (.nuxt/dist/server/server.mjs:11491:23)
  at callWithErrorHandling (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6621:22)
  at setupStatefulComponent (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6247:29)
  at setupComponent (node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6203:11)
  at renderComponentVNode (node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:198:17)
  at renderVNode (node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:304:22)
  at renderVNode (node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:310:17)
  at renderComponentSubTree (node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:269:13)
  at renderComponentVNode (node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:214:16)

I had same problem and searched a lot. Somewhere is written definePageMeta is only nuxt3 feature and not supported for nuxt bridge. But then i found this link and i get i to work! U have to add macros to bridge setup:
bridge: {
    nitro" true,
    macros: {
      pageMeta: true
    }
  },

and after this its working for me :)


How to add events using array of string

hiii, i like the way you design the calendar, we have a array of string containing dates. how to add in your calendar the array of strings.. appreciate your help in advance

Did you find a way to do this?

Do a for loop and pass the calendar instance to the addEvent method.
val c = Calendar.getInstance()
for(i in 0..3) {
   c.add(Calendar.DAY_OF_MONTH, i)
   eventsCalendar?.addEvent(c)
}


add type for separator

added it because there was no type for separator.
related  https://github.com/meinaart/cypress-plugin-snapshots/pull/82

Already fixed in another PR.


A rule that rejects obvious words in the commit title

Replaced https://github.com/nblockchain/conventions/pull/15

Let's consider the commitlint PR for fixing subject-full-stop highest priority, but after you've tackled that, you can address the feedback that I'm going to share about this PR.

Please add a new failing test with this commit message: https://github.com/realmarv/conventions/commit/006fe222f6911bb3a522325388f6ee339e986120
That is, if the subject contains just the word "fix", and there's no commit msg body, this rule should complain as well.

Please add a new failing test with this commit message: realmarv@006fe22
That is, if the subject contains just the word "fix", and there's no commit msg body, this rule should complain as well.

Done


Add skin tone modifier setting

Fixes #48.
Looks like this:

We can also add an option for "hold - select" or a similar pattern, but that can be a separate PR.

NICE

Is there a way to select skin tone ad hoc?


Create a "stats" page or section (maybe front page)

From Google analytics

Number of unique visitors to the site (all time)
Countries visitors are from (all time)
Top viewed categories (last 7 days)
Top viewed companies (last 7 days)

From github

latest additions to the directory
Australia map of headquarters breakdown
Number of companies total

https://www.lkhrs.com/blog/2022/04/add-stats-to-hugo/

https://github.com/am1t/plugin-post-stats/blob/main/layouts/shortcodes/poststats/detailed.html


UIA cleanup

Rename UIA structs, move individual structs into their own files, word wrap under 100 columns.

Merged.


Investigate warning that fails as an error on MSVC with openssl3

See https://github.com/conda-forge/open62541-feedstock/pull/14#issuecomment-960538846 .
If necessary, this should be reported upstream.

xref upstream issue: https://github.com/open62541/open62541/issues/4765 .


Remove GET resource listeners after a timeout

If a device connects on a different IP every time, GET responses will be sent to a large number of destinations when the resource is updated.

Address not by timeout, but by making GET notifications confirmable, allowing libcoap to handle automatic deletion if the client does not respond.


Locator documentation improvement

Following up on issue #185, these changes - hopefully - clarify the use of the the locator meta parameter to configure the dynamic built-in validations.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #186   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          20     20
  Lines         394    394
=====================================
  Hits          394    394

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 c60e948...579a58f. Read the comment docs.

Thank you very much 😃 This will be published on next docs rebuild.


Vague DNS Explanation

Is there any way you can elaborate on how to setup DNS properly?  I followed this document step by step and the only way to get a VM (on the same vNet) to communicate to my ILB is to manually set a hosts file.  It says above for "simple testing" but where do I do this for "non-simple testing"?  I've created the wildcard A records as instructed.

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

ID: 2b1afa49-a5b4-92db-68e8-3feeeff52eb3
Version Independent ID: c9191775-e49c-1462-e525-a5ce549ae743
Content: Create internal load balancer with App Service Environment - Azure
Content Source: articles/app-service/environment/create-ilb-ase.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

@EonHale Thanks for the question! We are investigating and will update you shortly.

@EonHale Thanks for the question! When you use an External VIP, the DNS is managed by Azure. Any app created in your ASE is automatically added to Azure DNS, which is a public DNS.
You may refer this link https://docs.microsoft.com/en-us/azure/dns/dns-zones-records
If issue persists it will be helpful if you elaborate your error.

Thanks, I read that document.  I can tell you this isn't working for
ILB-ASE.  I manually added the records as instructed in this article but
none of my VMs can communicate with my App unless I manually set a hosts
file.  Thanks.
On Tue, Apr 2, 2019 at 11:45 AM SnehaAgrawal-MSFT<EMAIL_ADDRESS>wrote:

@EonHale https://github.com/EonHale Thanks for the question! When you
use an External VIP, the DNS is managed by Azure. Any app created in your
ASE is automatically added to Azure DNS, which is a public DNS.
You may refer this link
https://docs.microsoft.com/en-us/azure/dns/dns-zones-records
If issue persists it will be helpful if you elaborate your error.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/28508#issuecomment-479060017,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGoDrCMeLZfYMA-0Sn4kdd0CCKPITk7_ks5vc3shgaJpZM4cWwRM
.

I have the same issue.

@EonHale and @aromanrod Thanks for bringing this to our attention. Your's feedback has been shared with the content owner for further review.

Is there any status on this request?  I also find the instructions very vague in the configuration of DNS, particularly in its interaction with the DNS settings on the vNet in which the ASE subnet is created.

same issue here!!

I'd also be interested in a little more detail on the DNS setup for ILB ASE's.
I have set this up based on this guide, deployed a web app and I can connect to it fine. But Kudu or basically anything around the scm url fails. Let's assume I'm using this URL... https://mynewaseapp730.scm.newase557.appserviceenvironment.net/
...it always redirects to...
https://newase557.appserviceenvironment.net/
..which obviously fails as there is just a zone behind this but no A record or the like.

I managed to reach SCM by just adding another A record for this. I dont like creating another ZONE as guide suggest! so instead for now i have 2 A records one for site.domain.com and another for site.scm.domain.com. Currently testing how a local install of Azure Devops connects to this, as iam uncertain how service connections through Azure will work!

I have the same issue, @allanmoller. I tried adding another A record both how the docs suggest and how you suggested but still unable to access SCM. Did you also configure the host file(I did)? trying to figure out what you may have done differently.

@SnehaAgrawal-MSFT  could we get someone to follow up on this to make sure the doc references the need for the dns entry for ilbasename.appserviceenvironment.net?

Docs should have been updated. #please-close


DCOS-10470: [1/4] Introducing the . dropdown-panel-group class

This PR introduces the .dropdown-panel-group class that is needed in order to implement the drop-down styling options for the DSL.

I'd reduce paddings a bit, still ✨!

The paddings are from the panel-styling, this PR only introduces the fact that a panel can now float under an element without much of fancy hacking.

Looks great. ✨ @jfurrow what do you think?

I'm not sure creating a new element is the right approach. Although it's hacky, I think it would be best to use the actual Dropdown component. This gives us a few advantages out of the box:

it will render on top of neighboring elements, always
it will render outside of Modal boundaries, should that situation arise
it will have the exact same styling and animation as the current Dropdown

For this to work, we would pass the Dropdown only two items: one would be the "trigger" element (the caret icon), and the other would be the component that contains all of the filtering options. Then we could set the persistentID prop on the Dropdown to display the caret icon in all cases.
In the future it would be best to create a more abstract component that gives us this "panel popup" beahavior and styling so that we can use it in multiple places, but I don't think we'll have time for that in this release.
@orlandohohmeier @wavesoft what do you think of the Dropdown approach? I'll leave some comments on the styling just in case you opt to move forward with this PR.

Hey @jfurrow , my two pieces of mind:

the truth is that I had a look on the Dropdown component but it felt a bit of an overkill. (Plus I saw that it's using absolute positioning + javascript to align the pop-up)
I wanted to re-use this panel component for also providing typeahead suggestions when the user is typing (hence the full-width class).
I saw that we have some amazing less variables, and therefore could address most of your bullet points.

I am also not opposing against Dropdown, but I felt it would cause more problems than solving them at this particularly short time.

@wavesoft That's three pieces of mind! 😄
Your points are valid, let's move forward with this for now. If we do need some of the functionality we've needed from the Dropdown, we can address that when we get there!
Nice work!

So, I am now using transform and I exposed two more variables in order for us to configure this easily in the future.


Enabling the RSpec InstanceVariable Rubocop rule on all but go_modules

https://www.rubydoc.info/gems/rubocop-rspec/RuboCop/Cop/RSpec/InstanceVariable
This code is pulled out of PR https://github.com/dependabot/dependabot-core/pull/10088 because it is working and shoud not be held up by the go_modules which is going to take more work.
What are you trying to accomplish?
Enabling the RSpec/InstanceVariable Rubocop rule
Anything you want to highlight for special attention from reviewers?
This PR will enable the rule on all but go_modules
How will you know you've accomplished your goal?
Rubocop rules wil be enforced and the changes will be transparent on testing.
Checklist

[x] I have run the complete test suite to ensure all tests and linters pass.
[x] I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
[x] I have written clear and descriptive commit messages.
[x] I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
[x] I have ensured that the code is well-documented and easy to understand.

Merging w/o deploying as this only adjusts test code... as long as CI passes, this essentially is deployed. So no point in dedicating a separate deploy for this.
The actual deploy will happen whenever the next PR gets picked up.


feat: add auto auth features

This adds most of the features available in google-auto-auth.  After we feel good about the API choices, I'll go back through and add tests.
Resolves #54!

@stephenplusplus could you take a look?

Codecov Report

Merging #281 into master will decrease coverage by 4.02%.
The diff coverage is 35.93%.

@@            Coverage Diff             @@
##           master     #281      +/-   ##
==========================================
- Coverage   91.67%   87.65%   -4.03%
==========================================
  Files          13       14       +1
  Lines         829      891      +62
  Branches      178      187       +9
==========================================
+ Hits          760      781      +21
- Misses         69      110      +41

Impacted Files
Coverage Δ

src/auth/envDetect.ts
27.58% <27.58%> (ø)

src/auth/googleauth.ts
79.2% <42.85%> (-6.06%)
:arrow_down:

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 78d6813...bf4c51a. Read the comment docs.

Nice! Would you mind showing some demos of authing with ADC, a key file, credentials object, pem/p12?

Sure!  Does this cover it?

LGTM. Here's a general look at how this would be used from GC/* libs. Let me know if anything looks wack.
const GoogleAuth = require('google-auth-library').GoogleAuth;

function Service(cfg) {
  // cfg may or may not have a `keyFilename` or `credentials` object:
  this.authClient = new GoogleAuth(cfg);
}

Service.prototype.request = function(reqOpts) {
  this.authClient.authorizeRequest(reqOpts, function(err, authorizedReqOpts) {
    // make request with authorizedReqOpts
  });
};

Looks great.  Only thing to note is that I decided to not support callbacks with new APIs.  This is totally up for debate though.  Is using promises a showstopper?

Oops. No, not at all, it shouldn't make a difference 👍

I think this is in it's final form, and ready for a good look over :) @google/google-node-team


Bug in the selection of Mark Region

When we do not mark region properly after clicking the 'Mark Region' Button and after that if we try to mark region properly in the page then at that time also it is not select the region or work properly.

Task completed at 8d9d780930317ef2552709ecbdc1c9b4b56722e1


YAML mappings require key uniqueness, but pyYAML does not.

Mapping
yaml.load('1: 1\n1: 2')

must raise an error, but it results in the dictionary
{1: 2}

https://github.com/yaml/pyyaml


Scoring positions

Fixes #89
Once #88 is done I can start working on #90

Now also fixes #88 and #90, but the arm positions still need to be set to the correct values.


WIP: first draft of simple gh-pages site

Preview at filtercake.com/peerdrop/
This could be made available at offlinefirst.org/peerdrop via fork or transferring since the org uses GitHub pages.

(Screenshot should probably get updated and show all supported platforms in the default avatars, as well as two or three peers with custom avatars. Will try to mock that later...)

LGTM!


#36: profile information for service seeker

UTs are failing,
TypeError: expected str, bytes or os.PathLike object, not NoneType
https://app.travis-ci.com/github/gcivil-nyu-org/wed-fall24-team1/builds/272901207


⚠ Bofrost.lu has degraded performance

In ab4e523, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1873 ms

Resolved: Bofrost.lu performance has improved in 6449248 after 8 minutes.


[Snyk] Upgrade next from 13.1.0 to 13.1.1

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade next from 13.1.0 to 13.1.1.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 3 versions ahead of your current version.
The recommended version was released a month ago, on 2022-12-24.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
Base: 80.00% // Head: 80.00% // No change to project coverage :thumbsup:

Coverage data is based on head (bbc0eaf) compared to base (e77b208).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #478   +/-   ##
=======================================
  Coverage   80.00%   80.00%
=======================================
  Files          31       31
  Lines         365      365
  Branches       60       60
=======================================
  Hits          292      292
  Misses         67       67
  Partials        6        6

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Cannot add page(s)

Description of bug
Cannot add pages and page tree is not visible
Steps to reproduce
List the precise steps to reproduce the bug:

Go to 'Pages'
Click on 'Add Page'

Current behavior
Error: 'There was een error retrieving your content'
Expected behavior
Add page interface to add pagename(s)
Screenshots

Error information
Provide any error information (console errors, error logs, etc.) related to this bug.
Affected version

[ ] 9.4.4 clean install
[ ] 9.4.4 upgrade

Affected browser
All

I cannot reproduce, do you have any logs in either:

The browser console
The admin logs
In the /portals/_default/logs folder

log is empty...

We added some pages yesterday without problems... but today we get this error...

console error:
An error has occurred.

An error occurred when trying to create a controller of type 'PagesController'. Make sure that the controller has a parameterless public constructor.

System.InvalidOperationException

at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.Create(HttpRequestMessage request, HttpControllerDescriptor controllerDescriptor, Type controllerType) at System.Web.Http.Tracing.Tracers.HttpControllerActivatorTracer.<>c__DisplayClass2.<System.Web.Http.Dispatcher.IHttpControllerActivator.Create>b__0() at System.Web.Http.Tracing.ITraceWriterExtensions.TraceBeginEnd(ITraceWriter traceWriter, HttpRequestMessage request, String category, TraceLevel level, String operatorName, String operationName, Action1 beginTrace, Action execute, Action1 endTrace, Action1 errorTrace) at System.Web.Http.Tracing.Tracers.HttpControllerActivatorTracer.System.Web.Http.Dispatcher.IHttpControllerActivator.Create(HttpRequestMessage request, HttpControllerDescriptor controllerDescriptor, Type controllerType) at System.Web.Http.Controllers.HttpControllerDescriptor.CreateController(HttpRequestMessage request) at System.Web.Http.Tracing.Tracers.HttpControllerDescriptorTracer.<>c__DisplayClass2.<CreateController>b__0() at System.Web.Http.Tracing.ITraceWriterExtensions.TraceBeginEnd(ITraceWriter traceWriter, HttpRequestMessage request, String category, TraceLevel level, String operatorName, String operationName, Action1 beginTrace, Action execute, Action1 endTrace, Action1 errorTrace) at System.Web.Http.Tracing.Tracers.HttpControllerDescriptorTracer.CreateController(HttpRequestMessage request) at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()

An error has occurred.

Unable to resolve DotNetNuke.Abstractions.INavigationManager as parameter "navigationManager" in scoped Dnn.PersonaBar.Pages.Services.PagesController. Where no service registrations found and number of Rules.FallbackContainers: 1 and number of Rules.UnknownServiceResolvers: 0

DnnSharp.DryIoc.ContainerException

at DnnSharp.DryIoc.Throw.It(Int32 error, Object arg0, Object arg1, Object arg2, Object arg3) at DnnSharp.DryIoc.Container.ThrowUnableToResolve(Request request) at DnnSharp.DryIoc.Container.DnnSharp.DryIoc.IContainer.ResolveFactory(Request request) at DnnSharp.DryIoc.ReflectionFactory.CreateExpressionOrDefault(Request request) at DnnSharp.DryIoc.Factory.GetExpressionOrDefault(Request request) at DnnSharp.DryIoc.Factory.GetDelegateOrDefault(Request request) at DnnSharp.DryIoc.Container.ResolveAndCacheDefaultDelegate(Type serviceType, Boolean ifUnresolvedReturnDefault) at DnnSharp.DryIoc.Container.DnnSharp.DryIoc.IResolver.Resolve(Type serviceType, Boolean ifUnresolvedReturnDefault) at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.GetInstanceOrActivator(HttpRequestMessage request, Type controllerType, Func`1& activator) at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.Create(HttpRequestMessage request, HttpControllerDescriptor controllerDescriptor, Type controllerType)

Maybe an issue with a DNN Sharp module?

Actionform is the problem... we will upgrade to the latest version first (Hotfix)

@idasbv glad you figured it out and thanks for letting us know.  We will go ahead and close this issue.

We found out the hotfix also doesn't work... The modules simple isn't compatible with DNN 9.4 because of the changes in some dependency injections... This is quite an issues for all people that use the DNNSharp modules...

Did you used 9.4.4? Did you get the latest DnnSharp version of their modules? I remember there was an issue but I think it was resolved in latest releases...


Signal names of length 1 fail to be evaluated

Repro:
https://jsfiddle.net/jrmeaphz/

    <input type="number" data-model="x">

Error:

Error evaluating Datastar expression:
return $x
Error: $x is not defined
Check if the expression is valid before raising an issue.

Fixed in v0.18.6


[All hosts](VSTO migration) Remove certificate steps

The sample referenced by Tutorial: Share code between both a VSTO Add-in and an Office Add-in with a shared code library was updated so you do not need to configure a test certificate. See https://github.com/OfficeDev/Office-Add-in-samples/pull/341 for details.
This PR removes the steps from the tutorial.

Docs Build status updates of commit 90d2e75:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/tutorials/migrate-vsto-to-office-add-in-shared-code-library-tutorial.md
:white_check_mark:Succeeded
View

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