remove comments from training data

i am currently training reformer on python code, from scratch, and it seems to be struggling the most with the code comments. i read in a paper... i think it was codeBERT? (https://arxiv.org/pdf/2002.08155.pdf) that they remove all comments from the codesearchnet dataset for some part of the training and im starting to think that would make sense. but im not sure how to reliably do that for any programming languages. im wondering if anyone knows of a good library for parsing the languages in the codesearchnet dataset.

i think if i were training a model pretrained on text (like gpt2), it would probably be better at learning comments.

i recently found this bit of code which seems like it could be useful for this task, im going to leave it here for now, im super busy lately but i havent forgotten about this project https://code.activestate.com/recipes/578178-colorize-python-sourcecode-syntax-highlighting/?in=user-178123


write temporary secret files to temp dir

To avoid writing these temporary files in current working dir. On my environment, os.Remove() does not work well due to error 32 (windows) which means file is used by other process, maybe antivirus scanning. Therefore secrets*.yaml files are left behind in working dir.

Thanks for your contribution! I think #2023 is the successor to this change. Let's close this one and get #2023 done


fix: add configurable clickhouse volume size

This PR creates a setting to allow to control the clickhouse volume size: CLICKHOUSE_VOLUME_SIZE

Thanks for the pull request, @Ian2012!  Please note that it may take us up to several weeks or months to complete a review and merge your PR.
Feel free to add as much of the following information to the ticket as you can:

supporting documentation
Open edX discussion forum threads
timeline information ("this must be merged by XX date", and why that is)
partner information ("this is a course on edx.org")
any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.
Please let us know once your PR is ready for our review and all tests are green.

@Ian2012 🎉 Your pull request was merged!  Please take a moment  to answer a two question survey so we can improve your experience in the future.


A way to redact text

Description
In some documents, especially legal documents, it is important to redact information with the content removed from the output pipeline so it can not be recovered. At the same time, it is important to provide a visual indication of the redacted information, and to do so in various formats. The most basic redaction is a black line that starts within a text paragraph to the end of the line. There is no indication of word length within the redacted text.
Some prior solutions tried to use the highlight function, but it does not hide the content (and does not work well with hide presently) and also does not hide the size of the redacted words, like here:

Use Case
The hide function seems to do exactly what is required, but its content is literally hidden and does not provide a visual indication of a deliberate redaction. It would be important for legal text if hide includes a fill argument that is customizable to provide this. #hide(fill: black, content) is the minimum needed, and should be easy to implement.

It would probably make sense to also include the other standard highlight arguments like stroke, etc. For example, a draft document could mark proposed redactions like this:

Isn't something like this already working?
// simple redaction
#let redact(body, color: black) = box(hide(body), fill: color)
// redaction as in the issue
#let redactre(body, color: black) = {
  show regex("[^\s]"): it => redact(it)
  body
}

Isn't something like this already doing the job?
// simple redaction
#let redact(body, color: black) = box(hide(body), fill: color)
// redaction as in the issue
#let redactre(body, color: black) = {
  show regex("[^\s]"): it => redact(it, color: color)
  body
}

That does not hide the size of redacted words

Then I do not understand what the intent is. By using "." as the regex expression, however, everything would be marked.

The regex approach still leaks information in the PDF output because the boxes contain information about the size of the glyphs or words. See https://www.wired.com/story/redact-pdf-online-privacy/

“Even if you do the redaction, supposedly correctly, even if you remove the text, there’s a lot of latent information that is dependent on the content that was redacted, and even that can leak information,” Levchenko says. “If you redact a name in a PDF, if the attacker has any context—they know this is an American—they will be able to, with high probability, either recover that name or narrow it down to a very small list of candidates.”

Edact-Ray focuses on the size of glyphs (broadly, characters or letters) and their positioning. “It’s pretty clear to a lot of people that the letter ‘L’ is skinnier than a letter ‘M,’ and that if you redacted just the letter ‘L,’ then you might be able to tell it is different from a redaction with just the letter ‘M,’” Bland says. The tool is essentially able to automatically compare the size of the redaction and the position of the letters with a predefined “dictionary” of words to estimate what has been replaced.

The code below shows the several issues. The first paragraph shows how #hide properly spaces, but does not communicate that there was a redaction. The second shows #box breaks the line if the selected overlaps into the next line. The third paragraph shows how #regex leaks the size of the glyphs in letters or words into the PDF file (even if it appears as all black that runs together).
// simple redaction
#let redact(body, color: black) = box(hide(body), fill: white, stroke: red)

// redaction as in the issue
#let redactre(body, color: black) = {
  show regex("."): it => redact(it, color: color)
  body
}

#box(stroke: black, inset: 1em)[#lorem(10) #lorem(10) #lorem(5)]

`#hide`
#box(stroke: black, inset: 1em)[#lorem(10) #hide(lorem(10)) #lorem(5)]

`#box`
#box(stroke: black, inset: 1em)[#lorem(10) #redact(lorem(10)) #lorem(5)]

`#regex`
#box(stroke: black, inset: 1em)[#lorem(10) #redactre(lorem(10)) #lorem(5)]

Well I guess one could create a broken/bad implementation by start & end point, text height, content size and line spacing measurements, but a good solution seems not possible to me with the current typst version.

How about something like this?
The function redact measures the width of the text that is to be redacted (say, 3.213cm), then it rounds that width to an integer millimetre (32mm) and creates that many 1mm-wide black boxes to fill the space.

The output pdf should not contain the text (though I don't know enough about Typst's internals to guarantee that).
You have a black bar that breaks at lines, but only tells an adversary roughly how wide the redacted text was (no information about individual glyphs).

I also tried to measure how much space is left on the current line (with layout, here().position(), etc.) but didn't succeed. If this was known, we could output one appropriately-sized black box per line (instead of one box per millimetre).
#set page(paper: "a6")

#let redact-box(width) = {
  box(rect(height: 1em, width: width, fill: black, stroke: none))
}

#let redact(size: none, body) = context {
  if size != none {
    redact-box(size)
  } else {
    let redact_size = measure(body) // size of the text that is to be redacted
    let redacted = int(redact_size.width.mm()) // width in number of mm's
    // create a 1mm-box for each mm
    for i in range(redacted) {
      redact-box(1mm)
    }
  }
}

Pursuant to Federal Circuit Rule 47.4, counsel for Petitioner certifies
the following:
1. The full name of the party represented by me: #redact[Public Co.], Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magnam aliquam quaerat voluptatem. Ut enim aeque doleamus animo, cum corpore #redact(size: 2cm)[dolemus], fieri tamen permagna accessio potest, si aliquod aeternum et infinitum impendere malum nobis opinemur.
2. Quod idem licet transferre in voluptatem, #redact[ut postea variari voluptas distinguique possit, augeri amplificarique non possit. At etiam Athenis, ut e patre audiebam] facete et urbane Stoicos irridente, statua est in quo a nobis philosophia defensa et collaudata est, cum id, quod maxime placeat, facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Temporibus autem quibusdam et.


Thanks!

Hi, and thank you!
Would you be able to add instructions as to how to use this functionality?
Thanks!

Hi @TheChildishMillennial  sorry to bug you, would you be able to outline the steps to run this code with an ONNX model?


Found error in contributing.md [Documentation]

Hi @avinashkranjan, I am a part of Gssoc'23 as a contributor.
Reference Screenshot

AIM

I would like to contribute to this project by updating the contributing.md file.
To remove the above highlighted writing error.

Any suggestion or guidance is welcomed.

Go Ahead @sam-arth07


Upgraded the projects to target net6.0 instead of net5.0

Update target for ScintillaNET from net40 to net45 that is supported by the Scintilla.NET <IP_ADDRESS> Changed the reference to the Scintilla.NET <IP_ADDRESS>, that is currently supported

Thank you 👍

Thanks, Petteri Kautonen for accepting the PR
On Sun, 5 Feb 2023 at 16:57, Petteri Kautonen @.***>
wrote:

@.**** approved this pull request.
—
Reply to this email directly, view it on GitHub
https://github.com/VPKSoft/ScintillaNET-FindReplaceDialog/pull/2#pullrequestreview-1284188223,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAY56A3XTE4OXWJOR52TGNLWV6FC3ANCNFSM6AAAAAAUKVFIXA
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


remove vendor dependency for bulid/test/lint rules in Makefile

Normally when building the binary and running make, it's expected to build from local vendor dependencies instead of having to retrieve dependency update remotely. With this change, it allows user to build locally without having a internet connection. For glide update, we could still use make vendor.

@zshi-redhat One little concern with this.
For example, say, someone updated their vendor with newer packages and trigger vendor update with make vendor. The subsequent make won't build the binary unless make clean is run because vendor is not a prerequisites. But I see your point there, build should be run with whatever in the vendor/ and it should not require to fetch them during build. But at minimum we should have a check that vendor/ exist before any build or else build may fail.
We could leave the vendor as order-only-prerequisites as described here. Wdyt?

@zshi-redhat One little concern with this.
For example, say, someone updated their vendor with newer packages and trigger vendor update with make vendor. The subsequent make won't build the binary unless make clean is run because vendor is not a prerequisites.

Yes, you're right, I didn't think that far, we'll have to first clean the environment and make after vendor packages be updated. do you think we can add another rule that is specific to vendor file update and replace current vendor rule with the new one in build/lint/test dependencies?
But I see your point there, build should be run with whatever in the vendor/ and it should not require to fetch them during build. But at minimum we should have a check that vendor/ exist before any build or else build may fail.

We could leave the vendor as order-only-prerequisites as described here. Wdyt?

+1, this is better than just removing the vendor dependencies.

@zshi-redhat One little concern with this.
For example, say, someone updated their vendor with newer packages and trigger vendor update with make vendor. The subsequent make won't build the binary unless make clean is run because vendor is not a prerequisites.

Yes, you're right, I didn't think that far, we'll have to first clean the environment and make after vendor packages be updated. do you think we can add another rule that is specific to vendor file update and replace current vendor rule with the new one in build/lint/test dependencies?

Considering the number of files under vendor is large, detecting the change of each file is time-consuming when just running make;  I assume it's better not have rule for vendor file update.

But I see your point there, build should be run with whatever in the vendor/ and it should not require to fetch them during build. But at minimum we should have a check that vendor/ exist before any build or else build may fail.

We could leave the vendor as order-only-prerequisites as described here. Wdyt?

+1, this is better than just removing the vendor dependencies.

@ahalim-intel Just realized that with vendor in the order-only-prerequisites, it will still be evaluated and corresponding commands will be executed. perhaps we want to just remove the vendor from rules.


Unable to use Ji on macOS 10.13.4

macOS 10.13.4
Xcode 9.3
My application uses "honghaoz/Ji" version "2.1.0".
When I compile my application, I get the following error:
Module compiled with Swift 4.0.3 cannot be imported in Swift 4.1: /Users/[...]/Projects/[...]/Carthage/Build/Mac/Ji.framework/Modules/Ji.swiftmodule/x86_64.swiftmodule
Is there a newer version of "honghaoz/Ji" available that supports Swift 4.1?
Thanks

Sorry to comment on my own post, but I found that if I ran the command:
carthage update Ji --platform macOS --no-use-binaries
it worked correctly.  I am not sure if this a proper fix, so maybe we do need a newer version of Ji that works with Swift 4.1 (macOS 10.13.4, Xcode 9.3)

Swift now has been upgraded to support Swift 5.0: https://github.com/honghaoz/Ji/tree/5.0.0


LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443

Bug Description
when I use yarn create eth-app my-eth-app, it reported an error:

Error log

"error Command failed.
Exit code: 128
Command: git
Arguments: fetch --tags
Directory: /Users/coln/Library/Caches/Yarn/v6/.tmp/166c4037ddf7608d79e84e263dcd7746
Output:
fatal: 无法访问 'https://github.com/edgeandnode/gluegun.git/'：LibreSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Error: Client network socket disconnected before secure TLS connection was established
    at connResetException (node:internal/errors:683:14)
    at TLSSocket.onConnectEnd (node:_tls_wrap:1577:19)
    at TLSSocket.emit (node:events:406:35)
    at endReadableNT (node:internal/streams/readable:1329:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Error: Client network socket disconnected before secure TLS connection was established
    at connResetException (node:internal/errors:683:14)
    at TLSSocket.onConnectEnd (node:_tls_wrap:1577:19)
    at TLSSocket.emit (node:events:406:35)
    at endReadableNT (node:internal/streams/readable:1329:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Aborting installation.
yarnpkg install --cwd /Users/coln/www/127/tech/create-eth-app/my-eth-app has failed.
error Command failed.
Exit code: 1
Command: /usr/local/bin/create-eth-app
Arguments: my-eth-app
Directory: /Users/coln/www/127/tech/create-eth-app
Output:
info Visit https://yarnpkg.com/en/docs/cli/create for documentation about this command."

My local network is accessible to GitHub. Also I can git clone https://github.com/edgeandnode/gluegun.git.
Steps to Reproduce
yarn create eth-app my-eth-app
Expected Behavior
create eth-app successfully

Hi @lcoln, can you share your environment please?

OS version
Node.js version
Yarn version

Plus any other details that you think might be relevant. Thank you!

it was because gluegun repo has renamed their branch name from Master to Main...


Migrate::execute() now returns exit code

Hi. I just made it so that it returns 1 if the environment doesn't exist, and 0 for everything else.
It would probably be nicer to get a status from the actual migrations to see if they ran correctly, but I haven't looked into that.

Seems to be related to #739.

Thanks for your contribution! In the future please follow these rules when making PRs for this project. Setting up a tool like static-review can help you verify your commits.


Automatically add timestamp

I found that I can't add time automatically by clicking the check box. Time only can be added via shortcut keys or commands. Is this normal?
I wonder if it is possible that when I set a line of text as to-do, it will add an timestamp automatically. When I click this checkbox ,It will add an end timestamp automatically.

@yoghurtdewdew

I found that I can't add time automatically by clicking the check box. Time only can be added via shortcut keys or commands. Is this normal?

It works in my environment🤔
Are the cssclasses set on the target note?

I wonder if it is possible that when I set a line of text as to-do, it will add an timestamp automatically. When I click this checkbox ,It will add an end timestamp automatically.

It seems like it would be difficult to determine if the checkbox was created, as it may require complex steps...
Wouldn't it be better to enable the doing(in Progress) status?

Thank you very much for your reply! So I need to add css to realize clicking the checkbox to add a timestamp?
But I'm still confused. Css would change the display, would it change some characters at the same time? I see from you that clicking once adds a timestamp and then click the second time to add an ending timestamp. But for checkbox, I think click the second time would make - [x]change to - [ ]? As clicking on it the first time would set this checkbox as - [x].
In addition, for automatic identification of checkbox, I think here is a reference https://github.com/Quorafind/Obsidian-Time-Counter-Releases .
I used to like it very much, but there is something wrong with its css at present.
Actually, I really want to realize a calculate of time duration. This will give me a better understanding of the length of time I spend on all kinds of things.

@yoghurtdewdew

So I need to add css to realize clicking the checkbox to add a timestamp?
But I'm still confused. Css would change the display, would it change some characters at the same time?

Clicking on the checkbox time tracker only works on pages that have the CSS class you set in CSS classes for track.
By default, clicking is only possible on pages that have the CSS classes checkbox-time-tracker and ctt applied.
Below is an example.

This is to ensure that the plugin is only applied on certain pages. On some pages, you may want to use the default checkbox function without measuring time.
Using CSS classes was confusing and may have been a mistake. Sorry.

I see from you that clicking once adds a timestamp and then click the second time to add an ending timestamp. But for checkbox, I think click the second time would make - [x]change to - [ ]? As clicking on it the first time would set this checkbox as - [x].

Do you have Enable doing status turned on?
You may be able to achieve the behavior you want by setting it like this:

The first time you click, - [ ] becomes - [/] and the start time is recorded.
The second time you click, - [/] becomes - [x] and the end time is recorded.
like below

In addition, for automatic identification of checkbox, I think here is a reference Quorafind/Obsidian-Time-Counter-Releases .

Thanks for sharing! I'll take a look!


Error RN 17.0.1

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/react
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/gridjs-react
npm ERR!   gridjs-react@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!

Still an issue. Had to use --legacy-peer-deps for installing Grid.js to my React application.

@amatzen i created @naterkane/gridjs-react-17 in the interim to provide coverage until the PR to this repo is accepted. The only change is a patch version and a slightly different range for react as a peer dependency

Thank you @naterkane ! I'll just mention your PR then to link the issue together with the PR #307


Allowed container images regex field, examples and syntax validation required.

Describe the bug
Allowed container images regex field, examples and syntax validation required.
The help for this field shows
"The RegEx rule used to match allowed container images in a Kubernetes cluster. For example, to allow any Azure Container Registry image by matching partial path: ^.+azurecr.io/.+$"
but is not considering the right syntax for multiple items, what would be a good example to multiple items, which is a good separator to be used?
To Reproduce
Steps to reproduce the behavior:
1 from azure portal , search for security center
2 from the left column click on security policy
3 select the subscription
4 click on view effective policy button
5 from top of next page , select ASC default.... the policy with hyperlinked text.
6 On next screen select Parameters.
Expected behavior
A clear and concise description of the syntax, a validation check for the syntax that explains the format expected to be entered in the field.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information if applicable):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Hi @porrascarlos802018
your issue seems to be related to Azure Security Center, not to an automation artifact within this repository. Unfortunately, we cannot provide product support for Azure Security Center in GitHub. If you feel this is a bug, please file an Azure Security Center support ticket or join the Azure Security Center TechCommunity for community support.

Closing this issue as it is not related to a Github artifact.


official doc page Running Containers on ECS Fargate tutorial doesn't work anymore

tutorial obsolete.
Expected behavior

tutorial thru
Current behavior

complaining about VPC not set up and errror out
Steps to reproduce

follow the tutorial and get example code in place
run "pulumi up"
see the error output

Context (Environment)

ubuntu 16.04 in virtualbox
Affected feature

bad publicity.
even example in this repo need extra setup.

Sorry guys for replying late...  I tried aws-py-fargate and this guide
https://www.pulumi.com/docs/tutorials/aws/ecs-fargate/


@ashfurrow => Everything

Use real images for the slideshow, show blank logo when the app is loading if not for the first time

Polish to the Show Locations VC

Shows have multiple pages:

Install Shots
Artworks
Metadata

Adds an Artworks VC when clicking on an Artwork in a Show

Adds an About VC for requesting a link to the app store

Looks :100: to me – merge when you're comfortable.

Cool, I've addressed feedback in the next PR


[Bug report] Commit message is converted from uppercase to lowercase

✅ Checklist

[X] I am using the latest version
[X] I have searched FAQ

📄 System Info
System:
    OS: Windows 11 10.0.22621
    CPU: (12) x64 Intel(R) Core(TM) i5-10500 CPU @ 3.10GHz
    Memory: 16.48 GB / 31.77 GB
  Binaries:
    Node: 20.10.0 - ~\AppData\Local\fnm_multishells\3712_1708410516510\node.EXE
    Yarn: 1.22.21 - ~\AppData\Local\fnm_multishells\3712_1708410516510\yarn.CMD
    npm: 10.2.3 - ~\AppData\Local\fnm_multishells\3712_1708410516510\npm.CMD
    pnpm: 8.12.0 - ~\AppData\Local\fnm_multishells\3712_1708410516510\pnpm.CMD
  npmPackages:
    czg: ^1.8.0 => 1.8.0

🔎 Description
Concise Description
Commit message is converted from uppercase to lowercase
Expected behavior
Steps to reproduce
Screenshots or Screen Recording(if possible)

🔗 Reproduction link / repo:
No response

https://cz-git.qbb.sh/config/engineer#uppercasesubject

https://cz-git.qbb.sh/config/engineer#uppercasesubject
For unification, prevent members from appearing in case confusion at the short subject. Avoid using uppercase at the beginning, or switch configurations.

Thanks for answering

I want close this rule, let subject based on user input, how can I do?


Support for Mounts

Clear and concise description of the problem
As a developer looking to use a tool to compile my HTML, like 11ty, I'd like to keep the compiled HTML directory separate from my asset directory so I don't need to juggle my compiled HTML in my Vite root.
Suggested solution
Add support for something similar to Snowpack mounts
Alternative
My current solution is compiling my HTML into my project root. git ignoring the compiled HTML, and deleting all of the compiled HTML using globing and then finding and deleting just the empty directories, which can be unreliable.
Additional context
Full configuration for this is available in this blog post

I think instead of another option, it would be better if this can be solved through a Vite plugin by mapping virtual HTML files to separate 11ty HTML files. This is blocked by https://github.com/vitejs/vite/issues/2321 however, but we could close this in favour of that issue.


Fix WaitForAvailableCinderVolume() to polling

This PR fix function WaitForAvailableCinderVolume() to polling check volume status, get volume every 3 seconds and up to 10 times
This PR closes #427

@aglitke , thanks for your comments. I had fixed it. please help review

@aglitke , we do not  have UT both for vsbroker.go and actions.go. So should I add UT in this PR or another one?

@chestack No need to test the vsbroker or actions directly.  What I mean is that we should test the provision flow in a few situations where polling for the volume may succeed or fail.  You can test these cases by overriding a new GetVolume interface just like we do for some of the other provisioner tests.

/lgtm
cc @childsb for merge

@chestack please rebase and ping us when ready for merge

@rootfs @childsb , has rebased, please review.


upd: timeline

PR

Types of changes

[x] New feature

Description

Checklist

[x] added: new content
[x] upd: old info

 Created from VS Code using CodeStream

Testing


Don't leave leftovers

https://github.com/NayamAmarshe/gameready/blob/4d21fbfa4f7eb2775f62d4fcc159e5dc9784de23/gameready.sh#L43
You are pre-checking if there's already a folder but not deleting it after cloning

Thanks a lot! Fixed :)


When run app with new version of *.js, error occurs

Error occurs when use SignalR with new version of  *.js

Visual Studio: Version 15.9.11, Mivrosoft Visual Studio Community 2017
jQuery: Scripts/jquery-3.3.1.min.js
signalR: Scripts/jquery.signalR-2.2.2.min.js
Chrome

I just create this app the same step with this doc, but get new version of jQuery and signalR.js, when I run the app with Script Debugging: Enabled, Chrome get some error:

Uncaught TypeError: Cannot read property 'client' of undefined
Failed to load resource: the server responded with a status of 404 (Not Found)  hubs 1

The code of  ChartHub.cs and index.html just copy from this doc.
When the app is not running, the Solution Explorer is:

And when the app is runnig, the Solution Explorer is:

I am newer of c# and asp.net, please help me, thank you!

I solution this issue, this is link:
https://code.msdn.microsoft.com/SignalR-Getting-Started-b9d18aa9/view/Discussions#content


Tries and fails to change ownership, when ownership is already fine.

/ # ls -nd data downloads passwd
drwxrwxrwx    5 1000     1000             5 Feb 25 03:17 data
drwxrwxrwx    2 1000     1000             2 Feb 24 01:22 downloads
drwxrwxrwx    2 1000     1000             2 Feb 24 01:22 passwd
And yet the container tries to change the ownership and fails
rtorrent-rtorrent-rutorrent-1  | [cont-init.d] 01-fix-uidgid.sh: exited 0.
rtorrent-rtorrent-rutorrent-1  | [cont-init.d] 02-fix-perms.sh: executing...
rtorrent-rtorrent-rutorrent-1  | Fixing perms...
rtorrent-rtorrent-rutorrent-1  | chown: changing ownership of '/data': Operation not permitted
rtorrent-rtorrent-rutorrent-1  | chown: changing ownership of '/data/rtorrent': Operation not permitted
rtorrent-rtorrent-rutorrent-1  | chown: changing ownership of '/data/rutorrent': Operation not permitted
rtorrent-rtorrent-rutorrent-1  | chown: changing ownership of '/downloads': Operation not permitted
rtorrent-rtorrent-rutorrent-1  | chown: changing ownership of '/passwd': Operation not permitted
rtorrent-rtorrent-rutorrent-1  | [cont-init.d] 02-fix-perms.sh: exited 1.
rtorrent-rtorrent-rutorrent-1  | [cont-finish.d] executing container finish scripts...
rtorrent-rtorrent-rutorrent-1  | [cont-finish.d] done.
rtorrent-rtorrent-rutorrent-1  | [s6-finish] waiting for services.
rtorrent-rtorrent-rutorrent-1  | [s6-finish] sending all processes the TERM signal.

@esiefker did you ever solve this issue?


cmd/cgo: incomplete "go tool fix -r cftype" suggestions

Go 1.10 introduces some changes to cgo, but I ran "go tool fix -r cftype" and still got compilation failures. Is the team still interested in improving the heuristics for "go tool fix"? I'm just an end user of a lot of these libraries, I haven't done that much with cgo and I'm not sure how to fix them.
Running "go tool fix" on this package makes some changes but there are still a number of compilation failures: https://github.com/keybase/go-keychain/issues/19
Also the "remaining change" listed here: https://github.com/golang/text/commit/572a2b141f625f4360cf42a41a43622067e0510b
Feel free to close as "this library needs to do some work, go tool fix is relatively complete."

CC @randall77


Add pixel_size parameter to segmentation with BABY

Description:
Add pixel_size parameter to segmentation with BABY

Solved with https://github.com/SchmollerLab/Cell_ACDC/commit/d21e8ef6b549372b7c9c421e9edfb3c009e69931


[WIP] Finalize Readme

Closes #60
Summary
Add description about why the deployment was created and who it is for, as well as a guide on how to deploy to azure

@SaladRaider do you still want to merge this?

Going to close this since I think Peter is working on unifying docs in a separate PR? Re-open if needed :)


Set memory resource limits in InfluxDB Edge

A user should be able to set how much memory the buffer will use and how much overall it can use. This way if a query or something would use too much we can stop it rather than proceeding unbounded and getting an OOM.

I'm having the same problem, the task is running and bring the container and VM on it's knees, there should be a limit on the amount of memory the process can use so it can do backpressure on batch size and still keep working without stopping the whole sistem, worst of all the ingestion of data.

@valeriob this issue is marked for version 3. If you're running tasks, you're using version 2. Unfortunately, we won't be able to add this kind of functionality to v2.

It's ok in version 3, as long as the migration path is smooth :D


RDKB-54270:Changing the zebra-restart event name when lanmanager distro enabled

Reason for change: Zebra-restart will be replaced with dhcpv6_raserver-restart
Test Procedure: 1. Lanmanger event should get triggered when
lanmanager distro is enabled
2. ra.conf file gets created Risks: None
Signed-off-by<EMAIL_ADDRESS>

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.rhegde114 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @guto86 , Can you please merge this change
Thanks


Unable to flash Zoozee SE131 smart wlan plugs

Trying to flash Zoozee SE131 without any luck, someone have an idea?
Flashing light goes either to solid, or off when trying to flash.
https://www.amazon.de/gp/product/B07J2CT8WL/ref=ppx_yo_dt_b_asin_title_o03_s00?ie=UTF8&psc=1
but only getting the following:
Starting pairing procedure in screen
RTNETLINK answers: File exists
~/tuya-convert
Waiting for the upgraded device to appear
If this does not work have a look at the '*.log'-files in the 'scripts' subfolder!
..........................................................................................................................
redone the pi several times  with strech and tried ct-Open-Source/tuya-convert as well as M4dmartig4n/tuya-convert , here are my logs:
smarthack-psk.log
smarthack-smartconfig.log
smarthack-web.log
smarthack-wifi.log
smarthack-mqtt.log

This device does not use an ESP82xx and therefore you can't install custom firmware like Tasmota which is built for the ESP82xx, OTA or otherwise. Unfortunately I'm not aware of any custom firmware for the Realtek chip your device is running.

@kueblc the device type is listed in the tasmota wiki as supported. Where do you see that the manufacturer has now switched to realtek?

The behavior of the device as reported by the log

Heho,
i opend up a recently bought one and can confirm that there is a module with Realtek Chip mounted.
The module is named SP21, chip beeing "W302" (probably a RTL8710BN).

From https://templates.blakadder.com/zoozee_SE131.html :

WARNING: There is a new version with a T102/WR2 WiFi module in it. This uses a RTL8710BN chip and can not be converted to Tasmota. Make sure that you get a plug with TYWE2S WiFi module based on ESP8266.


[TS Typing] allow mergeAll on Observable<T[]> like mergeMap(x => x) allows

On an observable of an array, it's possible to call .mergeMap(x => x) instead of .mergeMap(x => Rx.Observalble.from(x)).
While .mergeMap(x => x) should be identical to mergeAll(), in TS it's not allowed to call mergeAll() on Observable<T[]>, but .mergeMap(x => x) is allowed.

I'm not sure if I understood issue correctly. Can you provide detail with snippet example for clarity?

Code sample:
Rx.Observable.of([1,2,3]).mergeMap(x => x)

Rx.Observable.of([1,2,3]).mergeAll()

This will produce the same result, and observable of 1,2,3, but in Ts, the second one wont compile.

Maybe I'm lost, but isn't this in above code snippet?
https://travis-ci.org/kwonoj/mergeall-test#L162-L171

Oh, now I see. Sorry for confusions.

@kwonoj Sorry for the confusion, i should have added subscribe to the observable. My point is that the second line will return Number[] instead of Observable<number>

Actually I was surprised we have updated concatAll for similar reason but forgot mergemap. https://github.com/ReactiveX/rxjs/issues/1436 :p think you can blame me for that.


Dealing with unknown date for sensor

Before you submit a new bug report, please check that

[X] I have read frequently asked questions and limitations

Write your question here
I use the companion app actionable notifications to send me a notification on friday and saturday to see if the yard was mowed and there are grass clippings that need to go out.  I haven't quite figured out how this custom component works and how to deal with a sensor on home assistant restart.
This is my current sensor:
- trigger:
    - platform: event
      event_type: mobile_app_notification_action
      event_data:
        action: UPDATE GARBAGE INTEGRATION
  sensor:
    - name: 'grass trigger sensor'
      state: >-
        {% if now().isoweekday() == 5 %}
          {{(as_timestamp(now()) + (48*3600)) | timestamp_custom('%Y-%m-%d')}}
        {% elif now().isoweekday() == 6 %}
          {{(as_timestamp(now()) + (24*3600)) | timestamp_custom('%Y-%m-%d')}}
        {% else %}
          {{(as_timestamp(now()) | timestamp_custom('%Y-%m-%d')) }}
        {% endif %}

This is my automation:
- id: 'u2'
  alias: Update Grass Garbage Integration
  trigger:
    platform: event
    event_type: garbage_collection_loaded
    event_data:
      entity_id: sensor.grass
  action:
    - service: garbage_collection.add_date
      data:
        entity_id: '{{ trigger.event.data.entity_id }}'
        date: "{{ states('sensor.grass_trigger_sensor') }}"
    - service: garbage_collection.update_state
      data:
        entity_id: sensor.grass
  mode: single

At some point during the week, sensor.grass gets a state of null.  I have tried adding:
  - platform: homeassistant
  - event: start

as a trigger for sensor.grass_trigger_sensor but then it adds the current date for every home assistant restart.  otherwise I get these errors at startup:
Logger: homeassistant.components.automation.update_grass_garbage_integration
Source: helpers/script.py:1397
Integration: Automation ([documentation](https://www.home-assistant.io/integrations/automation), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+automation%22))
First occurred: 6:31:43 AM (18 occurrences)
Last logged: 6:34:33 AM

Update Grass Garbage Integration: Error executing script. Invalid data for call_service at pos 1: Could not parse date for dictionary value @ data['date']

Logger: homeassistant.components.automation.update_grass_garbage_integration
Source: components/automation/__init__.py:519
Integration: Automation ([documentation](https://www.home-assistant.io/integrations/automation), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+automation%22))
First occurred: 6:31:43 AM (18 occurrences)
Last logged: 6:34:33 AM

Error while executing automation automation.update_grass_garbage_integration: Could not parse date for dictionary value @ data['date']

What is the best way to deal with a null date in sensor.grass_trigger_sensor?

Suppose add a condition that the sensor state must not be Null?
 If you say yes, it will then trigger the sensor update with the current day (or in two days or tomorrow if it is Friday or Saturday). So it will say garbage collection is today. And after the day is finished it it will show None as there will not be any next collection date defined? Not sure I understand this use-case. But if this is how you want this to work, then ok.

Yes, you hit the nail on the head. So a condition on the automation that the template sensor is not null should work. I actually got my first working date this Saturday so I am waiting to determine the state of all sensors involved tomorrow.

Things seem to have stabilized. No idea what changes fixed things. I think trigger based template sensors maintaining state and some of the code stuff you have done.  Also, actually getting a valid date into the calendar. Anyway, I think all good at this stage. Thanks


Exponential backoff policy on DecisionTaskFailed response

Cadence server will immediately create new decision task when worker responds back with DecisionTaskFailed response.  This could cause decisions to spin when decisions are failing due to bad worker deployment.  Clients currently deal with this by dropping the decision if it fails again but looking at the attempt on decision task to let the decision timeout before creating a new one.
This task is to expose retry policy for decision tasks which could prevent the fast creation of decision tasks when they are continuously failing potentially allowing backoff which is much larger than DecisionTimeout.

need to prioritize this task for customers.


Reef is not defined when using router

Thank you for creating Reef, I'm really enjoying using it. I thought I would give the router a try and it seems I have fallen at the first hurdle.
I installed Reef using npm npm i reefjs and I am using webpack 5 to bundle my modules. The only thing that is in my index.js file is:
import Reef from 'reefjs';
import 'reefjs/router';

If I run using webpack serve then I get the following console error:
Uncaught ReferenceError: Reef is not defined
    at Object../node_modules/reefjs/router.js (router.js:2)
    at __webpack_require__ (bootstrap:21)
    at fn (hot module replacement:60)
    at Module../src/index.js (main.bundle.js:18)
    at __webpack_require__ (bootstrap:21)
    at startup:4
    at startup:5

If I build the bundle then it's the same error but in my js bundle:
Uncaught ReferenceError: Reef is not defined
    at Object.469 (main.bundle.js:2)
    at n (main.bundle.js:2)
    at main.bundle.js:2
    at main.bundle.js:2
    at main.bundle.js:2

I really wanted to get this working and build a single page site so any help would be gratefully received :)

Sorry for the late reply here... is the path to your files correct?
If you're using something like Rollup (my tool of choice), I typically need to update the import statement to point to the actual location of Reef (and the correct filename) in my filesystem. If you're using npm to install Reef, what you've got above should be fine.

HI, I am using npm and webpack. I have found that if I edit node_modules/reefjs/router.js and include import Reef from 'reefjs'; at the top of this file then it works but this isn't ideal because as soon as I update Reef this will be overwritten.

Can you link me to a reduced test case? Happy to do some debugging.

Hi
I have set up a reduced test case on CodePen, however (annoyingly and predictably) everything works fine. I have added my code which is essentially your code from the docs and I have commented out my two imports in favour of the cdn imports. You can view the pen at https://codepen.io/davidbrooksio/pen/MWjgaZz?editors=1111 but to be honest it isn't going to tell you much (because everything works).
With regards to my local code, I have created a repo at https://github.com/davidbrooksio/reefsinglepage which you can clone, npm install and then npm run start;
Hopefully this will show the error.

I can confirm the test cases
Browser console:
Uncaught ReferenceError: Reef is not defined
    at Object../node_modules/reefjs/router.js (router.js:2)
    at __webpack_require__ (bootstrap:21)
    at fn (hot module replacement:60)
    at Module../src/index.js (index.js:4)
    at __webpack_require__ (bootstrap:21)
    at startup:4
    at startup:5

On adding reefjs and reef-router as npm dependencies I've noticed this warning which might be relaviant:
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.

npm build:produiction is missing the mini-css-extract-plugin, however once added, this also throws a similar Uncaught ReferenceError, so Dev and Prod would seem to be giving the same results.
Uncaught ReferenceError: Reef is not defined
    at Object../node_modules/reefjs/router.js (router.js:2)
    at __webpack_require__ (bootstrap:21)
    at fn (hot module replacement:60)
    at Module../src/index.js (main.bundle.js:16)
    at __webpack_require__ (bootstrap:21)
    at startup:4
    at startup:4

I suspect this is a Webpack config issue?

Thanks for the extra details there! My lack of familiarity with webpack may be hurting me here. I tested using Rollup and everything worked as expected, but I know webpack is quite popular.
I'll see if I can get to the root of this. Thanks y'all!

Thanks @onionrush and @cferdinandi
Always nice to know I'm not going mad!

I had the same issue and solved it by extracting the router into a library on npm reefjs-browser-router.
Have resorted to installing reefjs and the library and everything works just fine in that instance. It would be nice to see this resolved.

I have the same problem, but I'm using https://parceljs.org/.

I have the same problem, but I'm using https://parceljs.org/.

I owe y'all an update, and I'm sorry!
I believe I've isolated the problem to ReefRouter using Reef internally. In non-NPM imports, that's generally not an issue since Reef is in the global or lexical scope. When using certain bundlers (like Webkit or ParcelJS), Reef is assigned to a different variable, and the methods the Router relies on can't be found.
This is why you're seeing the Reef not defined message.
This is going to require me to make some updates similar to what Vue has done with their Vue.use() plugin system. I'll keep you posted, but at the very least, I know why it's happening.

I owe y'all an update, and I'm sorry!
I believe I've isolated the problem to ReefRouter using Reef internally. In non-NPM imports, that's generally not an issue since Reef is in the global or lexical scope. When using certain bundlers (like Webkit or ParcelJS), Reef is assigned to a different variable, and the methods the Router relies on can't be found.
This is why you're seeing the Reef not defined message.
This is going to require me to make some updates similar to what Vue has done with their Vue.use() plugin system. I'll keep you posted, but at the very least, I know why it's happening.

This should be fixed with v8.x, but it does require an extra step when working with module bundlers.
When used with a module system, you must explicitly associate Reef with the router with the ReefRouter.install() method.
import Reef from 'https://cdn.jsdelivr.net/npm/reefjs/dist/reef.es.min.js';
import ReefRouter from 'https://cdn.jsdelivr.net/npm/reefjs/dist/router.es.min.js';

ReefRouter.install(Reef);

Also, please note that the naming convention has changed from Reef.Router() to ReefRouter().


Remediation

Testing Regal on some policy libraries found online, there are a lot of violations reported for style-related rules, like preferring := over = for top-level assignment. While we should be adamant about good style, there's also a clear risk that a user seeing hundreds of such violations either disables those rules, or worse — misses more severe violations as they drown in the amount of warnings reported.
For simple style rules like the one above, it would be interesting to explore if we could provide a remediation option, were we rewrote "bad" constructs to better ones without the user having to do the heavy lifting. Something similar to opa fmt, but limited to linter rules.

Two linter rules now have remediations available via the Regal language server: opa-fmt and use-rego-v1. More will likely follow soon. It would be good if all these remediations were made available via the CLI too as to avoid having drift in features supported by the CLI vs LSP.


[C220848] Failed to import from JLCPCB

I tried to import the part number C220848 from JLCPCB, but it failed. Here's the error I got:
Failed to generate snippet from JLCPCB part: object null is not iterable (cannot read property Symbol(Symbol.iterator))

Could be an issue in fetchEasyEDAComponent or convertRawEasyEdaToTs

@seveibar seems to be working

Ty!


overdragResistanceFactor set to 0 still allow to overdrag

Hello,
In the below example overdragResistanceFactor is set to 0, it's impossible to drag over 500 but it's still possible to drag under 160 and when it's released it bounces back to 160
Is it an expected behavior ?
let fall = new Animated.Value(1);

 <BottomSheet
        initialSnap={0}
        ref={bottomRef}
        enabledGestureInteraction={hasPlaylist}
        enabledInnerScrolling={false}
        callbackNode={fall}
        snapPoints={[
          160,
          500
        ]}
        renderContent={renderContent}
        renderHeader={renderHeader}
        overdragResistanceFactor={0}
      />

"react-native": "0.60.5"
"reanimated-bottom-sheet": "^1.0.0-alpha.13"
Thanks for this great module !

Same problem here. We should try to implement this behaviour using diffClamp for animated value.

Hey @DavoCg. I've implemented bottomClamp flag for this package. If you would like to try please, feel free to install form my fork using:
yarn add https://github.com/sebinq/react-native-reanimated-bottom-sheet.git#e1ca6ede0d77b988cacde90e0e88b2b06090dc5b
command. Then, you need to set enabledBottomClamp prop to your bottom sheet to True. After that your BottomSheet should not jump below the most bottom snapPoint. Let me know if it is working for you and then I may raise a Pull Request with this feature.
Thanks!

Hi @sebinq . I had the same problem and your fork made it work as expected. Thank you very much!

PR #108 is already in master and published so everyone who wants to clamp BottomSheet from bottom should set enabledBottomClamp property to true.


Move router for entity CRUD to bootsrap

Hi Nick,
We should move all routes definition with this pattern /admin/e/:entity/* to bootsrap. I am working on a solution to allow admin to define different template for each entity type. Pull request will be requested shortly. We should have a route.js there

Awesome!
But can we think an idea to do this without moving iron router?
Maybe using this http://docs.meteor.com/#/full/template_dynamic

I am open to suggestions, I tried two different concepts already I was leaning more on just changing the template rendered via the route api. I will pause and give dynamically template a try if that will save us from touching core

We must touch core. In core we must add the changes to the entity and also helpers for the templates. The important is that we try to not move things

Okay. Btw with route api method we don't have to move routes out I just felt since we were touching it we might as well do. Eveything entity should be bootsrap and I doubt any one will be using core without bootstrap? I realize it is a breaking change but this is bleeding edge project, you are practically adding stuff daily and this is just a separation of concerns

We should try to leave the minimum amount of things in orionjs:bootstrap, because someone could create foundation-views (for example) and the code would be duplicated

Your absolutely right about duplication, I didn't see it from the other framework perspective


[FAB-17517] Only Initialize specified BCCSP provider

Type of change

Bug fix

Description
Code currently tries to initialize multiple providers based on
provided config Opts being nil or not.
This update ensures that only specified provider is initialized
based on ProviderName.
This fixes "Failed initializing PKCS11.BCCSP %!s()" error
when the code complied with PKCS11 enabled expects
configuration to not be nil even when Provider is set to SW.
Signed-off-by: Ahmed Sajid<EMAIL_ADDRESS>Related issues
https://jira.hyperledger.org/browse/FAB-17517
#769
#821

Thank you, the maintainers are back from the Global Forum tomorrow, I will push for a follow up on this.

I was a bit concerned here that PKCS11 might use the configured SW provider when SoftVerify is true, but it configures it's own instance


localization doesn't work

Hi, i've just succefully packaged your applet for Fedora here https://copr.fedorainfracloud.org/coprs/wiiznokes/cosmic-applets-unofficial/ (still building atm).
While testing it, i noticed my default language was not used (french).
> echo $LANG
fr_FR.UTF-8
> ls /usr/share/dev.dominiccgeh.CosmicAppletEmojiSelector/i18n-json/fr
annotations.json

When i search meat, it found the corresponding emoji, but with viande, it does not. Other cosmic apps that use the LANGUAGE_LOADER thing work well for me.
Another small nit pick is that the crate name is not cosmic-ext-applet-emoji-selector which make it a little harder to package
Thanks

Btw, it would be nice to also support the LANGUAGE env variable https://wiki.archlinux.org/title/Locale#LANGUAGE:_fallback_locales for bilingual people

Thanks for packaging for packaging the applet.
What is XDG_DATA_DIRS is set to? Can you give the logs for cosmic-panel.
I'll eventually be working on renaming the crate.

Here is the code used to localize the emojis.
First  XDG_DATA_DIRS is read, then the first directory maching ID, "i18-json" is used.
https://github.com/leb-kuchen/cosmic-ext-applet-emoji-selector/blob/a5d94f611acfafca6f203d05b07770f26fb8d69d/src/main.rs#L21-L61

I don't see any logs of this applet.
> echo $XDG_DATA_DIRS
/home/fedasus/.local/share/flatpak/exports/share /var/lib/flatpak/exports/share /usr/local/share/ /usr/share/ /var/lib/snapd/desktop

I went a head a printed the current_languages variable. It only shows "en". This is because it will only contains the intersection of the translation of the app, and the language of the system + the fallback. In my case:

(de + en U fr) +en = en

I hope i was clear. You could fix it by using the $LANG and $LANGUAGE vars directly


Takes too long to sign in

I think the "Initializing your wallet" takes too long (~10 seonds). I really hope Oisy wallet can be successful for mass adoption but I fear the long sing in time will make the UX not as good as other wallet solutions. Is it possible to make it faster? Also I think letting user configure their own session expiration helps. I personally would like to make the session expires in 7 days or something like that so that I won't need to wait to sign in every time when I want to trade. Thanks!

](url)

Hi. Thanks for your valuable input. We will put the configurable session expiration as agenda item on our next planning round, and will give you an update shortly.
Also we have an improvement of the initialization phase already in the pipeline.

Would it be possible to calculate the public key/address locally in the frontend (or at least in the backend without a x-net call) based on the principal to speed things up?

We will put the configurable session expiration as agenda item on our next planning round, and will give you an update shortly

I think that makes absolutely sense.
this is a little bit out of context, but maybe you also want to give the user the option to secure transactions with an additional pin/password prompt. I think OpenChat rolled out such feature recently.

Hi all y'all
Faster initialization is already in discovery and will make it into the pipeline very soon. No exact date available yet though.
Customizable expiration threshold and the additional pwd/pin for transactions are filed as feature requests.
I will follow-up on the status of these requests or how it can be retrieved soon. tata

Would it be possible to calculate the public key/address locally in the frontend (or at least in the backend without a x-net call) based on the principal to speed things up?

@domwoe I'm not entirely sure, but I remember that the foundation invested some time last year around September when the Alpha version of OISY was created, to implement such a JS derivation without full success. As far as I recall, and if I recall correctly, the amount of work required to achieve such a derivation would be significant.

Faster initialization

General context for everyone in this thread: the sign-in has become slower because it now requires a few additional inter-canister update calls. This is due to the foundation's decision to decentralize the signer—'the derivation of the keys'—to a canister controlled by the NNS while retaining control of the OISY backend canister. Additionally, OISY was enhanced with key derivation for Bitcoin, in addition to ETH, which also requires extra update calls. Hence, the sign-in experience is slower.
This happens when you sign in for the first time in OISY. Subsequent sign-ins, as long as the derivation remains active—currently set to one hour—do not require upfront derivation. Keys are saved in the browser's cache and are validated asynchronously by a worker to avoid any security issues. Therefore, returning sign-ins with a valid session are still fast enough.


Not pausing system media player on sound play , probably via AVAudioSessionInterruption

Could you please add feature of pausing background audio (for example music) on moment of sound play and then continuing music play. as per : http://stackoverflow.com/questions/9476698/background-audio-doesnt-resume-after-a-call
or some functionality to let sound play with music concurrently, not setting system Music player, or Spotify on pause

Agree with this!  Currently this is a stop/ship issue for us.

I have a workaround for a similar issue that may solve your problem. It requires a small change to the a the line that sets up the audio session. https://github.com/floatinghotpot/cordova-plugin-nativeaudio/issues/75


Update HappyEyeball error

Ahh another note for why happy eyeballs could happen

What was the problem with the router?


Please add "Retry" switch to Invoke-VcCertificateAction and Invoke-VdcCertificateAction functions

Summary of the new feature/enhancement
There are scenarios where it would be helpful to retry a certificate request when the first attempt has failed. Usually this is the case where public CAs can not handle the velocity of my scripted certificate requests and Venafi TPP returns the error - "This certificate cannot be processed while it is in error state. fix any errors, and then click Retry"
Retry clears this issue and the certificate request is successful.
Reset and/or Renew does not resolve this issue.

Hi @wmcmiller.  It would make sense to add that switch to the invoke functions for existing functionality in those functions, eg. retire, recover, renew, etc, but if your goal is to retry when a certificate request fails, that would go into the new certificate functions.  'Retry' needs to know what it's retrying to do.  Perhaps we look at add retry functionality into New-VcCertificate and New-VdcCertificate on error by default and -NoRetry if folks want to turn it off?

The errors after what seems as a successful certificate creation using New-VcCertificate. The Certificate object is successfully created but the X.509 Certificate data is an error state.  The web interface gives the option to Retry.
Invoke-VcCertificate seems like the likely function to resolve the issue. I believe this issue is rooted in the DigiCert API's limitation and to Retry by default in New-VcCertificate would probably exhaust the API even more beyond the thousands of public certificates I attempted to generate in the first place.


Fix nested all include exclude

Change Summary
Fix the behavior of __all__ key, when used in conjunction with index keys in advanced exclude/include of fields that are sequences.
Related issue number
Fixes #1579
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

@samuelcolvin Thanks for the review. I hope the docstring makes it a bit clearer on what is going on. Updated the tests as well.


Revert "Update Nebula dates and registration links"

Reverts open-life-science/open-life-science.github.io#938
build failure

I think the environment broke, not our work.


pixi global list fails with error No such file or directory (os error 2) after fresh install

Checks

[X] I have checked that this issue has not already been reported.

[X] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example
$ brew install pixi
$ pixi global list
  × No such file or directory (os error 2)

Issue description
When I run pixi global list on a fresh install, I get a not-super-nice error No such file or directory (os error 2)
Presumably you expect me to run list only after install, but in any case the error message should be better - and ideally this shouldn't error at all.
Expected behavior
No error, or at least a clearer error message saying what I need to do instead.

A fix for that has coincidentally just been merged! https://github.com/prefix-dev/pixi/pull/865


Add a demo project and update docs

A demo project is now available to address issue raised in #488. The demo project includes a fixture with some starter queue and ticket info so that a new user may quickly get started and click around on live tickets without needing to set anything up.
Not only does it allow easier/faster demos and provide a template for starting new projects, this could be a good baseline for developers to test against.
I reworked the README to talk about the new demo project first thing. As I was re-writing it I realized there was a certain amount of redundancy between the the README, the CONTRIBUTORS file, and the docs/ files. I cut some stuff from the README and moved it to the docs/, to keep the README file shorters (more of a "quickstart" than an all-info document; IMO it should mostly just point at the other docs as like an index).

Codecov Report

Merging #498 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #498   +/-   ##
=======================================
  Coverage   59.92%   59.92%
=======================================
  Files          35       35
  Lines        3024     3024
  Branches      469      469
=======================================
  Hits         1812     1812
  Misses       1070     1070
  Partials      142      142

Continue to review full report at Codecov.

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

Thanks for holding down the fort single-handedly all this time! :1st_place_medal: I've been keeping a nervous eye on the notifications arriving in my inbox but have been able to just guiltily sigh with relief as they're handled without me... 🙇  I will be out of crunch-mode this week (delivery was today but there's still some hand-holding to do), so I should be able to review this PR in just a couple days if no-one else gets to it first.
Thanks again for putting in all the effort single-handedly of late, it's great Ross is still around and could grant the auth'z you were missing; having many hands on deck sure makes a difference! 🙏

No problem, happy to be able to fill in while you're busy :-) hope you get a break from crunch-time soon!

Wow, that is an awesome demo installer! Simple considering the flexibility in environments that it provides, it worked flawlessly even in my most tortured Python installation. I think the sample data provided is just enough for users to click their way through to a fast, hands-on. understanding of the system far more easily than they could before. Great job @gwasser! 👏


Feat/tooltip

Checklist

[ ] Fix linting errors
[ ] Tests have been added / updated (or snapshots)

Change information

Codecov Report

Merging #781 (9702df5) into feat/tooltip (60a4bd1) will decrease coverage by 2.58%.
The diff coverage is 3.77%.

@@               Coverage Diff                @@
##           feat/tooltip     #781      +/-   ##
================================================
- Coverage         95.15%   92.56%   -2.59%
================================================
  Files               241      244       +3
  Lines              5677     5719      +42
  Branches           1068     1068
================================================
- Hits               5402     5294     -108
- Misses              275      425     +150

Impacted Files
Coverage Δ

packages/varlet-ui/src/toolTip/index.ts
0.00% <0.00%> (ø)

packages/varlet-ui/src/toolTip/props.ts
0.00% <0.00%> (ø)

packages/varlet-ui/src/toolTip/tooltip.vue
0.00% <0.00%> (ø)

packages/varlet-ui/src/tooltip/Tooltip.vue
0.00% <0.00%> (-85.25%)
:arrow_down:

packages/varlet-ui/src/menu/usePopover.ts
91.04% <100.00%> (+0.41%)
:arrow_up:

packages/varlet-ui/src/tooltip/index.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

packages/varlet-ui/src/tooltip/props.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Create a separate CM script to get MLC rclone config as this config is used by multiple CM scripts

Implemented here


added OBJECT ORIENTED PROGRAMMING concept to the article

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Thanks @rajranjan0608, and congratulations on your first contribution to freeCodeCamp! We look forward to future contributions.
Thanks, and happy coding!


Error tab index out of size when opening project

Operating system or device - Godot version:
Windows 10, 2.1 alpha with 182ee80
Issue description (what happened, and what was expected):
When open project output console display this error:
http://postimg.org/image/e624va5nv/
ERROR: set_current_tab: Index p_current out of size (get_tab_count()).
   At: scene/gui/tab_container.cpp:478.

Steps to reproduce:
Open project and see output console.
Link to minimal example project (optional but very welcome):

Which error are you refering to? I can see 4 in the image.

First with tab.

I edited you message adding the error text after the image url. Did you start getting this error today? It may be a regression from #4926

I saw that error message for a long time.

This error is printed as a result of the changes in tab_container.cpp in this commit


Getting topic/partition/offset

Is there a way to get the topic, partition and offset of a message?

Hi,
No, it is currently not supported.
It makes a lot of sense to implement.
Next thing on the agenda is implementing producer next week.
Will try to find the time to implement message metadata afterward.
BR,
Eil

I actually quickly implemented it in a fork. If you like it we can expand it.
https://github.com/LivePersonInc/kafka-java-bridge/compare/master...itamarwe:feature_topicAndPartition

Thanks.
I'm sending the topic for a couple of reasons:

Replicating the behavior of the popular Kafka node library.
Hoping to move forward to a multi topic consumer (or filtered topic consumer). I'm currently consuming ~100 topic simultaneously and managing the ports becomes a pain and an overhead.

Also, notice I'm committing the offsets before shutdown, so I won't lose the last offsets consumed.

On Dec 23, 2016, at 03:05, Eli Ostro<EMAIL_ADDRESS>wrote:
Looking good at first glimpse.
But, we can skip sending the topic as we already have it in node tier.
And obviously will have to send the metadata as a second callback parameter so interface won't change for other users.
Will merge it into the code while writing the producer.
Thanks for contributing to the code.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi,
Limiting the consumer to a single topic was probably a mistake.
It can easily be implemented as shown here.
As I'm going to work on the code sometime next week lets see what will I have time to add to it.
Implementing the producer and performance testing it still remains main issue.
Regarding committing the offsets after shutdown - it is unnecessary.
Also from same source: "Additionally, with auto commit enabled, the call to consumer.shutdown() will commit the final offsets".
We only support auto commit, so offset commitment is unnecessary.

Implemented producer and added your code (with minor changes) to get consumed message metadata.


Display larger preview of image attachments

I review a ton of security camera footage. The pics come to me by email. This is what attached images are currently displayed like in K9:

It would be monumentally awesome if you guys simply changed the proportions of the same data, to behave a little more like gmails does, for the sake of being able to see more of the image. This would save folks in my boat a ton of time/clicks/taps :D

Hopefully this isn't a huge, massive change. And hopefully other users will agree with it! Otherwise, perhaps an option in the settings to change how inline images are displayed?
Thanks in advance!

I add images in mails with
Content-Type: image/jpeg; name=attachment-1.jpeg
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename=attachment-1.jpeg

Thunderbird correctly displays the whole image but K9 doesn't (like if Content-Disposition was "attachment"). Having the same behavior would be so nice.
Thanks for this great software, keep up the good work !

Yup, and the new way roundcube does it is pretty rad too, makes it really easy to see "a bunch of images that are attachments". I care more about the actual image than the metadata describing the image, and right now k9 gives more real estate to the text and not the image.
Here are two roundcube themes that do it really well just for claritys sake...


Rename noop -> bridge

Merged as https://github.com/spring-cloud/spring-cloud-stream-modules/commit/c00423ee9edc4886f88552f2590c37a0a7221ebd
Also did https://github.com/spring-cloud/spring-cloud-dataflow/commit/37f69e1e18262672ec97ffff68a49c82696f68f4


Implement Event API

Pull request checklist:

[ ] CHANGELOG.md was updated, if applicable

Description

Any update on this feature?


feat: add ADR-006 for web APIs and general description

Specs for the client package API.
Slogan of this PR is: better developer experience, greater penumbra adoption

looked over this, will post some detailed comments today

okay, this is a little excessive and kind of disorganized, but i'm trying to be
comprehensive and deliver all the necessary context. i think some of what's in
your draft is already achieved or partly achieved, there are some good ideas,
and there are some things that aren't possible or shouldn't be done.
this begins with historical reasons and choices just to cover the existing
situation
at the end i'll have a list of proposed actions, later i might suggest some
explicit changes to your doc or add inline comments linking to issues, PRs, or
code i think relevant.
we definitely need clear documentation and direction so thank you for starting
the writing process.
please read all of this as concept+notes+commentary+discussion in the interest
of collaboration. if it seems like i'm saying obvious things, i think that's a
good sign we are on the same page, if i say something that doesn't make sense or
feels conflicted, let's figure it out
the existing design
implementations announce by injection
due to ui behavior specifications, manifest v3 and chrome limitations, and
development priorities, implementations inject content scripts to provide
connection.
these scripts are injected not just to pages that the user approves, but to
nearly every browser tab the user opens. so the injected script must be
minimal.
proto spec first
using protofbuf to specify communication between dapp and extension was a
deliberate choice to minimize effort spent (re)designing and (re)implementing
the existing api in parallel.
use of the same protocol for both pd rpc and browser rpc ensures that browser
clients have access to all the same features as any direct pd client, and vice
versa.
support use of generated tools
so a dapp independenlty imports packages and service types to construct useful
clients. @penumbra-zone/client defines the simplest tools possible to enable
the dapp to create a connectrpc client. connectrpc provides a few different
kinds of generated clients and the page api alone supports any of them.
the client package exports very simple utilities that can validate providers as
much as possible, create clients, and fetch provider metadata. the exported
createPenumbraClient will completely handle connection
validation/request/approval/transport init and simply return a client to the
specified service.
react
react is eager to destroy and recreate state. sync rendering requirements make
it awkward to manage async behaviors of a PromiseClient. and unfortunately
connectrpc's react solution @connectrpc/connect-query is quite limited (no
streaming requests).
so an additional react-focused wrapper was requested.  the react wrapper focuses
on supporting transport lifecycle management and making lifecycle inspectable in
a detailed way without manual state management by an app importing the package.
internally it uses @penumbra-zone/client tools and sometimes uses the page api
directly for more detailed control. it provides hooks that support use of either
PromiseClient without constant destruction/recreation of the client, or
connect-query, if the developer chooses.
in the future it could export query functions for common activities that
currently require multiple requests.
too many words about 'wallet'
the term 'wallet' may be familiar to developers with experience with other
chains and cryptowallets software, but i think it's a confusing term in most
cases, and in the way it's used in this ADR.
The term 'wallet' is overloaded with several meanings. There are more than this,
but here are four:

wallet-keys: the cryptographic keys capable of mutating a specific part of the
chain state
wallet-custody: the software (and sometimes hardware) stack for gating secure
access to keys
wallet-app: a application user interface to examine associated state and
assets, usually with tools for authoring state activity.
wallet-api: closest to the subject of this ADR, the API surface or some
concept/metaphor of the API to a wallet-app.

penumbra wallets
Penumbra includes the concepts of many accounts per wallet-keys, and many
addresses per account. This satisfies some of the same solutions achieved by a
wallet-app hosting multiple wallet-keys, but it is different enough that
penumbra wallet-apps must use different metaphors.
Outside the proto spec, penumbra wallet-apps may also contain multiple
wallet-keys.  But this should not be considered.  Switching wallet-keys is not
described by the proto spec - stub references to walletId in the protos are
deprecated - so this probably shouldn't be exposed to dapps.
So penumbra wallet-apps will probably just expose one wallet at a time. It's
also worth considering that multiple penumbra wallet-apps, simultaneosuly
present, may hold the same wallet-keys.
So the term wallet may be 'familiar' but the familiarity might be more
misleading and confusing than useful.
'Prax wallet' does use the term, but critically, Prax only provides custody and
an api. it implements zero of the typical wallet-app features. independently, it
offers no UI for taking action.  it doesn't ever actually display existing chain
state, it only includes UI for viewing proposed state changes. dapps are
responsible for all the rest.
the existing penumbra api is more of a chain api
Clients to penumbra services are more literally clients to the chain, than
clients to a wallet.
the api is the same specified api used to query pd, the penumbra daemon
operating a remote chain node providing public rpc, just extended to also
include private chain state. clients using this api are literally querying a
local penumbra node, providing a private local rpc identical to the remote
public rpc, in some cases a straight proxy, plus the extra private services.
many of these services are entirely public, and don't actually involve
wallet-keys at all. This somewhat achieves the separation of public
state/private state apis as you suggested - much of that separation is
represented by the separation of services.
loosely, the 'view service' and 'custody service' together may be considered the
equivalent of a 'wallet api'.
penumbra api terms
Dapp developers won't be able to escape penumbra-specific concepts. The concepts
are introduced because they are necessary.
In terms of api i think it's important to clearly speak in terms of

penumbra 'services', the software implementing protobuf-specified rpc
interfaces

fullnode 'public services'. public view, opaque data, fullnode queries.
any service requiring no wallet keys.
local extension 'wallet services'. private view, decrypted data, local
queries.

notably the 'custody service' for keys and authorization
notably the 'view service' for inspecting private state

penumbra 'provider', a wallet-app handle within the page interface discussed
in this ADR, by which protobuf-specified rpc services are exposed to and
accessed by dapps
provider 'origin', uniquely identifies software providing services
penumbra 'client', the lowest-level tool used by dapps to query those provided
services

Reserve the term 'wallet' to refer to

the wallet-keys
at the user level, loosely qualified: the wallet-app in its capacity as a
metaphorical place, where accounts and addresses are located
at the developer level, always qualified: terms like 'wallet services' or
'wallet id' or 'wallet custody'

avoid applying 'wallet' to any concept not directly involving wallet-keys.

an injected connection handle is providing penumbra service
'balances' or 'assets' belong to an 'account'
tx assets are sourced from an 'account'
tx destinations are named by an 'address'
a destination 'address' selects a destination 'account'

action items
what the page api should not add
these are not action items: for privacy and security reasons, most
extension/provider settings, configuration, and control should not be available
to the dapp.

rpc endpoint should never be available to dapp
'default frontend' is a concept outside of spec, and is not likely to be
shared by other implementations
all other settings actions are very sensitive (clearing cache, recovery keys, etc)

in general: if it's not in the protobuf spec, there shouldn't be a page api for it.
what the page api could add
these suggestions need discussion and review before action.

a simple method to get a 'send' destination address pointing to the user.
this would function without requiring connection, but would trigger an approval
dialog. benefit: an app may 'send' to the user, without gaining full viewing
access.
a simple method to suggest a 'send' destination address and a specific asset
and quantity to the user. this would function without requiring connection, and
would trigger an approval dialog. benefit: an app may request a 'send' from the
user, without gaining full viewing access.
more detailed/restricted connection approval. a page might request approval
per-service, instead of general approval for all services.

This is probably it. These suggestions are candidates specifically because they
operate outside of the connection lifecycle.
Pretty much any other feature, involving an active connection to the provider,
should go into the proto spec.
what the proto spec could add

indefinite stream of transactions by height. this would allow dapps and dapp
components to be ambiently aware of arriving transactions, without being
specifically responsible for issuing the transactions.

errors

errors emitted from services are all using a special error class
ConnectError, which supports elaboration with detail.
errors in @penumbra-zone/client or @penumbra-zone/react do have room for
improvement and documentation

connectrpc tooling can be improved
with some effort applied to @connectrpc/connect-query, it could support
streaming endpoints. connect-query provides a similar pattern to the queriers
you've suggested, and generated queriers for every endpoint would make a lot of
existing code redundant.
a simple wrapper to PromiseClient or an alternative implementation could
provide the result-style errors described in your ADR.
maybe move interface definitions to a dedicated package
Interface definitions could be moved to a dedicated package, leaving
@penumbra-zone/client more directly concerned with client init.
focus on integrations
The primary objective right now is not dapp development but integration,
assisting other teams with integrations, and identifying what API or spec
changes other teams may benefit from in integration.
To this end, good demos, and a well-featured react package with helpful hooks
and queriers is a priority.
The react package could begin adding modules that export queriers. Some of the
current minifront hooks and queriers could be moved into the react package, and
thus be made available to consumers.

@turbocrime I highly appreciate the context and the ideas you shared. Special thanks for explaining different wallet-related terms – I never thought about Prax as just wallet-api implementation.
Interestingly, not so many things actually contradict with the ADR. Some needs to be rewritten, some apis updated and added. Strongly agree on integrations focus: making examples, writing docs and collecting feedback is extremely important too. It could open our eyes even wider to see the needs of the community.
Agree that wallet-app settings should not be exposed to the API, at least not in the injected connection and not in this ADR. If wallet developers want it, they could create their own logic exposing this feature. Going to remove this section from the proposal.
While I'm rewriting the ADR, one more question: can we actually use 'public services' publicly?
I mean, right now we require users to have an injected connection, and it's not public to me. It might not require the wallet keys but the service users are querying is kinda auth-protected by the connection. So maybe we shouldn't expose the 'public services' term to users?

@turbocrime I updated the ADR considering your feedback.
Would appreciate if you elaborate on the "what the page api could add" section of your comment with examples and maybe addition to this ADR

Some additional related issues:
https://github.com/penumbra-zone/web/issues/1522
https://github.com/penumbra-zone/web/issues/1521
https://github.com/prax-wallet/web/issues/120
https://github.com/prax-wallet/web/issues/121

@turbocrime Let's finish this up. Wanted to mention why stick to this design if we have almost the same api right now.
This ADR, as you mentioned before, renames a bunch of methods with the main idea to unify the notion of 'client'. It was mostly referred to the service client but is changing in this ADR to the Penumbra client as a set of encapsulated methods to work with the injected connection. It's a common pattern for libraries that users are used to: no need to guess the imports, create the 'client' once and share everywhere, while it stores the useful state and simplifies the work.
The main point disagreement for now is this Gabe's comment about the connection listener. We can vote on this, I don't mind different versions.
At tell me if there's more to add to this document, I might have forgotten something.

still going through this will add some more review later. please push the latest version it doesn't seem up-to-date wrt the comments

have some work done for implementing these issues and some ADR, will push tonight or in the morning


[Improvement][control plane][FE] check duplicate name when creating a new seller API server

a/c:

In seller api server creation page, check if the name is used or not after user inputs a name and press enter
if it is used, report error under the input box

Request:
curl -X 'GET'
'{{baseurl}}/v2/products/mef.sonata/components/mef.sonata/api-servers/test-1022'
-H 'accept: application/json'
-H 'Authorization: Bearer login-token-here'
Response:
{
  "code": 200,
  "message": "The API Server name has existed:test-1022",
  "data": false
}

If the Server name was the first time to use, then the response body is as following:
{
  "code": 200,
  "message": "OK",
  "data": true
}

pass


added fatal and gcd functions

I found it would be advantageous for your tools module to contain a fatal function, where you can gracefully exit a program AND return an error message, all in one line. You're welcome.

Check out my new additions. I am sure you will enjoy what they have to offer to your already-robust program.

Fantastic work Benjamin.


CSUB-659: Add CI job to check for changes in EPOCH_DURATION

we must make this CI check Required!
Description of proposed changes

Practical tips for PR review & merge:

[ ] All GitHub Actions report PASS
[ ] Newly added code/functions have unit tests

[ ] Coverage tools report all newly added lines as covered
[ ] The positive scenario is exercised
[ ] Negative scenarios are exercised, e.g. assert on all possible errors
[ ] Assert on events triggered if applicable
[ ] Assert on changes made to storage if applicable

[ ] Modified behavior/functions - try to make sure above test items are covered
[ ] Integration tests are added if applicable/needed

Codecov Report

Merging #1197 (9dabff2) into dev (f4d0188) will decrease coverage by 62.60%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev   #1197       +/-   ##
==========================================
- Coverage   69.65%   7.06%   -62.60%
==========================================
  Files         100      25       -75
  Lines       11743     722    -11021
  Branches       83      83
==========================================
- Hits         8180      51     -8129
+ Misses       3563     671     -2892

see 75 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


It is not watching for CSS

How to make it refresh on CSS updates?

Hmm...works for me.
What is the file structure of your project? That may have something to do with it.

Hmm...works for me.
What is the file structure of your project? That may have something to do with it.

@adriano-pinaffo
Is there a way to reproduce this?
Does it happen in https://github.com/tamago324/vim-browsersync/blob/master/example/style.css? Or is it a more complex project?

@adriano-pinaffo
Is there a way to reproduce this?
Does it happen in https://github.com/tamago324/vim-browsersync/blob/master/example/style.css? Or is it a more complex project?

That is so weird. I closed and re-opened the files and now they work just fine. Sorry for opening this ticket

That is so weird. I closed and re-opened the files and now they work just fine. Sorry for opening this ticket

@adriano-pinaffo
No, I'm glad it works.
If you have any further questions, please open an issue.

@adriano-pinaffo
No, I'm glad it works.
If you have any further questions, please open an issue.


Typo in variable name

Seems like there's an "s" missing here.

Good catch! Thank you!

It's on npm now. Thanks!


Converts preview to canvas

fixes #26

Side note, might want to make the layers all the same size


removing slack token credentials binding from unrelated CI jobs

Slack token credentials binding were added to the commonJobProperties while the only job which uses it is beam_PerformanceTest_Analysis.
That PR moves the credentials binding definition to the definition of this job.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

R: @aaltay

Should we completely remove this slack integration? Is anyone using it?

That's a long story. It was implemented 2 years ago BEAM-4065 and here are the details of that feature.
Then, AFAIK, beam migrated to the new slack and the token wasn't updated. So, yes, currently nobody is using it as it still posts to the old slack. But, perhaps, it may be worthy to generate a new token and give that feature a new life :)

Thank you. This change LGTM. I will merge it, but I want to keep people a chance to respond first.
@tysonjh @kennknowles - To respond to @damgad's previous comment. Do we want this feature or not? If yes, how can we get a new token?

Seems fine. I agree that if it is not used we can just delete it.

Thank you. This change LGTM. I will merge it, but I want to keep people a chance to respond first.
@tysonjh @kennknowles - To respond to @damgad's previous comment. Do we want this feature or not? If yes, how can we get a new token?

Is there another way to get this information via push? We recently didn't notice the regression in Nexmark benchmarks after migrating to the new infra until ~1mo afterwards and much of the logs were no longer around.

It is a good point. I think Slack also reaches only a small number of developers who happen to be looking at the time. Email to dev@ and/or filing a P1 bug would be best.

Merging this change based on the comments. Thank you.

Run Spotless PreCommit

I believe this PR broke Spotless PreCommit.

https://ci-beam.apache.org/job/beam_PreCommit_Spotless_Phrase/56/console

@udim @ibzib thank you!


Extend UIColor in stead of using the Helper.

I was wondering why you would use a helper class in stead of extending the UIColor class.
For example:
extension UIColor {

    convenience init(hex rgba:String) {

        var red:   CGFloat = 0.0
        var green: CGFloat = 0.0
        var blue:  CGFloat = 0.0
        var alpha: CGFloat = 1.0

        if rgba.hasPrefix("#") {
            let index   = advance(rgba.startIndex, 1)
            let hex     = rgba.substringFromIndex(index)
            let scanner = NSScanner(string: hex)
            var hexValue: CUnsignedLongLong = 0
            if scanner.scanHexLongLong(&hexValue) {
                switch (countElements(hex)) {
                case 3:
                    red   = CGFloat((hexValue & 0xF00) >> 8)       / 15.0
                    green = CGFloat((hexValue & 0x0F0) >> 4)       / 15.0
                    blue  = CGFloat(hexValue & 0x00F)              / 15.0
                case 4:
                    red   = CGFloat((hexValue & 0xF000) >> 12)     / 15.0
                    green = CGFloat((hexValue & 0x0F00) >> 8)      / 15.0
                    blue  = CGFloat((hexValue & 0x00F0) >> 4)      / 15.0
                    alpha = CGFloat(hexValue & 0x000F)             / 15.0
                case 6:
                    red   = CGFloat((hexValue & 0xFF0000) >> 16)   / 255.0
                    green = CGFloat((hexValue & 0x00FF00) >> 8)    / 255.0
                    blue  = CGFloat(hexValue & 0x0000FF)           / 255.0
                case 8:
                    red   = CGFloat((hexValue & 0xFF000000) >> 24) / 255.0
                    green = CGFloat((hexValue & 0x00FF0000) >> 16) / 255.0
                    blue  = CGFloat((hexValue & 0x0000FF00) >> 8)  / 255.0
                    alpha = CGFloat(hexValue & 0x000000FF)         / 255.0
                default:
                    print("Invalid RGB string, number of characters after '#' should be either 3, 4, 6 or 8")
                }
            } else {
                println("Scan hex error")
            }
        } else {
            print("Invalid RGB string, missing '#' as prefix")
        }

        self.init(red:red, green:green, blue:blue, alpha:alpha)
    }
}

Allows you to write the following:
let color = UIColor(hex:"#ff6600")

Yeah, you are totally right. Somehow I had this Helper class from an earlier projects where this method was defined. But actually it makes more sense to create an UIColor extension. I changed it to your proposed way. Thanks for bringing this up!


Codes on demos

Hi!!
Nice lightbox you have here! Great job!
It's not an issue, but an implementation actually...
On your page, for each demo, mind to add the code related to it? Like in Bootstrap page, where you can see what is and how is done.
Its better for everyone I guess! =)
Cheers =)

I will think about this, but in the mean time just view the source, it's very simple

Yeah... I do this.... its just for a time saver and understand what is happening there...  maybe it can be a codepen snippet if you like too =)

The plugin is really great but documentation is poor. I agree with @tofanelli . Documentation with code would be really helpful.

Feel free to submit PR's to the gh-pages branch 👍

Documentation is really poor. As I understood i need its js and css and do
Launch modal
But it just links me to the source of image.
Got to go - stalker your index.html with demos

@sabakilai did you read the bit under "Implementation"?

my bad

This will go in the docs for the https://github.com/ashleydw/lightbox/issues/166 branch


Turn on flag to parallelize build docs

-j auto uses the number of cpus.
On my box this sped up the test by a factor of 2.

sphinx-markdown-table is marked as parallelizable in version on github, but not in one that is pip installed.

OK, hacked in the fix for tables to see if we got a speed improvement, and...no.  So closing.


cli returns booleans as strings and not return codes

I was expecting that returning True would exit with a status of 0 and returning with False would exit with a status of 1.
However, this is not the case:
$ cat trueorfalse.py3
#!/usr/bin/env python3

import hug

API = hug.API('trueorfalse')

@hug.object(api=API)
class TRUEORFALSE(object):
    @hug.object.cli
    def true(self):
        return True

    @hug.object.cli
    def false(self):
        return False

if __name__ == '__main__':
    API.cli()
$ python3 trueorfalse.py3
trueorfalse

Available Commands:

        - false
        - true

$ python3 trueorfalse.py3 true; echo $?
True
0
$ python3 trueorfalse.py3 false; echo $?
False
0

Is this intentional? Would you be open to a patch which changed this behavior?
Thank you!

I would def be interested in a patch that adds that behavior, as I agree it's not intuitive. It would just need to be configurable somehow - which is why it's not the current behavior - the reason being that it should be valid for False to be returned without an error (say if you a service is running command line tool, it should be able to return True or False, without either representing an error state)

Thanks for getting back to me. I am looking through and this is definitely past the normal level of Python I write. OOP is pretty new to me, too.
I see in api.py you farm out the function that gets called, but does that directly call the function the user wrote, or does that happen down the road? I'm expecting a print() somewhere in hug/hug but none look quite like what I'd expect.
If you can point me to approximately where the function gets called (or a document that describes it) I can probably start adding that in.

This was biting me too. When I have an argument with default "active=False", in my case it became True as it is a string. But when you print it, it looks "okay". It's very difficult to spot it.

@timothycrosley I'd like to work on this if possible. I think I have a working patch, however I'm not quite sure how to go about adding a test for the CLIInterfaceAPI to make sure that a non-zero exit code is returned in the proper situation

@tizz98 sounds great! Thanks for being willing to take a stab at it. I'm not sure how to ensure a particular non-zero exit code is returned, but you can easily ensure something is outputted to stderr using capsys

@tizz98 thank you! Looking forward to using this in 2.3.3.


Align legends in Figma

We have 2 different legend components - one in internal assets and one in the main library. They are different sizes and fonts. The internal assets version (large legend) is used in the fieldset component, and then main library version (small legend) is used in our radio/checks component.

[x] Add the small legend as a new subcomponent to internal assets and remove from main library
[x] Add option to change the legend size to any Heading size
[ ] Potentially: add variant to fieldset legend that is styled as the component legend for the date input specifically
[x] Update components using small legend to use the new component (radios, checkboxes, and date input)
[x] Update fieldset component with new legend
[ ] Update posters using the legends to inlcude information about the legend (radios, checks, date input, and fieldset)
[ ] Repeat process for FR library

Awaiting translations

@nmakuch All FR legends have been updated along with their respective components. What needs to be done is:

Determine if we need to add a new fieldset legend style for the date input specifically since Daine said the date input is a filedset (right now it uses the 'component legend')
updating all posters in EN + FR to incorporate the info about using the legends/label in Figma:

Legend guidance that has been applied to posters in internal assets:
https://www.figma.com/design/7HNtNYzWNmcxjYtG8UlnBz/Internal-assets?node-id=4198-2696&node-type=CANVAS&t=ZuTi63HZroFWhwBZ-0

One last task to finish this @nmakuch

@nmakuch progressing this, not done today, as need to be brought to design sync next week to get team review + discussion on it . Needs to figure out a better way to present an easier way to maintain it long term considering french version too

https://www.figma.com/design/7HNtNYzWNmcxjYtG8UlnBz/Internal-assets?node-id=4198-2696&node-type=canvas&t=dfrZ7BkjKaYYnCdu-0
updated, reviewed and published


Wire directory search

Closes #20 , #21

Codecov Report

Merging #25 into master will increase coverage by 0.32%.
The diff coverage is 96.66%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
+ Coverage   94.89%   95.21%   +0.32%
==========================================
  Files           4        4
  Lines         274      355      +81
==========================================
+ Hits          260      338      +78
- Misses         11       14       +3
  Partials        3        3


Update ftp cert not working

Hi, thanx for a good program!
I'm using <IP_ADDRESS>6 on ISS10 Win server
When cert is updated, FTP cert is not in ISS, a known issue but I can't find a good solution to work..
Using --installation iisftp [--ftpsiteid 3] throws string error
Using --installation "iisftp [--ftpsiteid 3]" opens wacs but no binding is done
Pls help :) !
Best
/Peter

The [ and ] means the parameter between them is optional, you shouldn't literally include those characters.

Thx, sorry for beeing slow here ;)
Can't get ftp bindings to update. My idea was to run:

Once a month forced update: wacs.exe --renew --force --baseuri "https://acme-v02.api.letsencrypt.org/" --verbose (WORKS)
Same time after that run wacs.exe --installation iisftp (DONT WORK)
These can't be in the same command, then I'm getting "you cant change renew parameter on renew) - correct?
Pls help ;)
Best/Peter

Hi Peter, you need to configure the FTP installation step as you create the renewal, there is no way to tack it on later. Just create a new certificate (with full options) and pick the FTP step when it comes by.