Spring cloud client issue with decryption locally

we are trying to decrypt some of the properties locally before connecting to spring configserver.
as per the cloud documention we use the key and encrypt.* properties in our local application.yml and additionally added spring-security-rsa in our maven pom. we found its not able to load the key while startup and seems always throwing
java.lang.UnsupportedOperationException: No decryption for FailsafeTextEncryptor. Did you configure the keystore correctly?
	at org.springframework.cloud.bootstrap.encrypt.EncryptionBootstrapConfiguration$FailsafeTextEncryptor.decrypt(EncryptionBootstrapConfiguration.java:149)
	at org.springframework.cloud.bootstrap.encrypt.EnvironmentDecryptApplicationInitializer.decrypt(EnvironmentDecryptApplicationInitializer.java:91)

when we tried in debug we observed the TextEncryptor locally is not loaded with any of the values.
any suggestions or is this really works ?

You should put the properties in bootstrap.yml if you're using config server.

for eg : if iam using appA ( spring boot ) --> connecting to ( spring config server ). iam able to load properties from configserver for appA. ( no problem with this approach )
scenario :
if i have a encrypted property which is local to appA and iam not connecting to configserver., but when i startup my appA i heard from spring cloud doc where with same encrypt.* properties in our local application yml ( which is here appA) i should be able to decrypt if i additionally add (rsa dependency).
but when i startup iam always seeing the error during decryption of that local {cipher}XXX property.

Did you put the encrypt.* properties in bootstrap.yml?

no i placed the encrypt.* in application.yml

@praveenit219 try to add encrypt.key in "bootstrap.yml". http://projects.spring.io/spring-cloud/spring-cloud.html#_key_management

config encrypt.* properties in bootstrap.yaml.

Hi,
I had a problem with the same result ( which I solved by replacing in bootstrap.yml "key-store" by "keyStore"). It seems the spring boot condition org.springframework.cloud.bootstrap.encrypt.EncryptionBootstrapConfiguration$KeyCondition only recognise encrypt.keyStore.location and encrypt.keyStore.password
if (hasProperty(environment, "encrypt.keyStore.location")) {
				if (hasProperty(environment, "encrypt.keyStore.password")) {
					return ConditionOutcome.match("Keystore found in Environment");
				}
				return ConditionOutcome
						.noMatch("Keystore found but no password in Environment");
			}

My version is 1.1.2.RELEASE.
Regards


do not suggest unnecenssary route path

Now

https://stackblitz.com/edit/hono-client-typing-issue-middleware-s95kgm?file=src%2Fapp.ts
I'll create new pullrequest about this

ok, I understood


Separate the framework and the app to distinct repos

If the repos are distinct for framework and app, other projects that reference the framework won't drag all of the app code in the submodule. Can be done pretty easily and shouldn't break any existing projects. I have done this in a downstream clone and used Carthage to setup the submodule.

@seanwoodward thanks for your suggestion. The reason why we keep it as one repo because we want some one (maybe not good at iOS development) can download the repo and "CMD+R" to run and play around the demo app. Since we support CocoaPods or Carthage, they won't package the source code from IBAnimatableApp target.
Also to shrink the repo, we did move all assets for the README.md to another repo https://github.com/JakeLin/IBAnimatable-Misc
Please let me know if you have any suggestions.

@JakeLin first, thanks for coming up with such a great framework. I can't think of a project that would not benefit from its use. And that's why I think the separation is important. Package managers pull the entire repo for each reference (Carthage anyway), so the app storyboards, etc. get pulled along with it. A few releases ago, Carthage had trouble with the single Info.plist. Developers new to iOS would probably benefit more from learning to use dependent frameworks. Even if they chose not to use a package manager, a simple git statement get's them up and running with the example app.
My two cents, for what it's worth. I am grateful for the project and look forward to contributing when I can.
Cheers.

I don't really like the idea to separate the demo project, it's really useful to have just to clone a project, open the demo workspace, and run it to have a quick idea of how it's working. However, I understand what you are saying, that makes me asking how popular open source project such as Alamofire are handling that issue?
I'm pretty sure that they are not using a separate repot for their demo project, as well as their unit tests even if they are supporting SPM, carthage... did we miss something?

@tbaranes I have seen similar setups in other frameworks and thought it made sense here, and only, because it was easy to implement.

@seanwoodward  glad you like IBAnimatable. Can you please let us know which frameworks have similar setups if you find them? Are they UI frameworks?
I agree with @tbaranes because one of my repo called SwiftWeather, it has quick detailed description https://github.com/JakeLin/SwiftWeather#how-to-build but I still occasionally receive requests for asking for help to build the project. IBAnimatable is not only a library for developers but also for designers, I have chatted with some designers before they do want some thing download and run. we may keep the demo app in the same repo now until we find better solution to handle the onboarding process.

Since we decided to keep the current project structure, we close this issue now.
@seanwoodward please let me know if you have any questions or you'd like to provide more information on this, thanks.


Resolve one compiler warning under Windows related to debugging code

I haven't been able to test this myself on Windows, but I hope that this resolves the warning. Let me know. Thanks!

Stale


port naive_path_prediction from ROS1 to ROS2

edited CMakeLists.txt, package.xml, launch file
node.cpp & node.hpp files.

Merge this after CI is passed


index out of bounds - hog::cell_histograms always computes signed gradient orientation

I think hog::cell_histograms does not take into account HogOptions.signed - the gradient orientation d is not normalized to the [0, pi) interval when we compute unsigned gradients. When we subsequently compute the orientation bin indices from d / interval, the assumption of Interpolation::from_position_wrapping (that the left index is within bounds) will be violated. This resulted in 'index out of bounds' when I tried to compute the HOG descriptor of an image with unsigned gradients: I specified 9 unsigned gradient orientation bins but the indices in o_inter were {17, 0}  when this happened.
I think this can be fixed by inserting something like
if !spec.options.signed && d >= f32::consts::PI {
   d = d - f32::consts::PI;
}

before we calculate o_inter. The = in >= is again important to avoid index out of bounds error by ensuring that d is strictly less than pi.

Thanks for the bug report. I'll fix and add a test soon.


knex.transaction(function).finally(function) breaks in 0.7.x, but works in 0.5.x

It seems in 0.5.x, you can do this:
knex.transaction(function(trx) {
    // handles transaction
}).finally(function() {
    //do something
})

But this breaks in 0.7.x (or may even 0.6.x), the documentation said otherwise.

Sorry about that - will get this fixed very soon

Should be fixed in 0.8


chore: discv4 touchups

a few more docs

preemption on message handling

looks good just remains to add tracing as mentioned on last review of this pr @mattsse


Is there any plan to support SockJS?

I do not have any plan to write SockJS support by myself, but I would be very happy if someone implements it.


Hi, when will the source code could be released?

thanks for your very interesting works, same question...

Hi, thanks for your interest in this project!
We are currently cleaning up the code and streamlining some interfaces. Our ambition is to release the code by early next year.

Thank you for your reply!

@georghess Hi Georg, thanks for the great work! Just wondering if you could give any more info on the code release timeline. Is it expected to be released within a few weeks or could it take a few months?

Hi @MartinEthier, our aim is to release it within a few weeks.

Hi @MartinEthier, our aim is to release it within a few weeks.

Hi Georg, thanks for the great work！ I would like to ask, will it be open sourced in February?

Hi @georghess, do you have any updates regarding a potential release date?

Hi,
Due to the upcoming ECCV deadline, we've unfortunately had limited bandwidth to focus on the code release. But,  starting next week we'll give it more focus.

Hi @georghess ,is there any progress about the code release?


buf: 1.3.0 -> 1.3.1

Description of changes
Updates the buf package to 1.3.1 and adds me (lucperkins) as a maintainer.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 166505 run on x86_64-linux 1

1 package built:

buf

You're welcome to add yourself as a maintainer in a separate PR or wait for the next buf update to do it. Whatever works for you

Ah, so sorry I missed this one, I got pinged on https://github.com/NixOS/nixpkgs/pull/169714 so I just merged that...

You're welcome to add yourself as a maintainer in a separate PR

Yes, very welcome!


Toolbar: Responsive Bug + Extra Buttons

Noticed a bug in the responsive state of the -ng implementation

Also noticed that there were extra buttons in the -ng implementation. Menu action + an add action button (remove icon if keeping button). If there is a need to keep these button, might want to consider design adjustment of toolbar. Too many buttons in addition to the show more icon.
PatternFly-ng:

PatternFly-design:

Also noticed that the -ng implementation has no search icon. Is that just optional?

Is the responsive issue with the spacing between rows? Note that this mimics the Angular Patternfly behavior here:
http://www.patternfly.org/angular-patternfly/#/api/patternfly.toolbars.componenet:pfToolbar
Regarding the + icon, we discussed this topic earlier with the Action component. This feature was added to support Cloud Forms. Please see: https://github.com/patternfly/patternfly-ng/issues/78.
The extra buttons are in place to demo/test the component. We're trying to achieve feature parity with Angular Patternfly. That is, provide the ability to add a custom menu and custom button icons.

We could create a second example to show the extra/custom buttons, if that's preferable?
While the components fully support patternfly designs, we may also support additional features. Thus, it's not necessarily our intention that these examples only mimic the screen shots on patternfly.org.

This appears to be an issue with Patternfly's CSS. I can reproduce the same, unresponsive layout using the Patternfly test pages.
In our case, we have a 200px margin for the navigation pane. We also have two extra buttons, so space is somewhat limited. However, when the window is made small enough, the layout suddenly shows the correct spacing.
Using fewer buttons helps, but that won't solve the underlying layout issue. We'll need to file a bug with Patternfly to fix for all repos.

Created a Patternfly issue: https://github.com/patternfly/patternfly/issues/698

Closing due to inactivity.


ES6-ify Text Basics

Test Plan:
http://localhost:8079/react-native/docs/basics-component-text.html

By analyzing the blame information on this pull request, we identified @ericnakagawa and @lacker to be potential reviewers.

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review.


Design - Compile the runtime Lexer to WebAssembly

Beyond tooling issues, we also need to deal with paradigms that cannot work with WebAssembly.
In the current runtime, the Lexer is an abstract class, and the generated actual XXXLexer inherits from it.
This paradigm won't work with WebAssembly, especially not across language targets.
Looking at a generated XXXLexer, it doesn't provide behavior, rather it provides data that the runtime Lexer will use.
Therefore an idea that comes to mind is to evolve the design as follows:

the generated XXXLexer becomes a standalone class that:

provides data to a runtime Lexer instance
forwards calls such as nextToken to that Lexer instance

the data itself sits in a LexerData record (data class in Kotlin)
the runtime Lexer becomes a concrete class that requires a LexerData record when instantiated

My plan is to first make the above work in Kotlin, then compile to Wasm.
Your comments on the proposed design are welcome.

To me seems a plan that makes sense, and it is great to start to see experiments with WASM!

This paradigm won't work with WebAssembly, especially not across language targets.

I think this depends on your goals when exposing the WASM module to target languages.
Which parts of the lexer or parser do you want to expose?

Ahhh, I get what you mean now.
But wait, what you want to do is have:

a WASM module (.wasm binary) for the runtime
a WASM module for the generated grammar
a target language wrapper over the generated grammar module

Is that correct?
In case it is, I just don't see why we would want two separate modules. Wasn't the idea to have an all-in-one bundle?

What am I missing that would make it possible to use inheritance across 1, 2 and 3

I'd leave out 3, and focus on 1 and 2, if my understand of what you want to do is indeed correct.
For that to be possible I guess you'd need the WASM component model.
However, the way Kotlin will implement the component model isn't decided yet, as far as I know.
Thus, it's also impossible to know how we will be able to expose definitions from the WASM module, and what the limitations will be.

Can't we start with migrating to Gradle and running all tests with Kotlin Wasm? Is it possible?

I would do that before, yeah. We can discuss about it in tomorrow's call in case.

Looking at a generated XXXLexer, it doesn't provide behavior,

Does this mean no actions or predicates?

Looking at a generated XXXLexer, it doesn't provide behavior,

Does this mean no actions or predicates?

No, these would be invoked via callbacks rather than inlined. We might treat actions and predicates written in Kotlin differently since these could be inlined, but we're not there yet...

Can't we start with migrating to Gradle and running all tests with Kotlin Wasm? Is it possible?

I'm not bought into this approach because due to i/o stuff, it would require using WASI, which we're not looking to support (there is no WASI for the web). I'd rather get as close as possible to our target architecture before enabling wasm compilation. But as suggested we can discuss later today.

Ahhh, I get what you mean now. But wait, what you want to do is have:

a WASM module (.wasm binary) for the runtime
a WASM module for the generated grammar
a target language wrapper over the generated grammar module

Is that correct? In case it is, I just don't see why we would want two separate modules. Wasn't the idea to have an all-in-one bundle?

No, the idea is to have a reusable wasm runtime. I can see 3 benefits:

faster build time (we don't recompile the full runtime on each grammar change)
shared module for deployments that support multiple grammars
sticks to a proven and clear separation of concerns

What am I missing that would make it possible to use inheritance across 1, 2 and 3

I'd leave out 3, and focus on 1 and 2, if my understanding of what you want to do is indeed correct. For that to be possible I guess you'd need the WASM component model.

How do you run 1 and 2 without 3 ?

However, the way Kotlin will implement the component model isn't decided yet, as far as I know. Thus, it's also impossible to know how we will be able to expose definitions from the WASM module, and what the limitations will be.

Yes in the end state we should rely on the component model. Given the rather slow speed at which things get done though, we could rely on wasm-merge for the short term (a tool that merges 2 or more modules).

I'm not bought into this approach because due to i/o stuff, it would require using WASI, which we're not looking to support (there is no WASI for the web).

If I understand correctly, Strumenta antlr kotlin repository currently supports Kotlin wasm target.

I'm not bought into this approach because due to i/o stuff, it would require using WASI, which we're not looking to support (there is no WASI for the web).

If I understand correctly, Strumenta antlr kotlin currently supports Kotlin wasm target (I see a wasmJsMain directory there).

Yes, my understanding is that in Kotlin there are two WASM targets: one generating WASM and a Js wrapper, intended for running in the browser, and a second target producing WASM for WASI. Both should be supported by the Kotlin target for ANTLR 4
@lppedd please correct me if I am wrong

Yes, Strumenta's repository supports both WASM targets (but overall, it supports * all * Kotlin targets).

due to i/o stuff

It really depends on what I/O stuff we are talking about. If I/O is moved out of the test infrastructure (or at the very beginning, before passing the ball to WASM), targeting wasmJs shouldn't be an issue.

Moving I/O out is indeed one of the preliminary activities required.
Another one is to define an API that will be exposed by the runtime and the generated parser.

Looking at a generated XXXLexer, it doesn't provide behavior,

Does this mean no actions or predicates?

No, these would be invoked via callbacks rather than inlined. We might treat actions and predicates written in Kotlin differently since these could be inlined, but we're not there yet... (it's an optimization and we shouldn't optimize first)

For actions and predicates I would suggest looking at the approach used in templating languages like Handlebars.
One of the things that makes Handlebars so portable is that the "helpers" are provided externally, so there is no host language syntax leaking into the template.
I'm aware that the functionality in #51 does not follow this approach at all, but a major release like v5 seems like a good time to change the direction on actions and predicates.


[request-feature] issued to add food emojis

I'd like to contribute to add the food emojis, please assign to me

#3 assigned to @rasvanjaya21, create new pr and we'll review and merge it, don't forget to mention your pr here

Glad to you, this is my pr #4


⚠ Bofrost.be has degraded performance

In d7903f6, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1337 ms

Resolved: Bofrost.be performance has improved in 7523bf8.


what does the id mean?

Eg:VoxCeleb/aac/id00017/lvX8diWgriA/00187.m4a,
what  do the "id00017" and  "lvX8diWgriA" mean?

And how should I idenity the each audio's person id, please~


Support code-version-system reporting through SARIF and/or rdjson output formats

In order to take advantage of a CVS's ability to highlight issues in their UI (i.e Github review/annotation), producing output in a format that standard CVS reporters (i.e. Reviewdog) can ingest will be very useful.
There are two output formats that are generic for static analysis output which are SARIF and rdjson. SARIF is a good choice for as wide a range of CVS reporters as possible and is not tied to any particular CVS reporter. However, rdjson (specific to Reviewdog) is also very good additional format to support as Reviewdog can produce very detailed reviews/annotations for the main CVS-es from such.

Hey @github-charles-murphy! Can you share a little more about how you're using tach right now, and how you'd like to use it with Review Dog? This is my first time hearing about SARIF.

I'm triggering tach from a GitHub workflow as a triggered (for the moment) workflow. I prefer this to pre-commit because my philosophy is that the PR (to be squashed-merged) is the unit of change (not an individual 'transitory' commit).
Now when I trigger a tool within a workflow which identifies source files and lines with them for critique, I like to see the results in the PR review or check annotation tab. This can be handled by CVS reporters like Reviewdog so long as the output format of the tool matches one of their input formats.
I take it that you already know about Reviewdog and its rdjson input format since you only mentioned not knowing about SARIF.
Static Analysis Result Interchange Format (SARIF) is another standard for representing a critique of source code files and lines within them. Reviewdog accepts SARIF as one of its input formats. SARIF is also produced as an output format by OWASP tools for instance.
In the GitHub actions marketplace, there are GitHub actions that automatically handle SARIF and perform code reviews/annotations (probably using Reviewdog or similar under the hood).
In terms of work for the tach team. The only requirement is to provide a --format option for the output format of tach. This is the common pattern seen with other static analysis tools.
The interface violations found by tach relate to a specific (import) line of the code which can be the target line in the SARIF/rdjson output whilst the reasoning of the violation (i.e. a all line from another location due to the use of strict inn the tach file etc) can just be referenced as part of the diagnostic text in the SARIF/rdjson output.


Changed type Output = …; with redundant explicit type to use = Self instead

(Try to merge this PR after #6 to avoid conflicts.)

Thanks @regexident
bors r+


Fix - Remove video_title from media stream and fix media_insights for reels

Closes #8 and #9
Also, thanks for creating this tap! Very helpful 😸

We just had a ticket to look at why our prod runs were failing so this is perfect timing. Will take a look shortly - thanks for contributing @GtheSheep!

also adding a fix for primary_keys being a list on insights streams


mlflow issue

Thanks for your effort,
after i run this command: python3 deploy.py /mnt/DATA2/MultiSpeaker/thousandVoices-master/TTS/basemodel
an error with mlflow:
File "deploy.py", line 63, in _deploy
with open(model.context.artifacts["meta"], 'rb') as handle:
AttributeError: 'PyFuncModel' object has no attribute 'context'

Hello,
did you package the model before trying to deploy it?
There are basically two steps

Model packaging (using MLflow)
Package the model using the artifacts in TTS/artifacts, and storing the package in packages/test_deployment

python TTS/pack.py TTS/artifacts packages/test_deployment

Model deployment
Deploy the packaged model in packages/test_deployment using a Flask server

python TTS/deploy.py packages/test_deployment

I added a short description to the main README.md I hope that helps.

Thanks for your help,
but after i run your commands i still have an error at deployment stage:
File "/mnt/DATA2/ESPnet/envespnet/lib/python3.6/site-packages/click/core.py", line 610, in invoke
return callback(*args, **kwargs)
File "TTS/deploy.py", line 77, in deploy
app = _deploy(package)
File "TTS/deploy.py", line 58, in _deploy
with open(model.context.artifacts["meta"], 'rb') as handle:
AttributeError: 'PyFuncModel' object has no attribute 'context'

Thx for the response. I can confirm that upgrading mlflow to > 1.8.0 breaks the code.

The issue should be fixed with 0b4408d
The origin of the issue is an interface change since mlflow 1.9, I have opened and issue for it at
https://github.com/mlflow/mlflow/issues/3031


Importing new csv with relationships

References

Fixes https://github.com/DSpace/DSpace/issues/3008

Description
This PR ensures that Relationships can be created through the importing of CSVs to create Items and alter existing Items.
Instructions for Reviewers
List of changes in this PR:

Creation of Relationships is possible through the import CSV
Added tests for this

How to test this PR:

Create a CSV for a new Item, add a Relationship.type metadatafield and a relationship. metadatafield in the headers. Fill them in with proper values
Verify that an Item is created with a Relationship to the specified item in the CSV
Repeat but for an existing Item, verify that a new Relationship is made

Checklist

[x] My PR is small in size (e.g. less than 1,000 lines of code, not including comments & integration tests). Exceptions may be made if previously agreed upon.
[x] My PR passes Checkstyle validation based on the Code Style Guide.
[x] My PR includes Javadoc for all new (or modified) public methods and classes. It also includes Javadoc for large or complex private methods.
[x] My PR passes all tests and includes new/updated Unit or Integration Tests based on the Code Testing Guide.
[x] If my PR includes new, third-party dependencies (in any pom.xml), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
[x] If my PR modifies the REST API, I've linked to the REST Contract page (or open PR) related to this change.

Using: /dspace/bin/dspace -h the old metadata-import isn't displayed
https://wiki.lyrasis.org/display/DSDOC7x/Batch+Metadata+Editing

There is still the issue when trying to import data that belongs to a schema "person" (like person.giveName):
# /dspace/bin/dspace metadata-import -e<EMAIL_ADDRESS>-f /tmp/0519b1e8-3774-4822-b1c8-694dc5296c31-pub.csv
The script has started
org.dspace.app.bulkedit.MetadataImportInvalidHeadingException: Bad metadata declaration in column3: givenName
        at org.dspace.app.bulkedit.DSpaceCSV.<init>(DSpaceCSV.java:190)
        at org.dspace.app.bulkedit.MetadataImport.internalRun(MetadataImport.java:195)
        at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104)
        at org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:144)
        at org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:126)
        at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:93)

@paulo-graca The issue with the "person" schema is being fixed in a different pr: https://github.com/DSpace/DSpace/pull/3036
@tdonohue Good catch, I've renamed the class as requested


[Contributing] Remove pro tip

I feel like this is not really relevant, as most users just copy the link to the issue anyway.

👍


[Human App][Server] Change the way assignments stored in Redis

Description
In order to avoid unnecessary stress on Exchange Oracle we keep user’s job assignments data in human-app using Redis. Current implementation uses “String” data type (which is basic K-V structure), where key is jobs:assigned:<user_wallet_address> and value is JSON array of all user’s assignments for all statuses (i.e. active, expired, completed). When we need to display some portion of data for the “My Jobs” tab on the UI, human-app/server reads the whole JSON from Redis by its key into memory, then does in-memory filtering (assumed, not implemented yet) and sorting and responds with a prepared page of data to the client.
Assigned jobs have different statuses, and if for “active” jobs we don’t expect to have lots of items, then for statuses like “completed” and others the size of stored data (i.e. history log) will grow over time and if we keep storing the full history under single Redis key then at some point in the future we will have different issues:

size of an item in Redis can grow over 512 Mb limit and processing for it totally breaks
at the moment, single job assignment is up to 500 bytes, that means we can store up to ~ one million of items; even though it’s a lot, reading many big objects from Redis to app is slow and if we get many in parallel they might not fit app memory
even if we assume that each user will have up to a hundred thousand of assignments, applying filtering and sorting for array of such size in application memory is slow (~200ms), and taking into account that such operation is synchronous, it will cause - significant performance degradation in case of concurrent users access
taking into account that assignments array is kept in-sync with Exchange Oracle when a user assigns or resign some job, these operations performance also will be affected

Motivation
Current approach is doomed to be ineffective due to the constantly increasing size of the data stored in a key thus causing performance issues.
Implementation details
We want to change the way we store assignments in order to eliminates aforementioned issues or alleviates them for a long period of time with the option of revisiting it in the future if needed.
However, there are potential pitfalls that need to be clarified first, so we will check different options.

Chosen solution
After discussing different options and potential trade-offs, we decided to go with the next set of changes:

change current key jobs:assigned:<user_wallet_address> to be jobs:assigned<user_wallet_address>:<oracle_address>, thus reducing the size of data stored per item (access pattern on UI is bound to oracle address, so it's fine); however still store all items there
add "retention policy" for the items we store: when doing sync of assignments (atm when assign/resign a job) we will filter out old items (configurable via .env; default is 45 days) before saving new value in Redis; filtering should be based on updated_at field since it indicates that some job entered its final status

Retention policy of 45 should allow us to reduce the number of stored items to some reasonable value. We could expect up to 10K assignments per key, but with our inputs it means working with up to 3MB of data in memory and filtering + sorting of such array takes up to 20ms, which is affordable. In case if in the future we start to see some performance degradation in case of many concurrent users - we can reduce retention period and migrate to another storage engine, but only in case if it's really needed.
Options considered
Use Redis "Hash" to store and expire the data
We could use Redis hashes with jobs:assigned<user_wallet_address>:<oracle_address> key, assignment_id as fields and assignment JSON as value and set expiration per field, but expiration for field available only starting with 7.4.0 version of Redis and in Render we can't deploy that version.
Redefine the ways we store data in Redis
We've considered different ways of changing the data model, but none of them works for good.
1. Using "Sorted Sets"
By using sorted sets (with e.g. expires_at as a score) we could reduce the amount of data we retrieve into app memory, but we would need to implement some expiration mechanism anyways to not exceed the set size.
Also this approach increase complexity of implementation wrt filtering/sorting (or removing some functionality from UI)
2. Grouping items also by some extra field, e.g. by job status jobs:assigned<user_wallet_address>:<oracle_address>:<job_status>
We still have to thing about expiration mechanism, but for more than 1 key. + implementation is unnecessarily complex
3. Storing "flat" items, i.e. jobs:assigned<user_wallet_address>:<oracle_address>:<assignment_id>
With this approach we could store and expire data easily, but retrieving pages of data is tricky: we would need to use SCAN command that matches specific pattern for keys and scans all keys. It's not recommended for use in production due to performance reasons.
Use different storage engine
it would be better for us to use different storage engine that can store all assignments in “flat” format (i.e. one item/record per assignment object) and perform all necessary filtering/sorting operations on the engine level, so our application will need to only send optimized queries.
Pros

filtering/sorting/pagination is on storage engine, i.e. offloading backend from in-memory ops on big datasets
easy control on data retention
reduced amount of traffic we run between services

Cons

we have to deploy something more complex that Redis that we have to maintain
we have to rewrite app to use new engine, which is a good portion of effort

@dnechay just wanted to point out that the assignment_id is unique per oracle, so for example we might have several oracles with assignment_id=1

Merged, not yet in production


fix: Fix fetch datasource structure on datasource creation

When a datasource is created the datasource structure is not fetched. This PR introduces this functionality when datasources are created.
Fixes #21889

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions, so we can reproduce.
Please also list any relevant details for your test configuration.
Delete anything that is not important

Manual

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] 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
[ ] PR is being merged under a feature flag

QA activity:

[ ] Test plan has been approved by relevant developers
[ ] Test plan has been peer reviewed by QA
[ ] Cypress test cases have been added and approved by either SDET or manual QA
[ ] Organized project review call with relevant stakeholders after Round 1/2 of QA
[ ] Added Test Plan Approved label after reveiwing all Cypress test

/ok-to-test

Hey @Irongade
When the  datasource is closed and reopened on the entity pane the scheme appears is this expected.
Adding the video for clarity
https://www.loom.com/share/0a327fee7a594ab3b4bb52b7cbbbd2a2

https://www.loom.com/share/0a327fee7a594ab3b4bb52b7cbbbd2a2

Hi Prapulla, As seen in the video, the datasource was not created after you deleted it, I'm not sure why that is the case. Hence why the API was not called. The PR introduces calling the API when the datasource is created.

/ok-to-test

/ci-merge-check


Rotation marker or navigation mode

I'm submitting a ...*  (check one with "x")
[x] question
[ ] any problem or bug report
[ ] feature request
If you choose 'problem or bug report', please select OS:  (check one with "x")
[x] Android
[ ] iOS
cordova information:
cordova-background-geolocation-lt 2.8.5 "BackgroundGeolocation"
cordova-plugin-background-fetch 5.1.1 "CDVBackgroundFetch"
cordova-plugin-compat 1.2.0 "Compat"
cordova-plugin-console 1.1.0 "Console"
cordova-plugin-device 1.1.6 "Device"
cordova-plugin-geolocation 2.4.3 "Geolocation"
cordova-plugin-googlemaps 2.0.11 "cordova-plugin-googlemaps"
cordova-plugin-request-location-accuracy 2.2.2 "Request Location Accuracy"
cordova-plugin-splashscreen 4.0.3 "Splashscreen"
cordova-plugin-statusbar 2.2.3 "StatusBar"
cordova-plugin-whitelist 1.3.2 "Whitelist"
ionic-plugin-keyboard 2.2.1 "Keyboard"

Current behavior:
I need to do one of two things with my map.
1 - Place the map in navigation mode (GPS Style)
2 - Rotate the icon according to polyline direction
I would like to know if there is a way to do this with maps, and if this is a separate plugin or something of the maps themselves ..

https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v1.4.0/class/Marker/README.md#create-a-flat-marker

It would not be quite what I need, the real case is this of the video, I need my marker to follow the polyline as the [https://www.youtube.com/watch?v=JIs4kLZ8qQI](rotate marker polilyne)

You need to create flat marker or own icon, then you need to rotate it by yourself.
At least the marker has setRotation() method.
https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/class/Marker/setRotation/README.md

Thanks for the moment solved my problem with the marker now I need to solve with the maps. I'll create another inssue

flat marker
https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/class/Marker/setFlat/README.md
calculate angle from A to B
https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/class/utilities/geometry/spherical/computeHeading/README.md

Hi @renanmoraes , have you been able to rotate the map? how?


Add Crossfire and Deliantra multiplayer RPG servers

Motivation for this change
This adds the necessary packages and NixOS configuration options to self-host a Crossfire or Deliantra server (a fork of an older version of Crossfire, with changes focusing on UX and new-player experience). Or both! Crossfire -- which saw its last official release five years ago, but has been under constant development since -- gets both a -stable version for the latest release and a -latest version for the SVN build.
It also includes version 1.73.0 of the Crossfire GTK client.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[X] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-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)
[X] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Updated. Since this PR was opened one of the dependencies was deleted (the commit updating it was replaced with one re-adding it at a more recent version) and the default perl version changed.

Ok, I think this is finally ready for review (again).

I think this is ready now.

Beep?

All review comments addressed; a few weren't applied, or were applied only with modifications:

fetchsvn cannot take a meta attribute
"${foo}" is not equivalent to "${toString foo}" when foo is an integer
blitz's usage of optional/optionals is necessary

And a few other problems were found and addressed:

< and > need to be escaped in option documentation or docbook falls over
deliantra-arch and deliantra-maps are (unlike the crossfire versions, which can be used as is) fairly slow to build, so I removed hydraPlatforms = [] from them

Also, github says I have a change requested by @SuperSandro2000 , but it also won't show me what the change actually is, and the "changed files" tab lists all conversations as resolved, so...hopefully I dealt with whatever that was along with everything else.

Alright, I think this is ready, or will be once ofborg finishes.

I love the modules! Such fantastic work. All the descriptions are clear enough that users won't have to read the module source code 👍 and the module source code is very well documented so that anyone who reads it will know exactly what and why things are the way they are 🚀
Full bonus points awarded, and then some more! :sparkles:

Updated the documentation for stateDir (on both crossfire and deliantra) to clarify directory autocreation behaviour. Thanks for the correction, and for all the work reviewing this more generally :)


Added shorthand for grid-area

Changes

Added gridArea function with overloads for 1-4 values (row start, column start, row end, column end)
Created logic based on grid-area MDN for missing values
Added local helper function to determine if value is a custom-ident (could be pulled into a utils if other shorthands need it)
Added unit tests for each overload

Open issues

The ValueOrArray generic did not see appropriate for the gridArea function, so I defined GridAreaInput as CSS.Property.GridArea.  I'm unsure if both value and arrays should be supported for gridArea.

check there is a CSS variable passed to the shorthand function and throw in that case (is it a valid usecase to pass a theme token to grid-area? If so, isn't it just an edge case?)

flex shorthand has been merged recently in #127 which silently fails for flex('var(--my-var)').
@layershifter, @GeoffCoxMSFT  I vote for grid-area to fail similarly, what do you think?

Discussed offline with @layershifter and @ling1726 - let's check for the CSS variable in the value and fail silently.
Either we can check for -- in the string or var(?

Discussed offline with @layershifter and @ling1726 - let's check for the CSS variable in the value and fail silently. Either we can check for -- in the string or var(?

https://github.com/kentcdodds/rtl-css-js/pull/62/files#diff-be37810fd676724e7edb9627d74b7583e7c38153b3804c2213e84ae32cf4a65fR14
That should work, it's in rtl-css-js and we've been using it internally for some time

check there is a CSS variable passed to the shorthand function and throw in that case (is it a valid usecase to pass a theme token to grid-area? If so, isn't it just an edge case?)

flex shorthand has been merged recently in #127 which silently fails for flex('var(--my-var)'). @layershifter, @GeoffCoxMSFT I vote for grid-area to fail similarly, what do you think?

I update the PR for the fail silently approach.
I also added a console.error suppression for the flex shorthand tests to avoid failing tests when running yarn test locally.
I created this codepen to see how css vars are supported. https://codepen.io/GeoffCox/pen/xxYQpdG
We could have a 6th option: Check for css var and apply it to grid-row-start etc.

I created this codepen to see how css vars are supported. https://codepen.io/GeoffCox/pen/xxYQpdG
We could have a 6th option: Check for css var and apply it to grid-row-start etc.

I am sorry, I don't follow. The codepen shows that the browser expands based on the CSS variable value:

How are you suggesting to expand the css variable?

I am sorry, I don't follow. The codepen shows that the browser expands based on the CSS variable value:
How are you suggesting to expand the css variable?

I'm saying that when we see var( in the parameter passed to the shorthand, we can output it on the individual css properties.  It would assume that the var is a value compatible with grid-row-start.  Basically pass through var references rather than erroring.


Clean Up messages Table #1617

Alternate discussion space to issue: https://github.com/CounterpartyXCP/counterparty-core/issues/1617.

@ouziel-slama You can see what I meant with the "addition" of a messages-specific index in https://next.xcp.dev/block/846205. Toggle the 'show all events' checkbox.

@jotapea looks great!!
the message_index (exposed as event_index in the API v2) should be sufficient! all events are equals, there are just no messages here.. the thing that most deserves the name "message" is the data field of the transaction table.. so in the case of events it would be the tx_hash of the event which would be the message_index..
As a regular user of your site can I suggest presenting the list of events in the following form:
EVENT_NAME:
look at the following list that you can reuse as is: https://github.com/CounterpartyXCP/counterparty-core/blob/master/counterparty-core/counterpartycore/lib/log.py#L83-L132

Thank you @ouziel-slama , I've always wanted xcpdev to just be a friendlier frontend to the raw protocol data, and it makes me VERY happy to hear you (as the top code contributor) are a regular user.
If you want, you can take this opportunity to make a PR to xcpdev-spa with your suggestion? You can literally just keep the constant in a js file, and then I'll take it from there.
And I still see the messages a bit diferent from you, but that is fine as maybe you have future plans I cannot yet foresee. So, at least for now, I'll keep the separate message-index because it is cohesive to the whole messages-first design of xcp.dev.


Unable to get exit code on cp/rsync

I want to see if a cp/rsync fails, but when I try to use $? after the command has failed (sys.exit(2)) then I just get a 0.
OS: Windows WSL
me@PC:/mnt/c/Users/me/Documents/TMP/fw# rshell -p /dev/ttyS7 cp -r ./Pycom/* /flash
Using buffer-size of 32
Connecting to /dev/ttyS7 (buffer-size 32)...
Trying to connect to REPL  connected
Retrieving sysname ... GPy
Testing if ubinascii.unhexlify exists ... Y
Retrieving root directories ... /flash/
Setting time ... Jul 26, 2022 10:27:05
Evaluating board_name ... pyboard
Retrieving time epoch ... Jan 01, 1970
timed out or error in transfer to remote: b''
me@PC:/mnt/c/Users/me/Documents/TMP/fw# echo $?
0

Sidenote:
The way I tested this, was by disconnecting the serial wires doing upload.
Sometimes this caused the program to just hit an infinite loop.

Same on Ubuntu – this is a major bummer for me because I use this in scripts with set -o errexit and wrongly assumed the whole thing was successful when rshell cp had actually failed somewhere further up in the script.

Thanks for bring this up. This isn't a path I had considered. I'll see what I can do to fix this.

I think I've fixed it so that if that if you do rshell some-command and some-command encounters an error then the exit code will be non-zero (in version 0.0.36)

Thank you! I'll be working with this in the upcoming week and will report back!


fix: increase wild level to 55

The 55 might have been a bug I guess, or it's intended who knows :D

I think it's better to allow them to show up on map when they get turned on.

Seems working lel.


Add logo to README

Using a native font has proven to be difficult, especially when
accounting for light/dark themes - github doesn't seem to allow
inheriting font colour, and putting it outside of the svg makes the
alignment all weird.
Github also doesn't support using base64'd svgs, so I decided to put
kmonad.svg in the root directory.
Suggested by @slotThe https://github.com/kmonad/kmonad/issues/269#issuecomment-856480858
Feedback is very welcome.

This could be a good occasion to add links to the Discord and to IRC?

Nice idea, but what should the wording be, and where should it go?

I guess for now (might change when the wiki gets a bit more fleshed out), it could just be an addition to the introduction (so it gets good visibility), something like:
Additionally, if you need any help or if you just want to say hi, you can join our Discord server or jump into our IRC channel. We're friendly folk!
Btw I really like this version of the logo, with the full name. The uppercase M feels maybe a little off, idk if you've tried with a lowercase one. Might be just right as is, though.

M feels maybe a little off

I had this feeling too, kinda.
I didn't really experiment with it too much tbh

I had this idea, but I can't get the execution down right.

[sorry for spam]
What about small caps?

I do think I prefer lowercase M, it looks more like a single word.
I don't like the doubled M though, it's too messy IMO. Just having the K as the logo and then completing the name looks better.
I can't open the latest one.

I do think I prefer lowercase M

Personally I'm not a fan of the way lowercase m looks tbh - in most fonts, not just this one.

it looks more like a single word.

Fair point.

On Tue, Jun 08 2021 02:52, Vermoot wrote:

I do think I prefer lowercase M, it looks more like a single word.

kmonad's name is inspired by xmonad (who would have thought :)) and
there we (e.g. in the module names) very often use and see XMonad.  From
that perspective I think KMonad reads much nicer than Kmonad

Fair point, uppercase M it is then I guess

What about all-caps?

Eh, I prefer KMonad. Seems more uh, human

Thanks!

Thank you too!

Thanks indeed!!


Stop completion suggestions within comments

Fixes #47

I'm going to merge, need to get a build out today.


Authorization interface cleanup

This removes the erroneous http.Handler interface in favor a simple SetHeaders
method that only operates on the response. Several unnecessary uses of pointer
types were also fixed up.
auth.AccessController interface now uses distribution/context.
Closes #614

LGTM

cc @jlhawn @endophage

LGTM


Reduce duplicate state in ClientScene

.readyConnection should probably be obsoleted.

Please make sure this doesn't break the Lobby or Additive examples.


Remove training_data_diags workflow

We have separate diags workflow steps for training_data and offline_ml, but it's become clear that it's not worth the effort to maintain both as the former has fallen far behind.

Resolved by #1465


Need to run rake make before using it

Before start using this i need to run rake make in the master folder. If its required then it should be mention in the readme.

https://github.com/VundleVim/Vundle.vim/issues/643

@bulllog Have you completed step 3 in the Quick Start? https://github.com/VundleVim/Vundle.Vim#quick-start
Can you explain the steps needed to reproduce your error?

@bulllog is this safe to close now?

@bulllog there's no need to run make as far as I remember, unless you're using a custom setup…
@trygveu @nfischer thanks for jumping in guys!
Closing…


update pyenv to use pyenv installer

Switch pyenv to pyenv installer, added pyenv update command to the onbuild so we won't need to change this image every time new version of python is released

should also fix themattrix/docker-tox#13

Great stuff, thanks!

Can you make sure the image is built on docker hub?


hamming weight sampling.

HWT sampling.
given parameter k, to set k coefficients of the polynomials as -1 or 1.
using reservoir sampling to make sure that each coefficient will be set with an equal probability.

Already present on PR#37.

Closing it as a consequence.


photo credits

Marquis needs to be credited for his photos

No problem will do this when i do the google link

fixed


[$500] All participants are displayed into the room name which doesn't get truncated

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.3.83-5
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @johnmlee101
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1697125883138209
Action Performed:
Go to a workspace chat and open the details panel
Expected Result:
Room name and details are easily seen and truncated if the room name is too long
Actual Result:
All room participants are dumped into the room name which doesn't get truncated
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~013cba0507a16f71f7
Upwork Job ID:<PHONE_NUMBER>513602560
Last Price Increase: 2023-10-12

This is a regression, since its not on Prod

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

This is supposed to be handled in https://github.com/Expensify/App/issues/29321#issuecomment-1758531013.

Repro on prod so I'm going to take off the deploy blocker label

cc @techievivek

We are already handling this here: https://github.com/Expensify/App/issues/29321


Review request for Microsoft.ContainerService to add version 2022-08-02-preview

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
Alread deployed to all global regions by 08/29.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
ASAP, 09/01.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[x] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[x] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[x] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

Dear review board, I would like to clarify the failures in the CI checks.
For SDK azure-powershell, it happened in our previous PR 07-02-preview. From log it seems that the reason for the failure lies in the build tool /home/cloudtest/.autorest/@autorest_powershell<EMAIL_ADDRESS>- TypeError: value.replace is not a function. This CI used to be optional and is enabled recently.
For SDK azure-sdk-for-net, it happened in our previous PR 07-02-preview. I suppose this should be a known issue. Besides it's going to be replaced by track 2 SDK, which is expected to be GA in mid-August.
For Swagger Avocado, it should be a false alert. The reported missing API 2019-10-27-preview/openShiftManagedClusters.json is deprecated and removed from ARM manifest. The other one 2022-07-02-preview/fleets.json is expected. There are no updates to this sub-rp, so it's not included in the new API as requested by the feature owner. These errors started appearing after this update of Avocado. Would really appreciate if some mechanism could be provided to disable the alarms, cc owner @ruowan.
For ~[Staging] Service API Readiness Test, from the log, it seems that this part of the check in this CI is still being implemented, and the requests sent by the testing process are invalid.
For ~[Staging] Swagger LintDiff,

Violation of ProvisioningStateValidation, LroLocationHeader and XmsLongRunningOperationOptions should be fixed by PR #20490 and PR #20491 (under review by feature owners).

DefinitionsPropertiesNamesCamelCase, I suppose there's something wrong with the scanning results.

enableCustomCATrust, already exists in previous preview API 2022-07-02-preview.
capacityReservationGroupID, already exists in previous preview API 2022-07-02-preview.
issuerURL, already exists in previous preview API 2022-07-02-preview.
blobCSIDriver, already exists in previous preview API 2022-07-02-preview.
nonResourceURLs, already exists in previous preview API 2022-07-02-preview.

Modifications to the above properties will lead to breaking changes on the service side

          "$ref": "#/definitions/ListGuardrailsVersionsResponse"

The way this API is defined it will be interpreted as a call to get a collection of guardrailsVersions , which means that this needs o be defined as a collection of ARM resources (Proxy Resources ) rahter than the free form mode you are using here

Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/preview/2022-08-02-preview/managedClusters.json:2923 in f624962. [](commit_id = f6249624d2a93d0dd77669f2343f3eb746c99871, deletion_comment = False)

      "description": "The default value is false. Outbound NAT can only be disabled if the cluster outboundType is NAT Gateway and the Windows agent pool does not have node public IP enabled."

consider updating the new boolean values to enum as described here :
https://armwiki.azurewebsites.net/rp_onboarding/process/api_review_best_practices.html#common-issues-found-in-review
Replace boolean/switch properties with better enum
A Boolean will forever have two valid values (true or false). A string enum type is always preferred. Also, properties should always provide better values just than True and False. For example two switches "isTypeA" and "isTypeB" should be replaced with one enum "type": [A, B, DefaultType]. Even if you still believe [True, False] are the correct values for a property, you should use a string enum with values [True, False] instead of boolean. Enums are always a more flexible and future proof option because they allow additional values to be added in the future in a non-breaking way, e.g. [True, False, Unknown].

Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/preview/2022-08-02-preview/managedClusters.json:5997 in f624962. [](commit_id = f6249624d2a93d0dd77669f2343f3eb746c99871, deletion_comment = False)

"GuardrailsProfile": {

Where is definition being used ? Please remove any unused definitions

Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/preview/2022-08-02-preview/managedClusters.json:7209 in f624962. [](commit_id = f6249624d2a93d0dd77669f2343f3eb746c99871, deletion_comment = False)

Hi @raosuhas . Thanks for your comments.  About the boolean variable disableOutboundNat: As discussed internally, we still want to keep the variable type as boolean, because it's used for disabling a feature on Windows OS, and it won't add additional values in the future. Thank you.

          "$ref": "#/definitions/ListGuardrailsVersionsResponse"

The way this API is defined it will be interpreted as a call to get a collection of guardrailsVersions , which means that this needs o be defined as a collection of ARM resources (Proxy Resources ) rahter than the free form mode you are using here
Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/preview/2022-08-02-preview/managedClusters.json:2923 in f624962. [](commit_id = f624962, deletion_comment = False)

Presumably an alternative would be to do something like we do for GET /subscriptions/{subscriptionId}/providers/Microsoft.ContainerService/locations/{location}/trustedAccessRoles, which returns a list of trustedAccessRoles which are not themselves resources.
So if guardrails versions weren't nested under ManagedClusters it would be OK as well?

          "$ref": "#/definitions/ListGuardrailsVersionsResponse"

The way this API is defined it will be interpreted as a call to get a collection of guardrailsVersions , which means that this needs o be defined as a collection of ARM resources (Proxy Resources ) rahter than the free form mode you are using here
Refers to: specification/containerservice/resource-manager/Microsoft.ContainerService/preview/2022-08-02-preview/managedClusters.json:2923 in f624962. [](commit_id = f624962, deletion_comment = False)

Presumably an alternative would be to do something like we do for GET /subscriptions/{subscriptionId}/providers/Microsoft.ContainerService/locations/{location}/trustedAccessRoles, which returns a list of trustedAccessRoles which are not themselves resources.
So if guardrails versions weren't nested under ManagedClusters it would be OK as well?

That one is incorrect as well since ideally all GET resources in ARM need to follow the ARM schema with the top level ARM properties like id, name and type. That one was probably missed during review.  This would cause issues with clients that make the assumption for these properties. If you want to keep it free form I would suggest converting it to a POST .. i.e "POST .../listguardrailversions"
Just as a side note Even for location based resources like the trustecaccessroles , there is an expectation that it has the type and name property which includes the location value. https://armwiki.azurewebsites.net/rp_onboarding/ResourceProviderRegistrationRoutingTypes.html#locationbased

@raosuhas, I've forwarded you a mail where we explicitly asked about exactly this kind of API to the ARM API reviewers alias and were told that, provided the set of data is readonly (GET, no user PUT), the RP has flexibility to define it as "not a resource" and rather a static list of data.
I don't think that solves your critique of it being under ManagedCluster (or does it?). But at least at the region level (like the TrustedAccessRoles API), I believe that pattern is allowed.


Curvelanes implementation

Good job. How do you implement the Curvelanes dataset training? I tried to convert Curvelanes format to Tusimple format and train with curvelane params, but the performance is much lower than reported.

For our paper, we implemented CLRerNet on Curvelanes based on CondlaneNet implementation.
config: https://github.com/aliyun/conditional-lane-detection/blob/master/configs/condlanenet/curvelanes/curvelanes_medium_train.py
data preparation: https://github.com/aliyun/conditional-lane-detection/blob/master/tools/condlanenet/curvelanes/prepare_curvelanes_datasets.py
dataset: https://github.com/aliyun/conditional-lane-detection/blob/master/mmdet/datasets/curvelanes_dataset.py
metrics:
https://github.com/aliyun/conditional-lane-detection/blob/master/tools/condlanenet/lane_metric.py
And importantly if your model is anchor-based (like CLR(er)Net and LaneATT), don't forget to set the final NMS topk larger than 4 (e.g. 16) because Curvelanes has more lanes per image than CULane.

can you provide your exact config in your experiments, i want to reproduce your  curvelanes result. For example: which nms topk did you use

OK we will add configs for Curvelanes soon. Thank you.

We have added the configs for CurveLanes.
https://github.com/hirotomusiker/CLRerNet/tree/tmp/curvelanes_config
Note that the following modules are necessary to train / test CurveLanes models but they are not ready on the above branch.

CurvelanesDataset class
Evaluation script (we use condlanenet's metric script without modification)
Dynamic img_h and img_w settings for LaneIoU (Three crop settings are used for CurveLanes depending on image sizes. LaneIoU needs the crop information.)
Segmentation mask writer for aux. segmentation loss

@hirotomusiker thanks for your great work, can you share the mask generation code to the repo? because i reference the tusimple maks generation code and the F1-score is only up to 70? i think my mask is not precision.

Thank you.
The segmentation loss is auxiliary and contributes only slightly to the performance. Probably your training or inference code has issues other than that.

@hirotomusiker thanks for your reply, i have another question, because curve lanes have dense lines and 'Y' lines, and how to deal with these scenes in your paper? i think the nms is not suitable to deal with them, and perhaps i have some misunderstands, please help point out.

Thanks for your good question. We don't deal with Y lines like CondlaneNet does. We have just simply adapted CLRerNet to the dataset. Dealing with 'Y's will further improve the performance.

We have published the code for training on CurveLanes.
https://github.com/hirotomusiker/CLRerNet/tree/feature/curvelanes
tmp/curvelanes_config branch will be removed as the above branch includes the config file.


Add JSDoc to  for clarity

Hopefully avoids some confusion like I had here https://discord.com/channels/722131463138705510/910635844119982080/1192469806180483242

Thanks


initial upload - Pädagogische Hochschule Tirol

please see https://ph-tirol.ac.at/node/512 for one of many courses that Pädagogische Hochschule Tirol offers

@MichaelPlanckh First stage of verification passed, official domain for Pädagogische Hochschule Tirol is ph-tirol.ac.at as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@MichaelPlanckh Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Syntax for Knitro with outlev

Hi, I'm currently using Knitro solver in AmplNLWriter and I want to set the outlev for Knitro. Actually I have only m = Model(with_optimizer(AmplNLWriter.Optimizer, "knitro")) and I want to add the outlev.

Hi @felipeb95,
There is some documentation in the README about how to pass options:
https://github.com/JuliaOpt/AmplNLWriter.jl#usage
I don't have Knitro, so I can't test, but you can try
model = Model(with_optimizer(AmplNLWriter.Optimizer, "knitro", ["outlev=3"]))

Note that if you have KNITRO v11 or greater, you can use https://github.com/JuliaOpt/KNITRO.jl.
(@frapac: FYI.)

Closing as stale. This doesn't appear to be an issue with AmplNLWriter.jl. Please re-open if that isn't the case.


Soul shard stack is improperly handled when interaction with a Soul Cage

In BlockCage#onInteract, the ItemStack's size is decremented by 1. However, the ItemStack is never offered back to the player's hand. This code is only working because an ItemSoulShard's max stack size is 1 - since it will always be decremented to 0, Forge will detect this and set null into the player's hand. However, this would not work for other stack sizes.
For compatibility with Sponge, which doesn't expect this kind of behavior, it would be nice if you could either:

Offer the itemstack back to the player's hand.
Handle interactions through either Item#onItemUse or Block#onBlockActivated, which already properly handle changes in the ItemStack.

I should not need to "offer the itemstack back" as I am using the same object. This is valid behavior.

I should not need to "offer the itemstack back" as I am using the same object. This is valid behavior.

Not really - it only works because you always end up setting the size to 0. If you look at PlayerInteractionManager#processRightClickBlock, the stack is never set back into the player's hand at all. The only reason it's happening in your case is because NetHandlerPlayServer#processRightClickBlock handles ItemStacks of size 0 specially.

Edit: If you are breaking Forge behavior, I don't see why this is my fault.

Sponge is technically changing Forge behavior, but this is really more of a quirk of Forge's RightClickBlock than anything else. Were the initial size anything other than 1, it would not be properly updated on the server.

Changing behavior that mods expect is equivalent to breaking it.

@TehNut: After looking at the issue more, it appears that you were absolutely correct. This was indeed a bug in Sponge, and has since been fixed.
Sorry to have wasted your time.


YamlCreate Fixes

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?
[X] Does your manifest conform to the 1.0 schema?

Might be time to resolve a known issue if others get affected by it 🙄 #20343
I've been told this is a very ineffective way of dealing with Yaml's which is why the lack of fixes 🤷♂
@palenshus @denelon

Microsoft Reviewers: Open in CodeFlow

Any eyes on this? 🤔

Stuck here!


0.000000000000001 Discrepancy

Hello.
Have the same sum of value childrens  vs parent = 868 liters (0.868 m3) but there is some discrepancy almost zero. UoM is of entities are "m3" so why more than 3 digits discrepancy?

layout: horizontal
height: 500
unit_prefix: ''
round: 3
convert_units_to: ''
min_box_size: 10
min_box_distance: 6
show_states: true
show_units: true
sections:
  - entities:
      - entity_id: sensor.adapr_na_1_licznik_glowny
        type: remaining_child_state
        childern: []
        name: Discrepancy1
        color: red
        children:
          - sensor.1_zw
          - sensor.2_zw
          - sensor.2_cwu
          - sensor.3_zw
          - sensor.3_cwu
          - sensor.4_zw
          - sensor.4_cwu
          - sensor.5_zw
          - sensor.5_cwu
          - sensor.6_zw
          - sensor.7_zw
          - sensor.7_cwu
          - sensor.8_zw
          - sensor.8_cwu
          - sensor.9_zw
          - sensor.9_cwu
          - sensor.10_zw
          - sensor.10_cwu
          - sensor.11_zw
          - sensor.11_cwu
          - sensor.12_zw
          - sensor.12_cwu
          - sensor.12a_zw
          - sensor.12a_cwu
          - sensor.adm_cwu
          - sensor.adm_zw
      - entity_id: sensor.adapr_na_1_licznik_glowny
        type: entity
        color_on_state: true
        name: Main water meter
        icon: mdi:account
        children:
          - sensor.1_zw
          - sensor.2_zw
          - sensor.2_cwu
          - sensor.3_zw
          - sensor.3_cwu
          - sensor.4_zw
          - sensor.4_cwu
          - sensor.5_zw
          - sensor.5_cwu
          - sensor.6_zw
          - sensor.7_zw
          - sensor.7_cwu
          - sensor.8_zw
          - sensor.8_cwu
          - sensor.9_zw
          - sensor.9_cwu
          - sensor.10_zw
          - sensor.10_cwu
          - sensor.11_zw
          - sensor.11_cwu
          - sensor.12_zw
          - sensor.12_cwu
          - sensor.12a_zw
          - sensor.12a_cwu
          - sensor.adm_cwu
          - sensor.adm_zw
  - entities:
      - type: entity
        children: []
        entity_id: sensor.1_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.2_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.2_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.3_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.3_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.4_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.4_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.5_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.5_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.6_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.7_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.7_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.8_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.8_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.9_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.9_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.10_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.10_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.11_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.11_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.12_zw
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.12_cwu
        unit_of_measurement: l
        convert_units_to: l
      - type: entity
        children: []
        entity_id: sensor.12a_zw
        unit_of_measurement: l
      - type: entity
        children: []
        entity_id: sensor.12a_cwu
        unit_of_measurement: l
      - type: entity
        children: []
        entity_id: sensor.adm_zw
        unit_of_measurement: l
      - type: entity
        children: []
        entity_id: sensor.adm_cwu
        unit_of_measurement: l
        convert_units_to: l
type: custom:sankey-chart
energy_date_selection: true
min_state: 0
show_names: true
show_icons: false
title: Wodociągi
wide: true
sort_by: state

PS. The same with with commented  all unit_of_measurement: l   and convert_units_to: l too:

There is sometimes random tiny error like this when doing floating point arithmetic in JS and most languages.
The best option is to add min_state: 0.001 or a similar small value, so this is not displayed.

Understood the source of issue. Buy if there is round set (in my cause to 3) then in background logic should nothing display more than 3 digits after decimal separator. In my cause 0.000000000000001 should be visible as 0.000 hence should be not display because this is zero. This is my understanding round logic. Only need adopt displaying part to round logic

Then people submit bugs that the sum of children is different than the parent. This is why min_state exists


Update Rust to 1.72.1

Forgot to prepare this before now. None of the changes impact PL/Rust in particular, but perhaps it could have a compile time impact.

This has been replaced by #388.  Closing.


[SUPPORT] Hudi update will produce duplicated records

Tips before filing an issue

Have you gone through our FAQs? yes

Join the mailing list to engage in conversations and get faster support at<EMAIL_ADDRESS>

If you have triaged this as a bug, then file an issue directly.

Describe the problem you faced
Using flink to fall into the hudi data, using spark to modify it according to the primary key, a new piece of data will be inserted. That is, a primary key has two records. Conversely, the hudi table built by spark and flink to write new data will also have one more insert based on the primary key.(用flink落入的hudi数据，用spark根据主键去修改，会插入一条新的数据。也就是一个主键有两个记录。反之也一样，spark建的hudi表，flink去落新的数据，根据主键的insert也会多一条出来)
To Reproduce
Steps to reproduce the behavior:

use flink to fall into hudi data
use spark to update hudi data according to the primary key

Expected behavior
A clear and concise description of what you expected to happen.
Environment Description

Hudi version : 0.10.0

Spark version : 3.0.1

Flink version : 1.13.1

Hadoop version :3.1.0

Storage (HDFS/S3/GCS..) : s3

Running on Docker? (yes/no) : no

Additional context
Add any other context about the problem here.
Stacktrace
Add the stacktrace of the error.

Have you checked the key gen settings?

yes, I have used the org.apache.hudi.keygen.SimpleAvroKeyGenerator as the hoodie.datasource.write.keygenerator.class,
thanks for replying

@yangzhiyue can you provide code snippets for us to replicate the problem? it's likely mismatch btw spark and flink keygen settings. cc @danny0405

Spark SQL default use ComplexAvroKeyGenerator which does not match with Flink

@yangzhiyue can you provide code snippets for us to replicate the problem? it's likely mismatch btw spark and flink keygen settings. cc @danny0405

thanks for your reply, I found I have used the wrong way to check, now I found it is ok, I am sorry for this.

I think this issue can be closed.


[Sprint: 50] XD-3090 Use Job Wait times for JdbcHdfs Acceptance Tests.

Use Job Wait times for JdbcHdfs Acceptance Tests. This should resolve Acceptance tests failures.

Merged.


Update kzg_polynomial_commitment.md

Fixed broken link to ensure documentation remains accessible and useful for readers.

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

@woodruffw


Updating version for -dev build

Summary
Releases should have their own fixed version number, so we can tell from the logs if someone is using a release package or a dev build. Would be great if there were a way to append build number so we know what build someone is running from github. I can't think of a way to automate that easily.
Comments on how to handle this moving forward are welcome
Issues closed
None filed.
Additions/modifications proposed in this pull request:

Iterate build number to v0.6.5

We could formulate a solution based on Ryan Pavlik's answer here: https://stackoverflow.com/questions/1435953/how-can-i-pass-git-sha1-to-compiler-as-definition-using-cmake
@miles200 also brought up using the hash in Discord.
Utilizing Ryan's CMake modules, we could generate a file where Version.h resides containing various git data. The branch and hash (for example -- and/or other arbitrary git data such as tag, date, etc.) can be contained in the output that is displayed from ACE_TMAIN() on startup. This would allow people to easily identify the software being troubleshot once the end user provides a copy of their output.log.

Creating a custom CMake script based off an existing example works as well.  I favor the convention you used in Version.h. I'll let you merge when ready in case there are any other tweaks you may have forgotten.


이정안님 mentoring meeting 16, 2023-06-05

Google meet, 오후 11시

https://github.com/fkdl0048/Mentoring-Project/issues/84


Added active and hover styles for buttons.

#524

Do we want to add a permanent border around the product dropdown?
I think it looks a little strange with just the highlight border around it. What we have is consistent at least.
Also, on mobile, the hover styles stay on the buttons.
Not too experienced with mobile stuff, so not sure if this is avoidable?
Could just take the style off mobile if all else fails I guess...

Will +1 once we decide on what we're doing for those things.
Looks good to me other than those minor things though :)

On mobile the hover action persists after you tap, so the styling stays in hover mode. We agreed to stay consistent with bootstrap, and the same thing happens on mobile with bootstrap buttons.


Analyze effect of the introduction of instantaneous rewards certificates on pointer addresses

currently if an address appears in a MIR certificate but is not registered, then it will be registered later in stkCreds but no pointer entry will be created in the ptrs map. This could be resolved for example by adding the ptr to the i_rwd mapping when a MIR certificate is encountered.

A challenge is that the slot of the pointer would then not correspond to the slot of the credential registration (which is the first slot of the epoch).


Tests fail with newer libraries

Issue Description
What did you expect to see happen?
The tests to pass
What did you see instead?
Several of the tests failed with things like:
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Driver.py", line 278, in <module>
framework.testFactorials:     raven()
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Driver.py", line 231, in raven
framework.testFactorials:     simulation.run()
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Simulation.py", line 1051, in run
framework.testFactorials:     stepInstance.takeAstep(stepInputDict)
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Steps.py", line 235, in takeAstep
framework.testFactorials:     self._initializeStep(inDictionary)
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Steps.py", line 191, in _initializeStep
framework.testFactorials:     self._localInitializeStep(inDictionary)
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Steps.py", line 465, in _localInitializeStep
framework.testFactorials:     self._initializeSampler(inDictionary)
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Steps.py", line 448, in _initializeSampler
framework.testFactorials:     inDictionary[self.samplerType].initialize(**self._samplerInitDict)
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Samplers/Sampler.py", line 503, in initialize
framework.testFactorials:     self.localInitialize()
framework.testFactorials:   File "/home/jjc/sub/raven/framework/Samplers/FactorialDesign.py", line 136, in localInitialize
framework.testFactorials:     if self.designMatrix != None:
framework.testFactorials: ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
framework.testFactorials:

and
framework/PostProcessors/BasicStatistics.grid_analytic: Exception in thread 0:
framework/PostProcessors/BasicStatistics.grid_analytic: Traceback (most recent call last):
framework/PostProcessors/BasicStatistics.grid_analytic:   File "/home/jjc/miniconda2/lib/python2.7/threading.py", line 801, in __bootstrap_inner
framework/PostProcessors/BasicStatistics.grid_analytic:     self.run()
framework/PostProcessors/BasicStatistics.grid_analytic:   File "/home/jjc/miniconda2/lib/python2.7/threading.py", line 754, in run
framework/PostProcessors/BasicStatistics.grid_analytic:     self.__target(*self.__args, **self.__kwargs)
framework/PostProcessors/BasicStatistics.grid_analytic:   File "/home/jjc/sub/raven/framework/Runners/SharedMemoryRunner.py", line 135, in <lambda>
framework/PostProcessors/BasicStatistics.grid_analytic:     self.thread = threading.Thread(target = lambda q, *arg : q.append(self.functionToRun(*arg)), name = self.identifier, args=(self.subque,)+tuple(self.args))
framework/PostProcessors/BasicStatistics.grid_analytic:   File "/home/jjc/sub/raven/framework/Models/PostProcessor.py", line 202, in evaluateSample
framework/PostProcessors/BasicStatistics.grid_analytic:     returnValue = (Input, self.interface.run(Input))
framework/PostProcessors/BasicStatistics.grid_analytic:   File "/home/jjc/sub/raven/framework/PostProcessors/BasicStatistics.py", line 1090, in run
framework/PostProcessors/BasicStatistics.grid_analytic:     outputDict = self.__runLocal(input)
framework/PostProcessors/BasicStatistics.grid_analytic:   File "/home/jjc/sub/raven/framework/PostProcessors/BasicStatistics.py", line 938, in __runLocal
framework/PostProcessors/BasicStatistics.grid_analytic:     if None in pbWeightsList:
framework/PostProcessors/BasicStatistics.grid_analytic: ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or

Libraries used:

numpy 1.13.0
h5py 2.7.0
scipy 0.19.0
sklearn 0.18.1
matplotlib 2.0.2

Do you have a suggested fix for the development team?
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or improvement?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[x] 1. If the issue is a defect, is the defect fixed?
[x] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[x] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[x] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[x] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

An email to the user group might be sent out of consideration, but isn't required.

This should be closed


history.block broken on iOS Safari

I haven't investigated this personally, but according to https://github.com/ReactTraining/react-router/issues/4267 it looks like history.block may be broken on iOS Safari.
/cc @kdenz

Just realized that the original issue cites lack of support in mobile Safari for beforeunload, which is actually a separate issue. We don't currently use beforeunload anywhere, so I'm going to close this.


docs(mutations): describe difference between using callbacks in useMu…

Hi Folks!
I just noticed today that there is no explicit mention in Mutations guide about the fact that callbacks passed to useMutation will behave slightly different than the ones used in .mutate.
There is only small remark about that here:

If you make multiple requests, onSuccess will fire only after the latest call you've made.

I hope it may be useful to have this information more visible and that I haven't broken any contribution rules :)

@all-contributors add @zrwsk for docs

:tada: This PR is included in version 3.34.16 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-alpha.14 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add Ubuntu 22.04 Jammy to nightly test pipelines

needs:

https://github.com/theforeman/foreman-infra/pull/1735
https://github.com/theforeman/jenkins-jobs/pull/208
packages actually be built for jammy

@evgeni are this and https://github.com/theforeman/jenkins-jobs/pull/208 now redundant?

indeed.


Filter Subprovider Adds Redundant Filters

Multiple calls to newFilter with the same parameters will create a new polling process, even if the new filter has identical params.
We should dedupe redundant filters, to avoid creating filter leaks like this.
I think this is a pretty solid first mitigation strategy for https://github.com/MetaMask/eth-block-tracker/issues/21 because even if Web3 doesn't fix their Filter leak, we'll only leak as many filters as get registered by sites the user visits, which have a chance at being much more sustainable.

This can be fixed with the inflight caching!
Should be easy to wrap the new subprovider style with the old one

Oh, fun!  We did most of this work already! :D

I found the problem I was facing in https://github.com/MetaMask/eth-block-tracker/issues/21, which is likely related to this. In filter.js, the filterIndex is inconsistently converted to hex, which results in filters failing to uninstall properly.
Here it seems to be done correctly, with everything using the hex index:
https://github.com/MetaMask/provider-engine/blob/master/subproviders/filters.js#L109
Whereas on lines 134 and 156 a combination of hex strings and integers are used as indexes. On my local machine, if I use only hex indexes the filters uninstall correctly and there are no subsequent requests.

Ack? This is a pretty simple fix that will result in big performance gains. No longer an endless queue of filter requests.
Also for reference, here are the lines where the uninstall of the filter fails: https://github.com/MetaMask/provider-engine/blob/master/subproviders/filters.js#L209-L212

Sorry if you were under some false impression that this wasn't a high priority. This is a top priority right now. I'm addressing it in a couple of different ways. If you have a change that you think will help, please, submit a PR, that would be a lot more helpful than links to lines and what you think should be changed on them.

On my local machine, if I use only hex indexes the filters uninstall correctly and there are no subsequent requests.
@chejazi yes i see that inconsistency-- can you submit a PR for it?


remove optionals from type hints

Unless a field type is None since we can't create a type for each query, and queries can select fields, hence every field is basically optional.

Fixed in #72


Visual Studio 2017 and suspend and resume

I just created a new project, based on the Hamburger template, in Visual Studio 2017. If I launch the application in the debugger, selects Suspend and shutdown, and then launch the application it’s not resumed as expected. Instead it’s restarted. In OnStartAsync the value of PreviousExecutionState is always NotRunning.
I have two projects I’m working based on Template 10. Both have the same problem as above, but for some reason suspend and resume works fine in Visual Studio 2015. None Template 10 projects also seem to support suspend and resume properly in Visual Studio 2017. It’s very confusing.

I'm seeing this with the Minimal template as well. This is with the released v1.1.12. I haven't got VS2015 on my computer still so I can't verify that aspect of it.
If I upgrade T10 to v1.1.13-preview-20161207 and repeat the start/suspend & shutdown, suspending causes this exception:
"The group or resource is not in the correct state to perform the requested operation. (Exception from HRESULT: 0x8007139F)"

Yep. Clearly PreviousExceptionState is not reliable right now.

You know @pekspro I can't thank you enough for posting this because it's killing me and it's nice to know it's not something I am doing.

@JerryNixon, I´m glad to see that a bug report could make you happy :-) I reported this as a bug in Visual Studio for a while ago:
https://developercommunity.visualstudio.com/content/problem/50470/cant-resume-uwp-application-after-suspend-and-shut.html
Since it affected all my applications I assumed it was something with Visual Studio. For a few weeks ago I tried Template Studio, and created a project and then resume/suspend worked. That was a bit unexpected! Then I created a basic Template 10 project, and the problem was back. But it worked well in Visual Studio 2015…
I'm bit fascinated by bugs like this :-) Do we know if the bug is in Template10 or VS2017? I suspect the latter, but since it works with other frameworks the evidence is not clear.

I can now confirm that I caused it.

The core problem is the extended session logic added to template 10 a few months ago. It actually prevents suspension making your app NOT suspend when it is minimized. On one hand it is awesome. On the other, it makes it so your app does not suspend - better said, so your app suspension cannot be tested without invoking suspend and then waiting 10 minutes for the session extension to expire. Ha! In version 10.2 I have removed this feature, actually, I have made it a setting to toggle on and off and default to off.

I suppose that does not address the issue in Template 10.1 does it? Okay. I will go into the current branch and disable the extended session for you and publish a new Nuget for it in about a month. I say in about a month because I am trolling through the issues for critical other things that might need to be pushed into 10.1 so we don't release two or three new ones for a small batch of updates. To be honest, I am working on 10.2 all the time and I am not looking forward to opening 10.1, but I know this is a deal.

Thanks @JerryNixon, that's a pretty good explanation :-). But I just tried to set AutoExtendExecutionSession to false manually but that didn't solve the problem :-( I also looked in Template Studio and ExtendedExecutionSession doesn't seem to be used in there at all. I have also tried to wait for more than 10 minutes after the application been terminated, both with Template 10 and Template Studio, and the problem remained.  So, I think there is something more going on.
That said, making a new version may be a good idea but personally I don't need it. If I could work around the problem that would be good enough for me :-)


Update dependency axios

Staticmaps depends on axios, setting version ^0.17.1 in its package.json. However, axios is vulnerable to DoS attacks until version 0.18. So, you might want to update staticmaps' package.json to resolve version 0.18.1 or 0.19 of axios
See here: https://www.npmjs.com/advisories/880

Cannot find any peer dependency.

Sorry, had mixed up staticmaps and staticmap and thus posted on wrong repo, my bad.


Choosing content negotiation form selection will make config that causes API crash

If you choose an option from the Content Negotiation tab and save, the resulting module.config.php will result in an error that causes a stack trace in the API.

The resulting change in the module.config.php:

And the resulting crash:

Can confirm the same is happening here. A diff for module/Api/config/module.config.php:
     'zf-content-negotiation' => [
         'controllers' => [
-            'Api\\V1\\Rpc\\MyService\\Controller' => 'Json',
+            'Api\\V1\\Rpc\\MyService\\Controller' => [
+                'content_name' => 'HalJson',
+                'selectors' => [
+                    'ZF\\Hal\\View\\HalJsonModel' => [
+                        0 => 'application/json',
+                        1 => 'application/*+json',
+                    ],
+                ],
+            ],
         ],
         'accept_whitelist' => [

Same here. From a fresh install of 1.1.0.

Yup, same here.

Fixed in zfcampus/zf-apigility-admin-ui#40 to release with 1.1.1 this week.


Fix build issues

:tada: This PR is included in version 1.9.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


i18n(pl): translate contribute.mdx

Description (required)
Translate contribute.mdx to Polish.
Discord username: HSK (hskdaking)
Related issues & labels (optional)

Suggested label: i18n
Hacktoberfest: hacktoberfest-accepted

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

pl
contribute.mdx
Localization added, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


Incorrect html tag elements in List div mixing with li

I think need replace ul li to div elements

Open https://material-ui-1dab0.firebaseapp.com/demos/lists/#nested-list
Inspect to  nested-list

Your Environment

Tech
Version

Material-UI
1.0.0-beta.19

React
16

browser
Chromium  62 and Chrome 62

Yes, you are right.


[stdlib-private][os log] Add new log methods for each specific logging level.

Also, add aliases for the logging levels for source compatibility with swift-server side logging. Create a new initializer of Logger that can directly accept an existing os log object of type OSLog. This aids in porting uses of existing os_log API to the new API.

@swift-ci Please smoke test and merge