Update Banner for Project Repository

I amlooking to refresh the banner of our project repository to better reflect the project's identity and values. The current banner has served us well, but we believe it's time for a change to keep things fresh and engaging.

I am interested in working on this issue for gssoc 24, could you elaborate on what you would want the new banner to look like?
I have worked with various creative design platforms and can create a good design for the banner.
Kindly assign this to me.

I have created a design, if you like it then you could assign this issue to me and I will add it.

I am interested in working on this issue for gssoc 24, could you elaborate on what you would want the new banner to look like? I have worked with various creative design platforms and can create a good design for the banner.
Kindly assign this to me.

Okay, I will assign it to you.  Actually I don't have any idea on what the banner should look like, I just want the banner to make it pleasing to the eye and simple. Also the design should include the project name and the description, thats all.

 I have created a design, if you like it then you could assign this issue to me and I will add it.

@TanyaSingh103  is the first one who replied so she got the issue, sorry

Hi @jfmartinz
I've created two design, please pick whatever you like and I'll make a pr with that

Number one @TanyaSingh103. Also update the current banner, thanks

You can assign this task to me, would love to contribute under GSSOC'24


Track search results shown to users

To improve the search results we show, we want to record:

the list of results shown, in order
any spelling suggestions made
be able to represent groupings of results (eg, for the new "scoped" manuals searches)

This PR is split into three major sections:
1. Creating the testable code
Commits b3bafd0 and 061dc58 are where some tests are created around functions that do the main work associated with extracting the search results URLs.
2. Inlining the testable code
Commits 1f3eff9, 58707a1, and 58707a1 are where the code that was in a separate module is inlined into the search.js file and a GOVUK.search namespace is created.
3. Tracking the search results and spelling suggestions
Commits f197d7f and f1e9076 are where the tracking gets added.
Story: https://trello.com/c/TBJyZJDp

Closing this briefly. I want to check the naming of these tracking events with Tara.

Thank you for adding some tests to this :+1:. Would you however, be able to structure it more like how we describe in our JavaScript style guide. The big change is your collection of named self executing functions would ideally be exposed methods which are then called in some kind of constructor or init method. Possibly something like:
GOVUK.search = {
  init: function (){
    ...
  },
  extractSearchURLs: function ($searchResults) {
    ...
  },
  extractSearchURL: function (index, element) {
    ...
  },
  trackSearchResultURLs: function () {
    ...
  },
  trackSpellingSuggestion: function () {
    ...
  },
  trackSearchClicks: function (){
    ...
  },
  trackExternalSearchClicks: function (){
    ...
  }
}

@edds I've extracted all of the pre-existing self-executing functions into a single GOVUK.search namespace in 84a2deb. They're not triggered using a single GOVUK.search.init() function. I think this is what you meant, if not please let me know.

This is looking pretty good, though I'll happily defer to @edds on the javascript style stuff.
I think the scoped parameter is the wrong way round: specifically, you're setting it to "true" for results which are "unscoped" (ie, from a search across all of GOV.UK).  I'd expect that to be "false".

Thanks a lot @KushalP, that is exactly what I meant :+1:

@rboulton f11cb58 updates the labelling to use descoped and I've removed the second case to reduce the amount of information we transfer from the user's browser.


Multiple js contexts

We have a requirement to run multiple js threads. I have created two js contexts on the same runtime. When trying to run on the second js context, there is an exception stating that the run time is active on another thread. Do I need to create a runtime for each js thread?

In general JSRT runtimes are rental-threaded, meaning that at any given time, a runtime can only be active on one thread, although you're free to move runtime between threads. If you need to run two js threads concurrently, then yes, you need to create two js runtimes.

Thank you.


Enhance available_date query to support browser-specific filtering

This commit introduces a more precise way to filter features based on their availability date in a specific browser.  The existing available_date query is enhanced to optionally accept a browser prefix, enabling queries like available_date:chrome:2023-01-01..2024-01-01 to find features that became available specifically in Chrome within the given date range.
This addresses a potential inaccuracy in the previous behavior where available_date combined with available_on could include features that were initially released in other browsers. The new syntax provides clarity and flexibility for users to express their search intent more accurately.
Additionally, the ANTLR grammar and visitor code have been updated to handle the new syntax, and the availableDateFilter function has been modified to incorporate the browser-specific filtering logic when applicable.
Other changes:

Added a new None Operator to represent placeholder operators in cases where the children nodes contain a multi-value IR tree. This improves the clarity and flexibility of the intermediate representation.

Fixes #578

Reviewers can try it out on staging: https://website-webstatus-dev.corp.goog/?q=available_date%3Achrome%3A2023-01-01..2024-01-01


Adapt to the Lua Styleguide and introduce OOP

Background

https://github.com/exasol/advanced-analytics-framework/pull/47#discussion_r954668067
https://github.com/exasol/advanced-analytics-framework/pull/47#discussion_r954747010
https://github.com/exasol/advanced-analytics-framework/pull/47#discussion_r954964035
https://github.com/exasol/advanced-analytics-framework/pull/47#discussion_r954696054
https://github.com/exasol/advanced-analytics-framework/pull/47#discussion_r954965747

Shelved.


Enable SPF, DKIM and DMARC mail security features for O(1) Labs Domains

Overview:
In order to protect the integrity of O(1) Labs' mail correspondence and delivery pipeline from spammers who might attempt to spoof or send emails that only appear to come from O(1)'s trusted domain, it makes sense to ensure our mail and DNS host providers are properly configured for and make use of the following key anti-spoofing techniques available:

Sender Policy Framework (SPF) : lists the mail servers that can send email from your domain.

DomainKeys Identified Mail (DKIM): adds an encrypted signature to the header of all outgoing messages. Email servers that get signed messages use DKIM to decrypt the message header,  and verify the message was not changed after it was sent.

Domain-based Message Authentication, Reporting, and Conformance (DMARC) : ensures Incoming messages must be authenticated by SPF, DKIM, or both in addition to the authenticated domain aligning with the domain in the message From: header address.

Goals:
Ensure o1labs.org and codaprotocol.com DNS bindings are configured with the following:

[x] SPF TXT records
[x] DKIM TXT records
[ ] DMARC TXT records

Mail Provider:

G-Suite

DNS host providers:

o1labs.org: Namecheap
codaprotocol.com: Netlify

Hey @o1brad: appears as though I'll require admin privileges in order to generate the pub/priv key-pair for DKIM configuration+
Generate the domain key for outgoing email
You must be signed in as a super administrator for this task.

Your current account<EMAIL_ADDRESS>doesn't have permission to perform these steps. To continue, switch to a super administrator account. This will open the Google Admin console.

Switch to super administrator account or Learn more.
.
.
.

@o1brad @bkase @yourbuddyconner Seems as though both Domains were previously setup with SPF configs -- maybe some details about that setup would be appreciated...

@0x0I do you already have a DMARC policy in mind? who will be receiving the reports?

@emberian I would imagine we'd set up a<EMAIL_ADDRESS>address and receive them there if the generic contact@ email is insufficient.

Hey @emberian: I do for the most part though figured a discussion makes sense (in some channel) to source ideas and synchronize on a plan going forward.
Meant to link to support documentation which provides a recommended plan (e.g. including gradual deploys, limiting initial policy set, etc).

Updates:

SPF TXT record has been added for o1labs.org (via Namecheap)
DKIM TXT record added for o1labs.org domain (via Namecheap)
DKIM TXT record NOT added for codaprotocol.com domain (not believed to receive mail traffic)

Next Steps:

@o1brad + Ahmad to follow-up w/ enabling DKIM signing for o1labs.org GSuite mail traffic (via GSuite admin console)
validation steps [6-9] (from signing support doc) to be performed by @o1brad + Ahmad following signing with messaging to org re: success of activation
work with operations/infra to create a mailto email address to serve as a Reporting URI(s) for aggregate data (rua) -- necessary for DMARC setup.
Discuss and sync on DMARC policy with operations/infra - policy notes:

(v)DMARC protocol version is required (must == DMARC1)
(p)suspicious message policy handler is required (may make sense to start with none/log)
(sp) policy handler for subdomains (seems like it should currently match p)
(pct)percentage of suspicious messge above (p)olicy applies to (100% seems reasonable...)
(rua) violations reporting address (set to product of step #3)
remaining defaults appear reasonable

Example DMARC TXT Record for o1labs.org:
Name: dmarc.o1labs.org
Value:v=DMARC1; p=none<EMAIL_ADDRESS>pct=100; sp=none

DKIM TXT record for o1labs.orgs:
$ dig google._domainkey.o1labs.org TXT

; <<>> DiG 9.11.18-RedHat-9.11.18-1.fc32 <<>> google._domainkey.o1labs.org TXT
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4265
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;google._domainkey.o1labs.org.  IN      TXT

;; ANSWER SECTION:
google._domainkey.o1labs.org. 1799 IN   TXT     "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhjEaLC6UEoDoJEzNc5jCCco6rxzpOlx7M8ru1+KGvSvCT1GL+zCT1rcmSqJvyWlbNcMAG+J+IcTJCH+S05EiZIfdgt2fDFveoLJJYhTNuOhsL+x5sWcKI4VmcLkklGvaZzpCew1nuhJLwMOpzgdZTUeROViXNPiNRJagbsTyXCm+dv4+yGunBTiw4Lu9wmodJ" "1bzFhAeSYKjfN3XyRzYD9NjL1oPOgZPvWPMzoXoVnr5uJON0xyNHVrzT6xGX8yJ4oPYxpdaG2sjlera8rifQydikrMS5piZEN3DUDziRucSKOBscAjvYQ+uz6WiabLYoI062e7tkS0rhtYFncVa1QIDAQAB"

;; Query time: 81 msec
;; SERVER: <IP_ADDRESS>#53(<IP_ADDRESS>)
;; WHEN: Tue Jun 02 18:18:19 EDT 2020
;; MSG SIZE  rcvd: 481```

@o1brad @bkase  blocked due to upcoming changes?

DKIM and SPF are enabled. I don't think we need to prioritize enabling DMARC.


Add docker health checks

As part of our writing out tests, we should integrate health checks to our Dockerfiles
https://docs.docker.com/engine/reference/builder/#healthcheck
An example of a good health check for gps2tsdb would be a python script that gets the most recent gps point in the postgres db and ensures that it is no more than 5s old

Once #103 is merged, we will have gps, cell and can loggers with health checks. This leaves can_watchdog, oada_upload, and socketcand. Unsure if we can or want to do socketcand since it is developed by someone else.
@abalmos @facastiblancor what are your thoughts on how to check can_watchdog and oada_upload on a conceptual level?
can_watchdog does not modify anything so measuring it's effects would be hard
oada_upload would also be interesting. You could check to see if the sent column changed recently but then you would be settingoada_upload as unhealthy if it does not have internet and isn't uploading stuff even if it is otherwise working fine. Maybe combine that with an internet check? Issue then is that it could be broken but you would never know if you are not connected to the internet. Is oada_upload conceptually unhealthy if it does not have internet?

@aaron97neu I think socketcand does not need a health check. It will be eventually phased out by other messaging systems in the future. But if we wanted to do a health check, it would be to check the program is running and the desired CAN interfaces are exposed. In my opinion, it would be better to implement this check in the apps using socketcand. For can_watchdog I think we don't need to check its health status. If it fails, then it will keep restarting. That way we know something is wrong with it.


WIP(module:drawer): support service to create drawer

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #1937
What is the new behavior?
support service
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

Thanks, expectations

@HsuanXyz Conflicting files. i hope it can be used as fast. thanks very much


Plot Area White - Not Able to Update

When using the visual the Plot area is white and can not be changed. While you can update the background, it only applies to a small area that surrounds the actual graph.
In the sample available in the Sample_BarChart.pbix, it functions as expected, but when imported from the marketplace the issue with the plot area appears.

Fixed


Return type for MmGetMdlVirtualAddress

The function definition says return type is void (void MmGetMdlVirtualAddress) but the remark section says that the function returns starting virtual address of the MDL. Could you please clarify what does the function return?

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

ID: 08454e64-36f8-2a12-acfe-dbaa8279f7de
Version Independent ID: ba6bcd6b-fa1f-51af-2463-a9464edd2791
Content: MmGetMdlVirtualAddress - Windows drivers
Content Source: wdk-ddi-src/content/wdm/nf-wdm-mmgetmdlvirtualaddress.md
Product: windows-hardware
Technology: wdk-api-reference
GitHub Login: @barrygolden
Microsoft Alias: bagold

Hey Sai - thx for the feedback.  Looks like it's definitely not retval void.  See https://github.com/microsoft/Windows-driver-samples/search?q=MmGetMdlVirtualAddress.
From wdm.h:
//++
//
// PVOID
// MmGetMdlVirtualAddress (
//     _In_ PMDL Mdl
//     )
//
// Routine Description:
//
//     The MmGetMdlVirtualAddress returns the virtual address of the buffer
//     described by the Mdl.
//
// Arguments:
//
//     Mdl - Pointer to an MDL.
//
// Return Value:
//
//     Returns the virtual address of the buffer described by the Mdl
//
//--

#define MmGetMdlVirtualAddress(Mdl)                                     \
    ((PVOID) ((PCHAR) ((Mdl)->StartVa) + (Mdl)->ByteOffset))

Will work on updating the doc.

Update - doc page now has the correct syntax block -- https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/wdm/nf-wdm-mmgetmdlvirtualaddress
Thanks again for bringing this to our attention @prakhya!

@tedhudek Thanks for updating the doc.


Update surface to 0.5.0

Update surface to 0.5

@totaltrash it might take me a bit to review/merge this, primarily because I want to get this working with all the new form stuff in ash_admin once that is merged. I want to "maintain" the surface 0.4 branch for a while, because there may be users who can't upgrade at the moment.

Hey @totaltrash since I had to do a bunch of unrelated work, I introduced a lot of merge problems here. I'm just going to rerun the updater. Additionally, I'm making the next version of ash_admin work with the latest versions of phoenix live view and phoenix.

Sorry about that!


Change double and triple bonds in graphs to use ArcBetweenPoints

It is prettier (and easier to handle) this way.

Solved at https://github.com/UnMolDeQuimica/manim-Chemistry/pull/21


Convert all the MATLAB code for benchmarks to CamelCase rather than under_score.

Moreover, we should choose a consistent convention for function names to make things regular.
I propose:
runName

I actually simplified things to just 'runner' since the benchmark and implementation directory names give the context of what is actually run. So all runners implement a 'runner' or 'run' function which avoids the issue of CamelCase vs under_score convention.


Upgrade CodeQL v2.21.3 -> v2.21.4

This PR contains the following updates:

Package
Type
Update
Change

github/codeql-action
action
patch
v2.21.3 -> v2.21.4

Release Notes

github/codeql-action (github/codeql-action)
v2.21.4
Compare Source

[ ] If you want to rebase/retry this PR, check this box

Suggested commit message:
Upgrade CodeQL v2.21.3 -> v2.21.4

See:
- https://github.com/github/codeql-action/blob/main/CHANGELOG.md
- https://github.com/github/codeql-action/compare/v2.21.3...v2.21.4


Data structure for ctest is re-organized and cleaned up

Description

The data structure for ctest is re-organized.
All input data files are located in the centralized location.
The machine-dependent path is removed.

Anticipated changes to regression tests:

[ ] Is baseline change expected ?

Subcomponents involved:

[ ] apply_incr.fd (NOAA-PSL/land-apply_jedi_incr)
[ ] ufsLand.fd (NOAA-EPIC/ufs-land-driver-emc-dev)
[ ] ufs_model.fd (ufs-community/ufs-weather-model)
[ ] vector2tile_converter.fd (NOAA-PSL/land-vector2tile)
[x] none

Linked PR's and Issues:

Resolve Issue #114
Testing (for CM's):

RDHPCS

[x] Hera
[ ] Orion
[ ] Hercules
[ ] Derecho

CI

[x] Completed

PW-Clouds

[ ] AWS
[ ] AZURE
[ ] GCP

On Hera:
Test project /scratch2/NAGAPE/epic/Chan-hoo.Jeon/landda_test/land-DA_workflow/sorc/build
    Start 1: test_vector2tile
1/7 Test #1: test_vector2tile .................   Passed    1.62 sec
    Start 2: test_create_ens
2/7 Test #2: test_create_ens ..................   Passed    2.46 sec
    Start 3: test_letkfoi_snowda
3/7 Test #3: test_letkfoi_snowda ..............   Passed    4.94 sec
    Start 4: test_apply_jediincr
4/7 Test #4: test_apply_jediincr ..............   Passed    2.93 sec
    Start 5: test_tile2vector
5/7 Test #5: test_tile2vector .................   Passed    2.80 sec
    Start 6: test_land_driver
6/7 Test #6: test_land_driver .................   Passed    8.95 sec
    Start 7: test_ufs_datm_land
7/7 Test #7: test_ufs_datm_land ...............   Passed   69.66 sec

100% tests passed, 0 tests failed out of 7

Total Test time (real) =  93.76 sec


Update to latest atlas-web-core, fix artifactory

This PR adapts this repo to the changes I introduced in Atlas web core. Artifactory URL was pointing to older IP. There are more compilation errors that need to be fixed with the newer atlas-web-core.

Apologies, I have set up my commit signing. I'll abuse for this once if that is fine.


remove import to emptyFunction

fixes #43
:) thanks for the great component

Thanks, released as 2.5.1.


[BUG] Cannot Zoom in same Outline in two leaf

Describe the bug
When I wanted to zoom in or out the same outline in two different leaf, one of them cannot be edited.
To Reproduce
Steps to reproduce the behavior:

Created a new leaf of same document
Use hotkey to zoom in the same outline(and have zoomed in the same outline in another document.)
See error

Expected behavior
Can zoom in different item of the same outline in different leaf.
Screenshots
https://user-images.githubusercontent.com/13215013/112749875-c1707980-8ff7-11eb-90d1-62ee139733cc.mp4
Desktop (please complete the following information):

OS: macOS
Obsidian Version: 0.11.10

Additional context
NULL

@Quorafind Thank you for your contribution! Released in https://github.com/vslinko/obsidian-outliner/releases/tag/1.0.11


Publish Artifact task using share option does not work correctly on Windows or Linux

Agent version and platform
Version of your agent? 2.104.2
Windows 10
Linux CentOS 7.1

VSTS type and version
On-Prem TFS

15 RC1

What's not working?
Publish Artifact Task  now requires escaping the UNC path when it didn't used to.   Otherwise task fails to work on both Linux and Windows
On Linux, if you use escaped UNC path it does not copy the files and does not fail the task even though files weren't copied.  It does however associate the artifact even though nothing is there.

Build log on Windows where non-escaped UNC path causes failure
2016-08-15T16:57:52.3560684Z ##[section]Starting: Publish Artifact: drop
2016-08-15T16:57:52.7951030Z ##[debug]agent.workFolder=E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work
2016-08-15T16:57:52.7991008Z ##[debug]loading inputs and endpoints
2016-08-15T16:57:52.8001025Z ##[debug]loading ENDPOINT_AUTH_$/
2016-08-15T16:57:52.8021183Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_$/ACCESSTOKEN
2016-08-15T16:57:52.8021183Z ##[debug]loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
2016-08-15T16:57:52.8031066Z ##[debug]loading ENDPOINT_AUTH_SCHEME$/
2016-08-15T16:57:52.8031066Z ##[debug]loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
2016-08-15T16:57:52.8031066Z ##[debug]loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
2016-08-15T16:57:52.8051046Z ##[debug]loading INPUT_ARTIFACTNAME
2016-08-15T16:57:52.8051046Z ##[debug]loading INPUT_ARTIFACTTYPE
2016-08-15T16:57:52.8061013Z ##[debug]loading INPUT_PATHTOPUBLISH
2016-08-15T16:57:52.8061013Z ##[debug]loading INPUT_TARGETPATH
2016-08-15T16:57:52.8070977Z ##[debug]loaded 10
2016-08-15T16:57:52.8070977Z ##[debug]check path : E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\task.json
2016-08-15T16:57:52.8080970Z ##[debug]set resource file to: E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\task.json
2016-08-15T16:57:52.8080970Z ##[debug]system.culture=en-US
2016-08-15T16:57:52.8151032Z ##[debug]PathtoPublish=E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work\1\a
2016-08-15T16:57:52.8151032Z ##[debug]check path : E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work\1\a
2016-08-15T16:57:52.8160992Z ##[debug]ArtifactName=drop
2016-08-15T16:57:52.8171038Z ##[debug]ArtifactType=FilePath
2016-08-15T16:57:52.8171038Z ##[debug]TargetPath=\bowdmxtfs01\Builds\Windows DMX-UFS CI\Windows DMX-UFS CI_4.0.160815.4
2016-08-15T16:57:52.8291008Z ##[debug]creating path: \bowdmxtfs01\Builds\Windows DMX-UFS CI\Windows DMX-UFS CI_4.0.160815.4\drop
2016-08-15T16:57:57.2374429Z shell.js: internal error
2016-08-15T16:57:57.2384437Z RangeError: Maximum call stack size exceeded
2016-08-15T16:57:57.2384437Z     at String.slice (native)
2016-08-15T16:57:57.2384437Z     at Object.dirname (path.js:795:17)
2016-08-15T16:57:57.2384437Z     at mkdirSyncRecursive (E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:7:22)
2016-08-15T16:57:57.2384437Z     at mkdirSyncRecursive (E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
2016-08-15T16:57:57.2384437Z     at mkdirSyncRecursive (E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
2016-08-15T16:57:57.2384437Z     at mkdirSyncRecursive (E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
2016-08-15T16:57:57.2384437Z     at mkdirSyncRecursive (E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
2016-08-15T16:57:57.2384437Z     at mkdirSyncRecursive (E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
2016-08-15T16:57:57.2384437Z     at mkdirSyncRecursive (E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
2016-08-15T16:57:57.2384437Z     at mkdirSyncRecursive (E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
2016-08-15T16:57:57.5664681Z ##[error]Exit code 1 returned from process: file name 'E:\TfsBuildAgents\Agent2-BOWDMXTFS01\externals\node\bin\node.exe', arguments '"E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\publishbuildartifacts.js"'.
2016-08-15T16:57:57.5704716Z ##[debug]Microsoft.VisualStudio.Services.Agent.ProcessExitCodeException: Exit code 1 returned from process: file name 'E:\TfsBuildAgents\Agent2-BOWDMXTFS01\externals\node\bin\node.exe', arguments '"E:\TfsBuildAgents\Agent2-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\publishbuildartifacts.js"'.
at Microsoft.VisualStudio.Services.Agent.ProcessInvoker.d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.Agent.Worker.Handlers.NodeHandler.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.Agent.Worker.TaskRunner.d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Services.Agent.Worker.StepsRunner.d__0.MoveNext()
2016-08-15T16:57:57.5704716Z ##[section]Finishing: Publish Artifact: drop
Worker's diag log on Linux where files are not getting copied
[2016-08-15 17:55:07Z INFO StepsRunner] Processing step: DisplayName='Publish Artifact: drop', AlwaysRun=True, ContinueOnError=True, Critical=False, Enabled=True, Finally=False
[2016-08-15 17:55:07Z INFO StepsRunner] Starting the step.
[2016-08-15 17:55:07Z INFO TaskManager] Loading task definition '/home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/_work/_tasks/PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe/1.0.34/task.json'.
[2016-08-15 17:55:07Z INFO TaskRunner] The original input is a rooted path, return absolute path: /home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/_work/1/a
[2016-08-15 17:55:07Z INFO ExtensionManager] Getting extensions for interface: 'Microsoft.VisualStudio.Services.Agent.Worker.IJobExtension'
[2016-08-15 17:55:07Z INFO BuildJobExtension] Build JobExtension resolving path use source provide:
[2016-08-15 17:55:07Z INFO BuildJobExtension] The Default Path Root of Build JobExtension is build.sourcesDirectory: /home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/_work/1/s
[2016-08-15 17:55:07Z INFO BuildJobExtension] After prefix Default Path Root provide by JobExtension: /home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/_work/1/s
[2016-08-15 17:55:07Z INFO BuildJobExtension] Return absolute path after prefix DefaultPathRoot: /home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/_work/1/s
[2016-08-15 17:55:07Z INFO TaskRunner] build JobExtension resolved a rooted path:: /home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/_work/1/s
[2016-08-15 17:55:07Z INFO ProcessInvoker] Starting process:
[2016-08-15 17:55:07Z INFO ProcessInvoker]   File name: '/home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/externals/node/bin/node'
[2016-08-15 17:55:07Z INFO ProcessInvoker]   Arguments: '"/home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/_work/_tasks/PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe/1.0.34/publishbuildartifacts.js"'
[2016-08-15 17:55:07Z INFO ProcessInvoker]   Working directory: '/home/ufs/TfsBuildAgents/Agent1-DMX-UFS1/_work/1/s'
[2016-08-15 17:55:07Z INFO ProcessInvoker]   Require exit code zero: 'True'
[2016-08-15 17:55:07Z INFO ProcessInvoker]   Encoding web name:  ; code page: ''
[2016-08-15 17:55:07Z INFO ProcessInvoker] Process started with process id 29976, waiting for process exit.
[2016-08-15 17:55:07Z INFO JobServerQueue] Try to append 1 batches web console lines, success rate: 1/1.
[2016-08-15 17:55:07Z INFO JobServerQueue] Try to upload 1 log files or attachments, success rate: 1/1.
[2016-08-15 17:55:08Z INFO ProcessInvoker] Finished process with exit code 0, and elapsed time 00:00:01.4577354.
[2016-08-15 17:55:08Z INFO AsyncCommandContext] Start flush buffered output.
[2016-08-15 17:55:08Z INFO AsyncCommandContext] Finsh flush buffered output.
[2016-08-15 17:55:08Z INFO AsyncCommandContext] Wait till async command task to finish.
[2016-08-15 17:55:08Z INFO StepsRunner] Step result:
[2016-08-15 17:55:08Z INFO StepsRunner] Current state: job state = '', step failed = False, critical step failed = False

It turns out using \\server\folder is not a workaround.   If that syntax is used it create a folder on the build machine at \server\folder where server is not a network share but a non-shared folder on the build server with the same name as the networks server.  Below is the output if  \server\folder syntax is used instead.

Starting: Publish Artifact: drop

agent.workFolder=E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work
loading inputs and endpoints
loading ENDPOINT_AUTH_$/
loading ENDPOINT_AUTH_PARAMETER_$/ACCESSTOKEN
loading ENDPOINT_AUTH_PARAMETER_SYSTEMVSSCONNECTION_ACCESSTOKEN
loading ENDPOINT_AUTH_SCHEME$/
loading ENDPOINT_AUTH_SCHEME_SYSTEMVSSCONNECTION
loading ENDPOINT_AUTH_SYSTEMVSSCONNECTION
loading INPUT_ARTIFACTNAME
loading INPUT_ARTIFACTTYPE
loading INPUT_PATHTOPUBLISH
loading INPUT_TARGETPATH
loaded 10
check path : E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\task.json
set resource file to: E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\task.json
system.culture=en-US
PathtoPublish=E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work\2\a
check path : E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work\2\a
ArtifactName=drop
ArtifactType=FilePath
TargetPath=\bowdmxtfs01.micron.com\builds\Windows DMX-eMMC CI\Windows DMX-eMMC CI_4.1.160816.4
creating path: \bowdmxtfs01.micron.com\builds\Windows DMX-eMMC CI\Windows DMX-eMMC CI_4.1.160816.4\drop
shell.js: internal error
RangeError: Maximum call stack size exceeded
at String.slice (native)
at Object.dirname (path.js:795:17)
at mkdirSyncRecursive (E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:7:22)
at mkdirSyncRecursive (E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
at mkdirSyncRecursive (E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
at mkdirSyncRecursive (E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
at mkdirSyncRecursive (E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
at mkdirSyncRecursive (E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
at mkdirSyncRecursive (E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
at mkdirSyncRecursive (E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\node_modules\shelljs\src\mkdir.js:16:3)
Exit code 1 returned from process: file name 'E:\TfsBuildAgents\Agent1-BOWDMXTFS01\externals\node\bin\node.exe', arguments '"E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\publishbuildartifacts.js"'.
Microsoft.VisualStudio.Services.Agent.ProcessExitCodeException: Exit code 1 returned from process: file name 'E:\TfsBuildAgents\Agent1-BOWDMXTFS01\externals\node\bin\node.exe', arguments '"E:\TfsBuildAgents\Agent1-BOWDMXTFS01_work_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.0.34\publishbuildartifacts.js"'.

Copy Files task also has exact same defect.  It does not allow the use of a UNC path for the destination directory even though documentation for that field says that it does.

Thanks! I believe the problem is the share does not exist or the process does not have access to see it. I have an outstanding PR to improve the error messages returned from mkdirP.
I was not previously aware, but it appears that three or more leading slashes causes nodejs to treat the path as a local rooted path (from root of drive wherever cwd is). I just confirmed by playing around with fs.statSync from an interactive node session.

Regarding the issue you are seeing on Linux, it is probably creating a folder \\server\path locally somewhere under the agent directory or work directory. I know that if you don't use UNC format associating the artifact fails on Linux.
I have a PR where I'm trying to figure out the correct behavior on Linux - I think skip artifact creation is the correct thing and probably a warning in the build log. Artifact creation has special meaning (used for cleanup jobs, displayed in UI with copy-to-clipboard hyperlink). I'm not sure yet what the correct experience is for the Publish Artifacts task on OSX/Linux. My goal with the PR is a short-term fix.
I'm going to go ahead and close this issue. Feel free to reopen it if I'm wrong about the cause of the issue you are hitting on Windows. There is an issue in the tasks repo tracking this already. I don't believe it is an agent issue (please re-open if I'm wrong).
The task issue on Linux is tracked here. Again please re-open if I'm wrong and it is agent related.

Hi Eric,  The share does exist. It is physically on the same server as the build agent.   It  also worked with the old agent.
As seen in my issue,  copy files also doesn’t work and copy files doesn’t work with either a unc or an absolute path.
Brandon
From: ericsciple<EMAIL_ADDRESS>Sent: Wednesday, August 17, 2016 9:03 AM
To: Microsoft/vsts-agent<EMAIL_ADDRESS>Cc: Brandon Busacker (bbusacker<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/vsts-agent] Publish Artifact task using share option does not work correctly on Windows or Linux (#501)
Thanks! I believe the problem is the share does not exist or the process does not have access to see it. I have an outstanding PRhttps://github.com/Microsoft/vsts-task-lib/pull/115 to improve the error messages returned from mkdirP.
I was not previously aware, but it appears that three or more leading slashes causes nodejs to treat the path as a local rooted path (from root of drive wherever cwd is). I just confirmed by playing around with fs.statSync from an interactive node session.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vsts-agent/issues/501#issuecomment-240440536, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADwCYcMxWk9zHpe0BCJ1j3hvvZZbvoQRks5qgyKcgaJpZM4JkoBr.

Are you running the new agent as a different service account? Or with different elevated-ness? If you log in as the account, enter a node session in a console, and type require('fs').statSync('\\\\server\\share') you should be able to repro and troubleshoot.

Hi Eric,
I stand corrected.  Things are working fine now.   The issue was I was running the agent service and NETWORK SERVICE which is the default and NETWORK SERVICE didn’t have permission to my file system or share.  I’m now running it as my generic build account user and that has made all the difference.  Thanks for getting me set straight.
I’ll close this issue now.
I would like some clarification as to why you default the server user to network service.   I think that is a bad idea.   I think it is the origin of many bizarre unexpected issues.  I assume network service will have more permissions than it actually does.
Can you provide some guidance on when you would use network service?  Do you need to treat network or local service as just another user?  So do you need to add network service to your file system and share permissions?  I also couldn’t use my test adapters so those needed to be installed as network service as well.  Just some clarification would help.  Thanks.
Brandon
From: ericsciple<EMAIL_ADDRESS>Sent: Wednesday, August 17, 2016 9:58 AM
To: Microsoft/vsts-agent<EMAIL_ADDRESS>Cc: Brandon Busacker (bbusacker<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/vsts-agent] Publish Artifact task using share option does not work correctly on Windows or Linux (#501)
Are you running the new agent as a different service account? Or with different elevated-ness? If you log in as the account, enter a node session in a console, and type require('fs').statSync('\\server\share') you should be able to repro and troubleshoot.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vsts-agent/issues/501#issuecomment-240458689, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADwCYePY5RgEl2mQXIXj1-xalfLaiSylks5qgy-XgaJpZM4JkoBr.

The config prompts which service account to use, and as a convenience we provide a default value so you can hit enter to accept the default. I see a couple options here:

Don't default at all. That would force users to type NT AUTHORITY\NETWORK SERVICE if they indeed want to use network service - not a good experience.
Default to the current user. I don't think that is a good option as it leads the customer down an insecure path. Local admin is required to install a Windows service, so it would be better for customers to enter a different service account (and grant only required permissions) when running the Windows service.

Network service is just another user. It's identified in AD as <COMPUTER_NAME>$. E.g. if your computer name is JOHN_COMPUTER, then you would grant permissions within your network to JOHN_COMPUTER$.
Whether to use network service or a service account ultimately comes down the preference of the administrator and the scenario that you're trying to acheive. Network service is easier to setup and does not require managing credentials for the service account. Using a service account offers more granular permission management, and can simply disable a service account to disable permissions. I personally feel like service account is the cleaner approach, but both have advantages.

Thanks for the explanation.  It seems strange that if you are running your agent on JOECOMPUTER that the network service account permissions for that computer is not just automatically in place but it appears that is not the case.
From: ericsciple<EMAIL_ADDRESS>Sent: Wednesday, August 17, 2016 11:34 AM
To: Microsoft/vsts-agent<EMAIL_ADDRESS>Cc: Brandon Busacker (bbusacker<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Microsoft/vsts-agent] Publish Artifact task using share option does not work correctly on Windows or Linux (#501)
The config prompts which service account to use, and as a convenience we provide a default value so you can hit enter to accept the default. I see a couple options here:

Don't default at all. That would force users to type NT AUTHORITY\NETWORK SERVICE if they indeed want to use network service - not a good experience.
Default to the current user. I don't think that is a good option as it leads the customer down an insecure path. Local admin is required to install a Windows service, so it would be better for customers to enter a different service account (and grant only required permissions) when running the Windows service.

Network service is just another user. It's identified in AD as <COMPUTER_NAME>$. E.g. if your computer name is JOHN_COMPUTER, then you would grant permissions within your network to JOHN_COMPUTER$.
Whether to use network service or a service account ultimately comes down the preference of the administrator and the scenario that you're trying to acheive. Network service is easier to setup and does not require managing credentials for the service account. Using a service account offers more granular permission management, and can simply disable a service account to disable permissions. I personally feel like service account is the cleaner approach, but both have advantages.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vsts-agent/issues/501#issuecomment-240486701, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADwCYYZq-2jedAGzkxo8ZbmOq6IlQNTmks5qg0YGgaJpZM4JkoBr.


Insert in Sorted way in a Sorted DLL - POTD | 31-Oct-2024

Insert in Sorted way in a Sorted DLL
Link
Difficulty: Medium
Given a sorted doubly linked list and an element x, you need to insert the element x into the correct position in the sorted Doubly linked list(DLL).
Note: The DLL is sorted in ascending order
Example:
Input: LinkedList: 3->5->8->10->12 , x = 9

Output: 3->5->8->9->10->12

Explanation: Here node 9 is inserted in the Doubly Linked-List.
Input: LinkedList: 1->4->10->11 , x = 15

Output: 1->4->10->11->15

Constraints:

1 <= number of nodes <= 103
1 <= node -> data , x <= 104

Solved
def sortedInsert(self, head, x):
        new_node = Node(x)
        if head is None or head.data >= x:
            new_node.next = head
            if head:
                head.prev = new_node
            return new_node
        current = head
        while current.next and current.next.data < x:
            current = current.next

        new_node.next = current.next
        if current.next:
            current.next.prev = new_node
        new_node.prev = current
        current.next = new_node

        return head


Make destructor final to Mutex

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
✔

Fixed issues
-

👍


BUG: cirrus-ci nightly upload token is no longer valid - nightly builds are not being uploaded from cirrus

Describe your issue.
I was browsing the nightly wheels on https://anaconda.org/scipy-wheels-nightly/scipy/files and noticed that the macosx_arm64 and manylinux2014_aarch64 wheels were out of date - they should've been built last weekend.
When I look at the CI build log for the cron job the upload process failed.
The settings for the cron job can be found at https://cirrus-ci.com/settings/repository/4894635377033216. The build log for the last cron job can also be found there, https://cirrus-ci.com/build/5940032849575936. The tail end of the log is below.
The token is specified in ci\cirrus_wheels.yml using an encrypted variable, SCIPY_NIGHTLY_UPLOAD_TOKEN (originally created by @rgommers as SCIPY_NIGHTLY_UPLOAD_TOKEN_CIRRUS). I am not sure why the "Authorization token is no longer valid".
Assigning Ralf because he can create the tokens, and possibly try out a local upload. I wonder if the staging token is also broken.
Reproducing Code Example
N/A

Error message
Uploading file "scipy-wheels-nightly/scipy/1.10.0.dev0/scipy-1.10.0.dev0-cp310-cp310-macosx_12_0_arm64.whl"
[WARNING] Distribution "scipy-1.10.0.dev0-cp310-cp310-macosx_12_0_arm64.whl" already exists. Removing.
[ERROR] ('Authorization token is no longer valid', 401)

SciPy/NumPy/Python version information
N/A

The token is specified in ci\cirrus_wheels.yml using an encrypted variable, SCIPY_NIGHTLY_UPLOAD_TOKEN (originally created by @rgommers as SCIPY_NIGHTLY_UPLOAD_TOKEN_CIRRUS). I am not sure why the "Authorization token is no longer valid".

This is very strange, the tokens are still there and valid for a long time into the future.
Let me xref gh-17000, which is where I did the cleanup a month ago.

xref where we created the tokens (explains also how this actually works): https://github.com/scipy/scipy/pull/17029#issuecomment-1253139344

The Anaconda UI says that SCIPY_NIGHTLY_UPLOAD_TOKEN_CIRRUS was never used, so I revoked it. And I generated a new encrypted variable for SCIPY_NIGHTLY_UPLOAD_TOKEN:
ENCRYPTED[377be83afdaf9e8fa8bac105022bb1d362f72fff8501c2b5e827018b82270111828fb542fd7bd56bbfac9745603bd535]

And same for the staging token:
ENCRYPTED[5940af5e589adf1647fb2832be2c912812de22b5b6551d93e177600da69b2103ffdf0ee1cf16671cf5e76f69a966bc30]

Those encrypted values did change, and I am unclear on why. Maybe there was a change on the CirrusCI side in the encryption/decryption algo.
The token itself works fine, so I'll open a PR.


Is it possible to run prophetnet on 11G memory GPUs?

I tried to run prophetnet on 2080ti(11G memory) with Question Generation task. However, even if I set the max-sentences as 1, it still be out of memory. So I wonder whether it is possible to run this model on 11G memory GPU. Because it has similar structure and size to the other pretrained models like BERT and Unilm, which I can run them on 11G memory GPUs.

Hi，I tried ProphetNet in 1080Ti, with 11G memory. If I set the parameter --fp16, OOM occurs. However, if I remove --fp16, with batch_size 1, only 7.7GB memory is used. Please try removing --fp16 and tell us does it work.

It works. Thanks. That's really amazing.

Hi @Brandonnogithub,
I would like to run ProphetNet on Question Generation task. Could you please tell me how to proceed.

Hi @Brandonnogithub,
I would like to run ProphetNet on Question Generation task. Could you please tell me how to proceed.
Hi, you just need to follow the readme(https://github.com/microsoft/ProphetNet/tree/master/ProphetNet_Code) and change the datasest into SQuAD dataset

Hi @Brandonnogithub,
I would like to run ProphetNet on Question Generation task. Could you please tell me how to proceed.

Hi, you just need to follow the readme(https://github.com/microsoft/ProphetNet/tree/master/ProphetNet_Code) and change the datasest into SQuAD dataset
Thank you for your reply. Meantime, I found the answer to my question.
https://huggingface.co/microsoft/prophetnet-large-uncased-squad-qg


Convert file names from traditional to simplified(文件名繁体与简体转换)

Description of the new feature / enhancement
希望可以有一个可以繁体字与简体字相互转换
Scenario when this would be used?
有些时候我会在一些批量处理文件名，有些时候是不同名字的的繁体字，希望可以转换成简体字
Supporting information
No response

Thank you for your report. Your request is considered but currently is not planned.


Warnings when using generics with 3.0

Like I stated in https://github.com/greenrobot/EventBus/issues/249 I get warnings when I use generics with the indexer. This itself wouldn't be a problem, but Android Studio automatically switches to the code fragment where this happens, interrupting my current workflow which is somehow annoying.
The warning I get is like this (In the Gradle messages window):
Error:(196, 26) Note: Using upper bound type com.myapplication.event.IListEvent<T> for generic parameter

Would it be possible to degrade that warning so I get only notified about it, but without switching to the warning?

That would be great. It's not a big of an issue but still annoying.
I'm a friend of the verbose option.

I made a pull request to include the nolog option and only log generics when verbose is activated :)

@greenrobot Could the pull request made by @bishiboosh be merged ?
Thanks !

@jrdaher I just realized (ok, 5 years later) that there is a minor issue, I will fix it and push.

Done, and rebased on current master


Linux support please...

Good day...
Just hoping there will also be support for linux!
and thanks for this awesome package...
finally, meteor has something for the desktop in online mode..
tnx.

I don't need to support Linux at the moment, but I'd definitely take pull requests for this! A rough sketch of tasks:

[ ] support building for Linux — see if adding the appropriate platform/arch object to Meteor.settings.electron.build just works
[ ] support setting the app icon on Linux — will need to be handled differently than for Mac/Windows, see https://github.com/maxogden/electron-packager's README
[ ] support downloading the Linux app - probably just a matter of parsing the download URL here but I don't have a sense of what that looks like (is it an installer like on Windows, or a (zipped form of?) the app itself like on Mac?)
[ ] support remote updates

On the last note, I've heard that Electron's auto-updater framework doesn't actually support Linux—it's recommended that you update the app just via the system package manager. In that case, I don't know if there's anything for meteor-electron to do, I'd just want to document this in its README.


Fix unportable test(1) operator.

Only bash supports "==", the standard is "=".

Actually, "==" is also valid with the Bourne shell (which I use by default, bash is not installed on TrueOS/FreeBSD).
However, I will go ahead and commit this in case you have some old version of the Bourne shell which does not support that flag.  :-)


Update postal code regexes from rake task

A couple of postal code regexes got recently updated (fetched from rake postal_codes:update)
The diff for Israel shows that it's removed, but that's because it was duplicated (line 47-48 in the IL.yaml file)

Well spotted, thanks!


Show panels next to each other

Like in html-preview, open the preview directly in a new column next to the editor.

@salaboy Do we want to have this? I could imagine for bigger diagrams it would be hard to allocate enough space inside the editor.

Good question.. I think that is built in for the vs code editors...
It looks quite cool like that.. I imagine that this will be really cool for demos.. and if it is supported already I would leave it like it is in the GIF..

Something that I can see there is that you need to click into the diagram view to get updated.. I imagine that you can listen to the save events of the file and refresh, right?

I will create a PR for that feature 👍
Currently, it only updates on focus event of the preview panel. I'll create an issue for listening to the save event 👍


update .gitignore and slightly increase test coverage

I'm just delving into the project code here. I'm hoping to submit more stuff in the future. For now, I have a small PR doing two things:

Update .gitignore file with new comments and took out a duplicate reference to "env/" that was already there on line 11
made a small tweak to an existing test in order to get 100% code coverage for the middleware.py file. Basically, on line 148 of middleware.py there is a statement if key != 'Location': continue which never evaluates to True, because in the tests, the Location key is always first in the response headers list. I moved the code in the test around without otherwise changing functionality so that this conditional evaluates to True and therefore the next line of code gets hit during the test.

Awesome, thank you very much!
If you'd like to discuss more, feel free to join us on Slack as well!


Graphical Glitch After Many Calls to reset

Describe the bug
Reseting the state causes graphics to fail.
To Reproduce
Steps to reproduce the behavior:
very hard to reproduce in the current state. The original issue provides a script to reproduce the issue.
Expected behavior
The NES emulator should function the same after many calls to reset. The game should perfectly restore to its frozen point in time.

An initial reason for the current (esoteric) solution for backups between CPU and PPU namespaces was that circular dependencies between headers in C++ is problematic. However, this solution describes an effective technique to resolve circular dependencies that will work well for this use case.


Async connect gets fired before componentWillUnmount

Hello.
I have a pretty simple set up, a simple component, which dispatches a reset function in componentWillUnmount and a link, which routes on another page, where asyncConnect loads some data asynchronously. However, I have noticed, that an action in the next pages' asyncConnect gets dispached before the reset in the componentWillUnmount.
My question is - how can I dispatch some actions in the componentWillUnmount before asyncConnect's promise is fired?

use react-router on leave handler instead, that should be good enough for your case

@AVVS Will try it out! Thanks for the help


Partial Upstream Merge

Sorry, wrong project.

Coverage increased (+0.12%) to 88.93% when pulling 3791be9bcc7b5aeebd8ecd317c764ffaae7d3867 on Kixeye:test into 104a6b2039a033f7dfc4d3f513a24a0bd38d9a49 on graphite-project:master.


Add MaxCollisionLimitPerDigest

Description
Port of dapperlabs/atree-internal#4

[x] Targeted PR against main branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[x] Added appropriate labels

Codecov Report

Merging #271 (32d7f2a) into main (525fbc2) will increase coverage by 0.07%.
The diff coverage is 68.08%.

@@            Coverage Diff             @@
##             main     #271      +/-   ##
==========================================
+ Coverage   68.98%   69.05%   +0.07%
==========================================
  Files          14       14
  Lines        7257     7303      +46
==========================================
+ Hits         5006     5043      +37
- Misses       1619     1627       +8
- Partials      632      633       +1

Impacted Files
Coverage Δ

errors.go
19.70% <25.00%> (+0.32%)
:arrow_up:

map.go
71.67% <76.92%> (+0.26%)
:arrow_up:

Continue to review full report at Codecov.

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


cuBLAS tests failed after aligning with SYCL 2020 specification

Summary
After cuBLAS backend was aligned with SYCL 2020 specification, a large number of cuBLAS tests failed.
Environment

OS: Linux
Hardware: NVIDIA TITAN RTX
Backend library version: CUDA 10.2
Compiler version: sycl-nightly 20220210

Steps to reproduce
Clone the branch: https://github.com/dnhsieh-intel/oneMKL/tree/SYCL_2020_cuBLAS
$ mkdir build && cd build
$ cmake .. -DENABLE_CUBLAS_BACKEND=True -DENABLE_MKLCPU_BACKEND=False -DENABLE_MKLGPU_BACKEND=False -DREF_BLAS_ROOT=<reference_blas_install_prefix> -DTARGET_DOMAINS=blas
$ cmake --build .
$ ctest --output-on-failure

Observed behavior
Some cuBLAS tests using dynamic libraries reported segmentation faults in column major cases.
Output of cuBLAS unit tests: cublas_unit_tests.txt (81% tests passed, 321 tests failed out of 1668)
Examples of failed tests:
          Start    1: BLAS/RT/Nrm2TestSuite/Nrm2Tests.RealSinglePrecision/Column_Major_TITAN_RTX
   1/1668 Test    #1: BLAS/RT/Nrm2TestSuite/Nrm2Tests.RealSinglePrecision/Column_Major_TITAN_RTX ..................................***Exception: SegFault  1.42 sec

          Start  155: BLAS/RT/CopyUsmTestSuite/CopyUsmTests.RealSinglePrecision/Column_Major_TITAN_RTX
 155/1668 Test  #155: BLAS/RT/CopyUsmTestSuite/CopyUsmTests.RealSinglePrecision/Column_Major_TITAN_RTX ............................***Exception: SegFault  0.58 sec
Run this program with --terse_output to change the way it prints its output.
Note: Google Test filter = CopyUsmTestSuite/CopyUsmTests.RealSinglePrecision/Column_Major_TITAN_RTX
[==========] Running 1 test from 1 test suite.
[----------] Global test environment set-up.
[----------] 1 test from CopyUsmTestSuite/CopyUsmTests
[ RUN      ] CopyUsmTestSuite/CopyUsmTests.RealSinglePrecision/Column_Major_TITAN_RTX
relative error = 1.59858 absolute error = 0.543816 limit = 0.000161767
Difference in entry 0: DPC++ -0.203628 vs. Reference 0.340188
relative error = 2.13229 absolute error = 0.225206 limit = 0.000161767
Difference in entry 1: DPC++ -0.330823 vs. Reference -0.105617
relative error = 2.63611 absolute error = 0.746282 limit = 0.000161767
...

Expected behavior
cuBLAS tests passed.

@npmiller Would it be possible for you to take a look at this issue when you have a chance? Based on your experience of PR #136, Mesut (mmeterel) suggests that it would be more efficient to ask you for directions.

Hello @dnhsieh-intel, so I've had a look at this and I could reproduce the issues, I'm not getting segfaults but I am getting the incorrect results.
I don't think it's related to #136 but there does seem to be something strange here, maybe with the USM transfers or maybe a race condition in DPC++, I'm not too sure yet.
I did notice that the tests are waiting on the SYCL events, waiting on the SYCL queue instead seems to fix the issue, which also means that the _ct version of the tests works fine, but the _rt version is flaky indeed.
It seems to be very similar to what @densamoilov saw in oneDNN here:

https://github.com/oneapi-src/oneDNN/pull/1285#discussion_r816507853

But a clean build doesn't fix it in this scenario, so I suspect there might actually be an underlying issue.

Okay so I have figured out what is going on, with the way interop_task and host_task are currently defined they are required to be synchronous.
Meaning that starting asynchronous work in the lambda and not waiting for it is undefined behavior.
If you look at the proposal specification for interop_task, it says:

It is the user's responsibility to ensure that all operations performed inside the interop_task are finished before returning from it.

And this is also the case for the host_task, these two are meant to have the exact same semantics.
However these two are implemented a bit differently in DPC++, and it looks like currently interop_task actually ends up adding a wait on the CUDA stream. So this is what we're seeing there, under the hood waiting on the event of the interop_task will wait on the CUDA stream and the cublas operation will finish, however for the host_task it won't and that's why we're seeing incorrect results, because the cublas operation has not completed yet.
So it seems that this is an incorrect assumption on how interop_task are supposed to work in both oneMKL and DPC++, even though it is true that the current "incorrect" implementation is likely more efficient than the way it is supposed to work.
It looks to me like the way oneMKL is using these is more in line with hipSYCL's custom operations. But these are pretty different, the lambda of host_task and interop_task are essentially "host kernels", they execute at the exact same time a kernel would and once the lambda has finished executing all the work is meant to be over, so waiting on a host_task event signals when the lambda has finished executing, as opposed to custom operations where the lambda is executed when enqueuing the command and can only contain asynchronous work and waiting on a custom operation event signals when the asynchronous work has finished executing.

@npmiller Thank you so much for the investigation! @andrewtbarker Could you take a look please?

Meaning that starting asynchronous work in the lambda and not waiting for it is undefined behavior.
And this is also the case for the host_task, these two are meant to have the exact same semantics.

There is nothing preventing starting some work from such tasks in SYCL. It is just normal C++ and obviously it requires some planning about what is launched. For example starting a std::thread and never joining it later would be UB.

In my view there are two issues here: (1) functional failures (wrong answers) and (2) segfaults. For now I am only focused on (1).

@andrewtbarker do you still see segfault with your PR? I suspect it might fix both issues.
I've checked out your PR, and I do think that should fix the issue, I would be curious to know if there are performance implication for using host_task plus this patch as opposed to interop_task like before.

There is nothing preventing starting some work from such tasks in SYCL. It is just normal C++ and obviously it requires some planning about what is launched. For example starting a std::thread and never joining it later would be UB.

@keryell you're right it is absolutely possible. It's just a lot more tricky to handle than the interop_task because in the host_task case the SYCL runtime has no idea about the asynchronous work, so as far as the SYCL runtime is concerned once the lambda of the host_task has finished all tasks depending on it can start.

I have traced the segfaults to the destruction of the cublas handle on line 74 of cublas_scope_handle.cpp:
        CUBLAS_ERROR_FUNC(cublasDestroy, err1, handle);

It fails with the latest compiler I have access to. This doesn't get called twice (so if it's a double delete it happens somewhere else) and gdb does not think the pointer is null.

I see, that's interesting, it could have to do with the context stuff in https://github.com/oneapi-src/oneMKL/pull/136 still.
However I'm still unable to reproduce it locally with the latest DPC++ compiler so I'm not too sure what's going on, what version of the compiler are you using? There was also some issues regarding host tasks and context in the SYCL runtime, but that was quite a while ago.

Here's the version string for the particular clang++ that cmake is picking up. I've tried a couple other versions with the same result, this is the most recent:
clang version 15.0.0 (https://github.com/intel/llvm cae91b2b13af3915f4b6f990216146adde973903)

Can you share the script or command line you use to invoke cmake?

Sure, I'm doing the following:
export PATH=/path/to/llvm/build/bin:$PATH
export LD_LIBRARY_PATH=/path/to/llvm/build/lib
cmake -GNinja .. -DENABLE_CUBLAS_BACKEND=True -DENABLE_MKLCPU_BACKEND=False -DENABLE_MKLGPU_BACKEND=False -DREF_BLAS_ROOT=/usr -DTARGET_DOMAINS=blas
ninja
ctest

And everything passes:
100% tests passed, 0 tests failed out of 1668

I've rebuilt with the revision you provided (cae91b2b13af3915f4b6f990216146adde973903), and I'm still not getting any segfault, not sure if there's something wrong in my setup or if I'm just being lucky.
Are the segfault flaky? Do they happen every time? Even when running the tests individually?

The segfaults happen every time, even when running tests individually. I spent a little time trying to make a small reproducer but didn't make much progress. As far as I can tell, every cublas RT test fails - the ones reported passing in CI are actually just skipped, nothing runs.

@npmiller Which CUDA version are you using? 11.x? We have 10.2 installed. Do you think that would make a difference?

I've prepared a pull request into @dnhsieh-intel 's branch as a starting point for discussion.
In my view there are two issues here: (1) functional failures (wrong answers) and (2) segfaults. For now I am only focused on (1).
My solution in the linked PR is to try to recreate the previous behavior of interop_task within our cublas wrappers using host_task. Whether or not this is the correct or optimal behavior based on the spec, I think this should be similar to the what we have in this project before transitioning away from interop_task. @npmiller do you agree? Is there a better way to accomplish this?

@andrewtbarker Recently, @aelizaro merged this https://github.com/oneapi-src/oneMKL/pull/169 that brought oneMKL-cuBLAS backend performance on par with native cuBLAS. Can we check if this commit has any impact on performance? @aelizaro might have benchmarks we can re-use.

I ran a few basic performance tests, just using the reproducer from #106, and I can't distinguish between develop branch and my branch in performance:

m=n=k
my partial fix
develop

1024
138.639 gflops
138.637 gflops

4096
1600.91
1600.84

I ran a few basic performance tests, just using the reproducer from #106, and I can't distinguish between develop branch and my branch in performance:
m=n=k	my partial fix	develop
1024	138.639 gflops	138.637 gflops
4096	1600.91	1600.84

@andrewtbarker Thanks for confirming.

@npmiller Which CUDA version are you using? 11.x? We have 10.2 installed. Do you think that would make a difference?

I am running with 11.6, I've tried to switch to 10.2 but I'm still not seeing any segfaults there, so I'm not sure it's related.

I have a smaller reproducer, unfortunately it's not very informative to me. Here's the source:
#include <iostream>
#include "oneapi/mkl.hpp"

int main(int argc, char * argv[]) {
    std::cout << "Basic segfault reproducer, issue #175." << std::endl;
    auto dev = sycl::device(sycl::gpu_selector());

    sycl::queue queue(dev);
    sycl::context cxt = queue.get_context();
    const int N = 10;
    const int incx = 1;
    float * result_p = (float*) sycl::aligned_alloc_shared(64, sizeof(float), dev, cxt);
    auto ua = sycl::usm_allocator<float, sycl::usm::alloc::shared, 64>(cxt, dev);
    std::vector<float, decltype(ua)> x(ua);
    for (int i = 0; i < N; ++i) {
        x.push_back(i * 1.72);
    }

    std::cout << "  before actual call\n";
    auto done = oneapi::mkl::blas::column_major::nrm2(queue, N, x.data(), incx, result_p);
    std::cout << "  after actual call\n";

    sycl::free(result_p, cxt);
    std::cout << "done.\n";
    return 0;
}

One compilation and two separate link lines:
clang++ -g -Wno-deprecated-declarations -I${ONEMKL}/include -isystem ${LLVM_DIR}/compiler/include/sycl -isystem /usr/local/cuda/include -fPIC -fsycl -o app.o -c app.cpp

clang++ -g -fPIC -fsycl -L${ONEMKL}/lib -lonemkl app.o -o app1.exe
clang++ -g -fPIC -fsycl /usr/lib/x86_64-linux-gnu/libcublas.so -L${ONEMKL}/lib -lonemkl app.o -o app2.exe

For me, app1.exe crashes with a segfault at the very end of execution, while app2.exe runs to completion with no errors. This suggests that on our system here we are somehow picking up a wrong standard library and some symbol is resolving incorrectly. It probably has more to do with a local configuration than with the actual code or build system.

Is there any "stack" trace with gdb or whatever that works with cuBLAS?

Close this issue as it cannot be reproduced now. It appears to be related to machine environment and/or compiler packages.


Succubi are biased for Females

People were a bit unhappy that most Fertilin-Sources are centered around cum and cocks and thus heterosexual male succubi don't work. And people seem to dislike the incubi, what ingrateful bastards.
Some things discussed:

Rename "Drainer" to something more obvious, e.g. "demonic kiss".
Gain Fertilin on Partner-Orgasm
Maybe: Check nearby pawns, gain Fertilin for sexually satisfied pawns and loose for unhappy ones

I think with 1.3 there is a bit of re-balancing, let's see if people are happier.


WITH NAME should create a new instance regardless of arguments or library scope

I am using DatabaseLibrary to connect to a database for some tests. I want to instantiate another instance of DatabaseLibrary so that I can access two databases at the same time. In DatabaseLibrary, the ROBOT_LIBRARY_SCOPE is set to GLOBAL so that the library is not reimported on every test suite and can retain the connection state between tests. This is obviously required for a persistent connection.
I tried to use WITH NAME on my import statements to create two instances, like so:
Library  DatabaseLibrary  WITH NAME  db_driver_1
Library  DatabaseLibrary  WITH NAME  db_driver_2

However, this doesn't work - both db_driver_1 and db_driver_2 point to the same instance, and so I cannot connect to multiple databases even though the library is implemented as a class.
I've seen other tickets which suggest that providing different arguments to the Library import statement will indeed force it to create a new instance. However, in this case the library does not accept constructor arguments - the actual database parameters are specified later using a Connect To Database keyword.
It would be helpful if WITH NAME forced Robot to override whatever the library scope is and always create a new instance. IMHO if the user has specified WITH NAME then there is a strong implication that they want to create a new instance of a library (if it is a class), so that should be the default behaviour.

Any thoughts on this issue?

I've faced exactly the sam problem, would be nice to have some update on this issue :)

@pekkaklarck I've been looking into this issue and I'm interested in fixing it. I think that the culprit is here and here, which might be sorted out by deepcopy instead of copy, but this code was not touched for years. Could You help me out a bit?

What's the use case to import same library with same arguments twice?
Changing the logic is likely complicated and somewhat risky because the related code is so horrible and changes can affect so many users and use cases. There are also many other related issues such as #2106, #2377 and #2718, and all these needed to be thought together. Once we know how we want the whole import logic to work, the best way to get there is probably rewriting it pretty much fully. I have other higher priority issues in my todo list, but if someone else is interested to start looking at this for real I'm happy to help.

@pekkaklarck Thanks for the response. I think the use case I outlined above pretty much sums up the situation - if you have a library which is implemented as a Python class and you want 2 or more instances, but the constructor of the class does not take any arguments, then there doesn't seem any way to do it, because on the second "Import" statement, RF will return the previously cached copy of the library.
An example is DatabaseLibrary - a single instance can only connect to one database at a time. If I want to connect to two databases at the same time I can't currently do that by importing DatabaseLibrary twice and using "WITH NAME", because DatabaseLibrary's constructor does not accept arguments. Both of my aliases point to the same library instance.
I think the code changes required would be minimal: if the library is being imported with an alias (WITH NAME), then always create a new instance, instead of returning a cached copy. As far as I understand, this is what happens anyway if the constructor does accept arguments and you pass different arguments to the "Import" statement.

@pekkaklarck - let's take SeleniumLibrary as example.  It has plugin support that can modify what keywords are available. As I maintain a plugin for SL, I get bug reports because in scenario where users are trying out my stuff by adding plugin into one testdata file and their full suite has already imported SeleniumLibrary into global scope but that instance is not updated with the newly initialized on.


feat(ingest/bigquery): emit create operation event for view

Checklist

[x] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ ] Tests for the changes have been added/updated (if applicable)
[ ] Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
[ ] For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

This is inconsistent with the snowflake source and probably the redshift one as well. Do we want to update those too?

Good idea to fix those too, if they have this missing. The operation type (key in the dict) may be different for every source, though. Let me quickly check for snowflake. cc: @treff7es for tracking / following up on redshift.

From what I understand, the snowflake query type  in snowflake.account_usage.query_history is 'CREATE_VIEW' however the snowflake.account_usage.query_history does not log the view as part of OBJECTS_MODIFIED column which is typically used for snowflake operations, hence supporting this for snowflake is not a change on similar lines and needs more involving work (some simple query parsing). I'm tracking this internally and will create a separate PR for that.


  Does setenforce 0 fix it?
AVC messages?

selinux is already disabled on this host.

(like, not even permissive. Fully disabled)

how to reproduce step 2?  I've tried to build both Dockerfile's and it worked for me, but I think I've done something different with "step 2" as I've tried to build directly the cri-o Dockerfile from the host

hrm. The more full example, is that i'm testing https://github.com/knative/build-templates/pull/7
so, this build-image is running as a pod on a kubernetes v1.10.6 + cri-o v1.10.6 instance.
Let me try to reproduce with a more minimal set up.

i'm wondering if it is trying to mount proc on a tmpfs filesystem?

https://pastebin.com/ZPEHzAwc is the config.json that crio was running this pod with

the issue with running the container inside of the Docker/Podman container is that some /proc paths are masked.  This prevents the container spawned by Buildah to create new pid&user NS and mount /proc afterwards since that mount would be too "revealing", i.e. make visible paths that weren't visible before in the Docker/Podman context.
There are at least two ways to address it:

have no readonly/masked paths in the first container
don't create a PID namespace, so there is no need to mount a new procfs but re-use the already existing one

The second solution can be achieved setting the environment variable "BUILDAH_ISOLATION=chroot"

ah, i just found that I reverted changes to the Dockerfile for this buildah builder image.
The EPERM is buildah running as uid=0 inside the container and thinking it has privilege.
Last week I had
RUN adduser limited
USER limited
ENTRYPOINT ["buildah"]

Though now with adding that and building buildah from master, it failed with:
time="2018-08-10T20:22:49Z" level=error msg="error reading allowed ID mappings: error reading subuid mappings for user \"limited\" and subgid mappings for group \"limited\": No subuid ranges found for user \"limited\" in /etc/subuid"

So then I update Dockerfile to:
RUN adduser limited && \
  echo "limited:100000:65536" > /etc/subuid && \
  echo "limited:100000:65536" > /etc/subgid
USER limited
ENTRYPOINT ["buildah"]

And now it fails with:
Error: error running newgidmap: exec: "newgidmap": executable file not found in $PATH:
time="2018-08-10T20:35:00Z" level=error msg="error running newgidmap: : exec: \"newgidmap\": executable file not found in $PATH"
time="2018-08-10T20:35:00Z" level=error msg="(unable to determine exit status)"

not enough testing of buildah is done on centos ....
centos is now stuck due to less-than-latest shadow ...

even if switching this to "FROM fedora" works, it would just defer the headache of considering that many folks will expect this to work the same on RHEL and centos

switching to fedora yields a different error, and increased the image size by 500Mb. So I'm not going to add that as a stop-gap for now.

closing this, as I've fixed the EPERM (and on to new issues with buildah support on Centos ... https://github.com/projectatomic/buildah/issues/926)
Dockerfile that got past EPERM inside container was to actually create and use a limited user while inside the container:
FROM centos
ARG REVISION="master"

RUN \
  # Install buildah dependencies.
  yum -y install \
    make \
    golang \
    bats \
    btrfs-progs-devel \
    device-mapper-devel \
    glib2-devel \
    gpgme-devel \
    libassuan-devel \
    libseccomp-devel \
    ostree-devel \
    git \
    bzip2 \
    go-md2man \
    runc \
    skopeo-containers && \
  # Install buildah.
  mkdir ~/buildah && \
  cd ~/buildah && \
  export GOPATH=`pwd` && \
  git clone https://github.com/opencontainers/runc ./src/github.com/opencontainers/runc && \
  cd $GOPATH/src/github.com/opencontainers/runc && \
  make runc && \
  mv runc /usr/bin/runc && \
  cd $GOPATH/ && \
  git clone https://github.com/projectatomic/buildah ./src/github.com/projectatomic/buildah && \
  cd $GOPATH/src/github.com/projectatomic/buildah && \
  git checkout "${REVISION}" && \
  make && \
  make install && \
  buildah --help

RUN adduser limited
USER limited
ENTRYPOINT ["buildah"]


Helm3 does not do templating of CRDs

As noted by @bacongobbler here, CRDs are not templated in Helm3.  This is a breaking change from Helm2.  At Kubecon, I spoke to someone on the Helm team who acknowledged that this was intentional since often CRDs are implemented by an OPs team and not developers.  While I understand that rationale, it seems to me that CRD templating should be allowed in Helm3 as many charts rely on it.

This is also a valid scenario for us, we want to add some labels to CRDs by templating or conditionally install/skip some of the CRDs based on values provided.
I personally think, templating is the most powerful feature of helm and I don't think introducing limitations for this is a good idea since everyone has different use cases.

I would like to add that not allowing templatinf files inside crd folder makes it unusable for older version of Kubernetes. Since k8s 1.16 introduced structural schema, the CRD yaml file has fields like preservedUnknowfields etc that returns error in older version of k8s. Also, similar issue exists for K8s 1.11 (openshift 3.11) https://github.com/jetstack/cert-manager/issues/2200 .

Is there any work on this issue?
Would be great if CRDs were templated in Helm3.
In Velero chart I would like to include an option to disable hooks on crds folder, but I can't because it's not templated so the condition (if/else) is not rendered.

I am unsure that this feature will be implemented. The reason for not using templating with CRDs is described in the Helm CRD doc as follows:
"
Another important point to consider in the discussion around CRD support is how the rendering of templates is handled. One of the distinct disadvantages of the crd-install method used in Helm 2 was the inability to properly validate charts due to changing API availability (a CRD is actually adding another available API to your Kubernetes cluster). If a chart installed a CRD, helm no longer had a valid set of API versions to work against. This is also the reason behind removing templating support from CRDs. With the new crds method of CRD installation, we now ensure that helm has completely valid information about the current state of the cluster.
"

I don't get this:

This is also the reason behind removing templating support from CRDs. With the new crds method of CRD installation, we now ensure that helm has completely valid information about the current state of the cluster.

Why can't helm 3 do the templating initially when it deploys the files in the CRDs directory?  This is useful for metadata labels, for example.

@technosophos might be able to shed more insight on this.

I would also like to have templating support with the CRD folder.
I want to deploy the CRD and CR within the same chart and I have go templates within the CRD to ensure consistent naming. Currently this is not possible:

Let helm do it. Templating does work within the CRD folder.
Put the CRD in a subchart. Helm gives an error that the CRD is not installed when it attempts to load the CR, even if post-install hook is set on the CR.


Test multiple

Codecov Report

Merging #90 (a915442) into dev (1fa7dcc) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head a915442 differs from pull request most recent head a560b26. Consider uploading reports for the commit a560b26 to get more accurate results

@@           Coverage Diff           @@
##              dev      #90   +/-   ##
=======================================
  Coverage   50.09%   50.09%
=======================================
  Files          15       15
  Lines         523      523
  Branches      121      121
=======================================
  Hits          262      262
  Misses        261      261

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


Incompatibility with Mining Drones Mod by Klonan

Mod source
Factorio Mod Portal
Which mod are you having an issue with?

[ ] pyalienlife
[ ] pyalternativeenergy
[ ] pycoalprocessing
[ ] pyfusionenergy
[ ] pyhightech
[ ] pyindustry
[ ] pypetroleumhandling
[x] pypostprocessing
[ ] pyrawores

Operating system

=Windows 10

What kind of issue is this?

[x] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[x] Pypostprocessing failure
[ ] Other

What is the problem?
Since the update of the Pynadon Mods to 2.x versions, the postprocessing mod in the modpack throws an error when the "Mining Drones" v1.1.10 by Klonan is active.
The specific error is:
Failed to load mods: pypostprocessing/prototypes/functions/auto_tech.lua:150:
ERROR: Dependency loop detected
stack traceback:
[C]: in function 'error'
pypostprocessing/prototypes/functions/auto_tech.lua:150: in function 'run'
pypostprocessing/data-final-fixes.lua:144: in main chunck
Steps to reproduce
Activate full suit of current version Pymods
Activate "Mining Drones"  v1.1.10
(Re)start the game
Witness mod loading failure
Additional context

Log file
factorio-current.log

Fixed for v0.2.1


chore(graphiql): minor refactoring based on object destructuring

Trying to make code look cleaner and elegant.
Would love to make more enhancements :+1:

we are in the midst of rewriting this component! thanks though!


OpenGov. Vote. Vote confirmation screen

OpenGov. Vote. Vote confirmation screen
Wallets:

[x]  Single Polkadot Vault wallet
[ ]  Proxied wallet
[x]  WalletConnect, Nova Wallet wallet
[x]  Multishard wallet, Polkadot Vault wallet
[x]  Multisig wallet
[ ] Correct governance lock

Figma mockups

Status verification: ✅


Add a runtime-internal function, _enumerateTypes(fromImageAt:conformingTo:_:), that will walk the protocol conformance tables looking for types that conform to a given protocol.

Add a runtime-internal function, _enumerateTypes(fromImageAt:conformingTo:_:), that will walk the protocol conformance tables looking for types that conform to a given protocol.

Resolves rdar://67501458.

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 14e679336c9ee44cc253a991d2d09637d890a5bf

@swift-ci please test

@swift-ci please test

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 0edccaaf10173ce80fb0c01051918cccd2afa246

Build failed
Swift Test OS X Platform
Git Sha - 0edccaaf10173ce80fb0c01051918cccd2afa246

Build failure appears unrelated to my changes, caused by https://github.com/apple/swift-package-manager/pull/3929. @tomerd

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 65a039c5a0b9d57977d54fb12db60181f56f4158

Build failed
Swift Test Linux Platform
Git Sha - 65a039c5a0b9d57977d54fb12db60181f56f4158

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 9b503423e1fbf9699ec4bd6bced1a0ac9f9db8f8

Build failed
Swift Test OS X Platform
Git Sha - 9b503423e1fbf9699ec4bd6bced1a0ac9f9db8f8

Can we reuse the existing logic in the runtime, used by the conformance cache, that crawls the metadata in an image looking for matching conformances?

@swift-ci please test

Can we reuse the existing logic in the runtime, used by the conformance cache, that crawls the metadata in an image looking for matching conformances?

That's effectively what this new function does (as much as is possible.)

Build failed
Swift Test OS X Platform
Git Sha - 7aa9f5b317b536d7677ba2a19bc318c7901d3a85

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 7aa9f5b317b536d7677ba2a19bc318c7901d3a85

Build failed
Swift Test Linux Platform
Git Sha - 7aa9f5b317b536d7677ba2a19bc318c7901d3a85

@swift-ci please test

I stripped out special handling for dlopen() handles under Mach because… woof. Instead, just pass #dsohandle or something #dsohandle-compatible. On Apple, that's a Mach header; on most Unixes it's __dso_handle, and on Windows it's __ImageBase. We'd probably want to document that somewhere.

Build failed
Swift Test Linux Platform
Git Sha - cb22ec539b8b09c9dd90b0a442707dc9f7562cdd

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 87232e5dc11cbf87e8533fb279821425e9cf6e8b

Build failed
Swift Test OS X Platform
Git Sha - cb22ec539b8b09c9dd90b0a442707dc9f7562cdd

Build failed
Swift Test OS X Platform
Git Sha - 87232e5dc11cbf87e8533fb279821425e9cf6e8b


Matroska: show smallest supported version only if corresponding option is set

Contains an update of https://github.com/MediaArea/MediaInfoLib/pull/968

Does that mean that you won't see the 'Version 4/ Version 2' type of thing
by default?

Will be "Version 4" instead.


Space Travellers hub

Missions
Hi @KanzaTahreem ,
Here I have been able to achieve the following;

Fetch Data missions data from the endpoint #17
Display missions #14
Set up redux actions (Leaving and joining) #9
Render components conditionally for missions #5
Display joined missions in my profile #2

Please kindly review 😄

Hi @KanzaTahreem ,
Thank you for your review.
Please note that I have fixed all the errors you mentioned and I have also style the mission table on the profile page.
Please kindly review again.

Merge all branches into dev


ABCore randomly restarting

This is a problem I've been having for several releases, including the latest (0.48).
After stopping Core (by pressing the slider/button "Switch Core OFF"), and verifying that it indeed has stopped (debug.log shows "Shutdown: done"), the tray icon disappears. I leave the ABCore app, and remove it from the view of recently used apps (pressing the square button, and swiping the ABCore window off the screen).
Some time later (I think usually when leaving another, unrelated app), the ABCore tray icon automatically reappears, and it seems that it indeed is running again (by inspecting the debug.log). This makes it nearly unusable, as the memory/CPU/bandwidth usage is something I don't want to see appear unexpectedly.
The problem does not seem to occur if after stopping Core, and leaving ABCore, I go to the apps settings screen, and Force Kill the application.
I don't have the feature for automatically running when on power+wifi enabled.

fixed in 2cf694833ce1767659d95afbcd30cdda977eb37f
Sorry; it hit me and a friend as well (we run out of monthly mobile allowance), shouldn't happen anymore.
Mind you that the "power+wifi enabled." won't disable core if it was manually started when it was last started.
Will release after 0.13 final is out as 0.49

@sipa v0.49 is now available @ https://github.com/greenaddress/abcore/releases
Leaving this open in case there are more issues.

I haven't had the issue after upgrading. Thanks!


Remove mimic rule pending rework

About the PR

comment out MimicVendorRule from events entity table
Why / Balance

right now mimic has very low impact on the round and here is a small more detailed list

just replaces a vendor and gives nothing instead (might be annoying with some rare vendors)
has sprite of default robust softdrinks
has no loot
does nothing

with all this i think it's better to remove the rule until someone will rework it
Technical details

Media

Requirements

[X] I have read and I am following the Pull Request Guidelines. I understand that not doing so may get my pr closed at maintainer’s discretion
[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

remove: Mimic vendor event was removed pending rework.

but it's rare funny useless thing..... isn't there some beauty in that????

why can't you just do the rework and then merge that rather than remove it completely "pending" nothing

wyci
i don't know how to code

instead of removing em how about restricting it to targeting drinks/food/games/clothes vendors (aka non essential/rare) until more functionality is added?

but it's rare funny useless thing..... isn't there some beauty in that????

"Rare" is a stretch. Seems like every other soda machine starts scooting around doing absolutely nothing.

I brought this up for maintainer discussion and the agreement was that while this event has almost no impact on the round, we can keep it for now as a fun little easter egg. I will open an issue for it to be improved.


fix test_union_different_column_order

test failed for Clickhouse randomly here: https://github.com/iterative/datachain/actions/runs/10463877840/job/28976586712

LGTM, thanks for fixing this!

I broke it


feat: frontend prometheus reporting to sysdig

https://github.com/siimon/prom-client
https://developer.gov.bc.ca/docs/default/component/platform-developer-docs/docs/app-monitoring/sysdig-monitor-setup-team/
https://developer.gov.bc.ca/docs/default/component/platform-developer-docs/docs/app-monitoring/sysdig-monitor-set-up-advanced-functions/

Removed myself from this ticket.  Apparently it's up to the team.  ...but I'm still interested and happy to sidekick!  @SLDonnelly


[OFF-TOPIC] where is your ach linux theme that was hosted on rxyhn/dotfiles

I would like to know where is your arch linux theme awesomewm that you used to host on /rxyhn/dotfiles
Thanks

I think it was moved to Yoru.


Ubuntu 20.04 Support

Hi, I couldn't really find anything mentioning this. Is there support for versions of Ubuntu other than 14.04 and 16.04? I'm currently running 20.04, but I couldn't find any mention of 18.04 either.

Actually, Ubuntu 18.04 is supported but we are running into problems updating to it at AWS EC2: https://github.com/flynn/flynn/issues/4535
I will try that again soonish with a newer Flynn version. But if this doesn't work, I don't know what to do as the support of 16.04 will be EOL in April 2021.

Any news regarding this issue? I am planning on using Flynn in a new server with 20.04, then I saw this.

Any news regarding this issue? I am planning on using Flynn in a new server with 20.04, then I saw this.

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


Node-Forge package version outdated

Node-Forge package version is outdated(version 0.9.1) and its show as vulnerable, please update the Node-Forge dependency package to latest version (0.10.0), current wallet pass installation shows a high severity vulnerability warning message. Thank you

Looks like this has been updated in main, just needs a release to npm.

Thank you @saltire hope it will be released on npm soon.

Still an issue as of 2021-01-06

Still an issue as of 2021-01-06

please please new release

@saltire can somebody please create a new release to NPM to address this?

Still waiting for the new release with node-forge upgrade!!!  :(

So this library is dead. Any alternatives?


Enhancing the FTP protocol

What was done

Modified nxc/protocols/ftp.py

Modified the --ls flag to allow for listing the current directory and sub-directories. Default now lists .. If an argument is provided, it will list the provided sub-directory
Added the --get flag to download a file on the server. If the file exists and is successfully downloaded, it will be written to the users cwd with the remote file's filename.
Added the --put flag to upload files onto the server.

Modified nxc/protocols/ftp/proto_args.py to reflect the added features

Modified the --ls flag to allow for a default directory listing (.) or use a provided directory
Added the --get and --put flags

Modified nxc/protocols/ftp.py#L83 to comply with RFC 1635

Test environment used

During testing, different permissions were used to account for edge cases.

from pyftpdlib.authorizers import DummyAuthorizer
from pyftpdlib.handlers import FTPHandler
from pyftpdlib.servers import FTPServer

def start_ftp_server():
    # Instantiate an authorizer object responsible for managing authentication and authorization
    authorizer = DummyAuthorizer()

    # Allow anonymous access with read-only permissions
    authorizer.add_anonymous("./FTP_Folder/", perm="erlw")

    # Instantiate an FTP handler object and link it to the authorizer
    handler = FTPHandler
    handler.authorizer = authorizer

    # Create the FTP server on the desired address and port, and link it to the handler
    server = FTPServer(("<IP_ADDRESS>", 21), handler)

    # Start the FTP server
    server.serve_forever()

if __name__ == "__main__":
    start_ftp_server()

RFC 1635 Compliance

--ls
Standard usage

If permissions are not granted

--get
Standard usage

If the file does not exist

--put
Standard usage

If a local file does not exist

Permissions error

Couple things to mind about this merge, it currently doesn't allow the following:
--put

If a user attempts to upload a file like --put example.txt ., it will fail with Failed to upload file. Response: (550 Is a directory.)

The user will need to specify the filename or dir + filename to save to
--put example.txt example.txt or --put example.txt Sub/Dir/example.txt
If this current implementation is not prefered, let me know and I can make some adjustments to allow users to upload using either . or Sub/ and upload to the directory using the local_name

@RomanRII can you add these new flags to the e2e tests commands file under the FTP section (tests/e2e_commands.txt)?

@Marshall-Hallenbeck you got it. will get that done

Added new flags to (tests/e2e_commands.txt)
Added test file to test upload/download functions (tests/data/test_file.txt)


Issue with k8s.io/ko/docs/concepts/services-networking/endpoint-slices/

This is a Bug Report
Problem:
Translated sentence is awkward, etc., should be corrected.
Proposed Solution:
It should be modified and translated to an appropriate level.
Page to Update:
https://kubernetes.io/ko/docs/concepts/services-networking/endpoint-slices/

/language ko
/assign


Support to Image Quick View

EBSCO Discovery Service API 18.1: Release Notes February 2018
EDS API supports Image Quick View (IQV). Some records contain associated images. If a record contains associate images, the IQV feature provides links to the thumbnails of those images along with the search results. The query parameter includeimagequickview specifies whether or not the IQV data is included in the search response. To include available IQV images, append the includeimagequickview parameter set to y to the search request.

Image Quick View Available