iOS: Add peek preview on long press of story links

I can't remember when it started happening but tap & holding links is not working as it should in NewsBlur.
Tap & hold on a link in any other app in iOS  brings up the peek preview (I think it's called) of the link. It's the pop over that allows for example to share or copy the link destination. For example in Mail.app:

In NewsBlur app it selects the text like it's any other non-link text, only giving the regular text options like copy text, define, dictate etc. This is what happens in NewsBlur:

I agree, we should do a peek on long pressing links in stories.

This is a tricky one; I've investigated a couple of times, without success. The link preview does work in the simpler in-app browser, but something in the story web view is breaking it; I've tried stripping out the gesture recognizers, custom menus, JavaScript, etc, without making a difference. I'm sure I'll figure it out one day!

Just noting that this is a larger problem than no preview. Long press to share on a link inside a post doesn't work. I use this often when reading a post and adding what it links to into my read it later queue.


Why do class fields/properties violate thread-safety?

I understand that it is not a good approach to assign class fields/properties within the constructor of an IPlugin implentation and later make use of these fields/properties during the Execute-method, but why is it also a thread-safety violation when these fields/properties are set within the Execute-method?
In the example at the end of "Execute" the method "AccessViolationProperties" is called, but no other threads were created since the beginning of "Execute". I don't see where the thread-violation is coming from.
We created PluginBase and CodeActivityBase classes to reduce the amount of non-business-logic code inside our implementations of IPlugin and CodeActivity. Therefore our base classes provides multiple class fields such as PrimaryEntityId, a default IOrganizationService instance, a tracer and so on. This appeared to be a good/clean approach since we reduce the amount of copied code. We never experienced issues with this approach so far, but of course potential thread-safety issues makes me nervous.
Would you please explain in detail, why such thread-safety issues may occur and what code design should be chosen to reduce copied code without having thread-safety issues? In a previous version of our base classes we had a context class which provided all the fields/properties we commonly use. The context got created/set during the Execute method of the base class and then was passed to an abstract method "Run", which had to be implented in derived classes of PluginBase and CodeActivityBase.
Simply calling "Service.Retrieve" is just a little more comfortable than calling "context.Service.Retrieve", so we got rid of the context class and put those fields directly into the base classes. I consider bringing back the context class, but before doing so I'd like to get a confirmation that there really are potential thread-safety issues when setting class fields/properties during the Execute-method. Please explain how such issues can occur.

Dokumentdetails
⚠ Bearbeiten Sie diesen Abschnitt nicht. Er ist für die Verknüpfung von docs.microsoft.com zum GitHub-Artikel erforderlich.

ID: 7c1e71b1-7a82-b4b8-27ad-d1bbb78e3814
Version Independent ID: 7c28f677-aba1-bd0d-173e-eaf187bf32e9
Content: Entwicklung von IPlugin-Implementierungen als zustandslos - Power Apps
Content Source: powerapps-docs/developer/common-data-service/best-practices/business-logic/develop-iplugin-implementations-stateless.md
Service: powerapps
GitHub Login: @jowells
Microsoft Alias: jowells

The Execute() method can be called multiple times simultaneously on a single instance.
The article now contains an "Additional information" section that contains:

Because the platform caches plug-in class instances, the constructor is not called for every invocation of plug-in execution. For this reason, IPlugin implementations should not depend on the timing of operations in the constructor apart from obtaining static configuration data.
Another reason IPlugins should be stateless is that multiple system threads could execute the same, shared, plug-in instance concurrently.

The Execute() method can be called multiple times simultaneously on a single instance.
The article now contains an "Additional information" section that contains:

Because the platform caches plug-in class instances, the constructor is not called for every invocation of plug-in execution. For this reason, IPlugin implementations should not depend on the timing of operations in the constructor apart from obtaining static configuration data.
Another reason IPlugins should be stateless is that multiple system threads could execute the same, shared, plug-in instance concurrently.

@Martype You may want to look at Develop IPlugin implementations as stateless.


AlignTemplatedTestCases does not handle [Template] NONE as expected

If a test has set the template to none, I would not expect it to be formatted the same as the templates with a value. Even if the template has a value I would expect that the [] sections would not be aligned to the columns taking data. This is larger part of what is described in #443.
Example input:
Test Template       Test Commit Message

*** Test Cases ***    UNLINTED FILE    LINTED FILE
Misplaced Git Trailer    misplaced_trailer.txt    misplaced_trailer_linted.txt
Mixed Unordered List Symbols    mixed_unordered.txt    mixed_unordered_linted.txt
Incorrectly Ordered List    ordered.txt    ordered_linted.txt
Unaligned List Item Indention    unaligned.txt    unaligned_linted.txt
Garbage Commit Message    garbage.txt    garbage_linted.txt
Valid Commit Message    unchanged.txt    unchanged_linted.txt    ${type trailer}    ${type trailer}\n${trailer block}
Header Validation
    [Template]    NONE
    ${valid header} =    Validate Header    ${header}
    Should Be True    ${valid header}
    ${err invalid header} =    Validate Header    ${EMPTY}
    Should Not Be True    ${err invalid header}
Trailer Validation
    [Template]    NONE
    ${valid type trailer} =    Validate Type Trailer    ${type trailer}
    Should Be True    ${valid type trailer}
    ${err invalid trailer} =    Validate Type Trailer    ${EMPTY}
    Should Not Be True    ${err invalid trailer}

Generated output:
Test Template       Test Commit Message

*** Test Cases ***                  UNLINTED FILE               LINTED FILE
Misplaced Git Trailer               misplaced_trailer.txt       misplaced_trailer_linted.txt
Mixed Unordered List Symbols        mixed_unordered.txt         mixed_unordered_linted.txt
Incorrectly Ordered List            ordered.txt                 ordered_linted.txt
Unaligned List Item Indention       unaligned.txt               unaligned_linted.txt
Garbage Commit Message              garbage.txt                 garbage_linted.txt
Valid Commit Message                unchanged.txt               unchanged_linted.txt            ${type trailer}     ${type trailer}\n${trailer block}
Header Validation
                                    [Template]                  NONE
                                    ${valid header}=            Validate Header                 ${header}
                                    Should Be True              ${valid header}
                                    ${err invalid header}=      Validate Header                 ${EMPTY}
                                    Should Not Be True          ${err invalid header}
Trailer Validation
                                    [Template]                  NONE
                                    ${valid type trailer}=      Validate Type Trailer           ${type trailer}
                                    Should Be True              ${valid type trailer}
                                    ${err invalid trailer}=     Validate Type Trailer           ${EMPTY}
                                    Should Not Be True          ${err invalid trailer}

Expected output:
Test Template       Test Commit Message

*** Test Cases ***                  UNLINTED FILE               LINTED FILE
Misplaced Git Trailer               misplaced_trailer.txt       misplaced_trailer_linted.txt
Mixed Unordered List Symbols        mixed_unordered.txt         mixed_unordered_linted.txt
Incorrectly Ordered List            ordered.txt                 ordered_linted.txt
Unaligned List Item Indention       unaligned.txt               unaligned_linted.txt
Garbage Commit Message              garbage.txt                 garbage_linted.txt
Valid Commit Message                unchanged.txt               unchanged_linted.txt            ${type trailer}     ${type trailer}\n${trailer block}
Header Validation
    [Template]    NONE
    ${valid header} =    Validate Header    ${header}
    Should Be True    ${valid header}
    ${err invalid header} =    Validate Header    ${EMPTY}
    Should Not Be True    ${err invalid header}
Trailer Validation
    [Template]    NONE
    ${valid type trailer} =    Validate Type Trailer    ${type trailer}
    Should Be True    ${valid type trailer}
    ${err invalid trailer} =    Validate Type Trailer    ${EMPTY}
    Should Not Be True    ${err invalid trailer}

Interesting case and it totally makes sense. For sure we can just disable aligner if the template is set to be none. There is also option to allow such tests to be aligned by aligner for non templated tests. I will see what can be done.

Fix is included in just released Robotidy 4.0! However I recommend waiting till the Robotidy 4.0.1 is (soon) released because I introduced regression.


Is it possible to create an entity using a regular expression?

a question, is it possible to create an entity using a regular expression? (the entity would start with a # and end when typing a non-alphanumeric character)

did you find an answer to this questions?

No :sob:

Do you mean the decorator? Like a hashtag decorator to make it blue? Read this: https://draftjs.org/docs/advanced-topics-decorators#compositedecorator

@rahul1995 No, I really want entities, I needed to save information associated with a string preceded by a "#"

@Luccasoli same question, I want entity with hashtag but I don't know how.


Linux two streams main thread creation

Hi all, just a quick query about outlet creation on Linux.
I know there are some issues with Linux multithreading and the LSL, but throwing caution to the wind I've made a simple example where I'm attempting to make two outlets, one for setting marker information and the other for data, but when trying to create a second it seems to overwrite the first no matter the order, here's a simplified version which replicates the issue:
import pylsl

markerInfo = pylsl.StreamInfo("markers", "Markers", 1, 0, 'string', 'Dev')
markerOutlet = pylsl.StreamOutlet(markerInfo)
info = pylsl.StreamInfo("datatream", "EMG", 8, 250, 'float32', 'Dev')
chns = info.desc().append_child("channels")
for label in range(8):
	ch = chns.append_child("channel")
	ch.append_child_value("label", str(label+1))
	ch.append_child_value("type", "EMG")
outlet = pylsl.StreamOutlet(info)
streams = pylsl.resolve_streams()
for stream in streams:
	print(stream.name())
	print(stream.type())

Operating system: Ubuntu 22.04
Python version: 3.11.5
LSL version: 1.16.2
Any comments or suggestions of how to circumvent this issue would be greatly appreciated. (I've attempted multiprocessing but keep getting pickle errors in my more complex pybci PseudoDevice class )

Wait, silly me, i think i may have been missing libpugixml1v5
Just partitioned my home machine with a fresh install of Operating system: Ubuntu 22.04
Python version: 3.11.5
LSL version: 1.16.1 and lsllib.so 1.16.1 and this now prints both outlets, unsure if 1.16.2 has anything to do with it.


[SPARK-14149] Log exceptions in tryOrIOException

What changes were proposed in this pull request?
We ran into a problem today debugging some class loading problem during deserialization, and JVM was masking the underlying exception which made it very difficult to debug. We can however log the exceptions using try/catch ourselves in serialization/deserialization. The good thing is that all these methods are already using Utils.tryOrIOException, so we can just put the try catch and logging in a single place.
How was this patch tested?
A logging change with a manual test.

cc @yhuai

LGTM

Test build #54154 has started for PR 11951 at commit ed7766f.

Thanks - merging in master.

Test build #54154 has finished for PR 11951 at commit ed7766f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54154/
Test PASSed.

Merged build finished. Test PASSed.


Sequential job execution in stage

Hello everyone!
Consider the following scenario:

Multiple and different build pipelines in YML
Each pipeline has one stage and 3-4 jobs
Single, self-hosted agent

When multiple pipelines get enqueued, let's say for simplicity two, named P1 and P2:

Agent picks up P1, first job, finishes it, and... then, instead of continuing to the rest of the stage's jobs to finish them all in one run, back-to-back, it pauses and picks up P2 first job. And then, it follows the same back-and-forth pattern.

Desired scenario should be: Sequential execution of stage's jobs, by the same agent that started it.
I tried using exclusive lock with a variable group and the lockBehavior: sequential and all that, but it seems to ignore them all.
Agent version: v3.225.0
Host version: Windows 10 21H2
Thank you all.

@eskour -- Hello!  Thank you for your feedback.  This repo is solely for documentation issues, and this seems implementation-related.  Please consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

I am closing this issue now.  You are welcome to @ mention me for any followup.  We hope to hear from you again.


Fix README sample code errors

The README sample code should work now.

Thank you for this contribution. I added some more patches to the example in the README, so it should indeed work now.


Use the full key id for the Matt Rutter PPA

The short ID is not secure, demonstrated by a collision with "Totally
Legit Signing Key<EMAIL_ADDRESS>See https://keyserver.ubuntu.com/pks/lookup?search=0xE084DAB9&fingerprint=on&hash=on&op=vindex

https://github.com/travis-ci/travis-build/pull/1499


Facing error while using @salesforce/core on AWS serverless

Summary
I am using the @salesforce/core package and just upgraded to version 5.2.9. The issue that I am running into now is that when running the code on the server I get the error ERROR	Error: unable to determine transport target for "../../lib/logger/transformStream", even though I am using the flag SF_DISABLE_LOG_FILE: true in my env file to disable the logs. This was not happening in the previous version as the logger was honouring the flag passed in the env file.
I looked at the code and I think that this is the code that is causing the issue.
Steps To Reproduce
Any serverless project that uses the @salesforce/core package with the version. 5.2.9 with AWS serverless should have the issue with the logs disabled.
Expected result
Since I had not opted for the logs I should not have got the error.
Actual result
Serverless function threw an error
ERROR	Error: unable to determine transport target for "../../lib/logger/transformStream"
System Information
I am using zsh

@thebedroomprogrammer - the stack trace doesn't show it but I'm assuming the Logger creation is happening from other classes in @salesforce/core right?  It should be an easy fix to get in.  Thanks for reporting.


JS Standard style

https://github.com/feross/standard#badge

want to do a pr to add it? or I can when I get a chance

Will do


Add HostCertificate lines to sshd_config

Afaik, adding these lines does nothing unless the file(s) are present. Having them in let's admins supply certs instead of relying on TOFU.

Codecov Report

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

@@            Coverage Diff             @@
##           master   #13143      +/-   ##
==========================================
- Coverage   42.13%   42.11%   -0.02%
==========================================
  Files         678      678
  Lines       75041    75041
==========================================
- Hits        31617    31603      -14
- Misses      38275    38292      +17
+ Partials     5149     5146       -3

Impacted Files
Coverage Δ

models/repo_mirror.go
2.38% <0.00%> (-11.91%)
:arrow_down:

modules/cron/tasks_basic.go
87.35% <0.00%> (-3.45%)
:arrow_down:

models/unit.go
46.57% <0.00%> (-2.74%)
:arrow_down:

modules/log/event.go
59.90% <0.00%> (-1.89%)
:arrow_down:

modules/git/blame.go
75.43% <0.00%> (-1.76%)
:arrow_down:

services/mirror/mirror.go
18.51% <0.00%> (-1.35%)
:arrow_down:

routers/repo/view.go
37.47% <0.00%> (-0.65%)
:arrow_down:

models/issue_comment.go
52.93% <0.00%> (-0.16%)
:arrow_down:

models/error.go
34.39% <0.00%> (ø)

modules/util/timer.go
85.71% <0.00%> (ø)

... and 4 more

Continue to review full report at Codecov.

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

This could go into 1.13 if it is approved quickly enough.


curryRIght

How can I reproduce this method in Ramda https://lodash.com/docs#curryRight?

We so far haven't been very interested in that.  We do have partialRight.

Now I use const decrement = curryN(2, flip(dec)) http://codepen.io/xgrommx/pen/pJZbEz. partialRight probably isn't suitable.

That feels to me like a -- let's say "creative misuse" -- of flip.  I wouldn't want to guarantee that we won't some day choose to throw when you supply a unary function to flip.  I'll  try to think more on this when I'm not falling asleep.  :smile"

Not all code needs to be point-free. Wrapping third-party functions is a task to which the lambda is well suited. I would simply write:
const g = R.curry((a, b) => f(b, a));

@xgrommx if you're still interested ramda-adjunct contains implementation of curryRightN and curryRight. I had a usecase for it while bending some functions from underscore into autocurried data-last versions.


Updating code owners for backend and frontend for auto reviewer attachment

Updating code owners for backend and frontend for auto reviewer attachment

@DevilsAutumn please update the file according what suits the best.


[k8s operator] Allow every field from Credentials to be configured from a secret

Hi all
It would be useful to to extend credentials field to allow at least host and user to be picked up from a secret. Ideally every field could be picked up from the secret.
https://atlasgo.io/integrations/kubernetes/operator#credentials-object
The motivation is that we're using 3rd party software (Crossplane) to create DB and role for a microservices. As a result the k8s secret is generated with username, db host, port and password. Unfortunately Crossplane 's secret structure is static.  Also the db host / username can vary depending on Crossplane CRD config, so they can't be hardcoded in advance in Atlas CRD.
Currently as a workaround I have to generate another Atlas specific secret that contains URL from the secret created by Crossplane .
For the same purpose I also would like to have a new field of the same credentials type to be introduced for using it as a devDB credentials.
Crossplane secret for pgsql contains

username
password
endpoint (aka host)
port

Hi @eshepelyuk, thanks for your request, and it seems reasonable to pick the username and host from the secret. You will have it in the next release.

Does it also mean that devCredentials will be introduced to allow referring devDB credentials by using Crossplane secret ?

Hi @eshepelyuk, We will consider adding devCredentials. However, the operator already handles spinning up devDB for you and cleanup as well. So, may I ask if there is any special case where you need to use a custom devDB?

Does it also mean that devCredentials will be introduced to allow referring devDB credentials by using Crossplane secret ?

Hi @eshepelyuk, We will consider adding devCredentials. However, the operator already handles spinning up devDB for you and cleanup as well. So, may I ask if there is any special case where you need to use a custom devDB?

https://discord.com/channels/930720389120794674/1147429172076097647

Hi @eshepelyuk, we have released Operator v0.3.3 🎉  with more flexibility when configuring credentials #90. According to this update, we have also added a new flag prewarmDevDB to control the lifecycle of devDB. You can configure the flag as false if you want the devDB pod to be deleted entirely after the migration process. Here's an example of how to configure the flag during chart installation
helm install atlas-operator oci://ghcr.io/ariga/charts/atlas-operator --create-namespace --namespace atlas-operator --set prewarmDevDB=false

Thanks for your contribution ❤ . I will mark the issue as resolved. Feel free to create new issues if you have any ideas for improvements.

Thanks will give it a try hopefully this week.


Llama conversion

The PR captures the LLama model weights conversion from HF to FMS. This is done through a simple script and calling it as follows:
python foundation-model-stack/scripts/llama_conversion.py --input_dir=<input_path_to_hf_model> --output_dir=<output_path_to_store_fms_weights>

Tested with 7 and 13B models and it converts successfully, the weights equality themselves have not been tested. We also need to address 70B conversion separately.

have we tested running inference on the output of this script / what's the intended usage path?
I believe fms_hf_llama.save_pretrained(path_to_fms_model) will save an HF-style checkpoint (layer-sharded), which current inference scripts may not be able to handle. I think these checkpoints also wouldn't be compatible with TP-sharded model loading. i.e. if we write a script to load a 13B model this way, it's going put it all on one GPU (or use MP, which will probably be slower at inference time).

@ani300 How do we handle the above issue of checkpoint format? Ideally, once we convert to FMS, that should be the only option...

closing this PR since it is being addressed in the HF example notebooks


feat(modal): Allow inverted modals

Simple enhancement to allow inverted modals.


cw version bump

to be merged after #133

bumps cosmwasm-std version to 1.4.0
replaces deprecated to_binary, from_binary, and to_vec calls
adds clippy config file

Why not bump already to latest version? 1.5?

Why not bump already to latest version? 1.5?

didn't really consider it, just checked that neutron-sdk is on 1.4. do you think we should go to 1.5 instead?

I think so, as long as we don't include the feature flag which is not supported, we should be good with the most recent version, unless it might be broken.


Delegate input to #[proc_macro] at Rust 1.45+

Closes #62

This also fixes #20, #43, and #63 at Rust 1.45+.


[Question] Did you mean to shrink the README?

There used to be some great examples on there that I constantly used as reference.
Are those days over and it's all man hub now?

Yes. People used the README too much as documentation and, as a result, they got confused that a feature they've read about in master branch didn't work when they downloaded the latest stable release. So, it's best to use the man page now, especially after the next release when the man pages will be so much better. Of course, some people would like to read about the features of hub and examples on the web, so I'll be working on improving the Pages-powered site.
In the meantime, you can access the content that you're missing on the currently published man page online.

Thank you for the timely, well-articulated response.


Performance Enhancements #29 - candle chart

performance enhancement for the candle chart.

How exactly does this increase performance?
This actually makes the renderer loop over more labels than needed.
It also made scrolling jerkier when having 2.5K points

I'd forgot to make the same change in drawDataSet(), I've pushed the fix to the PR. please pull and run the candle demo with 2500 candles.

dataSet.entryIndex becomes slower as the chart is scrolled from left to right for datasets > 300.
I've added time measurements logs and ran the candle demo with 2500 candles (iPhone 5) and scrolled the chart all the way to the right. I've found out that the  4 lines of code with dataSet.entryForXIndex and  dataSet.entryIndex take about 70-90ms to complete and are called about 5-7 times a second i.e. (5 X 2 X 70ms) to (7 X 2 X 90ms) = 700ms to 1260ms per second are wasted.

The render loops over the same number of labels and candles as:
var entryFrom = dataSet.entryForXIndex(_minX)
var entryTo = dataSet.entryForXIndex(_maxX)
var minx = max(dataSet.entryIndex(entry: entryFrom!, isEqual: true), 0)
var maxx = min(dataSet.entryIndex(entry: entryTo!, isEqual: true) + 1, entries.count)

is always equal to
var minx = max(_minX, 0)
var maxx = min(_maxX + 1, entries.count)
You can test this easily by adding some testing code like:
var minx2 = max(_minX, 0)
var maxx2 = min(_maxX + 1, entries.count)
if (maxx != maxx2 || minx != minx2) {
println("maxx2 or minx2 are different ! ! !")
}

This introduces only a very minor improvement, even for 2500. You have probably measured in an un-optimized compilation. Anyway, I've tested and did not find any side effects.


Request: make the background of code blocks a darker color compared to the normal background color.

Currently, a code block has the same color as the normal background.

Dracula Color Pallet only provides so many colors.

@Kab1r then add some outline or something simillar

Source Blocks Seem to now have outlines


Inventory Stack Size

In the Inventory plugin, there seems to be a problem with the item stack size property. If I were to make an item with a stack size of 1, I will not be able to pick up another item. Stack size refers to how many of an item can fit in one slot, not how many can be in an inventory. Please fix this, your plugin is amazing for the development of my game, this problem is game breaking.
Ps - I realized the way the stack size property works is intentional, If you decide that you still want to keep something like it in your plugin, rename to something like max amount, which basically states how many of an item can be in an inventory, and if set to 0, infinite amount can be in the inventory, relative to stack size of course. But anyway, it is your plugin. Please do fix the stack size though.

For some reason it made two posts, probably because im on mobile...

I just ran into this exact limitation myself, having multiple inventories should mean each inventory can account for it's own maximum stack of items. Right now, the item's stack size is shared between all inventories.
Would really love for this to be changed as OP has proposed. Otherwise I'll have to find a crude workaround.


FX2_MEM EEPROM is absurdly slow

We should maybe use a faster one if it's not much more expensive, this is pretty annoying.
This also likely applies to ICE_MEM EEPROM.

That was a libfx2 bug, plus the absence of page writes. The EEPROM is actually pretty fast, around 2ms for a 64 byte page write, in practice. Though we can't even completely fill it most of the time because EP0BUF is only 64 bytes in size and not all writes are on page boundary. (This will be worse for ICE_MEM.)


how to intialize video after getting url from webservice....app crashes.. only works when the youtube video is loaded during create event

I am not sure what do you mean, please read the documentation and follow the examples.

Good day
1 Actually issue I am facing is that the   library is working ok if use it
during oncreate of activity

Now when the activity is loaded and then there is process of volley to
get link from webservice.  Now when get success in volley and get the I'd
of YouTube and when we try.to use.the library to view video it crashed

On Thu, Aug 8, 2019, 4:42 PM Pierfrancesco Soffritti <
<EMAIL_ADDRESS>wrote:

I am not sure what do you mean, please read the documentation and follow
the examples.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/PierfrancescoSoffritti/android-youtube-player/issues/406?email_source=notifications&email_token=AECX5VWPN6SINUHOIVSIDY3QDP5RBA5CNFSM4IJY4KO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD33I7MQ#issuecomment-519475122,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AECX5VTVXZFUJKPBME7CAVTQDP5RBANCNFSM4IJY4KOQ
.


Update delete-operation-issues.md

Add one more TS guide about how to troubleshoot issues when failed to delete ACR rep with error "disallowed"
Pull request guidance
Thank you for submitting your contribution to our support content! Our team works closely with subject matter experts in CSS and PMs in the product group to review all content requests to ensure technical accuracy and the best customer experience. This process can sometimes take one or more days, so we greatly appreciate your patience.
We also need your help in order to process your request as soon as possible:

We won't act on your pull request (PR) until you type "#sign-off" in a new comment in your pull request (PR) to indicate that your changes are complete.

After you sign off in your PR, the article will be tech reviewed by the PM or SME if it has more than minor changes. Once the article is approved, it will undergo a final editing pass before being merged.

#sign-off

@microsoft-github-policy-service agree company="Microsoft"

@JarrettRenshaw @chenlonglab198 the changes are correct from the technical point of view. We have similar content publicly mentioned here: https://learn.microsoft.com/en-us/troubleshoot/azure/azure-container-registry/troubleshoot-push-error-operation-disallowed-timeout#error-1-the-operation-is-disallowed-on-this-registry --> but this article it focuses on push error, while the mentioned locks can also lead to delete errors, so I agree the content should be present also in the delete TSG (https://learn.microsoft.com/en-us/troubleshoot/azure/azure-container-registry/delete-operation-issues).
As mentioned in the push doc "This issue might be caused by the write operation being disabled for repositories or images. This state denies the delete and push operations. " so you can copy that part from there, or just grammarly adjust the suggestions from Jacky.


Root 'a' tag causes: Template for directive '*' must have exactly one root element.

My directive contains an a tag as the root element with several a tags inside. AngularJS shows this error:
Template for directive 'example' must have exactly one root element.

directive template:

    ...

                edit

                delete

    ...

directive js:
angular
    .module('examples')
    .directive('example', example);

function example() {
    var directive = {
        restrict: 'E',
        replace: 'true',
        templateUrl: 'components/examples/views/example.directive.html',
        scope: {
            example: '=',
            index: '=',
            examples: '='
        },
        link: link,
        controller: ExampleDirectiveCtrl,
        controllerAs: 'vm',
        bindToController: true
    };

    return directive;

    function link(scope, $el, attr) { ... }

}

ExampleDirectiveCtrl.$inject = [ ... ];

function ExampleDirectiveCtrl( ... ) { ... }

I traced the issue back to the function removeComments on line 8312. In this function, jqLite is called with the template's content as the only argument, which returns an array of three elements instead of one element:
0: a.example
1: div.example__info
2: text

The directive won't cause any errors if I replace the root a tag with a div or remove all child a tags.
I'm using AngularJS v1.3.12.

@BastiHo you can't have links within links and divs within links might be problematic depending on the HTML version used. If you put your HTML fragment into a doc and let a browser parse it you will see that it re-organizes elements so you effectively 3 nodes (a, div, text), see: http://plnkr.co/edit/HTRmPV72Vxrr3sI37xmM?p=preview
This is really a browser trying to "fix" your HTML even before AngularJS has any chance of processing it. Please remember that AngularJS processes "live DOM" as processed / seen by a browser and not a textual representation of a template.
Closing as invalid.


couldn't find DSO to load: libyoga.so caused by: couldn't find DSO to load: libfb.so caused by:.........

this happens if I publish the app to the play store and then install the app from the play store, but if I install the apk directly to the phone then things are fine;
case of play store then phone [app crashes]:

data/data/com.myapp/lib -> doesn't exist
data/data/com.myapp/lib-0 -> .so files are here
data/data/com.myapp/[lib-1, lib-2, lib-main] -> empty
data/app/com.myapp/lib/arm64 -> empty

case of apk to phone directly [app working]:

data/data/com.myapp/[lib, lib-0, lib-1, lib-2, lib-main] -> doesn't exist
data/app/com.myapp/lib/arm64 -> .so files are here

stacktrace
msg: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libyoga.so caused by: couldn't find DSO to load: libfb.so caused by: Didn't find class "com.facebook.jni.HybridData$Destructor" on path: DexPathList[[zip file "/data/app/com.*******-*****************==/base.apk", zip file "/data/app/com.**************-*****************==/split_config.arm64_v8a.apk", zip file "/data/app/com.***********-*************==/split_config.en.apk", zip file "/data/app/com.********-*******************==/split_config.xxhdpi.apk"],nativeLibraryDirectories=[/data/app/com.*********-***************==/lib/arm64, /data/app/com.********-*******************==/base.apk!/lib/arm64-v8a, /data/app/com.********-*******************==/split_config.arm64_v8a.apk!/lib/arm64-v8a, /data/app/com.********-*******************==/split_config.en.apk!/lib/arm64-v8a, /data/app/com.********-*******************==/split_config.xxhdpi.apk!/lib/arm64-v8a, /system/lib64]] result: 0 result: 0
stacktrace: com.facebook.litho.a0: RecyclerCollectionComponent
Caused by: com.facebook.litho.a0: Column
Caused by: java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libyoga.so caused by: couldn't find DSO to load: libfb.so caused by: Didn't find class "com.facebook.jni.HybridData$Destructor" on path: DexPathList[[zip file "/data/app/com.********-*******************==/base.apk", zip file "/data/app/com.********-*******************==/split_config.arm64_v8a.apk", zip file "/data/app/com.********-*******************==/split_config.en.apk", zip file "/data/app/com.********-*******************==/split_config.xxhdpi.apk"],nativeLibraryDirectories=[/data/app/com.********-*******************==/lib/arm64, /data/app/com.********-*******************==/base.apk!/lib/arm64-v8a, /data/app/com.********-*******************==/split_config.arm64_v8a.apk!/lib/arm64-v8a, /data/app/com.********-*******************==/split_config.en.apk!/lib/arm64-v8a, /data/app/com.********-*******************==/split_config.xxhdpi.apk!/lib/arm64-v8a, /system/lib64]] result: 0 result: 0
	at com.facebook.j0.l.c(Unknown Source:343)
	at com.facebook.j0.l.o(Unknown Source:104)
	at com.facebook.j0.l.n(Unknown Source:2)
	at com.facebook.j0.l.l(Unknown Source:106)
	at com.facebook.j0.l.k(Unknown Source:1)
	at com.facebook.yoga.YogaNative.<clinit>(Unknown Source:2)
	at com.facebook.yoga.YogaNative.jni_YGConfigNew(Native Method)
	at com.facebook.yoga.a.<init>(Unknown Source:3)
	at com.facebook.yoga.b.a(Unknown Source:2)
	at com.facebook.litho.d6.a.a(Unknown Source:0)
	at com.facebook.litho.o3.<clinit>(Unknown Source:0)
	at com.facebook.litho.n2.a(Unknown Source:0)
	at com.facebook.litho.h.J1(Unknown Source:0)
	at com.facebook.litho.p2.g(Unknown Source:83)
	at com.facebook.litho.p2.f(Unknown Source:1)
	at com.facebook.litho.p2.g(Unknown Source:126)
	at com.facebook.litho.p2.f(Unknown Source:1)
	at com.facebook.litho.p2.i(Unknown Source:23)
	at com.facebook.litho.s2.z(Unknown Source:286)
	at com.facebook.litho.ComponentTree$e.d(Unknown Source:111)
	at com.facebook.litho.ComponentTree$e.c(Unknown Source:0)
	at com.facebook.litho.ComponentTree$e$a.a(Unknown Source:17)
	at com.facebook.litho.ComponentTree$e$a.call(Unknown Source:0)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at com.facebook.litho.ComponentTree$e.m(Unknown Source:15)
	at com.facebook.litho.ComponentTree.y(Unknown Source:82)
	at com.facebook.litho.ComponentTree.x(Unknown Source:96)
	at com.facebook.litho.ComponentTree.P0(Unknown Source:287)
	at com.facebook.litho.ComponentTree.T0(Unknown Source:13)
	at com.facebook.litho.ComponentTree.y0(Unknown Source:104)
	at com.facebook.litho.LithoView.onMeasure(Unknown Source:177)
	at android.view.View.measure(View.java:23233)
	at androidx.constraintlayout.widget.ConstraintLayout$c.b(Unknown Source:405)
	at e.c.b.k.m.b.a(Unknown Source:114)
	at e.c.b.k.m.b.b(Unknown Source:72)
	at e.c.b.k.m.b.d(Unknown Source:284)
	at e.c.b.k.f.Y0(Unknown Source:23)
	at androidx.constraintlayout.widget.ConstraintLayout.o(Unknown Source:135)
	at androidx.constraintlayout.widget.ConstraintLayout.onMeasure(Unknown Source:31)
	at android.view.View.measure(View.java:23233)
	at androidx.viewpager.widget.ViewPager.onMeasure(Unknown Source:234)
	at android.view.View.measure(View.java:23233)
	at androidx.constraintlayout.widget.ConstraintLayout$c.b(Unknown Source:405)
	at e.c.b.k.m.b.a(Unknown Source:114)
	at e.c.b.k.m.b.d(Unknown Source:594)
	at e.c.b.k.f.Y0(Unknown Source:23)
	at androidx.constraintlayout.widget.ConstraintLayout.o(Unknown Source:135)
	at androidx.constraintlayout.widget.ConstraintLayout.onMeasure(Unknown Source:31)
	at android.view.View.measure(View.java:23233)
	at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6748)
	at android.widget.FrameLayout.onMeasure(FrameLayout.java:185)
	at android.view.View.measure(View.java:23233)
	at androidx.constraintlayout.widget.ConstraintLayout$c.b(Unknown Source:405)
	at e.c.b.k.m.b.a(Unknown Source:114)
	at e.c.b.k.m.b.d(Unknown Source:594)
	at e.c.b.k.f.Y0(Unknown Source:23)
	at androidx.constraintlayout.widget.ConstraintLayout.o(Unknown Source:135)
	at androidx.constraintlayout.widget.ConstraintLayout.onMeasure(Unknown Source:31)
	at android.view.View.measure(View.java:23233)
	at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6748)
	at android.widget.FrameLayout.onMeasure(FrameLayout.java:185)
	at androidx.appcompat.widget.ContentFrameLayout.onMeasure(Unknown Source:154)
	at android.view.View.measure(View.java:23233)
	at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6748)
	at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1535)
	at android.widget.LinearLayout.measureVertical(LinearLayout.java:825)
	at android.widget.LinearLayout.onMeasure(LinearLayout.java:704)
	at android.view.View.measure(View.java:23233)
	at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6748)
	at android.widget.FrameLayout.onMeasure(FrameLayout.java:185)
	at android.view.View.measure(View.java:23233)
	at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6748)
	at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1535)
	at android.widget.LinearLayout.measureVertical(LinearLayout.java:825)
	at android.widget.LinearLayout.onMeasure(LinearLayout.java:704)
	at android.view.View.measure(View.java:23233)
	at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:6748)
	at android.widget.FrameLayout.onMeasure(FrameLayout.java:185)
	at com.android.internal.policy.DecorView.onMeasure(DecorView.java:729)
	at android.view.View.measure(View.java:23233)
	at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:2769)
	at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1619)
	at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1902)
	at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1507)
	at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:7431)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1019)
	at android.view.Choreographer.doCallbacks(Choreographer.java:830)
	at android.view.Choreographer.doFrame(Choreographer.java:765)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1005)
	at android.os.Handler.handleCallback(Handler.java:873)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loop(Looper.java:193)
	at android.app.ActivityThread.main(ActivityThread.java:6698)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:859)

this issue is fixed in v0.10.3


Build consistently failing on fresh project on xcode 12.2

Description
I cannot build the project in detox, It consistently fails on the build command. It is working on colleagues machine, which make this slightly more mysterious since otherwise our configurations are the same.

[x] I have tested this issue on the latest Detox release and it still reproduces

Reproduction

run detox clean-framework-cache && detox build-framework-cache
run detox build

Expected behavior

Detox builds

Screenshots

Environment (please complete the following information):

Detox: 17.14.1
React Native: 0.63.4
Node: v14.14.0
Device: iphone 12 simulator running 14.2
Xcode: 12.2
iOS:  14.2
macOS: 10.15.7

Logs
Libtool /Users/simonstern/Desktop/projects/loyalty-frontend/mobile/consumer-mobile/ios/build/Build/Products/Debug-iphonesimulator/react-native-netinfo/libreact-native-netinfo.a normal x86_64
    cd /Users/simonstern/Desktop/projects/loyalty-frontend/mobile/consumer-mobile/ios/Pods
    export IPHONEOS_DEPLOYMENT_TARGET=9.0
    export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/var/folders/w3/wwmwshgn075bxc12g9mpw9080000gn/T/yarn--1607110396745-0.13202298867541318:/Users/simonstern/Desktop/projects/loyalty-frontend/mobile/consumer-mobile/node_modules/.bin:/Users/simonstern/.config/yarn/link/node_modules/.bin:/Users/simonstern/Desktop/projects/loyalty-frontend/node_modules/.bin:/Users/simonstern/.nvm/versions/node/v14.14.0/libexec/lib/node_modules/npm/bin/node-gyp-bin:/Users/simonstern/.nvm/versions/node/v14.14.0/lib/node_modules/npm/bin/node-gyp-bin:/Users/simonstern/.nvm/versions/node/v14.14.0/bin/node_modules/npm/bin/node-gyp-bin:/Users/simonstern/.rvm/gems/ruby-2.7.0/bin:/Users/simonstern/.rvm/gems/ruby-2.7.0@global/bin:/Users/simonstern/.rvm/rubies/ruby-2.7.0/bin:/Users/simonstern/.rvm/bin:/Users/simonstern/.yarn/bin:/Users/simonstern/.config/yarn/global/node_modules/.bin:/Users/simonstern/.nvm/versions/node/v14.14.0/bin:/Users/simonstern/.yarn/bin:/Users/simonstern/.config/yarn/global/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/Library/Apple/usr/bin"
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool -static -arch_only x86_64 -D -syslibroot /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/SDKs/iPhoneSimulator14.2.sdk -L/Users/simonstern/Desktop/projects/loyalty-frontend/mobile/consumer-mobile/ios/build/Build/Products/Debug-iphonesimulator/react-native-netinfo -filelist /Users/simonstern/Desktop/projects/loyalty-frontend/mobile/consumer-mobile/ios/build/Build/Intermediates.noindex/Pods.build/Debug-iphonesimulator/react-native-netinfo.build/Objects-normal/x86_64/react-native-netinfo.LinkFileList -o /Users/simonstern/Desktop/projects/loyalty-frontend/mobile/consumer-mobile/ios/build/Build/Products/Debug-iphonesimulator/react-native-netinfo/libreact-native-netinfo.a

** BUILD FAILED **

The following build commands failed:
	CompileSwiftSources normal x86_64 com.apple.xcode.tools.swift.compiler
	CompileSwift normal x86_64 /Users/simonstern/Desktop/projects/loyalty-frontend/node_modules/lottie-react-native/src/ios/LottieReactNative/AnimationViewManagerModule.swift
	CompileSwift normal x86_64 /Users/simonstern/Desktop/projects/loyalty-frontend/node_modules/lottie-react-native/src/ios/LottieReactNative/ContainerView.swift
(3 failures)
detox[72573] ERROR: [cli.js] Error: Command failed: xcodebuild -workspace ios/Alle.xcworkspace -scheme Alle -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build -UseModernBuildSystem=NO -arch x86_64

error Command failed with exit code 1.

Appending my package.json detox config as well:
"detox": {
    "testRunner": "jest",
    "runnerConfig": "e2e/config.json",
    "verbose": true,
    "configurations": {
      "ios": {
        "binaryPath": "ios/build/Build/Products/Debug-iphonesimulator/Allē.app",
        "build": "xcodebuild -workspace ios/Alle.xcworkspace -scheme Alle -configuration Debug -sdk iphonesimulator -derivedDataPath ios/build -UseModernBuildSystem=NO -arch x86_64",
        "type": "ios.simulator",
        "device": {
          "type": "iPhone 12"
        }
      }
    }
  }

Did you read docs? Did you bother to search? Of course not.
https://github.com/wix/Detox/issues/2498

Did you read docs? Did you bother to search? Of course not.
#2498

Lets try and remember there is a person on the other end here asking these questions. I have been struggling with getting detox to work for weeks, without asking here because I have seen how you talk to other people Leo. I did search, and I did search the closed issues, but obviously didn't see that one.
Since I can't get this running, and even the maintainer has contributed to making this a really unpleasant experience, I will simply look into alternative tools.
Sorry for asking a question about the incredibly brittle tool you've created.

The problem here is that we get these questions on a daily basis, and it’s not even related to Detox. It’s stated in the docs that the build command is just a proxy for the command you provide. And that issue was asked just several days ago. It’s frustrating. You should start by first building your project with Xcode. Then find the correct xcodebuild command for your project. If you are unfamiliar with Xcode and it’s build system, this is not the place to start learning. But yes, let’s blame the inability to call xcodebuild with a few params on “our brittle tool”.

If you’d like help anyway, open an issue on stack overflow and link it here.

@simistern I got a hint from your command. and tried with this approach. https://stackoverflow.com/questions/63607158/xcode-12-building-for-ios-simulator-but-linking-in-object-file-built-for-ios
I changed my command for npm build.
xcodebuild -workspace ios/MyApp.xcworkspace -scheme MyApp -configuration Release -sdk iphonesimulator -derivedDataPath ios/build -UseModernBuildSystem=YES -arch x86_64

@simistern I got a hint from your command. and tried with this approach. and it helped.
what I tried is

changed "Build Active Architecture Only" to true on both your project and pod.
https://stackoverflow.com/questions/63607158/xcode-12-building-for-ios-simulator-but-linking-in-object-file-built-for-ios
and I changed my command to

xcodebuild -workspace ios/MyApp.xcworkspace -scheme MyApp -configuration Release -sdk iphonesimulator -derivedDataPath ios/build -UseModernBuildSystem=YES -arch x86_64

I hope it would help.

Thanks @gomdolkim , that solved my issue! A bit confusing that it had to be in release mode and with some of those other xcode flags, but it worked :) Thank you!!
I understand now that detox build is just a wrapper for xcodebuild, but maybe we can include an error message when the build fails to indicate that the issue is with xcodebuild and not detox, to prevent those errors bubbling back here and to guide newer users? I would be happy to help with this if its a (relatively) straightforward task :)

Hello,
I recently added a warning of this sort exactly to detox build, as well as adding a template to the issues that will hopefully catch these reports.
Thanks for the update.

@simistern I got a hint from your command. and tried with this approach. and it helped.
what I tried is

changed "Build Active Architecture Only" to true on both your project and pod.
https://stackoverflow.com/questions/63607158/xcode-12-building-for-ios-simulator-but-linking-in-object-file-built-for-ios
and I changed my command to

xcodebuild -workspace ios/MyApp.xcworkspace -scheme MyApp -configuration Release -sdk iphonesimulator -derivedDataPath ios/build -UseModernBuildSystem=YES -arch x86_64

I hope it would help.

It would be better if this command can be found in docs or example config


Ensure returned resolution artifacts are unique

Should hopefully fix issues sometimes seen on CIs using sbt-coursier

Should fix https://github.com/alexarchambault/coursier/issues/208, also seen on https://ci.appveyor.com/project/alexarchambault/coursier/build/536, https://ci.appveyor.com/project/alexarchambault/coursier/build/538, https://ci.appveyor.com/project/alexarchambault/coursier/build/539. The problem originates from coursier trying to download several times in parallel a given URL, and failing because of locks (there are no re-attempt to download / check things if they are locked for now).


Add Advantech interface epc_t4286-1.json

Add Advantech interface epc_t4286-1.json for Pnp certification.

Remove this pull-request.

Reopen.


Enhanced Function Signature Interpretation and Execution

The shell-craft project currently facilitates the execution of shell commands and template autofill via OpenAI's API. To extend its utility for developers, I suggest adding a feature that allows the tool to interpret function-like prompts that include a function signature and arguments for execution.
Proposed Solution
Modify the shell-craft tool to parse prompts that mimic a function call, extract the function name, arguments, and return type, and execute them. This functionality would emulate calling a function in a traditional programming environment
Example Usage
shell-craft --prompt function "add(int a, int b) -> int: add(5, 6)"

The tool would interpret this prompt and execute a function add with the provided arguments 5 and 6, expecting an integer return type.

Rewrote ticket.


Add support for RustCrypto's crypto-bigint

Hey everyone,
Currently, there are two supported bigint libraries: GMP and num-bigint. However, there is another option that hasn't been discussed here: RustCrypto's crypto-bigint (repo, crate).
It is an official Rust crate that is constant-time and no-std pure Rust. I see much value in this crate and for me this would seem like the obvious default, unless there are some other considerations that you take into account, and if so please explain them.
Esp. for WASM support this makes a lot of sense.
Thanks!

sounds great.

Any feedback from maintaners?


moved most of readme into index.md, link to github page

Coverage remained the same at 94.082% when pulling a3c0820bbfadcad1c9aa90bd5d953751cf583551 on gh-page into 78aae4bdbb46c3ff93b9f7856445576bd5ea39fa on master.


Updated information on EI332

BTW, seems that you have contributed to this project before.
Thanks for your contribution very much~😀

Added some explanation in README.md.


Tests: prevent double comment by the bot

Testing prevent double comment by the bot

Run following commands
/wallet 0x1F9FCc0E84dc2094499b848AE37Cd6a51db03Ff2
/help
After that edit, the first command /wallet 0x1F9FCc0E84dc2094499b848AE37Cd6a51db03Ff2 to /help
the bot should edit its response to wallet command with help command.

/wallet 0x1F9FCc0E84dc2094499b848AE37Cd6a51db03Ff2

/help

/help

/assign

/unassign


CancellationToken parameters in web apis appear as an expanded struct

for example
[HttpGet("SwaggerTest")]
public async Task SwaggerTest(CancellationToken cancellationToken)

is generated as
System.Threading.Tasks.Task SwaggerTestAsync(bool? isCancellationRequested, bool? canBeCanceled, IntPtr waitHandle_Handle, bool? waitHandle_SafeWaitHandle_IsInvalid, bool? waitHandle_SafeWaitHandle_IsClosed);

whereas the CancellationToken should be ignored when generating the client (CancellationTokens in MVC controllers are automagically bound to a per request token that is cancelled if the client connection drops).
swagger seems to be treating the token as a complex query parameter and expanding it as per
https://github.com/RicoSuter/NSwag/issues/96

The following error might help, shows that it's using AspNetCoreOpenApiDocumentGenerator which appears to call into an MS library.  (I'm trying to trace through it at present).
1>------ Build started: Project: Vendeq.Apps.Api, Configuration: Debug Any CPU ------
1>Vendeq.Apps.Api -> C:\dev\Vendeq.Apps.Api\Vendeq.Apps.Api\bin\Debug\netcoreapp2.2\Vendeq.Apps.Api.dll
2>------ Build started: Project: Vendeq.Apps.Api.Client, Configuration: Debug Any CPU ------
3>------ Build started: Project: Vendeq.Apps.Api.Tests, Configuration: Debug Any CPU ------
3>Vendeq.Apps.Api.Tests -> C:\dev\Vendeq.Apps.Api\Vendeq.Apps.Api.Tests\bin\Debug\netcoreapp2.2\Vendeq.Apps.Api.Tests.dll
2>NSwag command line tool for .NET Core NetCore22, toolchain v<IP_ADDRESS> (NJsonSchema v<IP_ADDRESS> (Newtonsoft.Json v<IP_ADDRESS>))
2>Visit http://NSwag.org for more information.
2>NSwag bin directory: C:\Users\mark\.nuget\packages\nswag.msbuild\13.0.4\tools\NetCore22
2>
2>Executing file 'nswag.json' with variables 'Configuration=Debug,OutputPath=obj\Debug\netcoreapp2.2\'...
2>Launcher directory: C:\Users\mark\.nuget\packages\nswag.msbuild\13.0.4\tools\NetCore22
2>dbug: Microsoft.AspNetCore.Mvc.MvcJsonOptions[0]
2>      Compatibility switch AllowInputFormatterExceptionMessages in type MvcJsonOptions is using default value False
2>dbug: Microsoft.AspNetCore.Mvc.MvcOptions[0]
2>      Compatibility switch AllowCombiningAuthorizeFilters in type MvcOptions is using default value False
2>dbug: Microsoft.AspNetCore.Mvc.MvcOptions[0]
2>      Compatibility switch AllowBindingHeaderValuesToNonStringModelTypes in type MvcOptions is using default value False
2>dbug: Microsoft.AspNetCore.Mvc.MvcOptions[0]
2>      Compatibility switch AllowValidatingTopLevelNodes in type MvcOptions is using default value False
2>dbug: Microsoft.AspNetCore.Mvc.MvcOptions[0]
2>      Compatibility switch InputFormatterExceptionPolicy in type MvcOptions is using default value AllExceptions
2>dbug: Microsoft.AspNetCore.Mvc.MvcOptions[0]
2>      Compatibility switch SuppressBindingUndefinedValueToEnumType in type MvcOptions is using default value False
2>dbug: Microsoft.AspNetCore.Mvc.MvcOptions[0]
2>      Compatibility switch EnableEndpointRouting in type MvcOptions is using default value False
2>dbug: Microsoft.AspNetCore.Mvc.MvcOptions[0]
2>      Compatibility switch MaxValidationDepth in type MvcOptions is using default value (null)
2>dbug: Microsoft.AspNetCore.Mvc.MvcOptions[0]
2>      Compatibility switch AllowShortCircuitingValidationWhenNoValidatorsArePresent in type MvcOptions is using default value False
2>dbug: Microsoft.AspNetCore.Mvc.ApiBehaviorOptions[0]
2>      Compatibility switch SuppressMapClientErrors in type ApiBehaviorOptions is using compatibility value True for version Version_2_0
2>dbug: Microsoft.AspNetCore.Mvc.ApiBehaviorOptions[0]
2>      Compatibility switch SuppressUseValidationProblemDetailsForInvalidModelStateResponses in type ApiBehaviorOptions is using compatibility value True for version Version_2_0
2>dbug: Microsoft.AspNetCore.Mvc.ApiBehaviorOptions[0]
2>      Compatibility switch AllowInferringBindingSourceForCollectionTypesAsFromQuery in type ApiBehaviorOptions is using compatibility value True for version Version_2_0
2>System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: Action 'Vendeq.Apps.Api.Controllers.GlobalAppController.UpdateBasicDetails (Vendeq.Apps.Api)' has more than one parameter that was specified or inferred as bound from request body. Only one parameter per action may be bound from body. Inspect the following parameters, and use 'FromQueryAttribute' to specify bound from query, 'FromRouteAttribute' to specify bound from route, and 'FromBodyAttribute' for parameters to be bound from body:
2>CancellationToken cancellationToken
2>BasicAppDetailsDto item
2>   at Microsoft.AspNetCore.Mvc.ApplicationModels.InferParameterBindingInfoConvention.InferParameterBindingSources(ActionModel action)
2>   at Microsoft.AspNetCore.Mvc.ApplicationModels.ApiBehaviorApplicationModelProvider.OnProvidersExecuting(ApplicationModelProviderContext context)
2>   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionDescriptorProvider.BuildModel()
2>   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionDescriptorProvider.GetDescriptors()
2>   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionDescriptorProvider.OnProvidersExecuting(ActionDescriptorProviderContext context)
2>   at Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider.UpdateCollection()
2>   at Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider.Initialize()
2>   at Microsoft.AspNetCore.Mvc.Infrastructure.DefaultActionDescriptorCollectionProvider.get_ActionDescriptors()
2>   at Microsoft.AspNetCore.Mvc.ApiExplorer.ApiDescriptionGroupCollectionProvider.get_ApiDescriptionGroups()
2>   at NSwag.Generation.AspNetCore.AspNetCoreOpenApiDocumentGenerator.GenerateAsync(Object serviceProvider)
2>   at NSwag.AspNetCore.OpenApiDocumentProvider.GenerateAsync(String documentName)
2>   at NSwag.Commands.Generation.AspNetCore.AspNetCoreToSwaggerCommand.GenerateDocumentWithDocumentProviderAsync(IWebHost host) in C:\projects\nswag\src\NSwag.Commands\Commands\Generation\AspNetCore\AspNetCoreToOpenApiCommand.cs:line 286
2>   at NSwag.Commands.Generation.AspNetCore.AspNetCoreToSwaggerCommand.GenerateDocumentAsync(AssemblyLoader assemblyLoader, IWebHost host, String currentWorkingDirectory) in C:\projects\nswag\src\NSwag.Commands\Commands\Generation\AspNetCore\AspNetCoreToOpenApiCommand.cs:line 275
2>   at NSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiGeneratorCommandEntryPoint.<>c__DisplayClass0_0.<<Process>b__0>d.MoveNext() in C:\projects\nswag\src\NSwag.Commands\Commands\Generation\AspNetCore\AspNetCoreToOpenApiGeneratorCommandEntryPoint.cs:line 30
2>--- End of stack trace from previous location where exception was thrown ---
2>   at NSwag.Commands.Generation.AspNetCore.AspNetCoreToOpenApiGeneratorCommandEntryPoint.Process(String commandContent, String outputFile, String applicationName) in C:\projects\nswag\src\NSwag.Commands\Commands\Generation\AspNetCore\AspNetCoreToOpenApiGeneratorCommandEntryPoint.cs:line 29
2>   --- End of inner exception stack trace ---
2>   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
2>   at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
2>   at NSwag.AspNetCore.Launcher.Program.Main(String[] args) in C:\projects\nswag\src\NSwag.AspNetCore.Launcher\Program.cs:line 170
2>System.InvalidOperationException: Swagger generation failed with non-zero exit code '1'.
2>   at NSwag.Commands.Generation.AspNetCore.AspNetCoreToSwaggerCommand.RunAsync(CommandLineProcessor processor, IConsoleHost host) in C:\projects\nswag\src\NSwag.Commands\Commands\Generation\AspNetCore\AspNetCoreToOpenApiCommand.cs:line 226
2>   at NSwag.Commands.NSwagDocumentBase.GenerateSwaggerDocumentAsync() in C:\projects\nswag\src\NSwag.Commands\NSwagDocumentBase.cs:line 279
2>   at NSwag.Commands.NSwagDocument.ExecuteAsync() in C:\projects\nswag\src\NSwag.Commands\NSwagDocument.cs:line 81
2>   at NSwag.Commands.Document.ExecuteDocumentCommand.ExecuteDocumentAsync(IConsoleHost host, String filePath) in C:\projects\nswag\src\NSwag.Commands\Commands\Document\ExecuteDocumentCommand.cs:line 85
2>   at NSwag.Commands.Document.ExecuteDocumentCommand.RunAsync(CommandLineProcessor processor, IConsoleHost host) in C:\projects\nswag\src\NSwag.Commands\Commands\Document\ExecuteDocumentCommand.cs:line 32
2>   at NConsole.CommandLineProcessor.ProcessSingleAsync(String[] args, Object input)
2>   at NConsole.CommandLineProcessor.ProcessAsync(String[] args, Object input)
2>   at NConsole.CommandLineProcessor.Process(String[] args, Object input)
2>   at NSwag.Commands.NSwagCommandProcessor.Process(String[] args) in C:\projects\nswag\src\NSwag.Commands\NSwagCommandProcessor.cs:line 56
2>C:\dev\Vendeq.Apps.Api\Vendeq.Apps.Api.Client\Vendeq.Apps.Api.Client.csproj(31,5): error MSB3073: The command "dotnet "C:\Users\mark\.nuget\packages\nswag.msbuild\13.0.4\build\../tools/NetCore22/dotnet-nswag.dll" run nswag.json /variables:Configuration=Debug,OutputPath=obj\Debug\netcoreapp2.2\" exited with code -1.
2>Done building project "Vendeq.Apps.Api.Client.csproj" -- FAILED.
4>------ Build started: Project: Vendeq.Apps.Functions, Configuration: Debug Any CPU ------
5>------ Build started: Project: Vendeq.Apps.Api.Client.Tests, Configuration: Debug Any CPU ------
5>CSC : error CS0006: Metadata file 'C:\dev\Vendeq.Apps.Api\Vendeq.Apps.Api.Client\bin\Debug\netcoreapp2.2\Vendeq.Apps.Api.Client.dll' could not be found
5>Done building project "Vendeq.Apps.Api.Client.Tests.csproj" -- FAILED.
4>CSC : error CS0006: Metadata file 'C:\dev\Vendeq.Apps.Api\Vendeq.Apps.Api.Client\bin\Debug\netcoreapp2.2\Vendeq.Apps.Api.Client.dll' could not be found
4>Done building project "Vendeq.Apps.Functions.csproj" -- FAILED.
6>------ Build started: Project: Vendeq.Apps.Functions.Tests, Configuration: Debug Any CPU ------
6>CSC : error CS0006: Metadata file 'C:\dev\Vendeq.Apps.Api\Vendeq.Apps.Api.Client\bin\Debug\netcoreapp2.2\Vendeq.Apps.Api.Client.dll' could not be found
6>Done building project "Vendeq.Apps.Functions.Tests.csproj" -- FAILED.
========== Build: 2 succeeded, 4 failed, 0 up-to-date, 0 skipped ==========

This is not aspnet core, right?
We need to exclude these params then

It's command line nswag on an dotnet core api via NSwag.MSBuild (v<IP_ADDRESS>) running the c# generator.
I think that the exception above is dotnet's api explorer blowing up on something tagged [ApiController], picking up the CancellationToken and assuming it should come from the request body, seeing another parameter that comes from the request body and deciding that something is amiss.  That looks like a separate bug in ApiExplorer to me -- I can work around that by suppressing the behaviour that infers binding sources and specifying them manually (services.Configure(options => options.SuppressInferBindingSourcesForParameters = true);
However even when ApiExplorer is reporting the parameters correctly the CancellationToken token parameter is interpreted as a parameter by nswag.  There doesn't seem to be any way of ignoring the parameter (both [NSwag.Annotations.OpenApiIgnore] and [NSwag.Annotations.SwaggerIgnore] have no effect).  Looking at the code it seems the JSON api generator ignores both parameters of type CancellationToken and that are tagged with ignore attributes so it would seem reasonable for them to do the same -- I'm not sure if nswag isn't doing this since ApiExplorer should be doing the filtering though (that said I can't find a way to get ApiExplorer to ignore parameters -- just whole methods).

It’s quite strange that api explorer reports cancellation tokens as params..

I think I've mixed up api explorer (being the ui) and Microsoft.AspNetCore.Mvc.ApplicationModels in what I said above.  I've done quite a bit more digging, and Microsoft.AspNetCore.Mvc.ApplicationModels is the thing that is reporting CancellationToken as an action parameter.  I'm not sure if that behaviour correct or not, but the nswag WebApi generator does contains an OperationProcessor that filters out cancellation tokens explicitly:
NSwag\src\NSwag.Generation.WebApi\Processors\OperationParameterProcessor.cs:
        public bool Process(OperationProcessorContext context)
        {
            var httpPath = context.OperationDescription.Path;
            var parameters = context.MethodInfo.GetParameters();

            var position = 1;
            foreach (var contextualParameter in parameters.Select(p => p.ToContextualParameter())
                .Where(p => p.Type != typeof(CancellationToken) &&
                            !p.ContextAttributes.GetAssignableToTypeName("SwaggerIgnoreAttribute", TypeNameStyle.Name).Any() &&
                            !p.ContextAttributes.GetAssignableToTypeName("FromServicesAttribute", TypeNameStyle.Name).Any() &&
                            !p.ContextAttributes.GetAssignableToTypeName("BindNeverAttribute", TypeNameStyle.Name).Any()))

the AspNetCore generator doesn't appear to have an equivalent of this which explains why it expands them as structs.  I can work around this by implementing an IActionDescriptorProvider that strips off CancellationToken parameters so nswag never sees them:
public class RemoveCancellationTokenActionDescriptorProvider : IActionDescriptorProvider
{
    public int Order => 1;

    public void OnProvidersExecuting(ActionDescriptorProviderContext context)
    {
        foreach (var descriptor in context.Results)
        {
            for (int i = 0; i < descriptor.Parameters.Count; ++i)
            {
                if (descriptor.Parameters[i].ParameterType == typeof(CancellationToken))
                {
                    descriptor.Parameters.RemoveAt(i);
                    --i;
                }
            }
        }
    }

    public void OnProvidersExecuted(ActionDescriptorProviderContext context)
    {
    }
}
...
services.AddTransient<IActionDescriptorProvider, RemoveCancellationTokenActionDescriptorProvider>();

However I think it's relatively easy to filter out cancellation tokens in the same way on the aspnet core side (if you think that's correct).  I had a bit of trouble reproducing this in the tests in the nswag codebase though (I was trying to add a test that would fail but couldn't figure out where exactly to put it to tickle this problem) -- if you would be so kind as to point me in the right direction I will happily have a go at implementing that.
I also encountered the issue with the exception above, which is simply a bug in  Microsoft.AspNetCore.Mvc.ApplicationModels.InferParameterBindingInfoConvention.InferBindingSourceForParameter that does not handle CancellationToken.  In other places in the same api  the binding source for CancellationToken is inferred correctly (as BindingSource.Special)
(I worked around that by copy/pasting InferParameterBindingInfoConvention and ApiBehaviorApplicationModelProvider and adding the relevant check to InferBindingSourceForParameter to return BindingSource.Special for the CancellationToken parameter, which is how it is handled elsewhere).

It appears that this is because I had the compatibility version for Mvc set to 2.0.  With compatibility version set to >= 2.1 then cancellation token parameters are filtered out by the api (and thus both my problems are solved).
https://github.com/aspnet/AspNetCore/issues/13045
Sorry for the noise!


Information not accurate for Az-library

Comment at the top of the page states "This article has been updated to use the new Azure PowerShell Az module."
All the information in this page is not valid for Az-library. It is not valid for its predessor AzureRM-library. All the information is valid only for deprecated Azure-library.
Please revise the information on this page to reflect current situation.

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

ID: 74cdb18f-aff3-4de9-455d-2107d5a00bc6
Version Independent ID: b266f482-0992-686b-091d-aa78c14a1025
Content: Using PowerShell to setup Application Insights in an Azure
Content Source: articles/azure-monitor/app/powershell-azure-diagnostics.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@HQJaTu Thank you for the feedback. I will assign this to the doc author to make the updates.

Thanks @HQJaTu. When they rolled out the new Az commands they tried to automate the process of updating the docs. In most cases it worked. In the case of this doc, it clearly did not. I will get this taken care of this week, thanks for letting us know!

The update to this doc will go-live on Monday 8/25 between 10-11 AM (UTC-7). Thanks again for bringing this to our attention. #please-close


New version: Yuanli.uTools version 3.0.2

[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?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.1 schema?

Microsoft Reviewers: Open in CodeFlow

@wingetbot waivers add Validation-Domain

@wingetbot waivers add Validation-Domain

@wingetbot run


Collapsible list group items and custom classes for list groups

Thanks once again for the contribution! BTW, if you think you will be contributing often, I would be pleased to make you a committer on this repo?

Hi,
As long as I'm using pug-bootstrap on my project I plan to update here all my needs for my project.
I can't say how often I'll be contributing but I'll be glad to be a committer.


Failed to connect

What version of Music Assistant has the issue?
2023.6.0b3
The problem
Failed to connect
How to reproduce
I go to integration and add integration, music assistant beta.
In music assistant server is http://mass.local:8095 , click next failed to connect.
Relevant log output
No response
Additional information
I try on other ip and ports, this same problem
What version of Home Assistant Core are your running
2023.9.1
What type of installation are you running?
Home Assistant Supervised
On what type of hardware are you running?
Raspberry Pi

Replace mass.local with the actual ip address

I'm experiencing the same issue and when I replace mass.local with the the IP address of my homeassistant docker instance, it still fails.

Is the MA server running? That is, can you get to the web interface ok?

I can't access the web server at the homeassistant ipaddress:8095 on a separate browser window.  I also tried running a separate docker container based off of this (https://github.com/music-assistant/server/blob/main/docker-compose.example.yml) and it almost seems like the docker container is unable to grab an IP address.

I assume from what you have said that you have initially added MA as an addon. If that is the case then just go to the addon page and access the server from there. In this situation the websever on port 8095 is not enabled by default.
if you have issues with the docker version check the instructions carefully and ensure you have created the container in host networking mode.

I'm getting this issue too. The MA server is running perfectly in a docker container on my network and the web interface is accessible at http://HOSTNAME:8095, but when I go to connect the integration, I just get a non-specific "Failed to connect" error message. Nothing shows up in Logs, so unsure what to try. I've unticked the box to use the official add-on as the server is already running separately.

Using homeassistant.local:8095 it worked for me


[Enum Request] RlshpMgtCommentLine.Table.al - Table Name

For our complaints module, we are integrating with relationship management. The only issue we're facing is that currently we can not store comment lines in table 5061 "Rlshp. Mgt. Comment Line", as we used to. If the "Table Name" field would be an enum, we could add our 'Complaint' to the current 'Contact,Campaign,To-do,Web Source,Sales Cycle,Sales Cycle Stage,Opportunity' options.

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


Update DIT for Super Mario Strikers

Uses HD font

They look really very good and fit perfectly with the original!
Good work.

Just to avoid misunderstandings, most of the font is made by mariostriker and is included in the hd texture pack, available in the dolphin forums. I just extended the font with Ä, Ö, Ü, Á and other european characters which are missing in his pack. I will contribute these textures to the texture pack as soon as I'm done with the other languages besides german.
I just contribute them to DIT aswell, because otherwise the DIT will overwrite the textures from the texture pack and one will end up with a mix from A, B, C etc. in HD and Ä, Ö, Ü in native (because there are other font textures too, which have no buttons included and therefore are not part of DIT).
On the other hand now someone who only uses DIT and not the texture pack will see A, B, C etc. in native and Ä, Ö, Ü in HD. Not sure if this is better... but I think v2 will adress this issue?
Alternatively one have to add the other font textures (without buttons included) to DIT aswell to avoid such a mix from HD and native font. In that case we had to ask mariostriker for permission and I'm not sure if he is still active in the forums.

I think you can make a region with the "Blank" key and it will be copied over.

I add it now simply because I assume that he will have nothing against it.


Appveyor

Currently they are an issue with RtMidi:
checking for MIDI API... configure: error: Unknown system type for MIDI support!
make[1]: *** [Makefile:121: bin/rtmidi.dll] Error 1
make[1]: Leaving directory '/c/projects/Rack/dep'
make: *** [Makefile:45: dep] Error 2


fix: fixed profile information components structuer

closes #210

I was checking the site and it seems that it doesn't match what we wanted to do.
.
The idea was to have rows instead of two columns, having the first row the name and the actions.
The styles on mobile seem to have shifted down from where they currently are:


arm-trusted-firmware: 2.7 -> 2.8

ZHF #230712
Description of changes

Updates ATF to the latest version.
https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#id1
sptool was replaced by a Python script and is not longer installed as part of armTrustedFirmwareTools. It wouldn't be too hard to install/wrap the new script, but I doubt anyone uses it. I made sptool part of the armTrustedFirmwareTools package when I created it simply because it was trivial to add, not because it was actually necessary.
I tested this on my Rock64v2 and ODROID-C2.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.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

[x] Fits CONTRIBUTING.md.

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

1 package built:

armTrustedFirmwareTools

[belated] Pulled, thank you!


Introduce @validated to mark pathref targets which need extra checks

This introduces a new annotation @mill.define.validated. Cached annotated targets returning a single PathRef or a collection of them, will also check the cached value against their current state in the filesystem. Only if these are correct (valid == same sig), the cached value is used, otherwise the target will be re-evaluated.
Why is this needed? Normally, PathRefs referring to files under T.dest do not need extra validation, as the target specific directory is considered as Mill managed storage, but if a PathRefs refers to a file or directory outside the Mill cache directory, it can become out of sync. The most prominent example is JavaModule.resolvedIvyDeps, which resolves and downloads the ivyDeps into an external storage location (~/.cache/coursier). If a user clears that cache storage, the cached result is stale, yet Mill does not recognize it. By annotating it with @validated, Mill is now also checking that the external cache storage is as expected and the returned PathRefs are valid.

Fix https://github.com/com-lihaoyi/mill/issues/2157

Hm, validate currently enforces existing paths, as the tests didn't work without it. We probably don't encode non-existence in the PathRef.sig. We should ensure, that a non-existing path and a missing path have different sigs.

Hm, validate currently enforces existing paths, as the tests didn't work without it. We probably don't encode non-existence in the PathRef.sig. We should ensure, that a non-existing path and an empty path have different sigs.

I removed the existence test from validate. I changed the test cases so that the validated paths also contains actual file(s). This should be in line with how we handle empty directories vs. non-existing directories elsewhere.

Not sure that an annotation and doing a type-test on the return value of the target is the right thing to do here. It seems pretty fragile and inextensible, e.g. if someone returns tuple of (PathRef, PathRef) or some other data structure.
How about the following:

We replace the @validated annotation and instead make those targets return a PathRef(...,  validated = true)
PathRef(...,  validated = true) is ~identical to a normal PathRef, but will perform validation on instantiation. If validation fails, it will throw new PathRefValidationException(...)
Inside Evaluator, we catch the PathRefValidationException when trying to deserialize the cached data into in-memory structures, and fall back to re-computing the value instead.

Notes:

My proposed approach has the advantage that we can handle a failed validation nested arbitrarily deep within arbitrary data structures.
There isn't really any other hook we can apply to every data type returned by a Target other than instantiation, so the only way we can perform any checks is by putting them in the data type constructor
The alternative would be to replace upickle.default.ReadWriter with our own custom typeclass that can perform "deep" checks inside the data structure in a statically-type-safe way. That seems a pretty invasive change and probably not worth it for such a small edge case
Throwing exceptions during uPickle deserialization isn't unheard of: the core parser relies heavily on exceptions deep inside the parser/visitor logic together with try/catch blocks to report errors, so while a bit gross it's no worse than the status quo

@lefou WDYT?

Not sure that an annotation and doing a type-test on the return value of the target is the right thing to do here. It seems pretty fragile and inextensible, e.g. if someone returns tuple of (PathRef, PathRef) or some other data structure.
How about the following:
1. We replace the `@validated` annotation and instead make those targets return a `PathRef(...,  validated = true)`

2. `PathRef(...,  validated = true)` is ~identical to a normal `PathRef`, but will perform validation on instantiation. If validation fails, it will `throw new PathRefValidationException(...)`

3. Inside `Evaluator`, we catch the `PathRefValidationException` when trying to deserialize the cached data into in-memory structures, and fall back to re-computing the value instead.

Notes:
1. My proposed approach has the advantage that we can handle a failed validation nested arbitrarily deep within arbitrary data structures.

2. There isn't really any other hook we can apply to every data type returned by a `Target` other than instantiation, so the only way we can perform any checks is by putting them in the data type constructor

3. An alternative would be to replace `upickle.default.ReadWriter` with our own custom typeclass that can perform "deep" checks inside the data structure in a statically-type-safe way. That seems a pretty invasive change and probably not worth it for such a small edge case

4. Another alternative is to keep the `@validated` annotation use java reflection to walk the reference tree of the object returned by a target. That is more robust than the original `@validated` proposal, and there is precedence e.g. java reflection is how we get the mill module tree. But IMO this would be worse than `PathRef(validated = true)` since it still allows the annotation to be used incorrectly on targets that do not include `PathRef`s

5. Throwing exceptions during uPickle deserialization isn't unheard of: the core parser relies heavily on exceptions deep inside the parser/visitor logic together with try/catch blocks to report errors, so while a bit gross it's no worse than the status quo

@lefou WDYT?

Yeah, an annotation is sub-optimal. I like your proposal as it removes many of the limitations. Thank you! I see one potential issue due to the side effects of re-using that validated-enabled PathRef later on, e.g. in a downstream target. It's something that could be handled by creating a new copy of it, but it's a bit of suprising effect. (I dropped the idea to use a wrapper type which would make it explicit but to cumbersome earlier.) Do you see any issues, by introducing a validateOnce flag, which is dropped after we instantiated the PathRef? It would require us to drop the case of the class and implement our own hashCode/equals though.

I think passing the pathref around is fine. There will always be a TOCTTOU race condition here no matter what we do, so we just need to do a best effort validation. "perform validation when pathref is first read from cache" feels best-effort enough for me, since that is guaranteed to happen at least once every time ./mill is invoked

@lihaoyi Based on your input, I reworked the PathRef validation completely.
We now check the validity of PathRefs upon upickle reading
and throw an exception if it is invalid. Beside a much simpler
implementation, this has also the benefit, that we can detect
deeply nested invalid PathRefs.
Failing deserialization is already handled in Evaluator and
the cached value is automatically dropped.
A PathRef can have three revalidation states, never, once and always.
Once means, that the revalidation state is changed to never when it
is successfully read from json.


[WFLY-9386] Several tests need FilePermission for standalone/tmp/auth…

… to pass with security manager
JIRA:  https://issues.jboss.org/browse/WFLY-9386

@stuartwdouglas The error stack is shown in the JIRA. It's not a @RunAsClient test so a ModelControllerClient running inside the server is trying to make a remote connection.
The call actually is in a privileged block, so the AccessControlContext passed to PrivilegedSaslClient and thus to doPrivileged must be restricting this.
I'm somewhat doubtful the client's read of the file should be done in a privileged manner. It's reading a file that some remote endpoint told it to read and will then report the file contents back to that endpoint. It's not obvious that the client should always do that.
OTOH, you could argue that if a thread has a "connect" permission that implies it can do whatever is necessary.
Also, I figure this used to work or this would have been among the many other similar permissions already added to these tests.
@dmlloyd FYI.

I think this is probably fine.  We can always fix it later anyway.


6.4.x: RHBPMS-4118 - 'SAXParseException; Premature end of file' due to incorrect encoding

@psiroky or @mswiderski Would you mind reviewing and merging? Relates to the upcoming release.

+1 to merge
shall this go to 6.5 and master too? as it seems valuable fix


Install test_tracetools_mark_process

This is needed if the build/ directory is not available when running the test_tracetools tests.

Linux
Linux-aarch64
Windows


Publish recovered sidecars on gossip

Addressing https://github.com/ethereum/consensus-specs/pull/3794
There is one issue in it: these sidecars will pass onNewValidatedDataColumnSidecar(DataColumnSidecar dataColumnSidecar) twice but I don't see any fatal consequences from this, though we could try to improve this in the future. Or maybe add comment to not forget.

This PR basically reseeds only the columns which were requested locally, but missed and then recovered.
I believe cross-seeding should be a separate component which tracks gossiped columns, detect missed ones and checks if we locally have > 50% to recover.
It also needs to implement a 'random' cooldown timeout

Also

we don't need to cross-seed historical columns
we should cross-seed only if we were able to recover 100%
we should cross-seed all recovered (missed), not only those we requested


Seeding the Random Number Generators?

Currently, in the documentation, it's unclear whether it's possible to control the RNGs' seeding, and if that's possible, where (server, client, problem, study, sampling?) and how to perform that seeding.

Hi,
Currently, it's only possible to control the RNG seeding at a Designer level, which can happen on the server code itself (e.g. in the policy factory code).
Part of what makes Vizier a good global optimizer is that it's stochastic, and we build a new Designer for every batch of trials. We typically only supply the seed when we want to replicate a specific trial that e.g. a user complained about, based on the seed that was used to generate the suggestion (and it stored in the trial metadata).
Do you have a specific use case where you'd want to control the seed from the client side?
Best,
Sagi

Seeding at the server level would work be totally fine for my use case. Do you have an example (or documentation) on how to use the Designer class to accomplish that?
For illustration, this is my current usage:
problem = vz.ProblemStatement()
problem.search_space.root.add_float_param('lr_exp', search_space['lr_exp_min'], search_space['lr_exp_max'])
problem.search_space.root.add_float_param('wd_exp', search_space['wd_exp_min'], search_space['wd_exp_max'])
problem.metric_information.append(vz.MetricInformation(name='dummy_metric', goal=vz.ObjectiveMetricGoal.MAXIMIZE))

study_config = vz.StudyConfig.from_problem(problem)
study_config.algorithm = 'QUASI_RANDOM_SEARCH'

server = servers.DefaultVizierServer(host='localhost', database_url=None)
clients.environment_variables.server_endpoint = server.endpoint
study_client = clients.Study.from_study_config(study_config, owner='owner', study_id = 'example_study_id')

suggestions = study_client.suggest(count=samples_n)

Apologies for the late response - you'll have to modify the code here, which is used by the server to initialize algorithms: https://github.com/google/vizier/blob/e35c2cb4512399a8d78d57a2f780d8013f4a8bd4/vizier/_src/service/policy_factory.py#L40-L53
from_problem allows a seed.


Cytoscape.js

[ Project Lead ] @maxkfranz
[ GitHub Repo ] https://github.com/cytoscape/cytoscape.js/
[ Track ] Tools: you are building a tool others can help you build
[ Level ] Intermediate
Description
Graph theory (a.k.a. network) library for analysis and visualisation : http://js.cytoscape.org. Server side network rendering with Cytoscape.js

Want to Contribute?
Join us at the Global Sprint June 2-3. Leave a comment in this issue to let the project lead know you're interested in contributing during #mozsprint 2016!

Note to the Project Lead
Congrats, @maxkfranz! This is your official project listing for the Mozilla Science Global Sprint 2016. To confirm your submission, please complete the following:

[x] Provide a GitHub repository for work and discussion on your project
[x] Confirm in a comment that at least one person will be available to review and answer questions on this project from 9-5 in their timezone on both June 2 & 3.

@acabunoc Yes, I'll be available

Project : Server side image rendering of Cytoscape.js graphs/networks using Node.js and PhantomJS
Repo : https://github.com/cytoscape/cytosnap

Thanks @maxkfranz! Feel free to update the issue with project info :)

Hi @maxkfranz, is your time zone Eastern Time (UTC-05:00)?

@eronisko Yes


goBGP handling

We need to be able to manage goBGP process from inside loxilb ( forking, restarting etc)

This commit fixes this


JulianDate.fromIso8601 throws error

var date = new Cesium.JulianDate()
var isoDate = Cesium.JulianDate.toIso8601(date) //  "-4713-11-24T12:00:00Z"
Cesium.JulianDate.fromIso8601(isoDate) // throws DeveloperError "Invalid ISO 8601 date."

Thanks, it is an invalid ISO8601 date, but we should throw in toIso8601 indicating why instead of in fromIso8601.

What makes it and invalid ISO8601 date?

According to the spec, 0000 and 9999 are the min/max values for the year components, so 0000-01-01T00:00:00Z is the earliest date possible.
That being said, the spec makes allowances for "expanded representation", which would allow Cesium to support an arbitrary number of digits for the year if the need every arises.

Okay thanks for explaining. Shouldn't the default JulianDate be 000-01-01T00:00:00Z if that's the case?

No, JulianDate is different format, Julian day.  A Julian day of 0 corresponds to -4713 BC.  There are lots of ways to represent dates and they are not all compatible.  JulianDate happens to be the most precise, accurate and performant for Cesium's use cases, so that's what we use internally.  We provide utility functions to go back and forth in different formats, but that does not mean all formats are compatible.  For example, JavaScript Date objects can't represent fractional milliseconds, so you lose precision when going from JulianDate to Date


Speech capture without wakeword when a follow-up is required

When we require the user to provide an answer (follow-up/clarifying a question) we need to just drop right back into speech capture without needing the wake word.
In case the user didn't provide an answer in time (phase 1 vad threshold * 2) we should play the no-match sound.

This is working now.


[SMALLFIX] Fix seek contract test

The test requires that available throws an IOException when the stream is closed.
Followup to https://github.com/Alluxio/alluxio/pull/3618

LGTM

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/10586/
Test PASSed.


[BugFix] Cherry-Pick ORC-1304 bug fix from apache-orc

Cherry-Pick from https://github.com/apache/orc/pull/1299
I didn't cp ut because many commits are missed in the middle, it will cause ut compilation to fail.
We will refactor orc later, so this is just a temporary solution.
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.1
[ ] 3.0
[ ] 2.5
[ ] 2.4

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 4 / 16 (25.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/formats/orc/apache-orc/c++/src/RLEv1.cc
0
7
00.00%
[190, 192, 197, 199, 201, 205, 212]

:large_blue_circle:
src/formats/orc/apache-orc/c++/src/ByteRLE.cc
4
9
44.44%
[382, 384, 386, 394, 395]

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 6 / 18 (33.33%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/formats/orc/orc_chunk_reader.cpp
0
1
00.00%
[512]

:large_blue_circle:
src/formats/orc/apache-orc/c++/src/RLEv1.cc
0
10
00.00%
[190, 191, 192, 193, 194, 195, 196, 200, 201, 208]

:large_blue_circle:
src/formats/orc/apache-orc/c++/src/ByteRLE.cc
6
7
85.71%
[391]

@Mergify backport branch-3.1 branch-3.0 branch-2.5


Mention secondary-nav in upgrade guide

I believe "secondary-nav" was in bootstrap 1* but is no longer in 2 at all. I looked for a mention of it in upgrade guide and docs and didn't see any.  Perhaps a brief "secondary-nav is no longer used, instead..." ?

Resolved, thanks!