Rc

Adding Microsoft Azure AD authentication.  #746
 authentmake test failures:
...
=== RUN   TestAuthProviderConfigSetupProvider
--- PASS: TestAuthProviderConfigSetupProvider (0.00s)
FAIL
coverage: 76.4% of statements
FAIL    github.com/pocketbase/pocketbase/core   0.043s
...
=== RUN   TestPointer
--- PASS: TestPointer (0.00s)
PASS
coverage: 97.5% of statements
ok      github.com/pocketbase/pocketbase/tools/types    0.002s  coverage: 97.5% of statements
?       github.com/pocketbase/pocketbase/ui     [no test files]
FAIL
make: *** [Makefile:5: test] Error 1

Changed the microsoftAuth names to azureAuth.
Also reordered the expected result in core/settings_test.go - TestNamedAuthProviderConfigs. Now the test failures from make test, mentioned in earlier, are gone.

@WouterVandeWiele Thank you. I've merged and squashed the PR locally in https://github.com/pocketbase/pocketbase/commit/5298543ce486b0e4fe53dc1fc9a38b02313e22c5.
At the end, I've decided to keep the provider name "Microsoft" for simplicity. Other than "Windows's Live ID" I couldn't find any other OAuth2 services (and it seems that it is a legacy as far as I understand reading https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/cleaning-up-the-azuread-and-microsoft-account-overlap/ba-p/245105 and other related resources). Additionally Microsoft Azure AD seems to support both cases - Microsoft personal accounts as well as Azure Active Directory accounts (Firebase also seems to use only "Microsoft" as label in their UI and documentations https://firebase.google.com/docs/auth/android/microsoft-oauth).
I've also decided to add support for custom provider components loaded through the provider.js config file, which should result in better UX since now we can show specialized help-blocks or hide unnecessary fields (eg. the user api endpoint for the microsoft provider).
I've tested the integration with a developer account and it seems to work fine. If you stumble on something or don't agree with the changes, feel free to let me know I'll revisit them.

I concur on the naming.
The optionsComponent is also a great addition. 👍
It's more customizable then the old way while keeping a clean interface IMHO.
Great work, thanks for adding the feature.


Add Ubuntu Artful section to build instructions

Build instructions for Ubuntu Xenial didn't work for me and needed an extra parameter. Added a section to the README.

(fixes issue #2544)

Thanks @DestyNova !


Notes Preview on Warrants Broken

What version of Node.js are you using?
18.17.1
What operating system are you using?
Linux
What version of SnailyCAD are you currently using?
v1.74.0
Describe the Bug
When looking at warrants on a character, the feature where you can put your mouse over the "Notes" section to see it displayed in one page. Instead, a scroll bar is present, which is a very difficult way to read the text of the warrant.

To Reproduce
No response

Same occurs with Notes on a character.


Add link to Google oss doc

Add this link
to 2017-10-04-github-oss-f17.md

Here: https://github.com/thehackerwithin/berkeley/blob/master/docs/_posts/2017-10-04-github-oss-f17.md


[Feature] Show Language Statistics

Gitea version (or commit ref): 1.15.0+dev-341-gb4d10598c
Can you reproduce the bug at https://try.gitea.io:

Yes

Description
It would be nice if there was a display of the percentage of languages used somewhere in the repo. Might even be inside the activity tab.
Later on, it would be even better, if these percentages were clickable to show only the files programmed in the given language, just like GitHub.
Screenshots

Language Statistics Appearance on GitHub

Did you mean

This has been implemented. But the filter via language is not.

Oh. I see. It's slightly hidden. I'll adapt the issue to only use the second part.


RFC: Mac kext virtualization root unit tests

This is based on top of @jeschu1 's PR #732 #802.
In my hunt for the source of #797, it seemed sensible to create unit tests for the functions likely to be the cause.
Those functions, VirtualizationRoot_RegisterProviderForPath, ActiveProvider_Disconnect, and FindRootAtVnode_Locked call out to a lot of functions including kernel APIs, so getting tests to build and run has required a fair bit of infrastructure work.
Specifically, this sequence of commits adds:

Basic mocking of vnodes and mount points.
Stub implementations for some memory allocation and lock functions. (These could get a lot fancier.)
Function call recording so we can verify that a mock function was or wasn't called by a test. (This currently does not support checking call order or argument values, but is in principle designed to be extended that way.)
100% test coverage of VirtualizationRoot_RegisterProviderForPath
Test coverage recording. In Xcode, test coverage is shown for each code block on the right side of the editor window.

Still missing: tests for ActiveProvider_Disconnect and infrastructure required to get them working.
The tests found a few bugs, they weren't the cause for #797 though, and they only kick in when you hit 32768 virtualisation roots in the system. There's lots of useful testing infrastructure there though that made this a worthwhile effort.
Reviewer notes: This is a pretty large PR; for now I'm mostly interested in what you think of the general approach, rather than picking it apart line-by line.

Can you refresh my memory on why we need both KEXT_UNIT_TESTING and TESTABLE_KEXT_TARGET?

@pmj I really like the approach!  I'm going thru the code now and asking any questions I have.

Can you refresh my memory on why we need both KEXT_UNIT_TESTING and TESTABLE_KEXT_TARGET?

In the unit test build target, we're using "normal" user space system headers. In the "PrjFSKextTestable" build target, we're using kernel headers so that the kext code compiles without modification. Both targets define KEXT_UNIT_TESTING, but we do sometimes need to know which one is the one currently being compiled, mostly so we can work around compile errors in system headers, such as in the vnode.h and mount.h wrappers.

@wilbaker I was able to extend this framework pretty easily for testing TryGetFileIsFlaggedAsInRoot.
POC here https://github.com/pmj/VFSForGit/pull/1/files

I think this is a phenomenal start!

Thanks!

I'm sure as we get more test coverage we'll make changes over time.
Please also wait for @wilbaker's approval before merging

I've been going through and incorporating feedback; I'm planning to complete that later this evening and push a new version of the PR so feel free to await that before approving.

I'm planning to complete that later this evening

I'm not quite done with this just yet, I'll try and get this done ASAP though.

I've just pushed an overhauled version of this PR without making any significant changes to the overall functionality to avoid overloading this PR. I'm hoping we can merge this soonish and make major improvements in future PRs. Please re-review at least briefly! Thanks.


Test data generation doesn't work with file formats count pie chart

The data generation tool's data doesn't work with the file formats count pie chart because there are too few common values for there to be clusters of the same value to count.

Fix merged.


ForkChoiceTest.onBlock_shouldNotProcessAttestationsForBlocksThatDoNotYetExist fails intermittently

Description
The test ForkChoiceTest.onBlock_shouldNotProcessAttestationsForBlocksThatDoNotYetExist failed on one run and then passed after just CI task restart
Additional Information
Stacktrace:
java.lang.IllegalStateException: Failed to create attestation for block 0xe22e97a922f8c534348cf141e997b5fd0257f2bb0120dec7c74be72413493fd0
genesis root: 0x6746e70ca3650fde87a039db48f9d1ff3877798112e2bd940f8987e2f76c9331
chain head: 0x333b17c60375387b3717ad7f28af2dce295427e00bb0535414dc1e9124ff5d94
validators: 0xa99a76ed7796f7be22d5b7e85deeb7c5677e88e511e0b337618f8c4eb61349b4bf2d153f649f7b53359fe8b94a38e44c, 0xb89bebc699769726a318c8e9971bd3171297c61aea4a6578a7a4f94b547dcba5bac16a89108b6b6a1fe3695d1a874a0b, 0xa3a32b0f8b4ddb83f1a0a853d81dd725dfe577d4f4c3db8ece52ce2b026eca84815c1a7e8e92a4de3d755733bf7e4a9b
	at tech.pegasys.teku.statetransition.forkchoice.ForkChoiceTest.lambda$onBlock_shouldNotProcessAttestationsForBlocksThatDoNotYetExist$2(ForkChoiceTest.java:183)
	at java.base/java.util.Optional.orElseThrow(Optional.java:408)
	at tech.pegasys.teku.statetransition.forkchoice.ForkChoiceTest.onBlock_shouldNotProcessAttestationsForBlocksThatDoNotYetExist(ForkChoiceTest.java:170)

I'm struggling to understand why this is failing intermittently.  It's trying to create an attestation and comparing the values in this error to what I get running locally (when it passes) all the values match.  So we're trying to create an attestation for the same block, with the same genesis, same validators and building on the same chain head but somehow we intermittently can't create a valid attestation.
There shouldn't be any other source of randomness...


scan_interval_seconds dont work?

Hi, i tried to use the edl21 integration.
i have create a folder named "edl21" over the HA UI (File Editor) into "custom_components" an copy the 3 files into this folder.
Then i have configured the configuration.yaml as follow:
######################################
############### EDL21 ################
sensor:
  - platform: edl21
    name: "Heizstrom"
    serial_port: socket://<IP_ADDRESS>:1234
    scan_interval_seconds: 15

but after restart home assistant, the updates comes in every 60 oder 90 seconds.
Please help me to find my mistake.

Follow these steps and it should work:

Uninstall the official edl21 integration
Restart Homeassistant
Add this custom integration
Add the configuration for example:sensor:
  - platform: edl21
    serial_port: /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_D306NKQQ-if00-port0
    scan_interval_seconds: 5

Restart Homeassistant
Check if it works or logs for errors

Hi, thanks, i try.
first i uninstall all integration, then i will step by step 1-6.

Uninstall the official edl21 integration mean i delete all my installed eHZ Devices right?

Ok, points 1-6 done.
Nothing has changed, updates still only come every 60 to 90 seconds.
Uninstall the official edl21 integration
-> OK, all devices deleted so that the integration is no longer displayed.
Restart Home Assistant
-> OK
Add this custom integration
-> OK, folder edl21 created and the three files copied into it.
Add the configuration for example:
-> OK, see above
Restart Home Assistant
-> OK
Check if it works or logs for errors
-> Data is read out every 60-90 seconds, not every 15 seconds
I don't know what I'm doing wrong.

OK, how do you say it in Germany? Once with professionals...
I'm currently in the process of moving everything from IO Broker to Home Assist and I forgot to deactivate the smart meter plugin in IO Broker.
Thanks for your help.

Done.

done


Service Bus: Added new cmdlet for Migration and added few properties

Change log:

Added New cmdlets for Service Bus Standard to Premium namespace:
'az servicebus migration start', 'az servicebus migration show', 'az servicebus migration complete', 'az servicebus migration stop',
'az servicebus migration delete'

Added new optional properties to Service Bus queue and Subscription

enable_batched_operations and dead_lettering_on_filter_evaluation_exceptions in queue
dead_lettering_on_filter_evaluation_exceptions in subscriptions

This checklist is used to make sure that common guidelines for a pull request are followed.

[X] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[X] I adhere to the Command Guidelines.

@williexu have resolved the review comments.

@williexu updated history.rst and CI passed.


datasets-cli test should work with datasets without scripts

It would be really useful to be able to run datasets-cli testfor datasets that don't have scripts attached  to them (whether the datasets are private or not).
I wasn't able to run the script for a private test dataset that I had created on the hub (https://huggingface.co/datasets/huggingface/DataMeasurementsTest/tree/main) -- although @lhoestq came to save the day!

It would be really useful to be able to run datasets-cli testfor datasets that don't have scripts attached to them (whether the datasets are private or not).
I wasn't able to run the script for a private test dataset that I had created on the hub (https://huggingface.co/datasets/huggingface/DataMeasurementsTest/tree/main) -- although @lhoestq came to save the day!

why don't you try to share that info with people, so you can also save some days.

Hi ! You can run the command if you download the repository
git clone https://huggingface.co/datasets/huggingface/DataMeasurementsTest

and run the command
datasets-cli test DataMeasurementsTest/DataMeasurementsTest.py

(though on my side it doesn't manage to download the data since the dataset is private ^^)

Hi ! You can run the command if you download the repository
git clone https://huggingface.co/datasets/huggingface/DataMeasurementsTest

and run the command
datasets-cli test DataMeasurementsTest/DataMeasurementsTest.py

(though on my side it doesn't manage to download the data since the dataset is private ^^)

Hi! Thanks for the info.
git cannot find the repository. Do you know if they have depreciated these tests and created a new one?

I think it's become private, but feel free to try with any other dataset like lhoestq/test for example at https://huggingface.co/datasets/lhoestq/test

I think it's become private, but feel free to try with any other dataset like lhoestq/test for example at https://huggingface.co/datasets/lhoestq/test

your example repo and this page ['https://huggingface.co/docs/datasets/add_dataset.html'] helped me to solve.. thanks a lot


Remington Orange Chat Test 2

I've added 3 responses from ChatGPT and would like my work to be reviewed. Thanks!

@Remdog712 your pull request is seen! Well find. We shall review on Friday. :-)


The yazi-fm crate can't be published to crates.io

Please describe the problem you're trying to solve
In the just released Yazi 0.3, we used an unpublished commit from notify-rs to fix a serious crash issue on Windows.
Unfortunately, this prevents Yazi from being published on crates.io, as crates.io requires that dependencies cannot be specified using a commit.
When I attempted to publish the yazi-fm crate, I got the following error:
❯ cargo publish -p yazi-core
    Updating crates.io index
error: all dependencies must have a version specified when publishing.
dependency `notify` does not specify a version
Note: The published dependency will use the version from crates.io,
the `git` specification will be removed from the dependency declaration.

This indicates that yazi-core cannot be published, which in turn prevents yazi-fm from being published since yazi-core is a required dependency.
This situation will persist until notify releases a new version with the fix (tracked by https://github.com/notify-rs/notify/issues/624). Please use other package managers to install Yazi for now, or wait until the issue is resolved.
Would you be willing to contribute this feature?

[ ] Yes, I'll give it a shot

Describe the solution you'd like
.
Additional context
No response

For anyone else using cargo, installing from git still works.
cargo install --locked --git https://github.com/sxyazi/yazi.git yazi-fm yazi-cli

For anyone else using cargo, installing from git still works.
cargo install --locked --git https://github.com/sxyazi/yazi.git yazi-fm yazi-cli

Pretty sure you don't need the yazi-fm yazi-cli part now: https://github.com/sxyazi/yazi/blob/3fdbbfe915717f2ddd0ba891b4d19354e3136ff9/Cargo.toml#L4.


SVG cannot be added

Hello,
My bug looks similar to 2157 : I'm trying to add an SVG to the PDF but the output is a blank page.
When I try to load the same SVG as an image, it works well :
<!doctype html>
<html>
	<head>
		<script src="https://cdnjs.cloudflare.com/ajax/libs/jspdf/1.5.3/jspdf.debug.js" integrity="sha384-NaWTHo/8YCBYJ59830LTz/P4aQZK1sS0SneOgAvhsIl3zBu8r9RevNg5lHCHAuQ/" crossorigin="anonymous"></script>
		<script type="text/javascript">
			function svgToImg(svg) {
				return new Promise(resolve => {
					var png = new Image();
					var DOMURL = self.URL || self.webkitURL || self;
					var img = new Image();
					var svgBlob = new Blob([svg.outerHTML], {type: "image/svg+xml;charset=utf-8"});
					var url = DOMURL.createObjectURL(svgBlob);

					img.onload = function() {
						var canvas = document.createElement("canvas");
						canvas.setAttribute("width", img.width);
						canvas.setAttribute("height", img.height);
						var ctx = canvas.getContext("2d");
						ctx.drawImage(img, 0, 0, img.width, img.height);
						var pngSrc = canvas.toDataURL("image/png");
						png.src = pngSrc;
						DOMURL.revokeObjectURL(pngSrc);

						resolve(png);
					};
					img.src = url;
				});
			}
			async function generatePDF() {
				var png = await svgToImg(document.querySelector("svg"));
				var pdf = new jsPDF();
				pdf.addSvg(document.querySelector('svg').outerHTML, 0, 0);
				pdf.addPage();
				pdf.addImage(png.src, 'png', 0, 0);
				pdf.save("svg.pdf");
			}
		</script>
	</head>
	<body onload="generatePDF()">
<svg width="62pt" height="44pt" viewBox="0.00 0.00 62.00 44.00" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink">
<g id="graph1" class="graph" transform="scale(1 1) rotate(0) translate(4 40)">
<title>G</title>
<polygon fill="white" stroke="white" points="-4,5 -4,-40 59,-40 59,5 -4,5"></polygon>
<!-- a -->
<g id="node1" class="node"><title>a</title>
<ellipse fill="none" stroke="black" cx="27" cy="-18" rx="27" ry="18"></ellipse>
<text text-anchor="middle" x="27" y="-13.8" font-family="Times,serif" font-size="14.00">a</text>
</g>
</g>
</svg>
	</body>
</html>

Having the addSvg() method working would be really appreciated since SVG contains text that can be searched, copied and pasted contrary to an image, and it would be great in a PDF file.

same problem here, no ouput, no error in console

The addSvg method supports only a very very small subset of the SVG specification. I recommend using either svg2pdf or canvg together with jsPDF.canvas/context2d. We should probably either mark addSvg as deprecated or make it use canvg like addSvgAsImage.

thank you very much, yes please update addSvg or just remove it. Currently this is very confusing.

Please do not close inactive open issues. This is very bad practise. Thank you.

I partly agree. For this repository, it makes sense, though, because there are many old and stale issues and the maintainers of the repository (currently mainly me) don't have time to look through all of them. By notifying the authors and closing them automatically, we can quickly decide which issues are still relevant.

ok, I understand. I consider this issue very relevant until it is solved :-)


chore: Update from _rust template

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
0

Relevant Lines:
13

💛  - Coveralls


Enhancement/houdini add path action for abc validator

Changelog Description
Add a default path attribute Action.
it's a helper action more than a repair action, which used to add a default single value.
Additional info
This validator is going to be skipped if the sop_path in the ROP doesn't point to a SopNode after merging this PR
otherwise the publisher will error
Testing notes:
use pointcache to export these examples, set the sop path explicitly

test 1 : create AUTO_PATH node before null node
test 2 : create AUTO_PATH node before output node
test 3 : create AUTO_PATH node after sphere node and set it as output node and update ROP node
test 4 :  create AUTO_PATH node after merge node and set it as output node and update ROP node
test 5 :  create AUTO_PATH node after copy node and set it as output node and update ROP node
test 6 : set sop_path explicitly to the parent geo node  of these nodes in screenshot, publish will crash
test 6 : after merging the mentioned PR, publisher will only show Validate Output Node error

We need to give it a test with another user, but looking great. We can merge it early next week.

@moonyuet
Could you give it a test  when you have time ?


npm install warning (...requires a peer of react... but none was installed)

I'm getting a warning when running npm install
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^0.14.0 || ^15.0.0 || ^16.0.0 but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^0.14.0 || ^15.0.0 || ^16.0.0 but none was installed.

I ran rm -rf node_modules and a clean npm install but I'm still seeing the warnings. Is anyone else experiencing this? Any ideas?
Mac OSX 10.11.6
npm version 4.6.1

I'm on MacOS 10.13.2 and I did not get this issue, but I used yarn install instead of npm install. Have you tried using that? You can easily install yarn using homebrew with the command brew install yarn.


Use appropriate dependency for handlebars template

When using metalsmith-layouts using the handlebars engine and with handlebars installed, I get this error:
Error: no files to process. See https://www.npmjs.com/package/metalsmith-layouts#no-files-to-process
    at Ware.<anonymous> (/Users/davidharting/repos/metalsmith-trial/node_modules/metalsmith-layouts/lib/index.js:141:7)
    at Ware.<anonymous> (/Users/davidharting/repos/metalsmith-trial/node_modules/wrap-fn/index.js:45:19)
    at Immediate.next (/Users/davidharting/repos/metalsmith-trial/node_modules/ware/lib/index.js:85:20)
    at Immediate._onImmediate (/Users/davidharting/repos/metalsmith-trial/node_modules/wrap-fn/index.js:121:18)
    at runCallback (timers.js:789:20)
    at tryOnImmediate (timers.js:751:5)
    at processImmediate [as _immediateCallback] (timers.js:722:5)

The metalsmith-layouts docs indicate that you should install jstransformer-handlebars instead of regular handlebars.
Installing jstransformer-handlebars solved my issue and I can build using handlebars layouts. I uninstalled handlebars and continue to have good builds.

Coverage remained the same at 96.875% when pulling 8602e43058de20ba48fea6f8c2e579a3a6279402 on davidharting:patch-1 into 8eacefcc58c00dd3a17e30184302b414e7cb14e2 on segmentio:master.

Closing in favor of https://github.com/segmentio/metalsmith/pull/320


settings API in MySQL

mock API is now migrated over to MySQL mostly except for the transports stuff (get_transports, set_transports), current DB schema needs slight modifications and a few other changes so the "real" API is conformant to behaviour of the mock API condenser has been working with as well as to spec.
This is an open task if anyone else has time to jump on it, otherwise I intend to work on it after wwwpoll

I've now made the schema changes and have this running with passing tests in MySQL.
See https://github.com/steemit/yo/pull/57

set_transports is in place now in branch yab-mark-returnval (apologies for non-sequitur sounding name, it started off as a quick fix on the return values from mark_* methods).
Closing


Removed glew fix from CI

A very simple PR, mostly to check that my corporate CLA is working fine.
This just removes a CI fix that was only necessary for packages that need glew on the VFX-2020 image, the fix is still needed for glew dependencies but I don't think OpenEXR requires glew?

No OpenEXR doesn’t require glew. I was working off of OCIO’s GHA files and wasn’t sure if that was for a dependency or something else so left it, meaning to ask later.

Thanks @xlietz ! All good I was looking for something small to enable my CLA :-)


Create a new customer.

Creating a new customer using the Spring JDBC metadata-driven insert client.
Adding helper constants: database table and column names for insert operations.
Adding a terminating part of an SQL query, used to retrieve the last record created.
Adding the Location response header with the URI of a newly created resource (customer profile).
Exposing the response body to make it more versatile to deal with.
Bumping version number to 0.1.9.

Ship it ! :+1: — Approved. :blue_heart:


Section regarding ways to format differences between addresses that are mapped and those that aren't

I'm not sure if it's possible, but it might be nice to show a way to handle when the address search simply doesn't work. For example working with dirty data it could be nice to conditionally format a table based on whether or not Bing Maps was able to find an address and plot it on the map. Quick at-a-glance way to see those which have issues if you do not have detailed data like longitude and latitude
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 735d805a-0981-4f84-12e7-b5560ea9c3bb
Version Independent ID: d5dce962-ecf1-014e-65d9-00121fdd6d3c
Content: Tips and Tricks for maps (including Bing Maps integration) - Power BI
Content Source: powerbi-docs/visuals/power-bi-map-tips-and-tricks.md
Service: powerbi
Sub-service: pbi-visuals
GitHub Login: @mihart
Microsoft Alias: mihart

Thanks for your comment, @jeremiah1119. This issue has been assigned to the doc author for review.

Thanks for your comment, @jeremiah1119 . This looks like a support request or product question rather than documentation feedback. You might find a solution in the Power BI Community, at https://community.powerbi.com. You may also be able to contact Support (refer to this article: https://docs.microsoft.com/en-us/power-bi/admin/service-support-options to review available Support options.)


Load chat template from GGUF file

As discussed in #326, we have support for loading the tokenizer from a GGUF file, but not the chat template. Currently using the tokenizer model ID or specifying a chat template file is necessary (see the example chat template files here). This feature will be helpful for loading a GGUF model from a GGUF file only.

Implemented in #416.


fix(python): mypy validation errors

Updated the type annotations of the jsii runtime for Python so that the
decorators carry appropriate type signatures. Additionally, enhanced
the code generation for Python so that mypy errors that are difficult or
impossible to address are ignored by the tool without requiring specific
user configuration.
Fixes #2464

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 0abdf094b35acb4f3192520e9d515aa89c00a4a7
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 0abdf094b35acb4f3192520e9d515aa89c00a4a7
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID:<PHONE_NUMBER>91761fe3b246ae1a71e7f02e6967ae
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID:<PHONE_NUMBER>91761fe3b246ae1a71e7f02e6967ae
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 04daf3c95e5f77826bf4111ab04b182300a9485b
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 04daf3c95e5f77826bf4111ab04b182300a9485b
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 7ea624d254402937b36e0fab35b031eaa9b5bfee
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 7ea624d254402937b36e0fab35b031eaa9b5bfee
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 1aa745fd9bae3f30a827986ff2341f2b14ee91bf
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 1aa745fd9bae3f30a827986ff2341f2b14ee91bf
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 894ed494dbeffcf4c6352686bd4b3a2c78f1804e
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 894ed494dbeffcf4c6352686bd4b3a2c78f1804e
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 47e0f63960ca289b1fddb705aae4fcc496e7a4b3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 47e0f63960ca289b1fddb705aae4fcc496e7a4b3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 22e7530abeb4e59391dcb2ada1e45c253e447575
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 22e7530abeb4e59391dcb2ada1e45c253e447575
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 55890b286ffad74e2e5d8f5c42ea03ff1693b9af
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 55890b286ffad74e2e5d8f5c42ea03ff1693b9af
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: f1d89f3eae17fc81aa0d6899ad6296cb9cc94d83
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: f1d89f3eae17fc81aa0d6899ad6296cb9cc94d83
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@Mergifyio update

@Mergifyio update

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 7ba7b9a65073f27a6654bf48754e53ed79883f65
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 7ba7b9a65073f27a6654bf48754e53ed79883f65
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


[Event Request] Codeunit 80 Sales-Post - OnPostItemJnlLineSetControls

Hi Team,
In Codeunit 80 we need possibility to have our additional checks. Having event in procedure PostItemJnlLine would be a perfect solution :

[IntegrationEvent(false, false)]
local procedure OnPostItemJnlLineSetControls(ItemJnlLine: Record "Item Journal Line"; SalesHeader: Record "Sales Header"; WhseShip: Boolean; var ItemJnlPostLine: Codeunit "Item Jnl.-Post Line")

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


GH1852: Incorrect escaping of semicolon in property values for msbuild

Changes:

The arguments of the properties specified in the _propertiesNotEscapeSemicolons HashSet will not escape semicolons.

Example: WithProperty("DefineConstants", "A=a;B=b"); will generate /p:DefineConstants=A=a;B=b

If more than one property argument is passed to WithProperty(), the argument parameters will be concatenated using a semicolon:

Example: WithProperty("C", "A=a", "B=b"); will generate /p:C=A=a;B=b
Current list of properties that will not escape semicolons:

DefineConstants
ExcludeFilesFromDeployment

Notes
If these changes are not quite what you had in mind -- or if there are any other issues, please let me know and I will do my best to amend them.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Joe-Dunleavy sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@Joe-Dunleavy your changes have been merged, thanks for your contribution 👍


Auto-select version for client-server communication

This allows the latest version of docker-py to connect to older docker servers.
Tag: 0.0.2?

Do you assume this is "Development" or "Do not use"? If development, then I'd say 0.1.0.

I reckon do-not-use unless someone else has a use for it

Ok. Keeping this at 0.0.2 but I don't imagine we want to stay in 0.0 land long. (It looks funny -- like 2 big eyes...)


Use more specific "when" clauses for commands contributed to views

For some context commands on views, we have "when" clauses that look like "view =~ /pr:/". Since this isn't a very specific regex, it can easily match views contributed from other extensions. We can use a direct match, "view == pr:github", instead.

@RMacfarlane  Unsure but will this also cause any issue - "when": "commentController =~ /^(browse|review)/"?

@RMacfarlane  Unsure but will this also cause any issue - "when": "commentController =~ /^(browse|review)/"?

I checked and comment context also needs to be updated

I checked and comment context also needs to be updated

@RMacfarlane Also I am not sure if this is related but the File Decoration is also duplicating. Will it always show on any URI that has query parameter set?

@RMacfarlane Also I am not sure if this is related but the File Decoration is also duplicating. Will it always show on any URI that has query parameter set?

Yes, currently the decorator is only checking if the uri has status in the query parameters. I can scope it to check the uri scheme as well.

Yes, currently the decorator is only checking if the uri has status in the query parameters. I can scope it to check the uri scheme as well.

Steps to verify this is fixed:

Create a test extension and add a view that starts with "pr", like

    "views": {
      "explorer": [
        {
          "id": "pr-not-github",
          "name": "Test"
        }
      ],

Confirm no actions from the GHPRI extension show up on it.

Steps to verify this is fixed:

Create a test extension and add a view that starts with "pr", like

    "views": {
      "explorer": [
        {
          "id": "pr-not-github",
          "name": "Test"
        }
      ],

Confirm no actions from the GHPRI extension show up on it.

Verified in code.
Note, the regex could also be made more specific:
view =~ /(pr|prStatus):github/  -> view =~ /^(pr|prStatus):github$/

Verified in code.
Note, the regex could also be made more specific:
view =~ /(pr|prStatus):github/  -> view =~ /^(pr|prStatus):github$/


Update dependency on bazel-integration-testing

It contains Bazel compatibility fixes (e.g.
incompatible_string_join_requires_strings)

I just merged #254 which should have the same effect. Thanks!


Is the project alive?

Hello,
I've noticed that the codebase has not been changed since 2 years and I'm wondering if this project is still alive. If not, what are other alternatives to the common problem: "django CMS works on the assumption that it will serve its content directly to a web browser" when more and more websites move into model where everything is rendered in JS.

I'd also love to know.

I'm also hopeful this project isn't dead, but 5 months without a response doesn't bode well.

It's dead, move over to wagtail.


fix: check if node exist before calling contains method

Fixes #6

:tada: This PR is included in version 1.1.2 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Kivy slider show no tracking

Following is adapted from https://stackoverflow.com/questions/41104810/kivy-slider-show-no-tracking/41111456
I started playing around with Kivy, and from the documentation I understand that I can create a slider that highlights its changing value using Slider(value_track=True ...)
Here's an mcve, but alas, tracking isn't working:
from kivy.app import App
from kivy.uix.slider import Slider

class TutorialApp(App):
    def build(self):

        s = Slider(min=-100, max=100, value=25,
                   value_track=True, value_track_color=[0, 1, 0, 1])
        return s

if __name__ == "__main__":
    TutorialApp().run()

@ronbarak, I see a green bar before the handle, could you test with kivy master?

@ronbarak -- Works perfectly for me on master.


best to have docker image

all datasets are downloaded
all requirements are installed
all dependency repos are prepared

Hi, @max-yue ,
Yeah, we plan to build a docker for VLMEvalKit.


No feature_importances_ for XGBRegressor()

XGBoost seems to be lacking feature_importances_ for XGBRegressor() while it does have that for XGBClassifier(). Is it possible to add it for the regression problems as well?

Is it stil the case on master? dd477ac seems to fix that.


[SYM-4796] Update OneLogin example to use runtime-connector module 2.x

Description

Updates the basic/onelogin_access_strategy example to use version 2.x of the runtime-connector module.
Updates the usages of main to reference the local.environment_name variable instead, for consistency.
Updates the Sym Terraform Provider to v3 and the sym_flow.implementation to be file contents, which is required in v3.

Testing
Tested using the alpha version of the runtime-connector module and the following override.tf:
provider "sym" {
  org = "sym"
}

module "runtime_connector" {
  source  = "symopsio/runtime-connector/aws"
  version = "2.0.0-alpha"

  environment_name = local.environment_name
  sym_account_id = "906191524257"
}

resource "sym_integration" "onelogin" {
  type = "onelogin"
  name = "${local.environment_name}-onelogin-integration"

  external_id = "symops-dev.onelogin.com"

  settings = {
    client_id     = "83c6598799dc280adccb1ced54339b77da5c6774e461bdc319bfd7804deec6a6"
    client_secret = sym_secret.onelogin_client_secret.id
  }
}

resource "sym_target" "onelogin_test_role" {
  type = "onelogin_role"

  name  = "onelogin-test-role"
  label = "OneLogin Test Role"

  settings = {
    role_id = "599901"
  }

  field_bindings = ["privilege_level"]
}

Current dependencies on/for this PR:

main

PR #73   👈

This comment was auto-generated by Graphite.


References for DE & PSO

Adding references to DE and PSO algorithms within the file that implements these two techniques may be a good idea.

Done.


Smaller docker image

The current docker image is about 750MB, which is a huge problem when bootstrapping a new seed cluster. We should use an Alpine base image instead of a Debian one to cut out a bunch of unnecessary stuff.

Comparison of the image sizes on my machine:
mc2-alpine               latest    1075400a4878    7 minutes ago     152.3 MB
praekeltfoundation/mc2   latest    dc3e880d5bef    7 weeks ago       748.3 MB

Yay 80% size reduction. :-D

\o/ will this work with all Django images?

@JayH5 mentioned problems with some dependencies on Alpine (uWSGI was the example he gave), so maybe not.
My primary concern here is the MC2 image, because that's the one I have to wait for every time I rebuild my seed VMs.

@miltontony see docker-django-bootstrap for a more general image for Django projects.
@jerith: Did you try with the praekeltfoundation/python-base image? Then you shouldn't need to install (and uninstall) the build dependencies.

That's where I started, but then I noticed mc2 didn't use it. I decided to keep this standalone for now and worry about the larger ecosystem later.

@jerith if it works, then :+1:


Vertex

Good morning Kibo
I am trying to add the Vertex point also in the chart - like the As, Dc, Ic, and MC. I got a red dot with a line at the right position....
I made the following changes to the code. I added the var
astrology.SYMBOL_VX = "Vx";
In the
astrology.Radix.prototype.drawAxis = function(){
function, I coded:
var VX = 12; ... [AS,IC,DC,MC,VX].forEach( function(i) {
There, if i==12, I made
startPosition = astrology.utils.getPointPosition( this.cx, this.cy, this.radius, this.data.planets['Vertex'] + this.shift); endPosition = astrology.utils.getPointPosition( this.cx, this.cy, axisRadius, this.data.planets['Vertex'] + this.shift);
As you can see, I've passed the Vertex as if it was a planet.
And finnaly added - in the same function:
if(i == VX){  textPosition = astrology.utils.getPointPosition( this.cx, this.cy, axisRadius + (10 * astrology.SYMBOL_SCALE), this.data.planets['Vertex'] - 2 + this.shift); wrapper.appendChild( this.paper.getSymbol( astrology.SYMBOL_VX, textPosition.x, textPosition.y)); }
Can you please help?
Kind regards

Hi Ptolemy
I was looking for meaning of Vertex in astrology wikipedie, because I dont know it.
According to that description is Vertex some point, similar to the northern and southern nodes.
You have to add Vx to "points".
This is probably bad:
var VX = 12; ... [AS,IC,DC,MC,VX].forEach( function(i) {
Regards
Tomas


chore: update dependency

Try to update

appreciated, @Arhell but we are currently not able to bump versions due to hugo concerns, see #4064

Got it, thanks, I'll close it for now


Poor Result on Using LM boosted Wav2Vec 2.0

Hey guys,
While using pyctcdecode package with Wav2Vec2 from huggingface, I came across a strange issue. It combines many words generated by a normal acoustic model. Eg: Acoustic Model: " I will definitely like to visit that place". LM Model: " I will definitely liketo visitthat place".

Hey, my guess would be a vocabulary mismatch. Do you have an example to reproduce? happy to look

Silly Me ! I made a small mistake which led to vocab mismatch. Thanks a lot for your time. Closing the issue.

Great :)


Rigid vars allowed to escape their scope

Rigid variables can escape their scope:
#lang hackett
(def weird
  (λ (x)
    (: (λ (y) (if True x y))
       (∀ (A) (-> A A)))))
;;;
> (#:type weird)
: (forall (A1618) {A9 -> A1618 -> A1618})

Weird scenarios can arise when rigid variables escape their scope. Here, A9 refers to a out-of-scope rigid variable. It will fail to unify with anything else but it is clearly not bound by the final forall.
The algorithm in Complete and Easy Bidirectional Typechecking prevents this by keeping a close eye on the scopes of rigid and solver variables.

I dropped the skolem escape check from the previous implementation because I clearly wasn’t doing it correctly, but I wasn’t sure precisely how to do it properly. I agree that it’s a bug that Hackett doesn’t properly check for skolem escapes. However, I’m not completely sure when it’s appropriate to perform the check.
A simple check that would catch your program would be to ensure rigid variables are never quantified over during generalization, but this seems like it might be too permissive? I’ve struggled to find a good treatment in the literature of the problem of skolem escape.

The way that Complete and Easy Bidirectional Typechecking handles this is by having rigid variables and solver variables in the same ordered context, and maintaining the invariant that solver variables are never instantiated to variables introduced after them; an attempt to do so results in a type error.
Granted, I'm not sure where this error comes up without intentionally provoking the typechecker.

My interpretation of the Complete and Easy paper is that the ordered context is quite useful for proving properties of their system, which they care a lot about. It does not seem very useful for actually implementing a practical type system because maintaining the necessary invariants is somewhat fragile in the face of extension. The paper takes great care to insert into the context in specific places, which I imagine they spent a great deal thinking about and picking to make their proofs as easy to specify as possible, but a real language is more complicated, and it doesn’t seem worth the balancing act.
Other typecheckers, such as GHC and PureScript, perform skolemization and check for skolem escape without the use of an ordered context. I think it would be worth understanding what they do in more detail. I’ve looked at the PureScript code before, but I did not feel like I fully understood the details. That said, perhaps what was in Hackett before is actually not too far from the right thing, and it should just be reinstated in a more careful way.


flaky: TestE2E/ExtProc

    --- FAIL: TestE2E/ExtProc (25.67s)
        --- PASS: TestE2E/ExtProc/http_route_with_ext_proc (21.03s)
        --- PASS: TestE2E/ExtProc/http_route_without_proc_mode (2.01s)
        --- FAIL: TestE2E/ExtProc/http_route_with_uds_ext_proc (2.01s)

https://github.com/envoyproxy/gateway/actions/runs/9584691590/job/26443469051

cc @guydc


Spoilers

Partially solves issue #138 :

spoilers are now hidden by default, they are replaced by spaces   and a colored background
a new action s has been added that toggles spoilers

Due to recent changes in the code, I find it easier to redo this PR entirely. Will be back next with with another one.


[feat] use space key to page down, use shift space key to page up

background
Browser defaults to use space key to page down, use shift space key to page up.
Calibre defaults to use space key to page down, use shift space key to page up.
feat
Foliate defaults to or able to use space key to page down, use shift space key to page up

Currently the library itself does not handle shortcuts as they are up to the application using the library.


Update everything to .NET 5

Abacus currently uses QActive which needs to be ported to .net core 5


Not found error in WMIQuerySensor 'more information' button

When in the Add Sensor dialog and selecting WMIQuerySensor, the 'Click for more information' button takes you to a not found page. Looks like there is just a / missing between sleevezipper and hass-workstation-service
https://github.com/sleevezipperhass-workstation-service/blob/master/documentation/WMIQuery.md#wmiquerysensor
Checked a few other types and they seem to be OK

I noticed this as well.


Issues While Open a Folder

Issue Type: Bug
【My Settings】
"workbench.editor.closeOnFileDelete": false,
"window.restoreWindows": "none",
"files.hotExit": "off"
【Steps】

Use right click menu "Open with Code" to open a folder which is never opened before.
Then the explore of VS Code will appear on the left.

Then close the explorer manually. (Click the button)

Close the window.
Use right menu to open the folder again.

The explorer of code will not appear any more unless I press the button again.
It seems that the folder isn't opened.
https://github.com/Microsoft/vscode/issues/38396
Actually, it has been opened, but the explorer didn't display.
Close the explorer again, and close the VS Code windows.
Rename the folder, and then open it with the right menu.

The folder is opened, and the explorer display on the left.
Repeat the steps if you like...

VS Code version: Code - Insiders 1.25.0-insider (7dc9539a421c9c33e57e2ce0b718f183bb44c756, 2018-06-15T05:17:41.405Z)
OS version: Windows_NT x64 10.0.17686

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz (4 x 2494)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.53GB (3.83GB free)

Process Argv
C:\Program Files\Microsoft VS Code Insiders\Code - Insiders.exe

Screen Reader
no

VM
50%

Extensions (1)

Extension
Author (truncated)
Version

vscode-language-pack-zh-hans
MS-
1.24.3

(1 theme extensions excluded)

Do you see anything in the console F1 > developer tools > console
What is the actual issue here, i do not understand

I mean, if I open a folder I have opened before, nothing will display in the main window.
It won't happen if I open a folder I never opened before.
I can create a gif if needed.

@byyxx128 you closed the sidebar and we just remember that the sidebar is closed when you start again. Closing "as designed".

While I don't want VS Code to remember what I did before. How can I do?
Is there a option for this?

@bpasero Well you are right. But I want VSCode not to remember what I did. Maybe it should be a feature request? I need a option to control if VSCode will remember what I did in a folder.
Maybe they are similar. https://github.com/Microsoft/vscode/issues/52086


[Docs] Issue Form Remove "free rider"

Motivation
The "free rider" statement is inappropriate. It will discourage contribution by those who see a problem, but have no idea what to do to fix it. It is not always the case that a user can understand how to even submit a PR.
For example this page - https://pulsar.apache.org/docs/en/client-libraries/#third-party-clients suggests that users submit a PR, but does not provide an easy way to do so.
Modifications
Rewrote the section including improving the English
Verifying this change
This change is a trivial change outside of the code base.
Does this pull request potentially affect one of the following parts:
If yes was chosen, please highlight the changes

Dependencies (does it add or upgrade a dependency): (no)
The public API: (no)
The schema: (no)
The default values of configurations: (no)
The wire protocol: (no)
The rest endpoints: (no)
The admin cli options: (no)
Anything that affects deployment: (no)

Documentation
Check the box below and label this PR (if you have committer privilege).
Need to update docs?

[X] no-need-doc
It changes the docs issue form

The ASF's mission is to provide software for the public good at no cost under a permissive license.
Free riding is the point.


A problem between RTSEG and SHUFFLRSEG

What‘s the differences between RTSEG and SHUFFLRSEG? Those papers used the same methods and code.

RTSeg paper is about the decoupling and evaluation of different architectures. While ShuffleSeg is about utilizing grouped convolution and channel shuffling in semantic segmentation :). I hope you realize its not an issue in the code so I will close and you can inquire on our emails on any further misunderstandings.


Fix Typos and Improve Grammar in README

This pull request addresses several grammatical issues and improves the phrasing in the README file. The changes made include:

Changed "uses tasks grouped into pipelines" to "organizes tasks into pipelines" for better flow.
Replaced "improving the answers generated by Large Language Models (LLMs)" with "enhancing the quality of answers produced by Large Language Models (LLMs)" for clarity.
Simplified "In this section, you'll find a template that you can use" to "This section provides a template to help" for a more direct tone.
Capitalized "Cognee" for consistency.

Summary by CodeRabbit

Documentation

Enhanced clarity and readability of the Cognee system's task organization and pipeline structure documentation.
Corrected grammatical errors and streamlined language in the "Task 1: Category Extraction" section.
Updated descriptions to emphasize the purpose of tasks within LLM pipelines.

@Mefisto04 thank you for the contribution. Would love to hear about your experience using cognee!
If you have some time, drop by to our Discord channel and we can chat there


Hatched bonds

I was trying to make some molecules and I noticed that hatched bonds show up as normal bonds
class Methane(Scene):
def construct(self):
f1 = ChemObject("C(-[5]H)(-[2]H)(<[:-70]H)(<:[:-20]H)")
self.play(Write(f1))
self.wait()

also I'm having some trouble trying to change the color of bonds and atoms
class Chem2(Scene):
def construct(self):
f1 = ChemObject("-[:30]=[:-30,,,,red]-[:30]")
self.play(Write(f1))
self.wait()

Does anyone know what am I doing wrong?

Hi, really sorry for a late response.
I looked into it and can confirm that the hatched bonds do in fact not show up.The SVG produced by TeX looks fine though:

I'm assuming this is a problem with Manim's SVG parser which already has quite a few problems. I'm sorry but I don't think there's anything I can do about this at the moment.
Regarding the colors, Manim flushes out all colors except black and white in SVGs. There is a workaround though:
        self.add(f1,get_submobject_index_labels(f1[0])) ## shows the indexes of each part of the molecule.

Result:

        ## you can remove the previous line if you want to
        f1[0][1:3].set_color(RED)
        self.add(f1)

Result:

Hope this helps. Once again, sorry for a late response.


Add descriptions

This list links a bunch of things but doesn't tell me why those links are worth checking out. Similar to other awesome lists you might want to consider a format like:
[name](link) - description.

which would be way more useful.
Thanks for the awesome list!

Why was this closed? It's in the awesome manifesto, by the way.

Can you add then @arthurvr

+1

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Claimed my free tokens on Binance! 🌟 #BinanceFreeTokens #Crypto

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Free Tokens Page.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰


Failed to call service fan/turn_on. invalid state "10000" for pin GPIO14

System Health details
System Information

version
core-2024.5.5

installation_type
Home Assistant OS

dev
false

hassio
true

docker
true

user
root

virtualenv
false

python_version
3.12.2

os_name
Linux

os_version
6.6.28-haos-raspi

arch
aarch64

timezone
Europe/London

config_dir
/config

Home Assistant Community Store

GitHub API
ok

GitHub Content
ok

GitHub Web
ok

GitHub API Calls Remaining
4575

Installed Version
1.34.0

Stage
running

Available Repositories
1395

Downloaded Repositories
21

Home Assistant Cloud

logged_in
false

can_reach_cert_server
ok

can_reach_cloud_auth
ok

can_reach_cloud
ok

Home Assistant Supervisor

host_os
Home Assistant OS 12.3

update_channel
stable

supervisor_version
supervisor-2024.05.1

agent_version
1.6.0

docker_version
25.0.5

disk_total
57.3 GB

disk_used
24.9 GB

healthy
true

supported
true

board
rpi4-64

supervisor_api
ok

version_api
ok

installed_addons
Duck DNS (1.17.0), Mosquitto broker (6.4.1), WireGuard (0.10.2), Advanced SSH & Web Terminal (18.0.0), File editor (5.8.0), ESPHome (2024.5.4), Log Viewer (0.17.0), Zigbee2MQTT (1.38.0-1), Whisper (2.1.0), Piper (1.5.0), Portainer (2.20.1), HassOS I2C Configurator (0.14), I2C OLED Display (1.0.5), pigpio (1.5.2), Epic Games Free (debian-2024-04-28), go2rtc (1.9.2), Speedtest (1.6.2), MQTT Explorer (browser-1.0.3), Neolink-latest (0.0.1), Network UPS Tools (0.13.0), Samba share (12.3.1), MeshCentral (1.1.22)

Dashboards

dashboards
5

resources
8

views
19

mode
storage

Recorder

oldest_recorder_run
24 May 2024 at 20:24

current_recorder_run
2 June 2024 at 22:57

estimated_db_size
653.79 MiB

database_engine
sqlite

database_version
3.44.2

Checklist

[X] I have enabled debug logging for my installation.
[X] I have filled out the issue template to the best of my ability.
[X] This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
[X] This issue is not a duplicate issue of currently previous issues..

Describe the issue
after upgrade to v2024.5.5, the control of my rpi fan no longer works
i keep getting an error saying Failed to call service fan/turn_on. invalid state "10000" for pin GPIO14
Reproduction steps

install v2024.3.3
setup in json
restart ha
control fan, then stop fan
upgrade to v2024.5.5
restart ha
try turning on fan

Debug logs
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/gpiozero/pins/pigpio.py", line 245, in _set_state
    if value != self.factory.connection.get_PWM_dutycycle(self.number):
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pigpio.py", line 1511, in get_PWM_dutycycle
    return _u2i(_pigpio_command(self.sl, _PI_CMD_GDC, user_gpio, 0))
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/pigpio.py", line 1011, in _u2i
    raise error(error_text(v))
pigpio.error: 'GPIO is not in use for PWM'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/commands.py", line 239, in handle_call_service
    response = await hass.services.async_call(
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2738, in async_call
    response_data = await coro
                    ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/core.py", line 2779, in _execute_service
    return await target(service_call)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 975, in entity_service_call
    single_response = await _handle_entity_call(
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/service.py", line 1047, in _handle_entity_call
    result = await task
             ^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/fan/__init__.py", line 328, in async_handle_turn_on_service
    await self.async_turn_on(percentage, preset_mode, **kwargs)
  File "/usr/src/homeassistant/homeassistant/components/fan/__init__.py", line 337, in async_turn_on
    await self.hass.async_add_executor_job(
  File "/usr/local/lib/python3.12/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/rpi_gpio_pwm/fan.py", line 177, in turn_on
    self._fan.value = self._percentage / 100
    ^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/gpiozero/devices.py", line 132, in __setattr__
    return super(GPIOBase, self).__setattr__(name, value)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/gpiozero/output_devices.py", line 448, in value
    self._write(value)
  File "/usr/local/lib/python3.12/site-packages/gpiozero/output_devices.py", line 435, in _write
    super(PWMOutputDevice, self)._write(value)
  File "/usr/local/lib/python3.12/site-packages/gpiozero/output_devices.py", line 96, in _write
    self.pin.state = self._value_to_state(value)
    ^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/gpiozero/pins/__init__.py", line 285, in
    lambda self, value: self._set_state(value),
                        ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/gpiozero/pins/pigpio.py", line 248, in _set_state
    raise PinInvalidState('invalid state "%s" for pin %r' % (value, self))
gpiozero.exc.PinInvalidState: invalid state "5000" for pin GPIO14

Diagnostics dump
No response

@erdnaxela02 This is the same issue

Same here.
Also changing the fan speed is not possible
Changing to e.g. 84% says
Fehler beim Aufrufen des Diensts fan/set_percentage. invalid state "8400" for pin GPI0

Yes, I see the same behavior.  Reverting to config through yaml seems to be the workaround for now.
I hope @erdnaxela02 has time to look at it cause setting it trough UI is a nice step forwards 😄

Hello !
I have a good new!
After many, many, many tries, I FINALLY found what appears to be the root of the problem!
I explored a lot of avenues which turned out not to be the right ones. Many things surprised me since everything seemed ok to me.
But it's finding! I just have to find a way to make this clean. Hope to send you an update tomorrow :D

That would be awesome!  I’ll check it as soon as you posted the push.

Fixed in latest release


[Question] PopOut! Module - JQuery Events

Hi! So let me start this thread off with the message that I do not know anything about coding, at all. It's magic to me.
But we've been using the PopOut! Module ( https://foundryvtt.com/packages/popout )  for a while, which is intended to only be used with 5e in fairness, but has worked wonderfully with the Pathfinder 2e module as well. Upon running into a bug last night, where characters were unable to swap equipment due to having the sheet 'Popped out', I've done some digging.
I ran into: https://github.com/League-of-Foundry-Developers/fvtt-module-popout/issues/95
And so basically, this 'Issue' is more of an attempt to gather information from my end. Apologies if that's not it's intended use. I'm willing to believe the Dev from PopOut! that'd it'd be a lot, if perhaps too much work, but I was wondering if another solution could perhaps be found to solve it. A work around on 2e's module, or perhaps someone with a better head for coding here could make a PopOut! Pf2e module/branch/similar module for the functionality. Or perhaps it's a thing that could be build into the sheets eventually and to not require a module at all.
For those of us with several monitors, being able to put pages/sheets/maps sheets over to the other one and reduce overlap is a really welcomed functionality. It's luckily a bug that can be worked around but figured I'd ask around nonetheless and this seemed like the best place to do it!
Thank you for reading, any bits of information is welcome about the issue. (I have no clue what a Jquery Event Listener even is)
Love all the work you all put into the module!

This is an issue that doesn’t really have anything to do with the PF2e system. It is just how core Foundry and the Pop Out module function. Your best bet is to find the ticket requesting that Foundry enable this functionality natively within the core software and support it.
We actively try not code the system for support for any specific module, no matter how good it is.
Closing as not within the scope of the system.

In case it is helpful, the issue you link is flat wrong: the pf2e system utilizes jquery less extensively than core Foundry or the dnd5e system (both of which are jquery-driven for virtually all interactivity within every application window).


overload resolution and disambiguation

Page 62, chapter 14, says:

The corresponding sections "overload resolution" and "overload disambiguation" contain the details.

References should be made to chapter 19 (Overload resolution) and section 19.4 (Overload disambiguation) directly.

This has been fixed in the later revision of the book.


Missing PATH on kubeless.js runtime

Is this a BUG REPORT or FEATURE REQUEST?:
BUG REPORT
What happened:
When I send request with path ping using kubeless.js middleware it send / instead of the path
What you expected to happen:
to send the path requested
How to reproduce it (as minimally and precisely as possible):
curl --header "Host: kubernetes.docker.internal.nip.io" localhost/ping
and logs says
  'event-type': undefined,
  'event-id': undefined,
  'event-time': undefined,
  'event-namespace': undefined,
  data: {},
  extensions: {
    request: IncomingMessage {
      _readableState: [ReadableState],
      readable: true,
      _events: [Object: null prototype],
      _eventsCount: 1,
      _maxListeners: undefined,
      socket: [Socket],
      connection: [Socket],
      httpVersionMajor: 1,
      httpVersionMinor: 1,
      httpVersion: '1.1',
      complete: false,
      headers: [Object],
      rawHeaders: [Array],
      trailers: {},
      rawTrailers: [],
      aborted: false,
      upgrade: false,
      url: '/',
      method: 'GET',
      statusCode: null,
      statusMessage: null,
      client: [Socket],
      _consuming: false,
      _dumped: false,
      next: [Function: next],
      baseUrl: '',
      originalUrl: '/',
      _parsedUrl: [Url],
      params: [Object],
      query: {},
      res: [ServerResponse],
      _startAt: [Array],
      _startTime: 2020-03-04T15:48:55.191Z,
      _remoteAddress: '::ffff:<IP_ADDRESS>',
      body: {},
      route: [Route]
    },
    response: ServerResponse {
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      outputData: [],
      outputSize: 0,
      writable: true,
      _last: false,
      chunkedEncoding: false,
      shouldKeepAlive: true,
      useChunkedEncodingByDefault: true,
      sendDate: true,
      _removedConnection: false,
      _removedContLen: false,
      _removedTE: false,
      _contentLength: null,
      _hasBody: true,
      _trailer: '',
      finished: false,
      _headerSent: false,
      socket: [Socket],
      connection: [Socket],
      _header: null,
      _onPendingData: [Function: bound updateOutgoingData],
      _sent100: false,
      _expect_continue: false,
      req: [IncomingMessage],
      locals: [Object: null prototype] {},
      _startAt: undefined,
      _startTime: undefined,
      writeHead: [Function: writeHead],
      __onFinished: [Function],
      [Symbol(isCorked)]: false,
      [Symbol(outHeadersKey)]: [Object: null prototype]
    }
  }
}
::ffff:<IP_ADDRESS> - - [04/Mar/2020:15:48:55 +0000] "GET / HTTP/1.1" 200 421 "-" "PostmanRuntime/7.20.1"

on AWS, works fine: because there is path sending...
  "message": "Go Serverless v1.0! Your function executed successfully!",
  "input": {
    "resource": "/users/create",
    "path": "/users/create",
    "httpMethod": "GET",
    "headers": {
      "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9",
      "Accept-Encoding": "gzip, deflate, br",
      "Accept-Language": "es-ES,es;q=0.9,en;q=0.8",
      "CloudFront-Forwarded-Proto": "https",
      "CloudFront-Is-Desktop-Viewer": "true",
      "CloudFront-Is-Mobile-Viewer": "false",
      "CloudFront-Is-SmartTV-Viewer": "false",
      "CloudFront-Is-Tablet-Viewer": "false",
      "CloudFront-Viewer-Country": "CL",
      "dnt": "1",
      "Host": "u5m2ln50ff.execute-api.us-east-1.amazonaws.com",
      "sec-fetch-dest": "document",
      "sec-fetch-mode": "navigate",
      "sec-fetch-site": "none",
      "upgrade-insecure-requests": "1",
      "User-Agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36",
      "Via": "2.0 1ddeacce24f5e91d497c9d8a72218fd2.cloudfront.net (CloudFront)",
      "X-Amz-Cf-Id": "l0OoCHP16-AiD4mWWZTppe3U1wRp1_nvKf4SAv2a11VpLJ4SxSW7ZA==",
      "X-Amzn-Trace-Id": "Root=1-5e5fb4f8-ef67231d936e9b9f5229f781",
      "X-Forwarded-For": "<IP_ADDRESS>, <IP_ADDRESS>",
      "X-Forwarded-Port": "443",
      "X-Forwarded-Proto": "https"
    },
    "multiValueHeaders": {
      "Accept": [
        "text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9"
      ],
      "Accept-Encoding": [
        "gzip, deflate, br"
      ],
      "Accept-Language": [
        "es-ES,es;q=0.9,en;q=0.8"
      ],
      "CloudFront-Forwarded-Proto": [
        "https"
      ],
      "CloudFront-Is-Desktop-Viewer": [
        "true"
      ],
      "CloudFront-Is-Mobile-Viewer": [
        "false"
      ],
      "CloudFront-Is-SmartTV-Viewer": [
        "false"
      ],
      "CloudFront-Is-Tablet-Viewer": [
        "false"
      ],
      "CloudFront-Viewer-Country": [
        "CL"
      ],
      "dnt": [
        "1"
      ],
      "Host": [
        "u5m2ln50ff.execute-api.us-east-1.amazonaws.com"
      ],
      "sec-fetch-dest": [
        "document"
      ],
      "sec-fetch-mode": [
        "navigate"
      ],
      "sec-fetch-site": [
        "none"
      ],
      "upgrade-insecure-requests": [
        "1"
      ],
      "User-Agent": [
        "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36"
      ],
      "Via": [
        "2.0 1ddeacce24f5e91d497c9d8a72218fd2.cloudfront.net (CloudFront)"
      ],
      "X-Amz-Cf-Id": [
        "l0OoCHP16-AiD4mWWZTppe3U1wRp1_nvKf4SAv2a11VpLJ4SxSW7ZA=="
      ],
      "X-Amzn-Trace-Id": [
        "Root=1-5e5fb4f8-ef67231d936e9b9f5229f781"
      ],
      "X-Forwarded-For": [
        "<IP_ADDRESS>, <IP_ADDRESS>"
      ],
      "X-Forwarded-Port": [
        "443"
      ],
      "X-Forwarded-Proto": [
        "https"
      ]
    },
    "queryStringParameters": null,
    "multiValueQueryStringParameters": null,
    "pathParameters": null,
    "stageVariables": null,
    "requestContext": {
      "resourceId": "j246vp",
      "resourcePath": "/users/create",
      "httpMethod": "GET",
      "extendedRequestId": "I3k21EGcIAMFePA=",
      "requestTime": "04/Mar/2020:14:02:32 +0000",
      "path": "/dev/users/create",
      "accountId": "081356250805",
      "protocol": "HTTP/1.1",
      "stage": "dev",
      "domainPrefix": "u5m2ln50ff",
      "requestTimeEpoch":<PHONE_NUMBER>468,
      "requestId": "65f053c2-cd2b-4ecf-a272-d6015ab24bad",
      "identity": {
        "cognitoIdentityPoolId": null,
        "accountId": null,
        "cognitoIdentityId": null,
        "caller": null,
        "sourceIp": "<IP_ADDRESS>",
        "principalOrgId": null,
        "accessKey": null,
        "cognitoAuthenticationType": null,
        "cognitoAuthenticationProvider": null,
        "userArn": null,
        "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.122 Safari/537.36",
        "user": null
      },
      "domainName": "u5m2ln50ff.execute-api.us-east-1.amazonaws.com",
      "apiId": "u5m2ln50ff"
    },
    "body": null,
    "isBase64Encoded": false
  }
}

Anything else we need to know?:
I found out in runtime:
https://github.com/kubeless/runtimes/blob/master/stable/nodejs/lib/helper.js#L38-L50
there no funtion for *
I would expect something like:
function routeAll(expressApp, promClient) {
  expressApp.get('/*', (req, res) => {
    return {req, res}
  });
}

I do not know if it works
Environment:

Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-13T18:08:14Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.5", GitCommit:"20c265fef0741dd71a66480e35bd69f18351daea", GitTreeState:"clean", BuildDate:"2019-10-15T19:07:57Z", GoVersion:"go1.12.10", Compiler:"gc", Platform:"linux/amd64"}
Kubeless version:
Kubeless version: v1.0.6
Cloud provider or physical cluster:
Docker 2 Machine

My test escenario https://github.com/jcalonsoh/test-kubeless

mm, I am not able to reproduce your issue, are you using an HTTP trigger?
In my case, I have deployed the sample nodejs function and a simple HTTP trigger:
▶ kubeless function deploy get-nodejs --runtime nodejs6 --handler helloget.foo --from-file nodejs/helloget.js
▶ kubeless trigger http create get-nodejs --function-name get-nodejs

I can see the path logged when I am doing requests:
▶ curl -H "Host: get-nodejs.<IP_ADDRESS>.nip.io" localhost:30080/foo
hello world!%
▶ kubectl logs get-nodejs-5bd7c8848b-hz5pf | grep foobar
        url: '/foobar',
        originalUrl: '/foobar',
     url: '/foobar',
     originalUrl: '/foobar',
        pathname: '/foobar',
        path: '/foobar',
        href: '/foobar',
        _raw: '/foobar' },
     params: { '0': '/foobar' },
        url: '/foobar',
        originalUrl: '/foobar',
::ffff:<IP_ADDRESS> - - [05/Mar/2020:10:48:42 +0000] "GET /foobar HTTP/1.1" 200 - "-" "curl/7.58.0"

mm, I am not able to reproduce your issue, are you using an HTTP trigger?
In my case, I have deployed the sample nodejs function and a simple HTTP trigger:
▶ kubeless function deploy get-nodejs --runtime nodejs6 --handler helloget.foo --from-file nodejs/helloget.js
▶ kubeless trigger http create get-nodejs --function-name get-nodejs

I can see the path logged when I am doing requests:
▶ curl -H "Host: get-nodejs.<IP_ADDRESS>.nip.io" localhost:30080/foobar
hello world!%
▶ kubectl logs get-nodejs-5bd7c8848b-hz5pf | grep foobar
        url: '/foobar',
        originalUrl: '/foobar',
     url: '/foobar',
     originalUrl: '/foobar',
        pathname: '/foobar',
        path: '/foobar',
        href: '/foobar',
        _raw: '/foobar' },
     params: { '0': '/foobar' },
        url: '/foobar',
        originalUrl: '/foobar',
::ffff:<IP_ADDRESS> - - [05/Mar/2020:10:48:42 +0000] "GET /foobar HTTP/1.1" 200 - "-" "curl/7.58.0"

can you share your repo, please

and what version are you using ??

I am using the helloget example from this repo (I only added a console.log of the request to print more info):
https://github.com/kubeless/runtimes/blob/master/stable/nodejs/examples/helloget.js
I am using kubeless 1.0.6.
In your case, I believe it's an issue with the HTTP trigger/ingress configuration. How did you create it? What ingress controller are you using?

Thanks I found out the problem, it's on plugin serverless-kubeless
https://github.com/serverless/serverless-kubeless/blob/master/lib/deploy.js#L533
looks like there is no definition function to create HTTPTrigger
kind: HTTPTrigger
metadata:
 name: cors-trigger
 annotations:
  nginx.ingress.kubernetes.io/enable-cors: "true"
  nginx.ingress.kubernetes.io/cors-allow-methods: "GET"
spec:
 function-name: get-python
 host-name: example.com
 path: echo```

Ah, yes, the serverless-kubeless creates an Ingress resource directly rather than creating an HTTP Trigger (which is the Kubeless abstraction). I recommend you to use the kubeless CLI to create the HTTP trigger since the serverless plugin is a bit behind regarding functionality.
In any case we are open to contributions for any project in case anyone wants to fix the issue there.

Nice... I am looking forward. Better if you have a Doc to setup an dev env for help on issues.

We have a bit of documentation for the Kubeless main project (https://kubeless.io/docs/dev-guide/) but unfortunately not here


brew doctor shows "pre-release" disclaimer on stable public release of macOS 14

brew doctor output
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: You are using macOS 14.
We do not provide support for this pre-release version.
It is expected behaviour that some formulae will fail to build in this pre-release version.
It is expected behaviour that Homebrew will be buggy and slow.
Do not create any issues about this on Homebrew's GitHub repositories.
Do not create any issues even if you think this message is unrelated.
Any opened issues will be immediately closed without response.
Do not ask for help from Homebrew or its maintainers on social media.
You may ask for help in Homebrew's discussions but are unlikely to receive a response.
Try to figure out the problem yourself and submit a fix as a pull request.
We will review it but may or may not accept it.

Verification

[ ] My "brew doctor output" above says Your system is ready to brew. and am still able to reproduce my issue.
[X] I ran brew update twice and am still able to reproduce my issue.
[X] This issue's title and/or description do not reference a single formula e.g. brew install wget. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.

brew config output
HOMEBREW_VERSION: 4.1.11
ORIGIN: https://github.com/Homebrew/brew
HEAD: 4afb8e5602f3ecc9edf67a44257d8eceeaa8a108
Last commit: 3 days ago
Core tap JSON: 14 Sep 18:56 UTC
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 16
Homebrew Ruby: 2.6.10 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
CPU: 16-core 64-bit kabylake
Clang: 15.0.0 build 1500
Git: 2.39.3 => /Applications/Xcode-15.0.0-Release.Candidate.app/Contents/Developer/usr/bin/git
Curl: 8.1.2 => /usr/bin/curl
macOS: 14.0-x86_64
CLT: <IP_ADDRESS>.1.1694021235
Xcode: 15.0 => /Applications/Xcode-15.0.0-Release.Candidate.app/Contents/Developer

What were you trying to do (and why)?
run brew doctor (to check my system for potential problems)
What happened (include all command output)?
brew doctor says that Homebrew does "not provide support for this pre-release version", despite me being on a public/stable OS version
What did you expect to happen?
brew doctor prints "Your system is ready to brew."
Step-by-step reproduction instructions (by running brew commands)
1. Install the latest stable version of macOS (14; Sonoma)
2. run `brew doctor`

14.0 (23A339) is still only a release candidate, so I suppose it's still considered pre-release

There is no public stable version of macOS 14. It's released on 26th September.
We'll update the pre-release status ahead of then however, likely when a sufficient number of bottles have been built for Sonoma over the next week or so. We started bottle builds yesterday after the first release candidate was released.

Also worth remembering: the last five macOS releases had two release candidates, so the first one isn't necessarily what ends up being the public release. Though it's good enough in our case for bottle building and CI.

Oh cool so the software updater lied to me. Thanks for letting me know; I wish Apple did


Compile error when trying to return a type predicate closure from a function

Bug Report

🔎 Search Terms
"type predicate"
"must be a type predicate"
🕗 Version & Regression Information
4.6.2

This is the behavior in every version I tried, and I reviewed the FAQ for entries about type predicates

⏯ Playground Link
Playground link with relevant code
💻 Code
type ThingWithId<T extends string> = {
  id: T;
}

function isThingWithId<T extends string>(id: T): (value: any) => value is ThingWIthId<T>{
  const predicate: (value: any) => value is ThingWIthId<T> = value => isThingWithIdImpl(value, id);

  return predicate;
}

function isThingWithIdImpl<T extends string>(value: any, id: T): value is ThingWIthId<T>{
    return true;
}

🙁 Actual behavior
Error:
Type '(value: any) => boolean' is not assignable to type '(value: any) => value is ThingWIthId<T>'.
  Signature '(value: any): boolean' must be a type predicate.

🙂 Expected behavior
Should compile fine

You haven't typed your anonymous function, so the return type is inferred as boolean. When you type it correctly it will work.
(value): value is ThingWIthId<T> => isThingWithIdImpl(value, id);

ok... So this works:
function isThingWithId<T extends string>(id: T): (value: any) => value is ThingWIthId<T>{
  return function(value: any) : value is ThingWIthId<T>{
    return isThingWithIdImpl(value, id)
  }
}

how would I type my original code using a lambda?

how would I type my original code using a lambda?

I.. told you already..?
function isThingWithId<T extends string>(id: T): (value: any) => value is ThingWIthId<T>{
  const predicate: (value: any) => value is ThingWIthId<T> = (value): value is ThingWIthId<T> => isThingWithIdImpl(value, id);

  return predicate;
}

Or simplified:
function isThingWithId<T extends string>(id: T): (value: any) => value is ThingWIthId<T>{
  const predicate = (value: any): value is ThingWIthId<T> => isThingWithIdImpl(value, id);

  return predicate;
}

ok, thanks. Couldn't quite see how to apply the type to the function but yes. Obvious now.


Feature: Translator-friendly plural rules

Problem
We are using plural rules in the JSON in our app, such as:
"myPluralRule": "{myCount, plural, =0 {no results} one {1 result} other {# results}}"
However, we need to translate these into 27 other languages and, although we've tried to explain precisely, the translators are having difficulty understanding what to do.
Preferred solution
Communication to the translators would be much simpler if the sections within the inner curly brackets referenced separate translations. Something like:
"myPluralRule": "{myCount, plural, =0 {@no_results} one {@one_result} other {@many_results}}",
"no_results": "No results",
"one_result": "1 result",
"many_results": "# results",

As well making it easier for the translators it would make it more straightforward for us to automate the preparation of the strings for translation.

@AndiBat Have you seen reference other keys section in the docs?

Hi Sharhar
Thanks for the pointer, but I couldn’t get it to work.
I tried…
"profile": {
"zero_credentials": "0 Credentials",
"one_credentials": "1 Credential",
"other_credentials": "# Credentials",
"credentials_plural_count_test": "{count, plural, =0 {{{zero_credentials}}} one {{{one_credentials}}} other {{{other_credentials}}}}"
}
…and …
"profile": {
"zero_credentials": "0 Credentials",
"one_credentials": "1 Credential",
"other_credentials": "# Credentials",
"credentials_plural_count_test": "{count, plural, =0 {{zero_credentials}} one {{one_credentials}} other {{other_credentials}}}”
}
…and …
"profile": {
"zero_credentials": "0 Credentials",
"one_credentials": "1 Credential",
"other_credentials": "# Credentials",
"credentials_plural_count_test": "{count, plural, =0 {{{profile.zero_credentials}}} one {{profile.{one_credentials}}} other {{{profile.other_credentials}}}}"
}
…and …
"profile": {
"zero_credentials": "0 Credentials",
"one_credentials": "1 Credential",
"other_credentials": "# Credentials",
"credentials_plural_count_test": "{count, plural, =0 {{profile.zero_credentials}} one {{profile.{one_credentials}}} other {{profile.other_credentials}}}”
}
All crashed silently 🙁
What am I doing wrong?
Cheers
Andrew

On 2 Apr 2021, at 11:48 am, Shahar Kazaz @.***> wrote:
@AndiBat https://github.com/AndiBat Have you seen reference other keys https://ngneat.github.io/transloco/docs/additional-functionality/#reference-other-keys section in the docs?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/ngneat/transloco/issues/420#issuecomment-812479073, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHUUEFU2JMNSHAZATUKVAFTTGWOHZANCNFSM42EJEAPA.

@AndiBat This is working as expected. Not sure what your use case is, maybe these translations are part of a scope and you are missing the prefix?
I've tried it on our playground you can clone and try it yourself (clone this repo to run it)
I've added the following to the assets/i18n/transpilers/messageformat/en.json:
{
"messageFormat": "The {gender, select, male {boy named {{mf.testKey}} won his} female {girl named {{mf.testKey}} won her} other {person named {{mf.testKey}} won their}} race - English",
"testKey": "🤡",
}

Note that the keys are prefixed with mf as this is the scope's alias.
And the result:

If you need further assistance please use our gitter channel or github discussions 🙂


Optional template?

I've encountered this pattern where I'm having an optional configuration block:
foo:
  x: false
  y: 42

In my template, I'm currently writing confuse.OneOf([None, dict]), but it's not really exactly right. This still requires foo: null in my config. What I want is an optional template where I can skip the definition of foo entirely. How would I do that?

Is the idea that both x and y are optional, or that they need to be specified together?
If the former, you can just access the individual fields, like config['foo']['x'].get(). Does that help at all?

Sorry if I wasn't clear, I used x and y only as dummy variables underneath foo. I was trying to figure out how to make foo optional, as opposed to x and y. So either the entire block should be there or it shouldn't matter if it's absent. Does that make sense? How would I describe that in a template?

I see! For the non-optional case, the right thing to use here is MappingTemplate—I assume you've tried that, right?
I think all that's needed to make the optional behavior work is to add a default option to MappingTemplate. If you take a look at the other Templates we have built in, such as String and Choice, you can see how that works. It may even be possible to get this behavior without modifying the Confuse source by assigning to the default field on the template "manually."

I see! For the non-optional case, the right thing to use here is MappingTemplate—I assume you've tried that, right?

Actually, no. I tried to skim the example but couldn't find a usage example.
Here's what I was looking for:
template = (
  'foo': confuse.Optional(dict)
)

If this existed, it would be okay to write a config with foo as dict or write a config without a foo key. That's what I'm trying to express. By using confuse.OneOf([None, dict]), I have to write foo: null in my config and cannot simply omit it. Otherwise config = lazy_config.get(template) will fail.
From a user perspective, I could now write config.foo and would know that it's either None or dict.

Indeed; it doesn't seem to be documented. Can I ask you the favor of forging ahead anyway, even if it means crossing into undocumented territory? Something like this should work:
map_tmpl = confuse.MappingTemplate({'x': some_template, 'y': other_template})
map_tmpl.default = None
template = {'foo': map_tmpl}

Thanks, this was helpful. With a slight tweak, I have now exactly what I want:
def optional(type):
    template = confuse.as_template(dict)
    template.default = None
    return template

This I can now use as follows:
template = (
  'foo': optional({
    'x': optional(str),
    'y': optional(int),
  })
)

It's super flexible: not only top-level records can now be optional, but also fields within mappings.
If this use case is convincing enough for you, I would propose that confuse.Optional for that 😉. From my side, this issue is resolved.

Actually, it doesn't quite work as expected, because foo was still defined. This worked though:
class OptionalMappingTemplate(confuse.MappingTemplate):
    def __init__(self, mapping):
        subtemplates = {}
        for key, typ in mapping.items():
            template = confuse.as_template(typ)
            template.default = None
            subtemplates[key] = template
        self.subtemplates = subtemplates
        self.default = None
    def value(self, view, template=None):
        out = confuse.AttrDict()
        for key, typ in self.subtemplates.items():
            x = typ.value(view[key], self)
            if x:
                out[key] = x
        return out if out else None

def optional(xs):
    return OptionalMappingTemplate(xs)

I really just hacked this together, there's probably a cleaner way to do it.

Aha! Yes, that looks a little more involved—but glad you figured it out!!


Improve protocol tests

The protocol unit tests currently include huge copypasted bytestrings that are hard to make changes to or reason about. To make these tests easier to read and write, we can make a utility that can turn this
"""
00 00 00 00 00 01 00
dummytopic
00 00 00 0c
testuserdata
"""

into this:
bytearray(b'\x00\x00\x00\x00\x00\x01\x00\ndummytopic\x00\x00\x00\x0ctestuserdata')

In other words, the utility trims whitespace and converts \b\d\d\b to the hex equivalent. This kind of utility pays off quickly for writing tests when developing protocol drivers.

What's the rule around the newlines? There's a newline in the bytearray example but it only seems to happen once, whereas the string has many newlines, so I'm wondering how to handle it.

@giulianob The example in the beginning of this issue breaks up these bytestrings into the parts denoted in the protocol documentation. The newline you see in the bytearray example isn't actually a newline, it's just some byte sequence representing the length of the string dummytopic that happens to also be the ascii code for \n (the number 10 represented as a bytestring).
Instead of writing a utility, this change can actually be as simple as taking a test that looks like this
bytearray(b'\x00\x00\x00\x00\x00\x01\x00\ndummytopic\x00\x00\x00\x0ctestuserdata')

and reformatting it as this
bytearray(b'\x00\x00'  # version
                b'\x00\x00\x00\x01'  # len(topic names)
                b'\x00\n'  # len(topic name)
                b'dummytopic'  # topic name
                b'\x00\x00\x00\x0c'  # len(user data)
                b'testuserdata')  # user data

by using this specification as a reference:
ProtocolMetadata => Version Subscription UserData
  Version => int16
  Subscription => [Topic]
    Topic => string
  UserData => bytes

Ok makes sense. I guess it would make more sense to write it as \x10 instead of a newline. So do you guys just want to format it and not have this utility? It's a bit more readable as a single string with standard hex formatting but its not native Python.

I'm in agreement with @rduplain here that we should stick with python-formatted bytestrings. Also, the \n is formatted as such because it was copypasted directly from a str(repr(msg)) in pdb. If formatting it as \x10 would work here (which I assume it would), that's certainly preferable for readability.
@giulianob If you'd like to work on a pull request for this, it would be pretty straightforward to get merged quickly.

@giulianob I'm going to grab this since I haven't heard anything here.

Sorry about that. Have been working on some other things.
On Mar 24, 2016 11:41 AM, "Emmett J. Butler"<EMAIL_ADDRESS>wrote:

@giulianob https://github.com/giulianob I'm going to grab this since I
haven't heard anything here.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/Parsely/pykafka/issues/475#issuecomment-200892099

Thanks a bunch for jumping in, @giulianob!


Tuple unions are not working correctly

This throws both when I use the tuple length and when I use the elements within the tuple to figure out which kind of tuple it is:
https://flow.org/try/#0PQKgBAAgZgNg9gdzCYAoVAXAngBwKZgAqArjjHgDJ4B2A5hgBYCMYAvGANpMC6A3JrgIkylGvQYAmNpwAMAGjA9+2fEVLkAsgEMsAIwLth5KnUYsAPmpEnxE-qgDGcagGcMYDOrwAuK5p360hzyinyOzm5gAG5aMMR4LOyeIgB05KYMbKzsLAD8Hl7B3GC+yeRcYU6u7jFxeFJJhTLF2Tlg+WV4RSUFIhW8QA
I would think this should work both ways I'm trying it.

Duplicate of #4556

I've got a PR for this over at https://github.com/facebook/flow/pull/5048. Unfortunately the maintainers don't seem interested.

Yeah, something tells me the Flow team and the Prepack team are just planning to come out with a joint package of some kind so focus is on that rather than on the little things.  Their long-term goals appear to be fairly similar.
Long Term — leveraging Prepack as a platform

JavaScript Playground — experiment with JavaScript features by tweaking a JavaScript engine written in JavaScript, all hosted just in a browser; think of it as a "Babel VM", realizing new JavaScript features that cannot just be compiled away
Bug Finding — finding unconditional crashes, performance issues, ...
Effect Analyzer, e.g. to detect possible side effects of module factory functions or to enforce pureness annotations
Type Analysis
Information Flow Analysis
Call Graph Inference, allowing inlining and code indexing
Automated Test Generation, leveraging the symbolic execution features in combination with a constraint solver to compute inputs that exercise different execution paths
Smart Fuzzing
JavaScript Sandbox — effectively instrument JavaScript code in a way that is not observable

Source - PrePack Roadmap

Duplicate of #4556


Move needed build packages to "dependencies"

Heroku (and soon Franklin) runs NODE_ENV=production npm install which doesn't install any packages listed in devDependeices.

Fixed by #22


Can this boiler plate be used for making API's?

I tried putting simple get request, which seems to work, but the server is not automatically restarted upon any code change.
Can anyone recommend me if it is good to use this also as an api and also solution to restart server upon change (used nodemon, but iseems to restart multiple times for 1 change which is weird).
Any help is much appreciated !
Thank you

I am using this as an API for one of my projects. Using nodemon works good for me. Make sure you ignore the app dir for nodemon as webpack middleware will take care of hot reloading the front-end. The idea is to use nodemon to only observe changes in server dir.
Here's my start script, if it helps, ignore the irrelevant parts.
"start:local:watch": "cross-env NODE_ENV=development nodemon --ignore /app/ run-s start:local"


VB.NET support

Issue
Expected Behavior:
VB.NET should be in the list of programming languages like c#
Actual Behavior:
VB.NET is not in the programming list
Reproduction Steps:
just type vb.net or visual basic with no result

Hello @unwaged,
Templates are stored here: https://github.com/toptal/gitignore/tree/master/templates
If you cannot find what you're looking for feel free to open a PR to add a new template.


Use a function to wrap git

This allows bash-powerline to work on macOS, which has Bash 3.

@riobard Are you accepting PRs in this repo?

Could you please explain a little bit why this PR is needed? The current code works with Bash 3 on macOS.

@riobard No, the current code does not work on macOS with Bash 3. That is why I submitted this PR. The current code silently fails, looking for a binary with name "env LANG=C git".

That's strange. What's the version of your macOS and its bash?

Bash is "3.2.57(1)-release (x86_64-apple-darwin18)" and macOS version is 10.14.5.

Easy to repro:
$ prog="X=Y ls"
$ $prog
-bash: X=Y ls: command not found

No, you're doing it wrong. Try cmd="env LANG=C git and run $cmd. It definitely works unless your $PATH is screwed.

$ cmd="env X=Y ls"
$ $cmd
-bash: env X=Y ls: command not found

I guess your bash might be misconfigured.
bash-3.2$ uname -a
Darwin Mac-mini 18.6.0 Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64 x86_64
bash-3.2$ bash --version
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin18)
Copyright (C) 2007 Free Software Foundation, Inc.
bash-3.2$ cmd="env LANG=C git"
bash-3.2$ $cmd --version
git version 2.20.1 (Apple Git-117)
bash-3.2$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin


Error when using snippet

I try to use the snippets and it's working but just after I press enter to select a snippet from cmp I have an error and after the error I don't have snippet in cmp
E5108: Error executing lua .../pack/packer/start/LuaSnip/lua/luasnip/nodes/snippet.lua:66: bad ar
gument #1 to 'ipairs' (table expected, got nil)
stack traceback:
        [C]: in function 'ipairs'
        .../pack/packer/start/LuaSnip/lua/luasnip/nodes/snippet.lua:66: in function 'init_nodes'
        .../pack/packer/start/LuaSnip/lua/luasnip/nodes/snippet.lua:297: in function 'fn'
        ...k/packer/start/LuaSnip/lua/luasnip/nodes/dynamicNode.lua:134: in function 'update'
        .../pack/packer/start/LuaSnip/lua/luasnip/nodes/snippet.lua:813: in function 'update'
        .../pack/packer/start/LuaSnip/lua/luasnip/nodes/snippet.lua:504: in function 'trigger_exp
and'
        ...nvim/site/pack/packer/start/LuaSnip/lua/luasnip/init.lua:227: in function 'snip_expand
'
        ...e/pack/packer/start/cmp_luasnip/lua/cmp_luasnip/init.lua:143: in function 'execute'
        .../nvim/site/pack/packer/start/nvim-cmp/lua/cmp/source.lua:378: in function 'execute'
        ...e/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/entry.lua:472: in function 'execute'
        ...re/nvim/site/pack/packer/start/nvim-cmp/lua/cmp/core.lua:469: in function <...re/nvim/
site/pack/packer/start/nvim-cmp/lua/cmp/core.lua:468>
        ...te/pack/packer/start/nvim-cmp/lua/cmp/utils/feedkeys.lua:47: in function <...te/pack/p
acker/start/nvim-cmp/lua/cmp/utils/feedkeys.lua:45>

Neovim v0.8 and last version of LuaSnip.
My configuration:
require("go").setup({
  luasnip = true,
})

which snippet you are using when the error occurred?

ret and ife. I never tested the others yet.

FYI, some snippets works without any errors.

May it be you did not install treesitter?
Do you get warnings when you run checkhealth?

I have treesitter and checkhealth is ok.
I've just updated all my plugins and it seems working :thinking: