Unable to install Xcode

Describe the bug
I am unable to install Xcode using Xcodes.
To Reproduce
Launch app, log in, choose an Xcode version to install.
Expected behavior
The version should install.
Screenshots
I see an error message.

Version

OS: macOS 12.3 beta
Xcodes: 13.0 (10)

login first

I am logged in.

Hi @jordanekay
I installed 12.3 tonight and don't get any issues on my machine. Which xcode version are you trying to install? Do you happen to have a different language or region set, or a different language somewhere set on Apple?
It's trying to parse a json that's from developer.apple.com and it's returning a different format for some reason. If you have a proxy to watch the url's it would be awesome to see what the difference is on the listDownloads.action url

I’m trying to install the 13.3 release candidate. I have no different language or region set.
Looking at the JSON in the response body via Proxyman, there are 2,240 dateModified fields and they all seem to have the correct date format.
downloads.zip

Yes, all versions have the same issue. No version can be installed through Xcodes.app.

I've got the same issue. I can help with debugging the error if needed.

I was also unable to install the latest version of Xcode via Xcodes with my system settings, with exactly the same error as above - I was attempting to install Xcode 12.3 on a machine that hadn't yet had that version installed.  As an aside, as a Brit, I had my locale set to en-GB - however, unusually I set my time format set to 12h.  The screenshot below shows my "Language & Region" settings:

Changing my region to "United States" fixed the issue at hand as a workaround & with that set, I was able to install Xcode 12.3 via this app.
The debug logs don't seem to reveal that much (other than the fact I changed bundle IDs), but I'll paste them here for completeness:
error: module importing failed: invalid pathname
2022-04-09 12:30:28.149257+0100 Xcodes[52855:172315] [helperClient] checkIfLatestHelperIsInstalled()
2022-04-09 12:30:28.149822+0100 Xcodes[52855:172315] [helperClient] getVersion()
2022-04-09 12:30:28.164295+0100 Xcodes[52855:172786] [helperClient] getVersion(): Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named com.robotsandpencils.XcodesApp.Helper" UserInfo={NSDebugDescription=connection to service named com.robotsandpencils.XcodesApp.Helper}
2022-04-09 12:30:28.164411+0100 Xcodes[52855:172786] [helperClient] checkIfLatestHelperIsInstalled(): false
ForEach<Array<Xcode>, Version, XcodeListViewRow>: the ID 3.2.3+10M2262 occurs multiple times within the collection, this will give undefined results!
2022-04-09 12:30:28.942075+0100 Xcodes[52855:172791] [subprocess] Process.run executable: file:///usr/bin/xcode-select, input: , arguments: -p
2022-04-09 12:30:28.947367+0100 Xcodes[52855:172791] [subprocess] Process.run output: /Applications/Xcode-13.2.1.app/Contents/Developer
2022-04-09 12:30:31.106167+0100 Xcodes[52855:172792] [logging] volume does not support data protection, stripping SQLITE_OPEN_FILEPROTECTION_* flags
2022-04-09 12:30:31.106434+0100 Xcodes[52855:172792] [logging] volume does not support data protection, stripping SQLITE_OPEN_FILEPROTECTION_* flags
2022-04-09 12:30:34.588862+0100 Xcodes[52855:172315] Metal API Validation Enabled

If there's anything else I could do to help, I'll be sure to uninstall & reinstall Xcode 12.3 and be more than happy to help nail this issue.


Remove make build-all, fix make run

When running make build-all on macOS, the following is seen:
% make build-all

Building /Users/michaeldockter/senzing.git/senzing-tools/target/darwin-amd64/senzing-tools
Building /Users/michaeldockter/senzing.git/senzing-tools/target/linux-amd64/senzing-tools
# github.com/senzing/serve-grpc/g2configmgrserver
../../go/pkg/mod/github.com/senzing/serve-grpc@v0.4.13/g2configmgrserver/g2configmgrserver.go:65:33: undefined: g2sdk.G2configmgr
# github.com/senzing/serve-grpc/g2configserver
../../go/pkg/mod/github.com/senzing/serve-grpc@v0.4.13/g2configserver/g2configserver.go:65:30: undefined: g2sdk.G2config
# github.com/senzing/serve-grpc/g2productserver
../../go/pkg/mod/github.com/senzing/serve-grpc@v0.4.13/g2productserver/g2productserver.go:65:31: undefined: g2sdk.G2product
# github.com/senzing/serve-grpc/g2diagnosticserver
../../go/pkg/mod/github.com/senzing/serve-grpc@v0.4.13/g2diagnosticserver/g2diagnosticserver.go:66:34: undefined: g2sdk.G2diagnostic
# github.com/senzing/serve-grpc/g2engineserver
../../go/pkg/mod/github.com/senzing/serve-grpc@v0.4.13/g2engineserver/g2engineserver.go:65:30: undefined: g2sdk.G2engine
# github.com/senzing/go-sdk-abstract-factory/factory
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:109:46: undefined: g2configbase.G2config
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:144:52: undefined: g2configmgrbase.G2configmgr
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:179:54: undefined: g2diagnosticbase.G2diagnostic
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:214:46: undefined: g2enginebase.G2engine
../../go/pkg/mod/github.com/senzing/go-sdk-abstract-factory@v0.3.2/factory/factory.go:249:48: undefined: g2productbase.G2product
make: *** [linux/amd64] Error 1

Given that dependencies can't be built (due to the dependence on the Senzing binaries), senzing-tools can be built cross-platform.
When running make run, the following is seen:
% make run

dyld[16516]: Library not loaded<EMAIL_ADDRESS>  Referenced from: '/private/var/folders/rd/zwh2c8ns7sl8k2b07rv56d100000gn/T/go-build2680064064/b001/exe/main'
  Reason: tried: '/usr/local/lib/libG2.so' (no such file), '/usr/lib/libG2.so' (no such file)
signal: abort trap
make: *** [run] Error 1

Pull requests:

https://github.com/Senzing/senzing-tools/pull/116


chore(master): release 1.9.8

:robot: I have created a release beep boop
1.9.8 (2023-08-27)
Bug Fixes

去除默认history模式 (84e4733)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/KYX1234/Element-Admin/releases/tag/v1.9.8 :sunflower:


Don't need CALICO_IPV6POOL_CIDR for kubeadm clusters

Description
... since we have autodetection for kubeadm! 😄
Should backport this to v3.13 too

Related issues/PRs

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Deploy preview for calico ready!
Built with commit 30f1498d21990775263b0c05e16918a760354c1b
https://deploy-preview-3431--calico.netlify.com

Deploy preview for calico ready!
Built with commit 53ad2fcb178907ac75a5de2ea2c1ad5d0952b6cd
https://deploy-preview-3431--calico.netlify.com


Upgrading to python 3.11

This upgrade requires:

Upgrading torch to 2.x
Upgrading springs to be compatible with changes to dataclasses in python 3.11
Loosening some of the fixed imports in decontext

Addresses #10


Dynamically exclude namespaces

Description
Removed default excluded namespaces and replaced them with logic that only excludes namespace used by the serverless
Related issue(s)
https://github.com/kyma-project/serverless/issues/241

/test all


It required some modifications to work with blazor server ... some instructions with build. in the start should be removed ... some instructions should be in the starup.cs not in program.cs

[Enter feedback here]

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

ID: 85af7a99-672c-0438-dcc2-e8edfaf70c54
Version Independent ID: 85af7a99-672c-0438-dcc2-e8edfaf70c54
Content: Use ASP.NET Core SignalR with Blazor
Content Source: aspnetcore/blazor/tutorials/signalr-blazor.md
Product: aspnet-core
Technology: aspnetcore-tutorials
GitHub Login: @guardrex
Microsoft Alias: riande

Hello @aldefrawy ...

should be in the starup.cs

I think you're looking at the wrong version of the topic. Use the doc version selector to load an earlier version of the topic. Startup.cs was a 5.0 or earlier default project file; so if you're working in 5.0, set the doc version selector to 5.0. You'll get this topic version ...
https://learn.microsoft.com/en-us/aspnet/core/blazor/tutorials/signalr-blazor?view=aspnetcore-5.0&tabs=visual-studio&pivots=server
... which will have the correct files indicated.

I'm working on version 7.0
On Tue, Dec 20, 2022, 10:16 PM Luke Latham @.***> wrote:

Closed #27939 https://github.com/dotnet/AspNetCore.Docs/issues/27939 as
completed.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/AspNetCore.Docs/issues/27939#event-8081173275,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR6JFVRN4P7AOXUKURLODF3WOIAXLANCNFSM6AAAAAATE2TUEI
.
You are receiving this because you were mentioned.Message ID:
@.***>

I think you are right my project was on old version
Thanks for your explanations
On Tue, Dec 20, 2022, 11:41 PM Mohammad Aldefrawy @.***>
wrote:

I'm working on version 7.0
On Tue, Dec 20, 2022, 10:16 PM Luke Latham @.***>
wrote:

Closed #27939 https://github.com/dotnet/AspNetCore.Docs/issues/27939
as completed.
—
Reply to this email directly, view it on GitHub
https://github.com/dotnet/AspNetCore.Docs/issues/27939#event-8081173275,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AR6JFVRN4P7AOXUKURLODF3WOIAXLANCNFSM6AAAAAATE2TUEI
.
You are receiving this because you were mentioned.Message ID:
@.***>


[v1.14] Backports 2024-03-05

Manual backport of

[ ] #29530
[ ] #29721
[ ] #29761
[ ] #29594
[ ] #29962
[ ] #30095

Once this PR is merged, a GitHub action will update the labels of these PRs:
 29530 29721 29761 29594 29962 30095

/test-backport-1.14


Images in bookmap title cause NPE and break PDF rendering wit DITA OT 3.0.1

Expected Behavior
An image in bookmap title should be displayed on the first page of the rendered PDF.
Actual Behavior
A NPE is thrown. With DITA-OT 2.5.4, no error occurs and a correct PDF is created.
Possible Solution
Unknown - seems to be a bug that must be fixed.
Steps to Reproduce
manual_test.zip

path\to\dita-ot-3.0.1\bin\dita -f pdf2 -i test.ditamap -v

Copy of the error message, log file or stack trace
topic-reader: [topic-reader] Using Xerces grammar pool for DTD and schema caching. [topic-reader] Reading file:/C:/Users/Demo/AppData/Local/Temp/temp20180130004418366/aadcc03c12e05a7a01b6aba3ecb0be7c3526f358.ditamap Error: java.lang.NullPointerException
Environment

DITA-OT version: 3.0.1
Operating system and version: Windows 10
How did you run DITA-OT? dita command
Transformation type: PDF

I just downloaded OT 3.0.2 and with that, it no longer crashes with a NPE. I don't see the coverimage yet, but for that I will try the hints you gave me in your previous comment (using the data element). If I run into new problems, I'll comment on this.

It is somewhat easier to use the <data> element approach to create cover images. If you use a <topic>, it is processed as a topic and is flavored with additional <xsl:attribute-set/> rules. This makes it much harder for you, because you have additional interferring processing.
ℹ You should buy and read DITA for Print V2
Example Bookmap
<?xml version="1.0" encoding="UTF-8"?>
<?xml-model href="urn:oasis:names:tc:dita:rng:bookmap.rng" schematypens="http://relaxng.org/ns/structure/1.0"?>
<bookmap>
    <booktitle>
        <mainbooktitle>Title</mainbooktitle>
    </booktitle>
    <bookmeta>
        <data name="cover-image">
            <image href="my.png"/>
        </data>
    </bookmeta>
</bookmap>

If you have generated a plugin using the dita-generator, you can find the cover-processing in this file:
my.custom.plugin\xsl\fo\front-matter.xsl
<?xml version='1.0' encoding='utf-8'?>
<xsl:stylesheet exclude-result-prefixes="ditaarch opentopic e dita-ot opentopic-func" version="2.0" xmlns:dita-ot="http://dita-ot.sourceforge.net/ns/201007/dita-ot" xmlns:ditaarch="http://dita.oasis-open.org/architecture/2005/" xmlns:e="my.custom.plugin" xmlns:fo="http://www.w3.org/1999/XSL/Format" xmlns:opentopic="http://www.idiominc.com/opentopic" xmlns:opentopic-func="http://www.idiominc.com/opentopic/exsl/function" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
  <!--cover-->
  <xsl:template name="createFrontCoverContents">
    <fo:block xsl:use-attribute-sets="__frontmatter__title">
      <xsl:choose>
        <xsl:when test="$map/*[contains(@class,' topic/title ')][1]">
          <xsl:apply-templates select="$map/*[contains(@class,' topic/title ')][1]" />
        </xsl:when>
        <xsl:when test="$map//*[contains(@class,' bookmap/mainbooktitle ')][1]">
          <xsl:apply-templates select="$map//*[contains(@class,' bookmap/mainbooktitle ')][1]" />
        </xsl:when>
        <xsl:when test="//*[contains(@class, ' map/map ')]/@title">
          <xsl:value-of select="//*[contains(@class, ' map/map ')]/@title" />
        </xsl:when>
        <xsl:otherwise>
          <xsl:value-of select="/descendant::*[contains(@class, ' topic/topic ')][1]/*[contains(@class, ' topic/title ')]" />
        </xsl:otherwise>
      </xsl:choose>
    </fo:block>
    <xsl:apply-templates select="$map//*[contains(@class,' bookmap/booktitlealt ')]" />
    <fo:block xsl:use-attribute-sets="__frontmatter__owner">
      <xsl:apply-templates select="$map//*[contains(@class,' bookmap/bookmeta ')]" />
    </fo:block>
    <fo:block xsl:use-attribute-sets="image__block">
      <xsl:call-template name="e:cover-image" />
    </fo:block>
  </xsl:template>
  <xsl:template name="e:cover-image">
    <xsl:for-each select="($map//*[contains(@class, ' topic/data ')][@name = 'cover-image']/*[contains(@class, ' topic/image ')])[1]">
      <xsl:apply-templates mode="placeImage" select=".">
        <xsl:with-param name="imageAlign" select="@align" />
        <xsl:with-param name="href" select="if (@scope = 'external' or opentopic-func:isAbsolute(@href)) then @href else concat($input.dir.url, @href)" />
        <xsl:with-param name="height" select="@height" />
        <xsl:with-param name="width" select="@width" />
      </xsl:apply-templates>
    </xsl:for-each>
  </xsl:template>
</xsl:stylesheet>

If you're unhappy with the appearance, this is the code snippet you need to touch/use as a starting point for your modifications.

I bought DITA for Print V2 and read the interesting sections in Google books (I will receive the printed book today). Thanks for the hint, very good book!
Maybe I'm doing something fundamentally wrong, but I still can't include the cover image, even though I get no more NPE.
My map starts like this:
``

      Handbuch EXAMPLE
Version vom xxx

``
When I render, I get before the first page:
``
      [fop] SEVERE: Image not found. URI: file:/home/install/manual_test/dd0180d0133ce33df916b90d20969c641562272c.jpg. (See position 19:26264)
``
Setting the explicit path to the image does not help. The file is there, but of course the name is the one in the href, and not the hex number.jpg.
Commenting out the entire bookmeta element from the map removes the error message, so apparently the problem is caused by the data element or its processing.
front-matter.xsl looks like this (created by online plugin generator):
``

<xsl:stylesheet exclude-result-prefixes="ditaarch opentopic e dita-ot opentopic-func" version="2.0" xmlns:dita-ot="http://dita-ot.sourceforge.net/ns/201007/dita-ot" xmlns:ditaarch="http://di$

<xsl:template name="createFrontCoverContents">
<fo:block xsl:use-attribute-sets="__frontmatter__title">
xsl:choose
<xsl:when test="$map/[contains(@class,' topic/title ')][1]">
<xsl:apply-templates select="$map/[contains(@class,' topic/title ')][1]" />
</xsl:when>
<xsl:when test="$map//[contains(@class,' bookmap/mainbooktitle ')][1]">
<xsl:apply-templates select="$map//[contains(@class,' bookmap/mainbooktitle ')][1]" />
</xsl:when>
<xsl:when test="//[contains(@class, ' map/map ')]/@title">
<xsl:value-of select="//[contains(@class, ' map/map ')]/@title" />
</xsl:when>
xsl:otherwise
<xsl:value-of select="/descendant::[contains(@class, ' topic/topic ')][1]/[contains(@class, ' topic/title ')]" />
</xsl:otherwise>
</xsl:choose>
</fo:block>
<xsl:apply-templates select="$map//[contains(@class,' bookmap/booktitlealt ')]" />
<fo:block xsl:use-attribute-sets="__frontmatter__owner">
<xsl:apply-templates select="$map//[contains(@class,' bookmap/bookmeta ')]" />
</fo:block>
<fo:block xsl:use-attribute-sets="image__block">
<xsl:call-template name="e:cover-image" />
</fo:block>
</xsl:template>
<xsl:template name="e:cover-image">
<xsl:for-each select="($map//[contains(@class, ' topic/data ')][@name = 'cover-image']/[contains(@class, ' topic/image ')])[1]">
<xsl:apply-templates mode="placeImage" select=".">
<xsl:with-param name="imageAlign" select="@align" />
<xsl:with-param name="href" select="if (@scope = 'external' or opentopic-func:isAbsolute(@href)) then @href else concat($input.dir.url, @href)" />
<xsl:with-param name="height" select="@height" />
<xsl:with-param name="width" select="@width" />
</xsl:apply-templates>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
``
Has anybody ever succeeded in rendering a cover image into the PDF using this method, and if so, may I ask for a short sample map where this actually works? I have no idea what to do to get this working.

I bought DITA for Print V2 and read the interesting sections in Google books (I will receive the printed book today). Thanks for the hint, very good book!
Maybe I'm doing something fundamentally wrong, but I still can't include the cover image, even though I get no more NPE.
My map starts like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE bookmap PUBLIC "-//OASIS//DTD DITA BookMap//EN" "bookmap.dtd">
<bookmap id="bookmap" xml:lang="de-DE">
  <booktitle>
    <mainbooktitle>
      Handbuch EXAMPLE</mainbooktitle>
    <booktitlealt>Version vom xxx</booktitlealt>
  </booktitle>
  <bookmeta>
      <data name="cover-image">
          <image align="center" href="EXAMPLE_Titel.jpg"/>
      </data>
    </bookmeta>
  <frontmatter>
    <booklists>
      <toc />
    </booklists>
    <topicref href="foo.dita" />
  </frontmatter>

When I render, I get before the first page:
[fop] SEVERE: Image not found. URI: file:/home/install/manual_test/dd0180d0133ce33df916b90d20969c641562272c.jpg. (See position 19:26264)

Setting the explicit path to the image does not help. The file is there, but of course the name is the one in the href, and not the hex number.jpg.
Commenting out the entire bookmeta element from the map removes the error message, so apparently the problem is caused by the data element or its processing.
front-matter.xsl looks like this (created by online plugin generator):
<?xml version='1.0' encoding='utf-8'?>
<xsl:stylesheet exclude-result-prefixes="ditaarch opentopic e dita-ot opentopic-func" version="2.0" xmlns:dita-ot="http://dita-ot.sourceforge.net/ns/201007/dita-ot" xmlns:ditaarch="http://di$
  <!--cover-->
  <xsl:template name="createFrontCoverContents">
    <fo:block xsl:use-attribute-sets="__frontmatter__title">
      <xsl:choose>
        <xsl:when test="$map/*[contains(@class,' topic/title ')][1]">
          <xsl:apply-templates select="$map/*[contains(@class,' topic/title ')][1]" />
        </xsl:when>
        <xsl:when test="$map//*[contains(@class,' bookmap/mainbooktitle ')][1]">
          <xsl:apply-templates select="$map//*[contains(@class,' bookmap/mainbooktitle ')][1]" />
        </xsl:when>
        <xsl:when test="//*[contains(@class, ' map/map ')]/@title">
          <xsl:value-of select="//*[contains(@class, ' map/map ')]/@title" />
        </xsl:when>
        <xsl:otherwise>
          <xsl:value-of select="/descendant::*[contains(@class, ' topic/topic ')][1]/*[contains(@class, ' topic/title ')]" />
        </xsl:otherwise>
      </xsl:choose>
    </fo:block>
    <xsl:apply-templates select="$map//*[contains(@class,' bookmap/booktitlealt ')]" />
    <fo:block xsl:use-attribute-sets="__frontmatter__owner">
      <xsl:apply-templates select="$map//*[contains(@class,' bookmap/bookmeta ')]" />
    </fo:block>
    <fo:block xsl:use-attribute-sets="image__block">
      <xsl:call-template name="e:cover-image" />
    </fo:block>
  </xsl:template>
  <xsl:template name="e:cover-image">
    <xsl:for-each select="($map//*[contains(@class, ' topic/data ')][@name = 'cover-image']/*[contains(@class, ' topic/image ')])[1]">
      <xsl:apply-templates mode="placeImage" select=".">
        <xsl:with-param name="imageAlign" select="@align" />
        <xsl:with-param name="href" select="if (@scope = 'external' or opentopic-func:isAbsolute(@href)) then @href else concat($input.dir.url, @href)" />
        <xsl:with-param name="height" select="@height" />
        <xsl:with-param name="width" select="@width" />
      </xsl:apply-templates>
    </xsl:for-each>
  </xsl:template>
</xsl:stylesheet>

Has anybody ever succeeded in rendering a cover image into the PDF using this method, and if so, may I ask for a short sample map where this actually works? I have no idea what to do to get this working.

I did some further analysis on this issue. The image I reference in the bookmeta and that's reported as missing by fop is not contained in the file image.list in the temp folder, contrary to the other objects referenced in the body content.
Could it be that there is still an issue in the preprocessing where such references are (or should be) extracted, or am I missing some configuration? I am really stuck here, and if I can't solve this within the next couple of days, I must go back to DITA-OT 2.5.x where this (hopefully) works.
Am I really the only person using cover images in DITA-OT 3.x?

... the image file reference is already missing from .job.xml. Seems to be an issue in or before the gen-list step, it apparently fails to collect the file inside of the data element.

Since I didn't get it to work with the data element approach, I linked in a topic in the frontmatter before the booklists as suggested as "plan b" above. Whenever I start referencing the image in that topic in front-matter.xsl though, I get the same problem again, a SEVERE error message in the fop block telling me it can't find the image.
I go back to DITA OT 2.5.4 now. Either 3.x still has a bug in that area (probably in or before gen-lists) or I am doing something fundamentally wrong that I can't resolve myself. I invested almost 3 days to no avail. With 2.5.4, I get the cover image without any modifications to the map (image directly placed inside mainbooktitle element). This might not be the most elegant approach, and it's based on an outdated DITA-OT version, but at least it yields the result the customer expects. Sorry :-(

Stuck with the same problem on the DITA OT 3.0.4 version. I fixed this problem in the AbstractReaderModule class by adding nonTopicrefReferenceSet to resourceOnlySet but I think it's not a good solution.

Tried to insert images via data elements.
OT 3.0.1 throws NPE, if href is used to reffer image.
Processing successfull with conkeyref instead of href.
In OT 3.1 both reference types processed without NPE.
But image publising does not work. A temporary numeric filename without path is pushed into the topic.fo.

Using DITA-OT 3.3.3 I also tried using <data>. I am getting the same errors reported by @boris-horner. Looking at the code from front-matter.xsl it seems that setting @external on <image> or using an explicit path would help, but neither do.
<bookmeta>
  <data name="cover-image">
    <image href="my.svg"/>
  </data>
</bookmeta>


Bump dependencies

Bump apache-arrow from 12.0.1 to 14.0.2
Bump nodemon from 2.0.22 to 3.0.2
Bump @grpc/grpc-js from 1.8.21 to 1.9.13

Cherry picked dependabot commits as I can't merge dependabot PRs as they fail on tests. It seems we have different Api-Key for dependabot secrets - Secret source: Dependabot vs Secret source: Actions (trunk) and as a result unexpected appId in tests.
`


Disable travis CI

Already created jenkins CI, so disable travis CI.

retest this please

retest this please

retest this please

retest this please

retest this please


feat(slonik): add support for custom sql factory class

In slonik package, make it easier to customize the SqlFactory class in the Service.
Instead of having to rewrite the getFactory method, s Service class now only has to define its sqlFactoryClass property
import MySqlFactory from "...";

class MyService extends BaseService {
  ...
  get sqlFactoryClass() {
    return MySqlFactory;
  }

I have tested this minimally in the website-build package, and it needs to be tested much more thoroughly. In particular, please check other projects to see if they already define a custom SqlFactory class.

I have tested it in app, working as expected.
Most of the model in different projects defined a custom SqlFactory (extending DefaultSqlFactory) rewriting getFactory method so this changes will not affect them. but devs can refactor the existing model services to adopt this as well as implement in new services.
Note: There is a typo in the branch name.


Use SIMD for sequence::reversecomplement

This PR uses google/highway to make portable compilation.
This is tested on:

ubuntu x86
mac OS x86
mac OS ARM64
windows

To make this work I had to add cmake to improve the developer experience.
This includes the ability to auto generate the build system, debug the code, and produce release and debug versions of the code.
This repo should be relatively straight forward to get started:
If you clone the repo and run
make

It will build the entire system for you.
The only system dependencies for this project are:
cmake
make
ninja-build
isal-dev

Any further commit to be pushed in?

Any further commit to be pushed in?

Not for now. I'll make a separate PR for future changes.
There are a couple of other things that I can be improved. In a future PR:

Add back in commented out tests for fastqreader.cpp
performance analysis shows that most of the time is spent in void Stats::statRead(Read* r). I'll look to see if that can be vectorised easily.
Update cmake to add precompiled headers for faster builds too.

Build on Mac osx arm64
-- Running vcpkg install - done
CMake Error: CMake was unable to find a build program corresponding to "Ninja Multi-Config".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage

Could you please check the CMakeLists.txt and CMakePresets.json, today I have no enough time to dive in.

Build on Mac osx arm64
-- Running vcpkg install - done
CMake Error: CMake was unable to find a build program corresponding to "Ninja Multi-Config".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
CMake Error: CMAKE_C_COMPILER not set, after EnableLanguage
CMake Error: CMAKE_CXX_COMPILER not set, after EnableLanguage

Could you please check the CMakeLists.txt and CMakePresets.json, today I have no enough time to dive in.

after installing ninja, it was successful to compile

I have merged this pr, but we still need to examine the necessity to make it so complicated. At first, I thought having cmake was enough, but now ninja and vcpkg are also introduced. Bioinformatics guys never run their pipelines on Windows, so actually I think we should skip Windows support to keep simplicity.

I have merged this pr, but we still need to examine the necessity to make it so complicated. At first, I thought having cmake was enough, but now ninja and vcpkg are also introduced. Bioinformatics guys never run their pipelines on Windows, so actually I think we should skip Windows support to keep simplicity.

Thanks for meging.
vcpkg should not be an issue. if you run make it will setup vcpkg for you without any extra steps for the user.
Sorry I forgot to mention that ninja-build is a new build dependency. If we don't want to support windows this can be removed by changing the cmake generator to generate Unix makefile instead.

I have merged this pr, but we still need to examine the necessity to make it so complicated. At first, I thought having cmake was enough, but now ninja and vcpkg are also introduced. Bioinformatics guys never run their pipelines on Windows, so actually I think we should skip Windows support to keep simplicity.

Thanks for meging. vcpkg should not be an issue. if you run make it will setup vcpkg for you without any extra steps for the user.
Sorry I forgot to mention that ninja-build is a new build dependency. If we don't want to support windows this can be removed by changing the cmake generator to generate Unix makefile instead.

Yes, please submit a PR  to generate Unix makefile and remove unnecessary dependencies. Currently we have no motivation to support Windows. I agree with you to make it faster, but let's keep the simplicity as well.

it failed to compile on my ubuntu:
/usr/bin/cmake --preset "ninja-multi-vcpkg"
CMake Error: The source directory "/root/github/fastplong/ninja-multi-vcpkg" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
Makefile:48: recipe for target 'builds/ninja-multi-vcpkg/build.ninja' failed
make: *** [builds/ninja-multi-vcpkg/build.ninja] Error 1

it failed to compile on my ubuntu:
/usr/bin/cmake --preset "ninja-multi-vcpkg"
CMake Error: The source directory "/root/github/fastplong/ninja-multi-vcpkg" does not exist.
Specify --help for usage, or press the help button on the CMake GUI.
Makefile:48: recipe for target 'builds/ninja-multi-vcpkg/build.ninja' failed
make: *** [builds/ninja-multi-vcpkg/build.ninja] Error 1

Ubuntu is my primary dev machine and I have tested on Ubuntu 24.04.
Make sure all the dev tools are installed.
sudo apt update && sudo apt install cmake make g++ gdb ninja-build curl zip unzip tar pkg-config

Then run
make

from the root directory.
If that fails try clean first by running
git clean -fdx

then run
make

latest ci run all seems to be passing.
https://github.com/OpenGene/fastplong/actions/runs/12384466602/job/34569070374

I am working on ubuntu 18.04.
the code is a clean checkout, and all dependencies are installed already.

I am working on ubuntu 18.04.
the code is a clean checkout, and all dependencies are installed already.

Have you tried updating to latest version?
sudo apt upgrade -y

If you want to compile the binary the easiest way is probably we add a new release workflow.
.github/workflows/release.yml

This will automatically build and publish the binaries to the github releases every time you push a new tag e.g. ("v0.2.3")

yes, my g++ is not supporting C++23, but we shouldn't require the users to have C++ 23 supported.
we should only consider C++ 17, or at most C++ 20.

it is also failing on my CentOS:
/usr/bin/cmake3 --preset "ninja-multi-vcpkg"
CMake Error: Could not read presets from /home/shifu/github/fastplong: Unrecognized "version" field
make: *** [Makefile:48: builds/ninja-multi-vcpkg/build.ninja] Error 1

Seems that cmake 3.28 is required to use this version field, we should definitely make the requirement lower.

I am working on ubuntu 18.04.
the code is a clean checkout, and all dependencies are installed already.

I suspect you're getting that issue because your g++ compiler is too old to support C++23.
Have you tried updating to latest version?
sudo apt upgrade -y

If you want to compile the binary the easiest way is probably we add a new release workflow.
.github/workflows/release.yml

This will automatically build and publish the binaries to the github releases every time you push a new tag e.g. ("v0.2.3")

hey, can you submit a PR to do this?

I am working on ubuntu 18.04.
the code is a clean checkout, and all dependencies are installed already.

I suspect you're getting that issue because your g++ compiler is too old to support C++23.
Have you tried updating to latest version?
sudo apt upgrade -y

If you want to compile the binary the easiest way is probably we add a new release workflow.
.github/workflows/release.yml

This will automatically build and publish the binaries to the github releases every time you push a new tag e.g. ("v0.2.3")

hey, can you submit a PR to do this?

I've done that here
https://github.com/OpenGene/fastplong/pull/13
https://github.com/OpenGene/fastplong/pull/12

but the issues are not resolved. I can 99% confirm that it's due to the CMake version.
CMake on my centos is 3.26
CMake on my ubuntu 18.04 is 3.10
They are the latest cmake on their apt/yum source.
I can change the source to upgrade cmake to the newer version, but you know, many other users may face the same problem.

I update my cmake to the latest version 3.31.2, compile again, and it's stuck here
[shifu@gm711-1 fastplong]$ make
git submodule update --init --recursive
Submodule 'vcpkg' (https://github.com/microsoft/vcpkg) registered for path 'vcpkg'
Cloning into '/home/shifu/github/fastplong/vcpkg'...
Submodule path 'vcpkg': checked out '3edabbe1407e2d4d8ce5b78bab8abf42cc966d10'
/usr/local/bin/cmake --preset "ninja-multi-vcpkg"
Preset CMake variables:

  CMAKE_TOOLCHAIN_FILE:FILEPATH="/home/shifu/github/fastplong/vcpkg/scripts/buildsystems/vcpkg.cmake"

-- Bootstrapping vcpkg before install

I update my cmake to the latest version 3.31.2, compile again with a new checkout, and it's stuck here
[shifu@gm711-1 fastplong]$ make
git submodule update --init --recursive
Submodule 'vcpkg' (https://github.com/microsoft/vcpkg) registered for path 'vcpkg'
Cloning into '/home/shifu/github/fastplong/vcpkg'...
Submodule path 'vcpkg': checked out '3edabbe1407e2d4d8ce5b78bab8abf42cc966d10'
/usr/local/bin/cmake --preset "ninja-multi-vcpkg"
Preset CMake variables:

  CMAKE_TOOLCHAIN_FILE:FILEPATH="/home/shifu/github/fastplong/vcpkg/scripts/buildsystems/vcpkg.cmake"

-- Bootstrapping vcpkg before install

So this gets stuck for a few mins?
This is the configuring step.
I was able to get this working on Ubuntu-22.04 and Ubuntu-24.04.
There are a couple of ways we can fix this.
Generally these kinds of issues are solved by using a Docker container so that everything is setup without the dev needing to touch their host system.
Though that would be adding yet another dependency....
For users that aren't working on the code, they should be able to download the latest version of the built binaries from github releases or this website.

Finally I succeeded to compile the code on my CentOS and ubuntu 18.04, after upgrading cmake to 3.31.1
It got stuck because the network issue, my server has bad connection to GitHub. It takes a very long time to bootstrap, and for many times it failed.
CMake 3.28.3 is required to support the preset you committed.


bencode: 0.5.0 -> 1.0.1

Description of changes
The release is not listed under the GitHub releases page, but tagged and mentioned in the changelog.
Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage

Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

bencode
torrenttools

[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 205709 run on x86_64-linux 1

2 packages built:

bencode
torrenttools


Angular apps not working in Safari v15 due to ReferenceError

Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
When we open angular.io website in safari browser in mac then it giving blank page and if we do refresh that page than also it's giving blank page and when we open inspect element from developer open in safari browser and do refresh that page then it open perfectly so it's an issue I have provided screenshot.

This when I open angular.io link in Safari browser in Mac.

This when I open inspect element of safari browser and still website is not working.

And at last this after opening Inspect element I refresh the page then website is working properly.

Please provide a link to a minimal reproduction of the bug
https://angular.io
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run ng version)
No response
Anything else?
No response

In my understanding, this happened specifically with this component because it's using animations + content projection.

Animations are causing the static block.
Content projection causes the static block to access the notification_component_c0 = ['*'] variable (outside the class) which breaks WebKit parser's scope analysis.
... but I might be totally wrong 🙃

The hardest thing here is to define what are other "similar" situations 😅

Had a similar issue on Safari Mobile on the iphone. I was able to fix only by reset the browserlistrc to
> 1%
last 2 versions
not ie > 0
not ie_mob > 0
not dead

Had a similar issue on Safari Mobile on the iphone. I was able to fix only by reset the browserlistrc to
> 1%
last 2 versions
not ie > 0
not ie_mob > 0
not dead

While I was upgrading to Angular v15 browserlistsrc was deleted automatically.


How do we plan to take CC payments from sponsors?

If we use the 'donate' page, then we'll probably want some more details about the company and contact information for the payer.
Otherwise, maybe a separate page and typeform specifically for sponsorship payments.
Could even be an unlisted page that we direct link to when needed.
Last option, probably, we might be able to invoice via stripe.
I'll have to look into that.

I'm all for sending an unlisted page. Something like https://acmutsa.org/sponsorship-payment
And we can setup on strip/zapier side to send a email for their payment.
sorry for the late reply


Update Deep_Learning_Project-Pytorch.ipynb

address two small error messages:

invalid index of a 0-dim tensor;
implicit dimension choice for softmax

ditto


framework: do not mix plain and keyword target_link_libraries() signa…

…tures
Fixes
| CMake Error at framework/CMakeLists.txt:461 (target_link_libraries):
|   The plain signature for target_link_libraries has already been used with
|   the target "framework".  All uses of target_link_libraries with a target                                            |   must be either all-keyword or all-plain.
|
|   The uses of the plain signature are here:
|                                                                                |    * framework/CMakeLists.txt:453 (target_link_libraries)
|
Signed-off-by: Khem Raj<EMAIL_ADDRESS>Description
Please include a summary of the change, new sample or fixed issue. Please also include relevant motivation and context.
Please read the contribution guidelines
Fixes #
General Checklist:
Please ensure the following points are checked:

[ ] My code follows the coding style
[ ] I have reviewed file licenses
[ ] I have updated the header Copyright to reflect the current year (CI build will fail if Copyright is out of date)
[ ] I have commented any added functions (in line with Doxygen)
[ ] I have commented any code that could be hard to understand
[ ] My changes do not add any new compiler warnings
[ ] My changes do not add any new validation layer errors or warnings
[ ] I have used existing framework/helper functions where possible
[ ] My changes build on Windows, Linux, macOS and Android. Otherwise I have documented any exceptions
[ ] My changes do not add any regressions
[ ] I have tested every sample to ensure everything runs correctly
[ ] This PR describes the scope and expected impact of the changes I am making

Sample Checklist
If your PR contains a new or modified sample, these further checks must be carried out in addition to the General Checklist:

[ ] I have tested the sample on at least one compliant Vulkan implementation
[ ] If the sample is vendor-specific, I have tagged it appropriately
[ ] I have stated on what implementation the sample has been tested so that others can test on different implementations and platforms
[ ] Any dependent assets have been merged and published in downstream modules
[ ] For new samples, I have added a paragraph with a summary to the appropriate chapter in the samples readme

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

Do you need CLAs for such one liners ?

I'm by no means the expert, but I think it'd be helpful if you're willing to accept the CLA even for the small commit.  The good news is it's a one time acceptance.


Auto free disk space for Mac DeviceLab bots

As of 04/09/2025, 7 out of 50 recent closed infra: device lab bugs are related to Mac bots low on disk space. Example: https://github.com/flutter/flutter/issues/146353
Current action: manually clean up some non critical logs/temp/cache dirs to free space.
We should auto the process to relieve maintenance burden.

[ ] Collect list of common dirs that need to free up /cc @kentnguyen99 Please help with this.
[ ] Implement auto free logics in device doctor and executed from bot config

Here directories need to clean out to free up disk space.
/private/var/folders/*
/opt/flutter/xcode/*

@kentnguyen99 Let's hold on cleaning up /opt/flutter/xcode, which are prod artifacts and are being auto handled by a separate salt state. /cc @ricardoamador will help confirm the logics work as expected from salt side for devicelab bots.

Okay I made a change to the salt cron as I had initially used the wrong xcode directory. Deploying and testing changes.

Looks like salt is not updating as I do not see this change on any of the machines.


Publish newest version to npm (including #81)

Hi,
first of all: great project. I had (nearly) no issue using and integrating it.
I was wondering whether the current state (best with an update to 0.0.9 including the latest minified output - see #81) could be published to npm? I looked through the changes and a project of mine could really benefit from the changes (looking at my bugtracking system). Seems there is already a version 0.0.8 but it is not published on npm.
Best regards

Hi,
It is published, thanks!


Positioned absolute lightbox opener causing issues

I wanted to add a positioned absolute View as the lightbox opener inside one of my images. With an icon suggesting: "MAXIMIZE", so i position it with 'absolute' property. Problem is, whenever i attempt to tap on it, it doesn't recognize the event. Whenever i removed the absolute, it started working normally but the size is huge whenever i press the button.
This is my structure:
<Lightbox
                                        springConfig={{tension: 15, friction: 7, overshootClamping: true}}
                                        swipeToDismiss={false}
                                        renderContent={this._renderCarousel}>

                                        <View style={scopedStyles.fullScreenContainer}>
                                            <Icon style={scopedStyles.fullScreenIcon} name={'md-open'} />
                                        </View>
                                    </Lightbox>

This is the styling:
    fullScreenContainer: {
        position: 'absolute',
        height: 50,
        width: 50,
        borderRadius: 25,
        backgroundColor: CommonStyles.BLACK,
        left: 10,
        bottom: 10,
        justifyContent: 'center',
        alignItems: 'center'
    },
    fullScreenIcon: {
        fontSize: 28,
        color: CommonStyles.WHITE
    },

Try it out and let me know if this occurs to you guys as well.
Btw, awesome library :)

My bad! i had to add the styling to Lightbox component.


Exaustive case patterns

Add it.
Fix the tests
Closes #613

Looks good. Just some minor things.
It is kind of sad that we always get worse coverage when adding better errors. I should look into if there is some way of testing the messages themselves.

How worth is it? I honestly think the coverage is fundementally a flawed metric, but we've already talked about that.
We fire each of the error paths, I honestly think it's just a problem with how coverage for rust is calculated. If you want to put time on it, feel free, but i think bugs are a better time investment right now.


Integer arrays are not working properly

convertParam function doesn't handle arrays. When it converts an integer array property (prisma type is Int[]) it tries to parse it as a Number and it leads to undefined behaviour. I believe to fix that you need to override isArray method in the Property class and adjust convertParam accordingly.
https://github.com/SoftwareBrothers/adminjs-prisma/blob/0cd6a63a18c0419942e00a3ed1a30847fd012a4b/src/utils/converters.ts#L8-L31
As a temporary fix I have to patch convertParam with something like this:
if (Array.isArray(value)) return value.map((v) => convertParam(property, fields, v));

Would love to see a fix for this, as any model with Type[] or JSONB arrays are no longer editable through the dashboard. All update requests send NaN for any Int[] fields that we're commonly using in our schema.


Update _encryption.py

Simple typo fix in encryption.py

Hi @dubrie
Thanks for catching this and post a pr!
While currently we don't have a plan to release the change in this repo.
You are highly encouraged to try the re-written azure-storage-blob (version 12.X.X) https://github.com/Azure/azure-sdk-for-python/tree/master/sdk/storage/azure-storage-blob
Thanks again!


Use windowed flyouts to improve accessibility at smaller window sizes

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #issue...
Related #issue...

Details of Changes
Add details of changes here.

set ShouldConstrainToRootBounds="False" for flyouts so that the full ui can be shown at smaller window sizes, and to prevent overlap with the secondary commands flyout when the command bar is overflowing

Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility

Screenshots (optional)

@winston-de can this be done on the context menu flyouts as well?

it should be already for menu flyouts and command bar flyouts, it's just the custom flyouts that didn't have it.


Dynamically changing "readOnly" does not work

Hey,
please have a look at my JSFiddle here: http://jsfiddle.net/hcpLn7t5/
I expect the Knob set to "readonly = false" when executing the last JS line.. why doesn't it work?

The event binding is only done on initialization, not when it is reconfigured.
https://github.com/aterrien/jQuery-Knob/issues/32

Having the same problem. Currently using this workaround when I want to prevent users changing the value by clicking.
$('#something').knob({
        change : function (v) {
                return false;
         }
 });

But proper dynamic configuration would be a great addition.


fix(docs): fix link to MySQL EntityManager test

Thanks. Looks like GH is having outage so the CI fails...

I also noticed that in the header EntityRepository on https://mikro-orm.io/docs/repositories is rendered backslash but here on GitHub is not rendered.

Afaik this is a markdown problem, docusaurus (used for docs) uses some different flavour of it I think. Originally I had that as code snippet which solves it, but the GH pages template was rendering it with wrong font size or something like that. I guess we could use code snippets there now.

Yeah, I see 500 a lot.
Also I noticed backslash in heading in docs here, but I don't know how to fix it. Markdown on GitHub is rendered correctly.


Any ETA for version 4.214 of "AzureRmWebAppDeployment@4" to be published?

Question, Bug, or Feature?
Type: Question
Enter Task Name: AzureRmWebAppDeployment@4
Issue Description
The change below introduced in version 4.212 causes no KUDU deployment history for Web Deploy:
Fix for Cosmetic API calls (#16868) · microsoft/azure-pipelines-tasks@b82a8e6 (github.com)

It should be fixed in revoke code fix done for cosmetic API calls by v-nagarajku · Pull Request #17309 · microsoft/azure-pipelines-tasks (github.com) which corresponds to version 4.214.
I notice version 4.214 was committed 3 weeks ago. But still version 4.213 is being used. Any ETA to publish version 4.214?
And in general, is there anywhere we can track the release status of specific commit?
Task logs
logs_155.zip

Hi @laika1234, thank you for your question.
The latest version of the task will be deployed with the next release. Unfortunately, there is no public option to track releases.

Hi @laika1234, thank you for your question. The latest version of the task will be deployed with the next release. Unfortunately, there is not public option to track releases.

Thanks @ismayilov-ismayil , is there any tentative ETA for next release?

My apologies, the date of the release is not known in advance. We will announce about release.

@ismayilov-ismayil  is it possible to update here when the release is ready or anywhere I can subscribe to?

214 has since been released. This issue can be closed.


Hi, thanks for answering and quick response and fix problem. But now there's a problem with row 58.

Hi, thanks for answering and quick response and fix problem. But now there's a problem with row 58.
Is there that's get_date((int) $added, the problem?
Im using autoinstaller https://github.com/darkalchemy/Pu-239-Installer and ubuntu 18.04
Sorry, but i no can reopen old issue

Originally posted by @RememberForgottenHits in https://github.com/darkalchemy/Pu-239/issues/16#issuecomment-557909312

Until I can fix it, just replace $added with$comment['added']
I will fix it tonight.

fixed fd113cd


Feat/assign task multi version prover1

Purpose or design rationale of this PR
Describe your change. Make sure to answer these three questions: What does this PR do? Why does it do it? How does it do it?

assign prover task to multi version prover
coordinator import genesis.json
coordinator get_task add fork_block_number param
prover add fork_block_number param

PR title
Your PR title must follow conventional commits (as we are doing squash merge for each PR), so it must start with one of the following types:

[ ] build: Changes that affect the build system or external dependencies (example scopes: yarn, eslint, typescript)
[ ] ci: Changes to our CI configuration files and scripts (example scopes: vercel, github, cypress)
[ ] docs: Documentation-only changes
[x] feat: A new feature
[ ] fix: A bug fix
[ ] perf: A code change that improves performance
[ ] refactor: A code change that doesn't fix a bug, or add a feature, or improves performance
[ ] style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
[ ] test: Adding missing tests or correcting existing tests

Deployment tag versioning
Has tag in common/version.go been updated or have you added bump-version label to this PR?

[ ] No, this PR doesn't involve a new deployment, git tag, docker image tag
[x] Yes

Breaking change label
Does this PR have the breaking-change label?

[x] No, this PR is not a breaking change
[ ] Yes

btw, the patch version of major.minor.patch seems very large now.

tweaking the PR's name, and can further consider it.


Performance improvements

This PR addresses the changes proposed in #203
As described in the issue, loading data seemed unnecessarily slow. On a test CSV file containing 50k rows, each with 2 cols of fixed length text, target-postgres was spending about 20 seconds loading the data.
Some profiling helped identify the bottlenecks, as described in the issue.
This PR proposes 3 distinct improvements, in decreasing order of time savings (based on my test case). With cProfile instrumentation, the loading took approx 32 seconds instead of 20:

There is only a limited combination of arguments to _serialize_table_record_field_name so that it can be cached to avoid recalculating over and over. The method was called for each field of each row, including all 5 metadata fields. In my example, this led to about 350k calls. With functools.lru_cache applied, cache_info showed that only 7 calls were really made, all remaining calls resulted in cache hits. My test data is extremely consistent, so might be a best case, but my understanding is that this should result in at most number_of_fields * possible_data_types actual calls. If multiple batches are required to load the data, each batch will recreate a fresh cache. My fix to allow caching feels a bit hackish, but it seems to work (improvement suggestions welcome!). This saves about 15s/32 (with profiling on).
The same seems to apply to serialize_table_record_datetime_value (in my tests, each record has the same value in _sdc_batched_at). The call to arrow is pretty expensive. In my testing, the exact same value was formatted once per row. Applying caching on this seems straightforward. In my sample, it led to about 14s/32 of time savings.
The last bit of excessive time is spent in deepcopy which is a weirdly slow function. Replacing it with pickling/unpickling saved about 1.5s again.

In the end, with these speedups applied, the same data now loads in under 4s instead of the original 20s.

This fix is remarkably effective. It cuts down my processing time in half.
I'm reading 102 smallish files (about 1MB each) from S3, and writing to AWS Aurora Serverless. I'm writing about 200,00 records. This patch cuts down my time from 6 minutes to 3 minutes.

And another test: 8.8 million rows. Used to take 86 minutes, now down to 57 (while the machine was overloaded doing other stuff). I think this should really be merged!

FWIW, I've forked this repo and added some further performance improvements and memory savings in https://github.com/oviohub/target-postgres/


Error: occurred while checking if volume exists: EOF

Rancher Version:
v1.1.4
Docker Version:
Docker version 1.12.1, build 23cf638
OS and where are the hosts located? (cloud, bare metal, etc):
OS: ros version v0.7.0
Cloud: Amazon Web Services - EC2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
My environment was built with a single node rancher running ros version v0.7.0 with external DB + single host running ros version v0.7.0
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
You will need an Amazon web services account.

Create an S3 bucket at Amazon Web Services. For this example, I'll use mybucket.
Create an IAM user with the following policy:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "s3:*"
            ],
            "Resource": [
                "arn:aws:s3:::mybucket",
                "arn:aws:s3:::mybucket/*"
            ]
        }
    ]
}

Build the following image and name it sb-baseimage. You need to download some packages first and put them into the same folder of the Dockerfile:

wget https://github.com/just-containers/s6-overlay/releases/download/v<IP_ADDRESS>/s6-overlay-amd64.tar.gz
wget https://github.com/jwilder/dockerize/releases/download/v0.2.0/dockerize-linux-amd64-v0.2.0.tar.gz
wget https://github.com/kelseyhightower/confd/releases/download/v0.11.0/confd-0.11.0-linux-amd64 ; gzip -9 confd-0.11.0-linux-amd64

FROM alpine:3.4

#------------------------------
# EVIRONMENT VARIABLES
#------------------------------

ENV S6_FILE=s6-overlay-amd64.tar.gz \
    DOCKERIZE_FILE=dockerize-linux-amd64-v0.2.0.tar.gz \
    CONFD_FILE=confd-0.11.0-linux-amd64.gz \
    BIN_PATH=/usr/local/bin

#------------------------------
# INSTRUCTIONS
#------------------------------

RUN apk --update add \
    tar

COPY root /

RUN cd /tmp \
    && tar -xzf ${S6_FILE} -C / \
    && tar -zxf ${DOCKERIZE_FILE} -C ${BIN_PATH}/ \
    && gunzip -c ${CONFD_FILE} > ${BIN_PATH}/confd \
    && chown root. ${BIN_PATH}/* \
    && chmod 0700 ${BIN_PATH}/* \
    && mkdir -p /etc/confd/conf.d \
    && mkdir -p /etc/confd/templates \
    && rm -rf /tmp/* \
    && apk del --purge tar \
    && rm -rf /var/cache/apk/* \
    && chmod 1777 /tmp

ENTRYPOINT ["/init"]

Execute the following commands on the registered host to enable kernel-headers (it is necessary to make possible run a nfsserver in a container)

sudo ros service enable kernel-headers
sudo ros service up -d kernel-headers

Build the following image: https://forums.rancher.com/t/nfs-server-no-support-in-current-kernel/4343/24?u=bruno.galindro and name it sb-s3nfs.
Add a stack called convoy-nfs using the docker-compose and rancher-compose from the above link. Don't forget to put the AMI Access Key into AWSACCESSKEYID and AWSSECRETACCESSKEY environment variables on the docker-compose.yml. The URL variable must meet your S3 region. See this documentation for more details.

# docker-compose.yml
s3nfs:
  image: sb-s3nfs
  environment:
    AWSACCESSKEYID: <put_here>
    AWSSECRETACCESSKEY: <put_here>
    URL: <S3 url>
  cap_add:
    - SYS_ADMIN
  tty: true
  privileged: true
  stdin_open: true

convoy-nfs:
  labels:
    io.rancher.container.create_agent: 'true'
    io.rancher.scheduler.global: 'true'
  privileged: true
  pid: host
  volumes:
    - /lib/modules:/lib/modules:ro
    - /proc:/host/proc
    - /var/run:/host/var/run
    - /run:/host/run
    - /etc/docker/plugins:/etc/docker/plugins
  image: rancher/convoy-agent:v0.9.0
  command: volume-agent-nfs
  links:
    - s3nfs:s3nfs

convoy-nfs-storagepool:
  labels:
    io.rancher.container.create_agent: 'true'
  image: rancher/convoy-agent:v0.9.0
  volumes:
    - /var/run:/host/var/run
    - /run:/host/run
  command: storagepool-agent
  links:
    - s3nfs:s3nfs

# rancher-compose.yml
s3nfs:
  scale: 1

convoy-nfs:
    metadata:
        nfs_server: "s3nfs"
        mount_dir: "/"
        mount_opts: "proto=tcp,nfsvers=4"
    health_check:
        request_line: GET /healthcheck HTTP/1.0
        port: 10241
        interval: 2000
        response_timeout: 2000
        unhealthy_threshold: 3
        healthy_threshold: 2

convoy-nfs-storagepool:
    metadata:
        nfs_server: "s3nfs"
        mount_dir: "/"
        mount_opts: "proto=tcp,nfsvers=4"
    scale: 1
    health_check:
        request_line: GET /healthcheck HTTP/1.0
        port: 10241
        interval: 2000
        response_timeout: 2000
        unhealthy_threshold: 3
        healthy_threshold: 2

Wait for the stack to be fully deployed:

Go to Infrastructure > Storage and Add a new Volume. You need to refresh the page to make the volume visible (this problem was reported before here: https://github.com/rancher/rancher/issues/3312 and it still occurs with 1.1.4 version @deniseschannon. I'm very sorry about not giving a feedback to you...)

Now add a stack (nfstest) with the following docker-compose and rancher-compose files:

# docker-compose.yml
nfsclient:
  tty: true
  entrypoint:
  - /bin/sh
  image: alpine
  volumes:
  - s3fs:/data
  stdin_open: true
  volume_driver: convoy-nfs

# rancher-compose.yml
nfsclient:
  scale: 1

Results:
After the nfstest stack is created, the following error is displayed:

I can confirm that on the S3 bucket, some files was created after I have launched the nfstest stack:
s3fs                                          # this is a directory
config/vfs_volume_s3fs.json   # this file has 0 bytes

Expected:
I expect to mount the nfs exported directory into a new container inside a different stack.

@galindro curious to know if this works with docker 1.10.3? Would there be any chance to validate the issue there?

@aemneina sorry about my late answer. Unfortunatelly I don't have much time to validate this env in a docker 1.10.3 version. Why did you suspect that this error could be related to docker version?

No worries, my thoughts are around the issue being go version related. Nothing definitive pointing to that, just a hunch I was trying to explore.

Any return about this problem? Anyone has tested this scenario? It is very important to many users to use s3 as a storage for cost reductions

@cjellick or @yasker do you spot anything obviously wrong with what @galindro is trying to do? Maybe you guys have some advice.

With the release of Rancher 2.0, development on v1.6 is only limited to critical bug fixes and security patches.


[Bug]: Call to undefined method Hasnayeen\Themes\Themes\Dracula::getPrimaryColor()

What happened?
After Update composer
themes 3.0.13 to 3.0.16
How to reproduce the bug
when updated composer
and applied new theme then
Call to undefined method Hasnayeen\Themes\Themes\Dracula::getPrimaryColor()
Package Version
3.0.16
Filament Version
3.0
PHP Version
8.1
Laravel Version
10
Notes
Call to undefined method Hasnayeen\Themes\Themes\Dracula::getPrimaryColor()
Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/117.0

Fixed by 7e53b64


feat: Add responsive Navbar

Preview

Hi @Kands221,
Thanks for your initial changes for this issue! I've made a few updates:

Refactored the dynamic content pages to utilize the child-parent page structure.
Updated the banner to appear above the navbar for better visibility.
You can now review these changes.
resolve app.css conflicts

Let me know if you have any questions or need further adjustments!


Remove timeouts from gen_server calls

Both the consumer and the producer may attempt to connect to several Kafka nodes when handling requests. In case of network hiccups or Kafka nodes being unavailable such operations may take many seconds.
Therefore it's better not to use 5 second timeouts in calls to these processes.

Please bump version in src/brod.app.src.

Done. (The old version was 1.5.0, but I bumped it to 1.5.2, because the last tag said 1.5.1.)

:+1:


example-runner-wgpu: surface configuration failed: native window is in use

I'm barely getting started but since the documentation recommends to file issues, here is one.
Example & Steps To Reproduce

cargo run --bin wgpu_runner (I guess it should be renamed to example-runner-wgpu to match the documentation):
backtrace
[2023-04-27T11:12:38Z ERROR wgpu_core::device] surface configuration failed: Native window is in use
thread 'main' panicked at 'Error in Surface::configure: Validation Error

Caused by:
    Invalid surface
', .../.cargo/git/checkouts/wgpu-53e70f8674b08dd4/a502282/wgpu/src/backend/direct.rs:734:18
stack backtrace:
   0: rust_begin_unwind
             at /rustc/44cfafe2fafe816395d3acc434663a45d5178c41/library/std/src/panicking.rs:579:5
   1: core::panicking::panic_fmt
             at /rustc/44cfafe2fafe816395d3acc434663a45d5178c41/library/core/src/panicking.rs:64:14
   2: wgpu::backend::direct::Context::handle_error_fatal
             at .../.cargo/git/checkouts/wgpu-53e70f8674b08dd4/a502282/wgpu/src/backend/direct.rs:308:9
   3: <wgpu::backend::direct::Context as wgpu::context::Context>::surface_configure
             at .../.cargo/git/checkouts/wgpu-53e70f8674b08dd4/a502282/wgpu/src/backend/direct.rs:734:13
   4: <T as wgpu::context::DynContext>::surface_configure
             at .../.cargo/git/checkouts/wgpu-53e70f8674b08dd4/a502282/wgpu/src/context.rs:2053:9
   5: wgpu::Surface::configure
             at .../.cargo/git/checkouts/wgpu-53e70f8674b08dd4/a502282/wgpu/src/lib.rs:4144:9
   6: example_runner_wgpu::graphics::run::{{closure}}::{{closure}}
             at ./examples/runners/wgpu/src/graphics.rs:108:13
   7: example_runner_wgpu::graphics::run::{{closure}}::{{closure}}
             at ./examples/runners/wgpu/src/graphics.rs:160:42
   8: winit::platform_impl::platform::sticky_exit_callback
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/platform_impl/linux/mod.rs:884:9
   9: winit::platform_impl::platform::x11::EventLoop<T>::run_return::single_iteration
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/platform_impl/linux/x11/mod.rs:334:17
  10: winit::platform_impl::platform::x11::EventLoop<T>::run_return
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/platform_impl/linux/x11/mod.rs:443:31
  11: winit::platform_impl::platform::x11::EventLoop<T>::run
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/platform_impl/linux/x11/mod.rs:498:25
  12: winit::platform_impl::platform::EventLoop<T>::run
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/platform_impl/linux/mod.rs:792:56
  13: winit::event_loop::EventLoop<T>::run
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/winit-0.28.3/src/event_loop.rs:305:9
  14: example_runner_wgpu::graphics::run::{{closure}}
             at ./examples/runners/wgpu/src/graphics.rs:145:5
  15: futures_executor::local_pool::block_on::{{closure}}
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.19/src/local_pool.rs:315:23
  16: futures_executor::local_pool::run_executor::{{closure}}
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.19/src/local_pool.rs:90:37
  17: std::thread::local::LocalKey<T>::try_with
             at /rustc/44cfafe2fafe816395d3acc434663a45d5178c41/library/std/src/thread/local.rs:446:16
  18: std::thread::local::LocalKey<T>::with
             at /rustc/44cfafe2fafe816395d3acc434663a45d5178c41/library/std/src/thread/local.rs:422:9
  19: futures_executor::local_pool::run_executor
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.19/src/local_pool.rs:86:5
  20: futures_executor::local_pool::block_on
             at .../.cargo/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.19/src/local_pool.rs:315:5
  21: example_runner_wgpu::graphics::start
             at ./examples/runners/wgpu/src/graphics.rs:433:13
  22: example_runner_wgpu::main
             at ./examples/runners/wgpu/src/lib.rs:171:5
  23: wgpu_runner::main
             at ./examples/runners/wgpu/src/bin/wgpu_runner.rs:9:5
  24: core::ops::function::FnOnce::call_once
             at /rustc/44cfafe2fafe816395d3acc434663a45d5178c41/library/core/src/ops/function.rs:250:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

here as a workaround:
diff --git i/examples/runners/wgpu/src/graphics.rs w/examples/runners/wgpu/src/graphics.rs
index 9a5bd43263..ca0ceef4cb 100644
--- i/examples/runners/wgpu/src/graphics.rs
+++ w/examples/runners/wgpu/src/graphics.rs
@@ -154,16 +154,6 @@ async fn run(
             Event::MainEventsCleared => {
                 window.request_redraw();
             }
-            Event::Resumed => {
-                let new_surface = unsafe { instance.create_surface(&window) }
-                    .expect("Failed to create surface from window (after resume)");
-                surface_with_config = Ok(auto_configure_surface(
-                    &adapter,
-                    &device,
-                    new_surface,
-                    window.inner_size(),
-                ));
-            }
             Event::Suspended => {
                 if let Ok((_, surface_config)) = &surface_with_config {
                     surface_with_config = Err(SurfaceCreationPending {

System Info

Rust: rustc 1.69.0-nightly (44cfafe2f 2023-03-03)
OS: NixOS 23.05.20230422.6c43a34
GPU: RUST_LOG=wgpu_hal=debug tells me it's using the discrete GPU here: NVIDIA GeForce RTX 3080 Ti Laptop GPU with driver /nix/store/...-nvidia-x11-530.41.03-6.1.25/lib/libGLX_nvidia.so.0

That should run under Xwayland (setup is similar to your default.nix, without the Wayland stuff that crashes for other reasons).

I'm not too familiar with this stuff, but it looks like the example in the wgpu repo calls surface.resume when start_condition() is met:
https://github.com/gfx-rs/wgpu/blob/0dc9dd6becdfd69ab241169171c37428fefaa1da/examples/src/framework.rs#L395
It looks like start_condition() is only met on android:
https://github.com/gfx-rs/wgpu/blob/0dc9dd6becdfd69ab241169171c37428fefaa1da/examples/src/framework.rs#L394
otherwise it doesn't do anything on resume, so your patch may be right! Well, after adding the android change.
Changing this would match what the wgpu folks said ("you are trying to use the same window more than once by different surfaces")


Make unit tests truly unit tests

Were previously running as integration tests.
FYI this breaks code coverage because unit tests are not run against the compiled module (whereas the integration tests do)

Closing as this seems to be a very very bad idea:

makes code coverage logic overly complex
makes CI/CD logic overly complex
deviates from the ModuleBuilder logic (test against the compiled module) even though using Pester InModuleScope is discouraged


swagger ui  was blocked when i use ginweb with token authentication  middleware

Describe the bug
g.Use(ginMiddleware.Cors()) // 跨域
tk := common.GetToken()
g.Use(ginMiddleware.Authorize(tk)) //鉴权
g.GET("/api/swagger/*any", ginSwagger.WrapHandler(swaggerFiles.Handler))

// Authorize 鉴权.
func Authorize(t *common.Token) gin.HandlerFunc {
	return func(c *gin.Context) {
		for _, b := range common.WhiteListUrl {
			if b == c.Request.URL.Path {
				c.Next()

				return
			}
		}
		// token校验
		tokenValue := c.Request.Header.Get("token")
		if _, err := t.Decode(tokenValue); err != nil { // token校验失败
			c.Abort()
			resp := common.NewRespMsg(common.StatusTokenInvalid, common.MsgFailAuthToken, nil)
			c.JSON(http.StatusOK, resp)

			return
		}
		// token校验成功
		c.Next()
	}
}

when i comment “g.Use(ginMiddleware.Authorize(tk))”   http://localhost:8080/api/swagger/index.html wil work. otherwise  swagger web ui will block, showing white
Your swag version
swag version v1.7.4
Your go version
go 1.8
Desktop (please complete the following information):

OS: mac
Browser: chrome

anybody meet this issue?
Maybe I'm not going about it the right way？

Authorize(tk) checks for a token in the request's header, and it's registered as a global middleware (at this line g.Use(ginMiddleware.Authorize(tk))). You're telling Gin to check for the token for all requests, including the request to Swagger web UI.
I'm guessing this is not what you want; you probably want to check for the token only for your API routes. You need to register the middleware on a per route or per route-group basis.
By the way, if the token doesn't pass validation, you should return a 401 http status code: replace c.JSON(http.StatusOK, resp) with c.JSON(http.StatusUnauthorized, resp).

Authorize(tk) checks if you're visiting a whitelisted URL, or if you have a token in the request's header. This function is registered as a global middleware (at this line g.Use(ginMiddleware.Authorize(tk))). You're telling Gin to perform the checks for all requests, including the request to Swagger web UI.
Is the web UI address in the whitelist? If it is, are you supplying the token in the request header when you visit the web UI?
You should break this into 2 middlewares: one checks the whitelist, the other checks the token.
By the way, if the token doesn't pass validation, you should return a 401 http status code: replace c.JSON(http.StatusOK, resp) with c.JSON(http.StatusUnauthorized, resp).

Authorize(tk) checks if you're visiting a whitelisted URL, or if you have a token in the request's header (you might want to split this into 2 middlewares). This function is registered as a global middleware (at this line g.Use(ginMiddleware.Authorize(tk))). You're telling Gin to perform the checks for all requests, including the request to Swagger web UI.
Is the web UI address in the whitelist? If it is, are you supplying the token in the request header when you visit the web UI?
By the way, if the token doesn't pass validation, you should return a 401 http status code: replace c.JSON(http.StatusOK, resp) with c.JSON(http.StatusUnauthorized, resp).

thanks for you reply, of course i  added "/api/swagger/index.html" into WhiteListUrl, and i also check web find some clue as below

Authorize(tk) checks if you're visiting a whitelisted URL, or if you have a token in the request's header (you might want to split this into 2 middlewares). This function is registered as a global middleware (at this line g.Use(ginMiddleware.Authorize(tk))). You're telling Gin to perform the checks for all requests, including the request to Swagger web UI.
Is the web UI address in the whitelist? If it is, are you supplying the token in the request header when you visit the web UI?
By the way, if the token doesn't pass validation, you should return a 401 http status code: replace c.JSON(http.StatusOK, resp) with c.JSON(http.StatusUnauthorized, resp).

i solved it ,i modified Authorize function ,it can works
`func Authorize(t *common.Token) gin.HandlerFunc {
return func(c *gin.Context) {
// 不需要token验证的白名单 strings.HasPrefix(r.URL.Path, "/hello") ||
for _, b := range common.WhiteListUrl {
if b == c.Request.URL.Path || strings.Contains(c.Request.URL.Path, "swag") {
c.Next()
			return
		}
	}
	// token校验
	tokenValue := c.Request.Header.Get("token")
	if _, err := t.Decode(tokenValue); err != nil { // token校验失败
		c.Abort()
		resp := common.NewRespMsg(common.StatusTokenInvalid, common.MsgFailAuthToken, nil)
		c.JSON(http.StatusUnauthorized, resp)

		return
	}
	// token校验成功
	c.Next()
}

}`


ESM support: allow package self-reference imports

Node permits an es module inside a package to reference that package by its name. The behavior is documented here. I propose that jest also support this, as I believe the feature was created with testing in mind. It's highly useful for your internal tests to be able to reference your package in exactly the same way that external consumers will. I am willing to provide the implementation.

Yeah, we should implement all Node does for ESM. This seems dependent on #9771 landing first, tho?

Yep. No hurry, I have a workaround I'm using for now. Just wanted to ticket it so I would know when it was safe to remove the workaround.

This is also for CommonJS modules.

Actually, a self-reference import causes an infinite loop.
Maybe add a line about that problem in the doc, until resolved?

@Lcfvs The usual use case is tests importing the package under test in its tests. Given that we're discussing jest, I'm not sure what other use cases there would be. And since jest seeks out tests without requiring them to be imported anywhere, I don't see any appreciable risk of jest causing a loop.

Sorry, maube not the same context.
In my case, I'm reporting something like that:
lib/selfImporting.js:
import * as self from './selfImporting.js'

export function test () {
  console.log(self.test)
}

And inside the test:
import * as self from '../../lib/selfImporting.js' // causes the infinite loop

That’s not what a self-reference is. It’s using a package name, inside the package, to import something following the semantics of the “exports” field.

That specific case is a circular dependency, which while bad code and a bad practice, should work just fine according to the ES spec, afaict.

@ljharb Why a bad practice, please? any link about it?

Node supports that without an infinite loop??

@conartist6 Yep

What's the purpose exactly? Is the idea to get around shadowed names or something? I never had thought of doing that. I just cooked up a test to see if you can do the same thing with require, and it seems you can.

There is some cases like

access to the default within a function, without name it

import self from './self.js'

export function test () {
  console.log(self.prop)
}

export default {
  prop: 'value'
}

import * as self from './self.js'

self.test() // 'value'

to resolve conflicts between exports and variables

export function model (model) {
  console.log([self.model, model]) // [function model(), model]
}

Hmm yeah. It isn't correct to have imports below code, but my simple using node ESM also worked fine:
import fn from './self.mjs';

export default function test() {
  return fn === test;
}

From another module test() === true.

Do you know what gets into an infinite loop in jest? In theory it should be OK since it's turning a circular import which node supports into a circular require which node supports...

I don't know the jest internals enough but got this error
    RangeError: Maximum call stack size exceeded
      at node_modules/jest-runtime/build/index.js:574:33

Because, as far I understand, it indefinitely tries to set the same module which imports itself, creating a loop.

@Lcfvs i don’t think there’s any benefit in debating best practices here :-) this issue is about node’s package self-reference feature, which has nothing inherently to do with circular dependencies.

Yeah you've convinced me that what you're seeing is a bug, but it should be independent from this one. That means you could seek a fix before the blockers holding this bug up are resolved.

@ljharb jest have 1.2k open issues and a broken build. I'm currently a bored unemployed OSS maintainer. I know how to repro things and dig to the bottom of issues.  If you'd like to give me triage permissions maybe I could help?

@conartist6 i have no more permissions on this repo than you do.

Do you know who does? That information is not provided anywhere...

Is there any update on this?

The way Jest currently supports package exports is by doingresolve.sync(`${packageName}/package.json`). This fails since resolve doesn't find "own"/"self". Not sure how to support this properly without resolve supporting it.
https://github.com/facebook/jest/blob/816789920fe08b2f0245963e91d3a96fe80e1311/packages/jest-resolve/src/defaultResolver.ts#L118

I've hidden a few comments discussing other things. @Lcf.vs feel free to open a new issue about the infinite loop, that sounds like a bug 🙂

@SimenB You'd need to know what the closest package.json file is for a given module, presumably by looking it up in some sort of cache. That's a relatively common requirement these days since it's also necessary to check for "type": "module". Does Jest maintain that cache itself?

Yep: https://github.com/facebook/jest/blob/199f9811ae68b15879cbe18b7ef7ebd61eefcf23/packages/jest-resolve/src/fileWalkers.ts#L94
It's quite simple to walk up the tree once you have a file, in this case we need to find the root first

Symlinks, and multiple nested package.jsons (like for the type, or main fields), make it much more complex.

@ljharb why not? ...I thought that was exactly what I just showed that you could do and still be compliant with node's behavior.

@conartist6 i'm not sure if i'm understanding; your repo doesn't have any scripts or anything so i'm not sure how to verify your expected behavior.
In general, node only respects "exports" in a package - meaning, in something consumed from node_modules/foo or node_modules/@foo/bar. I would expect self-referencing to only work with a package as well (plus, the current project), not merely a folder containing a package.json.

Yeah, that's my understanding as well. "Closest package.json`" applies to "is this ESM or not", not resolution of specifiers to files

Ah, my bad, the README is there now. If i'm not mistaken that's exactly the test case I created (I didn't check it in, I just deleted bar/package.json#name. Node does not continue looking upwards. Is that what you meant?

That is what I meant; that seems like a bug in node itself then.

I even just tried putting something completely invalid in package.json. npm still treats the directory containing the invalid package.json as a package, and just blows up when trying to work with it.

I'm saying exactly that - it's supported and it's what node's own docs recommend (i was on the node modules working group and was present for all those decisions)

So what's the problem for self-refs then? If the nearest package.json file in the tree has a name, my understanding is that that would be the only module name that can be used as a self-reference.
I didn't know you were part that @ljharb. I have mad respect for how much you've done, and I depend on your work work for my livelihood several times over.

I would expect, and hope, that node looks upwards until it finds a package boundary (a package.json next to the closest node_modules folder).

Why would a node_modules folder have anything to do with it? Packages do not necessarily have deps or devDeps.
My experimentation shows that only package.json#name has any bearing on self-refs, and that is exactly as I would expect and hope. Somehow we're not understanding each other here, but I can't tell how so yet.

OK, let me try again :-) does node skip a name-less package.json when looking to resolve a self-reference?
(The other question is: I believe self-reference respects "exports". But, node itself doesn't respect "exports" unless it's inside a node_modules package boundary. so i think that resolving a self-reference also requires "exports" support, which is why resolve doesn't have it yet)

No, node never skips that I can tell.
Copying from the node package.json#export docs (in case anyone else ever reads this):

The "exports" field allows defining the entry points of a package when imported by name loaded either via a node_modules lookup or a self-reference to its own name. It is supported in Node.js 12+ as an alternative to the "main" that can support defining subpath exports and conditional exports while encapsulating internal unexported modules.

My example repo uses only exports, and shows node to be respecting them even without the presence of node_modules. However I also see that the main field is still the preferred entry point if it exists, unless we are resolving a reference into node_modules (or a self-reference).
That's a bit weird, but I understand the need to preserve compatibility. I don't think it's an issue here since the behavior for self-references is specified, and jest-resolve uses the resolve.exports library to process exports itself:

Sorry to be stuck on this point - so you're saying that self-references inside a package only work when there's not an intermediate package.json file between the self-reference and the package's actual root? (ie, a file with just "type" or "main", but no "name")?

Yes, I am saying that.

Why does that surprise you? It seems to me to be wholly consistent with the other decisions you said you were involved in making -- decisions which to me amount to saying it will always be safe and correct to do a simple search upwards for a package.json file.

It surprises me because "exports" was specifically designed to only be respected at package boundaries. From the outside of a non-package-boundary directory, you can't require or import the contents of that directory in a way that respects "exports" (unlike "main").

Well the moment you create a package.json you've created a package boundary haven't you? It's a bit squirrely since I have no idea what nested packages even really mean, but it's a boundary for the interior package. Since the prominent practical application of nested pacakges is monorepos it's usually the interior package that's the "real" package, and thus it's the one whose boundary we care about. But the same principle could then nest into itself again, making a package in a package in a package, and really it would be the innermost package that was "real" to files inside it, even if it had no name. But with no name, there would also be no way to access the package or its exports from the outside.

A package is something you can publish and put in another project's package.json - it's not demarcated merely by the presence of a package.json file.

...so to sum up I'm not supposed to be able to make this exports object mean anything because this isn't a package in the technical sense (only in the sense of having a package.json file), but I can do an end-run around that by importing into a file inside the non-package package which uses a self-reference to access the exports.

How bad a problem is that?

It will likely cause user confusion, and it makes things much much more complex for tooling (like jest, resolve, etc) for minimal benefit to the user.

I was a bit wrong actually -- you can't even self-reference a package with no name. It's just one of those things that you shouldn't do and it's not clear why you would. Add it to all the other ways you can hurt yourself if you don't know what you're doing.
As for "something you can publish and put in another project's package.json". Well, you don't have to have something publishable to have a usable "package", and in fact virtually anything can be put into another project's package.json. I just tried using "bitbucket": "/dev/null" as a dep and npm happily created node_modules/bitbucket as a symlink to /dev/null!

Yeah, playing in https://github.com/conartist6/node-self-ref-test I see

bar passing, foo failing
removing name from bar/package.json makes both fail
deleting bar/package.json makes bar fail and foo pass

So to me logic look like

find closest package.json
if name matches and exports is present, use it
otherwise, go to normal node_modules resolution

I don't think exports should be check, but instead allows It to work with main field too.

Not from my testing, if main and no exports it's ignored

https://github.com/facebook/jest/releases/tag/v28.0.0-alpha.9


Hide all Overlays on cutscenes and loading screens?

Tried searching and couldn't find anything regarding if this was already a feature or possible? Basically what I'm referring to is the entire add on hiding iteself during cut scenes and loading screens. If not, maybe a suggestion for visual appearance? Love the project btw and really appreciate everyones hard work. <3

We can add this as an option, but we have to make sure it's an option because some users use Blish HUD while waiting for loading screens or while on the character select (which we can't detect the difference between character select, loading screens, and cut scenes).

We could spin out 'dynamic HUD' into a separate section in the settings and add this to it.


descriptors: add unsigned tx max size helper

This is a first step towards resolving #880.
It adds a helper function to LianaDescriptor that calculates the max size of an unsigned transaction after satisfaction,  assuming all transaction inputs are from that descriptor.
Separately, I use this new helper function in spend and commands modules (I can drop/squash these commits as required).

Oh, btw, the commit separation in this PR was neat.


Forecasted Grants

Why is this issue important?
Partner request and key area where grant finder returns less results than grants.gov as we don't include Forecasted grants in results
Current State
No forecasted grants are ingested to grant finder and therefore are not included in search
Expected State
Issue 330 exists for ingest
This ticket currently focused on what fields we want to bring in for forecasted grants and how we want them to display.
Action Items for scoping

[x] Confirm that only item on Search that needs to change is adding "Forecasted" option to the Opportunity Status field
[x] Determine how dates should display on results table for Forecasted - discussed that we want to rename "Open Date" field to show something like "Open Date (or Estimated Post Date)" and for the latter to display for posted. TBD we if we also  want to adapt the "Close Date" column to show either Close Date or "Estimated Application Due Date" for Forecasted. Caitlin also considering when doing mock-ups whether status column should display differently (i.e. combined w one of the date fields?)
[x] What new content should display on grant details page? Estimated Post Date and Estimated Application Due Date.
[x] @caitlinwinner (or design vols) to draft wireframes for results table and grant detail page

Implementation Plan
The following functions need to be added...
Relevant Code Snippets
No response

@caitlinwinner fyi that I scheduled a meeting next week to discuss this one with me, you, and Pari, but flagging for you here as well in case you have initial thoughts on the open questions listed above

Next step on this issue is to add design mock-ups and update requirements on the issue accordingly

Designs : https://www.figma.com/file/N1wuvwvciNhdKZNSdomTqn/Forecasted?type=design&node-id=0%3A1&mode=design&t=XfCrk3DmM98qakJR-1

acceptance criteria needs to be fleshed out and compared with #2066

Need to add details on how 'est' dates will sort
Also confirm that "see details" dates shows at the end when sorted
*designs need to be updated to show current grant details page & ensure that requirements align

estimated close dates should sort in with regular dates. so est. 5/5/25 would be next to est 5/5/25
see details should sort above not yet posted but below all dates
designs updated at the same link above

@ClaireValdivia regarding "For any new search, Forecasted should be defaulted to be checked" -> does this mean that we still only want to show posted grants on initial page load? We don't want to show forecasted grants when the table is first loaded, is this correct?

@masimons good catch! i think it would make sense to have both posted and forecasted show for "all grants", but curious for thoughts on if this would impact the load time of the page significantly if there are more total grants to load?

@ClaireValdivia Since we are paginating, the load time should be the same as it is now per page. There will just be more pages to click through, as there will be more grants. But as far as I can tell, there is currently a max of 50 records retrieved for the grants table per page.

awesome thank you! I'll adjust the requirements to reflect:

all grants should display posted + forecasted
default sort should be to display chronologically by created date with the most recently created displaying first

@ClaireValdivia regarding "If opp status = forecasted and Estimated Application Due Date is blank in grants.gov - then display "Not yet issued" in the Close Date column" - shall we display "Not yet issued" for any grant that has a blank posted date, not just forecasted grants? Or do we actively prefer for posted grants without a close date to not display anything? (I imagine that the happy path for posted grants is that they always have a non-blank close date, but just trying to consider consistency for the edge cases)

@masimons ah, I think it's addressed in a different bullet in that section: "If close date is blank AND opp status = posted - then display "Not yet issued" in the Close Date column" - does that address your question?

@ClaireValdivia yes! sorry - thanks for the quick response. I have a color-coded google doc to keep track of these specs, and I miscolored it!

https://github.com/usdigitalresponse/usdr-gost/pull/3346
Regarding "if opp status = Posted, Archived, or Closed, and Close Date is anything other than a date or blank, display: "see details" in the Close Date column" - from what I'm seeing, close_date in the database is a date type, which would mean that the close date would never be anything other than a date or blank. Is there an example of a grant we have on prod where we are seeing the close date as something other than blank or a date?
I did notice a field close_date_explanation on the grants table - would it make sense to display "See details" if:

the close_date is blank, and close_date_explanation is not blank?

Hmm this may be a case of me not knowing where things pull from in the table currently. This is an example of a grant where the close date is not a date: https://staging.grants.usdr.dev/grants/103313 -- is the text in the close date field pulling from close_date_explanation?

Hey @ClaireValdivia ! It looks like right now, on the grant details page, we are showing the close_date_explanation when we don't have a date - and if we also don't have any text for close_date_explanation, we show the default text "Not available".
Would we want to mirror this logic for the forecasted grants as well, on the grants detail page?
Separately though, for the grants table, I'm not seeing any logic around displaying alternate text (like "See details") if there's no close date (I believe this is because we force a display date  - 1/1/2100). So, regarding forecasted grants that don't have a close date, would we want to show "See details" if that grant has a non-blank close_date_explanation? And if the forecasted grant has both a blank close date and a blank close_date_explanation, shall we display "Not yet issued"? This text would show up in the grants table, under the Close Date column, to be clear.

@ClaireValdivia Thank you for talking this through with me!
Ok, that all sounds great. And, just to make sure I also understand what to do in the case that there is a blank close date/estimated application due date, but a non-blank close date explanation, shall I display "See details" under the Close Date column of the table? Regardless of opp status?
(In the grant details page, I will just display the full text of the close date explanation)

Yes, that is correct, @masimons!


Add hands class to target all hands

Right now the hand classes do not have a single SVG class to target them all, just individual ones. It's necessary to have a single class that targets all hand positions together so they can be animated up/down alongside the body.

Right now there is the class gotchi-handsDownOpen which targets both hands down and open.
And there is the class gotchi-handsUp that targets both hands up.
The gotchi-handsDownClosed class targets both hands down and closed.

Great, thanks.


WIP: Add interface for reflecting "magic" HLSL counter buffers.

Merging this is pending that glslang settles for this identifier format.

Hi, can we get this merged in please? The glslang implementation is in mainline now.


Plist values automatically revert after 5-10 seconds

I'm trying to update /Users/username/Library/Preferences/com.apple.ncprefs.plist but the change only sticks for 5-10 seconds before being reverted to the original value.
Can this caused by node-simple-plist, or is it something else? I'm running it on Big Sur
const plist = require('simple-plist')
const PATH = '/Users/username/Library/Preferences/com.apple.ncprefs.plist'

const data = plist.readFileSync(PATH)
data.apps[2].flags = newFlagsValue // I verified that the new value is valid
plist.writeBinaryFileSync(PATH, data)

That's actually caused by the CFPreferences daemon (cfprefsd). PlistBuddy would have the same issue. If you want to make modifications to files like these, you can use the defaults cli tool.
Here's a post from Greg Neagle from back in 2013 talking about the issue when it was being recognized by the mac admin community: https://www.jamf.com/jamf-nation/discussions/9052/default-dock-for-mavericks#responseChild49180

Ahh thank you @wollardj!


Make snapshot deployment work with travis.

I have fixed the same issue in dependency-injection-checks in this commit:
https://github.com/groupon/dependency-injection-checks/commit/234f330b35c7b1974809c7da4169998da89343bb
travis secret is creating a bash environment variable, you need to reference that in gradle to make uploadArchives work.

created a PR for this:
https://github.com/groupon/grox/pull/23


Cannot read property 'kind' of undefined error is shown when deselecting some text

monaco-editor version: 0.10.1
Browser: Google Chrome
OS: Windows 10

Open the Monaco Playground: https://microsoft.github.io/monaco-editor/playground.html
Add some comment block to the default javascript code so that the final model looks like this:

function hello() {
  alert('Hello world!');
}
/*
NativeScript adheres to the CommonJS specification for dealing with
JavaScript modules. The CommonJS require() function is how you import
JavaScript modules defined in other files.
*/

Select a portion of the text as shown in the attached video and click outside to deselect it

Actual result: The text is deselected but the following error is printed to the browser console:
Uncaught Error: Cannot read property 'kind' of undefined

TypeError: Cannot read property 'kind' of undefined
    at Object._t [as isJsxOpeningElement] (typescriptServices.js:33)
    at Object.r [as getDocumentHighlights] (typescriptServices.js:59)
    at C (typescriptServices.js:65)
    at D (typescriptServices.js:65)
    at Object.x [as getOccurrencesAtPosition] (typescriptServices.js:65)
    at e.getOccurrencesAtPosition (worker.js:9)
    at t.e.fmr (workerMain.js:7)
    at t._handleMessage (workerMain.js:7)
    at Object.handleMessage (workerMain.js:7)
    at e._handleMessage (workerMain.js:7)
    at Object._t [as isJsxOpeningElement] (typescriptServices.js:33)
    at Object.r [as getDocumentHighlights] (typescriptServices.js:59)
    at C (typescriptServices.js:65)
    at D (typescriptServices.js:65)
    at Object.x [as getOccurrencesAtPosition] (typescriptServices.js:65)
    at e.getOccurrencesAtPosition (worker.js:9)
    at t.e.fmr (workerMain.js:7)
    at t._handleMessage (workerMain.js:7)
    at Object.handleMessage (workerMain.js:7)
    at e._handleMessage (workerMain.js:7)
    at editor.main.js:31

Expected result: The text is deselected without errors
Repro demo:

P.S. The same error also happens in TypeScript files.

I also encountered such a problem.
#615

Upstream issue - https://github.com/Microsoft/TypeScript/issues/17245
Fixed by adopting TS 2.7.2 -- https://github.com/Microsoft/monaco-typescript/commit/4514e58f07deefea088fcd44beb4be685135c6fa

@jagenjo What version of the editor are you using?


Not working on Raspberry Pi 2

It seems the conversion silently fails on Rpi2, it is probably related to pdf2htmlex that has been manually compiled on a Rpi1 some times ago.

Tested on Raspberry Pi 2 V1.1, working.

#23

Looks like this can be closed since we don't use pdf2html anymore.


added organization event management system under GSSOC2022

Have you read the Contributing Guidelines ?
yes
Description
added event management system
Fixes #485

Checklist

[X] I've read the contribution guidelines.
[X] I've checked the issue list before deciding what to submit.
[X] I've edited the README.md and link to my code.

Related Issues or Pull Requests
(Write your answer here.)

done @Kushal997-das

Looks good to me. No Duplicity ✔ @Kushal997-das Please review once and recheck the path once as well.

Everything is looks correct please approve it @photon149

@prakhar3062 have a look .