Work around permission denied on /dev/stderr

Fix for the same error described in #3, except for /dev/stderr.

@oyvinev thanks for the PRs (#7), but I haven't read anything since I am not actually maintaining anything in @lbarchive.  So, I'd like to ask you if you are interested in taking over log.sh?
If you do, I will transfer this over to your account, then you can handle these two on your own.

I can't promise much maintenance myself, but since I'm actually using it (and liking it!) you never know. So yes, feel free to transfer it to my account.

@oyvinev "oyvinev already has a repository in the lbarchive/log.sh network and You can only transfer a repository from an organization to yourself at this time "
So you have to delete your repo on GitHub first.

Deleted now.

@oyvinev I had to transfer this repo back to my user account, so that I could make a transfer request, which should be in your mailbox.

Thanks.


ANSI Codes in output (e.g. from sphinx gallery)

Hopefully this is a reasonable place to ask this question:
I have some program that has terminal output with ANSI color codes that nicely display color in the terminal, but will show the literal ANSI codes in the HTML output unfortunately.
As a simple example, let's say I have some python file like this:
# -*- coding: utf-8 -*-
"""
Plot The Marvelous Colors
=========================

"""

print('\033[94m' + "hi" + '\033[0m')

then in doc after building with sphinx gallery unfortunately I get this:
his

This can also be seen in the second-last cell here:
https://braindecode.org/auto_examples/plot_bcic_iv_2a_moabb_trial.html
Is this something that this package would try to handle? Or do you know where else I might ask?

sphinxcontrib.ansi currently only supports the basic 8 ANSI foreground and background colors.
It does not support the bright-colours, with colour codes from 90 .. 97 that is used in your example above: bright-blue (94). Internally, a KeyError exception is raised which probably causes sphinx to ignore the paragraph/directive processing.
WORKAROUND:
Use the BOLD annotation instead of the BRIGHT annotation, like: "\033[34;1m COLORED_BLUE \033[0" (if possible)
SEE ALSO:

https://en.wikipedia.org/wiki/ANSI_escape_code


Prosed changes to Helm governance

Helm is a few years old now. Currently, the governance structure of Helm is very flat ("core maintainer" is the only official role). This is great for voting and other official decision making, but it does not lend well to explaining or ascribing responsibilities. So this document is an attempt to fix that.
tl;dr
There are two official categories of Helm leadership: Project Maintainers and Architecture Maintainers. Each has a designated communicator (Project Manager, Release Manager). All maintainers have equal votes in voting process, but the expectations and requirements for each group are slightly different.
A Project / Architecture Distinction
Among the existing maintainers, there is already a clear distinction of interest: Some are primarily interested in the Helm project as a whole, and ensuring that it blends well with the Kubernetes ecosystem. Some are focused on the actual code of the Helm project. The proposal at hand is that this distinction should become formal.
We should divide maintainer responsibilities into two categories: Project Maintainer and Architecture Maintainer.
Common responsibilities
The following responsibilities are common to all maintainers  (source):

Positively represent Helm, Tiller, and Charts
Hang out in the #helm-dev and #helm-users Slack channel
Make a good-faith effort to come to the public developer's meeting
Participate in formal Helm decision making, such as casting an official vote for new maintainers
Uphold the Code of Conduct (that is, not just follow, but cultivate that as part of the project's culture)

Project Maintainers
The project maintainers are primarily concerned with Helm's interface to the rest of the Kubernetes world, not in the support sense (though we of course participate in that) but in the directoral sense.
The project maintainers' responsibilities are:

Set and track the release roadmap
Facilitate/represent the needs of the Kubernetes Chart team
Act as "project management" for release cycles
Communicate upstream to the Kubernetes governance
Manage the kubernetes-helm org
Perform the champion role for projects working through the Helm incubator

Architecture Maintainers
Architecture maintainers are "close to the code" in the sense that they are responsible for currating the Helm codebase and its related aspects.
Architecture maintainers as a whole have the following responsibilities.

Participate in resolution of critical security issues as needed
Review PRs
Participate in bug resolution
Comment on proposals and issues as appropriate
Produce releases

The Roles of Project Manager and Release Manager
Out of this division, it seems sensible to give each group a designated spokesperson.
Project Manager
The project manager represents the project maintainers. This person's role is to make sure that a roadmap is created and updated, and that the current release candidate's target matches the roadmap.

Currate the roadmap
Present roadmap updates regularly in SIG-Apps and the Helm Public Dev meeting
Communicate "upstream" for the project (e.g. to the Kubernetes governance board

Release Manager
The release manager's role is to move the codebase forward. This is the individual who will typically make the final call on whether a release is ready to go.

Make the call on releases
Be the voice of SemVer compliance and other forms of code cleanliness
Be the Helm "subject matter expert"
Tie-breaker on difficult technical decisions

Starting Lineup
The Helm project already has a strong set of core maintainers, and it can be a delicate matter to divide a team. But to ease the initial transition, this proposal includes an initial lineup for the two maintainer categories (order is unimportant):

Project Maintainers
Architecture Maintainers

Manager (temporary): technosophos
Manager: adamreese

----
----

vaikas-google
seh

viglesiasce
fibonacci1729

prydonius
jascott1

migmartri
michelleN

thomastaylor312

bacongobbler

nebril

Ideally, the project manager role could be transitioned to an experienced project manager with sufficient time to perform the required duties.
Adding, Removing Maintainers
This makes only one change to the process for adding, removing, or stepping down from maintainership positions.
At nomination time, an individual should be nominated into one of those two categories, and that will be made clear during voting.

It may also be advisable to review how the helm governance structure (both current and proposed) fits into the larger Kubernetes organization and structure (what kind of oversight does sig-apps provide, helm contributors becoming k8s org members, etc).

I really like this and am fully supportive of it. I agree with @cblecker that it is probably a good idea to see what we can adopt from the larger Kubernetes community before giving this the final go ahead. Probably a good topic for the developer meeting

@technosophos Have we accepted and gone ahead with this or do we still need to do some discussion?

@technosophos @SlickNik was this going to be turned into documentation?

probably not rotten :)
/remove-lifecycle rotten

Hi @technosophos - looks like https://github.com/helm/community/blob/master/governance/governance.md has plenty of documentation now - is there more to do, or can this issue be resolved? Thanks.

I believe this is not completely superseded by existing documentation. So I am closing. Thanks for the ping.


Add What is UMA screen

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#116  👈
#115
#114
#113
#112
#108
#105 : 1 other dependent PR (#107 )
#104
#103
develop

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

Join @bsiaotickchong and the rest of your teammates on  Graphite


PMID:38376141

New term : normal histone H3 binding
A molecular function phenotype in which occurrence of histone H3 binding by a gene product (usually a protein) in a mutant is normal (i.e. indistinguishable from wild type). The affected gene product may be encoded by the mutated gene, or by a different gene.
New term : normal histone H4 binding
A molecular function phenotype in which occurrence of histone H4 binding by a gene product (usually a protein) in a mutant is normal (i.e. indistinguishable from wild type). The affected gene product may be encoded by the mutated gene, or by a different gene.

Weirdly this is in  Protege but not in the release.
Hopefully it mill be there tomorrow


Page.click() behaves differently than HTMLElement.click()

This was a gotcha I ran into when using Page.click():
Page.click() scrolls to the element and clicks the very center of it. The scroll to part is ok, but the latter behavior is different from what HTMLElement.click() does.
A twitter card with an embedded link to another tweet is a good example of where things can go wrong:

When you call Page.click() on that twitter card, pptr clicks the center of the element which is the "web component experience" link area. That's unexpected.
Is there a way we can restrict the click to the target element or wrap HTMLElement.click() so both methods are consistent with each other?
cc @JoelEinbinder

@ebidel you can always fall back to HTMLElement.click for this case.
The twitter example is indeed a good example: every other time I navigate somewhere when in fact I want to open a tweet..


Add integrations skeleton

Closes #1080

Coverage decreased (-0.3%) to 85.311% when pulling 0fbb519f616e734f66a92db6f7fbae8eafa9dd89 on eatonphil:add-integrations-skeleton into 9883be7e4b8aaa49333d1e0b9176791b170f0de1 on linode:master.

thanks!


Codejam#6 : Inheritance based vs composition based

In codejam#6, we add long discussion about getting back to composition based for neo objects with data (AnalogSignal, SpikeTrain, Epoch, Event).
Many would prefer composition instead of inheritance:

easier to manage deferred loading.
sig1 + sig2 magic is not so much used

Other prefer keep with inheritance:

easier to maintain this sig1+sig2. With inheritence it just works.

The assemblies decision is to delayed this 0.5 and keep with inheritence for 0.4.

I think the debate is closed and inheritenace wins.


[Impeller] Impeller implements ImageQuality differently than Skia.

During an overview of the use-cases of "pixel art" in Flutter, it was discovered that Impellers notion of ImageQuality as being tied to texture sampler options is incorrect. Instead, quality is determined using a separate filter. Impeller must match Skia behavior here. The "pixel art" use-case is not related to geometric aliasing (intentional or otherwise).

I don't think this is actually true? If you look at the Flutter API, setting FilterQuality on a transform widget causes us to create a Matrix IMageFilter instead of apply a transform to the children.
But setting the FilterQuality on an image should just be sampling options

I was under the impression that we were not matching Skia behavior. But this was a while ago. Thanks for the clarification.


RFC: fetch publisher data from crates.io, start build artifact caching

This is the first draft of my idea for the artifact caching between builds, to solve #1757 .
The basic idea is:

for each release, fetch the publisher from the API
let rustwide prepare all the needed folders, including the target folder
replace the target folder with a cached target folder, by publisher github ID.
run the build
clean the doc artifacts from the target directory
move the target back to the main cache folder.

also,

when the nightly toolchain changes, delete the whole cache.

I intentionally didn't compress the cache to I can easily just rename / move the folder.
My first short tests worked, but this needs validating by more people.
open questions

[x] check doc cleanup technique
[x] can we / should we use a symlink instead of the fs::rename? Someone with a linux machine should test if if it would also fallback to the copy mechanism, which could be too slow for caching. There is also a chance I'm missing some docker specifics that make the move / symlink impossible.
[ ] I'm not sure how much of the permission related parts of #1757 we would need here?

TODO

[ ] more manual tests
[ ] monitor free disk space & delete old artifacts if it gets too full
[ ] tests for the cache itself
[ ] tests for the builder-changes

@Nemo157 @jyn514 I would love to have your feedback, especially on the changes in the build process itself.
( most of the changed LOC are fetching the publisher / a related refactor)

@Nemo157 @jyn514 I would love to have your feedback, especially on the changes in the build process itself.

More specifically:
for a simple approach, ignoring timings, what is missing?

@Mark-Simulacrum https://github.com/rust-lang/docs.rs/issues/1757 has a detailed rationale. The tldr is that crates in workspaces often have very large dependency trees that are the same between all the crates in the workspace.

Given that lack of sharing opportunity, it seems like this would only help if crates are published more than once a day,

Crates in a workspace are often published all at once, one after another.

Thank you for taking the time to look at it!

Can you expand on the rationale for going by same owner rather than by same crate?

We have some publishers that always release batches of crates (sometimes 50-100 releases at once), also visible in the current queue. Recent examples would be google-*, waffles-solana-*, swc-*, azure-*, bevy_, ...
We typically deprioritize these, but sharing the assets between them would vastly increase build speed for these.

It seems to me that any cross-crate sharing is very iffy, since crates typically expect to build in a distinct workspace rather than in the same target directories as other crates. Crater has encountered a long tail of problems here that we're gradually fixing or hiding under the rug, and I wouldn't want to repeat that for something user facing like docs.rs.

Could you elaborate on this? Where these build failures? In which cases did crater share the target directory?

One particular thing to call out is to make sure to completely get rid of the cache on each nightly bump, Crater used to share target directories for that but stopped as we were hitting too many "wrong rustc version" errors in a typical run.

We're already doing this in this PR. When the nightly version switches, we purge the whole cache.

Given that lack of sharing opportunity, it seems like this would only help if crates are published more than once a day, which seems like a rare use case compared to the complexity of getting this right.

See the rationale, this is mainly for bulk-publishes.

Long-term (or really hopefully quite soon) I hope that the build environment will be an entirely ephemeral ec2 instance, which may get replaced even after every build eventually. That'll make caching here even harder.

I believe one-instance-per-build is more mid- to long-term.
What is currently in progress with infra is that we split the web & build-server, run web on ECS, and have an easy way to recreate build-servers when we want to. This would then be used to scale the build-servers (horizontally & vertically) when the queue gets full. So for these cases the caching would still help.

I'm not sure how much of the permission related parts of #1757 we would need here?

The main thing we're missing is that we're not marking the cache directory as read-only when we restore it. I would prefer to do that, but since we're only using builds by the same owner, it can only be a correctness issue, not a security issue, and in practice I doubt anything will go wrong.

@jyn514 could you explain more? You mean making it readonly when it's in the cache? Or when it's restored for the build?
To me a correctness issue with security impact is worth digging into, if we can protect ourselves against ourselves ;)

@jyn514 could you explain more? You mean making it readonly when it's in the cache? Or when it's restored for the build?

When it's restored. The idea is to prevent cargo (or build scripts) from modifying files it's already created in a previous build.

To me a correctness issue with security impact is worth digging into, if we can protect ourselves against ourselves ;)

This is a correctness issue that does not have a security impact.

@jyn514 could you explain more? You mean making it readonly when it's in the cache? Or when it's restored for the build?

When it's restored. The idea is to prevent cargo (or build scripts) from modifying files it's already created in a previous build.

So the build will ever only create files? And never update or delete them?
Setting them to readonly should be possible then, but that would have to be file-by-file, right?

To me a correctness issue with security impact is worth digging into, if we can protect ourselves against ourselves ;)

This is a correctness issue that does not have a security impact.

👍

So the build will ever only create files? And never update or delete them?
Setting them to readonly should be possible then, but that would have to be file-by-file, right?

that,s what I was imagining, yeah.

It seems to me that any cross-crate sharing is very iffy, since crates typically expect to build in a distinct workspace rather than in the same target directories as other crates. Crater has encountered a long tail of problems here that we're gradually fixing or hiding under the rug, and I wouldn't want to repeat that for something user facing like docs.rs.

Could you elaborate on this? Where these build failures? In which cases did crater share the target directory?

Crater currently shares target directories across ~all (up to disk space limits, so no per-crate property) crates it builds for a single run and compiler version.
Historically Crater used a single target directory for both the baseline and new compiler versions, which regularly exposed us to errors. I didn't spend a lot of time tracking those errors down in terms of root cause, but they typically were of the shape "found artifact X compiled by different version of rustc" or something along those lines.
I think I have seen cases where a crate won't build or will fail tests due to stale files, e.g., because it's build script assumes that it is only running once -- but with different features etc that may not be the case -- but I don't have links to those off hand. I think my advice here comes down to: be prepared for trouble if you do this, and make sure you have a way to disable it. Consider only enabling for known well-behaved crates, especially if you already have logic for those to automatically de-prioritize them in the queue.
This would also make me feel better because relying on crate owners as a security boundary doesn't feel right to me. For example, I have publishing rights to some rust-lang-owned crates, but I wouldn't want to see that mean that there is a security boundary breached if I have a side-project auto-published crate from some random repository or whatever.
It seems to me that the primary benefit is to already large projects, and ones we already treat specially in terms of queues etc, so we can readily mark those as sharing a build directory while not using any crate property.

One particular thing to call out is to make sure to completely get rid of the cache on each nightly bump, Crater used to share target directories for that but stopped as we were hitting too many "wrong rustc version" errors in a typical run.

We're already doing this in this PR. When the nightly version switches, we purge the whole cache.

👍 -- this seems like it would prevent most of the issues Crater saw.

I believe one-instance-per-build is more mid- to long-term.
What is currently in progress with infra is that we split the web & build-server, run web on ECS, and have an easy way to recreate build-servers when we want to. This would then be used to scale the build-servers (horizontally & vertically) when the queue gets full. So for these cases the caching would still help.

Yes, that seems right in terms of current trajectory. I would like to move us eventually to having no or minimal sandboxing ourselves (in Crater, docs.rs, playground) but rather rely on boundaries made by others (e.g., EC2 instance isolation).

I think I have seen cases where a crate won't build or will fail tests due to stale files, e.g., because it's build script assumes that it is only running once -- but with different features etc that may not be the case -- but I don't have links to those off hand. I think my advice here comes down to: be prepared for trouble if you do this, and make sure you have a way to disable it. Consider only enabling for known well-behaved crates, especially if you already have logic for those to automatically de-prioritize them in the queue.

I'll keep that in mind, thanks! The deprioritization is currently only based on name patterns, which means there are false positives where crates from other orgs might be also deprioritized only because they share the same prefix. So we would have to keep in mind that crates from different owners might be mixed up under the same prefix.

This would also make me feel better because relying on crate owners as a security boundary doesn't feel right to me. For example, I have publishing rights to some rust-lang-owned crates, but I wouldn't want to see that mean that there is a security boundary breached if I have a side-project auto-published crate from some random repository or whatever.

The current idea is that the security boundary is not the owner, but the publisher.

It seems to me that the primary benefit is to already large projects, and ones we already treat specially in terms of queues etc, so we can readily mark those as sharing a build directory while not using any crate property.

So this sounds like it boils down to a decision between a manual opt-in for caching artifacts, and automated caching based on some criteria (publisher, ... )

We could use sccache to manage the caching for us. Just mount a per-owner directory into the build container for it to use. It will then handle copying the minimal final artifacts for each dependency into this directory, and grabbing the correct ones on the next build. That avoids all issues around copying things like doc/ that aren't cacheable, and reduces the disk usage by not caching other intermediate files that aren't necessary.

I'll check out if / how that would work. I assume just setting RUSTC_WRAPPER should be good enough.

I haven't looked into this in detail since my last review, but i want to say - having a way to turn this off in prod without needing to revert seems good, and i don't mind making it opt-in on our end to start, but i would like to turn it on unconditionally at some point to avoid needing ongoing work to add new workspaces to the list.

I haven't looked into this in detail since my last review, but i want to say - having a way to turn this off in prod without needing to revert seems good, and i don't mind making it opt-in on our end to start, but i would like to turn it on unconditionally at some point to avoid needing ongoing work to add new workspaces to the list.

Yeah, these are valid points.
This would be the next topic, after I checked if I can make this work using sccache, using it felt like the better solution (please correct me if I'm wrong :) )

I am dubious how much sccache will actually help in practice. I would like to see benchmarks on how much it helps with large workspace if you're planning to only switch to sccache without further changes.

That said landing sccache seems fine as a first step as long as you don't close out the tracking issue.

That said landing sccache seems fine as a first step as long as you don't close out the tracking issue.

Hm, this sounds you would prefer the current approach over using sccache?

I am dubious how much sccache will actually help in practice. I would like to see benchmarks on how much it helps with large workspace if you're planning to only switch to sccache without further changes.

I definitely wanted to run some tests before starting to implement this

@jyn514 @Nemo157 I think this is ready for another round of checks.
It would be awesome to have your feedback on what might be missing, from my side it's relatively complete.
I'm not 100% certain about the disk-space safeguard, typically cache size limits are configured as cache-size, but that would have meant I have to du the whole cache directory each time.


Fetch & store Pull Request and related data

This should include:

Comments (with emoji!)
Users involved
Diff of the code

It should be idempotent (ie. it should allow to refresh the data when you run it once)
Use a JSON column to store the cleaned up data.
Save timestamps (created/updated at), save source of the data (PR link, repo name).
This is the first model, so the setup should be SQLite for the database.
The decision if we want to crawl the page or use the API is left to the person implementing this feature.

https://gist.github.com/Vadser/6cae9e9bf3d22def1f128ae18ccbdc17


Skype Online Connection Module requires newer Version

The newest version of Skype Online Connection Module now requires PowerShell 5.1 to be installed in order to run.

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

ID: 3117c408-39c5-df82-7238-3e842e953a64
Version Independent ID: 80a85e4e-a1b3-68a7-bb9c-544925bcb3ef
Content: Set up your computer for Windows PowerShell
Content Source: Skype/SfbOnline/set-up-your-computer-for-windows-powershell/set-up-your-computer-for-windows-powershell.md
Service: skype-for-business-online
GitHub Login: @tonysmit
Microsoft Alias: tonysmit

@bnicho02 - thank you for taking the time to provide feedback. I am getting this confirmed and updated. Thanks again, appreciated!

Sorry for long delay. I was able to get this into the backlog for the Skype team. The team will get this prioritized into a sprint plan. Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

Will this be supported through the Azure Cloudshell powershell module?

@c016smith - I found a User Voice with this idea too and upvoted it: https://office365.uservoice.com/forums/273493-office-365-admin/suggestions/32344114-add-cloudshell-like-azure-portal-has-with-all-of

@bnicho02 - I am confirming with support as there might even be new requirements now. Not sure how this slipped through the cracks but I am following up on it now. Sorry for the delay and will keep this open until I get that page mentioned updated.

@kenwith Any updates on this issue? Thanks!

@scanum - yes, the article now has download to PowerShell 5.1. This can be closed now. Thanks for follow up!

@bnicho02  Thank you for submitting this feedback.
From our understanding the issue has been resolved. If you feel it hasn't been resolved please re-open this issue.
@officedocsbot close


Pod name autocompletion does not work for the kubectl logs command

Issue:
When attempting to use the kubectl logs command, the available pods are not displayed.
Steps to reproduce:
With the kube-shell open, type kubectl logs and hit the tab key
Expected Results:
The available pods are displayed in the shell
Observed Results:
Nothing is displayed

@mbangert-smarsh thanks for opening issue. We will work on it.
In general, there are scenarios like 'kubectl logs' which need to be handled case by case (unlike kubeclt get kubectl-resource-name for e.g). I am collecting such scenarios, and make kube-shell at the least compatible with kubectl auto completion. We will fix it next release.

I am having the same issue.. for few people its  working on mac.
I am  using centos    and trying on the master node and it's not   working for me

I am using a centos machine  to run kubectl   and   executing the below  instruction worked for me
`yum install bash-completion
echo 'source <(kubectl completion bash)' >>~/.bashrc
kubectl completion bash >/etc/bash_completion.d/kubectl
echo "alias k='kubectl'" >> ~/.bashrc
echo 'complete -F __start_kubectl k' >>~/.bashrc
source ~/.bashrc `
once it's completed, it  should be  able to get the  response with TAB TAB

got the problem too running inside bash on WSL2/Ubuntu 20.04.2 LTS
i noticed that every once in great while it works
when i just do kubectl logs TAB TAB then i get listed the files in the current dir


update example

As per AHK documentation and  this Reddit thread (and my own tests confirm this as well) AHK has 3 places it looks for library files:
    %A_ScriptDir%\Lib\  ; Local library - requires [v1.0.90+].
    %A_MyDocuments%\AutoHotkey\Lib\  ; User library.
    directory-of-the-currently-running-AutoHotkey.exe\Lib\  ; Standard library.

This pull request would break 2 of these 3 options. Perhaps your current setup differs somehow, that it was necessary to specify ..\Lib ?


Upgrade to 8.1

see https://github.com/conda-forge/sage-feedstock/issues/10 for the issue tracking the dependencies.

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

The test section contained an unexpected subsection name. import is not a valid subsection name.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@isuruf Is CI somehow disabled for this repository?

Currently I get to
Error compiling Cython file:
------------------------------------------------------------
...
    void   pari_err_ROOTS0(const char *f)

# Auto-generated declarations. There are taken from the PARI version
# on the system, so they more up-to-date than the above. In case of
# conflicting declarations, auto_paridecl should have priority.
from .auto_paridecl cimport *
^
------------------------------------------------------------

/home/jule/proj/conda/miniconda3/envs/conda-build-sagelib/conda-bld/sagelib_1521489491380/_h_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehol/lib/python2.7/site-packages/cypari2/paridecl.pxd:5174:0: 'cypari2/auto_paridecl.pxd' not found

We updated Cython yesterday. So might want to check to see if Cython version affects the error (and thus whether it is an upstream issue).

Could you please try pushing again to see if CircleCI comes back now? Tried to fix it.

@jakirkham Thanks for the input. The file is missing on conda and I have it with my local install of cypari2, so I think it's a problem with the conda package.

@jakirkham No, CircleCI still does not do anything unfortunately.

Ah ok. Missed your xref. Sounds reasonable. Would just keep an eye on whether Cython version itself has any effect if the more obvious problems are ruled out.
Thanks for the info. Hmm. Can you please check if CircleCI shows up in your Authorized OAuth Apps in GitHub's Settings?

Yes, CircleCI is there. I also use it all the time.

Could you please try revoking it and readding it? We have in a few cases seen CircleCI gets a little confused for whatever reason and needs a reset to work on other orgs like conda-forge.

@jakirkham I just tried and it does not seem to work. It builds the branch https://circleci.com/gh/saraedum/sagelib-feedstock/1 but it does not show up here. (I guess it's not working in the conda-forge namespace or however that is called in CircleCI parlance.)

So, it built once for "Upgrade sage's dependencies", the second commit on this PR.

Ah ok. Thanks for the info.
CircleCI doesn't normally like to build on a user's fork and an org at the same time. It's a little strange. Disabling CircleCI on your fork and repushing should help.

I only enabled the build for my repo after it did not work just now. But let me try to stop that integration and push again.

Hm…now I also used the linter?

Yeah that was my thought too. 😕
If you look at the CircleCI settings on GitHub, does it actually show itself as enabled for conda-forge?

Looks good to me…

Thanks for providing ideas btw. It's bizarre because it works fine for other projects. I should probably contact CircleCI at some point.

Sorry you are running into this problem.
Yeah that might be best. Out of ideas for now.

Compilation ran through and then it fails with:
+ python -u setup.py install
Traceback (most recent call last):
  File "/opt/conda/bin/conda-build", line 6, in <module>
    sys.exit(conda_build.cli.main_build.main())
  File "/opt/conda/lib/python3.6/site-packages/conda_build/cli/main_build.py", line 342, in main
    execute(sys.argv[1:])
  File "/opt/conda/lib/python3.6/site-packages/conda_build/cli/main_build.py", line 333, in execute
    noverify=args.no_verify)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/api.py", line 97, in build
    need_source_download=need_source_download, config=config)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/build.py", line 1524, in build_tree
    config=config)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/build.py", line 1147, in build
    utils.check_call_env(cmd, env=env, cwd=src_dir)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/utils.py", line 628, in check_call_env
    return _func_defaulting_env_to_os_environ(subprocess.check_call, *popenargs, **kwargs)
  File "/opt/conda/lib/python3.6/site-packages/conda_build/utils.py", line 624, in _func_defaulting_env_to_os_environ
    return func(_args, **kwargs)
  File "/opt/conda/lib/python3.6/subprocess.py", line 291, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/bin/bash', '-x', '-e', '/feedstock_root/build_artefacts/sagelib_1522572220102/work/sage-8.1/conda_build.sh']' returned non-zero exit status 1.
+ exit 1
Exited with code 1

Can you remove the redirection to /dev/null in python -u setup.py install > /dev/null 2>&1 so that we can see the actual error?

With the output included, we get:
byte-compiling /feedstock_root/build_artefacts/sagelib_1522612852223/_b_env_placehold_plac************************************************************************
Traceback (most recent call last):
  File "setup.py", line 943, in <module>
    ext_modules = ext_modules)
  File "/feedstock_root/build_artefacts/sagelib_1522612852223/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python2.7/distutils/core.py", line 151, in setup
    dist.run_commands()
  File "/feedstock_root/build_artefacts/sagelib_1522612852223/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python2.7/distutils/dist.py", line 953, in run_commands
    self.run_command(cmd)
  File "/feedstock_root/build_artefacts/sagelib_1522612852223/_b_env_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_placehold_plac/lib/python2.7/distutils/dist.py", line 972, in run_command
    cmd_obj.run()
  File "setup.py", line 874, in run
    self.install_kernel_spec()
  File "setup.py", line 889, in install_kernel_spec
    from sage.repl.ipython_kernel.install import SageKernelSpec
  File "/feedstock_root/build_artefacts/sagelib_1522612852223/work/sage-8.1/src/sage/repl/ipython_kernel/install.py", line 16, in <module>
    from jupyter_core.paths import ENV_JUPYTER_PATH
ImportError: No module named jupyter_core.paths

Looks like jupyter_core is a dependency of sagelib. Can you add it to requirements?

Ok. Build finished, now tests fail:
+ source /opt/conda/bin/activate /feedstock_root/build_artefacts/sagelib_1522657960158/_t_env
+ /feedstock_root/build_artefacts/sagelib_1522657960158/_t_env/bin/python -s /feedstock_root/build_artefacts/sagelib_1522657960158/test_tmp/run_test.py
import: 'sage'
+ /bin/bash -x -e /feedstock_root/build_artefacts/sagelib_1522657960158/test_tmp/run_test.sh
+ sage -v
Error: You must set either the SAGE_LOCAL or SAGE_SCRIPTS_DIR environment variable to run this
Error setting environment variables by sourcing '/feedstock_root/build_artefacts/sagelib_1522657960158/_t_env/bin/sage-env';

Looks like there needs to be a sage-env-config file in $PREFIX/bin

Can you revert https://github.com/conda-forge/sagelib-feedstock/pull/16/commits/7c6ab27e6c829bb659bd99d05c65b3e87047c88b so that we can see the errors?

Sorry, I don't understand. Which logs are missing?

@isuruf I don't really understand how the activation scripts work. recipe/activate/sage-conda-env.py seems to be deactivated at the moment (it's not being run by activate.sh) or am I misunderstanding something here?
I tried to run doctests with SAGE_SPKG_INST=mktemp -d sage -tp src in meta.yml's test section. This did not work because sage apparently did not pick the variable up. What am I missing here? (I know that mktemp -d does not work on OSX but that's a different issue.)

@isuruf Could you have a look at the output of CircleCI/Travis? Does this otherwise look reasonable?

Activation script just sets SAGE_ROOT and SAGE_LOCAL. I tried to do a more advanced acivation using sage-env, but it didn't work.

This did not work because sage apparently did not pick the variable up. What am I missing here?

Are you sure that this works in sage-8.1? Looks like a sage issue to me.

Btw, for the tests you need all of the standard packages in sage-feedstock right?

Sure, I need the dependencies. I just wanted to see whether I could run the tests already like that.

@isuruf Anyway, is this now good to go?


Remove executable bit from Cargo.toml and CHANGELOG.md

I saw this in the only travis job that failed (799.1):
$ rustc --version
error: 'rustc' is not installed for the toolchain 'stable-x86_64-unknown-linux-gnu'

Sorry for the late reply. I restarted the travis job and it was indeed just a temporary failure. Is green now.
The change makes sense to me, no idea why the executable bit was set in the first place.

Commit 542c12c8a1683df6898f73ce64e6534c96c8a9c9 reinstated the execute bit on these files.


Add support for HTTPOption

This PR introduces support for HTTPOption (introduced in https://github.com/knative/networking/pull/415).
Changes

:gift: Add support for HTTPOption
:gift: Introduces a new configuration to specify the name of the http-listener for the gateways
:broom: Cleanup some redundancies in test code
:broom: Use new functions where deprecations were used

The implementation is based on the gateway-api example for redirects: https://github.com/kubernetes-sigs/gateway-api/blob/main/examples/standard/http-redirect.yaml. It was necessary to restructure some code, as two HTTPRoute objects need to be created, each referencing only a specific section in the gateway using sectionName. We should further discuss if we should use that approach also for the "normal" use-case (as we currently bind to all the sections in the gateway only differentiated by the hostname in the TLS case). Also The configuration key visibility seems now a bit off, maybe we can find a better name?
/kind cleanup
/kind enhancement
Fixes #130

/test all

/cc @nak3 , @dprotaso could you please look over this. I'm a bit unsure if this is the way to go.

Also not really sure about this change: https://github.com/knative-sandbox/net-gateway-api/pull/437/commits/663d28b982a2bd2c6f482d33fee9dcf5066b8774. Either unit tests complain about header mismatch (https://github.com/knative-sandbox/net-gateway-api/actions/runs/3949133837/jobs/6759963500#step:7:173) or golangci-lint complains about not preallocating the slice (https://github.com/knative-sandbox/net-gateway-api/actions/runs/3947688057/jobs/6756800214).

/retest

/test integration-tests-istio

Thank you so much, Reto!

It was necessary to restructure some code, as two HTTPRoute objects need to be created, each referencing only a specific section in the gateway using sectionName.

I wondered that upstream gateway-api to improve the two HTTPRoute objects for HTTPS redirection (I believe it is too redundant) and actually there are some on-going discussion:

https://github.com/kubernetes-sigs/gateway-api/issues/1185
https://github.com/kubernetes-sigs/gateway-api/discussions/1360

Once the upstream's latest example httproute-redirect-https.yaml (currently invalid!) work, we can simply implement this feature, can't we?

Interesting, haven't seen that. You are right about the verbosity, I agree there. But the discussion seems also unsure on how to resolve this. Seems like the current stable state is also the last discussed state (https://github.com/kubernetes-sigs/gateway-api/issues/1185#issuecomment-1149241414)?
Also I haven't found an issue that is related to the example you linked, so not sure if there is work going in that direction. But I'd be fine to hold this feature here until this is more clear.

Also I haven't found an issue that is related to the example you linked

Hmm...  As far as I tested, it keeps redirecting to HTTPS as explained in https://github.com/kubernetes-sigs/gateway-api/issues/1185 and never reached out to the backendRefs(example-svc). To solve it, it was necessary to create two HTTPRoutes.
Anyway, https://github.com/kubernetes-sigs/gateway-api/issues/1185 was tagged to 0.7.0 milestone so maybe it is better to wait a little bit for the upstream.

/remove-lifecycle stale

As it does not look like upstream gw-api is going to change this behaviour soon (the issue was moved out of GA) and the current redirect behaviour is perceived as stable, let's the current approach another go.
PTAL: @nak3 , @dprotaso

/retest

/assign @nak3
/assign @dprotaso

gentle ping ^^
@nak3 , @dprotaso

Ah, haven't seen that, thanks.
I don't think https://github.com/kubernetes-sigs/gateway-api/issues/1185 is really what we were originally discussing, right? I mean I agree with the argument there in general, but I think your argument for this PR here was that the current redirect configuration is too complex and verbose. If we would want to change that, we might need to open another GEP for it. WDYT?

Let me try to explain.
Yes, my arguments for this PR is too verbose because two HTTPRoutes objects need to be created in spite of same host name.
So, I thought we can combine it as the parentRefs supports multiple refs like:
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
  name: http-1
  namespace: gateway-api-example-ns1
spec:
  parentRefs:
    - name: my-gateway
      sectionName: http
    - name: my-gateway
      sectionName: https
  hostnames:
    - myapp.example.com
  rules:
    - filters:
        - type: RequestRedirect
          requestRedirect:
            scheme: https
    - matches:
        - path:
            type: PathPrefix
            value: /
      backendRefs:
        - name: my-svc1
          weight: 1
          port: 80

However, it does not work as https:// is also redirected to https:// and goes into infinite loop.
The solution was supposed to be simple. Upstream should support the redirect loop protection, which is "if the request is the same, the redirect does nothing" rule which was proposed in https://github.com/kubernetes-sigs/gateway-api/issues/1185.
(And then, the issue/1185 has started more discussion than Knative usecase... So I also wonder that we should apply this PR instead of waiting/driving the https://github.com/kubernetes-sigs/gateway-api/issues/1185 ...)

👍
Hm I think we could go both ways then. Also we are not in a hurry to support this here, as GW-API is lacking other things we'd need to be at feature parity. So we probably are not shipping net-gateway-api for a while anyways.
What is your opinion on this (also in general with regards to net-gateway-api) @dprotaso ?

Error: Consider pre-allocating headerMatchList (prealloc)

We probably do not want to prealloc here, as this will return an empty list instead of nil (which is the default).
/override "Code Style / style / Golang / Lint"

/override "style / Golang / Lint"

@dprotaso I looked at https://github.com/kubernetes-sigs/gateway-api/issues/1185#issuecomment-1962181068 again (and https://github.com/kubernetes-sigs/gateway-api/issues/2455). I don't think they would change the basic set-up for redirects but just prevent endless loops, right?
With that, do we want to go ahead with this PR to allow the http-option feature/test?

A full example of how the created resources look like can be found here: https://gist.github.com/ReToCode/2e4d2b3223752c6f380348ef027c55b3

/override "style / Golang / Lint"

@ReToCode gentle ping when you are back.

@dprotaso @skonto rebased, PTAL.

/hold

HTTP-Option test does not yet work on envoy gateway because of https://github.com/envoyproxy/gateway/issues/2149.
/unhold

HTTP-Option test does not yet work on envoy gateway because of envoyproxy/gateway#2149.
/unhold

hey @ReToCode thanks for flagging this, the issue has been fixed, can we retry the test for Envoy Gateway ?

@arkodg looks great. Thanks for the fix and the ping 👍

@dprotaso gentle ping, should we merge this?


[+] Adopt Contributor Covenant Code of Conduct

 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.You have signed the CLA already but the status is still pending? Let us recheck it.


"reinstall Windows"? Really?

There should be more details about the "If you plan to switch TPMs you should toggle to the new TPM, clear it, and reinstall Windows". The statement that I must reinstall Windows sounds ridiculous.
For example, I've replaced the motherboard in my laptop (new one is just the same) - it feels like this is somewhat similar to replacing the TPM you're talking about. Now I've got weird issues with re-enabling BitLocker protectors, related to TPM. And my TPM.msc just fails to load (TPM Console Error 0x8007007A). I've tried to clear the TPM but it doesn't help. I'm not going to reinstall Windows. I'd better just disable the TPM if Windows is unable to make use of it.

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

ID: 805915dd-11ed-01bb-47b8-7cd715275703
Version Independent ID: 5542a776-c895-b09b-d3eb-54cd8307b202
Content: Troubleshoot the TPM (Windows 10) - Microsoft 365 Security
Content Source: windows/security/information-protection/tpm/initialize-and-configure-ownership-of-the-tpm.md
Product: w10
Technology: windows
GitHub Login: @DulceMontemayor
Microsoft Alias: dansimp

Please forgive my ignorance, you may want to wait for answers from someone who is familiar with this and has got direct experience with TPM usage. Based on the general idea that the TPM acts as an ID key or identifying security component to be read by the encryption subsystem, I would see this as changing a key component if you replace either a mainboard or a TPM, making it unsustainable for the encryption to work as before with the new TPM and also necessitating an OS reinstallation. (Feel free to ignore my comment and wait for a more authoritative answer.)

Also: Please note that this repository is intended for improving the IT Pro documentation pages only. Unless you have got improvement suggestions or would like to point out obvious mistakes in the documentation, you may find it easier to get help by contacting your nearest Microsoft Support tenant directly.

@i3v . did you disabled bitlocker protection before changing the new motherboard.
Also make sure now current TPM have device drivers and working good. Check in device manager.  Also try to format the EFI partition and recreate bcdboot in EFI partition.
Afterwards you retry bitlocker

@RAJU2529 ,
Actually, I agree with @illfated , that this issue is hardly a good place for discussing my particular issue. My original intention was to bring your attention to the "reinstall Windows" statement, which, IMHO, deserves some detailed justification, at least.
But if it could help somehow:

No, I've not disabled the bitlocker protection before changing the motherboard.
TPM looks OK in device manager. It's using Microsoft driver 10.0.18362.693.
This is a legacy (~11 years old) system with no UEFI. (BTW, TPM version is 1.2).
I know that there's a newer BIOS available for this MB. Moreover, the original MB had newer BIOS version. Maybe I'll update it later, but I'd avoid this within the couple of months, just as a sort of precaution - everything works OK except BitLocker, and I don't want to take a chance to accidentally brick this system now.

@i3v. Currently reinstall windows. I never recommend this for simple problems. In mean you take system backup say C drive completely  into single file INSTALL.WIM*  using windows PE bootable usb pendrive.
That file will be reused to install windows within 10 minutes. No need  to reinstall applications and no need to reinstall driver's

@illfated . Today I have succeeded  by integrated  Chrome browser and Microsoft edge browser directly into windows PE wim file , I created latest windows PE 10.0.19546.1000. Made to iso file.  I can able to browse websites very fast with edge browser through windows PE.  Watched YouTube channel
Today I am happy.

@RAJU2529 : That sounds good and neat. Glad you are making progress in advanced use of software tech from Microsoft. Keep up the good work.
@i3v : I can only keep my fingers crossed while waiting for feedback from the MS Docs team to see how they want to make use of your feedback. Maybe it can be forwarded to another department, maybe someone has got alternate or optional feedback for you, I don't know. We will just have to be patient in these times where we are affected by the COVID-19 pandemic and social distancing.

I know that there's a newer BIOS available for this MB. Moreover, the original MB had newer BIOS version. Maybe I'll update it later

Just-in-case:
After all, I've updated my BIOS. Nothing changed - TPM.msc still fails with TPM Console Error 0x8007007A. Clearing TPM changes nothing.
I've created a separate thread for the possible further discussion of the possible fixes/workaround for my specific case here.

Thank you for the update. Your ticket on answers.microsoft.com looks quite appropriate.

A revision attempt is going to be published for this feedback. Thank you for the discussion.

@joinimran ,
Thanks for your answer, but...

OK, I understand that the "Endorsement Key" embedded into the TPM chip cannot be changed, once created. And that it must be created before Bitlocker would be able to use the TPM, as mentioned here. And that changing the hardware breaks the pair (thus one must disable Bitlocker in advance or use some backup key to unlock the disk after the MB change). But I do not understand how this limits my ability to re-initialize (I'm not sure if this is the correct word) the software thing, the Bitlocker.

When I started this thread, I thought that Bitlocker was unable to use my TPM. I don't actually remember why I thought so. Today I was able to successfully perform manage-bde -protectors -add c: -TPMAndPIN (just after enabling corresponding feature in gpedit.msc and doing gpupdate /force, nothing else... I'm not sure what was wrong before...). Now the PIN works. AFAIU, this means that Bitlocker is able to use my TPM, even after I've replaced my MB and not re-installed Windows (still v1909, no feature updates since then). Thus, AFAIU, this means that the statement that one must reinstall Windows is not true.

The TPM.msc still fails to load (still 0x8007007A). I think that's some separate bug, actually...

It's interesting that this issue is both "Closed" and "in progress" now.
The article itself was not updated anyhow yet.
Personally, I still think that " you have to reinstall the Windows" is incorrect.

@i3v It has been verified by an independent contributor that Windows needs to be reinstalled and this is why the article has not been updated: an explanation has been provided instead.

@e0i ,
OK... So, any idea why everything works for me without reinstalling Windows?


Fixed bug

Short description outlining key changes/additions
Bug fix
JIRA Ticket Number
IDVA6-1293
Type of change

[x] Bug fix
[ ] New feature
[ ] Breaking change
[ ] Infrastructure change

Pull request checklist

[ ] I have added unit tests for new code that I have added
[ ] I have added/updated functional tests where appropriate
[ ] The code follows our coding standards

An exhaustive list of peer review checks can be read here

CI: Security warnings found!


Cannot connect with user@host

Same issue as described in https://github.com/wrouesnel/postgres_exporter/issues/325.
2020-01-25T00:49:40.825790365Z time="2020-01-25T00:49:40Z" level=error msg="Error opening connection to database (postgresql://exporter%!d(MISSING)atabase:PASSWORD_REMOVED@databasehost/?sslmode=disable): pq: Invalid Username specified. Please check the Username and retry connection. The Username should be in <username@hostname> format." source="postgres_exporter.go:1474"

Tried in quotes/out of quotes/%40 instead of @.
I am using the prometheus-postgres-exporter helm chart.

I faced the same issue. I refactored the helm chart a bit to inject the envvar "DATA_SOURCE_NAME" as value a passed the connection string in following format:  host=host user=user@domain password=secret dbname=postgres sslmode=require


debezium connector cannot be interrupted while performing long-running initial snapshot

when debezium connector is performing long-running initial snapshot, stopping the connector via synchdb_stop_engine_bgw() will not be able to properly shutdown the connector until the initial snapshot is done

we may need to have a way in synchdb to get the current working status of debezium while it appears to be "hanging"


Make it actually work

it's done by @danioso. I just created the pull request.

@papnkukn Any reason this wasn't merged?

?

Why didn't you accepted this pull request ? It's solved a problemm to create QR codes.

@danioso thanks for contributing

Great. Thank you @papnkukn and @danioso..


Kademlia

I am reporting:

[ ] a bug or unexpected behavior
[] general feedback
[ ] feature request
[x] security issue

Bug Report
Please give us details about your installation to assist you. Run dat -v to see the version of Dat you are using.

Operating system:
Node Version:
Dat Version: 13.10.0

I read the whitepaper and since I understand Dat using original Kademlia design then how Dat handles number of attacks such as DDOS or sybil and/or churn?

We use kademlia as one discovery method for connection candidates. But then the protocol itself uses the public key (in the dat:// link) to verify the integrity of data being received. Dat is messaged based (protocol buffers) and uses UTP or TCP as the transport protocols. We opt for UTP, which has better DDOS protection than say HTTPS by default due to less statefulness.
One attack is that someone could spam fake entries in the DHT therefore making it difficult to find valid peers, so thats why we have a modular design in regard to discovery methods. Currently Dat also uses a set of DNS servers in addition to the DHT for peer discovery.

Why not S/Kademlia ?

Yes it would be interesting to see other approaches. I believe S/Kademlia describes the general idea of signing DHT entries but does not specify it as a RFC, and I do not believe there is an implementation in JavaScript. However if you know of one you can implement other providers by adding them to this module https://github.com/maxogden/discovery-channel. You could take the Dat keypair and use the S/Kademlia signature schemes.

SKademlia - Practicable Approach Towards Secure Key Based Routing.pdf

@pfrazee I would like your opinion on this.

I don't hold a strong opinion yet on the right solution. We're researching different things, not just around security, but also privacy and reliability. SKademlia should be one of the things we look at.


"Double click selection" should stick to the "variable name" pattern

My main issue is with the character "$", currently when trying to select $myVar the double click only select myVar.
This is uber annoying since i'm used to call my variable like this.
Moreover when editing php scripts it gets more difficult to avoid this issue.
Overall, the double click selection should stick to the variable name pattern of the current language if possible, or accept the $ in the word, at least.

This looks like a duplicate of https://github.com/atom/language-php/issues/43. As mentioned in that issue, you can change the set of non-word characters locally for each language (in your config), and it's possible to change the per-language default (which is what that issue is asking). Can you add a comment there? Thanks!


save perpective in Azure Analysis Services

Issue when saving perpective, return error about version of SQL server

Are you using the Basic pricing tier of Azure Analysis Services? Keep in mind that Perspectives is an Enterprise feature, and as such, it is only available in the Developer (D1) or Standard (S0+) tiers.


Fix sporadical kubernetes exception listing resources

@kornys can I ask for a bit more commentary on PRs please?  Explain what was wrong and the briefly intent of the fix.  Nothing lengthy is required - just the key points.  It speeds the review.  If the fix is addressing an exception, please include it too.  It helps if we see a problem again or explaining issues from test runs against older branches of the code.

@k-wall so on real cluster sometimes fabric8 client failed on listing resources (addresses) from all namesspaces or from one namespace, so I added try block to allow continue on checking addresses when fabric8 client fails on list resources.

@enmasse-ci run tests profile=smoke


Add timing code

This PR adds code that times regraph with rebuilding compared to regraph with upwards merging. It was taken from the original repo, https://github.com/oflatt/time-regraph

(Not ready to merge until it runs smoothly on the nightlies and I get it reviewed)

@pavpanchekha should I move the stuff in exprs somwhere else? Maybe a separate repo?
Note the timing code does just clone herbie right now to rely on the precomputation in the egraph


Fix README

The configuration example contains a small typo in CSVKWARGS. In addition, Poetry threw an error because the path to the README was incorrect.

Hi.  Thanks for this.  I actually maintain README.org but export to markdown before publishing because I believe PyPI only understands markdown.  Since I’ve been publishing by hand until now I do the conversion manually as well.  I’ll figure out the best way to add this to the build script and fix the typo.  Thanks again for the heads up.

Thank you for the quick review. In the meantime, I just created a dummy file. This was the error message I was getting when running poetry install:
  FileNotFoundError

  [Errno 2] No such file or directory: '/path/to/csv-reconcile/README.md'

  at ~/.pyenv/versions/3.7.10/lib/python3.7/pathlib.py:1063 in _opener
      1059│         raise ValueError("I/O operation on closed path")
      1060│
      1061│     def _opener(self, name, flags, mode=0o666):
      1062│         # A stub for the opener argument to built-in open()
    → 1063│         return self._accessor.open(self, flags, mode)
      1064│
      1065│     def _raw_open(self, flags, mode=0o777):
      1066│
      1067│         Open the file pointed by this path and return a file descriptor,

Great.  I did have a look at this and the short term fix was to add a build step which just writes a dummy file.  The alternative is require a dependency like pandoc to do the conversion or to use markdown directly.  On the one hand I’d like to keep the build simple and on the other I’m stubborn.  :)
I think I will add build and release steps but that will require using poethepoet.  I’ll add something to the doc on how to build.

FWIW, the doc has been updated.  I hope the instructions are clear.  Please let me know if they are not.  The extra build step simply creates a dummy file for now.


gshell 2.6.5 build fails with jline 2.10

hi,
gshell 2.6.5 build fails with jline 2.10
[ERROR] /builddir/build/BUILD/gshell-2.6.5/gshell-util/src/main/java/org/sonatype/gshell/util/io/PromptReader.java:[46,15] error: no suitable constructor found for ConsoleReader(InputStream,PrintWriter,Terminal)
[ERROR]     constructor ConsoleReader.ConsoleReader(String,InputStream,OutputStream,Terminal,String) is not applicable
(actual and formal argument lists differ in length)
constructor ConsoleReader.ConsoleReader(String,InputStream,OutputStream,Terminal) is not applicable
(actual and formal argument lists differ in length)
constructor ConsoleReader.ConsoleReader(InputStream,OutputStream,Terminal) is not applicable
(actual argument PrintWriter cannot be converted to OutputStream by method invocation conversion)
constructor ConsoleReader.ConsoleReader(InputStream,OutputStream) is not applicable
(actual and formal argument lists differ in length)
constructor ConsoleReader.ConsoleReader() is not applicable
(actual and formal argument lists differ in length)
/builddir/build/BUILD/gshell-2.6.5/gshell-util/src/main/java/org/sonatype/gshell/util/io/InputPipe.java:[80,19] error: cannot find symbol
thanks
regards
p.s. the jline2 groupId was changed from org.sonatype.jline to  jline

finally (years later) got around to updating gshell to latest jline3 as well as other modernization updates.


Added my project Whos that Pokemon

You can also contribute as a beginner to Hacktoberfest2023
You can also checkout our Idea-Arca, the project idea bank for any languages, for open-source contributions.
Happy Contributing season!
Keep up the good work!


Strange selection behavior in markdown editor

Testing #19089
In the example below, double clicking at this cursor position results in an odd selection behavior where the bracket on the previous line gets selected

Closing as a duplicate of #18494 since is behavior is another symptom of using the standard word range definition.


docs: add proposal for producing supply chain metadata for all ratify assets

Description
What this PR does / why we need it:
This pull request introduces significant changes to the docs/proposals/Release-Supply-Chain-Metadata.md file, outlining a comprehensive plan for improving the integrity and verifiability of Ratify's release assets. Key changes include proposals for signing all container images and binaries, generating Software Bill of Materials (SBOMs) for all assets, and publishing provenance information for each binary. The changes are organized into two stages of implementation and a future "to be determined" stage.
Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Fixes #
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

[ ] Test A
[ ] Test B

Checklist:

[ ] Does the affected code have corresponding tests?
[ ] Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
[ ] Does this introduce breaking changes that would require an announcement or bumping the major version?
[ ] Do all new files have appropriate license header?

Post Merge Requirements

[ ] MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

Thanks Akash, LGTM.
One minor details for the Q&A. "Do we need to publish the same artifacts as referrers as well or is it sufficient to use docker buildx attestations? Ratify will consider this in the future as need arises."
Could you remind us the reason to implement buildx attestations over referrers. thanks!

Buildx attestations are used in other OSS projects while referrers for the same content is not adopted in other larger projects. That's the only reason why to start with buildx attestations over referrers.


Issue running wide_resnet model

When I run python3 train.py I get the error :
File "train.py", line 234, in
main()
File "train.py", line 230, in main
train_model(args, model, train_loader, val_loader)
File "train.py", line 95, in train_model
tr_loss, tr_prec1 = train_epoch(train_loader, model, criterion, optimizer, epoch, args)
File "train.py", line 123, in train_epoch
output = model(input_var)
File "/home/sammer/.local/lib/python3.5/site-packages/torch/nn/modules/module.py", line 224, in call
result = self.forward(*input, **kwargs)
File "/home/sammer/fitting-random-labels/model_wideresnet.py", line 98, in forward
out = self.forward_repr(x)
File "/home/sammer/fitting-random-labels/model_wideresnet.py", line 103, in forward_repr
out = self.block1(out)
File "/home/sammer/.local/lib/python3.5/site-packages/torch/nn/modules/module.py", line 224, in call
result = self.forward(*input, **kwargs)
File "/home/sammer/fitting-random-labels/model_wideresnet.py", line 50, in forward
return self.layer(x)
File "/home/sammer/.local/lib/python3.5/site-packages/torch/nn/modules/module.py", line 224, in call
result = self.forward(*input, **kwargs)
File "/home/sammer/.local/lib/python3.5/site-packages/torch/nn/modules/container.py", line 67, in forward
input = module(input)
File "/home/sammer/.local/lib/python3.5/site-packages/torch/nn/modules/module.py", line 224, in call
result = self.forward(*input, **kwargs)
File "/home/sammer/fitting-random-labels/model_wideresnet.py", line 29, in forward
out = self.conv1(self.equalInOut and out or x)
File "/home/sammer/.local/lib/python3.5/site-packages/torch/autograd/variable.py", line 123, in bool
torch.typename(self.data) + " is ambiguous")
RuntimeError: bool value of Variable objects containing non-empty torch.cuda.FloatTensor is ambiguous
It is strange since i could run the mlp model without problems; Is there a fix for this issue ?

Can you try to replace line 29 in model_wideresnet.py which is
out = self.conv1(self.equalInOut and out or x)

by the following:
if self.equalInOut:
  out = self.conv1(out)
else:
  out = self.conv1(x)

and see if it resolves the issue?

Thanks for the comment. However, the changes did not helped. I tried to replace the code 29 in model_wideresnet.py as you suggested, but now another error pops up in line 37 (same error).
Can you clarify your pytorch and python version?

The original code was written for Python2. I have just pushed a fix for Python 3. Can you try it? I have tried it locally, with Python 3.6.3 and pytorch 0.3.0 it is running without issue.

Thank you, it is working!


Various improvements

CachyKit will now support:

URLRequest with additional headers and other settings. Previously was only referring to a new URLRequest created inside the load method getting its url even though the load method was accepting a urlRequest as a parameter.
Archiving now works correctly after supporting optional secure coding for disk saving
configure method is now accessible outside of the CachyKit pod and is now matching the documentation
Code documentation improved
Readme updated

@d4r1091 merged

Thanks, @Sadmansamee 🙌 - can you please push a new release with these changes? So that I won't need to specify the :branch => master in my Podfile


extend test suite

we now at least test one device per vendor in the SVD database
cc #45

@homunkulus r+

:pushpin: Commit 90ffa4e has been approved by japaric

:hourglass: Testing commit 90ffa4e with merge 90ffa4e...

:broken_heart: Test failed - status-travis

@homunkulus r+

:pushpin: Commit 1ca0769 has been approved by japaric

:hourglass: Testing commit 1ca0769 with merge 1ca0769...

@homunkulus r+

:pushpin: Commit 058330d has been approved by japaric

:hourglass: Testing commit 058330d with merge 058330d...

@homunkulus r+

:pushpin: Commit f82b05d has been approved by japaric

:hourglass: Testing commit f82b05d with merge f82b05d...

:broken_heart: Test failed - status-travis

@homunkulus r+

:pushpin: Commit 9d190f0 has been approved by japaric

:hourglass: Testing commit 9d190f0 with merge 9d190f0...

:sunny: Test successful - status-appveyor, status-travis
Approved by: japaric
Pushing 9d190f05765adb4aa7e4f51c63a084c22501cdef to master...


sizeMapping Not Working

I've implemented this library, but the sizeMapping is ignored. On mobile, I'm still getting desktop size ads, and on desktop, sometimes I'll get mobile size ads.
Can anyone verify that sizeMapping works?
I've even tried copying and pasting the example code into mine with the same results.

same issue

did you find any alternative?

Nope. I had to write my own code for now until we rip out this library completely.

Nope. I had to write my own code for now until we rip out this library completely.

if it;s working can you share your librarry?

I don't have a library. I have some random code that's custom to the project I was on. It's not sharable unfortunately.


slightly "Improve" human readability of start-up script logs

GCP likes to be difficult and appears that setup intermittently "takes too long" and cml runner believes something failed and terminates the instance thus failing workflows.
I have anecdotally found the issue to be most predominate during the PST morning on us-west datacenters.
This being a "first step" in more easily narrowing the repeat offenders /cough sudo curl https://amazon-ecr-credential-helper-releases.s3.us-east-2.amazonaws.com/0.5.0/linux-amd64/docker-credential-ecr-login --output /usr/bin/docker-credential-ecr-login

Alternatively, PS4='tpi:setup.sh: '; set -x and fi | sed "s/^/$PS4 /"

Alternatively, PS4='tpi:setup.sh: '; set -x and fi |& sed "s/^/$PS4 /"

that is arguably cleaner

giving it a try

Does one ever master bash-fu?

I don't think so.

On a side note, I Iike that eval is where you draw the line, but didn't somebody recently say friends don't let friends curl | sh I see two cases pretty close by 🤔 😇


Any settings for background and text colors?

The modern_dark color does not reflect the one used by my current theme.

Standard colors are used for Windows 11, Windows 10, and system colors for the time being. In the next update, the colors of the Windows theme will be applied.
To change the colors to a favorite color, use the following code:
default {
    item-text = [#fff, #fff]
    item-back = [#000, #333]
    separator-color = color.accent
    frame-color = color.accent
    symbol = [color.accent, color.accent]
}

Nice! Thank you.


[1.19] Crash when opening chest

Forge 41.0.109
indestructibletools-2022.2
Started a new world, went to right click on a spawn chest and immediately crashed with this error:
Exception caught during firing event: 'net.minecraft.world.entity.player.Player net.minecraftforge.event.entity.player.PlayerInteractEvent$RightClickBlock.getPlayer()
crashlog

Hey,
thanks for reporting the issue. I was able to reproduce it.
Do you need a fix for 1.19 or is 1.19.1 also OK?


More advanced ls aliases

Used more advanced ls aliases from: http://tldp.org/LDP/abs/html/sample-bashrc.html
Original ls remains unaliased (--> better if other programs depend on it)
Removed unneeded -if [ $(uname) = "Linux" ] that prevents colored ls output on OS X
--> tested on Linux and OS X wit coreutils

When I run this on OS X, I get an error that the --color option is not supported:
$ l
ls: illegal option -- -
usage: ls [-ABCFGHLOPRSTUWabcdefghiklmnopqrstuwx1] [file ...]

Thanks for checking. So we have to differ between two cases:

OS X native --> color not supported
OS X with coreutils, Linux --> color supported

I'll provide an update that takes care of that.

That would be fantastic - thanks!

I think in the stock OS X version of ls, one has to use -G for adding color to the output. The current version of the aliases redefine ls as ls -G to achieve this.
My environment also has LSCOLORS=Gxfxcxdxdxegedabagacad to define the colors to be used.

It should now correctly differentiate between:

Linux
Darwin
Darwin with coreutils ls bin and path set

The LSCOLORS seems to be already present here.
Could you verify that it works, again? thx

I see your points.
I already thought about whether a dedicated "advanced ls" alias module would be more meaningful than changing the general module that some people might be used to. After our discussion I think a separate module for Linux/coreutils ls only is the simpler way to go.

Yes, either that, or you could create your own set of aliases in a custom file. The deal breaker here is changing the functionality of ll, I think.


Turnstile

PCX-1182

Looks great!
Small comment here: at first read I was confused at the wording of "interstitial" (it only made sense when I read the line about Managed Challenges) so I'd recommend that be reworded to be a little more clear what it's referring to.


Error while Building tensorflow using cross-tool for aarch64

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): - Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): source trying to build and install for aarch64 (arm64)
TensorFlow version:  1.12.0 (trying to install)
Python version: 3.6
Installed using virtualenv? pip? conda?: NO - virtualenv or pip
Bazel version (if compiling from source): 0.19.0 (tried with new version same issue)
GCC/Compiler version (if compiling from source): - gcc-aarch64-linux-gnu & g++-arch64-linux-gnu
CUDA/cuDNN version: No CUDA or XcuDNN
GPU model and memory:  NO GPU used

Installed bazel - 0.19.0 version
Tensorflow source latest from git
Building in Ubuntu for arm64 bit(aarch64) cpu using cross-tool.
Command for building:
bazel build -c opt //tensorflow/examples/label_image --cpu=aarch64 -- crosstool_top=//tools/aarch64_compiler:toolchain --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --verbose_failures
And here is the error logs:
ERROR: /home/cmp/.cache/bazel/_bazel_root/b7eb2acccd1b56cb3e56479bb5f07f48/external/mkl_dnn/BUILD.bazel:71:1: C++ compilation of rule '@mkl_dnn//:mkldnn_single_threaded' failed (Exit 1): aarch64-linux-gnu-gcc failed: error executing command
(cd /home/cmp/.cache/bazel/bazel_root/b7eb2acccd1b56cb3e56479bb5f07f48/execroot/org_tensorflow &&
exec env -
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
PWD=/proc/self/cwd
PYTHON_BIN_PATH=/usr/bin/python3.6
PYTHON_LIB_PATH=/usr/lib/python3.6
TF_DOWNLOAD_CLANG=0
TF_NEED_CUDA=0
TF_NEED_OPENCL_SYCL=0
TF_NEED_ROCM=0
/usr/bin/aarch64-linux-gnu-gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++11' -MD -MF bazel-out/aarch64-opt/bin/external/mkl_dnn/objs/mkldnn_single_threaded/jit_avx512_core_x8s8s32x_conv_kernel.d '-frandom-seed=bazel-out/aarch64-opt/bin/external/mkl_dnn/objs/mkldnn_single_threaded/jit_avx512_core_x8s8s32x_conv_kernel.o' -iquote external/mkl_dnn -iquote bazel-out/aarch64-opt/genfiles/external/mkl_dnn -iquote bazel-out/aarch64-opt/bin/external/mkl_dnn -iquote external/bazel_tools -iquote bazel-out/aarch64-opt/genfiles/external/bazel_tools -iquote bazel-out/aarch64-opt/bin/external/bazel_tools -isystem external/mkl_dnn/include -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/include -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/include -isystem external/mkl_dnn/src -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src -isystem external/mkl_dnn/src/common -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src/common -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src/common -isystem external/mkl_dnn/src/cpu -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src/cpu -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src/cpu -isystem external/mkl_dnn/src/cpu/gemm -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src/cpu/gemm -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src/cpu/gemm -isystem external/mkl_dnn/src/cpu/xbyak -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src/cpu/xbyak -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src/cpu/xbyak -fexceptions '-DMKLDNN_THR=MKLDNN_THR_SEQ' -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE="redacted"' '-D__TIMESTAMP_="redacted"' '-D__TIME__="redacted"' -c external/mkl_dnn/src/cpu/jit_avx512_core_x8s8s32x_conv_kernel.cpp -o bazel-out/aarch64-opt/bin/external/mkl_dnn/_objs/mkldnn_single_threaded/jit_avx512_core_x8s8s32x_conv_kernel.o)
In file included from external/mkl_dnn/src/cpu/cpu_isa_traits.hpp:35:0,
from external/mkl_dnn/src/cpu/jit_generator.hpp:21,
from external/mkl_dnn/src/cpu/jit_avx512_core_x8s8s32x_conv_kernel.hpp:23,
from external/mkl_dnn/src/cpu/jit_avx512_core_x8s8s32x_conv_kernel.cpp:23:
external/mkl_dnn/src/cpu/xbyak/xbyak_util.h:84:21: fatal error: cpuid.h: No such file or directory
compilation terminated.
Target //tensorflow/examples/label_image:label_image failed to build
INFO: Elapsed time: 49.893s, Critical Path: 10.85s, Remote (0.00% of the time): [queue: 0.00%, setup: 0.00%, process: 0.00%]
INFO: 194 processes: 194 local.
FAILED: Build did NOT complete successfully

Thank you for your post. We noticed you have not filled out the fields in the issue template. Could you update them if they are relevant in your case, or leave them as N/A? Along with the template, please provide as many details as possible to find the root cause of the issue. Thanks!

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): - Ubuntu 16.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): source trying to build and install for aarch64 (arm64)
TensorFlow version:  1.12.0 (trying to install)
Python version: 3.6
Installed using virtualenv? pip? conda?: NO - virtualenv or pip
Bazel version (if compiling from source): 0.19.0 (tried with new version same issue)
GCC/Compiler version (if compiling from source): - gcc-aarch64-linux-gnu & g++-arch64-linux-gnu
CUDA/cuDNN version: No CUDA or XcuDNN
GPU model and memory:  NO GPU used

Installed bazel - 0.19.0 version
Tensorflow source latest from git
Building in Ubuntu for arm64 bit(aarch64) cpu using cross-tool.
Command for building:
bazel build -c opt //tensorflow/examples/label_image --cpu=aarch64 -- crosstool_top=//tools/aarch64_compiler:toolchain --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --verbose_failures
And here is the error logs:
ERROR: /home/cmp/.cache/bazel/_bazel_root/b7eb2acccd1b56cb3e56479bb5f07f48/external/mkl_dnn/BUILD.bazel:71:1: C++ compilation of rule '@mkl_dnn//:mkldnn_single_threaded' failed (Exit 1): aarch64-linux-gnu-gcc failed: error executing command
(cd /home/cmp/.cache/bazel/bazel_root/b7eb2acccd1b56cb3e56479bb5f07f48/execroot/org_tensorflow && exec env - PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin PWD=/proc/self/cwd PYTHON_BIN_PATH=/usr/bin/python3.6 PYTHON_LIB_PATH=/usr/lib/python3.6 TF_DOWNLOAD_CLANG=0 TF_NEED_CUDA=0 TF_NEED_OPENCL_SYCL=0 TF_NEED_ROCM=0 /usr/bin/aarch64-linux-gnu-gcc -U_FORTIFY_SOURCE -fstack-protector -Wall -Wunused-but-set-parameter -Wno-free-nonheap-object -fno-omit-frame-pointer -g0 -O2 '-D_FORTIFY_SOURCE=1' -DNDEBUG -ffunction-sections -fdata-sections '-std=c++11' -MD -MF bazel-out/aarch64-opt/bin/external/mkl_dnn/objs/mkldnn_single_threaded/jit_avx512_core_x8s8s32x_conv_kernel.d '-frandom-seed=bazel-out/aarch64-opt/bin/external/mkl_dnn/objs/mkldnn_single_threaded/jit_avx512_core_x8s8s32x_conv_kernel.o' -iquote external/mkl_dnn -iquote bazel-out/aarch64-opt/genfiles/external/mkl_dnn -iquote bazel-out/aarch64-opt/bin/external/mkl_dnn -iquote external/bazel_tools -iquote bazel-out/aarch64-opt/genfiles/external/bazel_tools -iquote bazel-out/aarch64-opt/bin/external/bazel_tools -isystem external/mkl_dnn/include -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/include -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/include -isystem external/mkl_dnn/src -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src -isystem external/mkl_dnn/src/common -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src/common -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src/common -isystem external/mkl_dnn/src/cpu -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src/cpu -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src/cpu -isystem external/mkl_dnn/src/cpu/gemm -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src/cpu/gemm -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src/cpu/gemm -isystem external/mkl_dnn/src/cpu/xbyak -isystem bazel-out/aarch64-opt/genfiles/external/mkl_dnn/src/cpu/xbyak -isystem bazel-out/aarch64-opt/bin/external/mkl_dnn/src/cpu/xbyak -fexceptions '-DMKLDNN_THR=MKLDNN_THR_SEQ' -fno-canonical-system-headers -Wno-builtin-macro-redefined '-D__DATE="redacted"' '-D__TIMESTAMP_="redacted"' '-D__TIME__="redacted"' -c external/mkl_dnn/src/cpu/jit_avx512_core_x8s8s32x_conv_kernel.cpp -o bazel-out/aarch64-opt/bin/external/mkl_dnn/_objs/mkldnn_single_threaded/jit_avx512_core_x8s8s32x_conv_kernel.o)
In file included from external/mkl_dnn/src/cpu/cpu_isa_traits.hpp:35:0,
from external/mkl_dnn/src/cpu/jit_generator.hpp:21,
from external/mkl_dnn/src/cpu/jit_avx512_core_x8s8s32x_conv_kernel.hpp:23,
from external/mkl_dnn/src/cpu/jit_avx512_core_x8s8s32x_conv_kernel.cpp:23:
external/mkl_dnn/src/cpu/xbyak/xbyak_util.h:84:21: fatal error: cpuid.h: No such file or directory
compilation terminated.
Target //tensorflow/examples/label_image:label_image failed to build
INFO: Elapsed time: 49.893s, Critical Path: 10.85s, Remote (0.00% of the time): [queue: 0.00%, setup: 0.00%, process: 0.00%]
INFO: 194 processes: 194 local.
FAILED: Build did NOT complete successfully

@TropSpirit One thing I quickly noticed is version of Bazel. Please check the test build configuration here. DO you mind downgrading Bazel to 0.15.0 and test whether the error is same or not. Meanwhile I will also take a deeper look at the issue. Thanks!

I tried using bazel 0.15.0 for crosscompiling still same error. i even tried tensorflow 1.8 and bazel 0.10.0
$ bazel build -c opt //tensorflow/examples/label_image --cpu=aarch64 --crosstool_top=//tools/aarch64_compiler:toolchain --host_crosstool_top=@bazel_tools//tools/cpp:toolchain --verbose_failures
_ERROR: /home/cmp/.cache/bazel/bazel_nshivash/a20291383e693f326d5a9bf14cdd7b80/external/nsync/BUILD:466:13: Configurable attribute "copts" doesn't match this configuration (would a default condition help?).
Conditions checked:
@nsync//:android_arm
@nsync//:android_arm64
@nsync//:android_armeabi
@nsync//:android_x86_32
@nsync//:android_x86_64
@nsync//:clang_macos_x86_64
@nsync//:freebsd
@nsync//:gcc_linux_aarch64
@nsync//:gcc_linux_ppc64
@nsync//:gcc_linux_s390x
@nsync//:gcc_linux_x86_32_1
@nsync//:gcc_linux_x86_64_1
@nsync//:gcc_linux_x86_64_2
@nsync//:ios_x86_64
@nsync//:msvc_windows_x86_64
ERROR: Analysis of target '//tensorflow/examples/label_image:label_image' failed; build aborted:

Any update on this ?

i have the same issue.. is there a way around?

Hi, I had the same issue. It seems to be solved with this flag in the baze build command:
bazel build --define tensorflow_mkldnn_contraction_kernel=0 ...

@AlbertoLanaro Thanks for the solution. @TropSpirit and @NKucza Could you both try the solution? Thanks!

Sorry for the slow response! We don't officially support aarch64 linux builds (we don't have continuous integration, etc set up to catch these sort of issues, so it's hard to offer a great experience) but the suggestions for disabling MKL in this case make sense. Closing since that seems like a fix.


Tutorial link is broken again

I noticed this same link was broken before in issue #3155 but it's broken again.
It's under "Third party tutorials" - Code highlighting in React using Prism.js

It seems it is now a proper redirect, which leads to https://reemus.dev/article/code-highlighting-in-react-using-prismjs


Provide spring-boot support

Spring boot starter
Make dozer work within spring-boot as a first-class-citizen

@garethahealy could you provide some details what exactly should be supported by dozer spring boot starter module? (bean creation, properties configuration etc..)

@vadeg ; i'd expect the first version to just provide support;
i.e.: @DozerMapperAutoConfiguration
which would create a default mapper. once thats done, we can build on other bits.
If you are interested in committing, that would be great.

@garethahealy yes, I am interested :) Thank you for explanation!

@vadeg ; if you are happy to commit, i am happy to review/merge :)


Implement POC for planner of pipedv1

What this PR does / why we need it:
This PR provides POC implementation for the Planner of pipedv1 (piped side). The logic of building plan as follow
// The strategy determination logic is based on the following order:
//   - Direct trigger via web console
//   - Force quick sync if there is no pipeline specified
//   - Force pipeline if the `spec.planner.alwaysUsePipeline` was configured
//   - CommitMatcher ensure pipeline/quick sync based on the commit message
//   - Force quick sync if there is no previous deployment (aka. this is the first deploy)
//   - Based on PlannerService.DetermineStrategy returned by plugins

Which issue(s) this PR fixes:
Part of #4980
Does this PR introduce a user-facing change?:

How are users affected by this change:
Is this breaking change:
How to migrate (if breaking change):

Close due to interface changed :ok:


feat: 🎸 get creation date of ConfidentialAsset

Description
adds method to get createdAt for ConfidentialAsset
Breaking Changes
Requires SubQuery version with eventIdx added to ConfidentialAssets related entities
JIRA Link
https://polymesh.atlassian.net/browse/DA-1033
Checklist

[x] Updated the Readme.md (if required) ?

:tada: This PR is included in version 24.0.0-confidential-assets.5 :tada:
The release is available on:

npm package (@confidential-assets dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update the Social Share Image with দাবির stats

Each of the shares should show the stats of the দাবি to encourage users to come in and vote.
/api/og?petition_id={petition_id} [If Main Image is Available]

/api/og?petition_id={petition_id} [If Main Image is Not Available]

Redoing it with Cloudflare Headless Browser API as Vercel/OG doesn't support Bengali Language.


Cluster splitting from TemplateFeatureView

In many instances, it is much easier to split a cluster on the TemplateFeatureView than on the FeatureView. It would be great if the polygon could be drawn on the TemplateFeatureView as well (now it is only possible on the FeatureView).

On a related note:
Is it possible to have the possibility of drawing connected lines instead of polygons?
The end result would be the same, but the issue with the current method is that the polygon is closed from the beginning which makes it very counterintuitive to create fine polygons.
What I am proposing is that for each click a line connecting the last point with the new one is formed, but the polygon remains open until you click again on the first node.

I also have found instances where splitting appears to be straightforward in the TemplateFeatureView. Here is a screenshot of one:

There are many spikes assigned to the red cluster which appear to fit better with the blue cluster (or maybe with both) in the TemplateFeatureView. I don't see a similar boundary in the FeatureView.

I've noticed this as well and would be a third person to support splitting in the TemplateFeatureView.

done in dev branch


Create SQL Connection

This creates a SQL connection object used to connect database to algorithm and frontend

Looks good to me. We need to think about passing in the details to create a config file to pass in the parameters for the connection. We can't be putting it in code text. For the next sprint, we need to create the config file.


Espresso tests for testing upload with multilingual descriptions

Summary:
It would be nice to automatically test uploads with multilingual descriptions. The user can click on the (+) button to add a description in another language.

IMO, there are two things that need to be tested here.

test that verifies that the user is able to enter descriptions in multiple languages.
test that verifies that an image with multiple descriptions is queued for upload.

Is it still open? , I would like to work on it.

@KaveriKR I have already started working on it. :)


每次都提示 componentWillReceiveProps has been renamed， 大佬们能更新下不

Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.

Move data fetching code or side effects to componentDidUpdate.
If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run npx react-codemod rename-unsafe-lifecycles in your project source folder.

Please update the following components: Dialog

i'm afraid this library is not maintained anymore, last commit 1 year ago :cry:


The sent input is invalid

I am using
documents4j-client-standalone-1.1.3-shaded.jar
documents4j-server-standalone-1.1.3-shaded.jar
In local machine it's working fine. But once i go on Cloud server(Windows server 2012 R2) with Microsoft word 2016 installed. It's giving the error (sent input file invalid).
Also attached the logs from both side (client and server) for your reference.
client.txt
server.txt

Seems like you are running a different Java version on that server. Ideally, you use a standard Java 11 distribution.

It's working now and that's not because of Java version
After running documents4j-server-standalone-1.1.3-shaded.jar  it is pasting some vbs scripts in temp folder to handle the DOCX/XLSX -> PDF
Inside word_convert vbs file i have updated it from :-
Set wordDocument = wordApplication.Documents.Open(inputFile, False, True, False, "dummy-password-to-avoid-lock")
to :-
Set wordDocument = wordApplication.Documents.Open(inputFile, False, True, False, "")
And it worked.

Good you found out. This seems to be a problem with some versions of MS Word, this is not the first time it is being reported. You can override the scripts on startup using a system property. I should probably remove the script change in the next version again.


Failed to activate the script package,operation not permitted

[Enter steps to reproduce below:]

everytime open atom and active script package even when run atom with administrator permissions.antivirus program has been turned off

Atom Version: 1.3.2
System: windows 7
Thrown From: script package, v3.2.0
Stack Trace
Failed to activate the script package
At EPERM: operation not permitted, write

Error: EPERM: operation not permitted, write
    at Error (native)
    at Object.fs.writeSync (fs.js:663:20)
    at SyncWriteStream.write (fs.js:1981:6)
    at execSync (child_process.js:491:20)
    at Object.<anonymous> (file:///C:/Users/xxx/.atom/packages/atom-script-master/lib/grammar-utils/coffee-script-compiler.coffee:6:10)
    at Object.<anonymous> (file:///C:/Users/xxxj/.atom/packages/atom-script-master/lib/grammar-utils/coffee-script-compiler.coffee:3:1)
    at Module._compile (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .coffee] (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\native-compile-cache.js:50:27)
    at Object.<anonymous> (file:///C:/Users/xxx/.atom/packages/atom-script-master/lib/grammar-utils.coffee:69:15)
    at Object.<anonymous> (file:///C:/Users/xxx/.atom/packages/atom-script-master/lib/grammar-utils.coffee:2:1)
    at Module._compile (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .coffee] (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\native-compile-cache.js:50:27)
    at Object.<anonymous> (file:///C:/Users/xxx/.atom/packages/atom-script-master/lib/grammars.coffee:5:16)
    at Object.<anonymous> (file:///C:/Users/xxx/.atom/packages/atom-script-master/lib/grammars.coffee:4:1)
    at Module._compile (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\native-compile-cache.js:103:30)
    at Object.defineProperty.value [as .coffee] (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\compile-cache.js:208:21)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (C:\Users\xxx\AppData\Local\atom\app-1.3.2\resources\app.asar\src\native-compile-cache.js:50:27)
    at Object.<anonymous> (file:///C:/Users/xxx/.atom/packages/atom-script-master/lib/code-context-builder.coffee:2:14)
    at Object.<anonymous> (file:///C:/Users/xxx/.atom/packages/atom-script-master/lib/code-context-builder.coffee:1:1)

Commands
     -0:11.7.0 script:run (atom-text-editor.editor.is-focused)

Config
{}

Installed Packages
# User
script, v3.2.0

# Dev
No dev packages

Care to try this again with the latest release?

@rgbkrk I'm setting up Script development environment locally (to help you guys with some issues) - got this error whilte trying to start with atom -d, I'll try to see why is this happening, but it would be just great if you have any advice or direction where to start digging =)

@rgbkrk wow, how very stupid of me not to get all of the dependencies :-\ sorry for bothering =(

Hey it's all good! If we're missing dev setup instructions in the README, it would be good to add that in.

I'm getting this error all the time, but i have the ansi-to-html package installed. Had to manually install it because of a NPM error, altough script cannot seem to find it

latest script release seems to be unable to install under windows see:  #815 #846 and #881

@DemersM see my comment on #881


VSCode is taking too long to execute first python test

Type: Bug
VSCode takes too long to execute first python test after refreshing the tests. This time increases quadratically with the number of tests in working directory. A side effect of this is that in repos with large number of tests especially parametrized tests, it drives the CPU consumption of extension host process to 100% and causes VSCode window to freeze. It only works again after reloading the window.

Number of tests
Time taken to run first test (s)

10000
8.6

20000
14.1

30000
46.1

40000
94.6

50000
194.5

60000
344.3

Note that the time taken by the run_adapter script to discover tests is proportional to the number of tests so this issue is in the VSCode UI itself.
Reproducer
Workspace settings:
{
    "python.testing.pytestEnabled": true,
    "python.testing.cwd": "src/python",
}

Directory structure:
.
└── src
    └── python
        ├── __pycache__
        │   ├── test_example.cpython-311-pytest-7.4.3.pyc
        │   └── test_sample.cpython-311-pytest-7.4.3.pyc
        ├── test_example.py
        └── test_sample.py

test_example.py contains:
import pytest

count = 10000

@pytest.mark.parametrize("x", [i for i in range(count)])
def test_parametrize(x):
    pass

test_sample.py contains:
def test_a():
    pass

Steps to reproduce:

Click on refresh tests icon.
Once the test tree loads and test_a is present, click on the run test icon.

VS Code version: Code 1.93.0 (4849ca9bdf9666755eb463db297b69e5385090e3, 2024-09-04T13:02:38.431Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 4.18.0-553.16.1.el8_10.x86_64
Remote OS version: Linux x64 4.18.0-553.16.1.el8_10.x86_64
Remote OS version: Linux x64 4.18.0-553.16.1.el8_10.x86_64
Remote OS version: Linux x64 4.18.0-553.16.1.el8_10.x86_64
Remote OS version: Linux x64 4.18.0-553.16.1.el8_10.x86_64

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i9-12900 (24 x 2419)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabledwebnn: disabled_off

Load (avg)
undefined

Memory (System)
31.70GB (17.77GB free)

Process Argv

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: dev-hyd

OS
Linux x64 4.18.0-553.16.1.el8_10.x86_64

CPUs
Intel(R) Xeon(R) Gold 6142 CPU @ 2.60GHz (32 x 3388)

Memory (System)
376.07GB (135.51GB free)

VM
0%

Extensions (7)

Extension
Author (truncated)
Version

remote-ssh
ms-
0.115.0

remote-ssh-edit
ms-
0.87.0

remote-explorer
ms-
0.4.3

black-formatter
ms-
2024.4.0

debugpy
ms-
2024.12.0

python
ms-
2024.14.1

vscode-pylance
ms-
2024.10.1

This is reproducible in the latest VSCode version i.e. 1.94.2 as well. Another observation: It is only reproducible when using remote SSH but not otherwise.

Hi @eleanorjboyd, are there any plans to take this up? This is a major blocker for us for using VSCode python testing feature as it causes the VSCode window to become unresponsive.