Publish recent changes

JsonUnsupportedObjectError (Converting object to an encodable object failed: Instance of 'MappedIterable<MapEntry<String, String>, Map<String, String>>')

NoSuchMethodError (NoSuchMethodError: Class 'MappedIterable<MapEntry<String, String>, Map<String, String>>' has no instance method 'toJson'.
Receiver: Instance of 'MappedIterable<MapEntry<String, String>, Map<String, String>>'
Tried calling: toJson())

This occurs at cosmosdb_http_client.dart:60 when trying to do jsonEncode(body) where body is as shown in the attached screenshot:

I'm trying to follow the code here:101. My code follows:
    final results = await _cosmosDB.documents.query(
      Query(
        query:
            'SELECT id FROM $_containerName c WHERE c.id = @id AND c.lockedBy NOT NULL',
        parameters: {
          'id': uuid,
        },
      ),
      database,
      _containerName,
    );

I'm on Dart SDK version: 2.13.1 (stable) (Fri May 21 12:45:36 2021 +0200) on "macos_x64" and using json_annotation: 4.0.1 and cosmosdb: 0.0.3-prerelease.

It appears that this is fixed by changes subsequent to 0.0.3-prerelease. Could we get a 0.0.4?

Sorry for replying that late. Yes I will release 0.0.4 with your changes soon. Thank you for your contribution :)

Released 🎉


Updates for responsive screens (1)

Key changes

Collapse drawer if screen width is < 400px. Drawer should be accessed via logo button in header.

Change error icon from Cancel to Error.
Update tab header and test item icon colors to use accessible orange.
Refactor RequestsBadge to use ProblemBadge.
Change styling of TestListItem tabs object to a nested box -- accessibility colors.

Several minor flex changes to handle overflow.

Testing

Run core.
Shrink window size -- all features should be legible, accessible, and otherwise work as normal, excepting those listed in Known Issues/TODO.
In browser dev tools, switch to responsive screen (or the device of your choice) -- all features should be legible, accessible, and otherwise work as normal, excepting those listed in Known Issues/TODO.

Chrome:

Firefox:

Known Issues/TODO

Field/JSON/YAML buttons do not flex/overflow correctly.
Move window width to Zustand. Related issues include:

Run All Tests button width should flex on small screen.
Landing page is still not usable in small screens.

MessageList tabs content overflow scrolling not accessible via keyboard (Axe error) -- this is a ReactMarkdown problem.
Report header flexing can be improved.

If you find any issues outside of those listed here, please let me know!

Codecov Report

Merging #205 (a868360) into main (71e4241) will increase coverage by 17.73%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main     #205       +/-   ##
===========================================
+ Coverage   76.19%   93.92%   +17.73%
===========================================
  Files         179      111       -68
  Lines        4033     2817     -1216
  Branches      384        0      -384
===========================================
- Hits         3073     2646      -427
+ Misses        958      171      -787
+ Partials        2        0        -2

Impacted Files
Coverage Δ

client/src/components/Footer/styles.tsx

client/src/components/Header/Header.tsx

client/src/components/Header/styles.tsx

client/src/components/LandingPage/LandingPage.tsx

...nfigMessagesDetails/ConfigMessagesDetailsPanel.tsx

client/src/components/TestSuite/TestSession.tsx

...nt/src/components/TestSuite/TestSessionWrapper.tsx

...nents/TestSuite/TestSuiteDetails/TestGroupCard.tsx

...s/TestSuite/TestSuiteDetails/TestGroupListItem.tsx

...uite/TestSuiteDetails/TestListItem/MessageType.tsx

... and 58 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 71e4241...a868360. Read the comment docs.

Looks good! My only nitpick is that changing the behavior of the logo into a 'drawer-open' button when the drawer is collapsed wasn't intuitive (I had to read the PR to figure out how to do it). I suppose I would have tried it eventually if I didn't have the PR to look at, but something to consider in the future :)

Yeah I wasn't sure about this at all but I don't have a better idea at the moment about handling drawers on narrow windows. Best practice is permanent drawer on larger screens and toggleable drawer on smaller ones with some menu button that only appears on the larger ones, but since we already have the logo there, it's a little weird. Maybe change the logo to menu button on small screens?
Also let me know if I should merge this in or wait for the release to be dealt with.

Could you add in the jira ticket number in the PR name, if one exists?  Also, not sure whats up with github actions...

Could you add in the jira ticket number in the PR name, if one exists? Also, not sure whats up with github actions...

No ticket!

I think this is fine to merge.  Also, I'm pretty sure the GitHub checks would pass if they were actually working, because we only failed on a prettier issue while it was still working, and i fixed that.  So I don't know if we need to wait until GitHub resolves its Action problem before merging...


Support Scratch.org

This should  Slove Issue #94
This should SSupport the Scratch.org Domain, I think I might have something wrong with the formatting,
@KennethSweezy  Please Review.

Going to merge, IF Crashes I will un-merge


Failed assertion in OverlappingPairs::setNeedToTestOverlap in v0.10.1

I have a simple scene with a few capsule and a box. The program encounter an assertion fail every time I use the setTransform on a kinematic body that is exting the collision with another body. I saw that this issue was marked as fixed in release 0.10.1 but even with the latest version I encounter it.
I'm working on windows with mingw and linking my program with g++ in c++23. The library was compiled using cmake gui on windows in debug mode.
Here is the gdb report :

#1  0x00007ff961711019 in ucrtbase!_get_wpgmptr ()
from C:\WINDOWS\System32\ucrtbase.dll
(gdb)
#2  0x00007ff961711201 in ucrtbase!_assert ()
from C:\WINDOWS\System32\ucrtbase.dll
(gdb)
#3  0x00007ff7d7eef566 in reactphysics3d::OverlappingPairs::setNeedToTestOverlap (needToTestOverlap=true,
pairId=59, this=0x2227964f090)
at C:/DEV/libs_build/reactphysics3d-0.10.1/include/reactphysics3d/engine/OverlappingPairs.h:461
461         assert(mMapConvexPairIdToPairIndex.containsKey(pairId) || mMapConcavePairIdToPairIndex.containsKey(pairId));
(gdb)
#4  reactphysics3d::CollisionDetectionSystem::notifyOverlappingPairsToTestOverlap (this=0x2227964ef80,
collider=0x22279678af0)
at C:\DEV\libs_build\reactphysics3d-0.10.1\src\systems\CollisionDetectionSystem.cpp:801
801             mOverlappingPairs.setNeedToTestOverlap(overlappingPairs[i], true);
(gdb)
#5  0x00007ff7d7f027a3 in reactphysics3d::BroadPhaseSystem::addMovedCollider (this=0x2227964f268,
broadPhaseID=3, collider=0x22279678af0)
at C:\DEV\libs_build\reactphysics3d-0.10.1\src\systems\BroadPhaseSystem.cpp:198
198         mCollisionDetection.notifyOverlappingPairsToTestOverlap(collider);
(gdb)
#6  0x00007ff7d7f01fa2 in reactphysics3d::BroadPhaseSystem::updateColliderInternal (this=0x2227964f268,
broadPhaseId=3, collider=0x22279678af0, aabb=...,
forceReInsert=false)
at C:\DEV\libs_build\reactphysics3d-0.10.1\src\systems\BroadPhaseSystem.cpp:150
150             addMovedCollider(broadPhaseId, collider);
(gdb)
#7  0x00007ff7d7f026ef in reactphysics3d::BroadPhaseSystem::updateCollidersComponents (this=0x2227964f268,
startIndex=3, nbItems=1)
at C:\DEV\libs_build\reactphysics3d-0.10.1\src\systems\BroadPhaseSystem.cpp:180
180                 updateColliderInternal(broadPhaseId, mCollidersComponents.mColliders[i], aabb, forceReInsert);
(gdb)
#8  0x00007ff7d7f01ebf in reactphysics3d::BroadPhaseSystem::updateCollider (this=0x2227964f268,
colliderEntity=...)
at C:\DEV\libs_build\reactphysics3d-0.10.1\src\systems\BroadPhaseSystem.cpp:121
121         updateCollidersComponents(index, 1);
(gdb)
#9  0x00007ff7d7eaea4a in reactphysics3d::CollisionDetectionSystem::updateCollider (colliderEntity=...,
this=0x2227964ef80)
at C:/DEV/libs_build/reactphysics3d-0.10.1/include/reactphysics3d/systems/CollisionDetectionSystem.h:457
457         mBroadPhaseSystem.updateCollider(colliderEntity);
(gdb)
#10 reactphysics3d::Body::updateBroadPhaseState (
this=0x22279660330)
at C:\DEV\libs_build\reactphysics3d-0.10.1\src\body\Body.cpp:235
235             mWorld.mCollisionDetection.updateCollider(colliderEntities[i]);
(gdb)
#11 0x00007ff7d7eb1029 in reactphysics3d::Body::setTransform (this=0x22279660330, transform=...)
at C:\DEV\libs_build\reactphysics3d-0.10.1\src\body\Body.cpp:399
399         updateBroadPhaseState();
(gdb)
#12 0x00007ff7d7ec299f in reactphysics3d::RigidBody::setTransform (this=0x22279660330, transform=...)
at C:\DEV\libs_build\reactphysics3d-0.10.1\src\body\RigidBody.cpp:853
853         Body::setTransform(transform);
(gdb)
#13 0x00007ff7d7e9c1ca in operator() (
__closure=, entity=...)
at ../src/Game__physicsloop.cpp:105
105                         b->setTransform(t);

I'm encountering the same problem here in 0.10.1 too. I can provide a project to reproduce this site if you need, Daniel.

Thanks a lot for taking the time to report this.
I am starting to think that this issue has been fixed but the original issue #376 which was about this has not been fixed actually.
I will investigate this.

I have pushed a fix for this issue with this commit in thedevelop branch. Feel free to test this branch to make sure that the issue is resolved.
This fix will be part of the next release of the library.

This should now be fixed in the last released version of the library.


Run with set -e

When I run with the bash -e option (stop at first command with a return code different from 0), the tests terminate at the first check because of this increment:
+ _smoke_success '2xx Response code'
+ REASON='2xx Response code'
+ _smoke_print_success '2xx Response code'
+ TEXT='2xx Response code'
+ echo '    [ OK ] 2xx Response code'
    [ OK ] 2xx Response code
+ ((  SMOKE_TESTS_RUN++  ))

I think this could be tweaked because incrementing 0 returns a 1 code which stops the script.

Good catch. I'm afraid smoke.sh isn't really set -e proof regardless as it relies on checking the exit code manually in various places as the moment.


Remove more unused variables

Follow-up #5107

I think there's only the false positives left after this
https://github.com/abaplint/abaplint/issues/2226.

@mbtools check conflicts
false positives fixed, https://github.com/abaplint/abaplint/issues/2226

no syntax errors in abapgit, I'll trigger the abaplint regression test to check cross repos


Asynchronous Call

I'm building a Python-based feedhandler. I start in a q session with the following
q) \p 5000
q) .u.upd:insert
q) tbl:([] a:`x`y;b:10 20)
q) num::count tbl
q) num
2

I then run the following script from PyQ
>>> from pyq import *
>>> conn = q.hopen("::5000")
>>> aconn = q.neg(conn) # Asynchronous Call Handle
>>> names = ["a","b","c"]
>>> nums = [1,2,3]
>>> k_names = K._ktn(11,0)
>>> k_nums=K._knt(6,0)
>>> for x in range(3):
        K._ja(k_names, names[x])
        K._ja(k_nums, nums[x])
>>> k_inputs = K._knk(2, k_names, k_nums)
>>> conn(K._knk(3, kp(".u.upd"), K._ks("tbl"), k_inputs))

This successfully add the records into the host environment table "tbl".
q) num
5

If I run the asynchronous call handle, however
>>> aconn(K._knk(3, kp(".u.upd"), K._ks("tbl"), k_inputs))

The table is not updated.
q) num
5

If I run the synchronous call again,
q) num
11

It seems that PyQ is caching my asynchronous call somewhere. Am I doing something wrong?

When pyq is running in Python REPL mode (started using the pyq executable), it blocks kdb+ event loop that is responsible for dispatching asynchronous messages.  If you want to use asynchronous calls, you need to call Python from a regular kdb+ instance as follows:
q)p)h = q.hopen('::5000')
q)p)h.neg(('.u.upd', 'tbl', (["a","b","c"], [1,2,3])))

Please also note that you should avoid using low level methods that start with an underscore directly.  As shown above, you can rely on PyQ to automatically convert Python objects to K instances when they are passed to the handle.


IssueID:1863:improve SPI driver framework

[Detail]
Improve SPI driver framework.
New VFS support.
Userspace support.
[Verified Cases]
Build Pass: helloworld_demo@haaseduk1
Test Pass: helloworld_demo@haaseduk1

感谢提交 Pull Requests！
Thanks for submitting a pull request.


Implement the CharNormalizer trait on the LowercaseNormalizer struct

Pull Request
Related issue
Fixes #239
What does this PR do?

Implements CharNormalizer for LowercaseNormalizer
Removes the previous Normalizer trait implementation
Updates tests to include an initialized char_map field on the produced Token

PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue, or have you listed the changes applied in the PR description (and why they are needed)?

Yes, and as explained in #239, it leads to a correctly populated char_map

[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

Some quick notes
I based my implementation on CompatibilityDecompositionNormalizer.
This leads to duplicated code. I considered adding a function that both implementations could share, if that seems more appropriate, I can propose an alternate solution.

Force-pushed to correct the use statements so they match the existing style.


Updates to indicator names in indicators-final.json

We received 11 updates to indicator names from Abdulla on August 15th. See the diff on https://github.com/GSA/sdg-indicators/commit/34472aab3828eac19684b0f0cd909a9d36f624be or this gist https://gist.github.com/philipashlock/b04b6d24dbddf98c73fe181bf1d05d8a

Hi @philipashlock! this is great thank you!

@philipashlock not sure what you are putting together, but would you want to collaborate on maintaining an SDG Metadata API?


Bumping minimum supported barrel version

This PR bumps the minimum version of barrel that is supported.
There have recently been a few fixes in the integration and also
starting with 0.5.0 the API will become more stable, leading up
to the 1.0.0 release soon™

That's kinda by design. I would argue that users always being on the latest barrel version is preferable to having to re-do PRs updating the maximum version

Sorry this took so long to review.
Just so folks are clear, @spacekookie owns any code related to barrel integration and gets the final say -- It's not maintained by the Diesel team, it's just in our code base because it sorta has to be to allow this sort of plugin functionality.


Windows Machine File Copy Stopped Working after the task update from 1.0.26 to 1.0.27

Our build stopped working after the task recently update from 1.0.26 to 1.0.27. Althought the source path exists (verified in the build drop)
2016-05-25T10:07:40.9878985Z ##[error]Source path 'xxxxxx' does not exist.
We are using paths related to the source root (using git) something like - src\Project\bin\Package_Project*
I guess the problem is in https://github.com/Microsoft/vsts-tasks/commit/9ec2222cdf7aca309ab74712f25e273b8027f830 revision. Where the testpath is now using the -literalPath parameter.
Is this expected behavior ?
Thanks !
Nikola

@nsgocev yes, this change is by design. Robocopy doesn't support wildcards in source or destination path.

@codito how it worked before then ? :)

Confirming that after removing the -LiteralPath check everything works as expected.

@nsgocev thanks for clarification. This task is a wrapper over robocopy; earlier it used to automatically find the set of files from a given source path. So the argument src\Project\bin\Package_Name\* was translating to source: src\Project\bin\Package_Name, files: *. This has been a source of confusion because robocopy doesn't support wildcards in source argument.
With the recent change to make the task to be inline with robocopy, the files to be copied need to be explicitly mentioned in Additional Arguments input field. For example:

Please let us know if it still fails.

@codito Still not working as expected. It seems to do them on the Dest folder instead of the SRC folder.

@nsgocev that's bad, sorry. Could you please share the logs (with system.debug variable set to true) on email with rm_customer_queries at microsoft domain?

Closing due to inactivity.

Just wanted to add a confirmation to this bug. We just recently installed TFS 2015 update 3, which updated the windowsmachinefilecopy script from 1.0.18 to 1.0.23 and added the -LiteralPath. Our build definition step previously had a source input of $(build.binariesdirectory)*.dll. Moving the wildcard to the Additional Arguments input as @codito suggested works like a charm now.


Fix Disposal Behavior - Generators No Longer Supported

Currently, in master the disposal behavior meets the older ES7 Observable spec proposal, so it triggers return (aka completed) when subscription.dispose() is called. This is so Observable could support a primed Generator as an Observer to subscribe.
This needs to be removed as it's no longer supported by the ES7 Observable spec. Again, this spec is settling down, but more importantly so is this library.  The plan is to change the behavior back to the good ol' RxJS 2 -esque behavior we know and love; Where dispose()-ing a subscription does not trigger the completed handler.
All references to the disposeHandler in Observer will also be removed.

I'm glad this project and the proposal are sticking to expect rxjs 2.0.0 behavior. Generators and zalgo behavior fixes felt goofy and forced (dare I say, unnatural!).

This is done in master now due to #68


Phase#3

When I try to run the project, it fails to load the courses. I guess this happens because there is no data in data.json.

When I try to run the project, it fails to load the courses. I guess this happens because there is no data in data.json.

fixed


Installation fails on ubuntu 20.10

Hi, I'm new to this tech, and I'm failing to install the asciidoctor-pdf with the following outputs:
gem install asciidoctor-pdf

ERROR:  While executing gem ... (NoMethodError)
    undefined method `request' for nil:NilClass

ruby -e 'puts RUBY_VERSION'
3.0.0

This is a duplicate of #1848.

This is a duplicate of #1848.

It's unclear at this point whether we can even support Ruby 3 in the 1.5.x branch since it requires incompatible upgrades to libraries.

It's unclear at this point whether we can even support Ruby 3 in the 1.5.x branch since it requires incompatible upgrades to libraries.


File Viewing Redesign

[pr-server]
View this change on PR Server

[pr-server]
View this change on PR Server

[pr-server]
View this change on PR Server

@anderscognite done!

[pr-server]
View this change on PR Server

[pr-server]
View this change on PR Server


Missing flag handling in ColorMyWorld

When there is a missing flag for a country in ColorMyWorld, the popup display undefined before the country name.
It will be better to display nothing in this case.

But i think you want to remove that undefined part, right ? not whole pop up box

Can you please how you want that?? because i am unable to understand your requirements

Can you please describe how you want that?? because i am unable to understand your requirements

The fix suggested by @hharshas is good but is not enough. It solve the case where there is no existing emoji matching the country name in the activity.
But like I mentioned here, there is an existing emoji for St Vincent Grenadines. The problem is that the name mentioned in the flag constant doesn't match the name of the country so just changing the value to Saint_Vincent_and_the_Grenadines will make the flag appears.
So it should be nice to fix the value and double-check values for other countries.

hi i would like to work on this issue.Can you assign it to me

@llaske i have made some changes could you review it and i also have some doubts.

@yashveeeeer thanks for your contribution.
BTW your PR is not a the right place. It should be done on this repo. See https://github.com/llaske/sugarizer/blob/dev/CONTRIBUTING.md for more.
Plus, as I mentioned here it will be nice to check other missing flags.

Thanks alot @llaske I'll take care of the original repo and I'll check that problem you mentioned.

Fixed in https://github.com/llaske/sugarizer/commit/461795ebeb5171f80e707f6b559ae0a42f86be3f

@llaske Is the Issue still there

No, it's fixed


PR Test of a Failing Test

Status Flag 'Pre-Test Inspection' - Auto Inspected - Inspection Is Not Necessary for this Pull Request.

Status Flag 'Pull Request AutoTest' - Testing Jenkins Projects:
Pull Request Auto Testing STARTING
Build Information

Test Name: BSSW_PR_AutoTest
Build Num: 22
Status: STARTED

Jenkins Parameters

Parameter Name
Value

BSSW_SOURCE_BRANCH
pr-test-fail-02

BSSW_SOURCE_REPO
https://github.com/william76/betterscientificsoftware.github.io

BSSW_SOURCE_SHA
a119f6b93d9027a972d60ad6e5ddb898ab3c5a3b

BSSW_TARGET_BRANCH
develop

BSSW_TARGET_REPO
https://github.com/william76/betterscientificsoftware.github.io

BSSW_TARGET_SHA
f2c52140450cd343c6fb8e40c5c6d00e9be283f2

JENKINS_JOB_TYPE
Experimental

TEST_REPO_ALIAS
BSSW

Using Repos:

Repo: BSSW (william76/betterscientificsoftware.github.io)
Branch: pr-test-fail-02
SHA: a119f6b93d9027a972d60ad6e5ddb898ab3c5a3b
Mode: TEST_REPO

Pull Request Author: william76 (William)

Status Flag 'Pull Request AutoTest' - Jenkins Testing: 1 or more Jobs FAILED
Note: Testing will normally be attempted again in approx. 4:00:00. If a change to the Pull Request source branch occurs, the testing will be attempted again.
Pull Request Auto Testing has FAILED
Failure Message(s)
File: test/test_001_fail.md
Invalid value for property 'Topics', given value 'documentation'.
>>> Failed depenency check against property/value pair 'Categories'/'['Planning', 'Reliability', 'Collaboration', 'Crosscutting', 'Performance']'
>>> Allowable values are:
>>> - 'Continuous integration testing'
>>> - 'Debugging'
>>> - 'Design'
>>> - 'Discussion forums'
>>> - 'Funding sources and programs'
>>> - 'High-performance computing (HPC)'
>>> - 'Improving productivity and sustainability'
>>> - 'Licensing'
>>> - 'Performance at leadership computing facilities (LCFs)'
>>> - 'Performance portability'
>>> - 'Projects and organizations'
>>> - 'Reproducibility'
>>> - 'Requirements'
>>> - 'Software interoperability'
>>> - 'Software publishing and citation'
>>> - 'Strategies for more effective teams'
>>> - 'Testing'

Build Information

Test Name: BSSW_PR_AutoTest
Build Num: 22
Status: FAILED

Jenkins Parameters

Parameter Name
Value

BSSW_SOURCE_BRANCH
pr-test-fail-02

BSSW_SOURCE_REPO
https://github.com/william76/betterscientificsoftware.github.io

BSSW_SOURCE_SHA
a119f6b93d9027a972d60ad6e5ddb898ab3c5a3b

BSSW_TARGET_BRANCH
develop

BSSW_TARGET_REPO
https://github.com/william76/betterscientificsoftware.github.io

BSSW_TARGET_SHA
f2c52140450cd343c6fb8e40c5c6d00e9be283f2

JENKINS_JOB_TYPE
Experimental

TEST_REPO_ALIAS
BSSW

Test Comment

Sample Summary Text
This is some test text that should be hidden by Markdown

first
second

AB
CD


Feature request: Parse User Account lockout policy setting

@flovilmart @drew-gross
Currently parse-server does not have a way to lock accounts after failed login attempts.
Would you be interested in taking a PR to allow developers the ability to set a Account lockout policy?
Account lockout policy at a high level:
Someone who attempts to use more than a few unsuccessful passwords while trying to log on to your system might be a malicious user who is attempting to determine an account password by trial and error.
Update parse-server to track logon attempts and respond to this type of potential attack by disabling the account for a preset period of time
This setting will have 3 parameters:
Account lockout duration
The Account lockout duration policy setting determines the number of minutes that a locked-out account remains locked out before automatically becoming unlocked. The available range is from 1 through 99,999 minutes. A value of 0 specifies that the account will be locked out until an parse server/app administrator explicitly unlocks it. If Account lockout threshold is set to a number greater than zero, Account lockout duration must be greater than or equal to the value of Reset account lockout counter after setting.
This policy setting is dependent on the Account lockout threshold policy setting that is defined, and it must be greater than or equal to the value specified for the Reset lockout counter after policy setting.
Account lockout threshold
The Account lockout threshold policy setting determines the number of failed sign-in attempts that will cause a user account to be locked. A locked account cannot be used until it is reset by an parse-server / app administrator or until the number of minutes specified by the Account lockout duration policy setting expires. You can set a value from 1 through 999 failed sign-in attempts, or you can specify that the account will never be locked by setting the value to 0. If Account lockout threshold is set to a number greater than zero, Account lockout duration setting must be greater than or equal to the value of Reset account lockout counter after setting.
Reset account lockout counter after
The Reset account lockout counter after policy setting determines the number of minutes that must elapse from the time a user fails to log on before the failed logon attempt counter is reset to 0. If Account lockout threshold is set to a number greater than zero, this reset time must be less than or equal to the value of Account lockout duration setting.
References
The above template was copied from: https://technet.microsoft.com/en-us/library/hh994563(v=ws.11).aspx

@cherukumilli That seems like an interesting feature!

@flovilmart
Just went through some of the client SDK's. I can handle the JS SDK and android SDK. I am not sure about the others.
Would guys accept a multi phased change?
i.e., in phase 1,
update parse-server only.
parse server returns an existing error like ParseError.OTHER_CAUSE for all errors related this new feature.
Even though the error code says OTHER_CAUSE, the error message describes the error in a little more detail.
in phase 2, update JS SDK and android SDK with new error codes
in phase 3, update the rest of the client SDK's with community contributors
in phase 4, update the server to use the new error codes in the client SDK's.

@flovilmart
Would you guys accept a PR with just changes to parse-server where the server returns an error code Parse.Error.OBJECT_NOT_FOUND with an error message like Your account is locked due to multiple failed login attempts. Please try again after xx minutes ?

As long as we're still in an 'opt-in' basis, that would be fine, you could introduce another error code, and let the people know the meaning of that error in the docs :)

Closing this feature request as the PR #2601 has been merged into the master and released as part of release 2.2.19 (https://github.com/ParsePlatform/parse-server/releases/tag/2.2.19).


flash does not connect and error 127 when trying to run debugger

ESP-prog dubugger connected to Lyrat 4.3
Windows 10
I have followed instructions and flash times out.
I tried changing terminal to git and ubuntu intergrated in JSON settings file in template but didn't appear to help.
If I try to run debugger mode I get this error
Error: couldn't bind tcl to socket: No error
The terminal process terminated with exit code: 127
do you have any idea what exit code: 127 could be ?

The terminal don't have anything to do with the debugger...
Make sure you ALLOW GDB server access to network when asked.
Your problem may be caused by OpenOCD that's unable to connect to GDB because you didn't allowed GDB to access the network.


[BUG]: Upload button on modal for 'Upload resources' feature doesn't work

Describe the bug
Here I try to upload a csv and it doesn't work.
To Reproduce
https://github.com/DARPA-ASKEM/Terarium/assets/28237258/239caffe-f93e-4a50-8b0a-822194d5af10

If you click cancel, most of the time the file has been uploaded. If possible, this modal should be simplified to load data automatically after selecting a file and once uploaded the Upload button should become enabled.


OAuthSwift does not work within a widget

*/Pods/OAuthSwift/OAuthSwift/OAuthSwiftURLHandlerType.swift:33:31: 'sharedApplication()' is unavailable: Use view controller based solutions where appropriate instead.

OAuthSwiftURLHandlerType is a protocol that you can implement
OAuthSwiftOpenURLExternally is just the default one, and simply use application method to open externally the URL
To allow compilation I don't think there is an other way than add "#if/#else/#endif" preprocessor macros to exclude code in widget
where

PR #143 add OAUTH_APP_EXTENSIONS var to disable code UIApplication. sharedApplication
With cocoapod post install setting must be add into podfile for extension target
https://guides.cocoapods.org/syntax/podfile.html#post_install

wiki page added, PR merge is next
https://github.com/dongri/OAuthSwift/wiki/Work-with-application-extension


Undo/redo

Split out from #5

https://news.ycombinator.com/item?id=34312546
This is a comically simple idea -- encode the entire state of the app into the URL every time there's a change.


fix(lint): out of the box, generated recognizer doesn't pass linting …

…with unused Ember imported.
Not sure how much you care about blueprint-generated files passing linting... but this fixes a failure, but if Ember is really generally needed in recognizers, then perhaps not importing it is a minor inconvenience.

I'd imagine it's unused more often.


Support for specifying ClusterConfig options

gocassa exposes no way for us to configure the gocql cluster config beyond setting authentication right now. It would be nice to be able to either pass a gocql.ClusterConfig when connecting to a key space, or at the very least have some alternative way of setting some of those options.
The one I'm interested in right now is ProtoVersion, as I'm trying to use Cassandra >= 3.0, which does not work with ProtoVersion 2 (the gocql default).

I'm using cassandra version 3.0.6 and shoud modify gocassa code to set ProtoVersion 3.
Unless modifying code, can't connect to cassandra.  I think  It's better to give a way to set gocql.ClusterConfig options to avoid unneccessary code modifying .

I need this too

There is a way to do this already: use https://godoc.org/github.com/hailocab/gocassa#GoCQLSessionToQueryExecutor and then pass the acquired  QueryExecutor to https://godoc.org/github.com/hailocab/gocassa#NewConnection


⚠ Samsung has degraded performance

In 083ca4c, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2660 ms

Resolved: Samsung performance has improved in 749a7e9.


Fayatte County, GA

http://arcgis4.roktech.net/arcgis/rest/services/FayetteCountyGA/dynamicLocal/MapServer/17

Close in exurbs south of Atlanta.

Fixed via https://github.com/openaddresses/openaddresses/pull/2627.


History in interactive should come from the json file, not the built-in readline

Currently the history uses the built in Readline library. Migrate to use our log in history.json. That way you get the same history from interactive and CLI.

On further thought, leave it as is.  The issue is that the CLI includes requests that come from files that can be huge and it doesn't seem to make sense to try to include them in interactive mode.


HBASE-23238 Additional test and checks for null references on Scanner…

…CallableWithReplicas

Thanks @busbey !

would the test also get forward ported to branches-2/master? or is there something providing equivalent coverage already?

I was planning to add the test in all branches, as I don't see any existing one checking on this particular condition. The null checks would also apply to branch-2, but not to master, so for master we should probably have a patch with the test only, but yeah, let's wait for qabot.


Decide on supported Python versions

What
Decide which Python (minor) versions to support
Why
This affects which Python features we can use (e.g. list[str] type annotation is 3.9+) , our CI config, and other ongoing maintenance burdens.

We need to support 3.7+ if possible, based on feedback from early adopters.

We should downgrade CI to the earliest version supported when we do this, to ensure we don't accidentally use newer language features.


[XR] Expose HTML overlay and allow styling

Closing #8754
It is now possible to configure the overlay of the XR buttons. The default styling is:
"z-index:11;
position: absolute;
right: 20px;bottom: 50px;"

The button has the class xr-button-overlay added to it, and is exposed if the dev wants to configure using javascript

Tiny conflict due to previous merge


Add database to availability group (on all nodes including backup/restore/seeding

Hi Guys,
I am trying to add database to AG without using manual full backup / restore , I think Add-dbaAgdatabase does it for us. But i am able to no do so is this code to latest version of dbatools ?

Slack Community Channel: https://sqlcommunity.slack.com/messages/C1M2WEASG/ (get an invite: https://dbatools.io/slack/)
Documentation within the module: Get-Help <command>
Database Administrator on Stack Exchange network, dbatools tag: https://dba.stackexchange.com/questions/tagged/dbatools
StackOverflow dbatools tag: https://stackoverflow.com/questions/tagged/dbatools

You have to perform an full backup prior to adding a database to the AG. We don't perform that to for you on the command.

HI, you need have a full backup of a database before you can add it to an Availability Group @PreacherCmdLets
This is the same output as in SSMS

The command should be taking the backups for you:
https://github.com/sqlcollaborative/dbatools/blob/51bc5eaf989c49f6aced69aa0d840c6d9562cdb7/functions/Add-DbaAgDatabase.ps1#L220-L239


Fix signed maurer distance map zero divide

PR Checklist

[x] No API changes were made (or the changes have been approved)
[x] No major design changes were made (or the changes have been approved)
[x] Added test (or behavior not changed)
[x] Updated API documentation (or API not changed)
[x] Added license to new files (if any)
[x] Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
[x] Added ITK examples for all new major features (if any)

Refer to the ITK Software Guide for
further development details if necessary.

addresses SimpleITK/SimpleITK#1213

CI errors are related to the persistent JPEG2000 test failure, and multi-line comment warning.


Unable to get entity reference for DatabaseService with python API

Affected module
Python API
Describe the bug
The current implementation of get_entity_reference depends on the entity's fullyQualifiedName field. DatabaseService Entities don't have such field and therefore trying to retrieve a ref for a DB Service entity crashes.
To Reproduce
Try to retrieve a reference to an existing DatabaseService entity using the python API:
server_config = MetadataServerConfig(api_endpoint="http://localhost:8585/api")
metadata = OpenMetadata(server_config)
metadata.get_entity_reference(
    entity=DatabaseService, fqdn=<my_db_service_name>,
)

Expected behavior
Reference to the existing databaseService is returned instead of crashing.
Version:

OS: iOS
Python version: 3.8.12
OpenMetadata version: 0.8.0
OpenMetadata Ingestion package version: 0.8.0

Additional context
N/A

@pmbrull FYI

@pmbrull is this still an issue? If so lets reopen


intellisense for nodejs not working

Issue Type: Feature Request
Intellisense support for nodejs is not working in my VS code app. Details below.

Details below.

There is only VS Code and OS versions.
Could you provide actual details about extensions, project setup and what actually doesn't work (how you observe this).
/needsMoreInfo

Closing as more information is needed from the original poster to investigate this


1.0

Current coverage is 100% (diff: 100%)

Merging #6 into master will not change coverage

@@           master    #6   diff @@
===================================
  Files           2     2
  Lines          52    52
  Methods         0     0
  Messages        0     0
  Branches        0     0
===================================
  Hits           52    52
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 5d3cf35...10292f1


Could elm be used outside the browser?

Particularly interested in server side rendering (the Isomorphic/Universal development pattern) and static site generation?

I'd say this is a question for the mailing list, not for an (Elm) GitHub repo's issue tracker.

Done: https://groups.google.com/forum/#!topic/elm-discuss/SFIC-yuHTI8

In short, yes, it's possible. It's something I am quite interested in, and I have already started doing some preliminary work in this direction. I don't know the exact timeline, but this is something to expect eventually.

Yes it would make elm even more appealing. Thanks, @evancz @jvoigtlaender

There are several closed issues around isomorphic / server side rendering Elm. I don't see any open issues - is there somewhere else I can subscribe for updates on how this feature is coming along? Is there a best guess for when it might drop?

I think you may want to check https://github.com/NoRedInk/take-home#support-summary. Note the item "Server-side rendered client-side HTML". (The organization that repository is from is where Evan currently works.)

@ariscn, I will share updates on the elm-dev mailing list as things progress.


[BEAM-14516] Add context support for Python callables

Adding context support for Python callable.
We could remove unnecessary workaround like:
PythonCallableSource.of(
    "lambda: __import__('apache_beam.ml.inference.sklearn_inference')"
  + ".ml.inference.sklearn_inference.SklearnModelLoader(model_uri='/tmp/staged/sklearn_model')")

and just use:
PythonCallableSource.of(
    "lambda: SklearnModelLoader(model_uri='/tmp/staged/sklearn_model')")
.withContext("from apache_beam.ml.inference.sklearn_inference import SklearnModelLoader")

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

#17767 provides a similar feature.


[Feature] Update docs and seeds

Is there an existing feature request for this?

[X] I have searched the existing issues

Describe the Feature
Seeds and docs contain references to customs columns in application and job tables. Remove from seeds and docs for a clean docs regen.
Also review docs for any columns missing descriptions.
Describe alternatives you've considered
No response
Are you interested in contributing this feature?

[X] Yes.
[ ] Yes, but I will need assistance and will schedule time during your office hours for guidance.
[ ] No.

Anything else?
No response

Testing comment after closing.


gvim --remote from a directory with non-word characters changes the current directory

Running gvim --remote from a directory where any path element contains non-word characters changes the current directory. To reproduce it:

Check gvim's current directory with :pwd

Create a directory with a non-word character, and enter it:

mkdir 'a b'
cd 'a b'

Run gvim --remote on any file. It doesn't matter whether the file exists or not, or whether there is an instance running or not: the results are the same.
gvim --remote x

Check gvim's current directory now, it will have been changed:

If the current directory has no path elements with non-word characters, gvim --remote doesn't change gvim' current directory, as expected.
This seems to be related to issues #1690 and #1689.
EDIT: I'm running gvim 8.0.0197-4ubuntu5 (from package vim-gtk3) on Xubuntu 17.10

I'm now running gvim GTK3 33c5e9fa7 on Xubuntu 18.04 and this issue is still present.

I observe this behavior as well on gvim 8.2 and Ubuntu 20.10.


Error question

Hi Alex,
While I am trying this tool, I have met several questions.
I installed it by
python -m venv venv
source venv/bin/activate
python setup.py install

and everything runs successfully.
Using /public/home/lanlan/software/ModDotPlot/venv/lib/python3.11/site-packages/MarkupSafe-2.1.2-py3.11-linux-x86_64.egg
Finished processing dependencies for moddotplot==0.4.2

Then I tried the example
moddotplot -i test/Chr1_cen.fa
Then it turned to the error message like
  File "<frozen importlib._bootstrap>", line 1206, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/__main__.py", line 7, in <module>
    sys.exit(main())
             ^^^^^^
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/moddotplot.py", line 154, in main
    paired_bed_file(
TypeError: paired_bed_file() missing 1 required positional argument: 'k'

I thought it could be dealt by adding the -k
moddotplot -i test/Chr1_cen.fa --kmer 21
but still return the error massage.
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "<frozen importlib._bootstrap>", line 1206, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/__main__.py", line 7, in <module>
    sys.exit(main())
             ^^^^^^
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/moddotplot.py", line 127, in main
    kmer_list = read_kmers_from_file(i, args.kmer)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/parse_fasta.py", line 103, in read_kmers_from_file
    all_kmers.append(report_all_kmers(seq.fetch(seq_id), ksize))
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/parse_fasta.py", line 85, in report_all_kmers
    for kmer in kmers:
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/parse_fasta.py", line 21, in generate_kmers
    mask = (1 << (3*k)) - 1
            ~~^^~~~~~~

How can I fix it?
Thanks,
Lan

I tried the solution and still comes the error messages,
  File "<frozen importlib._bootstrap>", line 1206, in _gcd_import
  File "<frozen importlib._bootstrap>", line 1178, in _find_and_load
  File "<frozen importlib._bootstrap>", line 1149, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 690, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 940, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/__main__.py", line 7, in <module>
    sys.exit(main())
             ^^^^^^
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/moddotplot.py", line 154, in main
    paired_bed_file(
  File "/public/home/lanlan/software/ModDotPlot/moddotplot/static_plots.py", line 96, in paired_bed_file
    create_plots([df], input_name, input_name, seq_length)
TypeError: create_plots() takes 3 positional arguments but 4 were given

While I tried twice, it finally worked!
Thanks!

Great, sorry for the problems. I'll have some continuous integration and tests ready soon to prevent this in the future


⚠ Samsung has degraded performance

In f20f297, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2946 ms

Resolved: Samsung performance has improved in 774ed44.


Fix "Mapping" typo in JSON body

In the table for "msdyn_CopyProjectV4" it lists one of the parameters as "TeamMembersMappint" but I think this is a typo and it should be: "TeamMembersMapping".

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

ID: 4cdc2125-bf2a-985a-d44f-6449a469636a
Version Independent ID: 5cdec51a-7530-a40f-cc70-6d3e7a838f76
Content: Develop project templates with Copy Project
Content Source: articles/project-management/dev-copy-project.md
Service: dynamics-365-project-operations
GitHub Login: @abriccetti
Microsoft Alias: abriccetti

@NickMoores Thank you for letting us know. This has been fixed and the changes should go live later today.


Add npmignore

Coverage remained the same at 98.425% when pulling 44265f5ecff6067dd8124a2dbc64fcfacad2a2d9 on npm-ignore into 592c66961559beb71d540766dc2553df38ded00e on master.

Coverage remained the same at 98.425% when pulling 44265f5ecff6067dd8124a2dbc64fcfacad2a2d9 on npm-ignore into 592c66961559beb71d540766dc2553df38ded00e on master.


Implement Create Drop Functionality

Impl keypom SDK:

[x] create-drop as was previously done work in https://github.com/keypom/keypom-airfoil/pull/67
[ ] nft
[ ] ticket

TODO
x save nft deets and artwork to localStorage / indexeddb
x create required deposit for 2 drops (1 storage payment for nft, 1 for drop itself)
x create subtotal for whole payment
x create add to balance call for whole payment
x return from redirect / await
WIP
- create drop for nft lazy mint
- check drop created successfully
- create drop for worker
- send drop to worker
- worker responds true
- show user success

Closing because we're going to merge to testnet branch first!


One non-fungible serpent

Thank you for your contribution to the KodaDot NFT gallery.
👇 _ Let's make a quick check before the contribution.
PR type

[ ] Bugfix
[ ] Feature
[ ] Refactoring

What's new?

[x] PR closes #4003
[ ] Requires deployment <rubick/magick_issue>
[ ] <brief_description_of_what_I've_added>

Before submitting Pull Request, please make sure:

[ ] My contribution builds clean without any errors or warnings
[ ] I've merged recent default branch -- main and I've no conflicts
[ ] I've tried to respect high code quality standards
[ ] I've didn't break any original functionality
[ ] I've posted a screenshot of demonstrated change in this PR

Optional

[ ] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything seems works
[ ] I found edge cases
[ ] I've written some unit tests 🧪

Had issue bounty label?

[ ] Fill up your KSM address: Payout

Community participation

[ ] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI; a screenshot is best to understand changes for others.

@petersopko 🫡 is everything working?

@petersopko 🫡 is everything working?

well everything was working on /snek (as mentioned in #4003) but it seems that for example assets page is gone on this new /bsx route + profile dropdown looks different (missing assets route and multi-currency balance showing)
new BSX route:

old SNEK route:

As for the functionality of the rest of the live (bsx) version, if I'm supposed to see empty NFT explorer then it's working 😄 How  should I try to get some KSM and BSX here, in order to try any transactions ?

asset page was added in 8fdb7f5
balance should also work since 81d3cc5
If you need some KSM on BSX check #4036

asset page was added in 8fdb7f5
balance should also work since 81d3cc5

assets route in navbar on bsx leads to /snek/assets + it seems it shows unit? After manually navigating to /bsx/assets I see only one currency here (I have 0 on both, but I guess that shouldn't matter)

If you need some KSM on BSX check #4036

thanks, will do

Asking for a friend

chad: PRO

🚀


Adds nav links for "Download App" and "View Resource" on blog

Closes #437
Added two navbar links on the blog website.

Download app - redirects to App store
View Resource - redirects to Githawk Repo page

This is how it looks.
On PC browser:

On Smart Phones:

I dig it, thank you!


Fixes #30025 : Add options for which messages are marked as read

Fixes: #30025 : I have added the options for mark as read.
It has three options :

Muted topics
topics I don't follow
All messages

It is multiple selection.
Screenshot :

Video demonstration :
https://github.com/user-attachments/assets/7ed3d6be-5e78-4ecc-90e3-9256c8729b6c

Self-review checklist

[x] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[x] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[x] Visual appearance of the changes.
[x] Responsiveness and internationalization.
[x] Strings and tooltips.
[x] End-to-end functionality of buttons, interactions and flows.
[x] Corner cases, error conditions, and easily imagined bugs.

Thanks! Please clean up your commit history and post again to request a review. See here for guidelines.
You'll also need to complete the self-review checklist.

Sorry for the inconvenience @alya , I will clean the commit history asap.

@alya , I have cleaned the commit history and completed the self-review check-list.

@alya kidnly review the PR.

This is missing copy changes and a default selection that are clearly spelled out in #30025

I will make changes asap @karlstolley .

@karlstolley , as per the flaws you pointed out, I have made the changes.

Waiting for your next review:)

Your commit history is still incorrect, as @alya pointed out. Please take care to read through our Git guide, including the need to rebase and avoid merge commits: https://zulip.readthedocs.io/en/latest/git/index.html

@karlstolley , I will clean the commit history asap.

@karlstolley , Can you advice me on this point if I should try to fix in the same PR or should I create a new one??

It's just noise to open and close PRs. This is fixable. You need to read up on how to do that.

Got it @karlstolley . Will try to fix it. Thanks:)


Strings instead of string arrays in whitelists can lead to unexpected results

'<script>alert(1)</script>' ==
sanitizeHtml(
    '<script>alert(1)</script>',
    { allowedTags: 'noscript' });

because sanitizeHtml internally ends up doing 'noscript'.indexOf('script') !== -1 to determine whether a <script> tag is allowed.
This is probably not security-critical.
A policy is unlikely to have just one tag, but one allowed attribute is more likely.
It would be nice if it were harder to write policies with unintended consequences.
Maybe, throw an exception, or wrap strings with arrays when the string is found.
Alternatively, instead of using .indexOf internally to check set membership, consistently call out to a function like
function policyWhitelistContains(whitelist, element) {
  if (Array.isArray(whitelist)) {
    return whitelist.indexOf(element) >= 0;
  }
  return element === whitelist;
}

Hello Team,
cc: @boutell
The issue caused is because indexOf works on both String and Array. Looking at the test cases, I think the intended use was with Array. But people might have used it on Strings too.
Should I add an agnostic check as proposed in this thread?
Another approach can be to sanitize the options and turn strings into arrays at the beginning.
Please let me know your opinion. I will be happy to contribute and close this issue.
Thanks,
Kedar Chandrayan

The documentation could be more explicit, but nowhere is it suggested that strings are supported for these list arguments, and I don't think we should add weight and impact performance by adding runtime checking of these or adding split calls for strings, etc.
Those who want to can already use the community-maintained TypeScript typings to avoid problems with incorrect option types.

Agreed! TypeScript typings will help solve the confusion, if any.


Twin with property using duration schema can not be updated.

I try to update a twin which contains a property using a duration schema.
A have created an "Asset" model (based on opendigitaltwins-building Ontology models) via the Azure Digital Twins Explorer.
As you can see here I have a TestAsset with almost all values filled except these which uses the duration schema.

Then I have tried to update the twin with the "expectedLife" value as following: P1Y for 1 year duration. But it never works. I always get an error:

I have also tried to update the twin via the C# SDK, but I have the same issue.

{"error":{"code":"ValidationFailed","message":"Invalid twin specified","details":[{"code":"ValidationFailed","message":"Validation failed for expectedLife on Twin."}]}}

Am I using a wrong format for my duration value ? I have reported to the documentation which explains that the used format should be ISO 8601.

So I have followed this documentation to build my duration value. But nothing seems to working.
I have tried the following values to update my twin:

P1Y
P1Y0M0D
P1Y0M0W0D

Hello @Lushkin, we have a bug with duration that is on our list to fix in the next parser update. I don't have an exact date on when that will be available but I will update this thread when we do. Most likely sometime this late spring or early summer.

just leaving this commemt to have a message when this gets solved. Ty Microsoft Team DT look amazing and very promising :) HOpe to see soon more features.

P1Y0M0W0D

For the record, this one is not a valid ISO-8601 duration, as weeks (W) should not appear together with any other units.


Vulnerability: XML-RPC

Can you please look in to this? We received the email last week from an Anonymous person. We don't know him however it might be interesting. Can you please investigate? Is this relevant for us? How to fix?
If you need access to the server directly, Brandon should be able to give you access.
Email Below
Hello Team
I Gaurang Maheta found security issue in your system {HIGH}
What is XML-RPC ?
XML-RPC on WordPress is actually an API or “application program interface“. It gives developers who make mobile apps, desktop apps and other services the ability to talk to your WordPress site. The XML-RPC API that WordPress provides gives developers a way to write applications (for you) that can do many of the things that you can do when logged into WordPress via the web interface. These include:
Publish a post
Edit a post
Delete a post.
Upload a new file (e.g. an image for a post)
Get a list of comments
Edit comments
The first thing to do now is Send a POST request and list all the available methods , why ? cause that’s how we’ll know which actions are even possible to make and potentially use one of them for an attack.
TO list all methods Send a POST request with the following POST data,like shown in the picture,you’ll get a response with all the methods available
https://www.asrg.io/xmlrpc.php

Let me know if you need video poc  i happy to share
Best Regards,
Gaurang

This is disabled in multiple different ways, but webpage is still accessible without 403 error.

Need to look into disabling this from config files on the web server.

In the WP-Config.php disabled directly XML-RPC, however no affect.
Need to research.

Hi yes logged this on audit XML-RPC is still available, assuming most will now be done through REST API as XML-RPC is being phased out - so will resolve as critical

It may still be used by WP to buffer other automatic tools like Jetpack - so once disabled I will monitor and test through

@heldyboy , I checked in on azure, but for some reason my<EMAIL_ADDRESS>account is not associated with it
Can you send an invite again for me please to set SFTP
I have checked xmlrpc and have disabled on the development staging website with ease (just checked incase it was a plugin confliction) , but there is a file permissions issue on the live website which is why it is not disabling xmlrpc set.

@KellyDSD You should have another invite email in your email box.

@heldyboy  I have checked and validate the xml-rpc status by following these methods mentioned in the below Link
https://mediatemple.net/community/products/dv/360048950192/how-to-disable-xmlrpc.php-for-wordpress
Its currently disabled and here is the attached document


Medusa purge task not running

What happened?
When creating a medusa purge task, the task get's started by the k8ssandra-operator, but nothing further happens.
Did you expect to see something different?
The obsolete medusa backups should get deleted.
How to reproduce it (as minimally and precisely as possible):
Have a running K8ssandra cluster with backups that are out of the rotation and run a Purge task:
apiVersion: medusa.k8ssandra.io/v1alpha1
kind: MedusaTask
metadata:
  name: purge-backups-1
spec:
  cassandraDatacenter: kubernetes-1
  operation: purge

`
Environment

K8ssandra Operator version: 1.10.3
Cassandra version: 4.1.3
Medusa version: 0.16.3
Kubernetes version: 1.24.17

Anything else we need to know?:
Discussed in Discord.

Hey, thank you for taking a more in-depth look into this. Eventually, I was able to take another look as well. As it seems, the purges do work again as intended, but I'm not quite sure what could have caused this issue.
Mainly it was weird, that I wasn't able to see any confirmation of an ongoing purge in the logs, and it seemed that it might have been stuck. But I can confirm that it works in our cluster again and also syncs the medusabackups correctly as well. So I'm going to close this issue. :)

Thanks for the update!


Upgrade to the latest version of golang-jwt.

Backport #16590

Forcibly update the vendored versions too
Update our minimal go lang version to 1.15 (differs from 1.16 in #16590)

Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>:warning: BREAKING :warning:
This PR raises the minimal version of go supported to 1.15 which will mean the end of support of 32-bit Mac and Mac OS versions before Sierra.
Signed-off-by: Andrew Thornton<EMAIL_ADDRESS>

realistically given the imminent release of 1.17 we may need to raise the supported go version to 1.16.


Provide repo information

Great tool, but to make it useful for an average user, please add:

[x] meaningful description of its features
[x] examples
[x] screenshots
[x] installation guides
[ ] optional prepare is to be installed via SAPlink and/or abapGit to automate the installation
[x] add .abap extension to source files to enable syntax highlighting

Done


freshadminvm: make SCRIPTS_DIR changeable

When using local copy of automation scripts, freshadminvm still uses
global /usr/src/automation in some parts. Having this changeable from
outside makes it a bit more flexible.

 Update scale cloud to latest bits and use SAP node distribution

 Update scale cloud to latest bits and use SAP node distribution


Remove aria-label from vaadin-grid

aria-label should be on px-data-grid, not on internal vaadin-grid

LGTM


Update GatewayClass Condition flow to add Accepted Condition type.

Fixes #465
Signed-off-by: Nick Young<EMAIL_ADDRESS>

/retest

I think that's everything from @robscott? @hbagdi, what do you think?

Thanks!
/lgtm
/approve


bumped codex-db and updated inserter to match

Codecov Report

Merging #125 into master will increase coverage by 0.52%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #125      +/-   ##
==========================================
+ Coverage   46.66%   47.18%   +0.52%
==========================================
  Files           7        7
  Lines         405      409       +4
==========================================
+ Hits          189      193       +4
  Misses        210      210
  Partials        6        6

Impacted Files
Coverage Δ

requestParser/metrics.go
100.00% <ø> (ø)

requestParser/requestParser.go
76.96% <100.00%> (+0.57%)
: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 e64f4dc...caa8eee. Read the comment docs.


Continuos Integration Delivery

Keep openharvest.net up to date with master branch

Duplicate of #20 I'll assign that to you instead


fix/404 on all react-router paths

Fixes a bug where routes defined only in the SPA (react-router etc.) returns 404.
nginx must return index.html for all files not found (assets, chunks, etc.)

Does this also fix the frontend tests?

Which tests are failing?

Does this also fix the frontend tests?

Which tests are failing?

hmm, hard to make out the actual error. But I see a "ERR_NETWORK" in there, so probably not related. Also, this change only affect build static js serving from prod version of NGINX.


rancher-externalip-webhook chart enhancements

rancher-externalip-webhook:0.1.4
In the rancher-externalip-webhook chart:

Expose the following as questions:

certificates.certManager.enabled
certificates.secretName
certificates.caBundle

In the chart's app-readme (not the helm readme) note that cert-manager integration is enabled by default, and if it is not installed, users will need to disable and provide their own certificates. Ensure this displays correctly in both ember and vue.
The link to values.yaml in the readme takes the user to a 404 page in Rancher. This should be removed or linked to the full values.yaml

Created PR https://github.com/rancher/externalip-webhook/pull/8 adding all requested enhancements.

Moving back to 2.5.4, we should have time to QA.

@rawmind0 looks like your PR closed it, re-opening for QA.

@bmdepesa new 2.5 rancher-external-ip-webhook v0.1.500 should be available at dev

With chart rancher-externalip-webhook:0.1.5 from dev branches
Tested in both ember UI and dashboard

The readme is updated with the information about cert-manager being enabled by default, and how to provide your own certificates
Certificate options are exposed as questions
Link to values.yaml is fixed to the full link.
Deploying chart from both repositories is successful with both deployment options


[BUG]

Describe the bug
Newest version of the plugin has combined the commands /team promote and /team demote.  Where /team promote executes the command /team demote and even in /team help the description for /team promote is for demoting a player.  /team demote no longer exists as a command.
To Reproduce
Steps to reproduce the behaviour:

/team help -> to view the fact only /team promote exists and the wrong desc.
/team promote "player" -> will demote the player instead of promoting
/team demote "player" -> brings up the list of team commands because demote does not exist

Expected behaviour
/team promote and /team demote both exist and work as promoting and demoting players of a team
Screenshots

No idea if that worked...
Details
Please provide the following details about your server set-up:

Spigot version: 1.15.2
BetterTeams version: 3.0.6

Additional context
Add any other context about the problem here.

Thank you for the report, this problem will be fixed in version 3.0.7.

The problem has been fixed and will be included within the 3.0.7 update.
There is a chance you will also need to change the messages.yml value for the promote message (help.promote in older versions will say demote)


Error when Installing environment for pre-commit/mirrors-prettier

I get the following error when installing environment for prettier:  (inside of visual studio code / powershell terminal)
[INFO] Installing environment for https://github.com/pre-commit/mirrors-prettier.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
An unexpected error has occurred: CalledProcessError: command: ('C:\\Users\\james\\.cache\\pre-commit\\repolhcz07g7\\node_env-default\\Scripts\\npm.CMD', 'install', '--dev', '--prod', '--ignore-prepublish', '--no-progress', '--no-save')
return code: 1
expected return code: 0
stdout: (none)
stderr:
    npm WARN config dev Please use --include=dev instead.
    npm WARN config production Use `--omit=dev` instead.
    npm ERR! Unexpected token '.'

    npm ERR!      C:\Users\james\AppData\Local\npm-cache\_logs\2022-07-31T15_17_09_027Z-debug-0.log

Check the log at C:\Users\james\.cache\pre-commit\pre-commit.log

Relevant error in the npm log:
31 timing npm:load:logFile Completed in 4ms
32 timing npm:load:timers Completed in 0ms
33 timing npm:load:configScope Completed in 0ms
34 timing npm:load Completed in 19ms
35 verbose stack C:\Users\james\.cache\pre-commit\repolhcz07g7\node_env-default\Scripts\node_modules\npm\node_modules\libnpmfund:1
35 verbose stack ../workspaces/libnpmfund
35 verbose stack ^
35 verbose stack
35 verbose stack SyntaxError: Unexpected token '.'
35 verbose stack     at Object.compileFunction (node:vm:360:18)
35 verbose stack     at wrapSafe (node:internal/modules/cjs/loader:1049:15)
35 verbose stack     at Module._compile (node:internal/modules/cjs/loader:1084:27)
35 verbose stack     at Module._extensions..js (node:internal/modules/cjs/loader:1174:10)
35 verbose stack     at Module.load (node:internal/modules/cjs/loader:998:32)
35 verbose stack     at Module._load (node:internal/modules/cjs/loader:839:12)
35 verbose stack     at Module.require (node:internal/modules/cjs/loader:1022:19)
35 verbose stack     at require (node:internal/modules/cjs/helpers:102:18)
35 verbose stack     at Object.<anonymous> (C:\Users\james\.cache\pre-commit\repolhcz07g7\node_env-default\Scripts\node_modules\npm\lib\utils\reify-output.js:16:38)
35 verbose stack     at Module._compile (node:internal/modules/cjs/loader:1120:14)
36 verbose cwd C:\Users\james\.cache\pre-commit\repolhcz07g7
37 verbose Windows_NT 10.0.19043
38 verbose node v18.7.0
39 verbose npm  v8.15.1
40 error Unexpected token '.'
41 verbose exit 1
42 timing npm Completed in 95ms
43 verbose code 1

I just tried running it in CMD instead of PowerShell, same problem.

that looks like a symlink but written out as a file on disk -- appears to be a problem with npm itself and not anything we control -- please report your bug to upstream

Install libnpmfund outside of this pre-commit worked just fine:
npm install libnpmfund

added 154 packages, and audited 155 packages in 1s

9 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

yeah it has nothing to do with installing libnpmfund -- there's a broken file in the node zip

Is there a way to constrain it to a different node version that doesn't have this issue? Seems to be the line ../workspaces/libnpmfund that is the issue.

I'm not going to tell you because you can just read the docs -- please understand that my free time is limited and I don't have the time to provide free support

This seems like part of the issue: https://github.com/coreybutler/nvm-windows/issues/814
Running pre-commit in an admin prompt didn't fix the broken symlink issue, and gave the same issue.
Which docs?

I can't quite tell a way to tell the prettier pre-commit hook to use a different node or npm version. It doesn't use my system Node version, instead using nodeenv to install one, but it always uses latest, which is broken it seems. I am not sure I can configure nodeenv because of the way it gets run within a virtualenv.

prettier runs fine on the command line with node 16 LTS, but because I'm doing xml plugin, I had to add the following to my .prettierrc.yaml file:
plugins: ["@prettier/plugin-xml"]
Then run with the command:
prettier --config .prettierrc.yaml -c **.xml
But as far as I can tell, there is no easy way to get prettier to work through pre-commit on windows.

Interesting, even though my nodeenv was updated, when I ran nodeenv --version it gave me an old version number.
Had to run:
pip uninstall nodeenv
pip install nodeenv

To fix that, but still didn't fix the issue. Annoying.
I did try a github action to test this pre-commit hook using try-repo, which fails for me locally, but worked on the github windows runner. I thought maybe it was because that defaults to a different shell, but that didn't seem to be it either.
Probably something weird with my environment, but I reinstalled python and it didn't fix it. So weird that this used to work just fine and then broke when updating some packages.
Here is the test.yml github action for testing the install of the env using try-repo:
---
name: test
on:
  push:
    branches: [main]

jobs:
  Test:
    strategy:
      matrix:
        # https://ncorti.com/blog/howto-github-actions-build-matrix
        os: [ubuntu-latest, windows-latest, macos-latest]
        python-ver: ["3.8", "3"]
    runs-on: ${{ matrix.os }}
    steps:
      - name: checkout this repo
        uses: actions/checkout@v3
      - name: Set up Python
        uses: actions/setup-python@v3
        with:
          python-version: ${{ matrix.python-ver }}
      - name: install pre-commit
        run: pip install pre-commit
      - name: run pre-commit try-repo
        run: pre-commit try-repo .

Example run here: https://github.com/jgstew/mirrors-prettier/actions/runs/2770245273


Optimize - 02 Mar 2019

Pull Request Test Coverage Report for Build 74

3 of 3 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.2%) to 82.1%

Totals

Change from base Build 73:
-0.2%

Covered Lines:
237

Relevant Lines:
272

💛  - Coveralls


Update 'mean time' to 'meantime' in Release Notes Known Issues part

Storage Explorer Version: 1.12.0
Build: 20200113.2
Branch: rel/1.12.0
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:

Launch Storage Explorer -> Open Release Notes.
Check the Known Issues part in Release Notes.

Expect Experience:
Show 'meantime' in the descriptions of the know issue.
Actual Experience:
Show 'mean time' in the descriptions of the know issue.

This issue has been fixed on the latest build 20200114.3. So we close it.


[teslamate] - bump teslamate default image to 1.22.0

Description of the change
Update the default teslamate container image to latest (1.22.0)
Benefits
Fixes login issues with Tesla API servers which requires a new version of Teslamate.
Possible drawbacks
Additional information
Ref #715 and #716  originally submitted by @EasternPA
Checklist

[x] Chart version bumped in Chart.yaml according to semver.
[x] Title of the PR starts with chart name (e.g. [home-assistant])
[ ] (optional) Chart is using our common library as a dependency.
[ ] (optional) Variables are documented in the README.md

Looks good - might want to take you hand at trying to update this to the common library :)

I did a complete reinstall -- works perfectly. Thanks!


Tags not matching PyPi releases?

While tracking down an error in an application, came across some potential weirdness with the databend-sqlalchemy package.
At present PyPi is showing the latest release to be version 0.2.4.  However, the latest tag in this repo is 0.2.3.
Is that because tags in this repo aren't really kept in sync, or has potentially something bad happened with the PyPi release? :frowning:

Sorry for the delay response and thank you for pointing this out.
To address this issue, I'd like to tag @hantmac

@justinclift Sorry for delay response 😄 . The tag on pypi it the latest release which is version 0.2.4. I just forgot update the repo tag. Thanks for your help!

Cool, thanks for getting it sorted out. :smile:


Update CONTRIBUTING.md

Update CONTRIBUTING.md file
#33

Hey @Moksh45, thank you very much for contributing! Could you please rebase your branch onto master so the checks will run through?

ok


add nested property test

Codecov Report

Merging #967 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #967      +/-   ##
============================================
+ Coverage     46.94%   46.97%   +0.03%
  Complexity     1555     1555
============================================
  Files           354      354
  Lines          9755     9755
  Branches        968      968
============================================
+ Hits           4579     4582       +3
+ Misses         4834     4829       -5
- Partials        342      344       +2

Impacted Files
Coverage Δ
Complexity Δ

...ervice/service/ReleaseMessageServiceWithCache.java
84.52% <0%> (-1.2%)
23% <0%> (-1%)

.../apollo/internals/RemoteConfigLongPollService.java
77.3% <0%> (-0.62%)
27% <0%> (-1%)

...work/apollo/biz/message/DatabaseMessageSender.java
66.66% <0%> (+10.41%)
8% <0%> (+2%)
: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 cf3194b...61a5aad. Read the comment docs.

Coverage increased (+0.05%) to 50.497% when pulling 61a5aad569352dcdcfd27b0d25a7259da78fb77c on nobodyiam:nested-property-test into cf3194b2ed0931db853bc57bd76ea971f70d4462 on ctripcorp:master.


NuGet.Build.Tasks use Microsoft.Build.Framework 16.5.0-preview-19606-01

Expected Behaviour
Build pipeline runs und the IDE build my project.
Actual Behaviour
I get an error : NuGet.Build.Tasks 5.6.0 depends on Microsoft.Build.Framework (>= 16.5.0-preview-19606-01) but Microsoft.Build.Framework 16.5.0-preview-19606-01 was not found
Steps to Reproduce
install this package und try to install another package.
Is it important to use the NuGet.Build.Tasks package inside the acpuserprofile package? The iOS version of this package dont use this NuGet. If its important maybe you can update the version of NuGet.Build.Tasks? This may fix the problem.
Platform and Version
its a droid project and i cant build (target version 12)
Logs taken while reproducing problem
Package restore failed. Rolling back package changes for 'MyProject.Droid'.
NuGet.Build.Tasks 5.6.0 depends on Microsoft.Build.Framework (>= 16.5.0-preview-19606-01) but Microsoft.Build.Framework 16.5.0-preview-19606-01 was not found. An approximate best match of Microsoft.Build.Framework 16.5.0  ... icrosoft.Build.Tasks.Core 16.5.0 was resolved.
NuGet.Build.Tasks 5.6.0 depends on Microsoft.Build.Utilities.Core (>= 16.5.0-preview-19606-01) but Microsoft.Build.Utilities.Core 16.5.0-preview-19606-01 was not found. An approximate best match of Microsoft.Build.Utilities.Core 16.5.0 was resolved.

Or maybe set NuGet.Build.Tasks to all

Hi Percy, thanks for bringing this to our attention - and for the great detail! We're looking into this problem, and we'll likely have it resolved by early next year.

@PercyMummelthey
We just released Adobe.ACPUserProfile.Android version 1.0.0, please check to see if it resolves the issue.

Closing the issue.  Please open a new issue if there is any question.


Defining data structure for LQ dynamic optimization

We should define the following data structure for LQ dynamic optimization
abstract type AbstractDynamicData{T,S} end

struct LQDynamicData{T,S,M} <: AbstractDynamicData{T,S}
s0::S
A::M
B::M
Q::M
R::M
Qf::M
# etc
end

abstract type AbstractDynamicModel{T,S} <: QuadraticModels.AbstractQuadraticModel{T, S} end

mutable struct LQDynamicModel{T, S, M1, M2, M3} <:  AbstractDynamicModel{T,S}
  meta::NLPModelMeta{T, S}
  counters::Counters
  data::QPData{T, S, M1, M2}
  dynamic_data::LQDynamicData{T,S,M3}
  condense::Bool
end

and

define a constructor for LQDynamicData
replace the current build_QM with LQDynamicModel(::LQDynamicData{T,S,M}; condense = false) where {T,S,M}
define dynamic optimization-specific APIs such as get_s0 and set_s0!

Since we want functions such as set_s0!, should LQDynamicData{T,S,M} be a mutable struct rather than just a struct?

Also, do you want me to get rid of build_H and build_J as well and just implement them internally within LQDynamicModel(::LQDynamicData{T,S,M}; condense = false)? Or should I leave them as stand alone functions?

set_s0! should only modify the entry of lq_dyn_data.s0, so the data don't need to be mutable. But if you find it is more proper to make it a mutable struct, go ahead and make it mutable (there's no particular reason for it to be immutable either).

we can keep _build_H and _build_J , but they should be called internally within LQDynamicModel(::LQDynamicData{T,S,M}; condense = false)

What all should our API be able to do? Right now, I am just building functions to get and set the entries of LQDynamicData (i.e., s0, A, B, R, Q, sl, su, ul, uu). My set! functionalities can also either redefine the matrix entirely or just modify an entry of the matrix. Is there more that I should include within the API functionalities?

for now that should be enough, but if there's anything you feel like it will be necessary for the user, you can add them. Those APIs should always change the entry, not the arrays themselves


Create tool to input Design-time data

As described in the TMA Framework:

The platform also receives the results of the design-time assessment tasks, in which the performance and scalability requirements are not so stringent. The tools used to perform these assessment tasks are able to push data through the ReceiveData interface. When this not possible, adapters are used to transform the output of the tools and submit it to the platform. In some cases these results may have to be added manually, through a supporting tool.

This issue was completed with PR #68 (https://github.com/eubr-atmosphere/tma-framework-m/pull/68)


Add a test to ReadsPagingIT or ReadGroupSetsPagingIT: collect objects using two page sizes, compare

Add a test to ReadsPagingIT or ReadGroupSetsPagingIT:

pick two relatively prime page sizes, A and B
while returned page token != null, fetch objects using page size A, collect in set SA
while returned page token != null, fetch objects using page size B, collect in set SB
assert that SA contains the same elements as SB, and vice-versa.

Hey @macieksmuga, this is what we were just discussing.

It seems I took care of this without marking this issue.  See ReadsPagingIT.checkPagingByRelativelyPrimeChunksOfReads and ReadGroupSetsPagingIT.checkPagingByRelativelyPrimeChunksOfReadGroupSets.


Colorbars on figures

Should add color bars to figures, eg fig.colorbar(pos,shrink=0.5)

completed, likely more beautifying of plots eventually, will wait for requests.


Adding KubeDL to sandbox

Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[x] ~15 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

Build failed because of:
No cached entry, and KubeDL has issues with logo: kubedl.svg, SVG file has a <text> element. Please convert it to the glyph first, because we can not render it the same way on all computers, especially on our render server
Empty twitter for Mail.Ru Cloud Solutions (member): https://twitter.com/mailru
Empty twitter for Mail.Ru Cloud Containers: https://twitter.com/mailru
Empty twitter for Spotinst Functions: https://twitter.com/spot_hq
Empty twitter for SeaTunnal: https://twitter.com/ASFSeaTunnel
Empty twitter for Karmada: https://twitter.com/karmada_io
No cached entry, and Sangfor EDS has issues with twitter: https://twitter.com/SangforUSA, Request failed with status code 404
Item KubeDL has no image_data

LGTM!


Create a single service for the whole cluster, not per DC

This PR is for #41.I still need to add some automated tests and possibly change the monitoring service as well.

@Orange-cscetbon and/or @allamand can you please review?
I have already pushed changes to address the earlier comments.
Thanks
John

@jsanda, lgtm, you may need to add your test in the CircleCI pipeline to be automatically tested https://github.com/Orange-OpenSource/cassandra-k8s-operator/blob/master/.circleci/config.yml#L286

you may need to add your test in the CircleCI pipeline to be automatically tested

done!

@jsanda I've made some changes in master in order to be able to tests from PRs.
This takes at this time a manual steps on our side to trigger the tests.
Can you rebase on master ?

Are there any other changes needed for this PR? If not do you want me to squash the commits?

@allamand where are we on this ?

Thanks @jsanda for the good work :)


Suddenly getting all sectors missing

Hi,
I have used fluxengine release 449 to successfully read a bunch of amiga DD disks (11 so far), and now suddenly am getting this result consistently, including for disks which have already been successfully read:
# fluxengine read amiga --output test.adf --write-csv test.csv --write-svg test.svg --write-flux test.flux
Reading from: :d=0:s=0-1:t=0-79
Writing a copy of the flux to test.flux
Measuring rotational speed... Using FluxEngine with serial number A40002010F112A94
200ms
  0.0: 399.712 ms in 81664 bytes
       0 records, 0 sectors;
       Required sector 0 missing;
       Required sector 1 missing;
       Required sector 2 missing;
       Required sector 3 missing;
       Required sector 4 missing;
       Required sector 5 missing;
       Required sector 6 missing;
       Required sector 7 missing;
       Required sector 8 missing;
       Required sector 9 missing;
       Required sector 10 missing;
       5 retries remaining

and so on for the whole of the disk:
...
1. 7 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
1. 8 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
1. 9 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
1.10 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Good sectors: 0/1760 (0%)
Missing sectors: 1760/1760 (100%)
Bad sectors: 0/1760 (0%)
writing 80 tracks, 2 heads, 11 sectors, 512 bytes per sector, 880 kB total

Around the time this stopped working I did observe fluxengine rpm would occasionally return Error: bad USB reply 0x 3, but now it's consistently ok, and fluxengine test bandwidth and fluxengine test voltages consistently produce sensible-looking results (though I'm not what a good result is for the voltage test):
# fluxengine rpm
Using FluxEngine with serial number A40002010F112A94
Rotational period is 200 ms (300 rpm)
# fluxengine test bandwidth
Using FluxEngine with serial number A40002010F112A94
Transferred 1048576 bytes from FluxEngine -> PC in 1025 ms (998 kB/s)
Transferred 1048576 bytes from PC -> FluxEngine in 1823 ms (561 kB/s)
# fluxengine test voltages
Using FluxEngine with serial number A40002010F112A94
Output voltages:
  Both drives deselected
      Logic 1 / 0:  0.08V / 5.00V
  Drive 0 selected
      Logic 1 / 0:  0.09V / 5.00V
  Drive 1 selected
      Logic 1 / 0:  0.09V / 5.00V
  Drive 0 running
      Logic 1 / 0:  0.08V / 5.00V
  Drive 1 running
      Logic 1 / 0:  0.09V / 5.00V
Input voltages:
  Both drives deselected
      Logic 1 / 0:  4.87V / 4.98V
  Drive 0 selected
      Logic 1 / 0:  0.01V / 4.87V
  Drive 1 selected
      Logic 1 / 0:  4.97V / 4.98V
  Drive 0 running
      Logic 1 / 0:  0.01V / 4.86V
  Drive 1 running
      Logic 1 / 0:  4.98V / 4.98V

This is on a centos tower where the floppy drive lives, I tried attaching the board to a ubuntu laptop where I have the same version client compiled, using the same microusb cable, but got the same results.
I'd welcome any troubleshooting tips for this scenario. I'll try reattaching various components, trying different floppy/usb cables, etc.

I just noticed, the last disk I read before I started getting these consistent error, had some failed sectors in a curious pattern.  Could this possibly indicate anything, like damage to the drive?
writing visualisation
H.SS Tracks --->
0. 0 .......................................X........................................
0. 1 .......................................X........................................
0. 2 .......................................X........................................
0. 3 .......................................X........................................
0. 4 .B.....................................X........................................
0. 5 .......................................X........................................
0. 6 .......................................X........................................
0. 7 .......................................X........................................
0. 8 .......................................X........................................
0. 9 .......................................X........................................
0.10 .......................................X........................................
1. 0 ........................X.............XX........................................
1. 1 ........................X.............XX........................................
1. 2 ........................X.............XX........................................
1. 3 ........................X.............XX........................................
1. 4 ........................X.............XX........................................
1. 5 ........................X.............XX........................................
1. 6 ........................X.............XX........................................
1. 7 .B......................X.............XX........................................
1. 8 .X.B....................X.............XX........................................
1. 9 ..B.....................X.............XX........................................
1.10 ........................X.............XX........................................
Good sectors: 1711/1760 (97%)
Missing sectors: 45/1760 (2%)
Bad sectors: 4/1760 (0%)
writing 80 tracks, 2 heads, 11 sectors, 512 bytes per sector, 880 kB total

Just to confirm: you haven't upgraded your firmware or client, have you? Nothing's changed on the software side of things?
If not, it does suggest a hardware problem.  Don't put any more new disks in the drive --- it's quite possible that whatever it is is scratching disks. I'd suggest inspecting the most recent disks to see if you can see anything on them, cleaning the heads (a good practice anyway!) and then testing carefully with a disposable disk.
If you've got a flux file read from a bad disk, it'd be useful to see the results of fe-inspect. If the histogram shows a single peak which trails off at higher frequencies, then it's read noise. If it shows multiple distinct peaks, then there's most likely data.

Hi David, yes nothing was changed in the software/firmware to coincide with the failures.
Here's the output of fluxengine inspect for a read which was wholly unsuccessful, in the manner described above:
[root@vixen timecode-9]# fluxengine inspect -s timecode-9.flux:t=0:s=0
Reading from: timecode-9.flux:d=0:s=0:t=0
  0.0: 400.019 ms in 76288 bytes
0x12a00 bytes of data in 400.019ms
Required USB bandwidth: 186.241kB/s

Clock detection histogram:
  0 0.00      1 ███
  1 0.08      0
  2 0.17      0
  3 0.25      0
  4 0.33      0
  5 0.42      0
  6 0.50      0
  7 0.58      0
  8 0.67      0
  9 0.75      0
 10 0.83      0
 11 0.92      0
 12 1.00      0
 13 1.08      0
 14 1.17      1 ███
 15 1.25      0
 16 1.33      2 ██████▏
 17 1.42      2 ██████▏
 18 1.50      0
 19 1.58      2 ██████▏
 20 1.67      2 ██████▏
 21 1.75      0
 22 1.83      1 ███
 23 1.92      0
 24 2.00      4 ████████████▎
 25 2.08      7 █████████████████████▌
 26 2.17      3 █████████▏
 27 2.25      5 ███████████████▍
 28 2.33      8 ████████████████████████▌
 29 2.42     12 ████████████████████████████████████▉
 30 2.50     13 ████████████████████████████████████████
 31 2.58      7 █████████████████████▌
 32 2.67      5 ███████████████▍
 33 2.75      3 █████████▏
 34 2.83      0
 35 2.92      2 ██████▏
 36 3.00      4 ████████████▎
 37 3.08      2 ██████▏
 38 3.17      0
 39 3.25      1 ███
 40 3.33      1 ███
 41 3.42      0
 42 3.50      0
 43 3.58      0
 44 3.67      2 ██████▏
 45 3.75      0
 46 3.83      0
 47 3.92      0
 48 4.00      0
 49 4.08      0
 50 4.17      0
 51 4.25      0
 52 4.33      0
 53 4.42      0
 54 4.50      0
 55 4.58      0
 56 4.67      0
 57 4.75      0
 58 4.83      0
 59 4.92      0
 60 5.00      0
 61 5.08      0
 62 5.17      0
 63 5.25      0
 64 5.33      0
 65 5.42      0
 66 5.50      0
 67 5.58      0
 68 5.67      0
 69 5.75      0
 70 5.83      0
 71 5.92      0
 72 6.00      0
 73 6.08      0
 74 6.17      0
 75 6.25      0
 76 6.33      0
 77 6.42      0
 78 6.50      0
 79 6.58      0
 80 6.67      0
 81 6.75      0
 82 6.83      0
 83 6.92      0
 84 7.00      0
 85 7.08      0
 86 7.17      0
 87 7.25      0
 88 7.33      0
 89 7.42      0
 90 7.50      0
 91 7.58      0
 92 7.67      0
 93 7.75      0
 94 7.83      0
 95 7.92      0
 96 8.00      0
 97 8.08      0
 98 8.17      0
 99 8.25      0
 100 8.33      0
 101 8.42      0
 102 8.50      0
 103 8.58      0
 104 8.67      0
 105 8.75      0
 106 8.83      0
 107 8.92      0
 108 9.00      0
 109 9.08      0
 110 9.17      0
 111 9.25      0
 112 9.33      0
 113 9.42      0
 114 9.50      0
 115 9.58      0
 116 9.67      0
 117 9.75      0
 118 9.83      1 ███
 119 9.92      0
 120 10.00      0
 121 10.08      0
 122 10.17      0
 123 10.25      0
 124 10.33      0
 125 10.42      0
 126 10.50      0
 127 10.58      0
 128 10.67      0
 129 10.75      0
 130 10.83      0
 131 10.92      0
 132 11.00      0
 133 11.08      0
 134 11.17      0
 135 11.25      0
 136 11.33      0
 137 11.42      0
 138 11.50      0
 139 11.58      0
 140 11.67      0
 141 11.75      0
 142 11.83      0
 143 11.92      0
 144 12.00      0
 145 12.08      0
 146 12.17      0
 147 12.25      0
 148 12.33      0
 149 12.42      0
 150 12.50      0
 151 12.58      0
 152 12.67      0
 153 12.75      0
 154 12.83      0
 155 12.92      0
 156 13.00      0
 157 13.08      0
 158 13.17      0
 159 13.25      0
 160 13.33      0
 161 13.42      0
 162 13.50      0
 163 13.58      0
 164 13.67      0
 165 13.75      0
 166 13.83      0
 167 13.92      0
 168 14.00      0
 169 14.08      0
 170 14.17      0
 171 14.25      0
 172 14.33      0
 173 14.42      0
 174 14.50      1 ███
 175 14.58      0
 176 14.67      0
 177 14.75      0
 178 14.83      0
 179 14.92      0
 180 15.00      0
 181 15.08      0
 182 15.17      0
 183 15.25      0
 184 15.33      0
 185 15.42      0
 186 15.50      0
 187 15.58      0
 188 15.67      0
 189 15.75      0
 190 15.83      0
 191 15.92      0
 192 16.00      0
 193 16.08      0
 194 16.17      0
 195 16.25      0
 196 16.33      0
 197 16.42      0
 198 16.50      0
 199 16.58      0
 200 16.67      0
 201 16.75      0
 202 16.83      0
 203 16.92      0
 204 17.00      0
 205 17.08      0
 206 17.17      0
 207 17.25      0
 208 17.33      0
 209 17.42      0
 210 17.50      0
 211 17.58      0
 212 17.67      0
 213 17.75      0
 214 17.83      0
 215 17.92      0
 216 18.00      0
 217 18.08      0
 218 18.17      0
 219 18.25      0
 220 18.33      0
 221 18.42      0
 222 18.50      0
 223 18.58      0
 224 18.67      0
 225 18.75      0
 226 18.83      0
 227 18.92      0
 228 19.00      0
 229 19.08      0
 230 19.17      0
 231 19.25      0
 232 19.33      0
 233 19.42      0
 234 19.50      0
 235 19.58      0
 236 19.67      0
 237 19.75      0
 238 19.83      0
 239 19.92      0
 240 20.00      0
 241 20.08      0
 242 20.17      0
 243 20.25      0
 244 20.33      0
 245 20.42      0
 246 20.50      0
 247 20.58      0
 248 20.67      0
 249 20.75      0
 250 20.83      0
 251 20.92      0
 252 21.00      0
 253 21.08      0
 254 21.17      0
 255 21.25      0
Noise floor:  0
Signal level: 0
Peak start:   0 (0.00 us)
Peak end:     255 (21.25 us)
Median:       29 (2.42 us)
2.42 us clock detected.

This is actually using a different 3.5" drive I had spare, it started reading fine then started failing consistently in the same way.
I can't see any damage on the disk surface, but I'll have a go at cleaning the heads with isopropyl alcohol and might try dismantling the disks & cleaning their surfaces also. I'm sure there's muck, they've not been stored well.  A bit of research suggests gentle non-abrasive wiping with mild soapy water might be ok, though the thought of dismantling a floppy to do that is worrying.

Do you live somewhere hot and humid, or have the disks lived somewhere like that? If so, they could be mouldy, which can build up on the heads. OTOH you said you inspected them... I'd say that the first thing to do here is not to try any more valuable disks or drives in case it breaks them!
One thing you might want to try is using the writetestpattern command to write a regular train of pulses onto the disk, and seeing if they can be successfully read back (with inspect).

Hi David,
I was able to use writetestpattern successfully, but the corresponding read failed in the same way as above, no sectors found. The inspect histogram is:
[root@vixen amiga]# fluxengine inspect -s test/test.flux:t=0:s=0
Reading from: test/test.flux:d=0:s=0:t=0
  0.0: 399.155 ms in 99776 bytes
0x185c0 bytes of data in 399.155ms
Required USB bandwidth: 244.11kB/s

Clock detection histogram:
 46 3.83    376 ▏
 47 3.92  16590 ██████████▏
 48 4.00  65268 ████████████████████████████████████████
 49 4.08  16939 ██████████▍
 50 4.17    578 ▎
...
Noise floor:  652
Signal level: 3263
Peak start:   46 (3.83 us)
Peak end:     50 (4.17 us)
Median:       48 (4.00 us)
4.00 us clock detected.

Thx
Phil

An update, I had some success after cleaning the heads with isopropyl alcohol. I couldn't see any muck on them, but after cleaning them I was able to read some disks that had previously failed entirely.
The saga's not quite over for me though, as whilst gently cleaning one floppy which clearly did have some visible dirt on the surface, evidently the glue holding the metal hub to the mylar donut had deteriorated and they parted ways.
I found this interesting page which goes into detail about how to reglue the donut (cyoanoacrylate, very carefully), but goes into detail about the problem of the donut almost inevitably being slightly offcentre, some software he wrote to read the flux, and crucially a custom controller that allows the stepper motor to perform micro-steps.  If you have any time to watch his short video I'd be interested to know your opinions - unless fluxengine can controll the stepper motor in this way then it looks like I have another project ahead of me :)
Thx
Phil

Yes, that pattern looks very familiar from misaligned disks. Nice diagonal patterns of bad sectors! I bet it's picking up sectors from consecutive tracks on a single rotation.
I did find someone who was thinking about doing microstepping by PWM of the direction and track step lines. Unfortunately this would only work on the really old drives --- new ones don't connect those lines to the stepper motor controller directly. Also, I think I don't want to go there!
Also, re the pattern you're getting from writetestpattern: that's actually exactly correct. writetestpattern doesn't write data; instead it just writes a regular stream of flux pulses, by default 4µs apart. So inspect is reading the result perfectly. Which is very interesting.

Cheers, thanks for your help David, once again thanks for sharing this amazing project. I'll let you know if I have success (I doubt it :) )

Oh just to add FYI, the fluxengine inspect -s timecode-9.flux:t=0:s=0 output I posted 3 days ago with the single spike at 2.50 - I realised that this disk also had it's donut 'spontaneously' seperated from the metal hub - it just wasn't spinning in the drive.
Thx
Phil


Currently Missing Rotten Tomatoes and Metacritic Ratings

I just noticed today that the ratings for Rotten Tomatoes and Metacritic are absent in Edge and Chrome.
IMDb is still there so the extension is partially working.

Ratings are working for some movies but not all, including Stop Making Sense, Bohemian Rhapsody, and Unfrosted. Sorry for the inconvenience.

Fixed in v3.12.2
Letterboxd made some changes to the HTML of the page which caused some errors.