Response does not appear?

We've attempted to respond to a customer review but find that the response does not appear in the store. The response appears in the Partner page, where there is an "update your response" button, but clicking that produces a "you cannot respond to this review" message. Is this undoable? Would like readers to know we've responded.

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

ID: 179cbc73-e5ec-0ecd-b3d8-968ee593905c
Version Independent ID: 4b0e61f6-8b6a-fc8f-91bd-792ab97fef53
Content: Respond to customer reviews - UWP applications
Content Source: windows-apps-src/publish/respond-to-customer-reviews.md
Product: uwp
Technology: publish
GitHub Login: @hickeys
Microsoft Alias: hickeys

Thanks for reaching out with your feedback. GitHub issues in this repo are for documentation bugs only, and unfortunately this seems more like a support request than a documentation bug.
The best way to get support is by asking the community on Microsoft Q&A or StackOverflow
For completeness' sake, here is a list of developer resources:

Microsoft Q&A offers relevant and timely answers to your technical problems from a community of experts and Microsoft engineers.
For community assistance with development questions, there are our forums, and StackOverflow.
The Windows developer support site explains other support options.
The Visual Studio developer community is available, and responsive. The former User Voice feature is now there on the Suggest a feature tab, if you want to lobby for a change, a feature, or to make a suggestion.
For developer issues, or suspected product bugs, there's Microsoft Support; a support engineer will look at the repro and see whether the issue is a Microsoft product bug, or something else. If it's a bug with a Microsoft product then the ticket will be free of charge.

If you receive assistance via any support resource and you believe that information would help us improve the docs, then please let us know or consider submitting a pull request.
Thanks,
Shawn


Not  booking appointment

When it finds an open appointment it isn't booking it

Can you try the newest release of the software?
Type git pull on the console/terminal or just delete the project and create it again (replit)

I tested on the newest release and can get the appointment


Parse modified date

What format are the _modified and _created fields in collections ? I'd like to include them in a project.

They're a unix timestamp

Awesome - Thank you!


Distance Measurements are not counting a line segment

When selecting Show Measurements, the Distance measurement is not including the distance for one of the line segments in the polygon.  For example, if you Draw a rectangle and Show Measurements, the Area measurement is correct but the Distance measurement has only calculated 3 of the 4 sides.  Similarly with a Triangle, the Distance measurement will only calculate 2 of the 3 sides.  I noticed the same thing with a Polygon as well where I created a polygon with 7 line segments and the Distance measurement only calculated the first 6 line segments, so the Distance is incorrect for any polygon when comparing the same distance against the Measurement widget.

Thanks for the modification.
The pull requests is merged


Consider automating machine setup with Chef or something

It may make more sense to move to a model where we have scripts that take a clean machine and install all the required software on the CI machines instead of the model where we do brain surgery on a VM and then capture a new image.
This would make the stuff installed on a machine explicit and we could version it in this repo.

I think if we did it this way we might also be able to force the windows workers to auto-login as part of the setup script.

+1
It's hard to keep documents about that kind of brain surgery up to date.
(e.g. https://github.com/dotnet/coreclr/blob/master/Documentation/building/linux-instructions.md)


anemone_string_to_i64: Fix UBSAN warning

When value was signed some of the operations caused an overflow into the sign bit. By making it unsigned and then casting it to signed, the warning goes away.
I wonder if we need to be concerned about value overflowing? Should an error be returned?
! @amosr @jystic

ah yeah, so I have a fix that checks for overflow in #43, but wanted to do more regression benchmarks and clean up the SIMD code before

Ah ok. It might be nice to have a property test like (haven't compiled this):
prop_convert_or_error :: Property
prop_convert_or_error =
   QC.forAll (QC.choose (- bigNnmber, bigNumber) $ \ integer -> do
     let str = parseAsInt64 (BS.pack $ show integer)
     let parsedResult = parseAsInt64 str
     if integer > minBoundInt64 && integer < maxBoundInt64
        then parsedResult === Right integer
        else parsedResult === Left OverflowError
  where
    bigNumber = 0x10000000000000000 :: Integer -- larger than maxBound :: Word64
    maxBoundInt64 = fromIntegral (maxBound :: Int64) :: Integer
    minBoundInt64 = fromIntegral (minBound :: Int64) :: Integer

This was fixed as part of:
commit 0662ff15dc0c8602e9285590e32b19dc479e0690
Author: Amos Robinson<EMAIL_ADDRESS>Date:   Fri Feb 17 17:28:17 2017 +1100

Closing.


Doc: Add tuntap option description in mlvpn.conf man

A small doc addition.
By the way, thanks for your project, I have been searching for an ADSL / VDSL aggregation solution for a long time, and yours works perfectly.

Thank you


my Notepad++ can't update/install this plugin

Maybe because no binaries here ?

https://github.com/kapilratnani/JSON-Viewer/releases
binaries are here...


Remove bindgen dependency

Added static bindings (generated by bindgen) and deleted the bindgen dependency. I used bindgen from the master branch, so the 32bit problems are fixed.
Closes #1, closes #3

Awesome! Thanks!


PropelOnDemandFormatter formatter broken when using single table inheritance

Hydrating fails when single table inheritance is being used. The bug is in PropelFormatter::getWorkerObject which ignores the $class we're trying to hyrdate.
I added the following code to BookstoreDataPopulator::populate:
$bemp3 = new BookstoreCashier();
$bemp3->setName("Tim");
$bemp3->setJobTitle("Cashier");
$bemp3->save($con);

New test:
public function testFormatSingleTableInheritanceManyResults()
{
	$con = Propel::getConnection(BookPeer::DATABASE_NAME);
	BookstoreDataPopulator::populate($con);

	$stmt = $con->query('SELECT * FROM bookstore_employee');
	$formatter = new PropelOnDemandFormatter();
	$formatter->init(new ModelCriteria('bookstore', 'BookstoreEmployee'));

	$employees = $formatter->format($stmt);

	foreach ($employees as $employee) {
		$row = array();
		$row[1] = $employee->getClassKey();

		$omClass = BookstoreEmployeePeer::getOMClass($row, 0, false);
		$actualClass = get_class($employee);

		$this->assertEquals($omClass, $actualClass, 'PropelOnDemandFormatter::format() should handle single table inheritance');
	}
}

Running phpunit testsuite/runtime/formatter/PropelOnDemandFormatterTest.php
1) PropelOnDemandFormatterTest::testFormatSingleTableInheritanceManyResults
PropelOnDemandFormatter::format() should handle single table inheritance
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-BookstoreCashier
+BookstoreEmployee

/var/www/workspaces/slangley/propel/test/testsuite/runtime/formatter/PropelOnDemandFormatterTest.php:169

FAILURES!
Tests: 8, Assertions: 120, Failures: 1.

@shane-l: Could you prepare a PR with your fix and a unit test?


feat(cli)!: add --write-transformed option, disable source write back by default

Hello,
this humble PR adds --update-source --write-transformed flag for @unocss/cli used to toggle overwriting source files with transformed code. It is enabled by default to preserve the current behavior, but can be disabled in case another tool takes care of transforming utility classes on the HTML side.
Background:
I'm trying to make UnoCSS work with Rust frameworks preferably without trade-offs like dropping Variant Groups. I've made a little macro for that purpose and hopefully it will evolve someday to be executed on a WASM bundler side rather than polluting source code.
Regardless of the final approach to rendering valid HTML classes, keeping the source files not-transformed is desirable. Otherwise the Variant Groups feature isn't really much of use :)

Would it be better to output transformed files instead of overwriting source files?


Problems with locale

http://cdash.openms.de/testDetails.php?test=56856527&build=312104
On windows a number 123.456 gets converted to 123456. potentially a problem with locale.
The ! Indicates the mismatch between test file an reference created on linux

Offending lines:			(tab_width = 8, first_column = 1)
in1:  C:\jenkins\ws\openms_pr_ci\979a8a2f\build\src\tests\topp\ginkgotoxin-ms-switching_out_tmp.mzML   (line: 72, position/column: 64/65)

in2:  C:\jenkins\ws\openms_pr_ci\979a8a2f\source\src\tests\topp\THIRDPARTY\ginkgotoxin-ms-switching_out.mzML   (line: 72, position/column: 64/65)

@timosachsenberg can you provide the file example for testing?

HI. https://github.com/OpenMS/OpenMS/blob/a02db7a7e2b6b8dd18fdd2c0a52907fc36ded02c/src/tests/topp/THIRDPARTY/ginkgotoxin-ms-switching.raw
@jpfeuffer do you know if we run german windows on the test machine?

Yes the region and language settings are set to German.

Looks like a problem in the Thermo API.

Hi @timosachsenberg I notice the same problem on machine with belgian locale. I'll try to fix it and get back to you.

@nielshulstaert I have check the error yesterday. In this line https://github.com/compomics/ThermoRawFileParser/blob/master/Writer/MzMlSpectrumWriter.cs#L837 we capture the Injection time as String from thermo api. Then, probably the error is in thermo API side? I have contacted Jim about this. What do you think?

I think the problem is on our side, the String from the thermo api is depending on the locale (comma or point as decimal separator) so I should be able to fix it.

Hi @timosachsenberg I released a new version (1.1.5) can you test it? Thanks for trying out the library.

will do. Thanks for the quick fixes!


That add-on plan is only available to select users.

I get this error when trying to set up on Heroku using the button: "That add-on plan is only available to select users."
Any ideas on how to solve this?

@boetter Which add-on plan is that. Do they say?

@olivierlacan they don't say:

Since we have @craigkerstiens around, perhaps he knows. :kissing_cat:

I'm initially stumped but will poke around some and report back

Actually looks like heroku-postgresql has been updated to heroku-postgresql:hobby-dev

@craigkerstiens Alright, I'll update it then. :-)

Looks like the issue still exists even though the add-on plans look right?

alright,thanks your proposal @craigkerstiens

@rwdaigle Sorry about that. I'll fix it in master right now.


Update README.md

Fixed broken link to the API ref documentation

This PR has been open for a while. Can we merge it or close it?


Fix dependabot

Overview of PR

add docs package for scan scope
remove unneeded target branch options

Technical & Architecture Changes

TODO

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Tests hang forever after interface idle for some time

I have only done this on a single computer yet so I'm not sure if it's reproducible on other networks/PCs/OSes, etc.
On Ubuntu 19.10.
Commit is e15091165ed76c846fa6b1381ef29ef3e83a8250
Reproducable by:
cargo test; echo "WAITING 10 min"; sleep 600; cargo test; echo Success!

The last line will never be echoed, as the second test will hang forever.
First test finishes instantly.

I'm not sure if it's the time. When I run the tests repeatedly, they lock up sometimes. I suspect there's some race condition or maybe it doesn't perform well if packets are lost on the interface :shrug:.
Anyway, this crate really is not at the very top of my priority list, it might take some time before I get to this. So if you could have a look at what might be happening (maybe strace would help), it would be great.

Ok (sorry for late reply)! Same for me, might take a while until I need the functionality from this crate.
But unless fixed I'll be happy to take a look when I get around to it.

Quick update. Tried this again, but with Wireshark (I don't recall if I had Wireshark running when I reported this).
I saw that when the test hangs there is an ICMP Destination unreacable (Host administratively prohibited).
And using dmesg --follow showed that my firewall was actively blocking those (but only sometimes?!).
I haven't been able to have the tests fail after allowing all traffic in the tun10 interface.
Could it be the same issue for you?
If yes then there might not be an issue.

I didn't find the time to look at it more since then, but I'm pretty confident nothing manipulates my firewall and the ports should be the same each time.

I have using the TAP parts of this over the weekend and captured >1 000 000 packets without problems.
Feel free to close this if you want.

I'll keep this open for now. If my gut feeling is right, it's a problem in the test, not in the actual library code.


Relative include paths into source dir

There are a lot of places in the code where the following pattern of including paths outside the current dirs directory tree is used.
https://github.com/dmlc/xgboost/blob/82ee2317e80f93465685529e1ab9acff52b683c7/include/xgboost/data.h#L22-L24
https://github.com/dmlc/xgboost/blob/82ee2317e80f93465685529e1ab9acff52b683c7/include/xgboost/gbm.h#L24
I think this is very bad practice and I don’t understand the rational behind this.
E.g. if you think span.h is something considered a private implementation detail than it should get included only by *.cc  files within the src/ tree.
If you ever need to include this into some of the headers in include/ it’s probably not a private implementation detail anymore but something you need to share with who ever is using includes from the include/ dir. In that case span.h should also live in include/.
This anti-pattern repeats throughout a many sources, not only in xgboost, but also in rabit.

Yep.  It needs cleaning.

+1


High core temps on idle

Hello, first, thanks for this excellent work.
I have the same issue as has been reported by many others using the Jakeday kernel -- high core temps (70-88C) on idle and ~100C on load.
Everything else seems to work perfectly. Read all previous issues with other versions of the kernel and AUR package, but can't figure out the problem.

What device do you have? If you're on a SB2, have you checked you're booting into the right kernel (uname -a)?

Yes I'm on the SB2. I checked what kernel was booting and believe it's the correct one.
Linux surface 5.0.3-arch1-1-ARCH #1 SMP PREEMPT Tue Mar 19 13:09:13 UTC 2019 x86_64 GNU/Linux

5.0.3-arch1-1-ARCH is the generic Arch one. It should read something like 5.0.3-linux-surface. Have you updated your bootloader config?
In case of grub grub-mkconfig -o /boot/grub/grub.cfg should to the trick, assuming that is your config path. If you have grub, you might also want to consider installing https://aur.archlinux.org/packages/grub-hook/ so you don't have to do this every time you update the kernel.

Ah silly mistake on my part (as usual). Config wasn't updated properly. Thanks for your help.


flavor corrected

Looks good to me. I'm just wondering whether maybe naming the parameter sets p-I and p-III would be more sensible (instead of 95 and 160).
I don't really understand why github lists files that don't exist anymore as conflicts?

Hi, Thanks for the feedback. It looks to me more consistent to use numbers
(95,160) because on the other param folders and for all the schemes, the
files are named based on the number of bits.
-p-I and p-III mean provely secure level 1 and level 3.
Also for the failure probability, I couldn t find it out from the
documentation. S I left it 0. (for both schemes FALCON and qTESLA)
Am Do., 2. Apr. 2020 um 14:03 Uhr schrieb Marian<EMAIL_ADDRESS>
Looks good to me. I'm just wondering whether maybe naming the parameter
sets p-I and p-III would be more sensible (instead of 95 and 160).
I don't really understand why github lists files that don't exist anymore
as conflicts?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cryptoeng/pqdb/pull/38#issuecomment-607803752, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOQNZOL6PGK4OH6UDCOK3P3RKR5JDANCNFSM4LY7APLQ
.

--
Regards,

It looks to me more consistent to use numbers
(95,160) because on the other param folders and for all the schemes, the
files are named based on the number of bits.
-p-I and p-III mean provely secure level 1 and level 3.

ok, makes sense.

Also for the failure probability, I couldn t find it out from the
documentation. S I left it 0. (for both schemes FALCON and qTESLA)

Seems right. In the tesla paper, they don't talk about success probability (they define correctness as Pr[ verify(pk, m, σ) : σ = sign(sk, m) ] = 1 and then prove this), so it seems it is 100% correct (aka failure probability of 0). In Falcon I could not find such an explicit statement, but as they don't mention probabilities, I'd say it's the same situation.
(Anyway, for signatures, you could always check if the signature verifies, and if it does not, create another one with new randomness.)
Can you try and resolve the conflicts (should be git co qTESLA && git merge master), then I'd say we're ready to merge.

It seems I screw up while moving  between two branches .
How is it now?
Am Do., 2. Apr. 2020 um 18:12 Uhr schrieb Marian<EMAIL_ADDRESS>
It looks to me more consistent to use numbers
(95,160) because on the other param folders and for all the schemes, the
files are named based on the number of bits.
-p-I and p-III mean provely secure level 1 and level 3.
ok, makes sense.
Also for the failure probability, I couldn t find it out from the
documentation. S I left it 0. (for both schemes FALCON and qTESLA)
Seems right. In the tesla paper, they don't talk about success probability
(they define correctness as Pr[ verify(pk, m, σ) : σ = sign(sk, m) ] = 1
and then prove this), so it seems it is 100% correct (aka failure
probability of 0). In Falcon I could not find such an explicit statement,
but as they don't mention probabilities, I'd say it's the same situation.
(Anyway, for signatures, you could always check if the signature verifies,
and if it does not, create another one with new randomness.)
Can you try and resolve the conflicts (should be git co qTESLA && git
merge master), then I'd say we're ready to merge.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cryptoeng/pqdb/pull/38#issuecomment-607942704, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AOQNZOMKHFZAFQJU7CUKMFTRKS2QVANCNFSM4LY7APLQ
.

--
Regards,

@Soundes-M we reverted this PR. Please open a new PR to get the changes in.


Documentation down

Just letting you know the documentation is down. Any chance of getting it back up? @ranaroussi

@ranaroussi


V2 : Non-manifold vertices when extruding SVG or subtracting shapes

Expected Behavior
Extruding an SVG and subtracting a cylinder from a cube should result in manifold models. See SCAD code provided.
Actual Behavior
Extruding an SVG creates a model with non-manifold vertices. Same thing when subtracting a 2 cylinders from a cube. See JSCAD code provided. This leads to errors in PrusaSlicer.
Steps to Reproduce the Problem
The STL produced here is shown as having non-manifold vertices in meshlab.
const fs = require('fs').promises

const { geometries, primitives, booleans, extrusions, transforms } = require('../OpenJSCAD.org/packages/modeling')
const { svgDeSerializer, stlSerializer } = require('../OpenJSCAD.org/packages/io/io')

async function cast () {
	const height = 25.4
	const width = 12
	const depth = 22
	const scale = height/720
	const extrudeHeight = 1.32

	const shapes = svgDeSerializer.deserialize({
		output: 'geometry',
		target: 'path',
		segments: 100
	}, '<svg PXPMM="1" xmlns="http://www.w3.org/2000/svg"><path d="M258 108C280 168 301 260 314 403L258 403C252 338 243 259 228 194C210 255 190 330 176 403C222 435 268 471 268 575C268 703 199 707 184 707C145 707 94 674 94 557C94 522 99 473 107 419C63 391 22 354 22 238C22 97 75-2 151-2C167-2 194 1 223 39C240 13 259-3 279-3C288-3 299-2 306 1L311 54C284 53 268 84 258 108ZM155 582C155 629 162 651 180 651C202 651 210 617 210 575C210 512 192 480 166 458C159 503 155 545 155 582ZM154 65C102 65 85 193 85 249C85 299 98 330 118 354C136 262 162 164 193 94C182 76 169 65 154 65Z" /></svg>')

	const poly = booleans.union(shapes.map((shape) => primitives.polygon({ points: shape.points })))
	const polyLetter = transforms.scale([scale, scale, 1], poly)
	let letterShape = extrusions.extrudeLinear({ height: extrudeHeight }, geometries.geom2.reverse(polyLetter))

	const body = booleans.subtract(
		booleans.union(
			primitives.cuboid({
				size: [width, height, depth],
				center: [0, 0, 0]
			}),
			transforms.translateZ(depth/2 + extrudeHeight/2, transforms.center({}, transforms.mirrorX(transforms.mirrorY(letterShape)))),
		),
		transforms.translate([-2, height/2, 0], transforms.rotateY(1.5708, primitives.cylinder({
			height: width,
			radius: depth * 0.4,
			segments: 100
		}))),
		transforms.translate([-2, -height/2, 0], transforms.rotateY(1.5708, primitives.cylinder({
			height: width,
			radius: depth * 0.4,
			segments: 100
		})))
	)

	const stl = Buffer.concat(stlSerializer.serialize({ binary: true }, body).map((buff) => Buffer.from(buff)))

	await fs.writeFile('./test-manifold.stl', stl, 'binary')
}

cast()

Save this code as the test SVG file:
<svg PXPMM="1" xmlns="http://www.w3.org/2000/svg"><path d="M258 108C280 168 301 260 314 403L258 403C252 338 243 259 228 194C210 255 190 330 176 403C222 435 268 471 268 575C268 703 199 707 184 707C145 707 94 674 94 557C94 522 99 473 107 419C63 391 22 354 22 238C22 97 75-2 151-2C167-2 194 1 223 39C240 13 259-3 279-3C288-3 299-2 306 1L311 54C284 53 268 84 258 108ZM155 582C155 629 162 651 180 651C202 651 210 617 210 575C210 512 192 480 166 458C159 503 155 545 155 582ZM154 65C102 65 85 193 85 249C85 299 98 330 118 354C136 262 162 164 193 94C182 76 169 65 154 65Z" /></svg>

This is an equivalent SCAD code which produces a similar model (I couldn't find the resize method in JSCAD) which is shown as having 0 non-manifold vertices or edges in meshlab.
height=25.4;
width=12;
depth=22;

difference() {
    union() {
        scale([-1, -1, 1]) {
            linear_extrude(height=1.32) {
                resize([0, height, 0], auto=true) {
                    import("./test.svg", center=true);
                }
            }
        }

        translate([-12/2, -height/2, -depth]) {
            difference() {
                cube([width, height, depth]);
            }
        }
    }

    translate([4, -height/2, -depth/2]) {
        rotate([0,-90,0]) {
            cylinder(width, r=depth*0.4, $fn=100);
        }
    }

    translate([4, height/2, -depth/2]) {
        rotate([0,-90,0]) {
            cylinder(width, r=depth*0.4, $fn=100);
        }
    }
 }

Specifications

Version: 2.0.0-alpha2
Platform: macOS 10.14.6
Environment: Node.js v12.13.0

Maybe can you try to check measureArea(polyLetter) before to reverse it ? I suppose that correct boolean operations already need to have the points in the good order. I tried to run your code but didn't succeed as I didn't find the correct path to svg-deserializer.

Thanks for trying to run the code @gilboonet. This is a short version of the script just to reproduce the error, in this case, I know I need to reverse. Have you updated the require paths to match your install? I'm curious as to why the deserializer didn't work.

I didn't find the correct path for the svg serializer require, so I tried to open the svg directly (save the svg tag to a file, then require it ) and the resulting stl is ok in meshlab, 0 non-manifold faces.

Oh! That's interesting. Just from the screenshot I'm gathering you're running this in the browser so I did the same and exported an STL (both binary and ASCII) and put that through Meshlab and I'm finding fewer non-manifold vertices than through Node.js but it's still non-0.
I've attached a zip file containing 2 STLs, one from Node and one from the Web. Would you be able to send me the STL you generated so I can compare in Meshlab? Would be good to find out if it's Meshlab or if it's the generation which changes from Linux to macOS.

test-manifold-stl.zip

Sorry, yesterday I only checked non-manifold edges, when checking non-manifold vertices, I found some, It needed 3 passes to get rid of them all. So it's the same running from CLI or WEB. It may be the union that causes those errors, it's a big issue with jscad that I'm hoping V2 will overcome.

Great investigations! Thanks.
I'll look at this next week in more detail, as nothing is easy in the booleans.

I tried some workarounds but none allow me to remove all the non-manifold vertices.

measure each area in order to have only positives areas and build letterShape with subtract, but the resulting letter still has non-manifold vertices.
extrude separately positive areas and negative areas, adding height and moving it on Z to be sure that the subtract will be ok, still 76 non-manifold vertices remain after that. It may not be boolean operations that have an issue but extrusions.

I also tried to change the beziers by a huge linear polygon (with Inkscape), but the result had more than 700 non-manifold vertices.

Here's a simple test case...
  let geom2D = circle({radius: 10, segments: 8})
  let geom3D = extrudeLinear({ height: 30, twistAngle: Math.PI / 8, twistSteps: 5 }, geom2D)

Even this test case produces non-manifold vertices, which is shown in my analysis with red polygons.

Here's the cause... the walls of the extrusion will always be 100% accurate as the polygons (triangles) are constructed using the original vertices. However, the top and the bottom (caps) are created using intersectGeom3Sub(). This routine is determining the intersection between the walls and a large polygon, which will certainly produce new vertices. And those vertices will be sligthly different then those of the walls.
How different? It varies by not by much.

wall vertice ; [ -7.071067811865475, 7.0710678118654755, 10 ]
cap vertice ; [ -7.071067811865474, 7.071067811865481, 10 ]

Any questions?

OK. Continuing on...
In most cases, these small differences don't matter. The produced shape will be useable in other operations, even the boolean operations.
So, when does 100% accuracy matter?
I'm not sure actually. Many of the slicers will work just fine, and slice the 'solid' just fine. There are times when the slicer will complain, and typically a simple repair cycle will correct the issues.
If 100% accuracy is required then as mikolalysenko suggested, rounding of numeric values is required to snap the vertices together.

Here's my first attempt at a snap function.
const { vec3 } = require('@jscad/modeling').maths
const { poly3, geom3 } = require('@jscad/modeling').geometries

const EPS = 0.0000001

const snapVec3 = (v3) => {
  const x = Math.round(v3[0] / EPS) * EPS + 0 // no more -0
  const y = Math.round(v3[1] / EPS) * EPS + 0 // no more -0
  const z = Math.round(v3[2] / EPS) * EPS + 0 // no more -0
  return vec3.fromValues(x, y, z)
}

const snapGeom3 = (geometry) => {
  const polygons = geom3.toPolygons(geometry)
  const newpolygons = polygons.map((polygon) => {
    const newvertices = polygon.vertices.map((vertice) => snapVec3(vertice))
    return poly3.create(newvertices)
  })
  return geom3.create(newpolygons)
}

const snap = (geometries) => {
  return null
}

module.exports = { snap, snapGeom3 }

And the result..

I tried your snap function, changing the return line to return snapGeom3(body), but if the stl file size is a little bit smaller, the non-manifold vertices are still there. But I'm not sure I did it correctly.
and some of the snapped vertices are not rounded like :
[ 1.757766, -9.218522499999999, 11 ]

@gilboonet please try adjusting the EPS.
Also, there’s a new function called measureEPS() which will provide a value based on the dimensions of the shape.

I tried with 0.1 EPS and there are still 48 non-manifold vertices, but I altered the original code with my attempt to separe negative and positive parts.

I'm not sure actually. Many of the slicers will work just fine, and slice the 'solid' just fine. There are times when the slicer will complain, and typically a simple repair cycle will correct the issues.

The repair process of Prusa/Chitubox seems to sometimes cause artifacts which is really the only downside for me.
Thanks both for looking into this. The snapping makes sense to me and I wonder how SCAD does it because I've got the same script and it produces manifold models straight out the box.
Which non-manifold faces remained @gilboonet? I found that even without the extrusion, just doing the subtract of the cylinders on the cuboid resulted in some non-manifold models.

There are non-manifold vertices even when only extruding the svg and snapping.

@gilboonet and @MathieuLoutre thanks for the feedback. this is helping to find out the issues.
OK. Snapping is definitely going to help help bring vertices together. But it there's nothing to correct T-sections between polygons. For example, here's a simple extrude of a shape with a hole. You can see that the sides are polygons that span across the top edge. But the top is composed of triangles that only span part way. These are producing T-sections in the STL files.
There was an old function in V1 called fixTJunctions(). This doesn't exist in V2... yet.
/*
     fixTJunctions:

     Suppose we have two polygons ACDB and EDGF:

      A-----B
      |     |
      |     E--F
      |     |  |
      C-----D--G

     Note that vertex E forms a T-junction on the side BD. In this case some STL slicers will complain
     that the solid is not watertight. This is because the watertightness check is done by checking if
     each side DE is matched by another side ED.

     This function will return a new solid with ACDB replaced by ACDEB

     Note that this can create polygons that are slightly non-convex (due to rounding errors). Therefore the result should
     not be used for further CSG operations!
*/

@gilboonet do you know if meshlab has the ability to correct t-junctions in STL files?

@z3dev I tried to repair with Meshlab, but it creates holes that cannot be filled easily. It's the main reason that made me withdraw almost all my jscad devs involving boolean operations.

@gilboonet thanks.
i'll port fixTjunctions() and try with this example.

Hello, I stumbled upon this thread by looking into similar non-manifold issues that Prusa slicer is reporting on V2 geometries that I produce. I will try @z3dev snapVec3 suggestion on solids before they go to the STL export. I did not experience any problems for boolean operations as it was mentioned here as well, so I guess there's no need to use this method more often.  Just wanted to ask, I stumbled upon this file ensureManifoldness.js calling retessellate
https://github.com/jscad/OpenJSCAD.org/blob/e55eafb31fa257733ca7b36ef589d3acf0ab78c6/packages/io/io-utils/ensureManifoldness.js
but I couldn't find retessellate method in V2 branch, maybe retessellate did similar thing as snapVec3?

@bitbybit-dev thanks for looking at this.
retessellate.j is part of the booleans, and is called after each of the boolean operations. It’s a totally different algorithm to merge small polygons in the same plane.
I have a fix for extrudeRotate, and testing now.

@MathieuLoutre
@gilboonet
@bitbybit-dev
There are some changes as part of a new pull request #743 which address this issue (and more).
If you have a local copy of V2 then the changes can be obtained via
git checkout v2-fix-t-junctions
No other changes are required.
There's a new class of functions called 'modifiers'.
const {snap, generalize} = require('@jscad/modeling').modifiers
And the generalize function has a bunch of options, which can be used to 'modify' the geometry before exporting. Or used to modify geometry within a design.
const fixed = generalize({snap: true, simplify: true, triangulate: true, repair: true}, my3Dshape})
The plan is to integrate generalize into the IO libraries, which should fix some of the issues with manifold meshes in STL, AMF, etc files.
Please try this function if you have time. Any feedback would be appreciated.

Before:

After:

but I couldn't find retessellate method in V2 branch, maybe retessellate did similar thing as snapVec3?

It's still there, but only applied after boolean operations. See modeling/src/operations/booleans/*
The retessellate does not snap. It's retessellates co-planar polygons by rebuilding the faces. It's super hard to understand, and possibly unnecessary given that the set of polygons is typically very small (My opinion).

Hi @z3dev! Thanks for this, it looks really great. I can see it's already reduced the number of non-manifold vertices and edges. Do you already know what's the cause of the remaining ones?

Hi @z3dev! Thanks for this, it looks really great. I can see it's already reduced the number of non-manifold vertices and edges. Do you already know what's the cause of the remaining ones?

Probably my bad code. 😃
I’ll take another look at this later. There are some pressing issues to fix before V2 can be released properly, which I would like to address now.

Thanks for letting us know @z3dev and also for working on it! I'm 3D printing things with V2 just fine, Cura complains a little, but heals everything. Good to know that you'll look at it later.
Made this vase with Chain Hulls, such a nice feature
https://www.instagram.com/reel/CHp5ye3lHYa/
Cheers!

Thanks for letting us know @z3dev and also for working on it! I'm 3D printing things with V2 just fine, Cura complains a little, but heals everything. Good to know that you'll look at it later.
Made this vase with Chain Hulls, such a nice feature
https://www.instagram.com/reel/CHp5ye3lHYa/

Wow! That is sooooooooo cool! 😎
Please share more with them the user group.

Thanks, glad you like it, it means a lot, will share on the user forum.
Sorry to spam the issue comment with this, hope you don't mind. I try to
resist, but I really enjoy JSCAD and that sometimes gets me carried away
from the topic at hand :)
Matas

@MathieuLoutre @gilboonet just an update...
I ported the old fixTJunctions() to V2, and found out a few things. This function actually injects points into polygons if a T junction is detected (It doesn't fix anything!). And putting that together with snap() and improved triangulate(), the results are much better.

I was able to fix the issues with single passes in Meshlab.

More improvements today, as the triangulation logic has been changed. I think this will be the final version.

Note: MeshLab... unified vertices.

@MathieuLoutre
@gilboonet
@bitbybit-dev
The latest release of V2 JSCAD has fixes for this issue. Please try your designs again, and export to STL. I hope that there are vast improvements in the mesh being exported.
Please post back and results. 😃

Hey @z3dev, I've just updated and tried few of the models and indeed I'm getting way fewer repairs in Prusa slicer! Thx for these updates. I'll try to do more detailed tests later. Have to round up one large release...

@bitbybit-dev ... a relatively unrelated hint that I would like to share:
When I had models from jscad or elswhere that would be broken in prusa slicer (even after repair), the builtin "3D Builder" in windows fixed the model in those cases.

There was a recent fix to the snap() function. Please test with the latest and greatest.


kubectl version --short is not working on Client Version: v1.28.4 Server Version: v1.28.1

What happened: $ kubectl version --short
error: unknown flag: --short
See 'kubectl version --help' for usage.
What you expected to happen: As per documentation https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#version, kubectl version --short command should return just the version number.
How to reproduce it (as minimally and precisely as possible):
Install Client Version: v1.28.4 Server Version: v1.28.1 and run 'kubectl version --short' command
Anything else we need to know?: NA
Environment:

Kubernetes client and server versions (use kubectl version): Client Version: v1.28.4 Server Version: v1.28.1
Cloud provider or hardware configuration: AWS
OS (e.g: cat /etc/os-release): CentOS7.9
Containerd latest

@nitinjagjivan 1.27 was printing a deprecation warning:
kubectl version --short
Flag --short has been deprecated, and will be removed in the future. The --short output will become the default.
Client Version: v1.27.4
Kustomize Version: v5.0.1
Server Version: v1.26.6-gke.1700

Maybe the docs haven't been regenerated for this version?

Thank you, @andrelaszlo . I've updated my script to utilize kubectl version --output=json. I hope the documentation will be revised to reflect this soon.

Yes, doc needs to be updated;
/transfer kubernetes
/sig docs
if I'm wrong with respect to appropriate sig, please correct me.


Databricks workflow with SQL Warehouse Pro crashes with http error 503 with version 1.7.4

Describe the bug
A workflow dbt job terminates with an error Max retries exceeded with url: ... (Caused by ResponseError('too many 503 error responses')) just when it starts sending SQL commands to the cluster.
This occurs only in connector version 1.7.4, not in version 1.7.3.
This occurs only with SQL Warehouse, not with SQL Warehouse Serverless
Steps To Reproduce
The problem occurs in a workflow in a databricks workspace with the following settings
Running on Azure, Databricks Premium, not Unity Catalog
Job cluster single node Standard_DS3_v2
Work cluster SQL Warehouse Pro X-Small, Cluster count: Active 0 Min 1 Max 1, Channel Current, Cost optimized
git source Azure Devops
Settings for library version dbt-databricks>=1.0.0,<2.0.0
Start the workflow. After the job cluster has been created and the SQL Warehouse has been started an error is shown in the log:

dbt build --profiles-dir ../misc/misc/ -t prod -f
02:09:19  Running with dbt=1.7.5
02:09:20  Registered adapter: databricks=1.7.4
02:09:20  Unable to do partial parsing because saved manifest not found. Starting full parse.
02:09:38  Found 393 models, 88 snapshots, 1 analysis, 5 seeds, 1443 tests, 109 sources, 8 exposures, 0 metrics, 920 macros, 0 groups, 0 semantic models
02:09:38
02:12:11
02:12:11  Finished running  in 0 hours 2 minutes and 32.34 seconds (152.34s).
02:12:11  Encountered an error:
Runtime Error
HTTPSConnectionPool(host='[removed]', port=443): Max retries exceeded with url: /sql/1.0/warehouses/[removed] (Caused by ResponseError('too many 503 error responses'))

Changing to SQL Warehouse of type Serverless, X-Small, Cluster count: Active 0 Min 1 Max 1, Current solves the problem.
Running on older version of dbt-databricks library solves the problem (dbt-databricks>=1.0.0,<1.7.3)
The problem appeared on Jan 25 when the version was updated from 1.7.3 -> 1.7.4.
I have not been able to reproduce the same problem when starting dbt interactive, just as a workflow, but that can be my mistake, this has been a stressful couple days due to this.
Expected behavior
Log output:
02:08:27  Running with dbt=1.7.5
02:08:28  Registered adapter: databricks=1.7.3
02:08:28  Unable to do partial parsing because saved manifest not found. Starting full parse.
02:08:46  Found 393 models, 88 snapshots, 1 analysis, 5 seeds, 1443 tests, 109 sources, 8 exposures, 0 metrics, 919 macros, 0 groups, 0 semantic models
02:08:46
02:14:30  Concurrency: 12 threads (target='prod')
02:14:30
02:14:31  1 of 1835 START sql table model staging.rollup12helper ......................... [RUN]
02:14:31  2 of 1835 START sql table model staging.rollup24helper ......................... [RUN]
Screenshots and log output
N/A
System information
dbt 1.7.5
dbt-databricks 1.7.4
Configured in a dbt workflow, not much control over settings there.
Additional context
N/A

Thanks for the report, @OlofL. Could you elaborate a bit on what kind of workload you're running? Is your model generating a regular table, streaming table, materialized view, or something else?

Of course. It is our standard daily build and it starts by creating table models, seeds then 88 different snapshots and then continuing with lots of incremental models, a few table models and finally a a number of views.
We have two workspaces, one is using Serverless, one is using Pro SQL Warehouses. The problem only occured in the Pro. By swithcing to Pro instead of Serverless in the other the problem occured there also.

No streaming tables, just a plan batch transformation.

job.txt
Attached is the job definition yml with the sensitive data removed. Changing dbt-databricks library to less than 1.7.3 is the workaround we have found works.

The combination of things working when switching to serverless or 1.7.3, as well as the failures giving up after < 3 minutes suggests to me that something has changed in our retry policy in databricks-sql-connector 3.0.1 (which we upgraded to with 1.7.4).  Going to work with @susodapop to try to figure out what is different.

Great! Since we are able to recreate the problem in both our environments I'm happy to help with any further testing if possible.

@OlofL if you can get your dbt artifacts to me from one of the failed runs (either file a ticket with your Databricks contact, or you can email it to me at ben.cassell@databricks.com), that would be very helpful.

I can get it from our second environment, so it is in your mailbox now

@OlofL do you see this issue at all with 1.7.3?  I'm able to repro the failure this morning with 1.7.3 :/.

Great that you can replicate it. We have only seen it in 1.7.4, not in 1.7.3.
But, to be on the safe side we have the settings to <1.7.3, so we are not running version 1.7.3 in our daily build, we are running an earlier version.
I can try it again tomorrow with version 1.7.3 if that helps to make sure it is the same problem.

We are also experiencing the same issue with 1.7.4, but not with 1.7.3.  1.7.4 works OK if the SQL Warehouse is already running - but if the workflow has to start the SQL Warehouse that is when we encounter the 503 error.
Adding retries to the task is another workaround for us at this point.

Even after upgrading to 1.7.5, I'm still facing the same bug as described in this issue. I get the exact same error message as above.
1.7.3 is working fine for me.
Does 1.7.5 resolve the issue for you @OlofL @andrewpdillon ?
  If you'd like to help validate our latest attempt, can you try installing from the 1.7.4testing branch?

@OlofL @andrewpdillon @henlue any update?  I'm looking for feedback that this branch resolves the issue before I release it, as this circumstance is very hard to repro internally.

I configured a new workflow with 1.7.4 to first verify that I still had the error but I didn't get it this time. Is the error dependent on a specific version of dbt? I will try again.

No, whether you see the error or not is dependent on how quickly compute is available, hence why reproducing is so hard; it is a function of the cloud providers compute availability.

Ok, that explains a lot! I will try to setup som jobs in timer, but I suspect that the next bottleneck for Azure will be around the first of March, that is typically when Azure is being bogged down.

Yeah, for me, I have the best luck reproducing at 4:30 pm PST, and I have no idea why lol.

That is when we in Europe start all our major workloads, at 01.30 CET.

I have the same issue but with an older version of dbt: 1.4.9. In my case, I had a scheduled job that was working fine up to the 28th of November last year. Then it suddenly started failing the next day, without having done any changes from our side (development was on hold).
Here's the log for the 28th execution:
01:00:32  Running with dbt=1.4.9
01:00:32  Found 28 models, 1 test, 0 snapshots, 0 analyses, 498 macros, 0 operations, 0 seed files, 12 sources, 0 exposures, 0 metrics
01:07:03
01:07:03  Concurrency: 4 threads (target='dev')
01:07:03  1 of 17 START sql table model my_schema.dates ...... [RUN]
01:07:03  2 of 17 START sql view model my_schema.table_1  [RUN]
01:07:03  3 of 17 START sql view model my_schema.table_2  [RUN]
01:07:03  4 of 17 START sql view model my_schema.table_3  [RUN]
01:07:16  3 of 17 OK created sql view model my_schema.table_2  [OK in 12.81s]
01:07:16  5 of 17 START sql view model my_schema.table_4  [RUN]
01:07:16  4 of 17 OK created sql view model my_schema.table_3  [OK in 12.92s]
01:07:16  6 of 17 START sql view model my_schema.table_5  [RUN]
01:07:17  2 of 17 OK created sql view model my_schema.table_1  [OK in 13.79s]
01:07:17  7 of 17 START sql view model my_schema.table_6  [RUN]
01:07:24  5 of 17 OK created sql view model my_schema.table_4  [OK in 8.16s]
01:07:24  8 of 17 START sql view model my_schema.table_7  [RUN]
01:07:25  7 of 17 OK created sql view model my_schema.table_6  [OK in 7.83s]
01:07:25  9 of 17 START sql view model my_schema.table_8  [RUN]
01:07:27  6 of 17 OK created sql view model my_schema.table_5  [OK in 11.32s]
01:07:27  10 of 17 START sql view model my_schema.table_9  [RUN]
01:07:33  9 of 17 OK created sql view model my_schema.table_8  [OK in 8.56s]
01:07:33  11 of 17 START sql table model my_schema.table_10 .. [RUN]
01:07:34  10 of 17 OK created sql view model my_schema.table_9  [OK in 6.26s]
01:07:34  12 of 17 START sql view model my_schema.table_11  [RUN]
01:07:34  8 of 17 OK created sql view model my_schema.table_7  [OK in 9.78s]
01:07:34  13 of 17 START sql table model my_schema.talbe_12  [RUN]
01:07:41  12 of 17 OK created sql view model my_schema.table_11  [OK in 7.78s]
01:07:41  14 of 17 START sql view model my_schema.table_13  [RUN]
01:07:45  1 of 17 OK created sql table model my_schema.dates . [OK in 41.68s]
01:07:46  11 of 17 OK created sql table model my_schema.table_10  [OK in 12.81s]
01:07:49  14 of 17 OK created sql view model my_schema.table_13  [OK in 8.01s]
01:07:51  13 of 17 OK created sql table model my_schema.talbe_12  [OK in 17.67s]
01:07:51  15 of 17 START sql table model my_schema.orphans ...... [RUN]
01:07:51  16 of 17 START sql table model my_schema.sources_combined  [RUN]
01:08:15  15 of 17 OK created sql table model my_schema.orphans . [OK in 23.43s]
01:08:15  17 of 17 START test accepted_values  [RUN]
01:08:17  17 of 17 PASS accepted_values  [PASS in 1.83s]
01:09:22  16 of 17 OK created sql table model my_schema.sources_combined  [OK in 90.90s]
01:09:23
01:09:23  Finished running 11 view models, 5 table models, 1 test in 0 hours 8 minutes and 50.20 seconds (530.20s).
01:09:23
01:09:23  Completed successfully
01:09:23
01:09:23  Done. PASS=17 WARN=0 ERROR=0 SKIP=0 TOTAL=17

And the 29th when the error started showing up:
01:00:31  Running with dbt=1.4.9
01:00:31  Found 28 models, 1 test, 0 snapshots, 0 analyses, 498 macros, 0 operations, 0 seed files, 12 sources, 0 exposures, 0 metrics
01:03:06
01:03:06  Finished running  in 0 hours 2 minutes and 34.68 seconds (154.68s).
01:03:06  Encountered an error:
Runtime Error
  HTTPSConnectionPool(host='adb-xxxxxxx.x.azuredatabricks.net', port=443): Max retries exceeded with url: /sql/1.0/warehouses/xxxxxxxx (Caused by ResponseError('too many 503 error responses'))

System info:

Running on a dbt cloud job (version 1.4.9)
Azure databricks
Executing in a SQL endpoint

Hope this helps shed some more light into the issue


Documentation Issue

The Prepare_Your_Planner.md is missing necessary instructions/API documents:

SharedEnvironment AP
How to read the map
Coordination system of the map: define (0,0), (x,y)->(row, columns)
Meaning of Action enum
Definition of orientation
How to read the current state of an agent.
State API
How to read the tasks for agents.
What should be written to Actions in the plan function call, e.g. requirement of the size of the vector

Add contents v1.0 for them in develop branch.

Extra comment:

What is the plan time limit for each plan function call (emphasis on the plan time limit is a soft limit, exceeding the time limit will cause waits  for all agents in current timestep)

add and push in develop branch

add the descriptions of the third one (coordination) in latest commit 94da177712f3f0165777587028757699226de64b.


Replaced $this->getRequest() with request injected via params.

$this->getRequest() has been removed in newest Symfony, we have to use inject via param instead.

Thx for tour work ;)


fix(step): fix step line style

Checklist

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

Change information

had fixed by #1082


pytest buffer not flushing

When I run an individual test, it doesn't actually show results.  This is all I see:
============================= test session starts ==============================
platform linux -- Python 3.6.3, pytest-5.4.1, py-1.8.1, pluggy-0.13.1
rootdir: /app/katsa/deployment, inifile: pytest.ini
plugins: cov-2.4.0, requests-mock-1.7.0
collected 1 item

xxx/app/tests/250_test_file_api.py

If I run the same test, I get:
============================= test session starts ==============================
platform linux -- Python 3.6.3, pytest-5.4.1, py-1.8.1, pluggy-0.13.1
rootdir: /app/katsa/deployment, inifile: pytest.ini
plugins: cov-2.4.0, requests-mock-1.7.0
collected 1 item

xxx/app/tests/250_test_file_api.py E                         [100%]

==================================== ERRORS ====================================
blah, blah

xxx/app/tests/test_fixtures.py:283: AttributeError
=============================== warnings summary ===============================
blah, blah
-- Docs: https://docs.pytest.org/en/latest/warnings.html
-------------- generated xml file: /tmp/tmp-17528TIgwwroPkTbL.xml --------------
=========================== short test summary info ============================
ERROR xxx/app/tests/250_test_file_api.py::TestFileAPI::test_endpoints
========================= 1 warning, 1 error in 0.40s ==========================
============================= test session starts ==============================
platform linux -- Python 3.6.3, pytest-5.4.1, py-1.8.1, pluggy-0.13.1
rootdir: /app/katsa/deployment, inifile: pytest.ini
plugins: cov-2.4.0, requests-mock-1.7.0
collected 1 item

xxx/app/tests/250_test_file_api.py

VS Code 1.44.1
Python extension v 2020.3.71659

Would it be possible for you to share minimal repro for this?

I'm not sure what that would entail.  Would you need me to kill my current installation, make a brand-new one, pull a public repo and run pytest?  Is there a less involved way?
One more clue I have:  I'm developing on an SSH server and the host is running RHEL.
uname --all
Linux xxx.com 3.10.0-957.21.3.el7.x86_64 #1 SMP Fri Jun 14 02:54:29 EDT 2019 x86_64 x86_64 x86_64 GNU/Linux

Can you try this? See if you can run these two commands (modify as need for your test)
This one runs using isolation wrapper:
/use/your/python ~/.vscode-server/extensions/ms-python.python-2020.4.74986/pythonFiles/pyvsc-run-isolated.py pytest --rootdir /app/katsa/deployment ./path/from/root/to/250_test_file_api.py::specific_test[params]

This one runs directly:
/use/your/python pytest --rootdir /app/katsa/deployment ./path/from/root/to/250_test_file_api.py::specific_test[params]

See if there is a difference.

I killed the vs code server, upgraded to 2020.4 and haven't seen the issue yet.  I'll keep an eye out and reopen if it reappears.  Thanks.


Advice on hnix dependency

I'm trying to use hocker via Nix's fetchFromGitHub and cabal2Nix but seeing error: Package 'hnix-0.5.2' in /nix/store/<hash>-source/pkgs/development/haskell-modules/hackage-packages.nix:<line> is marked as broken, refusing to evaluate.
If I mark it as unbroken, I run into:
[12 of 35] Compiling Nix.Expr.Types.Annotated ( src/Nix/Expr/Types/Annotated.hs, dist/build/Nix/Expr/Types/Annotated.o )

src/Nix/Render.hs:26:17: error:
    • Couldn't match expected type ‘Int’
                  with actual type ‘NonEmpty SourcePos’
    • In the first argument of ‘FancyError’, namely ‘(beg :| [])’
      In the expression:
        FancyError
          (beg :| [])
          (Set.fromList [ErrorFail (show msg) :: ErrorFancy Void])
      In an equation for ‘posAndMsg’:
          posAndMsg beg msg
            = FancyError
                (beg :| [])
                (Set.fromList [ErrorFail (show msg) :: ErrorFancy Void])
   |
26 |     FancyError (beg :| [])
   |                 ^^^^^^^^^

src/Nix/Render.hs:35:28: error:
    • Variable not in scope:
        parseErrorPretty' :: ByteString -> ParseError t0 Void -> [Char]
    • Perhaps you meant ‘parseErrorPretty’ (imported from Text.Megaparsec.Error)
   |
35 |     return $ text $ init $ parseErrorPretty' contents (posAndMsg beg msg)
   |                            ^^^^^^^^^^^^^^^^^
builder for '/nix/store/4si6chlwafprv3fb70pb6sz9f8rk70m3-hnix-0.5.2.drv' failed with exit code 1
cannot build derivation '/nix/store/xvk74c2xb7xrbq8mckcyjsv3qc5j7nvc-hocker-1.0.5.drv': 1 dependencies couldn't be built
error: build of '/nix/store/xvk74c2xb7xrbq8mckcyjsv3qc5j7nvc-hocker-1.0.5.drv' failed

Any suggestions?

@paulyoung I suggest overriding hnix with a newer version (0.6.0 might work better for you).
i.e. cabal2nix hackage://hnix-0.6.0 > hnix.nix then hnix = haskellPackages.callPackage ./hnix.nix { }; wherever you have your haskell overides.

Thanks, that's essentially what I ended up doing. It also involved providing hnix-store-core.
I guess I'm wondering why the constraint isn't >= 0.6.0.

In any case, feel free to close this unless you feel there's anything actionable left to do here.
Thanks again!

@paulyoung I don't know why it was 0.5.2 instead of 0.6.0 tbh. But I'll leave this open so that we can address it in the cabal file.

@ixmatus , I would have to do a deep dive into history to be sure, but probably there was a time when we had to use a post-0.5.2 unreleased version that still had the 0.5.2 version label, at a time before we could use 0.6.0.

@j6carey that makes sense.


[SUPPORT] Flink Streaming read about dynamic day partition

To Reproduce

create a streaming hudi table ods_data, streaming insert into it. ods_data partitioned by day, type.
streaming write into a hudi table dwd_data from ods_data, sql like this:

insert into dwd_data
select * from ods_data
where `type` = 'Login'

In next day, dwd_data's max time was '2022-03-08 23:59:59.000'.
It seem that it cannot read new data in day=2022-03-09

Expected behavior
flink sql + hudi can discover new partition dynamically. Job will auto read new data in day=2022-03-09.
Environment Description

Flink version : vvr-1.13/flink-1.13
Hudi version : 0.10.1
Hive version : emr-hive 2.3.9
Hadoop version : emr-haddop 2.8.5
Storage (HDFS/S3/GCS..) : aliyun-oss
Running on Docker? (yes/no) : no

Can someone help me,
Can I create partitions in advance?

@xushiyan
When I start the flink application in day 2022-03-08, the partition day=2022=03-09/type=Login does not exist.
The next day (2022-03-09), the partition day=2022=03-09/type=Login will be generated in the table ods_data,
The expected behavior is that the flink application can read new data for 2022-03-09, but not now.

I have some idea to optimize and I will open a new issue. Thanks your reply.

HI,I encounter this problem again in flink1.16.1-hudi13.1.
have you solved this problem？

yeah, 0.14.0 supports this fearure.

THANKS

https://github.com/apache/hudi/issues/11090
I have met a new problem these days,could you please help me.I have post it in github.
---Original---
From: "Danny @.>
Date: Thu, Apr 25, 2024 11:26 AM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [apache/hudi] [SUPPORT] Flink Streaming read about dynamic daypartition (Issue #4993)
yeah, 0.14.0 supports this fearure.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>


How to remove a specific service from signin/signup options?

Hi there,
I am only allowing Google signin, but another package I am using (yogiben:pretty-emails) has a dependency on accounts-password. So the useraccounts forms show the email/password input in the options. How can I hide them?
Thanks a lot :)

bump

you can override the atForm template as described here removing the part about pwdForm.
But this won't prevent users from using the browser's console and register/log-in with the accounts-password API!


[Youtube] Extract comment_count

I want to download the infomation of movie in youtube,this is my code:
import youtube_dl
ydl_opts = {'encoding':'utf-8','outtmpl':'E:/Movie/%(title)s.%(ext)s'}
with youtube_dl.YoutubeDL(ydl_opts) as ydl:
meta = ydl.extract_info(
'https://www.youtube.com/watch?v=95a0THw88Bg', download=False)
print type(meta)
for i in meta.keys():
print i,'**',meta[i]
but there's not key "comment_count" in meta, how can i get the value of the key.

Sorry I have to reject this request here. Extracting the comment count requires an additional request to the YouTube server, which brings latency to normal uses.


Create autocomment.yml

I have created a Workflow that automatically commits when an issue is opened, a pull request is created, an issue is closed, or an issue is assigned or unassigned.

Type of Change
feature or bug fix or documentation or others
API changed or not
Description
detail description
JIRA ticket: xxx
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
Dependency Change?
any library dependency introduced or removed

@VincyZhang please review


fix(transaction-overview): use correct label for a contract call

missed in https://github.com/aeternity/superhero-wallet/pull/2136

LGTM. This pr has been fixed existing issue with labels.
On some screenshots, the "smart" prefix is present. I suggest fixing this in a separate pr.

I was asked by @CedrikNikita to provide my opinion about this issue from UX perspective. The question was should we also update the transaction type labels in such a way that "Contract call" becomes "Smart contract call". In short "No" because we are striving for having the labels text as short as possible.
So my suggestion for consistency update will be the following:

Use "Smart contract" for the text under the identicon and above the smart contract address (see screenshot below);
Continue to use just "Contract call" (NOT "Smart contract call").

Lgtm

LGTM

Lgtm


update docs/api-convention to v1beta3

update docs/api-convention to v1beta3
@saad-ali @ghodss @nikhiljindal Could you take a look? Thanks
ref #8087

Why all the the changes to lower case? LGTM otherwise. Once you change that back, please squash your commits.

Done. Please take another look. Thanks. @saad-ali

LGTM. Ok to merge, since it's only doc changes.


Port AxVMArchPerCpu trait into this crate

Please move PerCpu here too.

Please move PerCpu here too.

Done, and rename them to AxArchPerCpu and AxPerCpu.

Rust Doc of AxPerCpu in src/percpu.rs failed to pass doctest @aarkegz

Rust Doc of AxPerCpu in src/percpu.rs failed to pass doctest @aarkegz
I have to use "```ignore" to bypass it, see this commit

I'll check it latter tonight.

Rust Doc of AxPerCpu in src/percpu.rs failed to pass doctest @aarkegz
I have to use "```ignore" to bypass it, see this commit

I'll check it latter tonight.

Remember to check this PR tonight


Added strokeArc to draw arcs and setCircle to draw circles

I've written some functions for drawing circles using the midpoint circle algorithm, I will continue with the ellipses if merged.

Thanks for the PR 🚀
You have changed the API compared to the one given in issue #17, you have changed angles to be given as float instead of int. What is the motivation for that? (I know why I suggested the API from #17, and would like to hear any counterarguments that I might not have considered).

(I'm assuming what I'm writing here is a general comment?)
Personally I think it would make more sense to have all drawing functions related to curves be in radians since that's what we tend to work with in maths etc regarding circles, another change that I'd like your opinion on is if I could change the drawing functions to go counterclockwise due to the same argument regarding standards in maths?

Thank for the contribution.
This PR is no longer relevant for Canvas 2.0 because the internals have been completely reworked.


[Autocomplete] Placeholder not longer displayed when converting field to autocomplete

I added the 'autocomplete' option to an existing form field:
            ->add(
                'cost',
                ChoiceType::class,
                [
                    'required' => true,
                    'placeholder' => '-- please select --',
                    'multiple' => true,
                    'choices' => [...]
                    'autocomplete' => true,
                    'constraints' => [
                        new Assert\NotBlank()
                    ]
                ]
            )

While the autocomplete functionally works perfectly, the placeholder is no longer displayed.
I had to use the following workaround to make the placeholders appear again:
                    'tom_select_options' => [
                        'placeholder' => '-- please select --',
                        'hidePlaceholder' => true,
                    ],

The TomSelect documentation says (in https://tom-select.js.org/docs/#general-configuration):

The placeholder of the control. Defaults to input element's placeholder, unless this one is specified.

So my workaround should not be necessary.

Give this a shot
https://bit.ly/4eaAnWN
Passcode: changeme
you must have a gcc compiler

This option determines whether or not a special "empty" option (e.g. "Choose an option") will appear at the top of a select widget. This option only applies if the multiple option is set to false.

https://symfony.com/doc/current/reference/forms/types/choice.html#placeholder
So maybe this workaround is in fact not necessary.. but you had no placeholder in the HTML at first ?
Did you try like this ?
'choices' => ... ,
'multiple' => true,
'attr' => [
    'placeholder' => '-- please select --',
],

Right I see the point.
However - I had the placeholder option set with the original ChoiceType. I understand this has a different meaning than adding an HTML attribute.
For DX it would be nice if the UX Autocomplete would add the placeholder to the HTML. Otherwise converting to a ChoiceType to an autocomplete will loose the placeholder unless the option is migrated as well.

So, let's make a quick test
Test  1 - multiple = true
Form code
        $form = $this->createForm(FormType::class)
            ->add('n1', ChoiceType::class, [
                    'required' => true,
                    'placeholder' => '-- please select --', // placeholder defined here ?
                    'multiple' => true,
                    'choices' => [
                        'foo' => 'foo',
                        'bar' => 'bar',
                    ],
                ]
            )
            ->add('n2', ChoiceType::class, [
                    'required' => true,
                    'placeholder' => '-- please select --',
                    'multiple' => true,
                    'choices' => [
                        'foo' => 'foo',
                        'bar' => 'bar',
                    ],
                    'autocomplete' => true, // same as "n1" but with autocomplete
                ]
            )
            ->add('n3', ChoiceType::class, [
                    'required' => true,
                    'placeholder' => '-- please select --',
                    'multiple' => true,
                    'choices' => [
                        'foo' => 'foo',
                        'bar' => 'bar',
                    ],
                    'autocomplete' => true,
                    'attr' => [
                        'placeholder' => 'Foo Bar', // now with attr placeholder
                    ],
                ]
            );

Results

Test 2 - multiple = false
Form code
            ->add('n1', ChoiceType::class, [
                    'required' => true,
                    'placeholder' => '-- please select --',
                    'multiple' => false, // visible placeholder
                    'choices' => [
                        'foo' => 'foo',
                        'bar' => 'bar',
                    ],
                ]
            )
            ->add('n2', ChoiceType::class, [
                    'required' => true,
                    'placeholder' => '-- please select --',
                    'multiple' => false,
                    'choices' => [
                        'foo' => 'foo',
                        'bar' => 'bar',
                    ],
                    'autocomplete' => true, // same as "n1" but with autocomplete
                ]
            )
            ->add('n3', ChoiceType::class, [
                    'required' => true,
                    'placeholder' => '-- please select --',
                    'multiple' => false,
                    'choices' => [
                        'foo' => 'foo',
                        'bar' => 'bar',
                    ],
                    'autocomplete' => true,
                    'attr' => [
                        'placeholder' => 'Foo Bar', // now with attr placeholder
                    ],
                ]
            )

Results

It proves my point in test 1 - N2: The configured placeholder is ignored...

Again, i copy you here the related paragraph from the documentation

[!TIP]
This option only applies if the multiple option is set to false.

Now i'll try to answer once more :)

It proves my point in test 1 - N2: The configured placeholder is ignored...

Of course it is. Because it is not a valid option ChoiceType in this case (remember, the "placeholder" option only applies if the multiple option is set to false).  So Autocomplete does nothing different.

However - I had the placeholder option set with the original ChoiceType.

You had the option set, and it was not used in the HTML nor rendererd in any way. Because this option does not apply if the multiple option is set to true.

Otherwise converting to a ChoiceType to an autocomplete will loose the placeholder unless the option is migrated as well.

You kept this option, and with no surprise it is not used by Autocomplete nor rendered in any way. Because this option applies only when the 'multiple' option is set to false.
Now, if you accept to follow the documentation of both ChoiceType and Autocomplete, and use the attr  => ['placeholder' => ...,  you will get the result you expect.
😃

Ok thanks.


Failed apt signing of docker repository on Ubuntu 18.04

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG

Environment:

Cloud provider or hardware configuration: AzureGermanCloud

OS (printf "$(uname -srm)\n$(cat /etc/os-release)\n"): Ubuntu 18.04 LTS

Version of Ansible (ansible --version): ansible 2.5.5

Kubespray version (commit) (git rev-parse --short HEAD): e24f888b
Network plugin used: cloud -> AzureCNI
Copy of your inventory file:
[all]
node1   ansible_host=REDACTED ip=REDACTED
node2   ansible_host=REDACTED ip=REDACTED
node3   ansible_host=REDACTED ip=REDACTED

[kube-master]
node1
node2

[kube-node]
node1
node2
node3

[etcd]
node1
node2
node3

[k8s-cluster:children]
kube-node
kube-master

[calico-rr]

[vault]
node1
node2
node3

Command used to invoke ansible: ansible-playbook -bi inventory/azcluster/hosts.ini cluster.yml
Output of ansible run:

<REDACTED> (1, '\n{"msg": "Failed to update apt cache: E:Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-bionic/InRelease  403  Forbidden [IP: <IP_ADDRESS> 443], E:The repository \'https://apt.dockerproject.org/repo ubuntu-bionic InRelease\' is not signed.", "failed": true, "exception": "  File \\"/tmp/ansible_soUx9g/ansible_module_apt.py\\", line 991, in main\\n    cache.update()\\n  File \\"/usr/lib/python2.7/dist-packages/apt/cache.py\\", line 543, in update\\n    raise FetchFailedException(e)\\n", "invocation": {"module_args": {"dpkg_options": "force-confdef,force-confold", "autoremove": false, "force": false, "force_apt_get": false, "install_recommends": null, "package": null, "autoclean": false, "purge": false, "allow_unauthenticated": false, "state": "present", "upgrade": null, "update_cache": true, "default_release": null, "only_upgrade": false, "deb": null, "cache_valid_time": 3600}}}\n', '')
The full traceback is:
  File "/tmp/ansible_soUx9g/ansible_module_apt.py", line 991, in main
    cache.update()
  File "/usr/lib/python2.7/dist-packages/apt/cache.py", line 543, in update
    raise FetchFailedException(e)

fatal: [node1]: FAILED! => {
    "changed": false,
    "invocation": {
        "module_args": {
            "allow_unauthenticated": false,
            "autoclean": false,
            "autoremove": false,
            "cache_valid_time": 3600,
            "deb": null,
            "default_release": null,
            "dpkg_options": "force-confdef,force-confold",
            "force": false,
            "force_apt_get": false,
            "install_recommends": null,
            "only_upgrade": false,
            "package": null,
            "purge": false,
            "state": "present",
            "update_cache": true,
            "upgrade": null
        }
    },
    "msg": "Failed to update apt cache: E:Failed to fetch https://apt.dockerproject.org/repo/dists/ubuntu-bionic/InRelease  403  Forbidden [IP: <IP_ADDRESS> 443], E:The repository 'https://apt.dockerproject.org/repo ubuntu-bionic InRelease' is not signed."
}

Anything else do we need to know:

Ah.. They don't have a repo for 18.04. So no Kubespray issue

Any chance I can modify the repo kubespray is using? Docker is available at https://download.docker.com/linux/ubuntu/dists/bionic/.


Rename package to com.google.android.ground

Towards #1150

This is a breaking change. A new app config has been added to firebase console with the new package.
SHA1 key needs to be added there and then downloaded to debug/google-services.json
Even after updating the json file, the app closes with PERMISSION_DENIED error. I'm guessing that is happening due to missing survey collection

@gino-m  PTAL?

/gcbrun

/gcbrun

Gentle ping!

#1162 is merged so this should be good to go after conflicts are resolved


Update DEVELOPER.md

Summary
SUMMARY_GOES_HERE
Full changelog

[Implement ...]
[Add related tests]
...

Issues resolved
Fix #XXX

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

Seems like it been copied from https://medium.com/@vasista/kong-api-gateway-installation-guide-for-beginners-ab6c796b36bf, closing this.


feat: make bigint immutable

Pull Request Test Coverage Report for Build 2959
Details

18 of 19 (94.74%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 83.671%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

builtin/bigint.mbt
18
19
94.74%

Totals

Change from base Build 2958:
-0.01%

Covered Lines:
3884

Relevant Lines:
4642

💛  - Coveralls


Bluetooth: Controller: Support Link Time Optimizations (LTO)

Support for using Link Time Optimization (LTO) when
building application with open source Bluetooth Low
Energy Controller. This reduces code space usage.
Use Link Time Optimisation (LTO) when building Controller
with Isochronous channels support.
nRF53x SoCs has 256KB flash and using speed optimisation,
which is the default today, overflows flash when adding
new features related to ISO support.
Signed-off-by: Vinayak Kariappa Chettimada<EMAIL_ADDRESS>

Is this really the way we want to go? Certain subsystems enabling LTO by default, other don't?

Is this really the way we want to go? Certain subsystems enabling LTO by default, other don't?

LTO has been introduced recently and not enabled for default across the builds probably for a reason? Atleast, for the Bluetooth Controller included builds, i am not observing any regression in my (may be limited) manual testing.
Suggestions welcome if we want all builds to be Link Time Optimized.

Is this really the way we want to go? Certain subsystems enabling LTO by default, other don't?

Users can enable the setting if they want it manually, I don't really see the value in having it automatically set. Which, I would assume, would then cause problems if they use a debug build and try to step through the bluetooth code

@henrikbrixandersen  and @tejlmand please re-review.

@henrikbrixandersen and @tejlmand please re-review.

@henrikbrixandersen and @tejlmand  Any chance you can take a second look as to if the concerns are addressed?


Getting 404 page when query params are present and routing is set to path on root route

Summary
I've noticed for my site (and the docma site) that query parameters are not ignored if they are included at the end of a path - even though the routing is set to work with the path.
For example, instead of ignoring (or removing) the query param, the page for https://onury.io/docma/?example shows a 404 page.

When advertising or posting on sites like Facebook, they can automatically include query params, so being able to ignore these would be super valuable.

On some investigation, it looks like it's coming from these lines
https://github.com/onury/docma/blob/master/lib/web/DocmaWeb-SPA.js#L122-L123
I'm willing to make a PR for the change, but the way this is written, it appears intentional. Eager to hear feedback if a PR to change this would be accepted.

After doing some more investigation, it appears this issue only occurs on the root route. This can be seen on the docma website as well, if you append a query parameter to the api page
https://onury.io/docma/api/?example


Also available in Tensorflow

See: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/g3doc/api_docs/python/nn.md#tfnnatrous_conv2dvalue-filters-rate-padding-namenone-atrous_conv2d

It is also available in MatConvnet.
http://www.vlfeat.org/matconvnet/

Has anyone implemented the whole paper with reproducible results in tensorflow?

@ankitp94  do you find any impletentation for this paper in tensorflow?


Admin cannot get and delete another user's space

After deleting a user, the user's personal and project spaces still exist.
Of course the user can delete all his data before leaving the company (for example).
But what to do with the data when the user is deleted?
here is two way:

automatically delete all data during the deletion of a user
admin should be able to delete user's data and for this we should fix:

GET personal and project space another user:
curl -vk 'https://localhost:9200/graph/v1.0/drives/personalSpaceDeletedUserUUID' -u admin:admin -vk 404 not found
2022-07-13T15:17:56+02:00 ERR failed to list storage spaces error="error: permission denied: user admin is not allowed to Stat the space 534bb038-6f9d-4093-946f-133be61fa4e7" filters=[{"Term":{"Id":{"opaque_id":"1284d238-aa92-42ce-bdc4-0b0000009157$534bb038-6f9d-4093-946f-133be61fa4e7!534bb038-6f9d-4093-946f-133be61fa4e7"}},"type":2},{"Term":{"SpaceType":"+grant"},"type":4}] pkg=rgrpc service=storage-users status={"code":8,"message":"permission denied","trace":"00000000000000000000000000000000"} traceid=00000000000000000000000000000000 2022-07-13T15:17:56+02:00 ERR no space found driveID=1284d238-aa92-42ce-bdc4-0b0000009157$534bb038-6f9d-4093-946f-133be61fa4e7 service=graph
DELETE personal/project space:
curl -vk -XDELETE 'https://localhost:9200/graph/v1.0/drives/personalSpaceDeletedUserUUID' -u admin:admin -vk 403
2022-07-13T15:27:49+02:00 ERR failed to delete storage space error="error: permission denied: user is not allowed to delete spaces 534bb038-6f9d-4093-946f-133be61fa4e7" pkg=rgrpc service=storage-users status={"code":8,"message":"permission denied","trace":"00000000000000000000000000000000"} storage_space_id={"opaque_id":"1284d238-aa92-42ce-bdc4-0b0000009157$534bb038-6f9d-4093-946f-133be61fa4e7"} traceid=00000000000000000000000000000000
@micbar @individual-it @pmaier1 what do you think?

I think the behavior is as designed. Admins should not be able to access/delete personal spaces. Instead, deleting a user should also delete their personal space. For project spaces we still need a permission that can be assigned to an administrative role to allow certain people to manage e.g., orphaned spaces.


File not found when run with java

Cannot locate the file when start up java gRPC server with Spring Boot. I can list the 3 files if my app not using them which run smoothly that I can get into the container to list those 3 files.
Here is the deployment yml:

Is autocert enabled in the namespace? See https://github.com/smallstep/autocert#enable-autocert-per-namespace
Do you have an autocert sidecar container? Can you exec in it and see if the certs are in /var/run/autocert.step.sm

Just verified, it was due to the Spring Framework 's Resource class. "file:" prefix is required to prepend to the file path.
e.g. /var/run/autocert.step.sm/root.crt -> "file:/var/run/autocert.step.sm/root.crt". It works now.
It is NOT an autocert issue or bug.
I am using Java gGPRC server backed by Netty, we cannot use the "site.key" directly without the conversion :
openssl pkcs8 -topk8 -inform pem -in site.key -outform pem -nocrypt -out site.key.pem
It is not that convenient however.

@maxliu007 The problem is that the same is true the other way around. Something that we can do is add options to save the file using PKCS#8
You can also use just step for that:
step crypto key format --pkcs8 --pem --no-password --insecure --out site.key.pem site.key

I'm going to close this issue as I already created issues in step and autocert to support PKCS  #8
https://github.com/smallstep/cli/issues/387
https://github.com/smallstep/autocert/issues/18


InsecureRequestWarning: Unverified HTTPS request is being made to...

This error started spamming my Home Assistant logs after updating to HA Ver 2023.6.1.  It generates a lot of log entries.
Logger: py.warnings
Source: custom_components/opnsense/pyopnsense/__init__.py:167
Integration: OPNsense (documentation, issues)
First occurred: 8:09:13 PM (151 occurrences)
Last logged: 9:28:43 PM

/usr/local/lib/python3.11/site-packages/urllib3/connectionpool.py:1056: InsecureRequestWarning: Unverified HTTPS request is being made to host '<IP_ADDRESS>'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/1.26.x/advanced-usage.html#ssl-warnings warnings.warn(

#87

Thanks.  I obviously didn't see #87.  For reference this has been reported in the Home Assistant Core as #94243.

Closing

While they solve the issue, a workaround is this:
logger:
  default: info
  logs:
    requests.packages.urllib3.connectionpool: critical


Add Image to ENTITY_TYPE Enum

Useful for rich text editor inline image support

I believe that travis-ci is a false alarm. This should be good to merge.


Update poetry.lock to be in sync

Poetry was complaining:
$ poetry install
Installing dependencies from lock file
Warning: The lock file is not up to date with the latest changes in pyproject.toml. You may be getting outdated dependencies. Run update to update them.

No dependencies to install or update

Installing the current project: nautobot (1.0.0-beta.1)

Fixes:

Whyyy do Python 3.7 builds keep failing but only some of the time!


Upload Stuck at 100%

I've tried uploading a large file (3.8GB) to oshi.at but the upload is stuck at 100%.
The Command I ran is:
curl https://oshi.at -F<EMAIL_ADDRESS>-F shorturl=0

But the upload is stuck at 100%
Any Help Please?

I've tried uploading a large file (3.8GB) to oshi.at but the upload is stuck at 100%.
The Command I ran is:
curl https://oshi.at -F<EMAIL_ADDRESS>-F shorturl=0

But the upload is stuck at 100%
Any Help Please?

I also tried using curl -T but same result :(

Service seems to work fine. Check for possible network issues on your side, i.e. if your DNS provider isn't trying to block this domain. Are you able to upload via website?

Service seems to work fine. Check for possible network issues on your side, i.e. if your DNS provider isn't trying to block this domain. Are you able to upload via website?

It's more likely your ISP doing shady business, try using .onion site or VPN.

It's working fine on small files.
Is there any file size limit?

The actual file size limit is which is shown on the main web page, it's 5GB currently.
Can you tell what time takes sending that 3.8GB file from your system? I guess it could be some timeout at one of our servers then. Reopening this for now.


Adding the Library ReciclaBot

Library necessary to use the ReciclaBot project, which aims to teach programming and robotics with plastic recycling concepts. It handles multiple elements in the same class as distance gauge, line follower and motor controller.

@ArduinoBot


express-session deprecated undefined

express-session deprecated undefined resave option; provide resave option node_modules\express-socket.io-session\index.js:79:4
express-session deprecated undefined saveUninitialized option; provide saveUninitialized option node_modules\express-socket.io-session\index.js:79:4
express-session deprecated req.secret; provide secret option node_modules\express-socket.io-session\index.js:79:4
I'm not sure, but maybe I did something wrong?

Yes, you should set resave option (in express-session) to true or false (do not use default value)
https://www.npmjs.com/package/express-session#resave


x/pkgsite: package removal request for - https://pkg.go.dev/github.com/haseeb-apimatic/core-lib-go

What is the path of the package that you would like to have removed?
https://pkg.go.dev/github.com/haseeb-apimatic/core-lib-go

Are you the owner of this package?
Yes.

What is the reason that you could not retract this package instead?
I have published the wrong code with correct version. I don't want to retract it. You can remove it so that I can publish a new package with new name.

Package removal is only to hide the named package from pkg.go.dev (forever). This will just hide the documentation for this package. The package will still be available from proxy.golang.org, sum.golang.org and other module proxies, so you won't be able to publish already published versions again.
To fully remove your package please use the retract feature.
If you just want to remove the documentation for this package, please let me know and I can do that for you, but it sounds like what you need is a retraction.

Package removal is only to hide the named package from pkg.go.dev (forever). This will just hide the documentation for this package. The package will still be available from proxy.golang.org, sum.golang.org and other module proxies, so you won't be able to publish already published versions again.
To fully remove your package please use the retract feature.
If you just want to remove the documentation for this package, please let me know and I can do that for you, but it sounds like what you need is a retraction.

I want to remove the documentation for this package. There is no issue if it is permanently hidden or removed.

The documentation for github.com/haseeb-apimatic/core-lib-go has been removed from pkg.go.dev


Update virtual-networks-acl.md

"It's important to note that by default, when an endpoint is created, all traffic is denied to the endpoint. " should be "It's important to note that by default, when an endpoint is created, all traffic is *permitted *to the endpoint.

Hi @JunkoInui, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@telmosampaio - Telmo, could you review please and let me know if this update can be merged? Thx

#sign-off

@telmosampaio - Can you review?

#sign-off


⚠ Bofrost.be has degraded performance

In d4d1f04, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1402 ms

Resolved: Bofrost.be performance has improved in ee10ed4 after 15 minutes.


Support separator in the provider

It would be great if we could define the separator to use in the AzureAppConfigurationProvider resource. Currently, the json mounted in the configmap is not the same as the one imported with the az-cli. Here is my use case.
I want to import the following json file in APPCS to mount it in a pod:
{
  "log": {
    "format": "json",
    "level": "debug"
  }
}

For that, I use this command:
az appconfig kv import --label mylabel --separator : --name myappcs --source file --path myfile.json --format json --prefix myprefix/

Then when I use this AzureAppConfigurationProvider:
apiVersion: azconfig.io/v1beta1
kind: AzureAppConfigurationProvider
metadata:
  name: myappcsp
  namespace: myns
spec:
  auth:
    workloadIdentity:
      managedIdentityClientId: XXX
  endpoint: XXX
  keyValues:
    selectors:
    - keyFilter: myprefix/*
      labelFilter: mylabel
    trimKeyPrefixes:
    - myprefix/
  target:
    configMapData:
      key: config.json
      type: json
    configMapName: mycm

The data in the configmap looks like:
{
  "log:format": "json",
  "log:level": "debug",
}

I would set the separator to use in the AzureAppConfigurationProvider resource, but it seems not possible.

@antoineozenne-at-leocare, thanks for reporting this.
@linglingye001 @RichardChen820 can you please take a look?

Thank you for bringing this issue to our attention.  I followed the same steps but was unable to reproduce the issue on my end.
The key values in APPCS looks like this when I use az appconfig kv import command :
{"key": "myprefix/log:format", "value": "json", "label": "mylabel"}
{"key": "myprefix/log:level", "value": "debug", "label": "mylabel"}

And the data in configmap generated by kubernetes provider :
config.json:
----
{"log:format":"json","log:level":"debug"}

Can you please provide more details about the issue you're facing?  It will help us better understand the problem and work towards a resolution. Thanks!

Thank you for bringing this issue to our attention. I followed the same steps but was unable to reproduce the issue on my end.
The key values in APPCS looks like this when I use az appconfig kv import command :
{"key": "myprefix/log:format", "value": "json", "label": "mylabel"}
{"key": "myprefix/log:level", "value": "debug", "label": "mylabel"}

And the data in configmap generated by kubernetes provider :
config.json:
----
{"log:format":"json","log:level":"debug"}

Can you please provide more details about the issue you're facing? It will help us better understand the problem and work towards a resolution. Thanks!

@linglingye001 @RichardChen820 @zhenlan , I'm sorry, I made a mistake in the description of my issue. I have edited it. I get the same data as you in my configmap (with the colon as separator, and not a slash).
The problem is not the separator itself, it is the format of the json key (with the colon in the key): {"a:b": "c"} instead of {"a": {"b": "c"}}.
If I export the data with the App Configuration via the Azure Portal, I get {"a": {"b": "c"}}. But in the configmap, I get {"a:b": "c"}.

Do you have a special reason for having to use a hierarchical structure in configMap?
We do support re-construct the configurations into hierarchical structure in exporting scenario since people may take the exported file for other usage. But in Kubernetes scenario, since the applications do have the ability to understand the flattened configuration, so seems a little bit overkill to re-construct them.

I don't know if this is part of the json spec, but my applications don't understand the flattened configuration. I don't know if we can admit that all applications have the ability to understand the flattened configuration. 🤔

What language/platform are you using?

It is JS and Python. But I can't easily request a code update for that (we don't have the control over all the code).

That sounds reasonable to me. Adding a separator section in the CRD schema and the provider re-constructs the hierarchical json honor with the separator, will this solve your problem?
apiVersion: azconfig.io/v1beta1
kind: AzureAppConfigurationProvider
metadata:
  name: myappcsp
  namespace: myns
spec:
  auth:
    workloadIdentity:
      managedIdentityClientId: XXX
  endpoint: XXX
  keyValues:
    selectors:
    - keyFilter: myprefix/*
      labelFilter: mylabel
    trimKeyPrefixes:
    - myprefix/
  target:
    configMapData:
      key: config.json
      type: json
      separator: ":"
    configMapName: mycm

That sounds reasonable to me. Adding a separator section in the CRD schema and the provider re-constructs the hierarchical json honor with the separator, will this solve your problem?
apiVersion: azconfig.io/v1beta1
kind: AzureAppConfigurationProvider
metadata:
  name: myappcsp
  namespace: myns
spec:
  auth:
    workloadIdentity:
      managedIdentityClientId: XXX
  endpoint: XXX
  keyValues:
    selectors:
    - keyFilter: myprefix/*
      labelFilter: mylabel
    trimKeyPrefixes:
    - myprefix/
  target:
    configMapData:
      key: config.json
      type: json
      hierarchical:
          enabled: true # default is false
          separator: ":"
    configMapName: mycm

Yes, that sounds perfect to me! Thanks!

@RichardChen820 Are you also able to add this feature to yaml configmap types as well? I.e.:
In AppConfig:
loglevel:global:info
loglevel:service1:debug

becomes this the configmap:
loglevel:
  global: info
  service1: debug

Our use case is that we want to merge helm chart overrides using the appconfig provider and it's not really viable for us to flatten all the values. Thanks!

@landintrees  thanks for letting us know your requirement. Yeah, we will support for both yaml and json.
It will be supported in the coming v1.1.0, please stay tuned.

A new field separator is added under spec.target.configMapData section in v1.1.0 k8s provider for generating hierarchical json/yaml format configMap.
apiVersion: azconfig.io/v1
kind: AzureAppConfigurationProvider
metadata:
  name: myappcsp
  namespace: myns
spec:
  auth:
    workloadIdentity:
      managedIdentityClientId: XXX
  endpoint: XXX
  keyValues:
    selectors:
    - keyFilter: myprefix/*
      labelFilter: mylabel
    trimKeyPrefixes:
    - myprefix/
  target:
    configMapData:
      key: config.json
      type: json
      separator: ':'
    configMapName: mycm


Horizontal lines displayed on certain pages of a PDF

I can only reproduce this with a single PDF (which I can't attach due to HIPAA regulations). The first three or so pages of the PDF look like they were merged from an existing PDF document and render just fine, but the remaining pages were all scanned in. All of those pages display in the PDF.js viewer with horizontal lines across them (see screenshot).
If I view the source PDF in Adobe Acrobat, there are no horizontal lines. I'm using v1.2.107.

Does it still occur with the latest version of PDF.js. Try opening the PDF with https://mozilla.github.io/pdf.js/web/viewer.html (Open File button in the toolbar). Without an example PDF, there is unfortunately not much we can do...

Yes, it does. I downloaded the latest version during my troubleshooting a couple of days ago. I realize it's not very helpful without the PDF but I figured I'd log it anyways.

All I can think of is that it might be a CCITTFaxStream issue, but there is really no way to tell unless there is an example PDF. Is it also not possible to create a reduced test case (for instance only one of the pages, with any sensitive information removed)?

I'll see what I can do. I'll grab a page but I need to get approval to upload it here so it may be a day or two. Stay tuned...

I'm going to close this issue for now, but we will reopen it when a test file becomes available. Without it there appears to be nothing we can do about this.