Encode conditional rewrites within the egglog egraph

We need a way to represent conditional equality within Egglog. Non-conditional equality is easy; this is just represented with e-classes.
Getting the actual conditional rewrite rule is relatively straightforward:

Come up with way of encoding a predicate as a function.

Have a rule which rewrites lhs ~> rhs if the predicate holds for some term.

However, we need a way to encode the conditional rewrite inside Chompy, so that when we begin enumerating programs of a greater depth, we don't re-generate conditional rules linking two eclasses together.

Closed by #8.


Issue#566

In this PR,
I have made changes in the speed.rs module . Explaining how the entire module works
I have also added a note on the set speed function - Specifying there would be an increase of pitch
I have also removed the note comment from @dvdsk on the try_seek method : As the reason for the commit is now fixed

super! two small things, you need to run cargo fmt to fix the formatting and I would suggest moving some of the documentation to source/mod.rs specifically add it to fn speed. Since that is what most ppl will see.

@dvdsk , Ohh I forgot to run cargo fmt and yes your right . I should probably move the docs to the mod file, so it's more accessible.
Expect the commit, any hour 24hrs from now . I was just so busy enjoying the weekend . 😅.

Alright , I think this is good @dvdsk , please review and merge.

I found a great resource on documenting items, I have added it to the CONTRIBUTING.md guidlines: https://github.com/RustAudio/rodio/blob/master/CONTRIBUTING.md#documentation

@dvdsk nice vets , I would take an extra look on the contribution guidelines you cited and by tomorrow , I should have this in optimum status .
Btw I wanted to propose a new feature on the output stream structure , could I create a new issue for that .

Btw I wanted to propose a new feature on the output stream structure , could I create a new issue for that .

yes please do

@dvdsk Thanks for the resources you added to the contribution guidelines ; they were very useful . I think we are good now , please review and merge if its ok.

thank you very much!


update Blacklists used in the pipelines

The blacklists used by the pipeline seem to be an old version, with fewer entries than the ones we can find in the newly updated versions here:  https://sites.google.com/site/anshulkundaje/projects/blacklists
For instance, the GRcm38 provided with the 1.2.2 chipseq version appears to have 164 entries, while the mm10 one in the followig link https://github.com/Boyle-Lab/Blacklist/tree/master/lists (version 2) has 3435 entries.
For human there's even a newer update version3, it would be great if the most up to date versions would be provided with the pipelines
Would it be possible to update them please?  @Jose Espinosa-Carrasco

Thanks for reporting @sopenaml ! We are working on the transition to DSL2 and we should also include the updated blacklists. Anyway, if you want to provide the updated blacklist bed with the current stable version of the pipeline, you could use the blacklist parameter, e.g. --blacklist /path/to/your/updated/file/mm10-blacklist.bed.

Closed https://github.com/nf-core/chipseq/pull/257


Revised breaking changes for structs in .NET Core 2.1

Also, added the link to breaking changes to the page about What's new in .NET Core 2.1.

@tdykstra @Thraka could anyone of you merge this PR, please.


An article about How to sort items by a custom date in an Umbraco v13…

An article about how to sort items by a custom date in an Umbraco v13+ Examine Index with code examples.

Thanks @NurhakKaya for this article 👍


Resource path as URL

How about ability to use URL as resource path?
For example, variables file dynamic and store on s3 and needs to use it for build

@bogish can you provide a more detailed example?


remove artifact preview

closes: https://issues.redhat.com/browse/RHOAIENG-8765
Description

removes the component and all uses of ArtifactPreview
How Has This Been Tested?

Make sure artifact previews are not shown when the s3 feature flag is flipped on. You can check by going to a run with artifacts and going to its node details. its preview will be shown there
Test Impact

no tests for removal
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Commits have been squashed into descriptive, self-contained units of work (e.g. 'WIP' and 'Implements feedback' style messages have been removed)
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change (find relevant UX in the SMEs section).

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

/approved

/approve


Pattern not working

After recent "required" flag commit, my pattern checking is NOT working anymore. Why remove the validate function?

The validation should be performed by browser directly.
Maybe your pattern content is not HTML5-compatible? What did you write
inside it?
Il 22/11/2019 10:42, gavinsin0001 ha scritto:

After recent "required" flag commit, my pattern checking is NOT
working anymore. Why remove the validate function?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/KasperOlesen/DataTable-AltEditor/issues/72?email_source=notifications&email_token=ACLII2AQOHUH7Q7RAIBUTEDQU6SRJA5CNFSM4JQOGNFKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3KYXBQ,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLII2EXJSVVAAKK765DSRLQU6SRJANCNFSM4JQOGNFA.

My previous patterns are for ID number (pattern:"^\S+\(\S\)$"), phone number (pattern:"^\d{8,13}$") and email (pattern: "^\S+\@\S+$").
Are they not HTML5-compatible?
And so we cannot have custom error message then.

I think you should remove the trailing "?" and "$". Can you try?
Moreover, yes, you can have custom error messages, see e.g.
https://developer.mozilla.org/en-US/docs/Learn/HTML/Forms/Form_validation
I understand this breaks old AltEditor's, however this approach is more
standard nowadays. Maybe can you guess some form of
backward-compatibility ?
Il 22/11/2019 11:35, gavinsin0001 ha scritto:

My previous patterns are for ID number (pattern:"^\S+(\S)$"), phone
number (pattern:"^\d{8,13}$") and email (pattern: "^\S+@\S+$").
Are they not HTML5-compatible?
And so we cannot have custom error message then.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/KasperOlesen/DataTable-AltEditor/issues/72?email_source=notifications&email_token=ACLII2FMRQT2KORMTEWARVDQU6YXLA5CNFSM4JQOGNFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEE5H3WA#issuecomment-557481432,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLII2GYI4CJ44MHWQQKYZDQU6YXLANCNFSM4JQOGNFA.

Seems removing the trailing "$" works. Thanks.


Next.js 14 cannot load any .riv file

NextJS: 14.1.4
@rive-app/react-canvas": "^4.9.0"
I already used Rive in other React apps with Vite and everything was working as intended. However, I cannot for the life of me makes things work with Next.js in that regard. Some Next.js devs seems to don't have any problem importing .riv files from public folder and I just don't understand what is different on my side.
I tried many solutions and none seems to work. I always get the dreaded "Bad header" and "Problem loading file; may be corrupt!".
The only way a Rive component seems to load is if I load it from an external source. The webpack or turbo bundler doesn't seems to find any .riv files in my public directory.
Here's what my code currently looks like :
"use client";

import { useRive } from "@rive-app/react-canvas";

export default function RiveCubeSautant() {
  const STATE_MACHINE_NAME = "State Machine 1";
  const INPUT_NAME = "Pressed";

  const { RiveComponent, rive } = useRive({
    src: "/rive/cube.riv",
    stateMachines: STATE_MACHINE_NAME,
    artboard: "Cube",
    autoplay: true,
    onLoadError: () => console.log("ERROR LOADING CUBE"),
  });

  return (
    <div style={{ height: "500px", width: "500px" }}>
      <RiveComponent />
    </div>
  );
}

I tried "rive/cube.riv" as an alternative or again importing it as module with the url-loader and the webpack rules. Nothing works. Is there any Next.js dev that have a workaround? I am at wits end here... Many thanks!

Same problem. Only solution for now is to use:
"@rive-app/react-canvas": "^4.6.2",
"@rive-app/canvas": "^2.9.2",
those for me in the meantime

works for me. Also highly doubt this has anything to do with next.js. Its just serving static files after all.

I don't know but with last versions of rive in next js, if I use
    "next": "^14.2.3",
    "@rive-app/canvas": "^2.15.6",
    "@rive-app/react-canvas": "^4.9.5",

The animations don't load and I get this error in the console:
app-index.js:33 TypeError: a.startsWith is not a function
    at Sa (rive.js:685:12)
    at Ya (rive.js:728:73)
    at eval (rive.js:3273:3)
    at Module.eval (rive.js:3277:3)
    at RuntimeLoader.loadRuntime (rive.js:3825:67) [...]

works fine with those versions in my case:
"next": "^14.2.3",
"@rive-app/react-canvas": "^4.6.2",
"@rive-app/canvas": "^2.9.2",

I'm moving from Vite to Next, and the latest is working in our Vite project, but not with the latest of next.js 15 (we are going to try 14 too)
receiving this error:
Console Error
Problem loading file; may be corrupt!
Call Stack
Next.js
createUnhandledError
./node_modules/next/dist/client/components/react-dev-overlay/internal/helpers/console-error.js
handleClientError
./node_modules/next/dist/client/components/react-dev-overlay/internal/helpers/use-error-handler.js
console.error
./node_modules/next/dist/client/components/globals/intercept-console-error.js
eval
<EMAIL_ADDRESS>(5259:1)
I also tried the older versions suggested above, but have not had luck, not sure if this is the best place though since this is 15 and not 14, and 15 is new.

To follow-up on this, we figured out it was a CORS issue, it is working on next 15 for us, apologies for the false flag.


Support clojure.core/tap>

Describe the bug
It would be nice if values captures using clojure.core/tap> would be shown somewhere in the IDE (ideally next to the code that emitted it), both when evaluating something on the REPL and also when running tests.

Right now I cannot even evaluate (tap> {:test 1}):
;; Connected to nREPL server - nrepl://localhost:7888
;; Clojure REPL Intellij 1.3.1
;; Clojure 1.11.3, Java 11.0.22, nREPL 1.1.1

user> {:test 1})

             java.lang.RuntimeException: Unmatched delimiter: )
clojure.lang.LispReader$ReaderException: java.lang.RuntimeException: Unmatched delimiter: )
             clojure.lang.ExceptionInfo:

user>

             java.lang.RuntimeException: Unmatched delimiter: )
clojure.lang.LispReader$ReaderException: java.lang.RuntimeException: Unmatched delimiter: )
             clojure.lang.ExceptionInfo:

;; => {:test 1}
user> {:test 1})

             java.lang.RuntimeException: Unmatched delimiter: )
clojure.lang.LispReader$ReaderException: java.lang.RuntimeException: Unmatched delimiter: )
             clojure.lang.ExceptionInfo:

user>

             java.lang.RuntimeException: Unmatched delimiter: )
clojure.lang.LispReader$ReaderException: java.lang.RuntimeException: Unmatched delimiter: )
             clojure.lang.ExceptionInfo:

;; => {:test 1}
user> {:test 1})

             java.lang.RuntimeException: Unmatched delimiter: )
clojure.lang.LispReader$ReaderException: java.lang.RuntimeException: Unmatched delimiter: )
             clojure.lang.ExceptionInfo:

user>

             java.lang.RuntimeException: Unmatched delimiter: )
clojure.lang.LispReader$ReaderException: java.lang.RuntimeException: Unmatched delimiter: )
             clojure.lang.ExceptionInfo:

;; => {:test 1}
user>

Each time I entered (tap> {:test 1}), but the Clojure REPL plugin seems to only pass  {:test 1}) to the REPL.

@devurandom I understand that the suggestion isn't equal to that, but for the sake of knowledge, I use the Portal plugin for IntelliJ. It works well with tap> and achieves a similar effect to what you suggested (print all tap> in a tab and you can interact with the data in a visual matter).
Maybe can be used as a inspiration also.

Ah that's a bug because of the way we parse the > character in the repl, I'll take a look

Fixed in 1.4.1! Thanks @lread for the help!

Just out of curiousity, after skimming the tests added in https://github.com/afucher/clojure-repl-intellij/commit/74c904300a3df19dcccc5ef2283596cb33d28c3b: Why do you have to parse several request/response pairs and extract the last? Is that a restriction of nREPL, that it does not deal with structured data?


SAML Response not found, Only supported HTTP_POST Binding

I'm trying to implement an SP for a client. When I run this on my dev server, it runs perfect. When I run it on the prod server though, I get the error message
SAML Response not found, Only supported HTTP_POST Binding and a 500 error.
I have the binding set in the SP to urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST .
When I run the program and initialize OneLogin_Saml2_Auth, $_POST is empty. What steps should I take to try and fix this?

Maybe the IdP is not sending properly the SAMLResponse in a POST parameter.
Download and install SAML Tracer and use it to record the SAML flow. You can then verify if the data is there.
SAML Tracer howto: https://helpx.adobe.com/enterprise/kb/perform-a-saml-trace.html

I have the same issue during trying demo1 with this tutorial: https://developers.onelogin.com/saml/php. I'm getting SAMLResponse in GET parameters, instead of getting it in POST. How can I fix it?


set IgnoreUnknown=true for JsonCreator

To prevent we might be incompatible with future tidb version in Json format, we should add IgnoreUnknown=true.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@df61ab5). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #405   +/-   ##
=========================================
  Coverage          ?   55.18%
=========================================
  Files             ?      127
  Lines             ?     5808
  Branches          ?      864
=========================================
  Hits              ?     3205
  Misses            ?     2309
  Partials          ?      294

Impacted Files
Coverage Δ

.../src/main/java/com/pingcap/tikv/meta/TiDBInfo.java
73.91% <ø> (ø)

...main/java/com/pingcap/tikv/meta/TiIndexColumn.java
75% <ø> (ø)

...c/main/java/com/pingcap/tikv/meta/TiIndexInfo.java
60.37% <ø> (ø)

...ent/src/main/java/com/pingcap/tikv/meta/CIStr.java
85.71% <ø> (ø)

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 df61ab5...1b91eee. Read the comment docs.


Struct/union failing due to overlapping cursor enum in libclang Index.h

https://clang.llvm.org/doxygen/Index_8h_source.html#l02582
Both CXCursor_FirstAttr and CXCursor_UnexposedAttr map to 400 which appears to cause issues when wrapping certain C structs and unions.
Example header declarations:
 #ifndef CVITime_DECLARED
 #define CVITime_DECLARED
         typedef struct CVITime { uInt64 lsb; int64 msb; } CVITime;
 #endif
 #ifndef CVIAbsoluteTime_DECLARED
 #define CVIAbsoluteTime_DECLARED
         typedef union CVIAbsoluteTime { CVITime cviTime; uInt32 u32Data[4]; } CVIAbsoluteTime;
 #endif

Resulting cursor info when parsed by Clang.jl:
using Clang, Clang.LibClang

ctx = DefaultContext()
trans_unit = parse_header("NIDAQmx.h")
root_cursor = getcursor(trans_unit)
struct_cursor = search(root_cursor, "CVITime")[1]

for c in children(struct_cursor)
    println("Cursor: ", c, "\n  Kind: ", kind(c), "\n  Name: ", name(c), "\n  Type: ", type(c))
end

wrap!(ctx, struct_cursor)

Output:
Cursor: CLCursor (CLUnexposedAttr)
  Kind: CXCursor_FirstAttr
  Name:
  Type: CLType (CLInvalid)
Cursor: CLCursor (CLFieldDecl) lsb
  Kind: CXCursor_FieldDecl
  Name: lsb
  Type: CLType (CLTypedef)
Cursor: CLCursor (CLFieldDecl) msb
  Kind: CXCursor_FieldDecl
  Name: msb
  Type: CLType (CLTypedef)
┌ Warning: Skipping struct: "CLCursor (CLStructDecl) CVITime" due to unsupported field: CLCursor (CLUnexposedAttr)
└ @ Clang ~/.julia/packages/Clang/CiPzM/src/wrap_c.jl:156

I have fixed this locally by skipping fields where field_kind == CXCursor_FirstAttr in the struct/union dispatches for wrap!(). However, I don't know whether this is a more general bug, or if my fix generalizes appropriately.
The header used to produce this MWE is found here.

fixed by #250.

fixed by #250.


offlineimap: 6.6.0 → 6.6.1

Nitpick: Even though the unicode arrow looks nice, it makes it more complex to filter package updates out of the commit log. Care to use ASCII arrow next time?

In general, I think we should target more Unicode rather than less. But I don't care enough to change the tools and people's habits

@DamienCassou: I do agree unicode is nice. But isn't there many unicode arrows? I think that at least for the commit subject line it'd be nice to have a standard grep'able pattern. (Just my opinion of course.)

I agree that a standard is important.


SearchFacetTest failing with XDMP-BOUNDS

The fix for #804 needs to also be applied to the 3.0-develop branch.  This is simply a unit test failure, so not a critical issue.

Fixed in commit 68ce6e6

The test passed for the 8.0-9.3 release on different platforms. Refer to internal test tracking page for test.
https://regr-status.marklogic.com/platform/result?area=patch&branch=b8_0&date=2019-02-20&platform=linux-64-rh6-cluster&type=passed


feat: add api for configuring commit-hooks based on files

Changes
Minor improvement. I've added api for configuring commit hooks based on File in addition to String and URL.
Context
I find it useful to store commit hooks inside files in my project. For now this case looks a bit ugly in build scripts.
Documentation (please check one with an [x])

[x] I have updated the README.md file, or
[ ] No documentation update is required

How I've tested my work (please tick one)
I have verified these changes via:

[ ] Code inspection only, or
[x] No unit tests but ran on a real Gradle project, or
[ ] Newly added/modified unit tests

Nice, thanks. Reviewed and approved, will auto-rebase in the change as soon as the pipeline gets green.


Running pact test with a matcher in request body returns a Server Error from mock server

🌎 Environment

Platform: PactSwift
pact-reference: libpact_mock_server_ffi built from master (cargo build --release)

💬 Description
When writing a pact test where the request body includes a matcher, the response from mock server is Server Error, status code: 500.
Update:
Happens with POST and request body without a matcher too, but when I used PUT and passed a a request body without a matcher, I received a 201 response as expected.
No change even when specifically defining the request's expected headers to be Content-Type: application/json.
🦶 Reproduction Steps

Steps to reproduce the behavior:

Prepare a unit test that generates a Pact object where a matcher is in the request body
Pass Pact object to libpact_mock_server_ffi
Trigger network request to test the interaction

🤔 Expected Results
The response from mock server returns the value provided in the matcher and status code as defined in pact test.
😲 Actual Results
The response from mock server returns 500 - Server Error.
🌳 Logs
Pact object sent to libpact_mock_server_ffi.create_mock_server()
{
	"metadata": {
		"PactSwift": { "version": "0.0.0" },
		"pactSpecification": { "version": "3.0.0" }
	},
	"interactions": [{
		"response": {
			"status": 201
		},
		"providerState": "users does not exist",
		"request": {
			"path": "\/user",
			"body": {
				"name": "Joe"
			},
			"method": "post",
			"matchingRules": {
				"body": {
					"$.name": {
						"matchers": [{
							"match": "type"
						}]
					}
				}
			}
		},
		"description": "Request to create a user"
	}],
	"provider": { "name": "unit-test-api-provider" },
	"consumer": { "name": "pactswift-unit-tests" }
}

📄 Stack Traces
n/a

🤝 Relationships

Related PRs or Issues:

Update, perhaps it has to do with existing Pact file in PACT_OUTPUT_DIR?
Or maybe having multiple tests setup with same path, query and body but different method?
The following test written in PactSwift passes just fine:
    func testMockService_Succeeds_ForPOSTRequestWithMatchersInRequestBody() {
		mockService
			.uponReceiving("Request to create a new user")
			.given("user does not exist")
			.withRequest(
				method: .POST,
				path: "/user/add",
				query: nil,
				headers: ["Content-Type": "application/json"],
				body: [
					"name": Matcher.SomethingLike("Joe"),
				        "age": Matcher.IntegerLike(42)
				 ]
			)
			.willRespondWith(
				status: 201
			)

		let testExpectation = expectation(description: #function)

		mockService.run { completion in
			let requestURL = URL(string: "\(self.mockService.baseUrl)/user/add")!
			let session = URLSession.shared
			var request = URLRequest(url: requestURL)

			request.httpMethod = "POST"
			request.setValue("application/json", forHTTPHeaderField: "Content-Type")
			request.httpBody = #"{"name":"Joseph","age":24}"#.data(using: .utf8)

			let task = session.dataTask(with: request) { data, response, error in
				if let response = response as? HTTPURLResponse {
					XCTAssertEqual(response.statusCode, 201)
				}
				testExpectation.fulfill()
				completion()
			}
			task.resume()
		}

		waitForExpectations(timeout: 1)
	}

This might be affected by #77, if there was an existing pact file, it would not have been merged correctly.


Load property ContentTypesEnabled before calling method on it

Currently, the methods called separately throws exception:
Field or property ContentTypesEnabled is not initialized.

Hello Erwin,
Thank you for the valuable suggestion.
I will add the check to see IsPropertyAvailable, before loading it.
Thank you.

Implemented the new changes here: https://github.com/OfficeDev/PnP/pull/411
Closing this pull request


Shouldn't return error if IsErrUserNotExist

Shouldn't return an error and stop verifing if the error IsErrUserNotExist.
Related to #22119.

Looks like it should return an error and stop verifing if the error IsErrUserNotExist.


Assertion Failed: You cannot use attributeBindings on a tag-less component: component:mdc-list/item

Probably introduced by #61 and is currently live in v0.0.39.
After fixing and publishing a new version, be sure to deprecate v0.0.39 on npm.

Upon further investigation, this is happening in one of our private apps but the {{#mdc-list/item}} component isn't tagless... Needs more investigation.
https://github.com/secondstreet/ember-material-components-web/blob/v0.0.39/addon/components/mdc-list/item.js#L5-L12

Update: This happened because we were overriding tagName in the hbs in our application. Not the fault of this library.
{{#mdc-list tagName="" as |list|}}


Game titles are not responsive

Can i work on this issue?

@hhhrrrttt222111 Let me know if I can create a new issue to add the code in python/txt folder for a sudoku solver.

can i work on this ? i can make the ui of the webpage better and can a footer too. if u could create an issue and assign me i would love to contribute.
By the way, there is no hacktober fest tag on this repo. kindly do that too.

can i work on this ? i can make the ui of the webpage better and can a footer too. if u could create an issue and assign me i would love to contribute.
By the way, there is no hacktoberfest tag on this repo. kindly do that too.

Yep, You can wrk on it.
And there is hacktoberfest tag ;}}}}}

can i work on this ? i can make the ui of the webpage better and can a footer too. if u could create an issue and assign me i would love to contribute.
By the way, there is no hacktoberfest tag on this repo. kindly do that too.

Yep, You can wrk on it. And there is hacktoberfest tag ;}}}}}

Please do assign me


Transparent hover

Sometimes I accidentally leave my mouse on the in-line blame annotation, and the hover appears, blocking code I'm trying to read. I haven't found a way to make the hovers transparent. Ideally, it could follow the behavior specified by the following in settings.json:
"workbench.colorCustomizations": {
    // transparent code suggestions
    "editorSuggestWidget.background": "#21252BAA"
}

Let me know if I simply haven't found the setting to change.

editorHoverWidget.background should be what you are looking for
You can see them all here:
https://code.visualstudio.com/api/references/theme-color#editor-widget-colors
Hope that helps!


SPFarmSolution install under service account without localLogonAllowed permission

Hi guys.
Many time passed since MSFT_SPFarmSolution.psm1 has been released, but I didn't see possibility to install wsp under service account without localLogonAllowed permission. If I skip PsDscRunAsCredential or InstallAccount it fail with
You need to specify a value for either InstallAccount or PsDscRunAsCredential
If I pass PsDscRunAsCredential it fail with something like

User don't have permissions to local log on.

In that way I can not use your scripts.
Details of the scenario you tried and the problem that is occurring
Verbose logs showing the problem
Suggested solution to the issue
Change Invoke-SPDscCommand in SharePointDsc.Util.psm1 to make it possible to run commands under users without locallogonallowed permission. Like entering pssession or something like this?
The DSC configuration that is used to reproduce the issue (as detailed as possible)

[CmdletBinding()]
param(
	[parameter(Mandatory = $true)]
	[String]
	$OutputPath,

	[parameter(Mandatory = $true)]
	[String]
	$WspPath,

	[parameter(Mandatory = $true)]
	[String]
	$Version,

	[parameter(Mandatory = $true)]
	[PSCredential]
	$InstallAccount
)
Configuration WspConfig
{
	[CmdletBinding()]
	param(
		[parameter(Mandatory = $true)]
		[String]
		$WspPath,

		[parameter(Mandatory = $true)]
		[String]
		$Version,

		[parameter(Mandatory = $true)]
		[PSCredential]
		$InstallAccount
	)

	Import-DscResource -ModuleName 'PSDesiredStateConfiguration'
	Import-DscResource -Name 'SPFarmSolution' -ModuleName 'SharePointDsc'

	Node $AllNodes.NodeName {

		$file = [System.IO.Path]::GetFileName($WspPath)

		SPFarmSolution SampleWsp
		{
			Name                 = $file
			LiteralPath          = $WspPath
			Ensure               = "Present"
			Version              = $Version
			SolutionLevel        = "All"
			Deployed             = $true
			PsDscRunAsCredential = $InstallAccount
		}
	}
}

WspConfig -OutputPath $OutputPath -ConfigurationData "$PSScriptRoot\ConfigurationData.psd1" -WspPath $WspPath -Version $Version -InstallAccount $InstallAccount -Verbose

The operating system the target node is running
OsName               : Microsoft Windows Server 2012 R2 Standard

OsOperatingSystemSKU : StandardServerEdition
OsArchitecture       : 64-bit
WindowsBuildLabEx    : 9600.18589.amd64fre.winblue_ltsb.170204-0600
OsLanguage           : en-US
OsMuiLanguages       : {en-US}
Version of SharePoint that is used (e.g. SharePoint 2016)
SharePoint 2013
Version and build of PowerShell the target node is running
PSVersion                      5.1.14409.1005
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.14409.1005
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
Version of the DSC module that was used ('dev' if using current dev branch)
master

Hi @VerdonTrigance Unfortunately we cannot implement your suggestion because SharePoint doesn't allow PowerShell commands to be run under the system account. The system account of a SharePoint server doesn't have any permissions to connect to a database on a SQL server.
However, both the InstallAccount and PsDscRunAsCredential parameters should work. What permissions does the account you are using have?

However, both the InstallAccount and PsDscRunAsCredential parameters should work. What permissions does the account you are using have?

As I told previously my account can not login into system because of "Allow log on locally" equals false. And this leads to fail during execution.

Have you tried the InstallAccount option instead of PsDscRunAsCredential? So:
SPFarmSolution SampleWsp
{
	Name                 = $file
	LiteralPath          = $WspPath
	Ensure               = "Present"
	Version              = $Version
	SolutionLevel        = "All"
	Deployed             = $true
	InstallAccount       = $InstallAccount
}

NOTE: The InstallAccount method is a little slower than the PsDscRunAsCredential, but might work in your case.
NOTE2: This solution requires CredSSP to be configured, but is using a remote session to itself to run the command under different credentials.

Have you tried the InstallAccount option instead of PsDscRunAsCredential? So:
SPFarmSolution SampleWsp
{
	Name                 = $file
	LiteralPath          = $WspPath
	Ensure               = "Present"
	Version              = $Version
	SolutionLevel        = "All"
	Deployed             = $true
	InstallAccount       = $InstallAccount
}

NOTE: The InstallAccount method is a little slower than the PsDscRunAsCredential, but might work in your case.
NOTE2: This solution requires CredSSP to be configured, but is using a remote session to itself to run the command under different credentials.

I have tried it and it works. I was confused with description:
[Write, Description("POWERSHELL 4 ONLY: The account to run this resource as, use PsDscRunAsCredential if using PowerShell 5"), EmbeddedInstance("MSFT_Credential")] String InstallAccount;
As solution for this may be you add some words about this case in https://github.com/PowerShell/SharePointDsc/blob/dev/Modules/SharePointDsc/DSCResources/MSFT_SPFarmSolution/Readme.md ?

This parameter is required if you use PSv4, but of course still works in PSv5. However since PsDscRunAsCredential was introduced in PSv5, which is much more performant and doesn't require the use of CredSSP, we recommend to use that instead of the InstallAccount.
This is however not specific to SPFarmSolution, but applies to all resources. So adding it to the Readme for SPFarmSolution doesn't make much sense. I will see how we can include this in the overall documentation/wiki.

Ok. Thank you. You may link this issue as a reason for changing documentation.


Backend does not need to be in its own folder

The backend to PyJet is currently so small, it does not need to be in its own folder. It should be moved into a python file named "backend.py".

Fixed with commit @298c45d72cdcfc74291e1ca193538aaa0cbd5a68


Support AllCops:ActiveSupportExtensionsEnabled for Style/SymbolProc

Follow up https://github.com/rubocop/rubocop/commit/d39f07376d7928f7b6ee1df12cdba086cb552e5e.
This PR supports AllCops:ActiveSupportExtensionsEnabled instead of a TODO comment in Style/SymbolProc cop.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!

I'm seeing a false positive here with CSV converters. They also check the arity of the proc, so auto-correcting from ->(x) { x.upcase } to lambda(&:upcase) breaks. I guess it's fine because the autocorrect is not safe, but just wanted to point it out in case someone else hits this.
I was able to prevent Rubocop from reporting the offense by using the ActiveSupportExtensionsEnabled configuration option: https://github.com/Shopify/maintenance_tasks/commit/d24e07a9087b8159502198ce439b6e8a08ac6149. Although I don't think this applies to everybody because a Ruby gem without Active Support could hit the same issue, but my case is a Rails engine so it's fine.


This enables creating deployments with some additional options

A use case example is that without this code it isn’t possible to create a deployment for a custom virtual network/subnet…
See PR #107 for the complete story on this one.

@svanharmelen it looks like tests have some references to the old CreateDeployment method signature (but we're investigating why they're not failing on CI). Can you please fix the tests as well, thanks.

LGTM. Also @svanharmelen did you manually test this if this actually can deploy the VM with specified settings. The comment by @paulmey on the other thread was Azure APIs are sometimes sensitive to  order of the elements in the request XML (although this is not clearly documented). That's why we try to manually test the new implementations as much as we can.

@ahmetalpbalkan which tests? I couldn't spot them at first sight...
And yes, see my replies on his comments/questions:
@paulmey yes, I certainly tested this :smiley: It's not only reordered but I also added the `Subnet` field and I did more then a few tests today with creating virtual networks and subnets and then adding virtual machines to them.

So during the day I added a few, updated a few existing ones and also deleted a few again. So I would say I touched all operations at least a couple of times.

But even through I did test it pretty well, I did also revert the ordering change and replied that as well:
@paulmey just reverted the ordering as there isn't any good argument for the reordering other than personal preference. So if you have any experience with the order being picky, let's just keep that in sync with the API docs...

@svanharmelen there are two test files:
$ ack --go CreateDeployment
management/virtualmachine/client.go
27:func (self VirtualMachineClient) CreateDeployment(role Role, cloudServiceName string) (management.OperationId, error) {

management/vmutils/examples_test.go
42:	operationId, err = virtualmachine.NewClient(client).CreateDeployment(role, dnsName)

management/vmutils/integration_test.go
109:		return vmc.CreateDeployment(role, vmname)
189:		return vmc.CreateDeployment(role, vmname)

Ah... In the vmutils package... Check, will have a look.

@ahmetalpbalkan updated the tests...

@svanharmelen can you please rebase your branch on top of master? I just renamed MSOpenTech word in the imports to Azure (that was causing false positives in the CI earlier).

Grr... Rebasing => OK, but then squashing it => NOK
Will create yet another PR.

@svanharmelen I will write a blog post about how to squash things. :-)

Well I know how to squash commits, no worries :wink: And I also know how to update my fork from a remote source... But when doing a fetch remote, rebase upstream and then a squash, ofter causes me to have older commits in any outstanding PRs based on the branch I'm squashing.
So if you have a good workflow which prevents that, please do write it up and send me the link :smiley:


Can't browse discovery with EF store in RC4-update1

When using IdSrv4 with EF store (RC4-update1) the discovery document (/.well-known/openid-configuration) can't be browsed due to breaking changes in EF I'm guessing.
MissingMethodException: Method not found:
    'Microsoft.EntityFrameworkCore.Query.IIncludableQueryable`2<!!0,!!2>

Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.ThenInclude(Microsoft.EntityFrameworkCore.Query.IIncludableQueryable2<!!0,System.Collections.Generic.ICollection1<!!1>>, System.Linq.Expressions.Expression1<System.Func2<!!1,!!2>>)'.
IdentityServer4.EntityFramework.Stores.ResourceStore.GetAllResources()
IdentityServer4.Stores.IResourceStoreExtensions+d__2.MoveNext()
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

Tmp fix for this is to provide your own impl. of IResourceStore, copied the one from this repo and just changed all ThenInclude to Include.

Duplicate of #38. IdentityServer 4 is currently being migrated to support .NET 1.1 only.


Increase loki storage

The Loki pod is running out of space.
I am not sure yet if it support live resizing

It appears that it can automatically resize the disk, we just have to restart the pod
https://kubernetes.io/blog/2018/07/12/resizing-persistent-volumes-using-kubernetes/


Playlist demo

You can demo playlist video

Hey,
No need for a demo,  check this page: Moovie Playlist
If there is something else you think it would be nice to have, feel free to open a PR


[EN] Feedback for: /web/tools/chrome-devtools/?hl=en

Can't properly read the page on my Galaxy S5. No shrink or 'View as web page' functionality.
What happened to 'mobile first design'?

Thanks for the feedback, we've got an update coming this week that should fix this.


Error messages are quite uninformative

Syntax errors look like this right now:
$ eslc <<< "("

/home/an/code/eslisp/node_modules/sexpr-plus/index.js:1054
      throw peg$buildException(null, peg$maxFailExpected, peg$maxFailPos);
      ^
SyntaxError: Expected ")", comment or whitespace but end of input found.

The SyntaxError-object sexpr-plus returns has line and column properties. We should perhaps use them.

Invalid AST errors look like this:
$ eslc <<< "(+ x %)"
{ [InvalidAstError: Identifier `name` member must be a valid IdentifierName]
  node: { type: 'Identifier', name: '%' },
  message: 'Identifier `name` member must be a valid IdentifierName' }
x + %;

That's already getting there, but it would still be best if exact positions in code were passed on to AST nodes, so the error reporter could point out the exact in-source position that an error happened.

Here's what we have as of bf7bb54:

An illegal identifier occurring in a built-in macro is highlighted in source. This should work with any error returned by esvalid, but I haven't tested it comprehensively.
As you can see in the last command, the invalid AST node originating from the user-defined macro nonsense isn't shown with highlighted source. This is because macros aren't necessarily even in the source: they may have been required from another module or themselves generated by another macro.
It would be good to at least display the macro's name ([ returned from macro 'nonsense' ]), but macro return values are not currently tagged with that information.

@anko
Could this be implemented via an env::fail() method? That could also be potentially useful for macro writers as well, if they need to fail with a more descriptive error than simply "Oh, by the way, this will break if you're not careful", which is a common problem with macros, especially when you're dealing with DSLs.
I was just thinking of this when I was working on #41. That as a high-level method might be the best way to do it, and it would definitely be worth exposing.

@isiahmeadows I've just had macros throw an error when user input is nonsensical.
However, the compilation env makes no attempt to catch errors from macros at the moment. Hence the stack traces don't tell you useful stuff e.g. which macro it was that errored. I think catching would be a better way than an env::fail, because something the macro-writer didn't think to check for might throw an error too.

f19be373fbcba3c0fc380c2adc15d0f4e171b1f0 now catches macro errors and adds diagnostic data before rethrowing. Thanks for raising that.


A cool port would be the game Dementium 2, it is available on steam. Normally a NDS game, but it is rough on such a small screen.

Before submitting your issue or feature request.  DO NOT REQUEST PORTS THROUGH THIS PROCESS.  I will no longer be focusing on adding additional ports at this time.  You may try to post your request here for an alternative unofficial solution.  Do understand support for those ports will not be available on this github.

This is not Anbernic Stock Emuelec or 351Elec.  ArkOS is a different distribution from those systems and will have differing features.  The only somewhat similarity is that they both use EmulationStation as a frontend.  Even with that, the versions of EmulationStation that's used in between ArkOS and Anbernic Emuelec/351Elec is different with different capabilities.  If there are features you prefer with Anbernic Emuelec/351Elec, just use those distributions instead.  The choice is yours.

Have you reviewed the Frequently Asked Questions available at https://github.com/christianhaitian/arkos/wiki/Frequently-Asked-Questions---RG351P ?

If your issue is related to being able to run certain emulators or ports, have you reviewed the Emulators and Ports section available at https://github.com/christianhaitian/arkos/wiki/ArkOS-Emulators-and-Ports-information for needed bios files and supported rom extensions?

Have you reviewed the known issues section available at https://github.com/christianhaitian/arkos/wiki/Known-issues ?

Describe the Issue (If applicable)
A clear and concise description of what the bug is.
How can the issue be reproduced? (If applicable)
What device are you using?
What version of ArkOS are you on?

You can find this during the initial boot process right before the Emulationstation loading screen

Anything else you'd like to include that may help to review this issue or feature request?

I thought the game is cool but the steam version who be better for the rg351p not having to split the screen.

I'm not focusing on working on getting anymore ports.  See here for more info.


Image loader part 10

Previous ImageLoader version had an issue that could cause Publish to load images in an infinite loop.  So taking my 10th shot at this.

[x] Create a demo encapsulating all possible use cases (switching inputs, going back to null/placeholder state, etc)
[x] Get rid of nativeElement manipulation - just use angular bindings
[x] Reset entire ImageLoader state on changes, then wait for the prx:image / src to load before displaying anything at all.

Correct - we're not doing that.  I spent some time trying to get both to behave ... but would always get into strange scenarios where the 2nd wouldn't onLoad.  So ended up giving the src precedence.

Makes total sense. Feels like src and imageDoc should have been separate components. Hind sight 👓


:herb: add response models

Summary
This PR shows an example of how to annotate FastAPI methods with response models. This will improve the generated OpenAPI and documentation.

Closing in favour for #297


Made some refinements

Made some refinements
I've also added a pull request to hascal.github.io
Please review and merge the request
I've also added a message in the hascal gitter community - here
Hopefully Pranav

I can only merge your commits about readme file,other files are not compatible with the compiler structure


Experiencing Error 'option pickDate is not recognized!' only on external domain w/ Chrome 40.0

Im experiencing the following error option pickDate is not recognized! when my code is deployed to my domain. While running locally on a PHP server it does fine and i experience no error. However when i deploy my code to my AWS PHP hosted server and am running Google Chrome i am presented with the following error as soon as the input is rendered on the page. This issue doesnt seem to happen on Firefox or Safari.
Any ideas? or work arounds? or am i simply missing something here?
Current Setup

Beta v4 of the datetimepicker
JQuery (google hosted v. 2.1.3)
HTML 5 doctype
PHP v5.5
Google Chrome 40.0.2214.94 (64-bit)

Chrome Stacktrace (if helpful)
/**
Uncaught TypeError: option pickDate is not recognized!
bootstrap-datetimepicker.min.js:1 (anonymous function)
jquery.min.js:2
n.extend.eachbootstrap-datetimepicker.min.js:1
j.optionsbootstrap-datetimepicker.min.js:1
cbootstrap-datetimepicker.min.js:1 (anonymous function)
jquery.min.js:2
n.extend.eachjquery.min.js:2
n.fn.n.eachbootstrap-datetimepicker.min.js:1
a.fn.datetimepickerindex.js:30 (anonymous function) **/

Code
$(function () {
        $('#time_in').datetimepicker();
        $('#time_out').datetimepicker();
        $("#time_in").on("dp.change",function (e) {
            $('#time_out').data("DateTimePicker").minDate(e.date);
        });
        $("#time_out").on("dp.change",function (e) {
            $('#time_in').data("DateTimePicker").maxDate(e.date);
        });
    });

<form method="post">
...
    <input type='text' class="form-control text-center" id='time_in' name="time_in" value="<?php echo $time_in; ?>" required />
    <input type="text" class="form-control text-center" name="time_out" id="time_out" value="<?php echo $time_out;?>" required/>
...
</form>

pickDate is an option we removed from v4 in favor of using the format string to determine what components to show.
Can you setup a jsfiddle with a minimal example of your code/issue?

Here is the jsfiddel => http://jsfiddle.net/jaisonbrooks/Lgo9n256/
And i pulled the current external resource from the predefined jsfiddle to ensure it was the latest v4 and im receiving an error at this part in the script.
throw new TypeError('option ' + key + ' is not recognized!');

please let us know if you're still having this issue.


As a user, I want to view all the cities in a continent organized by largest population to smallest.

Done


Add support for parsing healing elemental damages

Some creatures are healed by elemental damage. tibia library displays this information.

What is more, they are healed when fire damage is used against them.

source: https://www.tibia.com/library/?subtopic=creatures&race=lavablob
I would expect this information to be in a [string] field and work the same as immune, strong, and weakness fields

Interesting catch.. is that the only monster healed by anything or are there any other?

Seems to be the only one from what I can tell so it makes this rather low importance. Yet it would still be nice to have.

@soul4soul ye of course, I just thought that there might be some else so that the parsing can be tested against another creature as well. Even if its one it should be added. I'll check into it on the weekend or so :-)

On.. one more:
https://www.tibia.com/library/?subtopic=creatures&race=foamstalker

On.. one more: https://www.tibia.com/library/?subtopic=creatures&race=foamstalker

Wow that is super interesting consider players can't deal agony damage, and last time I was at foamstalkers they don't deal that damage either.


Build failure on windows after commit 6bfc2c7

Build output:
vendor\github.com\prometheus\procfs\internal\util\parse.go:79:28: cannot use int(f.Fd()) (type int) as type syscall.Handle in argument to syscall.Read

Please fix this asap. These are no tags or "stable" branches in this repo. This is breaking builds all over the place that include prometheus golang client. Not having tags will force people to disable windows builds or vendor the whole repo just to remove it when this is fixes.
Maybe should use some other branch than master to do dev and run tests.

I'm importing client_golang and using dep (still). This means that procfs is a transitive dependency to my project and thus will only get the required packages. So client_golang requires procfs package which in turns requires xfs and nfs packages which, finally, require the util package.
So, moving this function (which is OS-specific if I understand correctly) to the util package, makes every attempt to build to another OS unsuccessful.
I hope that was helpful.

I would appreciate some help from some more experienced Windows developers.
One thing I'm thinking about is how does the processCollector work on Windows?
Does this bit of code work at all? Perhaps we can fix the dependency tree there, so that on windows it doesn't use any Linux-specific stuff like procfs.

@SuperQ as described, this seems to break all builds that fetch latest prometheus go client.
If you don't yet know how to fix it properly, please revert the commit. Do the change later when you figure it out.
Do this to fix this now:
git revert 6bfc2c70c4ee6da6946888bb96dec33f825df32b
git push origin/master

When you try again locally, just run GOOS=windows go build in this repos folder to test if the bug is fixes, you will get what was reported in the first message. You don't need access to windows to figure this out.

One thing I'm thinking about is how does the processCollector work on Windows?

It doesn't report metrics, but an error. The code in question is https://github.com/prometheus/client_golang/blob/master/prometheus/process_collector.go#L128-L135 .
Thus, it depends on the NewStat constructor to return an error on platforms that aren't covered by prometheus/procfs. The latter should have all the build guards to not try anything on (e.g.) MS Windows that wouldn't compile.

I think the problem is that the sysfs package wouldn't work on MS Windows but wasn't used by any binaries meant for MS Windows. Now SysReadFile got moved into the util package, which is used by binaries meant to be built for MS Windows. I would just not move it into the general util package. (Am I missing a reason for doing so?)

@beorn7 The reason to move it to the internal/util package was to make it more useful across the procfs package.
IMO, the problem here is we don't have a platform-specific setup for client_golang's process collector.

client_golang is not the only user of this repo. I don't think all users of this repo should pull up the information on which platform it works and on which not. This should only be maintained at one place, which is here in the repo. Currently, the API works in a way that you call NewStats and check the error to see if the process stats are supported on your platform. It would be a breaking change to change that to "the package doesn't compile and you need build tags to guard its usages".

For now, I'd just not move SysReadFile into the util package. You are not yet using in anywhere outside of the sysfs package. Perhaps discuss a possible change with @grobie when he is back.

Ok.  I'm setting up a test matrix on Travis right now so we can verify the change works.

I've finished the test matrix, and refactoring the code.
https://github.com/prometheus/procfs/pull/112

Ok, please test your windows builds with the latest commit. Sorry for the breakage, we now have a CI test to prevent this in the future. :smile:

All good. Thank you!


Migrate to ruff linter and formatter

We're currently processing your upload.  This comment will be updated when the results are available.


A set of semantic tokens

Main issue: #307.
We should define a set of semantic token at server-side, and use these tokens during the parsing process.
See here for LSP reference.
See here for TextMate scope conventiion
Structure
Server
string -> number by enumerators.
Client
number -> string by arrays in the returned legend.
List

Semantic Token Selector
TextMate Scope
Note

annotation
markup.heading.annotation.mcfunction
A doc comment annotation

boolean
constant.language.boolean.mcfunction
A real boolean value

comment
N/A
-

entity
support.class.entity.mcfunction
An entity or a score holder

keyword
N/A
.. in number ranges and time units

literal
keyword.other.mcfunction
A literal argument

literal.firstArgument
keyword.control.mcfunction
A literal argument which is also the first argument

namespacedID
entity.name.function
A namespaced ID

number
N/A
-

operator
N/A
matches, =, /=, etc.

property
N/A
entity selector arguments keys, block property keys, NBT compound tag keys, and NBT path keys

string
N/A
-

type
N/A
Item slots, scoreboard slots, and objective criteria

variable
N/A
Objectives, teams, and tags

vector
constant.numeric.vector.mcfunction
A vector

N/A means that this token is a standard token and is implemented in VSCode by default.

:tada: This issue has been resolved in version 1.13.0 :tada:
The release is available on:

npm package (@latest dist-tag)
Visual Studio Marketplace
GitHub release

Your semantic-release bot :package::rocket:


Make TagBot work again (at all)

With https://github.com/JuliaRegistries/TagBot/pull/279 merged, we need to wait for a new version of the TagBot action to be tagged (no pun intended). Once this has happened, we should be able to use TagBot for automatic new release creation.

A new version of TagBot (v1.16.0) has been released - I think we should be good to go!

@bgeihe Once this has been merged, you could also create a new release v0.1.2 that incorporates the fixes to HDF5.


[@azure/openai] - Test Case Bug that reports success even in case of failure

Package Name:  @azure/openai
Package Version: 1.0.0-beta.12
Operating system:
[X] nodejs

version:

[X] browser

name/version:

[ ] typescript

version:

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
In the @azure/openai package, under test/public folder, test file embeddings.spec.ts, we have a test case wrong prompt type. The code for the following is presented below:
it("wrong prompt type", async function () {
  // TODO: Update the error message expectations
  assertOpenAiError(client.getEmbeddings(modelName, true as any), {
      messagePattern: /\$.input invalid/,
      type: `invalid_request_error`,
  });
});

export async function assertOpenAiError<T>(
  promise: Promise<T>,
  expectations: {
    messagePattern?: RegExp;
    type?: string;
    errorCode?: string;
  },
): Promise<void> {
  try {
    await promise;
  } catch (e: any) {
    assert.equal(true, false);  <====== USER ADDED CODE LINE FOR HIGHLIGHTING THE ISSUE
    const { messagePattern, type, errorCode } = expectations;
    if (messagePattern) {
      assert.match(e.message, messagePattern);
    } else {
      assert.isUndefined(e.message);
    }
    if (type) {
      assert.equal(e.type, type);
    } else {
      assert.isUndefined(e.type);
    }
    if (errorCode) {
      assert.equal(e.code, errorCode);
    } else {
      assert.isUndefined(e.code);
    }
  }
}

Basically, the function of the above test code is that it expects an error and the error is validated in the assertOpenAiError method's catch block. But, what is happening is even though assertions are failing, it is never reported and the test case is reported as success.
Let me give an example. The message patter is mentioned as /\$.input invalid/. The actual error message is '$,input' is invalid'. The assertion  assert.match(e.message, messagePattern);` will normally fail. But, it is not reported as failure. The test case is marked as success.
A more clear example would be the assert.equal(true, false); assertion that I added in the above. You can execute with the above line and still the test case will be marked as Success. This should be fixed.
Since this method is just used by only one test case, we could fix it simply by modifying the code as mentioned in https://github.com/Azure/azure-sdk-for-js/pull/28539.  I have made the PR. But, I could not get all the recordings since the code runs for a long time and eventually fails in some unrelated tests.
To Reproduce
Provided context and other required details above.
Expected behavior
Provided context and other required details above.
Screenshots
NA
Additional context
NA
@deyaaeldeen @minhanh-phan @xirzec FYI.......

Ah, the promise is not awaited inside the unit test.


Added workitem.GormWorkItemTypeRepository.CreateFromModel

Allow work items to be created from a given model an not only from a given set of arguments.

Ike Plugins (test-keeper)
Thank you @kwk for this contribution!

It appears that no tests have been added or updated in this PR.
Automated tests give us confidence in shipping reliable software. Please add some as part of this change.
If you are an admin or the reviewer of this PR and you are sure that no test is needed then you can use the command /ok-without-tests as a comment to make the status green.
For more information please head over to official documentation. You can find there how to configure the plugin.

Codecov Report

Merging #2185 into master will increase coverage by <.01%.
The diff coverage is 92%.

@@            Coverage Diff             @@
##           master    #2185      +/-   ##
==========================================
+ Coverage   69.63%   69.64%   +<.01%
==========================================
  Files         170      170
  Lines       15675    15682       +7
==========================================
+ Hits        10916    10921       +5
- Misses       3769     3770       +1
- Partials      990      991       +1

Impacted Files
Coverage Δ

workitem/workitemtype_repository.go
78.01% <92%> (-0.35%)
:arrow_down:

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 eb7b815...d1589b6. Read the comment docs.

/ok-without-tests


Strange behavior with custom "value" property

I have a custom Polymer component which has a property:
value: {
    type: String,
    value: "",
    observer: "valueChanged"
}

And I noticed that the value of the property being changed when it should not. Here is a minimal example to reproduce the issue: https://jsfiddle.net/vskkLr1t/1/.
Steps to reproduce:

Open console.
Input 1 in the first field.
Wait till the sum updates.
Input 2 in the second field.
The sum (value property) will be set to 2.
Wait till the sum is updated again, this time to 3 which is correct.

Console output:
1: valueChanged 1
2: valueChanged 1
3: valueChanged 2
4: valueChanged 3

The lines 1 and 3 should not be there.
Exactly same code works as expected if I rename property from value to v: https://jsfiddle.net/vskkLr1t/.

The change event from the input bubbles, so you're setting model.value to the value of each input individually from the change events, then the timeout in abChanged will set value to what you expected.
A better setup would be to use a complex observer and just observe the value property like this example: http://jsbin.com/xaqana/edit?html,console,output


Update sanger_test_full.yml -test linting fixing

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

@sanger-tol-bot fix linting

@nf-core-bot fix linting


feat: T2 instance for one point compactification

The one point compactification of a locally compact T2 space is T2.

Sorry for the disturbance, I realized this instance is implied by the one below, I should have read the doc more carefully.


dpram memory error in OpenFPGA arch file

I am trying to integrate my own architecture with dpram by taking an architecture file with dpram property as reference. However when I try to run a benchmark I'm getting Error 1: Miss a default circuit model for the type hard_logic! Try to define it in your architecture file!
Error 2: Command 'read_openfpga_arch' execution has fatal errors I integrated a few architectures with dpram before and I did same process on this one, however I'm facing an error like this first time. What could be the reason @tangxifan @ganeshgore ? Thanks.

openfpga arch file:
openfpga_arch.txt

I solved the issue by adding "is_default=true" parameter to the hard_logic dpram definition. Thanks.


Fix #193: don't fail when there is no remote named origin

This doesn't add support for remotes with names other than origin, but it does add a default value when there isn't a remote named origin so that we don't freak out while parsing the project & repo names. This should fix #193.
Also minor update to README to document the "copy hash on click" feature.
Note: all of the tests in specs/RemoteRevision-spec.js are passing, but the spec/git-blame-spec.coffee tests are not. From what I can tell, these appear to be outdated tests and I don't think the failures are related to my changes.

@claytonrcarter this was released in v1.8.0


HDFS-14638. [Dynamometer] Fix scripts to refer to current build structure.

NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute

@smengcl would you like to review this?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
77
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

0
shelldocs
0
Shelldocs was not available.

+1
@author
0
The patch does not contain any @author tags.

-1
test4tests
0
The patch doesn't appear to include any new or modified tests.  Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

0
mvndep
34
Maven dependency ordering for branch

+1
mvninstall
1234
trunk passed

+1
mvnsite
80
trunk passed

+1
shadedclient
808
branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

0
mvndep
13
Maven dependency ordering for patch

+1
mvninstall
72
the patch passed

+1
mvnsite
61
the patch passed

+1
shellcheck
1
There were no new shellcheck issues.

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedclient
896
patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1
unit
21
hadoop-dynamometer-workload in the patch passed.

+1
unit
22
hadoop-dynamometer-infra in the patch passed.

+1
unit
21
hadoop-dynamometer-blockgen in the patch passed.

+1
asflicense
32
The patch does not generate ASF License warnings.

3497

Subsystem
Report/Notes

Docker
Client=19.03.4 Server=19.03.4 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1673/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/1673

Optional Tests
dupname asflicense mvnsite unit shellcheck shelldocs

uname
Linux 22665cb4a1c6 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / fd84ca5

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1673/1/testReport/

Max. process+thread count
342 (vs. ulimit of 5500)

modules
C: hadoop-tools/hadoop-dynamometer/hadoop-dynamometer-workload hadoop-tools/hadoop-dynamometer/hadoop-dynamometer-infra hadoop-tools/hadoop-dynamometer/hadoop-dynamometer-blockgen U: hadoop-tools/hadoop-dynamometer

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1673/1/console

versions
git=2.7.4 maven=3.3.9 shellcheck=0.4.6

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

Thanks @jojochuang for pinging.
Thanks @tasanuma for the patch. I tested this locally. Those scripts correctly points to the jars now:
$ mvn install -Pdist -DskipTests -e -Dmaven.javadoc.skip=true
$ cd hadoop-dist/target/hadoop-3.3.0-SNAPSHOT
$ ./share/hadoop/tools/dynamometer/dynamometer-blockgen/bin/generate-block-lists.sh
Exception in thread "main" org.apache.commons.cli.MissingOptionException: Missing required options: fsimage_input_path, block_image_output_dir, num_datanodes
...
$ ./share/hadoop/tools/dynamometer/dynamometer-infra/bin/start-dynamometer-cluster.sh
2019-10-24 09:16:16,098 INFO dynamometer.Client: Initializing Client
2019-10-24 09:16:16,099 ERROR dynamometer.Client: Error running Client
org.apache.commons.cli.MissingOptionException: Missing required option: ...
$ ./share/hadoop/tools/dynamometer/dynamometer-workload/bin/start-workload.sh
Exception in thread "main" org.apache.commons.cli.MissingOptionException: Missing required options: nn_uri, mapper_class_name
...

Before the patch is was complaining:
$ ./share/hadoop/tools/dynamometer/dynamometer-blockgen/bin/generate-block-lists.sh
JAR does not exist or is not a normal file: /Users/smeng/repo/trunk/hadoop-dist/target/hadoop-3.3.0-SNAPSHOT/share/hadoop/tools/dynamometer/dynamometer-blockgen/lib/dynamometer-blockgen-*.jar

LGTM +1

+1 will merge the PR shortly.

Thanks for reviewing and committing it, @smengcl and @jojochuang!


release/0.116.1

chore: skip node_sqlite3.node copyplugin if missing
chore: publish minor
resolved merge conflict in yarn.lock
fix(publish): make safe access to iframe (#3707)
fix fuzz threshold issue
fix(publish): correct hashtag parsing (#3708)
throttle engine calls

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 5 committers have signed the CLA.:white_check_mark: jonathanyeung:white_check_mark: Harshita-mindfire:white_check_mark: kevinslin:white_check_mark: namjul:x: github-actionsgithub-actions seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Response to voice commands targeting an entity respond based on the domain and not with the terminology that the user used

I have a number of entities that are exposed to Assist that I use voice commands to control and I find that the response uses HA-specific terminology, specifically the domain of the entity, rather than the term that the user used.  For example, I have an input_boolean helper with an alias of "pump", and when I say "turn on the pump", the voice response is "turned on input_boolean" (as "input underscore boolean", which is especially weird and robotic).  Same thing when I say "Turn on the family room lights", which is an alias for a light entity, and the response is "turned on the light", because it's a light group.  I guess my "complaint" is that it responds based on domain of the entity, rather than just parroting what the user asked for, which can be confusing.  It seems like Assist knows what the user asked for, and could respond in kind.
I've noticed this behavior for "a while", but I'm not sure when it started, or if it ever responded based on the initial request.  I do see this behavior in 2023.3.0b1.  @tetele asked that I open an issue here based on a discussion on Discord.

Hi, I also struggled with avoiding the underline in Hungarian :)
I solved it in the following way:
     {% set translations_domains_with_article = {
        "button": "gombot",
        "camera": "kamerát",
        "input_button": "gombot",
        "alarm_control_panel": "riasztót",
        "automation": "automatizálást",
        "fan": "ventilátort",
        "climate": "hőmérsékletszabályozót",
        "humidifier": "párásítót",
        "input_boolean": "kapcsolót",
        "siren": "szirénát",
        "water_heater": "melegvíz tartályt",
        "light": "lámpát",
        "switch": "kapcsolót",
        "script": "szkriptet",
        "remote": "távirányítót",
        "lock": "zárat",
        "vacuum": "porszívót",
        "scene": "jelenetet",
        "media_player": "médialejátszót",
        "lawn_mower": "fűnyírót",
        "valve": "szelepet"
        } %}

I'm looking at it now, and indeed in English it displays the domain. I can't even remember what I translated from, but in Hungarian it confirms back the name of the tool.
As I read, this is due to the simplification of the response.
But the system is capable of displaying the name, so it's a matter of decision. With the translation part, the underscores can be eliminated. Although in English it might be sufficient to just replace the '_' character with a space.
Turned on the {{ state.domain | replace('_', ' ') }}


Wrong arcLength result

I'm looking on data like this:
Vector<3, double> points:
[0]	(0.00000000000000000,0.00000000000000000,0.00000000000000000)
[1]	(1.0000000000000000,0.00000000000000000,0.00000000000000000)
[2]	(4.0000000000000000,0.00000000000000000,0.00000000000000000)
[3]	(9.0000000000000000,0.00000000000000000,0.00000000000000000)
[4]	(16.000000000000000,0.00000000000000000,0.00000000000000000)
[5]	(25.000000000000000,0.00000000000000000,0.00000000000000000)
NaturalSpline<Vector<3,double>, double> spline(points, true, 0.5);
double 		t = 0.38215637207031250, t0	= 0.47108459472656250;
Then I get this:
	spline.arcLength(t0, t0 +t)	 == 0.50000331420977806

but:
spline.getPosition(t0) == (1.0000076740967552,0.00000000000000000,0.00000000000000000)
and
spline.getPosition(t0 + t)	== (2.2312049143150867,0.00000000000000000,0.00000000000000000)
Since all the points are on the same straight line (and looks like there's no wiggles between t0 and t0 + t), I'd expect arcLength to be 1.2312....

Hey! So this is caused by the same problem as #4 where several spline types weren't computing the arc length correctly when alpha was nonzero. This particular problem comes up when a and b are inside the same segment and alpha is nonzero.
I designed the unit tests I wrote for #4 to cover this exact special case for each spline type, But there was a flaw in my thinking, so it was setting up scenarios where a and b weren't actually in the same segment, and so the test passed without ever identifying this problem.
So I fixed this problem and modified the test to make sure it's actually testing this special case.

Out of curiosity, what use case are you using the library for?

Thanks for quick response, I appreciate that! I'm trying to build a simulation for some medical research, and the spline is modelling an elastic probe defined by several points that are entered manually. In fact I need the equidistant split of the spline, so I wrote a (dumb) solver for the spline.arcLength(t) == L equation. BTW, I did some googling and there's quite some demand for this feature, may be you could add it to your lib? I'd be happy to do it myself, if only I was good enough at math... :)

Create a new issue for it and I'll look into it. What would the API look like?


Best first search error when the number of phase < max_search

Ideally, we probably want to always search single phase model (because these are more likely be the right model in real cases). In current bestfirstsearch implementation, the initialized search_node vector has the wrong size, which later causes the error.

Fixed in latest commit.


spacy-llm custom task configuration

Hi,
Is a more detailed explanation of the custom task configuration in the works? The current documentation is a bit too generic and unclear, and the NoOp file isn't very informative. Any assistance would be greatly appreciated! I'm excited about using this library for other tasks; it fits perfectly with other NLP tasks that don't rely on large language models. Thank you for any help you can provide!

Hi! Yes, you're right, we need to document this better.
Currently, the best explanation is over at https://github.com/explosion/spacy-llm/tree/main/usage_examples#writing-your-own-task.
Any thoughts on what would be helpful to add to this? Are there particular bits you're stuck on? Does it help looking at the built in tasks we have over at https://github.com/explosion/spacy-llm/tree/main/spacy_llm/tasks? I can imagine that the class inheritance makes it a bit difficult to follow, so maybe we should work on a fully written-out, self-contained example. The recently introduced sharding functionality also makes this slightly more complicated.

I'm stuck on multiple points, I get a few sharding configuration errors and a bit of problems in configuring the prompt for few-shot tasks. I could do it with other LLM wrappers but I really enjoy the structured doc output so it can seamlessly go the llm-rel task. The task I'm interested is entity typing, i.e. given an entity, induce the class from the context
E.g. "Babylonia was an ancient Akkadian-speaking Semitic state and cultural region based in central-southern Mesopotamia (present-day Iraq)."
Output: {"entity": "Babilonia", "class":"state"}, {"entity": "Mesopotamia", "class":"region"}
or
Bājíquán is a Chinese martial art that features explosive, short-range power and is famous for its elbow strikes.
Output: {"entity": "Bājíquán ", "class":"martial art"}

In our test suite, we have a toy task implemented called "spacy.CountWithSharding.v1", you can find it here. Maybe you can use that as a "template" for now, while we work on the docs.
With respect to your entity typing task - can't you use Named Entity Recognition for this? spacy-llm has built-in tasks for NER as well as spancat - maybe that will already fulfill your needs for this particular use-case.

Hello! Thanks for your suggestion, I managed to use NER.v3 to also recognise classes by providing examples and to connect it to another spacy REL model by combining the pipelines.
I just have a question:
The template argument in the few-shot NER v3 configuration lets you add a different path for a jinja template. I created a 1:1 jinja template for the NER v3 task just by changing the text, but I always get an empty Entities array.
In the fewshot.cfg file I've wrote:
[components.llm.task]   @llm_tasks = "spacy.NER.v3"   labels = ["ENTITY", "CLASS"]   template = "./template-ent-classification.v3.jinja"
Is something wrong there? Thank for any help, it is much appreciated.

Thanks for writing back, happy to hear you got this working!


U/update gopls 0 9 0

Not READY

Are you planning to do something about keeping the settings file in sync also?

Got catch. I'll add a second command to generate a settings dict as well. I'll refactor this today to make it much more readable


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>chore(scripts): cover@#overwrite c8 --temp-directory build/tmp ava && c8 report -r lcov -o build/coverage --temp-directory build/tmp
chore(package): add main from template
docs(package): remove keyword null
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/*-test.mjs' as in template
chore(package): set $.ava.extensions='mjs' as in template
chore(package): remove unknown value for main ({{main}})

Coverage remained the same at 33.78% when pulling 7a0998d60779fa74a9be683675821d7495f58e80 on npm-template-sync-1 into 85b6e349fc954b979dfd8521885326424c7ec8c9 on master.

Coverage remained the same at 33.78% when pulling 7a0998d60779fa74a9be683675821d7495f58e80 on npm-template-sync-1 into 85b6e349fc954b979dfd8521885326424c7ec8c9 on master.


Update installation instructions for Windows in INSTALLING.md

Hi everyone,
This pull request adds Windows installation instructions to the Installing.MD file and fixes the markdown validation for the table.
Thank you.

This is great. Thanks!


No error accessing non-existent method on string with strictNullChecks on

TypeScript Version:  3.0.1

Search Terms: strictNullChecks, inferred any, no error, parameter, argument, implicit any, property does not exist
Code
function getString(required: {}): string {
  return '';
}

function functionThatReturnsAString() {
  const optional: {} | null = null;
  return getString(optional);
}

const s = functionThatReturnsAString(); // s is correctly inferred as 'string'
s.foo(); // no error?

Expected behavior:
Expected to get error Property 'foo' does not exist on type 'string' on the last line.
Actual behavior:
No error on the last line.
With all the strict settings on, there's a different error on the argument to the getString call, but that should not affect the return type of functionThatReturnsAString. The function could be in a completely separate part of the codebase. Inspecting that should not be required when trying to debug the s.foo() call.
Playground Link:  https://www.typescriptlang.org/play/#src=function getString(required%3A {}) {
  return ''%3B%0D%0A%7D%0D%0A%0D%0Afunction%20functionThatReturnsAString()%20%7B%0D%0A%20%20const%20optional%3A%20%7B%7D%20%7C%20null%20%3D%20null%3B%0D%0A%20%20return%20getString(optional)%3B%0D%0A%7D%0D%0A%0D%0Aconst%20s%20%3D%20functionThatReturnsAString()%3B%0D%0As.foo()%3B%0D%0A
Tested with all strict options on. (Note that Playground has been finnicky today.)
Related Issues:

I believe this is because of this line in checker.ts:
return produceDiagnostics || !args ? resolveErrorCall(node) : getCandidateForOverloadFailure(node, candidates, args, !!candidatesOutArray);
If produceDiagnostics is true, we just return anySignature (from resolveErrorCall) and don't get downstream errors. But if not, we get the best candidate we can (which happens to be the only one). Maybe we could just always getCandiateForOverloadFailure?

That PR didn't fix this, the line I pointed out still exists.

But I see error reported by running tsc as well as from language service so its fixed?

We get s: string, but there's no compile error when calling a method that doesn't exist on string -- because the diagnostics-producing TypeChecker has different behavior than the one used for services.

@sheetalkamat You probably don't have strictNullChecks enabled since getString(optional) should be an error.

Duplicate of #19686 .


Add AntiforgeryHttpClientFactory, reduce nuget dependencies and improve code quality

Changes

use of expression bodies
use new top-level statements and remove
enable ImplicitUsings
add IAntiforgeryHttpClientFactory/AntiforgeryHttpClientFactory
it just gets the authorized httpClient and adds the antiforgery token header
Replace of IdentityModel with System.Security.Claims and remove IdentityModel nuget package
replace foreach loops with linq
fix remaining warnings

Maybe you like (some of) the changes. I guess they could be usefull for the nuget package.

Thanks @Q-Sharp Looks great, I'll do some testing and release, thanks a million!
Greetings Damien

had to change the server header, all great.
Released 1.2.1,
Thanks @Q-Sharp Do you have a linked, twitter? will add you if you want to the publish info tweet, linkedIn post.
Greetings Damien

Always happy to help :)


Conda-forge package ?

Hi again @mcarans.
I was wondering if you would be interested making pytest-loguru available on conda-forge ? I can craft the recipe very quickly and tag you as maintainer if that interests you. Maintenance is completely automated, so very little additional effort needed. Let me know!

I'm not familiar with conda-forge. Is it possible to upload from Linux? Would the recipe be in GitHub Actions?

The process is entirely Azure CI-based, and the recipe outlines can be found here: https://github.com/conda-forge/staged-recipes#faq.
Once the recipe PR is merged, a new repo will be created with you as a maintainer. When new versions are published on PyPI, automation will open a PR to update the recipe based on the new version available. No manual package uploading necessary.
Putting together a recipe for pytest-loguru would be very fast/easy. If this interests you, I can draft something up.

OK sure, please go ahead.

See: https://github.com/conda-forge/staged-recipes/pull/18673

@Zeitsperre Thanks for the PR and conda recipe. Please let me know all is good and then I'l lclose this issue (or you can).

Everything is good to be closed. Thanks again!


Windows build always fails with failed to find symbols

The tail of my Run cargo-dist step in the cargo-dist-generated release.yml  always looks like this:
   Compiling foo v0.1.3 (D:\a\foo\foo)
    Finished dist [optimized] target(s) in 2m 23s
dist ran successfully
{"error": {"message": "failed to find symbols glyphana for glyphana 0.1.3 (path+file:///D:/a/foo/foo)","severity": "error","causes": [],"labels": [],"related": []}}
jq: error (at <stdin>:1): Cannot iterate over null (null)
uploading...
requires at least 2 arg(s), only received 1
uploaded!
Error: Process completed with exit code 1.

I found this error in the source code of cargo-dist.  Any pointers how to fix this?

Hmm weird, can you link the task run/repo? The error looks like it wanted the .pdb for your project but couldn't find it...

I think this might be your problem: https://github.com/axodotdev/cargo-dist/issues/122#issuecomment-1428614186

I think this might be your problem: https://github.com/axodotdev/cargo-dist/issues/122#issuecomment-1428614186
Cheers!

I do indeed have:
[profile.release]
strip = true

[profile.dist]
inherits = "release"

But if I remove this my release binary is considerably larger. I don't want any unneeded symbols in there. What's the solution?

the next release disables pdb support pending a rework in #136


Save changes when closing menu

This PR adds auto-saving of changes when the quick menu is closed. The implementation is very naive. It accepts any changes, and grabs the text after the first space in each line. No validations included.
I also added a .editorconfig and the dev reloader you helped me with.

I'll merge, just answer questions


Exact Matches

Suggestion
In SKOS mapping properties, exact matches are transitive, where x = y and y = z then x = z. Therefore, I highly recommend limiting terms borrowed from other standards (e.g. schema:name) to exact matches. Currently, the openDS model uses borrowed terms with a broader scope in the source vocabulary such as schema:name.  If the mappings are narrower or broader, and therefore not transitive, then a minting a new term is highly recommended.

can we not describe the mapping scope as broader or narrower instead?

Unfortunately not. The issue is the transitive property. I think you should include the mappings, but it doesn't mitigate the issue of borrowing terms that are not exact matches. Here's a better way of representing it:
x = y and y = z then x must equal z.
Including the mappings doesn't make this statement true.

Hi Ben, thanks for putting forth this point.
To borrow or not to borrow has been a topic I tried to wrap my head around for a while.
If you have any references explaining what the specific rules are, I would definitely be interested.
What we decided for within openDS is to generally stick with relatively open, reusable term lists such as the TDWG term lists, schema.org and dcterms.
As these term list are not full-fledged ontologies, they don't enforce a specific structure but are aimed at reusability.
The term schema:name is a good example.
The definition for this term is: "The name of the item" with as datatype: "Text".
We include the term in for example the ods:SourceSystem to give the source system a name.
To me, this falls in line with what the term is intended to as we name the item (in this case ods:SourceSystem).
As schema.org does not restrict the classes on which you can use, the term is safe to reuse in an openDS defined class.
Reusing terms where possible/sensible is also in line with how we interpret Semantic Data and Linked Open Data.
By using the globally used term for naming an item, we connect with the broader semantic language of the web.
This way, we only need to create new terms for domain or even infrastructure specific information.
I believe this is also in line with how TDWG reuses for example dcterms terms in DarwinCore or Audiovisual Core and other projects such as https://oceaninfohub.org/ use schema.org (who actually gave us feedback that we didn't use enough schema.org).
Do you feel we misinterpret how we should use existing term lists?
Any suggestions in how we could improve the use of existing terms is always welcome.


Updated one note in the documentation

How to add a machine for deployment. This detail was missing

Docs Build status updates of commit 1733c45:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/feature-pack-create-vsts-token.md
:bulb:Suggestion
View
Details

biztalk/core/feature-pack-create-vsts-token.md

Line 21, Column 21: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/vsts/accounts/use-personal-access-tokens-to-authenticate' will be broken in isolated environments. Replace with a relative link.
Line 69, Column 300: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/vsts/build-release/concepts/definitions/release/deployment-groups/index' will be broken in isolated environments. Replace with a relative link.
Line 116, Column 36: [Suggestion-docs-link-absolute] Absolute link 'https://docs.microsoft.com/vsts/build-release/actions/agents/v2-windows' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit cd64a74:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/feature-pack-create-vsts-token.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5759fe6:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/feature-pack-create-vsts-token.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


[Toolplate] -> [HTML & CSS Templates]

Toolplate
Toolplate is a free collection of HTML/CSS templates place.
Link: https://www.tooplate.com/
Checklist:

[x ] I have performed a self-review of submitted resource and its follows the guidelines of the project.

#370


bug(mat-tooltip): tooltip shows up even if the trigger was left before the show delay

Is this a regression?

[x] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
12.2.13
Description
When matTooltipShowDelay is used and mouse entered and left the trigger element, the tooltip will still briefly show up after the delay time.
Reproduction
Steps to reproduce:

open tooltip example StackBlitz (https://material.angular.io/components/tooltip/examples#tooltip-delay): https://stackblitz.com/run?file=src%2Fapp%2Ftooltip-delay-example.ts
enter and leave the Action button with your mouse
wait till the delay expires
see the tooltip blink in and out of existence

Expected Behavior
If the mouse leaves the trigger before the enter animation starts (before the show delay) then the tooltip will not show at all.
Actual Behavior
The tooltip will show briefly after the delay even if the mouse entered the trigger and left immediately.
Environment

Angular: 14.0.0
CDK/Material: 14.0.5
Browser(s): Chrome 103.0.5060.114
Operating System (e.g. Windows, macOS, Ubuntu): Windows 10 Business Version 21H2 OS build 19044.1826 x64

Duplicate of https://github.com/angular/components/issues/24614.


Add relevant academic / literature citations

Ground work in academic / literature discussion.  In the "Rationale" section

Complete in outFormatSelect branch https://github.com/DanNBullock/citeas-on-requirements/commit/ea21ec4292c121436d6ab8aae8fb077dc15c5667


open a modal from the code

Hi,
i want to open the modal when certin condition on the code,
so i have the openModal as in the example code
   openModal() {     this.modalActions.emit({action:"modal",params:['open']});   }
if i bind it to a button , the model do open , if i call it within a code it dose not
is there any way to do so ?

The following works for me. It's from the code, and not as a result of event. Is that what you're trying to do?
constructor() {
    window.setTimeout(()=>{
      console.log("here");
      this.modalActions1.emit({action:"modal",params:['open']});
    },3000);
  }

seems the problem is related the the phaser library , that i am trying to open the model from its method


Duplication scene.

Version
Tell us which versions you are using:

react-native-router-flux 4.0.0-beta.28
react v 16.2.0
react-native v 0.53.3

Expected behaviour
Create one scene.
Actual behaviour
Create two scene.
Steps to reproduce
The source code is as follows.
<Provider store={createStore(reducers)}>
        <Router>
          <Scene key="root" hideNavBar>
            <Scene key="registInit" component={RegistInit} initial />

           <Scene key="sceneHistory" component={RemitHistory} />

            <Drawer contentComponent={SideMenuMain} panHandlers={null}>
              <Scene key="mainonly" hideNavBar>
                <Scene key="sceneRemit" component={Remit} initial />
              </Scene>
            </Drawer>

          </Scene>
        </Router>

Current Situation
When I go from the first scene 'registInit' to 'sceneRemit', two instances of sceneRemit are made.
If I put Alert popup in componentDidMount, two popups appears repeatedly. So, the instances are real.
Of course, I can 'pop' the 2nd scene, but it makes uncanny animation.
Workaround and side effect
If I remove scene 'mainonly', only one instance is generated, but  popTo('sceneRemit') doesn't work.
From registInit > sceneRemit > sceneHistory >> popTo('sceneRemit')  this doesn't work.
Am I using Drawer or Scenes incorrectly?
How can I use these scenes with or without Drawer ?

+1

It is not a bug, but feature - first scene is already part of the stack. So you name of stack/drawer, not name of first scene


Symptom Log Calendar

Why
We'd like users to be able to view their longer-term (4 week) symptom log/checkin history in the form of a calenday
This Commit
This commit implements a calendar view containing a 4-week window of the user's checkins. Because data older than 14 days is deleted from the device, dates prior to 14 days from the current date are disabled in the calendar.

Also, lets not merge this this week so that we can cut a release candidate build with just the symptom checker


Linux.zip: lxc execution problem

Required information

Distribution: RedHat Linux
Distribution version: CentOS Linux release 8.3.2011
The output of "lxc info" or if that fails:

Kernel version: uname -r: 4.18.0-240.22.1.el8_3.x86_64
LXC version: ? (lxc info fails too, see below)
LXD version: Server version: 4.14
Storage backend in use: ZFS

Issue description
I have downloaded latest "Client build and unit tests" Linux.zip artifact from https://github.com/lxc/lxd/actions/runs/903979689
Unpacked, chmod 755 lxc pxd-p2c and getting this error:
./lxc version
panic: list flag redefined: format

goroutine 1 [running]:
github.com/spf13/pflag.(*FlagSet).AddFlag(0xc00030ca00, 0xc000306e60)
        /home/runner/go/pkg/mod/github.com/spf13/pflag@v1.0.5/flag.go:848 +0x825
github.com/spf13/pflag.(*FlagSet).VarPF(0xc00030ca00, 0xd4a200, 0xc0001a6c98, 0xc4c1a4, 0x6, 0xc49b49, 0x1, 0xc0002eeea0, 0x1e, 0x1e)
        /home/runner/go/pkg/mod/github.com/spf13/pflag@v1.0.5/flag.go:831 +0x10b
github.com/spf13/pflag.(*FlagSet).VarP(...)
        /home/runner/go/pkg/mod/github.com/spf13/pflag@v1.0.5/flag.go:837
* github.com/spf13/pflag.(*FlagSet).StringVarP(0xc00030ca00, 0xc0001a6c98, 0xc4c1a4, 0x6, 0xc49b49, 0x1, 0xc4b67e, 0x5, 0xc0002eeea0, 0x1e)
        /home/runner/go/pkg/mod/github.com/spf13/pflag@v1.0.5/string.go:42 +0xad
main.(*cmdStorageVolumeList).Command(0xc0001a6c80, 0xc0001a6c80)
        /home/runner/work/lxd/lxd/lxc/storage_volume.go:1092 +0x405
main.(*cmdStorageVolume).Command(0xc0002f6d60, 0xc0002f6d60)
        /home/runner/work/lxd/lxd/lxc/storage_volume.go:81 +0x5c6
main.(*cmdStorage).Command(0xc000280ee0, 0xc000280ee0)
        /home/runner/work/lxd/lxd/lxc/storage.go:74 +0x532
main.main()
        /home/runner/work/lxd/lxd/lxc/main.go:198 +0x166c

Steps to reproduce

See above.
Version 4.13 is last one worked properly (after download from github).

Information to attach

lxd-p2c utility, from same Linux.zip, outputs version correctly

Regards.

I just tried this locally from the same link as above and ./lxc version works fine.
Also the stack trace doesn't look right, the part:
main.(*cmdStorageVolumeList).Command(0xc0001a6c80, 0xc0001a6c80)
        /home/runner/work/lxd/lxd/lxc/storage_volume.go:1092 +0x405

doesn't match up with what is in the code base:
Line 1092 is empty: https://github.com/lxc/lxd/blob/master/lxc/storage_volume.go#L1092
And cmdStorageVolumeList doesn't start until line 1158: https://github.com/lxc/lxd/blob/master/lxc/storage_volume.go#L1158
Are you certain you're running the copy you think you are?

Hi @tomponline,
I have downloaded same zip file a month ago and utilities are in use on my linux system (was one requirement for packer utility -- https://www.packer.io):
:; ls -al /home/predrag_zecevic/bin/lx*
-rwxr-xr-x. 1 predrag_zecevic support 19290419 May  6 00:27 /home/predrag_zecevic/bin/lxc
-rwxr-xr-x. 1 predrag_zecevic support 16473813 May  6 00:27 /home/predrag_zecevic/bin/lxd-p2c

:; /home/predrag_zecevic/bin/lxc version
Client version: 4.13
Server version: unreachable

:; /home/predrag_zecevic/bin/lxd-p2c --version
4.13

This morning I have tried to use newer versions, and thus get into trouble with lxc functionality. Nothing else was changed on system.
Regards.

@3eka I just tried the Linux.zip file from https://github.com/lxc/lxd/actions/runs/903979689 inside a brand new centos 7 VM and it works fine:
lxc file push /home/user/Downloads/Linux.zip vcentos7/root/
user@user-MS-7821:~/go/src/github.com/lxc/go-lxc$ lxc shell vcentos7
[root@vcentos7 ~]# yum install unzip
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.cwcs.co.uk
 * centosplus: mirror.as29550.net
 * extras: mirror.freethought-internet.co.uk
 * updates: mirror.as29550.net
Resolving Dependencies
--> Running transaction check
---> Package unzip.x86_64 0:6.0-21.el7 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

============================================================================================================================================
 Package                         Arch                             Version                              Repository                      Size
============================================================================================================================================
Installing:
 unzip                           x86_64                           6.0-21.el7                           base                           171 k

Transaction Summary
============================================================================================================================================
Install  1 Package

Total download size: 171 k
Installed size: 365 k
Is this ok [y/d/N]: y
Downloading packages:
unzip-6.0-21.el7.x86_64.rpm                                                                                | 171 kB  00:00:00
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
  Installing : unzip-6.0-21.el7.x86_64                                                                                1/1
  Verifying  : unzip-6.0-21.el7.x86_64                                                                                1/1

Installed:
  unzip.x86_64 0:6.0-21.el7

Complete!
[root@vcentos7 ~]# unzip Linux.zip
Archive:  Linux.zip
  inflating: lxc
  inflating: lxd-p2c
[root@vcentos7 ~]# ls
Linux.zip  lxc  lxd-p2c
[root@vcentos7 ~]# chmod +x lxc
[root@vcentos7 ~]# ./lxc version
Client version: 4.14
Server version: unreachable

Can you try it inside a VM or different machine too please. Also what OS and version are you running?

Hi @tomponline,
hmm, thanks for checking (It might be that my VM -- lxd container, CentOS 8 x86_64 -- is somehow broken).
I will try it on CentOS 8, VirtualBox VM (fully virtualized) and will paste result here soon.
Regards.

Sorry everybody for noise.
Seems that everything is fine:
:; ./lxc --version
4.14
:; ./lxd-p2c --version
4.14

I will re-install my VM.
Thanks and best regards.


Support of the None for the String type

Coverage increased (+0.2%) to 99.778% when pulling d74613b6ee27429c0080cc06a499802602b2eac6 on nullabletype into 105669e13fcdcdf9aaa765b00f1aad1a840a8e60 on master.


Add authorization tokens for API access

For documentation, see https://github.com/ava-labs/docs/pull/75

Generally not a best practice to show a password in plaintext
Multiple passwords could potentially get confusing to some users
Different password strength tests for the different passwords

Authorization token password

Not strength checked

User keystore passwords

Strength checked

If a user calls auth.changePassword and then restarts their node then the password reverts to the original flag password and all the issued tokens under the new password are revoked

@cgcardona
Generally not a best practice to show a password in plaintext
Fixed in latest commit
Multiple passwords could potentially get confusing to some users
Yeah, I'm not really sure how to deal with this...I'm not sure how else to do this other than to have a password (or some other secret) known only by the node operator. I agree it could be confusing to have another password protected thing besides the keystore.
Different password strength tests for the different passwords
Good point. Will add a commit for this, too.
If a user calls auth.changePassword and then restarts their node then the password reverts to the original flag password and all the issued tokens under the new password are revoked
I think this is OK for now but not ideal

@cgcardona Added password strength checking


[DOCS] Add Contributor over time in README.md

Why are the changes needed?

Add Contributor over time in README.md
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[x] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

late lgtm


CHANGE Get-ADGroupReport to show member count

Get-ADGroupReport should show a member count in the default display. Alert on 0 members in the formatting.

Fixed in v1.0.0 (6456fc4)