[stable/jenkins] Continue receiving 404 error when trying to load jenkins server.

Is this a request for help?:
Yes
Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Version of Helm and Kubernetes:
kubernetes nodes version 1.10.12
Which chart:
stable/jenkins
What happened:
Tried helm upgrade after updating plugin versions and although pods are running and available, i continue receiving a 404 error.  No other changes have been made and was working perfectly fine before i attempted to upgrade my chart.
What you expected to happen:
When entering my URL, i expected it to hit my upgraded server that includes new plugin versions
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:

Without any context e.g from which version to which version you tried to update, you used values etc. it will be hard to support you.


WIP: Extract GEOSldas_GridComp and LDAS_App into separate repos

This is a work-in-progress PR for extracting out the GEOSldas_GridComp and LDAS_App directories into their own components (for work with @saraqzhang and @rtodling in integrating LDAS into the ADAS).
Using RepoExtractor, the two repos were extracted with:
./extract_repo.bash -r "GEOSldas" -d "LDAS_App" --newrepo "LDAS_App" --develop --create-repo --push
./extract_repo.bash -r "GEOSldas" -d "GEOSldas_GridComp" --newrepo "GEOSldas_GridComp" --develop --create-repo --push

In my test it built. Which is nice.

NOTE 1: This should not be depended on. Most likely the two new repos will need to be deleted and remade once this is done "for real"
NOTE 2: In this PR, I kept GEOSgcm_GridComp underneath GEOSldas_GridComp. It could be moved parallel as well. CMake doesn't care, but in this way the directory tree before and after will look nigh the same

I suppose up next would be to have @biljanaorescanin test to see if this does more than build! :)

@mathomp4, thanks for putting this PR and the Github Project together, very helpful.   I'm starting to understand what this all means.  Here are a couple of initial thoughts:

For consistency with the nomenclature of GEOSgcm, I suggest calling the "App" repo "GEOSldas_App" (not "LDAS_App").  This makes it more obvious to developers that GEOSldas, GEOSldas_App, and GEOSldas_GridComp all go together.

I'm wondering if there's any chance we can limit the split to just two repos, GEOSldas (fixture) and GEOSldas_App_and_GC.  I recognize that this is not following the current template across other GEOS repos, and it won't neatly fit into the directory tree of  GEOSadas.  But the GEOSadas and GEOSldas fixtures need both the GEOSldas_App and the GEOSldas_GridComp elements, so importing them from separate repos does not seem strictly necessary.  Put differently, the motivation for having three repos in total seems to be coming only from having split other components (e.g., the GCM) into separate "App" and "GC" repos.  I might be missing something, of course, but I thought I should at least ask before committing myself to start juggling lots of extra LDAS PRs.

cc: @tclune @weiyuan-jiang @rtodling

@gmao-rreichle You are the closest to the issue.   I have no strong opinions.  I will point out that it is easier to split again later on than to undo a split that you come to regret.

@gmao-rreichle I mean, there is no reason that LDAS_App/ is in Applications/ other than that's how it was in CVS and when we went to Git, we tried to emulate the directory structure.
We could put LDAS_App/ inside of the GEOSldas_GridComp repo, I think. CMake doesn't care. But I'd have to do some testing to figure out if the tool I use to extract the history of it cares.
My guess is the best way to do this is I'd first make a PR to GEOSldas where all we do is a git mv of Applications/LDAS_App into Components/GEOSldas_GridComp/GEOSldas_App (and I guess delete the Applications/ folder as well. I'll make a quick draft PR of that just to see what happens with the history here on GitHub.

Update: Okay. I can also do it in my extraction process too. The one thing is it looks like that way the history is not retained. This might not be a bad thing, we can just tell people this history for GEOSldas_App is in the GEOSldas repo.
But I'll keep trying things...


A11y_AzureDataStudioStayHealthy_Welcome_ExtendyourdataStudio_Keyboard:The install button tool tip is not hoverable.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHubTags:#A11y_AzureDataStudioStayHealthy;#A11ySev2;#A11yTCS;#A11yWCAG2.1;#NonBenchmark;#DesktopApp;#MAS1.4.13;#SQL Azure Data Studio;#FTP;#Keyboard;#STP;#Win32;
Environment Details:
Application Name: Azure Data Studio
Version: 1.19.0-insider
Commit: e8dc0d1
Date: 2020-05-27T17:24:57.733Z
VS Code: 1.46.0
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.18363
Additional Details:
MAS References:MAS1.4.13
Repro Steps:
1 . Launch Azure Data Studio Insiders application.
2 . If Welcome screen is not shown on application launch, then navigate to Help --> Welcome.
3 .
4 . Navigate to install button
Actual:
On hovering over the button install the tooltip appears but on moving to the tooltip it disappears.
Expected:
When hovered over the tooltip the tooltip should be hoverable and not dismiss.
User Impact:
Keyboard user on trying to move to the tooltip won't be able to view it since it disappears.
Attachment link for Reference:
10642A11y_AzureDataStudioStayHealthy_Welcome_ExtendyourdataStudio_Keyboard.zip

@v-bbrady looks like we don't have an active PR to fix this issue.

Hi @fsteffi, the tooltip is standard html tooltip, also, we are updating the tooltip to match the aria-label to be 'Install' so there is no inaccessible information for keyboard users.
there is already an umbrella issue tracking the keyboard accessible tooltip issue: https://github.com/microsoft/vscode/issues/52016

Hi @alanrenmsft the issue, we are not able to interact (Copy the tooltip text, moving the move hover into the tooltip, etc) with the tooltip which appears on hovering with mouse on Install button.
the issue you mentioned in above comment is about tooltip appearing with keyboard focus. which are 2 different issues.
and the above issue is still repro in the latest Azure Data Studio Insiders application.

Please reopen the bug. the bug should be closed by trusted testers after verificaton.
GitHub Tags: #Regressed:02-20-23;

@Roopesh-T can you please test this on the latest insiders build? The tooltip on the "Install" button has been removed.

@Roopesh-T please retest this

closing the bug as the tooltip on the install but got removed.

Version: 1.46.0-insider (user setup)
Commit: f8cd52f70a55e3dd510188b65144dbae3cb07cd4
Date: 2023-09-01T05:36:22.643Z
VS Code: 1.79.2
Electron: 22.3.14
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.22621
Github : #closed;


Bug: requirements.txt

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Current behavior
A clear and concise description of what issues the bug causing.
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

we can't able to install the requirements.txt file


Investigate sagemaker serializer for prediction

Currently using CSVSerilize.
Check out the others and determine the best one in terms of cost/efficieninecy
https://sagemaker.readthedocs.io/en/stable/api/inference/serializers.html#sagemaker.serializers.NumpySerializer

Not all serialization methods are supported for each algorithm used in SageMaker Autopilot (*). CSVSerilaze runs without any problems.

https://docs.aws.amazon.com/sagemaker/latest/dg/cdf-inference.html


Start On Right Page

I've spent the last couple days looking for a solution to this and haven't found one, so pardon me if I've just missed it.  I'm writing a script that takes an input file (in this case a novel) and outputs a print-ready version of the file in Docx format.  Everything is working great with the exception of the Gutter function, which is applying the gutter to the wrong side of the pages because it is assuming that the first page of the document is the left page, which isn't true in printed documents like books.
Is there a way to set the document to "start" on the right page?

Hmm, that doesn't sound quite right, I think we'll need to see an example. Page 1 is always a recto page, and the gutter would appear added to its left margin. Please post what you're doing and what you're getting, and how you can tell it's different from what you expect, perhaps by comparing the same thing done by hand in Word.

Hey, thanks for the reply.
So, what I'm doing is taking a .docx that has been exported form a Google Docs document, and I'm using python-docx to set margins, page bounds, and a bunch of formatting tweaks to get it ready to go directly into KDP's print format.  It isn't complex, but it saves me a great deal of time and allows for consistency across projects.
The code as it stands now is below.  It's messy, just a basic proof-of-concept that I'll clean up and streamline once it's all working.  It's not even all annotated yet.
I don't have a working copy of Word to check things on at the moment.  I used to do this manually using Word and never had issues with the gutter coming out as it has here.  I could e-mail you a copy of the  output file, but I'm not comfortable of posting it publicily since it's a finished novel.  If you'd like to reach out via e-mail you can get me at fox (at) chaosawakens (dot) com.  I can send the finished file directly from there.
When I preview the output file in my unactivated copy of Word it shows the title page (first page) on the left side and the gutter on the right side.  I thought this might just be a display issue so I uploaded the file to the publishing sight and ran the preview there on the file and it showed the same problem, the "gutter" was on the page edges instead of on the inner side, thus confirming that the gutter was set in the wrong place.
Thoughts I've had since your reply:

Perhaps Google Docs did somethign to the format that has messed up the way python-docx sees the format?
Is setting the first page as a title page having an effect on it?

from docx import Document
from docx.shared import Inches, P
![page 01](https://user-images.githubusercontent.com/17713625/53830591-d087b900-3f50-11e9-9e2c-5008a181e275.jpg)
![page 04 05](https://user-images.githubusercontent.com/17713625/53830592-d087b900-3f50-11e9-9f55-411b1fbce233.jpg)

t
from docx.enum.style import WD_STYLE_TYPE
from docx.enum.text import WD_ALIGN_PARAGRAPH
from docx.enum.text import WD_TAB_ALIGNMENT
import string
import re

#This grabs the filename for the input source.  It should be in docx, but maybe we can support other formats later.
print ("What file would you like to convert?")
inputFile = input("(.docx will be added automatically, defaults to bookfile.docx)\n") or "bookfile"

#This puts our working document in a place we can address it.
document = Document(inputFile + '.docx')

#This establishes differing headers and footers for odd and even pages.
document.settings.odd_and_even_pages_header_footer = True

#This gathers the book title for placing in the header.
bookTitle = input("What is your book title?\n") or "Captain Stinky's Fun Time Rodeo Show"
#This gathers the series name for placing in the even page footer.
seriesTitle = input("What is the Series Name?\n") or "Goat Whispering #125"

#This gathers the desired output file name.
print ("What is your desired output filename?")
desiredOutput = input("(.docx is added by default.  outputFile.docx is the default.)\n") or "outputFile"

#The below establish the basic page properties necessary for a printed document.
section = document.sections[0]
section.page_width = Inches(6)
section.page_height = Inches(9)
section.top_margin = Inches(.76)
section.bottom_margin = Inches(.76)
section.right_margin = Inches(.6)
section.left_margin = Inches(.6)
section.gutter = Inches(.3)
paragraph_format = document.styles['normal'].paragraph_format
#paragraph_format.space_after = Pt(12)  #This can be used to create spaces after a paragraph if there isn't already spacing accounted for.

styles = document.styles

style1 = styles.add_style("Header", WD_STYLE_TYPE.PARAGRAPH)
style1.base_style = styles["normal"]
tab_stops = style1.paragraph_format.tab_stops
tab_stops.add_tab_stop(Inches(2.2), WD_TAB_ALIGNMENT.CENTER)
tab_stops.add_tab_stop(Inches(4.4), WD_TAB_ALIGNMENT.RIGHT)

style5 = styles.add_style("chaptbreaks", WD_STYLE_TYPE.PARAGRAPH)
style5.base_style = styles["normal"]
font5 = style5.font
font5.bold = True

style6 = styles.add_style("regular", WD_STYLE_TYPE.PARAGRAPH)
style6.base_style = styles["normal"]
paragraph_formatter = style6.paragraph_format
paragraph_formatter.alignment = WD_ALIGN_PARAGRAPH.JUSTIFY_LOW
paragraph_formatter.first_line_indent = Pt(20)

headerE = section.even_page_header
headerE.add_paragraph('\tHeath Pfaff', style = "Header")

header = section.header
header.add_paragraph('\t' + bookTitle, style = "Header")

footerE = section.even_page_footer
footerE.add_paragraph('\t' + seriesTitle, style = "Header")

style = document.styles['Heading 1']
font = style.font
font.name = 'Perpetua Titling MT Light'

style2 = document.styles['Heading 2']
font2 = style2.font
font2.name = 'Perpetua Titling MT Light'

style3 = document.styles['Title']
font3 = style3.font
font3.name = 'Perpetua Titling MT Light'

style4 = document.styles['Subtitle']
font4 = style4.font
font4.name = 'Perpetua Titling MT Light'

i = 0

print ('Formatting your novel . . .')
for paragraph in document.paragraphs:

	if paragraph.style.name == 'Heading 1':
#		print ('Chapter Heading converted.')
		paragraph.insert_paragraph_before("\n\n\n\n\n\n")
	elif paragraph.style.name == 'Heading 2':
#		print ('Chapter flair added.\n')
		paragraph.add_run('\n\u2619\u2735\u2767')
	elif paragraph.style.name == 'normal' and re.match("^[0-9\u2619].*?[0-9\u2767]$", paragraph.text): # len(paragraph.text) < 5 and paragraph.text != "":
		paragraph.style = "chaptbreaks"
#		print ('BOLD')
	elif paragraph.style.name == 'normal' and re.match("[A-Z,.\"\u2018\u2019\u201c\u201d\\s].*?[\"\u2018\u2019\u201c\u201d.!?]" , paragraph.text):
		if i == 0:
			print ('tidying up justification. . . ')
			i = i + 1
		paragraph.style = "regular"
#		paragraph.alignment = WD_ALIGN_PARAGRAPH.JUSTIFY_LOW
#		paragraph_format.first_line_indent = Pt(20)

print ("Finished!\n")

document.save(desiredOutput + '.docx')

Well, I think getting it to show up correctly in Word (by hand initially) is going to be an important first step. There's a decent chance that will solve the problem right there (like identifying a setting that was missed) and if not, it will give us the model XML to determine which setting isn't getting in there from python-docx. You could probably use LibreOffice instead, depending on your platform. There are some differences between the two, but I don't expect this would be among them.
I noticed in the "side-by-side" print-layout mode that Word was placing page one on the left, as though it were a verso page, but the gutter was showing up in the right place (on the outside in this case, so page 1 had gutter on the left). I think that just means its multi-page display is not really a print-preview for book-style layout.
This may be related to a "mirror-margins" setting related to page layout (Layout > Margins > Margins > Pages > Multiple Pages: Mirror Margins on my version of Word). I'm not sure where that appears in the XML; we might have to inspect the XML created by Word in a document where that setting has been selected. Once identified there's a decent chance something can be patched in to set it.

I'm going to borrow my wife's laptop when she gets home and try loading it up on there.  She has Word.  I tried Libre but I couldn't find the gutter setting.  I'll let you know what I find once I have a template to compare the original to.   I have to get some other work done so I might not get back to you until tomorrow, but I will get back. Thanks for the help.

Alright, went back to it today.  I discovered that when I look in the Page Setup settings in Word that the preview for the Python-Docx file shows the first page being the left page, and the second being the right.  If I take the file and set the margins manually in Word then it shows the first page as the right page.
I've attached a zip file that has screenshots of the two settings pages, and the example files, both named so they're easy to differentiate.  The one I made in Word doesn't have all of the header/footer pieces, but I don't believe that is causing an issue?  I might be wrong.  I can go back and perfectly format the word version to match.  I mainly kept to the page margins since that was where the problem was manifesting, but sometimes the source of such problems can be more complex then it seems on the surface.  Let me know if you need anything else, or have something else you want me to check.
docx.zip

Okay, I can't figure this out exactly, but what I recommend is that you try creating a "custom" blank "template" .docx that has the margin (and I think "mirror margin") settings you want, then use that as your starting place for this doc, like document = Document("my-marginized-blank.docx").
I think that should work. I'm not able to work out how the mirror-margins setting is stored in the .docx file, mostly because I don't have time for a full exploration and it's not yielding to a quick one. But I think that's an important part of what you want, meaning the gutter appears on the left on odd pages and on the right on even pages.

Alright, thanks for the help.  I'll give the template a go.  I knew that might be a possible workaround, but I was hoping to find a more direct fix.  Well wishes, and thanks again for the time.

Okay, it looks like the mirrorMargins element lives in the settings.xml part, which has partial support in the Settings object: https://python-docx.readthedocs.io/en/latest/api/settings.html#docx.settings.Settings
It doesn't give much API support yet, but critically, it provides access to the root element of the w:settings XML tree on document.settings._element. So if the other approach doesn't work out, this might be another avenue to pursue.

I got it working by adding the mirrorMargins setting directly to the
settings.xml file.  I added a bit to my script that unpacks it, modifies
it, and then (not quite done with tis bit) repacks the whole thing, and I
believe this will fix the issue.  Doing it manually without attempting it
prgramatially works..  . . . and wow, Zip needs some better tool sets.  You
can't overwrite a file in an archive and you can't - easily - repack a zip
without getting a root directory that throws off the entire directory
structure, which is what I'm now fighting with.  If I wasn't so far into
this I might just go back to doing it all manually.
On Wed, Mar 6, 2019 at 6:00 PM Steve Canny<EMAIL_ADDRESS>wrote:

Okay, it looks like the mirrorMargins element lives in the settings.xml
part, which has partial support in the Settings object:
https://python-docx.readthedocs.io/en/latest/api/settings.html#docx.settings.Settings
It doesn't give much API support yet, but critically, it provides access
to the root element of the w:settings XML tree on
document.settings._element. So if the other approach doesn't work out,
this might be another avenue to pursue.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/python-openxml/python-docx/issues/627#issuecomment-470311881,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ5J2eqzZrGjOcaHFjIWiAm7XqlpfBcqks5vUEh4gaJpZM4bfLzp
.

--
Heath Pfaff
www.fantasymeetshorror.com

I spoke too soon in my last message, but I thought I would let you know
what I've found after digging around through this for quite some time.
There is a setting in Word under layout, page-setup, layout(tab) that lets
you set sections to start on "odd pages."  Once that is set it fixes my
problem.  I've run a comparison of the settings.xml between having that
option set to "normal" and to "odd page"  but the only differences between
the two files were the w:rsid save records.  I don't see anything in there
that looks like it changes due to this setting being switched, which makes
me think it might be somewhere else in the document, perhaps part of the
document.xml itself.
For now I'm going to take a break from this.  I can do most of what I want
programatically, and I'll just have to flip this last option manually for
the time being.  Thanks for all the help you offered and the time you spent
looking into this with me.  I wouldn't say it has been "fun," but I've
certainly learned a great deal, and that's always a positive.
On Wed, Mar 6, 2019 at 8:57 PM Somber Fox<EMAIL_ADDRESS>wrote:

I got it working by adding the mirrorMargins setting directly to the
settings.xml file.  I added a bit to my script that unpacks it, modifies
it, and then (not quite done with tis bit) repacks the whole thing, and I
believe this will fix the issue.  Doing it manually without attempting it
prgramatially works..  . . . and wow, Zip needs some better tool sets.  You
can't overwrite a file in an archive and you can't - easily - repack a zip
without getting a root directory that throws off the entire directory
structure, which is what I'm now fighting with.  If I wasn't so far into
this I might just go back to doing it all manually.
On Wed, Mar 6, 2019 at 6:00 PM Steve Canny<EMAIL_ADDRESS>wrote:

Okay, it looks like the mirrorMargins element lives in the settings.xml
part, which has partial support in the Settings object:
https://python-docx.readthedocs.io/en/latest/api/settings.html#docx.settings.Settings
It doesn't give much API support yet, but critically, it provides access
to the root element of the w:settings XML tree on
document.settings._element. So if the other approach doesn't work out,
this might be another avenue to pursue.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/python-openxml/python-docx/issues/627#issuecomment-470311881,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ5J2eqzZrGjOcaHFjIWiAm7XqlpfBcqks5vUEh4gaJpZM4bfLzp
.

--
Heath Pfaff
www.fantasymeetshorror.com

--
Heath Pfaff
www.fantasymeetshorror.com

I wonder if it's this setting in the section:
https://python-docx.readthedocs.io/en/latest/api/section.html#docx.section.Section.start_type
It had not occurred to me, but that makes some sense now that you mention it. You have to choose which type of section (break) when you insert one, but there is always a single section already, even in a new blank document. Might be worth a quick try.
It might also be related to the fact you have a page 0 in that file. If it started on page 1 maybe the automatic behavior would work the way one would expect.

That did it, the Section.start_type was exactly what I needed.  Wow, I even
read that whole section early on in the process.  I guess I just went so
far down this hole I forgot all about it.  The script now works 100% and I
just have to go back through and clean it up.  You've been awesome, Steve.
Thanks!
On Fri, Mar 8, 2019 at 12:39 PM Steve Canny<EMAIL_ADDRESS>wrote:

I wonder if it's this setting in the section:
https://python-docx.readthedocs.io/en/latest/api/section.html#docx.section.Section.start_type
It had not occurred to me, but that makes some sense now that you mention
it. You have to choose which type of section (break) when you insert one,
but there is always a single section already, even in a new blank document.
Might be worth a quick try.
It might also be related to the fact you have a page 0 in that file. If it
started on page 1 maybe the automatic behavior would work the way one would
expect.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/python-openxml/python-docx/issues/627#issuecomment-471012991,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQ5J2YBZy6O4ZdArb7WQ_mWncoiJkg6Uks5vUqBEgaJpZM4bfLzp
.

--
Heath Pfaff
www.fantasymeetshorror.com

Glad it worked out :)


Called methods improvements

Added CalledAtNWith method to conveniently check if a certain call (eg, the second or third) had the given arguments. I find that this is useful in quite a lot of testing scenarios
Made error messages from argument matchers more descriptive
Fixed some godoc statements

Would it be possible to fill out a symmetric match for the gomega testutil? Here is the implementation of BeCalledNWith. Having BeCalledAtNWith as well would be really great.
Otherwise I like the general approach of this PR and won't block 🎉


Mark all classes as final to discourage inheritance

Classes should be used via composition rather than extension.
This reduces our API footprint and avoids future BC breaks by avoiding
exposing its internal assumptions.
Builds on top of #128

@jsor funny enough before one loop can't be mocked 😂

Rebased now that #132 is in, this should fix the build error :shipit:

Yup looks good 👍


Init

From: https://github.com/8p/guzzle-wsse-middleware/pull/13
Todo:

[x] add GuzzleBundle in requirements in composer.json
[x] rename GuzzleWsseBundle into GuzzleBundleWssePlugin
[ ] tests
[x] travis build

Changes Unknown when pulling 64e5cdc84fd3c3deff03de82dda3af4944b971e3 on init into ** on master**.

Very nice! Just a question, @gregurco: I thought you are ging to use wsse-plugin and creating the bundle around it. So the bundle only created the bridge to make it usable in guzzle bundle / symfony.

I thought about that but in this case I had  to do one more PR in wsse-plugin with many changes and to track dependency on two repos. I decided that guzzle-bundle with version <7 will use wsse-plugin but >=7 will use this repo. Just not to have many repos with 1-2 files. What do you think? What's your suggestion?

Yeah, that's totally fine for me 👍  I mean, we are talking about 1-2 files, as you said.


I had some files in which there was a reference to some links in my computer .. While editing some of those files i replaced the directory with another directory and saved the file. All of my work was erased as the directory was changed somehow.. Please help me get back the files

Prerequisites

[ ] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
[Description of the issue]
Steps to Reproduce

[First Step]
[Second Step]
[and so on...]

Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.
Additional Information
Any additional information, configuration or data that might be necessary to reproduce the issue.

Thanks for reaching out and sorry for the trouble - can you update the issue body and fill out the issue template? The information is super helpful for us when investigating issues. In particular, for the steps to reproduce, please provide specific and numbered steps so that we can better understand what happened.
Once you provide this information we can re-open and go from there.

We require the template to be filled out on all new issues and pull requests so if you can open a new issue with the template filled out, that would be helpful for us. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us half way :grinning:


Incomplete installation on Mac OS 10.9.5?

I did this:
sudo gem install boojs

and after I entered my password, I got this:

Fetching: phantomjs-<IP_ADDRESS>.gem (100%)
Successfully installed phantomjs-<IP_ADDRESS>
Fetching: greenletters-0.3.0.gem (100%)
Successfully installed greenletters-0.3.0
Fetching: boojs-0.0.16.gem (100%)
Successfully installed boojs-0.0.16
Parsing documentation for phantomjs-<IP_ADDRESS>
Installing ri documentation for phantomjs-<IP_ADDRESS>
Parsing documentation for greenletters-0.3.0
Installing ri documentation for greenletters-0.3.0
Parsing documentation for boojs-0.0.16
Installing ri documentation for boojs-0.0.16
3 gems installed
The I tried this:
boojs

and I got this:

Phantomjs does not appear to be installed in /Users/myname/.phantomjs/1.9.8/darwin/bin/phantomjs, installing!
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     0    0     0    0     0      0      0 --:--:--  0:00:04 --:--:--     0
100 9187k  100 9187k    0     0   838k      0  0:00:10  0:00:10 --:--:-- 1979k
Archive:  phantomjs-1.9.8-macosx.zip

and some creating/inflating, and at the end this:

Successfully installed phantomjs. Yay!
Removed temporarily downloaded files.

and that's all, no prompt. I did Ctrl-C and boojs again, but no prompt.
I then removed an old phantomjs 1.9.1, and made sure that the 1.9.8 was now in my PATH, but I still get no prompt from books, and no reactions when I try some commands.

You may also want to try an update, there have been many improvements over the past 24 hours.
gem uninstall boojs
`gem install boojs``
Also, could you execute these two commands and paste them into here, that would help diagnosing the issue as this could be many possible problems:

ruby -v
gem env

Sorry, I see that my Ruby is to old:
$ ruby -v
ruby 2.0.0p481 (2014-05-08 revision 45883) [universal.x86_64-darwin13]
$ gem env
RubyGems Environment:

RUBYGEMS VERSION: 2.0.14
RUBY VERSION: 2.0.0 (2014-05-08 patchlevel 481) [universal.x86_64-darwin13]
INSTALLATION DIRECTORY: /Library/Ruby/Gems/2.0.0
RUBY EXECUTABLE: /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
EXECUTABLE DIRECTORY: /usr/bin
RUBYGEMS PLATFORMS:

ruby
universal-darwin-13

GEM PATHS:

/Library/Ruby/Gems/2.0.0
/Users/myname/.gem/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/gems/2.0.0

GEM CONFIGURATION:

:update_sources => true
:verbose => true
:backtrace => false
:bulk_threshold => 1000

REMOTE SOURCES:

https://rubygems.org/

I'll consider upgrading my Ruby.

Have you tried https://rvm.io?  You just run \curl -sSL https://get.rvm.io | bash -s stable your terminal and follow the directions.  The native ruby environment that comes preinstalled with Mac OS X is broken.


Why are snapshot role hashes not provided in the timestamp role?

From the TUF spec, 5.5.2:

Check against timestamp role’s snapshot hash. The hashes of the new snapshot metadata file MUST match the hashes, if any, listed in the trusted timestamp metadata. This is done, in part, to prevent a mix-and-match attack by man-in-the-middle attackers. It is safe to check the hashes before the signatures, because the hashes come from the timestamp role, which we have already verified in the previous step; it is also a quick way to reject bad metadata. If the hashes do not match, discard the new snapshot metadata, abort the update cycle, and report the failure.

It seems like no hashes are published https://tuf-repo-cdn.sigstore.dev/timestamp.json. They mention man-in-the-middle, but I guess the same could be achieved by a server compromise, so TLS would protect in one case but not the other. Is there a reason why this is not considered useful?

There is an advantage to using hashes but it's not in my opinion a massive one:

Lack of hashes does not meaningfully  enable mix-and-match attacks with current TUF spec (with "consistent snapshot" feature): if repository gives the client an old snapshot, the client will refuse because the version is incorrect
the potential protection covers the json parsing and canonicalization ( because after that point we can verify the actual signatures which are a significantly stronger protection than the hashes). This is certainly an attack surface  but...
a malicious repository could just stop using hashes whenever it wants -- there's no repository level flag that says "this repository always uses hashes". So the hash protection really only works against someone who can e.g. replace snapshot metadata with malicious data but can't for some reason do the same attack on root or timestamp metadata (which are not protected by hashes)...

So using hashes could be useful but not a game changer. The main reason hashes are not currently used is that maintaining the repository becomes a little more complicated with hashes -- while tuf-on-ci tool was being developed we really tried to keep it simple and did not originally implement hashes. We could consider adding that now that things seem to be working solidly.
Another reason some people might avoid the hashes is that it does prevent a use case where additional signatures are added after the metadata is published (Imagine a case where published metadata was signed by threshold of signers but not all of the signers, and then the remaining signers still want to sign) . To be fair this sounds unusual and tuf-on-ci certainly does not do this.

Hey, thank you for the detailed explanation. I am mostly asking for both curiosity of TUF internals and being sure I implement a reasonably secure client. This really helps.


tsx should have option to not do extra things

Bug description

tsx should have option to not do extra things.
Reproduction
Prepare
reproduce1.mjs
// @ts-check
import playwright from 'playwright-core'
const browser = await playwright.firefox.launch()
const browserContext = await browser.newContext()
const page = await browserContext.newPage()
await page.goto('http://<IP_ADDRESS>:1234/')
await page.waitForFunction('() => true')
await page.close()
await browserContext.close()
await browser.close()

$ cp reproduce1.mjs reproduce2.mts

Actual
$ npm exec -- tsx reproduce1.mjs
node:internal/process/esm_loader:97
    internalBinding('errors').triggerUncaughtException(
                              ^

page.waitForFunction: __name is not defined
@debugger eval code line 195 > eval:1:95
evaluate@debugger eval code:197:17
@debugger eval code:1:44

    at file:///path/to/reproduce1.mjs:7:12 {
  name: 'Error'
}

Node.js v18.15.0

$ npm exec -- tsx reproduce2.mts
node:internal/process/esm_loader:97
    internalBinding('errors').triggerUncaughtException(
                              ^

page.waitForFunction: __name is not defined
@debugger eval code line 195 > eval:1:95
evaluate@debugger eval code:197:17
@debugger eval code:1:44

    at <anonymous> (/path/to/reproduce2.mts:7:12) {
  name: 'Error'
}

Node.js v18.15.0

Expected
$  node --loader @esbuild-kit/esm-loader reproduce1.mjs && echo OK
(node:615388) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
OK

$ node --loader @esbuild-kit/esm-loader reproduce2.mts && echo OK
(node:615873) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
OK

Environment
Binaries:
    Node: 18.15.0 - /usr/sbin/node
    Yarn: 1.22.19 - /usr/sbin/yarn
    npm: 8.19.2 - /usr/sbin/npm

Can you work on a fix?

[ ] I’m interested in opening a pull request to address this issue.

Related
https://github.com/esbuild-kit/tsx/issues/113

tsx should have option to not do extra things.

Not sure what you're talking about. Can you elaborate?
Seems like a duplicate of #113?

@privatenumber

Seems like a duplicate of https://github.com/esbuild-kit/tsx/issues/113?

No.
https://github.com/esbuild-kit/esno/blob/v0.14.1/esmo.mjs
For example<EMAIL_ADDRESS>just means node --loader esbuild-node-loader.
tsx does not mean node --loader @esbuild-kit/esm-loader, they have different output.
node --loader @esbuild-kit/esm-loader  works fine.
But tsx works unexpected.

I see.
node --loader @esbuild-kit/esm-loader works for your input because playwight-core is a CommonJS package, and @esbuild-kit/esm-loader only transforms ESM files.
tsx does node --loader @esbuild-kit/esm-loader --require @esbuild-kit/cjs-loader which adds support for transforming CommonJS too (transforming playwright-core). But currently, it transforms more than it needs to (it doesn't need to transform playwright-core).

mark

same error here
mark

playwright-core should work expectedly now with https://github.com/privatenumber/tsx/releases/tag/v4.0.0
Hope it works well for you!


page-level-url

New Feature

/pages now have a url property that must be a valid url and will not be expanded, cloned or resolved.
On publish, a /uris/<new page> will be created from the url.
Publishing will 400 if the url is missing.

:+1:

+1


elm-format doesn't work on save

Hi,
I can access elm-format globally and have no problem running it from VSCode's terminal but when I try to use it on save it just doesn't work anymore. It tells me that I should install it and check if it is on my path.  This is my settings.json:
{
    "[elm]": {
        "editor.formatOnSave": true,
        "editor.formatOnSaveTimeout": 1500
    }
}

It has been like that since I upgraded to 0.19. After noticing it doesn't work anymore I reverted back my elm-format and it worked again! But recently that one also stopped working. It might be connected to the update for the extension recently.

Could you check if in your "path" variable elm 0.19 is included?
it might have been not includes with the upgrade from 0.18. since the auto format is still working for me.

Thanks for the reply! It is included.

I've been having the same issue on and off since 0.19 came out. Same settings apply to me, though haven't set a timeout.

I'm using Windows10 64bit.
it occurs same issue.
I set timeout 3000.then format work for me.
{
    "[elm]": {
        "editor.formatOnSave": true,
        "editor.formatOnSaveTimeout": 3000
    }
}

It seems like setting the timeout works for some but not everyone.

suggested solution did not work for me =( I'm on MacOS

For me I had a problem because elm-format is trying to detect the version of elm.
It needs to be run from the folder that has elm.json
But I like opening up individual files in vs code (not the entire folder / project). So elm-format was failing silently.
Opening up the folder with elm.json is my workaround... but I would prefer if the extension could look for an elm.json in parent directories... and have setting for choosing a default elm version.

I can get elm-format to work on save in atom, vim, and emacs, but I cannot seem to get it to run from inside vscode. I've tried the above tricks and also tried playing around with the look up paths. Not sure what the issue is :(

Just as @insight1111 did, doubling the suggested time out for windows machines fixed the issue for me. Instead of 1500 I set it to 3000.
{
"[elm]": {
        "editor.formatOnSave": true,
        "editor.formatOnSaveTimeout": 3000
    }
}

This looks like a possible duplicate: https://github.com/Krzysztof-Cieslak/vscode-elm/issues/294

Interestingly it does appear that in my case that this issue is happening only for a specific file which happens to be 2182 lines long. Another file in the project is being handled just fine through VSCode and upon save.

setting a timeout worked for me too, 1000 was enough, didn't test the limit though to find the smallest needed. so thx for the tip.
{
"[elm]": {
        "editor.formatOnSave": true,
        "editor.formatOnSaveTimeout": 1000
    }
}


Parsing Transform tags

Within the prtr ICC profile, a set of tags which I will list below define a set of color transform. The issue here is that these tags can regularly defy the size set for them in the tag in the tag table. A solution on how to parse them would be nice as I cannot figure this out myself.
Some info about these special tags can be found in this doc.

A2B0
A2B2
A2B1
B2A0
B2A1
B2A2

Hello, at the moment this module only looks for tags with a tagType it knows about, namely desc and text - https://github.com/lovell/icc/blob/master/index.js#L83-L109
Perhaps it should provide a bit more data about the presence of other tags, including the 6 you list, exposing the raw data as a Buffer. In the case of the A2B and B2A tags, these would be look up tables (LUTs) with a tagType of mft1 (8 bit) or mft2 (16-bit).
Happy to accept a PR if you're able.

I will try to implement this tag in my ICC implementation first. When I get that working i will port that tag implementation to you ICC parser.

What is the status of this, I've looked through #3 and seems to meet the goals of this issue? I'd be interested in extending this so that functions could be derived from the A2Bx, B2Ax tables.

I'd be very happy to accept a new PR if you're able, thank you. The work in #3 could be used as the basis with the addition of more unit tests to cover all the extra logic.

I've added a few new tests and fixtures to the repo, including the ICC "probe" profiles that include sample transform tags. This should make testing a little easier should anyone like to work on a follow up to the original PR at #3.

I am trying to work on a PR, do you have an idea how you would like the final json format to be ?
Would it be something like this ? with a major of upgrade since we put all previous answers in a key header
{
header: {
version: '2.1',
  intent: 'Perceptual',
  cmm: 'Adobe',
  deviceClass: 'Printer',
  colorSpace: 'CMYK',
  connectionSpace: 'Lab',
  platform: 'Apple',
  manufacturer: 'Adobe',
  creator: 'Adobe',
  tagCount: 10,
},
tables:{
 A2B0: [],
    A2B2: [],
    A2B1: [],
    B2A0: [],
    B2A1: [],
    B2A2: [],
    gamt:
}
}

or should we just have something like this
{
version: '2.1',
  intent: 'Perceptual',
  cmm: 'Adobe',
  deviceClass: 'Printer',
  colorSpace: 'CMYK',
  connectionSpace: 'Lab',
  platform: 'Apple',
  manufacturer: 'Adobe',
  creator: 'Adobe',
  tagCount: 10,
tables:{
 A2B0: [],
    A2B2: [],
    A2B1: [],
    B2A0: [],
    B2A1: [],
    B2A2: [],
    gamt:
}
}

@Aminelahlou Thank you very much for picking this up and tackling it again.
I think I'd prefer not to alter the existing response structure and instead add to it.
Perhaps we can have A2B0, A2B1 and A2B2 as direct properties in the response? Or maybe an a2b property with perceptual, colorimetric and saturation as children might be easier to understand?
In terms of what lives under this, the structure in the closed-but-not-forgotten PR #3 looked pretty good to me.
https://github.com/lovell/icc/pull/3/files#diff-e727e4bdf3657fd1d798edcd6b099d6e092f8573cba266154583a746bba0f346R62
If the raw lookup table data could use the relevant TypedArray e.g. Uint8Array or Uint16Array then that would be great.
{
  version: '2.1',
  ...
  a2b: {
    perceptual: {
      inputChannels: ...
      matrix: ...
      ...
    },
    colorimetric: { ... }
    ...
  }
}

I'm trying to achieve this at the moment. Is there anything wrong with what PR https://github.com/lovell/icc/pull/3 is doing at the moment? I see it needs more tests but the current state of parsing is useful (not sure returning a buffer instead of a processed array makes sense). I'm working on attaching functions for A2B/B2A/gamt but I'm struggling with the testing step.
I see the probe profile in the fixtures but I'm unsure about how to proceed to see if the extracted tables are correct or if the transform functions derived give the correct output.

@MathieuLoutre Thanks for taking a look at this, always happy to accept/review a (partial) PR if you're able.
If you hadn't seen, the expected behaviour of the probe profile is documented at https://www.color.org/probeprofile.xalter

The rendering intent transforms (BToA tags) of the probe profile ignore the a* and b* components of incoming PCS colors, and map the L* components directly to monotone tints of process colorants. (L* = 0 is rendered as maximum colorant coverage, and L* = 100 is rendered as unmarked media.) The B2A0 tag (perceptual rendering intent transform) renders the L* values as tints of pure cyan. The B2A1 tag (relative colorimetric intent transform) renders them as tints of pure magenta, and the B2A2 tag (saturation intent transform) renders them as tints of pure yellow.

Thanks @lovell! I had a look at this page but couldn't make sense of it at the time of my previous comment. Now that I've worked with ICC profiles for a few days, I think I understand it.
At the moment, the unit tests have something like this:
const B2A0Min = profile.B2A0.transform([0, 0.5, 0.5]);
assert.deepStrictEqual(B2A0Min, [1, 0, 0, 0])
const B2A0Max = profile.B2A0.transform([1, 0.5, 0.5]);
assert.deepStrictEqual(B2A0Max, [0, 0, 0, 0])

This passes successfully (transform is the function that takes the input and passes it through the various tables). However, it's maybe a little unclear from the above text whether a value of 0.5 in L* should yield a value of 0.5 in Cyan. That's what I understood from "monotone tints of process colorants" but at the moment, that returns 1 for C as well.
That being said, I'm. not sure how to approach the unit tests which currently verify the output with deepStrictEqual and as a result, we'd need a source of truth for each table. Would you be happy to exclude the tables from the equal check and use the transform functions as a way to verify that they're correct?

...use the transform functions as a way to verify that they're correct?

That sounds sensible, yes please.

Hi @lovell! I've made a new PR (#7) that picks up the work from #3. The A2B0 tests are failing (everything else seems fine). I can't pick out why. It returns 0.61 instead of a value between 0.7 and 1 as explained in https://www.color.org/probeprofile.xalter.
Any ideas?


Missing ImageIndex Artifact on ECR

I downloaded the latest release v0.1.1 and run it within a docker agent to test how soci-wrapper works, it runs smoothly and the artifact Soci Index was pushed to ECR. But there was no artifact of Image Index had been created and pushed to ECR. According to this POC blog, these two artifacts should come together for AWS fargate to work with the lazy loading feature.

Thanks, I confirmed the issue. I downgraded soci-snapshotter and oras-go packages, and confirmed it's now fixed (v0.1.2). I'll wait for the original repo to upgrade soci-snapshotter to v0.5.0.

Please reopen this issue if you find anything further, thanks!

It works with v0.1.2.


[ONBOARDING] General Member - GitHub (Additional Members)

TODO General Member Onboarding
This is an issue created to onboard new TODO Group General Members.
Company
GitHub
Members

Lynette Rayle @elrayle
Eric Sorenson @ahpook
Kevin Dangoor @dangoor
Andrew Henry @ajhenry
Derek Prior @derekprior
Zack Koppert @zkoppert

Contact Information

[x] For each representative of the General Member company, collect the
following:

name
pronouns
company email address
GitHub username
whether or not the representative is the primary contact for the company

[x] Update the members list to included the collected contact information

[x] administration repo
[x] governance repo

Communication channels
Ensure that member representatives have joined the following:

[x] TODO Group Slack
[x] Community Mailing List

GitHub

[x] Invite members to the Core GitHub team
(this will send them an invite to the GitHub organization and grant them
access to private repositories)

Private channels
Add members to the following:

[x] General Member mailing list
[x] General Member Slack channel: #private

Meetings and Calls
Google Groups should automatically invites members to meetings, but ensure that
they have invites for the following meetings:

[x] General Members Touchpoint
[x] General Members AMA session

Resources and initiatives

[x] Ensure members are aware of the General Members onboarding guide

@ashleywolf just sent the invites & access to all of the OSPO @ Github additional members from this ticket 👍 If nothing else is missing, please let me know to close the ticket 😊


Android API 31: bottomsheet is going below the virtual buttons.

I can add a bot padding to the content as a workaround, when android displays those virtual buttons (if I find how to detect that).

Android Simulator Pixel 5 / API 31.
mapsui 4.0.0-rc2

btw ty for the fix to scrolling.

I observed similar behavior, which might be related to this issue.
How to reproduce:

Set the bottom sheet height to a fixed value, e.g. RatioDetent with Ratio=0.95
Set the bottom sheet content up to fill its parent. For example in xaml you could set the content to this:

<Grid RowDefinitions="*,100">
            <Grid Grid.Row="0" BackgroundColor="Orange" />
            <Button Grid.Row="1" HeightRequest="100" Text="this will be cut off" />
</Grid>

The important part in this example is the "*" which makes the grid take all available space provided by its parent (the bottom sheet).
Running this, you should see that the button is only half visible - if at all. It seems that the bottom sheet provides more space to its child that in should. Taking a smaller ratio for the detent, e.g. 0.6 will cut off a larger portion of the content and the button will not be visible at all.
With Ratio 0.95:

Investigation
In the android specific BottomSheetManager.cs in the CreateLayout method, specify layout parameters when adding the content containerView to the layout:

This seems to  help a bit with the issue and might be part of the solution. With this change, different bottom sheet sizes do not influence the overflow size anymore, so RatioDetent with Ratio 0.6 or 0.95 now have the same amount of overflow.
On the Google Pixel 7 Pro (or any Google device actually, I tested a few more using an emulator) the overflow height is now exactly 8 device independent pixels, which is much more consistent than the previous overflow.
I also tested on the Samsung A52 and here the overflow is 32 dip. So this makes the overflow consistent for across different settings on the same device, but on a different device the overflow height can still be different, indicating that this might be caused by the OS or the screen in any way.
I compared it against the navigation bar height and there does not seems to be a direct linear relationship between the amount of the remaining overflow and the height of the navigation bar: On the Google phones the navigation bar has 24 dip, so 3x the overflow height. On the samsung phone the navigation bar has 48 dip, so 1.5x the overflow height.
I am out of ideas at this point and hoping that someone else can continue the investigation and make this work properly.

I added @madp4ul demo to the sample project and updated the android height sizing to take in account the container height and any potential display cutouts.
Please try rc5 and let me know if this fixes the issue

Unfortunately i dont have the Samsung phone available to me right now so i can not check whether the bottom "padding" is consistent between devices, but it seems to be fixed on the google pixel phone. Thank you very much!
This is the same example in my code base now:

Hi,
A new version was released with a better height calculation logic. Please test it out and let me know if this is still an issue


forward the React ref

This enables you to
this.badgeRef = React.createRef()

// ...

<Badge ref={this.badgeRef}>A badge</Badge>
<UncontrolledTooltip target={this.badgeRef}>But no badger</UncontrolledTooltip>

(https://reactjs.org/docs/forwarding-refs.html)

[x] Bug fix
[x] New feature
[ ] Chore
[ ] Breaking change
[ ] There is an open issue which this change addresses
[x] I have read the CONTRIBUTING document.
[x] My commits follow the Git Commit Guidelines
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.

[ ] I have updated the documentation accordingly.

[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@TheSharpieOne so innerRef?

Yes, please use innerRef.

@TheSharpieOne see 82f4e8f
(will squash when necessary)

Several other components need it to, e.g Button


TF-M: Use secure services in board and SoC init

Use TF-M platform partition for secure services in SoC and board init code that can only be done from secure processing environment.
Since nothing of zephyrs init code is included in the secure image with TF-M enabled this code is effectively excluded in the current configuration.
Note: The platform services are not yet available in the current version of TF-M.
TF-M review: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/12685
Will have to wait for TF-M 1.5 release and cherry-pick the above patch.

@SebastianBoe can you take a look please?

@SebastianBoe can you take a look please?

This might be easier to review once we sort of the final TF-M 1.5 issue, pending some feedback from ST.

@SebastianBoe @tejlmand I reverted the change to include the TF-M header in all cases.
This caused issues with the psa/crypto_*.h headers, which are exposed by both TF-M and MbedTLS. Even though these are both at version 3.0.0 they are not compatible.
This can be done at a later time instead once we have figured out what is actually going on with those headers.

From the description:

This fixes the following issues.

Logging over UART not working from the network core when TF-M is enabled.
TF-M CI tests not compiling for nrf5340 and nrf9160
NRF Cache Kconfig not functional when TF-M is enabled.

Taking this into 3.0.0 as a bugfix for the aforementioned issues.


backup: add "none" storage type

If “pv-provisioner” is set to “none”, then operator won’t create any
storage class and users couldn’t make use of PV backup feature.
Also fix that if s3 config isn’t set but spec asks for “S3” storage
type, we will reject it immediately.
fix https://github.com/coreos/etcd-operator/issues/921

@xiang90 @uruddarraju

fixed

lgtm


Where is the urd data?

I’m interested to contribute to this project, therefore I’m trying to first understand how it works. I see both README and CONTRIBUTING refer to Urdu, but I can’t find Urdu’s data anywhere, and I got this error when I tried to run the check:
> shaperglot check font.otf urd
Language '['urd']' not known

Alrighty. Mention me when you’re happy with how the new reality is documented! Meanwhile @roberto-arista and I will play with the Latin data.

@RickyDaMa Use BCP47 language tags with script en_Latn ga_Latn it_Latn ... like gflanguages does.


Your discord invite link is broken, wanted to ask about how to set up Vault

I have Vault and an Eco Plugin, the plugin page on Modrinth mentioned I can sell Networks with Vault Economies, can't seem to see that in the conf file

Hey, thanks for reporting! The link on Modrinth is fixed now and I updated the description.
The economy feature was abandoned in v1.2.1 after it wasn't used by anyone for almost a year.
If enough people want it, I will reimplement it in v3


build failed. cannot find -lxml2

when I build tvm from source with cuda version, I encounter the following problem. I have installed libxml2 with conda, but the problem still exists. I also try installing libxml2 from source from website, and adding corresponding lib dir to LD_LIBRARY_PATH, it cannot solve the problem.
[  1%] Built target project_libbacktrace
[  1%] Built target tvm_libinfo_objs
[ 10%] Built target tvm_runtime_objs
[ 10%] Built target tvm_runtime
[100%] Built target tvm_objs
[100%] Linking CXX shared library libtvm_allvisible.so
[100%] Linking CXX shared library libtvm.so
/usr/bin/ld: cannot find -lxml2
collect2: error: ld returned 1 exit status
/usr/bin/ld: cannot find -lxml2
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/tvm.dir/build.make:2231: libtvm.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:177: CMakeFiles/tvm.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
make[2]: *** [CMakeFiles/tvm_allvisible.dir/build.make:2231: libtvm_allvisible.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:260: CMakeFiles/tvm_allvisible.dir/all] Error 2

I have met the same problem. How to solve this ?  Thank you so much


Any documentation pointers ?

is there a documentation and/or usage examples something similar to cocotb-axi

+up @mgielda
any issues that limits the cocotb compatibility version to < 1.7?


Performance

@keremispirli, we have a "performance-improvement" label. Do we need this epic at all?

If we had a target to deliver these improvements by a deadline/milestone, then this epic would make sense. But only #133 has a set milestone for Q4,  some have 2018H1 and some have none; so this epic does look meaningless.


CVE-224-23444 security vulnerability fix issue

Excuse me, isn't this tokenization warehouse maintained by anyone?
The CVE-224-23444 vulnerability, disclosed on August 1, 2024, appears to require an upgrade to ES version v8.13+. It has been 5 months since then, but the repository has not yet provided the relevant IK synchronized update version.
Has the warehouse given up on repairs now?

Hi, @FreemanKevin, I think you are refer to ES's version, we do have updated plugins, all versions should be address as fast as we can, since the plugin code is not necessary to touch, we didn't need to tag for any versions change only,  and you can find all the packaged version here: https://release.infinilabs.com/analysis-ik/stable/

Wow, thank you for your reply. I'm glad to see the link for this packaged version. It's really the first time I've known about it. Previously, if I needed plugin packaging files, I always obtained them from the GitHub repository. I always thought that the ik plugin lagged behind the iteration speed of Elasticsearch version updates, so when we use Elasticsearch version, we are completely constrained by the updated version of ik plugin. Now we have really solved a big problem.
Finally, can I provide you with the link to update all packaged versions directly to the Readme.md file? It seems that many people may not be aware of this like me.
Thanks a lot,
Have a good day.

There should be a link in README already, but it seems many people not aware of this, also there is a Latest release noticed that, I think i may cleanup old releaes to make it simplier and cause less confusion


Dependencies of dependencies are being installed

I'm seeing dependencies of dependencies being installed in my own app when using this plugin.
e.g., with<EMAIL_ADDRESS>if I require('react-fa') (which has a dependency on font-awesome), the following happens:
webpack building...
npm install --save react-fa
<EMAIL_ADDRESS>node_modules\react-fa
└──<EMAIL_ADDRESS>npm install --save font-awesome
<EMAIL_ADDRESS>node_modules\font-awesome

If I already have react-fa installed locally when I start my webpack server, then font-awesome will be installed when I start it up.

Hi @insin,
I just tried to look at the problem and actually failed to run my own (manual) tests so it might take a while for me to fix this problem. I am currently not sure what the future holds for this plugin but a lot of discussion takes place here which might eventually result in a completely new plugin (or whatever).


Handle mySNU login request

Send mysnu login request when click login button.
TODO:

backend

modify major info api definition ( when major_info is true)

ex) "majors": [{"type": "주전공", "name" : "컴퓨터공학전공"}, ...]

frontend

handle major list when major_info is true

Have you tested that frontend gets the response correctly? If so, I'll approve.
Then I'll update API at #28, with changing url-encoded request parameters to JSON.

Yes, we can login by mysnu successfully.


useDarkMode() always returning false on simulator

Hi,
just implemented this library, and using
const isDarkMode = useDarkMode()
within a component leads always to return false on ( iOS ) simulator.
I enabled dark mode via: settings-> developer -> Appearance -> Dark Mode
Does it work on simulator or devices only?
Thanks!

Try disabling debugger

perfect, that works! unfortunately, i need to use Alert to check for some behaviours then.
Cheers, thanks for superfast reply!


update snapshot to reference master branch - fixes infura issue

@andytcf @clementbalestrat @evgenyboxer It seems that something is wrong with new dependency reference. CI failed on npm install, so I've regenerated package-lock.json which fixed the issue. However now, npm build is failing.


Failed to upload stub when flashing ESP32-S2 via built-in USB_OTG

Uploading to the same ESP32-S2 via a CP2102 works okay, but with the built-in USB_OTG in download mode, fails as follows:
esptool.js v0.1-dev
Serial port WebSerial VendorID 0x303a ProductID 0x2
Connecting..._connect_attempt default_reset false

Sync
Sync err Error: Timeout

.Sync
Sync err Error: Timeout

.Sync
Sync err Error: Timeout

.Sync
538052359

Chip Magic 7c6
Detecting chip type... ESP32-S2
Chip is ESP32-S2
Features: Wi-Fi,ADC and temperature sensor calibration in BLK2 of efuse
Crystal is 40MHz
MAC: 7c:df:a1:0f:4d:6e
Uploading stub...
mem_begin 4316 1 6144 40028000
check_command enter RAM download mode
check_command write to target RAM
Error: Timeout

This is probably a duplicate of https://github.com/espressif/esptool-js/issues/38.


ingress-contour Support

contour   projectcontour.io/ingress/ingress-contour-contour
What would you like to be added:
We would like to migrate Countour-envoy provider , is not listed on the existing 3
Why this is needed:
this will help us migrating a lot of our existing
We are getting error
`...go/bin/ingress2gateway print -n backend                                                      6s
Error: failed to read istio resources from the cluster: failed to read resources from cluster: failed to read gateways: failed to list istio gateways: failed to get API group resources: unable to retrieve the complete list of server APIs: networking.istio.io/v1beta1: the server could not find the requested resource
Usage:
ingress2gateway print [flags]
Flags:
-A, --all-namespaces      If present, list the requested object(s) across all namespaces. Namespace in current context is ignored even
if specified with --namespace.
-h, --help                help for print
--input_file string   Path to the manifest file. When set, the tool will read ingresses from the file instead of reading from the cluster. Supported files are yaml and json
-n, --namespace string    If present, the namespace scope for this CLI request
-o, --output string       Output format. One of: (json, yaml) (default "yaml")
--providers strings   If present, the tool will try to convert only resources related to the specified providers, supported values are [ingress-nginx istio kong apisix] (default [kong,apisix,ingress-nginx,istio])`

The error your are getting is related to https://github.com/kubernetes-sigs/ingress2gateway/issues/138
In the meantime, you can solve it by specifying the provider/s you need with the flag.
/cc @sunjayBhatia for contour support request

Hi @LiorLieberman  @sunjayBhatia  Countour is not in the list of supported providers , so we can not select it , this is for adding that provider to the supported ones

To add the provider for the supported providers, someone need to implement the provider specific logic. Thats the reason I cc'd @sunjayBhatia

Yep, I haven't had a lot of bandwidth to implement contour support in ingress2gateway, but if there is a willing contributor I would definitely help shepherd the changes!

Yep, I haven't had a lot of bandwidth to implement contour support in ingress2gateway, but if there is a willing contributor I would definitely help shepherd the changes!是的，我没有足够的带宽来在 ingress2gateway 中实现轮廓支持，但如果有愿意的贡献者，我肯定会帮助引导这些更改！

@sunjayBhatia  @LiorLieberman   hi, i want to give it a try, can u tell me how to finish it?

/assign


Launching spark clusters in QHub

per Chris:
Create a general launcher for launching various clusters. IE Spark, MPI, Dask
Similar to kubernetes launcher. Have a CRD (https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/) that launches higher level objects. Could be leveraged for CDS dashboards and the above. Does lock us into using Kubernetes. There already exists a pyspark CRD.

@tylerpotts @costrouc can you please confirm the status of this? the linked issue seems to be open so this should too?


⚠ Contemporanea has degraded performance

In 2f614b1, Contemporanea ($SITE_CNTM) experienced degraded performance:

HTTP code: 200
Response time: 26191 ms

Resolved: Contemporanea performance has improved in c0c15ed.


Center image shields

Alright one second

Oops, looks like I was run on the div tag. it's not rendering properly on github. Change it back to whatever works and I'll go ahead and merge it now!

Okay thanks!
On Sat, Oct 2, 2021 at 10:00 AM Othneil Drew @.***>
wrote:

Oops, looks like I was run on the div tag. it's not rendering properly on
github. Change it back to whatever works and I'll go ahead and merge it now!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/othneildrew/Best-README-Template/pull/46#issuecomment-932784288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR6WMU5X23ZNDPI7IWQW6V3UE43CNANCNFSM5EPQIKOQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I made a new pr, you can view it here: https://github.com/othneildrew/Best-README-Template/pull/48


module 'medspacy' has no attribute 'load'

I installed medspacy using the setup.py on windows. But I can't use the load() attribute. It throws an error

Could you share more about the error?  I am curious since all of our continuous integration is running and uses this function without issue (see https://github.com/medspacy/medspacy/actions).
A few questions:

Can you share the callstack of the error?
Can you share the code you are running which reproduces this?
Were there any errors or failures when running setup.py?
Which medspacy and Python versions are you using?

I am getting the error while using medspacy.load().
The error message I got  is AttributeError: module 'medspacy' has no attribute 'load'
I modified the get_version() function of the setup.py file. Instead of getting the version from _version.py file I returned the value of the version.

I am using python 3.8.13 and medspacy 1.0.0

@pssllp  Sorry I have not communicated with you about this in several months.  Since this comment above, a medspacy 1.0.1 was released to address Windows issues.
Could you try this again with medspacy >= 1.0.1 and let us know if you are still having issues?
I see that our continuous integration is running successfully for medspacy 1.0.1 and multiple versions of Python.

Hello @burgersmoke medspacy 1.0.1 is working fine... Thanks !!!

Great news @pssllp !  Thank you for the update.


g:fake_bootstrap not defined

Hi,
Found a small issue when adding to fake definition through fake#define API. On Vim startup I get this error message:
Error detected while processing vim-fake/autoload/fake.vim: line  298:
E121: Undefined variable: g:fake_bootstrap
E116: Invalid arguments for function empty(g:fake_bootstrap)
E15: Invalid expression: !empty(g:fake_bootstrap)
Press ENTER or type command to continue

This is easily fixed by defining g:fake_bootstrap to an empty string in my .vimrc:
let g:fake_bootstrap=''

But this should probably be intialized within the plugin itself?
Thanks for this plugin!

Fixed the bug. Thanks


Run tests by Ruby 2.2.4 and 2.3.0

Ruby 2.2.4 and 2.3.0 has been released :santa:

2.3 seems like a nice minor release, thanks!
Looking at Travis, I see we're not covering 2.1.x.  Each new Ruby version we add adds three builds to Travis, but maybe we don't need to test all versions of Neo4j against each version of Ruby...

Thank you for merging :snowman:
[IMO] It would be better to covering 2.1.x on Travis. It is true that increase run-time of Travis, but a sense of relief can be imparted to 2.1.x users.
Of course, I thought NOT necessary to non-supported Ruby versions (e.g. EOL Ruby versions) .

I'd be ok only testing against the oldest and newest versions that we
support. If it works against 2.0.x and 2.3.x, it should work against
everything in between. For now, I'd also like to continue testing against
2.2.x until 2.3.1 is released, too.
We had a lot of reports of terrible performance in 2.1.0 but were never
able to replicate it. I don't think we ever took the position of it being
officially unsupported but we do not encourage its use, especially when
upgrading from 2.1.x to 2.2.x comes without issues for most users.
On Sunday, December 27, 2015, Koichi ITO<EMAIL_ADDRESS>wrote:

Thank you for merging [image: :snowman:]
[IMO] It would be better to covering 2.1.x on Travis. It is true that
increase run-time of Travis, but a sense of relief can be imparted to 2.1.x
users.
Of course, I thought NOT necessary to non-supported Ruby versions (e.g.
EOL
https://www.ruby-lang.org/en/news/2014/07/01/eol-for-1-8-7-and-1-9-2/
Ruby versions) .
—
Reply to this email directly or view it on GitHub
https://github.com/neo4jrb/neo4j/pull/1089#issuecomment-167467322.

I got it. Thank you for the thorough explanation.


Add freestanding default()

The freestanding default() function, formerly available under #![feature(default_free_fn)], was removed in https://github.com/rust-lang/rust/pull/113469. I've seen it used in some projects' docs (namely bevy), and I think it's at the same time less unwieldy than StructWithReallyLongName::default(), less ugly than <_>::default(), and less stuttery than Default::default().

Thanks!

Published in 0.3.3


Fix/remove qm-qua 1.2.0 deprecations

Fixed deprecated imports:

from qm.QuantumMachinesManager import QuantumMachinesManager -->
from qm import QuantumMachinesManager
from qm.QuantumMachine import QuantumMachine --> from qm import QuantumMachine
from qm.QmJob import QmJob --> from qm import QmJob

@yonatanrqm could you please review/approve this today? Should take 30s

I suggest we look at all of the deprecation, even those not removed soon, and fix those as well

I looked into them and made a list. I'll make a PR for it at a late date.


Update new icon

Land-based fighter -> Interceptor Fighter
Land-based fighter (陸軍戦闘機) icon added.
Night Fighter icon added.
Interceptor Fighter:

Land-based Fighter:

Night Fighter:

thanks! 👍


[products] Show Identifiers in product pages

Currently, we don't expose identifiers beyond storing them in the front-matter. This will start exposing the identifiers on the website as a start.
Simple version to start with, based on https://github.com/package-url/packageurl-python/blob/main/src/packageurl/contrib/purl2url.py, with a few more types, and no support for "versions", since identifiers won't have that.

Sample Pages:

https://deploy-preview-5356--endoflife-date.netlify.app/contour
https://deploy-preview-5356--endoflife-date.netlify.app/envoy
https://deploy-preview-5356--endoflife-date.netlify.app/python

Working on generating links, converting to draft.

I'll drop the PURL fix commits and rebase this.
A PURL validator will be nice to have.

I'll drop the PURL fix commits and rebase this.

@captn3m0, don't mind I am doing it right now.

@marcwrobel you're removing the wrong PURLs (and adding the right ones) and not working on any repology/CPE identifiers, right? not that I do something that you already did, but isn't in the master at the moment 😆

@marcwrobel you're removing the wrong PURLs (and adding the right ones) and not working on any repology/CPE identifiers, right? not that I do something that you already did, but isn't in the master at the moment 😆

Yes, that's right. Credit goes to @captn3m0 though ;)

@captn3m0 I improved the PR:

Merging, will see tomorrow how many broken links this generates.


Dimensions output

I made some options and noticed that dimensions field type does not work with output (css_module as it is written in your documentation ). Is this field compatible to output some css and if so how to make it work ?
I attach the code i used for that so that you can tell me if there is smth wrong in code or it is just a bug. The output does not work with no 'transport=>auto' nor 'transport=>refresh'. Thx.
Kirki::add_field( 'theme_config', array(
	'type'        => 'dimensions',
	'settings'    => 'container_padding',
	'label'       => esc_html__( 'Paddings', $domain ),
	'description' => esc_html__( 'Controls the paddings.', $domain ),
	'section'     => 'section_02',
	'transport' => 'refresh',
	'default'     => array(
		'padding-top'    => '',
		'padding-bottom' => '',
		'padding-left'   => '',
		'padding-right'  => '',
	),
	'choices'     => array(
		'labels' => $padding_labels,
	),
	'output'      => array(
		array(
	      'choice'      => 'padding-top',
	      'element'     => '.container',
	      'property'    => 'padding-top',
	    ),
	    array(
	      'choice'      => 'padding-bottom',
	      'element'     => '.container',
	      'property'    => 'padding-bottom',
	    ),
	    array(
	      'choice'      => 'padding-left',
	      'element'     => ' .container',
	      'property'    => 'padding-left',
	    ),
	    array(
	      'choice'      => 'padding-right',
		  'element'     => '.container',
	      'property'    => 'padding-right',
	    ),
	),
) );

Are you using the stable version from w.org, or the develop branch from this repository?

@aristath Yes i am using the laster stable version from wordpress.org

Hello and thank you for reporting this issue.
We are closing most open GitHub issues with the release of Kirki 4 to start fresh with this major release.
If you are still running into issues after you have tested your theme with Kirki 4, please let us know so we can reopen the issue.
Please note that Kirki 3 is no longer actively supported. Moving forward, we will only provide support the very latest version of Kirki.
Thank you for your understanding.
Best,
David


Update Kale in NPM Lab Extension Repository

I would like to run the latest version of this extension (with the metrics tag now added in the UI), but this seems to not be updated on the NPM repo that stores this extension.
Thank you!

@TomLaMantia can I ask you to open this issue in the kale repo? I will answer you in details there. I am about to archive this repository as we have moved all the code there. Thanks!


Pre-Built Categories

There are a lot of moving pieces to this one. I want to present the user with a list of pre-built categories that they can load into their agent. For the moment I am choosing to do this on the create Category screen.
There is also a large API component to this since the API will need to have some methodology for storing these and loading them into an agent.
Pre-Built categories will contain:

Sayings (training data for the category)
Keywords (for example locations for weather?)
we'll need to handle when the keyword we're trying to create already exists
parameters
Webhooks
responses

Here's a rough rendition of how I see this looking in the UI:

I really like this idea, and maybe also prebuilt sayings & actions, keywords, slots to go along with those categories. Having an example of every entity in Articulate really makes it easier to understand how to use the platform IMO.

This is too understated. and doesn't provide a way for you to give info about it. I envisioned them as complete as cards.

Above img: I made the cards the same size at the inputs so that it doesn't stand out dominating too much

Above Img: I made the cards even smaller to not draw more attention and let the pre-built feel more like a suggestion instead of a main point of creating categories

So in the end there could be 10-20 of these so we should think about what that could look like. Just a large side scrolling list?
Also, should we/could we add an info icon that pops up a modal of what types of sayings/etc are included inside that category?

I was thinking of having it as a button to expand towards a pop-up module presenting all 20+ pre-built categories that can be scrolled.

Once clicked on the button it will pop-up the category lists and a sayings icon on the hovered list-item to the right. if clicked there will slide to image 4 below with the <-back arrow to go back to the category list.

If a user clicked on a prebuilt category, a little green notification status will be below the category name to confirm to the user the prebuilt is added.

One thing to note here if the user clicks on the sayings, the example above image, this module pop-up will not have the <- Back button. That button will only be present if the user clicks on the sayings icon in the category list (2nd image)

Thoughts?

I kind of want to show them off more than any of those screens accomplish.
Also here's the Dialogflow equivalent:

@wrathagom Is this something you would consider seeing?

I like it. @dcalvom @broham89 what about if instead of trying to integrate this into the current "Create a category" screen we added a routing step before it. Essentially the grid that is displayed above, but with the top left item being Create Custom Category

@wrathagom so to clarify, you want the grid to be the default when users get to this page and have a custom create btn as a secondary thing?


support broken-link-checker

would be great if this lib would detect https://github.com/stevenvachon/broken-link-checker as a crawler
the user agent is broken-link-checker/0.8.0 Node.js/14.16.0 (OS X; x64) see https://github.com/stevenvachon/broken-link-checker#useragent

We do! See here

Peferct thx. Couldnt find the ua in the repo :-)


Use image metadata version instead of the old env vars

Backport of #14650
Impact

[ ] New migrations
[ ] New/Updated API fields or mutations
[ ] Deprecated API fields or mutations
[ ] Removed API types, fields, or mutations

Docs

[ ] Link to documentation:

Pull Request Checklist

[ ] Privileged queries and mutations are either absent or guarded by proper permission checks
[ ] Database queries are optimized and the number of queries is constant
[ ] Database migrations are either absent or optimized for zero downtime
[ ] The changes are covered by test cases

As per d69bb446eff47a767903bdbe840b7db25532b3b0, we are no longer maintaining 3.11

Closing as not supported version.


JSON-formatted logs fail on portainer-ce 2.16.0

Bug description
Viewing JSON-formatted container logs in portainer-ce 2.16.0 shows this "Failure" popup:
JSON.parse: unexpected non-whitespace character after JSON data at line 2 column 1 of the JSON data

Same problem here, after upgrading to 2.16.0
When I go here:

I get screen with logs, but next requests (Auto refresh logs) fails:

One thing I did (except upgrading), I enabled logging via loki (it also logs via JSON formatting)
Here is my loki service (follow these instructions: https://grafana.com/docs/loki/latest/installation/docker/):
  loki:
    restart: unless-stopped
    depends_on:
      - alertmanager
    image: grafana/loki:latest
    command: [
      "-config.file=/etc/loki/local-config.yml",
      "-log.level=debug",
    ]
    volumes:
      - ${STACK_ROOT}/loki-config.yml:/etc/loki/local-config.yml
      - loki-data:/loki
    logging:
      driver: loki
      options:
        loki-url: "http://localhost:3100/loki/api/v1/push"
        loki-external-labels: "container_name={{.Name}}"
        loki-timeout: "10s"
        loki-batch-wait: "1s"
        loki-retries: 5
        keep-file: "true"
        no-file: "false"
        max-size: "200m"
        max-file: 2
    networks:
      monitoring-net:
      office-net:

can you please let us know what piece of software is the one that outputs these logs?

Chainlink node with environment variable JSON_CONSOLE=true

Downgrading to 2.15.1 works fine with same configuration.

Also experiencing this problem. Checking logs of containers that ran before I opened the logs works fine but as soon as new lines appear in the logs, it throws this error.
Docker version: 20.10.21, build baeda1f
Portainer version: 2.16.0

I can confirm this is a new issue with portainer 2.16.  The error message "JSON.parse ..." only happens with 2.16. But not all containers have this issue. For example Bookstack, AdguardHome, SWAG or Home Assistant are showing successfully their logs in portainer 2.16. I only have this problem with my "WhatsUpDocker" (https://github.com/fmartinou/whats-up-docker) or with the "Uptime-kuma" (https://github.com/louislam/uptime-kuma) container so far.

Hello there,
first thank you all for your reports that helped narrow the issue :raised_hands:
To give you some details, with 2.16 we introduced the ability for Logs Viewers to automatically format / prettify JSON logs (so you don't have to read raw JSON). The prettified version being what you can find in Portainer container's logs.
These logs can be in many formats:

already prettified logs (that we don't touch)
JSON logs (that we parse once then prettify)
and in some situations, serialized JSON logs (JSON logs but coming as a raw string
like "{\"some_key\":\"some value\"}\")

This 3rd scenario (serialized JSON logs) requires to parse the logs 2 times to be able prettify them

a first time to have it as raw JSON (tranform it to the same format as scenario 2)
then another time to generate JS objects that we can use to prettify the logs (like what we do for scenario 2)

The pattern used to detect if we were receiving logs as serialized JSON was broken and detected serialized JSON logs in regular logs when there was none...
:arrow_right: A fix candidate is available in image portainerci/portainer:pr7961.
This image is based on our latest release image portainer/portainer-ce:2.16.0. If some of you are able to give it a shot, with the diversity of images you all have, it will ensure everything is working fine for everyone :raised_hands:

Thanks a lot for your quick feedback. I wanted to give portainerci/portainer:pr7961 a try, but I guess it is not builded for an arm64 arch, because portainer says "Unable to retrieve server settings and status" and docker logs portainer-server shows an exec format error. As mentioned, I normally use the CE edition on a raspberry pi4.

@FastHogi according to dockerhub it is available for arm64
As a fallback you may be able to use portainerci/portainer:pr7961-linux-arm64 directly even if docker should pick the same image with portainerci/portainer:pr7961

Sorry, can't get the container to run. I only replaced the image in my docker compose file (see below). As you assumed it makes no difference. The image is pulled correctly. Here is my terminal output, if that might help:
14:03:08 root@PI-LIVE:/data/portainer# docker-compose up -d
Pulling portainer-server (portainerci/portainer:pr7961-linux-arm64)...
pr7961-linux-arm64: Pulling from portainerci/portainer
772227786281: Already exists
96fd13befc87: Already exists
6974406ea9d5: Pull complete
0372f6ae7a52: Pull complete
Digest: sha256:7bc08efe7bbb719456430cd71ffc5d3664dcaf1c0606a7cb3caa664bf149c7fb
Status: Downloaded newer image for portainerci/portainer:pr7961-linux-arm64
portainer-agent is up-to-date
portainer-server is up-to-date
14:05:47 root@PI-LIVE:/data/portainer# docker logs portainer-server
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
exec /portainer: exec format error
14:06:09 root@PI-LIVE:/data/portainer# cat docker-compose.yml
version: '3'

services:
  portainer-server:
    container_name: portainer-server
    restart: always
#    image: portainer/portainer-ce:latest
    image: portainerci/portainer:pr7961-linux-arm64
    networks:
      - CustomNet_Docker
    ports:
      - 9000:9000
      - 9443:9443
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - /data/portainer:/data

Thanks for your feedback.

And we will investigating the issue with the ARM64 image.

Also, from what I can read over the internet, it seems Raspberry Pi4 needs arm/v7 images and not arm64
The arm:v7 image is available at portainerci/portainer:pr7961-linux-arm

Fixed by introducing a fallback to "raw display" if an error is encountered during parsing.
The fix will be available in the next release.


issue running the example with external postgres

Hello,

I was trying the docker-compose-example.yaml --> it worked

then I changed hasura-auth's HASURA_GRAPHQL_DATABASE_URL to postgres://postgres@host.docker.internal:5432/test --> still worked

changed graphql-engine's to the same and I'm having this issue (I've run the initdb script):

,"data":{"path":"$.args","error":"source with name \"default\" does not exist","code":"not-exists"}},"isAxiosError":true,"stack":"Error: Request failed with status code 400\n    at createError (/app/node_modules/.pnpm/axios@0.21.1/node_modules/axios/lib/core/createError.js:16:15)\n    at settle (/app/node_modules/.pnpm/axios@0.21.1/node_modules/axios/lib/core/settle.js:17:12)\n    at IncomingMessage.handleStreamEnd (/app/node_modules/.pnpm/axios@0.21.1/node_modules/axios/lib/adapters/http.js:260:11)\n    at IncomingMessage.emit (events.js:412:35)\n    at endReadableNT (internal/streams/readable.js:1334:12)\n    at processTicksAndRejections (internal/process/task_queues.js:82:21)","type":"Error","msg":"Request failed with status code 400"}
schootive-hasura-auth-hasura-auth-1     | (node:19) UnhandledPromiseRejectionWarning: Error: Error tracking table provider_requests
schootive-hasura-auth-hasura-auth-1     |     at trackTable (/app/dist/metadata.js:29:19)
schootive-hasura-auth-hasura-auth-1     |     at processTicksAndRejections (internal/process/task_queues.js:95:5)
schootive-hasura-auth-hasura-auth-1     |     at async applyMetadata (/app/dist/metadata.js:127:5)
schootive-hasura-auth-hasura-auth-1     |     at async start (/app/dist/server.js:39:5)
schootive-hasura-auth-hasura-auth-1     | (Use `node --trace-warnings ...` to show where the warning was created)
schootive-hasura-auth-hasura-auth-1     | (node:19) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
schootive-hasura-auth-hasura-auth-1     | (node:19) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
schootive-hasura-auth-hasura-auth-1 exited with code 0

what could be the problem?

seems like only changing graphql-engine's HASURA_GRAPHQL_DATABASE_URL to postgres://postgres@host.docker.internal:5432/test already caused the error regardless of hasura-auth's config

I think the postgres database has to be called "default" in Hasura for it to work

that seems to be it. Additionally, I had to remove/rename an existing table called user to something else.


feat: upgrade to new flutter app and improve code generation.

This updates the generator to Flutter 3.0 and improves the generated code with new dart features (final class).
Furthermore, the responsiveValue function is updated to use the new API for getting the screen width (not the deprecated one). And also supports passing a context now.

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

v3.0.0
GitHub release

Your semantic-release bot :package::rocket:


Delete and recreate index if it already exists

Pull Request
What does this PR do?
Closes #10
PR checklist
Please check if your PR fulfills the following requirements:

[x] Does this PR fix an existing issue?
[x] Have you read the contributing guidelines?
[x] Have you made sure that the title is accurate and descriptive of the changes?

What's inside this PR ?

Check for an existing index with the same name. If it already exists, then delete and recreate it
Addition of a new test

How to test ?

yarn test
You can also make your own tests with the playground: yarn playground:dev and edit the query in playground/gatsby-config.js

bors merge


Remove go-shutil

Fixes #132

Current coverage is 76.21% (diff: 34.88%)

Merging #133 into master will decrease coverage by 0.75%

@@             master       #133   diff @@
==========================================
  Files            23         24     +1
  Lines          3469       3540    +71
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2670       2698    +28
- Misses          608        635    +27
- Partials        191        207    +16

Powered by Codecov. Last update f23dc66...92b0003

Current coverage is 76.21% (diff: 34.88%)

Merging #133 into master will decrease coverage by 0.75%

@@             master       #133   diff @@
==========================================
  Files            23         24     +1
  Lines          3469       3540    +71
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2670       2698    +28
- Misses          608        635    +27
- Partials        191        207    +16

Powered by Codecov. Last update f23dc66...92b0003


Is the table structure for 1:1 relations backwards?

Will try to make this as concise as possible:

Given the example above, the relation to UserInformation is defined in my User class.  My UserInformation rows are not really useful unless they specify a UserId, but I'll always be navigating from the other direction.  That is to say: User can be complete without a UserInformation, but a UserInformation is always incomplete when it doesn't have a User.
Additionally, if I set the relation up on both sides, EF gets tripped up.  And really, I don't need to specify the User relation going back the other way as I'm always coming from the other direction.
I'm wondering if EF landed on the wrong default policy for the columns being created here.  There might be a perfectly valid reason for it (let me know!), but my User object doesn't need to store a foreign key for 1:1 relations that it has, tables that relate to my User almost always seem like a better spot to put the foreign key.
So, I get that I can customize this, but I'd hate to have to do this once for every 1:1 in my system.  Is there maybe even just a flag I can flip to tell EF to put the foreign key on the related side, not the relating side?

@atrauzzi Can you show the entity types and model builder configuration that generates this?

Sure thing.  I've pulled out unrelated fields just to keep the noise down.
namespace Domain
{
    public class User
    {
        public Guid Id { get; set; }

        public UserInformation Information { get; set; }
    }
}

using System;

namespace Domain
{
    public class UserInformation
    {
        public Guid Id { get; set; }
    }
}

I haven't done any model builder configuration because I figured the defaults would do the right thing.  Which is more or less the basis.  I feel like when setting up a 1:1 relation, the defaults are putting the FK on the wrong side.

@atrauzzi For that model it is ambiguous as to whether the relationship should be 1:1 or 1:* because there is no navigation property from UserInformation back to User. What to map for this by default is something that we discussed a lot and tried several things, but ultimately decided on 1:* by default because it is often what is intended and even when not intended will often work correctly for 1:1 relationships as well.

To be honest, I completely agree with what you just said, but still don't see how that explains why the key is on the table that doesn't depend on it.
It's got to be beyond rare where you'd need/benefit from having the FK on the side the navigation property is defined.
User.Information would be an instance of Information.  User is complete on its own.  Information instances will always be incomplete if they do not relate to a user.

@atrauzzi Consider this model, which is a type of model that we see quite frequently:
public class Order
{
    public Guid Id { get; set; }

    public User AuditedBy { get; set; }
}

public class User
{
    public Guid Id { get; set; }
}

The semantics of this model are that every order is audited by some user. A single user can audit many orders, so this is a 1:* relationship, and the FK must therefore go on Order. You could argue that in this case User should have a collection navigation property for Orders, but from what we see the domain model often does not have this.
This is not to say that your model isn't equally valid, and as I said, we did discuss this at length, but in considering all the feedback and models we have seen the pragmatic decision was that the 1:* interpretation more often works for people.

EF Team Triage: we discussed this and agreed not to make any changes. If the expected relationship configuration is different from what our conventions decide then the right solution is to configure the relationship explicitly.

That's unfortunate.  I still say the majority of scenarios will prefer it the other way.  So this is going to result in more configuration code for the majority of scenarios.

@atrauzzi Just some context on our thought process. I am not expecting you to agree but it might help you understand why this decision.
When I look at the example you provided (User/UserInformation) it seems obvious that the model should be setup the way you expect. When I look at the example @ajcvickers provided (Order/User) it seems obvious that it should be the other way around. It is because my brain is doing something that the EF Core conventions currently cannot do: understand the semantics of the model!
When we looked at this originally we even consider other alternatives, e.g.:

Throw, because the model is ambiguous
Use some kind of heuristic to simulate intelligence, e.g. "is the singularized version of the name of one of the entities included in the name of the other entity"?

But in the end we decided to adopt a convention that is applied consistently. Conventions are not mean to make perfect judgements. They are just meant to implement behaviors that we pick to be the defaults but that we know sometimes will be wrong. That is why we allow conventions to be overridden. At some point in the future EF Core will allow you to even replace conventions with your own as EF6 did.
Also a simple convention that is easy to learn is often better than a complex one. Once you learn what the convention will do by default, you can anticipate in what cases you will have to override it without testing it.

I think I understand even more than what you've said and yes, most of the explanation jives - except that you say "what makes most sense", and yet when you look at your peers in the ORM space, they landed on the other side.
Why?  The tldr; is: Have another internal discussion and ask "Why?" - and be sure to get the honest answer for yourselves.
So:

Yes, my example makes sense, as does the example from @ajcvickers.
At no point would I think you need to do any kind of fancy detection or error.
Storing the foreign key on the other side is consistent too

To be honest, every point you raised balances equally in favour of either approach, yet the approach chosen still goes against what I'm arguing is the majority use case.
But:

Storing the foreign key on the owned side of the relation rather than the owning is inherently decoupled rather than guaranteeing bi-directional coupling
Storing the foreign key on the owned side shrinks the size of owning data sets retrieved when not joined in by reducing the number of redundant columns (acknowledging that projections are just messy and a bother to maintain)
Storing the foreign key on the owned side reinforces a compositional approach
As I argued before, from an OO perspective it's more cohesive

So, I've provided a list of concrete reasons.  Nothing abstract or driven by preference.  And it all points pretty clearly to the wrong convention having been selected here.
I'll take a moment and offer full apologies - I'm not trying to be mean - but I'm calling into question the rationale because based only on what is here and what is common practice, there's some unaccounted for influence.  Whether that's fear of change, legacy limitations, timeline constraints, or the dreaded and invariably false it's too late to change now attitude.
Finally, the reason why I compare to other ORMs from other ecosystems is to avoid any echo chambers. I 'd guess there will be many people acclimated to always having to write extra code for the norm rather than the exceptional case in EF.  But that kind of isolation and preference can be deadly for software communities.

or the dreaded and invariably false it's too late to change now attitude.

I'm not sure whether or not I agree with you, but on a side note if EF Core has shipped with this behavior, then it literally is too late to change unless they want to break their users and rev to v2.

@atrauzzi Are you saying you think this should be interpreted as 1:1 by default? If that is the case, then everything else you say follows on from that. However, it is also valid to interpret it as 1:*, which is what EF does. At that point there is no longer any choice where to co-locate the FK--it has to be on the dependent, and that has to be the entity without the navigation property.

@ajcvickers - That doesn't change or address any of my points about the default behaviour.
I know how it works.  I'm saying the way it currently works is the less frequent and less desirable default.

@atrauzzi I'm trying to understand if it is your opinion that this should be by-convention mapped as a 1:1 instead of a 1:*.