<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Issue with os and sys Operations in Repo Path on Databricks in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75842#M35074</link>
    <description>&lt;P&gt;I think I am experiencing the same issue with workflows that need the internal cluster path to the cloned repo in the cluster. We are using the path to import additional methods for the job. Getting this error "&lt;SPAN class=""&gt;BlockingIOError: [Errno 11] Resource temporarily unavailable: '/Workspace/Repos/.internal/&lt;/SPAN&gt;....'"&lt;/P&gt;</description>
    <pubDate>Wed, 26 Jun 2024 12:28:57 GMT</pubDate>
    <dc:creator>jdev220999</dc:creator>
    <dc:date>2024-06-26T12:28:57Z</dc:date>
    <item>
      <title>Issue with os and sys Operations in Repo Path on Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75836#M35072</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Starting from today, I have encountered an issue when performing operations using the os and sys modules within the Repo path in my Databricks environment. Specifically, any operation that involves these modules results in a timeout error. However, when I use os.chdir or other os and sys operations outside of the Repo path, everything functions as expected.&lt;/P&gt;&lt;P&gt;Could you please assist in diagnosing and resolving this issue? It is impacting my workflow significantly, and I need a solution as soon as possible.&lt;/P&gt;&lt;P&gt;Thank you for your support and assistance.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jun 2024 11:59:41 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75836#M35072</guid>
      <dc:creator>pm71</dc:creator>
      <dc:date>2024-06-26T11:59:41Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with os and sys Operations in Repo Path on Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75842#M35074</link>
      <description>&lt;P&gt;I think I am experiencing the same issue with workflows that need the internal cluster path to the cloned repo in the cluster. We are using the path to import additional methods for the job. Getting this error "&lt;SPAN class=""&gt;BlockingIOError: [Errno 11] Resource temporarily unavailable: '/Workspace/Repos/.internal/&lt;/SPAN&gt;....'"&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jun 2024 12:28:57 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75842#M35074</guid>
      <dc:creator>jdev220999</dc:creator>
      <dc:date>2024-06-26T12:28:57Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with os and sys Operations in Repo Path on Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75847#M35078</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Error from FUSE process during `ls /Workspace`:&lt;BR /&gt;&lt;BR /&gt;2024/06/26 11:15:39.286089 workspace.WARNING [CP] ResponseLogHook: databricks api &lt;A href="https://westeurope-c2.azuredatabricks.net/api/2.0/workspace-files/list-files" target="_blank" rel="noopener nofollow noreferrer"&gt;https://westeurope-c2.azuredatabricks.net/api/2.0/workspace-files/list-files&lt;/A&gt;: 504 Gateway Timeout. body:{"error_code":"TEMPORARILY_UNAVAILABLE","message":"The service at /api/2.0/workspace-files/list-files is taking too long to process your request. Please try again later or try a faster operation. [TraceId: 00-0a794387a987fc4de1cb8a6b70214774-97e61adb2ab644d5-00]"}&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jun 2024 12:46:13 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75847#M35078</guid>
      <dc:creator>mgradowski</dc:creator>
      <dc:date>2024-06-26T12:46:13Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with os and sys Operations in Repo Path on Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75848#M35079</link>
      <description>&lt;P&gt;&lt;A href="https://status.azuredatabricks.net/pages/incident/5d49ec10226b9e13cb6a422e/667c08fa17fef71767abda04" target="_blank"&gt;https://status.azuredatabricks.net/pages/incident/5d49ec10226b9e13cb6a422e/667c08fa17fef71767abda04&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;"Degraded performance" is a pretty mild way of saying almost nothing productve can be done ATM...&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jun 2024 12:49:40 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75848#M35079</guid>
      <dc:creator>mgradowski</dc:creator>
      <dc:date>2024-06-26T12:49:40Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with os and sys Operations in Repo Path on Databricks</title>
      <link>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75849#M35080</link>
      <description>&lt;P&gt;Yep, just saw it. Nothing to do but waiting...&lt;/P&gt;</description>
      <pubDate>Wed, 26 Jun 2024 12:50:56 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/issue-with-os-and-sys-operations-in-repo-path-on-databricks/m-p/75849#M35080</guid>
      <dc:creator>pm71</dc:creator>
      <dc:date>2024-06-26T12:50:56Z</dc:date>
    </item>
  </channel>
</rss>

