How to disable button response on second click in Microsoft teams?

Hi Team,
I wanted to know is there any way in teams where we can disable the second button click on a button. I don't want the user to scroll back and click on the button again if they have already clicked it once before.
I have read a article on Suggested actions :
https://docs.microsoft.com/en-us/azure/bot-service/dotnet/bot-builder-dotnet-add-suggested-actions?view=azure-bot-service-3.0
This one works in bot emulator but not in teams.
So what to know if there is any solution to my problem in Microsoft teams

@vishmonne- Suggested actions are not supported in Microsoft Teams. Here is how you could achieve this with Card Updates:

Create the card:

                var Card = new AdaptiveCard(new AdaptiveSchemaVersion("1.0"))
                {
                    Body = new List<AdaptiveElement>()
                    {
                        new AdaptiveTextBlock(){Text="This is a test adaptive card"}
                    },
                    Actions = new List<AdaptiveAction>()
                    {
                        new AdaptiveSubmitAction()
                        {
                           Title="Update Me",
                        }
                    }
                };
                var attachment = new Attachment()
                {
                    ContentType = AdaptiveCard.ContentType,
                    Content = Card
                };
                reply.Attachments.Add(attachment);
                await `connector.Conversations.ReplyToActivityWithRetriesAsync(reply);

Here is the code to update your card on click of a button:

                var reply = Activity.CreateMessageActivity();
                var Card = new AdaptiveCard(new AdaptiveSchemaVersion("1.0"))
                {
                    Body = new List<AdaptiveElement>()
                    {
                       new AdaptiveTextBlock(){Text="This is a test adaptive card without button"}
                    },
                };
                var attach = new Attachment()
                {
                    ContentType = AdaptiveCard.ContentType,
                    Content = Card
                };
                reply.Attachments.Add(attach);
                await connector.Conversations.UpdateActivityAsync(activity.Conversation.Id, activity.ReplyToId, (Activity)reply);

@vishmonne ,  are you referring to Update method.
I also wanted to know how your solution will fit into following user case where Bot's skill flow is as  follows.
( At 4pm )
User: Tell me available times to meet Bob for today
Bot: Shows Adaptive cards with 4 submit button which are nothing but available times
User: Clicks on one if the submit
bot: Shows some plain text output and drops the invite on Bob's and User's calendar.
( At 5pm )
User just goes to old conversation and click on existing suggested submit where data available data is stale.
are you suggesting to have 'Update' button on the Adaptive card in case User wanted new available times for Bob ?


(misc) Exclude the .git directory when packaging

When building a package for the Puppet Forge, do not include the .git
directory.

thanks!


⚠ TROJAN 🇸🇬 Singapore SGO 1 has degraded performance

In 3000b70, TROJAN 🇸🇬 Singapore SGO 1 (https://sgt-2.opensvr.net/) experienced degraded performance:

HTTP code: 200
Response time: 17108 ms

Resolved: TROJAN 🇸🇬 Singapore SGO 1 performance has improved in d62a4e9.


Debounce?

Is it possible to prevent Measure from firing until you stop resizing the window?
I'm currently using react-measure 1.4

If you are using 1.0 you can pass shouldMeasure={false} and that will prevent it from updating. Curious if there is any reason you are not using 2.0?

But to use shouldMeasure, I'd have to listen to window resize events and then trigger Measure. I was hoping to not have it fire while I was resizing the window - only when I release the mouse. Granted, that's how only a few older browser handle it, thus my request for debounce, to have it fire every few hundred milliseconds or so.
I found pre 2.0 easier to use. I've only needed to measure smaller components inside containers, and the wrapping nature of react-measure < 2.0, without the need for a ref, was more straightforward.

So I have a question: how I can use debounce now?
Like @designbyadrian says:

I was hoping to not have it fire while I was resizing the window - only when I release the mouse.


systemctl start fails causing fail on ansible run

In my manual attempts to deploy rke2, I often would get failure return codes from systemctl start .... Because of the way the restart logic is written the service appears to fail and restart several times during initialization. While that logic is beyond the scope of this project, I wonder if perhaps failures could be ignored during the start tasks in the role(s)?

@jberger Could you elaborate on the conditions required to observe the failure and which type of nodes you're seeing this for? We have tried to work in enough staggering logic where each "start" happens in sequence and the systemd unit then waits until ETCD has joined to return exit 0.

I don't think this is related to staggering. Even when doing the deploy manually (without the ansible stuff) sometimes the initial systemctl start rke2-server.service exits 1. It then continues to retry until it works. Mostly I think this is due to round-robin DNS for the registration url. Anyway, the logic later on in ansible seems to be fine for detecting that the kubelet and etcd come up it just is noise that the start shows as an error.
Anyway, if you need any other details I'm happy to give them. Ubuntu 20.04, rke2 latest. Baremetal servers.

It would be good not to expect systemd here at all.  systemd is 1m+ lines of code, not really fit for purpose on a small lean server that just wants to run rke.  For these and other reasons, Devuan (debian/ubuntu compatible in all other ways) doesn't include it, and instead provides options of sysvinit, runit, etc.

We are unable to replicate any issues with rke2 starting. Feel free to open a new ticket if you're still experiencing issues.


Feature/key provisioning

Key Provisioning Demo (Internally Generated Keys)
Description
Demo to demonstrate how users can generate private keys on device instead of importing into header file. Option to run old demo using #define variable.
Demo located in demos/dev_mode_key_provisioning/src/aws_key_provisioning_demo.c
Script to create CA certificate in tools/create_certs/generate_CA.sh
Script to create device certificate in tools/create_certs/device_cert.sh
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Apart from the memory leak issue and the two tasks that I've deferred (see unresolved above - I've added these tasks to my current sprint at https://sim.amazon.com/issues/TS-8256), I believe I've addressed all comments. Feel free to take a look at my updates when you get a chance. Thank you -- I appreciate it. :)

Closing this PR. Thank you for all your help! We've made another branch "sukhmanm/jitpdemo" that contains the following core files to be picked off of for future use:
tools/create_certs/deviceandCAcerts.sh
tools/create_certs/.gitignore
libraries/3rdparty/mbedtls/include/mbedtls/config.h
demos/dev_mode_key_provisioning/src/aws_key_provisioning_demo.c
demos/include/iot_demo_runner.h
Thanks again! :)


Incompatibility with rehype-slug+rehype-autolink-headings

I am trying to allow a permissive parsing to get a flexible mardown to react rendering with mapping.
I saw in a comment that using rehype-raw was one solution. And it looks good!
I just found an issue tho.
Whenever I use remark/rehype -slug+autolinks (I tried with remark-* initially and when I got the issue, tried with rehype-* versions but no luck) with rehype-raw, I am getting an error.
Here is a minimal snippet that should trigger a similar error I am getting
var unified = require('unified');
var markdown = require('remark-parse');
var remark2rehype = require('remark-rehype');
var slug = require('rehype-slug');
var link = require('rehype-autolink-headings');
var raw = require('rehype-raw');
var stringify = require('rehype-stringify');

const input = `## Test
[link](href)
\`\`\`js
console.log(window)
\`\`\`

<button>Random Html</button>
<Button>Random react like stuff</Button>
`;

unified()
  .use(markdown)
  .use(remark2rehype, {allowDangerousHTML: true})
  .use(slug)
  .use(link)
  .use(raw)
  .use(stringify)
  .processSync(input);

You can test is there http://requirebin.com/?gist=3feede6e8cc19e061589bdc2f6634bef
And here is my version of the error
TypeError: Cannot read property 'length' of undefined

      at all (node_modules/hast-util-raw/index.js:103:23)
      at element (node_modules/hast-util-raw/index.js:120:5)
      at one (node_modules/zwitch/index.js:20:25)
      at all (node_modules/hast-util-raw/index.js:107:7)
      at element (node_modules/hast-util-raw/index.js:120:5)
      at one (node_modules/zwitch/index.js:20:25)
      at all (node_modules/hast-util-raw/index.js:107:7)
      at element (node_modules/hast-util-raw/index.js:120:5)
      at one (node_modules/zwitch/index.js:20:25)
      at all (node_modules/hast-util-raw/index.js:107:7)
      at root (node_modules/hast-util-raw/index.js:112:5)
      at one (node_modules/zwitch/index.js:20:25)
      at fragment (node_modules/hast-util-raw/index.js:85:5)
      at wrap (node_modules/hast-util-raw/index.js:41:43)
      at wrapped (node_modules/trough/index.js:93:19)
      at next (node_modules/trough/index.js:56:24)
      ...

Not sure if it's directly a rehype-raw error but I don't have it until I use this module, that's why I opened an issue here :)

Sorry to be annoying @wooorm, but do you have any clue about where should I look to fix this bug?

Sorry for the slow reply! I’m super busy making a syllabus for a class that’s starting soon.
This seems to work, any reason why you’re not using it?
var unified = require('unified');
var markdown = require('remark-parse');
var remark2rehype = require('remark-rehype');
var slug = require('rehype-slug');
var link = require('rehype-autolink-headings');
var raw = require('rehype-raw');
var stringify = require('rehype-stringify');

const input = `## Test
[link](href)
\`\`\`js
console.log(window)
\`\`\`

<button>Random Html</button>
<Button>Random react like stuff</Button>
`;

unified()
  .use(markdown)
  .use(remark2rehype, {allowDangerousHTML: true})
+ .use(raw)
  .use(slug)
  .use(link)
- .use(raw)
  .use(stringify)
  .processSync(input);

The problem has two sides btw:

rehype-autolink-headings creates invalid elements (those without children)
hast-util-raw cannot deal with invalid elements (those without children)

Yeah I saw that with your github activity. Hope I didn't bother you too much!
For your response... Wow, that's weird (UX speaking). Anyway, it's working indeed. Feel free to close if you feel this issue is not relevant then.
My knowledge of unified and friends is limited (I am kind of "mind blow" of the work you did to be honest).
Thanks for you previous time!

Oh I see. Glad you find the origins of the problem. Should I open issues over there?

Yeah I saw that with your github activity. Hope I didn't bother you too much!
For your response... Wow, that's weird (UX speaking). Anyway, it's working indeed. Feel free to close if you feel this issue is not relevant then.

...and...

Oh I see. Glad you find the origins of the problem. Should I open issues over there?

No problem, I’ll fix them there and close this issue when done! I’d like to create more starter issues, but as you’ve been waiting for a week and I don’t have a lot of time mentoring people into the ecosystem right now I’ll just do it myself now.

My knowledge of unified and friends is limited (I am kind of "mind blow" of the work you did to be honest).

Thank you! I like the code and where it’s going, but there’s a lot of stuff and thoughts that are only in my head and not in docs. If you have suggestions for documentation, please let me know by creating an issue, pinging me, or chatting in Gitter. I’d love to get better docs!


iiif manifests served from iiif.wellcomecollection.org

What
Relates to #6373. When iiif manifests are being served from iiif.wellcomecollection.org we are seeing a few issues on the /works and /items pages.

[x] 1. where items are 'open with advisory' / 'restricted' only a blank page is showing
[x] 2. work pages with videos that are open with advisory , no longer display the message and clickthrough (likely related to the issue above)
[x] 3. search functionality does not work correctly, wrong pages highlight and links from the results don't work
[ ] 4. where items have multiple volumes the ability to navigate them is missing
[ ] 5. Items with restricted images don't show the restricted text or symbol

is a bug for Digirati to fix
https://wellcome.slack.com/archives/CBT40CMKQ/p1619106343467900?thread_ts=1619007552.436700&cid=CBT40CMKQ

(see https://github.com/wellcomecollection/platform/issues/5146 mentioned above for DDS-side fixes)


Improve RegisterPersistentWorker by bulk persistence to reduce cluster blocking

Please answer these questions before submitting pull request

Why submit this pull request?
[ ] Bug fix
[ ] New feature provided
[x] Improve performance

New feature or improvement
We found that when skywalking block in RegisterPersistentWorker, the grpc threads will be blocked, and then the entire cluster will not accept requests.
Here are some fixes:

Added LRU cache to reduce query quantity
Update and insert are aggregated and updated with bulk

Could you indicate what is the difference between your LRU and existing Map.
Such as following, this should have guaranteed there is no duplicated.
    private void onWork(RegisterSource registerSource) {
        if (!sources.containsKey(registerSource)) {
            sources.put(registerSource, registerSource);
        } else {
            sources.get(registerSource).combine(registerSource);
        }

Could you indicate what is the difference between your LRU and existing Map.
Such as following, this should have guaranteed there is no duplicated.
    private void onWork(RegisterSource registerSource) {
        if (!sources.containsKey(registerSource)) {
            sources.put(registerSource, registerSource);
        } else {
            sources.get(registerSource).combine(registerSource);
        }

This Map is used to combine the registration information of this batch.
In this improvement, LRU can be access across batches. It is used to cache the registration information to reduce access to data sources.

@lt964709769  LRU could cause dirty read. Because the oap node doing register could change because cluster size change in some case.

@peng-yongsheng I think you need to review this. RegisterDAO interface even is being changed in this PR. I think we need to be careful about this change.

@lt964709769 Please put the test report before and after modification in this PR. Is this the real problem? How many inventories need to register in 20ms or end of the datacarrier batch?
sources.size() > 1000 || registerSource.getEndOfBatchContext().isEndOfBatch();

@lt964709769  If you say, the heartbeat of the inventory update causes the gRPC block, I think its the real problem. Inventory register just occurs at the moment of the new application started and all the applications keep beating all the time.

@peng-yongsheng Yes,The heartbeat is the main problem. Currently, there are 96 updates of service_inventory, 399 updates of service_instance_inventory, 93 updates of endpoint_inventory, and 17 updates of network_address_inventory every 3 seconds in our production environment. The 3 seconds param can be change to 1 min may alleviate the problem,but our system may scale to 10 times larger. This is why we do the optimization.

Yes,The heartbeat is the main problem. Currently, there are 96 updates of service_inventory, 399 updates of service_instance_inventory, 93 updates of endpoint_inventory, and 17 updates of network_address_inventory every 3 seconds in our production environment. The 3 seconds param can be change to 1 min may alleviate the problem,but our system may scale to 10 times larger. This is why we do the optimization.
Before the use of bulk, the online registration service was often blocked, which eventually led to the collapse of the whole cluster. After the use of bulk, the registration service ran stably.

The heartbeats of 400 instances look like not large scale, but it depends on the ElasticSearch performance.

@peng-yongsheng Yes,The heartbeat is the main problem. Currently, there are 96 updates of service_inventory, 399 updates of service_instance_inventory, 93 updates of endpoint_inventory, and 17 updates of network_address_inventory every 3 seconds in our production environment. The 3 seconds param can be change to 1 min may alleviate the problem,but our system may scale to 10 times larger. This is why we do the optimization.
Before the use of bulk, the online registration service was often blocked, which eventually led to the collapse of the whole cluster. After the use of bulk, the registration service ran stably.

Extending the interval between heartbeats is the best solution. The register is a core competence, I am not very sure about the bulk. Maybe it is no problem, but I don't think we have the necessary to risk fixing this because it's not the main problem.

All right. What is the role of the heartbeat in skywalking?

All right. What is the role of the heartbeat in skywalking?

Keep services shown in the UI.


Backup file

I think developer should create backup file after opening an existing project.

What developer? What project?


For Calico utilizing etcd as its backend storage, implementation supports P2P (Peer-to-Peer) mode.

What would you like to be added:
For the P2P mode ClusterLink, implementation supports cross-cluster network connectivity for Calico plugin using etcd as its backend storage.
Why is this needed:
Currently, Kosmos utilizes ClusterLink to implement cross-cluster network connectivity. ClusterLink currently supports two modes: gateway mode and P2P mode. Gateway mode selects one node in the cluster to act as the gateway for the tunnel network, while P2P mode is a direct node-to-node communication method. When Calico's backend storage is etcd, the P2P mode is currently not supported. The reason for this is because we need to investigate how to retrieve blockaffinity information from the etcd backend storage. Meanwhile, in gateway mode, we only need to obtain ippools information.

/help-wanted


Props of type any becomes unknown in template

See screenshot.
In script-setup I define a prop of type any but inside the template it is considered as unknown

This is DefineComponent types problem, you can see
const Foo = defineComponent({
	props: { foo: Object as PropType<any> }
});
(new Foo()).foo; // <-- unknown


Structure with some S-groups cannot be opened

Steps to Reproduce

Go to 'https://lifescience.opensource.epam.com/ketcher/demo/ketcher_2_3_remote.html'

Click on 'Open...', 'Open From File'

Select attached
UnsupportedSGroup.mol.txt
and click Ok

See error
Error: Unsupported S-group type

Expected behavior
Support all SGroups described https://discover.3ds.com/sites/default/files/2020-08/biovia_ctfileformats_2020.pdf
or import structure without unsupported SGroup
Actual behavior
We cannot open structure at all
Screenshots

Desktop (please complete the following information):

OS: [Windows]
Browser [chrome]

Hi, @troits!
We are implementing a temporary solution that will warn and allow the user to choose whether he wants to import the structure without rendering unsupported s-group or not. Also, we are researching our services to work out a further solution for the implementation of unsupported s-groups.
Thank you for using our product!


Kernel 4.19 support

Is it possible to get a galcore.ko version compiled to work with  kernel 4.19?

just to be clear I mean support for vermagic:   4.19.111  aarch64, as modinfo * in npu_ko directory shows that support for 4.19 is only avaliable for archv7 puma

filename:
/external/rknpu/drivers/npu_ko/galcore_fedora.ko

alias:
of:NTCrockchip,npu*

vermagic:
4.4.194 SMP preempt mod_unload aarch64

filename:
/external/rknpu/drivers/npu_ko/galcore.ko

alias:
of:NTCrockchip,npu*

vermagic:
4.4.194 SMP preempt mod_unload aarch64

filename:
/external/rknpu/drivers/npu_ko/galcore_puma.ko

alias:
of:NTCrockchip,npuC*

alias:
of:NTCrockchip,npu

vermagic:
4.19.111 SMP preempt mod_unload ARMv7 p2v8

filename:
/external/rknpu/drivers/npu_ko/galcore_puma_tb.ko

name:
galcore

vermagic:
4.19.111 SMP preempt mod_unload ARMv7 p2v8

filename:
/external/rknpu/drivers/npu_ko/galcore_rk1806.ko

alias:
of:NTCrockchip,npu*

vermagic:
4.4.194 SMP preempt mod_unload aarch64

filename:
/external/rknpu/drivers/npu_ko/galcore_rk3399pro-npu.ko

alias:
of:NTCrockchip,npu*

vermagic:
4.4.194 SMP preempt mod_unload aarch64

filename:
/external/rknpu/drivers/npu_ko/galcore_rk3399pro-npu-pcie.ko

alias:
of:NTCrockchip,npu*

vermagic:
4.4.194 SMP preempt mod_unload aarch64


is the def of male germ cell correct?

male germ cell: germ cell and (capable of some spermatogenesis). Should this be capable of part of some spermatogenesis. The individual precursors like spermatogonium are not entirely capable of carrying out the process.

@dosumis @shawntanzk could you please confirm the correct object property to use for this case? Both these guidelines say "capable of some":
https://obophenotype.github.io/cell-ontology/patterns/cellCapableOfBiologicalProcess/
https://github.com/obophenotype/cell-ontology/blob/draft_relations_doc/documentation/relations_guide.md

@shawntanzk yeah, that's partly why I'm confused. The broad parent term could be capable of the whole process because the sum of its children would be?
Let's tag @ukemi who raised the ticket (hi David!).

Hi Paola!
Old ticket. I think the reason I raised the issue was two-fold. First, does it really mean the sum of all of the subclasses or does it mean any instance of the class is capable of the whole process? If it is the latter, then no one individual of the subtype can carry out the process by itself.  This assumes that as we go through successive stages of spermatogenesis cells divide and change identity, suggested by the children of male germ cell. I also had the concern that if I recall correctly in some organisms spermatogenesis also requires Sertoli cells to contribute to the process. If that is the case, then the definition wouldn't be necessary and sufficient either way. Does this make sense? I don't think spermatogenesis is just the male germ cell(s) going through the developmental process but the process itself, which requires more.

Oh sorry, should have probably checked CL before responding >.< didn't realise spermatogonium was a subclass of male germ cell. From the definition of spermatid,spermatocyte, and spermatogonium, I think the problem is that they are wrongly placed as a subclass of male germ cell - those cells are not male germ cells but rather develops from male germ cells. I think we should instead categorise them as precursor cells (that's the right superclass right?), and have a develop from some male germ cell axiom on them instead

Thanks @ukemi, sorry for confusion, been a long day and my brains not quite on it today >.<

does it really mean the sum of all of the subclasses or does it mean any instance of the class is capable of the whole process?

I think because all subclasses inherit the axiom, it means means any instance of the class is capable of the whole process

if I recall correctly in some organisms spermatogenesis also requires Sertoli cells to contribute to the process

If this is true and is in the GO process, then I think you are right that it should instead be capable of part of.
Overall I think you are right that it should be changed. I don't think it should be an equivalent class though for the above reason - esp if something like Sertoli cell is involved.

Yeah, it gets to the murky subject of process boundaries, but I think that the things that the Sertoli cells do would be considered part of the process of spermatogenesis. PMID:29462262

@ukemi @shawntanzk @dosumis
Thank you for confirming. I edited 'male germ cell' as follows:

added PMID:29462262
changed def from "Male germ cell is a germ cell that supports male gamete production." to "A germ cell that supports male gamete production. In some species, non-germ cells known as Sertoli cells also play a role in spermatogenesis."
replaced the equivalence with subclasses 'germ cell' + 'capable of part of' some spermatogenesis
added a seeAlso pointing to this ticket.

Closing now, but feel free to reopen if you have any concern.


Use yail

Replaces some utility functions in nanshe.util.iter with functions from yail.

There's certainly room to continue down this path. However, this is more than sufficient for our purposes ATM.


Use parameter for the PassHostHeader optSetter

This change is to ensure the parameter passed into PassHostHeader is what is used to set the behavior.
This is to ensure explicit enablement/disablement work as expected, and f.passHost isn't set to true asymptotically.

looks good!


fix github.Auth() in README.md

fix github.Auth() in GH part of the README.md

@signifox thanks for the PR, could you please signoff your commit! :)

:+1:

thanks @signifox !

:+1:


Sanitize documentation for G2Diagnostic to remove examples and mark methods as internal

Too many G2Diagnostic examples and the documentation exposes G2Diagnostic functions that should be considered unsupported/experimental/internal.
Get with @antaenc to determine which G2Diagnostic functions are visible in G2Command.

No longer needed


[nRF Platform Example] Bring up CHIP Stack - Support Input Button

Problem
<what's wrong or missing, please include any applicable:

expected behavior
actual behavior
steps to reproduce
system configuration
screenshots, images, logs, etc.

Proposed Solution
<suggested fix, suggested enhancement>

Already done.


Added Olmec details and timings

I'm pretty sure some of this doesn't work when there's multiple olmecs (mods can do that) but we can fix it later...


Hard to see the date and Link's mosaic subject and

With mosaic theme, date and Link the same theme dark and difficult to see.
These strings could change into something bright?

I've just updated some stylesheets and I will release an app update today or tomorrow. After you update, please re-open the issue if the text is still hard to see.

Determine which is correct.
Thank you for your support!


Database event store

Notice I removing FlatFile as a viable option for event store. Only memory event store and database event store is considered stable.


Messed up parameters of event in CU "Transfer Extended Text"

Hi,
I found a small error in an event in the codeunit "Transfer Extended Text", I guess the prameter was messed up here:
Event:
[IntegrationEvent(false, false)]
local procedure OnBeforeToServiceLineInsert(var **ToServLine**: Record "Service Line"; **ServLine**: Record "Service Line"; TempExtTextLine: Record "Extended Text Line" temporary; var NextLineNo: Integer; LineSpacing: Integer)

Code in function InsertServExtText:
...
if TempExtTextLine.Find('-') then begin
            repeat
                ToServiceLine.Init();
                ToServiceLine."Document Type" := ServiceLine."Document Type";
                ToServiceLine."Document No." := ServiceLine."Document No.";
                ToServiceLine."Service Item Line No." := ServiceLine."Service Item Line No.";
                ToServiceLine."Line No." := NextLineNo;
                NextLineNo := NextLineNo + LineSpacing;
                ToServiceLine.Description := TempExtTextLine.Text;
                ToServiceLine."Attached to Line No." := ServiceLine."Line No.";
                ToServiceLine."Service Item No." := ServiceLine."Service Item No.";
                OnBeforeToServiceLineInsert(**ServiceLine**, **ToServiceLine**, TempExtTextLine, NextLineNo, LineSpacing);
                ToServiceLine.Insert(true);
            until TempExtTextLine.Next() = 0;
            MakeUpdateRequired := true;
        end;
...

I was a bit confused when subscribing the event :)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Question: browser-fs IRC?

I'm really excited for the new version of browser-fs that's coming out. Is there any IRC chats (discord/slack etc) for this project?
I'm willing to create a Discord server if there's an appetite for it

I don't believe there is a discord server or slack project for browserfs. I would be willing to create one after I finish some of the more pressing issues.

I can offer myself to make a Discord server for it -- making you and whoever else you specify an admin/team member.
If you want to create it, it's no big deal -- I'm just trying to help out :)

@knackstedt,
I've made a discord server for BrowserFS. You can join here: https://discord.gg/CxYFAfsV5X


[proj] Update to 9.2

[x] Changes comply with the maintainer guide
[x] SHA512s are updated for each updated download
[x] The "supports" clause reflects platforms that may be fixed by this new version
[x] Any fixed CI baseline entries are removed from that file.
[x] Any patches that are no longer applied are deleted from the port's directory.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

Thanks for beating me in adding this upgrade PR 👍

Feature proj[tools] passed with following triplets:
x86-windows
x64-windows
x64-windows-static


BUG> Number only subject name (like "1") breaks app submitter UI

If I have a datasets with just number as subject like "1", it will break the simple application submitter's dataset selecter.

Soichi, could you describe to me exactly what breaks on the UI? Can't seem to replicate this

@soichih

Steven, I tried recreating it but I couldn't. I am closing this ticket until this reoccurs. Sorry about that!


Allow reading parsed params in after-route plug

Given the following Maru 0.12.5 setup in a Phoenix 1.3.0 project:
defmodule MyApp.Web.Router do
  use MyApp.Web, :router

  pipeline :my_api do
  end

  scope "/api" do
    pipe_through :my_api
    forward "/", MyAPI
  end
end

defmodule MyAPI.Authenticate do
  use Maru.Middleware

  def call(conn, _opts) do
    conn.params[:app_id]
    conn
  end
end

defmodule MyAPI do
  use Maru.Router, make_plug: true
  plug MyAPI.Authenticate
  mount MyAPI.Resources
end

defmodule MyAPI.Resources do
  use Maru.Router

  params do
    requires :app_id, type: Integer
    requires :id, type: Integer
  end
  get "/:app_id/resources/:id" do
    ...
  end
end

The middleware is unable to read the :app_id and :id params when a request is made to get "/:app_id/resources/:id". My expectation is that because plug MyAPI.Authenticate is not defined in a before block, the plug will run after routing the request, which leads me to think I should be able to read the params after they are parsed, but before the get block is called.
How can I read the endpoint params in a plug invoked before the endpoint code?

Hi @aiwilliams
I think it's really hard to get params within the middleware.
Because the params is per endpoint variable, the params parser won't be run before the request reach the endpoint logic.
I'm sorry I think we have to match the conn.path_info to get :app_id and :id manually.

Thank you for your reply. I did use the path info because it was the only approach I could see as well.


Propagate list of changed files through PPS DAG

Background
Right now, PPS jobs avoid the cost of reprocessing datums by this mechanism:

Each worker claims some subset of the job's datums
The worker hashes each datum and checks if the hash is present in the tagged object store
If so, the worker claims a new subset of datums

If almost all of a job's datums have already been processed, each worker still has to claim every datum in order to check that it's been processed, which may carry significant overhead.
We've discussed changing PPS so that we generate and propagate the set of changed files (or a superset of the list of changed files), and only allow workers to claim datums containing those.
Design
This section documents how the change would work at a high level.
Every time we finish a commit, we can generate an approximate list of changed files:

Input commits: we have a list of file modifications in etcd. When applying those modifications to the parent tree of a new input commit, we could also record the name of every modified file and directory. That would form the list of changed files for input commits
Output commits: generating the list of changed files for output commits is somewhat complex. Here I'll describe the most general case, which can be extrapolated to other cases:

(I0 and I1 are input commits. O0 and O1 are output commits. J0 and J1 are jobs)
When a file F is in I1's list of changed files, then J1 needs to:

Determine if F is in I0
Find all datums df1, ... , dfn containing F (which may be many e.g. for cross inputs) and retrieve the output trees for those datums
Every file present in some output_treeJ0(dfi) is in the delta list for O1
Every dfi must be processed by J1 to produce output_treeJ1(dfi). Every file present in one of these output trees is also in the delta list for O1
To actually generate O1, every output_treeJ0(dfi) must be removed from O0 and output_treeJ1(dfi) should be merged in its place

Note that to do this, we need a way to remove datum hash trees from the result hash tree

To illustrate, the set of changed files from 3) and 4) are the files circled in green:

Hurdles
As hinted above, there's no easy way, in Pachyderm's current model, to "unmerge" a datum's output from a job's output tree. I don't think this operation would be as simple as finding the first occurance of the first object of every file in the old datum's tree, as objects could repeat (e.g., in word count, the output tree of the map job is the object containing 1, repeated once for every occurance of a word). If we can figure out a way to do that though, then that would unblock this optimization, at least conceptually

This issue is documentary, we're not currently planning to implement this, so I'm marking it closed

I didn't initially think this design could be implemented. Specifically, I thought that propagating missing files through the dag via deltas wouldn't work—in pipelines, a file may be "deleted" not because any delete command was issued, but simply because no datum output it. However, the files present in a job's output commit are the union of the files present in the datum output commits, so the only way for a file to be deleted in an output commit is if its input datum was removed in the job's input commit. By removing files' old output trees, we handle the case where a file is removed because its input datum was removed

This is definitely an optimization we want to make and I think we're in a good place to do it in the near future. I have a slightly different design in mind. I don't think we need to store a list of changed files, we can just get that by using the existing DiffFile API call, this solves the deleted file problem that you mention above, allows us to treat all commits (output and input) the same, and saves us having to store additional information. It does have a cost in that it requires reading 2 trees instead of 1, but that's a much smaller performance issue than the fact that we need to send an object store request per skipped datum. Especially considering that the parent's tree should be cached since it was recently processed. This is also strikes me as a bit more stable, for example if a commit gets skipped (i.e. if a Pipeline was stopped), or if its parent failed to process we can just diff with the parent's parent. Granted we could also merge the list of changed files, but now we're reading out potentially a large number of trees rather than just one.
The second issue that needs to be taken into account here is that jobs may fail, which means that just because a datum isn't new it may not have been processed. This seems fairly easy to solve, because we can just find the most recent job that did succeed and use the input to that job as the old argument to DiffFile.

I certainly agree that getting that full list once seem like it should be (significantly) faster than checking each of those 12 billion files one-by-one in the object store. When i brought this up with @msteffen what i was trying to get at was how it might be possible to make job overhead scale relative to the number of files changed in a commit, rather than the total number contained. it seems like the difference you're talking about isn't so much 1-vs-2 trees, but the cost of downloading/processing of a potential "diff" tree (containing the often-relatively-small number of files that have been added) vs the tree(s) containing the full list of 12-billion (or whatever) files. I'd imagine that computing the diff to find that only one of the 12 billion files changed must still have pretty significant overhead, no?
From what Matt said/wrote here, it sounds like the tricky part seems to be modifying a parent tree to remove the old datums' output before adding in the new datums' output to generate the new child tree. Am I understanding correctly that this is basically because we don't have a mapping from (chunks of) output files back to the datums that created them?

@gabrielgrant you're really talking about 2 optimizations here:

using diffs to make processing more efficient
making diffs more efficient to compute

The second optimization only makes sense after we've done the first one, no one really cares about the performance of DiffFile right now, partly because it's already pretty good, partly because it's not on the critical path for anyone. Just making the first optimization and leaving DiffFile as is will have a huge impact on the performance of a ton of workloads (the majority of Pachyderm workloads I think). After that, DiffFile will be on the critical path for important parts of the system and we'll be able to benchmark it and decide then how we want to improve it. But I think the answer is likely going to be a secondary index of some sort that tells you which parts of the tree are new.

Talked more with @msteffen about how removing a datum's output tree from a merged commit tree could work. At the moment we store each datum's output tree, so from that we can know which files in the commit tree will need objects removed. In most cases we can just remove the datum's contributed object, but in some cases a file may have the same object multiple times (if multiple datums output the same data to the same file). In these cases, we don't know which instance of the object came from which output tree. A few options to deal with this:

store the originating datum's ID along with the object pointer in the file
consistently order the objects in a file (based on, say, a lexicographic ordering of originating datums' IDs)
just remove an arbitrary instance of the object

My inclination is that 3. is valid, since we don't guarantee object order in the first place. @msteffen expressed concern that, although the absolute ordering of objects in a file isn't guaranteed, with our current implementation the ordering of objects across different files will be "consistent": ie. if an object from datum A comes before an object from datum B in one file, we know it's objects will come before those of datum B in all files. Removing objects in an arbitrary order breaks that "consistency":
Do we consider that "defined behavior"? Or just a consequence of our current implementation that people shouldn't be depending on? (TBH i have trouble coming up with why people would be depending on that, but that could just be for lack of imagination)

@gabrielgrant this all seems accurate to me, a few things to add though. First, it's important that we be explicit about exactly which cases we're optimizing. The case that these optimizations are most relevant to are the append only cases. Those are the most common workloads, and they are sinfully slow. Once we start talking about workloads with deletes (or overwrites) the benefits get a lot less clear, it's still a big win if people are frequently deleting a small number of keys, but I haven't seen that very much. More what I've seen is deletes are a rare occurrence, used when data was mistakenly committed, in which case it might not be a big deal if, in those rare occurrences you have to merge from scratch. Or, deletes happen constantly because they're overwriting the same few values, in which case these optimizations won't save you much over remerging everything from scratch.
All that being said I think this is a very doable optimization, the solution that makes the most sense to me is 1), that way we can just zip through the objects and remove the ones we don't want. 2) is actually something I've wanted to do for a while and just haven't gotten to yet, there's a bunch of nice things you can do with it: for example if you have timeseries data where the filenames are timestamps and you want to extract a certain type of event to a file called event then when the job finishes event will contain the relevant events ordered by timestamp, despite the fact that the timestamp isn't explicitly recorded anywhere in the file. However I don't think this would quite solve of problem of knowing which object to remove, since you'd need to find all the other datums that contributed to this output file, which would either require a linear scan, or would require being able to index from output files to input datums, at which point you might as well do 1) since it takes the same amount of space. 3) won't work if we want to care about order at some point in the future, which I think we do.

@msteffen was concerned about the added overhead of storing an extra datum ID with every object reference (perhaps especially so if this info is getting in-lined into the commit tree, which IIUC is happening with the current optimization pass?), but a nice side benefit of storing that info is that it makes it easy to achieve #1914


Juliaup installed in .julia/juliaup despite asking to installing it in a different directory

During the installation I chose to install juliaup in a directory different from .julia/juliaup and yet it is installed in .julia/juliaup which is not what I wanted nor what I asked and makes it impossible having two separate installations on the same filesystem.

Also, doing juliaup update from one installation overwrites the other one, making it unusable.  This is particularly unusable and unintuitive, since I specifically asked for a different directory.
For those reading along, this is related to https://github.com/JuliaLang/juliaup/issues/397#issuecomment-1244376331

There are two locations in play here: the location where Juliaup itself is installed, and the Julia depot where Juliaup installs Julia versions. If you specify your own location during setup that only affects the former, not the latter. The latter is controlled by the JULIA_DEPOT_PATH env variable.
If you install two versions of Juliaup (which is probably not a good idea in general), then each will store things in the same Julia depot, unless you launch with a custom JULIA_DEPOT_PATH.
So, at the moment I'd say this is all by design. We probably should add more documentation to this and also maybe try to make this distinction clear in the installer, though.

There are two locations in play here: the location where Juliaup itself is installed, and the Julia depot where Juliaup installs Julia versions. If you specify your own location during setup that only affects the former, not the latter. The latter is controlled by the JULIA_DEPOT_PATH env variable.

Why they are different?  I share the same (already custom) depot for two different installations of julia of two different architectures, and this design breaks my setup.

If you install two versions of Juliaup (which is probably not a good idea in general), then each will store things in the same Julia depot, unless you launch with a custom JULIA_DEPOT_PATH.

Why it's not a good idea?  Why would I want to duplicate registries, and source packages?  Compile cache is different because the path of the julia is different.  You're already taking advantage of this in julaup by using different versions of julia with the same depot, if you say sharing the depot is a bad idea the whole juliaup setup is a bad idea.  I've been using this setup for years.  That's also the typical setup of most users on an M1/M2 MacBook who use native and Rosetta builds of Julia, with or without juliaup.

I think I very generally do not understand what you are trying to do :) Can you explain a bit why you would want to install two versions of Juliaup on your system?
Juliaup itself (and I'm specifically referring to the julialauncher and juliaup binaries here) can be installed in many different ways. One is the standalone installer via the shell script, but on Windows for example it is installed by the Windows Store, or one can use brew, or hopefully eventually we can also get it say into the default distribution mechanism for Ubuntu etc.
And Juliaup then installs Julia versions into the currently active Julia depot, in the same way that Julia installs packages and artifacts etc. into the active Julia depot.

I think I very generally do not understand what you are trying to do :) Can you explain a bit why you would want to install two versions of Juliaup on your system?

Since I can't have a single installation of juliaup to manage two different architectures, I have to use separate installations of juliaup, which I had already explained in https://github.com/JuliaLang/juliaup/issues/397#issuecomment-1244376331.  I think having two separate installations of juliaup is reasonable (but the error message reported in #397 should be improved, it's rather confusing), but it's apparently impossible if one wants to use the same depot.

One possibility would be to always install Juliaup into ${JULIA_DEPOT_PATH}/juliaup-${arch}.

I'm starting to wonder whether the best option would be to just generally allow installation of all archs always... Sure, in some situations one can then install something that won't run, but maybe that is OK? @giordano I think that would solve your situation, right?
It would still be limited to the same platform, though. I.e. one couldn't install a Julia Windows binary on a Mac system.

I'm starting to wonder whether the best option would be to just generally allow installation of all archs always... Sure, in some situations one can then install something that won't run, but maybe that is OK? @giordano I think that would solve your situation, right?

Not really because without some sort of emulation (which I don't have here) you can't run the launcher for both architectures,only one at the time will work, which isn't much useful. Having the two separate installations is fine with me, if that worked at all, i.e. they should truly be separate and not ending up putting anything in clashing directories.

Chiming in from the perspective on an HPC center: We want to provide Juliaup + global preferences to allow users to deploy and update their own preferred version of Juliaup. I tried:
blaschke@cori01:~/julia> ./juliaup-init --path=$(pwd)/juliaup --no-add-to-path --yes

info: downloading installer
Welcome to Julia!

This will download and install the official Julia Language distribution
and its version manager Juliaup.

Juliaup will be installed into the Juliaup home directory, located at:

  /global/homes/b/blaschke/.julia/juliaup

The julia, juliaup and other commands will be added to
Juliaup's bin directory, located at:

  /global/homes/b/blaschke/.julia/juliaup/bin

This path will then be added to your PATH environment variable by
modifying the profile files located at:

  /global/homes/b/blaschke/.bashrc
  /global/homes/b/blaschke/.profile
  /global/homes/b/blaschke/.bash_profile
  /global/homes/b/blaschke/.zshrc

Julia will look for a new version of Juliaup itself every 1440 minutes when you start julia.

and as you can see the install prompt still shows up. This is a problem, because the Julia modules here are generate using CI, so I need to find a way to install and download Juliaup to a specific location without an interactive prompt. Any ideas? Should I be cloning + building Juliaup instead?

It looks like the --path setting has been deprecated now:
blaschke@cori16:~/julia> curl -fsSL https://install.julialang.org | sh -s -- --path=$(pwd)

info: downloading installer
error: Found argument '--path' which wasn't expected, or isn't valid in this context

Usage: juliainstaller <--default-channel <DEFAULT_CHANNEL>|--juliaup-channel <JULIAUP_CHANNEL>|--yes>

For more information try '--help'

even though it is still listed in the help prompt:
blaschke@cori16:~> curl -fsSL https://install.julialang.org | sh -s -- --help
juliaup-init: the installer for juliaup

USAGE:
    juliaup-init [FLAGS] [OPTIONS]

FLAGS:
    -y, --yes               Disable confirmation prompt.
        --no-add-to-path    Don't add to user PATH environment variable
    -h, --help              Prints help information

OPTIONS:
    -p, --path              Custom install path

The same happens when I try to use --no-add-to-path. At least --yes works. So now I can use juliaup in non-interactive mode. Is there a chance that we can get --path and --no-add-to-path added to juliaup again?

That never worked, that help prompt is more aspirational, the way I'd like it to work :)
But it should be fairly simple now to actually implement that. All that needs to be done is to add these options to https://github.com/JuliaLang/juliaup/blob/fc9a7f7b48e1f03b00f5a24f89e6d34c5ab8ed20/src/bin/juliainstaller.rs#L93 and then use those values in the actual logic.

@davidanthoff I've been meaning to learn Rust -- so I tried adding these myself. I think I have a decent solution and submit a PR today.

@davidanthoff I have just submitted PR #582 -- This add the missing CLI parameters + adds one for the update intervals. @giordano these changes now would let you install juliaup in a specific location and use it to manage julia versions. Eg:
ULIA_DEPOT_PATH=/path/to/global/shared/depot ./juliainstaller --path=/models/bin/path --no-add-to-path --background-selfupdate=0 --startup-selfupdate=0 --yes

I think the command line parameters now work, and we are all good here?


win: add disk read/write count to uv_getrusage

adding some improvements as discussed in https://github.com/libuv/libuv/issues/342
CI: https://ci.nodejs.org/view/libuv/job/libuv-test-commit/114/

LGTM with a style nit. Can you add some "Refs: " metadata when you merge?

Updated changeset, and will do!

Landed https://github.com/libuv/libuv/commit/a7dfee3b02c70ca872c750fc60860d238623be69


Maven support

There are no instructions on what to put in the pom to include this dependency.
Could you please provide some ?

Here is the latest release version:
<dependency>
    <groupId>com.savoirtech.logging</groupId>
    <artifactId>slf4j-json-logger</artifactId>
    <version>2.0.2</version>
</dependency>


Fix multiple autocomplete (on List form)

The autocompleter is able to autocomplete multiple records, if the user enters the right "separator" (like a \n or ,). Had unintentionally blocked this at some point, this resolves it.
However, I'd also like to get this autocompleter to store the array of record ids of the matching records. That takes quite a bit of refactoring of the Stimulus for autocompleters.

coverage: 93.422%. remained the same
when pulling 840a00c2a3d1f51395f2af2f3048bd44ff3c1d43 on multiple-record-autocompleter
into 85ad13355f088ea80a26f58089a4e0a9debfd5d9 on main.

TODO:

[ ] Add autocomplete unit tests for first_matching_record / exact_match
[ ] Add a system test for multiple autocomplete (Name)


versioned std

using current version fails because of a breaking change in std on the deno master branch

fixes #6


pkg/terminal: print DWARF location expression with whatis

Split out of https://github.com/derekparker/delve/pull/958.
Another possibility is to make &x return a string with the location expression of x when it doesn't have a phisical address.
pkg/terminal: print DWARF location expression with whatis

Adds a configuration option (show-location-expr) that when activated
will cause the whatis command to also print the DWARF location
expression for a variable.

@aarzilli can you rebase, and then I will review.

Done.

Overall LGTM -- but we should add this to the default config that gets written out.

Done.


Synthesis failed for AndroidDeviceProvisioning

Hello! Autosynth couldn't regenerate AndroidDeviceProvisioning. :broken_heart:
Here's the output from running synth.py:
.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:12:04.043 [info]  FETCHING: https://androiddeviceprovisioning.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:12:04.172 [info]  FETCHING: https://androiddeviceprovisioning.googleapis.com/$discovery/rest?version=v1

12:12:04.189 [info]  FOUND: https://androiddeviceprovisioning.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200509, new=20200530, generating=true
Creating leading directories
Writing ClaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_device_request.ex.
Writing ClaimDeviceResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_device_response.ex.
Writing ClaimDevicesRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_devices_request.ex.
Writing Company to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/company.ex.
Writing Configuration to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/configuration.ex.
Writing CreateCustomerRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/create_customer_request.ex.
Writing CustomerApplyConfigurationRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_apply_configuration_request.ex.
Writing CustomerListConfigurationsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_configurations_response.ex.
Writing CustomerListCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_customers_response.ex.
Writing CustomerListDevicesResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_devices_response.ex.
Writing CustomerListDpcsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_dpcs_response.ex.
Writing CustomerRemoveConfigurationRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_remove_configuration_request.ex.
Writing CustomerUnclaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_unclaim_device_request.ex.
Writing Device to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device.ex.
Writing DeviceClaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_claim.ex.
Writing DeviceIdentifier to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_identifier.ex.
Writing DeviceMetadata to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_metadata.ex.
Writing DeviceReference to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_reference.ex.
Writing DevicesLongRunningOperationMetadata to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/devices_long_running_operation_metadata.ex.
Writing DevicesLongRunningOperationResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/devices_long_running_operation_response.ex.
Writing Dpc to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/dpc.ex.
Writing Empty to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/empty.ex.
Writing FindDevicesByDeviceIdentifierRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_device_identifier_request.ex.
Writing FindDevicesByDeviceIdentifierResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_device_identifier_response.ex.
Writing FindDevicesByOwnerRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_owner_request.ex.
Writing FindDevicesByOwnerResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_owner_response.ex.
Writing ListCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_customers_response.ex.
Writing ListVendorCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_vendor_customers_response.ex.
Writing ListVendorsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_vendors_response.ex.
Writing Operation to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/operation.ex.
Writing OperationPerDevice to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/operation_per_device.ex.
Writing PartnerClaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/partner_claim.ex.
Writing PartnerUnclaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/partner_unclaim.ex.
Writing PerDeviceStatusInBatch to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/per_device_status_in_batch.ex.
Writing Status to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/status.ex.
Writing UnclaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/unclaim_device_request.ex.
Writing UnclaimDevicesRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/unclaim_devices_request.ex.
Writing UpdateDeviceMetadataInBatchRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_device_metadata_in_batch_request.ex.
Writing UpdateDeviceMetadataRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_device_metadata_request.ex.
Writing UpdateMetadataArguments to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_metadata_arguments.ex.
Writing Customers to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/customers.ex.
Writing Operations to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/operations.ex.
Writing Partners to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/partners.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:12:04.631 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-06 05:12:07,919 synthtool [DEBUG] > Wrote metadata to clients/android_device_provisioning/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/android_device_provisioning/synth.metadata.
2020-06-06 05:12:07,946 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating AndroidDeviceProvisioning. :sob:
Here's the output from running synth.py:
.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:10:45.069 [info]  FETCHING: https://androiddeviceprovisioning.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:10:45.190 [info]  FETCHING: https://androiddeviceprovisioning.googleapis.com/$discovery/rest?version=v1

12:10:45.212 [info]  FOUND: https://androiddeviceprovisioning.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200509, new=20200530, generating=true
Creating leading directories
Writing ClaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_device_request.ex.
Writing ClaimDeviceResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_device_response.ex.
Writing ClaimDevicesRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_devices_request.ex.
Writing Company to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/company.ex.
Writing Configuration to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/configuration.ex.
Writing CreateCustomerRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/create_customer_request.ex.
Writing CustomerApplyConfigurationRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_apply_configuration_request.ex.
Writing CustomerListConfigurationsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_configurations_response.ex.
Writing CustomerListCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_customers_response.ex.
Writing CustomerListDevicesResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_devices_response.ex.
Writing CustomerListDpcsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_dpcs_response.ex.
Writing CustomerRemoveConfigurationRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_remove_configuration_request.ex.
Writing CustomerUnclaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_unclaim_device_request.ex.
Writing Device to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device.ex.
Writing DeviceClaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_claim.ex.
Writing DeviceIdentifier to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_identifier.ex.
Writing DeviceMetadata to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_metadata.ex.
Writing DeviceReference to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_reference.ex.
Writing DevicesLongRunningOperationMetadata to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/devices_long_running_operation_metadata.ex.
Writing DevicesLongRunningOperationResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/devices_long_running_operation_response.ex.
Writing Dpc to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/dpc.ex.
Writing Empty to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/empty.ex.
Writing FindDevicesByDeviceIdentifierRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_device_identifier_request.ex.
Writing FindDevicesByDeviceIdentifierResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_device_identifier_response.ex.
Writing FindDevicesByOwnerRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_owner_request.ex.
Writing FindDevicesByOwnerResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_owner_response.ex.
Writing ListCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_customers_response.ex.
Writing ListVendorCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_vendor_customers_response.ex.
Writing ListVendorsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_vendors_response.ex.
Writing Operation to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/operation.ex.
Writing OperationPerDevice to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/operation_per_device.ex.
Writing PartnerClaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/partner_claim.ex.
Writing PartnerUnclaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/partner_unclaim.ex.
Writing PerDeviceStatusInBatch to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/per_device_status_in_batch.ex.
Writing Status to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/status.ex.
Writing UnclaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/unclaim_device_request.ex.
Writing UnclaimDevicesRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/unclaim_devices_request.ex.
Writing UpdateDeviceMetadataInBatchRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_device_metadata_in_batch_request.ex.
Writing UpdateDeviceMetadataRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_device_metadata_request.ex.
Writing UpdateMetadataArguments to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_metadata_arguments.ex.
Writing Customers to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/customers.ex.
Writing Operations to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/operations.ex.
Writing Partners to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/partners.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:10:45.629 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-07 05:10:48,672 synthtool [DEBUG] > Wrote metadata to clients/android_device_provisioning/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/android_device_provisioning/synth.metadata.
2020-06-07 05:10:48,696 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating AndroidDeviceProvisioning. :sob:
Here's the output from running synth.py:
.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:10:44.298 [info]  FETCHING: https://androiddeviceprovisioning.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:10:44.428 [info]  FETCHING: https://androiddeviceprovisioning.googleapis.com/$discovery/rest?version=v1

12:10:44.448 [info]  FOUND: https://androiddeviceprovisioning.googleapis.com/$discovery/rest?version=v1
Revision check: old=20200509, new=20200530, generating=true
Creating leading directories
Writing ClaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_device_request.ex.
Writing ClaimDeviceResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_device_response.ex.
Writing ClaimDevicesRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/claim_devices_request.ex.
Writing Company to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/company.ex.
Writing Configuration to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/configuration.ex.
Writing CreateCustomerRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/create_customer_request.ex.
Writing CustomerApplyConfigurationRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_apply_configuration_request.ex.
Writing CustomerListConfigurationsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_configurations_response.ex.
Writing CustomerListCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_customers_response.ex.
Writing CustomerListDevicesResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_devices_response.ex.
Writing CustomerListDpcsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_list_dpcs_response.ex.
Writing CustomerRemoveConfigurationRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_remove_configuration_request.ex.
Writing CustomerUnclaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/customer_unclaim_device_request.ex.
Writing Device to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device.ex.
Writing DeviceClaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_claim.ex.
Writing DeviceIdentifier to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_identifier.ex.
Writing DeviceMetadata to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_metadata.ex.
Writing DeviceReference to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/device_reference.ex.
Writing DevicesLongRunningOperationMetadata to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/devices_long_running_operation_metadata.ex.
Writing DevicesLongRunningOperationResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/devices_long_running_operation_response.ex.
Writing Dpc to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/dpc.ex.
Writing Empty to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/empty.ex.
Writing FindDevicesByDeviceIdentifierRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_device_identifier_request.ex.
Writing FindDevicesByDeviceIdentifierResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_device_identifier_response.ex.
Writing FindDevicesByOwnerRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_owner_request.ex.
Writing FindDevicesByOwnerResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/find_devices_by_owner_response.ex.
Writing ListCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_customers_response.ex.
Writing ListVendorCustomersResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_vendor_customers_response.ex.
Writing ListVendorsResponse to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/list_vendors_response.ex.
Writing Operation to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/operation.ex.
Writing OperationPerDevice to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/operation_per_device.ex.
Writing PartnerClaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/partner_claim.ex.
Writing PartnerUnclaim to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/partner_unclaim.ex.
Writing PerDeviceStatusInBatch to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/per_device_status_in_batch.ex.
Writing Status to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/status.ex.
Writing UnclaimDeviceRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/unclaim_device_request.ex.
Writing UnclaimDevicesRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/unclaim_devices_request.ex.
Writing UpdateDeviceMetadataInBatchRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_device_metadata_in_batch_request.ex.
Writing UpdateDeviceMetadataRequest to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_device_metadata_request.ex.
Writing UpdateMetadataArguments to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/model/update_metadata_arguments.ex.
Writing Customers to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/customers.ex.
Writing Operations to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/operations.ex.
Writing Partners to clients/android_device_provisioning/lib/google_api/android_device_provisioning/v1/api/partners.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:10:44.869 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-08 05:10:47,470 synthtool [DEBUG] > Wrote metadata to clients/android_device_provisioning/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/android_device_provisioning/synth.metadata.
2020-06-08 05:10:47,499 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


INFRA-113: Orchard Core fork sync workflow

INFRA-113

We used Git-hg Mirror for this in the end.


send_control: Untangle send-button css.

clean up of send-control / send_button CSS, so changes to button-size won't create layout issues.

@Alex-CodeLab for this PR, is the intent that there should be no visual change after merging it?  Mentioning whether that's the case is helpful for using my time well in reviewing it.

(Did we really have a -7px right and a 7px margin-right cancelling each other out?  Sigh.)

Also, this seems to include the changes from #11614; next time, feel free to just stack additional commits on and existing PR that fix similar issues; we don't need a new PR for each few lines change.

yes, there should be no visual change.

.


Create UIInputData.cs

Welp, there's a first for everything or so they say, so here's me making a PR for CS.
Thanks to @UnknownX7 for the original sig and code that made me want to dig here and @MidoriKami for all the help :)
Let me know what's wrong with the PR (if anything, but surely there will be).
Also, naming stuff was hard, please suggest better ideas.
Note: I didn't build CS, I just used the struct in a plugin to test it, so there might be things that won't work.

Other notes:

I wanted to use VirtualKey directly in the method, but it's in Dalamud so I revert back to int.
The only 2 keys (on my keyboard at least, if anyone feels like trying to check, please lemme know) where the offsets don't match the VirtualKey values are Num lock and Scroll lock. Hence the specific handling.
I could also create a new enum with all the keys if that's preferred, I just thought using (int) VirtualKey was probably the most dev friendly in the end.

Why are the button flags split?

Why are the button flags split?


Wrong file name in SattrackLoader.get_track_for_day()

The file name of the satellite track files stored on https://sattracks.orcestra-campaign.org has changed. In the filename, the valid date is now preceded by a 'V' and the forecast issued date is preceded by an 'F'. This is currently not implemented in the SattrackLoader.get_track_for_day() in https://github.com/orcestra-campaign/pyorcestra/blob/main/orcestra/sat.py#L154.

@d70-t @lkluft Somehow I cannot assign anyone to this issue. Please have a look on it.

Yes, I've seen it 😬


add more scalar stats

total missing
total samples
avg samples per hour
q0.1,q0.2,q0.8,q0.9

https://github.com/IBM/TSML.jl/pull/22


[EventRequest] VendorStatistics.Page.al (page 152 "Vendor Statistics")

Hi MS,
Please help us in migrating our verticalized solution by adding below Event in VendorStatistics.Page.al Page.
Standard Code

Modified Code

Event Signature

Thanks
SUD

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


Expose the tri-state checkbox "indeterminate" state in the semantics data

Right now we treat "indeterminate" and "unchecked" as the same. This works for Android and iOS since their accessibility APIs don't support tristate checkboxes, but hopefully Fuchsia's API will support tristate checkboxes so we should expose the data there at least.

As we expose more information to the semantics layer, we should also consider a strategy to make it hard or impossible to represent mutually exclusive states (Also we're almost out of bits).


Updated master branch alias

Hi there,
This is just a plain simple dump of the master branch alias so people using master because a PR was merged but not yet released can use something like ~1.3, >= 1.3.3 and it will pick up the master branch.

Outdated PR now, so closed. Thanks for your time.


Forward clears

When you forward an email it wipes out the formatting.

@mfoote Unfortunately there's little that can be done about forwarding. Here's a good post from Litmus.
That said, in your issue you mention it clearing <head>. If you have your CSS inlined then this should have minimal effect. What does your original code look like that you're sending? And what client are you testing?


[ansible/artifactory] Fix for #281 restore SELinux context on bin directory on RedHat-like distros

PR Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[X] Title of the PR starts with installer/product name (e.g. [ansible/artifactory])
[X] CHANGELOG.md updated
[ ] Variables and other changes are documented in the README.md

What this PR does / why we need it:
Fixes an SELinux issue on AlmaLinux 8 (and probably Rocky/Oracle/Fedora)
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #281
Special notes for your reviewer:
Check /var/log/messages on AlmaLinux8

@bbaassssiiee can you pls rebase to jp-10.12.3 branch to fix conflicts   so that I can plan to merge to master


Support (Aries RFC 36) issue-credential protocol v1.1

Address https://github.com/hyperledger/aries-cloudagent-python/issues/341
Signed-off-by: sklump<EMAIL_ADDRESS>

It turns out that the v1.1 upgrade was inappropriately handled for this. The version is on the protocol, not on the messages, so what should have happened (and what will be corrected) is that ALL of the messages will have the v1.1 tag on them.
A further complication is that the change that was made to go from v1.0 was to add Indy specific data to the proposal message.  However, we took pains to prevent Indy specific data in the other credential exchange messages -- through the use of attachments.  We need to relook at the change in that light.
More discussion in the community...

What is indy-specific in the proposal message?

That's good about the message types. The RFC needs to be updated.
The Indy-specific fields are these ones:

"schema_issuer_did": "DID of the proposed schema issuer",
"schema_id": "Schema ID string",
"schema_name": "Schema name string",
"schema_version": "Schema version string",
"cred_def_id": "Credential Definition ID string"

I guess the way forward here would be to base64-encode and wrap the five-or-six* criteria into a "filter~attach" attachment.

in or out: issuer_did.
IN:

one place for all filter criteria

not backward-compatible with v1.0
OUT:

backward-compatible with v1.0

need to visit two places to assemble filtration criteria: we're only on v1.1 and it's already got a tumour
An a


Kibana authentication Issues

Hi Team -
By following bleow link & docker-compose instructions we deployed containers and when we hit the url http://localhost:5601/ kibana UI is asking for authentication to get in but it is never accepting the default password which is there in /usr/share/kibana/config/kibana.yml file .
What might be the cause & Is there a way to disable password authentication for kibana UI ?
https://opendistro.github.io/for-elasticsearch-docs/docs/install/docker/

Hi Team - Could some one assist on this ?


Replace web server example static and homepage templates with something more esthetically pleasing and on brand

The static home page in the "simple" examples and the templates in the "basic" and "role" examples of apache and nginx are rather pain and pretty ugly. They should be replaced with something that is more esthetically pleasing though simple and on brand. Something like this one: https://github.com/tima/8ball-service/blob/master/app/templates/8ball.j2

@gdykeman is working on this. He's not a member of this project currently that I can assign it to him.

Closed with commit of 7f30e5f1d and 2952d338.


No known class method for selector 'extraModulesForBridge:'

Description
iOS build is being failed but it successfully runs on iOS simulators.
Also getting another errors
Property 'moduleRegistryAdapter' not found on object of type 'AppDelegate *'
Unknown receiver '_moduleRegistryAdapter'; did you mean 'UMModuleRegistryAdapter'?
React Native version:
System:
    OS: macOS 10.15.4
    CPU: (8) x64 Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz
    Memory: 57.29 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.18.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK: Not Found
  IDEs:
    Android Studio: Not Found
    Xcode: 11.5/11E608c - /usr/bin/xcodebuild
  Languages:
    Java: 14.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Xcode > Product > Build

Expected Results
Expected to build app successfully.
AppDeletage.m
#import "AppDelegate.h"

#import <React/RCTBridge.h>
#import <React/RCTBundleURLProvider.h>
#import <React/RCTRootView.h>

#import <UMCore/UMModuleRegistry.h>
#import <UMReactNativeAdapter/UMNativeModulesProxy.h>
#import <UMReactNativeAdapter/UMModuleRegistryAdapter.h>
#import "RNSplashScreen.h"

#if DEBUG && TARGET_OS_SIMULATOR
#import <FlipperKit/FlipperClient.h>
#import <FlipperKitLayoutPlugin/FlipperKitLayoutPlugin.h>
#import <FlipperKitUserDefaultsPlugin/FKUserDefaultsPlugin.h>
#import <FlipperKitNetworkPlugin/FlipperKitNetworkPlugin.h>
#import <SKIOSNetworkPlugin/SKIOSNetworkAdapter.h>
#import <FlipperKitReactPlugin/FlipperKitReactPlugin.h>
#import <CodePush/CodePush.h>

@interface AppDelegate () <RCTBridgeDelegate>

@property (nonatomic, strong) UMModuleRegistryAdapter *moduleRegistryAdapter;

@end

static void InitializeFlipper(UIApplication *application) {
  FlipperClient *client = [FlipperClient sharedClient];
  SKDescriptorMapper *layoutDescriptorMapper = [[SKDescriptorMapper alloc] initWithDefaults];
  [client addPlugin:[[FlipperKitLayoutPlugin alloc] initWithRootNode:application withDescriptorMapper:layoutDescriptorMapper]];
  [client addPlugin:[[FKUserDefaultsPlugin alloc] initWithSuiteName:nil]];
  [client addPlugin:[FlipperKitReactPlugin new]];
  [client addPlugin:[[FlipperKitNetworkPlugin alloc] initWithNetworkAdapter:[SKIOSNetworkAdapter new]]];
  [client start];
}
#endif

@implementation AppDelegate

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
#if DEBUG
  InitializeFlipper(application);
#endif

  self.moduleRegistryAdapter = [[UMModuleRegistryAdapter alloc] initWithModuleRegistryProvider:[[UMModuleRegistryProvider alloc] init]];

  RCTBridge *bridge = [[RCTBridge alloc] initWithDelegate:self launchOptions:launchOptions];
  RCTRootView *rootView = [[RCTRootView alloc] initWithBridge:bridge
                                                   moduleName:@"getlug"
                                            initialProperties:nil];

  rootView.backgroundColor = [[UIColor alloc] initWithRed:1.0f green:1.0f blue:1.0f alpha:1];

  self.window = [[UIWindow alloc] initWithFrame:[UIScreen mainScreen].bounds];
  UIViewController *rootViewController = [UIViewController new];
  rootViewController.view = rootView;
  self.window.rootViewController = rootViewController;
  [self.window makeKeyAndVisible];
  [RNSplashScreen show];
  [super application:application didFinishLaunchingWithOptions:launchOptions];
  return YES;
}

- (NSURL *)sourceURLForBridge:(RCTBridge *)bridge
{
#if DEBUG
  return [[RCTBundleURLProvider sharedSettings] jsBundleURLForBundleRoot:@"index" fallbackResource:nil];
#else
  return [CodePush bundleURL];
#endif
}

- (NSArray<id<RCTBridgeModule>> *)extraModulesForBridge:(RCTBridge *)bridge
{
    NSArray<id<RCTBridgeModule>> *extraModules = [_moduleRegistryAdapter extraModulesForBridge:bridge];
    // If you'd like to export some custom RCTBridgeModules that are not Expo modules, add them here!
    return extraModules;
}

@end

AppDelegate.h
#import <React/RCTBridgeDelegate.h>
#import <UIKit/UIKit.h>
#import <UMCore/UMAppDelegateWrapper.h>
#import <UMReactNativeAdapter/UMModuleRegistryAdapter.h>

@interface AppDelegate : UMAppDelegateWrapper <UIApplicationDelegate, RCTBridgeDelegate>

@property (nonatomic, strong) UIWindow *window;

@end

Adding #import <UMReactNativeAdapter/UMModuleRegistryAdapter.h> to top of  AppDelegate.h and @property (nonatomic, strong) UMModuleRegistryAdapter *moduleRegistryAdapter; between line @interface AppDelegate : UMAppDelegateWrapper <UIApplicationDelegate, RCTBridgeDelegate> and @end solved issue.

@tsdmrfth your solution led to this:
UMReactNativeAdapter/UMModuleRegistryAdapter.h' file not found

@darmie Were you able to resolve your issue?

I don't remember, I use Flutter now.
On Fri, 12 Mar 2021, 10:21 Ravi Poonia, @.***> wrote:

@darmie https://github.com/darmie Were you able to resolve your issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/29340#issuecomment-797356063,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGPBATWOW2OJHWBG637VGDTDHFHVANCNFSM4OXI4IYQ
.

I was facing the same issue and then I removed the flipper code from AppDelegate.m and it build successfully. Strange...
Was hoping someone could provide some insight on this.

Had the same problem and @tsdmrfth 's solution worked.
RN: 0.63.2
react-native-unimodules: 0.13.3
xcode: 12.5


Show some information to the user while it is processing

Currently the application does not show any indication to the user when it takes long time to to do some job, specially when creating a VC with ZK, which takes several seconds.
Show better information like a GIF, progress bar, or another better indication.

Let me handle this issue!


Razor: Typing directive tokens can occasionally fail to auto-complete

Describe the bug
Racey Bug
To Reproduce
Steps to reproduce the behavior:

Open a Razor file
Type @inject Date
Hit enter to auto-complete DateTime
You see that you just have @inject Date

Note: This bug is racey so it may take a few times for it to happen.
Expected behavior
Auto-completion works as expected and you get @inject DateTime.
Screenshots
Actual:

Expected:

Additional context

This did not happen in dev15
This happens because a completion session starts when we've rendered a marker directive token without a line pragma and then we return our parse results which provide a C# buffer with a line pragma.
The correct fix here is to always generate the line pragma even for marker tokens.

vsts issue: https://devdiv.visualstudio.com/DevDiv/_workitems/edit/738275

https://github.com/aspnet/AspNetCore-Tooling/commit/ca593c80f750495d0b215a7fc5671706747348e0


Add argus admin to email when alert evaluation exceptions happen so w…

…e know what data/transform/time has caused exception

Current coverage is 36.54% (diff: 0.00%)

Merging #193 into develop will decrease coverage by 0.01%

@@            develop       #193   diff @@
==========================================
  Files           259        259
  Lines         14027      14026     -1
  Methods           0          0
  Messages          0          0
  Branches       2348       2348
==========================================
- Hits           5128       5126     -2
- Misses         8185       8186     +1
  Partials        714        714

Powered by Codecov. Last update a8c0759...11ce389