Rate Rules Pull

Finished

Delete all of your .DS_Store files.
Examples in /BioModels should not be changed, please revert those changes and test your features in a separate file.
Let's not have the test files in this PR.
node_modules.zip should not be pushed.
everything in /out should also not be pushed.
Can you explain your changes in package-lock.json? I don't think implementing this feature will require us to change anything in that file.
Some of your changes include adding annotation descriptions. Please only include changes regarding rate rules in this PR.
I'll take another look at your changes once you're done with the items above. Closing PR for now.


equal_up_to_global_phase() depends on the order of its arguments for EigenGates

Description of the issue
the wrapping of the modulo operation in EigenGate._equal_up_to_global_phase_ makes it dependent on the sign of the difference between the exponents. As a result cirq.equal_up_to_global_phase() depends on the ordering of its arguments when the two gates' exponents differ by a negligible factor (see below)
i think all it would take to fix this is adding an abs() to the linked lines, e.g.:
canonical_diff = abs(exponents[0] - exponents[1]) % period
return np.isclose(canonical_diff, 0, atol=atol)

or alternatively replacing both with linalg.tolerance.near_zero_mod()
How to reproduce the issue
gate1 = cirq.Z
gate2 = cirq.Z ** (1 + 1e-10)

assert cirq.equal_up_to_global_phase(gate2, gate1, atol=1e-5)  # ok
assert cirq.equal_up_to_global_phase(gate1, gate2, atol=1e-5)  # fails

Cirq version
1.2.0.dev20230105212249

@web3quantum Are you working on this issue? Do you have any questions or expected timeline by which you would be able to send a PR?

Hi, I was planning to work on this.


Maven Dependency not working

Hi there,
This is Kumar, I have been learning kafka for my final semester project and wanted to do a hands-on exercise on kafka-connect, I tried including this project into my spring boot application via maven dependency but it is not working can anyone please help me with this or is what I'm doing even right can this be used as a dependency for my spring boot application? Thank you so much for considering to reply.

Hi Kumar
This is not really supposed to be used as a Java dependency directly. You need to set up a Kafka Connect worker(s) to run this connector. Please see here for details

Hi @ivanyu - is this request not similar to the following issue where it was decided releasing to maven made sense for some people:
https://github.com/Aiven-Open/gcs-connector-for-apache-kafka/issues/77

Hi @bkinzle
Sorry for the inconvenience, the latest release has been published, it should be available soon.


Voice commands need to be re-implemented post HoloToolkit port

None of the voice commands present in the original GE have been implemented with the new HoloToolkit.

fixed in #118


[DEV] python-dev dependency / greenlet error

2805cb7 introduced eventlet==0.19.0 in requirements.txt.
This depends on greenlet which cannot be installed when the python-dev package is not installed.
Can be fixed by apt-get install python-dev, but took me a few minutes to figure out.

There's a quick solution for this.
pip uninstall greenlet easy_install greenlet


Support using logical view in query aligned by time.

Support using logical view in query aligned by time.
The commits do NOT support using logical view in query aligned by device till now.

Please add some IT.


Distinction between pump() and pumpUntilNoTransientCallbacks() is not clear

Case A
await scroll(tester, const Offset(x, y));
await tester.pump();                          // Not sufficient
await tester.pumpUntilNoTransientCallbacks(); // Required

Case B
Scrollable.ensureVisible(tester.element(finder));
await tester.pump();                          // Required
await tester.pumpUntilNoTransientCallbacks(); // Does nothing

Most of the time, what you want as a test author is a "pump until the app is stable" method.  What we don't want is for test authors to get in the habit of "I always just do both pump() and pumpUntilNoTransientCallbacks(), and it seems to work."

@abarth agrees with you. :-)

Fixed in #8751


☂ Consider making certain JNI routines leaf functions

For some of the routines, we can generate both the normal and the leaf versions, and call each one depending on the situation. For example Set<PrimitiveType>ArrayRegion could be fast depending on the length of the region, maybe it makes sense to conditionally call one or the other based on this.
Candidates:

[ ] FindClass
[ ] DeleteGlobalRef
[ ] Get<Member>ID
[ ] GetStringLength
[ ] GetArrayLength
[ ] IsInstanceOf
[ ] Primitive array operations
[ ] Direct byte buffer operations
[ ] String methods – especially when https://github.com/dart-lang/sdk/issues/39787 is landed

For jnigen, users should be able to specify if a method is leaf or not, this can be done as a part of jnigen transformation. However simply:

[ ] Getting a field
[ ] Setting a field
Can be safely turned into leaf calls.

cc/ @dcharkes

For some of the routines, we can generate both the normal and the leaf versions, and call each one depending on the situation.

Regarding this, I don't have a clear guide on where to draw a line between a leaf functions and a non-leaf function, for example for array allocation, or setRange-like JNI methods.
From a quick chat with @dcharkes: Running dart --verbose-gc runtime/tests/vm/dart/gc/splay_test.dart does ~67 GCs on an M1 machine. So limiting the time of a leaf function to ~1 ms means that we delay the GC about 1% of the time. So we could do some benchmarks for each function and see what is N where f(N) takes ~1ms. And maybe take N / 10 as a cut-off to account for the performance differences of different machines.
Another option is to delegate the responsibility to the user by having two versions of each function, but I would still want to have good documentation in this case.
@rmacnak-google @mraleph @mkustermann @alexmarkov What is your take on this?

Not delaying GC for more than 1% is the longest-running we can aim for for making things leaf calls. Maybe typical usages are causing less GC than our splay_tree benchmark. Anyway if we want to be on the safe side: 100 us on an M1.
We could also check what the shortest running time is for which marking it a leaf call still provides as significant performance benefit. For just summing two numbers it is a 3x speedup, but if a function is doing anything interesting, the run time of the function might dwarf the overhead of a non-leaf call anyway, in which case making it a leaf-call doesn't gain us much.
$ dart benchmarks/FfiCall/dart/FfiCall.dart
FfiCall.Uint8x01(RunTime): 74.21317274823117 us.
FfiCall.Uint8x01Leaf(RunTime): 49.1377612881323 us.
FfiCall.Uint8x01Native(RunTime): 77.78375360923965 us.
FfiCall.Uint8x01NativeLeaf(RunTime): 34.90857473140215 us.

A leaf call with a single argument saves 25 us - 40 us on an M1 (if this benchmark correctly reports the time per call). So that would give us still a 10% performance gain for calls up to 400 us on an M1.
So maybe if normal GC behavior is not as extreme as the splay_tree, we could consider setting the cutoff point at 0.5 ms on an M1.

For now I've decided not to make any of the potentially longer running functions into leaf calls. We can reopen/open another issue if someone has another idea.


fix: 修复form单词 "Feild" 为 "Field" [昨天merge的是错的]

General

✏ Mark the necessary items without changing the structure of the PR template.

[ ] Pull request template structure not broken

Type

ℹ What types of changes does your code introduce?

👉 Put an x in the boxes that apply

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

ℹ Check all checkboxes - this will indicate that you have done everything in accordance with the rules in CONTRIBUTING.

👉 Put an x in the boxes that apply.

[ ] My code follows the style guidelines of this project
[ ] Is the code format correct
[ ] Is the git submission information standard?
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

正解，我把错的改成了错的


Search Engines Somehow Getting Removed

OS/Platform
Portable Linux
Installed
Flatpak
Version
107.0.5304.110
Have you tested that this is not an upstream issue or an issue with your configuration?

[X] I have tried reproducing this issue in Chrome and it could not be reproduced there
[X] I have tried reproducing this issue in vanilla Chromium and it could not be reproduced there
[ ] I have tried reproducing this issue in ungoogled-chromium with a new and empty profile and it could not be reproduced there

Description
google.com disappears after being re-added as an enabled search engine repeatedly
How to Reproduce?

Have a non-google default search engine
Go to the search engine list and click activate
Use the browser for a while and somehow tab-complete stops working and I see the search engine is not activated in settings

Actual behaviour
Search engines somehow get de-activated for URL bar tab-complete
Expected behaviour
Once they're activated in settings, then I don't think they're supposed to be deactivated by anything without our permission - but I could be wrong
Relevant log output
No response
Additional context
I'm guessing this happens for other search engines, but it never seems to have happened with youtube.com for example.

@rany2 Have you encountered a similar issue?

@PF4Public I followed the submitter's steps and I wasn't able to face the issue on the flatpak.

Thanks for verifying this, @rany2.


Added names and remarks WHSSD PEV

Added the new properties "correctedName", "alternativeName" and "additionalRemarks" to all PEV instances and filled them in where necessary.

@UlrikeS91 Please let me know if I missed something!

@MaaikevS I only did a rough check now, but it looks correct except for the 2 issues above. Let me know when you fixed them. Then I can review the PR again and more thoroughly ☺


Update to use metapkg and distro-specific repo.

Update to use metapkg and distro-specific repo.
Promote go versions to 1.19.
Increase initial CSI startup timeout.
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #90
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

My changes to bump the go version did not fix the the integ tests, static checks, or vulnerability scanner.  Are these things that are configured in the repo configuration?  These tests were passing until my recent change to fix the CVEs.


fix(velocity_controller, mpc_follower): use common ego nearest search

Signed-off-by: Takayuki Murooka<EMAIL_ADDRESS>Description
use the new nearest index search algorithm in controller to deal with edge cases shown in the issue.

Related links
issue
https://github.com/autowarefoundation/autoware.universe/issues/1581
depends on
https://github.com/tier4/autoware_launch/pull/442

Tests performed

Notes for reviewers

Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.
[ ] The PR has been properly tested.
[ ] The PR has been reviewed by the code owners.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.
[ ] The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.

I confirmed that this PR worked with tier4's and awf's meta repository


Fix #3036: Workaround GCC's dce being too enthusiastic.

In NoModule, sometimes GCC thinks that $e is not used and can therefore be dce'ed away ... along with all our exports. We work around that bug by forcing a non-dce'able read of $e.
This workaround existed in the past. It was first introduced in 6680f72e8167af954d58797d26e943cf3326c4af. It was later removed in d28845a866bca1968658de1556577564cf9b74b3 to fix #2708, as it appeared not to be necessary anymore. However, we later broke what it was solving in d07af7c79b0ecca3498c0fe96c8fc223ad4abdb4. This commit reintroduces the previous workaround, but only in NoModule so that we do not recreate #2708.

I manually tested the HTML runner of Reversi and testingExample in fullOpt, obviously.

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


Add sleep/wake handlers in provider

Suspend networking and keep-alive while device is sleeping.
Hopefully a huge improvement on #4.

A few things may still break. Reopen later.


feat: application CRD

Issue:
https://gravitee.atlassian.net/browse/APIM-767

:tada: This PR is included in version 0.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Calling read-only function in contract seems to cache result

Describe the bug
When I call a read-only function from the contract page, then call it again with a different input, it returns me the result with the first inputs, and not a new result with the new inputs.
To Reproduce
Steps to reproduce the behavior:

Go to https://explorer.hiro.so/txid/0x57bfa7245d88105259a97ab8dd77ec664202c74562700fe73b95bb20534705e2?chain=testnet
Click on "Available functions"
Click on "block-info"
Enter argument, e.g. 109944
Click on "Call function"
See result, note the (height u109944) in the result
Click cancel
Enter new argument, e.g. 109945
Click on "Call function"
See result, not that it still shows (height u109944) and not (height u109945) which it should show

Expected behavior
The function should be called with each new set of arguments.
Desktop (please complete the following information):

OS: MacOS 13.4.1
Browser: Chrome
Version: 114

I just noticed this again. It seems important to fix, as it could cause someone to get incorrect results that seem legitimate. Here's a screen capture of an example of this happening. The first time, I click cancel and go back to the function again and get the incorrect result. The second time I refresh the page and get the correct result.
https://github.com/hirosystems/explorer/assets/1473715/1235beb8-095a-4d42-8572-46c8398ce3ce

:tada: This issue has been resolved in version 1.120.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Fix write conflicts in parallel output

Replace instance lock with static lock, because there can be multiple different ThreadSafeStringWriters writing into the same async context. Reduce the locking only to state initialization and dictionary lookups and edits, but don't hold the lock over StringBuilder operations.
Add a wrapper for StringBuilder that locks on every method on the instance level, so when two threads get the same instance of StringBuilder then will sync together, but they won't sync with other threads that have different string builder.
Fix #1063

I've used the project from https://github.com/microsoft/testfx/issues/1063#issuecomment-1098155363 that @JustArchi so helpfully provided, and run it 100 times in a loop without error. And without any regression in execution time.
This might be slightly improved by locking only when we grab or initialize the State, and then making the edits on concurrent dictionary, but it adds more logic and I guess the improvements would be marginal.


Additional parameter

I add additional parameter in CustomOAuth2AuthorizationRequestResolver, but how and where I can get it after answer from OAuth?

Hi @sl3w The additional parameter is added in the authorization request sent to the Authorization Server. This server is the one that can read and handle this parameter, but it's not required to return it in the response. That depends on the Authorization Server you're using and how its requests/responses are customized.

@lor6 Ok, thank you. I solved it in the following way: after the answer from OAuth I take this parameter from the request and add it to the response :) I don't see other way


Keep favicon.ico at Root of Project

I have an issue where the favicon.ico is missing in subdirectories. Since this plugin only copies the favicon.ico to the root of the project, the path should be absolute.

I see your point but this will break a lot for people who are already using the plugin.
The plugin copies the favicon to the same location as the index.html.


hyphen symbol is not recognized as a word delimiter

When I specify the setting "editor.wordSeparators": "-", in the settings.json, I expect the part of a compound word (one-large-word) to be selected. But it doesn't happen. It's probably a bug. Everything works fine in the not insider version - 1.34.0.
VSCode Version where the bug has been found: 1.35.0-insider

@iliazlobin can you share more details for better troubleshooting

which platform you are on
can you search word separators in Settings editor to see if there is workspace setting override it

I didn't reproduce this issue in latest Insiders on both macOS and Windows.


More gracefully handle error on no space left

Currently we fail out with generic 500 when an OSError is raised for the target partition being out of space. It would be nice returning specific errors for being out of space or quota.

Yeah, we can add errno.ENOSPC to https://github.com/unioslo/tsd-file-api/blob/e8bf6102522d15da84883dd94521c511334d591f/tsdfileapi/exc.py#L198


IDENTITY-6152 Make Symmetric Key Encryption the default

Mail : [Architecture] [IS] Move to symmetric data encryption from asymmetric encryption
Labels
Type: Task
Priority: Highest
Component/s: product-is
Severity: Major
Estimated Complexity: Novice
Issue migrated from: https://wso2.org/jira/browse/IDENTITY-6152

This is now addressed with https://github.com/wso2/product-is/issues/7898


mathlib + matrix

We currently have duplicated libraries for Matrix, Vector, Quaternions across mathlib and matrix. This is unnecessarily confusing for adopters, especially when it's common to mix usage of both in a single module.
https://github.com/PX4/Firmware/tree/master/src/lib/mathlib/math
https://github.com/PX4/Matrix/tree/e595ebb9a704c24aeae990dac768d26949fcaee0/matrix
We should discuss a path forward to remove the duplication. There's also the matrix submodule being included twice https://github.com/PX4/Firmware/issues/7991.
Since ecl is a core dependency I think Firmware should use the version of Matrix included by ecl. Then the existing mathlib can gradually be gutted so that it simply uses Matrix + any functions needed for compatibility. Eventually the need for compatibility functions can be removed entirely and mathlib Vector, Matrix, Quaternion can be a typedef for the Matrix version.
@MaEtUgR @Stifael FYI

I use the matrix library everywhere I do changes. The problem is there's usually a big bulk to change it for the whole module and that's why I end up with conversions to math::matrix back again to stay compatible which is far from nice.
I think we need a joint effort for a release (why not 1.8) to concentrate and switch the majority. They are pretty easy to switch out in most cases because the basic interface is the same but I'm personally against a typdef because it could generate even more confusion in the future and even lead to problems because of incompatibility.

@MaEtUgR @dagar how about to switch to matrix any time we encounter vectors/matrices that are of type mathlib, even if it just means to copy it directly over to matrix for just one calculations. This way we can do it incrementally and it is probably easier to switch everything in one shot even if it is just module based

@Stifael that could work if we make sure everyone is actually working towards that goal. We've had matrix for 2 years and new mathlib matrix usage is still coming in, so I figured it might be time to try something new.
It's messier, but the other compelling part about getting to typdef compatibility is not breaking external code.

We should push for what @Stifael suggested regardless (replace mathlib matrix usage with Matrix as you come across it). Removing mathlib matrix entirely or replacing with typedefs can be decided separately.

for reference: https://github.com/PX4/Firmware/issues/7991

@dagar, I would like to start with ecl l1 controller, which currently uses math::Vector.
As we have discussed, I would like to enable L1 for local coordinates as well, and by doing so, i will switch to matrix

I want to start out with the mc attitude controller. I'm anyways looking at it for quaternion control and introduced new matrix library functionality for making that more efficient.

Hey, this issue has been closed because the label status/STALE is set and there were no updates for 30 days. Feel free to reopen this issue if you deem it appropriate.
(This is an automated comment from GitMate.io.)


[MINOR] Fix the check condition in the readFromVector method to alway true

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
if (stringType == null || !stringType.equals(StringType.String)) {
This condition, one is an enumeration type and the other is a string type, the result is always true
Brief change log
(for example:)

Modify AnnotationLocation checkstyle rule in checkstyle.xml

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

CC: @jintaoguan @danny0405 @vinothchandar

@hudi-bot run azure

Can we please file a jira. I see lot of discussions going on. So, may not be trivial.

@danny0405 : Is this PR still valid or ok to be closed ?

I think we can close it currently.


Fix {Map,WeakMap}.prototype.set method

The second parameter is specified as required by the interface of spec.
TypeScript Version:  master
Code
interface Map<K, V> {
-    set(key: K, value?: V): this;
+    set(key: K, value: V): this;
}

interface WeakMap<K, V> {
-    set(key: K, value?: V): this;
+    set(key: K, value: V): this;
}

http://www.ecma-international.org/ecma-262/6.0/#sec-map.prototype.set
http://www.ecma-international.org/ecma-262/6.0/#sec-weakmap.prototype.set

Actually, the spec indicates that a lack of value is not a run-time error (as well as in practice).  For both, it would be a mechanism to clear a value without deleting the key, therefore freeing the value up for GC (while it does seem a bit silly and is likely not a good practice):
const m = new Map();
const obj = {};
const value = {};
m.set(obj, value);
m.set(obj); // key still in map, value is `undefined`, value could be GC'ed

as @kitsonk mentioned, it is a valid signature per the spec.

no, it is the behavior, not the signature. the spec defined that signature Map.prototype.set ( key , value ), not Map.prototype.set ( key [, value] ). it means value is not optional in the signature.

JS allows not passing parameters. so if value is not passed is implicitly undefined. most of these declarations are written by reading the spec and making a call if it should be there or not. from reading the spec again, so not see why it is not valid.

because current definitions make the following bug.
var m = new Map<number, number>();
m.set(0);
var v: number = m.has(0) ? m.get(0)! : 0;
v.toFixed(); // typeof v is number, but runtime value is undefined.

well.. you banged your way into this one. if you remove the bang in m.get(0)! you should get number|undefined, which is correct.
keep in mind that m.get("some random key") would return undefined anyways.

i guess you are right. we should not allow undefined to get there unnoticed. A PR would be appreciated.

Thanks @mhegazy!


Generic table

Propose a feature to allow users of getting easily a table without a dedicated mixin.

@jmanteau - thank you for this PR.  I understand what you are looking for to add, and I agree this is a good idea, and very useful.  I am going to "promote" this feature idea directly to the base class rather than a mixin.  I'll do this as part of the 6.0.2 release and attribute you on the idea.  I'll leave this issue open until I've completed that code.

This PR has been resolved into 0.6.3, available in PyPi.


Generate menu from json

Hi,
Can you provide example how to generate dynamically menu/menuitems from json template from ajax call.
This will be nice feature.
Thanks and you are doing great job with this 👍

Hi, no idea haha
There's no such feature at the moment.


[5.0] Adding title_case() helper

Please send this to 5.1.

Haha but I want it on 5.0, and I won't be able to upgrade to 5.1 for a few weeks! ><

We're not accepting PRs that add things to 5.0 anymore, sorry.


Merge compatible to develop (2024 jul09)

Upstream merge compatible -> develop

!ci-build-me

Didn't notice mergify does that for us now


How to prepare doc translations for Vue 3 release?

Since I'm the main maintainer of the Brazilian Portuguese translation, I'm a bit worried... Based on @NataliaTepluhina comment here, I suppose that the Vue 3 documentation is being reworked from scratch.
Did I understood it right? If so, is there anything our community could do to anticipate the work and be ready to release the new translation aligned (at least almost) with the Vue 3 release when it finally arrives?

@ErickPetru it's reworked from scratch indeed and we plan to publish it as soon as it's 'ready enough' for the translations. This should happen before the release, hopefully, next weeks. Why not right now? There are many moving parts and if translations will be started right now, it will add a lot of work on translators to rewrite things that already have been translated.

@ErickPetru it's reworked from scratch indeed and we plan to publish it as soon as it's 'ready enough' for the translations. This should happen before the release, hopefully, next weeks. Why not right now? There are many moving parts and if translations will be started right now, it will add a lot of work on translators to rewrite things that already have been translated.

It's been 16 days, Any progress? looking forward to seeing it

@NataliaTepluhina Any update on the status of the doc?

@NatanCieplinski Official docs have been published! https://github.com/vuejs/docs-next

Yes @varHarrie, the repo is there, but not officially ready to release. @NataliaTepluhina is there any information about starting translations based in this new repo? Should we start it right now?

Hey @ErickPetru and @NatanCieplinski! We have just posted an official translations page on the v3 guide: https://v3.vuejs.org/guide/contributing/translations.html#can-we-start-translating-vue-3-docs
At this time, it is probably worth getting familiar with the codebase and how it works, but as far as major translation work, it might be best to still wait for the release candidate of the docs since we're still modifying things as we gather feedback.
Let me know if you have any other questions!


Fix link to nuget in conceptual overview

The failing check has nothing to do with the file I have edited.

Thanks for the PR!
af9a78748a6213734a2a861a58a806319e31a1b1


Fix Panic on Introspection of Schema using ToJSON

Introspection via ToJSON works differently when used via the Schema.ToJSON function than when making an introspection query from a client such as GraphiQL. In the later case, introspection uses the Schema's registered resolver, while in the former case, a resolvable.Schema is faked
Without the Meta being set on this resolvable.Schema (following the recent changes to address race conditions around the Meta schema), this resulted in a panic when using this form of schema introspection.

Fixes #327

I was able to confirm that this PR resolves my issue by adding this fork as a remote and checking out this branch:
[bhatfield graphql-go]% git remote add dackroyd https://github.com/dackroyd/graphql-go.git
[bhatfield graphql-go]% git fetch dackroyd
remote: Enumerating objects: 9, done.
remote: Counting objects: 100% (9/9), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 9 (delta 3), reused 9 (delta 3), pack-reused 0
Unpacking objects: 100% (9/9), done.
From github.com:dackroyd/graphql-go
 * [new branch]      bug/fix-data-race-on-schema-parsing   -> dackroyd/bug/fix-data-race-on-schema-parsing
 * [new branch]      bug/fix-panic-on-introspection-tojson -> dackroyd/bug/fix-panic-on-introspection-tojson
 * [new branch]      experimental-lexer                    -> dackroyd/experimental-lexer
 * [new branch]      master                                -> dackroyd/master
 * [new branch]      new-resolvers                         -> dackroyd/new-resolvers
[bhatfield graphql-go]% git checkout dackroyd/bug/fix-panic-on-introspection-tojson
Note: checking out 'dackroyd/bug/fix-panic-on-introspection-tojson'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at e571531 Fix Panic on Introspection of Schema using ToJSON

Out of curiosity, is there any particular reason why this hasn't been merged yet?

I assume that @pavelnikolov has not yet had time to revisit this since I made the corrections for schemas without resolvers

Thanks, Dave! It looks awesome! 🎉


HBASE-24664 Some changing of split region by overall region size rath…

…er than only one store size
(cherry picked from commit b434ccaaeaeb08b3088a6a437e5d49ef1fcbb0cb)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 33s
Docker mode activated.

-0 :warning:
yetus
0m  6s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m  7s
branch-2 passed

+1 :green_heart:
compile
2m 40s
branch-2 passed

+1 :green_heart:
shadedjars
5m 58s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 18s
root in branch-2 failed.

-0 :warning:
javadoc
0m 16s
hbase-common in branch-2 failed.

-0 :warning:
javadoc
0m 40s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m  4s
the patch passed

+1 :green_heart:
compile
2m 42s
the patch passed

+1 :green_heart:
javac
2m 42s
the patch passed

+1 :green_heart:
shadedjars
6m  0s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 16s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

-0 :warning:
javadoc
0m 15s
root in the patch failed.

_ Other Tests _

-1 :x:
unit
14m 49s
root in the patch failed.

45m 42s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2054

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 966516f934f5 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / fce1df9a3c

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk11-hadoop3-check/output/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/testReport/

Max. process+thread count
685 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 45s
Docker mode activated.

-0 :warning:
yetus
0m  7s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 16s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 40s
branch-2 passed

+1 :green_heart:
compile
2m  9s
branch-2 passed

+1 :green_heart:
shadedjars
4m 58s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m  7s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 11s
the patch passed

+1 :green_heart:
compile
2m  9s
the patch passed

+1 :green_heart:
javac
2m  9s
the patch passed

+1 :green_heart:
shadedjars
4m 54s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
3m  1s
the patch passed

_ Other Tests _

-1 :x:
unit
21m 41s
root in the patch failed.

52m 10s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk8-hadoop2-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2054

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 28d70b58dfbc 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / fce1df9a3c

Default Java
1.8.0_232

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-jdk8-hadoop2-check/output/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/testReport/

Max. process+thread count
811 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 10s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 48s
branch-2 passed

+1 :green_heart:
checkstyle
2m 24s
branch-2 passed

+0 :ok:
refguide
12m 12s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
11m 46s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 11s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 30s
the patch passed

+1 :green_heart:
checkstyle
2m 25s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
7m 35s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
hadoopcheck
12m 38s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
12m 24s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 36s
The patch does not generate ASF License warnings.

79m 20s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2054

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide xml

uname
Linux 9bbc0459aaa5 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / fce1df9a3c

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
122 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 38s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 17s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
3m 36s
branch-2 passed

+1 :green_heart:
checkstyle
2m  5s
branch-2 passed

+0 :ok:
refguide
11m 52s
branch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
spotbugs
11m 15s
branch-2 passed

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
3m 24s
the patch passed

+1 :green_heart:
checkstyle
2m 11s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s
The patch has no ill-formed XML file.

+0 :ok:
refguide
7m 13s
patch has no errors when building the reference guide. See footer for rendered docs, which you should manually inspect.

+1 :green_heart:
hadoopcheck
12m  6s
Patch does not cause any errors with Hadoop 3.1.2 3.2.1.

+1 :green_heart:
spotbugs
11m 40s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 38s
The patch does not generate ASF License warnings.

75m 39s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2054

Optional Tests
dupname asflicense spotbugs hadoopcheck hbaseanti checkstyle refguide xml

uname
Linux c1a0091e7d8a 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a3567037c6

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-general-check/output/branch-site/book.html

refguide
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-general-check/output/patch-site/book.html

Max. process+thread count
137 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f) spotbugs=3.1.12

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m  6s
Docker mode activated.

-0 :warning:
yetus
0m  5s
Unprocessed flag(s): --brief-report-file --spotbugs-strict-precheck --whitespace-eol-ignore-list --whitespace-tabs-ignore-list --quick-hadoopcheck

_ Prechecks _

_ branch-2 Compile Tests _

+0 :ok:
mvndep
0m 14s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
4m 34s
branch-2 passed

+1 :green_heart:
compile
2m 58s
branch-2 passed

+1 :green_heart:
shadedjars
6m 28s
branch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 17s
root in branch-2 failed.

-0 :warning:
javadoc
0m 15s
hbase-common in branch-2 failed.

-0 :warning:
javadoc
0m 40s
hbase-server in branch-2 failed.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

+1 :green_heart:
mvninstall
4m 21s
the patch passed

+1 :green_heart:
compile
2m 56s
the patch passed

+1 :green_heart:
javac
2m 56s
the patch passed

+1 :green_heart:
shadedjars
6m 22s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 16s
hbase-common in the patch failed.

-0 :warning:
javadoc
0m 39s
hbase-server in the patch failed.

-0 :warning:
javadoc
0m 15s
root in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
232m 57s
root in the patch passed.

267m  9s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2054

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux 3a0a228e903d 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
branch-2 / a3567037c6

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/testReport/

Max. process+thread count
4003 (vs. ulimit of 12500)

modules
C: hbase-common hbase-server . U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2054/2/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

@wchevreuil Could you help to merge this PR? Thanks.

@wchevreuil Ping.


Master

HistoricalRequest: A lot of bugs in original versión fixed around of subRequests dealing.

Hi @Jumaga2015, thanks for your PR!
Can you please splitt the commits to a seperate pull requests and descripe the changes a bit?
I made a quick review of your commits:
3899d83 is already fixed with 544432f, so I think i will skipp it. Please update your fork.
In 756e2d1 you removed some historical data feeds in QDMSServer/MainWindow.xaml.cs - i think this is a customization that does not fit for all who will use QDMS. A better approach would be to make a more generic solution. F.e. a possibility to configure the historical data sources via app.config or a GUI function wich you have to use to add the historical data sources to the currently running broker.

ok and sorry.


Database table prefix

Some table prefixes are different from joomla installation table prefixes. Tables other than the Joomla table prefix are not listed.
FFExplorere -v: 1.0.6 [Update on 2021-07-07 17:22 (GMT+3)]
System Information

PHP Built On
Linux nwcompactap 4.18.0-305.el8.x86_64 #1 SMP Thu Apr 29 08:54:30 EDT 2021 x86_64

Database Type
mysql

Database Version
5.5.5-10.4.19-MariaDB

Database Collation
utf8mb4_general_ci

Database Connection Collation
utf8mb4_general_ci

PHP Version
7.4.19

Web Server
Apache/2.4.47 (Unix) OpenSSL/1.1.1k PHP/7.4.19 mod_perl/2.0.11 Perl/v5.32.1

WebServer to PHP Interface
apache2handler

Joomla! Version
Joomla! 3.9.28 Stable [ Amani ] 6-July-2021 15:00 GMT

Joomla! Platform Version
Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT

User Agent
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36

Hi,
I only want to modify joomla tables. That's why i did it.

Hi,
As you can imagine, it may be necessary to use the prefixes of some tables for other purposes. This situation creates a deficiency as there is no access to other tables.
Tan///

Maybe you can also add the ability to make sql queries. :)

have you an update?

have you an update?

Sorry, i don't have any plan for this feature.


Add support for Viewing rds files

I save R objects regularly as rds files, and it would be great to view them as one can with other file types. An example would be the docx viewer which opens tab with a view of the document. This view should be read only, but editing could be a nice plus. This obviously would only work for tabular data. If the data is not tabular, a message could be displayed.
At the moment, I am using readRDS() |> View() in the running R session, but a bild in solution would be really useful.

Maybe you should consider incorporating a customizable keybinding like this:
    {
        "key": "ctrl+r ctrl+v",
        "command": "r.runCommandWithSelectionOrWord",
        "when": "editorTextFocus && editorLangId == 'r' || editorTextFocus && editorLangId == 'rmd'",
        "args": "utils::View(readRDS($$))"
    }

Sounds like a solution.
I have put this into my keybinding.json. Then I have to press ctrl+r ctrl+v when the rds is selected in the browser panel? I tried this, but it does not work. What am I doing wrong?


Model Extensions

Hi @donotdespair,
Per our discussion today, I will look to implement the GIG full conditional prior for the $\kappa_+$ parameter for my first extension. I would appreciate any reference material that you can provide to implement this extension.
For my second extension, I will look to implement the proxy SVAR algorithm. I look forward to reading the Arias et. al paper here and discussing the procedure with you as we go forward.
Thank you!
@yobin-tim

Hey @yobin-tim
It was a nice talk! I am looking forward to the developments in your report and afterwards :)
The references:

This is the normal-triple-gamma prior paper It's a bit complicated, but it's great! It it a level of Journal of Econometrics! I don't know why Silvia sent it there!
This is the R package: GIGrvg

That's to begin with! Good luck!

Hi @donotdespair,
I am leaving a poke here in relation to receiving your feedback on my derivation of the full-conditional posterior of the hyperparameters in my extended model.
I also wanted to ask if you have any good resources on hyperparameter estimation. I was especially looking to understand how the hyperparameters are calibrated in such models.
I appreciate your help!

OK @yobin-tim
I have found the reference to the normal-gamma prior that you are using.
The most relevant paper introducing this type of priors is the one by Griffin and Brown and these fellows (fantastic statisticians and econometricians) show how far this type of hierarchical modelling can go.

Thank you @donotdespair! I will give it a read and then approach you if I have questions.

Hey @yobin-tim
Please look at the common SV sampler for structural models in line with what we were talking about.
SVcommonSF.R.zip

Sample code for the B0_hat for the normalisation:
B0_hat = diag(sign(diag(B0.last_draw))) %*% B0.last_draw

Thanks @donotdespair! I have implemented the sampler in my model.


Native linking fails when Xamarin.Firebase.iOS.InstanceID added

Starting with an empty Xamarin.Forms project, adding Xamarin.Firebase.iOS.InstanceID package to the iOS project causes linker errors upon build.
I attached the full msbuild log, but here are a few of the errors. Ultimately I was trying to use the Xamarin.Firebase.iOS.Analytics package, but I was able to recreate with just its dependencies.
3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(804,3): error MT5210: Native linking failed, undefined symbol: _FIRLogBasic. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. 3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(804,3): error MT5210: Native linking failed, undefined symbol: _FIRLogError. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. 3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(804,3): error MT5210: Native linking failed, undefined symbol: _FIRLogWarning. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. 3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(804,3): error MT5210: Native linking failed, undefined symbol: _GULIsLoggableLevel. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. 3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(804,3): error MT5210: Native linking failed, undefined symbol: _GULLogBasic. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. 3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(804,3): error MT5210: Native linking failed, undefined symbol: _GULLogError. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in. 3>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Xamarin\iOS\Xamarin.iOS.Common.targets(804,3): error MT5210: Native linking failed, undefined symbol: _GULLogInfo. Please verify that all the necessary frameworks have been referenced and native libraries are properly linked in.
VS solution to repro issue:
App.zip
VS About:
VS2019_About.txt
MSBuild log:
msbuild_log.txt

@applied-kevinsalot Can you update to the most recent version and try again? Thanks in advance!

@SotoiGhost Sorry for the late reply, I was unavailable last week. I upgraded to version 4.2.1 and no longer receive the above error. Thanks!


Errors in using pretrained models

Hi! I am trying to predict protein ensembles by using the pretrained model offered on Google Drive (named pretrain.pth). However, something seems to be wrong when loading the state dict.
my command: python eval.py task_name=inference target_dir=null ckpt_path=/home/jyzha/software/Str2Str/data/pretrain.pth
the output and error after printing config:

[2024-03-07 13:48:24,178][main][INFO] - [rank: 0] Instantiating datamodule <src.data.protein_datamodule.ProteinDataModule>
[2024-03-07 13:48:24,187][main][INFO] - [rank: 0] Instantiating model <src.models.diffusion_module.DiffusionLitModule>
/home/jyzha/software/anaconda3/envs/str2str/lib/python3.9/site-packages/torch/nn/modules/transformer.py:286: UserWarning: enable_nested_tensor is True, but self.use_nested_tensor is False because encoder_layer.self_attn.batch_first was not True(use batch_first for better inference performance)
warnings.warn(f"enable_nested_tensor is True, but self.use_nested_tensor is False because {why_not_sparsity_fast_path}")
/home/jyzha/software/anaconda3/envs/str2str/lib/python3.9/site-packages/lightning/pytorch/utilities/parsing.py:199: Attribute 'net' is an instance of nn.Module and is already saved during checkpointing. It is recommended to ignore them using self.save_hyperparameters(ignore=['net']).
[2024-03-07 13:48:28,277][main][INFO] - [rank: 0] Instantiating loggers...
[2024-03-07 13:48:28,278][src.utils.instantiators][WARNING] - [rank: 0] No logger configs found! Skipping...
[2024-03-07 13:48:28,278][main][INFO] - [rank: 0] Instantiating trainer <lightning.pytorch.trainer.Trainer>
GPU available: True (cuda), used: True
TPU available: False, using: 0 TPU cores
IPU available: False, using: 0 IPUs
HPU available: False, using: 0 HPUs
[2024-03-07 13:48:28,512][src.utils.utils][ERROR] - [rank: 0]
Traceback (most recent call last):
File "/home/jyzha/software/Str2Str/src/utils/utils.py", line 68, in wrap
metric_dict, object_dict = task_func(cfg=cfg)
File "/home/jyzha/software/Str2Str/src/eval.py", line 144, in evaluate
model, ckpt_path = checkpoint_utils.load_model_checkpoint(model, cfg.ckpt_path)
File "/home/jyzha/software/Str2Str/src/utils/checkpoint_utils.py", line 19, in load_model_checkpoint
model.net.load_state_dict(net_params)
File "/home/jyzha/software/anaconda3/envs/str2str/lib/python3.9/site-packages/torch/nn/modules/module.py", line 2153, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for DenoisingNet:
Unexpected key(s) in state_dict: "translator.trunk.ipa_0.linear_rbf.weight", "translator.trunk.ipa_0.linear_rbf.bias", "translator.trunk.ipa_1.linear_rbf.weight", "translator.trunk.ipa_1.linear_rbf.bias", "translator.trunk.ipa_2.linear_rbf.weight", "translator.trunk.ipa_2.linear_rbf.bias", "translator.trunk.ipa_3.linear_rbf.weight", "translator.trunk.ipa_3.linear_rbf.bias".
[2024-03-07 13:48:28,516][src.utils.utils][INFO] - [rank: 0] Output dir: /home/jyzha/software/Str2Str/logs/inference/runs/2024-03-07_13-48-23
Error executing job with overrides: ['task_name=inference', 'target_dir=null', 'ckpt_path=/home/jyzha/software/Str2Str/data/pretrain.pth']
Traceback (most recent call last):
File "/home/jyzha/software/Str2Str/src/eval.py", line 173, in main
evaluate(cfg)
File "/home/jyzha/software/Str2Str/src/utils/utils.py", line 78, in wrap
raise ex
File "/home/jyzha/software/Str2Str/src/utils/utils.py", line 68, in wrap
metric_dict, object_dict = task_func(cfg=cfg)
File "/home/jyzha/software/Str2Str/src/eval.py", line 144, in evaluate
model, ckpt_path = checkpoint_utils.load_model_checkpoint(model, cfg.ckpt_path)
File "/home/jyzha/software/Str2Str/src/utils/checkpoint_utils.py", line 19, in load_model_checkpoint
model.net.load_state_dict(net_params)
File "/home/jyzha/software/anaconda3/envs/str2str/lib/python3.9/site-packages/torch/nn/modules/module.py", line 2153, in load_state_dict
raise RuntimeError('Error(s) in loading state_dict for {}:\n\t{}'.format(
RuntimeError: Error(s) in loading state_dict for DenoisingNet:
Unexpected key(s) in state_dict: "translator.trunk.ipa_0.linear_rbf.weight", "translator.trunk.ipa_0.linear_rbf.bias", "translator.trunk.ipa_1.linear_rbf.weight", "translator.trunk.ipa_1.linear_rbf.bias", "translator.trunk.ipa_2.linear_rbf.weight", "translator.trunk.ipa_2.linear_rbf.bias", "translator.trunk.ipa_3.linear_rbf.weight", "translator.trunk.ipa_3.linear_rbf.bias".
Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

I am looking for the solution to fix it and very thanks.

Hi @JinyinZha, thanks for pointing out this bug. Now it is fixed with the newly uploaded gdrive link to the model weight. Please download the .pth file again.


A multi-update will terminate too early upon a validation failure

FerretDB version
In MongoDB, it seems that if an update with multi-true, tries to modify a field that causes a validation error it will terminate the update without modifying subsequent documents.
This behavior is consistent in SQLite but not in PostgreSQL.
Backend
PostgreSQL
Environment

OS:
Deployment:
Deployment details:

What did you do?
See #3352.
What did you expect to see?
The first document updated:
> t.find()
{ "_id" : ObjectId("65017c093bcc164ebd17079a"), "a" : [ 2 ] }
{ "_id" : ObjectId("65017c093bcc164ebd17079c"), "a" : 1 }
{ "_id" : ObjectId("65017c093bcc164ebd17079e"), "a" : [ ] }

What did you see instead?
Nothing updated

https://github.com/FerretDB/FerretDB/pull/3352#issuecomment-1905626886

It was fixed some time ago


Vector Tiles

2D maps like Google, Apple, MapBox GL, and OL3 are moving to actual vectors for rendering vector data, instead of baking vector data into a raster tile.  This allows, for example, to make labels always face up even if south is up and to fade out labels so they never hit each other.
For now, this roadmap is a collection of resources on this topic.

Google Maps + WebGL = MapsGL
Vector tiles for fast custom maps (video)
Videos from FOSS4G
Mapbox Vector Tile Specification

blog post
tools: vector-tile-js and mapnik-vector-tile
Client-side: pbf.js to decode tiles (protocol buffers).

geojson-vt
MMT-Vector-Tiles

More discussion: https://groups.google.com/forum/#!topic/cesium-dev/QnOxsA0iwa0

Looks like ESRI is adopting Mapbox vector tiles: https://www.mapbox.com/blog/vector-tile-adoption/

Info from FOSS4G NA 2015.

From Mapzen: Look Upon Our Squares of Math in Three Dimensions

State of the Map 2015 - Vector Rendering Panel - video, transcript

http://osgeo-org.1560.x6.nabble.com/Asking-for-new-vector-tiles-community-module-tt5211994.html

From Esri: http://blogs.esri.com/esri/arcgis/2015/07/20/vector-tiles-preview/

Demo of vector tiles at Esri UC is last video on page
http://www10.giscafe.com/blogs/gissanjay/2015/07/20/keynote-from-jack-dangermond-at-the-2015-esri-user-conference/
From: Patrick Cozzi<EMAIL_ADDRESS>Sent: Monday, July 20, 2015 5:45 PM
To: AnalyticalGraphicsInc/cesium
Subject: Re: [cesium] Vector Tiles (#2132)

From Esri: http://blogs.esri.com/esri/arcgis/2015/07/20/vector-tiles-preview/

—
Reply to this email directly or view it on GitHubhttps://github.com/AnalyticalGraphicsInc/cesium/issues/2132#issuecomment-123053536.

Is this still being considered by Cesium? It would be an impressive feature to tout.

Yes, but our current focus is on 3D Tiles.

Hello, I want to know when will it come out, I'm very looking forward to it~

Current work-in-progress for 3D Tiles vector tiles is in the vector-tiles branch.  The final date is still TBA.

@davidyaha that added support for the draft vector tile payload in 3D Tiles, but I would still leave this issue open for other potential vector tile specs.

OSM has global vector data, it would be cool to support that in Cesium and eventually serve it from ion:
https://openmaptiles.com/downloads/dataset/osm/#0.23/0/-26

Requested again here: https://github.com/AnalyticalGraphicsInc/cesium/issues/7939
Also perhaps relevant, some thoughts on how TerriaJS loads these vector tiles? https://github.com/AnalyticalGraphicsInc/cesium/issues/6182#issuecomment-362723885

Is there any related work or PR that we could follow up?

How can I extend MapboxImageryProvider to load PBF files instead PNG ? I think I can do something to put it to work using this : https://landtechnologies.github.io/Mapbox-vector-tiles-basic-js-renderer/.
As I can see, this renderer can get a PBF from {x},{y},{z} and render it in any canvas (the Cesium canvas??).
https://landtechnologies.github.io/Mapbox-vector-tiles-basic-js-renderer/debug/basic/google
it is just an idea to start. I know almost nothing about how Providers work. I need to know how to test a new Provider without need to compile all Cesium code. Any way to add it as a plugin? Some code to show me how?
What do you say?

@icemagno What if we suse something like this library
https://github.com/Leaflet/Leaflet.VectorGrid

@am2222 I'm using Cesium not Leaflet

@icemagno yeah I know, I am also looking for a way to make vector tiles work on cesium, but that plugin actually is doing the same thing as you said.it reads pbf files draws them on a canvas and leaflet plots that canvas. in our case we need draw pbf using cesium's canvas.

Terriajs has a MapboxVectorTileImageryProvider which draws (polygons only at this point in time) to canvas - see https://github.com/TerriaJS/terriajs/blob/master/lib/Map/MapboxVectorTileImageryProvider.js
@steve9164 created this a few years ago, he can give you more info about it

@nf-s I think the provided sample helps me alot. I have not looked at it in details yet, Does it use any internal files fron terriajs library as well?

It uses 2 small utility functions from the terria library which are essential, but everything else is imported from Cesium, @mapbox/vector-tile, pbf and urijs (except the i18next internationalisation stuff which can be stripped out)

@nf-s thanks I could make it work

Either of you make any progress on this with working code? I was going to try to hack together an implementation soon as well.

@davenquinn this code works well with polygons
https://github.com/TerriaJS/terriajs/blob/master/lib/Map/MapboxVectorTileImageryProvider.js

Hi,  I am currently working an an implementation of a StyledVector Map tile provider for Cesium.  I am doing this work for a commercial project that I am working on and am willing to contribute the code to the community project. I am making steady progress and will be continuing to develop a solution until it provides at least around 85% of the StyledVector map features.  Would the community be interested in receiving this code and if so should I submit through a pull request on a branch associated with this ticket?

@robbo1975 I think it would be great thing having vectoretiles in cesium,

@robbo1975: excited to see this contribution! It is sorely needed.
There are different strategies taken by different providers for styling vector layers (e.g. Mapbox, Carto, Deck.gl, and probably OpenLayers although I haven't looked deeply). Does your layer take a separate strategy? Or does it adopt one of the existing solutions (e.g. CartoCSS)?
Either way, would it make sense to first package the project outside of core Cesium as a separate module? This might allow it to evolve quickly and independently — if it proves to be a widely useful solution, it could easily be integrated into Cesium itself at that point. I recently packed up a terrain provider that might be a good example of how to structure an external Cesium plugin.

@davenquinn I have adopted the mapbox standard in my approach because of a need to support ESRI Vector tile services. Your suggestion of developing as an external plugin module seems eminently sensible; however, JavaScript is not my first language so I'm still trying to find my feet with all of the language concepts and associated Frameworks and tools! I will take a look at your example module and see if I can replicate the core modular capability. Thanks for your feedback :)

@robbo1975 the Mapbox standard is the most widely used, so having a renderer targeted at that would be wonderful, and extremely useful for our work as well. If you were able to create a project, I'd be happy to help with code review etc. (as someone who is mostly an outsider to Cesium, but a fairly proficient javascript developer).

Hey @robbo1975, thanks for working on this and for sharing your code! I just wanted to mention real quick that CesiumJS can't accept GPL-licensed code because of CesiumJS's much more permissive Apache 2.0 license. I suspect most CesiumJS applications would also be unable to use it. Not sure if the license was a conscious choice there, but thought I should mention it.

@kring Thanks for the observation; it was an oversight on my part.  I have updated the license to the more permissive MIT license

+1 for Mapbox vector tile support!

has there been any further development on this? There are several vector basemaps provided by esri that I would love to use as imagery providers

Hi,
Thanks for the interest. I do need to complete this project, but recently
I've been tied up with other work. I will need to complete within the next
6 months or so, but with will depend on getting time to focus on the
improvements that need to be made.
Happy to take assistance if anybody has the skills to help.
Robbo
On Thu, 24 Sep 2020, 11:01 TJPovey<EMAIL_ADDRESS>wrote:

has there been any further development on this? There are several vector
basemaps provided by esri that I would love to use as imagery providers
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/CesiumGS/cesium/issues/2132#issuecomment-698246088,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/APJN7WTFXVZQNTWKXBAXU6DSHMKHLANCNFSM4AUKTBAQ
.

Hi, here is another implementation of MapboxVectorTileImageryProvider using Mapbox-vector-tiles-basic-js-renderer, https://github.com/kikitte/MVTImageryProvider.  I hope it will help somebody who want to render mapbox vector tile in cesium.

Hi — just an update on this thread: I tried several approaches to this rendering problem for my work on visualizing Mars in advance of the Perseverance landing this week. The approach brought over from TerriaJS works well but is relatively slow. @kikitte's renderer based on the Mapbox GL fork also works well and is much quicker (that's what I ended up using, ultimately). I think some sort of WebGL approach based on Mapbox GL (pre-license-change) or Deck.gl would be appropriate long term, with the significant benefit that we could reuse some of the work on styling/symbology that has gone into these renderers. There's no reason why we couldn't have multiple vector-tile backends, too.

Updates?

Actually, yeah there are some updates! I just finished the initial public rollout of the cesium-vector-provider module and created a demo website that shows it in action.
I think this will be pretty great implementation that maximizes compatibility with the Mapbox stack, especially once some of the outstanding design deficiencies are addressed. I'm working to ensure that the project can be based directly on the rendering stack within Maplibre GL (see https://github.com/maplibre/maplibre-gl-js/issues/166). It'd be nice if we could eventually drop in a Mapbox stylesheet to Cesium and get a functional basemap.
Contributions to the project are welcome!

Hi @ebogo1, and thanks for looking at this. I agree that the size of Maplibre GL is a bit of a problem here. Right now the cesium-vector-provider module references a full/compiled version of Maplibre, but that is because I haven't figured out the right strategy for referring to things directly from their source code (a large part of the problem here is replicating their wasm compilation pipeline). This is probably simple but the module just hasn't evolved to that point.
Thinking ahead, I suspect that having this component as a standalone module makes sense. Ideally, it would just be a custom layer that can be imported with all dependencies from an external node module (this is the role that cesium-vector-provider seeks to fill). This would allow glue code between Maplibre and Cesium to have a lifecycle independent of Cesium's internals, and would allow (the large majority of) people with no need for Mapbox-compatible vector rendering to omit this heavy dependency.
I don't know if keeping things outside of the Cesium core library is a preferred approach of the team or how it fits with your development workflow, but it's how I'd try to proceed, at least initially.

I will also note that one of the potential improvements to rendering will be if we can directly render into Cesium-managed canvas contexts rather than creating our own, serializing as images, and exposing in a tile provider.
This feels like a lot of hoops to jump through and is purely a function of my and previous folks’ unfamiliarity with Cesium’s internals.

A light-weight alternative to mapbox-gl/maplibre-gl is https://github.com/protomaps/protomaps.js - it supports MVT and a subset of mapbox style spec.
We have been using it in TerriaJS for nearly a year - and it works quite well.
https://github.com/TerriaJS/terriajs/blob/main/lib/Map/ImageryProvider/ProtomapsImageryProvider.ts

For information, MapLibre is building their roadmap and calling for popular vote.
There is a proposition for a minimal build which may align with your needs @davenquinn.
See https://github.com/maplibre/maplibre/discussions/159 / https://maplibre.org/news/2023-03-13-second-call-for-bounties/

@davenquinn Any updated progress on the module?

We really look forward to vector tile (PBF) support for cesium. The newer ESRI services use this format, and currently cannot be used in cesiumjs. This is a much needed enhancement.

Fyi we're in a similar boat and our company is having a hard time justifying going all-in with Cesium because of this.


sudo: switch download from FTP to HTTPS

Many firewalls don't allow FTP traffic through; HTTPS should be preferred when
possible for both availability and performance.
Sending this PR to staging just to avoid unnecessary merge conflicts with #83394
when maintainers do the master -> staging merge.
This passes nix-build -A sudo.src --check and causes no rebuilds.

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

For reference, such changes cause no rebuilds, so they certainly don't need to go through staging.

Yeah, under normal circumstances I'd send it straight to master, but since this is not an urgent change and since there are sudo changes on the staging branch that'd cause git merge conflicts when you eventually hit master, I sent it to staging to save you and @FRidh some effort.  :)


Provider API server : Reduce length of the user secret name for consumer

This PR is to reduce the length of the user secret name that needs to be created in the consumer as Kubernetes expects the length should not be more than 63 characters when on provisioning volumes
Signed-off-by: kesavan<EMAIL_ADDRESS>

/cherry-pick release-4.10

Closing this one as we got to an agreement that this fix takes the wrong approach.
Keeping this open until we have the "right" fix, just creates confusion.


[Bug] symbolRotate for legend is neither inherited nor being set in case of scatter series.

Version
5.4
Link to Minimal Reproduction
https://echarts.apache.org/examples/en/editor.html?c=line-simple&code=PYBwLglsB2AEC8sDeAoWsAeBBDEDOAXMmurGAJ4gCmRA5AMYCGYVA5sAE7m0A0J6AE2aMiAbVoBZGL1i0AKgFcqM2gHUqAlXIAWClQDEOEFQGVmphdFoBdEgF8-6cjnxFUpMpRqyAbowA2SrT2jrB4VEZUhLCi_MQegsJiAIwArAAMPLAATADMmTnZACxZ2ckAHFnJualVRQDspQBs6dahHhTUdHhMYCwcvHHoeOQAtgBGwP4EtGBGjNCs_srtpCMTUyYQAF402ZlDYWOT_gBKwGDMNBUHCbDQjKM0tNqMr8EediRtJMusVNABAQkF87ABuIA
Steps to Reproduce
1.Plot a basic scatter chart.
2.Add symbol as triangle and symbolRotate as 180 in series object.
3.Plot legend by legend object in options
Current Behavior

Legend symbol and series symbol are not on sync.
Expected Behavior
Series symbols rotation should be inherited by legend.
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

Related to #17359


update probe exclusions to speed up install and single-node reaction

the bootstrap kube-apiserver and the single-node kube-apiserver will never be able to reach the openshift-apiserver or oauth-apiserver, so the probe check for them simply delays startup until the timeout is reached.  This updates PR excludes the reachability checks where appropriate to gain 60s.

oh, forgot the install is currently broken overall.  will recheck tomorrow

/retest

/hold
there's a type mismatch and in the slack thread, it might be more useful to actually disable these entirely for single-node so we end up more similar to microshift.


Add API filters to the frontend interface

Theres currently no filtering for data akin to the filters on the dev website provided.
They should be added to the Drakebane interface.

Optionally:
There is no filter for matchIds to filter based on game version but this could still be achieved through an internal matching of patch starts and time filters


remove package-lock.json

added package-lock.json to gitignore

Hi, thanks for creating an PR. Following the official npm documentation this file should be committed. Are there any errors you've encountered?

actually yes you're completely correct, It should be committed. I think I mixed it up with something else! sorry about that


Implement faster chebyshev evaluation

Using Python libraries is generally faster

Thanks! Could you please report timings for evaluating the ChebyshevFirstKind before and after this PR?
You can use the built-in timeit module to do this:
https://docs.python.org/3/library/timeit.html

When running 1000 random calls for n = 0 to 99 each, it took about 4.17 seconds before. With this fix, it takes about 0.33 seconds.

Thanks, that is great! To make it easier for me to understand, can you run just n=2, 4, 8, 16, 32 for one point (say x=0.5), and report the timeit for 1000 or maybe even 10000 calls as a table here in the PR with three columns: n, old method, new method.
How to make tables of GitHub Markdown:
https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/organizing-information-with-tables

Times in seconds after running 100,000 times with x = 0.5

n
Before
After

2
0.143598
0.119076

4
0.201770
0.120749

8
0.333639
0.121037

16
0.656484
0.123332

32
1.482065
0.131643

Great! This is what I thought could happen. The cost of evaluating the polynomials increases greatly with n for the old method, but is nearly constant for the new method. This will be a huge improvement for higher accuracy surrogates that contain higher order polynomials. Good find and good work!


Placeholder values can only be idents

This:
gflags::define! {
    /// Address to listen on
    -a, --addr <HOST:PORT> = "localhost:8080"
}

doesn't work, as HOST:PORT can't be parsed as an ident.

I would accept a PR to make this work, or alternatively --addr <"HOST:PORT">.

String in all cases (that would be a breaking change, and I've got code that does that), or only where necessary?

I would want it to keep working with ident, too.


@/charterafrica Dockerfile migration

Description
This PR migrates the final app, charterAFRICA, into a single multi-stage Dockerfile.
Type of change

[x] Chore

Screenshots
N/A
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation

Earth to @CodeForAfrica/tech ...

Seems like people are having Internet issues to really test this...


Returned images are poor quality (not the originals from asset library)

Calling imagePicker(_ picker: OpalImagePickerController, didFinishPickingImages images: [UIImage]) returns scaled down square images (the ones in the picker itself) instead of the full quality images.

Never mind, I realized you have to get the assets instead of the images. However, offering a function picking images only should return full images, not previews.


Added synchronized block to avoid multi thread issue of SimpleDateFormat

Because SimpleDateFormat is not thread safe, added synchronized block to avoid unexpected error due to multi thread use.

thank you !!!


HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can find and easily read information
Acceptance criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes. titled HTML, CSS, Git, and. JavaScipt with. associated notes listed

closed


Improve AutoSDE Refresher Specs

Depends on:

[x] https://github.com/ManageIQ/manageiq-providers-autosde/pull/111

Merged #111 - Can you rebase, cause this is hard to follow otherwise?

NOTE I split up the git mv of the inventory_spec -> refresher_spec into its own commit to make the changes there easier to follow


[AutoPR sql/resource-manager] [DO NOT MERGE] Managed instance updates plus examples

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5730

(message created by the CI based on PR content)

Codecov Report

Merging #4930 into restapi_auto_sql/resource-manager will decrease coverage by <.01%.
The diff coverage is 18.64%.

@@                          Coverage Diff                          @@
##           restapi_auto_sql/resource-manager    #4930      +/-   ##
=====================================================================
- Coverage                              49.79%   49.78%   -0.01%
=====================================================================
  Files                                   6223     6223
  Lines                                 174571   174603      +32
=====================================================================
+ Hits                                   86930    86934       +4
- Misses                                 87641    87669      +28

Impacted Files
Coverage Δ

azure-mgmt-sql/azure/mgmt/sql/models/__init__.py
59.02% <ø> (ø)
:arrow_up:

...ure/mgmt/sql/models/sql_management_client_enums.py
100% <100%> (ø)
:arrow_up:

...-sql/azure/mgmt/sql/models/managed_instance_py3.py
19.23% <20%> (-3.5%)
:arrow_down:

...ure/mgmt/sql/models/managed_instance_update_py3.py
19.23% <20%> (-3.5%)
:arrow_down:

...gmt/sql/operations/managed_instances_operations.py
16.75% <9.09%> (-1.04%)
:arrow_down:

Continue to review full report at Codecov.

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

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/4858


BPSW: use extra strong Lucas compositeness test

Codecov Report

Merging #13 (dcd3960) into main (c9cdecb) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            6         6
  Lines          240       270   +30
  Branches        75        84    +9
=========================================
+ Hits           240       270   +30

Flag
Coverage Δ

unittests
100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/pseudoprimes/baillie_psw.py
100.00% <100.00%> (ø)

src/pseudoprimes/lucas.py
100.00% <100.00%> (ø)

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 c9cdecb...dcd3960. Read the comment docs.


bazel-deps: update to 2018-08-16

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[x] macOS
[x] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Fits CONTRIBUTING.md.

@GrahamcOfBorg build bazel-deps

No attempt on aarch64-linux (full log)
The following builds were skipped because they don't evaluate on aarch64-linux: bazel-deps
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-darwin (full log)
Attempted: bazel-deps
Partial log (click to expand)
INFO: 50 processes: 46 processwrapper-sandbox, 4 worker.
INFO: Build completed successfully, 92 total actions
INFO: Build completed successfully, 92 total actions
installing
post-installation fixup
/nix/store/5im29qx9rni3w8l3j8i2yr22sin55kxv-cctools-binutils-darwin/bin/strip is /nix/store/5im29qx9rni3w8l3j8i2yr22sin55kxv-cctools-binutils-darwin/bin/strip
stripping (with command /nix/store/5im29qx9rni3w8l3j8i2yr22sin55kxv-cctools-binutils-darwin/bin/strip and flags -S) in /nix/store/9abpqmq32dcrpj015k05j42ay2xvfyyg-bazel-deps-2018-08-16/bin
patching script interpreter paths in /nix/store/9abpqmq32dcrpj015k05j42ay2xvfyyg-bazel-deps-2018-08-16
/nix/store/9abpqmq32dcrpj015k05j42ay2xvfyyg-bazel-deps-2018-08-16/bin/.gen_maven_deps.sh-wrapped: interpreter directive changed from "/bin/bash" to "/nix/store/zbhk0jhc9y8hmbcax9nvddbik3rgsary-bash-4.4-p23/bin/bash"
/nix/store/9abpqmq32dcrpj015k05j42ay2xvfyyg-bazel-deps-2018-08-16

Success on x86_64-linux (full log)
Attempted: bazel-deps
Partial log (click to expand)
INFO: Build completed successfully, 92 total actions
installing
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/g187k46dyb9idwflyzqgj2v06zbci7i0-bazel-deps-2018-08-16
/nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip is /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip
stripping (with command /nix/store/vp40my263xk32f07788srrgl59rycsna-binutils-2.30/bin/strip and flags -S) in /nix/store/g187k46dyb9idwflyzqgj2v06zbci7i0-bazel-deps-2018-08-16/bin
patching script interpreter paths in /nix/store/g187k46dyb9idwflyzqgj2v06zbci7i0-bazel-deps-2018-08-16
/nix/store/g187k46dyb9idwflyzqgj2v06zbci7i0-bazel-deps-2018-08-16/bin/.gen_maven_deps.sh-wrapped: interpreter directive changed from "/bin/bash" to "/nix/store/6v88ick1cxnn5g91m8qrrqww0lrlr27x-bash-4.4-p23/bin/bash"
checking for references to /build in /nix/store/g187k46dyb9idwflyzqgj2v06zbci7i0-bazel-deps-2018-08-16...
/nix/store/g187k46dyb9idwflyzqgj2v06zbci7i0-bazel-deps-2018-08-16


[Rx -> Coroutine] : Migrate methods related to persisting mutations to coroutine

Towards https://github.com/google/ground-android/issues/1581

Changes verified by running the app locally, creating a new submission and ensuring that the mutation was successfully stored to remote firestore.

@gino-m @JSunde  PTAL?

/gcbrun

/gcbrun

/gcbrun


Implement feature uttmm-24-53

Can you please fix this build warning:
Field 'ProjectRepository.uow' is never assigned to, and will always have its default value null [D:\a\TheraLang\TheraLang\examples\MvcWeb\MvcWeb.csproj]


i18n

Proposal: Internationalize the ACC interface.  Thoughts?

Unnecessary.  We serve the English Wikipedia and we users need to know proper English to even be allowed to join the team.  This is needless work.

@Matthewrbowker internal, external, or both?

@stwalkerster I am thinking more extrernal.  Both may be down the road, but I see no need for it now.
Especially with the SUL finalization, we have potential to handle account requests beyond the English Wikipedia.

Yep, I agree there's no need for the internal interface.
External feels like a good idea at first glance, but you've got to think about several things:

Effort involved (extracting to a messages table isn't too hard, but there'll have to be an internal management interface there too)
Translation of page
Will users then be expected to respond in the relevant language? If so, how does oversight work?
What about updates to the text of the page for rules changes etc? Translating those as well will only add to the workload.

@stwalkerster which is why I'm proposing rather than just doing.
translatewiki.net can handle most of the translation proper from what I understand.  And wrapping the messages in a data structure wouldn't be that hard, we would either put the translations in a separate repo or as a part of the main ACC repo and just pull them occasionally.  The difficult part would be your third pint... the responding in a relevant language.  The easy answer would be to run them trough Google translate, but that probably would not be ideal.

I am against this myself, but the big reason is that we are still the English Wikipedia ACC.  We do our checks against the English Wikipedia, enforce the English Wikipedia's Username Policy (and others), etc.  Despite SUL, users who come to us need to understand this.
If we want to broaden our scope to encompass all Wikipedias because of ACC, I think we would need to have a discussion with both the Foundation about the implications of this, as well as internally decide how we want to operate (e.g., whose policies do we enforce, what wikis do we check for sockpuppetry on, etc.).  Internationalization just isn't a bridge we're even close to crossing yet.

(Some of the points I mention above aren't issues inherent to ACC either, but to SUL on a whole - for example, the practicability of enforcing enwiki's UPol on accounts now that accounts are global.  As far as I know, there is no global username policy.  But that's a whole other issue that needs a discussion well beyond the scope of ACC.)

(Ugh, sorry for the spam :P)
Actually, on second thought, this might be something to consider, but executed in a slightly different way - perhaps we should be offering internationalization insofar as to offer the tool to other language wikis (and other projects, as well) that wish to offer their own ACC.  I think with the way things are, the most practical way to do things would be to have a separate ACC with its own team for each language, since they would be able to specialize in their relevant policies (of course, this would also require a discussion with the Foundation, but anyway).
If this is the case, I think the best way to do internationalization would be to work directly with those interested in running their language's ACC, instead of using Translatewiki or a similar service, simply because ACC is not really of brought enough interest IMO.

So looking at it from a technical standpoint, ever since the move to Smarty, it's not been possible to customize interface messages from the web UI - it has to be done in code. I've been pushing this way due to the horrendously fragile and production-dependent nature of how it was implemented.
We could achieve i18n-capability by re-adding this functionality to the web UI, so that other copies of the tool would be able to customise their interface. Maybe that's what we should be looking at.
I do have some minor security concerns for code injection.
For the record, I'm kinda neutral on the technical front for this - it's a nice-to-have but practically we don't need it. As to the bureaucratic management stuff, that's someone else's problem :P
I get the feeling that this probably isn't going to happen, simply because it'll fall pretty damn low on the prioritised list, amongst @FastLizard4 's comments.

Since I'm no longer an ACC team member even though I am still on the development team, I will try to make this short expecting my input to not mean much to anyone. I agree with @cyberpower678 that this is unnecessary busy work for something that is intended to only serve the English Wikipedia. I'd be afraid that if it was made i18n compatible that the foundation would decide to just take over the project.  I had though that was why some of this kind of stuff had been left out in the first place.

Gonna close this for now, if we want to revisit it we can always reopen it :)


Remove dependency bounds on QuickCheck

Description
We have a dependency bound in QuickCheck in cardano-ledger-shelley-test and constrained-generators. We'd like to remove these constraints to enable the latest version of QuickCheck because it fixes a bug that's causing some of our other tests to fail occasionally.
Checklist

[x] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages.
New section is never added with the code changes. (See RELEASING.md)
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated.
If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[x] Self-reviewed the diff

@lehins Could you check what I've done with CHANGELOGs and versions, please


Updates command.json to use a full url value (#747)

This updates the single command.json entry to use a URL instead
of a pypi version spec. Solves Issue #747 .

Check failures seem to be based on CI system issues? Or can somebody pls hint me on how the package might cause those failures?

@casusbelli Are you still working on changed here or is this ready for review?

@ryadav88 This is ready for review! Originally there were CI issues as it seems but the change is ready. Should i trigger a review manually somehow?

@casusbelli any update here? want to make sure your updates get merged promptly. :)

@ryadav88 Will update today, was down with sickness for a few days :/

@casusbelli Ping

sorry for the delay, not forgotten but i'm currently busy. I'll come back to this!

@casusbelli any update here? If you'd like to come back to this at a later point, we should close the PR for now and reopen later.

That currently does make sense. :-/


Bug fixes on Example.Forms project

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)
I fixed Example.Forms project it had this error:
NU1106	Unable to satisfy conflicting requests for 'Xamarin.Android.Arch.Lifecycle.Runtime': Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2), Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2), Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2), Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2), Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2), Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2), Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2), Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2), Xamarin.Android.Arch.Lifecycle.Runtime (>= 1.0.3) (via package/Xamarin.Android.Support.Compat 27.0.2) Framework: (MonoAndroid,Version=v9.0)	Example.Forms.Droid
:arrow_heading_down: What is the current behavior?
The Example.Forms project build without problems.
:new: What is the new behavior (if this is a feature change)?
:boom: Does this PR introduce a breaking change?
:bug: Recommendations for testing
:memo: Links to relevant issues/docs
:thinking: Checklist before submitting

[x] All projects build
[x] Follows style guide lines
[ ] Relevant documentation was updated
[ ] Rebased onto current develop

Problem with this is that you can't test code properly. Let me think about it what would be the best stratergy. Thanks in any case for helping out so far!

@martijn00 Can you tell us why we can't test code properly? Do we need  Lottie.iOS and Lottie.Android referenced instead of Lottie.Forms?

@adrianknight89 you need both a macbook and windows to build everything. The iOS binding project can only be build on mac. The Android is possible on both. Then to make it more complicated Forms needs UWP which only build on Windows, but the project also references the iOS project because it has a nuget reference.
With this change you would not be able to debug for iOS. It's all a bit complicated but the Xamarin team said they are trying to fix it.


Adjust records in MSPileup DB for support partial pileup data placement

Impact of the new feature
Prepare MSPIleup database for handling partial pileup data placement
Is your feature request related to a problem? Please describe.
At the moment all existing documents in MSPileup DB contains empty transition record list. The new MSPileup code base requires to have full transition record at the time we need to update it. Current the code creates it on its own but we need to adjust existing records to align with it.
Describe the solution you'd like
Create a new script and run it on production cmsweb cluster within MSPileup MongoDB. It should have the following logic:

Get list of existing pileup records in MongoDB
Loop over records
For each record extract pileup name and
Create new transition record with the following content: {‘containerFraction’:1, ‘customDID’: , ‘updateTime’: gmtimeSeconds(), ‘userDN’: }
We must use WM robot DN for userDN value, e.g. /DC=ch/DC=cern/OU=Organic Units/OU=Users/CN=cmsunified/CN=658085/CN=Robot: CMS Unified account
We must use gmtimeSeconds() function or properly determine number seconds since epoch in GMT time zone

Describe alternatives you've considered
None
Additional context

@vkuznet Can you please update the project fields for this issue so that it's properly tracked?  This looks like new High priority issue that was created for the partial pileup feature.


Node scenarios with Kraken on Single Node Openshift fail because it looks for "Unknown" status when the node is trying to recover from Chaos

Node scenarios (eg Node reboot) with Kraken on Single Node Openshift fail because it looks for Unknown status when the node is trying to recover from Chaos. SNO does not go to Unknown state, it directly goes from "Connection Timeout" to Ready state.

It appears that the check for the node status stalls when it can't connect. And it does so despite the timeout parameter because it's stalling on the status call within the function that looks for unknown status.

@Noreen21 I think I know how to fix this issue but would you be able to put the output from your run. I know it was run a while ago but that would help recreate this issue and give a fix

@paigerube14 It got stuck in here:
def wait_for_unknown_status(node, timeout):
    for _ in range(timeout):
        if kubecli.get_node_status(node) == "Unknown":
            break
        time.sleep(1)
    if kubecli.get_node_status(node) != "Unknown":
        raise Exception("Node condition status isn't Unknown")

It didn't have very valuable output, if I remember correctly. It just got stuck there.
This appears to happen because kraken expects enough nodes to be online to report the node status, but the only node that can report it is offline.

@paigerube14 I have the environment that can be used to test the fix. Let me know when you are ready.


Use nodemon and Docker volumes for development

Use bind mounts for code
Use named Docker volume for nix
Use nodemon for development
A similar implementation was discussed here before: https://discord.com/channels/473161189120147456/483979558249562112/826009512561344522
This removes the need to rebuild the base docker image every time a code change happens.
Initially, I thought about doing it for development only. But I don't think it would affect portability in production, so there was no need to have divergent workflows.

The issue now is that the npm packages aren't bundled into the container, and thus you cant install this at scale on something like Kubernetes.

Yeah they are installed in the mount point in ./piston build. If such portability is really needed, we can do this for development only

Now it mounts the code on a Docker volume in development only.

Actually why not get rid of the mkYarnPackage and Yarn completely and bake the code in the container? Directories could be added to the docker image using contents in default.nix

Rebased and implemented the requested changes.

I have changed the logic to determine the image name in flake.nix according to whether it is for development (piston) or production (ghcr.io/engineer-man/piston). This allows us to have two separate images. Now ./piston test-dev will use the development image and Docker volume, and ./piston test will use the production image.
The development image is created using ./piston build-dev and started using ./piston start-dev. The production image is created using ./piston build