Icons not showing

The icons in the latest update aren't showing.
1.11.0 Build 89

@jacobgonzales20 ok somehig is weird. can you give details: icon pack, location, provider,...

@jacobgonzales20 the bug is fixed and the app is waiting for review!

@jacobgonzales20 , are you talking about hourly icons, like above ?

@Jerome-Herbinet  yes hopefully i fixed all that. are you using icon animations?
Will need to make a new release on android too.
 How can I transmit you the location privately ?

@Jerome-Herbinet Ok you can contact me with dev at akylas dot fr.

@Jerome-Herbinet Ok you can contact me with dev at akylas dot fr.

Done :-)

@Jerome-Herbinet thanks! there is a new release on github if you want to test. Should be fixed

I juste tested this new release and it crashes. Maybe its not directly related to the fix we're talking about in this issue but ... thanks anyway ... I'm just rolling back until you can fix it (take your time, we're on weekend 🙂).

@Jerome-Herbinet I am really sorry. not sure why but I can't reproduce this. will try harder !


Automated cherry pick of #6085

Cherry pick of #6085 on release-5.26.
/cc  @jasonblais

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: ac04f1dc6ef3875d480fe17b35143c705094b537


skeleton variant wave has issue in v6

Search keywords
wave
Latest version

[X] I have tested the latest version v6

@essuraj We are waiting for the patch release to have the fix.
FYI This issue has been reported https://github.com/mui/material-ui/issues/43475

It was fixed in #43474 and will be released in the next version as pointed out above.


Pylint suggested fixes

Specify encoding when opening files. (fix for W1514)
Disable Pylint warning R1732 ("Consider using 'with' for resource-allocating operations (consider-using-with)"). It's a correct suggestion but it's not straightforward how to apply here, if at all possible.

If I understand correctly, it is tempfile causing the pylint call for "with". If in the end we still have to manually delete the directory, what is the benefit of using tempfile? We are already working in a specific directory so the need for uniqueness of the directory name is zero
The disable line in pylintrc is already quite long and it seems to me that we should use "with" when possible. I think it would be better to find a solution which would only affect the file itself rather than all the files of the repo

Fully agree on the length of the Pylint ignore list being too long, I converted the fix to a local ignore for just the instantiation of the temp directory. And it's probably a good idea to even study the global ignore list and shorten it further.
As for using the tempfile, not sure what the best approach here.

Repeat Detector argument "gnm" points to a directory where all the fasta files would be processed. "tempfile.TemporaryDirectory" is used to make sure that only "genome_file" is processed by making a symlink to it from the temporary directory. It might be possible to wrap it around a "with" just to assign it to "gnm" or maybe there is some other alternative to "tempfile".


tests: properly propagate the AZURE_STORAGE_KEY variable

E2E: https://github.com/EnterpriseDB/cloudnative-pg/actions/runs/6769065595


Moved all react code to monorepo package

Here is my take on this idea: https://github.com/boringdesigners/boring-avatars/issues/11#issuecomment-851592480
This is a starting point which could be a draft or a final impl for moving this repository to monorepo structure.

Remove stale label

don't

Hey @quentincaffeino, thanks for the work but we don't have any plans to transform the react library into a monorepo structure, as we will keep it as it is for the moment.


Remove hanging back-quote

Under the "Additional Linux Command-Linux Prerequisites", there was a hanging back-quote in the android home sdk path. This removes the quote.

Author vaage not on autobuild list. Waiting for curator authorization before starting CI build.

Author vaage not on autobuild list. Waiting for curator authorization before starting CI build.


Can't use port.on(readable):read() instead of port.on(data)

SerialPort Version: 5.0.0

NodeJS Version: v6.11.2 LTS

Operating System and Hardware Platform: raspbian jessy lite on RPI 2 B

Have you checked the right version of the api docs?: yes, 5.0.0

Are you having trouble installing and you checked the Installation Special Cases docs? other troubles

Are you using Electron and have you checked the Electron Docs?: not using Electron

Summary of Problem
Until now I used SerialPort to read from a ublox GPS receiver without problems. However, I now notices a weird bug: Randomly, I don't get any data events for 1-3 seconds and then I receive all the missing data at once. In order to fix this, I tried to upgrade to the newer API usage from port.on(data) to port.on(readable)=>read(). Unfortunately, when using the sample code in the Docs (Usage), I don't get any readable events.
Update: I did not wait long enough as I received data within 1 second with port.on(data). Using port.on(readable) takes about 27 seconds until the first call is executed. Any idea why this is the case and if/how I can get a same response time like with port.on(data)?
Update 2, solved: Okay, my mistake: I called port.on(readable), however, with my implementation (see below) I need to call parse.on(readable) an with this I instantly receive data again.
Steps and Code to Reproduce the Issue
Everything works as expected (but I have the "delay bug" described above) with:
port.on('data', function (data) {
      console.log('Data, flowing mode:', data);
    });

When I use the new API usage, no readable events are fired:
port.on('readable', function () {
      console.log('Data:', port.read());
    });

What do I do wrong? I open the port with:
const SerialPort = require('serialport');
  const Readline = SerialPort.parsers.Readline;
  var port = new SerialPort('/dev/ttyACM0', { autoOpen: false, baudRate: 115200 });
  var parser = port.pipe(new Readline());
  port.open(function (err) {...});

The weird bug I am trying to fix when using port.on(data) can be seen here in the debugging output:
    serialport:unixRead waiting for readable because of code: EAGAIN +16ms
    serialport:poller Polling for "readable" +0ms
    serialport:poller received "readable" +173ms
    serialport:bindings read +0ms
    serialport:unixRead Starting read +1ms
    serialport:unixRead Finished read 240 bytes +6ms
    serialport:main binding.read finished +1ms
    serialport:main _read reading +1ms
    serialport:bindings read +1ms
    serialport:unixRead Starting read +0ms
    serialport:unixRead waiting for readable because of code: EAGAIN +7ms
    serialport:poller Polling for "readable" +1ms
  2017-08-10T09:46:01.064Z - info: GPS:    5Hz       ARM: ( 143| 143|   0)Hz     caching:    0Hz     saving:  241Hz     uploaded: 0 batches
    serialport:poller received "readable" +190ms
    serialport:bindings read +1ms
    serialport:unixRead Starting read +0ms
  2017-08-10T09:46:02.071Z - info: GPS:    0Hz       ARM: ( 142| 142|   0)Hz     caching:    0Hz     saving:    0Hz     uploaded: 0 batches
    serialport:unixRead Finished read 1200 bytes +1s !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    serialport:main binding.read finished +1ms
    serialport:main _read reading +7ms
    serialport:bindings read +0ms
    serialport:unixRead Starting read +1ms
    serialport:unixRead Finished read 240 bytes +51ms
    serialport:main binding.read finished +0ms
    serialport:main _read reading +2ms
    serialport:bindings read +0ms
    serialport:unixRead Starting read +1ms
    (... more of these regular 240 byte data events ...)
  2017-08-10T09:46:03.083Z - info: GPS:   10Hz       ARM: ( 127| 127|   0)Hz     caching:    0Hz     saving:  596Hz     uploaded: 0 batches

Still,  I am wondering where this bug/lag/delay comes from which I described above: I usually receive packages of 242 bytes now with parser.on(readable) but sometimes there are silent 1-3 seconds and then I receive ~2kB at once:
 serialport:poller Polling for "readable" +0ms   serialport:poller received "readable" +188ms   serialport:bindings read +1ms   serialport:unixRead Starting read +0ms   serialport:unixRead Finished read 242 bytes +13ms   serialport:main binding.read finished +0ms   serialport:main _read reading +2ms   serialport:bindings read +0ms   serialport:unixRead Starting read +1ms   serialport:unixRead waiting for readable because of code: EAGAIN +8ms   serialport:poller Polling for "readable" +0ms   serialport:poller received "readable" +167ms   serialport:bindings read +0ms   serialport:unixRead Starting read +1ms 2017-08-10T13:42:57.309Z - info: GPS:    4Hz       ARM: ( 149| 149|   0)Hz     caching:    0Hz     saving:  236Hz     uploaded: 0 batches 2017-08-10T13:42:58.315Z - info: GPS:    0Hz       ARM: ( 139| 139|   0)Hz     caching:    0Hz     saving:    0Hz     uploaded: 0 batches   serialport:unixRead Finished read 1936 bytes +1s   serialport:main binding.read finished +1ms   serialport:main _read reading +7ms   serialport:bindings read +1ms   serialport:unixRead Starting read +0ms   serialport:unixRead waiting for readable because of code: EAGAIN +66ms

Thanks for the reply!
I gave it a try but this didn't change the problem, that sometimes the data is "hold back" for a couple of seconds: Such a delay looks now e.g. like the following with highwaterMark = 500b:

@10s 0ms: 240B
@10s 200ms: 240B
... nothing for 1000-2000ms
@ 12s 0ms-12ms: 500, 500, 500, 500 (instead of a 2kB event with higher highwaterMark)

Very weird. I guess I have (or better my code has) to live with this kind of behavior.
Thanks anyway for the great module!

Thanks :) When I get hold of another GPS receiver, I'll keep you updated if
the problem exists there, too.
2017-08-12 1:10 GMT+02:00 Francis Gulotta<EMAIL_ADDRESS>
I don't want you to live with it, but I can't tell you for sure what's
going on, or even if it's an issue with node serialport.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/EmergingTechnologyAdvisors/node-serialport/issues/1295#issuecomment-321937956,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF1D8QxKCBopF-5lOPIOIx4d9_InMLEMks5sXN-DgaJpZM4OzQdt
.


use Vale to fix small typos and spelling errors

This PR includes 60+ small changes to the docs. Most are for small typos, spelling errors, or slight changes to the spelling/capitalization of proper names.
I used Vale to find these as a test. Figured I would fix them and submit while I was at it :)

wooo! pausing this PR for now until Melissa merges her overhaul


Make Gantt chart date inclusive

This is a feature request.
It would be cool if we can configure our Gantt chart so that the dates are inclusive. For example if there is a task from June 1st to June 3rd I can write 2019-06-01, 2019-06-03. Currently the ending date is exclusive, so I have to write 2019-06-01, 2019-06-04 which is counter-intuitive.
It can be either a switch in JavaScript API, or some command in the diagram definition (similar to dateFormat and title).

Hey, @ThePenguin1140. This is done and we can close it, right?

Verified with ./dist/index.html. Looking forward to next release!


(HTTP code 404) unexpected - {"message":"manifest for mobz/elasticsearch-head:latest not found"}

Expected behavior
not 404
Actual behavior
404
Information about the Issue
Steps to reproduce the behavior

... select docker image
...run
...observe fail

Looks like that repository does not have a :latest tag, so you will have to specify a specific tag to use; here's the steps to do so (steps below are for the offciel elasticsearch image, but the steps are similar for the image you're using):

Click on the ... button to view the image's details

Click on the Selected tag: latest to open the "tag selection" window

Click the tag / version of the image you want to run

Click the (X) to close the tag selector window

Click on the Create button to pull the image and start the container


ci: add beta releasy to fuels-rs to track fuel-core

Description
This PR adds beta version of releasy which will create upgrade/fuel-core branch and track changes happening in the fuel-core. This way any commits that merged to fuel-core which will be breaking fuels-rs once released, will be catched by the CI of that branch.
This is for testing, we will install this to all repos once we are sure that everything works nicely.
Checklist

[ ] I have linked to any relevant issues.
[ ] I have updated the documentation.
[ ] I have added tests that prove my fix is effective or that my feature works.
[ ] I have added necessary labels.
[ ] I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
[ ] I have requested a review from the relevant team or maintainers.

I am not sure why the CI is failing. Any ideas?

cc @digorithm

It seems like the CI is passing 🤔

failing again because sway changed the installation page to "getting-started": https://github.com/FuelLabs/sway/commit/98d0810facc2030bc208daadd68b89b3c3d4be89

Looks like ci is passing again


There is no setting 'Resource type' on the Summary dialog when attaching one file share

Storage Explorer Version: 1.20.0-dev
Build Number: 20210511.3
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ MacOS Big Sur 11.3
Architecture: ia32/x64
How found: exploratory test
Regression From: Not a regression
Steps to Reproduce

Expand one storage account -> File Shares.
Select one file share -> Generate its shared access signature -> Copy the SAS.
Open the connect dialog -> Select 'File share' -> Paste the copied SAS to the 'File share SAS URL' filed -> Click 'Next'.
Check whether there is the setting 'Resource type' on the Summary dialog.

Expected Experience
There is the setting 'Resource type' on the Summary dialog.
The screenshot for one blob container:

Actual Experience
There is no setting 'Resource type' on the Summary dialog.

Additional Context

This issue doesn't reproduce for one blob container.
This issue reproduces for one table & queue.

@craxal
Verified this issue on build 20210524.3.

Fixed for one file share.
Still reproduce for one queue/table.

So we are going to re-open this issue.

@v-xianya I will do this for table and queue. May I suggest that in the future, you mention all areas that need fixing in the title or bug description? For example, "...when attaching file share, queue, or table". The Additional Context area is meant more supplemental information, such as for helping describe or reproduce the bug, not important information such as other areas that need fixing.

@craxal Got it. thanks for your response and clarification!
We will mention all areas that need fixing in the title or bug description.


Component refactor

Refactor application to split out components into a components directory.
Split out TodoListOptions into a TodoList type in the types directory.
ListItem highlighting now works on a nullable boolean idea. True is highlighted, false is highlighting is active but item is not highlighted and null is no highlighting active. Not really sure if I like the idea but it works and gets around Svelte css class shaking.
I understand that this is quite a large pull request and if this isn't the way you want the application to change then that's totally fine, let me know what changes you'd like me to make and I'll take a look. Otherwise we can just scrap this request :)

Sorry I haven't been able to look over it, I hoped that my PR preview would work :D
Will try to look at it around tmrw-ish

thank you very much, nice refactoring :) 🎉
My local testing worked (need to figure out how to test atleast some stuff on the CI^^)


Fix x86 builds of Clang 3.9, Clang 4 and Clang 5

See failing logs in the current default branch on Travis.
E.g. https://travis-ci.org/inexorgame/conan-grpc/builds/475561210
Contributions or tips highly appreciated! 😄

No, --start-group are not supported by Conan. I just tried to use with Abseil, but it's a total mess, because I can't wrap the library list. I'm investigating to find a correct fix.

@Croydon The problem is that gRPC is using an internal protobuf.cmake file, which doesn't list libatomic and of course, ignores conan libs.
There are few options:

Patch gRPC/CMakeLists.txt to use conan protobuf libs:

tools.replace_in_file(os.path.join(self._source_subfolder, "CMakeLists.txt"), "_gRPC_PROTOBUF_LIBRARIES", "CONAN_LIBS_PROTOBUF")

Patch gRPC/cmake/protobuf.cmake to use ${CONAN_LIBS_PROTOBUF} instead of forcing libprotobuf only
Replace protobuf.cmake by find_package(protobuf) and set all expected definitions

The first option worked for me, I'm using conanio/clang50-x86 to reproduce your error.

Option 1 seems to work. Thank you so much for investigating this!
https://github.com/inexorgame/conan-grpc/commit/39da3b5c001ee026578a7087c55c1ee7500205f2
What I'm wondering however, if atomic only makes problems on  x86 on Clang 3.9, 4 and 5 why do we add it for all Clang versions? Is this necessary?

According the documentation:

Clang does not currently automatically link against libatomic when using libgcc_s. You may need to manually add -latomic to support this configuration when using non-native atomic operations

Thus when cross-building to x86 we need to add -libatomic. However, LLVM docs use the same note for Clang 6, 7 and 8, which puzzles me because it only happens with previous versions. :thinking:

Hm, alright. We can review this workaround somewhen in the future again.
This issue seems to be done for now.
Thanks again!


Secure property for type password freezing the screen and disabling the other text fields. IOS

Steps to reproduce
Add following tags to the page.
<MDTextField #username ios:variant="underline"
class="large-input-field" autocapitalizationType="none"
autocorrect="false"
[automationText]="Username"
[returnKeyType]="next"
[hint]="Username">

<MDTextField #password ios:variant="underline"
class="large-input-field" autocapitalizationType="none" secure="true"
autocorrect="false"
[automationText]="Password"
[returnKeyType]="done"
[hint]="Password">

Enter username and then password. After entering password try to edit username, it will freezes the screen, unable to enter data, resulting in crash of application.
You can add signIn() function linked to the returnPress of Password field, and add function to it. It will also result in same behaviour resulting in crash of app on IOS.
Occurring only in IOS
Which platform(s) does your issue occur on?

iOS
emulator or device.

Please, provide the following version numbers that your issue occurs with:

CLI: 6.8.0 (run tns --version to fetch it)
IOS version: 2.7.0

Please, tell us how to recreate the issue in as much detail as possible.
Describe the steps to reproduce it.

@ruminder90 i need a simple repro example to fix it. And not in Angular it adds too much making it really hard to debug

It working fine with the sample application I created, however in my other project I am not able to edit the username field after entering the password. There were not much logs, only logs related to "unable to simultaneously constraints". However on making secure=false, everything works fine. Can any one tell me what could be possible cause creating the issue.

Facing a similar issue with the secure text field - have anyone fixed it or have any workaround?

Same here... I hate iOS... it's always before my public release that this kind of fuc*** skd14 is making me crazy.... I cannot publish an app with clear password.... please...

I've temporary replace all my "secure" MD input with simple NS Textfield....the secure is ok for those one.

@lostation @akanksha0514 @chuckmitchell could you try 5.3.4-alpha.0+3df91bf4 ? It has the new implementation of the textfield. Not sure it is perfect yet though


is there a way to select all within a group?

Before I begin, thank you very much. Its a great utility.
I am looking for a feature of selecting a group of items.
Group by is working, is there a way I can have a checkbox for the group by header and select all inside that group only.???

If the category can be accepted as template, that could solve this functionality.

duplicate of #69

hi oi need this feature ..please tel how to do

currently this feature possible ?

Hi, even I need this feature for my project urgently. Could you please help @CuppaLabs ?
Thank you in advance.

Hello @CuppaLabs Thanks a lot for the angular2-multiselect-dropdown this is advancing my life a lot, I would like my colleagues to select this feature by group, I tried to understand the angular2-multiselect-dropdown core to implement the functionality but I could not do it unhappily I do not have the same level of maturity that you, I would like to know if you have any date to implement the functionaldiade? Thanks in advance.


Add device ready check

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Looking for some feedback on where else this is needed for testing. Not looking to merge yet.

What's the link for the tracking issue on this one? I'd like to refresh myself on the context.

Oh sorry, I had to step out and forgot to link the issue but looks like you found it.

For this change can we take a snapshot of the android flakiness now to compare after this change lands?

Do you mean a snapshot as in record all the current android flakes? That can be done via the CiYaml correct? As we record the open issues for flakes directly in that file?

Do you mean a snapshot as in record all the current android flakes? That can be done via the CiYaml correct? As we record the open issues for flakes directly in that file?

Nope, I meant a screenshot of the flakiness dashboard for devicelab android

Ahhh okay. Yeah will do.

The top flaky test over the past 90 days:

Top flaky linux android prod tasks by tags last 90 days:

Top flaky linux android try tasks by tags last 90 days:


Remap key to key combination

I'm thinking how to bind y to the equivalent of 'a 5'. So, current song, copy link.
I think either having it so you can bind to a sequence of commands, or bind a key to a sequence of keys would be nice.
Something like
[[keymaps]]
command = "ShowActionsOnCurrentTrack; CopyTrackLink"
key_sequence = "y"
or
[[keymaps]]
command = "a 5" // maybe a different name instead of command? idk
key_sequence = "y"

It's better to define a separate mapping for actions:
[[actions]]
action = "GoToTrackRadio"
key = "r"

[[actions]]
action = "AddToLikedTracks"
key = "y"

I just started to take a look at the actions! Nice one.
Unfortunately it seems it still doesnt allow to implement the example I gave? I can only for example copy the link of the current selection. I can't do the equivalent of 'a 5' right now.
I'd need to go to currently playing context and select the song I'm playing for example and then use the CopyLink action.
Unless I'm getting something wrong?

Unfortunately it seems it still doesnt allow to implement the example I gave? I can only for example copy the link of the current selection. I can't do the equivalent of 'a 5' right now.
I'd need to go to currently playing context and select the song I'm playing for example and then use the CopyLink action.
Unless I'm getting something wrong?

Yeah, you're right. The current action only works on currently selected item. We can update action keymap to also support currently playing track, which can be configured by a new field ActionType
enum ActionType {
   PlayingTrack
   SelectedItem
}

cc @juliamertz is this something you're interested in working on as a follow-up?

cc @juliamertz is this something you're interested in working on as a follow-up?

Doesn't look like this would be too much work, i'll take a look at it when i get some time

cc @juliamertz is this something you're interested in working on as a follow-up?

Doesn't look like this would be too much work, i'll take a look at it when i get some time

Great, thank you!


Error while creating job: job job-executor-service-job- failed

Hi @agardnerIT can you address this issue if I you have faced it?
Reason: BackoffLimitExceeded

I'm afraid I cannot reproduce this. Closing as a transient Killercoda (environment) caused issue. Please re-open this thread if more reports come in and thank you to the reporter (whomever it was) for taking the time to report this :)


chore(examples): generate examples index

This generates single index file with (potentialy nested) groups and generated screenshots of examples.
The whole thing is written to be reusable, therefore there should be no problem porting this to Graph3D or Timeline. However it get's almost all of it's information from the examples. All examples have to have the canvas in a container with given id (configurable on CLI). Their titles have to follow this structure:
Group | [Another Group | [Another Group | …]] Example Title.
There is also some primitive linting that requires the title to match the heading in the body (not enforced in any way, just a warning).
Result: https://jsfiddle.net/thomaash/fn5mzokq/embedded/result (the links would lead somewhere and the images would't be inlined if this was on GitHub Pages instead of JSFiddle).
PS: I tried to fix this real quick but there may still be some issues with example names as they we're a total mess with a lot of them called Basic Usage or whatever they were originally copy pasted from.

This could be used to improve https://github.com/visjs/vis-graph3d/issues/2

Maybe we should create vis-dev-util package for this and potentially other reusable tools created in the future so that we can easily share them across projects.

It might be a good idea to give every network a "seed" so that they look the same every time they get rendered. This blows up the demo-code a little bit but maybe be could inject this option only while rendering!?

It might be a good idea to give every network a "seed" so that they look the same every time they get rendered. This blows up the demo-code a little bit but maybe be could inject this option only while rendering!?

@Thomaash What do you think about that?
The option I have in mind is the randomSeed in the layout config.

It might be a good idea to give every network a "seed" so that they look the same every time they get rendered. This blows up the demo-code a little bit but maybe be could inject this option only while rendering!?

@Thomaash What do you think about that?
The option I have in mind is the randomSeed in the layout config.

This was a bit tricky but done. I'll have a look at exampleUtil now because it uses Math.random() and screws things up. This should be an easy fix.

No problem.


IntelliSense - self invoking bind pattern

From @NikosEfthias on September 29, 2016 14:33

VSCode Version:1.5.3
OS Version:ubuntu 16.4

Steps to Reproduce:

write a function that is borrowing props through bind to something else
intelisense wont work

Copied from original issue: Microsoft/vscode#13010

@NikosEfthias thank you for opening this issue.
I'm not understanding what is going on. Can you provide a minimal repo that I can clone or copy to recreate what you are seeing?
Also if you provide an animation that will help me see what is going on.

Thanks @NikosEfthias. I don't believe this pattern is supported by TS Server currently Moving to TS repo to track it as a feature request.

From @NikosEfthias on September 29, 2016 21:38
interface data {
    count: number
}
const data:data={count:0}
data.count //intelisense works here and auto completes the count
(function(){
    this.count// intelisense does not understand this keyword here although its context was bound to data
}).bind(data)

@waderyan

Note I reproduced this with the latest bits.

We don't really want to encode the semantics of one-off JS functions into the type system


ukvm: Fix overflow if solo5_poll() called too late

If solo5_poll() on ukvm is called after until_nsecs have passed then we
pass a negative value to UKVM_PORT_POLL which results in waiting for a
very long time.
Also clarify the UKVM_PORT_POLL interface to make it clear that the
timeout is relative, not absolute.

good catch!


feat: add class named & string/class qualifier

Can you also support complex types?

Can you also support complex types?

Why do you need such a complex structure?

Well, imagine Mapper<MyDomain, MyView>
we inject it using @Factory and we also need to add type qualifier, and just MyDomain alone isn't enough.
Or Imagine we use Serializer<List<MyDomain>>, so we need to add type qualifier not for List, not for MyDomain, but for List<MyDomain>, so here tree-structure is preferable for such usecases (and not flat one, because we must distinguish SomeClass<Int, OtherClass<Int>> and SomeClass<Int, OtherClass, Int>)
Such tree structure required only at annotation definition, and then can be converted to string for example, to be easily compared (see code I linked above).
So that's why I think that if we adding support for type-based qualifiers, then we need to at least support generic-types.

Well, imagine Mapper<MyDomain, MyView> we inject it using @Factory and we also need to add type qualifier, and just MyDomain alone isn't enough. Or Imagine we use Serializer<List<MyDomain>>, so we need to add type qualifier not for List, not for MyDomain, but for List<MyDomain>, so here tree-structure is preferable for such usecases (and not flat one, because we must distinguish SomeClass<Int, OtherClass<Int>> and SomeClass<Int, OtherClass, Int>) Such tree structure required only at annotation definition, and then can be converted to string for example, to be easily compared (see code I linked above).
So that's why I think that if we adding support for type-based qualifiers, then we need to at least support generic-types.

possible solution:
Nested Structure
sealed interface ListQualifier {
  data object Int : ListQualifier
  sealed interface Str : ListQualifier {
    data object String : Str
  }
}

@Module
class ListModule {
  @Singleton(createdAtStart = true)
  @Qualifier(ListQualifier.Int::class)
  fun provideIntList() = listOf(1, 2, 3)

  @Singleton(createdAtStart = true)
  @Qualifier(ListQualifier.Str.String::class)
  fun provideStringList() = listOf("hi", "hello")
}

class MyActivity : ActivityScope() {
  private val intList: List<Int> by inject(qualifier<ListQualifier.Int>())
  private val stringList: List<String> by inject(qualifier<ListQualifier.Str.String>())
}

Flat Structure
annotation class IntListQualifier
annotation class StringListQualifier

@Module
class ListModule {
  @Singleton(createdAtStart = true)
  @Qualifier(IntListQualifier::class)
  fun provideIntList() = listOf(1, 2, 3)

  @Singleton(createdAtStart = true)
  @Qualifier(StringListQualifier::class)
  fun provideStringList() = listOf("hi", "hello")
}

class MyActivity : ActivityScope() {
  private val intList: List<Int> by inject(qualifier<IntListQualifier>())
  private val stringList: List<String> by inject(qualifier<StringListQualifier>())
}

### Generated Code
#### Nested Structure
```kotlin
single(qualifier=org.koin.core.qualifier.StringQualifier("com.parsuomash.sdk.di.qualifier.ListQualifier\$Int"),createdAtStart=true) { moduleInstance.provideIntList() } bind(kotlin.collections.List::class)
	single(qualifier=org.koin.core.qualifier.StringQualifier("com.parsuomash.sdk.di.qualifier.ListQualifier\$Str\$String"),createdAtStart=true) { moduleInstance.provideStringList() } bind(kotlin.collections.List::class)
}

Flat Structure

Well that looks kinda hacky. The flat structure looks interesting (except it quickly gets verbose).
But it does not create clear connection between real kotlin types and qualifier, so it will be hard to query instances later on.
I mean, while simple querying is still trivial, it will be quite hard to retrieve Mapper<Domain, View> for specific Domain and View, known at compile-time. You'll end up building yet another big when condition to get MapperDomain1View1, MapperDomain2View2 ... or Mapper.Domain1.View1, Mapper.Domain2.View2.
With my solution, on the other hand you'll still be able to use FlatMeaninglessAnnotation for trivial usecases, but you will also able to (with the help of an inline function) retrieve instances for class with specific generics. So I can write one little function  getMapper which will build TypeQualifier and quickly find what I need.
inline function (aka typeQualifierOf) should be part of API (I'll try to write/suggest one, later on).

Also please provide any feedback on my reasoning and code above, because, well, I see reflection of our discussion in commit name, but not in code changes itself.

Also please provide any feedback on my reasoning and code above, because, well, I see reflection of our discussion in commit name, but not in code changes itself.

I think this method can also be implemented in another PR.
@arnaudgiuliani

Anyway your current annotation can't be used to build complex type structure (yeah that recursive-annotation thing looks even more horrible than my DSL), am I right?

I should clarify my intentions: even if u don't want to implement support for complex types by yourself, please at least add support for that at annotation side, so next changes can be implemented incrementally, without need of breaking existing interface (without need of rewrite TypeQualifier annotation)

Ghm.. this whole time we can just use typeOf... My bad, I've almost forgot about such simple thing.
package org.example

import kotlin.reflect.KClass
import kotlin.reflect.KType
import kotlin.reflect.jvm.jvmErasure
import kotlin.reflect.typeOf

annotation class TypeQualifier(val value: KClass<*>, vararg val params: TypeQualifier)

val TypeQualifier.qualifier: String get() {
    var qualifier = value.qualifiedName!!
    if (params.isNotEmpty())
        qualifier += "<" + params.joinToString { it.qualifier } + ">"
    return qualifier
}

fun typeQualifierOf(type: KType): TypeQualifier
    = TypeQualifier(type.jvmErasure, *type.arguments.map {
        typeQualifierOf(it.type!!)
    }.toTypedArray())
inline fun <reified T : Any> typeQualifierOf()= typeQualifierOf(typeOf<T>())

fun main() {
    println(typeQualifierOf<Map<Map<Int, String>, String>>().qualifier)
}

So.. now such simple thing can be implemented in the scope of the same PR, what do you think?

Would be valuable if defining type annotations could be less verbose. Usually a qualifying annotation is used in many places in the code causing it to look cluttered.
Instead of this:
@Scope(name = "scope1")

@Named(name = "name1")

Prefer less verbose definitions like:
annotation class Scope1

annotation class Name1

This way @Scope1 could be used instead of @Scope(name = "scope1")

same about preparing 1.4.0 branch - https://github.com/InsertKoinIO/koin-annotations/pull/107

I tried to do that. And it only works
@Named("CoroutineDispatcherIO")
annotation class NamedCoroutineDispatcherIO

@Named("CoroutineDispatcherMain")
annotation class NamedCoroutineDispatcherMain
@Single
@NamedCoroutineDispatcherIO
fun provideDispatcherIO(): CoroutineDispatcher = Dispatchers.IO

@Single
@NamedCoroutineDispatcherMain
fun provideDispatcherMain(): CoroutineDispatcher = Dispatchers.Main

But there is a bug. When using two annotations at the same time. It turns out that there will be an instance of one object. Although it should be different.
class Test(
    @NamedCoroutineDispatcherIO dispatcherIO: CoroutineDispatcher,
    @NamedCoroutineDispatcherMain dispatcherMain: CoroutineDispatcher
) {
    init {
        // Wrong
        println(dispatcherIO.hashCode() == dispatcherMain.hashCode()) // True (expect false)
    }
}

@ghasemdev when are you planning to merge it?


doc: fix example file after v0.5.0 update

Example files does not reflect the change in v0.5.0. The documentation refers to the parameter terraform.enabled = true but the file used with kubectl apply does not reflect this change.

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 50.99%. Comparing base (96f8443) to head (d40a498).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main     #380   +/-   ##
=======================================
  Coverage   50.99%   50.99%
=======================================
  Files          73       73
  Lines        4334     4334
=======================================
  Hits         2210     2210
  Misses       1935     1935
  Partials      189      189

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Make strings_to_categoricals upon .write() optional

To illustrate that it'd be a simple change, this PR adds the 3 lines for what @ivirshup suggested here 3 years ago:

I think I'd be fine with a keyword argument for this.

In the two issues below, @grst, @adamgayoso, @lazappi & @ljjh20 expressed that "forced" sanitization is problematic.

https://github.com/scverse/anndata/issues/534
https://github.com/scverse/scanpy/issues/1747

I found these issues only now but also agree that a write function should not mutate the object that's about to be written. @chaichontat made me aware.
Things turn out particularly bad for gene symbols, which should remain strings even for performance reasons and compatibility with JS. Having 30k categories in a 32k dimensional genes vector is detrimental, not beneficial.

Just chipping in to say that while I think this would be great, it doesn't really solve https://github.com/scverse/scanpy/issues/1747 as scanpy functions will still cause this conversion (unless something has changed). So this helps if you are just reading/writing AnnData but anything that goes through scanpy is still likely to be converted to categoricals.
You probably knew this already but wanted to make it clear for anyone reading this later.

Just chipping in to say that while I think this would be great

Great that you're also onboard, @lazappi!

as scanpy functions will still cause this conversion (unless something has changed)

Yes, you're right about the Scanpy plotting functionality. But I think the issue is more pressing for anndata, given its widespread use outside of Scanpy.

@flying-sheep I am disabling auto-merge.  Isaac brought up a good point about whether this should be in settings on zulip.  What do you think?  I think it's fine to leave this here because you might have different behavior for different datasets.  If you agree we can merge (two against one haha).

@ivirshup your call then.

I am fine leaving this as-is @flying-sheep so will enable auto-merge

I think we didn’t fully agree on if this should be an “and” or an “or” for things to go into settings.

I am comfortable with "or" here


test(fabric): fix fabric AIO couchdb No such file or directory

Describe the bug
When I try to run the command that's in the Fabric connector's README.md, it
does not work for multiple reasons:

It does not specify the elevate permissions via the --privileged flag
The image at the current latest version (1.0.0-rc.3) seems broken altogether due to the Fabric CouchDB container image not being cached locally as intended.

To Reproduce
docker run --privileged -p <IP_ADDRESS>:8545:8545/tcp  -p <IP_ADDRESS>:8546:8546/tcp  -p <IP_ADDRESS>:8888:8888/tcp  -p <IP_ADDRESS>:9001:9001/tcp  -p <IP_ADDRESS>:9545:9545/tcp ghcr.io/hyperledger/cactus-fabric-all-in-one:v1.0.0-rc.3
Expected behavior
The container should boot up without issues to the point where the healthcheck is passing and the ledger is operational.
Logs/Stack traces
2021-12-21-fabric-1-aio-tar-couchdb-crash.log
2021-12-21 23:51:49,022 INFO spawned: 'fabric-network' with pid 15217
Loaded image: hyperledger/fabric-peer:1.4.8
2021-12-21 23:51:49,236 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-peer:1.4.8

Loaded image: hyperledger/fabric-orderer:1.4.8
2021-12-21 23:51:49,448 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-orderer:1.4.8

Loaded image: hyperledger/fabric-ccenv:1.4.8
2021-12-21 23:51:50,200 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-ccenv:1.4.8

2021-12-21 23:51:50,200 INFO success: fabric-network entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Loaded image: hyperledger/fabric-tools:1.4.8
2021-12-21 23:51:51,103 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-tools:1.4.8

Loaded image: hyperledger/fabric-ca:1.4.9
2021-12-21 23:51:51,415 DEBG 'fabric-network' stdout output:
Loaded image: hyperledger/fabric-ca:1.4.9

tar: can't change directory to '/etc/hyperledger/fabric/fabric-couchdb/': No such file or directory
2021-12-21 23:51:51,428 DEBG 'fabric-network' stderr output:
tar: can't change directory to '/etc/hyperledger/fabric/fabric-couchdb/': No such file or directory

open /var/lib/docker/tmp/docker-import-640167045/repositories: no such file or directory
2021-12-21 23:51:51,489 DEBG 'fabric-network' stderr output:
open /var/lib/docker/tmp/docker-import-640167045/repositories: no such file or directory

2021-12-21 23:51:51,491 DEBG received SIGCHLD indicating a child quit
2021-12-21 23:51:51,491 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>82560 for <Subprocess at<PHONE_NUMBER>49008 with name fabric-network in state RUNNING> (stdout)>
2021-12-21 23:51:51,492 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at<PHONE_NUMBER>82512 for <Subprocess at<PHONE_NUMBER>49008 with name fabric-network in state RUNNING> (stderr)>
2021-12-21 23:51:51,492 INFO exited: fabric-network (exit status 1; not expected)

Screenshots
N/A
Cloud provider or hardware configuration:
dev machine
Operating system name, version, build:
Linux 5.11.0-43-generic x86_64
NAME="Ubuntu"
VERSION="20.04.3 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.3 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

Hyperledger Cactus release version or commit (git rev-parse --short HEAD):
1.0.0-rc.3
Hyperledger Cactus Plugins/Connectors Used
Fabric Connector Plugin
Additional context

Came up during the migration to the GitHub Container Registry.
It works just fine with 1.0.0-rc.2 so this must be a recently introduced bug in the Dockerfile

@outSH Is this what you fixed in that other PR related to the Fabric AIO image? If yes, then we can close this one.

@petermetz Yes, this error is fixed in https://github.com/hyperledger/cactus/pull/1754

@outSH Cool, thank you. I'm closing this issue then.


Disabled collapse-link when document.ready

Some divs at my page uses the class "collapse-link" so the box expands and contracts as the icon "chevron" is clicked. Everything wokrs perfectlly, but I´ll rather the default effect  be just the contracted box or div instaed of the expanded type. Thank you all. Here is my code:
`    HTML:

Fecha

Código / Calificación
Nuevo campo agregado:

Modificaciones 1

Modificaciones 2

Selecciona la fecha

SELECCIONE UNA OPCION

                        <button type="submit" class="btn btn-primary animated fadeInUp">Cancelar</button>
                        <button type="button" class="btn btn-success animated fadeInUp">Filtrar</button>

                  </form>

JAVASCRIPT:

`

Please post your example as a JS Bin, JS Fiddle, CodePen, or similar.

Hey there!
We're automatically closing this issue since the original poster (or another commenter) hasn't yet responded to the question or request made to them 14 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.
Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.
Thanks!
(Please note that this is an automated comment.)


runtime: VirtualAlloc of 505413632 bytes failed with errno=487 on windows buildbot

See https://build.golang.org/log/b4ba26bd8ca310b020793e8b8667aaf13fd65cc9.
Buildbots has started failing w/ CL 45113 and 45114, which contain a test case that claims a growing of slice from (len:0xc, cap:0x10) to (len:0x14, cap:0x20? maybe) in the append operation at https://github.com/golang/net/blob/master/internal/socket/socket.go#L200.
Looks like this issue already happened in Go 1.7, see #14638, and there are no other complaints.

Also on windows/amd64: https://build.golang.org/log/22ed6085158eec0ec2246e869517fb31ae3df4c9
runtime: VirtualAlloc of<PHONE_NUMBER> bytes failed with errno=1455
fatal error: runtime: cannot map pages in arena address space

Nope, this is an issue in internal/socket package. I forgot that the cmsghdr is defined as zero-sized stuff like type cmsghdr struct{}.


fix DNI projection into POA

[x] Closes #718  .
[x] I am familiar with the contributing guidelines.
[x] Tests added.
~Updates entries to docs/source/api.rst for API changes.~
[x] Adds descriptions to appropriate "what's new" file in docs/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[x] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

Also closes #522
master 15 and 60 minute ahead persistence

this PR 15 and 60 minute ahead persistence

@lboeman not sure why the tests keep failing on that one API test again. Maybe we need to wipe the test database again? (And ultimately write better core tests?)

@lboeman not sure why the tests keep failing on that one API test again. Maybe we need to wipe the test database again? (And ultimately write better core tests?)

I'm not sure why the data ends up in this state. I reset dev mysql and reran the tests. I think we need to move away from using the dev db for these tests.


[fix] use upgrade property for uws http server

fixes #1079
@yasserf e2e:v3 tests are not passing, should they be removed from the husky script? Since they're alredy removed from CI...of course it's not ideal but given the scarce ressources...if you have any hint on how to fix them let me know.

Yeah let’s just ignore them. If someone uses a V3 combo and has issues they can raise a GitHub issue.


Missing typescript sourcemap

I downloaded this repo to try out Webpack 4 configuration for Angular 6. I followed instructions to download npm packages, build using

npm run build:dev

and ran the application. Application successfully started with home page displayed in browser but looking at "Sources" in Firefox and Chrome browser debugger I only see the "JavaScript" code.
Here is the actual "app.component.ts" in VSCode:

// i18n support
import { TranslateService } from '@ngx-translate/core';
import { REQUEST } from '@nguniversal/aspnetcore-engine/tokens';

@Component({
    selector: 'app-root',
    templateUrl: './app.component.html',
    styleUrls: ['./app.component.scss'],
    encapsulation: ViewEncapsulation.None
})
export class AppComponent implements OnInit, OnDestroy {

Here is what "app.component.ts" shows in browser debugger:
// i18n support

var AppComponent = /** @class */ (function () {
    function AppComponent(router, activatedRoute, title, meta, linkService, translate, injector) {
        this.router = router;
        this.activatedRoute = activatedRoute;
        this.title = title;
        this.meta = meta;
        this.linkService = linkService;
        this.translate = translate;

What is the solution? With older Webpack version I can see the correct sourcemap and it is easy to debug. I noticed a previous Issue reported here, that is closed now but no resolution was provided in comments.
I tried different settings for devtool: isDevBuild ? 'cheap-eval-source-map' : false, but didn't get any results. I am sure others have noticed this issue too, so any solution??
Thanks

I'm hitting my head against a wall right now trying to figure this out as well.

I think at least Firefox has issues...

I have tried it on "Chrome", "IE 11" and Firefox. It didn't work on either. I tried project with Angular CLI on all three browsers and it worked perfectly fine. I believe Angular 6+ CLI uses WebPack 4 too.

Not sure what the issue is. Works for me just fine.

Can you open any of the ".ts" file and see the TypeScript code? In your screenshot it shows "app.component.ts", does it show actual TS code in it? I could see the "*.ts" files but they show "JavaScript" code, as mentioned in my comment.

@supetronix
any solution for this ?

In Chrome, when you go to Sources tab.
Do Ctrl-P (or Cmd-P on MAC), you can actually type the name of the file you're looking for.
Do you see the typescript files there?

Mmmm I can see the names of the typescript files, but when I open it, is javascript, look

@cristiancpl - I didn't find solution and I was in the same boat as you are (.ts file showing the JS code). I gave up and move on to using the VS2017 .net core 2.1 template that comes with builtin angular cli (I believe 6+) and it worked perfect for me.


[Bug]: Blender doesn't updates to 4.0.1

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
blender
Expected/Current Behaviour
blender does not update to version 4.0.1, although this version is downloaded normally from the official site
Steps to Reproduce
scoop update blender
blender: 4.0.0 -> 4.0.1
Updating one outdated app:
Updating 'blender' (4.0.0 -> 4.0.1)
Downloading new version
The remote server returned an error: (429) Too Many Requests.
At C:\Users\Samson\scoop\apps\scoop\current\lib\install.ps1:111 char:9
+         throw $e
+         ~~~~~~~~
    + CategoryInfo          : OperationStopped: (:) [], WebException
    + FullyQualifiedErrorId : The remote server returned an error: (429) Too Many Requests.

Possible Solution
Possubly replace url in blender.json from https://download.blender.org/release/Blender4.0/blender-4.0.1-windows-x64.zip to https://mirrors.sahilister.in/blender/release/Blender4.0/blender-4.0.1-windows-x64.zip
Scoop and Buckets Version
scoop --version
Current Scoop version:
v0.3.1 - Released at 2022-11-15

'extras' bucket:
afd20e313 (HEAD -> master, origin/master, origin/HEAD) tor-browser: Update to version 13.0.5

'main' bucket:
eebcc4ee8 (HEAD -> master, origin/master, origin/HEAD) spicetify-cli: Update to version 2.27.2

Scoop Config
scoop config

last_update                       scoop_branch scoop_repo
-----------                       ------------ ----------
2023-11-23T18:08:57.4636632+03:00 master       https://github.com/ScoopInstaller/Scoop

PowerShell Version
$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.19041.3570
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.3570
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

Additional Softwares
No response

can confirm this issue


Add cask: Visual Studio for Mac preview-1

[x] brew cask audit --download {{cask_file}} is error-free.
[x] brew cask style --fix {{cask_file}} reports no offenses.
[x] The commit message includes the cask’s name and version.
[x] Named the cask according to the [token reference].
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no [open pull requests] for the same cask.
[x] Checked that the cask was not already refused in [closed issues].

Note, this is distinct from Visual Studio Code. They can be installed
concurrently. I was unable to find any info on the installer arguments
for unattended installation, so this will show the user a UI.
See https://www.visualstudio.com/vs/visual-studio-mac/ to confirm download link.
Fixes #26882

I was unable to find any info on the installer arguments for unattended installation, so this will show the user a UI.

In that case, this needs installer :manual, not :script.

In that case, this needs installer :manual, not :script.
Done

Looks like it's still using script. Are you sure you pushed the right branch?

Heh, nope ;) Fixed it now.
Is changing to manual all that's required there, or does the path change as well?

Thank you for the contribution. It needed some fixes, so they were made in 721d04dc8304ff9215d8274797465b6fcd7baa89. Your contribution is still included (and still credited to you), with the appropriate modifications. Please feel free to ask about any of the changes.


uv_get_process_title ends with a segfault if process_title.len is 0

Version: v1.x
Platform: x86_64 GNU/Linux

uv_get_process_title terminates with a segfault when process_title.str is null and process_title.len is 0.
I got it by running the tests of uvw through gtest in a local branch. If you need to reproduce the error, I can push the branch and it will be a matter of compiling the project and running the tests.
Anyway it's pretty simple to reproduce: do not call uv_setup_args and invoke uv_get_process_title. That's all.
That being said, uv_set_process_title does a check on process_title.len before to call strncpy and perform its tasks.
Shouldn't uv_get_process_title do something similar before to use memcpy?
Consider the following line from proctitle.c:
memcpy(buffer, process_title.str, process_title.len + 1);

In case of process_title.str null and process_title.len 0, libuv keeps asking to read a byte from a null pointer.
Isn't it an error?
A possible alternative implementation of uv_get_process_title could be:
int uv_get_process_title(char* buffer, size_t size) {
  if (buffer == NULL || size == 0)
    return -EINVAL;
  else if (size <= process_title.len)
    return -ENOBUFS;

  if (process_title.len != 0) {
    memcpy(buffer, process_title.str, process_title.len + 1);
  }

  buffer[process_title.len] = '\0';

  return 0;
}

That is, if process_title.str is null and thus process_title.line is 0, skip the memcpy step.
I tested it locally and it works just fine as expected. If it sounds good for you, I can create a PR for that. Let me know.

I'm going to guess you didn't call uv_setup_args(), otherwise process_title.str cannot reasonably be NULL.  From the documentation:

Store the program arguments. Required for getting / setting the process title.

It's right above the entries for uv_get_process_title() and uv_set_process_title() but perhaps they should call it out too.

As I said in the issue:

Anyway it's pretty simple to reproduce: do not call uv_setup_args and invoke uv_get_process_title.

Therefore yes, I didn't call it.
Actually gtest doesn't give you access to argc/argv.
Is it normal that the library crashes in this case?
At least it should be documented.

Oh, I see you edited your comment.  It originally said this:

Anyway, uv_set_process_title does a check on process_title.len before to call strncpy and perform its tasks.  Shouldn't uv_get_process_title do something similar?

Which seems okay to me (i.e., PR welcome) but the point about needing to call uv_setup_args() first remains, and yes, that could be improved in the documentation.

Got it. So both a check on process_title.len in uv_get_process_title and a call to uv_setup_args in the setter and the getter.
What arguments should I use to call it if I don't have them exactly?

So both a check on process_title.len in uv_get_process_title and a call to uv_setup_args in the setter and the getter.

No, just a check.  It makes no sense to call uv_setup_args() if you don't have access to argv.
If process_title.len == 0, uv_get_process_title() should probably just copy out an empty string.  The alternative is to return an error but uv_set_process_title() doesn't do that either.

Oh, I thought you meant to call uv_setup_args in those functions. Sorry. You were referring to the client code instead. My fault.
Good. I'll create a PR tomorrow morning with both code and improved doc.
Thank you very much.

The alternative is to return an error but uv_set_process_title() doesn't do that either.

uv_get_process_title() already returns errors, so maybe we should.

As you prefer. They both make sense.
For you know better than me what are the errors in libuv and what they mean, can you suggest the right one in this case?
Let me know what should I put in the PR.
Either an error or an empty strings are acceptable from my point of view.
Anyway, probably it would be better if both the getter and the setter do the same thing, that is (for the setter at least) silently return successfully. Wouldn't it?

uv_get_process_title() already returns errors, so maybe we should.

uv_set_process_title() has a if (process_title.len == 0) return 0; guard.  It's inexplicably inconsistent to make the same condition an error in uv_get_process_title(), IMO.

Fair enough. Maybe something for v2.

Fixed in f2756500


perf counter test improvements

In tests/core/perf_counters/

Some counters generate zero events with the test vectors: PERF_L2_WRITEBACK, PERF_STORE_ROLLBACK, PERF_ITLB_MISS, PERF_DCACHE_MISS, PERF_DTLB_MISS. Modify test so it generates these events.
Add a test to verify the counters continue to increase. Read them three times, with two invocations of the test function between.

I deleted this test in 4209ac27eb4c0056594fad654b34992d78e70527, because it was flaky.


TSM: Check if Hello is coming from peerd

Fixes an issue where the reconnect message would be triggered by a Hello of an arbitrary peer.

Don't forget to change the sequence diagram. Make it clearer what happens when state is added.


sqlx::migrate!() single DB multiple application support

While I was creating a few separate applications that used migrations I ran into this issue:
Error: migration<PHONE_NUMBER>4552 was previously applied but is missing in the resolved migrations

Caused by:
    migration<PHONE_NUMBER>4552 was previously applied but is missing in the resolved migrations

After looking into it it appears that there isn't support for multiple applications to run migrations on the same database. I noticed that there were a couple other issues reporting similar issues:

https://github.com/launchbadge/sqlx/issues/1356
https://github.com/launchbadge/sqlx/issues/946

Although either of these might be able to resolve the issue the first still requires migrations to be run within the same application and the second starts spreading around where migrations live.
I would like to propose that sqlx::migrate!() gain an additional parameter that can specify a unique key/application name/id that can be added as a column and used in the _sqlx_migrations table in the database to separate migrations from one another.
This would support multiple application migrations support while keeping the migration logic in a single place.
Thank you in advance for the consideration.

While I don't think it would be that hard to add something like this, I fear that you're setting up to shoot yourself in the foot doing it this way.
If multiple applications are looking at the same database, you really want a single source of truth for migrations so you don't end up in a situation where you have migrations clobbering each others' work because they touch the same tables but were defined in different parts of the code.
What you could do is have a separate crate specifically to hold and embed the migrations, and then invoke this crate from your applications:
migrations/src/lib.rs:
pub async fn run(pool: &PgPool) -> sqlx::Result<()> {
    sqlx::migrate!().run(pool).await
}

app/src/main.rs:
async fn main() -> anyhow::Result<()> {
    let pool = PgPool::connect("<DATABASE URL>").await?;

    migrations::run(&pool).await?;

    // ...
}

If you want applications to only run migrations that they actually need, then I think we're talking more about having a graph-based resolver for migrations where you can express more complex "depends-on" relationships than you can with the current linear resolver. That sounds really cool to implement but I think it still risks running into the same issue of potential conflicts between sibling migrations.

@abonander I agree that the norm is to have a single source of truth and crate/repository/code that centrally controls your company's schema, but this is not the only use case.
My current use case is I'm building a set of products that companies can use. Each is an individual product/application that I want to make as easy as possible by making it a self contained binary containing the migrations for the specific product/application.
There are several applications I want to do this for that all have their own migrations, however, they are as I said independent and don't have to be deployed together or even at all together. Each individual application also doesn't need a dedicated database due to low throughput/io of some of the applications.
I'm hoping this can be supported otherwise the only other option right now is creating a new database for each application which is both heavy, costly and should be unnecessary.

I'm hoping this can be supported otherwise the only other option right now is creating a new database for each application which is both heavy, costly

Really? It shouldn't be. What database and host are you using?

Yes I know you can create different schema namespaces and DB's in aurora, but it would be nice to not have to distribute the tables all over the place.
Feel free to close if you want there are options, just sub-optimal.

As someone who has started using sqlx for a monorepo that contains multiple services, I would also like to use the migrate! macro to apply migrations within a single postgresDB across segregated schemas.
At the moment, I've patched sqlx-core to accept a schema in the migrate! macro which allows me to run the migrate commands against silo'd schemas. I've only patched postgres, and I think it would take a bit more work to make this reasonable for providers like Sqlite.
While I agree with @abonander in spirit, I do think offering flexibility to allow someone to shoot themselves in the foot is warranted. In particular, if I want to impose a particular segregation scheme, then it's up to me to not screw it up by practicing good hygiene in my DB.
Let me know if you believe providing an optional segregation param to migrate! works as an API, and I'm happy to put together a more carefully considered PR for all the existing providers. In this case, the api would be something like:
migrate!("path/to/migrations", "optional_scheme_prefix")

If multiple applications are looking at the same database, you really want a single source of truth for migrations so you don't end up in a situation where you have migrations clobbering each others' work because they touch the same tables but were defined in different parts of the code.

Caveat emptor -- it's entirely possible to create a migration set for updating database roles and permissions within different schemas to make sure said clobbering of work doesn't happen in the first place. Then all the apps/clients you wish to co-host in the same database are migrated with / accessed by different security roles. In a sophisticated database setup the super admin user isn't used for migrations nor access by services.

I have the same issue.
Has anyone considered using the migrations table as the source of truth? This would require the migrations table to store the sql for each migration and have some sort of sync'ing logic within the CLI/migrator to keep each applications migration files up to date with what is stored in the database.
Before any migration operation is ran, the CLI/migrator would ensure local migration state matches the state of migrations table.
I'm just thinking aloud here, but it seems reasonable for my situation. Maybe it's the dawn of the pseudo-monolith where db state is shared between projects/services and API's aren't always required for them to communicate.
Also, please feel free to tell me if this is a horrible idea and I've lost my mind.


Ready for production?

Hi thanks for the package! I want to use value classes for various ids, say, value class UserId(value: Long) and so on. Thus, I wonder whether you suggest to use this library in production env?

Not recommended for production use.
This project is being developed privately and I will continue to implement experimental features without being willing to make destructive changes for some time.
If you want to use value class in your production code, kotlinx.serialization is probably your only option.
However, the features developed in this project will be incorporated into jackson-module-kotlin in the future, so your use and feedback are welcome.

@k163377 Thank you for the information!

If you want to use value class in your production code, kotlinx.serialization is probably your only option.

I see, thank you! However, my existing codebase is using jackson so I hope to use it ;)

However, the features developed in this project will be incorporated into jackson-module-kotlin in the future

Good job and looking forward to it!


 Once the drilling is done, the door opens and there should either be nukes, coke, or money. In order to do that, I have to make different instances. I made one for the shipping container, then I made one for the nukes.
But, when I used an InstancePoint within the shipping container instance to spawn the nukes, the game would crash every time I hit F10. When I removed the container instance, the game would work.
Steps to reproduce the issue

Create two instances (we'll call them parent and child)
Place the child instance inside the parent instance
Set the child instance to "Mission Placed" and use an InstancePoint to spawn it in on startup.
 Cannot add part wpn_fps_upg_gadget_heartsensor to it.
04:58:10 AM Lua: [Heartbeat Sensor Attachment][ERROR] [WeaponMod] Weapon wpn_fps_ass_acwr2 does not exist. Cannot add part wpn_fps_upg_gadget_heartsensor to it.
04:58:10 AM Lua: [Heartbeat Sensor Attachment][ERROR] [WeaponMod] Weapon wpn_fps_ass_mk17 does not exist.  Cannot add part wpn_fps_upg_gadget_heartsensor to it.
04:58:35 AM Lua: [Heartbeat Sensor Attachment][ERROR] [WeaponMod] Weapon wpn_fps_ass_acwr2 does not exist. Cannot add part wpn_fps_upg_gadget_heartsensor to it.
04:58:35 AM Lua: [Heartbeat Sensor Attachment][ERROR] [WeaponMod] Weapon wpn_fps_ass_mk17 does not exist. Cannot add part wpn_fps_upg_gadget_heartsensor to it.
04:58:35 AM Lua: [ERROR] [Hooks] Could not hook function 'update' (update_menu)
04:58:36 AM Lua: [INFO] Loading mod settings : nil
04:58:38 AM Lua: [BeardLib-Editor] Loading DBPaths
04:58:38 AM Lua: [BeardLib-Editor] DBPaths already loaded
04:58:38 AM Lua: [BeardLib-Editor] Loading Custom Assets to Hashlist
04:58:40 AM Lua: successfully loaded rss feed
04:58:40 AM Log:  (C:\projects\payday2-superblt\src\InitiateState.cpp:96) mods/Twitter Tips/src/tipstweakdata.lua:53: bad argument #1 to 'match' (string expected, got table)
04:58:44 AM Log:  (C:\projects\payday2-superblt\src\http\http.cpp:57) CURL CLOSED
04:58:44 AM Log:  (C:\projects\payday2-superblt\src\xaudio\XAudio.cpp:137) Closing OpenAL XAudio API

Minimal reproduction
big_bomb.tar.gz

Instance Point is not intended to be used inside Instances, Theyre only for positioning instances in your main level.
This issue would also be more an issue with Diesel rather than Beardlib.

I see. What should I do instead?


fix code quality issues

Description
Hi :wave: I work at DeepSource, I ran DeepSource analysis on the forked copy of this repo and found some interesting code quality issues in the codebase, opening this PR so you can assess if our platform is right and helpful for you.
Summary of changes

Remove unnecessary use of comprehension
Remove length check in favour of truthiness of the object
Remove unused global variable
Remove methods with unnecessary super delegation.
Iterate dictionary directly
Add .deepsource.toml to continuously analyze the repo for code quality issues

Sorry, but I don't think we want to add config for another service to the repo, If we do want these kind of code checks we would do it using our existing git hook, but expand the things we check for.
Additionally, I don't think these changes are worth the risk to creating a bug, which admittedly is not very likely, but is still not worth it, especially when these changes don't really seem important. I can see removing the functions that just call super, but everything else doesn't seem an issue, just because one form is used over another. In new code maybe I'd suggest to call if not x rather than if not len(x), but even there it's not a big deal.


[Feature Request] Docker 安装

Describe the feature
https://cloud.tencent.com/developer/article/1701451
Additional context
No response

paperless安装
https://blog.csdn.net/wangwenzhe222/article/details/135698512


Regarding Connection time out

What is the default time for Connection time out. Is there a way, we can customise the timeout variable based on the requirements.

@rajgorantla9  Have resolved this. Added option to add connecttimeout in Downloaderconfig


support updated cargo component

Bindings generator in the graph crate is no longer valid with the updated version of cargo-component, which no longer supports the bindgen macro.
I believe this resolves #14.

Thanks for the fix!


PriorBox layer

Hi @chuanqi305 ,
I saw there has step in weiliu's PriorBox layer but it doesn't exist in your prototxt. Is this intentional?

The default step is img_width / layer_width, img_height / layer_height.
For the first step, 300 / 19 = 15.

OK, I think I have to read the code . Thanks!


Investigate Git Webhook proxy setup for CI server

User Story

As a [user role below]:
IBM.com Library Devops

I need to:
set up webhooks for Github on our CI server behind a firewall

so that I can:
disable polling of the repo

Additional information

Due to the number of jobs we run, we are running into rate limiting caps for our functional ID user. Creating a webhooks proxy server may mitigate this issue.
one possible solution: https://github.com/stakater/GitWebhookProxy
another solution: https://lmammino.github.io/webhook-tunnel/
Jobs that require the authenticated public user are the only ones needed here (mainly for deploy previews), but would be ideal for all public repo polling.

Acceptance criteria

[ ] Webhook proxy created
[ ] Jenkins jobs adjusted to use webhooks instead of polling

@RobertaJHahn moving this one out.

@RobertaJHahn I'm iceboxing this, I already offloaded a lot of the CI to Github Actions, so this doesn't appear to be a huge issue at the moment.

@RobertaJHahn bringing this in. I stumbled on documentation for TAAS Jenkins that would actually help out a lot, I'm almost done reconfiguring our CI to use web hooks instead.

Related documentation: https://taas.cloud.ibm.com/guides/jenkins-trigger-build-from-github-webhooks.md


Upating of date

Dear @lisphilar ,
Please help me in updating date in following scenario's....,actually i want to add date as per my wish..
1)ind_scenario = cs.Scenario(jhu_data, pop_data, "India")
ind_scenario.records().tail()
2)ind_scenario.trend()
With regards,
Rakesh

I replied this issue in #123


Updated publication date for azps 8.0.0 release

Docs Build status updates of commit 305122a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-conceptual/azps-8.0.0/release-notes-azureps.md
:warning:Warning
View (azps-8.0.0)
Details

docs-conceptual/azps-8.0.0/authenticate-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/az-powershell-proxy.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/az-predictor.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azps-msgraph-migration-changes.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azps-versioning-release-cadence.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-in-docker.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-support-lifecycle.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-vm-tutorial.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/context-persistence.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/faq.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/formatting-output.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/get-started-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/index.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/install-az-ps-msi.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/install-az-ps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/manage-azure-resources-invoke-azrestmethod.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/manage-subscriptions-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-1.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-2.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-3.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-4.1.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-5.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-6.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

This comment lists only the first 25 files in the pull request.

docs-conceptual/azps-8.0.0/release-notes-azureps.md

Line 1158, Column 12: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/dotnet/api/system.runtime.loader.assemblyloadcontext' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 1771, Column 255: [Warning: insecure-link - See documentation] Link 'http://aka.ms/azpslifecyle' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 4011, Column 77: [Warning: file-not-found - See documentation] Invalid file link: 'aka.ms/InstallASHPowerShell'.
Line 5269, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 5676, Column 5: [Warning: hard-coded-locale - See documentation] Link 'https://docs.microsoft.com/en-us/rest/api/monitor/scheduledqueryrules' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 5729, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 5833, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 5890, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 5947, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6002, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6076, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6109, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6127, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6213, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 6275, Column 63: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/blog/completers-in-azure-powershell/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 930, Column 152: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'string' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 1158, Column 12: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/en-us/dotnet/api/system.runtime.loader.assemblyloadcontext' will be broken in isolated environments. Replace with a relative link.
Line 1186, Column 109: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'String' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 1262, Column 99: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'String' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 1263, Column 7: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/powershell/module/az.aks/get-azakscluster' will be broken in isolated environments. Replace with a relative link.
Line 1266, Column 24: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'String' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 3480, Column 25: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/rest/api/aks/managedclusters/getaccessprofile' will be broken in isolated environments. Replace with a relative link.
Line 3480, Column 133: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/rest/api/aks/managedclusters/listclusteradmincredentials' will be broken in isolated environments. Replace with a relative link.
Line 3480, Column 241: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://docs.microsoft.com/rest/api/aks/managedclusters/listclusterusercredentials' will be broken in isolated environments. Replace with a relative link.
Line 3717, Column 105: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SubResource' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

Docs Build status updates of commit 37e603e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-conceptual/azps-8.0.0/release-notes-azureps.md
:warning:Warning
View (azps-8.0.0)
Details

docs-conceptual/azps-8.0.0/authenticate-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/az-powershell-proxy.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/az-predictor.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azps-msgraph-migration-changes.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azps-versioning-release-cadence.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-in-docker.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-support-lifecycle.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-vm-tutorial.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/context-persistence.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/faq.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/formatting-output.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/get-started-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/index.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/install-az-ps-msi.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/install-az-ps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/manage-azure-resources-invoke-azrestmethod.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/manage-subscriptions-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-1.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-2.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-3.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-4.1.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-5.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-6.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

This comment lists only the first 25 files in the pull request.

docs-conceptual/azps-8.0.0/release-notes-azureps.md

Line 1771, Column 255: [Warning: insecure-link - See documentation] Link 'http://aka.ms/azpslifecyle' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 4011, Column 77: [Warning: file-not-found - See documentation] Invalid file link: 'aka.ms/InstallASHPowerShell'.
Line 5269, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).
Line 930, Column 152: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'string' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 1186, Column 109: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'String' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 1262, Column 99: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'String' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 1266, Column 24: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'String' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 3717, Column 105: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SubResource' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.
Line 3717, Column 127: [Suggestion: disallowed-html-tag - See documentation] HTML tag 'SubResourceWithColocationStatus' isn't allowed.  Replace it with approved Markdown or escape the brackets if the content is a placeholder.

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

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

File
Status
Preview URL
Details

docs-conceptual/azps-8.0.0/release-notes-azureps.md
:warning:Warning
View (azps-8.0.0)
Details

docs-conceptual/azps-8.0.0/authenticate-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/az-powershell-proxy.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/az-predictor.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azps-msgraph-migration-changes.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azps-versioning-release-cadence.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-in-docker.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-support-lifecycle.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-vm-tutorial.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/context-persistence.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/faq.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/formatting-output.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/get-started-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/index.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/install-az-ps-msi.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/install-az-ps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/manage-azure-resources-invoke-azrestmethod.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/manage-subscriptions-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-1.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-2.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-3.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-4.1.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-5.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-6.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

This comment lists only the first 25 files in the pull request.

docs-conceptual/azps-8.0.0/release-notes-azureps.md

Line 5269, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

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

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

File
Status
Preview URL
Details

docs-conceptual/azps-8.0.0/release-notes-azureps.md
:warning:Warning
View (azps-8.0.0)
Details

docs-conceptual/azps-8.0.0/authenticate-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/az-powershell-proxy.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/az-predictor.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azps-msgraph-migration-changes.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azps-versioning-release-cadence.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-in-docker.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-support-lifecycle.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/azureps-vm-tutorial.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/context-persistence.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/create-azure-service-principal-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/faq.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/formatting-output.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/get-started-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/index.yml
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/install-az-ps-msi.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/install-az-ps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/manage-azure-resources-invoke-azrestmethod.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/manage-subscriptions-azureps.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-1.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-2.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-3.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-4.1.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-5.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

docs-conceptual/azps-8.0.0/migrate-az-6.0.0.md
:white_check_mark:Succeeded
View (azps-8.0.0)

This comment lists only the first 25 files in the pull request.

docs-conceptual/azps-8.0.0/release-notes-azureps.md

Line 5269, Column 1: [Warning: code-block-indented - See documentation] Indented code blocks aren't allowed. Use a Markdown code block surrounded by triple backticks (```).

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


rig library (add|default) panic

I'm a n00b with rig but I dig the idea.
I'm trying to wrap my head around it, and want to tie a specific library as a default for a particular R version. Lots of my work leverages bioconductor mojo, so I'm also interested in tying default libraries to default versions based on their norms as well.
So, the current release of bioconductor is 3.18, and is tied to R version 4.3 ... they will upgrade to 3.19 (with R4.4 any day now, tho).
So I'm currently using R 4.3:
$ rig list
* name       version    aliases
------------------------------------------
  4.2-arm64  (R 4.2.2)
* 4.3-arm64  (R 4.3.3)
  4.4-arm64  (R 4.4.0)  release

And I'd like to set a bioc3.18 library as the default for R 4.3:
$  rig library list
bioc3.18
main (default)

So I do:
$ rig library default bioc3.18

But I'm greeted with this error:
thread 'main' panicked at /Users/gaborcsardi/.cargo/registry/src/index.crates.io-6f17d22bba15001f/clap_builder-4.5.2/src/parser/error.rs:32:9:
Mismatch between definition and access of `lib-name`. Could not downcast to TypeId { t:<PHONE_NUMBER>60759320943513204350442872190 }, need to downcast to TypeId { t:<PHONE_NUMBER>427391105921880143968470858 }

Now I reckon I may have cast the wrong rig library default spell, but I feel like that particular error message is telling me there's something else cooking that could use a fix either way :-)
Thanks!

This is a bug indeed, thanks for reporting it! Using the previous version of rig will probably fix this, if you can install that.


Support Tokens in Page Mapping

Category
[ ] Bug
[X] Enhancement
Problem Area
[ ] Page Transformation: Error during the setup/use of the Page Transformation UI solution (did you check our troubleshooting guide?)
[X] Page Transformation: Error during the use of page transformation from PnP PowerShell
[ ] Page Transformation: Error during the use of page transformation from .Net
[ ] Page Transformation: Page is not looking correct after transformation
[ ] Modernization Scanner: something went wrong...
Expected or Desired Behavior
Consider adding tokenization to the mapping file to populate properties like Header type in PowerShell before passing the mapping file into ConvertTo-PnPClientSidePage.
A mechanism much like the properties you can pass to PnP Provisioning that replace values prior to processing the file.
This would reduce the number of duplicate mapping files for variants of a transformation based on criteria, see ref #459 for details of a recent scenario example.

@pkbullock , @mbice,
Simple token support (non nested simple tokens in webpartmapping.xml and your page layout mapping files) in combination with having an option to pass them along on the PS commandline shouldn't be hard to build. I'm OOF until April 20th, but will assign this to the May release for now.

I will be starting this one next, sorry missed June release.