Update safe target to determine which arg is the URL and which arg is the alias

safe target <url> <alias> should detect if the user swapped alias and url, and Do The Right Thing. URLs are required to have scheme, so we should be able to detect which one starts matches m|https?://| and set that as the URL and the other as the alias

v0.0.16 should have this feature.


Gradle 3.4 does not work with IntelliJ on MacOS

Expected Behavior
I should be able to run the project from within IntelliJ on both, Linux and MacOS.
Current Behavior
I'm trying to run a gradle project from within IntelliJ 2016.3.4. When doing this on a Ubuntu 16.10 with all updates installed everything works like a charm. But when importing the very same project into an IntelliJ on a Mac and trying to run the application from within IntelliJ I get some exceptions:
Exception in thread "main" java.lang.NoClassDefFoundError: com/google/inject/Injector
    at java.lang.Class.getDeclaredMethods0(Native Method)
    at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
    at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
    at java.lang.Class.getMethod0(Class.java:3018)
    at java.lang.Class.getMethod(Class.java:1784)
    at com.intellij.rt.execution.application.AppMain.main(AppMain.java:126)
Caused by: java.lang.ClassNotFoundException: com.google.inject.Injector
    at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
    ... 6 more

Process finished with exit code 1

The configuration for IntelliJ is as similar as possible. The project contains the gradle wrapper. Compiling and running the project from the command line works on both systems like a charm. When I downgrade to gradle 3.3, without changing anything else in the project it works.
Context
This issue prevents me from upgrading to gradle 3.4 as I neither can run the project nor debug it in IntelliJ
Steps to Reproduce (for bugs)

Your Environment

Build scan URL:

See https://github.com/gradle/gradle/issues/1276 for an explanation and workaround.

@oehme, thanks for pointing me to the other issue. This solved my issue.


How to add prepdetails list item when creating inbound shipment

When creating an inbound shipment plan, how do I add PrepDetails ?
https://docs.developer.amazonservices.com/en_US/fba_inbound/FBAInbound_Datatypes.html#InboundShipmentPlanRequestItem
I looked at the the source code in inbound_shipments.py and there is no reference to this parameter. We would like to set the PropOwner property when creating shipments
For example the request items would be like this:
&InboundShipmentPlanRequestItems.member.1.SellerSKU=SKU00001 &InboundShipmentPlanRequestItems.member.1.Quantity=1 &InboundShipmentPlanRequestItems.member.1.PrepDetailsList.member.1.PrepInstruction=Taping &InboundShipmentPlanRequestItems.member.1.PrepDetailsList.member.1.PrepOwner=AMAZON

Looking at create_inbound_shipment_plan(self, items, country_code='US', subdivision_code='', label_preference='') https://github.com/python-amazon-mws/python-amazon-mws/blob/develop/mws/apis/inbound_shipments.py#L192
and
https://docs.developer.amazonservices.com/en_US/fba_inbound/FBAInbound_CreateInboundShipment.html
so the items argument relates to InboundShipmentItems
This then passes items through the parse_item_args function which checks that required keys are in place, or throws an error.
PrepDetailsList is not a required argument, so should be able to be added to this dictionary
I've not tried this, and I'm using the dev branch for reference here.

Definitely some room for improvement here. parse_item_args was an early attempt to handle this with some special dictionary conversion, but it is cannot currently handle PrepDetailsList; and adding that to the existing code would be cumbersome.
This needs some new architecture, I think. Some native objects like a PrepDetail class and an Item class (or two separate classes for InboundShipmentPlanRequestItem and InboundShipmentPlanItem) that can contain multiple PrepDetails in a list, and each should be able to serialize itself into the appropriate parameter.
I'll spend some time on this in the near term.


Convert to plugin

This is pretty much what BC-breaking conversion to a plugin would look like right now (as discussed in, and based on, #80).
exports = module.exports = function plugin (b, opts) {
  if (opts.basedir === undefined) opts.basedir = b._options.basedir;
  b.transform(es6ify(opts));
};

Latest: bc-breaking-plugin HEAD

Any way we could make it not breaking? Just asking cause in proxiquireify it was possible somehow.

I think so, I was just going by @domenic's comment where it sounded like he favored converting it to a plugin exclusively (BC-breaking), but I may have misunderstood.

Well it'll be a major release, so we could break things.
People just need to upgrade their browserify. It has had plugins now for a good while.
So go ahead break things :)

I'd like to also include the runtime automatically, when we do a plugin. (I guess we can have an option to turn it off but you really shouldn't be using Traceur without the runtime.)

but you really shouldn't be using Traceur without the runtime.

What if you just want to transpile ES6 module syntax?

Then you should probably be using a dedicated transpiler for that (e.g. es6-module-transpiler or whatever), cuz at any moment Traceur could update their transpilation to depend on the runtime (and in fact at least one of the module output formats does depend on it).

Well it'll be a major release, so we could break things.
People just need to upgrade their browserify. It has had plugins now for a good while.
So go ahead break things :)

Ok. What versions of browserify do you want to support?

@jmm the last 5 majors should be sufficient and plugins have been around that long.

Then you should probably be using a dedicated transpiler for that (e.g. es6-module-transpiler or whatever), cuz at any moment Traceur could update their transpilation to depend on the runtime (and in fact at least one of the module output formats does depend on it).

Ok, thanks.
So plugin with runtime included by default and option to opt-out?

@domenic talking about that, I'm wondering what es6ify at this point provides that modules like 6to5 don't?

So plugin with runtime included by default and option to opt-out?

Sounds good to me.

the last 5 majors should be sufficient and plugins have been around that long.

Ok, thanks. What's a strategy for testing that?

@jmm yeah that sounds good to me.
@thlorenz well Traceur is in general better than 6to5, in a large part because it's written by people who are deep into the spec. 6to5 fixes spec compliance issues as fast as I can file them, which is to their credit, but I would rather use Traceur.

Ok, thanks. What's a strategy for testing that?

I usually just test the latest and wait for people to file bugs on anything else :P.

I usually just test the latest and wait for people to file bugs on anything else :P.

Ok, I'll go with that for now.
Since we're breaking BC there's no reason for traceurOverrides to be an export now, right? It can just be an option to the plugin?

Agreed. Might also be good to remove compileFile.

Agreed. Might also be good to remove compileFile.

Up to you guys. That didn't have use cases that are still relevant?

Re: the discussion in #25 about being able to do this...
browserify('./entry')
  // Includes runtime by default
  .plugin(es6ify)

...vs having to do this to get the runtime executed first...
browserify()
  .plugin(es6ify)
  .add('./entry')

It looks like @guzart was dealing with that by somehow prepending the runtime to the bundle and adjusting source maps accordingly. I haven't nailed it down 100%, just skimming. I experimented with a different approach, which there's a prototype of in https://github.com/jmm/es6ify/commit/33ec7d0b53b9439b0a41dfab7d3fa49b3630da01. I haven't tested it extensively or tried to analyze all the possible ramifications, it's just an experiment so far. Even if it seemed like it wouldn't screw anything up I don't know if you guys want to rely on browserify internals like that.

In order to run the transform tests as currently configured you still need access to the function that's registered with b.transform(func) inside the plugin (what es6ify.configure() previously returned). Since browserify doesn't do anything with plugin return values, I set it up so that calling the plugin function (the main export) will return the transform function. So in the tests where it had:
something.pipe(es6ify.configure(opts))

It's this instead:
something.pipe(es6ify(browserify(), opts))

For that scenario it means you either have to test the first arg to es6ify() to see if it's a browserify instance before calling methods like add() on it, or pass a browserify instance (or something imitating it). So far I took the approach of just passing a browserify instance.

Re: plugin vs transform, there'll still need to be a transform for package.json, right?


Codes for MAY221

Hey @swoyam2609 ,
I would like to upload solutions for the problems of May Long One 22.
Would you mark it under hacktoberfest ?
Regards.

Cool, assigning it to you, create a proper directory and upload your codes
Happy Contributing

Closed as completed by @amanmodiii


Support XGBClassifier with pandas DataFrame in PermutationImportance

fix for issue:
https://github.com/TeamHG-Memex/eli5/issues/256

Codecov Report

Merging #296 into master will decrease coverage by 0.2%.
The diff coverage is 40%.

@@            Coverage Diff             @@
##           master     #296      +/-   ##
==========================================
- Coverage   97.25%   97.05%   -0.21%
==========================================
  Files          44       44
  Lines        2841     2851      +10
  Branches      539      541       +2
==========================================
+ Hits         2763     2767       +4
- Misses         41       46       +5
- Partials       37       38       +1

Impacted Files
Coverage Δ

eli5/sklearn/permutation_importance.py
93.4% <40%> (-6.6%)
:arrow_down:

Codecov Report

Merging #296 into master will decrease coverage by 0.2%.
The diff coverage is 40%.

@@            Coverage Diff             @@
##           master     #296      +/-   ##
==========================================
- Coverage   97.25%   97.05%   -0.21%
==========================================
  Files          44       44
  Lines        2841     2851      +10
  Branches      539      541       +2
==========================================
+ Hits         2763     2767       +4
- Misses         41       46       +5
- Partials       37       38       +1

Impacted Files
Coverage Δ

eli5/sklearn/permutation_importance.py
93.4% <40%> (-6.6%)
:arrow_down:

@lopuhin added a unit test. not sure about your assumption about having pandas and xgboost when running the tests.

I left a few minor comments, but the code looks good to me - thanks @hofesh!

@kmike fixed your comments

Thanks @hofesh for the fix!


How to analyze a pod?

We have two apps and a library which we share between the two as a cocoapod. Reporting works great for the apps themselves, but I'd like for them to include the compile times of the shared pod. Any idea how to achieve this?
Great little utility btw 👍🏼

That's a good question. I haven't tried to analyze pods and am uncertain if those can be included in the log files. Worst case, you will need to analyze the shared project separately.

Our shared project has its own app just for a few demonstrative purposes, but the code of value is all in library form. I think the problem is that the compiler flags are set on a target, yet the code in the shared pod is not directly part of any runnable target.

On a different note though, is your library pre-compiled?
If you're having problems with long running build times, it may seem a bit unnecessary to recompile the framework each time. Particularly if the project is maintained separately.


App API

Provide a simple container API for running containers. Doesn't have to be on our own infra. Can be google cloud run.

Currently doing an App API https://github.com/micro/services/pull/291

Added with #291 , right?
https://m3o.com/app

Yes that's right. Closing.


WS 2012 R2 OS- Lun Reset Test With Outstanding IO - All Disks  test failing

I am trying to run the below test cases on WS 2012 R2 OS for our Storage controller but all the tests are failing with the error.
Cause : The Execute Task with Commandline cmd /c copy /y \WIN-F0I16VVJOTF\c$\set_params.cmd c:\ && c:\set_params.cmd && del \WIN-F0I16VVJOTF\c$\set_params.cmd Failed with ExitCode 1
The tests are:
Lun Reset Test With Outstanding IO - All Disks
Lun Reset Test With Outstanding IO - Single Disk
Lun Reset Test Without Outstanding IO - All Disks
Lun Reset Test Without Outstanding IO - Single Disk
Bus Reset Test
Please help me to resolve this issue.

Hi Vadim,
This is WS 2012 R2 but still i am facing the same error as indicated for WS 2008R2, I referred the error in the blog u shared in above comment.
Can you please let me know if there is a separate procedure to run these test cases ?
I am running these tests  on our storage controller .
Is that manual ERRATA 5906 can be used for for 2012 R2 OS also.
https://sysdev.microsoft.com/en-US/Hardware/EC/FilterDetail.aspx?id=32016

5906 is for Windows 8 / Windows Server 2008 as mentioned in the description.
I'm a bit confused with "our storage controller". If it is not any of our "official" qemu
virtio-win drivers, then I suggest you to check if you properly handle
SRB_FUNCTION_RESET_BUS, SRB_FUNCTION_RESET_DEVICE, and SRB_FUNCTION_RESET_LOGICAL_UNIT requests.
Cheers,
Vadim.

If the problem happens with virtio storage device then please let us know the kernel, qemu, and driver versions as well as qemu command line. Then we should be able to reproduce, investigate and find a way how fix the problem.

Results of the optional tests can be omitted.

Results of the optional tests can be omitted
What is the procedure to do this can u help..
I am running for server 2012R2 OS..
Is there a filter or manual errata ...How to ommit these test cases

Did you follow below steps when running the jobs?

nonboot disk
two machines connected to shared storage

“Running the test
This test should be run on a nonboot storage controller. Running on a boot controller is possible, but requires at least one nonboot disk attached. This test will not execute on the boot disk. The expected result is for there to be no IOs stuck in the miniport after the RESET_LUNs and RESET_BUSs. Verification is done by restarting the machine after the test. To run this in a dual initiator setup, schedule this test on two machines connected to shared storage. Resets on one initiator should not adversely affect the other initiator. For Single Disk tests, double check that the two initiators are testing against the same physical disk in the shared storage.“
https://docs.microsoft.com/en-us/windows-hardware/test/hlk/testref/f42046f1-ebf4-49dd-9eba-6ee766727fa9


Dispatch merge

Creating a merged file from the uploaded chunks is synchronous at the moment and depending on the file size it can take a long time. By dispatching it as a job the owner of the application can execute it in background with an asynchronous queue driver.

This probably won't execute fileUploaded closure passed to handle method.


[WIP] Add preamble search.

Part of https://github.com/eregs/notice-and-comment/issues/118.
Tasks:

[x] Client-side preamble search
[x] Server-side preamble search
[ ] Update tests

@cmc333333: this is working, AFAICT. Let me know if this needs major revisions, and then I'll update the tests.

Handful of little things, but the overall logic makes sense, I think

Based on slack conversation, we're going to merge this after reverting the regulation url pattern (which is done) and continue cleanup and testing separately.

Let's do this


Added Wink Key support

While working on the Garage issue, I discovered another API endpoint /keys. This is how the Wink app is able to do robots based on the user code entered on the Wink lock. This PR will add Wink keys as a "sensor" returning a state of True if the key was recently used. I still need to test to see how long the state stays True. If the state stays True for less then 60 seconds this may be useless unless subscription support is added to the Application using python-wink.
**Update, it does appear that the state reverts back to false between 30-45 seconds. Maybe there is a way to fix this in code?
The API returns activity_detected_changed_at as well maybe we could set the state based on activity_detected and activity_detected_changed_at depending on how long it has been since the activity_detected_changed_at was changed, thoughts?
**Update, I will try to get this PR updated once I am back from vacation next week. Now that we have subscription support I believe this should work quite well. Also I noticed that they moved keys into the same API endpoint as all the other devices so this PR should be less complex.

Coverage increased (+0.01%) to 85.921% when pulling df5c41bfea32ad5ba8c62e1ac67c71175fc6f95b on w1ll1am23:keys into 79a9b4ca45ba68d374336a0452d5514e0c7d7343 on python-wink:master.

Coverage increased (+0.01%) to 85.921% when pulling 856f4bd8b8840dbfbdc0643859b7655a49dd6670 on w1ll1am23:keys into 79a9b4ca45ba68d374336a0452d5514e0c7d7343 on python-wink:master.


v1.21.0 libDefaultClient.so and libADSL.so and libACL.so undefined references to alexaClientSDK

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:
When I run make SampleApp -j2 the compilation goes well until almost 100% completed. After the [100%] Linking CXX executable SampleApp message, I got different messages of undefined references like:

libDefaultClient.so undefined reference to alexaClientSDK::acl::AVSConnectionManager::createMessageSenderInterface
libADSL.so undefined reference to alexaClientSDK::adsl::DirectiveProcessor::enable
libACL.so undefined reference to alexaClientSDK::acl::DownchannelHandler::create

What is the expected behavior?
Successful compilatio of SampleApp
What behavior are you observing?
Undefined references on three libraries.
Provide the steps to reproduce the issue, if applicable:
Execute make SampleApp -j2
Tell us about your environment:

What version of the AVS Device SDK are you using?
  <1.21.0>

Tell us what hardware you're using:

[ ] Desktop / Laptop
[X] Raspberry Pi
[ ] Other - tell us more:

Tell us about your OS (Type & version):

[ ] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[X] Other - tell us more: Ubuntu 20.10 for Raspberry Pi

Hi @jcatumba, can you build and run an earlier version of the SDK (say 1.20) on your platform, or is this specific to 1.21?
Are you using one of our setup scripts to build the SDK, or following one of our guides? If so, which one, and have you made any modifications?

Hi @caleighatamazon, I'm going to try to build the 1.20 version.
The guide I'm following is the one for Ubuntu since that the Raspberry Pi guide recomends Raspbian.

Hi @caleighatamazon, the build of v1.20.1 was successful. I managed to launch the SampleApp, and also see it on the Alexa App on my phone.

Hi @jcatumba can you post the cmake command you used with 1.21.0 version here so that I can try and reproduce this locally? Also, it would be helpful if you post the full build log along with all the commands you run. Thanks!

Hi @mvelegon-amzn. The cmake command was
cmake $HOME/alexa/source/avs-device-sdk  -DGSTREAMER_MEDIA_PLAYER=ON  -DPORTAUDIO=ON -DPORTAUDIO_LIB_PATH=$HOME/alexa/third-party/portaudio/lib/.libs/libportaudio.so  -DPORTAUDIO_INCLUDE_DIR=$HOME/alexa/third-party/portaudio/include  -DCMAKE_BUILD_TYPE=DEBUG

I tried to clean up the build directory to get a clean log output for v1.21.0, but this time the built was successful.

@jcatumba Glad that worked. Will be closing this issue, please open a new issue if you need further assistance.


Docs: update Middy.js docs with v2 changes

What were you searching in the docs?
The Middy.js docs have a page dedicated to Powertools for AWS Lambda (TypeScript). Our new major version includes changes on how customers use our middlewares so we should make sure that the docs reflect them.
Is this related to an existing documentation section?
https://middy.js.org/docs/integrations/lambda-powertools
How can we improve?
With v2 becoming available we want customers using the Middy.js documentation to have access to the latest features and info about Powertools.

Got a suggestion in mind?
No response
Acknowledgment

[X] I understand the final update might be different from my proposed suggestion, or refused.

Opened PR on Middy.js' repo: middyjs/middy#1199


Function returning a struct cannot be declared nogil

Example:
cdef struct Structure:
    double x

cdef Structure build() nogil:
    return Structure(0.0)

The bug is actually due to Structure (0.0) looking like a Python call.

I believe this is a duplicate of #1642.

I am not able to replicate it on master branch anymore (commit https://github.com/cython/cython/commit/0b3c45b59626858a9d6717583429496f50b9f441):
$ cat delete.pyx
cdef struct Structure:
    double x

cdef Structure build() nogil:
    return Structure(0.0)

$ cythonize -3fib delete.pyx
[1/1] Cythonizing /Users/matus/dev/cython/test/delete.pyx
performance hint: delete.pyx:4:5: Exception check on 'build' will always require the GIL to be acquired. Declare 'build' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions.
running build_ext
building 'delete' extension
creating /Users/matus/dev/cython/test/tmpw6ba0rju/Users
creating /Users/matus/dev/cython/test/tmpw6ba0rju/Users/matus
creating /Users/matus/dev/cython/test/tmpw6ba0rju/Users/matus/dev
creating /Users/matus/dev/cython/test/tmpw6ba0rju/Users/matus/dev/cython
creating /Users/matus/dev/cython/test/tmpw6ba0rju/Users/matus/dev/cython/test
clang -Wsign-compare -Wunreachable-code -fno-common -dynamic -DNDEBUG -g -fwrapv -O3 -Wall -I/Users/matus/dev/cython311/include<EMAIL_ADDRESS>-c /Users/matus/dev/cython/test/delete.c -o /Users/matus/dev/cython/test/tmpw6ba0rju/Users/matus/dev/cython/test/delete.o
/Users/matus/dev/cython/test/delete.c:1754:41: warning: unused function '__pyx_f_6delete_build' [-Wunused-function]
static struct __pyx_t_6delete_Structure __pyx_f_6delete_build(void) {
                                        ^
1 warning generated.
clang -bundle -undefined dynamic_lookup /Users/matus/dev/cython/test/tmpw6ba0rju/Users/matus/dev/cython/test/delete.o -o /Users/matus/dev/cython/test/delete.cpython-311-darwin.so
$ python -c 'import delete'
$


webkitAutoFill type is the wrong case

For creating a new element, the typescript file lists the CSS class for autofill as webkitAutoFill, however, when using that - an error is thrown by stripe because the letter F should be lowercase.
The error is Unrecognized create() parameter: classes.webkitAutoFill is not a recognized parameter. This may cause issues with your integration in the future.
I think the types file needs to be updated to be webkitAutofill.

Thank you for pointing this out, @Joebayld!
You're correct, this should be webkitAutofill. We'll get a PR up with this fix soon. 👍


Fix kernel version check to >= 4.19

Fixing the kernel version check for amd64 from >= 4.15 to >= 4.19

Huh, I could've sworn that we've changed that already previously.

Yeah, we have in prodfiler. But it looks like we didn't update main.go with the big sync.


Ignore io.reactivesocket.aeron.internal.reactivestreams.AeronChannelTest

Problem
The test fails on travis all the time.
Modification
Ignored it for now. I am not yet clear about the reason for the failure.
Result
Travis build should pass now and so other PRs can be validated.

@robertroeser I am ignoring this for now. Maybe we can fix it or invest in something that only ignores it on travis. My preference will be the former :)


Don't spell check citation keys

When citing other papers, the spell checker picks up on the citation keys and tries to correct them. It racks up a lot of annoying warnings. See picture.

In this case, it suggests that "Dourish2004" should be "Nourished". I would like the spell checker to just skip these kinds of suggestions.

Just pushed out a patch since think this got fixed in 396f81647cd7da4624ad0144e124bc074f459ba6

Please try updating to 0.7.1

That did it! Thanks for the fast update.
On a related note: Comments are also spell checked. I usually write todos to myself, something like % TODO Baltrunas' ideas should be explored further. The spell checker then complains on the words "TODO" and "Baltrunas'" (which is a surname). I see the point in spell checking comments, but in this case it also kind of annoying. Maybe one should be able to turn spell checking for comments on and off? I can make another issue out of this, if you want.

I agree that the spell checking in comments is an issue. I haven't figured out the best way to resolve it yet.
Please create a new issue and I'll start working on some ideas.


The overlay doesn't display for one second at the load of the page

How could I fix this please ? For some reason, when I load the page, during 1 second, DOM elements are visible and then the overlay is appearing.

Do you have a link to your implementation so I can take a look?

Checking in again.

Hey Gaya,
First of all, thanks for the great plugin!
I experience the same issue as the OP.
The issue can be seen in IE11 and Chrome 56.
The page is seen for a fraction of the second and only then the Overlay is shown.
I load the script in the <head>.

I would like to know how to solve this problem :)


docs: regenerate rules documentation

#17

@allcontributors add @StyleShit for idea

@all-contributors please add @styleshit for doc.

🤖 Beep boop! This comment was added automatically by all-contributors-auto-action.
Not all contributions can be detected from Git & GitHub alone. Please comment any missing contribution types this bot missed.
...and of course, thank you for contributing! 💙


really decouple the nixpkgs workaround

Follow-up to #84 for testing

[x] Wait for upstream PR to be merged
[x] The module will be moved to its own git repo.

https://github.com/srid/nixpkgs-140774-workaround


More args to creating dummy

BeardId, FaceId, SteamId ( Id ), Name, Position, AutoVanish, AutoGod

https://github.com/openmod/openmod/issues/453
Waiting..

https://github.com/EvolutionPlugins/Dummy/releases/tag/v2.7.0 Added --name argument


Installed the setup exe file still facing the issue that dotnet sdk is not installed

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-cli-tutorial/install
Operating System: windows
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Can you let us know what dotnet --info returns?


Trademark Violation?

https://itunes.apple.com/us/app/cesium-streamlined-music-player/id924491991?mt=8
Noticed this app using the same name. Just thought I would bring your attention to it.

Thanks @drakej.  In the future, feel free to email me directly<EMAIL_ADDRESS>about things like this so we can keep the GitHub issues focused on code.


scream-pcap: libpcap mode for those that can only see their UDP multicasts in wireshark/tcpdump

This allows the Scream client to be started in libpcap (sniffer) mode.
Mostly useful if you are not a part of the lucky group to have their UDP multicast packets be successfully delivered to the user-space applications by their kernel.
If you are able to see the UDP multicast/unicast transmission of scream in wireshark/tcpdump but unable to have it be delivered to the user-space scream client (or netcat, even), you're a part of this group. You tried everything from disabling hardware offloading for UDP checksums to adjusting net.*.mc_forwarding or net.*.rp_filter with no luck, and fell back to the IVSHMEM solution, which is polling, resulting in less than ideal latency for gaming.
With this PR, you can run scream unix receiver in pcap mode with scream -P -i macvtap0 and if you have uid/gid issues due to a hard requirement to be a specific user for your pulseaudio/alsa setup, you can do setcap cap_net_raw,cap_net_admin=eip ./scream as root and give it the capabilities it needs to capture packets without being root. I am relatively sure this can be narrowed down to specific interfaces or ports if need be.
Let me know if you have any questions. In my VFIO setup, with this I see a 3x reduction in audio latency compared to the IVSHMEM.
I will be experimenting with eBPF for further latency improvements.
This primarily enables people having issues with multicast UDP not getting delivered to the user-space applications for various reasons but has the additional benefit of allowing VFIO users to utilize their macvtap setup without having to take the convoluted path of vm -> macvtap -> eth0 -> router -> eth0.

Looks good, thanks! Although I really wonder what makes the mcast packets disappear ...


WIP: Fixing afterMount not being called when in the DOM

This change makes afterMount always occur when the component is in the DOM. Potentially kind of hacky.
This will fix #108
/cc @staygrimm

Will this be merged?

This will be a breaking change if I do it like this, as it will call it on the next frame. This could break some existing functionality, so I want to have a look at this now and see if I can get it working properly.

This now happens at the end of the render pass. It will happen in the same frame, but just after everything else has rendered.
Just need to add some tests to make sure the mount hooks are called in the correct order.

This should work in practice, but i've noticed that there are some inconsistencies in the way the hook events are called. In reality this probably won't matter as you shouldn't care about the state of the DOM in other components anyway, as long as the DOM element for the component you're looking at (and all child components) are completely rendered in the DOM in afterMount and afterRender.
When the tests pass, I'll merge this in and we can look at hook order later if it becomes an issue.


MySQL support?

This is a great generator, I wonder how much work would be necessary to make it compatible with MySQL

MySQL does not have a COMMENT ON statement.
Therefore, it must be handled completely differently from PostgreSQL.
It must also be carried out with an ALTER statement, and information on the column type must also be specified.
I don't think there is anything i can't handle, but it will take time.
Thanks.

Hey I made a small generator work, however I'm struggling with Prisma generating a extra migration after the migration with the comments, this extra migration is just redeclaring the ALTER TABLE with the column type minus the comment, thus erasing the past modification. Have you ever seen this behavior? I remember this also happened when using @dbgenerated in some cases.

I have never encountered this phenomenon.
I am sorry I am not able to help you.


[0.4.3-dev]: ssh key is lost on reboot

Verified that after several reboots, still able to log in using my ssh key.
v0.4.3-rc3


Detected XCPU in the GDB loop (0x9db00000)

1. SDK version（SDK 版本）
{
V2.107
}
2. In what kind of operation problems appear, and how to reproduce the problem ?（什么样的操作步骤问题会出现，是否是稳定复现，如何复现问题？）
{
Unsure:
I suspect the cause might be the use of Trace, memcpy, memset or strcmp in the function(handle_response) triggered after the API_EVENT_ID_SOCKET_RECEIVED event. i.e:
...
void handle_response(char *response, double lat, double lng) {
    // uses `Trace`, `memcpy`, `memset` and `strcmp`
}
...
void EventDispatch(API_Event_t* pEvent) {
    ...
    case API_EVENT_ID_SOCKET_RECEIVED:
        ...
        handle_response(myBuffer, latVal, lngVal);
        ...
}
...

Ruby Script Output
Detected event: 0x820c4c88.
Detected event: 0x820c4db4.
Assert received!! Reading detail...
ASSERT DETAIL :

##############################################
# FATAL assert
# --> Active Job = 184
# --> Old Job = 0x8209c2c4
# --> New Job = 0x8209c2b8
##############################################
Detected BCPU in the GDB loop (0x9db10000), connect GDB debugger for more info.
Detected XCPU in the GDB loop (0x9db00000), connect GDB debugger for more info.

gdb info
(gdb) bt f
#0  0x8200deb1 in sxs_Raise ()
No symbol table info available.
#1  0x00000000 in ?? ()
No symbol table info available.

Source window content
}

Another similar error (GDB output):
(gdb) bt f
#0  0x81c0741b in _sxr_HFree ()
No symbol table info available.
#1  0x8200e4f3 in sxr_FreeJob ()
No symbol table info available.
Backtrace stopped: frame did not save the PC

please dump longer logs in pastebin!

@punee995 Thanks. I was unaware of its existence. Also, I am unsure if the information I am providing is adequate to get the issue resolved. Feel free to request for and instruct on how to obtain more information.

Different backtrace after re-flashing:
(gdb) bt f
#0  0x8200deb1 in sxs_Raise ()
No symbol table info available.
#1  0x81c07385 in _sxr_HFree ()
No symbol table info available.
#2  0x881406f9 in l1a_MonitorReq ()
No symbol table info available.
#3  0x88097e4b in l1s_CchControlJob ()
No symbol table info available.
#4  0x88097d21 in l1s_RxCbchJob ()
No symbol table info available.
#5  0xfdfdfdfd in ?? ()
No symbol table info available.

I have been trying to narrow down the possible causes of this error. Currently, I think it is being caused by multiple writes to the socket. I have different programs achieving the same task of obtaining data from a server and after a few running iterations, this error pops after Line 206

It means we can not use Socket_TcpipWrite twice to write data to the socket server in one process? how can we write several char variables to the socket server? I have also confusing about this issue.

我重新烧录较大的lod文件可以顺利解决这个问题

alguien pudo solucionarlo?

I fixed this by flashing the Factory AT command binary from
https://docs.ai-thinker.com/en/gprs/firmware
with this tool
https://docs.ai-thinker.com/_media/gprs/ai-thinker_a9_a9g_at_v02.02.20190915r.rar


Why did you change flow formula?

I wanted to ask about this commit: https://github.com/lucidrains/e2-tts-pytorch/commit/953a3b672b8089e7b61e696ddf1468006ac70537#diff-aa4e45ab239723e4fe2411800a686d4b7d1a7235044da0fec1ce924182e03aceR989
Why did you change these formulas? For example, formula for flow? Does it help with convergence? What is the reasoning behind this?

It was just a simplification as sigma doesn't seem to affect much and in the original paper on audio flow matching, as far as i remember, it was set to 0.

It was just a simplification as sigma doesn't seem to affect much and in the original paper on audio flow matching, as far as i remember, it was set to 0.

So if in my implementation I still have original formula and sigma is 1e-5 it basically doesn't affect anything but does not make training worse either?

most likely
On Friday, November 15, 2024, Julia Korovsky @.***>
wrote:

It was just a simplification as sigma doesn't seem to affect much and in
the original paper on audio flow matching, as far as i remember, it was set
to 0.
So if in my implementation I still have original formula and sigma is 1e-5
it basically doesn't affect anything but does not make training worse
either?
—
Reply to this email directly, view it on GitHub
https://github.com/lucidrains/e2-tts-pytorch/issues/39#issuecomment-2478446374,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHIJQDVQ52UPQWWGM4GXIT2AXAQVAVCNFSM6AAAAABR2WU47WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZYGQ2DMMZXGQ
.
You are receiving this because you commented.Message ID:
@.***>


prepare_metadata_for_build_wheel() exits the interpreter when invoked for the 2nd time

I've reproduced this over the https://github.com/pytest-dev/pluggy and https://github.com/pytest-dev/pytest directories. Happens both on setuptools 40.8.0 and master.

Run a fresh Python interpreter:

$ python

Attempt to run prepare_metadata_for_build_wheel twice:

Python 3.7.4 (default, Jul  9 2019, 16:32:37)
[GCC 9.1.1 20190503 (Red Hat 9.1.1-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import setuptools.build_meta
>>> setuptools.build_meta.prepare_metadata_for_build_wheel('.')
running dist_info
creating pluggy.egg-info
writing pluggy.egg-info/PKG-INFO
writing dependency_links to pluggy.egg-info/dependency_links.txt
writing requirements to pluggy.egg-info/requires.txt
writing top-level names to pluggy.egg-info/top_level.txt
writing manifest file 'pluggy.egg-info/SOURCES.txt'
reading manifest file 'pluggy.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
warning: no files found matching 'CHANGELOG'
warning: no previously-included files matching '*.pyc' found under directory '*'
warning: no previously-included files matching '*.pyo' found under directory '*'
writing manifest file 'pluggy.egg-info/SOURCES.txt'
creating '.../python-pluggy/pluggy-0.12.0/pluggy.dist-info'
'pluggy.dist-info'
>>> setuptools.build_meta.prepare_metadata_for_build_wheel('.')
running dist_info
error: [Errno 2] No such file or directory

Interpreter exists. Restarting the interpreter results in the same behavior (works for the first time, exists for the second).

@hroncok It is actually required by PEP 517 that each backend call is in a fresh subprocess:

Frontends should call each hook in a fresh subprocess, so that backends are free to change process global state (such as environment variables or the working directory). A Python library will be provided which frontends can use to easily call hooks this way.

From what I can tell, the problem is not reproducible if you always use a fresh subprocess (the following works, for example):
from setuptools import build_meta
from subprocess import run

run(['python', '-c',
     'from setuptools import build_meta; ' +
     'build_meta.prepare_metadata_for_build_wheel(".")'])

run(['python', '-c',
     'from setuptools import build_meta; ' +
     'build_meta.prepare_metadata_for_build_wheel(".")'])

Is there a particular reason you wanted to call this function twice in a single interpreter run?

Is there a particular reason you wanted to call this function twice in a single interpreter run?

Not really, I was just testing something and got confused by this behavior.

I think this is basically not a bug, because it only occurs when violating the contract of how this function is called. That said, it seems unlikely that it is actually intended behavior, and I'm not entirely sure why it is crashing, so I'm going to leave this open to track why it's happening in case it is an unexpected side effect of some bug that we don't want happening.
Regardless, I think we may want to take this as an opportunity to be more explicit about the fact that we are only supporting calling each of these hooks exactly once per process by setting some global flag like "_BUILD_HOOK_CALLED` and explicitly raising an exception when the contract is violated. We could do this, for example, with a decorator like this:
def _build_hook_call(f):
    @functools.wraps(f)
    def hook(*args, **kwargs):
        global _BUILD_HOOK_CALLED
        if _BUILD_HOOK_CALLED:
            raise ReusedSubprocessError("Build backend hooks are each intended to " +
                                        " be called in a fresh subprocess, per PEP " +
                                        "517. Calling a hook more than once during an " +
                                        "interpreter lifetime is undefined behavior.")
        rv = f(*args, **kwargs)
        _BUILD_HOOK_CALLED = True
        return rv

    return hook

@hroncok It is actually required by PEP 517 that each backend call is in a fresh subprocess:

Frontends should call each hook in a fresh subprocess, so that backends are free to change process global state (such as environment variables or the working directory). A Python library will be provided which frontends can use to easily call hooks this way.

😢 I mean damn. This is good for build backends convenience but is really bad for performance because now you're forcing every backend/frontend interaction to pay the full price of python interpreter startup/teardown... 😢 for this...


Add runtime configuration validation

What does this PR do?
Adds config models from https://github.com/DataDog/integrations-core/pull/8675

Can you update the tests to use dd_run_check so validation executes?

Done! E2E tests were already doing that though


Error: Could not link main/homebrew/etc/bash_completion.d/brew

Hi,
our installation fails now with the following error. It was still working a few hours ago.
Could it be related to #1616
==> Searching taps...

Error: Could not link:
.../main/homebrew/etc/bash_completion.d/brew

Please delete these paths and run `brew update`.
Error: Could not link:
.../main/homebrew/share/doc/homebrew

Please delete these paths and run `brew update`.
Error: Could not link:
.../main/homebrew/share/zsh/site-functions/_brew

Please delete these paths and run `brew update`.
Error: Could not link:
.../main/homebrew/share/man/man1/brew-cask.1
.../main/homebrew/share/man/man1/brew.1

Did you try to delete those paths and run brew update?

Still trying to pin down the root cause. If I delete those paths and run brew update it works.
But we are currently depending on installing homebrew newly with an automated method. So I think there must be something broken in the homebrew installation itself.

Sorry the problem was with our setup, we pulled in an old dependency.


Move back towards Distributed's _retire_workers method

Currently our _retire_workers implementation implementation deviates from Distributed's _retire_workers implementation. Would be nice if we could bring them back into correspondence and/or eliminate our copy of _retire_workers entirely in favor of the Adaptive base class implementation.
ref: https://github.com/dask/dask-drmaa/pull/63#pullrequestreview-105608839

I'm guessing the spirit is that scale_down() should actually be stopping the DRMAA jobs (similar to how remove_workers() is implemented) instead of the current implementation of calling scheduler.retire_workers(). So first Adaptive would communicate to the workers to stop via RPC in scheduler.retire_workers(), and second we would also terminate the jobs directly via DRMAA in scale_down().
Assuming there is no error in either step, these steps I think would be redundant (so we could even have the option to do nothing in scale_down() perhaps), but probably there is no downside in redundancy?

(As a potential reference, KubeCluster.scale_down() does no book-keeping nor any calls to its scheduler, all it does is stop the kubernetes pods for the provided list of workers. Might not be a perfect analogy for dask-drmaa but that's how I formed my mental model.)

FWIW this comment suggests your understanding is correct. We could use Session.control for the same purpose.

Attempting to solve this in PR ( https://github.com/dask/dask-drmaa/pull/85 ). Please take a look.


Add data collection notice

@avanigupta do we still have the "AppConfiguration-DotnetProvider-Windows-Buddy-main" (see it under "show all checks")? I can remove it from the branch policy. It's blocking from merging the PR.

https://github.com/Azure/AppConfiguration-DotnetProvider/blob/3e4de83d71b12fcb952cd20d19712dd232522ced/src/Microsoft.Extensions.Configuration.AzureAppConfiguration/AzureAppConfigurationProvider.cs#L115-L115

You may turn off the telemetry by setting the environment variable AZURE_APP_CONFIGURATION_TRACING_DISABLED to True or 1

For "True". I'm thinking what the result will be if the env is set to true (lowercase). According to the impl, as far as I understand it should be the same as True, because it's eventually parsed by bool.TryParse. Anyway, it doesn't matter much as it's impossible/unnecessary for us to list all possible strings that can be parsed as True.
For "1". Learning from the examples of system.boolean.tryparse, I'm wondering whether setting it to 1 can really disable the request tracing. Because environment variable is of string type, and the string "1" should fail the parsing, thus enables the request tracing. Maybe it's a stupid question as I lack expertise on c#, please let me know then.

do we still have the "AppConfiguration-DotnetProvider-Windows-Buddy-main" (see it under "show all checks")? If not, I can remove it from the branch policy. It's blocking from merging the PR.

@zhenlan I'm trying to fix some issues since the automatic triggers seemed to stop working on some PRs. I ran the pipeline for this branch for now.

https://github.com/Azure/AppConfiguration-DotnetProvider/blob/3e4de83d71b12fcb952cd20d19712dd232522ced/src/Microsoft.Extensions.Configuration.AzureAppConfiguration/AzureAppConfigurationProvider.cs#L115-L115

You may turn off the telemetry by setting the environment variable AZURE_APP_CONFIGURATION_TRACING_DISABLED to True or 1

For "True". I'm thinking what the result will be if the env is set to true (lowercase). According to the impl, as far as I understand it should be the same as True, because it's eventually parsed by bool.TryParse. Anyway, it doesn't matter much as it's impossible/unnecessary for us to list all possible strings that can be parsed as True.
For "1". Learning from the examples of system.boolean.tryparse, I'm wondering whether setting it to 1 can really disable the request tracing. Because environment variable is of string type, and the string "1" should fail the parsing, thus enables the request tracing.

That is a good catch, request tracing will not be disabled of the environment variable is set to "1". It only works for true/false (case-insensitive).

I think we should fix the code to support "0/1" values for disabling telemetry. Azure SDK also does the same (code).

Thanks for the feedback. I updated the text to just TRUE.

@zhenlan do you think we need to support "0/1" values as well if SDK supports this?

I think it's fine not to. We can't go back to fix released versions anyway.


Pie chart shows on wall after resetting

Solved by pressing f3 when in a world before pressing reset key

Not worth solving as of right now


fix: Add Index out of bound exception handling for PropertiesFile.save()

Summary
Expection catch and log for PropertiesFile.save()
Change more general Exception catch for PropertiesFile.load()
Unit test for added function
Checklist

[x] Does your PR title have the correct title format?
Does your PR have a breaking change?:  no

This should workaround the issue. Were you able to locate the root cause? Is this from lack of file access or is it the Properties have become corrupted?

I'll ask if customer can give us some log info that Marvin previous added. It sounds like a random access issue that caused by multithreading

Will the logs you and Marvin added provide more info about the root cause? It looks like we're logging the file path and the stack trace, but the problem appears to be with the values in the properties map.
Do we blanket catch Exception normally in our SDKs? It's normally an anti-pattern since it can potentially hide serious problems that should actually escalate instead of leaving the app in an uncertain state.


Update sbt-scoverage to 1.9.1

Updates org.scoverage:sbt-scoverage from 1.8.2 to 1.9.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scoverage", artifactId = "sbt-scoverage" } ]

labels: sbt-plugin-update, semver-minor

Superseded by #574.


Buffer stalls due to null current segment reference in some DASH live streams

Have you read the FAQ and checked for duplicate open issues?
yes
If the problem is related to FairPlay, have you read the tutorial?

n/a
What version of Shaka Player are you using?

v4.10.9
Can you reproduce the issue with our latest release version?
yes
Can you reproduce the issue with the latest code from main?
yes
Are you using the demo app or your own custom app?
custom
If custom app, can you reproduce the issue using our demo app?
yes
What browser and OS are you using?
Chrome Version 127.0.6533.120
macOS Ventura Version 13.6
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
n/a
What are the manifest and license server URIs?

Can send via email.
What configuration are you using?  What is the output of player.getConfiguration()?

default
What did you do?

Play a live, multi-period DASH manifest.
What did you expect to happen?
Seamless playback.
What actually happened?

Playback is fine during the first period, but when new periods are entered, playback will freeze a few segments into the new period. Logs indicate the buffer has run out. After falling out of seek range, the playhead will then jump forward and resume playback, then temporarily freeze again when another new period has been entered.
Are you planning send a PR to fix it?
Possibly. If someone more familiar with MetaSegmentIndex and TimelineSegmentIndex is able to look at this, a fix might be more obvious. I will add debugging notes in the comments.

We are seeing a race condition where the value of mediaState.segmentIterator.current() can be null in the streaming engine, and a current segment is never found on updates. So playback stalls until the playhead is forced to seek forward.

We get a null reference even when that reference is present in a SegmentIndex of the MetaSegmentIndex. This occurs when in the MetaSegmentIndex.get method, the numPassedInEarlierIndexes calculation gets out of sync. The SegmentIterator ends up trying to find a reference at a negative position which never exists.
numPassedInEarlierIndexes uses this.numEvicted_ to calculate the offset for the position of the current reference. However in a multi-period scenario (i.e content plus ad breaks), once the playhead has moved from one period into the next and a manifest update occurs, evict in TimelineSegmentIndex gets called on the first period's references. That number of references is then added to this.numEvicted_. The next time the correctedPosition is calculated for the current reference position, this.numEvicted is a much larger number than the current position and is subtracted from position to return the negative correctedPosition.

An easier to read log:

The PR adds a null check in getSegmentReference which allows the current reference to be found by time in the following else if block. The correctedPosition in MetaSegmentIndex.get falls back in sync after the current reference is found by time.


To the bitter end

OK, fixed up everything which @bbatsov commented on.

The ClassStructure cop looks the same to me. I really think that making it flexible is the key to its long-term usefulness. The defaults are pretty sensible for sure, but as you mentioned yourself - preferences on the subject will vary.

I'd suggest moving the ClassStructure work to a separate PR and merging everything else right away.

Removed Style/ClassStructure.


V0.2.1

What type of PR is this?

What this PR does / why we need it
Which issue(s) this PR fixes

Fixes #
Special notes for your reviewer

database change in v0.2.1:

https://github.com/kubeagi/arcadia/pull/914

database change in v0.2.1:

feat:the time consumed for data processing. #914

Done


Release v1.0.3

Added * in subheadlines for them to appear as bullet points in Markdown.

Hi! Sorry I forgot to reply (thought I did) - make a PR into the develop branch instead! @darensin01

Any news?

Hey so sorry, this year has been insane. I'm not actively maintaining this project any more. Feel free to fork it and maintain it, I'm also happy to kill my bot and give you the space to run yours on /r/singapore if you want to.

@fterh does not look like any of the current forks are active. Just to confirm - the current active bot is still yours?

Yes it is, it's not being actively maintained but it's still running.
On Thu, Nov 4, 2021 at 1:58 AM Ashwani @.***> wrote:

@fterh https://github.com/fterh does not look like any of the current
forks are active. Just to confirm - the current active bot is still yours?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fterh/sneakpeek/pull/58#issuecomment-960566569, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AF5XZGAPHQP7EFHD24MPRXLUKJKMTANCNFSM4KLPO62Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Cheers,
Fabian Terh


descriptor: sha{256,512}: disallow /[A-F]/ characters

Disallowing upper characters will be useful for avoiding implementation bugs
Signed-off-by: Akihiro Suda<EMAIL_ADDRESS>

Should probably make the regex [:upper:] then; i imagine base64 will make
an appearance eventually.
On Wed, May 10, 2017 at 9:37 PM Akihiro Suda<EMAIL_ADDRESS>wrote:

@AkihiroSuda commented on this pull request.
In descriptor.md
https://github.com/opencontainers/image-spec/pull/667#discussion_r115890030
:

@@ -137,11 +140,17 @@ If a useful algorithm is not included in the above table, it SHOULD be submitted
[SHA-256][rfc4634-s4.1] is a collision-resistant hash function, chosen for ubiquity, reasonable size and secure characteristics.
Implementations MUST implement SHA-256 digest verification for use in descriptors.

+When the algorithm identifier is sha256, the encoded portion MUST match /[a-f0-9]{64}/.
+Note that [A-F] MUST NOT be used here.
I think hex-encoding is specific to algorithm.
Depending on the algorithm, hex-encoded digest can be
somealgorithm+uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/opencontainers/image-spec/pull/667#discussion_r115890030,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABJ6yL43ceEiR5nfhpDRLHU1jnXm-lfks5r4mZwgaJpZM4NWKVg
.

@erikh
base64 should use different algorithm identifier, so I think that is the out scope of this PR, which only focuses on sha256 and sha512.

@AkihiroSuda This looks good. Could you also make a PR to go-digest?

sure https://github.com/opencontainers/go-digest/pull/34

LGTM

LGTM


Avoid double-build of referenced projects

I added a verifier that runs with every test to cause a test failure if double-build ever occurs.
Then I removed the test code that sets the CustomAfterMicrosoftCommonTargets global property for every build request because that masks the bug in the nuproj.targets file. Users don't set that global property, and the fact that the test does made it appear everywhere, resulting in only a single build in each project even though for the user, double builds result.
Finally, with the bug exposed and tests now failing, I removed the code in NuProj.targets that caused the double-build. I did not see any regressions in the tests from its removal (which was disappointing as this probably does regress something), but I suspect that whatever regressed is less important than fixing frequent timing build failures. And when we identify the regression, we can design a proper fix that doesn't regress this one now that we have a test to help lock it in.
Fix #118

OK, so I found a regression. It only happens when building from the command line:

C:\Users\andarno\git\nuproj\src\NuProj.Tasks\NuProj.Tasks.csproj : error MSB4057: The target "_NuProjGetProjectCl osure" does not exist in the project.

It should be a simple fix.

IIRC, I've started inserting CustomAfterMicrosoftCommonTargets for nuget integration, in case the build server cannot find c:\Program Files (x86)\MSBuild\12.0\Microsoft.Common.Targets\ImportAfter\Microsoft.Common.NuProj.targets file.
Maybe better workaround would be add a build\Nuproj.targets to package, that would import  tools\NuProj.targets for NuProj projects, and tools\Microsoft.Common.NuProj.targets for all project types. In that case user would have to install package for all projects, not just .nuproj ones.
Thoughts?

@kovalikp Thanks for your reply. I've been planning/thinking about creating a NuGet package for Microsoft.Common.NuProj.targets, yes. But I've been thinking it should be a separate package (NuProj.Common, perhaps?) rather than the same one, but your approach seems like it would work, so I could be persuaded.


Determine feasibility of pure ESM package

What are your thoughts on that? Can common.js be dropped?

All stable node.js versions support ESM
Same with browsers https://caniuse.com/?search=ESM
Using ESM removes necessity of building / bundling files

Sindre Sorhus who maintains tons of popular packages have been using esm for a long time. His guide: https://gist.github.com/sindresorhus/a39789f98801d908bbc7ff3ecc99d99c
I want to move to ESM asap. Note that esm deps can't be used from commonjs, BUT commonjs deps can be used from ESM.

Note that esm deps can't be used from commonjs
I guess this a big problem for us

Yes

Could you clarify why? Every env supports esm these days except for electron where folks use bundlers to convert back to commonjs.

@paulmillr what's the drawback of supporting cjs on your end?
I'm pretty sure we have plenty of applications which use starknet.js as a dependency and still use cjs

I agree on same

I would just like to add that this topic would maybe be better suited in 1-2 months - since now we have a very important Starknet update coming in ~2 weeks and we need to adapt starknet.js accordingly!

Hey Paul, I agree that pure ESM is the direction that JS packages should move going forward.
However, as you know, we're all working around the clock to migrate and support starknet v0.11. Would it be possible to support cjs so that starknet.js can support starknet v0.11, and then we can discuss moving to pure ESM for subsequent versions of noble after starknet v0.11?
I think our top priority is supporting starknet v0.11 as fast and best we can. Then we can move to pure ESM when things are more settled.
Let me know if that would work for you

That makes sense. How about I release 0.8.1 with esm+commonjs, for your release? Any bugfixes we could do 0.8.x And 1.0.0 pure esm after this.

this sounds like a nice compromise :)

OK folks, cjs is done: use https://github.com/paulmillr/micro-starknet 0.2.1; api is the same. I've moved stark curve back into a separate package because it seems like stark would be changing more than other curves.


Bridge: Use 24h time format

At the moment bridge uses 12 hour time format without AM/PM.
This is confusing, as 15:35 would be displayed as 03:35 (without AM/PM).
I propose that we change this to 24h time format (for now).

Fixed with 0.6.0.beta


push_project_to_gcs is not working with credentials stored in a prefect block

I've created a new project using the docker-gcs template. The credentials of my GCP service account are stored in a prefect block. According to the prefect project tutorial, this is the recommended setup. This is the push section in my deployment.yaml :
push:

prefect_gcp.projects.steps.push_project_to_gcs:
requires: "prefect-gcp>=0.4.1"
bucket: "somebucketname"
folder: somefolder
credentials: "{{ prefect.blocks.gcp-credentials.gcp-cred }}"

When initiating a deploy via prefect deploy --name ... , the step fails with
AttributeError: 'str' object has no attribute 'keys'
Expectation / Proposal
Using credentials stored in a prefect blocks works. Even better, I can use a prefect gcs block directly.
Traceback / Example

[ ] I would like to help contribute a pull request to resolve this!

An older version of the GcpCredentials block saved the service_account_json fields as JSON string instead of an object, which is the root cause of this error. Recreating the GcpCredentials block will use the new version and save the service_account_json field in with the correct type. To guard against service_account_json values that are saved as JSON strings, we should attempt to parse the service_account_json field value if it is a string.


How do I use this to replace mozilla overlay in presence of rustup toolchain file?

If we look at something like crate2nix, it's documented how to use mozilla overlay: https://github.com/kolloch/crate2nix#choosing-a-rust-version
What is done there is we generate the toolchain then override individual components like rustc and such in the nixpkgs.
However, fromRustupToolchainFile only produces a single derivation and individual components don't seem accessible. This is documented at https://discourse.nixos.org/t/rust-overlay-a-better-rust-toolchain-provider-and-drop-in-replacement-of-nixpkgs-mozilla/10986/14
I have something like this

let
  sources = import ./sources.nix;
  rustChannelsOverlay = import sources.rust-overlay;
  # rustChannelsSrcOverlay =
  #   import "${sources.nixpkgs-mozilla}/rust-src-overlay.nix";
in import sources.nixpkgs {
  overlays = [
    rustChannelsOverlay
    # rustChannelsSrcOverlay
    (self: super:
      let rustChannel = self.rust-bin.fromRustupToolchainFile ../rust-toolchain;
      in {
        rustc = rustChannel;
        cargo = rustChannel;
        # rust = rustChannel;
        rust-fmt = rustChannel;
        rust-std = rustChannel;
        clippy = rustChannel;
        # inherit (rustChannel) cargo rust rust-fmt rust-std clippy;
      })
  ];
}

and it kind of seems to be working (I haven't completely verified) but it seems a bit wrong somehow. Also rust attribute doesn't exist so it's probably going to do wrong with if we try to cross-compile or something.

Using the returned derivation of fromRustupToolchainFile to override all components as you did should work since it is a symlinkJoin of all these components.
If you run into some errors (whether cross-compiling or not), please provide more details and steps to reproduce.


Serve static assets wtih an efficient cache policy

https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl/?utm_source=lighthouse&utm_medium=devtools

Github has an unalterable policy, so unless I move away from Github Pages, this is just gonna be like this.
See: https://github.com/orgs/community/discussions/11884


Autorestart probably shouldn't restart a process if terminated intentionally

If a process is set to autorestart: true then it will restart when killed by mprocs, e.g. as a result of pressing 'x' or using the term-proc command.
I assume that the purpose of autorestart is to re-start processes if they crash, exit due to errors, or even due to user interaction in the terminal. However, I do not expect the process to restart if I have issued a command to terminate it from within mprocs. Is the current behaviour correct? If so, should there be a command which can terminate a process without auto-restarting?

Yes, the process certainly should NOT autorestart if stopped manually. This is a bug.


fix: Inconsistent naming of params and incorrect example in readme

Why

We are using inconsistent naming of params
Readme is showing an incorrect example

How

Make the params that are referring to a pk use uid
params that are to be used in a query ?user_uid=xxx can be named as user_uid
Fix example to what we are currently using

How Has This Been Tested?

Locally

Checklist

Note: this will break existing usage if they use kwargs, but better to just get it fixed now and inform clients than back compat this imo


docs: use --save-dev to align with main project

Description

Motivation and Context

Usage examples

// commitlint.config.js
module.exports = {

};

echo "your commit message here" | commitlint # fails/passes

How Has This Been Tested?

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Thany you ❤


We are able to conduct experiments that uses swept parameters

We aren't as of now apparently due to cadCAD bugs

Using @LinuxIsCool fix seems to solve it. Testing underway
https://github.com/BlockScience/aztec-gddt/commit/d109aab154c0b7e4370f4274f46206ce5f53c703


[VL] Potential compatibility issues for Spark get_json_object function

Description
Currently, get_json_object is enabled to use velox's current implementation. It works for basic cases. But there are still some potential compatibility issues, which means returned result can be inconsistent with spark.

Moving on, we shall switch to use SIMD_JSON in Velox
https://github.com/facebookincubator/velox/pull/5179


Feedback form changes

"Get in Touch" should appear in center. Also while filling the form the text is not readable properly in active input box.

Hey, I'd like to contribute to this issue.

I can do this task for you

assign me this plz

check out the PR

Thank you for assigning, would send a PR in some time.

both the task should be done to get the PR approved

@devansh016  Check out and Approve

Check Now
On Sat, 2 Oct 2021 at 14:30, Devansh Chaudhary @.***>
wrote:

both the task should be done to get the PR approved
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/devansh016/Minimal-News/issues/25#issuecomment-932718216,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQC7BW5GVLNLREPT6U2YX5LUE3C3PANCNFSM5FGA2ZWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Erro Instalação

Opa, tudo blz?
Formatei a minha maquina e, baixei novamente o mapos ... ao instalar apresenta erro no "composer install"
`Your lock file does not contain a compatible set of packages. Please run composer update.
Problem 1
- chillerlan/php-qrcode is locked to version 4.2.0 and an update of this package was not requested.
- chillerlan/php-qrcode 4.2.0 requires php ^7.2 -> your php version (8.0.9) does not satisfy that requirement.
Problem 2
- chillerlan/php-settings-container is locked to version 2.1.0 and an update of this package was not requested.
- chillerlan/php-settings-container 2.1.0 requires php ^7.2 -> your php version (8.0.9) does not satisfy that requirement.
Problem 3
- fzaninotto/faker is locked to version v1.9.2 and an update of this package was not requested.
- fzaninotto/faker v1.9.2 requires php ^5.3.3 || ^7.0 -> your php version (8.0.9) does not satisfy that requirement.
Problem 4
- piggly/php-pix is locked to version 1.2.6 and an update of this package was not requested.
- piggly/php-pix 1.2.6 requires chillerlan/php-qrcode ^3.4 -> found chillerlan/php-qrcode[4.2.0] but it does not match the constraint.`
como posso resolver?

Hi, i just stumbled across this issue - i have fixed the requirement for the v3.4 branch of chillerlan/php-qrcode (as of 3.4.1) so that it also will install on PHP8. However, v4.3.x is recommended but this would require PHP7.4+ and therefore a change in piggly/php-pix (pinging @caiquearaujo).


Rename check instance argument to _

What does this PR do?

Rename check instance argument to _
Motivation

Additional Notes

Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached
[ ] If the PR doesn't need to be tested during QA, please add a qa/skip-qa label.

Removed changelog label as a result of review


Provided doc-block methods to assist in facade intellisense

#4  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @GoodM4ven and the rest of your teammates on  Graphite


MQTT not workin and hass can't be uninstalled (0.79.0)

Home Assistant release with the issue:
0.79.0
Last working Home Assistant release (if known):
0.78.3
Operating environment (Hass.io/Docker/Windows/etc.):
Rpi 3 with latest updates
Component/platform:
Initially MQTT,then pip
Description of problem:
I upgraded to 0.79.0. This version doesn't seem to connect to my external MQTT server (Mosquitto). Other connections work fine by the way (have some scripts, apps and devices connecting to MQTT). The MQTT sensors within Hass stay at unknown and switches don't work.
To compare the working with the previous version and to determine if the problem is the latest version I wanted to do a quick rollback:
sudo pip3 install homeassistant==0.78.2

Pip eventually gave the error:
Installing collected packages: homeassistant
  Found existing installation: homeassistant 0.79.0
Exception:
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/pip/_internal/basecommand.py", line 141, in main
    status = self.run(options, args)
  File "/usr/local/lib/python3.6/site-packages/pip/_internal/commands/install.py", line 347, in run
    use_user_site=options.use_user_site,
  File "/usr/local/lib/python3.6/site-packages/pip/_internal/req/__init__.py", line 42, in install_given_reqs
    auto_confirm=True
  File "/usr/local/lib/python3.6/site-packages/pip/_internal/req/req_install.py", line 863, in uninstall
    uninstalled_pathset = UninstallPathSet.from_dist(dist)
  File "/usr/local/lib/python3.6/site-packages/pip/_internal/req/req_uninstall.py", line 357, in from_dist
    for path in uninstallation_paths(dist):
  File "/usr/local/lib/python3.6/site-packages/pip/_internal/req/req_uninstall.py", line 50, in unique
    for item in fn(*args, **kw):
  File "/usr/local/lib/python3.6/site-packages/pip/_internal/req/req_uninstall.py", line 68, in uninstallation_paths
    for row in r:
_csv.Error: line contains NULL byte

There's no way to rollback or reinstall (tried sudo pip3 install --upgrade --force-reinstall homeassistant --no-cache-dir), but it gives the same error. Probably some error in some requirements file?
On the MQTT part: I can't get home assistant to provide me with any errors there. Will try to add debugging information and get back to you with relevant errors.

Tried to rollback too, did not work (stuck "upgrading configuration")  But MQTT seems to work (that is, I don't use the discovery)

Have you since tried to install ? it was not HA failing but pip....

Tried to rollback too, did not work (stuck "upgrading configuration") But MQTT seems to work (that is, I don't use the discovery)

I don't use the discovery either. But location isn't picked up anymore (OwnTracks) and the MQTT cover doesn't work as well as the MQTT sensors.

Have you since tried to install ? it was not HA failing but pip....

Yes. Works fine for other python modules. Just gives this error for homeassistant.

I gave up downgrading, so installed latest again.   MQTT works ok.

I seem to have the pip install/uninstall working again by clearing all the pip caches and the deps from home assistant and then:
sudo pip3 install --ignore-installed homeassistant
And just to be sure did the next command again:
sudo pip3 install --upgrade --force-reinstall homeassistant --no-cache-dir
Home assistant is now restarting and building the dependencies. I hope that MQTT will be solved as well.

I gave up downgrading, so installed latest again. MQTT works ok.

Ok... Glad it works for you. Downgrading seems not to be succeeding for me either. Got the current 0.79.1 version running.
How is your MQTT server secured? Using TLS and username+password?
Still nog result on the MQTT part. In the debug log I see:
2018-09-30 14:21:13 INFO (Thread-2) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2018-09-30 14:21:14 INFO (Thread-2) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2018-09-30 14:21:16 INFO (Thread-2) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2018-09-30 14:21:20 INFO (Thread-2) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2018-09-30 14:21:27 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to home/livingroom/sunscreen_perc
2018-09-30 14:21:27 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to home/livingroom/light_sensor
2018-09-30 14:21:27 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to devices/doorbell/ring
2018-09-30 14:21:28 INFO (Thread-2) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2018-09-30 14:21:33 DEBUG (MainThread) [homeassistant.components.mqtt] Subscribing to owntracks/#
2018-09-30 14:21:44 INFO (Thread-2) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2018-09-30 14:22:16 INFO (Thread-2) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2018-09-30 14:23:20 INFO (Thread-2) [homeassistant.components.mqtt] Successfully reconnected to the MQTT server
2018-09-30 14:23:59 DEBUG (MainThread) [homeassistant.components.mqtt] Transmitting message on home/livingroom/sunscreen/set: {action:"DOWN"}
2018-09-30 14:24:02 DEBUG (MainThread) [homeassistant.components.mqtt] Transmitting message on home/livingroom/sunscreen/set: {action:"STOP"}
But I see no updates on the values and no reaction on the mqtt cover buttons. It does work when using my own script ow mosquitto_pub/mosquittos_sub clients.
Any ideas? It worked fine so far?

The Moqsuitto log has the following:
1538310460: New connection from <IP_ADDRESS> on port 8883.
1538310460: New client connected from <IP_ADDRESS> as mosqpub|25200-raspberry (c1, k60, u'{redacted mysuser}').
1538310460: Client mosqpub|25200-raspberry disconnected.
1538310460: New connection from <IP_ADDRESS> on port 8883.
1538310460: New client connected from <IP_ADDRESS> as mosqsub|25203-raspberry (c1, k60, u'{redacted mysuser}').
1538310460: Client mosqsub|25203-raspberry disconnected.
1538310520: New connection from <IP_ADDRESS> on port 8883.
1538310520: New client connected from <IP_ADDRESS> as mosqpub|25317-raspberry (c1, k60, u'{redacted mysuser}').
1538310520: Client mosqpub|25317-raspberry disconnected.
1538310520: New connection from <IP_ADDRESS> on port 8883.
1538310520: New client connected from <IP_ADDRESS> as mosqsub|25318-raspberry (c1, k60, u'{redacted mysuser}').
1538310520: Client mosqsub|25318-raspberry disconnected.
1538310531: Client  has exceeded timeout, disconnecting.
1538310531: Socket error on client , disconnecting.
1538310561: New connection from <IP_ADDRESS> on port 8883.
1538310561: OpenSSL Error: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol
Switching to MQTT protocol 3.1 instead of 3.1.1 doesn't help.

Ok. I can't get the latest version get to work with MQTT. Tried the configurator in the web-ui, but that kept saying it couldn't connect to MQTT.
I managed to downgrade to 0.78.3 and that works fine with my MQTT setup.
My MQTT configuration is:
mqtt:
broker:
port: 8883
client_id: home-assistant-1
keepalive: 60
username: !secret mqtt_user
password: !secret mqtt_pwd
certificate: /path/to/ca.crt
protocol: 3.1.1
Glad to have it working again with the previous version. Anyone else experiencing this problem?

I dont use any encryption or login/passwd  between homeassistant and my MQTT server, it's all running on my internal network, so no need.  Only use TLS for stuff coming in from outside, like owntracks.

I dont use any encryption or login/passwd between homeassistant and my MQTT server, it's all running on my internal network, so no need. Only use TLS for stuff coming in from outside, like owntracks.

Ok, thanks! So there might be the difference in why it working for you and not for me. But even for running on my home network I's like to apply TLS and username/password. I like to apply defence in depth, even at home :-)

Please try 0.79.2

0.79.2 works like a charm! Thanks!


Revert this shit.. NOW!!!

Revert the probably most hated update evr

Looks like it has no any conflicts? My client crashes tho.

crashes server bruh

Bro

Okay discuss this change in dev channel i disagree with this


Add library carpentry links to confirmation pages

Fixes #1401

Do not merge - this may not be the correct URL.

@maneesha I made you a reviewer, please decide if you give this PR a green light via GitHub review interface.

@libcce and @ErinBecker   can you verify the correct URL for Library Carpentry's website?  Earlier today Erin told me www.librarycarpentry.org is not correct.

@maneesha @ErinBecker the URL is https://librarycarpentry.org/

Yes, verifying this is the correct url:  https://librarycarpentry.org/


Missing property on web page

Go to :
https://mapping-commons.github.io/sssom/
publication_date is referred here:
https://mapping-commons.github.io/sssom/publication_date/
However, the properties is not used by any of the objects described on the page (Mapping, MapppingSet, MappingRegistry, MappingSetReference).

Thank you @jonquet for the report! This will be fixed in #294!


Brig windows can be broken by prisoners themselves

It takes about 20 seconds worth of hitting.
Reported by @"Herbert Falsevor#3037"

On vgstation from what I can tell it pulls a random number from 0-hand max damage (humans being 5) and does that. If it rolls a 0 then it plays a miss sound. We could probably use that + bump up window health to something like 50 instead maybe?

iirc reinforced windows just cannot be attacked by hands on /vg/

even better

closed in favour of #3174


[Bulk] Validation: validation fixes JM 6/10c

Category

[x] Content fix

[ ] New article

fixes 30 issues

What's in this Pull Request?
Adds missing description or fixes duplicate description, adds missing column headers, cleans up tables with unnecessary html.

Docs Build status updates of commit 85a2004:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/propertyoperator-element-propertyrule-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrule-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrule-element-arrayofpropertyrule-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrule-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrulecollection-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrulecollection-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyruleoperator-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyruleoperator-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrules-element-propertyrulecollection-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyvalueattributedefinition-complextype-apphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/propertyvalues-element-propertyrule-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propset-element-crawledpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/providerid-element-source-complextypesps15xsdsearchset1.md
:warning:Warning
View
Details

docs/schema/proxy-element-in-lobsystem-bdcmetadata-schema.md
:warning:Warning
View
Details

docs/schema/qat-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/propertyoperator-element-propertyrule-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrule-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrule-element-arrayofpropertyrule-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrule-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrulecollection-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrulecollection-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyruleoperator-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyruleoperator-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrules-element-propertyrulecollection-complextypesps15xsdsearchset2.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 8: [Warning: yaml-header-syntax-error] While scanning a multi-line double-quoted scalar, found wrong indentation.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

docs/schema/propertyvalueattributedefinition-complextype-apphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyvalues-element-propertyrule-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propset-element-crawledpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/providerid-element-source-complextypesps15xsdsearchset1.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/proxy-element-in-lobsystem-bdcmetadata-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/qat-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b2381a9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/schema/propertyoperator-element-propertyrule-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrule-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrule-element-arrayofpropertyrule-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrule-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrulecollection-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrulecollection-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyruleoperator-complextype-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyruleoperator-element-sps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyrules-element-propertyrulecollection-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propertyvalueattributedefinition-complextype-apphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/propertyvalues-element-propertyrule-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/propset-element-crawledpropertyinfo-complextypesps15xsdsearchset2.md
:warning:Warning
View
Details

docs/schema/providerid-element-source-complextypesps15xsdsearchset1.md
:warning:Warning
View
Details

docs/schema/proxy-element-in-lobsystem-bdcmetadata-schema.md
:warning:Warning
View
Details

docs/schema/qat-element-commanduidefinitiontype-complextypeapphostwebfeatures.md
:warning:Warning
View
Details

docs/schema/propertyoperator-element-propertyrule-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrule-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrule-element-arrayofpropertyrule-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrule-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrulecollection-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrulecollection-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyruleoperator-complextype-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyruleoperator-element-sps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyrules-element-propertyrulecollection-complextypesps15xsdsearchset2.md

Line 1, Column 1: [Warning: title-missing - See documentation] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 2, Column 8: [Warning: yaml-header-syntax-error] While scanning a multi-line double-quoted scalar, found wrong indentation.
Line 1, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

docs/schema/propertyvalueattributedefinition-complextype-apphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propertyvalues-element-propertyrule-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/propset-element-crawledpropertyinfo-complextypesps15xsdsearchset2.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/providerid-element-source-complextypesps15xsdsearchset1.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/proxy-element-in-lobsystem-bdcmetadata-schema.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

docs/schema/qat-element-commanduidefinitiontype-complextypeapphostwebfeatures.md

Line 2, Column 1: [Warning: ms-prod-and-service - See documentation] Only one of the following attributes can exist: 'ms.prod', 'ms.service'. Use ms.prod for on-premise products, or ms.service for cloud services.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix(ci): All mac connectors and Archicad for windows deployment

Fixes CI deploy jobs for mac, which were not uploading due to misconfiguration on the extension and expected file name.
Mac deploys:

The output of our mac installer build would be called rhino-mac.zip, following the slug. The slug has now been changed to be universal (i.e. rhinoorgrasshopper), and the deploy job uses the correct parameters for osandarch`.
Added arch parameter to the deploy-connector-new job
Extension parameter was not being used in all necessary places.
deploy-connectors job no longer uploads to the new manager. Instead, it's just used as a buffer step to wait for all build jobs to be completed before proceeding to deployment.
Some changes were made on the Speckle.Manager.Feed CLI so that the job would fail if the upload is not successful.

Python CircleCI config generator script:
Since the slug no longer contains -mac suffix, we now use the name of the job if it exists to figure out if it's a mac build or not.
Archicad windows installer:
While fixing this we found out that the Archicad connector was not properly configured:

Added MSBuild nuget to ConnectorArchicad.csproj
Added Properties/AssemblyInfo.cs
Added  as false.

I'm merging this in as it has no changes in connector code, and the CI runs as expected


Add package-lock.json

When using npm 5 to build a package-lock.json file is created with the following message:

npm notice created a lockfile as package-lock.json. You should commit this file

Looks good to me. @simonbrunel ?

If I understand correctly, the package-lock.json only makes sense if:

Travis is setup to build on Node.js 8 / npm 5 (not sure if it's supported yet),
all contributors switch their environment to Node.js 8 (6.11.0 LTS is currently recommended),
package-lock.json is not updated in every PR (what npm commands update this file?)

If we can't get Travis to use this package-lock.json file, then I would not add this file to the repository  because builds will not reflect the expected dependencies. And since most of the dependencies are dev, does it make really sense to lock these deps? I would rather use pinned versions for the 2 non dev dependencies we have (moment and chartjs-color) and git ignore this package-lock.json.
Don't you think that this file will finally generate more noise and work than benefits?

package-lock.json doesn't require a certain version of Node. Only of npm
I use node 6 to build locally, which is the latest LTS as you've pointed out. I've sent a separate PR to update Travis to use node 6 instead of node 5
Travis uses npm 3 by default regardless of node version, so you're right that it's ignoring this file at the moment. For people who use npm 5 they're going to be continually bugged to check in this file. So it seems like we should either ask Travis to use npm 5 or maybe add this file to .gitignore?

That's exactly what I suggested: Travis upgrade or .gitignore this file! But I'm still thinking it will bring more noise than benefits, so my personal choice would be to .gitignore it.
I suggested Node.js 8 because I think npm 5 comes bundled in that version (at least on Windows).

@etimberg what do you think?

I think it really depends on how often we update it. It's noisy if it's always updating

I believe it will only update upon request or when package.json is updated.
However, I'm going to close this for now because I discovered there's a bug in npm's handling of this file that's a dealbreaker. I may reopen when the bug is fixed


schema merging doesn't work when overwriting with a predicate

Environment
Delta-rs version:
0.17.4
Binding:
Python

Bug
What happened:
I attempted to update a table from a Polars DataFrame with mode="overwrite" and a predicate to use for replacement. The DataFrame had a subset of the columns that are in the table. While the rows matching the predicate are successfully replaced with the new data, the table's schema becomes the schema of the DataFrame, rather than being merged with the existing schema.
What you expected to happen:
The original table schema is preserved.
How to reproduce it:

Create a table with a set of columns
Write to that same table with:

mode="overwrite"
schema_mode="merge"
a replacement predicate provided
a DataFrame containing a subset of the columns in the table

@polivbr please create a reproducible example

Here you go:
import polars as pl
import deltalake as dl

df = pl.DataFrame({'a': [1, 2, 3, 4], 'b': [1, 1, 2, 2], 'c': [10, 11, 12, 13]})

df.write_delta("test_table")

df2 = pl.DataFrame({'a': [100, 200, 300], 'b': [1, 1, 1]})

df2.write_delta(
    "test_table",
    mode="overwrite",
    delta_write_options={
        "predicate": "b = 1",
        "schema_mode": "merge",
        "engine": "rust"
    }
)

table = dl.DeltaTable("test_table")
schema = table.schema()

print(schema)

# OUTPUT:
# Schema([Field(a, PrimitiveType("long"), nullable=True), Field(b, PrimitiveType("long"), nullable=True)])
#
# Note that Field c is absent


Update Lab_16_ConfigureAuthenticationSessionControls.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by ParamRamki on behalf of MOC Labs Review


ZEPPELIN-3661. Remove property zeppelin.interpreters

What is this PR for?
This PR is to remove property zeppelin.interpreters which is not used anymore.
What type of PR is it?
[Refactoring]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-3661

How should this be tested?

CI pass

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Will merge it if no more comments


feat: add gRPC 1.63.0 release

update gRPC with release 1.63.0

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